OSN 7500 II&7500&3500&1500 V200R011C02 Feature Description (Packet Transport Domain) 03

OptiX OSN 7500 II/7500/3500/1500
V200R011C02
Feature Description (Packet

Transport Domain)
Issue
03
Date
2012-11-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 03 (2012-11-30)
Huawei Proprietary and Confidential

Copyright Huawei Technologies Co., Ltd.
OptiX OSN 7500 II/7500/3500/1500

Feature Description (Packet Transport Domain)
About This Document
About This Document

Related Versions
The following table lists the product versions related to this document.
Product Name
Version
OptiX OSN 7500 II
V200R011C02
OptiX OSN 7500
V200R011C02
OptiX OSN 3500
V200R011C02
OptiX OSN 1500
V200R011C02
iManager U2000
V100R005
Intended Audience
This document describes the features and functions of the OptiX OSN 7500II/7500/3500/1500
equipment, in terms of basic concepts, availability, implementing principles, applications,
configuration, and troubleshooting.
After reading this document, you can deeply understand these features and functions. Moreover,
you can configure these features and functions on the U2000, and learn about the methods of
troubleshooting these features and functions on the U2000.
This document is intended for:
l
Installation and Commissioning Engineer
Data Configuration Engineer
Symbol Conventions
The symbols that may be found in this document are defined as follows.
Issue 03 (2012-11-30)

ii
OptiX OSN 7500 II/7500/3500/1500

Symbol
About This Document
Description
DANGER
WARNING
CAUTION
Indicates a hazard with a high level of risk, which if not

avoided, will result in death or serious injury.
Indicates a hazard with a medium or low level of risk, which
if not avoided, could result in minor or moderate injury.
Indicates a potentially hazardous situation, which if not
avoided, could result in equipment damage, data loss,
performance degradation, or unexpected results.
TIP
Indicates a tip that may help you solve a problem or save

time.
NOTE
Provides additional information to emphasize or supplement

important points of the main text.
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
Updates between document issues are cumulative. Therefore, the latest document issue contains
all updates made in previous issues.
Updates in Issue 03 (2012-11-30) Based on Product Version V200R011C02

This document of the V200R011C02 version is of the third release. Compared with Issue 02,
Issue 03 includes the following updates in V200R011C02SPC106:
l
"SNMP" is added in "RMON".
"Feature Dependency and Limitation" is modified in "Link Aggregation".

This document of the V200R011C02 version is of the second release. Compared with the first
release, this version has the following optimized contents:
Issue 03 (2012-11-30)

iii
OptiX OSN 7500 II/7500/3500/1500

About This Document
"Availability" is optimized for each feature.
T2PSXCSA is deleted in "Availability" of "HWECC Solution", "Hybrid Networking

Solution of DCC Transparent Transmission", "IP over DCC Solution", and "OSI over DCC
Solution".
The "PW FRR" is modified to "PW FPS".

This document of the V200R011C02 version is of the first release. Compared with
V200R011C01, this version has the following new or optimized contents:
l
The description about the OptiX OSN 3500 and OptiX OSN 7500 supporting "ATM
PWE3", "ATM QoS", and "ATM OAM" is added. "Availability" is updated.
"Feature Dependency and Limitation" is added for each feature in "Packet Features".
"Specifications" is added for each feature.
"Configuring PW FPS Protection Groups" and "Configuration Example (PW FPS)" are
added in "MPLS PW APS".

l
"MPLS Basics" is added in "Packet Features".
"PWE3 Basics" is added in "Packet Features".
"IMA" is added in "Packet Features".
"ETH PWE3" is added in "Packet Features".
"PW FPS Protection" is added in "MPLS PW APS".
"TDM PWE3" is added in "Packet Features".
"CES ACR" is added in "Clock Solution".

This document of the V200R011C01 version is of the first release. Compared with
V200R011C00, this version has the following new or optimized contents:
l
OptiX OSN 7500 II is added.
"ATM PWE3" is added in "Packet Features".
"ATM Traffic Management" is added in "Packet Features".
"ATM OAM" is added in "O&M Solutions".
"IGMP Snooping" is added in "Packet Features".
"Packet-based linear MSP" is added in "Packet Features".
"Protection Solutions for a 3G Bearer Network" is added.

Issue 03 (2012-11-30)

iv
OptiX OSN 7500 II/7500/3500/1500

"MC-LAG" is optimized.
"MPLS PW APS" is optimized.
"MS-PW" is optimized.
"ETH-OAM" is optimized.
"MPLS OAM" is optimized.
About This Document

This document of the V200R011C00 version is of the first release.
Issue 03 (2012-11-30)

OptiX OSN 7500 II/7500/3500/1500

Contents
Contents
About This Document.....................................................................................................................ii
1 MPLS Basics...................................................................................................................................1
1.1 Introduction........................................................................................................................................................2
1.2 Basic Concepts...................................................................................................................................................2
1.2.1 MPLS Network Architecture.....................................................................................................................3
1.2.2 LSP............................................................................................................................................................3
1.2.3 Bearer Mode for MPLS Packets................................................................................................................5
1.2.4 MPLS Label...............................................................................................................................................6
1.3 Reference Standards and Protocols....................................................................................................................7
1.4 Availability.........................................................................................................................................................8
1.5 Principles............................................................................................................................................................9
2 PWE3..............................................................................................................................................12
2.1 PWE3 Basics....................................................................................................................................................13
2.1.1 Introduction.............................................................................................................................................13
2.1.2 Basic Concepts........................................................................................................................................13
2.1.2.1 PWE3 Network Reference Model..................................................................................................14
2.1.2.2 PWE3 Protocol Reference Model...................................................................................................15
2.1.2.3 PWE3 Encapsulation Format..........................................................................................................17
2.1.2.4 MS-PW...........................................................................................................................................18
2.1.2.5 VCCV.............................................................................................................................................20
2.1.3 Reference Standards and Protocols.........................................................................................................21
2.1.4 Availability..............................................................................................................................................21
2.1.5 Principles.................................................................................................................................................23
2.1.5.1 Packet Forwarding Process of SS-PW............................................................................................23
2.1.5.2 Packet Forwarding Process of MS-PW..........................................................................................24
2.2 ATM PWE3......................................................................................................................................................25
2.2.1 Introduction.............................................................................................................................................25
2.2.2 Basic Concepts........................................................................................................................................26
2.2.2.1 ATM N-to-One Cell Encapsulation................................................................................................26
2.2.2.2 ATM One-to-One Cell Encapsulation............................................................................................28
2.2.2.3 Number of ATM Cells Encapsulated in PWE3 Packets.................................................................30
2.2.2.4 QoS of ATM PWE3.......................................................................................................................31
Issue 03 (2012-11-30)

vi
OptiX OSN 7500 II/7500/3500/1500

Contents
2.2.3 Specifications...........................................................................................................................................31
2.2.5 Availability..............................................................................................................................................34
2.2.6 Feature Dependency and Limitation........................................................................................................34
2.2.7 Principles.................................................................................................................................................38
2.2.8 Configuring ATM PWE3........................................................................................................................40
2.2.9 Configuration Example............................................................................................................................40
2.2.10 Relevant Alarms and Performance Events............................................................................................40
2.2.10.1 Relevant Alarms...........................................................................................................................40
2.2.10.2 Relevant Performance Events.......................................................................................................41
2.2.11 Parameter Description...........................................................................................................................41
2.2.11.1 Creating an ATM Service.............................................................................................................41
2.2.11.2 Connection....................................................................................................................................43
2.2.11.3 SDH Ports.....................................................................................................................................46
2.3 ETH PWE3.......................................................................................................................................................49
2.3.1 Introduction.............................................................................................................................................49
2.3.2 Basic Concepts........................................................................................................................................50
2.3.2.1 Format of an ETH PWE3 Packet....................................................................................................50
2.3.2.2 PW Encapsulation Mode................................................................................................................51
2.3.2.3 QoS of ETH PWE3.........................................................................................................................53
2.3.2.4 E-Line Services Carried on PWs....................................................................................................53
2.3.4 Availability..............................................................................................................................................56
2.3.6 Principles.................................................................................................................................................59
2.3.7 Configuration Example............................................................................................................................60
2.4 TDM PWE3......................................................................................................................................................60
2.4.1 Introduction.............................................................................................................................................60
2.4.2 Basic Concepts........................................................................................................................................61
2.4.2.1 E1 Frame Format............................................................................................................................61
2.4.2.2 SAToP............................................................................................................................................63
2.4.2.3 CESoPSN........................................................................................................................................66
2.4.2.4 Data Jitter Buffer............................................................................................................................69
2.4.2.5 CES Alarm Transmission...............................................................................................................70
2.4.2.6 Clock Recovery Schemes of TDM PWE3.....................................................................................71
2.4.2.7 QoS of TDM PWE3.......................................................................................................................72
2.4.3 Specifications...........................................................................................................................................73
2.4.5 Availability..............................................................................................................................................74
2.4.7 Principles.................................................................................................................................................78
3 ATM OAM....................................................................................................................................79
Issue 03 (2012-11-30)

vii
OptiX OSN 7500 II/7500/3500/1500

Contents
3.1 Introduction......................................................................................................................................................80
3.2 Basic Concepts.................................................................................................................................................80
3.2.1 ATM OAM Levels..................................................................................................................................80
3.2.2 Segment and End Attributes and Directions of CPs................................................................................81
3.2.3 ATM OAM Functions.............................................................................................................................83
3.3 Reference Standards and Protocols..................................................................................................................85
3.4 Availability.......................................................................................................................................................85
3.5 Feature Dependency and Limitation.................................................................................................................86
3.6 Principles..........................................................................................................................................................87
3.6.1 AIS/RDI...................................................................................................................................................87
3.6.2 CC............................................................................................................................................................89
3.6.3 LB............................................................................................................................................................90
3.7 Configuring ATM OAM..................................................................................................................................91
3.7.1 Setting Segment End Attribute................................................................................................................91
3.7.2 Setting the CC Activation Status.............................................................................................................92
3.7.3 Setting Local Loopback ID......................................................................................................................93
3.7.4 Setting a Remote Loopback Test.............................................................................................................94
3.7.5 Configuring ATM Alarm Transmission..................................................................................................95
3.8 Configuration Example.....................................................................................................................................95
3.8.1 Example Description...............................................................................................................................95
3.8.2 Configuration Process..............................................................................................................................97
3.9 Relevant Alarms and Performance Events.......................................................................................................99
3.9.1 Relevant Alarms......................................................................................................................................99
3.9.2 Relevant Performance Events................................................................................................................100
3.10 Parameter Description..................................................................................................................................100
3.10.1 Segment and End Attributes................................................................................................................100
3.10.2 CC Activation Status...........................................................................................................................101
3.10.3 Remote Loopback Test........................................................................................................................103
3.10.4 LLID....................................................................................................................................................105
3.10.5 Insert OAM Cell to ATM....................................................................................................................106
4 ATM Traffic Management.......................................................................................................107

4.1 Introduction....................................................................................................................................................108
4.2 Basic Concepts...............................................................................................................................................108
4.2.1 ATM Traffic Parameters.......................................................................................................................108
4.2.2 ATM Service Categories.......................................................................................................................110
4.2.3 ATM Traffic Categories........................................................................................................................111
4.2.4 ATM Traffic Control Schemes..............................................................................................................112
4.3 Reference Standards and Protocols................................................................................................................113
4.4 Availability.....................................................................................................................................................113
4.5 Feature Dependency and Limitation...............................................................................................................114
4.6 Principles........................................................................................................................................................115
4.7 Configuring ATM QoS...................................................................................................................................124
Issue 03 (2012-11-30)

viii
OptiX OSN 7500 II/7500/3500/1500

Contents
4.7.1 Configuring ATM CoS Mapping..........................................................................................................124

4.7.2 Creating the ATM Policy......................................................................................................................126
4.8 QoS Configuration Case of ATM Services....................................................................................................127
4.8.1 Case Description....................................................................................................................................127
4.8.2 Configuration Process............................................................................................................................129
4.9 Parameter Description: ATM QoS.................................................................................................................131
4.9.1 CoS Mapping.........................................................................................................................................131
4.9.2 Configuring an ATM Service Class Mapping Table.............................................................................132
4.9.3 ATM Policies.........................................................................................................................................133
5 IMA.............................................................................................................................................. 139
5.1 Introduction....................................................................................................................................................141
5.2 Basic Concepts...............................................................................................................................................142
5.2.1 IMA Protocol Reference Model............................................................................................................142
5.2.2 IMA OAM Cells....................................................................................................................................142
5.2.3 IMA Frame Format................................................................................................................................145
5.2.4 IMA Timing...........................................................................................................................................147
5.4 Availability.....................................................................................................................................................148
5.6 Principles........................................................................................................................................................151
5.7 Configuration Procedure.................................................................................................................................151
5.8 Configuring IMA............................................................................................................................................152
5.8.1 Binding ATM TRUNKs........................................................................................................................152
5.8.2 Configuring an IMA Group...................................................................................................................154
5.8.3 Configuring ATM Interface Management Attributes............................................................................154
5.8.4 Querying Running Status of an IMA Group.........................................................................................155
5.8.5 Querying Link Running Status of an IMA Group.................................................................................155
5.8.6 Resetting an IMA Group.......................................................................................................................156
5.8.7 Modifying an IMA Group.....................................................................................................................156
5.8.8 Deleting an IMA Group.........................................................................................................................157
5.9 Configuration Example...................................................................................................................................157
5.9.1 Network Diagram..................................................................................................................................157
5.9.2 Service Planning....................................................................................................................................158
5.10 Relevant Alarms and Performance Events...................................................................................................160
5.10.1 Relevant Alarms..................................................................................................................................160
5.10.2 Relevant Performance Events..............................................................................................................162
5.11 Parameter Description..................................................................................................................................162
5.11.1 Configuring Bound Paths....................................................................................................................162
5.11.2 IMA Group Management....................................................................................................................164
5.11.3 ATM Port Management.......................................................................................................................169
5.11.4 IMA Group Status...............................................................................................................................170
Issue 03 (2012-11-30)

ix
OptiX OSN 7500 II/7500/3500/1500

Contents
5.11.5 IMA Link Status..................................................................................................................................171
6 ETH-OAM...................................................................................................................................175
6.1 Introduction to ETH-OAM.............................................................................................................................176
6.2 Ethernet Port OAM.........................................................................................................................................177
6.2.1 Basic Concepts......................................................................................................................................177
6.2.2 Reference Standards and Protocols.......................................................................................................178
6.2.3 Availability............................................................................................................................................178
6.2.4 Feature Dependency and Limitation......................................................................................................180
6.2.5 Principle Description.............................................................................................................................180
6.2.5.1 OAM Auto-Discovery..................................................................................................................180
6.2.5.2 Link Performance Monitoring......................................................................................................183
6.2.5.3 Remote Fault Detection................................................................................................................185
6.2.5.4 Remote Loopback.........................................................................................................................186
6.2.5.5 Selfloop Test.................................................................................................................................187
6.2.6 Networking and Application.................................................................................................................188
6.2.7 Configuring Ethernet Port OAM...........................................................................................................189
6.2.7.1 Setting the MAC Address for a Board..........................................................................................190
6.2.7.2 Enabling the Auto-Discovery Function of Ethernet Port OAM...................................................191
6.2.7.3 Configuring the Remote Alarm Support for Link Event..............................................................192
6.2.7.4 Setting OAM Error Frame Monitoring Parameters......................................................................193
6.2.7.5 Configuring the Remote Loopback..............................................................................................193
6.2.7.6 Enabling Self-Loop Detection......................................................................................................194
6.2.8.1 Relevant Alarms...........................................................................................................................195
6.2.9 Parameter Description: Ethernet Port OAM..........................................................................................196
6.2.9.1 OAM Parameters..........................................................................................................................196
6.2.9.2 Remote OAM Parameters.............................................................................................................197
6.2.9.3 OAM Error Frame Monitoring.....................................................................................................198
6.3 Ethernet Service OAM...................................................................................................................................200
6.3.1 Basic Concepts......................................................................................................................................200
6.3.2 Reference Standards and Protocols.......................................................................................................203
6.3.3 Availability............................................................................................................................................203
6.3.4 Feature Dependency and Limitation......................................................................................................205
6.3.5 Principle Description.............................................................................................................................208
6.3.5.1 Continuity Check..........................................................................................................................209
6.3.5.2 Loopback Test..............................................................................................................................210
6.3.5.3 Link Trace Test.............................................................................................................................210
6.3.5.4 Performance Detection.................................................................................................................212
6.3.6 Networking and Application.................................................................................................................215
6.3.7 Configuring Ethernet Service OAM......................................................................................................217
6.3.7.1 Creating an MD............................................................................................................................217
Issue 03 (2012-11-30)

OptiX OSN 7500 II/7500/3500/1500

Contents
6.3.7.2 Creating an MA............................................................................................................................218

6.3.7.3 Creating an MEP..........................................................................................................................218
6.3.7.4 Adding a Remote MEP.................................................................................................................219
6.3.7.5 Performing a Continuity Check....................................................................................................219
6.3.7.6 Performing an LB Test.................................................................................................................220
6.3.7.7 Performing an LT Test.................................................................................................................221
6.3.8.1 Relevant Alarms...........................................................................................................................222
6.3.9 Parameter Description: Ethernet Service OAM....................................................................................224
6.3.9.1 Ethernet Service OAM Management...........................................................................................224
6.3.9.2 Starting LB...................................................................................................................................226
6.3.9.3 Starting LT....................................................................................................................................227
7 MPLS OAM................................................................................................................................ 230

7.1 Introduction to MPLS OAM...........................................................................................................................232
7.2 Basic Concepts...............................................................................................................................................233
7.2.1 Packet Types..........................................................................................................................................233
7.2.2 Reverse Tunnel......................................................................................................................................235
7.2.3 Ping........................................................................................................................................................235
7.2.4 Traceroute..............................................................................................................................................236
7.4 Availability.....................................................................................................................................................237
7.6 Principles........................................................................................................................................................241
7.7 Networking and Application..........................................................................................................................244
7.8 Configuring the MPLS OAM.........................................................................................................................244
7.8.1 Enabling MPLS Tunnel OAM...............................................................................................................245
7.8.2 Setting the MPLS Tunnel OAM Parameters.........................................................................................245
7.8.3 Starting a CV/FFD for an MPLS Tunnel...............................................................................................246
7.8.4 Performing an MPLS Tunnel Ping Test................................................................................................247
7.8.5 Performing an MPLS Tunnel Traceroute Test......................................................................................248
7.9 Configuring PW OAM...................................................................................................................................249
7.9.1 Enabling PW OAM...............................................................................................................................249
7.9.2 Setting the Parameters of PW OAM......................................................................................................249
7.9.3 Performing a PW Ping Test...................................................................................................................250
7.9.4 Performing a PW Traceroute Test.........................................................................................................251
7.10 Configuration Case of the MPLS OAM.......................................................................................................252
7.10.1 Case Description..................................................................................................................................252
7.10.2 Configuration Process..........................................................................................................................254
7.11 Configuration Example of PW OAM...........................................................................................................254
7.11.1 Description of the Example.................................................................................................................254
Issue 03 (2012-11-30)

xi
OptiX OSN 7500 II/7500/3500/1500

Contents
7.12 Parameter Description: MPLS OAM...........................................................................................................256

7.12.1 Tunnel OAM Parameters.....................................................................................................................256
7.12.2 PW OAM Parameters..........................................................................................................................259
7.12.3 Ping Test..............................................................................................................................................262
7.12.4 Traceroute Test....................................................................................................................................262
7.13 Related Alarms and Performance Events.....................................................................................................263
7.13.1 Related Alarms....................................................................................................................................263
7.13.2 Related Performance Events................................................................................................................265
8 HQoS............................................................................................................................................266
8.1 Introduction....................................................................................................................................................268
8.2 Basic Concepts...............................................................................................................................................268
8.2.1 QoS Requirements.................................................................................................................................268
8.2.2 DiffServ.................................................................................................................................................269
8.2.3 Traffic Classification.............................................................................................................................273
8.2.4 Queue Scheduling..................................................................................................................................273
8.2.5 Committed Access Rate.........................................................................................................................275
8.2.6 Congestion Management.......................................................................................................................276
8.2.7 QoS Policy.............................................................................................................................................276
8.3 Specifications..................................................................................................................................................277
8.5 Availability.....................................................................................................................................................279
8.7 Principles........................................................................................................................................................285
8.7.1 Traffic Policing......................................................................................................................................285
8.7.2 QoS Model.............................................................................................................................................288
8.9 Configuring the HQoS....................................................................................................................................290
8.9.1 HQoS Configuration Flow.....................................................................................................................290
8.9.2 Creating the DiffServ Domain...............................................................................................................293
8.9.3 Creating the Port WRED Policy (OptiX OSN 1500)............................................................................294
8.9.4 Creating a Service WRED Policy..........................................................................................................294
8.9.5 Creating the WFQ Scheduling Policy...................................................................................................295
8.9.6 Creating the Port Policy (OptiX OSN 3500/7500/7500 II)...................................................................296
8.9.7 Creating the Port Policy (OptiX OSN 1500).........................................................................................297
8.9.8 Creating the V-UNI Ingress Policy (OptiX OSN 3500/7500/7500 II)..................................................298
8.9.9 Creating the V-UNI Ingress Policy (OptiX OSN 1500)........................................................................299
8.9.10 Creating a V-UNI Egress Policy.........................................................................................................300
8.9.11 Creating the PW Policy (OptiX OSN 3500/7500/7500 II)..................................................................301
8.9.12 Creating the QinQ Policy....................................................................................................................303
8.9.13 Creating the CAR Policy (OptiX OSN 1500).....................................................................................304
8.10 Configuration Example.................................................................................................................................304
Issue 03 (2012-11-30)

xii
OptiX OSN 7500 II/7500/3500/1500

Contents

8.11 Troubleshooting............................................................................................................................................310
8.12 Parameter Description: HQoS......................................................................................................................313
8.12.1 Diffserv Domain Management............................................................................................................313
8.12.2 Service WRED Policy.........................................................................................................................315
8.12.3 WFQ Schedule Policy.........................................................................................................................317
8.12.4 Port Policy...........................................................................................................................................320
8.12.5 V-UNI Ingress Policy..........................................................................................................................325
8.12.6 V-UNI Egress Policy...........................................................................................................................331
8.12.7 PW Policy............................................................................................................................................334
8.12.8 QinQ Policy.........................................................................................................................................337
8.13.1 Relevant Alarms..................................................................................................................................340
9 IGMP Snooping.........................................................................................................................341
9.1 Introduction to IGMP Snooping.....................................................................................................................343
9.2 Basic Concepts...............................................................................................................................................344
9.2.1 Multicast Protocol..................................................................................................................................344
9.2.2 IGMP.....................................................................................................................................................344
9.2.3 IGMP Snooping.....................................................................................................................................345
9.4 Availability.....................................................................................................................................................347
9.6 Principle Description......................................................................................................................................349
9.8 Configuring the IGMP Snooping...................................................................................................................351
9.8.1 Setting the IGMP Snooping Parameters................................................................................................351
9.8.2 Configuring the Route Management.....................................................................................................352
9.8.3 Configuring the Route Member Port Management...............................................................................353
9.8.4 Configuring the Packet Statistics...........................................................................................................353
9.9 Configuration Example...................................................................................................................................354
9.9.1 Network Diagram..................................................................................................................................355
9.9.2 Service Planning....................................................................................................................................355
9.11 Parameter Description: IGMP Snooping......................................................................................................358
9.11.1 Protocol Configuration........................................................................................................................358
9.11.2 Router Management............................................................................................................................359
9.11.3 Route Member Port Management........................................................................................................360
9.11.4 Packet Statistics...................................................................................................................................361
10 Link Aggregation.....................................................................................................................363
10.1 Introduction..................................................................................................................................................365
Issue 03 (2012-11-30)

xiii
OptiX OSN 7500 II/7500/3500/1500

Contents
10.2 Basic Concepts.............................................................................................................................................365

10.2.1 LACP...................................................................................................................................................365
10.2.2 Link Aggregation Types......................................................................................................................366
10.2.3 Load Sharing Modes............................................................................................................................367
10.2.4 Port Types............................................................................................................................................368
10.2.5 Priority.................................................................................................................................................368
10.3 Specifications................................................................................................................................................369
10.4 Reference Standards and Protocols..............................................................................................................370
10.5 Availability...................................................................................................................................................371
10.6 Feature Dependency and Limitation.............................................................................................................373
10.7 Principles......................................................................................................................................................375
10.7.1 LAG Establishment Process................................................................................................................375
10.7.2 LAG Link Switchover and Reversion.................................................................................................377
10.8 Configuring a LAG.......................................................................................................................................378
10.8.1 Configuration Procedure......................................................................................................................378
10.8.2 Creating a LAG...................................................................................................................................381
10.8.3 Setting Port Priorities...........................................................................................................................382
10.9 Maintaining a LAG.......................................................................................................................................383
10.9.1 Querying LAG Configuration and Running Information....................................................................383
10.9.2 Querying LAG Information and LACPDU Statistics..........................................................................384
10.9.3 Changing LAG Configurations...........................................................................................................384
10.9.4 Deleting a LAG...................................................................................................................................386
10.10 Configuration Example (LAG Configured to Increase Ethernet Link Bandwidth)...................................387
10.10.1 Example Description.........................................................................................................................387
10.10.2 Configuration Process........................................................................................................................389
10.11 Configuration Example (LAG Configured to Provide Link Protection)....................................................390
10.12 Verifying a LAG.........................................................................................................................................392
10.13 Troubleshooting..........................................................................................................................................394
10.14 Relevant Alarms and Performance Events.................................................................................................396
10.14.1 Relevant Alarms................................................................................................................................396
10.14.2 Relevant Performance Events............................................................................................................397
10.15 Relevant Parameters...................................................................................................................................397
10.15.1 LAG Management_LAG Creation....................................................................................................397
10.15.2 LAG Management_Port Priority Setting...........................................................................................403
10.15.3 LAG Management_LAG Information Query....................................................................................404
11 LPT..............................................................................................................................................407
11.1 Introduction..................................................................................................................................................409
11.2 Basic Concepts.............................................................................................................................................409
11.3 Specifications................................................................................................................................................410
Issue 03 (2012-11-30)

xiv
OptiX OSN 7500 II/7500/3500/1500

Contents
11.5 Availability...................................................................................................................................................411
11.7 Principles......................................................................................................................................................413
11.7.1 LPT State Transition............................................................................................................................414
11.7.2 Point-to-Point LPT Switching.............................................................................................................415
11.7.3 Point-to-Multipoint LPT Switching.....................................................................................................417
11.8 Configuring LPT...........................................................................................................................................422
11.8.2 Configuring Point-to-Point LPT..........................................................................................................425
11.8.3 Configuring Point-to-Multipoint LPT.................................................................................................425
11.9 Maintaining LPT Configurations..................................................................................................................427
11.9.1 Querying Point-to-Point LPT Configurations.....................................................................................427
11.9.2 Changing Point-to-Point LPT Attributes.............................................................................................427
11.9.3 Deleting Point-to-Point LPT Configurations.......................................................................................428
11.9.4 Querying Point-to-Multipoint LPT Configurations.............................................................................428
11.9.5 Changing Primary and Secondary Points for Point-to-Multipoint LPT..............................................429
11.9.6 Changing Point-to-Multipoint LPT Attributes....................................................................................430
11.9.7 Deleting Point-to-Multipoint LPT Configurations..............................................................................431
11.10 Configuration Example (LPT Based on an E-Line Service Exclusively Occupying a UNI Port).............431
11.11 Configuration Example (LPT Based on Ethernet Services Sharing a UNI Port).......................................433
11.12 Verifying LPT.............................................................................................................................................436
11.14.1 Relevant Alarms................................................................................................................................439
11.15 Relevant Parameters...................................................................................................................................440
11.15.1 LPT Management_Point-to-Point LPT.............................................................................................440
11.15.2 LPT Management_Point-to-Multipoint LPT.....................................................................................444
12 MC-LAG....................................................................................................................................446
12.1 Introduction..................................................................................................................................................448
12.2 Basic Concepts.............................................................................................................................................449
12.3 Specifications................................................................................................................................................450
12.5 Availability...................................................................................................................................................451
12.7 Principles......................................................................................................................................................453
12.8 Configuring MC-LAG..................................................................................................................................456
12.8.1 Configuring Multi-chassis Synchronous Communication Tunnel......................................................456
Issue 03 (2012-11-30)

xv
OptiX OSN 7500 II/7500/3500/1500

Contents
12.8.2 Configuring MC-LAGs.......................................................................................................................457

12.10.1 Relevant Alarms................................................................................................................................463
12.11 Parameter Description: MC-LAG..............................................................................................................463
12.11.1 Synchronization Protocol Management.............................................................................................463
12.11.2 Link Aggregation Group Management..............................................................................................464
13 MPLS PW APS.........................................................................................................................468
13.1 Introduction..................................................................................................................................................470
13.2 Basic Concepts.............................................................................................................................................472
13.3 Specifications................................................................................................................................................473
13.5 Availability...................................................................................................................................................475
13.7 Principles......................................................................................................................................................479
13.7.1 State Model..........................................................................................................................................479
13.7.2 PW APS 1+1 Protection......................................................................................................................480
13.7.3 PW APS 1:1 Protection.......................................................................................................................481
13.7.4 PW FPS Protection..............................................................................................................................482
13.7.5 Switching Condition............................................................................................................................484
13.7.6 Switching Impact.................................................................................................................................486
13.8 Configuring PW APS...................................................................................................................................487
13.8.1 Configuring PW APS Protection Groups............................................................................................487
13.8.2 Configuring Slave Protection Pairs of PW APS..................................................................................492
13.8.3 Starting the APS Protocol....................................................................................................................495
13.8.4 Performing External Switching of PW APS........................................................................................495
13.8.5 Configuring PW FPS Protection Groups.............................................................................................496
13.9 Configuration Example (PW APS)...............................................................................................................500
13.9.2 PW APS Configuration Process..........................................................................................................508
13.9.3 PW APS Slave Protection Pair Configuration Process.......................................................................512
13.9.4 Verifying PW APS..............................................................................................................................516
13.10 Configuration Example (PW FPS).............................................................................................................517
13.10.1 Description of the Example...............................................................................................................517
13.10.2 PW FPS Configuration Process.........................................................................................................523
13.10.3 Verifying PW FPS.............................................................................................................................528
13.11.1 Relevant Alarms................................................................................................................................529
Issue 03 (2012-11-30)

xvi
OptiX OSN 7500 II/7500/3500/1500

Contents
13.12 Parameter Description: MPLS PW APS....................................................................................................530

13.12.1 Parameter Description: PW APS ......................................................................................................530
13.12.2 Parameter Description: MS-PW........................................................................................................534
14 MPLS Tunnel APS..................................................................................................................536

14.1 Introduction to MPLS Tunnel APS..............................................................................................................538
14.2 Basic Concepts.............................................................................................................................................538
14.3 Specifications................................................................................................................................................539
14.5 Availability...................................................................................................................................................541
14.7 Principles......................................................................................................................................................544
14.7.1 Single-Ended Switching......................................................................................................................544
14.7.2 Dual-Ended Switching.........................................................................................................................545
14.7.3 Protection Attributes............................................................................................................................546
14.7.4 Switching Rules...................................................................................................................................546
14.7.5 Switching Impact.................................................................................................................................548
14.8 Networking and Application........................................................................................................................548
14.9 Configuring an MPLS Tunnel APS Protection Group.................................................................................549
14.10 MPLS Tunnel APS Configuration Case.....................................................................................................551
14.10.1 Case Description................................................................................................................................551
14.10.2 Configuration Flow............................................................................................................................553
14.11 Verifying the MPLS Tunnel APS...............................................................................................................554
14.13.1 Relevant Alarms................................................................................................................................558
14.14 Parameter Description: MPLS Tunnel APS...............................................................................................560
14.14.1 Parameters for Configuring MPLS Tunnel APS (on a Per-NE Basis)..............................................560
14.14.2 Parameters for Configuring MPLS Tunnel APS (in End-to-End Mode)..........................................561
15 MS-PW.......................................................................................................................................565
15.1 Introduction..................................................................................................................................................567
15.2 Basic Concepts.............................................................................................................................................568
15.4 Availability...................................................................................................................................................569
15.6 Principles......................................................................................................................................................571
15.7 Configuring MS-PWs...................................................................................................................................572
15.9 Verifying MS-PW.........................................................................................................................................578
Issue 03 (2012-11-30)

xvii
OptiX OSN 7500 II/7500/3500/1500

Contents
15.10.1 Relevant Alarms................................................................................................................................581

15.11 MS-PW Parameters....................................................................................................................................581
16 Packet-based linear MSP........................................................................................................586

16.1 Introduction to Packet-based linear MSP.....................................................................................................588
16.2 Basic Concepts.............................................................................................................................................589
16.3 Specifications................................................................................................................................................593
16.5 Availability...................................................................................................................................................594
16.7 Principles......................................................................................................................................................595
16.9 Creating Packet-Based Linear MSP.............................................................................................................599
16.10 Verifying Packet-Based Linear MSP.........................................................................................................601
16.11.1 Relevant Alarms................................................................................................................................602
17 Power Consumption Control................................................................................................604

17.1 Overview......................................................................................................................................................605
17.2 Availability...................................................................................................................................................605
17.3 Principles......................................................................................................................................................606
17.4 Setting the NE Power Consumption Threshold............................................................................................607
17.5 Querying the Power Consumption of NEs and Boards................................................................................608
17.6.1 Relevant Alarms..................................................................................................................................608
18 Protection Solutions for a 3G Bearer Network..................................................................610

18.1 RNC Dual-Homing.......................................................................................................................................611
18.1.1 Scenario Description............................................................................................................................611
18.2 Cross-Domain Protection.............................................................................................................................618
18.2.1 Scenario Description............................................................................................................................619
18.3 Protection Solutions for Typical Network Topologies.................................................................................622
18.3.1 Protection for a Typical Network Involving Overlapped TDM Domain and Packet Domain............622
18.3.2 Protection Solution for a Hybrid Network Consisting of Hybrid MSTP Equipment and Routers
........................................................................................................................................................................624
18.3.3 Protection Solution for a Hybrid Network Consisting of Hybrid MSTP Equipment and PTN Equipment
........................................................................................................................................................................626
18.3.4 Protection Solution for a Hybrid Network Consisting of Hybrid MSTP Equipment and RTN Equipment
........................................................................................................................................................................628
19 RMON........................................................................................................................................631
Issue 03 (2012-11-30)

xviii
OptiX OSN 7500 II/7500/3500/1500

Contents
19.1 Introduction to RMON.................................................................................................................................632

19.2 Basic Concepts.............................................................................................................................................632
19.2.1 SNMP..................................................................................................................................................632
19.2.2 Ethernet Statistics Group.....................................................................................................................633
19.2.3 Ethernet History Control Group..........................................................................................................633
19.2.4 Ethernet History Group.......................................................................................................................633
19.2.5 Ethernet Alarm Group.........................................................................................................................633
19.4 Availability...................................................................................................................................................634
19.7 Configuring the RMON................................................................................................................................639
19.7.1 Browsing the History Group Performance of an Ethernet Port...........................................................639
19.7.2 Browsing the Statistics Group Performance of an Ethernet Port........................................................640
19.7.3 Customizing the RMON Performance Attribute Template.................................................................640
19.7.4 Configuring an RMON History Control Group..................................................................................641
19.9.1 Statistics of RMON basic performance (packet domain)....................................................................644
19.9.2 Statistics of RMON extended performance (packet domain)..............................................................647
19.9.3 Statistics of specific events of RMON performance (packet domain)................................................652
20 Clock Solution..........................................................................................................................656
20.1 SDH Clock Synchronization........................................................................................................................657
20.1.1 Clock....................................................................................................................................................657
20.1.2 Basic Concepts....................................................................................................................................657
20.1.2.1 Clock Synchronization...............................................................................................................657
20.1.2.2 SSM Protocol and Clock ID.......................................................................................................658
20.1.2.3 Clock Protection.........................................................................................................................660
20.1.2.4 Tributary Retiming.....................................................................................................................665
20.1.3 Reference Standards and Protocols.....................................................................................................668
20.1.4 Availability..........................................................................................................................................668
20.1.5 Principles.............................................................................................................................................669
20.1.6 Configuring Clocks..............................................................................................................................670
20.1.6.1 Guidelines on Clock Configuration............................................................................................670
20.1.6.2 Clock Configuration Process......................................................................................................671
20.1.6.3 Viewing Clock Synchronization Status......................................................................................672
20.1.6.4 Configuring NE Clock Sources..................................................................................................673
20.1.6.5 Configuring the Clock Source Protection...................................................................................674
20.1.6.6 Configuring Switching Conditions for Clock Sources...............................................................675
20.1.6.7 Configuring the Clock Source Reversion...................................................................................675
Issue 03 (2012-11-30)

xix
OptiX OSN 7500 II/7500/3500/1500

Contents
20.1.6.8 Configuring the Phase-Locked Source for External Clock Output............................................676

20.1.6.9 Setting the Clock Source Quality...............................................................................................677
20.1.6.10 Configuring the SSM Output....................................................................................................678
20.1.6.11 Checking the Clock Switching Status......................................................................................679
20.1.6.12 Switching a Clock Source.........................................................................................................680
20.1.7 Configuring Clocks When the SSM Protocol Is Not Enabled.............................................................681
20.1.7.1 Sample Networking....................................................................................................................681
20.1.7.2 Configuring Clocks When No External Equipment Is Available...............................................683
20.1.7.3 Configuring Clocks When One Set of External Clock Equipment Is Available........................684
20.1.8 Configuring Clocks When the Standard SSM Protocol Is Enabled....................................................684
20.1.8.1 Sample Description.....................................................................................................................684
20.1.8.2 Configuring Clocks.....................................................................................................................685
20.1.9 Configuring Clocks When the Extended SSM Protocol Is Enabled...................................................686
20.1.9.1 Sample Networking....................................................................................................................686
20.1.9.2 Configuring a Ring Network......................................................................................................689
20.1.9.3 Configuring a Long Transmission Chain...................................................................................690
20.1.10 Troubleshooting.................................................................................................................................691
20.1.11 Relevant Alarms and Performance Events........................................................................................695
20.1.11.1 Related Alarms.........................................................................................................................695
20.1.11.2 Related Performance Events.....................................................................................................695
20.1.12 Parameter Description.......................................................................................................................696
20.1.12.1 Managing External Clock Sources...........................................................................................696
20.1.12.2 Configuring Clock Protection and Restoration........................................................................700
20.1.12.3 Clock Quality and Status Management....................................................................................702
20.1.12.4 Retiming Management.............................................................................................................704
20.2 IEEE 1588v2 Time Synchronization and Clock Synchronization...............................................................705
20.2.1 Introduction to the IEEE 1588v2 Time Synchronization and Clock Synchronization........................705
20.2.2 Basic Concepts....................................................................................................................................706
20.2.2.1 Clock Architecture and Models..................................................................................................706
20.2.2.2 Bearer Mode of IEEE 1588v2 Packets.......................................................................................707
20.2.3 Specifications.......................................................................................................................................709
20.2.5 Availability..........................................................................................................................................710
20.2.6 Feature Dependency and Limitation....................................................................................................713
20.2.7 Realization Principle............................................................................................................................715
20.2.7.1 Establishing the Master/Slave Relationship...............................................................................715
20.2.7.2 Clock Information Synchronization...........................................................................................717
20.2.8 Application Scenarios of the IEEE 1588v2 Time Synchronization and Clock Synchronization........720
20.2.9 Configuring the IEEE 1588v2 Time Synchronization and Clock Synchronization............................721
20.2.9.1 Setting the NE Parameters..........................................................................................................721
20.2.9.2 Configuring the Encapsulation Type of IEEE 1588 V2 Packets on the Data Board..................722
20.2.9.3 Setting the Attributes of the External Clock Interface for an NE...............................................722
Issue 03 (2012-11-30)

xx
OptiX OSN 7500 II/7500/3500/1500

Contents
20.2.9.4 Configuring the Clock Source Priority Table for an NE............................................................723

20.2.9.5 Querying the Current Clock Tracing Source..............................................................................724
20.2.9.6 Configuring the Clock Interface.................................................................................................725
20.2.10 Configuration Example......................................................................................................................725
20.2.10.1 Example Description................................................................................................................726
20.2.10.2 Configuration Process...............................................................................................................730
20.2.11 Verifying the IEEE 1588 V2 Time Synchronization and Clock Synchronization............................730
20.2.12 Routine Maintenance.........................................................................................................................731
20.2.14.1 Relevant Alarms.......................................................................................................................734
20.2.14.2 Relevant Performance Events...................................................................................................734
20.2.15 Parameter Description: IEEE 1588v2 Time Synchronization and Clock Synchronization..............734
20.2.15.1 NE Parameters..........................................................................................................................734
20.2.15.2 Clock Source Priority Table.....................................................................................................736
20.2.15.3 Configuration of the IEEE 1588v2 Packet on the Data Board.................................................736
20.2.15.4 Clock Interface Configuration..................................................................................................737
20.2.15.5 External Clock Interface Configuration....................................................................................738
20.3 Synchronous Ethernet Clock........................................................................................................................740
20.3.1 Introduction.........................................................................................................................................740
20.3.2 Basic Concepts....................................................................................................................................741
20.3.3 Specifications.......................................................................................................................................742
20.3.5 Availability..........................................................................................................................................743
20.3.7 Principles.............................................................................................................................................745
20.3.7.1 Protocol Data Unit of the Synchronous Ethernet Clock.............................................................745
20.3.7.2 Process for Realizing the Synchronous Ethernet Clock.............................................................747
20.3.8 Networking and Application...............................................................................................................748
20.3.9 Configuring Synchronous Ethernet Clocks.........................................................................................749
20.3.9.1 Configuring NE Clock Sources..................................................................................................749
20.3.9.2 Configuring Protection for Clock Sources.................................................................................750
20.3.10 Configuration Example......................................................................................................................750
20.3.10.1 Description of the Example......................................................................................................751
20.3.10.2 Configuration Process...............................................................................................................751
20.3.11 Verifying Synchronous Ethernet Clocks...........................................................................................753
20.3.13 Relevant Alarms and Performance Events .......................................................................................755
20.3.13.1 Relevant Alarms.......................................................................................................................755
20.3.14 Parameter Description: Synchronous Ethernet Clock.......................................................................756
20.3.14.1 Managing External Clock Sources...........................................................................................756
Issue 03 (2012-11-30)

xxi
OptiX OSN 7500 II/7500/3500/1500

Contents
20.3.14.2 Configuring Clock Protection and Restoration........................................................................759

20.3.14.3 Clock Quality and Status Management....................................................................................762
20.3.14.4 Retiming Management.............................................................................................................764
20.4 CES ACR......................................................................................................................................................765
20.4.1 Introduction.........................................................................................................................................765
20.4.2 Basic Concepts....................................................................................................................................766
20.4.2.1 CES ACR Clock Domain...........................................................................................................766
20.4.2.2 Enhanced CES ACR Clock Synchronization Solution...............................................................767
20.4.2.3 Standard CES ACR Clock Synchronization Solution................................................................768
20.4.4 Availability..........................................................................................................................................769
20.4.6 Principles.............................................................................................................................................772
20.4.8 Configuring CES ACR........................................................................................................................774
20.4.8.1 Configuring the Primary Clock for an ACR Clock Domain......................................................774
20.4.8.2 Configuring Ports Using the Clock Domain...............................................................................775
20.4.9 Configuration Example........................................................................................................................776
20.4.9.1 Network Diagram.......................................................................................................................776
20.4.9.2 Service Planning.........................................................................................................................776
20.4.9.3 Configuration Process.................................................................................................................777
20.4.10.1 Relevant Alarms.......................................................................................................................779
20.4.11 Parameter Description: CES ACR.....................................................................................................779
20.4.11.1 ACR Clocks..............................................................................................................................779
20.4.11.2 Clock Domain...........................................................................................................................780
20.4.11.3 Creating a Clock Domain.........................................................................................................781
21 Outband DCN..........................................................................................................................782
21.1 Introduction to the DCN...............................................................................................................................784
21.1.1 DCN Composition...............................................................................................................................784
21.1.2 Huawei DCN Solution.........................................................................................................................785
21.2 HWECC Solution.........................................................................................................................................786
21.2.1 Solution Overview...............................................................................................................................786
21.2.1.1 Basic Concepts...........................................................................................................................786
21.2.1.2 Networking.................................................................................................................................789
21.2.2 Availability..........................................................................................................................................791
21.2.3 Relation with Other Features...............................................................................................................792
21.2.4 Principles.............................................................................................................................................792
21.2.4.1 Establishing ECC Routes............................................................................................................792
21.2.4.2 Transferring Messages................................................................................................................794
21.2.4.3 Extended ECC............................................................................................................................795
Issue 03 (2012-11-30)

xxii
OptiX OSN 7500 II/7500/3500/1500

Contents
21.2.5 Planning Guide....................................................................................................................................796

21.2.5.1 Planning Guidelines....................................................................................................................796
21.2.5.2 Planning Example.......................................................................................................................798
21.2.6 Configuring HWECC..........................................................................................................................800
21.2.6.2 Changing the ID of an NE..........................................................................................................803
21.2.6.3 Setting Communication Parameters of an NE............................................................................803
21.2.6.4 Configuring DCCs......................................................................................................................804
21.2.6.5 Dividing a Network into Multiple ECC Subnets........................................................................807
21.2.6.6 Configuring the Extended ECC..................................................................................................807
21.2.6.7 Configuring DCC Transparent Transmission.............................................................................810
21.2.6.8 Querying and Allocating DCC Resources..................................................................................812
21.2.6.9 Querying the ECC Routes of an NE...........................................................................................813
21.2.7 Application Example Based on HWECC............................................................................................814
21.3 IP over DCC Solution...................................................................................................................................815
21.3.1.1 Basic Concepts...........................................................................................................................815
21.3.1.2 Networking.................................................................................................................................818
21.3.2 Availability..........................................................................................................................................819
21.3.4 Principles.............................................................................................................................................820
21.3.5 Network Planning................................................................................................................................821
21.3.6 Configuring IP over DCC....................................................................................................................824
21.3.6.5 Querying IP Routes....................................................................................................................831
21.3.6.6 Querying the OSPF Protocol Status...........................................................................................831
21.3.6.7 Enabling the Proxy ARP.............................................................................................................832
21.3.6.8 Configuring the IP Static Route for an NE.................................................................................833
21.3.7 Application Example for Hybrid Networking Based on IP over DCC...............................................834
21.4 OSI over DCC Solution................................................................................................................................835
21.4.1.1 Basic Concepts...........................................................................................................................835
21.4.1.2 Networking.................................................................................................................................840
21.4.2 Availability..........................................................................................................................................841
21.4.4 Principles.............................................................................................................................................842
Issue 03 (2012-11-30)

xxiii
OptiX OSN 7500 II/7500/3500/1500

Contents

21.4.6 Configuring OSI over DCC.................................................................................................................847
21.4.6.4 Setting the NSAP Address of an NE..........................................................................................851
21.4.6.6 Setting the Node Type for an NE...............................................................................................854
21.4.6.7 Configuring the Communication Protocol Stack and LAPD Role for an Optical Interface
..................................................................................................................................................................856
21.4.6.8 Query Routing Information........................................................................................................857
21.4.6.9 Creating an OSI Gateway NE.....................................................................................................857
21.4.7 Application Example for Hybrid Networking Based on OSI over DCC............................................858
21.5 Hybrid Networking Solution of DCC Transparent Transmission................................................................859
21.5.2 Availability..........................................................................................................................................862
21.5.4 Principles.............................................................................................................................................863
21.5.6 Configuring DCC Transparent Transmission......................................................................................866
21.5.6.5 Configuring DCC Transparent Transmission.............................................................................872
21.5.6.6 Querying the ECC Routes of an NE...........................................................................................874
21.5.7 Application Example for Hybrid Networking Based DCC Transparent Transmission......................875
21.6 Transparent Transmission of DCC Bytes Through the External Clock Interface........................................876
21.6.1 Solution Description............................................................................................................................876
21.6.2 Availability..........................................................................................................................................877
21.6.3 Relationship with Other Features........................................................................................................878
21.6.4 Principles.............................................................................................................................................878
21.6.6 Configuring Transparent Transmission of DCC Bytes Through the External Clock Interface..........881
21.6.6.3 Configuring a Cross-Connection for E1 Services......................................................................885
Issue 03 (2012-11-30)

xxiv
OptiX OSN 7500 II/7500/3500/1500

Contents
21.6.7 Example of Hybrid Networking Based on Transparent Transmission of DCC Bytes Through the External
Clock Interface...............................................................................................................................................886
21.7 DCN Maintenance........................................................................................................................................886
21.7.1 Troubleshooting...................................................................................................................................886
21.7.1.1 A Single NE Being Unreachable................................................................................................886
21.7.1.2 All NEs of the Subnet Being Unreachable.................................................................................889
21.7.1.3 NEs Being Unreachable Frequently...........................................................................................893
21.7.2 Maintenance Cases..............................................................................................................................894
21.7.3 Relevant Alarms and Performance Events..........................................................................................895
22 Inband DCN Solution............................................................................................................896

22.1 Overview of the Inband DCN.......................................................................................................................898
22.2 Basic Concepts.............................................................................................................................................899
22.2.1 Protocol Stack......................................................................................................................................899
22.2.2 Access Methods...................................................................................................................................901
22.2.3 Access Control.....................................................................................................................................902
22.4 Availability...................................................................................................................................................903
22.6 Principles......................................................................................................................................................910
22.6.1 Message Transfer in the HW ECC Protocol Stack .............................................................................910
22.6.2 Message Transfer in the IP Protocol Stack..........................................................................................911
22.8 Configuring the Inband DCN.......................................................................................................................913
22.8.1 Setting the VLAN ID and Bandwidth Used by the Inband DCN........................................................913
22.8.2 Setting the NMS Access Parameters...................................................................................................914
22.8.3 Configuring the DCN Function of a Port............................................................................................915
22.8.4 Configuring the Protocol Stack Used by the Inband DCN..................................................................916
22.9 Configuration Case of the Inband DCN.......................................................................................................916
22.9.1 Case Description..................................................................................................................................916
22.10 Verifying the Configuration of the Inband DCN........................................................................................919
22.12 Parameter Description: Inband DCN..........................................................................................................923
22.12.1 Bandwidth Management....................................................................................................................923
22.12.2 Access Control...................................................................................................................................924
22.12.3 Port Settings.......................................................................................................................................925
22.12.4 Protocol Settings................................................................................................................................926
22.13 Related Alarms and Performance Events...................................................................................................926
22.13.1 Related Alarms..................................................................................................................................926
22.13.2 Related Performance Events..............................................................................................................926
A List of Parameters.....................................................................................................................927
A.1 Ethernet Port Associated Parameters (Packet Mode)....................................................................................929
Issue 03 (2012-11-30)

xxv
OptiX OSN 7500 II/7500/3500/1500

Contents
A.1.1 MAC Loopback(Ethernet Interface).....................................................................................................929

A.1.2 PHY Loopback(Ethernet Interface)......................................................................................................930
A.1.3 Enable Port(Ethernet Interface)............................................................................................................931
A.1.4 Encapsulation Type(Ethernet Interface)...............................................................................................932
A.1.5 Working Mode(Ethernet Interface)......................................................................................................933
A.1.6 Max Frame Length(byte) for an Ethernet Port.....................................................................................934
A.1.7 Enable Tunnel(Ethernet Interface)........................................................................................................935
A.1.8 Specify IP(Ethernet Interface)..............................................................................................................936
A.2 Ethernet Port Associated Parameters (TDM Mode)......................................................................................937
A.2.1 Port Attribute (Ethernet Port)...............................................................................................................937
A.2.2 Enable Port (Ethernet Port Attribute)...................................................................................................939
A.2.3 Max. Frame Length (Ethernet Port Attribute)......................................................................................939
A.2.4 Non-Autonegotiation Flow Control Mode (Ethernet Port Attribute)...................................................940
A.2.5 Autonegotiation Flow Control Mode (Ethernet Port Attribute)...........................................................941
A.2.6 MAC Loopback (Ethernet Port Attribute)............................................................................................942
A.2.7 PHY Loopback (Ethernet Port Attribute).............................................................................................943
A.2.8 QinQ Type Area...................................................................................................................................944
A.2.9 Loop Detection (Ethernet Port Attribute).............................................................................................945
A.2.10 Loop Port Shutdown (Ethernet Port Attribute)...................................................................................945
A.2.11 Traffic Threshold(Mpbs)(External Ethernet Port Attribute)..............................................................946
A.2.12 Broadcast Packet Suppression Threshold (Ethernet Interface Attributes)..........................................946
A.2.13 Enabling Broadcast Packet Suppression (Ethernet Interface Attributes)...........................................947
A.2.14 Zero-Flow Monitor (Ethernet Interface Attributes)............................................................................948
A.2.15 Port Traffic Threshold Time Window(Min).......................................................................................948
A.2.16 Jumbo Frame Type.............................................................................................................................949
A.2.17 Default VLAN ID (Ethernet Port Attribute).......................................................................................950
A.2.18 VLAN Priority (Ethernet Port Attribute)............................................................................................950
A.2.19 Entry Detection (Ethernet Port Attribute)...........................................................................................951
A.2.20 Tag Identifier......................................................................................................................................952
A.2.21 Mapping Protocol...............................................................................................................................953
A.2.22 Scramble.............................................................................................................................................955
A.2.23 Set Inverse Value for CRC.................................................................................................................956
A.2.24 Check Field Length.............................................................................................................................956
A.2.25 FCS Calculated Bit Sequence.............................................................................................................957
A.2.26 Extension Header Option....................................................................................................................959
A.3 Ethernet Service Associated Parameters (Packet Mode)...............................................................................960
A.3.1 PW Signaling Type(PW Management)................................................................................................960
A.3.2 Bearer Type (E-Line Service)...............................................................................................................961
A.3.3 PW ID(E-Line Service)........................................................................................................................961
A.3.4 BPDU....................................................................................................................................................962
A.3.5 MTU(bytes)(E-Line Service)................................................................................................................963
A.3.6 Static MAC Address (E-LAN Service)................................................................................................964
Issue 03 (2012-11-30)

xxvi
OptiX OSN 7500 II/7500/3500/1500

Contents
A.3.7 Self-Learning MAC Address (E-LAN Service)...................................................................................965

A.3.8 Aging Time (min)(E-LAN Service).....................................................................................................966
A.3.9 Default Forwarding Priority.................................................................................................................967
A.3.10 Default Packet Relabeling Color(E-LAN Service).............................................................................968
A.3.11 Split Horizon Group ID(E-LAN Service)...........................................................................................969
A.3.12 Split Horizon Group Member (E-LAN Service)................................................................................970
A.3.13 Source Interface Type(E-AGGR Service)..........................................................................................970
A.3.14 Sink Interface Type(E-AGGR Service)..............................................................................................971
A.4 CES Service Associated Parameters..............................................................................................................972
A.4.1 Packet Loading Time (us).....................................................................................................................972
A.4.2 RTP Header..........................................................................................................................................973
A.4.3 Jitter Compensation Buffering Time (us).............................................................................................974
A.4.4 Clock Mode..........................................................................................................................................976
A.5 Data Service Associated Parameters (TDM Mode).......................................................................................977
A.5.1 Operation Type (EPL Service).............................................................................................................977
A.5.2 Service Type (EPL Service).................................................................................................................979
A.5.3 Encapsulation Format of P Port (Network Attributes).........................................................................980
A.5.4 C-VLAN and S-VLAN.........................................................................................................................981
A.5.5 VLAN ID (For Creation of Ethernet Virtual Private Lines).................................................................982
A.5.6 MAC Address Aging Time / Aging Time Unit....................................................................................983
A.5.7 Hub/Spoke (Ethernet LAN Service).....................................................................................................984
A.5.8 Actual MAC Address Table Capacity (Ethernet LAN Service)...........................................................984
A.5.9 Specified MAC Address Table Capacity (Ethernet LAN Service)......................................................985
A.5.10 Bridge Learning Mode (Ethernet LAN Service)................................................................................987
A.5.11 Self-learning MAC Address (Ethernet LAN Service)........................................................................988
A.5.12 Tunnel.................................................................................................................................................988
A.5.13 VC.......................................................................................................................................................989
A.5.14 Operation Type(IEEE 802.1ad Bridge)..............................................................................................990
A.5.15 Bridge Type........................................................................................................................................991
A.5.16 SAN Service Type..............................................................................................................................992
A.5.17 Concatenation Level (SAN)...............................................................................................................993
A.5.18 Enabled Flow Control of FC Port.......................................................................................................994
A.5.19 Initial Value of CREDIT at the Client Side........................................................................................995
A.5.20 Initial Value of CREDIT at the WAN Side........................................................................................996
A.6 ETH OAM Associated Parameters (Packet Mode).......................................................................................997
A.6.1 CC Test Transmit Period(Ethernet Service OAM Management).........................................................997
A.6.2 Maintenance Domain Level(Ethernet Service OAM Management)....................................................997
A.6.3 CC Status(Ethernet Service OAM Management).................................................................................998
A.6.4 Service Name(Ethernet Service OAM Management)..........................................................................999
A.6.5 Service Type(Ethernet Service OAM Management)............................................................................999
A.6.6 Activation Status(Ethernet Service OAM Management)...................................................................1000
A.6.7 Transmitted Packet Count(Ethernet Service OAM Management).....................................................1001
Issue 03 (2012-11-30)

xxvii
OptiX OSN 7500 II/7500/3500/1500

Contents
A.6.8 Transmitted Packet Length(Ethernet Service OAM Management)....................................................1002

A.6.9 Transmitted Packet Priority (Ethernet Service OAM Management)..................................................1003
A.6.10 Destination Maintenance Point MAC Address(Ethernet Service OAM Management)...................1003
A.6.11 Response Maintenance Point ID(Ethernet Service OAM Management).........................................1004
A.6.12 Hop Count(Ethernet Service OAM Management)...........................................................................1004
A.6.13 Test Result(Ethernet Service OAM Management)...........................................................................1005
A.7 ETH-OAM Associated Parameters (TDM Mode).......................................................................................1006
A.7.1 MP ID (Ethernet OAM)......................................................................................................................1006
A.7.2 Maintenance Point Type (Ethernet OAM).........................................................................................1006
A.7.3 CC Status (Ethernet OAM).................................................................................................................1007
A.7.4 CC Activate Flag................................................................................................................................1007
A.7.5 Test Result (LB and LT Test).............................................................................................................1008
A.7.6 Responding MP Type (Ethernet LT Test)..........................................................................................1009
A.7.7 Hop Count (Ethernet LT Test)............................................................................................................1009
A.7.8 Send Mode (Ping Test).......................................................................................................................1010
A.7.9 Packet Length (Ping Test)..................................................................................................................1011
A.7.10 Timeout (Ping Test)..........................................................................................................................1011
A.7.11 Time To Live....................................................................................................................................1012
A.7.12 Delay.................................................................................................................................................1013
A.7.13 Average Delay..................................................................................................................................1013
A.7.14 Max. Delay.......................................................................................................................................1014
A.7.15 Min. Delay........................................................................................................................................1014
A.7.16 Detect Attempts................................................................................................................................1015
A.7.17 Send Direction (Ethernet Test).........................................................................................................1015
A.7.18 Error Frame Monitor Window(ms)..................................................................................................1016
A.7.19 Error Frame Monitor Threshold (Entries)........................................................................................1017
A.7.20 Error Frame Period Window (Frame)...............................................................................................1017
A.7.21 Error Frame Monitor Threshold (Frame).........................................................................................1018
A.7.22 Error Frame Second Window(s).......................................................................................................1019
A.7.23 Error Frame Second Threshold(s)....................................................................................................1019
A.7.24 Enable OAM Protocol......................................................................................................................1020
A.7.25 OAM Working Mode.......................................................................................................................1021
A.7.26 Remote Alarm Support for Link Event............................................................................................1021
A.7.27 Unidirectional Operation..................................................................................................................1022
A.7.28 Loopback Status (OAM Parameter).................................................................................................1023
A.8 PW Associated Parameters..........................................................................................................................1023
A.8.1 Control Word......................................................................................................................................1024
A.8.2 Control Channel Type.........................................................................................................................1025
A.8.3 VCCV Verification Mode...................................................................................................................1026
A.8.4 Request VLAN...................................................................................................................................1026
A.8.5 Overall Operating Status.....................................................................................................................1027
A.8.6 Associate AC State.............................................................................................................................1028
Issue 03 (2012-11-30)

xxviii
OptiX OSN 7500 II/7500/3500/1500

Contents
A.8.7 Max.Concatenated Cell Count............................................................................................................1029

A.9 PW APS Protection Associated Parameters (Packet Mode)........................................................................1029
A.9.1 Protection Mode..................................................................................................................................1029
A.9.2 Protection Mode..................................................................................................................................1030
A.9.3 Switchover Status...............................................................................................................................1031
A.9.4 Protocol Status....................................................................................................................................1034
A.9.5 PW Type.............................................................................................................................................1035
A.10 HQoS Associated Parameters....................................................................................................................1036
A.10.1 Traffic Classification Rule(Policy Management).............................................................................1036
A.10.2 Match Type(Policy Management)....................................................................................................1037
A.10.3 Match Value(Policy Management)...................................................................................................1040
A.10.4 Wildcard(Policy Management).........................................................................................................1042
A.10.5 PW Direction(PW Policy)................................................................................................................1045
A.10.6 Direction (PW Policy)......................................................................................................................1045
A.10.7 Duplicated Policy Name(PW Policy)...............................................................................................1046
A.10.8 Policy ID(Policy Management)........................................................................................................1046
A.10.9 Policy Name (Policy Management)..................................................................................................1047
A.10.10 QinQ Link ID(QinQ Policy)...........................................................................................................1048
A.10.11 Physical Port ID(QinQ Policy).......................................................................................................1048
A.10.12 S-VLAN ID(QinQ Policy)..............................................................................................................1048
A.10.13 Traffic Classification Bandwidth Sharing(Policy Management)....................................................1049
A.10.14 Coloring Mode (V-UNI Ingress Policy).........................................................................................1050
A.10.15 Logical Relation Between Matched Rules(V-UNI Ingress Policy)................................................1051
A.10.16 Processing Mode(V-UNI Ingress Policy).......................................................................................1052
A.10.17 AF1 Schedule Weight(%)(WFQ Schedule Policy)........................................................................1053
A.10.21 Discard Lower Threshold (256 bytes) (Service WRED Policy).....................................................1055
A.10.22 Discard Upper Threshold (256 bytes) (Service WRED Policy).....................................................1056
A.10.23 Discard Probability (%) (Service WRED Policy)..........................................................................1057
A.10.24 PHB (Diffserv domain Management).............................................................................................1057
A.10.25 Packet Type (Diffserv domain Management).................................................................................1058
A.10.26 Committed Information Rate (Kbit/s)............................................................................................1059
A.10.27 Committed Burst Size (byte)..........................................................................................................1060
A.10.28 Peak Information Rate (kbit/s)........................................................................................................1060
A.10.29 Peak Burst Size (byte)....................................................................................................................1061
A.10.30 EXP.................................................................................................................................................1062
A.10.31 LSP Mode.......................................................................................................................................1063
A.11 QoS Associated Parameters.......................................................................................................................1064
A.11.1 Flow Type (Flow Configuration)......................................................................................................1064
A.11.2 Bound CAR (Flow Configuration)...................................................................................................1065
Issue 03 (2012-11-30)

xxix
OptiX OSN 7500 II/7500/3500/1500

Contents
A.11.3 Bound CoS (Flow Configuration)....................................................................................................1066

A.11.4 CAR ID (CAR Configuration)..........................................................................................................1066
A.11.5 CAR Enabled/Disabled (CAR Configuration).................................................................................1067
A.11.6 Committed Information Rate (CAR Configuration).........................................................................1068
A.11.7 Committed Burst Size (CAR Configuration)...................................................................................1069
A.11.8 Peak Information Rate (CAR Configuration)...................................................................................1069
A.11.9 Maximum Burst Size (CAR Configuration).....................................................................................1070
A.11.10 CoS ID (CoS Configuration)..........................................................................................................1071
A.11.11 CoS Type (CoS Configuration)......................................................................................................1072
A.11.12 CoS Priority (CoS Configuration)..................................................................................................1073
A.11.13 Shaping...........................................................................................................................................1076
A.12 ATM Interface Associated Parameters (Packet Mode).............................................................................1077
A.12.1 ATM Cell Payload Scrambling(ATM Interface Management)........................................................1077
A.12.2 Min.VPI(ATM Interface Management)............................................................................................1078
A.12.3 Min.VCI(ATM Interface Management)...........................................................................................1079
A.12.4 VCC-Supported VPI Count(ATM Interface Management)..............................................................1080
A.13 ATM/IMA Services Associated Parameters (Packet Mode).....................................................................1081
A.13.1 IMA Transit Frame Length...............................................................................................................1081
A.13.2 IMA Symmetry Mode.......................................................................................................................1082
A.13.3 Maximum Delay Between Links(ms)(IMA Group Management)...................................................1083
A.13.4 Minimum Number of Active Transmitting Links(IMA Group Management).................................1084
A.13.5 Minimum Number of Active Receiving Links(IMA Group Management).....................................1085
A.13.6 Clock Mode(IMA Group Management)...........................................................................................1086
A.13.7 Near-End Group Status(IMA Group Status)....................................................................................1087
A.13.8 Differential Delay Check Status(IMA Link States)..........................................................................1088
A.13.9 Connection Type(Per-NE ATM Service Management)...................................................................1089
A.13.10 Uplink Policy(Per-NE Configuration for ATM Connections).......................................................1090
A.13.11 Downlink Policy(Per-NE Configuration for ATM Connections)..................................................1091
A.13.12 CoS Mapping(Per-NE Configuration for CoS Mapping)...............................................................1092
A.13.13 Traffic Service(ATM Policy).........................................................................................................1092
A.13.14 Clp01Pcr(cell/s)(ATM Policy).......................................................................................................1096
A.13.15 Clp01Scr(cell/s)(ATM Policy).......................................................................................................1098
A.13.16 Clp0Pcr(cell/s)(ATM Policy).........................................................................................................1100
A.13.17 Clp0Scr(cell/s)(ATM Policy).........................................................................................................1102
A.13.18 Clp01Mcr(cell/s)(ATM Policy)......................................................................................................1104
A.13.19 Max.Cell Burst Size(cell)(ATM Policy).........................................................................................1106
A.13.20 Cell Delay Variation Tolerance(0.1us)(ATM Policy)....................................................................1107
A.13.21 UPC/NPC(ATM Policy).................................................................................................................1109
A.14 ATM OAM Associated Parameters (Packet Mode)..................................................................................1110
A.14.1 Connection Direction........................................................................................................................1110
A.14.2 Segment and End Attribute...............................................................................................................1111
A.14.3 Country Code(Hexadecimal Code)...................................................................................................1113
Issue 03 (2012-11-30)

xxx
OptiX OSN 7500 II/7500/3500/1500

Contents
A.14.4 Network Code(Hexadecimal Code)..................................................................................................1114

A.14.5 NE Code(Hexadecimal Code)..........................................................................................................1115
A.15 ATM/IMA Associated Parameters (TDM Mode).....................................................................................1116
A.15.1 VCTRUNK Port (ATM Bound Path Management).........................................................................1116
A.15.2 Level (ATM Bound Path Management)...........................................................................................1119
A.15.3 Direction (ATM Bound Path Management).....................................................................................1120
A.15.4 Port (ATM Port Management)..........................................................................................................1121
A.15.5 Port Type (ATM Port Management)................................................................................................1124
A.15.6 Max. VPI Bits...................................................................................................................................1124
A.15.7 Max. VCI Bits...................................................................................................................................1125
A.15.8 Max. VPC.........................................................................................................................................1126
A.15.9 Max. VCC.........................................................................................................................................1126
A.15.10 VPC Configured.............................................................................................................................1127
A.15.11 VCC Configured.............................................................................................................................1128
A.15.12 Number of VPI that Supports VCC................................................................................................1128
A.15.13 UPC/NPC Enabled/Disabled..........................................................................................................1129
A.15.14 Positive UPC/NPC(ATM Service Management)...........................................................................1130
A.15.15 ID (ATM Traffic Management)......................................................................................................1131
A.15.16 Traffic Type (ATM Traffic Management)......................................................................................1132
A.15.17 Service Type (ATM Traffic Management).....................................................................................1136
A.15.18 PCR (ATM Traffic Management)..................................................................................................1139
A.15.19 SCR (ATM Traffic Management)..................................................................................................1140
A.15.20 MBS................................................................................................................................................1141
A.15.21 CDVT.............................................................................................................................................1142
A.15.22 Open Flow Frame Discarding Flag.................................................................................................1142
A.15.23 Positive Traffic Descriptor.............................................................................................................1143
A.15.24 Connection ID (ATM Service Management).................................................................................1144
A.15.25 Connection Type (ATM Service Management).............................................................................1145
A.15.26 Spread Type (ATM Service Management).....................................................................................1146
A.15.27 VPI and VCI (ATM Service Management)....................................................................................1148
A.15.28 Positive Service Status(ATM Service Management).....................................................................1150
A.15.29 Positive Service Failure Reason(ATM Service Management).......................................................1151
A.15.30 Source/Sink Switching Cause.........................................................................................................1152
A.15.31 Protection Type (ATM Service Management)...............................................................................1153
A.15.32 Switching Direction (ATM Service Management).........................................................................1155
A.15.33 Switching Status (ATM Service Management)..............................................................................1155
A.15.34 Switching Type (ATM Service Management)...............................................................................1156
A.15.35 Revertive Mode (ATM Service Management)...............................................................................1158
A.15.36 Pause Time(0-100) *100 ms (ATM Service Management)............................................................1158
A.15.37 WTR Time(0-30min) (ATM Service Management)......................................................................1159
A.15.38 External Command (ATM Protection Group)................................................................................1159
A.15.39 IMA Group Number.......................................................................................................................1161
Issue 03 (2012-11-30)

xxxi
OptiX OSN 7500 II/7500/3500/1500

Contents
A.15.40 IMA Protocol Version....................................................................................................................1161

A.15.41 IMA Transmit Frame Length..........................................................................................................1162
A.15.42 IMA Group Configuration Mode....................................................................................................1162
A.15.43 Minimum Number of Active Links................................................................................................1165
A.15.44 IMA Group Status...........................................................................................................................1166
A.15.45 Protocol Mode (IMA1.0 Mode)......................................................................................................1167
A.15.46 Enable/Disable Cell Payload Scramble..........................................................................................1168
A.15.47 Link Frame Format.........................................................................................................................1168
A.15.48 Connection Direction (ATM Segment End Attribute)...................................................................1169
A.15.49 Segment and End Attribute (ATM Segment End Attribute)..........................................................1170
A.15.50 LLID...............................................................................................................................................1172
A.15.51 Maximum Ingress Bandwidth.........................................................................................................1173
A.15.52 Maximum Egress Bandwidth.........................................................................................................1173
A.16 RPR Associated Parameters......................................................................................................................1174
A.16.1 RPR Node ID....................................................................................................................................1174
A.16.2 RPR Protocol....................................................................................................................................1175
A.16.3 RPR Node Protection Slow Timer Value(ms)..................................................................................1176
A.16.4 RPR ATD Timer Value(s)................................................................................................................1177
A.16.5 RPR Protection Mode.......................................................................................................................1177
A.16.6 RPR Hold-off Time(ms)...................................................................................................................1180
A.16.7 RPR Protection Restoration Mode....................................................................................................1181
A.16.8 RPR Protection Wait-to-restore(s)....................................................................................................1182
A.16.9 RPR Send link weight.......................................................................................................................1183
A.16.10 RPR Used and Reserved bandwidth of priority A..........................................................................1184
A.16.11 RPR Used bandwidth of priority B-CIR(Mbps).............................................................................1185
A.16.12 RPR Circle Name...........................................................................................................................1186
A.16.13 RPR Node Reachability..................................................................................................................1187
A.16.14 RPR Node Hop...............................................................................................................................1188
A.16.15 RPR Adjacent node ID...................................................................................................................1188
A.16.16 RPR Node Direction.......................................................................................................................1189
A.16.17 ECHO Path ID (RPR Node Information).......................................................................................1190
A.16.18 ECHO Working Mode (RPR Node Information)...........................................................................1190
A.16.19 ECHO Request Loop (RPR Node Information).............................................................................1192
A.16.20 ECHO Response Loop (RPR Node Information)...........................................................................1193
A.16.21 ECHO Frame Service Type (RPR Node Information)...................................................................1194
A.16.22 Is ECHO Path Protected (RPR Node Information)........................................................................1194
A.16.23 ECHO T1 Transmit Period (RPR Node Information)....................................................................1195
A.16.24 ECHO T2 Response Time (RPR Node Information).....................................................................1196
A.16.25 Number of Echo Messages Received (RPR Node Information)....................................................1197
A.16.26 Successfully Processed (RPR Node Information)..........................................................................1197
A.16.27 Unsuccessfully Processed (RPR Node Information)......................................................................1198
A.16.28 dLoc Detected (RPR Node Information)........................................................................................1198
Issue 03 (2012-11-30)

xxxii
OptiX OSN 7500 II/7500/3500/1500

Contents
A.16.29 Loc Detected (RPR Node Information)..........................................................................................1199

A.16.30 RPR Node Protection Status...........................................................................................................1200
A.16.31 RPR Node Switching Status...........................................................................................................1201
A.16.32 RPR Node Accumulated Protection Times....................................................................................1202
A.16.33 RPR Node Accumulated Protection Time......................................................................................1202
A.16.34 RPR Node Last Switch Request.....................................................................................................1203
A.16.35 RPR Switch Request.......................................................................................................................1203
A.17 LAG Associated Parameters (TDM Mode)...............................................................................................1204
A.17.1 LAG Type(Link Aggregation Group Management).........................................................................1205
A.17.2 Revertive Mode(Link Aggregation Group Management)................................................................1206
A.17.3 Load Sharing(Link Aggregation Group Management)....................................................................1207
A.17.4 Load Sharing Hash Algorithm(Link Aggregation Group Management)..........................................1208
A.17.5 System Priority(Link Aggregation Group Management).................................................................1209
A.17.6 Main Port(Link Aggregation Group Management)..........................................................................1209
A.17.7 Main Port Status(Link Aggregation Group Management)...............................................................1210
A.17.8 Port Priority(Link Aggregation Group Management)......................................................................1211
A.18 MC-LAG Associated Parameters..............................................................................................................1212
A.18.1 Protocol Channel ID.........................................................................................................................1212
A.18.2 Hello Packet Sending Interval (s).....................................................................................................1213
A.18.3 Timeout Time (s)..............................................................................................................................1213
A.19 LAG/DLAG Associated Parameters (TDM Mode)...................................................................................1214
A.19.1 Port Priority (Link Aggregation)......................................................................................................1214
A.19.2 System Priority (Link Aggregation).................................................................................................1215
A.19.3 Slave Port (Link Aggregation)..........................................................................................................1216
A.19.4 Status (Link Aggregation)................................................................................................................1217
A.19.5 Branch Port.......................................................................................................................................1218
A.19.6 Load Sharing(Ethernet Link Aggregation).......................................................................................1219
A.19.7 Revertive Mode (DLAG)..................................................................................................................1220
A.19.8 Main Port Priority (DLAG)..............................................................................................................1220
A.19.9 Slave Port Priority (DLAG)..............................................................................................................1221
A.20 STP/RSTP Associated Parameters............................................................................................................1222
A.20.1 Protocol Enabled (Spanning Tree)....................................................................................................1222
A.20.2 Protocol Type (Spanning Tree Protocol)..........................................................................................1223
A.20.3 VB Priority (Bridge Parameters)......................................................................................................1223
A.20.4 Max Age(s).......................................................................................................................................1224
A.20.5 Hello Time(s) (Spanning Tree).........................................................................................................1225
A.20.6 Forward Delay(s) (Spanning Tree)...................................................................................................1225
A.20.7 TxHoldCount(per second) (Spanning Tree).....................................................................................1226
A.20.8 Root Path Cost..................................................................................................................................1226
A.20.9 Hold Count (Spanning Tree)............................................................................................................1227
A.20.10 Port ID............................................................................................................................................1227
A.20.11 Port Path Cost.................................................................................................................................1228
Issue 03 (2012-11-30)

xxxiii
OptiX OSN 7500 II/7500/3500/1500

Contents
A.20.12 Designated Path Cost......................................................................................................................1229

A.20.13 Designated Root Bridge Priority....................................................................................................1230
A.20.14 Designated Bridge Priority(Spanning Tree)...................................................................................1231
A.20.15 Designated Bridge MAC Address (Spanning Tree).......................................................................1231
A.20.16 Protocol Enabled (Port Parameter of Spanning Tree)....................................................................1232
A.20.17 Admin Edge Attribute.....................................................................................................................1233
A.20.18 Edge Port Status (Spanning Tree)...................................................................................................1234
A.20.19 VB Port Priority..............................................................................................................................1234
A.20.20 VB Port Status................................................................................................................................1235
A.20.21 Point to Point Attributes(External Ethernet Port Attributes)..........................................................1236
A.21 LCAS Associated Parameters....................................................................................................................1237
A.21.1 Enabling LCAS.................................................................................................................................1237
A.21.2 LCAS Mode......................................................................................................................................1238
A.21.3 Hold off Time(ms) (LCAS)..............................................................................................................1238
A.21.4 WTR Time(s) (LCAS)......................................................................................................................1239
A.21.5 TSD (LCAS).....................................................................................................................................1240
A.21.6 Minimum Number of Members in the Transmit Direction..............................................................1240
A.22 Packet LPT Associated Parameters...........................................................................................................1241
A.22.1 Binding Status...................................................................................................................................1241
A.22.2 Primary Function Point.....................................................................................................................1241
A.22.3 Secondary Function Point Type........................................................................................................1242
A.22.4 Secondary Function Point.................................................................................................................1243
A.22.5 Fault Detection Mode.......................................................................................................................1244
A.22.6 User-Side Port Status........................................................................................................................1245
A.23 LPT Associated Parameters (TDM Mode)................................................................................................1245
A.23.1 LPT...................................................................................................................................................1245
A.23.2 Bearer Mode.....................................................................................................................................1246
A.23.3 Port-Type Port Hold-Off Time(ms)..................................................................................................1247
A.23.4 VCTRUNK Port Hold-off Time(ms)................................................................................................1247
A.24 IGMP Snooping Associated Parameters....................................................................................................1248
A.24.1 Protocol Enable (IGMP Snooping Protocol)....................................................................................1248
A.24.2 Multicast Aging Time.......................................................................................................................1249
A.25 Test Frame Associated Parameters............................................................................................................1250
A.25.1 Frames to Send.................................................................................................................................1250
A.25.2 Status.................................................................................................................................................1250
A.25.3 Counter of Frames Sent....................................................................................................................1251
A.25.4 Counter of Received Response Test Frame......................................................................................1252
A.25.5 Counter of Test Frames to Receive..................................................................................................1252
A.25.6 Bearer Mode (Ethernet Test)............................................................................................................1253
A.25.7 Send Mode (Ethernet Test)...............................................................................................................1253
A.26 Orderwire Associated Parameters..............................................................................................................1254
A.26.1 Call Waiting Time(s)........................................................................................................................1254
Issue 03 (2012-11-30)

xxxiv
OptiX OSN 7500 II/7500/3500/1500

Contents
A.26.2 Conference Call................................................................................................................................1255

A.26.3 Phone................................................................................................................................................1256
A.26.4 Available Orderwire Port..................................................................................................................1256
A.26.5 Available Conference Call Port........................................................................................................1257
A.26.6 Subnet No. Length............................................................................................................................1258
A.26.7 Subnet (Subnet No. for the Optical Interface)..................................................................................1259
A.26.8 No.(F1 Data Port).............................................................................................................................1259
A.26.9 Data Channel (F1 Data Port)............................................................................................................1260
A.26.10 Overhead Byte (Broadcast Data Port)............................................................................................1261
A.26.11 Working Mode (Broadcast Data Port)............................................................................................1262
A.26.12 Broadcast Data Source (Broadcast Data Port)................................................................................1263
A.26.13 Broadcast Data Sink (Broadcast Data Port)....................................................................................1264
A.27 Clock Associated Parameters....................................................................................................................1264
A.27.1 External Clock Output Mode............................................................................................................1265
A.27.2 External Clock Output Timeslot.......................................................................................................1265
A.27.3 External Source Output Threshold...................................................................................................1267
A.27.4 2M Phase-Locked Source Fail Condition.........................................................................................1268
A.27.5 2M Phase-Locked Source Fail Action..............................................................................................1269
A.27.6 Clock Source Priority Sequence (1 Is the Highest)..........................................................................1270
A.27.7 Clock Source Threshold...................................................................................................................1271
A.27.8 Protection Status...............................................................................................................................1272
A.27.9 AIS Alarm Generated.......................................................................................................................1273
A.27.10 B1 BER Threshold-Crossing Generated.........................................................................................1274
A.27.11 B2-EXC Alarm Generated..............................................................................................................1275
A.27.12 Higher Priority Clock Source Reversion Mode..............................................................................1276
A.27.13 Clock Source WTR Time...............................................................................................................1277
A.27.14 Switching Status (Clock)................................................................................................................1278
A.27.15 Lock Status (Clock)........................................................................................................................1279
A.27.16 Clock Source ID.............................................................................................................................1279
A.27.17 Synchronous Source.......................................................................................................................1280
A.27.18 Synchronous Status Byte................................................................................................................1281
A.27.19 S1 Byte Synchronization Quality Information...............................................................................1282
A.27.20 NE Clock Working Mode...............................................................................................................1284
A.27.21 Clock Source Quality......................................................................................................................1285
A.27.22 S1 Byte Received............................................................................................................................1286
A.27.23 Line Port (Clock)............................................................................................................................1287
A.27.24 Control Status (Clock)....................................................................................................................1288
A.27.25 Line Port (Clock ID).......................................................................................................................1289
A.27.26 Enabled Status (Clock ID)..............................................................................................................1290
A.27.27 Data Output Method in Holdover Mode.........................................................................................1291
A.27.28 Manual Setting of 0 Quality Level.................................................................................................1292
A.27.29 Retiming Mode...............................................................................................................................1294
Issue 03 (2012-11-30)

xxxv
OptiX OSN 7500 II/7500/3500/1500

Contents
A.28 Protection Associated Parameters..............................................................................................................1295

A.28.1 Switching Mode (MSP)....................................................................................................................1295
A.28.2 Initiation Condition (SNCP).............................................................................................................1296
A.28.3 Group Type (SNCP).........................................................................................................................1296
A.28.4 Configure SNCP Tangent Ring........................................................................................................1297
A.28.5 Source(Sink)Timeslot Range(e.g.1,3-6)...........................................................................................1298
A.28.6 Switching Status (BPS).....................................................................................................................1299
A.28.7 Switching Status (PPS).....................................................................................................................1299
A.28.8 External Switching Command Type (BPS)......................................................................................1300
A.28.9 External Switching Command Type (PPS)......................................................................................1301
A.29 Other Parameters.......................................................................................................................................1303
A.29.1 E1/T1 Interconnection......................................................................................................................1303
A.29.2 T1 Frame Structure...........................................................................................................................1304
A.29.3 E1 Frame Structure...........................................................................................................................1305
A.29.4 Service Mode....................................................................................................................................1306
A.29.5 Service Type.....................................................................................................................................1307
A.29.6 Service Frame Format.......................................................................................................................1308
A.29.7 Connection Mode (NE Attribute).....................................................................................................1309
A.29.8 Enable Tandem Connection at the Source........................................................................................1309
A.29.9 APId to be Sent at the Source...........................................................................................................1310
A.29.10 Optimize Higher Order Pass-Through............................................................................................1311
B Glossary....................................................................................................................................1312
Issue 03 (2012-11-30)

xxxvi
OptiX OSN 7500 II/7500/3500/1500

1 MPLS Basics
MPLS Basics
About This Chapter

This chapter describes the basics of the Multiprotocol Label Switching (MPLS) technology.
1.1 Introduction
This section provides the definition of MPLS and describes its purpose.
1.2 Basic Concepts
This section describes the basic concepts associated with MPLS.
1.3 Reference Standards and Protocols
This section describes the standards and protocols associated with MPLS basics.
1.4 Availability
The MPLS function requires the support of the applicable equipment, boards, and software.
1.5 Principles
On an MPLS network, LSRs enable the packets with the same characteristics to be transmitted
on one LSP based on a unified forwarding mechanism.
Issue 03 (2012-11-30)

OptiX OSN 7500 II/7500/3500/1500

1 MPLS Basics
1.1 Introduction
This section provides the definition of MPLS and describes its purpose.
Definition
Based on IP routes and control protocols, MPLS is a connection-oriented switching technology
for the network layer. MPLS uses short and fixed-length labels at different link layers for packet
encapsulation, and switches labels based on the encapsulated labels.
MPLS has two planes: control plane and forwarding plane. The control plane is connectionless,
featuring powerful and flexible routing functions to meet network requirements for a variety of
new applications. This plane is mainly responsible for label distribution, setup of label
forwarding tables, and setup and removal of label switched paths (LSPs). The forwarding plane
is also called the data plane. It is connection-oriented and supports Layer 2 networks such as
ATM and Ethernet networks. The forwarding plane adds or deletes IP packet labels, and forwards
the packets according to the label forwarding table.
Purpose
In the packet domain, MPLS helps to set up MPLS tunnels to carry PWs that transmit a variety
of services on a PSN in an end-to-end manner. These services include TDM, ATM, and Ethernet
services. Figure 1-1 shows the typical MPLS application in the packet domain. In the figure,
the services between the NodeBs and RNCs are transmitted by PW1 and PW2 carried by the
MPLS tunnel.
Figure 1-1 Typical MPLS application
Ethernet/ATM/TDM
Ethernet/ATM/TDM
PSN
NodeB
RNC
PW1
PW2
NE1
MPLS tunnel
NodeB
Ethernet/ATM/TDM
NE2
RNC
Ethernet/ATM/TDM
Packet transmission equipment
1.2 Basic Concepts

This section describes the basic concepts associated with MPLS.
Issue 03 (2012-11-30)

OptiX OSN 7500 II/7500/3500/1500

1 MPLS Basics
1.2.1 MPLS Network Architecture

An MPLS network, also called an MPLS domain, is a network area that consists of
interconnected label switching routers (LSRs). An LSR, also called an MPLS node, is a network
device that performs MPLS label switching and packet forwarding.
Figure 1-2 shows the MPLS network architecture. On an MPLS network, LSRs on the network
edge are called label edge routers (LERs), and LSRs within the network range are called core
LSRs. An LER may have one or more adjacent non-LSR nodes, but all the adjacent nodes of a
core LSR are LSRs.
Figure 1-2 MPLS network architecture
LER
Other
MPLS
network
LER
LSR
MPLS
network
Core LSR
LSR
Other
MPLS
network
LER
LER
Other
MPLS
network
An LSR ID uniquely identifies an LSR on an MPLS network. An LSR ID can be 4-byte long or
16-byte long. A 4-byte LSR ID is based on an IPv4 address, and a 16-byte LSR ID is based on
an IPv6 address.
NOTE
Currently, the Hybrid MSTP equipment supports only LSR IDs based on IPv4 addresses.
1.2.2 LSP
Label switched paths (LSPs), also called MPLS tunnels, are classified into various types
depending on different classification criteria.
Basic Concepts of LSPs

On an MPLS network, an LSR adopts the same label switching mechanism to forward packets
with the same characteristics. The packets with the same characteristics are called a forwarding
equivalence class (FEC). The path along which an FEC travels through the MPLS network is
called an LSP, or an MPLS tunnel.
To provide a unified interface for upper-level applications of an LSP, the system needs to assign
an ID to the LSP. This ID is called an LSP ID or tunnel ID. An LSP ID is 4-byte long, and is
only valid for the local LSR.
Issue 03 (2012-11-30)

OptiX OSN 7500 II/7500/3500/1500

1 MPLS Basics
An LSP is unidirectional. As shown in Figure 1-3, LSRs on an LSP can be classified into the
following types:
l
Ingress
An LSP ingress node pushes a label onto the packet for MPLS packet encapsulation and
forwarding. One LSP has only one ingress node.
Transit
An LSP transit node swaps labels and forwards MPLS packets according to the label
forwarding table. One LSP may have one or more transits nodes.
Egress
An LSP egress node pops the label and recovers the packet for forwarding. One LSP has
only one egress node.
Figure 1-3 Classification of LSRs on an LSP
MPLS
network
Other
MPLS
network
Ingress
Transit
Transit
Egress
Other
MPLS
network
LSP
LSP Types
LSPs are classified into various types depending on different classification criteria. For details,
see Table 1-1.
Table 1-1 LSP types
Issue 03 (2012-11-30)
Aspect
LSP Type
Definition
Support
Capability
Setup mode
Static tunnel
It refers to an LSP for

which a static label is
configured by using
the management
plane.
The Hybrid MSTP

equipment supports
static tunnels.
Dynamic tunnel
It refers to an LSP
established by
running the label
distribution protocol
(LDP).

OptiX OSN 7500 II/7500/3500/1500

1 MPLS Basics
Aspect
LSP Type
Definition
Support
Capability
Direction
Unidirectional
tunnel
It refers to an LSP in
a specific direction.
Bidirectional tunnel
It refers to a pair of
LSPs that have the
same path but reverse
directions.
The Hybrid MSTP

equipment supports
both types.
E-LSP
An E-LSP uses the

EXP field for
prioritizing packet
scheduling. One ELSP supports PWs
belonging to up to
eight scheduling
types.
L-LSP
An L-LSP uses the

MPLS label value for
prioritizing packet
scheduling priority.
One L-LSP supports
PWs belonging to
one scheduling type.
Uniform
When an egress node

pops the label, it
renews the packet
scheduling priority
according to the EXP
field in the label.
Pipe
When an egress pops

the label, it does not
renew the packet
scheduling priority.
DiffServ
identification mode
LSP mode
The Hybrid MSTP

equipment supports
E-LSP.
However, the Hybrid
MSTP equipment
does not support
prioritizing packet
discarding.
The Hybrid MSTP

equipment supports
both types.
1.2.3 Bearer Mode for MPLS Packets

The Hybrid MSTP equipment uses Ethernet frames to bear MPLS packets.
Figure 1-4 shows the format of an Ethernet frame that bears an MPLS packet.
Figure 1-4 Format of an Ethernet frame that bears an MPLS packet
Ethernet header
Destination
address
Issue 03 (2012-11-30)
Source
address
MPLS packet
FCS
(CRC-32)
802.1q header Length/Type

OptiX OSN 7500 II/7500/3500/1500

1 MPLS Basics
Destination address: It is the MAC address of the opposite interface, learned through the
Address Resolution Protocol (ARP). It changes at each hop.
Source address: It always takes the MAC address of the system. It changes at each hop.
802.1q header: The Hybrid MSTP equipment determines whether an Ethernet frame at the
egress port carries the 802.1q header based on the TAG attribute of an Ethernet port. If the
TAG attribute is Access, the Ethernet frame will not carry the 802.1q header; if the TAG
attribute is Tag aware, the VLAN ID of the 802.1q header in an MPLS packet is the tunnel
VLAN ID that is set on the NMS; if the tunnel VLAN ID is absent, the VLAN ID of the
802.1q header is the default VLAN ID (that is, 1) at the NNI port transmitting MPLS
packets.
Length/Type: It is always set to 0x8847. After detecting the value, the Hybrid MSTP
equipment considers the packet is the Ethernet frame carrying MPLS packet. The NE will
not detect MPLS packets at the ingress port based on the TAG attribute and VLAN ID of
an LSP.
MPLS packet: It consists of the MPLS label and Layer 3 user packet. For details on its
format, see 1.2.4 MPLS Label.
Frame check sequence (FCS): It is used to verify that the Ethernet frame is correct.
NOTE
The ARP is used to translate the IP address at the network layer (that is, logical address) into the MAC
address at the data link layer (that is, physical address). By default when the TAG attribute of a UNI port
is Tag ware, an ARP packet that is transmitted or received through an NNI port has a VLAN ID that is
the default value of the NNI port. Therefore, the TAG attribute and default VLAN ID of an NNI port must
be the same as those of a peer NNI port.
Both FE and GE ports use Ethernet frames to bear MPLS packets.
1.2.4 MPLS Label

MPLS uses short and fixed-length labels at different link layers for packet encapsulation, and
supports MPLS label stacking to form label stacks.
Label Format
The Hybrid MSTP equipment uses Ethernet frames to bear MPLS packets. Figure 1-5 shows
the format of the MPLS label.
Figure 1-5 Format of the MPLS label
20
Label
MPLS label
23 24
EXP
31bit
TTL
Layer 3 Payload
MPLS packet
Issue 03 (2012-11-30)

OptiX OSN 7500 II/7500/3500/1500

1 MPLS Basics
Label: This 20-bit field indicates the actual label value.
EXP: Theis 3-bit field is reserved for experimental use. On the Hybrid MSTP equipment,
the EXP is used to identify the priority of an MPLS packet, similar to the VLAN priority
specified in IEEE 802.1q.
S: This 1-bit field identifies the bottom of stack. MPLS supports multiple labels, that is,
label stacking. This bit is set to 1 for the bottom label in the label stack.
Time to Live (TTL): This 8-bit field has the same meaning as the TTL specified for IP
packets.
Label Stack
A label stack refers to an ordered set of labels. MPLS allows a packet to carry multiple labels.
The label next to the Layer 2 header is called the top label or outer label, and the label next to
the IP header is called the bottom label or inner label. Theoretically, an unlimited number of
MPLS labels can be stacked.
Figure 1-6 MPLS label stack
Label stack
Ethernet header
/PPP header
Outer label
Inner label
Layer 3 Payload
The label stack is organized as a Last In, First Out stack. The top label is always processed first.
Label Space
The value range for label distribution is called a label space. Two types of label space are
available:
l
Per-platform label space

An LSR uses one label space; that is, the labels are unique per LSR.
Per-interface label space

Each interface on an LSR uses a label space; that is, the labels are unique per interface, but
can be repeated on different interfaces.
The Hybrid MSTP equipment supports only the per-platform label space with a fixed value of
32768. Values of 0 to 15 are reserved for special use and cannot be assigned to LSPs as service
labels. Ingress labels and egress labels must be unique per NE.

This section describes the standards and protocols associated with MPLS basics.
The following standards and protocols are associated with MPLS:
l
IETF RFC 3031: Multiprotocol Label Switching Architecture
IETF RFC 3032: MPLS Label Stack Encoding
Issue 03 (2012-11-30)

OptiX OSN 7500 II/7500/3500/1500

1 MPLS Basics
1.4 Availability
The MPLS function requires the support of the applicable equipment, boards, and software.
Version Support
Applicable Equipment
Applicable Version
OptiX OSN 1500/3500
V100R009C03 and later
T2000
U2000
Applicable Version
OptiX OSN 7500
U2000
Applicable Version
OptiX OSN 7500 II
U2000
Hardware Support
Issue 03 (2012-11-30)
Applicable
Board
Applicable Version
N1PEG16
OptiX OSN 3500
N1PEX1
OptiX OSN 3500
N1PETF8
OptiX OSN 3500/7500
R1PEFS8
OptiX OSN 1500A/1500B
Q1PEGS2
R1PEGS1
N1PEG8
OptiX OSN 3500/7500
N1PEX2
OptiX OSN 3500/7500
N2PEX1
OptiX OSN 3500/7500

OptiX OSN 7500 II/7500/3500/1500

1 MPLS Basics
Applicable
Board
Applicable Version
N1PEFF8
OptiX OSN 3500/7500
R1PEF4F
TNN1EX2
OptiX OSN 7500 II
TNN1EG8
OptiX OSN 7500 II
TNN1ETMC
OptiX OSN 7500 II
TNN1EFF8
OptiX OSN 7500 II
1.5 Principles
On an MPLS network, LSRs enable the packets with the same characteristics to be transmitted
on one LSP based on a unified forwarding mechanism.
Basic Concepts of Packet Forwarding

l
Next Hop Label Forwarding Entry (NHLFE)

The NHLFE is fundamental to packet forwarding implemented by an LSR. An NHLFE
contains the following information: the next hop address, interface address, operation type
for labels, and the data link layer protocol to use. The operations to perform on the label
may be Push, Pop, Swap, and Null (retaining a label).
FEC to NHLFE (FTN)

The FTN maps each FEC to a set of NHLFEs. Only an ingress node supports this operation.
Incoming Label Map (ILM)

The ILM maps each incoming label to a set of NHLFEs. Only transit and egress nodes
support this operation.
MPLS Packet Forwarding Process

Figure 1-7 shows the MPLS packet forwarding process.
Issue 03 (2012-11-30)

OptiX OSN 7500 II/7500/3500/1500

1 MPLS Basics
Figure 1-7 MPLS packet forwarding process

FTN
ILM
ILM
ILM
Push
Swap
Swap
Pop
Label=20
PORT1 PORT2
NE A
Ingress
PORT3
PORT5 PORT6
PORT4
NE B
Transit
LSP
(LSP ID=101)
Label=22
Label=21
NE C
Transit
NE D
Egress
Label operation
The ingress, transit, and egress nodes handle an MPLS packet as follows.
Procedure on an Ingress Node

Table 1-2 provides the NHLFE for NE A (ingress node).
Table 1-2 NHLFE for NE A
LSP ID
Outgoing
Interface
Next Hop
Outgoing
Label
Operation
101
PORT 1
PORT 2
20
Push
NE A process an MPLS packet as follows:

1.
Receives a packet, and finds the LSP ID based on the FEC of the packet.
2.
Finds the NHLFE based on the LSP ID and then obtains the information such as outgoing
interface, next hop, outgoing label, and operation. The label operation for an ingress node
is Push.
3.
Pushes an MPLS label to the packet, and forwards the encapsulated MPLS packet to the
next hop.
Procedure on a Transit Node

Table 1-3 provides the NHLFE for NE B (transit node).
Table 1-3 NHLFE for NE B
Issue 03 (2012-11-30)
LSP ID
Outgoing
Interface
Next Hop
Outgoing
Label
Operation
101
PORT 3
PORT 4
21
Swap

10
OptiX OSN 7500 II/7500/3500/1500

1 MPLS Basics
NE B processes an MPLS packet as follows:

1.
Finds the LSP ID based on the label value of the MPLS packet received at the incoming
interface.
2.
Finds the NHLFE based on the LSP ID and then obtains the information such as outgoing
interface, next hop, outgoing label, and operation. The label operation for a transit node is
Swap.
3.
The outgoing label value of the NHLFE is 21. Thus, NE B replaces the old label value of
20 with a new label value of 21 and then sends the MPLS packet carrying the new label to
the next hop.
NOTE
If the value of the new label is equal to or greater than 16, the label operation is Swap. If the value of the
new label is less than 16, this label is special and needs to be processed according to the specific value of
the label.
The processing of an MPLS packet on NE C is similar to the that of an MPLS packet on NE B.
Procedure on an Egress Node

Table 1-4 provides the NHLFE for NE D (egress node).
Table 1-4 NHLFE of NE D
LSP ID
Outgoing
Interface
Next Hop
Outgoing
Label
Operation
101
Pop
NE D processes an MPLS packet as follows:

1.
Finds the LSP ID based on the label value of the MPLS packet received at the incoming
interface.
2.
Finds the NHLFE based on the LSP ID and then determines that the label operation is Pop.
3.
Pops the MPLS label and forwards the MPLS packet.
Issue 03 (2012-11-30)

11
OptiX OSN 7500 II/7500/3500/1500

2 PWE3
PWE3
About This Chapter

In a packet switched network (PSN), PWE3 is a Layer 2 service bearing technology that emulates
as faithfully as possible the basic behaviors and characteristics of ATM services, Ethernet
services, low-rate time division multiplexing (TDM) circuit services, and other services. Such
a technology can interconnect the traditional network with PSN network to share resources and
expand the network.
2.1 PWE3 Basics
This chapter describes the basics of pseudo wire emulation edge-to-edge (PWE3).
2.2 ATM PWE3
This chapter describes the ATM PWE3 feature.
2.3 ETH PWE3
This chapter describes the ETH PWE3 feature.
2.4 TDM PWE3
This chapter describes the TDM PWE3 feature.
Issue 03 (2012-11-30)

12
OptiX OSN 7500 II/7500/3500/1500

2 PWE3
2.1 PWE3 Basics

This chapter describes the basics of pseudo wire emulation edge-to-edge (PWE3).
2.1.1 Introduction
This section provides the definition of pseudo wire emulation edge-to-edge (PWE3) and
describes its purpose.
Definition
PWE3 is a Layer 2 service bearer technology that emulates the basic behaviors and
characteristics of services such as ATM/IMA, Ethernet, and TDM on a packet switched network
(PSN).
Aided by the PWE3 technology, conventional networks can be connected by a PSN. Therefore,
resource sharing and network scaling can be achieved.
Purpose
PWE3 aims to transmit various services such as ATM, Ethernet, and TDM over a PSN. Figure
2-1 shows the PWE3 application. The Ethernet, ATM, and TDM services between NodeBs and
RNCs are emulated by means of PWE3 on NE1 and NE2, and then are transmitted on the pseudo
wires (PWs) between NE1 and NE2.
Figure 2-1 Typical application of PWE3
Ethernet/ATM/TDM
Ethernet/ATM/TDM
PSN
NodeB
RNC
PW1
PW2
NE1
MPLS tunnel
NodeB
Ethernet/ATM/TDM
NE2
RNC
Ethernet/ATM/TDM
2.1.2 Basic Concepts

This section describes the basic concepts associated with PWE3.
Issue 03 (2012-11-30)

13
OptiX OSN 7500 II/7500/3500/1500

2 PWE3
2.1.2.1 PWE3 Network Reference Model

In the PWE3 network reference model, a PW connects two provider edges (PEs), and an
attachment circuit (AC) connects a PE device and a customer edge (CE) device.
Figure 2-2 shows the PWE3 network reference model. One or more PWs are created between
PE1 and PE2 based on the service access requirements at the CEs. Several PWs can be carried
in one or more PSN tunnels. In this manner, native services can be transmitted over a PSN.
Figure 2-2 PWE3 network reference model
Emulated service
PW
PSN tunnel
Native
service
PE1
Native
service
PE2
PW1
CE1
CE2
PW2
AC
AC
AC: attachment circuit
CE: customer edge
PE: provider edge
PW: pseudo wire
NOTE
In the network reference model, PWs are carried in a PSN tunnel; that is, a single-segment PW (SS-PW).
The concepts found in the network reference model shown in Figure 2-2 are defined as follows.
CE
A CE is a device that originates or terminates a service. The CE is not aware that it is using an
emulated service rather than a native service.
PE
A PE is a device that provides PWE3 to a CE. Located at the edge of a network, a PE is connected
to a CE through an AC.
In the PWE3 network reference model, the mapping relationship between an AC and a PW is
determined once a PW is created between two PEs. As a result, Layer 2 services on CEs can be
transmitted over a PSN.
AC
An AC is a physical or virtual circuit attaching a CE to a PE. An AC can be, for example, an
Ethernet port, a VLAN, or a TDM link.
Issue 03 (2012-11-30)

14
OptiX OSN 7500 II/7500/3500/1500

2 PWE3
PW
A PW is a mechanism that carries emulated services from one PE to another PE over a PSN. By
means of PWE3, point-to-point channels are created, separated from each other. Users' Layer 2
packets are transparently transmitted on a PW.
PWs are available in two types depending on whether signaling protocols are used or not.
Specifically, a PW that does use signaling protocols is called a dynamic PW, whereas a PW that
does not use signaling protocols is called a static PW.
NOTE
The Hybrid MSTP equipment supports only static PWs.
Tunnel
A tunnel provides a mechanism that transparently transmits information over a network. In a
tunnel, one or more PWs can be carried. A tunnel connects a local PE and a remote PE for
transparently transmitting data.
PSN tunnels are available in several types, but the Hybrid MSTP equipment supports only MPLS
tunnels. In this document, PWE3 is generally based on the MPLS tunnel (LSP), unless otherwise
specified.
NOTE
PW and tunnel are both logical concepts. PW bandwidth is the bandwidth of its carried service, and tunnel
bandwidth is the bandwidth of all its carried PWs.
2.1.2.2 PWE3 Protocol Reference Model

The protocol reference model used by the Hybrid MSTP equipment includes pre-processing of
native services.
Figure 2-3 shows the PWE3 protocol reference model.
Issue 03 (2012-11-30)

15
OptiX OSN 7500 II/7500/3500/1500

2 PWE3
Figure 2-3 PWE3 protocol reference model
Forwarder
Native Service
Processing
Service
Interface
(TDM, ATM,
Ethernet,
etc)
To CE
Physical
Pre-processing
Emulated
Service
(TDM, ATM,
Ethernet,
etc)
Emulated Service
Payload
Encapsulation
Pseudo Wire
PW
Demultiplexer
PSN Tunnel,
PSN &
Physical
Headers
PSN Tunnel
Physical
To PSN
In the PWE3 protocol reference model, pre-processing involves the native service processing
layer and forwarder layer, whereas protocol processing involves the encapsulation layer and
demultiplexer layer. The main functions of these layers are described as follows.
Native Service Processing

Native service processing refers to the processing of service payloads (such as QoS processing),
before emulation of the native services are received on an AC.
Forwarder
A forwarder selects the PW for the service payloads received on an AC. The mapping
relationships can be specified in the service configuration, or implemented through certain types
of dynamically configured information.
Payload Encapsulation Layer

The encapsulation layer provides support for real-time processing and encapsulates the data
transmitted on a PW into PWE3 packets in standard format. The encapsulation layer also
provides support for adding and extracting timing information, in addition to sequencing packets.
PW Demultiplexer Layer
The PW demultiplexer layer enables one or more PWs to be carried in a single PSN tunnel.
Issue 03 (2012-11-30)

16
OptiX OSN 7500 II/7500/3500/1500

2 PWE3
2.1.2.3 PWE3 Encapsulation Format

The specific PWE3 encapsulation format varies slightly according to the type of emulated
service, but a generic encapsulation format is also available.
Figure 2-4 shows the generic PWE3 encapsulation format. A PWE3 packet contains the MPLS
label, control word, and payload.
Figure 2-4 PWE3 encapsulation format
20
23 24
31bit
Tunnel label
EXP
TTL
PW label
EX
P
EXP
S
S
TT
L
TTL
Control Word
Laye 2
r PDU
Payload
MPLS label
Control word
Payload
MPLS Label
The MPLS labels include tunnel labels and PW labels, which are used to identify tunnels and
PWs respectively. The format of the tunnel label is the same as that of the PW label. For details,
see 1.2.4 MPLS Label.
Control Word
The 4-byte control word is a header used to carry packet information over an MPLS PSN.
The control word is used to check the packet sequence, to fragment packets, and to restructure
packets. As shown in Table 2-1, the specific format of the control word is determined by the
service type carried by PWE3 and the encapsulation mode adopted.
Table 2-1 Formats of the control word for various services in different encapsulation modes
Issue 03 (2012-11-30)
Service Type
Format of Control Word
TDM PWE3
SAToP
17
OptiX OSN 7500 II/7500/3500/1500

2 PWE3
Service Type
Format of Control Word

CESoPSN
ATM PWE3
ATM N-to-one cell encapsulation

ATM one-to-one cell encapsulation
ETH PWE3
Ethernet encapsulation
Payload
Payload indicates the payload of a service in a PWE3 packet.
2.1.2.4 MS-PW
A PW that is carried in a PSN tunnel is called a single-segment PW (SS-PW). A PW is called a
multi-segment PW (MS-PW) if it is segmented and carried in multiple PSN tunnels.
MS-PW Network Reference Model

Figure 2-5 shows the MS-PW network reference model.
Figure 2-5 MS-PW network reference model
Emulated service
MS-PW
PSN
tunnel
1
Native
service
T-PE1
PW1
PSN
tunnel
2
S-PE1
PW3
Native
service
TPE2
CE1
CE2
PW2
PW4
AC
AC
PW switching point
T-PE: terminating provider edge
S-PE: switching provider edge
In the preceding network reference model, T-PE1 and T-PE2 provide PWE3 services to CE1
and CE2. The PWs are carried in two PSN tunnels, and constitute the MS-PW.
The two tunnels (PSN tunnel 1 and PSN tunnel 2) that are used to carry PWs reside in different
PSN domains. PSN tunnel 1 extends from T-PE1 to S-PE1, and PSN tunnel 2 extends from SPE1 to T-PE2. Labels of PW1 carried in PSN tunnel 1 and PW3 carried in PSN tunnel 2 are
swapped at S-PE1. Similarly, labels of PW2 carried in PSN tunnel 1 and PW4 carried in PSN
tunnel 2 are swapped at S-PE1.
Issue 03 (2012-11-30)

18
OptiX OSN 7500 II/7500/3500/1500

2 PWE3
MS-PW Application
Compared with the SS-PW, the MS-PW has the following characteristics:
l
Reduces required tunnel resources.
Traverses different PSNs.
Provides segment-based protection for tunnels.
The following paragraphs and figures compare the application scenarios of the SS-PW and MSPW to show that it is easier for the MS-PW to implement segment-based protection for tunnels.
Figure 2-6 shows the SS-PW networking mode. The services between PE1 and PE2 are
transmitted on PW1 carried in MPLS tunnel 1. Both MPLS tunnel 1 and MPLS tunnel 2 are
configured with 1:1 protection. Protection, however, fails to be provided if disconnection faults
occur on different sides of the operator device (called the P device).
Figure 2-6 SS-PW application
SS-PW
MPLS tunnel 1
PW1
PE1
PW1
PW1
PE2
PW1
MPLS tunnel 2
Figure 2-7 shows the MS-PW networking mode. The services between T-PE1 and T-PE2 are
transmitted on PW1 carried in MPLS tunnel 1 and PW2 carried on MPLS tunnel 2. The paired
tunnels (MPLS tunnel 1 and MPLS tunnel 3; MPLS tunnel 2 and MPLS tunnel 4) are configured
with 1:1 protection. In this configuration, protection can still be provided even when
disconnection faults occur on different sides of the S-PE1 device.
Figure 2-7 MS-PW application
MS-PW
MPLS tunnel 1
MPLS tunnel 2
PW1
PW2
PW2
PW1
T-PE1
MPLS tunnel 3
S-PE1
MPLS tunnel 4
T-PE2
Issue 03 (2012-11-30)

19
OptiX OSN 7500 II/7500/3500/1500

2 PWE3
2.1.2.5 VCCV
As specified in IETF RFC5085, virtual circuit connectivity verification (VCCV) is an end-toend fault detection and diagnostics mechanism for a PW. The VCCV mechanism is, in its
simplest description, a control channel between a PW's ingress and egress points over which
connectivity verification messages can be sent.
The VCCV messages are exchanged between PEs to verify connectivity of PWs. To ensure that
VCCV messages and PW packets traverse the same path, VCCV messages must be encapsulated
in the same manner as PW packets and be transmitted in the same tunnel as the PW packets.
VCCV messages have the following formats.
Format of a VCCV Message Based on Control Word

Figure 2-8 Format of a VCCV message based on control word
20
23 24
31bit
Tunnel label
EXP
TTL
PW label
EX
P
EXP
S
S
TT
L
TTL
0001 Version
Reserved
Channel type
Laye
MPLS echor message (IPv4 UDP)
The control word in a VCCV message is defined as follows:

l
Header: This field is always 0001.
Version: This field is always 0.
Reserved: This field is always 0.
Channel type: The Channel Type is set to 0x0021 for IPv4 payloads and 0x0057 for IPv6
payloads.
The payloads are MPLS echo packets encapsulated in IPv4 UDP.
Issue 03 (2012-11-30)

20
OptiX OSN 7500 II/7500/3500/1500

2 PWE3
Format of a VCCV Message Based on OAM Alert Label

Figure 2-9 Format of a VCCV message based on OAM alert label
20
23 24
31bit
Tunnel label
EXP
TTL
PW label
EX
P
EXP
S
S
TT
L
TTL
EXP
TTL: 1
Label : 1 (OAM Alert Label)
MPLS echo packet (IPv4 UDP)
The main fields in a VCCV message based on OAM alert label are defined as follows:
l
Label: The value of this field is 1 and indicates an OAM packet.
Time to Live (TTL): The value of this field is set to 1, to ensure that the MPLS OAM packet
is not transmitted beyond the sink end of the monitored LSP.
The payloads are MPLS echo packets encapsulated in IPv4 UDP.
2.1.3 Reference Standards and Protocols

This section describes the standards and protocols associated with PWE3 basics.
The following standards and protocols are associated with PWE3:
l
IETF RFC 3916: Requirements for Pseudo-Wire Emulation Edge-to-Edge (PWE3)
IETF RFC 3985: Pseudo Wire Emulation Edge-to-Edge (PWE3) Architecture
IETF RFC 5085: Pseudowire Virtual Circuit Connectivity Verification (VCCV): A Control
Channel for Pseudowires
IETF RFC 5254: Requirements for Multi-Segment Pseudowire Emulation Edge-to-Edge

(PWE3)
2.1.4 Availability
The PWE3 function requires the support of the applicable equipment, boards, and software.
Version Support
Issue 03 (2012-11-30)
Applicable Version
OptiX OSN 1500/3500
T2000

21
OptiX OSN 7500 II/7500/3500/1500

2 PWE3
Applicable Version
U2000
Applicable Version
OptiX OSN 7500
U2000
Applicable Version
OptiX OSN 7500 II
U2000
Hardware Support
Issue 03 (2012-11-30)
Applicable
Board
Applicable Version
N1PEG16
OptiX OSN 3500
N1PEX1
OptiX OSN 3500
N1PETF8
OptiX OSN 3500/7500
R1PEFS8
Q1PEGS2
R1PEGS1
N1PEG8
OptiX OSN 3500/7500
N1PEX2
OptiX OSN 3500/7500
N2PEX1
OptiX OSN 3500/7500
N1PEFF8
OptiX OSN 3500/7500
R1PEF4F
N1CQ1
OptiX OSN 7500/3500
N1MD12
OptiX OSN 7500/3500
N1MD75
OptiX OSN 7500/3500
R1ML1

22
OptiX OSN 7500 II/7500/3500/1500

2 PWE3
Applicable
Board
Applicable Version
TNN1EX2
OptiX OSN 7500 II
TNN1EG8
OptiX OSN 7500 II
TNN1ETMC
OptiX OSN 7500 II
TNN1AFO1
OptiX OSN 7500 II
TNN1D75E
OptiX OSN 7500 II
TNN1D12E
OptiX OSN 7500 II
TNN1CO1
OptiX OSN 7500 II
TNN1EFF8
OptiX OSN 7500 II
2.1.5 Principles
The SS-PW and MS-PW use different packet forwarding mechanisms.
2.1.5.1 Packet Forwarding Process of SS-PW

In the SS-PW networking mode, the PW label is not swapped during the packet forwarding
process.
Figure 2-10 shows the packet forwarding process in the SS-PW networking mode.
Figure 2-10 SS-PW packet forwarding process
PSN
MPLS tunnel
AC
PW1
PE1
CE1
(NodeB)
AC
PW1
PE2
B
CE2
(RNC)
Payload
PW label
A
Tunnel label A
Tunnel label B
NOTE
The PWs are invisible to the P device on a PSN; the P device provides transparent transport in tunnels.
Issue 03 (2012-11-30)

23
OptiX OSN 7500 II/7500/3500/1500

2 PWE3
The local PE (PE1) forwards packets as follows:

1.
Extracts the local service packets that are transmitted by CE1 from the AC.
2.
Pre-processes the service payloads before PWE3 emulation.
3.
Uses the forwarder to map service payloads to the corresponding PW.
4.
Encapsulates the data transmitted on a PW into PWE3 packets in standard format. The
process involves generation of the control word, and adding of the PW label and tunnel
label (tunnel label A) to the data.
5.
Maps the PW into the MPLS tunnel for transmission.
The P device forwards packets as follows:

When PWE3 packets transmitted from PE1 to PE2 traverse the P device, the tunnel label in the
packets is swapped. That is, tunnel label A is changed to tunnel label B.
The remote PE (PE2) forwards packets as follows:
1.
Demultiplexes the PW from the MPLS tunnel.
2.
Decapsulates the PW, and removes the tunnel label (tunnel label B), PW label, and control
word.
3.
Extracts service payloads from the PW.
4.
Restores service payloads to the local service packets.
5.
Selects an AC by using the forwarder, and forwards the packets to CE2 at the remote end
over the AC.
2.1.5.2 Packet Forwarding Process of MS-PW

In the MS-PW networking mode, the PW label is swapped at S-PE during the packet forwarding
process.
Figure 2-11 shows the packet forwarding process in the MS-PW networking mode.
Figure 2-11 MS-PW packet forwarding process of MS-PW
PSN
AC
CE
1
(NodeB)
T-PE1
Payload
PW label A
PW label B
Tunnel label A
Tunnel label B
Tunnel 1
Tunnel 2
PW1
PW2
A
A
S-PE1
B
B
AC
T-PE2
CE
2
(RNC)
Issue 03 (2012-11-30)

24
OptiX OSN 7500 II/7500/3500/1500

2 PWE3
The T-PE in the MS-PW networking mode forwards packets in the same manner as PE in the
SS-PW networking mode. In the MS-PW networking mode, S-PE needs to swap the tunnel label
and PW label.
The S-PE device (S-PE1) forwards packets as follows:
When PWE3 packets transmitted from PE1 to PE2 traverse the P device, the tunnel label in the
packets is swapped. That is, tunnel label A is changed to tunnel label B. In addition, the PW
label in the packets is swapped. That is, PW label A is changed to PW label B.
2.2 ATM PWE3

This chapter describes the ATM PWE3 feature.
2.2.1 Introduction
This section provides the definition of ATM PWE3 and describes its purpose.
Definition
The ATM PWE3 technology emulates the basic behaviors and characteristics of ATM services
on a packet switched network (PSN) by using the PWE3 mechanism, so that the emulated ATM
services can be transmitted on a PSN.
Purpose
Aided by the ATM PWE3 technology, conventional ATM networks can be connected by a PSN.
Specifically, ATM PWE3 allows transmitting conventional ATM services over a PSN by
emulating the ATM services.
The networking type of ATM PWE3 can be one-to-one, N-to-one or ATM-TRANS depending
on the encapsulation type of ATM PWE3 packets. It is obvious that ATM PWE3 helps to transmit
ATM services over the PSN, without adding ATM equipment or changing the configuration of
the ATM CE equipment.
Figure 2-12 Typical application of ATM PWE3 (in the one-to-one encapsulation mode)
PSN
PW
AC
AC
CE1
PE1
LSP
PE2
CE2
ATM PWE3
1-to-1 ATM
PWE3
service
Issue 03 (2012-11-30)
1-to-1 ATM
PWE3
service
NodeB

RNC
25
OptiX OSN 7500 II/7500/3500/1500

2 PWE3
Figure 2-13 Typical application of ATM PWE3 (in the N-to-one encapsulation mode)
CE1
PSN
PW
AC
AC
CE2
PE1
LSP
PE2
CE4
ATM PWE3
N-to-1 ATM
PWE3
service
CE3
N-to-1 ATM
PWE3
service
NodeB
RNC
NOTE
The cell encapsulation modes at both ends of a PW must be the same.

This section describes the basic concepts associated with ATM PWE3.
2.2.2.1 ATM N-to-One Cell Encapsulation

The ATM N-to-one cell encapsulation modes are classified into N-to-one VPC and N-to-one
VCC. In N-to-one VPC mode, one PW carries one or more VPCs; in N-to-one VCC mode, one
PW carries one or more VCCs.
Figure 2-14 shows the ATM N-to-one cell encapsulation. The PWE3 packet contains the MPLS
label, control word, and payload.
Issue 03 (2012-11-30)

26
OptiX OSN 7500 II/7500/3500/1500

2 PWE3
Figure 2-14 ATM N-to-one cell encapsulation
20
0000
23 24
31bit
Tunnel label
EXP
TTL
PW label
EX
P
EXP
S
S
TT
L
TTL
Flags Rsv Length
Sequnce number
VPI
VCI
PTI
ATM Cell Payload (48 byte)
.
..
VPI
Concatenated
Cells
VCI
PTI
.
..
MPLS label
Control word(Optional)
ATM service payload
Format of the MPLS Label

MPLS labels include tunnel labels and PW labels, which are used to identify tunnels and PWs
respectively. The format of the tunnel label is the same as that of the PW label. For details, see
1.2.4 MPLS Label.
Control Word
The meanings of the fields in the control word are as follows:
l
Flags: This field has a length of 4 bits. The 4 bits are not used and are set to 0s.
Rsv: This field has a length of 2 bits. The 2 bits are reserved and are generally set to 0s.
Length: This field has a length of 6 bits. The 6 bits are not used and are set to 0s.
Sequence number: This field has a length of 16 bits. It is optional and used to guarantee
ordered packet delivery. If the 16 bits are set to 0s, the algorithm for checking sequence
numbers is not used.
Issue 03 (2012-11-30)

27
OptiX OSN 7500 II/7500/3500/1500

2 PWE3
ATM Service Payload

The ATM service payload contains one or more ATM cells. Each ATM cell consists of the 4byte ATM header and the 48-byte ATM cell payload. The ATM header includes these four parts:
l
VPI: The ingress PE copies the VPI field contained in the ATM service payload of the
incoming ATM cell into this field. When the equipment on an MPLS PSN network sets up
a VP, the VPI field contained in the ATM service payload of the incoming ATM cell is not
used.
VCI: The ingress PE copies the VCI field contained in the ATM service payload of the
a VC, the VCI field contained in the ATM service payload of the incoming ATM cell is
not used.
PTI: This field indicates the bit payload type identifier and has a length of 3 bits. The ingress
PE copies the PTI field contained in the ATM service payload of the incoming ATM cell
into this field.
C: This field indicates the cell loss priority (CLP) and has a length of 1 bit. The C field is
used for congestion control. When the network becomes congested, cells with CLP = 1 are
discarded first. The ingress PE copies the CLP field contained in the ATM service payload
of the incoming ATM cell into this field.
NOTE
An ATM service payload has a length of 52 bytes (that is, a 4-byte ATM cell header and a 48-byte ATM cell
payload), whereas a general-purpose ATM cell has a length of 53 bytes. The 1-byte header error check (HEC)
field found in the ATM NNI cell is not present in the ATM service payload.
2.2.2.2 ATM One-to-One Cell Encapsulation

ATM one-to-one cell encapsulation modes are classified into one-to-one VPC and one-to-one
VCC. In one-to-one VPC mode, one PW carries one VPC; in one-to-one VCC mode, one PW
carries one VCC. The two modes adopt different encapsulation modes.
Figure 2-15 shows the encapsulation modes of one-to-one VPC and one-to-one VCC, including
the MPLS label, control word, ATM specific, and payload. ATM specific contains control
information required by the ATM service. ATM specific may be longer than one byte, which is
determined by the type of ATM service.
Issue 03 (2012-11-30)

28
OptiX OSN 7500 II/7500/3500/1500

2 PWE3
Figure 2-15 ATM one-to-one cell encapsulation

1-to-1 VCC ATM
1-to-1 VPC ATM
Control Word Required

0
0000
20
Control Word Optional
23 24
31bit
Tunnel label
EXP S
TTL
PW label
EX
S
EXP
S
P
TT
TT
L
L
Rsv
Sequnce number
M V Rsv PTI C
0000
20
23 24
31bit
Tunnel label
EXP S
TTL
PW label
EX
S
EXP
S
P
TT
TT
L
L
Rsv
Sequnce number
M V Rsv PTI C
VCI
ATM Cell Payload (48
byte)
.
.
.
M V Rsv PTI C

M VRsv PTI C
VCI
VCI
. byte)
.
.

. byte)
.
.
MPLS label
Control Word
ATM specific
ATM cell payload
For traditional ATM VPC, the egress PE cannot change the VCI field. For ATM one-to-one cell
encapsulation, the VCI field of the egress PE can be set to a different value from that of the
ingress PE. The VCI field of the egress PE is set to a value that is determined by the PW label.
MPLS Label
1.2.4 MPLS Label.
Control Word
The meanings of the fields in the control word are as follows:
l
0000: This field has a length of 4 bits and they must be set to 0.
Rsv: This field has a length of 4 bits. The 4 bits are reserved and are generally set to 0.
Sequence number: This field has a length of 16 bits. It is optional and used to guarantee
ordered packet delivery. If the 16 bits are set to 0, the algorithm for checking sequence
numbers is not used.
ATM Specific
The meanings of the fields in ATM specific are as follows:
l
M: This field has a length of 1 bit and indicates the transfer mode (that is, whether the
packet is an ATM cell or the payload of a frame). If M = 0, the packet is an ATM cell; if
M = 1, the packet is an ALL5 frame.
V: This field has a length of 1 bit and indicates whether the packet contains the VCI field.
If V = 0, the packet does not contain the VCI field; if VCI = 1, the packet contains the VCI
field.
Issue 03 (2012-11-30)

29
OptiX OSN 7500 II/7500/3500/1500

2 PWE3
NOTE
The VCC is an ATM connection mode that is based on the VCI value of the ATM cell header. That is, it
does not use the VCI field ( V = 0).
VPC is an ATM connection mode that is based on the VPI value of the ATM cell header. That is, each
cell contains the VCI field (V = 1).
Rsv: This field has a length of 2 bits. The 2 bits are reserved and are generally set to 0.
into this field.
ATM Service Payload

The ATM service payload contains one or more ATM cells. Each ATM cell consists of the 4byte ATM header and the 48-byte ATM cell payload. The ATM header includes these four parts:
l
VCI: The ingress PE copies the VCI field contained in the ATM service payload of the
a VC, the VCI field contained in the ATM service payload of the incoming ATM cell is
not used.
into this field.
NOTE
An ATM service payload has a length of 52 bytes (that is, a 4-byte ATM cell header and a 48-byte ATM cell
payload), whereas a general-purpose ATM cell has a length of 53 bytes. The 1-byte header error check (HEC)
field found in the ATM NNI cell is not present in the ATM service payload.
2.2.2.3 Number of ATM Cells Encapsulated in PWE3 Packets

The number of ATM cells encapsulated in PWE3 packets is determined by the parameters
Maximum Number of Concatenated Cells and Loading Time.
l
When Maximum Number of Concatenated Cells is set to 1, each PWE3 packet contains
only one ATM cell. Specifically, an ATM cell is directly encapsulated into a PWE3 packet
after the PE receives an ATM cell from the AC.
When Maximum Number of Concatenated Cells is set to a value greater than 1, the PE
uses the timer ATM Cell Concatenation Waiting Time. If the PE receives the maximum
number of ATM cells from the AC before the timer expires, the PE encapsulates all the
received ATM cells into a PWE3 packet and resets the timer. If the timer expires, the PE
encapsulates all the received ATM cells into a PWE3 packet and resets the timer, even if
the maximum number of ATM cells is not reached.
Issue 03 (2012-11-30)

30
OptiX OSN 7500 II/7500/3500/1500

2 PWE3
2.2.2.4 QoS of ATM PWE3

The QoS requirements depend on the category of the ATM service. As such, set the PHB service
level of an ATM PWE3 packet based on the category of the emulated ATM service to ensure
specific QoS objectives.
Specify an appropriate PHB service level for an ATM service based on its category. The
following table provides the default mapping relationships between ATM service categories and
PHB service levels.
Table 2-2 Mapping relationships between ATM service categories and PHB service levels
ATM Service Category
PHB Service Level
CBR
EF
RT-VBR
AF3
NRT-VBR
AF2
UBR+
AF1
UBR
BE
PORT-TRANS
BE
The OptiX OSN equipments perform QoS for ATM PWE3 packets as follows.
l
Ingress node
The PHB service class of an ATM PWE3 packet can be manually specified. When a packet
leaves an ingress node, the EXP value of the packet is determined according to the mapping
(between PHB service classes and EXP values) defined by the DiffServ domain of the
egress port.
Transit node
When a packet enters a transit node, the PHB service class of the packet is determined
according to the mapping (between EXP values and PHB service classes) defined by the
DiffServ domain of the ingress port. When a packet leaves a transit node, the EXP value
of the packet is determined according to the mapping (between PHB service classes and
EXP values) defined by the DiffServ domain of the egress port.
NOTE
When an MPLS tunnel uses a manually specified EXP value, the EXP value of ATM PWE3 packets is fixed,
not affected by a DiffServ domain.
2.2.3 Specifications
This section describes the capacity of the OptiX OSN equipment for supporting ATM PWE3.
Table 2-3 provides the specifications associated with ATM PWE3.
Issue 03 (2012-11-30)

31
OptiX OSN 7500 II/7500/3500/1500

2 PWE3
Table 2-3 Specifications associated with ATM PWE3

Item
Specifications
Service type
l Point-to-point service based on ATM connections.

That is, several ATM connections on one service
port correspond to one PW.
l Convergence service based on ATM connections.
That is, several ATM connections on different
service ports correspond to one PW.
l ATM transparent transmission service based on
port. That is, all the ATM connections on one port
correspond to one PW.
Connection type
l PVP
l PVC
l Transparent
Protection type
l No Protection
l PW APS
l Slave Protection Pair
Number of local ATM

connections supported by boards
OptiX OSN 7500 II

l TNN1AFO1: 4096
l TNN1D75E and TNN1D12E: 256
OptiX OSN 7500/3500: 256
Number of local ATM

connections supported by
equipment
OptiX OSN 7500 II:

4096
OptiX OSN 7500: 2048
Number of remote ATM

connections supported by boards
OptiX OSN 7500 II

l TNN1AFO1: 8192
OptiX OSN 3500/7500: 512
Number of remote ATM

connections supported by
equipment
OptiX OSN 7500 II: 8192
Number of local ATM services

supported by boards
OptiX OSN 7500 II

l TNN1AFO1: 2048
OptiX OSN 3500/7500: 64
Issue 03 (2012-11-30)

32
OptiX OSN 7500 II/7500/3500/1500

2 PWE3
Item
Specifications
Number of local ATM services

supported by equipment

OptiX OSN 7500: 512
Number of remote ATM services

supported by boards
OptiX OSN 7500 II

l TNN1AFO1: 4096
OptiX OSN 3500/7500: 128
Number of remote ATM services


Maximum number of
concatenated ATM cells
1 to 31 (10 by default)
ATM cell concatenation waiting

time
0 or 100 s to 50000 s, in steps of 1000 s
Number of ATM OAM

supported by boards
TNN1AFO1: 512
Number of ATM OAM

NOTE
When the number of ATM cells is 1, this parameter should be
set to 0.
N1MD12, N1MD75, TNN1D12E, TNN1D75E: 128
OptiX OSN 7500: 512

Issue 03 (2012-11-30)
ATM OAM type
CC, LB, RDI, and AIS
Maximum VPI value of ATM

services
l UNI port: 255
Maximum VCI value of ATM

services
65535
Number of transparently
transmitted ATM services
supported by boards
TNN1D75E and TNN1D12E on the OptiX OSN 7500

II, or OptiX OSN 7500/3500: 32
Number of IMA groups

II or OptiX OSN 3500/7500: 32
Maximum members in one IMA

group
16
Minimum number of active

transmitting links

II or OptiX OSN 3500/7500: 16
Maximum delay between links

(ms)
120
l NNI port: 4095
TNN1AFO1 on the OptiX OSN 7500 II: 8

33
OptiX OSN 7500 II/7500/3500/1500

2 PWE3

This section describes the standards and protocols associated with ATM PWE3.
The following standard is associated with ATM PWE3:
IETF RFC 4717: Definitions of Textual Conventions and Object-identities for ATM
Management
2.2.5 Availability
This section describes the support required by the application of the ATM PWE3 feature.
Version Support
Applicable Version
OptiX OSN 7500 II
U2000
Applicable Version
OptiX OSN 3500/7500
U2000
V100R005 and later
Hardware Support
Applicable Board
Applicable Version
TNN1AFO1
OptiX OSN 7500 II
TNN1D75E
OptiX OSN 7500 II
TNN1D12E
OptiX OSN 7500 II
N1MD12
OptiX OSN 3500/7500
N1MD75
OptiX OSN 3500/7500
2.2.6 Feature Dependency and Limitation

This section describes the limitations on and precautions for ATM PWE3 in the network design
phase, configuration and commissioning phase, and maintenance phase.
Issue 03 (2012-11-30)

34
OptiX OSN 7500 II/7500/3500/1500

2 PWE3
Network Design Principles

Applicable
Object
Dependency and Limitation

Details
Remarks
Connection
type of ATM
services
l VPC-based ATM services are

used to transmit ATM services
over VPCs. Traffic management
policies need to be configured
based on VPCs.
l VCC-based ATM services are

over VCCs. Traffic management
policies need to be configured
based on VCCs.
l The ATM services that can be
transparently transmitted by
ports are used when all ATM
services on a UNI port need to be
transparently transmitted to a
PW and no traffic management
is required.
ATM service
connection
l Different PWs are used for the

ATM connections leading to
different PEs.
l Different PWs are used to

transmit ATM connections of
various PHB classes over a PSN
network.
l If multiple ATM connections of
the same PHB class need to be
transmitted to the same
destination over a PSN network,
these ATM connections can be
mapped into one PW.
l One PW can carry ATM
connections from different UNI
ports.
ATM
convergence
service
l The TNN1AFO1 does not

support cross-optical-port
convergence services.
l The TNN1D12E and

TNN1D75E do not support
cross-area convergence services.
(Links 1-16 and links 17-32
belong to two areas.)
Issue 03 (2012-11-30)

35
OptiX OSN 7500 II/7500/3500/1500

2 PWE3
Applicable
Object

Details
Remarks
ATM CoS
mapping table
An ATM CoS mapping table needs

to be configured for each ATM
service.
In most cases, the default ATM CoS

mapping table will suffice. In a few
cases, a new ATM CoS mapping
table needs to be created.
UNI port
When the type of UNI port is

Fractional ATM or Fractional IMA,
serial ports must be created to bind
the timeslots that carry ATM
services within E1s.
UNI port
l When one or more E1s are used to transmit ATM services

between a PE and a CE, that is,
when UNI port type is ATM E1
or IMA E1: The E1 ports must
work in a Layer 2 mode; the E1
frame format and E1 frame mode
must be the same at both ends.
Generally, the E1 frame format
is CRC-4 multiframe and the E1
frame mode is PCM30.
l When some timeslots of one or
more E1s are used to transmit
ATM services between a PE and
a CE, that is, when the UNI port
type is Fractional ATM or
Fractional IMA: The E1 ports
must work in a Layer 1 mode; the
E1 frame mode must be PCM31;
the E1 frame format must be the
same at both ends. Generally, the
E1 frame format is CRC-4
multiframe.
PW carrying
ATM services
Issue 03 (2012-11-30)
Ensure that the PW parameter

settings are the same on the local and
opposite PEs.

36
OptiX OSN 7500 II/7500/3500/1500

2 PWE3
Applicable
Object

Details
Remarks
PW carrying
ATM services
l The 1-to-1 encapsulation mode

is recommended if one PW
carries one ATM connection. In
this mode, the control word must
be used.
l The N-to-1 encapsulation mode

is recommended if one PW
carries multiple ATM
connections. In this mode, the
control word is not used unless
otherwise specified.
l For High Speed Downlink
Packet Access (HSDPA), it is
recommended that a maximum
of 31 cells are concatenated and
the packet loading time is 50000
us.
PW carrying
ATM services
l For other services, it is

recommended that the maximum
number of concatenated cells
and packet loading time take
default values unless otherwise
specified.
Maximum number of
concatenated cells: 10
Packet loading time: 1000 us
PW carrying
ATM services
Enable the virtual circuit

connectivity verification (VCCV)
function to perform constant fault
detection for PWs.
l If a PW uses the control word, set

the control channel type to CW.
l If a PW does not use the control
word, set the control channel
type to Alert label.
PW carrying
ATM services
The ATM connection type must be

the same with the PW type.
QoS policy for

ATM services
l CBR is recommended for

signaling flows.
l RT-VBR is recommended for

voice services.
l UBR is recommended for data
services.
Issue 03 (2012-11-30)

37
OptiX OSN 7500 II/7500/3500/1500

2 PWE3
Applicable
Object

Details
Remarks
ATM service
protection
scheme
l Configure 1+1 linear MSP for

ATM services over UNI-side
optical ports on the TNN1AFO1.
l Configure tunnel APS or PW

APS for NNI ATM services.
Configuration and Commissioning Principles

None.
Maintenance Principles
None.
2.2.7 Principles
This section describes the principles of ATM PWE3.
NOTE
The ATM PWE3 in the encapsulation format of one-to-one VPC can be replaced by the ATM PWE3 in the
encapsulation format of N-to-one VPC; the ATM PWE3 in the encapsulation format of one-to-one VCC can be
replaced by the ATM PWE3 in the encapsulation format of N-to-one VCC. This section considers the ATM
PWE3 in the encapsulation format of N-to-one VCC as an example, which functions as a reference for the other
ATM types.
In the scenario as shown in Figure 2-16, the PEs emulate Ethernet services in the encapsulation
format of N-to-one VCC.
Issue 03 (2012-11-30)

38
OptiX OSN 7500 II/7500/3500/1500

2 PWE3
Figure 2-16 Principles of the ATM PWE3 service (N-to-one VCC)

VPI=10
VCI=10
VPI=20
VCI=20
CE1
PSN
AC
PW
CE3
AC
AC
PE1
LSP
PE2
VPI=21
VCI=21
MPLS Label
CE2
VPI=11
VCI=11
ATM Control Word

ATM Service
Payload

NodeB
RNC
ATM services
ATM PWE3 services

1.
Extracts the ATM service packets that are transmitted by CE1 and CE2 from the ACs.
2.
Pre-processes the service payloads prior to PWE3, including set-up of the ATM connections
and QoS policies between CE1 and PE1, and between CE2 and PE1.
3.
Maps ATM service payloads to the corresponding PW.
4.
Encapsulates the ATM services into PWE3 packets in standard format.
5.
Maps the PW into the LSP for transmission.

1.
Demultiplexes the PW from the LSP.
2.
Decapsulates the PW, and extracts service payloads from the PW.
3.
Restores the ATM services based on the service payloads.
Issue 03 (2012-11-30)

39
OptiX OSN 7500 II/7500/3500/1500

4.
2 PWE3
Selects the AC for forwarding packets, performs corresponding QoS processing, and
forwards the ATM service cells to CE3, based on the created ATM connections and QoS
policies between PE2 and CE3.
2.2.8 Configuring ATM PWE3

Operation tasks for ATM services include quickly creating ATM services and creating ATM
services on a per-NE basis.
For the operation tasks of ATM PWE3, see Configuration Guide (Packet Transport Domain):
Configuring ATM Interfaces
Creating an ATM Service by Using the Trail Function
Creating ATM Services on a Per-NE Basis
2.2.9 Configuration Example

This section uses an example to describe how to plan and configure UNI-UNI and UNI-NNI
ATM services according to network conditions.
For the configuration example of ATM PWE3, see Configuration Guide (Packet Transport
Domain):
l
Configuration Example (UNI-UNI ATM Services)
Configuration Example (UNIs-NNI ATM Services)
2.2.10 Relevant Alarms and Performance Events

This topic describes the alarms and performance events that are related to the ATM PWE3
feature.
2.2.10.1 Relevant Alarms

This topic describes the alarms related to ATM PWE3.
Table 2-4 lists the alarms that are related to the ATM PWE3.
Table 2-4 Alarms related to ATM PWE3
Issue 03 (2012-11-30)
Alarm Name
Meaning
ATMPW_LOSPKT_EX
C
The ATMPW_LOSPKT_EXC is an alarm indicating that the

number of lost ATM service packets exceeds the specified
threshold in a time unit. This alarm is reported when the number
of lost frames exceeds the specified threshold within a certain
period of time (2.5s by default). This alarm is cleared when the
number of lost frames is lower than the specified threshold within
another period of time (10s by default).

40
OptiX OSN 7500 II/7500/3500/1500

2 PWE3
Alarm Name
Meaning
ATMPW_MISORDER
PKT_EXC
The ATMPW_MISORDERPKT_EXC is an alarm indicating that

the number of lost disordered ATM packets exceeds the specified
of lost disordered ATM packets exceeds the specified threshold
within a certain period of time (2.5s by default). This alarm is
cleared when the number of lost disordered ATM packets is lower
than the specified threshold within another period of time (10s by
default).
ATMPW_UNKNOWN
CELL_EXC
The ATMPW_UNKNOWNCELL_EXC is an alarm indicating

that the number of unknown ATM cells exceeds the specified
of unknown ATM cells exceeds the specified threshold within a
certain period of time (2.5s by default). This alarm is cleared when
the number of unknown ATM cells is lower than the specified
threshold within another period of time (10s by default).
2.2.10.2 Relevant Performance Events

This topic describes the performance events related to ATM PWE3.
Table 2-5 lists the performance events that are related to ATM PWE3.
Table 2-5 Relevant Performance Events to ATM PWE3
Performance Event Name
Full Name
ATMPW_LOSPKTS
Count of lost packets
ATMPW_MISORDERPKTS
Count of out-of-order packets
ATMPW_SNDCELLS
Count of transmitted cells
ATMPW_RCVCELLS
Count of received cells
ATMPW_UNKNOWNCELLS
Count of unknown cells
2.2.11 Parameter Description

This topic describes the parameters required for configuring ATM PWE3.
2.2.11.1 Creating an ATM Service

This section describes the parameters for creating an ATM service.
Table 2-6 lists the parameters for creating an ATM service.
Issue 03 (2012-11-30)

41
OptiX OSN 7500 II/7500/3500/1500

2 PWE3
Table 2-6 Parameters for creating an ATM service

Field
Value
Description
Service ID
1 to 4294967295
Specifies the service ID.
Default: none
Set this parameter according to

the planning information.
Specifies the service name.
Service Name

Service Type
UNIs-NNI, UNI-UNI
Default: UNIs-NNI
Specifies the type of the ATM

service.
l UNIs-NNI: This value
applies to ATM PWE3
services. The attributes in
Connection, PW, and CoS
Mapping need to be
configured.
l UNI-UNI: This value applies
to common ATM services.
Only the attributes in
Connection need to be
configured.
Issue 03 (2012-11-30)

42
OptiX OSN 7500 II/7500/3500/1500

2 PWE3
Field
Value
Description
Connection Type
PVP, PVC, Port Transparent
Specifies the connection type of

the ATM service.
l If Service Type is UNIsNNI, the default value is

PVC.
l If Service Type is UNI-UNI,
the default value is PVP.
l PVP: Only the VPIs of the

source and sink are
exchanged.
l PVC: The VPIs and VCIs of
the source and sink are
exchanged.
For ATM PWE3 services (UNIsNNI):
l PVP: This value applies to
the N-to-1/1-to-1 VPC
encapsulation mode.
l PVC: This value applies to
the N-to-1/1-to-1 VCC
encapsulation mode.
Port Transparent: This value
applies if all services regardless
of their VPIs and VCIs are
transparently transmitted.
For details, see A.13.9
Connection Type(Per-NE
ATM Service Management).
Protection Type
Unprotected, PW APS, Slave

Protection Pair
Specifies the protection type of

the PW.
Default: Unprotected
This parameter is available only

when Service Type is UNIsNNI.
2.2.11.2 Connection
This section describes the parameters for creating a connection.
Table 2-7 lists the parameters for creating a connection.
Issue 03 (2012-11-30)

43
OptiX OSN 7500 II/7500/3500/1500

2 PWE3
Table 2-7 Parameters for creating a connection

Field
Value
Description
Connection Name
A character string of less than 64

characters, which may contain
letters, numbers, Chinese
characters, or special symbols.
Specifies a name for an ATM

connection.
Example: 28-N1D12E
Source Board
Slot ID-board name

Example: 28-N1D12E
Specifies the source board of the

ATM service.
Source Port
Port ID(Port-port ID)

Example: 1(Trunk-1)
Specifies the source port of the

ATM service.
Source VPI
(example:35,36-39)
Source VCI
(example:35,36-39)
ATM UNI cell: 0 to 255

NNI ATM cell: 0 to 4095
Specifies the VPI of the source

port of the ATM service.
Default: none

32 to 65535
Specifies the VCI of the source

port of the ATM service.
Default: none
This parameter does not need to

be set if Connection Type is
PVP.
PW ID
1 to 4294967295
Default: none
Specifies the ID of the PW that

carries ATM services.
Sink Board
Slot ID-board name

Example: 28-N1D12E
Specifies the sink board of the

ATM service.
l This parameter does not need
to be set if Service Type is
UNIs-NNI.
l This parameter needs to be set
if Service Type is UNI-UNI.
Issue 03 (2012-11-30)

44
OptiX OSN 7500 II/7500/3500/1500

2 PWE3
Field
Value
Description
Sink Port
Port ID(port-port ID)
Specifies the sink port of the

ATM service.
Example: 1(Trunk-1)
l This parameter does not need

to be set if Service Type is
UNIs-NNI.
l This parameter needs to be set
if Service Type is UNI-UNI
and its value must be different
from that of the source port.
Sink VPI(example:
35,36-39)
Sink VCI(example:
35,36-39)
UNI ATM cell: 0 to 255

NNI ATM cell: 0 to 4095
Specifies the VPI of the sink port

of the ATM service.
Default: none

32 to 65535
Specifies the VCI of the sink port

of the ATM service.
Default: none
This parameter does not need to

be set if Connection Type is
PVP.
-
Uplink Policy
Specifies the QoS policy of the

uplink ATM connection (from
the source direction to the sink
direction).
For details, see A.13.10 Uplink
Policy(Per-NE Configuration
for ATM Connections).
Downlink Policy
Specifies the QoS policy of the

downlink ATM connection
(from the sink direction to the
source direction).
Downlink Policy(Per-NE
Configuration for ATM
Connections).
Issue 03 (2012-11-30)

45
OptiX OSN 7500 II/7500/3500/1500

2 PWE3
2.2.11.3 SDH Ports

This section describes parameters for a SDH interface.
Table 2-8 Descriptions of the parameters of the general attributes of an SDH port
Field
Value
Description
Port
Slot ID-board name-port

ID
Displays the port name.
Example: 36-N1AFO1-1
(PORT-1)
Name
Port Mode
Displays or specifies the name of the port.
Example: Port1
Set this parameter according to the planning

information.
Layer 2
Specifies the mode of the SDH port. The fixed

value is Layer 2.
Layer 2 indicates the current ATM STM port.
Encapsulatio
n Type
ATM
Indicates the link layer encapsulation type of the

port. It specifies the link layer encapsulation type
that can be identified and processed by the port.
The fixed value is ATM.
ATM: The ATM encapsulation is identified and
processed.
Channelize
No
Specifies whether the port is channelized. The

fixed value is No.
No: The port is not channelized.
Max Data
Packet Size
(bytes)
Specifies the maximum packet length. The fixed

value is -.
Laser
Interface
Status
On, Off
Enables or disables the laser.
Default: On
The default value is recommended.
This parameter does not need to be set if Port

Mode is Layer 2.
Table 2-9 Descriptions of the parameters for SDH interface Layer 2 Attributes
Field
Value
Description
Port

ID
(PORT-1)
Issue 03 (2012-11-30)

46
OptiX OSN 7500 II/7500/3500/1500

2 PWE3
Field
Value
Description
Port Type
UNI, NNI
Specifies the type of the ATM port.
Default: UNI
l UNI: the port connecting user-side devices.

For example, the UNI port applies to the userside port on the common ATM network or to
the user-side port of the PE on the PSN
network that transmits ATM PWE3 services.
l NNI: the port connecting network-side
devices. For example, the NNI port applies to
the network-side port on the common ATM
network.
information.
ATM Cell
Payload
Scrambling
Enabled, Disabled
Default: Enabled
The ATM Cell Payload Scrambling (ATM

Interface Management) parameter specifies
whether to scramble the payload of cells on
asynchronous transfer mode (ATM) links.
l ITU-T G.804 stipulates that the payload (48
bytes) of ATM cells must be scrambled
before it is mapped into E1 signals.
Therefore, it is recommended that you set
ATM Cell Payload Scrambling to Enabled
for both end of an ATM link.
l ATM Cell Payload Scrambling must
assume the same value on the two ends of an
ATM link. Otherwise, packet loss will occur.
For details, see A.12.1 ATM Cell Payload
Scrambling(ATM Interface Management).
Min. VPI
UNI port: 0-255; NNI

port: 0-4095
Default: 0
The Min.VPI parameter specifies the minimum

virtual path identifier (VPI) value of the
permanent virtual paths (PVPs) and permanent
virtual channels (PVCs) that are applicable to a
selected board.
For details, see A.12.2 Min.VPI(ATM
Interface Management).
Max. VPI
UNI port: 0-255; NNI

port: 0-4095
Default: 255
Min. VCI
0-65535
Default: 65535
The Max. VPI parameter specifies the maximum

virtual path identifier (VPI) value of the
permanent virtual paths (PVPs) and permanent
virtual channels (PVCs) that are applicable to a
selected board.
The Min.VCI parameter specifies the minimum
virtual channel identifier (VCI) value for
permanent virtual channels (PVCs) that are
applicable to a selected board.
For details, see A.12.3 Min.VCI(ATM
Interface Management).
Issue 03 (2012-11-30)

47
OptiX OSN 7500 II/7500/3500/1500

2 PWE3
Field
Value
Description
Max. VCI
0-65535
The Max VCI parameter specifies the maximum

virtual channel identifier (VCI) value for
permanent virtual channels (PVCs) that are
applicable to a selected board.
Default: 65535
VCCSupported
VPI Count
0-256, 65535
Default: 65535
The VCC-Supported VPI Count parameter

specifies the number of virtual path identifiers
(VPIs) available for a permanent virtual channel
(PVC) connection at a port. That is, only the
specified number of VPIs can be adopted for
establishment of a PVC connection regardless of
the specified VPI value. In other circumstances,
the specified number of VPIs can be adopted for
establishment of a permanent virtual path (PVP)
connection.
For details, see A.12.4 VCC-Supported VPI
Count(ATM Interface Management).
Table 2-10 Descriptions of the parameters for Advanced Attributes of the SDH interface
Field
Value
Description
Port

ID
(PORT-1)
Laser
Transmissio
n Distance
(m)
Scrambling
Capability
Display the transmission distance of the laser.

The fixed value is -.
The Hybrid MSTP does not support this
parameter.
Suppresses multiple 0s and 1s in the data when
the Scrambling Capability is enabled. The fixed
value is -.
parameter.
CRC Check
Length
Specifies the length of the CRC field in the

mapping protocol. The fixed value is -.
parameter.
Clock Mode
Specifies the re-timing mode of a port. The fixed

value is -.
parameter.
Issue 03 (2012-11-30)

48
OptiX OSN 7500 II/7500/3500/1500

2 PWE3
Field
Value
Description
Loopback
Mode
Non-loopback, Inloop,
Outloop
Specifies the loopback status of the port.
Default: Non-loopback
The loopback mode is used for locating a fault.

Outloop is used for testing whether the port
module and external fiber or cable of a board are
proper. Inloop is used for testing whether the
cross-connect unit and service path of the
equipment are proper.
information.
2.3 ETH PWE3

This chapter describes the ETH PWE3 feature.
2.3.1 Introduction
This section provides the definition of ETH PWE3 and describes its purpose.
Definition
The ETH PWE3 technology emulates the basic behaviors and characteristics of Ethernet services
on a packet switched network (PSN) by using the PWE3 mechanism, so that the Ethernet services
can be transmitted on a PSN.
Purpose
ETH PWE3 aims to transmit Ethernet services over a PSN. Figure 2-17 shows the typical
application of ETH PWE3.
Figure 2-17 Typical application of ETH PWE3
PSN
PW
CE1
(NodeB)
AC
AC
PE1
Native
Ethernet
service
Issue 03 (2012-11-30)
LSP
CE2
(RNC)
PE2
ETH PWE3
Ethernet frame

Native
Ethernet
service
ETH PWE3 packet
49
OptiX OSN 7500 II/7500/3500/1500

2 PWE3

This section describes the basic concepts associated with ETH PWE3.
2.3.2.1 Format of an ETH PWE3 Packet

After an Ethernet frame is encapsulated into a PWE3 packet, the PWE3 packet contains the
MPLS label, control word (optional), and payload.
Packet Format
Figure 2-18 shows the format of an ETH PWE3 packet, consisting of the MPLS label, control
word, and payload.
Figure 2-18 Format of an ETH PWE3 packet
20
0000
23 24
31bit
Tunnel label
EXP
TTL
PW label
EX
P
EXP
S
S
TT
L
TTL
Reserved
Sequence number
Payload
(Ethernet Frame)
MPLS label
Control word (Optional)
Payload
MPLS Label
1.2.4 MPLS Label.
Control Word
The 4-byte control word within an ETH PWE3 packet is optional and contains the following
fields:
l
Issue 03 (2012-11-30)
0000: This field indicates the first 4 bits and they must be set to 0.
50
OptiX OSN 7500 II/7500/3500/1500

2 PWE3
Reserved: This field has a length of 12 bits and is reserved.
Sequence number: This field has a length of 16 bits and indicates the delivery sequence
number of an ETH PWE3 packet. Its initial value is random, and is increased by one integer
with each ETH PWE3 packet sent.
Payload
The payload refers to the Ethernet frame that is encapsulated into an ETH PWE3 packet. One
ETH PWE3 packet can encapsulate only one Ethernet frame. During the encapsulation, the preset
PW Encapsulation Mode is adopted.
2.3.2.2 PW Encapsulation Mode

The service-delimiting tag and PW encapsulation mode are used to indicate how the outer layer
of the C-/S-VLAN tag of an Ethernet packet is processed when the Ethernet packet is forwarded.
PW Encapsulation Mode
The PW encapsulation mode is used to indicate whether a P-Tag is added when an Ethernet
frame is encapsulated into an ETH PWE3 packet. The PW encapsulation modes are classified
into two categories:
l
Raw mode
In this mode:
When the service-delimiting tag is User, in the direction that an Ethernet frame enters
the PW, the PE directly encapsulates the Ethernet frame into a PWE3 packet after
receiving it from the AC; in the direction that an Ethernet frame leaves the PW, the PE
transmits the decapsulated Ethernet frame to the AC.
When the service-delimiting tag is Service, in the direction that an Ethernet frame enters
the PW, the PE strips the outer tag (P-Tag) of the Ethernet frame and encapsulates it
into a PWE3 packet after receiving it from the AC; in the direction that an Ethernet
frame leaves the PW, the PE adds a P-Tag to the decapsulated Ethernet frame before
transmitting it to the AC.
Tagged mode
In this mode:
When the service-delimiting tag is User, in the direction that an Ethernet frame enters
the PW, the PE adds a P-Tag and encapsulates the Ethernet frame into a PWE3 packet
after receiving it from the AC (the added P-Tag is called request VLAN); in the direction
that an Ethernet frame leaves the PW, the PE strips a P-Tag off the decapsulated Ethernet
frame before transmitting it to the AC.
When the service-delimiting tag is Service, in the direction that an Ethernet frame enters
the PW, the PE swaps P-Tag for U-Tag, and encapsulates the Ethernet frame into a
PWE3 packet after receiving it from the AC (the added P-Tag is called request VLAN);
in the direction that an Ethernet frame leaves the PW, the PE decapsulates the Ethernet
frame, and swaps U-Tag for P-Tag before transmitting it to the AC.
NOTE
For the Hybrid MSTP equipment, you can set a request VLAN value for each PW whose encapsulation
mode is the Ethernet tagged mode, but the T-PID value in the request VLAN must be unique on the NE.
Issue 03 (2012-11-30)

51
OptiX OSN 7500 II/7500/3500/1500

2 PWE3
Typical Application
Figure 2-19 shows a NodeB backhaul network.
l
The RNC can process S-VLAN tags. It allocates an S-VLAN ID to each NodeB to separate
the services of a NodeB from those of another.
The NodeB can process C-VLAN tags only. It allocates an C-VLAN ID to each type of
service on a NodeB.
Therefore, the request VLAN function must be enabled to add S-VLAN IDs to isolate the
services on different NodeBs.
Set the request VLAN values on NE1 and NE2 as follows:
l
If the PW1 encapsulation mode of NE1 is the tagged mode, set the request VLAN to 100;
if PW2 encapsulation mode of NE1 is the tagged mode, set the request VLAN to 200.
The PW1 and PW2 encapsulation mode of NE2 is the raw mode.
NE1 and NE2 process the services as follows:

l
In the service uplink direction, to transmit the service of NodeB 1 from NE1 to PW1, NE1
adds the request VLAN (S-VLAN) 100 to the service because the PW encapsulation mode
is the tagged mode; to transmit the service from NE2 to the RNC, NE2 decapsulates the
service packet and transparently transmits the S-VLAN tag (100). Likewise, the service of
NodeB 2 carries an S-VLAN tag (200) when transmitted from NE2 to the RNC. In this
case, the services at the same port (PORT1) are isolated.
In the service downlink direction, to transmit the service of the RNC from NE2 to PW1,
NE2 directly adds the S-VLAN tag to the service because the PW encapsulation mode is
the raw mode; to transmit the service from NE1 to NodeB 1, NE1 decapsulates the service
packet and strips the S-VLAN tag. Likewise, the service of the NodeB 2 does not carry an
S-VLAN tag when transmitted from NE1 to NodeB 2.
Figure 2-19 Typical application of the PW encapsulation mode

PW1: tagged mode
Request VLAN: 100
PW1: raw mode

PORT 1
C-VLAN: 100-200
PSN
NodeB 1
AC
AC
S-VLAN: 100
AC
PW1
NE1
PW2
LSP
AC
RNC
NE2
S-VLAN: 200
C-VLAN: 100-200
NodeB 2
PW2: tagged mode

Request VLAN: 200
PW2: raw mode
Issue 03 (2012-11-30)

52
OptiX OSN 7500 II/7500/3500/1500

2 PWE3
2.3.2.3 QoS of ETH PWE3

After being encapsulated into ETH PWE3 packets, Ethernet services still retain the original PHB
service levels.
The Hybrid MSTP equipment performs QoS for ETH PWE3 packets as follows.
l
Ingress node
The PHB service class of an ETH PWE3 packet can be manually specified. When a packet
leaves a node, the EXP value of the packet is determined according to the mapping (between
PHB service classes and EXP values) defined by the DiffServ domain of the egress port.
Transit node
NOTE
When an MPLS tunnel uses a manually specified EXP value, the EXP value of ETH PWE3 packets is fixed,
2.3.2.4 E-Line Services Carried on PWs

For the E-Line service category, a PW can be used to carry Ethernet services on an Ethernet
port. In this scenario, this type of Ethernet service is called the E-Line service carried on PWs.
Service Mode
Table 2-11 defines the model of the E-Line services carried on PWs.
Table 2-11 Model of the E-Line services carried on PWs
Service Model
Service Flow
Service
Direction
Port Mode
Encapsulation
Mode of Port
Service
Description
Model 1
PORT+CVLAN
(source)
UNI-NNI
Layer 2 (source)
IEEE 802.1q
(source)
A UNI port
processes the
packets carrying
a specific CVLAN ID based
on its tag
attribute, and
then sends the
packets to the
NNI side for
transmission on
PWs.
PW (sink)
Issue 03 (2012-11-30)
Layer 3 (sink)
- (sink)

53
OptiX OSN 7500 II/7500/3500/1500

2 PWE3
Service Model
Service Flow
Service
Direction
Port Mode
Encapsulation
Mode of Port
Service
Description
Model 2
PORT+SVLAN
(source)
UNI-NNI
Layer 2 (source)
QinQ (source)
Layer 3 (sink)
- (sink)
A UNI port
processes the
packets carrying
a specific SVLAN ID based
on its QinQ
attribute, and
then sends the
packets to the
NNI side for
transmission on
PWs.
Layer 2 (source)
802.1Q or QinQ
(source)
PW (sink)
Model 3
PORT (source)
PW (sink)
UNI-NNI
Layer 3 (sink)
- (sink)
A UNI port
processes the
packets carrying
a specific CVLAN ID based
on its tag
attribute or
QinQ type
domain, and
then sends the
packets to the
NNI side for
transmission on
PWs.
Typical Application
Figure 2-20 shows the typical application of service model 1. Service 1 is present between the
NodeB 1 and the RNC, and service 2 is present between the NodeB 2 and the RNC. The two
services have different VLAN IDs and need to be transmitted over the PSN.
On the UNI side of NE1, service 1 is transmitted to port 1 and service 2 is transmitted to port 2.
On the NNI side of NE1, service 1 and service 2 are transmitted on different PWs. In this manner,
the two services are separately transmitted.
NE2 processes the two services in the same manner as NE1.
Issue 03 (2012-11-30)

54
OptiX OSN 7500 II/7500/3500/1500

2 PWE3
Figure 2-20 Typical application of service model 1

Service 1
Service 1
Port: 1(802.1Q)
VLAN ID: 100
Port: 1(802.1Q)
VLAN ID: 100
PSN
NodeB 1
AC
PW2
LSP
AC
NE1
UNI
NodeB 2
AC
PW1
NNI
AC
NE2
NNI
RNC
UNI
Service 2
Service 2
Port: 2(802.1Q)
VLAN ID: 200
Port: 2(802.1Q)
VLAN ID: 200
Figure 2-21 shows the typical application of service model 2. Service 1 (QinQ service) is present
between NodeB 1 and the RNC, and service 2 (QinQ service) is present between the NodeB 2
and the RNC. The two services have different S-VLAN IDs and need to be transmitted over the
PSN.
Service 1
Service 1
Port: 1(QinQ)
S-VLAN ID: 100
Port: 1(QinQ)
S-VLAN ID: 100
PSN
NodeB 1
AC
PW2
LSP
AC
NE1
NodeB 2
AC
PW1
UNI
NNI
Service 2
Port: 2(QinQ)
S-VLAN ID: 200
AC
NE2
NNI
RNC
UNI
Service 2
Port: 2(QinQ)
S-VLAN ID: 200
Issue 03 (2012-11-30)

55
OptiX OSN 7500 II/7500/3500/1500

2 PWE3
Figure 2-22 shows the typical application of service model 3. Service 1 (Ethernet service) is
present between the NodeB 1 and the RNC, and service 2 (Ethernet service) is present between
the NodeB 2 and the RNC. Service 1 carries various C-VLAN IDs, and service 2 carries various
S-VLAN IDs. The two services need to be transmitted over the PSN.
Service 1
Service 1
Port: 1 (802.1Q)
Port: 1 (802.1Q)
PSN
NodeB 1
AC
PW2
LSP
AC
NE1
NodeB 2
AC
PW1
UNI
AC
NE2
NNI
NNI
RNC
UNI
Service 2
Service 2
Port: 2(QinQ)
Port: 2(QinQ)

This section describes the standards and protocols associated with ETH PWE3.
The following standard is associated with ETH PWE3:
IETF RFC 4448: Encapsulation Methods for Transport of Ethernet over MPLS Networks
2.3.4 Availability
The ETH PWE3 function requires the support of the applicable equipment, boards, and software.
Version Support
Issue 03 (2012-11-30)
Applicable Version
OptiX OSN 1500/3500
T2000

56
OptiX OSN 7500 II/7500/3500/1500

2 PWE3
Applicable Version
U2000
Applicable Version
OptiX OSN 7500
U2000
Applicable Version
OptiX OSN 7500 II
U2000
Hardware Support
Issue 03 (2012-11-30)
Applicable
Board
Applicable Version
N1PEG16
OptiX OSN 3500
N1PEX1
OptiX OSN 3500
N1PETF8
OptiX OSN 3500/7500
R1PEFS8
Q1PEGS2
R1PEGS1
N1PEG8
OptiX OSN 3500/7500
N1PEX2
OptiX OSN 3500/7500
N2PEX1
OptiX OSN 3500/7500
N1PEFF8
OptiX OSN 3500/7500
R1PEF4F
TNN1EX2
OptiX OSN 7500 II
TNN1EG8
OptiX OSN 7500 II
TNN1ETMC
OptiX OSN 7500 II
TNN1EFF8
OptiX OSN 7500 II

57
OptiX OSN 7500 II/7500/3500/1500

2 PWE3

This section describes the limitations on and precautions for ETH PWE3 in the network design
Issue 03 (2012-11-30)
Applicable
Object

Details
Remarks
Entire feature
Do not configure services carried by

ports on a DCN-enabled port.
ETH PWE3
service for the
OptiX OSN
1500
E-Line services are recommended

for the OptiX OSN 1500. If E-LAN
services are required, make sure that
the total service traffic over a port is
less than or equal to its traffic
capacity and the number of VLANs
of all V-UNI ports is less than or
equal to 500.
Multiple ELAN services

configured on
one port
The settings regarding the broadcast

packet suppression function or
broadcast packet bandwidth limit
for one E-LAN service also take
effect for all the other E-LAN
services on the port.
MAC address
learning mode
When the MAC address learning

mode of E-LAN services is SVL, the
OptiX OSN 1500 does not support
mounting of nodes based on PORT
+VLAN to a VSI port. If this
scenario is required, set the MAC
address learning mode to IVL.
MAC address
learning mode
For E-LAN services, set MAC

address learning mode to SVL when
PWs are set to ETH-TAG.
MAC address
table capacity
For E-LAN services, the MAC

address table capacity is applicable
only to dynamic MAC addresses.

58
OptiX OSN 7500 II/7500/3500/1500

2 PWE3

Applicable
Object

Details
Remarks
Static/
Dynamic
MAC
addresses
For E-LAN services, configured

static MAC addresses do not
overwrite dynamic MAC addresses;
configured static MAC addresses
take precedence over dynamic MAC
addresses. Services are forwarded
based on configured static MAC
addresses, and dynamic MAC
addresses disappear after they age.
None.
2.3.6 Principles
This section describes the principles of ETH PWE3.
In the scenario as shown in Figure 2-23, the PE devices emulate Ethernet services.
Figure 2-23 Principles of ETH PWE3
PSN
PW
CE1
(NodeB)
AC
AC
PE1
Native
Ethernet
service
LSP
ETH PWE3
CE2
(RNC)
PE2
Native
Ethernet
service
Ethernet frame
ETH PWE3 packet

1.
Extracts the Ethernet frames that are transmitted by CE1 from the AC.
2.
Encapsulates the Ethernet frames into PWE3 packets in standard format.
3.
Maps the PWE3 packets to an LSP for transmission.

Issue 03 (2012-11-30)

59
OptiX OSN 7500 II/7500/3500/1500

1.
2.
Extracts Ethernet frames from the PWE3 packets carried on the PW.
3.
Forwards the Ethernet frames to CE2 over the AC.
2 PWE3
Transmission Efficiency of an ETH PWE3 Service

You can calculate the transmission efficiency of an ETH PWE3 service as follows:
Transmission efficiency = Ethernet frame length/(Payload length + PWE3 overhead length +
Ethernet Layer 2 overhead length)
l
Ethernet frame length

Untagged Ethernet frame length = 18 + Ethernet payload length
Tagged Ethernet frame length = 22 + Ethernet payload length
QinQ frame length = 26 + Ethernet payload length
PWE3 overhead length = MPLS label length + PW label length + CW length

An MPLS label, PW label, and CW are all four bytes.
Ethernet Layer 2 overhead length = Ethernet frame header length + FCS length
An untagged Ethernet frame header is 14 bytes.
A tagged Ethernet frame header is 18 bytes.
An FCS is 4 bytes.
By default, an Ethernet packet carrying the MPLS packet is tagged. Therefore, the
Ethernet Layer 2 overhead is 22 bytes.
NOTE
l The previous formula computes the payload transmission efficiency, without the consideration of the 20byte interframe gap and preamble. These 20 bytes are omitted in ETH PWE3.
l When ETH PWE3 services are transmitted over radio links or Ethernet links, the ETH PWE3 service
transmission efficiency pertains to the efficiency of physical links transmitting Ethernet frames.

This section uses an example to describe how to plan and configure ETH PWE3 services
according to network conditions.
For the configuration example of ETH PWE3, see Configuration Guide (Packet Transport
Domain):
l
Configuration Example: E-Line Services Carried by PWs
Configuration Example: E-LAN Services Carried by PWs
Configuration Example: E-AGGR Services Carried by PWs
2.4 TDM PWE3

This chapter describes the TDM PWE3 feature.
2.4.1 Introduction
This section provides the definition of TDM PWE3 and describes its purpose.
Issue 03 (2012-11-30)

60
OptiX OSN 7500 II/7500/3500/1500

2 PWE3
Definition
The TDM PWE3 technology emulates the basic behaviors and characteristics of TDM services
on a packet switched network (PSN) by using the PWE3 mechanism, so that the emulated TDM
services can be transmitted on a PSN.
TDM PWE3 services are also called CES services carried by PWE3. In this document, all the
CES services are carried by PWE3.
Purpose
TDM PWE3 aims to transmit TDM services over a PSN. Especially, the 2.4.2.3 CESoPSN mode
can compress idle timeslots to reduce the required transmission bandwidth.
Figure 2-24 shows the typical application of TDM PWE3. The native TDM services between
the BTS and the BSC are transmitted over a PSN. PE1 emulates the native TDM services from
the BTS into CES services by using the CESoPSN technology. Then, the CES services are
transmitted to PE2 over the PSN. Finally, PE2 restores the CES services to the native TDM
services for transmission to the BSC.
Figure 2-24 Typical application of TDM PWE3 (CESoPSN mode)
Framed E1
Service TS
Idle TS
PSN
LSP
PW
AC
CE1
(BTS)
AC
PE1
Native TDM
service
CE2
(BSC)
PE2
TDM PWE3
Native TDM
service
Framed E1
TDM PWE3 packet
Aided by the TDM PWE3 technology, conventional TDM networks can be connected by a PSN.
In this manner, PWE3 protects customer investment in TDM networks and constructs all-IP
network architecture.

This section describes the basic concepts associated with TDM PWE3.
2.4.2.1 E1 Frame Format

An E1 frame consists of 32 timeslots. E1 frames are available in different formats when classified
based on the usage of timeslot 0 and timeslot 16.
Issue 03 (2012-11-30)

61
OptiX OSN 7500 II/7500/3500/1500

2 PWE3
Frame Formats Based on the Usage of Timeslot 0

Figure 2-25 shows the formats of timeslot 0 in E1 frames.
Figure 2-25 Formats of timeslot 0 in E1 frames
32 timeslots per frame
(125 us
PCM
frame
TS1
TS0
TS2
TS16
TS30
TS31
Timeslot 0
FAS
NFAS
X 0 0 1 1 0 1 1
X 1 A
Sa4-Sa8
Even-numbered
frame
Odd-numbered
frame
As shown in Figure 2-25, the format of timeslot 0 in an odd-numbered frame is different from
that in an even-numbered frame. The signal contained in timeslot 0 of an even-numbered frame
is called frame alignment signal (FAS); the signal contained in timeslot 0 of an odd-numbered
frame is called not frame alignment signal (NFAS), which contains the A-bit indicating remote
alarms and spare bits Sa4 to Sa8. The FAS and NFAS each contain an X-bit. Based on the
function of the X-bit, E1 frames are classified into generic dual-frames and cyclic redundancy
check 4 (CRC-4) multiframes.
l
When the E1 frame is a generic dual-frame, the X-bit functions as the Si-bit.
When the E1 frame is a CRC-4 multiframe, the X-bit is used to transmit CRC-4 multiframe
check signal, CRC-4 check error bits, and multiframe alignment signal (MFAS).
Frame Formats Based on the Usage of Timeslot 16

E1 frames can be classified into PCM30 frames and PCM31 frames, depending on whether
timeslot 16 transmits voice or signaling.
l
A PCM30 frame uses channel associated signaling (CAS). In this mode, timeslot 0, as a
synchronous timeslot, cannot carry voice; timeslot 16, to carry CAS, cannot carry voice
either. As a result, one E1 frame can carry only 30 voice signals, and it is therefore called
a PCM30 frame.
A PCM31 frame uses common channel signaling (CCS). A multiframe in CCS mode does
not need to transmit CAS. In this mode, except for timeslot 0 that carries synchronous
signals, one E1 frame can carry 31 voice signals and it is therefore called a PCM31 frame.
The two classification methods focus on two attributes of E1 frames, and they can be combined.
Specifically, there are four E1 frame formats in actual application:
l
PCM30CRC (PCM30 + CRC-4 multiframe)
PCM30NOCRC (PCM30 + generic dual-frame)
PCM31CRC (PCM31 + CRC-4 multiframe)
PCM31NOCRC (PCM31 + generic dual-frame)
Issue 03 (2012-11-30)

62
OptiX OSN 7500 II/7500/3500/1500

2 PWE3
2.4.2.2 SAToP
Structure Agnostic TDM over Packet Switched Network (SAToP) is a method for encapsulating
TDM serial bit streams as pseudo wires.
SAToP provides the emulation and transport functions for unchannelized TDM services. That
is, it addresses only structure-agnostic transport. Therefore, SAToP can meet the transport needs
when a user needs services based on E1s.
SAToP segments and encapsulates TDM services as serial bit streams, and then transmits the
bit streams in PW tunnels. Although it disregards the TDM frame structure, it supports
transmission of synchronous information.
Figure 2-26 shows the encapsulation format of a SAToP packet.
Figure 2-26 Encapsulation format of a SAToP packet
20
23 24
31bit
Tunnel label
EXP
TTL
PW label
EX
P
EXP
S
S
TT
L
TTL
0000 L R RSV FRG
LEN
Sequence number
RTP header (Optional)

TDM data
MPLS label
RTP header
Control word
TDM data
A SAToP packet contains the MPLS label, control word, RTP header, and TDM data.
MPLS Label
1.2.4 MPLS Label.
Control Word
The control word of a SAToP packet is 4-byte long and contains the following fields:
Issue 03 (2012-11-30)

63
OptiX OSN 7500 II/7500/3500/1500

2 PWE3
0000: The 4 bits are generally set to all 0s. They are used to indicate the start of an Associated
Channel Header (ACH). The ACH is needed if the state of the SAToP PW is monitored
using virtual circuit connectivity verification (VCCV).
L: This bit indicates whether the TDM data carried in a packet is valid. If set to 1, it indicates
that the TDM data is omitted in order to conserve bandwidth.
R: This bit indicates whether its local CE-side interworking function (IWF) is in the packet
loss state. If set to 0, it indicates that a preconfigured number of consecutive packets are
received.
RSV: The 2 bits are reserved.
FRG: The 2 bits indicate fragmentation with the following values:

00: indicates that the entire TDM data is encapsulated in the packet.
01: indicates that the first fragmentation of the TDM data is encapsulated in the packet.
10: indicates that the last fragmentation of the TDM data is encapsulated in the packet.
11: indicates that the middle fragmentation of the TDM data is encapsulated in the
packet.
LEN: The 6 bits indicate the length of the SAToP packet (including the SAToP header and
TDM data). The minimum length of a transport unit on a PSN is 64 bytes. When a packet
is shorter than 64 bytes, LEN indicates the actual length of the packet, representing padding
bits. If a packet is longer than 64 bytes, LEN is set to all 0s.
NOTE
If LEN is 0, the packet length is supposed to be equal to the default value. If the actual packet length
is different from the default value, the packet is considered as a malformed packet.
Sequence number: The 16 bits indicate the transmission sequence number of a SAToP
packet. Its initial value is random, and is incremented by one with each SAToP data packet
sent. If the sequence number of a packet reaches the maximum (65535), the sequence
number of its next packet will start with the minimum. The sequence number can be in two
modes:
Huawei mode: applies to the scenario where only Huawei equipment composes a
network. In this mode, the minimum sequence number is 0.
Standard mode: applies to the scenario where Huawei equipment networks with thirdparty equipment. In this mode, the minimum sequence number is 1.
RTP Header
The Real-time Transport Protocol (RTP) header is used to carry timestamp information to the
remote end so that the packet clock can be restored. The RTP header is 12-byte long. The 32bit timestamp field in the RTP header represents the timestamp information.
Figure 2-27 shows the RTP header format.
Issue 03 (2012-11-30)

64
OptiX OSN 7500 II/7500/3500/1500

2 PWE3
Figure 2-27 RTP header format
Set Version (V) to 2. Set Padding (P), Header Extension (X), CSRC Count (CC), and Marker
(M) to 0.
Payload type (PT):
l
PT values are allocated to each direction of a PW, and the PT values are in a dynamic value
range. The receive and transmit directions of a PW can share a PT value. Different PWs
can share a PT value.
The PE on the upstream PW puts the allocated PT value in the PT field of the RTP header.
The PE on the upstream PW can detect exceptional packets according to the received PT
value.
The sequence number must be the same as the serial number in the SAToP control word.
The timestamp is used for carrying the time information in the network. Two timestamp
generation modes are as follows:
l
Absolute mode: The TDM circuit can restore clock information and upstream PE sets the
timestamp according to the clock. The timestamp is closely related to the serial number.
All equipment supporting CESoPSN must support the absolute mode.
Differential mode: The PE on the PW receives high-quality synchronization clock source,

which is used to generate the timestamp. The timestamp indicates the difference between
the common clock source and the TDM circuit clock. The differential mode is optional.
The synchronization source identifiers are used for detecting errored connections.
NOTE
On the Hybrid MSTP equipment, you can set whether the RTP header is encapsulated into the SAToP
packet.
TDM Data
"TDM data" indicates the TDM data payload in the form of serial bit stream. When a PW packet
is shorter than 64 bytes, fixed bits are padded to meet Ethernet transmission requirements.
The amount of E1 bit streams that are encapsulated in a PW packet is determined by Packet
Loading Time. Packet Loading Time indicates the duration for a PW packet to load TDM bit
streams. Regarding that the number of loaded TDM bit streams is equal to Packet Loading
Time multiplied by the E1 rate, Packet Loading Time limits the number of loaded TDM bit
streams. For instance, when the packet loading time is 1 ms, each PW packet can load 2048-bitlong E1 payloads.
Issue 03 (2012-11-30)

65
OptiX OSN 7500 II/7500/3500/1500

2 PWE3
2.4.2.3 CESoPSN
Circuit Emulation Service over Packet Switched Network (CESoPSN) is a method for
encapsulating TDM frames as pseudo wires.
CESoPSN provides the emulation and transport functions for channelized TDM services. That
is, it identifies the TDM frame format and signaling in the frame. Therefore, CESoPSN can meet
the transport needs when a user needs services based on timeslots.
With the frame format of the TDM service identified, CESoPSN does not transmit idle timeslot
channels; instead, CESoPSN extracts only the usable timeslots from the service flow and then
encapsulates these timeslots as PW packets for transmission.
NOTE
CESoPSN does not support the automatic detection of idle timeslots. Therefore, idle timeslots must be
manually specified.
Figure 2-28 shows the encapsulation format of a CESoPSN packet.

Figure 2-28 Encapsulation format of a CESoPSN packet
20
0000 L R
23 24
31bit
Tunnel label
EXP
TTL
PW label
EX
P
EXP
S
S
TT
L
TTL
FRG
LEN
Sequence number
RTP header (Optional)

Timeslot 1
Timeslot 5
Timeslot 1
Timeslot 5
Timeslot 2
Timeslot 3
Timeslot n (Frame 1#)

Timeslot 2
Timeslot 3
Timeslot n (Frame 2#)
Timeslot 4
Timeslot 4
Timeslot n (Frame m#)

MPLS label
RTP header
Control word
TDM data
A CESoPSN packet contains the MPLS label, control word, RTP header, and TDM data.
Issue 03 (2012-11-30)

66
OptiX OSN 7500 II/7500/3500/1500

2 PWE3
MPLS Label
1.2.4 MPLS Label.
Control Word
The control word of a CESoPSN packet is 4-byte long and contains the following fields:
l
0000: The 4 bits are generally set to all 0s. They are used to indicate the start of an Associated
Channel Header (ACH). The ACH is needed if the state of the CESoPSN PW is monitored
using virtual circuit connectivity verification (VCCV).
L: This bit indicates whether the TDM data carried in a packet is valid. If set to 1, it indicates
that the TDM data is omitted in order to conserve bandwidth.
R: This bit indicates whether its local CE-side interworking function (IWF) is in the packet
loss state. If set to 0, it indicates that a preconfigured number of consecutive packets are
received.
M: The 2 bits are used for alarm transparent transmission, indicating that the CE end or AC
side of the uplink PE detects a critical alarm.
RSV: The 2 bits are reserved.
FRG: The 2 bits indicate fragmentation with the following values:

00: indicates that the entire TDM data is encapsulated in the packet.
01: indicates that the first fragmentation of the TDM data is encapsulated in the packet.
10: indicates that the last fragmentation of the TDM data is encapsulated in the packet.
11: indicates that the middle fragmentation of the TDM data is encapsulated in the
packet.
LEN: The 6 bits indicate the length of the CESoPSN packet (including the CESoPSN header
and TDM data). The minimum length of a transport unit on a PSN is 64 bytes. When a
packet is shorter than 64 bytes, LEN indicates the actual length of the packet, representing
padding bits. If a packet is longer than 64 bytes, LEN is set to all 0s.
NOTE
If LEN is 0, the packet length is supposed to be equal to the default value. If the actual packet length
is different from the default value, the packet is considered as a malformed packet.
Sequence number: The 16 bits indicate the transmission sequence number of a CESoPSN
packet. Its initial value is random, and is incremented by one with each CESoPSN data
packet sent. If the sequence number of a packet reaches the maximum (65535), the sequence
number of its next packet will start with the minimum. The sequence number can be in two
modes:
Huawei mode: applies to the scenario where only Huawei equipment composes a
network. In this mode, the minimum sequence number is 0.
Standard mode: applies to the scenario where Huawei equipment networks with thirdparty equipment. In this mode, the minimum sequence number is 1.
RTP Header
The Real-Time Transport Protocol (RTP) header is used to carry timestamp information to the
remote end so that the packet clock can be restored. The RTP header is 12-byte long. The 32bit timestamp field in the RTP header represents the timestamp information.
Issue 03 (2012-11-30)

67
OptiX OSN 7500 II/7500/3500/1500

2 PWE3
Figure 2-29 shows the RTP header format.

Figure 2-29 RTP header format
(M) to 0.
Payload type (PT):
l
The PE on the upstream PW can detect abnormal packets according to the received PT
value.
The sequence number must be the same as the serial number in the CESoPSN control word.
l

NOTE
On the Hybrid MSTP equipment, you can set whether the RTP header is encapsulated into the CESoPSN
packet.
TDM Data
"TDM data" indicates TDM data payloads. When a PW packet is shorter than 64 bytes, fixed
bits are padded to meet Ethernet transmission requirements.
"Timeslot" indicates the timeslot in TDM frames. Each timeslot uses 8 bits. All the timeslots
are encapsulated as TDM data payloads (excluding the CRC bit). The number of encapsulated
frames and the number of timeslots in each frame can be set as required.
Issue 03 (2012-11-30)

68
OptiX OSN 7500 II/7500/3500/1500

2 PWE3
NOTE
On the Hybrid MSTP equipment: CESoPSN does not encapsulate timeslot 0 of E1 into the payload, and
the remote PE restructure the timeslots.
The amount of E1 frames that are encapsulated in a PW packet is determined by Packet Loading
Time. Packet Loading Time indicates the duration for a PW packet to load TDM frames, and
therefore limits the number of loaded TDM frames. The period of a TDM frame is 125 s. As
a result, if the packet loading time is 1 ms, each PW packet loads eight TDM frames.
2.4.2.4 Data Jitter Buffer

After CES packets are transmitted over a PSN, the intervals between packet arrivals may be
different and the packets may be misordered. To ensure that the TDM bit streams can be
reconstructed on the egress PE, a jitter buffer is required to smooth the intervals between packet
arrivals and to reorder the misordered packets.
The data jitter buffer technology re-arranges packet sequence by using the sequence numbers
of CES packets.Figure 2-30 shows the working principle of the data jitter buffer.
1.
Upon receipt of a CES packet, the PE computes the offset address of the packet based on
the packet sequence number. The offset address equals the arithmetical compliment after
the sequence number is divided by the buffer size. For example, when the jitter buffer time
is 8 ms and the packet loading time is 1 ms, the buffer size is 8 (= 8 ms/1 ms). The offset
address of a CES packet equals the arithmetical compliment after the sequence number is
divided by 8.
2.
The CES packet is saved at a position corresponding to the offset address in the buffer.
3.
After the jitter buffer time, the PE sends packets in the buffer in the sequence number order.
If a packet with a certain sequence number is missing, an idle code is inserted.
NOTE
The size of the data jitter buffer can be set as required. A low-capacity jitter buffer easily overflows, and
as a result data may be lost at different degrees; a high-capacity jitter buffer can absorb jitters resulting
from larger packet transmission intervals on the network, but a large delay may be generated when the
TDM bit streams are reconstructed. Therefore, during service deployment, you need to properly configure
the data jitter buffer based on the actual network delay and jitter conditions.
Figure 2-30 Working principle of the data jitter buffer

1 Data frames in forward order
Offset address
Sequence of received packets
Jitter buffer
2
Egress queue
Misordered data frames

Offset address
Sequence of received packets
Jitter buffer
Issue 03 (2012-11-30)

Egress queue
69
OptiX OSN 7500 II/7500/3500/1500

2 PWE3
2.4.2.5 CES Alarm Transmission

The OptiX OSN 7500 II uses the L/M and R fields in the control word to transparently transmit
alarms.
CES alarm transparent transmission involves transmitting local CES alarms to the remote end,
and inserting corresponding alarms to notify the remote end of faults in the local end. Depending
on the position where the alarm is generated, CES alarm transparent transmission can be between
AC sides, and from the NNI side to the AC side.
CES Alarm Transparent Transmission Between AC Sides

There are two scenarios where CES alarms are transparently transmitted between AC sides.
l
The fault information on the AC link or port is transmitted through the PSN as follows:
Figure 2-31 CES alarm transparent transmission between AC sides (1)
PSN
AC1
NodeB
AC2
PW
PE1
LSP
RNC
PE2
If PE1 detects a link fault or an E1 port fault on the AC1 side, PE1 returns RDI to upstream
and informs PE2 of the fault through the L field of control word. Upon receiving the control
word, PE2 reports the CESPW_OPPOSITE_ACFAULT alarm and inserts AIS to the AC2
side.
l
The service alarms on the AC side are transparently transmitted through the PSN as follows:
Figure 2-32 CES alarm transparent transmission between AC sides (2)
PSN
AC1
NodeB
AC2
PW
PE1
LSP
PE2
RNC
Issue 03 (2012-11-30)

70
OptiX OSN 7500 II/7500/3500/1500

2 PWE3
If the RNC detects a link fault or an E1 port fault on the AC2 side, the RNC returns RDI
to PE2; PE2 reports the RAI alarm and informs PE1 of the fault through the L/M field of
control word. Upon receiving the control word, PE1 reports the RAI alarm and returns RDI
to AC1.
NOTE
The SAToP encapsulation mode does not support the M field, and therefore cannot transparently
transmit the RAI alarm.
CES Alarm Transparent Transmission from the NNI Side to the AC Side
Figure 2-33 shows the CES alarm transparent transmission from the NNI side to the AC side.
Figure 2-33 CES alarm transparent transmission from the NNI side to the AC side
PSN
AC1
NodeB
AC2
PW
PE1
LSP
PE2
RNC
When detecting that packet loss ratio continuously beyond the preset threshold, PE2 inserts the
AIS alarm into AC2, and uses the R field in the control word to transmit the information to PE1.
Then, PE1 reports the RAI alarm based on the R field.
2.4.2.6 Clock Recovery Schemes of TDM PWE3

When clocks need to be transmitted with CES services, you can adopt CES retiming or CES
adaptive clock recovery (ACR) as required.
CES Retiming
CES retiming is an approach to reduce signal jitter after CES services traverse a transmission
network. It combines the timing reference signal and CES service signal for transmission.
Therefore, the transmitted CES service signal carries the timing information that is synchronized
with the timing reference signal. CES retiming is applicable when the following conditions are
met:
l
All the clocks on the PSN are synchronous.
All the clocks on the PSN are synchronized with the clock of the incoming service.
Figure 2-34 shows a clock solution wherein the BSC transmits synchronization information to
the BTS over the PSN with CES retiming enabled. In this solution:
l
Issue 03 (2012-11-30)
PE1 receives an E1 service from the BSC, and extracts the clock from the E1 service (the
E1 service is emulated into the CES service after entering the PSN). The extracted clock
71
OptiX OSN 7500 II/7500/3500/1500

2 PWE3
functions as the primary reference clock, and is traced by the other NEs on the PSN. In this
manner, all the clocks on the PSN are synchronized with the clock of the BSC.
l
CES retiming is enabled on PE2 so that the system clock of PE2 can be carried in the E1
service sent to the BTS (the CES service is restored to the E1 service after leaving the PSN).
The clock of PE2 is synchronized with that of the BSC, so the BTS can extract the clock
of the BSC from the received E1 service.
Figure 2-34 Principles of CES retiming
PSN
CE1
(BSC)
E1
service
PE1
LSP
PE2
E1
service
CE2
(BTS)
Read clock (System clock)

Clock
CES service
E1
service
FIFO
E1
service
CES retiming is implemented as follows: The E1 bit streams restored from the CES service are
written into a First In, First Out (FIFO) queue, and then are read out from the FIFO queue by
using the retiming clock. The output signal contains the retiming clock; therefore, it is
synchronized with the primary reference clock, with the jitter and wander in the original E1
service absorbed by the data jitter buffer.
CES ACR
CES ACR is a technology wherein the CES service is used to restore the clock of the source end
in an adaptive manner. The sink end recovers the clock based on the packet received on its NNI
side.
l
All the clocks on the PSN are not synchronous.
All the clocks on the PSN are synchronous, but the clocks on the PSN are not synchronized
with the clock of the incoming service.
For the principle and implementation process of CES ACR, see 20.4 CES ACR.
2.4.2.7 QoS of TDM PWE3

The QoS of TDM services features low delay, low jitter, and fixed bandwidth. Therefore, a high
enough per-hop behavior (PHB) level needs to be assigned to CES packets.
The Hybrid MSTP equipment performs QoS for TDM PWE3 packets as follows.
Issue 03 (2012-11-30)

72
OptiX OSN 7500 II/7500/3500/1500

2 PWE3
Ingress node
The PHB service class of a TDM PWE3 packet can be manually specified (the PHB service
class is set to EF, by default). When a packet leaves an ingress node, the EXP value of the
packet is determined according to the mapping (between PHB service classes and EXP
values) defined by the DiffServ domain of the egress port.
Transit node
NOTE
When an MPLS tunnel uses a manually specified EXP value, the EXP value of TDM PWE3 packets is fixed,
In addition, the Hybrid MSTP equipment supports the CES CAC function. If bandwidth
resources are insufficient when CES services are created, the services cannot be created and the
system will display a prompt message.
NOTE
l To enable the CES CAC function, set the bandwidth of tunnel carrying CES services, and PW
bandwidth of other PWE3 services carried on the tunnel.
This section describes the capacity of the OptiX OSN equipment for supporting TDM PWE3.
Table 2-12 provides the specifications associated with TDM PWE3.
Table 2-12 Specifications associated with TDM PWE3
Item
Specifications
Maximum number of private line

CES services supported by the
equipment
OptiX OSN 1500: 64

Number of CES services

supported by boards
The R1ML1 on the OptiX OSN 1500: 16

OptiX OSN 3500/7500
l N1CQ1: 252
l N1MD75 and N1MD12: 32
OptiX OSN 7500 II
l TNN1CO1: 504
Emulation mode
l SAToP
l CESoPSN
Issue 03 (2012-11-30)

73
OptiX OSN 7500 II/7500/3500/1500

2 PWE3
Item
Specifications
Clock mode
l CES ACR
l CES retiming
Number of CES ACR clocks

supported by boards
R1ML1 on the OptiX OSN 1500, N1MD75/N1MD12

on the OptiX OSN 3500/7500, and TNN1D75E/
TNN1D12E on the OptiX OSN 7500 II: 4
Packet loading time
125 s to 5000 s, in steps of 125 s
Jitter buffer time
375 s to 16000 s, in steps of 125 s
Maximum number of available

timeslots for CES services
31

This section describes the standards and protocols associated with TDM PWE3.
The following standards and protocols are associated with TDM PWE3:
l
IETF RFC 3550: RTP: A Transport Protocol for Real-Time Applications
IETF RFC 4197: Requirements for Edge-to-Edge Emulation of Time Division Multiplexed
(TDM) Circuits over Packet Switching Networks
IETF RFC 4553: Structure-Agnostic Time Division Multiplexing (TDM) over Packet
(SAToP)
IETF RFC 5086: Structure-Aware Time Division Multiplexed (TDM) Circuit Emulation
Service over Packet Switched Network (CESoPSN)
ITU-T G.704: Synchronous frame structures used at 1544, 6312, 2048, 8448 and 44 736
kbit/s hierarchical levels
2.4.5 Availability
The TDM PWE3 function requires the support of the applicable equipment, boards, and
software.
Version Support
Issue 03 (2012-11-30)
Applicable Version
OptiX OSN 1500/3500/7500
U2000
Applicable Version
OptiX OSN 7500 II

74
OptiX OSN 7500 II/7500/3500/1500

2 PWE3
Applicable Version
U2000
Hardware Support
Applicable
Board
Applicable Version
N1CQ1
OptiX OSN 7500/3500
N1MD12
OptiX OSN 7500/3500
N1MD75
OptiX OSN 7500/3500
R1ML1
TNN1CO1
OptiX OSN 7500 II
TNN1D75E
OptiX OSN 7500 II
TNN1D12E
OptiX OSN 7500 II

This section describes the limitations on and precautions for TDM PWE3 in the network design
Issue 03 (2012-11-30)
Applicable
Object

Details
Remarks
CES service
CES services are used to transmit

TDM services over a PSN network.
CES service
Retain the default values of RTP

head enabling, serial number mode,
jitter buffer time, and packet loading
time, unless otherwise specified.

75
OptiX OSN 7500 II/7500/3500/1500

2 PWE3
Applicable
Object

Details
Remarks
Emulation
mode
l If the bandwidth allows, use the

simulation mode, Structure
Agnostic TDM over Packet
Switched Network (SAToP).
This simulation mode does not
differentiate the E1 frame format
at the opposite end and the E1
frame format at the local end is
unframed E1.
l To improve the transmission

efficiency of CES services or to
transmit Fractional CES
services, use the simulation
mode, Circuit Emulation Service
over Packet Switched Network
(CESoPSN). The E1 frame mode
at the local end is always PCM
31. The E1 frame format at the
local end is set to the same as that
at the opposite end. If the E1
frame mode at the opposite end
is PCM 30, timeslot 16 is used
for service transmission.
PHB
It is recommended that the PHB of

CES services take the default value
EF.
CES service
protection
The TNN1CO1/N1CQ1 board

supports 1+1/1:1 linear MSP. The
protection modes at both ends
should be the same.
Clock
Clocks must be configured for CES

service transmission. Three clocks
are available: system clock, line
clock, and adaptive clock recovery
(ACR) clock.
ACR clock
The TNN1D75E/TNNID12E/
N1MD75/N1MD12 board supports
32xE1 ports.
l The former 16 ACR clock

domains can bind the CES
services of the former 16 E1
ports.
l The latter 16 ACR clock
domains can bind the CES
services of the latter 16 E1 ports.
Issue 03 (2012-11-30)

76
OptiX OSN 7500 II/7500/3500/1500

2 PWE3
Applicable
Object

Details
Remarks
ACR clock
N1MD75/N1MD12 board supports
four ACR clocks.
Service
bandwidth
When a tunnel carrying CES PWs

has a bandwidth lower than the
bandwidth required by CES PWs,
packet loss occurs in CES services.
Service
bandwidth
The bandwidth of each PW carrying

CES services is 3 Mbit/s. When the
packet loading time is 125 us or 250
us and the RTP header is enabled,
the bandwidth of each PW is 4 Mbit/
s.
The total bandwidth is calculated

based on the number of specific
services. Ensure that the total
bandwidth does not exceed the port
bandwidth.

Applicable
Object

Details
Remarks
VCCV
Use the VCCV message based on

control word if constant fault
detection for PWs is required.
Transparent
transmission
of CES alarm
Enable the transparent transmission

of CES alarms if the service fault
information on the AC side or
network side needs to be transmitted
to the remote PE or CE.
Jitter buffer
time, packet
loading time
Jitter buffer time is two to three

times of packet loading time, with a
step of 125 us.
The packet loading time is the same

at both ends.
None.
Issue 03 (2012-11-30)

77
OptiX OSN 7500 II/7500/3500/1500

2 PWE3
2.4.7 Principles
This section describes the principles of TDM PWE3.
As shown in Figure 2-35, the PE device uses 2.4.2.3 CESoPSN to emulate native TDM services.
2.4.2.2 SAToP uses a similar encapsulation process, but does not identify the E1 frame format
or process the timeslots of the E1 frame.
Figure 2-35 Principles of TDM PWE3 services (CESoPSN mode)
Framed E1
Service TS
Idle TS
PSN
LSP
PW
AC
CE1
(BTS)
AC
PE1
Native TDM
service
CE2
(BSC)
PE2
TDM PWE3
Framed E1
Native TDM
service
TDM PWE3 packet

1.
Extracts the E1 bit streams that are transmitted by CE1 from the AC.
2.
Segments the E1 bit streams, with a specified number of E1 frames contained in each
segmentation.
3.
Extracts valid payloads from the specified timeslots in each segment, and encapsulates the
valid payloads into a PWE3 packet in standard format.
4.
Maps the PWE3 packets to an LSP for transmission.

1.
2.
Extracts the valid payloads from the PWE3 packets carried on the PW.
3.
Restores E1 frames based on the valid payloads (the unused timeslots are padded based on
the preconfigured 8-bit pattern), and reconstructs the E1 bit streams.
NOTE
Timeslot 0 is not padded based on the preconfigured 8-bit pattern, but is regenerated based on the
preconfigured PCM format.
4.
Forwards the E1 bit streams to CE2 over the AC.
5.
Combines the CES clocks into bit streams.
Issue 03 (2012-11-30)

78
OptiX OSN 7500 II/7500/3500/1500

3 ATM OAM
ATM OAM
About This Chapter

This chapter describes the ATM OAM feature.
3.1 Introduction
This section provides the definition of ATM OAM and describes its purpose.
3.2 Basic Concepts
This section describes the basic concepts associated with ATM OAM.
This section describes the standards and protocols associated with ATM OAM.
3.4 Availability
This section describes the support required by the application of the ATM OAM feature.
3.5 Feature Dependency and Limitation
This section describes the limitations on and precautions for ATM OAM in the network design
3.6 Principles
The functions of ATM OAM are implemented by means of specific ATM OAM cells.
3.7 Configuring ATM OAM
The main operation tasks of configuring ATM OAM include settings of the segment and end
attributes, CC activation status, remote loopback test, and LLID (local loopback ID).
3.8 Configuration Example
This section uses an example to describe how to plan and configure ATM OAM according to
network conditions.
3.9 Relevant Alarms and Performance Events
This topic describes the alarms and performance events that are related to the ATM OAM feature.
3.10 Parameter Description
This topic describes the parameters required for configuring ATM OAM.
Issue 03 (2012-11-30)

79
OptiX OSN 7500 II/7500/3500/1500

3 ATM OAM
3.1 Introduction
This section provides the definition of ATM OAM and describes its purpose.
Definition
ATM OAM is used for detecting and locating ATM faults, and monitoring ATM performance.
In this document, ATM OAM refers to OAM only at the ATM layer and implements various
OAM functions by means of specific ATM OAM cells.
Purpose
ATM OAM provides segment-based ATM OAM between the CE and the PE and end-to-endbased ATM OAM between CEs.
As shown in Figure 3-1, ATM OAM cells are transmitted and detected between the CE and the
PE, or between the CEs to monitor the ATM link.
Figure 3-1 Typical application of ATM OAM
CE1
(NodeB)
PE2
PE1
CE2
(RNC)
Segment check
End-to-end check
3.2 Basic Concepts

This section describes the basic concepts associated with ATM OAM.
3.2.1 ATM OAM Levels

ATM OAM is performed on five OAM hierarchical levels. Three levels are associated with the
physical layer, and two levels are associated with the ATM layer.
ATM OAM checks an ATM link by inserting certain OAM cells of the standard cell structure
into the user cell flow. As specified in Table 3-1, ATM OAM is classified into five hierarchical
levels.
Issue 03 (2012-11-30)

80
OptiX OSN 7500 II/7500/3500/1500

3 ATM OAM
Table 3-1 OAM levels

Flow
Level
Description
F1
Regenerator
section level
F2
Digital section
level
F3
Transmission
path level
F1, F2, and F3 are OAM flows at the physical layer. The
generation of OAM flows at the physical layer and the
implementation of the OAM functions depend on the
transport mechanism of the transmission system. Three
types of transmission can be provided on ATM networks:
l SDH-based transmission system
l Cell-based transmission system
l PDH-based transmission system
F4
Virtual path
level
F5
Virtual channel
level
F4 and F5 are OAM flows at the ATM layer. Independent

of a transmission system, implementation of the OAM
functions at the ATM layer is based on VPs/VCs.
As an OAM cell flow in the virtual path connection (VPC),
F4 provides VP-level operation management and
maintenance functions.
As an OAM cell flow in the virtual channel connection
(VCC), F5 provides VC-level operation management and
maintenance functions.
After the OAM function in F4 and F5 flows is activated,
corresponding OAM cells are inserted into user cells.
From the perspective of the functioning span, there are two
types of F4 flows and two types of F5 flows. These are:
l End-to-end F4 flow and end-to-end F5 flow, which are
used for end-to-end communication of virtual
connections.
l Segment F4 flow and segment F5 flow, which are used
for communication within the bounds of one virtual
connection or multiple interconnected virtual
connections.
3.2.2 Segment and End Attributes and Directions of CPs

Connection points (CPs) are reference points which are defined along a VPC/VCC.
Segment and End Attributes of CPs

The segment and end attributes include:
l
End point: refers to the end point for an ATM network connection or generally refers to
the edge on an ATM network.
Segment point: refers to the end point of a segment. One ATM link consists of multiple
segments.
Segment-end point: refers to the edge of a segment and an end.
Issue 03 (2012-11-30)

81
OptiX OSN 7500 II/7500/3500/1500

3 ATM OAM
Intermediate point: refers to the OAM node between segment points or end points.
Therefore, intermediate points can be further classified into intermediate points between
segment points and intermediate points between end points.
The segment and end attributes are set to intercept ATM OAM cells in the expected direction
and location.
Figure 3-2 shows the segment and end attributes of CPs.
Figure 3-2 Segment and end attributes of CPs
End points
Segment-end Points
Segment Points
Intermediate Points
Packet Transmission Equipment
Directions of CPs
The directions of CPs are classified into forward and backward directions.
Figure 3-3 shows the directions of CPs.
Figure 3-3 Directions of CPs
End points
Segment Points
Intermediate Points
Packet Transmission Equipment
Backward direction
Source
Sink
Forward direction
ATM connection
Direction
Issue 03 (2012-11-30)

82
OptiX OSN 7500 II/7500/3500/1500

3 ATM OAM
3.2.3 ATM OAM Functions

The equipment supports the following ATM OAM functions: alarm indication signal (AIS),
remote defect indication (RDI), continuity check (CC), and loopback (LB).
AIS/RDI
AIS cells are used for reporting defect indications in the forward direction. Table 3-2 lists the
types and functions of AIS cells.
Table 3-2 AIS/RDI functions
Cell Generation and
Transmission Mechanism
AIS State Release Condition
RDI State Release Condition
l Upon detecting a fault, an end

point reports the LCD alarm but
does not insert any AIS cells. An
end point catches end AIS/RDI
cells and terminates CC cells.
l The AIS state is released when a

user cell or CC cell is received.
The RDI state is released when RDI

cells are absent for 2.5 seconds, with
a margin of 0.5 seconds.
l Upon detecting a fault, a

segment point reports the LCD
alarm and inserts end AIS cells
to the downstream. Afterwards,
the segment point periodically
sends these cells. A segment
point catches segment AIS/RDI
cells only.
l If the CC function is not

activated, the AIS state is also
released when AIS cells are
absent for 2.5 seconds, with a
margin of 0.5 seconds.
l Upon detecting a fault, an

intermediate point reports the
LCD alarm and inserts segment
AIS cells and end AIS cells to the
downstream. Afterwards, the
intermediate point periodically
sends these cells. An
intermediate point does not catch
any AIS/RDI cells.
l Upon detecting a fault, a
segment-end point reports the
LCD alarm but does not insert
any AIS cells. A segment-end
point catches the AIS/RDI cells
of a segment and an end.
CC
CC is used for continuously monitoring link continuity. With the CC function, unexpected
interruption of a link (the link is intermittently disconnected) during a continuous period can be
detected. Table 3-3 lists the types and functions of CC cells.
Issue 03 (2012-11-30)

83
OptiX OSN 7500 II/7500/3500/1500

3 ATM OAM
Table 3-3 CC functions

Insertion Mode of CC
Cells
Segment and End

Attribute of CC
Source and Sink of CC
Description of CC
Two alternative modes are

available for the insertion
of the CC cells after the
activation of the CC
function:
Segment points or end

points support activation
of the CC function.
l The source point with

CC activated only
transmits CC cells.
l seg_CC is responsible
for transmitting or
receiving segment CC
cells.
l The sink point with CC

activated only receives
CC cells.
l When the specified

receive point does not
receive any service cell
or CC cell within a
time interval of 3.5
seconds, with a margin
of 0.5 seconds, it
reports the LOC alarm
and transmits AIS cells
in the forward
direction.
l CC cells are inserted

with a periodicity of
nominally one cell per
second when no user
cells have been sent on
the link.
l ete_CC is responsible
for transmitting or
receiving end-to-end
CC cells.
l The source point+sink

point with CC
activated transmit and
receive CC cells.
l When the specified

receive point receives
CC cells or service
cells again, the LOC
alarm is released.
l CC cells are sent

repetitively with a
periodicity of
nominally one cell per
second independent of
the user cells flow.
LB
LB is used for detecting link continuity and locating faults. LB cells can be inserted at one
location on which the segment and end attribute is set along a virtual connection and looped
back at different downstream locations on which the segment and end attributes are set,
eliminating the need to interrupt services.
Table 3-4 LB functions
Loopback Location Identifier (LLID)
Loopback
Indication (LI)
Segment and
End Attribute of
LB
Test Result
The LLID field is used to identify the location

where the loopback is to occur.
LI is used to
identify the
loopback status of
LB cells.
l LI = 1: indicates
that LB cells are
not looped
back.
l LI = 0: indicates
that LB cells are
looped back.
seg_LB cells can

be looped back at
segment points,
segment-end
points or
intermediate
points.
Success/Failure
NOTE
Actually, the LLID field can be set to any value. The
LLID field is designed according to the second
coding mode (0x01) specified in ITU-T I.610. For
this reason, you can enter 15 bytes, which consist of
2-byte country code (the default value is 0000 in the
hexadecimal system), 2-byte network code (the
default value is 0000 in the BCD code pattern), and
11-byte NE code (by default, the first four bytes use
the NE ID and the last seven bytes are 0s). In addition,
once the LLID field is set, the LLID field does not
vary with the NE ID even if the NE ID changes. The
last byte of the LLID field is unused.
Issue 03 (2012-11-30)
e-t-e_LB cells can

be looped back at
segment-end
points or end
points.

NOTE
If the test fails, the
error code and
failure cause are
displayed; if the test
is successful, the
message indicating
a successful test is
displayed. The LB
test result can be
found in the
network
management
events.
84
OptiX OSN 7500 II/7500/3500/1500

3 ATM OAM
In F4 flows, the VCI value of a segment OAM cell is 3 (VCI = 3) and the VCI value of an endto-end OAM cell is 4 (VCI = 4).
In F5 flows, the payload type identifier (PTI) value of a segment OAM cell is 4 (PTI = 4), and
the PTI value of an end-to-end OAM cell is 5 (PTI = 5).

This section describes the standards and protocols associated with ATM OAM.
The following standard is associated with ATM OAM:
ITU-T I.610: B-ISDN operation and maintenance principles and functions
3.4 Availability
This section describes the support required by the application of the ATM OAM feature.
Version Support
Applicable Version
OptiX OSN 7500 II
U2000
Applicable Version
OptiX OSN 3500/7500
U2000
V100R005 and later
Hardware Support
Issue 03 (2012-11-30)
Applicable Board
Applicable Version
TNN1AFO1
OptiX OSN 7500 II
TNN1D75E
OptiX OSN 7500 II
TNN1D12E
OptiX OSN 7500 II
N1MD12
OptiX OSN 3500/7500
N1MD75
OptiX OSN 3500/7500

85
OptiX OSN 7500 II/7500/3500/1500

3 ATM OAM

This section describes the limitations on and precautions for ATM OAM in the network design

Applicable
Object

Details
Remarks
ATM OAM
For the N1MD12/N1MD75/

TNN1D12E/TNN1D75E
, it is recommended that the number
of ATM connections with ATM
OAM enabled is less than or equal
to 128.
For the TNN1AF01, it is

recommended that the number of
ATM connections with ATM OAM
enabled is less than or equal to 512.
Issue 03 (2012-11-30)
ATM OAM
Real-time monitoring is performed

on important ATM connections. For
common ATM connections, ATM
OAM is enabled only in the
commissioning phase, preventing
generating a large number of
performance overheads.
ATM OAM
ATM OAM must be configured for

a specific VPC or VCC in ATM
services.
ATM OAM
ATM services that are transparently

transmitted over ports do not
support ATM OAM.
Segment and
end attributes
Do not set segment-end points or

activate continuity check (CC) on a
protection connection in a 1+1
protection group. Do not set a
segment point on a connection in a
protection group.
Loopback
(LB) test
The local loopback ID (LLID) of

each NE must be unique on the
network. The default LLID of an NE
is usually used.

86
OptiX OSN 7500 II/7500/3500/1500

3 ATM OAM
Applicable
Object

Details
Remarks
NE code
If the default NE code of an NE is

unique, the NE can use its default
NE code.
The NE code of an NE is associated

with it NE ID. Generally, the NE
code of an NE is unique on the
network.

Applicable
Object

Details
Remarks
Remote LB
test
l Before an end-to-end LB test, set

end points at both ends of the test
domain. After the test, remove
the end points.
l Before a segment-to-segment
LB test, set a segment point or
non-segment-end point at one
segment of the test domain. After
the test, remove the segment
point or non-segment-point.
None.
3.6 Principles
The functions of ATM OAM are implemented by means of specific ATM OAM cells.
3.6.1 AIS/RDI
This section provides an example wherein an intermediate point detects a VPC/VCC fault to
describe how the AIS/RDI functions are implemented.
NOTE
VPC fault detection and VCC fault detection have the same principles. The following part uses a VPC fault
detection process as an example to describe the principles of AIS/RDI functions.
As shown in Figure 3-4, on the ATM network, the end points are set up in the backward direction
of NE1 and in the forward direction of NE5, the segment points are set up in the backward
direction of NE2 and in the forward direction of NE4, and NE3 is the intermediate point. The
Issue 03 (2012-11-30)

87
OptiX OSN 7500 II/7500/3500/1500

3 ATM OAM
VPC from NE2 to NE3 breaks due to a fault. In this case, the AIS/RDI function is implemented
as follows:
l
NE3 immediately reports the LCD alarm. Since NE3 is an intermediate point, it
immediately inserts seg_VP-AIS and e-t-e_VP-AIS cells in the forward direction. Then, it
continues to periodically transmit these cells.
After the forward segment point of NE4 captures seg_VP-AIS cells, NE4 immediately
reports the VP-AIS status. Meanwhile, the forward segment point of NE4 immediately
transmits seg_VP-RDI cells to the upstream.
NOTE
The forward segment points of NE4 do not capture e-t-e_VP-AIS cells.
After the forward segment point of NE5 captures e-t-e_VP-AIS cells, NE5 immediately
reports the VP-AIS status. Meanwhile, the forward segment point of NE5 immediately
transmits e-t-e_VP-RDI cells to the upstream.
Since NE3 is an intermediate point, it does not capture any RDI cell.
After the backward segment point of NE2 captures seg_VP-RDI cells from NE4, NE2
immediately reports the VP-RDI status.
NOTE
The backward segment point of NE2 does not capture e-t-e_VP-RDI cells.
After the backward end point of NE1 captures e-t-e_VP-RDI cells from NE5, NE1
immediately reports the RDI status.
Figure 3-4 Principles of AIS/RDI

Reporting the
AIS status
Reporting the
AIS status
Reporting the
LCD alarm
NE1
end point
NE5
end point
seg_VP-AIS
cell
NE3
intermediate
point
e-t-e_VP-AIS
cell
NE2
segment
point
seg_VP-RDI cell
NE4
segment point
e-t-e_VP-RDI cell
Reporting the
RDI status
Reporting the
RDI status
VPC
VPC direction
Issue 03 (2012-11-30)

88
OptiX OSN 7500 II/7500/3500/1500

3 ATM OAM
NOTE
If the ATM trunks at both ends of NE2 and NE3 are enabled with the IMA protocol, a unidirectional VPC
interruption from NE2 to NE3 will result in a bidirectional VPC interruption between NE2 and NE3 because
the OptiX OSN equipments support only Symmetrical Mode and Symmetrical Operation. In this case, NE1
and NE2 as shown in Figure 3-4 cannot capture any RDI cells, and will not report any RDI status.
3.6.2 CC
This section provides an example to describe the CC function at the segment and end-to-end
levels.
As shown in Figure 3-5, on the ATM network, the ATM link is enabled with the CC function
at the segment and end-to-end levels. Wherein, NE1 initiates an end-to-end CC test to NE5, and
NE2 initiates a segment CC test to NE4. CC cells are then continuously transmitted between
end-to-end points, and between segment points. The VPC between NE3 and NE4 breaks due to
a fault. In this case, the CC function is implemented as follows:
l
NE4 fails to receive user cells or seg_CC cells, so NE4 immediately reports the VP_LOC
alarm and transmits VP_AIS cells to the downstream.
NE5 receives only VP_AIS cells, but fails to receive e-t-e_CC cells or user cells. Therefore,
NE5 immediately reports the VP_AIS status.
Figure 3-5 Principles of CC

Reporting the
AIS status
Reporting the
VP_LOC alarm
NE1
end point
NE5
end point
NE3
intermediate
point
NE2
segment point
NE4
segment point
Sending the
seg_CC cell
Sending the
e-t-e_CC cell
Receiving the
seg_CC cell
Receiving the
e-t-e_CC cell
CC
Issue 03 (2012-11-30)

89
OptiX OSN 7500 II/7500/3500/1500

3 ATM OAM
3.6.3 LB
This section provides an example wherein the LB function is enabled on segment points to
describe how the LB function is implemented.
As shown in Figure 3-6, segment points are set up in the backward direction of NE2 and in the
forward direction of NE4, and NE3 is the intermediate point.
1.
When the backward segment point of NE2 initiates an LB test to NE3, it inserts a seg_LB
cell whose LLID value is the same as that of NE3; after the backward segment point of
NE2 initiates an LB test to NE4, it inserts a seg_LB cell whose LLID value is the same as
that of NE4. Before a cell is looped back, its LI value is equal to 1.
2.
When the intermediate point (NE3) receives a seg_LB cell, it first analyzes whether the
LLID value of the cell is the same as the local LLID value.
l If the LLID values are different, the cell is transmitted to the downstream without being
processed.
l If the LLID values are the same, NE3 analyzes whether the LI value of the cell is equal
to 1. If the LI value of the cell is equal to 1, the cell is not looped back yet. NE3 then
sets the LI value to 0 and returns the cell, so that the backward segment point of NE2
can receive the returned cell within 6 (+/-1) seconds. If the LI value of the cell is equal
to 0, the cell is transmitted to the downstream without being processed.
3.
When the forward segment point of NE4 receives a seg_LB cell, it first analyzes whether
the LLID value of the cell is the same as the local LLID value.
l If the LLID values are different, the cell is discarded.
l If the LLID values are the same, the forward segment point of NE4 analyzes whether
the LI value of the cell is equal to 1. If the LI value of the cell is equal to 1, the cell is
not looped back yet. The forward segment point of NE4 then sets the LI value to 0 and
returns the cell, so that the backward segment point of NE2 can receive the returned cell
within 6 (+/-1) seconds. If the LI value of the cell is equal to 0, the cell is discarded.
4.
Issue 03 (2012-11-30)
If an LB cell fails to be looped back to the backward segment of NE2 within 6 (+/-1) seconds
seconds, the failure of the LB test is reported.

90
OptiX OSN 7500 II/7500/3500/1500

3 ATM OAM
Figure 3-6 Principles of LB

NE1
end-to-end point
LLID="NE4", LI="1"
NE5
end-to-end point
LLID="NE3", LI="1"
NE3
intermediate
point
NE4
segment point
NE2
segment point
LLID="NE3", LI="0"
LLID="NE4", LI="0"
Inserting the LB cell

Extracting and analyzing the LB cell
LB cell (before loopback)
LB cell (after loopback)
3.7 Configuring ATM OAM

The main operation tasks of configuring ATM OAM include settings of the segment and end
attributes, CC activation status, remote loopback test, and LLID (local loopback ID).
3.7.1 Setting Segment End Attribute

You need to set the segment end attributes of the connection before performing ATM OAM
maintenance. The segment end attributes determine how the port handles the OAM cell.
Prerequisites
l
You must be an NM user with NE operator authority or higher.
ATM services are created.
Issue 03 (2012-11-30)

91
OptiX OSN 7500 II/7500/3500/1500

3 ATM OAM
Background Information
The segment end attribute of ATM connection points (CPs) contains Segment point,
Endpoint, Segment and Endpoint, and Non segment and Endpoint.
The ways that the port handles the OAM cell in different segment end attributes are described
as follows:
l
If the segment end attribute is set to Segment point, only the segment-to-segment OAM
cells at the segment can be terminated.
If the segment end attribute is set to Endpoint or Segment and Endpoint, the end-to-end
OAM cells and segment-to-segment OAM cells at the segment and end can be terminated.
If the segment end attribute is set to Non segment and Endpoint, the OAM cell is not
terminated.
CAUTION
You cannot set OAM segment endpoint or activate CC at the protection connection to which 1
+1 source or 1+1 sink protection group is applied. In addition, you cannot set segment end
attribute at the connection that is added to a protection group.
Procedure
Step 1 In the NE Explore, select the NE and choose Configuration > Packet Configuration > ATM
OAM Management from the Function Tree. Click the Segment End Attributes tab.
Step 2 Set the Segment and End Attribute of the connection point.
Step 3 Click Apply. A dialog box is displayed, indicating that the operation succeeded.
Step 4 Click Close.
----End
3.7.2 Setting the CC Activation Status

You can perform continuity check (CC) on the ATM connection to check connection continuity
for troubleshooting.
Prerequisites
l
ATM services are created.
After you activate the CC check at the source and sink ends of a service, the source end
periodically builds and sends a CC cell. If the sink end does not receive the CC cell from the
source, it automatically reports the LOC alarm, and inserts the corresponding AIS cells
downstream.
Issue 03 (2012-11-30)

92
OptiX OSN 7500 II/7500/3500/1500

3 ATM OAM
CAUTION
When activating the CC, activate the source and sink ends almost at the same time in a short
period. You are recommended to activate the sink prior to the source. Otherwise, the NE may
report a timeout event.
Procedure
OAM Management from the Function Tree. Then, click the CC Activation Status tab.
Step 2 Set the CC Activate Flag of the connection point and the Segment and End Attribute of the
CC cell.
NOTE
l Segment and End Attribute: Sets the segment end attribute of the CC cell. It corresponds to the segment
end attribute of the connection point. The CC cell terminates at the connection point of the same segment
attribute.
l After CC Activate Flag is activated, the CC check is started.
Step 4 Click Close.
----End
3.7.3 Setting Local Loopback ID

You must set the local loopback ID (LLID) for an NE before performing the loopback (LB) test
on it. It is unnecessary to change it if the default LLID is unique on the network.
Prerequisites
The LB test recognizes an NE by LLID, so the LLID must be unique on the network. After the
LLID is set for an NE, the LLID value is sent to all the boards to keep consistency of LLID
values on all the boards.
Procedure
OAM Management from the Function Tree. Then, click the LLID tab.
Step 2 Set the Country Code, Network Code, and NE Code.
Step 4 Click Close.
----End
Issue 03 (2012-11-30)

93
OptiX OSN 7500 II/7500/3500/1500

3 ATM OAM
3.7.4 Setting a Remote Loopback Test

A remote loopback check on the ATM connection without interrupting services can check the
connection connectivity for troubleshooting.
Prerequisites
l
Segment and end attributes are configured.
The LLID of the remote loopback node is set.
During a remote loopback check, the source end builds an LB cell, and starts the timer. If the
sink end receives the LB cell, it sends the cell back to the source. If the source end detects a
returned LB cell in a specified time, the loopback succeeded. Otherwise, the loopback fails.
Procedure
OAM Management. Click the Remote Loopback Test tab.
Step 2 Set the Loopback Point NE and Segment and End Attribute.
NOTE
Segment End Attribute of ATM service specifies the type of the transmitted OAM cells during an LB test.
l If Segment End Attribute is set to Segment Point, seg_LB cells is transmitted.
l If Segment End Attribute is set to Endpoint, e-t-e_LB cells is transmitted.
Step 3 Click Test to start a remote loopback test.

Step 4 Click Test Result to view the test result.
l Normally, Test Result should be Test Succeeded. After the message is displayed, view new
performance events to determine whether the LB test succeeded.
Issue 03 (2012-11-30)
1.
In the Main Topology, click the

icon to display Query Event Logs. Then, select
the Reporting of LB status information performance event.
2.
Right-click Reporting of LB status information. Then, choose Details ... from the
shortcut menu. The detailed information is displayed. Then, check the additional
information to confirm the test result.

94
OptiX OSN 7500 II/7500/3500/1500

3 ATM OAM
l If the test result is Test Failed, an error code and failure cause are displayed.
----End
3.7.5 Configuring ATM Alarm Transmission

In the ATM alarm transmission function, ATM OAM cells are inserted downstream or upstream
when the equipment detects an ATM service fault, so that the fault information can be transmitted
to a remote end. This topic describes the method of configuring ATM alarm transmission.
Prerequisites
Procedure
Step 1 In the NE Explorer, click the NE and choose Configuration > Packet Configuration > ATM
OAM Management. Click the Insert OAM Cell to ATM tab.
Step 2 Set Insert OAM Cell to ATM to Enabled. After the setting, AIS/RDI cells can be generated
at any connection point where a fault is detected and is transmitted to a remote end.
Step 3 Click Apply. The Operation Result dialog box is displayed, indicating that the operation
succeeded.
----End

This section uses an example to describe how to plan and configure ATM OAM according to
network conditions.
3.8.1 Example Description

This section describes the functional requirement, network diagram, and service planning.
Networking and Requirements

ATM OAM is an end-to-end OAM function for services. It can check the quality of ATM links.
ATM OAM is used to insert some OAM cells with a standard cell structure to user cell flows to
provide some specific information of the network. The following detection methods are
available: CC, LB, segment and end attribute, AIS cells, and RDI cells.
As shown in Figure 3-7, a UNIs-NNI ATM service from the NodeB to the RNC is created. The
service is connected to the NodeB through NE1, and is connected to the RNC through NE2. The
service type is N:1 VC switching. The source VPI/VCI is 32/33, and the sink VPI/VCI is 52/53.
The ATM service needs to be checked. Only the connectivity of the services in the directions
from the NodeB to NE1 and from the RNC to NE2 can be checked. Enable the CC and LB
functions to check whether the link is normal. If the services are unavailable, an alarm will be
reported.
Issue 03 (2012-11-30)

95
OptiX OSN 7500 II/7500/3500/1500

3 ATM OAM
Figure 3-7 Networking of ATM OAM

32-N1AFO1-1(PORT-1)
35-N1D12E-1(PORT-1)
Node B
NE1
RNC
NE2
PW
Service Planning
For ATM services, the segment and end attributes, CC activation status or remote loopback test
of each connection needs to be set. In this case, the ATM service has only one connection. The
related parameters need to set in the forward directions of the source NE and sink NE. The
forward direction is from the user side to the network side, that is, the directions from the NodeB
to NE1 and from the RNC to NE2 as shown in Figure 3-7. The service shown in Figure 3-7 is
taken as an example. Table 3-5 shows the parameters planned for ATM OAM.
Table 3-5 Parameters planned for ATM OAM
Attribute
Value
NE
NE1
NE2
Source
35-N1D12E-1
(PORT-1)-32-33
32-N1AFO1-1
(PORT-1)-52-53
Sink
PW(ATM n to one
VCC cell transport,
20)-32-33
PW(ATM n to one VCC cell

transport,20)-52-53
Connection
Direction
Sink
Source
Segment and End

Attribute
Segment point
Segment point
Source
35-N1D12E-1
(PORT-1)-32-33
32-N1AFO1-1
(PORT-1)-52-53
Sink
PW(ATM n to one
VCC cell transport,
20)-32-33
PW(ATM n to one VCC cell

transport,20)-52-53
Connection
Direction
Sink
Source
Segment and End

Attribute
Segment point
Segment point
Segment and
End
Attributes
CC
Activation
Status
Issue 03 (2012-11-30)

96
OptiX OSN 7500 II/7500/3500/1500

Attribute
LLID
Remote
Loopback
Test
3 ATM OAM
Value
CC Activate Flag
Source Activate
Sink Activate
Country Code
(Hexadecimal
Code)
[2BYTE]00 00
[2BYTE]00 00
Network Code
(Hexadecimal
Code)
[2BYTE]00 00
[2BYTE]00 00
NE Code
(Hexadecimal
Code)
[11BYTE]00 09 00 02
00 00 00 00 00 12 00
[11BYTE]00 09 00 02 00 00
00 00 00 12 00
Source
35-N1D12E-1
(PORT-1)-32-33
Sink
PW(ATM n to one
VCC cell transport,
20)-32-33
Connection
Direction
Sink
Segment and End

Attribute
Segment point
Loopback Point
NE
NE2
Test Result
3.8.2 Configuration Process

This section describes the process of data configuration.
Prerequisites
An ATM service must be created.
Procedure
Step 1 On the U2000, set segment and end attributes for NE1 and NE2. For the setting method, see
Setting Segment End Attribute.
Set the following parameters that are related to the segment and end attributes of NE1:
l Source: 35-N1D12E-1(PORT-1)-32-33
l Sink: PW(ATM n to one VCC cell transport,20)-32-33
Issue 03 (2012-11-30)

97
OptiX OSN 7500 II/7500/3500/1500

3 ATM OAM
l Connection Direction: Sink

l Segment and End Attribute: Segment point
The following parameters, which are related to the segment end attributes of NE2, should be
configured.
l Source: 32-N1AFO1-1(PORT-1)-52-53
l Connection Direction: Source
Step 2 On the U2000, see the CC activation status for NE1 and NE2. For the setting method, see Setting
the CC Activation Status.
The following parameters, which are related to the CC activation status of NE1, should be
configured.
l CC Activate Flag: Source Activate
Set the following parameters that are related to the CC activation status of NE2:
l Source: 32-N1AFO1-1(PORT-1)-52-53
l Connection Direction: Source
l CC Activate Flag: Sink Activate
Step 3 On the U2000, set LLIDs for NE1 and NE2. For the setting method, see Setting Local Loopback
ID.
The following parameters, which are related to the LLID of NE1, should be configured.
l Country Code (Hexadecimal Code): [2BYTE] 00 00
l Network Code (Hexadecimal Code): [2BYTE] 00 00
l NE Code (Hexadecimal Code): [11BYTE] 00 09 00 02 00 00 00 00 00 12 00
Set the following parameters that are related to the LLID of NE2:
l Country Code (Hexadecimal Code): [2BYTE] 00 00
l Network Code (Hexadecimal Code): [2BYTE] 00 00
l NE Code (Hexadecimal Code): [11BYTE] 00 09 00 02 00 00 00 00 00 12 00
Step 4 On the U2000, configure a remote loopback test for NE1. For the configuration method, see
Setting a Remote Loopback Test.
Set the following parameters that are related to the remote loopback test of NE1:
Issue 03 (2012-11-30)

98
OptiX OSN 7500 II/7500/3500/1500

3 ATM OAM

l Loopback Point NE: NE2
NOTE
If a remote loopback test needs to be initiated on NE2 and performed on NE1, configure the test on NE2. The
configuration method is the same as that used on NE1.
----End

This topic describes the alarms and performance events that are related to the ATM OAM feature.
3.9.1 Relevant Alarms

This topic describes the alarms related to ATM OAM.
Table 3-6 lists the alarms that are related to the ATM OAM.
Table 3-6 Alarms related to ATM OAM
Issue 03 (2012-11-30)
Alarm Name
Meaning
VP_AIS
The VP_AIS is an alarm indication signal for the virtual path (VP).
This alarm occurs when a forward or backward VP that is
configured with the segment end point attribute receives the AIS
cells, indicating that the upstream services are incorrect.
VP_LOC
The VP_LOC is an alarm indicating that the connectivity check

(CC) of the virtual path (VP) is lost. This alarm occurs after the
activated CC sink of a VP connection fails to receive any user
cells or CC cells within 3.5 (0.5) seconds. This alarm is cleared
after the CC sink receives user cells or CC cells.
VP_RDI
The VP_RDI is an alarm of remote defect indication. This alarm

occurs when a forward or backward virtual path (VP) that is
configured with the segment end point attribute receives the RDI
cells, indicating that the downstream services are incorrect.
VC_AIS
The VC_AIS is an alarm indication signal for the virtual channel

(VC). This alarm occurs when a forward or backward VC that is
configured with the segment end point attribute receives the AIS
cells, indicating that the upstream services are incorrect.
VC_LOC
The VC_LOC is an alarm indicating that the connectivity check

(CC) of the virtual channel (VC) is lost. This alarm occurs after
the activated CC sink of a VC connection fails to receive any user
cells or CC cells within 3.5 (0.5) seconds. This alarm is cleared
after the CC sink receives user cells or CC cells.

99
OptiX OSN 7500 II/7500/3500/1500

3 ATM OAM
Alarm Name
Meaning
VC_RDI
The VC_RDI is an alarm of remote defect indication. This alarm

occurs when a forward or backward virtual channel (VC) that is
configured with the segment end point attribute receives the RDI
cells, indicating that the downstream services are incorrect.
3.9.2 Relevant Performance Events

None.

This topic describes the parameters required for configuring ATM OAM.
3.10.1 Segment and End Attributes

This section describes the parameters for configuring segment and end attributes of ATM OAM.
Table 3-7 lists the parameters for configuring segment and end attributes of ATM OAM.
Table 3-7 Parameters for configuring segment and end attributes of ATM OAM
Field
Value
Description
Source
Slot ID-board name-port-VPIVCI
Displays the source node of the

ATM/IMA service.
For example: 38-N1D75E-1

(Trunk-1)-10-66
Sink
l UNI-UNI: slot ID-board

name-port-VPI-VCI
(Trunk-1)-10-66
Displays the sink node of the

ATM/IMA service.
l UNIs-NNI: PW(type)-VPIVCI
For example: PW(ATM n to
one VCC cell transport,
16385)-10-66
Issue 03 (2012-11-30)

100
OptiX OSN 7500 II/7500/3500/1500

3 ATM OAM
Field
Value
Description
Connection Direction
Source, Sink
Displays the direction of the

ATM connection.
l Source: that is, Forward, the
direction in which the ATM
OAM cell stream enters the
ATM connection.
l Sink: that is, Backward, the
OAM cell stream leaves the
ATM connection.
Connection Direction.
Segment and End

Attribute
Non segment and Endpoint,

Segment point, Endpoint,
Segment and Endpoint
Default: Non segment and
Endpoint
The Segment and End

Attribute parameter specifies
the type of an operation,
administration and maintenance
(OAM) maintenance point. For
different segment and end
attributes, different ranges of
asynchronous transfer mode
(ATM) OAM cells are processed.
For details, see A.14.2 Segment
and End Attribute.
3.10.2 CC Activation Status

This section describes the parameters for configuring the CC activation status of ATM OAM.
Table 3-8 lists the parameters for configuring the CC activation status of ATM OAM.
Table 3-8 Parameters for configuring the CC activation status
Field
Value
Description
Source

ATM/IMA service.

(Trunk-1)-10-66
Issue 03 (2012-11-30)

101
OptiX OSN 7500 II/7500/3500/1500

3 ATM OAM
Field
Value
Description
Sink

name-port-VPI-VCI
(Trunk-1)-10-66

ATM/IMA service.
16385)-10-66
Source, Sink

ATM connection.
ATM connection.
ATM connection.
Segment and End

Attribute
Non segment and Endpoint,

Segment point, Endpoint,
Displays the segment and end

attributes of the source and sink
nodes,or specifies the range of
the link checked by CC.
For details, see A.14.2 Segment
and End Attribute.
Issue 03 (2012-11-30)

102
OptiX OSN 7500 II/7500/3500/1500

3 ATM OAM
Field
Value
Description
CC Activate Flag
Deactivate, Source activate, Sink

activate, Source + sink activate
Specifies the CC activation flag.
Default value: Deactivate
l Deactivate: This node does

not transmit or receive CC
cells.
l Source activate: This node
transmits but does not receive
CC cells.
l Source activate: This node
receives but does not transmit
CC cells. If this node does not
receive any service cells or
CC cells within a time
interval of 3.5 (0.5) seconds,
it will report the LOC alarm
and transmit AIS cells in the
forward direction. Once the
node receives any CC cells or
service cells, the LOC alarm
will be cleared.
l Source + sink activate: This
node transmits and receives
CC cells. If this node does not
receive any service cells or
CC cells within a time
interval of 3.5 (0.5) seconds,
it will report the LOC alarm
and transmit AIS cells in the
forward direction. Once the
node receives any CC cells or
service cells, the LOC alarm
will be cleared.
3.10.3 Remote Loopback Test

This section describes the parameters for the remote loopback (LB) test.
Table 3-9 lists the parameters for the remote LB test.
Issue 03 (2012-11-30)

103
OptiX OSN 7500 II/7500/3500/1500

3 ATM OAM
Table 3-9 Parameters for the remote LB test

Field
Value
Description
Source

ATM/IMA service.

(Trunk-1)-10-66
name-port-VPI-VCI
(Trunk-1)-10-66
Sink

ATM/IMA service.
16385)-10-66
Source, Sink

ATM connection.
ATM connection.
ATM connection.
Segment and End

Attribute
Segment point, Endpoint

Default: Segment point
Specifies the segment and end

attributes of the source and sink
nodes of the connection.
l Segment point: Segment LB
cells are looped back only at
a Segment point, Segment
and Endpoint, or Non
segment and Endpoint.
l Endpoint: End-to-end LB
cells are looped back only at
an Endpoint or Segment and
Endpoint.
Issue 03 (2012-11-30)

104
OptiX OSN 7500 II/7500/3500/1500

3 ATM OAM
Field
Value
Description
Loopback Point NE
NE ID or NE LLID
Specifies the NE where the

loopback point is located.
For example: NE(9-22) or

Country Code: [2BYTE]00 00,
Network Code: [2BYTE]00 00,
NE Code: [11BYTE]00 09 00 02
00 00 00 00 00 15 00
l Before an end-to-end LB test,

you need to set the segment
and end attributes of the two
end nodes in the test domain
to Endpoint. After the test,
restore the segment and end
attributes of the two end
nodes to their original values.
l Before a segment-to-segment
LB test, you need to set
segment and end attributes of
the one end node in the test
domain to Segment point or
Non segment and
Endpoint. After the test,
restore the segment and end
attributes of the one end node
to its original values.
Test Result
Test succeeded
Displays the remote LB test

command is applied. The test
results can be queried in the NMS
events.
3.10.4 LLID
This section describes the parameters for LLID.
Table 3-10 lists the parameters for LLID.
Table 3-10 Parameters for LLID
Field
Value
Description
Country Code
(Hexadecimal Code)
[2BYTE]00 00-ff ff
Displays or specifies the country

code of the ATM service. The
value is 2 bytes in length.
Default: [2BYTE]00 00

For details, see A.14.3 Country
Code(Hexadecimal Code).
Issue 03 (2012-11-30)

105
OptiX OSN 7500 II/7500/3500/1500

3 ATM OAM
Field
Value
Description
Network Code
(Hexadecimal Code)
[2BYTE]00 00-ff ff
Displays or specifies the network

code of the ATM service. The
value is 2 bytes in length.
Default: [2BYTE]00 00

For details, see A.14.4 Network
Code(Hexadecimal Code).
NE Code
(Hexadecimal Code)
[11BYTE]00 00 00 00 00 00 00
00 00 00 00-ff ff ff ff ff ff ff ff ff
ff ff
Displays or specifies the NE code

of the ATM service. The value is
11 bytes in length.
Default: 4-byte NE ID + 7-byte

0s
The default NE code can be used

if it is unique on the network.
The NE code and NE ID are
associated. Therefore, each NE
on the network has a unique NE
code.
For details, see A.14.5 NE Code
(Hexadecimal Code).
3.10.5 Insert OAM Cell to ATM

This section describes the parameters for insert OAM cell to ATM.
Table 3-11 lists the parameters for insert OAM cell to ATM.
Table 3-11 Parameters for insert OAM cell to ATM
Issue 03 (2012-11-30)
Field
Value
Description
Insert OAM Cell to

ATM
Enabled, Disabled
If the cell inserting function is

enabled, when the equipment
detects a service or link fault, it
inserts the AIS cell on the NNI
side and transparently transmits
the AIS cell to the remote
equipment.
Default: Enabled

106
OptiX OSN 7500 II/7500/3500/1500

4 ATM Traffic Management
ATM Traffic Management
About This Chapter

This chapter describes the ATM QoS feature.
4.1 Introduction
This section provides the definition of ATM QoS and describes its purpose.
4.2 Basic Concepts
This section describes the basic concepts associated with ATM traffic management.
This section describes the standards and protocols associated with ATM QoS.
4.4 Availability
This section describes the support required by the application of the ATM QoS feature.
This section describes the limitations on and precautions for ATM QoS in the network design
4.6 Principles
ATM traffic management is achieved by using the generic cell rate algorithm (GCRA).
4.7 Configuring ATM QoS
The main operation tasks of configuring ATM QoS include configuring ATM CoS mapping and
creating the ATM policy.
4.8 QoS Configuration Case of ATM Services
Configure an ATM policy and use the ATM policy for a specified ATM service. In this way,
the QoS for the ATM service is ensured. In addition, the tunnel QoS can be configured to control
the tunnel bandwidth of service flow.
4.9 Parameter Description: ATM QoS
This topic describes the parameters required for configuring ATM QoS.
Issue 03 (2012-11-30)

107
OptiX OSN 7500 II/7500/3500/1500

4.1 Introduction
This section provides the definition of ATM QoS and describes its purpose.
Definition
ATM QoS is a mechanism provided by the ATM network. With the mechanism, an ATM
network assures services of expected QoS objectives such as amount of bandwidth, delay, delay
variation, and packet loss ratio in whatever situations, so that users can know the expected service
level.
The equipment can provide ATM services with ensured quality levels by applying ATM traffic
control policies.
Purpose
ATM QoS aims to prevent occurrence of congestion in ATM services and improve utilization
of resources.
If ATM services are transmitted in PWE3 mode, service policies with appropriate priorities can
be provided for various categories of ATM services carried by VPCs or VCCs before the ATM
cells are encapsulated into PW packets. As shown in Figure 4-1, ATM QoS generally functions
in the ingress direction of a UNI on a PE.
Figure 4-1 Functioning point of ATM QoS
Functioning point of
ATM traffic control
ATM cells
Ingress
PSN
CE
PE
4.2 Basic Concepts

This section describes the basic concepts associated with ATM traffic management.
4.2.1 ATM Traffic Parameters

ATM traffic parameters are grouped into an ATM QoS descriptor.
ATM traffic parameters include peak cell rate (PCR), sustained cell rate (SCR), cell delay
variation tolerance (CDVT), and maximum burst size (MBS). For information about each traffic
parameter, see Table 4-1.
Issue 03 (2012-11-30)

108
OptiX OSN 7500 II/7500/3500/1500

Table 4-1 ATM traffic parameters

ATM
Traffic
Parameter
Full Name
Description
PCR
Peak cell rate
The PCR traffic parameter specifies an upper bound on the

rate at which traffic can be transmitted to a network.
An increased PCR allows a higher cell burst rate for a
connection but also results in utilization of more resources.
It is recommended that you set the value of the PCR twice
that of the SCR.
SCR
Sustained cell
rate
The SCR traffic parameter specifies an upper bound on the

sustained average rate at which traffic can be transmitted
to a network.
An increased SCR directly increases the connection rate
but also results in utilization of more resources.
It is recommended that you set the SCR to the required
amount of bandwidth.
CDVT
Cell delay
variation
tolerance
When cells from two or more connections are multiplexed,

transmission of cells in a given connection may be delayed
as cells of another connection are being inserted at the
output of the multiplexer. Similarly, transmission of some
cells may be delayed as physical layer overhead or OAM
cells are inserted. Consequently, from the perspective of a
receive site, the inter-arrival time between consecutive
cells varies in different periods of time. The CDVT
parameter specifies an upper limit on the variation
tolerance.
An increased CDVT enhances the ability of a system to
protect against cell delay variation and allows a larger link
differential delay for cells. When the PCR and SCR are
correctly set, you can increase the CDVT if some cells are
still discarded.
MBS
Maximum
burst size
The MBS traffic parameter specifies an upper bound on the

number of burst cells that are transmitted at an allowed rate.
An increased MBS helps a system be more tolerant of
bursts on a particular connection; that is, a connection is
allowed to transmit more burst cells.
Increase the MBS if traffic burst is likely to occur within a
certain period of time.
MCR
Issue 03 (2012-11-30)
Minimum Cell
Rate
The MCR traffic parameter specifies the minimum cell

rate. The rate at which traffic can be transmitted to a
network cannot be less than this value.

109
OptiX OSN 7500 II/7500/3500/1500

4.2.2 ATM Service Categories

ATM Forum defines five service categories, each of which has different conformance definitions
regarding traffic parameters.
ATM Forum defines five service categories, namely, CBR, UBR, UBR+, RT-VBR, and NRTVBR, as provided in Table 4-2. If the equipment needs to control traffic, set traffic parameters
for each service category on the equipment.
Table 4-2 ATM service categories and ATM traffic parameters
ATM
Service
Catego
ry
Full
Name
Applicat
ion
Example
ATM
Traffic
Paramete
r
Description
CBR
Constant
bit rate
Voice,
CBR
video, and
circuit
emulation
PCR and
CDVT
The CBR service requires tightly

constrained delay variation and requires
that data be transmitted at a constant rate.
In addition, the CBR service requests a
static amount of bandwidth and the
highest priority.
The CBR service is characterized by
stable traffic and few bursts.
Issue 03 (2012-11-30)
UBR
Unspecifi
ed bit rate
LAN
emulation
, IP over
ATM, and
unspecifie
d traffic
(such as
file
transfer
and email)
PCR and
CDVT
The UBR service is intended for non-realtime applications that allow many bursts.
The UBR service does not specify traffic
related service guarantees. Instead, the
UBR service only requires that the
network side provide the service with the
best effort (BE) guarantee, and the
network side does not provide any
guarantee for the UBR service. In the case
of network congestion, the UBR cells are
discarded first.
UBR+
Unspecifi
ed bit rate
plus
LAN
emulation
, IP over
ATM, and
unspecifie
d traffic
(such as
file
transfer
and email)
PCR,
CDVT,
and MCR
The UBR+ service is supplementary to

the UBR service and is intended for
applications that require an ensured
minimum cell rate, which is indicated by
the minimum cell rate (MCR) parameter.
The other characteristics of the UBR+
service are the same as the corresponding
characteristics of the UBR service.

110
OptiX OSN 7500 II/7500/3500/1500

ATM
Service
Catego
ry
Full
Name
Applicat
ion
Example
ATM
Traffic
Paramete
r
Description
RTVBR
Real-time
variable
bit rate
Voice and
VBR
video
PCR,
SCR,
CDVT,
and MBS
The RT-VBR service requires tightly

constrained delay and delay variation.
Compared with the CBR service, the RTVBR service allows sources to transmit
data at a rate that varies with time.
Equivalently, the sources can be
described as bursty. In addition, the RTVBR service does not require a static
amount of bandwidth.
NRTVBR
Non-realtime
variable
bit rate
Packet
transmissi
on,
terminal
meeting,
and file
transfer
PCR,
SCR, and
MBS
Compared with the RT-VBR service, the

NRT-VBR service does not require
tightly constrained delay or delay
variation, and is intended for non-realtime applications.
The NRT-VBR service has a lower
priority than the RT-VBR service but still
has variable bit rate and bursty traffic
characteristics.
4.2.3 ATM Traffic Categories

Directly apply an appropriate ATM traffic category descriptor to provide traffic management
for a specific ATM service category.
Table 4-3 provides the mapping relationships between ATM service categories, ATM traffic
category descriptors, and traffic parameters. The mapping relationships provide a basis for ATM
policy configuration.
Table 4-3 Mapping relationships between ATM service categories, ATM traffic category descriptors, and traffic
parameters
ATM
Service
Category
ATM Traffic Category

Descriptor
Traffic
Parameter 1
Traffic
Parameter 2
Traffic
Parameter 3
Traffic
Parameter 4
UBR
NoTrafficDescriptor
NoClpTaggingNoScr
Clp01Pcr
CDVT
NoClpNoScr
Clp01Pcr
NoClpNoScrCdvt
Clp01Pcr
CDVT
ClpTransparentNoScr
Clp01Pcr
CDVT
ClpNoTaggingNoScr
Clp01Pcr
Clp0Pcr
CBR
Issue 03 (2012-11-30)

111
OptiX OSN 7500 II/7500/3500/1500

ATM
Service
Category
NRT-VBR
RT-VBR
UBR+
ATM Traffic Category

Descriptor
Traffic
Parameter 1
Traffic
Parameter 2
Traffic
Parameter 3
Traffic
Parameter 4
ClpTaggingNoScr
Clp01Pcr
Clp0Pcr
NoClpNoScr
Clp01Pcr
NoClpNoScrCdvt
Clp01Pcr
CDVT
NoClpScr
Clp01Pcr
Clp01Scr
MBS
ClpNoTaggingScr
Clp01Pcr
Clp0Scr
MBS
ClpTaggingScr
Clp01Pcr
Clp0Scr
MBS
ClpTransparentScr
Clp01Pcr
Clp01Scr
MBS
CDVT
NoClpScrCdvt
Clp01Pcr
Clp01Scr
MBS
CDVT
ClpNoTaggingScrCdvt
Clp01Pcr
Clp0Scr
MBS
CDVT
ClpTaggingScrCdvt
Clp01Pcr
Clp0Scr
MBS
CDVT
AtmNoTrafficDescriptorMcr
Clp01Mcr
AtmNoClpMcr
Clp01Pcr
Clp01Mcr
AtmNoClpMcrCdvt
Clp01Pcr
Clp01Mcr
CDVT
NOTE
"-" indicates that the traffic parameter is unused.
4.2.4 ATM Traffic Control Schemes

The equipment supports the following ATM traffic control schemes: connection admission
control (CAC), usage parameter control (UPC)/network parameter control (NPC), and early
packet discard (EPD)/partial packet discard (PDD).
CAC
The CAC function is used to determine whether a connection can be progressed or should be
rejected. A connection request is progressed only when sufficient resources are available, in
order to maintain the agreed QoS of established connections.
The equipment determines whether a connection can be progressed or should be rejected
according to the following principle: The SCR sum of all the connections does not exceed the
maximum service access bandwidth of the equipment.
UPC/NPC
UPC/NPC is defined as the set of actions taken to monitor traffic and enforce the traffic contract.
Its main purpose is to monitor the cells received on ATM virtual connections according to
negotiated traffic parameters, thus to avoid possible network congestion.
Issue 03 (2012-11-30)

112
OptiX OSN 7500 II/7500/3500/1500

Connection monitoring at a UNI (private or public) is referred to as UPC. Connection monitoring

at an NNI (private or public) is referred to as NPC.
At the cell level, actions of the UPC function may include:
l
Cell passing
The UPC function considers that the cell conforms to the negotiated traffic contract and
therefore allows the cell to pass.
Cell tagging
Cell tagging is operated for CLP = 0 cells only, by converting CLP = 0 into CLP = 1. The
UPC function considers that the tagged cell conforms to the negotiated traffic contract and
therefore allows the cell to pass. In the case of network congestion, however, the tagged
cell is discarded.
Cell discarding
The UPC function considers that the cell violates conformance to the negotiated traffic
contract and therefore discards the cell.
EPD/PPD
l
EPD
If the EPD function is enabled, the system always monitors the status of the cell buffer.
Once the network is detected congested, the system discards all the cells in the next ATM
Adaptation Layer Type 5 (AAL5) packet. The EPD function is effective for congestion
prevention because cell discarding is performed at the packet level. The system, however,
cannot selectively discard packets because the EPD function cannot differentiate a good
packet from a bad packet.
PPD
The system starts to discard an ATM cell and all the following cells in the same AAL5
packet, to reduce the load on the network if all the following conditions are met: (1) The
PPD function is enabled; (2) AAL5 packets are used to carry ATM cells; (3) Network
congestion occurs or the transmit traffic volume exceeds the amount of allocated
bandwidth. The AAL5 packet, however, may fail to be restored and results in a bad packet
due to loss of an ATM cell. Therefore, the AAL5 packet needs to be retransmitted.

This section describes the standards and protocols associated with ATM QoS.
The following standards and protocols are associated with ATM QoS:
l
ATM Forum AF-TM-0121.000: Traffic Management Specification Version 4.1
IETF RFC 2514: Definitions of Textual Conventions and Object-identities for ATM
Management
4.4 Availability
This section describes the support required by the application of the ATM QoS feature.
Issue 03 (2012-11-30)

113
OptiX OSN 7500 II/7500/3500/1500

Version Support
Applicable Version
OptiX OSN 7500 II
U2000
Applicable Version
OptiX OSN 3500/7500
U2000
V100R005 and later
Hardware Support
Applicable Board
Applicable Version
TNN1AFO1
OptiX OSN 7500 II
TNN1D75E
OptiX OSN 7500 II
TNN1D12E
OptiX OSN 7500 II
N1MD12
OptiX OSN 3500/7500
N1MD75
OptiX OSN 3500/7500

This section describes the limitations on and precautions for ATM QoS in the network design
Issue 03 (2012-11-30)
Applicable
Object

Details
Remarks
ATM policy
The TNN1D12E and TNN1D75E

support a maximum of 32 CBR
policies.
ATM CoS
mapping table
A maximum of eight ATM CoS

mapping tables are supported. The
default ATM CoS mapping table
(the first one) cannot be deleted.

114
OptiX OSN 7500 II/7500/3500/1500

Applicable
Object

Details
Remarks
Pcr/Scr
The value of Pcr or Scr must be less

than or equal to the physical
bandwidth of associated ATM ports
or IMA groups.
Maximum cell
burst size and
cell delay
variation
tolerance
It is recommended that you set the

maximum cell burst size and cell
delay variation tolerance to values
greater than or equal to those of the
opposite equipment.
NOTE
Setting the uplink policy of
TNN1AFO1:
l The CDVT value needs to be set to
meet CDVT<=1/PCR.
l The MBS value needs to be set to
meet MBS<=SCR.

Applicable
Object

Details
Remarks
ATM CoS
mapping table
Do not modify an ATM CoS

mapping table after it is applied to
NNI ports.
ATM policy
Do not enable the ATM policy UPC/

NPC on the NNI side for the
TNN1AFO1.
None.
4.6 Principles
ATM traffic management is achieved by using the generic cell rate algorithm (GCRA).
Basic GCRA Principles

The GCRA is used to determine whether ATM traffic conforms to the traffic contract. If the
ATM network becomes congested because the received cells within a short period of time exceed
the contract or the affordable capability of the receive equipment due to very heavy ATM traffic,
the GCRA takes some punishment actions.
Fundamentally, the GCRA complies with the following principles: The GCRA allows the actual
inter-arrival time between cells to be equal to (arrival on schedule) or vary from the expected
Issue 03 (2012-11-30)

115
OptiX OSN 7500 II/7500/3500/1500

inter-arrival time. The variation can be a negative value (arrival ahead of schedule) or a positive
value (delayed arrival). If a cell arrives ahead of schedule, however, the variation must not exceed
the preset CDVT. Otherwise, the GCRA considers that the cell violates conformance to the
contract.
Figure 4-2 uses an example to describe how the equipment performs traffic management on cell
2 in four arrival scenarios based on the principles of the GCRA. Assume the following
conditions: The contracted maximum traffic rate is PCR; the UPC/NPC function is enabled;
variable T is equal to 1/PCR, that is, a cell is transmitted to the network at an interval not shorter
than T; cell 1 arrives at time t1; cell 2 is expected to arrive at time t2 (t2 = t1 + T).
Figure 4-2 Illustration of basic GCRA principles
T
T
L
1
Cell 1
1
Cell 2 arrives T after the arrival of cell 1 (on schedule).
2
t2
t1
Cell 3 is expected to arrive at time t2 + T.

T
2
t1
e
3
1
t1
1
t1
t2 + d
Cell 2 arrives d late.

Cell 3 is expected to arrive at time t2 + d + T.
T
Cell 2 arrives e early and the

variation can be tolerated.
t2 - e
T
Cell 2 arrives very early and the variation exceeds the preset
CDVT, and therefore the equipment discards or remarks the cell.
Cell 3 is expected to arrive at time t2.
Table 4-4 describes the preceding example.

Table 4-4 Description of basic GCRA principles
Issue 03 (2012-11-30)
Cell Arrival
Description
UPC/NPC
Operation
Normal
(arrival
on
schedule
)
Cell 2 arrives T after the arrival of cell 1 (on schedule).

Cell passing
Normal
(delayed
arrival)
Cell 2 is expected to arrive at time t1 + T but actually

arrives at time t2 + d. The time variation is d.
Cell passing
Cell 3 is expected to arrive at time t2 + d + T (not t1 +

2 x T).
116
OptiX OSN 7500 II/7500/3500/1500

Cell Arrival
Description
UPC/NPC
Operation
Cell 2 is expected to arrive at time t1 + T but arrives e

early because the cell rate exceeds the contracted PCR.
e, however, is smaller than L (representing the preset
CDVT), and therefore the GCRA considers that cell 2
does not violate conformance to the contract.
Cell passing
Burst
(arrival
ahead of
schedule
)
Note that cell 3 is expected to arrive at time t2 + T (not

t2 - e + T). This prevents cells from being transmitted
at a rate higher than the contracted PCR within a period
of time.
4
Violatio
n
Cell 2 is transmitted at a very high rate and as a result,

cell 2 arrives very early and the time variation exceeds
L. Therefore, the GCRA considers that cell 2 violates
conformance to the contract.
Cell tagging or
discarding
Leaky Bucket Algorithm of the GCRA

The following part uses the example provided in Figure 4-2 to describe the implementation
process of the leaky bucket algorithm. For easy understanding, assume that cells are transmitted
to a bucket with an entry and an exit as shown in Figure 4-3, instead of being transmitted to the
equipment. In addition, assume that the capacity of the bucket is T + L, wherein T is equal to 1/
PCR and L represents the variation tolerance. Both T and L are time factors.
l
In normal cases (for example, scenario 1 or scenario 2 in Figure 4-2), cell 2 uses capacity
T after arrival. When cell 3 arrives T after the arrival of cell 2, cell 2 leaks from the bucket
and the used capacity of the bucket remains T.
In the case of cell bursts (for example, scenario 3 in Figure 4-2), cell 2 arrives e early.
When cell 2 arrives, cell 1 partially leaks from the bucket and therefore a cell capacity e
remains in the bucket. In this case, the used capacity of the bucket is T + e. The leaky bucket
algorithm performs strict control and adjusts the expected arrival time of cell 3 to time t2
+ T (as specified in Table 4-4). As a result, if the arrival time of the subsequent n cell(s)
is normal (that is, the arrival time of the cells is not greater than t2 + n x T, where n = 1, 2,
3, ...), these cells can completely leak from the bucket; if bursts occur in the subsequent
cells (that is, the arrival time of certain cells is smaller than t2 + n x T), the used capacity
of the bucket gradually increases. When the used capacity of the bucket exceeds T + L,
overflow cells are tagged or discarded.
Issue 03 (2012-11-30)

117
OptiX OSN 7500 II/7500/3500/1500

Figure 4-3 Leaky bucket algorithm
Cells at each arrival

uses a capacity T.
Contract conformance
violation cell
One unit of cells

leaks per time-unit.
ATM Traffic Management by Using the Two-Level Leaky Bucket Algorithm

The equipment monitors ATM traffic by using the two-level leaky bucket algorithm, as shown
in Figure 4-4. Contract conformance violation cells are discarded or tagged according to UPC/
NPC actions.
Figure 4-4 Two-level leaky bucket algorithm
Level-1 bucket
Contract
conformance
violation cell
Level-2 bucket
Contract
conformance
violation cell
The ATM traffic management sequence by using the two-level leaky bucket algorithm is
different for different chips or service types, as shown in Table 4-5.
Issue 03 (2012-11-30)

118
OptiX OSN 7500 II/7500/3500/1500

Table 4-5 ATM traffic management sequence by using the two-level leaky bucket algorithm
ATM traffic
management
sequence by
using the twolevel leaky
bucket
algorithm
ATM
Servic
e
Catego
ry
UBR
CBR
Issue 03 (2012-11-30)
ATM Traffic
Category
Descriptor
Traffic
Param
eter 1
Traffic
Param
eter 2
Traffic
Param
eter 31
Traffic
Param
eter 4
TNN1
AFO1
TNN1
D75E,
TNN1
D12E,
N1MD
75,
N1MD
12
NoTrafficDescriptor
NoClpTaggingNoScr
Clp01P
cr
CDVT
NoClpNoScr
Clp01P
cr
NoClpNoScrCd
vt
Clp01P
cr
CDVT
ClpTransparent
NoScr
Clp01P
cr
CDVT
ClpNoTaggingNoScr
Clp01P
cr
Clp0Pcr
ClpTaggingNo
Scr
Clp01P
cr
Clp0Pcr
At level-1 bucket,
Clp01 is processed
based on Clp01Pcr,
and improper cells
are discarded.
At level-2 bucket,
Clp0 is processed
based on Clp0Pcr,
and improper cells
are discarded.
NoClpNoScr
Clp01P
cr
NoClpNoScrCd
vt
Clp01P
cr
CDVT

119
OptiX OSN 7500 II/7500/3500/1500

ATM traffic
management
sequence by
bucket
algorithm
ATM
Servic
e
Catego
ry
NRTVBR
ATM Traffic
Category
Descriptor
Traffic
Param
eter 1
Traffic
Param
eter 2
Traffic
Param
eter 31
Traffic
Param
eter 4
NoClpScr
Clp01P
cr
Clp01S
cr
MBS
ClpNoTagging
Scr
Issue 03 (2012-11-30)
Clp01P
cr
Clp0Scr
MBS

TNN1
AFO1
TNN1
D75E,
TNN1
D12E,
N1MD
75,
N1MD
12
At
level-1
bucket,
Clp01 is
process
ed
based
on
Clp01P
cr, and
imprope
r cells
are
discarde
d.
At
level-1
bucket,
Clp01 is
process
ed
based
on
Clp01S
cr, and
imprope
r cells
are
discarde
d.
At
level-2
bucket,
Clp01 is
process
ed
based
on
Clp01S
cr, and
imprope
r cells
are
discarde
d.
At
level-2
bucket,
Clp01 is
process
ed
based
on
Clp01P
cr, and
imprope
r cells
are
discarde
d.
At
level-1
bucket,
Clp01 is
process
At
level-1
bucket,
Clp0 is
process
120
OptiX OSN 7500 II/7500/3500/1500

ATM traffic
management
sequence by
bucket
algorithm
ATM
Servic
e
Catego
ry
RTVBR
Issue 03 (2012-11-30)
TNN1
AFO1
TNN1
D75E,
TNN1
D12E,
N1MD
75,
N1MD
12
ed
based
on
Clp01P
cr, and
imprope
r cells
are
discarde
d.
At
level-2
bucket,
Clp0 is
process
ed
based
on
Clp0Scr
, and
imprope
r cells
are
discarde
d.
ed
based
on
Clp0Scr
, and
imprope
r cells
are
discarde
d.
At
level-2
bucket,
Clp01 is
process
ed
based
on
Clp01P
cr, and
imprope
r cells
are
discarde
d.
CDVT
At
level-1
bucket,
Clp01 is
process
ed
based
At
level-1
bucket,
Clp01 is
process
ed
based
ATM Traffic
Category
Descriptor
Traffic
Param
eter 1
Traffic
Param
eter 2
Traffic
Param
eter 31
Traffic
Param
eter 4
ClpTaggingScr
Clp01P
cr
Clp0Scr
MBS
ClpTransparentScr
Clp01P
cr
Clp01S
cr
MBS

121
OptiX OSN 7500 II/7500/3500/1500

ATM traffic
management
sequence by
bucket
algorithm
ATM
Servic
e
Catego
ry
Issue 03 (2012-11-30)
TNN1
AFO1
TNN1
D75E,
TNN1
D12E,
N1MD
75,
N1MD
12
CDVT
on
Clp01P
cr, and
imprope
r cells
are
discarde
d.
At
level-2
bucket,
Clp01 is
process
ed
based
on
Clp01S
cr, and
imprope
r cells
are
discarde
d.
on
Clp01S
cr, and
imprope
r cells
are
discarde
d.
At
level-2
bucket,
Clp01 is
process
ed
based
on
Clp01P
cr, and
imprope
r cells
are
discarde
d.
CDVT
At
level-1
bucket,
Clp01 is
process
ed
based
At
level-1
bucket,
Clp0 is
process
ed
based
ATM Traffic
Category
Descriptor
Traffic
Param
eter 1
Traffic
Param
eter 2
Traffic
Param
eter 31
Traffic
Param
eter 4
NoClpScrCdvt
Clp01P
cr
Clp01S
cr
MBS
ClpNoTaggingScrCdvt
Clp01P
cr
Clp0Scr
MBS

122
OptiX OSN 7500 II/7500/3500/1500

ATM traffic
management
sequence by
bucket
algorithm
ATM
Servic
e
Catego
ry
UBR+
Issue 03 (2012-11-30)
TNN1
AFO1
TNN1
D75E,
TNN1
D12E,
N1MD
75,
N1MD
12
CDVT
on
Clp01P
cr, and
imprope
r cells
are
discarde
d.
At
level-2
bucket,
Clp0 is
process
ed
based
on
Clp0Scr
, and
imprope
r cells
are
discarde
d.
on
Clp0Scr
, and
imprope
r cells
are
discarde
d.
At
level-2
bucket,
Clp01 is
process
ed
based
on
Clp01P
cr, and
imprope
r cells
are
discarde
d.
At level-1 bucket,
Clp01 is processed
based on
Clp01Mcr, and
ATM Traffic
Category
Descriptor
Traffic
Param
eter 1
Traffic
Param
eter 2
Traffic
Param
eter 31
Traffic
Param
eter 4
ClpTaggingScrCdvt
Clp01P
cr
Clp0Scr
MBS
AtmNoTraffic
DescriptorMcr
Clp01
Mcr
AtmNoClpMcr
Clp01P
cr
Clp01
Mcr

123
OptiX OSN 7500 II/7500/3500/1500

ATM traffic
management
sequence by
bucket
algorithm
ATM
Servic
e
Catego
ry
ATM Traffic
Category
Descriptor
Traffic
Param
eter 1
Traffic
Param
eter 2
Traffic
Param
eter 31
Traffic
Param
eter 4
AtmNoClpMcr
Cdvt
Clp01P
cr
Clp01
Mcr
CDVT
TNN1
AFO1
TNN1
D75E,
TNN1
D12E,
N1MD
75,
N1MD
12
improper cells are

discarded.
At level-2 bucket,
Clp01 is processed
based on Clp01Pcr,
and improper cells
are discarded.
NOTE
"-" indicates that the traffic parameter is unused.
4.7 Configuring ATM QoS

The main operation tasks of configuring ATM QoS include configuring ATM CoS mapping and
creating the ATM policy.
4.7.1 Configuring ATM CoS Mapping

Configure the mapping between ATM service types and PHB service classes to ensure end-toend QoS for ATM services.
Prerequisites
Context
The OptiX OSN 7500 II equipment supports the flexible mapping between the ATM service
type and PHB service class. Table 4-6 lists the default ATM CoS mapping relation.
Issue 03 (2012-11-30)

124
OptiX OSN 7500 II/7500/3500/1500

Table 4-6 Mapping relation between the ATM service type and PHB service class
ATM Service Category
PHB Service Class
CBR
EF
RT-VBR
AF31
NRT-VBR
AF21
UBR+
AF11
UBR
BE
PORT-TRANS
BE
NOTE
The default ATM CoS mapping cannot be modified or deleted.
Procedure
Step 1 In the NE Explorer, click the NE and choose Configuration > Packet Configuration > QoS
Management > Diffserv Domain Management > ATM CoS Mapping Configuration from
the Function Tree.
Step 2 Click Create. The Create ATM CoS Mapping Relation dialog box is displayed.
Step 3 Set the following parameters in the dialog box.
l Mapping Relation ID
l Mapping Relation Name
l Mapping between the Service Type and PHB
Step 4 Click OK.

----End
Issue 03 (2012-11-30)

125
OptiX OSN 7500 II/7500/3500/1500

4.7.2 Creating the ATM Policy

Create the ATM policy to configure the service type and bandwidth for the ATM traffic.
Prerequisites
Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > Packet Configuration > QoS
Management > Policy Management > ATM Policy from the Function Tree.
Step 2 Click New. The Create ATM Policy dialog box is displayed.
Step 3 Set the following parameters in the dialog box.
l Policy ID and name
NOTE
Select one from the drop-down list that contains five levels of ATM service policies. Alternatively, enter a
policy name.
l Service type
l Traffic parameter
l Frame discarding label
l UPC/NPC
NOTE
The service encapsulated in AAL5 is sliced into cells. Enable Traffic Frame Discarding Flag determines
whether to discard cells or to discard the complete AAL5 frames for the cells. When Enable Traffic Frame
Discarding Flag is set to Enabled, the equipment will discard the complete AAL5 frames for the cells.
The Scr, Pcr, MBS, and CDVT bucket parameters are functional only when UPC/NPC is enabled for the ATM
policy.
Issue 03 (2012-11-30)

126
OptiX OSN 7500 II/7500/3500/1500

Step 4 Click OK.

----End
4.8 QoS Configuration Case of ATM Services

Configure an ATM policy and use the ATM policy for a specified ATM service. In this way,
the QoS for the ATM service is ensured. In addition, the tunnel QoS can be configured to control
the tunnel bandwidth of service flow.
4.8.1 Case Description

This section describes the networking and data planning of this case.
As shown in Figure 4-5, the OptiX OSN 7500 II equipment has IMA connections to two NodeBs
through E1 ports, and receives ATM services from these NodeBs. The OptiX OSN 7500 II
equipment first encapsulates the incoming ATM services into PWE3 packets, and transports the
packets to the opposite OptiX OSN 7500 II equipment over a PSN. When receiving the packets ,
the opposite OptiX OSN 7500 II equipment decapsulates the packets, and transports the ATM
services to the RNC through STM-1 optical interfaces.
Each NodeB transports services such as real-time voice services, signals, and data services. To
ensure QoS for different service types, the OptiX OSN 7500 II equipment specifies different
ATM policies for different service types, and uses different PWs to carry these services of various
types.
Figure 4-5 Networking diagram for the QoS configuration of ATM services
NE5
GE ring on
access layer
NE6
NE1
pw1
pw2
10 GE ring
on
convergence
layer
NE4
NE3
ATM
STM-1
NE2
pw3
IMA1
IMA2
RNC
Working Tunnel
NodeB 1
UNI
IMA1:
Connection 1
Connection 2
Connection 3
R99
HSDPA
Signaling
VPI
1
1
1
R99
HSDPA
Signaling
VPI
1
1
1
NNI
IMA2:
Issue 03 (2012-11-30)
Protection Tunnel
NNI
UNI
VCI
100
101
102
VPI
VCI
VPI
VCI
VPI
VCI
50
32
50
32
50
32
51
52
32
32
51
52
32
32
51
52
32
32
VCI
100
101
102
VPI
VCI
VPI
VCI
VPI
VCI
60
32
60
32
60
32
61
62
32
32
61
62
32
32
61
62
32
32
UNI
Connection 1
Connection 2
Connection 3
PW
NodeB 2
NNI
NNI

UNI
127
OptiX OSN 7500 II/7500/3500/1500

Figure 4-5 lists the service types of IMA traffic and QoS requirements.
Table 4-7 Service types and QoS requirements
Application Scenario
ATM Policy
PW
Bandw
idth
Tunnel Bandwidth
Voice service, which is

carried by the RT-VBR
type.
l Policy ID: 1
Bandwi
dth: 4
Mbit/s
30 Mbit/s
l Policy name: RTVBR

l Service type: RTVBR
l Traffic type:
ClpNoTaggingScrCdvt
l Clp01Pcr(cell/s):
4000
l Clp0Scr(cell/s): 1000
l MBS(cell): 100
l CDVT(us): 10000
l Enable Traffic Frame
Discarding Flag:
Disable
l UPC/NPC: Disable
Signaling service, which

is carried by the CBR
type.
l Policy ID: 2
l Policy name: CBR
l Service type: CBR
Bandwi
dth: 1
Mbit/s
l Traffic type:
NoClpNoScr
l Clp01Pcr(cell/s): 800
Discarding Flag:
Disable
l UPC/NPC: Disable
Data service, which is
carried by the UBR type.
l Policy ID: 3
l Policy name: UBR
l Service type: UBR
Bandwi
dth: 15
Mbit/s
l Traffic type:
NoTrafficDescriptor
Discarding Flag:
Disable
l UPC/NPC: Disabled
Issue 03 (2012-11-30)

128
OptiX OSN 7500 II/7500/3500/1500


This section describes the configuration process for this example. The configuration steps
include ATM policy configuration and application.
Prerequisites
l
Be aware of the networking and data planning of the example.
Procedure
Step 1 Configure the RT-VBR policy.
1.
In the NE Explorer, select NE1 and choose Configuration > Packet Configuration > QoS
Management > Policy Management > ATM Policy.
2.
Click New, and set the parameters in the Create ATM Policy dialog box displayed. Click
OK.
Set the parameters for the RT-VBR policy as follows:
l Policy ID: 1
l Policy name: RT-VBR
l Service type: RT-VBR (Select the service type based on the type of incoming service.
Specifically, the voice service corresponds to RT-VBR, which is of the highest service
priority.)
l Traffic type: ClpNoTaggingScrCdvt (This parameter indicates that the two-level bucket
is valid. At one level, CLP01 is processed based on Clp01Pcr, and improper cells are
discarded. At the other level, CLP0 is processed based on Clp0Scr, and improper cells
are discarded.)
l Clp01Pcr(cell/s): 4000 (This parameter indicates the maximum permitted rate at which
cells are transmitted. Set the parameter based on the service rate.)
l Clp0Scr(cell/s): 1000 (This parameter indicates the sustainable cell rate at which cells
are transmitted. Set the parameter based on the service rate.)
l MBS(cell): 100 (This parameter indicates the maximum number of burst cells tolerated
by the equipment after the traffic exceeds Clp01Pcr.)
l CDVT(us): 10000 (This parameter indicates the capability of tolerating burst ATM
cells. When a cell arrives later than it is expected, the cell bursts. The burst volume is
measured by the time difference between the actual arrival time and expected arrival
time. If the burst volume of multiple consecutive cells exceeds the CDVT, the equipment
discards the improper cells. Set the parameter to a large value, when possible, to
minimize the number of lost packets.)
l Enable Traffic Frame Discarding: Disabled (The service encapsulated in AAL5 is sliced
into cells. This parameter specifies whether to discard cells or to discard the complete
AAL5 frames for the cells.)
l UPC/NPC: Enable (UPC and NPC stand for user parameter control and network
parameter control respectively. The bucket algorithm is based on the content of UPC/
NPC. UPC/NPC is intended to monitor the cells received by the equipment based on
the specified traffic parameters, and thus to avoid network congestion. The Scr, Pcr,
MBS, and CDVT bucket parameters are functional only when UPC/NPC is enabled for
the ATM policy.)
Issue 03 (2012-11-30)

129
OptiX OSN 7500 II/7500/3500/1500

3.
Click OK.
4.
In the NE Explorer, select NE3 and repeat the previous steps to create the ATM policies
for NE3. Set the policy-related parameters of NE3 as the same as the policy-related
parameters of NE1.
Step 2 Configure the CBR policy.

1.
Management > Policy Management > ATM Policy in the Function Tree.
2.
Click New, set the parameters in the Create ATM Policy dialog box. Click OK.
Set the parameters for the CBR policy as follows:
l Policy ID: 2
l Policy name: CBR
l Service type: CBR (Select the service type based on the type of incoming service.
Specifically, the signal service corresponds to the CBR service, which is of the highest
service priority.)
l Traffic Type: NoClpNoScr (The bucket at the first level takes effect, processes the cells
with the Clp01 flags based on Clp01Pcr, and discards the cells without the Clp01 flags.)
l Clp01Pcr(cell/s): 800
l Enable Traffic Frame Discarding: Disabled
l UPC/NPC: Enable
3.
Click OK.
4.
In the NE Explorer, select NE3 and repeat the previous two steps to create the ATM policies
parameters of NE1.
Step 3 Configure the UBR policy.

1.
Management > Policy Management > ATM Policy in the Function Tree.
2.
Click New, and set the parameters in the Create ATM Policy dialog box. Click OK.
Set the parameters for the UBR policy as follows:
l Policy ID: 3
l Policy name: UBR (Select the service type based on the type of incoming service.
Specifically, the data service corresponds to the UBR service, which is of the lowest
service priority.)
l Service type: UBR (No QoS is ensured for the accessed service. In the case of network
congestion, the UBR cells are discarded at the earliest.)
l Traffic type: UBR (No QoS is ensured for the accessed service. In the case of network
congestion, the UBR cells are discarded at the earliest.)
l Enable Traffic Frame Discarding: Disabled
l UPC/NPC: Disabled
3.
Click OK.
4.
In the NE Explorer, select NE3 and repeat the previous steps to create the ATM policies
parameters of NE1.
Issue 03 (2012-11-30)

130
OptiX OSN 7500 II/7500/3500/1500

Step 4 Configure the ATM service.

When creating an ATM service, do as follows.
l Configure the ATM connection.
Specify the uplink and downlink ATM policy, that is, Policy 1(RT-VBR), for the ATM
connections that carry the voice services.
Specify the uplink and downlink ATM policy, that is, Policy 2(CBR), for the ATM
connections that carry the signal services.
Specify the uplink and downlink ATM policy, that is, Policy 3(UBR), for the ATM
connections that carry the data services.
l Configure the PW.
Specify the bandwidth for the PW in the QoS tab.
The bandwidth of PW 1 (corresponding to CBR service type) is 4 Mbit/s.
The bandwidth of PW 2 (corresponding to rt-VBR service type) is 1 Mbit/s.
The bandwidth of PW 3 (corresponding to UBR service type) is 15 Mbit/s.
l Configure the ATM CoS mapping relation.
Specify the ATM CoS mapping the ATM service. The mapping ID is 1 and the mapping
name is DefaultAtmCosMap.
NOTE
DefaultAtmCosMap is the default ATM CoS mapping table of the equipment and cannot be deleted. In this
example, the default CoS mapping table is used. The user can also create an ATM CoS mapping table as
required. For details on how to create an ATM CoS mapping table, see Configuring ATM CoS Mapping.
NOTE
For the ATM service configuration method, see Configuration Example (UNIs-NNI ATM Services).
----End
4.9 Parameter Description: ATM QoS

This topic describes the parameters required for configuring ATM QoS.
4.9.1 CoS Mapping

This section describes the parameters for CoS mapping.
Table 4-8 lists the parameters for CoS mapping.
Table 4-8 Parameters for CoS mapping
Issue 03 (2012-11-30)
Field
Value
Description
PW ID
Displays the ID of the PW that

carries services.

131
OptiX OSN 7500 II/7500/3500/1500

Field
Value
Description
CoS Mapping
Mapping Relation ID(Mapping

Relation Name)
Specifies the policy for mapping

different ATM service classes to
CoS priorities. By setting this
parameter, different quality
levels are provided for different
ATM services.
Default: 1(DefaultAtmCosMap)

For details, see A.13.12 CoS
Mapping(Per-NE
Configuration for CoS
Mapping).
4.9.2 Configuring an ATM Service Class Mapping Table

This section describes the parameters for configuring an ATM service class mapping table.
Table 4-9 lists the parameters for configuring an ATM service class mapping table.
Table 4-9 Parameters for configuring an ATM service class mapping table
Field
Value
Description
Mapping Relation ID
2 to 8
Specifies the ID of the ATM

service class mapping table.
Default: none
NOTE
1 is the default ID for the ATM

Mapping Relation
Name
A character string of less than 32

characters, which may contain
letters, numbers, and underlines.
For example: mapping_1
UBR
CBR
RT-VBR
NRT-VBR
UBR+
Issue 03 (2012-11-30)
BE, AF11, AF12, AF13, AF21,

AF22, AF23, AF31, AF32,
AF33, AF41, AF42, AF43, EF,
CS6, CS7
Default:
UBR: BE
CBR: EF
RT-VBR: AF31
NRT-VBR: AF21
UBR+: AF11
PORT-TRANS: BE
Specifies the name of ATM

Displays or specifies the PHBs
that correspond to different ATM
service categories.
l Eight PHB service classes are
available: BE, AF1, AF2,
AF3, AF4, EF, CS6, and CS7
for eight queues. Different
QoS policies are provided for
the queues of different PHBs.
132
OptiX OSN 7500 II/7500/3500/1500

Field
Value
Description
l CS6 to CS7: highest service
classes, mainly applicable to
signaling transmission.
l EF: fast forwarding,
applicable to services of low
transmission delays and low
packet loss rates.
l AF1 to AF4: assured
forwarding, applicable to
services that require an
assured transmission rate
rather than delay or jitter
limits.
PORT-TRANS
NOTE
The AF1 class includes three
subclasses: AF11, AF12, and
AF13. Only one of these
subclasses can take effect for
one queue. It is the same case
with AF2, AF3, and AF4.
l BE: best effort, applicable to

services that do not require
special processing.
4.9.3 ATM Policies

This section describes the parameters for configuring ATM policies.
Table 4-10 lists the parameters for configuring ATM policies.
Table 4-10 Parameters for configuring ATM policies
Field
Value
Description
Policy ID
1 to 256
Specifies the policy ID of the

ATM service.
Default: 1

Assign automatically
Selected, Not selected

Default: Not selected
Specifies whether the ID is

automatically assigned.
Issue 03 (2012-11-30)

133
OptiX OSN 7500 II/7500/3500/1500

Field
Value
Description
Policy Name
Synchronous Signal, Signaling,

Voice, Data, Video, or an entered
character string
Specifies the policy name of the

ATM service. The maximum
length of the value is 64 bytes.
Default: Synchronous Signal
NOTE
You can select one of the five ATM
service policy names from the dropdown list or enter the policy name.

Issue 03 (2012-11-30)

134
OptiX OSN 7500 II/7500/3500/1500

Field
Value
Description
Service Type
UBR, CBR, RT-VBR, NRTVBR, UBR+
Specifies the type of the ATM

service.
Default: UBR
l The UBR service is

characterized by non-realtime applications and many
bursts. The UBR service does
not specify traffic-related
service guarantees. To be
specific, the UBR service
only requires that the network
side provides the service with
the best effort. The network
side does not provide any
assured QoS for the UBR
service. In the case of network
congestion, the UBR cells are
discarded first.
l The CBR service requires
tightly constrained delay
variation and requires that
data be transmitted at a
constant rate. In addition, the
CBR service requests a static
amount of bandwidth and the
highest priority. The CBR
service is characterized by
stable traffic and few bursts.
l The RT-VBR service
requires tightly constrained
delay and delay variation.
Compared with the CBR
service, the RT-VBR service
allows sources to transmit
data at a rate that varies with
time. Equivalently, the
sources can be described as
bursty. In addition, the RTVBR service does not require
a static amount of bandwidth.
l Compared with the RTVBR service, the NRT-VBR
service does not require
tightly constrained delay or
delay variation, and is
intended for non-real-time
applications.
l The UBR+ service is
supplementary to the UBR
service and is intended for
Issue 03 (2012-11-30)

135
OptiX OSN 7500 II/7500/3500/1500

Field
Value
Description
applications that require
assured minimum cell rate,
which is indicated by the
minimum cell rate (MCR)
parameter. The other
characteristics of the UBR+
service are the same as the
corresponding characteristics
of the UBR service.
Traffic Service
The value range and default value

of Traffic Service vary with
Service Type.
For details, see A.13.13 Traffic
Service(ATM Policy).
The Traffic Service parameter

specifies the sub-type of a service
type. That is, multiple traffic
types are available for each type
of service. A traffic type specifies
the traffic parameters that can be
set, the methods of handling cells
whose cell loss priority (CLP)
values are 0 and 1, and the
supported functions (such as cell
labeling).
For details, see A.13.13 Traffic
Service(ATM Policy).
Clp01Pcr(cell/s)
90-149078
Default: None.
Specifies the peak cell rate of a

service whose CLP in the ATM
cell header is 1 or 0.
Clp01Pcr(cell/s)(ATM Policy).
Clp01Scr(cell/s)
90-149078
Default: None.
Specifies the sustainable cell rate

of a service whose CLP in the
ATM cell header is 1 or 0.
Clp01Scr(cell/s)(ATM Policy).
Issue 03 (2012-11-30)

136
OptiX OSN 7500 II/7500/3500/1500

Field
Value
Description
Clp0Pcr(cell/s)
90-149078
Specifies the peak cell rate of a

service whose CLP in the ATM
cell header is 0.
Default: None.

For details, see A.13.16 Clp0Pcr
(cell/s)(ATM Policy).
Clp0Scr(cell/s)
90-149078
Default: None.
Specifies the sustainable cell rate

of a service whose CLP in the
ATM cell header is 0.
For details, see A.13.17 Clp0Scr
(cell/s)(ATM Policy).
Clp01Mcr(cell/s)
566-32664
Default: None.
Specifies the minimum

transmission rate of cells whose
CLP in the ATM cell header is 1
or 0.
Clp01Mcr(cell/s)(ATM
Policy).
Max.Cell Burst Size

(cell)
2-200000
Default: None.
Specifies the maximum number

of cells that are continuously
transmitted on ATM path of a
VBR service at a rate of r (SCR
< r <PCR).
Max.Cell Burst Size(cell)
(ATM Policy).
Issue 03 (2012-11-30)

137
OptiX OSN 7500 II/7500/3500/1500

Field
Value
Description
Cell Delay Variation

Tolerance(0.1us)
7 to 13300000
Specifies the burst cell tolerance

of an ATM connection.
Default: None.
l The greater the parameter

value, the better performance
the service for burst cells. If
conditions are allowed, you
can set CDVT to a large value
to minimize packet loss.
l If UPC/NPC is enabled, The
CDVT recommended that
this parameter takes
maximum value.
For details, see A.13.20 Cell
Delay Variation Tolerance
(0.1us)(ATM Policy).
Discard Traffic
Frame
Enabled, Disabled
Default: Disabled
Specifies the frame discarding

mark in ATM policies. This
parameter is effective to AAL5
traffic.
It is recommended that this
parameter takes the default value.
UPC/NPC
Disabled, Enabled
Default: Disabled
The UPC/NPC parameter

specifies the user-network
interface (UNI) traffic
parameters based on usage
parameter control (UPC) and
network parameter control
(NPC).
l Disabled: The configured
ATM QoS parameters do not
take effect.
l Enabled: The configured
ATM QoS parameters take
effect.
l It is recommended that this
parameter takes Enabled.
NOTE
On the TNN1AFO1 board, UPC/
NPC cannot be enabled on the
downlink ATM connection (from
the sink to the source).
For details, see A.13.21 UPC/

NPC(ATM Policy).
Issue 03 (2012-11-30)

138
OptiX OSN 7500 II/7500/3500/1500

5 IMA
IMA
About This Chapter

This chapter describes the inverse multiplexing for ATM (IMA) feature.
5.1 Introduction
The inverse multiplexing for ATM (IMA) technology multiplexes multiple low-speed ATM
links into a high-speed link, providing protection for services when one of the low-speed ATM
links fail.
5.2 Basic Concepts
This section describes the basic concepts associated with IMA.
This section describes the standards and protocols associated with IMA.
5.4 Availability
The IMA function requires the support of the applicable equipment, boards, and software.
This section describes the limitations on and precautions for IMA in the network design phase,
configuration and commissioning phase, and maintenance phase.
5.6 Principles
This section describes the principles of the IMA feature.
5.7 Configuration Procedure
On an Hybrid MSTP equipment, an ATM trunk is used to describe an IMA group. Therefore,
the key to configuring IMA is to configuring an ATM trunk.
5.8 Configuring IMA
This topic describes the IMA configuration tasks.
This section uses an example to describe how to plan and configure IMA according to network
conditions.
This topic describes the alarms and performance events that are related to the IMA feature.
Issue 03 (2012-11-30)

139
OptiX OSN 7500 II/7500/3500/1500

5 IMA
This topic describes the parameters required for configuring IMA.
Issue 03 (2012-11-30)

140
OptiX OSN 7500 II/7500/3500/1500

5 IMA
5.1 Introduction
The inverse multiplexing for ATM (IMA) technology multiplexes multiple low-speed ATM
links into a high-speed link, providing protection for services when one of the low-speed ATM
links fail.
Definition
Specifically, the IMA technology provides inverse multiplexing of an ATM cell stream over
multiple low-speed links and retrieves the original stream at the far-end from these physical
links.
Figure 5-1 IMA
IMA group
IMA group
PHY
PHY
Link 0
PHY
PHY
Link 1
PHY
Link 2
PHY
TRUNK link
ATM layer cells
The IMA technology helps to group multiple physical links to form a higher bandwidth logical
link whose rate is approximately the sum of the link rates. When the member links in the IMA
group are dynamically added/deleted, or fail/recover, the logical link changes only in bandwidth.
The services on the logical link are not interrupted only if the bandwidth of the logical link is
not lower than the required minimum bandwidth.
When a link in an IMA group fails, the cells carried by the link are distributed to other normal
links. In this manner, the IMA services are protected.
Purpose
With the IMA technology, the transport network can transmit ATM services from customer
equipment on an IMA group formed by multiple low-speed links (for example, the three E1 links
shown in Figure 5-2), therefore increasing link bandwidth and providing link protection.
Issue 03 (2012-11-30)

141
OptiX OSN 7500 II/7500/3500/1500

5 IMA
Figure 5-2 Typical application of the IMA technology
IMA group
E1 link
NodeB
Packet
transmission equipment
5.2 Basic Concepts

This section describes the basic concepts associated with IMA.
5.2.1 IMA Protocol Reference Model

To implement the IMA technology, the ATM protocol reference model defines an IMA sublayer
between the transmission convergence (TC) sublayer and the ATM layer.
Figure 5-3 provides the positions and functions of the IMA sublayer in the ATM protocol
reference model.
Figure 5-3 IMA protocol reference model
User plane functions
Control plane functions
Management plane
functions
ATM
layer
IMA specific
TC sublayer
Physical
layer
ATM cell stream splitting and

reconstruction
ICP cell insertion/removal
Cell rate decoupling
IMA frame synchronization
Stuffing
Discarding of cells with bad HEC
IMA connectivity
ICP cell errors (OIF)
LIF/LODS/RDI-IMA defect
processing
RDI-IMA alarm generation
Tx/Rx IMA link state report
IMA group configuration

Link addition/deletion
ATM cell rate change
IMA group failure
notification
IMA statistics
Interface
specific TC
sublayer
Physical
medium
dependent
sublayer
5.2.2 IMA OAM Cells

IMA OAM cells are transmitted at the ATM physical layer. By processing IMA OAM cells, the
IMA sublayer provides inverse multiplexing for ATM. Two IMA OAM cells are defined: filler
cells and IMA control protocol (ICP) cells.
Issue 03 (2012-11-30)

142
OptiX OSN 7500 II/7500/3500/1500

5 IMA
Filler Cell
Filler cells are used to stuff IMA frames when no ATM cell arrives at the ATM layer.
Table 5-1 provides the format definition of the filler cell.
Table 5-1 Filler cell format
Octet
Label
Comment
1-5
ATM cell
header
Octet 1 = 00000000, octet 2 = 00000000, octet 3 =

00000000, octet 4 = 00000001, octet 5 = valid HEC
OAM label
IMA version value

l 00000001: version 1.0
l 00000011: version 1.1
Cell ID
Bit 7: IMA OAM cell type (0: filler cell; 1: ICP cell)
Link ID
Bits 6-0: unused and set to 0
8-51
Unused
Set to 0x6A as defined in ITU-T I.432 for unused bytes
52-53
CRC error
control
Bits 15-10: reserved for future use and set to 0

Bits 9-0: CRC-10 as specified in ITU-T I.610
ICP Cell
ICP cells are used to communicate information for setting up the IMA protocol between two
IMA units.
Table 5-2 provides the format definition of the ICP cell.
Table 5-2 ICP cell format
Octet
Label
Comment
1-5
ATM cell
header
Octet 1 = 00000000, octet 2 = 00000000, octet 3 =

00000000, octet 4 = 00000001, octet 5 = valid HEC
OAM label
IMA version value

l 00000001: version 1.0
l 00000011: version 1.1
Cell ID
Bit 7: IMA OAM cell type (1: ICP cell; 0: filler cell)
Link ID

Bits 4-0: logical ID for physical link range
Issue 03 (2012-11-30)
IMA frame
sequence
number (IFSN)
0 to 255 and cycling

143
OptiX OSN 7500 II/7500/3500/1500

5 IMA
Octet
Label
Comment
ICP cell offset
Range: 0 to M-1
Indicates position of ICP cell within the IMA frame. M
indicates the length of the IMA frame.
10
Link stuff
indication
(LSI)

Bits 2-0: link stuffing indication
l 111 = no imminent stuff event
l 100 = stuff event in 4 ICP cell locations (optional)
l 001 = stuff event at the next ICP cell location
l 000 = one out of the 2 ICP cells comprising the stuff
event
11
Status and
control change
indication
(SCCI)
Bits 7-0: status change indication; 0 to 255 and cycling

(count to be incremented every change of octets 12-49)
12
IMA ID
Bits 7-0: IMA ID
13
IMA group
status and
control
Bits 7-4: IMA group state

l 0000 = start-up
l 0001 = start-up-ack
l 0010 = config-aborted - unsupported M
l 0011 = config-aborted - incompatible group symmetry
l 01XX = config-aborted - other reasons
l 1000 = insufficient-links
l 1001 = blocked
l 1010 = operational
l Others: reserved
Bits 3-2: IMA group symmetry mode
l 00 = symmetrical configuration and operation
l 01 = symmetrical configuration and asymmetrical
operation (optional)
l 10 = asymmetrical configuration and asymmetrical
operation (optional)
l 11 = reserved
Bits 1-0: IMA frame length (M)
l 00: M = 32
l 01: M = 64
l 10: M = 128
l 11: M = 256
Issue 03 (2012-11-30)

144
OptiX OSN 7500 II/7500/3500/1500

5 IMA
Octet
Label
Comment
14
Transmit
timing
information
Tx test control
Bit 5: test link command (0: inactive; l: active)
15
Bit 5: transmit clock mode (0: ITC mode; 1: CTC mode)

Bits 4-0: Tx LID of the timing reference (0 to 31)
Bits 4-0: Tx LID of test link (0 to 31)

16
Tx test pattern
Bits 7-0: Tx test pattern (0 to 255)
17
Rx test pattern
Bits 7-0: Rx test pattern (0 to 255)
18
Link 0
information
Bits 7-5: transmit state

Bits 4-2: receive state
Bits 1-0: Rx defect indicators
19-49
Link 1-31
information
Status and control of link with LID in the range 1-31
50
Unused
Set to 0x6A as defined in ITU-T I.432 for unused bytes
51
End-to-end
channel
Proprietary channel (set to 0 if unused)
52-53
CRC error
control
Bits 15-10: reserved for future use and set to 0

Bits 9-0: CRC-10 as specified in ITU-T I.610
5.2.3 IMA Frame Format

To retrieve the original ATM cell stream from links with differential delays, the receive end
needs to receive ATM cells according to the IMA frame format.
IMA Frame
The IMA frame is used as the unit of control in the IMA protocol. An IMA frame is defined as
M consecutive cells (numbered 0 to M-1) on each link, across the linksa in an IMA group. M is
called the length of an IMA frame.
NOTE
a: "Across the links" in an IMA group is the same as the mechanism in which the transmit end distributes cells
from link to link within an IMA group. That is, ATM cells are placed on each link in a circulating manner.
One of the M cells on each link within an IMA group is an ICP cell; that is, the ICP cell is sent
once on each link per IMA frame. The ICP cell may be at different positions on different links.
In addition to ICP cells, each IMA frame has filler cells and ATM layer cells. The filler cells
are used to fill IMA frames when no ATM cell is received, and are discarded at the receive end.
The IFSN field in the ICP cell, indicating the sequence number of the IMA frame, increments
from 0 to 255 and repeats the sequence. Within an IMA frame period, the ICP cells on all the
links have the same IFSN value.
Issue 03 (2012-11-30)

145
OptiX OSN 7500 II/7500/3500/1500

5 IMA
Figure 5-4 shows an example of the transmission of IMA frames over three links in an IMA
group. In IMA frame 0, the IFSN of the ICP cell is 0; in IMA frame 1, the IFSN of the ICP cell
is 1; in IMA frame 2, the IFSN of the ICP cell is 2.
Figure 5-4 Transmission of IMA frames over three links in an IMA group
IMA frame 2
ATM
M-1
... ATM ATM

2
IMA frame 1
F
ICP2
M-1
... ICP2 ATM
... ATM ATM ICP2
...
IMA frame 0
ATM
ICP1 ATM
0
M-1
ATM
... ICP1 ATM ATM ATM ATM
ATM
...
...
ATM ICP1 ATM ATM
ATM
ICP0
... ICP0 ATM
...
ATM ICP0 ATM
Link 0
Link 1
Link 2
Time
ICP1
F
ATM
1# ICP cell
Filler cell
ATM layer cell
ICP Cell Offset

The ICP cell may be located anywhere on the links of each IMA frame. Therefore, the ICP cell
offset (of any value from 0 to M-1) is defined to indicate the position of an ICP cell on each link
within an IMA frame period.
An ICP cell offset of 0 means that the ICP cell is the first cell of the IMA frame on a particular
link. An ICP cell offset of M-1 means that the ICP cell is the last cell of the IMA frame on that
link. In Figure 5-4, the ICP cell offset on link 0 is 0 and the ICP cell offset on link 1 is 3. It
should be noted that all the IMA frames should have the same ICP cell offset on the same link,
which means that the IMA group needs to transmit cells in the same IMA frame format.
The IMA transmit end may distribute the ICP cells, from link to link, within the IMA group.
Uniform distribution of the ICP cells in the IMA frame allows in-time insertion of ATM cells.
Link Differential Delay Compensation

The delay of each link in the IMA group is different (differential delay), so compensation must
be performed at the receive end. The principle of the link differential delay compensation is
using the buffer mechanism for compensation as the ICP cell offset of each link is fixed. Figure
5-5 shows the methods of compensating for the link differential delay.
l
The transmit end allocates the ICP cell offsets of 1, 0, and 2 to links 0, 1, and 2 respectively.
During transmission, link 0 and link 2 have the same amount of propagation delay but link
1 has a delay one cell time longer than link 0 and link 2.
Issue 03 (2012-11-30)

146
OptiX OSN 7500 II/7500/3500/1500

5 IMA
At the receive end, the cells from each link enter the delay compensation buffer (DCB). In
the DCB, the ICP cell of each link obtains its offset based on the IMA frame header. In this
manner, the entire IMA frame is aligned. In this example, the offset of ICP1 is 0. Therefore,
ICP1 in the DCB is moved to the frame header so that the entire IMA frame is aligned.
Figure 5-5 Link differential delay compensation

Receive end
Transmit end
...
ICP0
...
ICP0
...
ICP0
...
ICP
1
...
ICP2
Link 0
...
ICP1
...
ICP1
Link 1
Delay
...
ICP2
...
ICP2
2
Link 2
t4
t3
t2
t1
Delay compensation buffer
Time
Maximum Link Differential Delay Tolerance

At the receive end, the DCB length required by the link differential delay compensation is
determined by the maximum link differential delay. The greater the maximum link differential
delay, the larger is the DCB. However, the larger the DCB, the greater is the transmission delay
of the entire IMA group. In addition, service transmission may be affected. To solve the problem,
you can set the Maximum Link Differential Delay Tolerance parameter. If the IMA group
detects a member link is beyond the specified value of that parameter, it automatically deactivates
the link. In this manner, the transmission delay of the entire IMA group is under control.
5.2.4 IMA Timing

For synchronization between links of an IMA group, the IMA group needs to adjust cell transmit
rates on the links according to the timing information. Two IMA timing configuration modes
are available: common transmit clock (CTC) configuration and independent transmit clock (ITC)
configuration.
The ITC configuration mode is used when the transmit clock on each link of an IMA group is
independently derived from a clock source. In this mode, at least one of switches Sw (0) to Sw
(N-l), as shown in the IMA timing configuration reference model in Figure 5-6, is set to position
"1". That is, the transmit clock of a member link is the receive clock of the link. In this manner,
the transmit end considers the clock as the reference to adjust the transmission frequency of filler
cells on the other links. Thus, rate matching is achieved to minimize the differential delay
between links.
The CTC configuration mode is used when the same clock is used for all the links of an IMA
group. In this mode, switches Sw (0) to Sw (N-l), as shown in the IMA timing configuration
reference model in Figure 5-6, are set to position "0". That is, the transmission clocks of the
Issue 03 (2012-11-30)

147
OptiX OSN 7500 II/7500/3500/1500

5 IMA
member links are co-sourced. In this manner, the transmit end triggers a filler event to match
the rate of each link with a fixed interval of 2048 ATM cells.
Figure 5-6 IMA timing configuration reference model
Tx clock unit
Local oscillator
Sw
External source
Sw (0)
Tx
Rx
Sw (1)
Tx
Rx
0
Link 0
. . .
Link 1
...
Sw (N-1)
Tx
0
1
Rx
Link N-1

This section describes the standards and protocols associated with IMA.
The following standard is associated with IMA:
The ATM Forum Technical Committee: Inverse Multiplexing for ATM (IMA) Specification
Version 1.1 AF-PHY-0086.001
5.4 Availability
The IMA function requires the support of the applicable equipment, boards, and software.
Version Support
Issue 03 (2012-11-30)
Applicable Version
OptiX OSN 7500 II
U2000

148
OptiX OSN 7500 II/7500/3500/1500

5 IMA
Applicable Version
OptiX OSN 3500/7500
U2000
V100R005 and later
Hardware Support
Applicable Board
Applicable Version
TNN1D75E
OptiX OSN 7500 II
TNN1D12E
OptiX OSN 7500 II
N1MD12
OptiX OSN 3500/7500
N1MD75
OptiX OSN 3500/7500

This section describes the limitations on and precautions for IMA in the network design phase,

Applicable
Object

Details
Remarks
IMA
l Create an IMA group if multiple

E1s are used to transmit ATM
services between a PE and a CE.
l Create an IMA group if some

timeslots of multiple E1s are
between a PE and a CE. All
member ports of an IMA group
must bind the same number of
timeslots and the number cannot
be smaller than three.
l The IMA group is not
recommended if only one E1 or
some timeslots of only one E1
are used to transmit ATM
services between a PE and a CE.
In this scenario, the IMA
function helps little to the
transmission but increases delay
of services.
Issue 03 (2012-11-30)

149
OptiX OSN 7500 II/7500/3500/1500

5 IMA
Applicable
Object

Details
Remarks
IMA
The enabling status and parameter

settings of the IMA function must be
the same on the PE and the CE.
IMA group
l It is recommended that you set

the IMA group negotiation mode
to symmetrical mode and
symmetrical operation.
l It is recommended that you set

the clock mode to CTC.
l Specify the minimum number of
links in the receive direction and
transmit direction in one IMA
group based on the required
minimum service bandwidth. If
the number of activated links is
less than the specified minimum
value, the IMA group will fail to
work properly.
l Make sure that protocol versions
of IMA ports on the source and
sink NEs are the same.
Otherwise, the IMA group will
fail to work properly. IMA
protocol V1.1 is recommended if
it is supported by the opposite
equipment.
IMA group
Members in one IMA group must be

on the same board and the same area.
(Links 1-16 and links 17-32 belong
to two areas; links in one IMA group
must be in the same area.)
IMA
symmetric
mode
N1MD75/N1MD12 supports only
symmetrical mode and symmetrical
operation.

None.
None.
Issue 03 (2012-11-30)

150
OptiX OSN 7500 II/7500/3500/1500

5 IMA
5.6 Principles
This section describes the principles of the IMA feature.
Figure 5-7 shows the processing of an ATM cell stream in the IMA technology.
l
The IMA transmitter sends the ATM user cells and ICP cells from the ATM layer to the
active member links within an IMA group. When the ATM user cells need to be transmitted
but no cell is received from the ATM layer, filler cells are transmitted to maintain a
continuous stream of IMA cells.
The IMA receiver retrieves the original ATM cell stream by using the link differential delay
compensation technique and then transmits the ATM cell stream to the ATM layer.
When a member link in the IMA group is faulty, the transmitter and receiver transmit the
new IMA frame wherein the member link is removed. In this manner, link protection is
achieved.
Figure 5-7 Processing of an ATM cell stream in the IMA technology

IMA group
IMA group
PHY
PHY
Link 0
PHY
PHY
Link 1
PHY
Link 2
PHY
TRUNK link
ATM layer cells
5.7 Configuration Procedure

On an Hybrid MSTP equipment, an ATM trunk is used to describe an IMA group. Therefore,
the key to configuring IMA is to configuring an ATM trunk.
Table 5-3 provides the procedure for configuring IMA.
Issue 03 (2012-11-30)

151
OptiX OSN 7500 II/7500/3500/1500

5 IMA
Table 5-3 Procedure for configuring IMA

St
ep
Operation
Description
Binding ATM TRUNKs
Required.
l For ATM/IMA services, set Level to E1. For
Fractional E1 services, set Level to Fractional
E1.
l Set the other parameters according to the
planning information.
NOTE
When the E1 frame mode is PCM 30, timeslot 16 cannot
be bound.
Configuring an IMA Group
Required.
l For an ATM trunk requiring the IMA function,
set IMA Protocol Enable Status to
Enabled.
l Set Clock Mode of the local NE and the NE
at the opposite end of the IMA trunk to be the
same as Clock Mode of the interconnected
NodeB.
l The other parameters are only valid for IMA
E1 and Fractional IMA. The parameters at
both ends of an IMA link must be set to the
same, which are recommended to set to default
values.
Configuring ATM Interface

Management Attributes
Optional.
l It is recommended that you set Port Type and
ATM Cell Payload Scrambling by default
based on the type of access equipment. The
parameter values must be the same for both
ends of a link.
l The other parameters take the default values.
5.8 Configuring IMA

This topic describes the IMA configuration tasks.
5.8.1 Binding ATM TRUNKs

An ATM TRUNK can bind one or more E1 ports that transmit ATM/IMA services, or serial
ports (SPs) that transmit ATM/IMA services.
Prerequisites
l
Issue 03 (2012-11-30)
You must be an NM user with NE administrator authority or higher.

152
OptiX OSN 7500 II/7500/3500/1500

5 IMA
For IMA E1 ports, set Port Mode in PDH Interface to Layer 2.
For Fractional ATM/IMA ports, set Port Mode in PDH Interface to Layer 1 and configure
serial port parameters.
Context
NOTE
Only the E1 ports or the serial ports on the same processing board can be bound.
Procedure
Step 1 In the NE Explorer, select the NE from the Object Tree.
Step 2 Choose Configuration > Packet Configuration > Interface Management > ATM IMA
Management from the Function Tree.
Step 3 Click the Binding tab.
Step 4 Click Configuration.
Step 5 The Bound Path dialog box is displayed. Configure the related parameters according to planning
information. Then, click
to bind the required E1 ports or SPs to the ATM TRUNK.
NOTE
l If ATM/IMA services need to be mapped into the ATM TRUNK that binds one or more E1 ports, select
E1 in Level.
l If ATM/IMA services need to be mapped into the ATM TRUNK that binds one or more serial ports,
select Fractional E1 in Level.
Step 6 Click Apply, and then close the dialog box that is displayed.
----End
Follow-up Procedure
If the IMA group is required, you need to bind the member links of the IMA group with the
ATM TRUNK, enable the IMA protocol for the ATM TRUNK, and then configure the
parameters of the IMA group.
Issue 03 (2012-11-30)

153
OptiX OSN 7500 II/7500/3500/1500

5 IMA
5.8.2 Configuring an IMA Group

If the ATM TRUNK binds IMA E1 links or Fractional IMA links, you need to configure the
parameters of the IMA group.
Prerequisites
l
Procedure
Step 3 Click the IMA Group Management tab.
Step 4 Optional: Select a ATM trunk. The services associated with the ATM trunk are displayed in
the lower pane.
Step 5 Configure the parameters of the IMA Group Management tab according to planning
information.
Step 6 Click Apply, and then close the dialog box that is displayed.
Step 7 Optional: Click Reset, can reset an IMA group to re-enable the IMA group protocol.
----End
5.8.3 Configuring ATM Interface Management Attributes

This topic describes how to configure ATM port management attributes.
Prerequisites
l
Procedure
Step 3 Click the ATM Interface Management tab.
Step 4 Configure the ATM Interface Management attributes.
Issue 03 (2012-11-30)

154
OptiX OSN 7500 II/7500/3500/1500

5 IMA
Step 5 Click Apply, and close the dialog box that is displayed.
----End
5.8.4 Querying Running Status of an IMA Group

In the case of routine maintenance and troubleshooting, the operator need query information on
states of an IMA group to check whether the IMA group is normal.
Prerequisites
l
Procedure
Step 3 Click the IMA Group States tab.Then, close the dialog box that is displayed.
Step 4 Click Query, and then close the dialog box that is displayed.
Step 5 Query the running status of an IMA group.
----End
5.8.5 Querying Link Running Status of an IMA Group

In the case of routine maintenance and troubleshooting, the operator need query information on
states of an IMA link to check whether the IMA link is normal.
Prerequisites
l
Procedure
Step 3 Click the IMA Link States tab.Then, close the dialog box that is displayed.
Step 4 Click Query, and then close the dialog box that is displayed.
Step 5 Query the running status of the member links of an IMA group.
----End
Issue 03 (2012-11-30)

155
OptiX OSN 7500 II/7500/3500/1500

5 IMA
5.8.6 Resetting an IMA Group

In the case of deployment and troubleshooting, can reset an IMA group to re-enable the IMA
group protocol.
Prerequisites
l
You must complete the creation of the IMA group.
Procedure
Step 3 Click the IMA Group Management tab and select the IMA group.
Step 4 Select a ATM trunk.
Step 5 Click Reset, and close the dialog box that is displayed.
----End
5.8.7 Modifying an IMA Group

When attributes of an IMA group displayed on the U2000 are not consistent with those in the
network, modify attributes of this IMA group. If any service is configured and activated at the
ATM Trunk port for an IMA group, modification of the IMA group may interrupt services.
Prerequisites
l
You must complete the creation of the IMA group.
Context
CAUTION
If any service is configured and activated at the ATM Trunk port for the IMA group, modification
of the IMA group may interrupt services. Exercise caution for this.
Procedure
Step 3 Click the IMA Group Management tab.
Issue 03 (2012-11-30)

156
OptiX OSN 7500 II/7500/3500/1500

5 IMA
Step 4 Configure the parameters of the IMA Group Management tab according to planning
information.
Step 5 Click Apply, and close the dialog box that is displayed.
----End
5.8.8 Deleting an IMA Group

Delete the redundant or idle IMA groups to release the resources. If any service is configured
and activated at the ATM Trunk port for an IMA group, deleting the IMA group may interrupt
the services.
Prerequisites
l
The IMA Protocol Enable Status of the IMA group must be Disabled.
The IMA group cannot be used by ATM service.
Context
CAUTION
If any service is configured and activated at the ATM Trunk port for the IMA group, deleting
the IMA group may interrupt the services. Exercise caution for this.
Procedure
Step 3 Click the Banding tab.
Step 4 Select an IMA group. Click Delete, and close the dialog box that is displayed.
----End

This section uses an example to describe how to plan and configure IMA according to network
conditions.
5.9.1 Network Diagram

This section describes the hybrid MSTP equipment receives ATM services from the NodeB.
As shown in Figure 5-8, NE1 receives ATM services from the NodeB. The IMA group binds
three E1 links to transmit services from the NodeB. IMA 1 connects to port 1 to port 3 on an
N1D12E board. NE1 has been configured with E1 port parameters based on E1 link conditions.
Issue 03 (2012-11-30)

157
OptiX OSN 7500 II/7500/3500/1500

5 IMA
Figure 5-8 Network diagram of IMA

IMA1
NodeB
NE1
5.9.2 Service Planning

The service planning information contains all the parameters required for configuring the NE
data.
Table 5-4 lists the bound paths in the ATM TRUNK planned for NE1.
Table 5-4 Bound paths in the ATM TRUNK planned for NE1
Attribute
Description
Available Boards
35-N1D12E
Configuration Ports
35-N1D12E-1(Trunk-1)
Level
E1
Direction
Bidirectional
Available Resources
35-N1D12E-1(PORT-1), 35-N1D12E-2
(PORT-2), 35-N1D12E-3(PORT-3)
Table 5-5 lists the IMA group management parameters planned for NE1.
Table 5-5 IMA group management parameters planned for NE1
Issue 03 (2012-11-30)
Attribute
Description
IMA Protocol Enable Status
Enabled
Minimum Number of Active Transmitting

Links
Minimum Number of Active Receiving Links
IMA Protocol Version
1.1
IMA Transmit Frame Length
128
IMA Symmetry Mode
Symmetrical Mode and Symmetrical

Operation
Maximum Delay Between Links (ms)
25
Clock Mode
CTC Mode
158
OptiX OSN 7500 II/7500/3500/1500

5 IMA
Table 5-6 lists the ATM interface parameters planned for NE1.
Table 5-6 ATM interface parameters planned for NE1
Attribute
Description
Name
conn_nodeb_trunk1
Port Type
UNI
ATM Cell Payload Scrambling
Enabled

Prerequisites
l
For IMA E1 ports, set Port Mode in PDH Interface to Layer 2.
You must understand the networking, requirements and service planning of the example.
Procedure
Step 1 In the NE Explorer, select the NE1 from the Object Tree.
Step 3 Bind ATM TRUNKs.
1.
Click the Binding tab.
2.
Click Configuration.
3.
The Bound Path dialog box is displayed. Configure the related parameters according to
planning information. Then, click
ATM TRUNK.
Issue 03 (2012-11-30)
to bind the required E1 ports or SPs to the
Attribute
Description
Available Boards
35-N1D12E
Configuration Ports
35-N1D12E-1(Trunk-1)
Level
E1
Direction
Bidirectional
Available Resources
35-N1D12E-1(PORT-1), 35-N1D12E-2
(PORT-2), 35-N1D12E-3(PORT-3)

159
OptiX OSN 7500 II/7500/3500/1500

4.
5 IMA
Click Apply, and then close the dialog box that is displayed.
Step 4 Configure an IMA group.

1.
Click the IMA Group Management tab.
2.
Configure the parameters of the IMA Group Management tab according to planning
information.
3.
Attribute
Description
IMA Protocol Enable Status
Enabled
Minimum Number of Active Transmitting

Links
Minimum Number of Active Receiving

Links
IMA Protocol Version
1.1
IMA Transmit Frame Length
128
IMA Symmetry Mode

Operation
Maximum Delay Between Links (ms)
25
Clock Mode
CTC Mode
Click Apply, and then close the dialog box that is displayed.
Step 5 Configure ATM Interface Management Attributes.

1.
Click the ATM Interface Management tab.
2.
Configure the ATM Interface Management attributes.
3.
Attribute
Description
Name
conn_nodeb_trunk1
Port Type
UNI
ATM Cell Payload Scrambling
Enabled
Click Apply, and close the dialog box that is displayed.
----End

This topic describes the alarms and performance events that are related to the IMA feature.

This topic describes the alarms related to IMA.
Issue 03 (2012-11-30)

160
OptiX OSN 7500 II/7500/3500/1500

5 IMA
Table 5-7 lists the alarms that are related to the IMA.
Table 5-7 Alarms related to IMA
Issue 03 (2012-11-30)
Alarm Name
Meaning
IMA_GROUP_RE_DO
WN
The IMA_GROUP_RE_DOWN is an alarm indicating that the

IMA group fails at the remote end.
IMA_GROUP_LE_DO
WN
The IMA_GROUP_LE_DOWN is an alarm indicating that the

IMA group fails at the local end.
ALM_IMA_LINK_LC
D
The ALM_IMA_LINK_LCD is an alarm indicating the loss of

cell delimitation in the IMA link. This alarm shows the failure of
delimitating the cells received in the local IMA link.
ALM_IMA_LODS
The ALM_IMA_LODS is an alarm indicating that the differential

delay of the IMA link crosses the threshold. This alarm occurs
when the maximum differential delay on the IMA link at the local
end crosses the threshold.
IMA_TXCLK_MISMATCH
The IMA_TXCLK_MISMATCH is an alarm indicating that the

transmit clock modes at the two ends of the IMA group are
different.
ALM_IMA_RFI
The ALM_IMA_RFI is an alarm indicating that the frame

delimitation is out-of-frame at the remote end of the IMA group.
This alarm occurs when the frame delimitation is out-of-frame at
the remote end of the IMA group.
ALM_IMA_LIF
The ALM_IMA_LIF is an alarm indicating that the frame

delimitation is out-of-frame at the local end of the IMA link. This
alarm occurs when the frame delimitation is out-of-frame at the
local end of the IMA link.
ALM_IMA_RE_RX_U
NUSABLE
The ALM_IMA_RE_RX_UNUSABLE is an alarm indicating

that the IMA link on the opposite NE fails in the receive direction.
This alarm occurs when the IMA link on the opposite NE works
incorrectly in the receive direction.
ALM_IMA_RE_TX_U
NUSABLE
The ALM_IMA_RE_TX_UNUSABLE is an alarm indicating

that the IMA link on the opposite NE fails in the transmit direction.
This alarm occurs when the IMA link on the opposite NE works
incorrectly in the transmit direction.
LFA
The LFA is an alarm indicating the loss of E1 basic frame

alignment. This alarm shows the failure of delimitating the frames
received in the local IMA link.
ALM_E1AIS
The ALM_E1AIS is an alarm indication signal in the E1 link. This

alarm shows that the payload in the E1 link is all "1"s.

161
OptiX OSN 7500 II/7500/3500/1500

5 IMA
Alarm Name
Meaning
LMFA
The LMFA is an alarm indicating the loss of multiframe

alignment. This alarm shows the failure of delimitating the CRC-4
multiframes received in the local IMA link. The local end expects
to receive the CRC-4 multiframes, but it actually receives the
basic frames. In this case, the LMFA alarm is reported.

None.

This topic describes the parameters required for configuring IMA.
5.11.1 Configuring Bound Paths

This section describes the parameters for configuring bound paths.
Table 5-8 lists the parameters for configuring bound paths.
Table 5-8 Parameters for configuring bound paths
Field
Value
Description
Available
Boards
Slot ID-board name
Specifies the available boards.
For example: 29-N1D12E

information.
Configuratio
n Ports
Slot ID-board nameTrunk ID (Trunk-Trunk

ID)
Specifies the logical ports for carrying ATM

services on the available boards.
For example: 29N1D12E-1(Trunk-1)
l For ATM/IMA E1 services, set Port Mode

in PDH Interface to Layer 2.
l For Fractional ATM/IMA services, set Port
Mode in PDH Interface to Layer 1 and set
serial port parameters.
information.
Issue 03 (2012-11-30)

162
OptiX OSN 7500 II/7500/3500/1500

5 IMA
Field
Value
Description
Level
E1, Fractional E1
Specifies the level of bound paths.
Default: E1
l If ATM/IMA services need to be mapped into

the ATM TRUNK that binds one or more E1
ports, select E1 in Level.
l If ATM/IMA services need to be mapped into
the ATM TRUNK that binds one or more
serial ports, select Fractional E1 in Level.
information.
Direction
Bidirectional
Displays the direction of the bound paths. The

fixed value is Bidirectional.
If this parameter is set to Bidirectional, the
transmit and receive directions of the physical
paths are bound in the ATM TRUNK.
Optical
Interface
Hybrid MSTP equipment does not support this

parameter.
Available
Resources
l For bound paths of

E1 level,
Displays the ports that carry the available paths

for IMA services.
Slot ID-board nameport ID (PORT-port

ID)
For example, 29N1D12E-1(PORT-1)
l For bound paths of
Fractional E1 level,
Slot ID-board nameport ID (Serial-Serial
ID)
For example, 29N1D12E-1(Serial-1)
Available
Timeslots
Hybrid MSTP equipment does not support this

parameter.
Selected
Bound Paths
Displays the configured bound paths.
Display in
Combination
Selected, Not selected
Specifies whether to display selected bound

paths in combination.
Default: Selected

information.
Issue 03 (2012-11-30)

163
OptiX OSN 7500 II/7500/3500/1500

5 IMA
Field
Value
Description
VCTRUNK

ID)
Displays the ATM TRUNK that is the logical

port on the board for carrying ATM services.

Level
E1, Fractional E1
Displays the level of bound paths.
Bound Paths
Slot ID-board name-(port

ID-port ID)
Displays the bound physical paths in the ATM

TRUNK.
For example, 29N1D12E-1(1-2)

Bound Path
Count
Example: 4
Displays the number of bound paths.

NOTE
Bound Path Count displays the number of
unidirectional bound paths. For examples, if two E1
ports are bound, Bound Path Count is 4.
5.11.2 IMA Group Management

This section describes the parameters for configuring the management of an IMA group.
Table 5-9 and Table 5-10 list the parameters for configuring the management of an IMA group.
Table 5-9 Parameters for configuring the management of an IMA group
Field
Value
Description
VCTRUNK

ID)
Specifies the ATM TRUNK that is the logical


IMA
Protocol
Enable
Status
Enabled, Disabled
Specifies the IMA protocol enable status.
Default: Disabled
l Set IMA Protocol Enable Status to

Enabled if the links bound with the ATM
TRUNK require the IMA protocol;
otherwise, set this parameter to Disabled.
l After IMA Protocol Enable Status is set to
Enabled, the E1 links or Fractional E1
timeslots bound in the ATM TRUNK start
running the IMA protocol.
Issue 03 (2012-11-30)

164
OptiX OSN 7500 II/7500/3500/1500

5 IMA
Field
Value
Description
Minimum
Number of
Active
Transmitting
Links
1-16
The Minimum Number of Active

Transmitting Links parameter specifies the
lower threshold of active links in the transmit
direction in an inverse multiplexing for ATM
(IMA) group to maintain proper operation of the
IMA group.
Default: 1
l The links of the IMA group can carry services

only when the number of activated links in
the transmit/receive direction is not smaller
than the value of Minimum Number of
Active Transmitting Links/Minimum
Number of Active Receiving Links.
l The values of Minimum Number of Active
Transmitting Links and Minimum
Number of Active Receiving Links must be
the same because the N1D12E/N1D75E
supports Symmetrical Mode and
Symmetrical Operation only. The
parameters Minimum Number of Active
Number of Active Receiving Links must
IMA link.
l The default value is recommended.
For details, see A.13.4 Minimum Number of
Active Transmitting Links(IMA Group
Management).
Issue 03 (2012-11-30)

165
OptiX OSN 7500 II/7500/3500/1500

5 IMA
Field
Value
Description
Minimum
Number of
Active
Receiving
Links
1-16
The Minimum Number of Active Receiving

Links parameter specifies the lower threshold of
active links in the receive direction in an inverse
multiplexing for ATM (IMA) group to maintain
proper operation of the IMA group.
Default: 1
l The links of the IMA group can carry services

only when the number of activated links in
the transmit/receive direction is not smaller
than the value of Minimum Number of
Active Transmitting Links/Minimum
Number of Active Receiving Links.
l The values of Minimum Number of Active
Number of Active Receiving Links must be
the same because the N1D12E/N1D75E
supports Symmetrical Mode and
Symmetrical Operation only. The
parameters Minimum Number of Active
Number of Active Receiving Links must
IMA link.
For details, see A.13.5 Minimum Number of
Active Receiving Links(IMA Group
Management).
IMA
Protocol
Version
1.0, 1.1
Specifies the IMA protocol version.
Default: 1.1
l The parameter IMA Protocol Version must

IMA link.
Issue 03 (2012-11-30)

166
OptiX OSN 7500 II/7500/3500/1500

5 IMA
Field
Value
Description
IMA Transit
Frame
Length
32, 64, 128, 256
The IMA Transit Frame Length parameter

specifies the length of an inverse multiplexing
for ATM (IMA) frame transmitted by the
equipment at the local end. That is, this
parameter specifies the number of asynchronous
transfer mode (ATM) cells in an IAM frame.
Default: 128
l Based on the IMA frame format, the receive

end rebuilds the ATM cell stream with the
cells arriving from diversely-delayed links.
Longer IMA frames result in higher
transmission efficiency and occupy more
resources. Once a member link fails, the
impact on the entire IMA group increases as
the length of IMA frames increases.
l The parameter IMA Transmit Frame
Length must assume the same value on the
two ends of an IMA link.
For details, see A.13.1 IMA Transit Frame
Length.
IMA
Symmetry
Mode
Symmetrical Mode and

Symmetrical Operation,
Asymmetrical Operation,
Asymmetrical Mode and
Asymmetrical Operation
Default: Symmetrical
Mode and Symmetrical
Operation
The IMA Symmetry Mode parameter specifies

the configuration and operation mode of inverse
multiplexing for ATM (IMA) links in an IMA
group.
l The N1D12E/N1D75E supports
Operation only.
l If the symmetrical mode and symmetrical
operation are adopted, the bandwidth of the
IMA group is always consistent in the
transmit direction and in the receive
direction, even when some member links fail.
In symmetrical mode:
Bandwidth of the IMA group = min
{bandwidth in the transmit direction,
bandwidth in the receive direction}
The unidirectional failure of one member
link is equivalent to the bidirectional
failure of one member link.
For details, see A.13.2 IMA Symmetry Mode.
Issue 03 (2012-11-30)

167
OptiX OSN 7500 II/7500/3500/1500

5 IMA
Field
Value
Description
Maximum
Delay
Between
Links(ms)
1-120
The Maximum Delay Between Links(ms)

parameter specifies the maximum delay
tolerance between links in an inverse
multiplexing for ATM (IMA) group. That is, this
parameter specifies the allowed maximum
difference between the maximum delay value
and the minimum delay value of all links in an
IMA group. If the maximum difference exceeds
the specified value, the equipment reports the
lODS alarm for a link who has the largest offset
value compared with the average delay value of
all links in the MA group. Then, the equipment
removes the alarmed link from the IMA group.
Default: 25
l If this parameter is set to a value greater than

the allowed maximum value, the delay of
IMA services may be prolonged and even
packet loss may occur; if this parameter is set
to a value smaller than the allowed minimum
value, a working link will be deleted by
mistake.
l The parameter Maximum Delay Between
Links (ms) must assume the same value on
the two ends of an IMA link.
For details, see A.13.3 Maximum Delay
Between Links(ms)(IMA Group
Management).
Clock Mode
CTC Mode, ITC Mode

Default: CTC Mode
The Clock Mode parameter specifies the clock

mode for operations of an inverse multiplexing
for ATM (IMA) group.
l Clock Mode is set to the same value for the
interconnected ends of IMA links.
l Set this parameter according to the planning
information.
For details, see A.13.6 Clock Mode(IMA
Group Management).
Table 5-10 Parameters for an associated service

Field
Value
Service Type For example: ATM

service
Issue 03 (2012-11-30)
Description
Displays the type of the service associated with
the port.

168
OptiX OSN 7500 II/7500/3500/1500

5 IMA
Field
Value
Description
Service ID
For example: 20
Displays the ID of the service associated with the

port.
When you select the value of the service ID, the
active window changes to the service
management dialog box of the corresponding
service type.
Service
Name
For example: ATM
Displays the name of the service associated with

the port.
Used
Resource
Displays the resource used by the service

associated with the port.
5.11.3 ATM Port Management

This section describes the parameters for configuring the management of an ATM port.
Table 5-11 lists the parameters for configuring the management of an ATM port.
Table 5-11 Parameters for configuring the management of an ATM port
Field
Value
Description
Port

ID)
Displays the port that is the logical port on the

board for carrying ATM services.

Name
Example: Port 1
Displays or specifies the name of the port.
Port Type
UNI, NNI
Specifies the type of the ATM port.
Default: UNI.
l UNI: the port connecting user-side devices.

For example, the UNI port applies to the userside port on the common ATM network or to
the user-side port of the PE on the PSN
network that transmits ATM PWE3 services.
l NNI: the port connecting network-side
devices. For example, the NNI port applies to
the network-side port on the common ATM
network.
information.
Issue 03 (2012-11-30)

169
OptiX OSN 7500 II/7500/3500/1500

5 IMA
Field
Value
Description
ATM Cell
Payload
Scrambling
Enabled, Disabled
The ATM Cell Payload Scrambling (ATM

Interface Management) parameter specifies
whether to scramble the payload of cells on
asynchronous transfer mode (ATM) links.
Default: Enabled
l ITU-T G.804 stipulates that the payload (48

bytes) of ATM cells must be scrambled
before it is mapped into E1 signals.
Therefore, it is recommended that you set
ATM Cell Payload Scrambling to
Enabled for both end of an ATM link.
l ATM Cell Payload Scrambling must
ATM link. Otherwise, packet loss will occur.
For details, see A.12.1 ATM Cell Payload
Scrambling(ATM Interface Management).
Min. VPI
The N1D12E/N1D75E does not support this

parameter.
Max. VPI

parameter.
Min. VCI

parameter.
Max. VCI

parameter.
VCCSupported
VPI Count

parameter.
Loopback
No Loopback, Outloop,
Inloop
Specifies the loopback status of the port.
Default: No Loopback

information.
5.11.4 IMA Group Status

This section describes the parameters for IMA group status.
Table 5-12 lists the parameters for IMA group status.
Issue 03 (2012-11-30)

170
OptiX OSN 7500 II/7500/3500/1500

5 IMA
Table 5-12 Parameters for IMA group status

Field
Value
Description
VCTRUNK

ID)


Near-End
Group Status
Start-Up, Start-Up-ACK,
Config-Aborted,
Insufficient-Links,
Operational
Default: Start-Up
Far-End
Group Status
Start-Up, Start-Up-ACK,
Config-Aborted,
Insufficient-Links,
Operational
The Near-End Group Status parameter

displays the status of an inverse multiplexing for
ATM (IMA) group at the local end.
For details, see A.13.7 Near-End Group Status
(IMA Group Status).
Displays the status of the far-end IMA group.
The value of Far-End Group Status is the same
as that of Near-End Group Status.
Default: Start-Up
Transmit
Rate (cell/s)
Displays the cell transmit rate.
Receive Rate
(cell/s)
Displays the cell receive rate.
Number of
Transmit
Links
Displays the number of transmit links.
Number of
Receive
Links
Displays the number of receive links.
Number of
Activated
Transmit
Links
Displays the number of activated transmit links.
Number of
Activated
Receive
Links
Displays the number of activated receive links.
5.11.5 IMA Link Status

This section describes the parameters for IMA link status.
Table 5-13 lists the parameters for IMA link status.
Issue 03 (2012-11-30)

171
OptiX OSN 7500 II/7500/3500/1500

5 IMA
Table 5-13 Parameters for IMA link status

Field
Value
Description
VCTRUNK

ID)


E1 Link

ID (PORT-port ID)
Displays E1 links.
For example, 29N1D12E-1(PORT-1)

Differential
Delay Check
Status
Unknown, Valid, Invalid
Near-End
Receiving
Status
Not In Group, Unusable,

Usable, Active
Default: Unknown
The Differential Delay Check Status parameter

displays the result returned when you query the
statuses of inverse multiplexing for ATM (IMA)
links.
Displays the near-end receiving status.
l Not In Group: This state is displayed if a link
is not included in an IMA group.
l Unusable: This state is displayed when an
IMA link is added to an IMA group but the
IMA link is not available because of faultcaused or manual suppression.
l Usable: This state indicates that the link is
available and it is displayed when the link is
waiting for the remote receive link to be
activated. In this case, this link is not added
to the cyclical transmitting process of the
IMA group.
l Active: This state indicates that the link is
activated. If service cells are received, they
can be transmitted. This link is added to the
cyclical transmitting process of the IMA
group.
Issue 03 (2012-11-30)

172
OptiX OSN 7500 II/7500/3500/1500

5 IMA
Field
Value
Description
Near-End
Transmitting
Status

Usable, Active
Displays the near-end transmitting status.

IMA group.
group.
Far-End
Receiving
Status

Usable, Active
Displays the far-end receiving status.

IMA group.
group.
Issue 03 (2012-11-30)

173
OptiX OSN 7500 II/7500/3500/1500

5 IMA
Field
Value
Description
Far-End
Transmitting
Status

Usable, Active
Displays the far-end transmitting status.

IMA group.
group.
Issue 03 (2012-11-30)

174
OptiX OSN 7500 II/7500/3500/1500

6 ETH-OAM
ETH-OAM
About This Chapter

ETH-OAM detects and monitors the connectivity and performance of the service trail.
6.1 Introduction to ETH-OAM
With the continuous development of the Ethernet, especially when the network develops from
LAN to WAN, operators pay more attention to equipment maintainability. Solutions to
operations, administration, and maintenance (OAM) on the transmission network are required
urgently. Thus, ETH-OAM is developed. ETH-OAM enhances the Ethernet Layer 2
maintenance to strongly support the service continuity verification, service deployment
commissioning and network fault locating.
6.2 Ethernet Port OAM
Ethernet port OAM maintains point-to-point Ethernet links between directly-connected devices
by performing OAM auto-discovery, link performance monitoring, fault check, remote
loopback, and selfloop check.
6.3 Ethernet Service OAM
Ethernet service OAM focuses on Ethernet services and maintains end-to-end Ethernet links. It
implements sectional and segmental maintenance over service flows by specifying the
maintenance domain, maintenance association, and maintenance point.
Issue 03 (2012-11-30)

175
OptiX OSN 7500 II/7500/3500/1500

6 ETH-OAM
6.1 Introduction to ETH-OAM

With the continuous development of the Ethernet, especially when the network develops from
LAN to WAN, operators pay more attention to equipment maintainability. Solutions to
operations, administration, and maintenance (OAM) on the transmission network are required
urgently. Thus, ETH-OAM is developed. ETH-OAM enhances the Ethernet Layer 2
maintenance to strongly support the service continuity verification, service deployment
commissioning and network fault locating.
Definition
As a protocol based on the MAC layer, ETH-OAM checks Ethernet links by transmitting OAM
protocol packets. Compared with the transmission medium, this protocol is independent. The
OAM packets are processed only at the MAC layer, having no impact at other layers on the
Ethernet. Moreover, as a low-rate protocol, the ETH-OAM protocol occupies a low bandwidth.
Thus, this protocol does not affect services carried on the link.
Application
Figure 6-1 shows the application of Ethernet service OAM and Ethernet port OAM.
Figure 6-1 Application of Ethernet service OAM and Ethernet port OAM
Ethernet
Port OAM
Ethernet Service OAM
P
Router1
Ethernet
Port OAM
CE1
PE2
PE1
CE3
Router3
CE2
Custom
Network
Router2
Access
Network
Core
Network
CE4
Access
Network
Custom
Network
OptiX NE
The application of Ethernet service OAM is based on services. It realizes the end-to-end
Ethernet link maintenance on the basis of each maintenance domain.
The Ethernet port OAM application does not focus on the specific service, but focuses on
the end-to-end Ethernet link maintenance between two directly-connected equipment in
the first mile (EFM).
The Ethernet service between router 1 and router 3 involves NEs CE1, PE1, P, PE2, and CE3
in transmission.
Issue 03 (2012-11-30)

176
OptiX OSN 7500 II/7500/3500/1500

6 ETH-OAM
On the premise that router 1 supports the Ethernet port OAM protocol, Ethernet port OAM can
be used to test the end-to-end Ethernet link continuity and performance from client-side router
1 to NE CE1 at the access-layer.
Ethernet service OAM can be used to test the continuity and performance of end-to-end Ethernet
links where the service is carried from CE1 at the access layer and CE3.
In terms of the maintenance domain, Figure 6-1 shows two main application scenarios of
Ethernet service OAM.
l
Maintenance domain related to users at the access layer: MEPs are created on CE1 and
CE3 at two ends of the network, and MIPs are created on PE1 and PE2. In this manner, all
links where the customer services are carried on the entire Ethernet can be detected.
Maintenance domain related to operators at the core layer: MEPs are created on PE1 and
PE2. In this manner, the link quality on the access side can be ignored and the network of
carriers is focused on.
Purpose
Comparison between ETH-OAM and existing network maintenance and fault locating methods
is described as follows:
l
The current frame test method is based on only the encapsulation format where the data of
the same type is contained. Thus, this test method is not applicable to other encapsulation
formats (such as GFP encapsulation format and HDLC encapsulation format) where the
data of different types is contained.
The current port loopback function focuses on all packets at the port. Thus, the loopback
cannot be performed for a specific service selectively.
ETH-OAM can detect hardware faults.
ETH-OAM can detect and locate faults automatically.
6.2 Ethernet Port OAM

Ethernet port OAM maintains point-to-point Ethernet links between directly-connected devices
by performing OAM auto-discovery, link performance monitoring, fault check, remote
loopback, and selfloop check.

Ethernet port OAM focuses on maintenance of the end-to-end Ethernet link between two systems
that are connected directly. It does not focus on the specific services, but maintains the Ethernet
end-to-end link by using OAM auto-discovery, link performance monitoring, fault locating,
remote loopback, and selfloop test.
OAM Auto-Discovery
OAM auto-discovery is the first phase for running the Ethernet port OAM protocol. By
exchanging the information OAM protocol data unit (OAMPDU) periodically, equipment at two
ends inform each other of the capability that supports the Ethernet port OAM protocol.
OAM auto-discovery is a prerequisite to realize the link performance monitoring, fault locating,
and remote loopback.
Issue 03 (2012-11-30)

177
OptiX OSN 7500 II/7500/3500/1500

6 ETH-OAM
Link Performance Monitoring

Link performance monitoring is used to monitor the bit error performance (error frames or error
signals) of links. When bit errors cross the threshold, the event notification OAMPDU is used
to inform the remote OAM entities of bit error events.
Fault Locating
When faults (including link faults, dying gasps, and critical events) occur at the local end, the
local OAM entities transmit the OAMPDU where the fault information is contained to the remote
end. In this manner, the fault notification is realized.
Remote Loopback
By transmitting the loopback control OAMPDU to the remote OAM entity, the local OAM entity
applies for the loopback from the remote OAM entity.
In the loop mode, all packets, excluding OAMPDU packets, revert back to original routes. In
the case of equipment installation and troubleshooting, the remote loopback provides necessary
assistance.
Selfloop Test
Ethernet service processing boards enabled with the self-loop detection function can detect a
self-loop. In self-loop mode, a fiber from the transmit port is looped back to the receive port on
the same board.
When a self-loop is detected, an alarm is reported and ports where the self-loop occurs are
blocked.

This topic describes the standards and protocols that Ethernet port OAM complies with.
Ethernet port OAM complies with the following standards and protocols: IEEE 802.3ah Carrier
Sense Multiple Access with Collision Detection (CSMA/CD) Access Method and Physical
Layer Spectifications
6.2.3 Availability
The Ethernet port OAM function requires the support of the applicable equipment, boards, and
software.
Version Support
Issue 03 (2012-11-30)
Applicable Version
OptiX OSN 1500/3500
T2000
U2000

178
OptiX OSN 7500 II/7500/3500/1500

6 ETH-OAM
Applicable Version
OptiX OSN 7500
U2000
Applicable Version
OptiX OSN 7500 II
U2000
Hardware Support
Applicable
Board
Applicable Version
N1PEG16
OptiX OSN 3500
N1PEX1
OptiX OSN 3500
N1PETF8
OptiX OSN 3500: V100R009C03

and later
OptiX OSN 3500/7500

and later
Issue 03 (2012-11-30)
R1PEFS8
Q1PEGS2
R1PEGS1
N1PEG8
OptiX OSN 3500/7500
N1PEX2
OptiX OSN 3500/7500
N2PEX1
OptiX OSN 3500/7500
N1PEFF8
OptiX OSN 3500/7500
R1PEF4F
TNN1EX2
OptiX OSN 7500 II
TNN1EG8
OptiX OSN 7500 II
TNN1ETMC
OptiX OSN 7500 II
TNN1EFF8
OptiX OSN 7500 II

179
OptiX OSN 7500 II/7500/3500/1500

6 ETH-OAM

This section describes the limitations on and precautions for Ethernet port OAM in the network
design phase, configuration and commissioning phase, and maintenance phase.

Applicable
Object

Details
Remarks
OAM working
mode
There are two OAM modes: active

mode and passive mode. Only the
end in active mode can initiate an
auto-discovery or remote loopback.
Of the two interconnected ends, one
end must work in active OAM
mode.
Remote
loopback
The remote loopback function can

be enabled to monitor link
performance and locate faults.
Normal service packets will be
looped back and discarded when this
function is enabled.

None.
None.
6.2.5 Principle Description

Ethernet port OAM is realized through the OAM auto-discovery, link performance monitoring,
remote fault detection, remote loopback and selfloop test.
6.2.5.1 OAM Auto-Discovery

By exchanging the information OAMPDU periodically, the equipment at local end is informed
that the opposite end supports the Ethernet port OAM protocol. OAM auto-discovery is a
prerequisite to realize the link performance monitoring, fault locating and remote loopback.
Working Principle
As shown in Figure 6-2, the Code field of the OAMPDU is 0x00. This indicates that the
OAMPDU is the information OAMPDU and used for OAM auto-discovery.
Issue 03 (2012-11-30)

180
OptiX OSN 7500 II/7500/3500/1500

6 ETH-OAM
Figure 6-2 Packet format of the information OAMPDU
Octets
Fields
Fixed Values
Destination Address
01-80-c2-00-00-02
Source Address
Length/Type
88-09
Subtype
0x03
Flags
Code
0x00
42-1496 Data/Pad
4
FCS
INFORMATION OAMPDU
Octets
Fields
1
1
1
2
1
1
2
3
4
Information Type
Information Length
OAM Version
Revision
State
OAM Configuration
OAMPDU Configuration
OUI
Vendor Specific Information
Fixed
Values
0x01
0x10
0x01
LOCAL INFORMATION TLV
1
1
1
2
1
1
2
3
Information Type
Information Length
OAM Version
Revision
State
OAM Configuration
OAMPDU Configuration
OUI
Vendor Specific Information
0x02
0x10
0x01
REMOTE INFORMATION TLV
1
1
1
2
Information Type
Information Length
OUI
Organization Specific Value
0xFE
ORGANIZATION SPECIFIC
INFORMATION TLV
The Data field of the information OAMPDU includes local information type-length-value (TLV)
domain and remote information type-length-value (TLV) domain. A OAM configuration byte
is contained in the TLV domain. When the link is normal, successful OAM auto-discovery
depends on information of bit digits in the OAM configuration bytes. Also, the information of
bit digits decides what functions are performed after OAM auto-discovery succeeds.
Table 6-1 lists details of OAM configuration bytes.
Issue 03 (2012-11-30)

181
OptiX OSN 7500 II/7500/3500/1500

6 ETH-OAM
Table 6-1 Details of OAM configuration bytes

Bit
Name
Description
7-5
Reserved
The reserved bits are all 0s when the OAMPDU

is transmitted and these bits are ignored in
receiving.
Variable retrieval
l When the value is set to 1, it indicates that the

data terminal equipment (DTE) supports the
transmission of the variable response
OAMPDU.
DTE does not support the transmission of the
variable response OAMPDU.
Link events

DTE supports the monitoring on bit error
performance (error frames or error signals) of
links. When bit errors cross the threshold, the
bit error event is transmitted to the opposite
end over the specified OAMPDU.
DTE does not support the monitoring on bit
error performance of links.
OAM remote loopback

support

DTE supports the loopback request of the
remote end. When the loopback command is
issued at the remote end, the local end
transmits all packets back to the remote end for
loopback, excluding OAMPDU packets.
DTE does not support the remote loopback.
Unidirectional support

local end can transmit the OAMPDU packets
to the local end when the fault occurs in the
receive direction.
local end cannot transmit the OAMPDU
packets to the local end when the route is faulty
in the receive direction.
OAM mode

OAM mode of the DTE is set to Active.
OAM mode of the DTE is set to Passive. When
the local end works in the passive mode, some
OAM functions cannot be enabled. For details,
see Table 6-2.
Issue 03 (2012-11-30)

182
OptiX OSN 7500 II/7500/3500/1500

6 ETH-OAM
Table 6-2 Mapping relation between OAM working modes and OAM functions
OAM Capability
OAM Mode
Active Mode
Passive
Mode
Initiates OAM auto-discovery process
Yes
No
Reacts to OAM auto-discovery process
Yes
Yes
Required to send information OAMPDUs.
Yes
Yes
Permitted to send event notification OAMPDUs
Yes
Yes
Permitted to send variable request OAMPDUs
Yes
No
Permitted to send variable response OAMPDUs
Yes
Yes
Permitted to send loopback control OAMPDUs
Yes
No
Reacts to loopback control OAMPDUs
Yes
Yes
Permitted to send organization specific OAMPDUs
Yes
Yes
When the Ethernet port OAM protocol is enabled for the port on the Ethernet service processing
board, the information OAMPDU is broadcast periodically. At the same time, the information
OAMPDU from the opposite port is received and processed. In this way, two peer ends exchange
the OAM information (including OAM configuration information and OAM state information)
to establish the OAM connection between two ends.
Function
The following functions are available at the port only when the OAM auto-discovery succeeds:
link performance monitoring, fault locating and loopback.
6.2.5.2 Link Performance Monitoring

Link performance monitoring is used to monitor the bit error performance (error frames or error
signals). When the local end detects that the bit errors cross the threshold, the bit error event is
transmitted to the opposite end over the specified OAMPDU. In this case, the opposite end
reports the alarm accordingly.
Working Principle
As shown in Figure 6-3, the Code field of the OAMPDU is 0x01. This indicates that the
OAMPDU is the event notification OAMPDU and used for notifying the bit error performance
event mutually.
Issue 03 (2012-11-30)

183
OptiX OSN 7500 II/7500/3500/1500

6 ETH-OAM
Figure 6-3 Packet format of event notification OAMPDU

Octets
Fields
Sequence Number
SEQUENCE NUMBER
Event Type
Event Length
Event Time Stamp
Errored Svmbol Window
Errored Svmbol Threshol
Errored Svmbol
Error Running Total
Event Running Total
1
1
2
8
8
8
8
4
Octets
Fields
Fixed Values
Destination Address
01-80-c2-00-00-02
Source Address
Length/Type
88-09
Subtype
0x03
Flags
Code
0x01
42-1496 Data/Pad
4
FCS
ENENT
NOTIFICATION
OAMPDU
Fixed
Values
0x01
0x28
ERRORED SYMBOL PERIOD EVENT

1
Event Type
0x02
1
Event Length
0x1A
2
Event Time Stamp
2
Errored Frame Window
4
Errored Frame Threshol
4
Errored Frames
8
Error Running Total
4
Event Running Total
1
1
2
4
4
4
8
4
ERRORED FRAME ENENT

Event Type
0x03
Event Length
0x1
Event Time Stamp
C
Errored Frame Window
Errored Frame Threshol
Errored Frames
Error Running Total
Event Running Total
ERRORED FRAME PERIOD EVENT

1
Event Type
0x04
1
Event Length
0x12
2
Event Time Stamp
2
Err.Fr.Sec.Sum.Window
2
Err.Fr.Sec.Sum.Threshol
2
Err.Fr.Sec.Summary
4
Error Running Total
4
Event Running Total
ERRORED FRAME SECONDS SUMMARY
1
Event Type
0xF
1
Event Length
E
3
OUI
x
Organization Specific Value
ORGANIZATION SPECIFIC EVENT
To perform performance statistics from different aspects, the link performance monitoring is
classified into bit error frame event monitoring, error frame second event monitoring, error frame
period event monitoring.
l
Issue 03 (2012-11-30)
Trigger condition of error frame events: Within a period of the error frame monitor window,
the number of actually received error frames is larger than the configured threshold value.
184
OptiX OSN 7500 II/7500/3500/1500

6 ETH-OAM
NOTE
The period of the error frame monitor window indicates the time period for each error frame statistics.
Trigger condition of error frame second events: Within the specific seconds, the detected
error frame seconds is larger than defined threshold value.
NOTE
When the error frame number is larger than 0 within a second, this second is called an error frame
second.
Trigger condition of error frame period events: Among the received frames of a specific
amount, the number of error frames is larger than defined threshold value.
When the Ethernet port OAM protocol is enabled at a port, the port queries the RMON statistic
count of the hardware chip periodically to acquire the information such as the number of accurate
packets and the number of error packets. You can find out whether the preceding three
performance events occur or not according to corresponding processing of the information. In
the case that a performance event occurs, the opposite end is informed of this event over the
event notification OAMPDU. After receiving the notification, the opposite equipment reports
the ETHOAM_RMT_SD alarm for maintenance personnel to perform troubleshooting.
Function
The link performance monitoring function is used to precisely analyze and monitor the link
performance within a specific range.
According to actual requirements, the user can configure window values and threshold values
of three link performance events respectively on the U2000. In this case, whether the link
performance degrades to the threshold can be detected.
6.2.5.3 Remote Fault Detection

The Ethernet port OAM entity transmits the faults (including link faults, dying gasps, critical
events) detected by the local end over the flag field defined by the OAMPDU to the remote end.
In this manner, the fault notification is realized.
Working Principle
When faults such as fiber cuts are detected in the receive direction at the port, the Ethernet port
OAM protocol is informed of these faults through the hardware module. Then the protocol
modifies 0-2 bit digits that correspond to flag domain fields of the OAMPDU. Thus, the event
notification OAMPDU packets are constructed and transmitted to the opposite equipment.
According to the flag domain fields of the OAMPUD, the opposite equipment can check whether
faults occur at the opposite entity and what fault types are. Based on the results, the opposite
equipment reports the fault alarms. In this way, the fault detection is realized.
Function
At the external physical port on the Ethernet service processing board, enable the Ethernet port
OAM protocol. Once the local end reports the fault alarms, it indicates that the link faults occur
in the receive direction of the opposite equipment.
Issue 03 (2012-11-30)

185
OptiX OSN 7500 II/7500/3500/1500

6 ETH-OAM
6.2.5.4 Remote Loopback

The OAM entity at the local end transmits the loopback control OAMPDU packets to the remote
OAM for applying for the loopback. According to loopback data analysis, the fault locating and
link performance test are performed.
Working Principle
As shown in Figure 6-4, the code field of the OAMPDU is 0x04. This indicates that the
OAMPDU is the loopback control OAMPDU and is used for the loopback test.
Figure 6-4 Packet format of the loopback control OAMPDU
Octets
Fields
Fixed Values
Destination Address
01-80-c2-00-00-02
Source Address
Length/Type
88-09
Subtype
0x03
Flags
Code
1+41
4
0x04
Data/Pad
Octets
Fields
Fixed
Values
Remote Loopback Command
0x01
ENABLE REMOTE
LOOPBACK COMMAND
FCS
LOOPBACK
CONTROL OAMPDU
Remote Loopback Command
0x02
DISABLE REMOTE
LOOPBACK COMMAND
The loopback transmit end transmits the loopback control OAMPDU packets to the opposite
end first. After receiving the packets, the opposite end checks whether it can respond to the
remote loopback first. If it can respond to the remote loopback, the opposite end starts remote
loopback and transmits a response packet back to the end that initiates the loopback at the same
time.
After receiving the response packets from the response end, the transmit end analyzes the packets
to confirm that the opposite end is in the response loopback state. Then the transmit end starts
the loopback. In this manner, the entire process of loopback initiation is complete.
During the entire loopback, the transmission trails of the data packets are marked by arrows in
Figure 6-5.
Issue 03 (2012-11-30)

186
OptiX OSN 7500 II/7500/3500/1500

6 ETH-OAM
Figure 6-5 Transmission trails of the data packets
Local
Remote
Client
Client
LLC
LLC
OAM
OAM
MAC CTRL
MAC CTRL
MAC
MAC
RS
RS
PCS
PCS
PMA
PMA
PMD
PMD
MEDIUM
MEDIUM
Tx
Rx
Tx
Rx
Port that initiates the loopback:

l
Transmit direction: Transmits all kinds of packets, including OAM protocol packets and
data service packets.
Receive direction: Extracts only the OAM protocol packets and discards other packets.
Port that responds to the loopback:

l
Receive direction: Transmits all packets, excluding the OAM packets, back to the transmit
end of this port for loopback.
Transmit direction: Transmits only the packets that are received in the receive direction
during loopback externally.
NOTE
During the loopback, the OAM protocol packets are transmitted and received normally at both the loopback
initiation end and loopback response end.
Function
The loopback is a method to locate the faults and test the performance. Compare the number of
transmitted packets with that of received packets in loopback. The result can be used to detect
link performance and link faults in this link bidirectionally from the loopback initiation end to
the loopback response end.
6.2.5.5 Selfloop Test

Ethernet service processing boards enabled with the self-loop detection function can detect a
self-loop. In self-loop mode, a fiber from the transmit port is looped back to the receive port on
Issue 03 (2012-11-30)

187
OptiX OSN 7500 II/7500/3500/1500

6 ETH-OAM
the same board. When a self-loop is detected, an alarm is reported and ports where the self-loop
occurs are blocked.
Working Principle
The selfloop test is a function developed by Huawei on the basis of the IEEE 802.3ah protocol.
By testing and blocking the selfloop port, you can solve the port loop problems.
l
The selfloop test packets are constructed as the Ethernet port OAM protocol packets, with
a packet type of protocol reservation type 6. The first eight significant reserved bits in the
flag fields are used to carry the ID of the transmit port.
When the selfloop test is enabled at a port, the specified selfloop check packets are
transmitted from the port. One packet is transmitted each second.
When a port receives the selfloop check packets, it compares the source MAC address
carried in the packets with its own MAC address. If the former MAC address is the same
with the later, it indicates that the local port and the opposite port are located in the same
Ethernet service processing board. At this moment, further compare IDs of two ports. If
the IDs are the same, they are the same port actually. In this case, this indicates the port
selfloop. If the IDs are different, it indicates the intra-board port selfloop.
Function
When the selfloop function is enabled at all ports on the equipment, the ring network that is
available during the networking can be detected. In addition, the ETHOAM_SELF_LOOP alarm
is reported. When the selfloop function is enabled at the port, the protocol closes the selfloop
port automatically after detecting the selfloop port.
6.2.6 Networking and Application

Ethernet port OAM is not applicable to specific services. The application of Ethernet port OAM
focuses on the maintenance of the point-to-point Ethernet link between two sets of equipment
that are directly connected to each other with fibers or network cables.
Ethernet port OAM is only applicable to external physical ports. See Figure 6-6.
Figure 6-6 Application range of Ethernet port OAM
VCG
MAC
Board
MAC
VCG
Board
Physical connection
OAMPDU interworking available
Issue 03 (2012-11-30)
OptiX NE

188
OptiX OSN 7500 II/7500/3500/1500

6 ETH-OAM
If two sets of directly connected equipment support the Ethernet port OAM protocol, first enable
the directly connected protocol at the connected ports. Then, the protocol starts the autodiscovery. If the auto-discovery succeeds, you can enable the following functions as required.
l
After the auto-discovery succeeds, the protocol automatically monitors the link
performance of the link. If Remote Alarm Support for Link Event is set to Enabled,
when detecting that the error frames or error signals cross the threshold, the protocol sends
a message about the link performance event to the opposite equipment. After receiving the
message, the opposite equipment reports an alarm indicating the link performance event.
If detecting a fiber cut in the receive direction of the local equipment, the protocol sends a
message about the fiber cut to the opposite equipment. After receiving the message, the
opposite equipment reports an alarm indicating the remote link fault.
To detect the link status from the local equipment to the opposite equipment, you can initiate
the loopback operation at the local equipment. After the opposite equipment successfully
responds to the loopback, the local equipment and the opposite equipment are in the Initiate
Loopback at Local status and the Respond Loopback of Remote status respectively. At
this time, you can send data services at a certain rate from the local equipment, and then
check the RMON statistics of transmitted and received data services. By comparing the
count of transmitted services and the count of received services, you can determine the link
performance.
Enable the selfloop detection function for all the external physical ports on the local
equipment. Then, if any loop is detected, a selfloop alarm is reported. If the function of
blocking the selfloop port is also enabled, the port where the selfloop is performed is
blocked.
6.2.7 Configuring Ethernet Port OAM

Ethernet port OAM is not applicable to specific services. The application of Ethernet port OAM
focuses on the maintenance of the point-to-point Ethernet link between two sets of equipment
that are directly connected to each other with fibers or network cables.
l
Different from Ethernet service OAM, Ethernet port OAM is not related to services.
The interconnected systems must support the Ethernet port OAM protocol.
Ethernet port OAM requires that the system MAC address of the Ethernet service
processing board must be unique on the entire network.
Determine the maintenance operations based on the actual OAM requirement and 6.2.6
Networking and Application.
Configuration Flow
Figure 6-7 shows the flow of configuring Ethernet port OAM.
Issue 03 (2012-11-30)

189
OptiX OSN 7500 II/7500/3500/1500

6 ETH-OAM
Figure 6-7 Configuration flow of Ethernet port OAM

Start
Whether
the board MAC
address is
normal
Configure the board

MAC address
No
Yes
Enable the OAM

auto-discovery
Auto-discovery
succeeds at the
two ends
Refer to the Alarms

and Performance
Events Reference for
the handling
No
Yes
Fault detection
automatically starts
Inform the
opposite end of
the detected
fault
Link performance detection

automatically starts
Inform
the opposite end
of the performance
threshold-crossing
event?
Yes
No
Yes
No
Adjust
the monitoring
threshold?
Objective of the
loopback test is
achieved?
No
Yes
Enable remote alarm

support for link event
Enable remote alarm

support for link event
Configure the self-loop

detection
Configure the
remote loopback
Cancel the remote

loopback
Is it
necessary to
enable the loop
shutdown port
function?
No
No
Yes
Yes
Configure OAM error frame
monitoring threshold
Report
ETHOAM_RMT_CRIT_FAULT
No
Enable the the loop

port shutdown function
Report
No
ETHOAM_RMT_SD
Report
Report
ETHOAM_SELF_LOOP
ETHOAM_VCG_SELF_LOOP
No
4
Yes
Yes
Yes
Refer to the Alarms and

Performance Events
Reference for the handling

Performance Events
Reference for the handling
Prerequisite for configuring Ethernet port OAM
Configure Ethernet port OAM functions
Perform optional operations
Handle the Ethernet port OAM test result
No
Yes

Performance Events Reference
for the handling
End
6.2.7.1 Setting the MAC Address for a Board

The Ethernet OAM function requires that the board has a unique MAC address. If the MAC
address is unavailable for the board, you can set and query this address by using the U2000.
Prerequisites
l
The board cannot be configured with the Ethernet OAM function.
Issue 03 (2012-11-30)

190
OptiX OSN 7500 II/7500/3500/1500

6 ETH-OAM
The system MAC address must be legally obtained to ensure its uniqueness in the entire
network.
To apply the settings, you need to perform a cold reset or warm reset on the board after
modifying the MAC address.
After setting the MAC address, do not modify it unless necessary.
Context
Procedure
Step 1 In the NE Explorer, select the required Ethernet board and then choose Configuration >
Advanced Attribute > Set Board MAC Address from the Function Tree.
Step 2 Click Query to query the current MAC address of the board.
l
If the MAC address of the board is "00-00-00-00-00-00", the MAC address of the board is
not set. Apply for an MAC address and set it for the board. Go to Step 3.
If the MAC address of the board is not "00-00-00-00-00-00", the MAC address of the board
is set. No more operations are needed.
Step 3 Double-click the parameter field, enter the unique MAC address that you obtain, and confirm
it. Click Apply. A dialog box is displayed, indicating that the operation is successful.
Step 4 Click Close.
Step 5 Right-click on the board, and choose Cold Reset or Warm Reset from the shortcut menu to
apply the settings.
----End
6.2.7.2 Enabling the Auto-Discovery Function of Ethernet Port OAM

The OAM auto-discovery functions as a basis to realize the link performance monitoring, fault
detection, and remote loopback.
Prerequisites
Context
l
The OAM mode includes the active mode and the passive mode. For two interconnected
systems, the OAM mode of one system must be the active mode. Otherwise, the OAM
auto-discovery fails.
if the OAM modes of the two systems are both active modes, a link fault occurs, or one
system fails to receive the OAM protocol message, an alarm is reported, indicating that the
OAM auto-discovery fails.
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Packet
Configuration > Ethernet OAM Management > Ethernet Port OAM Management from
the Function Tree.
Issue 03 (2012-11-30)

191
OptiX OSN 7500 II/7500/3500/1500

6 ETH-OAM
Step 2 Click the OAM Parameter tab. Select the port, and set OAM Working Mode. In the Enable
OAM Protocol drop-down list, select Enabled.
Step 3 Click Apply.
Step 4 Click the Remote OAM Parameter tab. Click Query.
----End
6.2.7.3 Configuring the Remote Alarm Support for Link Event

To report the link fault event and link performance event to the opposite equipment, the capability
of remote alarm support for the link event must be provided on the local end.
Prerequisites
l
The OAM auto-discovery must be successful at the two ends.
Context
When the OAM auto-discovery is successful at the two ends, the link fault detection and
performance detection are automatically started.
l
To report the detected link fault event to the opposite equipment, Remote Alarm Support
for Link Event must be set to Enabled for the local equipment.
To report the detected link fault event to the opposite equipment, the following operations
must be performed for the local equipment.
Set Remote Alarm Support for Link Event to Enabled.
Set Error Frame Period Window (Frame) and Error Frame Monitor Threshold.
After Remote Alarm Support for Link Event is set to Enabled at the opposite port, if the
opposite end detects link performance degradation, you can query the ETHOAM_RMT_SD
alarm, which is reported on the local end, by using the U2000. Based on the alarm, you can
determine the type of the link performance event.
After Remote Alarm Support for Link Event is set to Enabled at the opposite port, if the
opposite equipment detects a link fault event or encounters a fault that makes the equipment fail
to be restored (such as a power failure), you can query the ET_RMT_CRIT_FAULT alarm,
which is reported at the local end, by using the U2000. Based on the alarm, you can determine
the fault type.
Procedure
the Function Tree.
Step 2 Click the OAM Parameter tab. Select the port, and set Remote Alarm Support for Link
Event to Enabled.
Step 3 Click Apply.
----End
Issue 03 (2012-11-30)

192
OptiX OSN 7500 II/7500/3500/1500

6 ETH-OAM
6.2.7.4 Setting OAM Error Frame Monitoring Parameters

You can set the error frame monitoring parameters to customize the threshold of link
performance and to monitor link performance.
Prerequisites
l
The Ethernet port OAM function must be enabled on the remote equipment, and the OAM
auto-discovery must be successful at the two ends.
Context
After the OAM auto-discovery is successful, set the error frame period window and error frame
monitor threshold parameters, and enable the remote alarm support for link event for the local
equipment. If the local equipment detects a link event in the receive direction, it informs the
opposite equipment of the link event. If the remote alarm for the link event is also supported on
the opposite end, the opposite equipment can also inform the local equipment of the link event
that is detected on the side of the opposite end. Then, the ETHOAM_RMT_SD alarm is reported
on the local end, asking the maintenance personnel to handle the link event.
Procedure
the Function Tree.
Step 2 Click the OAM Error Frame Monitor tab.
Step 3 Select a port and set the error frame monitoring parameters.
For the description of OAM error frame monitoring parameters, see OAM Errored Frame
Monitoring.
Step 4 Click Apply. A dialog box is displayed, indicating that the operation is successful. Click
Close.
----End
6.2.7.5 Configuring the Remote Loopback

On the local equipment, the external physical port of the Ethernet service processing board can
request the interconnected equipment to perform the loopback. By analyzing the loopback data,
the local equipment can realize the fault locating and the link performance detection.
Prerequisites
l
The OAM auto-discovery must be successful at the two ends.
For the equipment where the loopback is initiated, OAM Working Mode must be set to
Active.
The equipment that responds to the loopback must have the capability of supporting the
remote loopback.
Issue 03 (2012-11-30)

193
OptiX OSN 7500 II/7500/3500/1500

6 ETH-OAM
Context
l
If a port is capable of responding to loopbacks, it enters the "respond loopback of remote"

state and reports the loopback responding alarm when receiving the command of enabling
the remote loopback function sent from the opposite OAM port. In this case, the equipment
that initiates the loopback enters the "initiate loopback at local" state and reports the
loopback initiating alarm.
If the port receives the command of disabling the remote loopback function sent by the
opposite OAM port, it exits from the "respond loopback of remote" state and ends the
loopback responding alarm. In the meantime, the equipment that initiates the loopback ends
the loopback initiating alarm.
After the remote loopback function is enabled, normally, service packets, except the
OAMPDU, are looped back at the remote end.
After using the remote loopback function to complete the fault locating and the link
performance detection, you should disable the remote loopback function at the end where
the loopback is initiated and then restore the services. At this time, the alarm is automatically
cleared.
Procedure
the Function Tree.
Step 2 Click the OAM Parameter tab. Select the port that needs to initiate a loopback, and select
Enable Remote Loopback from the drop-down list of OAM.
Step 3 Click Apply.
----End
6.2.7.6 Enabling Self-Loop Detection

After enabling the self-loop detection on an Ethernet port, you can check the loopback of the
port and the loopback between the port and other Ethernet ports on the board.
Prerequisites
l
All the external physical ports of the Ethernet service processing board must be enabled.
Procedure
Configuration > Interface Management > Ethernet Interface from the Function Tree.
Step 2 Click the Advanced Attributes tab.
Step 3 Set Loopback Check to Enabled.
Step 4 Click Apply. Close the displayed dialog box.
----End
Issue 03 (2012-11-30)

194
OptiX OSN 7500 II/7500/3500/1500

6 ETH-OAM

This topic describes the alarms and performance events that are related to the Ethernet port OAM
function.

This topic describes the alarms that are related to the Ethernet port OAM function.
Table 6-3 lists the alarms that are related to the Ethernet port OAM function.
Table 6-3 Alarms related to the Ethernet port OAM function
Issue 03 (2012-11-30)
Alarm Name
Description
ETHOAM_RMT_LOOP
This alarm indicating the remote loopback of point-topoint Ethernet OAM. This alarm only occurs on the port
with the point-to-point OAM protocol enabled. If the
port is able to respond to loopback, it enters the
loopback response state and reports the loopback
response alarm after it receives the remote loopback
enabling command sent by the opposite OAM port. The
loopback initiator reports the loopback initiating alarm.
If the port receives the loopback disabling command,
it exits the loopback response state and ends the
loopback response alarm. The loopback initiator end
also ends the loopback initiating alarm.
ETHOAM_RMT_SD
This alarm indicating the remote SD of point-to-point

Ethernet OAM. When the port with the OAM protocol
enabled receives the link event message from the
opposite end which indicates that the remote Ethernet
performance degraded, this alarm occurs.
ETHOAM_RMT_CRIT_FAULT
This alarm indicating that a critical fault occurs on the

remote end of point-to-point Ethernet OAM. When the
port with the OAM protocol enabled receives the OAM
message that contains critical fault information from
the opposite end, this alarm occurs.
ETHOAM_DISCOVER_FAIL
This alarm indicating the point-to-point Ethernet OAM

discovery failure. When the OAM protocol is enabled
at the port of a board and the negotiation with the
opposite equipment fails, this alarm occurs.
ETHOAM_SELF_LOOP
This alarm indicating loopback of the MAC port that

receives the OAM protocol packets in a point-to-point
manner. If the MAC port of a board receives the OAM
protocol packets sent by itself or the board after
detection of the loop is enabled, the
ETHOAM_SELF_LOOP alarm is reported.

195
OptiX OSN 7500 II/7500/3500/1500

6 ETH-OAM
Alarm Name
Description
ETHOAM_VCG_SELF_LOOP
This alarm indicating loopback of the VCTRUNK port

that receives the OAM protocol packets in a point-topoint manner. If the VCTRUNK port of a board
receives the OAM protocol packets sent by itself or the
board after detection of the loop is enabled, the
ETHOAM_VCG_SELF_LOOP alarm is reported.

There are no performance events related to the Ethernet port OAM.
6.2.9 Parameter Description: Ethernet Port OAM

This topic describes the parameters that are related to the service configuration.
6.2.9.1 OAM Parameters

You need to set the OAM parameters before enabling the Ethernet port OAM function.
Table 6-4 list the OAM parameters.
Table 6-4 OAM parameters
Field
Value
Description
Port
For example, PORT3
Enable OAM Protocol
Enabled, Disabled
Default: Disabled
The Enable OAM Protocol

parameter specified whether the
end-to-end OAM protocol
(namely, the IEEE 802.3ah
protocol) is enabled at a port.
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.
Click A.7.24 Enable OAM
Protocol for more information.
Issue 03 (2012-11-30)

196
OptiX OSN 7500 II/7500/3500/1500

6 ETH-OAM
Field
Value
Description
OAM Working Mode
Active, Passive
Default: Active
The port for which this field is set

to Active can initiate the OAM
connection. The port for which
this field is set to Passive can
only wait for the opposite end to
send the OAM connection
request.
Click A.7.25 OAM Working
Mode for more information.
Remote Alarm Support for

Link Event
Enabled, Disabled
Default: Enabled
The Remote Alarm Support for

Link Event parameter specifies
whether to report the detected
link events (for example, Error
Frame Period Threshold,
Error Frame Monitor
Threshold, and Error Frame
Second Threshold) to the
opposite end.
Click A.7.26 Remote Alarm
Support for Link Event for
more information.
Max. OAM Packet Length

(byte)
For example, 1000
Displays the maximum OAM

packet length.
Remote Side Loopback

Response
Disabled, Enabled
If the Remote Side Loopback

Response is enabled, this port
responds to the loopback request
from the opposite end.
Loopback Status
Initiate Loopback at
Local, Respond
Loopback of Remote,
Non-Loopback
Default: Non-Loopback
Default: Disabled
The Loopback Status (OAM

Parameter) parameter specifies
whether a port on the board is in
the loopback state. If yes, the port
is in the Initiate Loopback at
Local or Respond Loopback of
Remote state.
Click A.7.28 Loopback Status
(OAM Parameter) for more
information.
6.2.9.2 Remote OAM Parameters

Before enabling the Ethernet port OAM function, you need to set the OAM parameters of the
Ethernet port at the opposite end.
Table 6-5 list the remote OAM parameters.
Issue 03 (2012-11-30)

197
OptiX OSN 7500 II/7500/3500/1500

6 ETH-OAM
Table 6-5 Remote OAM parameters

Field
Value
Description
Port
For example,
PORT3
Remote OAM Working

Mode
Active, Passive
Queries the working mode of the OAM

at the opposite port.
Click A.7.25 OAM Working Mode for
more information.
Remote Alarm Support for

Link Event
Enabled, Disabled
Default: Enabled
The Remote Alarm Support for Link

Event parameter specifies whether to
report the detected link events (for
example, Error Frame Period
Threshold, Error Frame Monitor
Threshold, and Error Frame Second
Threshold) to the opposite end.
Click A.7.26 Remote Alarm Support
for Link Event for more information.
Remote Side Loopback

Response
Disabled, Enabled
Queries the loopback response at the

opposite port.
Unidirectional Operation
Enabled, Disabled
The Unidirectional Operation

parameter specifies the hardware
capability. If a port fails at the receive
end, but can transmit data frames at the
transmit end, it has the capability of
performing unidirectional operations.
Otherwise, it does not have the
capability of performing unidirectional
operations.
Default: Disabled
Click A.7.27 Unidirectional

Operation for more information.
Max. OAM Packet Length
(byte)
For example, 1000
Displays the maximum OAM packet

length.
6.2.9.3 OAM Error Frame Monitoring

You need to set the parameters for error frame monitoring before enabling the Ethernet port
OAM function.
Table 6-6 lists the parameters for OAM error frame monitoring.
Table 6-6 Parameters for OAM error frame monitoring
Issue 03 (2012-11-30)
Field
Value
Description
Port
For example, PORT3

198
OptiX OSN 7500 II/7500/3500/1500

Issue 03 (2012-11-30)
6 ETH-OAM
Field
Value
Description
Error Frame Monitor

Window(ms)
1000-60000, in step length of

100
Default: 1000
The Error Frame Monitor

Window(ms) parameter
specifies the period during
which the number of error
frames received at the port
exceeds the specified upper
threshold. In this case, a link
event alarm is reported.
Click A.7.18 Error Frame
Monitor Window(ms) for
more information.
Error Frame Monitor

Threshold
1-4294967295 (in step length

of 1)
Default: 2

Threshold (Entries)
parameter specifies the upper
threshold of error frames
received at the port. In this
case, a link event alarm is
reported.
Monitor Threshold
(Entries) for more
information.
Error Frame Period Window
Maxpps/10-Maxpps*60, in
step length of 1
Default: Maxpps
The Error Frame Period

Window (Frame) parameter
specifies the received N
frames in which the number
of error frames reach the
specified upper threshold. In
this case, a link event alarm is
reported.
Period Window (Frame) for
more information.
Error Frame Monitor

Threshold
1-892800000, in step length

of 1
Default: 1

Threshold (Frame)
parameter specifies the
received N frames in which
the number of error frames
reach the specified upper
threshold. In this case, a link
event alarm is reported.
Monitor Threshold
(Frame) for more
information.

199
OptiX OSN 7500 II/7500/3500/1500

6 ETH-OAM
Field
Value
Description
Error Frame Second Window

(s)
10-900, in step length of 1

Default: 60
The Error Frame Second

Window(s) parameter
specifies the error frame
second when any error
frames are received at the
port within one second. If the
error frame seconds within a
certain time period reach the
specified upper threshold,
link event alarms are
reported. The time period in
which error frames are
received is called the error
frame second window.
Second Window(s) for more
information.
Error Frame Second

Threshold(s)

Default: 2
The Error Frame Second

Threshold(s) parameter
specifies the second during
which error frames are
received at the port. If the
error frame seconds within a
certain time period reach the
specified upper threshold, a
link event alarm is reported.
The upper threshold is called
the error frame second
threshold.
Second Threshold(s) for
more information.
6.3 Ethernet Service OAM

Ethernet service OAM focuses on Ethernet services and maintains end-to-end Ethernet links. It
implements sectional and segmental maintenance over service flows by specifying the
maintenance domain, maintenance association, and maintenance point.

Ethernet service OAM focuses on maintenance of end-to-end Ethernet links. By defining the
maintenance domain, maintenance association, and maintenance point, Ethernet service OAM
can manage service flows by segment and by layer.
As a protocol based on the MAC layer, ETH-OAM detects Ethernet links by transmitting OAM
packets. The OAM packets are processed at only the MAC layer.
With regard to ETH-OAM, the following concepts must be defined:
Issue 03 (2012-11-30)

200
OptiX OSN 7500 II/7500/3500/1500

6 ETH-OAM
Maintenance domain (MD): An MD refers to a network that requires OAM.
Maintenance association (MA): An MA is a domain associated with services, and an MA

consists of several maintenance end points (MEPs) and maintenance intermediate points
(MIPs).
Maintenance point (MP): MPs include MEPs and MIPs.

MEP: MEPs function to initiate and terminate all OAM packets, and are associated with
services. On a network, an MA and a maintenance point identification (MPID) work
together to specify a unique MEP.
MIP: MIPs cannot initiate OAM packets. If the non-standard protocol is used, MIPs
can respond to and forward LB packets and LT packets, and can only forward CC
packets. If the standard protocol is used, MIPs can forward CC packets and LB packets,
and can respond to and forward LT packets.
MD
On a network, customers, service providers, and operators focus on different network segments.
Thus, management over different network segments that a service traverses is required. In
addition, different service flows need to be managed separately. Ethernet service OAM maintains
the Ethernet by performing end-to-end check based on MDs.
MA
An MA is a part of an MD. An MD can be divided into one or multiple MAs. On an operator
network, a VLAN corresponds to a service instance; on equipment, a VLAN corresponds to one
or multiple MAs. Therefore, you can detect the connectivity faults of a network that transmits
a certain service instance by dividing an MD into multiple MAs. An MA is at the same level as
the MD it belongs to.
MP
An MP is the functional entity of Ethernet service OAM. MPs are classified into MEPs and
MIPs.
Each MP has a unique MPID on the entire network. The information about the MP, in which
the service type, service ID, and VLAN tag is key, is recorded in the MAC address table, MP
table, and routing table. Once a Huawei MP is created successfully, the protocol packet carrying
the information about this MP is broadcast to the entire network periodically. Then, the other
MPs receive the protocol packet and record the information for future use.
NOTE
All OAM operations must be initiated by an MEP. An MIP cannot initiate any OAM operation or send any
OAM packet.
MEP
An MEP specifies the starting position of an MA. It functions to initiate and terminate all
OAM packets, and is associated with services. On a network, an MA and an MEP ID work
together to specify a unique MEP.
As shown in Figure 6-8, an arrow generally indicates an MEP and the direction of the
arrow specifies the direction of the MEP.
An MEP provides the following functions:
Allows transmission of all service packets without any requirement for their directions.
Issue 03 (2012-11-30)

201
OptiX OSN 7500 II/7500/3500/1500

6 ETH-OAM
Checks all the OAM packets that traverse the MEP along the direction of the arrow.
Allows transmission of the OAM packets at a level higher than the level of the local
MEP, without performing further checks.
Discards the OAM packets at a level lower than the level of the local MEP or at the
same level as the local MEP.
Checks all the OAM packets that traverse the MEP in the opposite direction of the arrow.
Allows transmission of the OAM packets at a level higher than the level of the local
MEP, without performing further checks.
Processes the OAM packets at the same level as the local MEP.
Discards the OAM packets at a level lower than the level of the local MEP.
An MEP can generate OAM packets at the same level as the local MEP and transmit
them in a specified direction.
l
MIP
As shown in Figure 6-8, an ellipse generally indicates an MIP, which has no direction.
An MIP provides the following functions:
Allows transmission of all the service packets.
Checks all the OAM packets that need to traverse the local MIP.
Allows transmission of all the OAM packets at a level higher than the level of the local
MIP.
Based on the special operation code or destination MAC address, processes the packets
as follows:
Transparently transmits them.
Transparently transmits and processes them.
Intercepts the OAM packets at the same level as the local MIP and processes them.
Based on the special operation code, discards all the OAM packets at a level lower than
the level of the local MIP.
Layered Management
Ethernet service OAM adds the management level fields to OAM protocol packets to provide
layered management. A higher-level MD can cross a lower-level MD, but a lower-level MD
cannot cross a higher-level MD. Based on such layered management, a service can be maintained
differently in different segments, and different service flows can be managed.
Figure 6-8 shows the logical diagram of MD layers.
Issue 03 (2012-11-30)

202
OptiX OSN 7500 II/7500/3500/1500

6 ETH-OAM
Figure 6-8 Logical diagram of MD layers

CE
a
Operator A Provider Bridges

b
c
Operator B Provider Bridges

d
e
CE
f
Customer ME Level
Service Provider ME Level
Operator ME Level
Physical ME Level
Bridge with Bridge Ports
Maintenance End Points
Maintenance Intermediate Points
AIS Convergence Function
Logical path of CFM

Messages
Maintenance
Entities
Currently, the protocol specifies division of 8-level layers, from level 0 to level 7. Eight
maintenance entity (ME) levels are assigned to differentiate customers, service providers, and
operators.
Layer levels are arranged in a descending order as follows: customer ME level > service provider
ME level > operator ME level.
The dashed lines in Figure 6-8 show the logical paths that Ethernet service OAM packets travel
through. MPs at different layers process OAM protocol packets as follows:
l
MPs transparently transmit OAM protocol packets at a higher layer level.
MPs discard OAM protocol packets at a lower layer level.
MPs choose to respond to or terminate OAM protocol packets at the same layer level, based
on the message types of these packets.

This topic describes the standards and protocols that Ethernet service OAM complies with.
Ethernet service OAM complies with the following standards and protocols:
l
IEEE 802.1ag Connectivity Fault Management (CFM)
ITU-T Y.1731 OAM functions and mechanisms for Ethernet based networks
6.3.3 Availability
The Ethernet service OAM function requires the support of the applicable equipment, boards,
and software.
Issue 03 (2012-11-30)

203
OptiX OSN 7500 II/7500/3500/1500

6 ETH-OAM
Version Support
Applicable Version
OptiX OSN 1500/3500
T2000
U2000
Applicable Version
OptiX OSN 7500
U2000
Applicable Version
OptiX OSN 7500 II
U2000
Hardware Support
Applicable
Board
Applicable Version
N1PEG16
OptiX OSN 3500
N1PEX1
OptiX OSN 3500
N1PETF8

and later
OptiX OSN 3500/7500

and later
Issue 03 (2012-11-30)
R1PEFS8
Q1PEGS2
R1PEGS1
N1PEG8
OptiX OSN 3500/7500
N1PEX2
OptiX OSN 3500/7500
N2PEX1
OptiX OSN 3500/7500
N1PEFF8
OptiX OSN 3500/7500

204
OptiX OSN 7500 II/7500/3500/1500

6 ETH-OAM
Applicable
Board
Applicable Version
R1PEF4F
TNN1EX2
OptiX OSN 7500 II
TNN1EG8
OptiX OSN 7500 II
TNN1ETMC
OptiX OSN 7500 II
TNN1EFF8
OptiX OSN 7500 II

This section describes the limitations on and precautions for Ethernet service OAM in the
network design phase, configuration and commissioning phase, and maintenance phase.
Issue 03 (2012-11-30)
Applicable
Object

Details
Remarks
Ethernet
service OAM
The Ethernet service OAM function

does not support the Ethernet
service model for unidirectional
communication. When the Ethernet
service OAM function is enabled,
unidirectional Ethernet services are
not affected but the Ethernet service
OAM function cannot be
completely implemented. Users
need to add or delete maintenance
points and perform required OAM
operations on the existing
bidirectional end-to-end services.
Ethernet
service OAM
The Ethernet service OAM function

supports end-to-end maintenance
only when the OAM service model
is symmetrical. A symmetrical
OAM service model means that all
maintenance points in a
maintenance domain must belong to
the same service flow (the same
VLAN). When the OAM service
model is asymmetrical, the OAM
function fails to work properly.

205
OptiX OSN 7500 II/7500/3500/1500

6 ETH-OAM
Applicable
Object

Details
Remarks
Ethernet
service OAM
A maintenance domain (MD)

consists of n (n2) maintenance
association end points (MEPs) and
m (m0) maintenance association
intermediate points (MIPs) at the
same level. In an OAM test, all
maintenance points (MPs) that are
involved in a service flow must be in
the same MD. In addition, if MPs of
higher levels are added to an existing
MD, the existing MD is impaired.
As a result, the OAM test fails.
Ethernet
service OAM
and LAG
If the N1PEX1 or N1PEG16 is

configured with Ethernet service
OAM, the CC function is
unavailable when the MEP on the
ingress node coexists with a crossboard load-sharing LAG.
Ethernet
service OAM
and LAG
Ethernet service OAM and loadsharing LAG are not simultaneously

supported by the N1PEG8/
N2PEX1/N1PEX2 board on the
OptiX OSN 3500/7500 and the
TNN1EG8/TNN1EX2/
TNN1ETMC/TNN1EFF8 board on
the OptiX OSN 7500 II.
MD
l An MD name identifies a unique

MD on a network.
l Multiple MDs can be embedded

or tangent. A lower-level MD
can be embedded into a higher
level MD. Multiple MDs,
however, cannot intersect.
l To test Ethernet services
between edge nodes of a
transport network, it is
recommended that you create an
MD with a level being 4; to test
Ethernet services between nodes
within a transport network, it is
recommended that you create an
MD with a level lower than 4.
Issue 03 (2012-11-30)

206
OptiX OSN 7500 II/7500/3500/1500

6 ETH-OAM
Applicable
Object

Details
Remarks
Maintenance
association
(MA)
l An MA needs to be associated
with an MD and can be
associated with only one MD.
l An MA name must be unique in

one MD. MA names in different
MDs can be the same.
l An MA needs to be associated
with services. For services
sharing one port (namely,
services based on PORT
+VLAN), an MA must be
associated with one service
VLAN.
l Set the same continuity check
message (CCM) transmission
period for all MEPs that belong
to one MA. The shorter a CCM
transmission period is, the faster
link fault detection by continuity
check (CC) is performed, but the
more resources and bandwidths
are used. It is recommended that
you set a CCM transmission
period to the default value (1s).
Issue 03 (2012-11-30)

207
OptiX OSN 7500 II/7500/3500/1500

6 ETH-OAM
Applicable
Object

Details
Remarks
MP
l To perform a CC or a loopback
(LB) test, set MEPs only at end
points; to perform a link trace
(LT) test, select some Ethernet
ports that services pass as MIPs
in addition to the setting of
MEPs.
l All MEPs and MIPs involved in

an OAM test must belong to one
MA.
l The MAC addresses of the MEPs
and MIPs involved in an OAM
test cannot be the same.
l Each MEP in one MA must have
a unique ID.
l When ETH-OAM streams pass a
packet switching unit, set the
direction of the MEP involved to
ingress; otherwise, set the
direction of the MEP to egress.
l Configure a remote MEP list for
an NE where an MEP is created,
and include all remote MEPs that
interact with the MEP into the
list.

Applicable
Object

Details
Remarks
OAM
operation
If AIS is activated on an MEP, the

reported level of customer layer
should be higher than the level of the
MD where the MEP is.
None.
6.3.5 Principle Description

The Ethernet service OAM function can be realized through the continuity test, loopback test,
link trace test, and OAM_Ping test.
Issue 03 (2012-11-30)

208
OptiX OSN 7500 II/7500/3500/1500

6 ETH-OAM
6.3.5.1 Continuity Check

The continuity check (CC) is used to test the link state unidirectionally.
Working Principle
The source MEP constructs the continuity check message (CCM) packets and transmits them
periodically. After receiving the CCM packets from the source MEP, the sink MEP directly
enables the CC function that focuses on this source MEP.
If the sink MEP fails to receive the CCM packets from the source MEP within a check period,
it reports the alarm automatically until the link is recovered. That is, the sink MEP does not clear
the alarm until it receives the CCM packets from the sink MEP.
As shown in Figure 6-9, the CC function of the MEP1 is enabled. The MEP1 transmits the CCM
packets externally. After receiving the first CCM packet, the MEP2, MEP3 and MEP4 in the
same maintenance domain start the timer respectively to receive all CCM packets from the MEP1
periodically. Once the link is faulty, the sink MEP fails to receive the CCM packets within a
check period. In this case, the sink MEP reports the ETH_CFM_LOC alarm. The alarm is not
cleared until the link is recovered.
Figure 6-9 Continuity check diagram
MEP1
VB
MEP2
VB
MEP4
VB
MEP3
When the CC function is enabled at MEP1, MEP2, MEP3 and MEP4 at the same time, each
MEP is both the source end and sink end for the CC function. In this way, the bidirectional
continuity test is realized.
NOTE
Only the MEP can enable the continuity check and be the receive respond end for the check.
Function
Based on the regular check mechanism of the CC, the check is performed automatically after it
is configured successfully. In this way, the link fault check and fault auto-discovery are realized.
Additionally, the broadcast protocol packets generated with the CC are used to realize the pointto-multipoint detection and multipoint-to-multipoint detection, especially the detection of the
Layer 2 switching network. In this way, the network detection of the entire maintenance domain
is realized.
Issue 03 (2012-11-30)

209
OptiX OSN 7500 II/7500/3500/1500

6 ETH-OAM
6.3.5.2 Loopback Test

The loopback (LB) can be used to test the state of any MP link from the source MEP to the
maintenance domain.
Working Principle
Based on the bidirectional service, the loopback is a test performed manually at a time. The
source MEP constructs the loopback message (LBM) packets and adds the destination MP (MIP
or MEP) IDs to the packets. When the packets are transmitted, the timer is started.
After receiving the LBM packets, the sink MP constructs the loopback return (LBR) packets
and transmits them back to the source MEP. In this case, the loopback succeeds. If the source
MEP timer expires and fails to receive the LBR from the sink MP, the loopback fails.
As shown in Figure 6-10, MEP1 transmits LBM packets to the sink MEP4. When receiving the
packets, MIP2 and MIP3 in the same maintenance domain transparently transmit the packets.
After receiving the packets, the sink MEP4 transmits LBR packets to the source MEP1. Then
the loopback test is complete.
Figure 6-10 Loopback test diagram
MEP1
MIP2
MIP3
MEP4
LBM
LBR
NOTE
Only the MEP can initiate the loopback test, and both the MEP and MIP can be the receive end in the test.
To prevent LB packets from being transmitted continuously between different NEs, the OAM protocol
does not support coexistence of two management units on an NE. That is, different boards on the same NE
should not have the same loopback local identification (LLID).
Function
The loopback can be used to test the state of any node link from the source to the maintenance
domain. As the sink MP can be the MIP, the loopback can be used to locate the faults. Compared
with the continuity test, the loopback test is not a continuous test. Thus, you need start the test
manually each time.
6.3.5.3 Link Trace Test

Compared with the LB test, the link trace (LT) test provides enhanced fault locating capability.
That is, the faulty network segment can be located the first time in an LT test.
Issue 03 (2012-11-30)

210
OptiX OSN 7500 II/7500/3500/1500

6 ETH-OAM
Working Principle
The source MEP constructs the link trace message (LTM) packets and adds the ID of the sink
MEP to the packets for transmission. At the same time, the timer is started.
All MIPs that belong to this maintenance domain on the link continuously transmit the packets
to the sink MEP. At the same time, a link trace replay (LTR) packet is transmitted back to the
source MEP.
After the sink MEP receives the LTM packets, the packet transmission is complete. Then the
sink MEP transmits LTR packets back to the sink. In this case, the link trace test is successful.
If the source MEP timer expires and fails to receive the LTR from the sink MEP, the loopback
fails.
In addition, the parameter hop is added to the packet that is transmitted back. The hop is used
to indicate the MP ID of the returned maintenance point on the link during the link trace test. If
the first MP passed through the LTM is on the same board with the source MP, the hop starts
from 0 and accumulates in the sequence. Otherwise, the hop starts from 1.
The function of the link trace test is similar to the function of the loopback test. The difference
lies in the response to the LBM frames. In the loopback test, only the sink MP responds to the
LBM frames. In the link trace test, the MPs on the link respond to the LTM frames. According
to these response messages, the MIPs that are involved from the source MEP to the destination
MEP can be recognized, as shown in Figure 6-11
Figure 6-11 Link trace test diagram
MEP1
1
MIP2
MIP3
MEP4
LTR
LTM
LTR
LTM
LTR
LTM
1.
The source MEP1 transmits the LTM packets to the destination MEP4.
2.
After receiving the LTM packets, the MIP2 transmits the LTR packets to the source MEP1
and forwards the LTM packets at the same time.
3.
After receiving the LTM packets, the MIP3 transmits the LTR packets to the source MEP1
and forwards the LTM packets at the same time.
4.
After receiving the LTM packets, the destination MEP4 concludes the LTM packets and
transmits the LTR packets to the source MEP1.
NOTE
Only the MEP can initiate the link trace test and be the termination of the test.
Issue 03 (2012-11-30)

211
OptiX OSN 7500 II/7500/3500/1500

6 ETH-OAM
Function
Compared with the LB test, the LT test enhances the capability of fault locating.
1.
According to the returned MIP, the route that involves the protocol packets can be
determined.
2.
Once a link segment where the fault occurs is determined, the link state can be checked
according to the returned LTP packets. That is, links that transmit the packets back are
normal. In this manner, the faulty network segment is located.
6.3.5.4 Performance Detection

This section describes loss measurement (LM) and delay measurement (DM) that are defined
in ITU-T Y.1731. These functions are used for Ethernet service performance monitoring by
providing frame loss ratio (FLR), frame delay, and frame delay variation (FDV) between two
maintenance end points (MEPs) on an Ethernet link.
Single-ended LM
Single-ended LM is used to count lost packets on an Ethernet link within a specified period of
time.
NOTE
LM can be performed in two ways: dual-ended LM and single-ended LM. Currently, the OptiX OSN
equipment supports single-ended LM only. To learn about dual-ended LM, see ITU-T Y.1731, OAM
functions and mechanisms for Ethernet based networks.
Single-ended LM is used for on-demand OAM. That is, a single-ended LM test is manually
triggered. In this mode, a local MEP, within a specified period of time, periodically sends packets
with ETH-LM request (ETH-LMM) information to its opposite MEP, and receives packets with
ETH-LM reply (ETH-LMR) information from its opposite MEP.
NOTE
LM is performed between two MEPs, measuring the following:

l Local packet loss ratio: packet loss statistics in the receive direction of a local MEP
l Remote packet loss ratio: packet loss statistics in the transmit direction of a local MEP
To calculate packet loss ratio in the receive and transmit directions of a local MEP, an MEP maintains the
following two local counters:
l TxFCl: counts packets transmitted to the opposite MEP.
l RxFCl: counts packets received from the opposite MEP.
NOTE
A maintenance intermediate point (MIP) transparently transmits packets with ETH-LMM and ETH-LMR
information, without the need to support LM.
Figure 6-12 shows the single-ended LM process.

NOTE
The following considers MEP (PE1) as an example to illustrate the single-ended LM process. The same
process goes to MEP (PE2).
Issue 03 (2012-11-30)

212
OptiX OSN 7500 II/7500/3500/1500

6 ETH-OAM
Figure 6-12 Single-ended LM process

Transmission
network
CE1
PE1
PE2
1. Sending an ETH-LMM frame
CE2
Information carried in the frame:
TxFCf
2. Sending an ETH-LMR frame
TxFCf
RxFCf
TxFCb
: MEP
1.
A local MEP periodically sends an ETH-LMM frame to its opposite MEP. An ETH-LMM
frame contains the following values:
l TxFCf: value of local counter TxFCl at the time of ETH-LMM frame transmission
2.
When receiving a valid ETH-LMM frame, the opposite MEP transmits an ETH-LMR
frame. An ETH-LMR frame contains the following values:
l TxFCf: value of TxFCf copied from the ETH-LMM frame
l RxFCf: value of local counter RxFCl at the time of ETH-LMM frame reception
l TxFCb: value of local counter TxFCl at the time of ETH-LMR frame transmission
3.
Upon receiving an ETH-LMR frame, a local MEP uses the following values to make nearend and far-end loss measurements:
l Frame lossfar-end = |TxFCf[tc] - TxFCf[tp]| - |RxFCf[tc] - RxFCf[tp]|
l Frame lossnear-end = |TxFCb[tc] - TxFCb[tp]| - |RxFCl[tc] - RxFCl[tp]|
NOTE
l TxFCf[tc], RxFCf[tc], and TxFCb[tc] represent the received ETH-LMR frame's TxFCf, RxFCf,
and TxFCb respectively. RxFCl[tc] represents the local counter RxFCl value at the time this
ETH-LMR frame was received, where tc is the reception time of the current ETH-LMR frame.
l TxFCf[tp], RxFCf[tp], and TxFCb[tp] represent the previous ETH-LMR frame's TxFCf, RxFCf,
and TxFCb respectively. RxFCl[tp] represents the local counter RxFCl value at the time the
previous ETH-LMR frame was received, where tp is the reception time of the previous ETHLMR frame.
FLR
FLR is a measure of the packet loss ratio between two MEPs that belong to the same CoS instance
on a point-to-point ETH connection. During the LM, a local MEP counts lost packets, and records
the total number of transmitted packets.
FLR is calculated as follows.
FLR = Frame loss/Total number of transmitted packets
Two-Way DM
Two-way DM can be used to measure frame delay and frame delay variation of bidirectional
service packets on an Ethernet link within a specified period of time.
Issue 03 (2012-11-30)

213
OptiX OSN 7500 II/7500/3500/1500

6 ETH-OAM
NOTE
DM can be performed in two ways: two-way DM and one-way DM. Currently, the OptiX OSN equipment
supports two-way DM only. To learn about one-way DM, see ITU-T Y.1731, OAM functions and
mechanisms for Ethernet based networks.
Two-way DM is used for on-demand OAM. That is, a two-way DM test is manually triggered.
In this mode, a local MEP, within a specified period of time, periodically sends packets with
ETH-DM request (ETH-DMM) information to its opposite MEP, and receives packets with
ETH-DM reply (ETH-DMR) information from its opposite MEP.
NOTE
An MIP transparently transmits packets with ETH-DMM and ETH-DMR information, without the need
to support DM.
Figure 6-13 shows the two-way DM process.

NOTE
The following considers MEP (PE1) as an example to illustrate the two-way DM process. The same process
goes to MEP (PE2).
Figure 6-13 Two-Way DM process

Transmission
network
CE1
PE1
1. Sending an ETH-DMM frame
2. Sending an ETH-DMR frame
PE2
CE2
Information carried in the frame:
TxTimeStampf
TxTimeStampf
RxTimeStampf
TxTimeStampb
: MEP
1.
A local MEP periodically sends an ETH-DMM frames to its opposite MEP. An ETH-DMM
frame contains the following values:
l TxTimeStampf: time of ETH-DMM frame transmission
2.
When receiving a valid ETH-DMM frame, the opposite MEP transmits an ETH-DMR
frame. An ETH-LMR frame contains the following values:
l TxTimeStampf: value of TxTimeStampf copied from the ETH-DMM frame
l RxTimeStampf: time of ETH-DMM frame reception
l TxTimeStampb: time of ETH-DMR frame transmission
3.
Upon receiving an ETH-DMR frame, a local MEP uses the following values to make frame
delay measurements:
l Frame delay = RxTimeb - TxTimeStampf (RxTimeb represents the reception time of
the ETH-DMR frame.)
This value contains the time the opposite node handles the DM packet, and serves as
input for frame delay variation measurement.
l Frame delay = (RxTimeb - TxTimeStampf) - (TxTimeStampb - RxTimeStampf)
Issue 03 (2012-11-30)

214
OptiX OSN 7500 II/7500/3500/1500

6 ETH-OAM
This value does not contain the time the opposite node handles the DM packet, and is
more accurate.
FDV
FDV is a measure of the delay variations of service packets between two MEPs that belong to
the same CoS instance on a point-to-point ETH connection. During the DM, a local MEP
measures frame delays, and records the maximum frame delay and minimum frame delay.
FDV is calculated as follows.
FDV = Frame delaymax - Frame delaymin

Ethernet service OAM implements end-to-end maintenance for specific services by network
section, which is used on CEs and PEs that Ethernet services traverse.
Figure 6-14 shows an application example of Ethernet service OAM for Ethernet line services.
Figure 6-14 EVPL (QinQ) service model
CE1
C_VLAN
PE1
Network A
C_VLAN
P1
CE2
S_VLAN_A1 C_VLAN
S_VLAN_A2 C_VLAN
P2
Network B
PE2
C_VLAN
CE3
S_VLAN_B1 C_VLAN
S_VLAN_B2 C_VLAN
C_VLAN
CE4
OptiX NE
CE1-CE4 refer to the equipment on the access side. The packets that are transmitted on the
operator network contain C_VLAN tags.
1.
Issue 03 (2012-11-30)
When these packets are transmitted to the operator network (PE equipment) in the uplink,
the S_VLAN tags defined by the operator are added to the packets for service grooming.
215
OptiX OSN 7500 II/7500/3500/1500

6 ETH-OAM
2.
When service packets are transmitted from one operator network to the other operator
network, the S_VLAN tags are replaced by the S_VLAN tags defined by the later operator.
3.
When service packets are transmitted from the operator network to the client-side
equipment in the downlink, the S_VLAN tags are stripped. At this time, the remote
transmission is complete.
The service transmission involves the equipment CE1-CE4 on the access side, operator network
A and operator network B. These entities have different requirements for the ETH-OAM.
l
Either operator needs to focus on OAM in their own network segments respectively and
does not focus on network segments of the other operator.
The user on the access side cares whether the service can be transmitted to the destination.
In this case, the state of the entire link needs to be detected.
As shown in Figure 6-15, multiple maintenance domains that are based on different VLAN
values are established. In this way, requirements of operators and users on the access side can
be met.
Figure 6-15 Maintenance domains based on different VLAN values
CE1/CE2
CE3/CE4
C_VLAN
Maintenance domain 1
MEP1
MEP2
Level = 5-7
PE1
MEP3
S_VLAN_A1
P1
P2
PE2
MEP4
MEP7
S_VLAN_A2
MEP8
S_VLAN_B2
MEP5
S_VLAN_B1
MEP6
MEP9
MEP10
Level = 0-4
User on the access side: Maintenance domain 1 that is based on the C_VLAN value between
access side equipment CEs at two ends of transmission network is created. Because
maintenance domain 1 covers maintenance domains 2-5 of the network operator, its
maintenance point level must be higher than levels of maintenance domains 2-5. In this
manner, the OAM packets of maintenance domain 1 are not interrupted by MEPs of
maintenance domains 2-5.
Operator network A: Network A carries two services: SVLAN_A1 and SVLAN_A2. By

establishing mutually independent maintenance domains 2 and 3, network A can manage
two services respectively. The two maintenance domains replace the C_VLAN tag with
the S_VLAN tag.
Issue 03 (2012-11-30)

216
OptiX OSN 7500 II/7500/3500/1500

6 ETH-OAM
Operator network B: Network B carries two services: S_VLAN_B1 and S_VLAN_B2. By

establishing mutually independent maintenance domains 4 and 5, network B can manage
two services respectively. The two maintenance domains suppress the C_VLAN tag and
take the S_VLAN tag as the identifier.
Ethernet service processing boards of OptiX NG-SDH series equipment provide the ETH-OAM
function, and thus maintenance domains 4 and 5 are based on the S_VLAN tags. For services
that have multiple VLAN tags, only the most external tag is identified. Thus, the most external
tag is considered as the VLAN tag of a service.
The layered management principle defines that the upper level management domain can cross
the lower level management domain, but the lower level management domain cannot cross the
upper level management domain. In this case, the level of maintenance domain 1 must be higher
than levels of other maintenance domains. For maintenance domains 2-5, they can be set to the
same level because their domains do not overlap. For example, maintenance domains 2 and 4
are in the same level, and maintenance domains 3 and 5 are at the same level. Maintenance
domains 2-5 carry different S_VLAN tags, and thus they do not affect each other.
6.3.7 Configuring Ethernet Service OAM

This topic describes how to configure the Ethernet service OAM for the packet transmission
service.
6.3.7.1 Creating an MD
An MD defines the range and level of the Ethernet OAM. MDs of different ranges and levels
can provide users with differentiated OAM services.
Prerequisites
Procedure
Step 1 Select the NE in the NE Explorer. Choose Configuration > Packet Configuration > Ethernet
OAM Management > Ethernet Service OAM Management from the Function Tree.
Step 2 Click New, and select New Maintenance Domain.
Step 3 When the New Maintenance Domain dialog box is displayed, set Maintenance Domain
Name and Maintenance Domain Level.
NOTE
When setting these parameters, note the following points:

Maintenance Domain Level: The value ranges from 0 to 7, and 7 indicates the highest priority.
Step 4 Click Apply. The Operation Result dialog box is displayed, indicating that the operation is
successful.
Step 5 Click Close.
----End
Issue 03 (2012-11-30)

217
OptiX OSN 7500 II/7500/3500/1500

6 ETH-OAM
6.3.7.2 Creating an MA
An MD can be divided into several independent MAs. By creating MAs, you can associate
specific Ethernet services with MAs. This facilitates Ethernet OAM operations.
Prerequisites
l
The Ethernet service must be created.
The MD must be created.
Procedure
Step 2 Click New, and select New Maintenance Association.
Step 3 When the New Maintenance Association dialog box is displayed, set the required parameters.
NOTE

CC Test Transmit Period: This parameter specifies the duration of a CC test and can be set.
successful.
Step 5 Click Close.
----End
6.3.7.3 Creating an MEP

The Ethernet OAM detects the connectivity of a channel based on the MEPs at the two ends of
this channel. An MEP initiates and terminates the Ethernet OAM packet. After an MEP is created
successfully, you can check the connectivity of a channel segment within an MA.
Prerequisites
l
The MA must be created.
Procedure
Step 2 Select the created MA, click New, and select New MEP Maintenance Point.
Step 3 When the New MEP Maintenance Point dialog box is displayed, set the required parameters.
Issue 03 (2012-11-30)

218
OptiX OSN 7500 II/7500/3500/1500

6 ETH-OAM
NOTE

l Direction: When this parameter is set to Ingress, the packet is transmitted to the network side. When
this parameter is set to Egress, the packet is transmitted to the user side.
l CC Status: When this parameter is set to Active, the link can be checked in real time.
Step 4 Click Apply. The Operation Result is displayed, indicating that the operation is successful.
Step 5 Click Close.
----End
6.3.7.4 Adding a Remote MEP

A remote maintenance association MEP is intended to confirm that the OAM packet is initiated
from the MEP of the same MA when the MEP processes an OAM packet.
Prerequisites
l
An MA must be created.
Procedure
Step 1 In the NE Explorer, select an NE. Then, choose Configuration > Packet Configuration >
Ethernet OAM Management > Ethernet Service OAM Management in the Function Tree.
Step 2 Click OAM and select Manage Remote MEP Point. The Manage Remote Maintenance
Point dialog box is displayed.
Step 3 Set the relevant parameters.
Step 4 Click Apply. Then, the Operation Result dialog box is displayed, indicating that the operation
is successful.
Step 5 Click Close.
----End
6.3.7.5 Performing a Continuity Check

You can perform a continuity check for the Ethernet service to check the continuity of the service
and to facilitate fault location and rectifying.
Prerequisites
l
The OAM maintenance node must be created.
Procedure
Step 2 Select Maintenance Domain, and select Maintenance Association. Select MEP Point.
Issue 03 (2012-11-30)

219
OptiX OSN 7500 II/7500/3500/1500

6 ETH-OAM
Step 3 Click OAM, and select Activate CC from the drop-down list. The Operation Result dialog
box is displayed, indicating that the operation is successful.
Step 4 Click Close.
----End
6.3.7.6 Performing an LB Test

You can perform an LB test for the Ethernet service without service interruptions, to check the
continuity of the service and to facilitate fault location and rectifying.
Prerequisites
l
Procedure
Step 3 Click OAM, and choose Start LB from the drop-down list. The LB Test dialog box is displayed.
Step 4 Set the required parameters. For the parameters to be set, see 6.3.9.2 Starting LB.
NOTE
l To identify the destination MP according to the MP ID, select Destination Maintenance Point ID.
l To identify the destination MP according to the MAC address, select Destination Maintenance Point
MAC Address. After selecting Destination Maintenance Point MAC Address, manually copy the
MAC address of the port at which the sink MP is configured to the value field of Destination
Maintenance Point MAC Address. See Setting the Advanced Attributes of Ethernet Ports for the
navigation path of the MAC address of the port at which the sink MEP is configured.
Step 5 Click Start Test. The Operation Result dialog box is displayed, indicating that the operation
is successful.
Step 6 Click Close. Check the test result.
Issue 03 (2012-11-30)

220
OptiX OSN 7500 II/7500/3500/1500

6 ETH-OAM
----End
6.3.7.7 Performing an LT Test

You can perform an LT test for the Ethernet service to detect the MIP information of the link
and to facilitate fault location and rectifying.
Prerequisites
l
Procedure
Step 3 Click OAM, and choose Start LT from the drop-down list. The LT Test dialog box is displayed.
Step 4 Set the required parameters. For the parameters to be set, see 6.3.9.3 Starting LT.
NOTE
l To identify the destination MP according to the MP ID, select Destination Maintenance Point ID.
l To identify the destination MP according to the MAC address, select Destination Maintenance Point
MAC Address. After selecting Destination Maintenance Point MAC Address, manually copy the
MAC address of the port at which the sink MP is configured to the value field of Destination
Maintenance Point MAC Address. See Setting the Advanced Attributes of Ethernet Ports for the
navigation path of the MAC address of the port at which the sink MEP is configured.
Step 5 Click Start Test. The Operation Result dialog box is displayed, indicating that the operation
is successful.
Step 6 Click Close. Check the test result.
Issue 03 (2012-11-30)

221
OptiX OSN 7500 II/7500/3500/1500

6 ETH-OAM
----End

This topic describes the alarms and performance events that are related to the Ethernet service
OAM function.

This topic describes the alarms that are related to the Ethernet service OAM function.
Table 6-7 lists the alarms that are related to the Ethernet service OAM function.
Table 6-7 Alarms related to the Ethernet service OAM function
Issue 03 (2012-11-30)
Alarm Name
Description
EX_ETHOAM_CC_LOS
This alarm indicating the loss of the periodic continuity

check message. When the sink maintenance point
receives the continuity check (CC) message from the
source maintenance point, the timer is started to
periodically check the link between the source and sink
maintenance points. If the sink maintenance point does
not receive the CC message from the source
maintenance point in one period (3.5 times of the time
during which the CC message is transmitted from the
source maintenance point to the sink maintenance
point), this alarm occurs.
EX_ETHOAM_MPID_CNFLCT
This alarm indicating the maintenance point ID

conflict. When a maintenance point receives the
message sent by another maintenance point with the
same MPID in a maintenance domain, this alarm
occurs.
ETH_CFM_LOC
This alarm indicating the loss of connectivity. This

alarm is reported when the system does not receive
CCM packets from the remote MEP in the 3.5xCC
period.
ETH_CFM_MISMERGE
This alarm indicating that the connection is incorrect.

This alarm is reported when the system receives the
continuity check message (CCM) packets with
mismatched maintenance association (MA) ID or the
CCM packets of a lower level.
ETH_CFM_RDI
This alarm indicating that the function of receiving the

CCM packets of the remote MEP fails. This alarm is
reported when the system receives the CCM packets
with RDI transmitted from the remote end.

222
OptiX OSN 7500 II/7500/3500/1500

6 ETH-OAM
Alarm Name
Description
ETH_CFM_UNEXPERI
This alarm indicating the errored frame. This alarm is

reported when the system receives invalid CCM
packets.
ETH_EFM_DF
This alarm indicates discovery failure. This alarm is

reported when the negotiation of the P2P OAM
protocol fails at a port.
ETH_EFM_EVENT
This alarm indicates that an event occurs on the

opposite NE. This alarm is reported when the P2P
OAM protocol is enabled and the local end receives an
event indication from the opposite end.
ETH_EFM_LOOPBACK
This alarm indicates loopback. This alarm is reported

when the P2P OAM protocol is enabled and the local
end initiates a loopback or performs a loopback at the
request from the opposite end. If the ports at both ends
can respond to the loopback,
l The local OAM port receives the remote loopback
control enable commandissued by the opposite
OAM port, responds to the command, and reports
the corresponding alarm, and the opposite port
reports the alarm indicating the initiation of the
loopback.
l The local OAM port receives the remote loopback
control disable commandissued by the opposite
OAM port, responds to the command, and clears the
corresponding alarm, and the opposite port clears
the alarm indicating the initiation of the loopback.
ETH_EFM_REMFAULT
This alarm indicates that the opposite NE is faulty. This

alarm is reported when the P2P OAM protocol is
enabled and the local end receives a fault indication
from the opposite end.

This topic describes the performance events that are related to the Ethernet service OAM
function.
Table 6-8 lists the performance events that are related to the Ethernet service OAM function.
Table 6-8 Performance Events related to the Ethernet service OAM function
Issue 03 (2012-11-30)
Description
ETH_CFM_CSLS
The consecutive severe packet loss seconds of the ELine service.
ETH_CFM_LS
The packet loss seconds of the E-Line service.

223
OptiX OSN 7500 II/7500/3500/1500

6 ETH-OAM
Description
ETH_CFM_SLS
The severe packet loss seconds of the E-Line service.
ETH_CFM_UAS
The unavailable seconds of the E-Line service.
6.3.9 Parameter Description: Ethernet Service OAM

6.3.9.1 Ethernet Service OAM Management

In this interface, you can query, create, delete, and modify the maintenance points, and can
trigger the OAM maintenance function.
Table 6-9 lists the parameters for Ethernet service OAM management.
Table 6-9 Parameters for Ethernet Service OAM Management
Field
Value
Description
Maintenance Domain Name
8 bytes
Sets the name of the

maintenance domain.
Maintenance Domain Level
0-7
The Maintenance Domain

Level parameter indicates the
level of the maintenance
domain (MD). The MD level
restricts the usage scope of
the OAM.
Default: 4
Click A.6.2 Maintenance

Domain Level(Ethernet
Service OAM
Management) for more
information.
Maintenance Association
Name
8 bytes
Sets the name of the

maintenance association.
Relevant Service
Service ID + Service name.

For example, 10-service
Selects relevant service.
CC Test Transmit Period
3.33 ms, 10 ms, 100 ms, 1s,

10s, 1m, 10m
Sets the transmit period for

the CC test.
Perform the CC test to check
the service connectivity.
Issue 03 (2012-11-30)
Node
For example, 21-N1PETF8-1

(Port-1)
Sets the MEP node.
VLAN
For example, 5
Displays the VLAN of the

monitored service.

224
OptiX OSN 7500 II/7500/3500/1500

6 ETH-OAM
Field
Value
Description
MP ID
For example, 6
Sets the ID of the MP.

The MP includes the MEP
and MIP.
Direction
Ingress, Egress
Sets the direction of the MEP.

Ingress indicates the node incoming direction.
Egress indicates the node
out-going direction.
CC Status
Active, Inactive
Default: Active
The CC Status parameter

indicates whether the CC
check function of this MEP is
activated.
Click A.6.3 CC Status
(Ethernet Service OAM
information.
Board
For example, 1-N1PEG16
Sets the board.
Port
For example, 1-N1PEG16-8

(Port-8)
Sets the port.
Service ID
For example, 10
Displays the Service ID.
Service Name
A character string of not

more than 64 characters
The Service Name

parameter indicates the type
of the service to be detected
by the OAM during the
creation of an MA.
Click A.6.4 Service Name
information.
Service Type
E-Line, E-LAN, E-AGGR
The Service Type parameter

indicates the type of the
service to be detected by the
OAM during the creation of
an MA.
Click A.6.5 Service Type
information.
Issue 03 (2012-11-30)

225
OptiX OSN 7500 II/7500/3500/1500

6 ETH-OAM
Field
Value
Description
Activation Status
Active, Inactive
The Activation Status

parameter indicates whether
to send the CC packet. The
CC packet refers to service
connectivity checking
packet.
Default: Active
Click A.6.6 Activation

Status(Ethernet Service
OAM Management) for
more information.
6.3.9.2 Starting LB
Perform loopback for the Ethernet service without interrupting the service to check the
connectivity of the service and thus to locate and rectify the fault.
Table 6-10 list the parameters for starting LB.
Table 6-10 Parameters for starting LB
Field
Value
Description
8 bytes
Displays the name of the

maintenance domain.
Name
8 bytes

Source Maintenance Point ID
For example, 5
Sets the source maintenance

point ID for the LB test.
Destination Maintenance
Point MAC Address
Any valid destination unicast

MAC address
The Destination
Maintenance Point MAC
Address parameter indicates
the MAC address of the port
where the destination
maintenance point (MP) is
located.
Click A.6.10 Destination
Address(Ethernet Service
OAM Management) for
more information.
Issue 03 (2012-11-30)

226
OptiX OSN 7500 II/7500/3500/1500

6 ETH-OAM
Field
Value
Description
Transmitted Packet Count
1-255
The Transmitted Packet

Count parameter indicates
the number of the transmitted
loopback message (LBM).
Default: 3
Click A.6.7 Transmitted

Packet Count(Ethernet
Service OAM
information.
Transmitted Packet Length
64-1400
Default: 64

Length parameter indicates
the length of the transmitted
loopback message (LBM).
Packet Length(Ethernet
Service OAM
information.
Transmitted Packet Priority
0-7
Default: 7

Priority (Ethernet Service
OAM) parameter indicates
the VLAN priority in the
Ethernet service OAM
protocol packets transmitted
by the equipment.
Packet Priority (Ethernet
Service OAM
information.
Test Result
Character string
Confirms the connectivity of

the service flow from the
source maintenance point to
the destination maintenance
point.
6.3.9.3 Starting LT
Perform loopback trace for the Ethernet service without interrupting the service to check the
connectivity of the service and thus to locate and rectify the fault.
Table 6-11 lists the parameters for starting LT.
Issue 03 (2012-11-30)

227
OptiX OSN 7500 II/7500/3500/1500

6 ETH-OAM
Table 6-11 Parameters for starting LT

Field
Value
Description
8 bytes

maintenance domain.
Name
8 bytes

Source Maintenance Point ID
For example, 5
Sets the source maintenance

point for the LT test.
The source maintenance
point starts the LT test.
Point MAC Address
Any valid destination unicast

MAC address
The Destination
Address parameter indicates
the MAC address of the port
where the destination
maintenance point (MP) is
located.
Click A.6.10 Destination
Address(Ethernet Service
OAM Management) for
more information.
Point ID/MAC
For example,
1A-2B-3C-4D-5E-6F
Displays the sink

maintenance point for the LT
test.
Response Maintenance Point

ID
Indicates the MAC address of

the port.
The Response Maintenance

Point ID parameter identifies
the response MP according to
the MAC address.
Click A.6.11 Response
Maintenance Point ID
information.
Issue 03 (2012-11-30)

228
OptiX OSN 7500 II/7500/3500/1500

6 ETH-OAM
Field
Value
Description
Hop Count
1-64, /
The hop count, also called

time to live (TTL), is carried
with the OAM packets. The
Hop Count parameter
indicates the connection from
the response MP to the source
MP. On the trail from the
source MP to the destination
MP, the hop count for the
packets decreases by one
when the packets pass
through each maintenance
intermediate point (MIP).
Default: /
Click A.6.12 Hop Count

information.
Test Result
Character string
The Test Result parameter

indicates the trail information
about the link connection
from the source maintenance
point to the destination
maintenance point during the
LT test. If the trail from the
source maintenance point to
the destination maintenance
point cannot be obtained, the
operation failure information
is reported. If the trail from
the source maintenance point
to the destination
maintenance point transits
the intermediate equipment
or destination equipment, the
operation success
information is reported.
Click A.6.13 Test Result
information.
Issue 03 (2012-11-30)

229
OptiX OSN 7500 II/7500/3500/1500

7 MPLS OAM
MPLS OAM
About This Chapter

The MPLS OAM technology provides a defect detection tool and a defect correction mechanism
for the MPLS network. You can perform the detection function of the forwarding plane through
the MPLS OAM and protection switching mechanism, and complete a protection switching in
50 ms after a defect occurs. In this way, the impact caused by the defect is minimized.
7.1 Introduction to MPLS OAM
The MPLS OAM mechanism supported by the equipment includes tunnel OAM and PW OAM.
Tunnel OAM operates at the tunnel layer, and PW OAM operates at the PW layer. Tunnel OAM
and PW OAM both provide the complete fault detection and locating mechanism, and network
performance monitoring function. According to the OAM detection status, the equipment can
trigger protection switching to quickly detect a fault and protect services against the fault.
7.2 Basic Concepts
The basic concepts of MPLS OAM include CV/FFD, Ping and Traceroute.
This topic describes the standards and protocols that MPLS OAM complies with.
7.4 Availability
The MPLS OAM function requires the support of the applicable equipment, boards, and
software.
This section describes the limitations on and precautions for MPLS OAM in the network design
7.6 Principles
This topic describes the principles of MPLS OAM.
7.7 Networking and Application
MPLS OAM provides end-to-end detection methods in the MPLS network.
7.8 Configuring the MPLS OAM
This section describes how to configure the MPLS OAM.
7.9 Configuring PW OAM
This topic describes how to configure PW OAM.
Issue 03 (2012-11-30)

230
OptiX OSN 7500 II/7500/3500/1500

7 MPLS OAM
7.10 Configuration Case of the MPLS OAM

The configuration case of MPLS OAM describes how to configure the MPLS OAM.
7.11 Configuration Example of PW OAM
This topic considers an example to describe how to configure PW OAM.
7.12 Parameter Description: MPLS OAM
7.13 Related Alarms and Performance Events
This topic describes alarms and performance events related to this feature.
Issue 03 (2012-11-30)

231
OptiX OSN 7500 II/7500/3500/1500

7 MPLS OAM
7.1 Introduction to MPLS OAM

The MPLS OAM mechanism supported by the equipment includes tunnel OAM and PW OAM.
Tunnel OAM operates at the tunnel layer, and PW OAM operates at the PW layer. Tunnel OAM
and PW OAM both provide the complete fault detection and locating mechanism, and network
performance monitoring function. According to the OAM detection status, the equipment can
trigger protection switching to quickly detect a fault and protect services against the fault.
Tunnel OAM
l
Description
The tunnel OAM mechanism helps to effectively detect, identify, and locate internal defects
at the tunnel layer of an MPLS network. The equipment triggers the protection switching
based on the OAM detection status. Therefore, quick fault detection and service protection
can be achieved.
Objectives and benefits

As a key bearer technology for the scalable next generation network (NGN), MPLS
provides multi-service capabilities with ensured QoS. In addition, MPLS introduces a
unique network layer (tunnel), which may cause some faults. Therefore, an MPLS network
must have the OAM capability.
By providing a tunnel OAM mechanism independent of any upper layer or lower layer, the
tunnel OAM supports the following features:
Provides query-on-demand and consecutive detections so that at any moment you can
learn whether the monitored tunnel has defects.
Detects, analyzes, and locates any defect that occurs, and notifies the NMS of the
relevant information.
Triggers a protection switching immediately after a defect or fault occurs on a link.
Monitors the performance events indicating packet loss ratio, delay, and jitter in real
time and reports them to the NMS.
PW OAM
l
Description
The PW OAM mechanism helps to effectively detect, identify, and locate internal defects
at the PW layer of a network. The equipment triggers the protection switching based on the
OAM detection status. Therefore, quick fault detection and service protection can be
achieved.
Objectives and benefits

The equipment performs PW encapsulation on service packets, and then transmits the
service packets over tunnels. The network consists of two layers: tunnel and PW. Tunnels
use tunnel OAM for maintenance and management, and PWs use PW OAM for
maintenance and management. Currently, the equipment can detect the connectivity of a
certain PW through ping packets and traceroute packets, and then reports the result to the
NMS.
The local equipment encapsulates ping packets or traceroute packets into PWs and then
transmits the packets over tunnels. After receiving the tunnel packets, the opposite
equipment decapsulates and handles the packets, encapsulates response packets, and then
Issue 03 (2012-11-30)

232
OptiX OSN 7500 II/7500/3500/1500

7 MPLS OAM
sends the response packets to the local equipment. The local equipment can determine that
the PW connectivity is normal only after receiving the response packets.
7.2 Basic Concepts

The basic concepts of MPLS OAM include CV/FFD, Ping and Traceroute.
7.2.1 Packet Types

In MPLS OAM, the commonly used packets include connectivity verification (CV) packets, fast
failure detection (FFD) packets, forward defect indication (FDI) packets, and backward defect
indication (BDI) packets.
l
CV packet
CV packets are used to check connectivity of LSPs. The ingress node sends CV packets at
an interval of 1s, and the egress node checks the number of received CV packets and
correctness of the CV packets in any 3s.
Figure 7-1 shows the format of a CV packet.
Figure 7-1 Format of a CV packet

0
19
Label: 14 (OAM alert label)
Function type (0x01)
31 bit
22 23
EXP S
TTL: 1
Reserved (all 0x00)

7
TTSI (20 octets)
Padding (all 0x00)

(18 octets)
BIP 16 (2 octets)
OAM packet header
The fields of a CV packet are as follows:

Label: The value of the field is 14 and indicates an OAM packet.
Time to Live (TTL): The value of the field is set to 1, to ensure that the MPLS OAM
packet is not transmitted beyond the sink end of the monitored LSP.
Function type: The value of the field is set to 0x01, indicating that the OAM packet type
is CV.
Issue 03 (2012-11-30)

233
OptiX OSN 7500 II/7500/3500/1500

7 MPLS OAM
Trail termination source identifier (TTSI): TTSI consists of the LSR ID and LSP ID of
the ingress node. It is used to uniquely identify an LSP on a network.
16-bit interleaved parity (BIP 16): If a CV packet contains an incorrect BIP 16, the
receiver discards the packet. When CV packets are continuously discarded due to
incorrect BIP 16s, the equipment will notify the NMS.
Reserved: The reserved field is reserved for future use and is set to all 0s.
Padding: The field is for padding bytes and is set to all 0s.
l
FFD packet
FFD packets are also used to check connectivity of LSPs. The ingress node sends FFD
packets at an interval of 3.3 ms to 500 ms, and the egress node checks the number of received
FFD packets and correctness of the FFD packets in any three packet transmission periods.
The transmission interval can be 3.3 ms, 10 ms, 20 ms, 50 ms, 100 ms, 200 ms, or 500 ms.
Figure 7-2 shows the format of an FFD packet.
Figure 7-2 Format of an FFD packet

0
19
Label: 14 (OAM alert label)
Function type (0x07)
22 23
EXP S
31
bit
TTL: 1
Reserved (all 0x00)

7
TTSI (20 octets)
Frequency (1 octet)
Padding (all 0x00)
(17 octets)
BIP 16 (2 octets)
OAM packet header
Table 7-1 provides the differences between an FFD packet and a CV packet.
Table 7-1 Format differences between an FFD packet and a CV packet
Issue 03 (2012-11-30)
Field
CV Packet
FFD Packet
Function type
The field is set to 0x01,

indicating that the OAM
packet type is CV.
The field is set to 0x07,

indicating that the OAM
packet type is FFD.

234
OptiX OSN 7500 II/7500/3500/1500

7 MPLS OAM
Field
CV Packet
FFD Packet
Frequency
None.
The frequency field

indicates that the FFD
packet can support several
transmit intervals.
FDI packet
Generated by LSRs that detect defects, an FDI packet is used to respond to defects detected
by transmitting CV or FFD packets. FDI packets help to prevent the affected LSP from
generating an alarm.
An LSR generates an FDI packet to notify the egress node of the fault.
After the OAM function is disabled for the ingress node, an FDI packet is generated to
notify the egress node. After the OAM adaptive mode is enabled for the egress node,
the egress node responds to the FDI packet and stops OAM detection.
BDI packet
After detecting a defect, the egress node transmits a BDI packet that carries the defect
information to the upstream ingress node along a reverse tunnel.
7.2.2 Reverse Tunnel

A reverse tunnel is a tunnel that has opposite ingress and egress nodes to the tunnel being
checked. A reverse tunnel is generally used to carry BDI packets.
Bind a reverse tunnel to the tunnel being checked when you configure basic detection functions
of MPLS OAM.
Reverse tunnels are classified into the following types:
l
Dedicated reverse tunnel

A dedicated reverse tunnel serves only one forward tunnel. This method is fairly stable but
may waste resources.
Shared reverse tunnel

A shared reverse tunnel serves many forward tunnels, and BDI packets of all the forward
tunnels are transmitted over the reverse tunnel. This method improves resource utilization;
congestion, however, may occur on the reverse tunnel when failures occur on multiple
forward tunnels at the same time.
Currently, the equipment supports only the dedicated reverse tunnel.
7.2.3 Ping
The ping function helps to check connectivity of links, tunnels, and virtual circuits. With a similar
implementation method, the tunnel ping and PW ping functions are applicable to different layers
and detected objects. The tunnel ping function is commonly used at the MPLS layer, and the
PW ping function is commonly used at the PW layer.
Tunnel Ping
The tunnel ping function uses MPLS echo request and MPLS echo reply packets to check
availability of a tunnel. An MPLS echo request packet carries the forwarding equivalence class
Issue 03 (2012-11-30)

235
OptiX OSN 7500 II/7500/3500/1500

7 MPLS OAM
(FEC) information to be checked and is transmitted with other packets that also belong to this
FEC along the tunnel. In this way, this tunnel is checked.
When the tunnel ping function is used, an MPLS echo request packet is transmitted to the egress
node of the tunnel and then the control plane of the egress node checks whether the local node
is the egress of the FEC. The tunnel ping is used to check whether a tunnel is successfully created.
PW Ping
With a similar implementation method to the tunnel ping function, the PW ping function helps
you manually detect the connection status of a virtual circuit. If a PW fails to forward data, the
control plane in charge of creating the PW cannot detect this failure. In such scenarios, the PW
ping function works.
The PW ping function uses MPLS echo request and MPLS echo reply packets to check
availability of a PW. An MPLS echo request packet carries the FEC information to be checked
and is transmitted with other packets that also belong to this FEC along the PW. In this way,
this PW is checked.
7.2.4 Traceroute
Similar to the ping function, the MPLS traceroute function helps to check the connectivity of
MPLS tunnels. In addition, the MPLS traceroute function can locate a faulty node accurately.
MPLS Tunnel Traceroute

The MPLS tunnel traceroute function uses the MPLS echo request and MPLS echo reply packets
to check availability of a tunnel. An MPLS echo request packet carries the FEC information to
be checked and is transmitted with other packets that also belong to this FEC along the tunnel.
In this way, this tunnel is checked.
When the MPLS tunnel traceroute function is used, an MPLS echo request packet is transmitted
to each transit node and then the control plane of each transit node checks whether the local node
is the intermediate node of a tunnel. The MPLS tunnel traceroute function is used to locate a
fault on the network.
PW Traceroute
The PW traceroute function uses the MPLS echo request and MPLS echo reply packets to check
availability of a PW. An MPLS echo request packet carries the FEC information to be checked
and is transmitted with other packets that also belong to this FEC along the PW. In this way,
this PW is checked.

This topic describes the standards and protocols that MPLS OAM complies with.
MPLS OAM complies with the following standards and protocols:
l
Issue 03 (2012-11-30)
ITU-T Y.1711 Operation & Maintenance mechanism for MPLS networks

236
OptiX OSN 7500 II/7500/3500/1500

7 MPLS OAM
7.4 Availability
The MPLS OAM function requires the support of the applicable equipment, boards, and
software.
Version Support (MPLS Tunnel OAM)

Applicable Version
OptiX OSN 1500/3500
T2000
U2000
Applicable Version
OptiX OSN 7500
U2000
Applicable Version
OptiX OSN 7500 II
U2000
Version Support (MPLS PW OAM)
Issue 03 (2012-11-30)
Applicable Version
OptiX OSN 1500/3500/7500
U2000
Applicable Version
OptiX OSN 7500 II
U2000

237
OptiX OSN 7500 II/7500/3500/1500

7 MPLS OAM
Hardware Support (MPLS Tunnel OAM)

Applicable
Board
Applicable Version
N1PEG16
OptiX OSN 3500
N1PEX1
OptiX OSN 3500
N1PETF8
OptiX OSN 3500/7500
R1PEFS8
Q1PEGS2
R1PEGS1
N1PEG8
OptiX OSN 3500/7500
N2PEX1
OptiX OSN 3500/7500
N1PEX2
OptiX OSN 3500/7500
N1PEFF8
OptiX OSN 3500/7500
R1PEF4F
TNN1EX2
OptiX OSN 7500 II
TNN1EG8
OptiX OSN 7500 II
TNN1ETMC
OptiX OSN 7500 II
TNN1EFF8
OptiX OSN 7500 II
Hardware Support (MPLS PW OAM)
Issue 03 (2012-11-30)
Applicable
Board
Applicable Version
N1PETF8
OptiX OSN 3500/7500
R1PEFS8
Q1PEGS2
R1PEGS1
N1PEG8
OptiX OSN 3500/7500
N2PEX1
OptiX OSN 3500/7500
N1PEX2
OptiX OSN 3500/7500
N1PEFF8
OptiX OSN 3500/7500
R1PEF4F

238
OptiX OSN 7500 II/7500/3500/1500

7 MPLS OAM
Applicable
Board
Applicable Version
TNN1EX2
OptiX OSN 7500 II
TNN1EG8
OptiX OSN 7500 II
TNN1ETMC
OptiX OSN 7500 II
TNN1EFF8
OptiX OSN 7500 II

This section describes the limitations on and precautions for MPLS OAM in the network design
Issue 03 (2012-11-30)
Applicable
Object

Details
Remarks
Tunnel OAM
and PW OAM
PW OAM and tunnel OAM can

coexist.
Tunnel OAM
Tunnel OAM works after being

enabled on the ingress and egress
nodes. The forward tunnel and
reverse tunnel must be on the same
board.
Tunnel OAM
To achieve fast fault detection for

MPLS APS, configure FFD packets
as detection packets on ingress
nodes. To ensure that the APS
switching time is less than 50 ms, set
the FFD packet transmission
interval to 3.3 ms. If the frame delay
variation on a tunnel exceeds 3.3 ms,
the transmission interval of FFD
packets is a value greater than the
frame delay variation.
Tunnel OAM
To achieve constant fault detection

for key MPLS tunnels, configure
CV packets as detection packets on
ingress nodes. If there are special
requirements on the transmission
interval of detection packets, FFD
packets can be used instead of CV
packets and the transmission
interval can be specified as required.

239
OptiX OSN 7500 II/7500/3500/1500

Issue 03 (2012-11-30)
7 MPLS OAM
Applicable
Object

Details
Remarks
Tunnel OAM
If tunnel OAM is applied to a

unidirectional MPLS tunnel,
configure the reverse tunnel so that
the egress node can send BDI
packets to the ingress node. Forward
and reverse tunnels cannot be
configured on different boards.
Tunnel OAM
It is recommended that the detection

mode of tunnel OAM should be
manual. That is, tunnel OAM
detection is manually triggered.
Tunnel OAM
It is recommended that the SD and

SF thresholds of tunnel OAM take
the default value 0. The SD and SF
thresholds of tunnel OAM are set
only when bit error rates are used to
determine the status of tunnels.
Tunnel OAM
Unless otherwise specified, the

forward defect indication (FDI)
function should be enabled on each
NE.
PW OAM
Unless MS-PW is configured, PW

OAM should be enabled on each
PW.
PW OAM
PW OAM works after the PW OAM

function is enabled on the local PE
and opposite PE. The PW OAM
configuration is the same on the two
PEs.
PW OAM
To achieve fast fault detection for

PW APS, configure FFD packets as
detection packets. To ensure that the
APS switching time is less than 50
ms, set the FFD packet transmission
interval to 3.3 ms. If the frame delay
variation on a PW exceeds 3.3 ms,
PW OAM
To achieve fast fault detection on

service networks for LPT, configure
FFD packets as detection packets for
PW OAM and set the transmission
interval as required.

240
OptiX OSN 7500 II/7500/3500/1500

7 MPLS OAM
Applicable
Object

Details
Remarks
PW OAM
It is recommended that the detection

mode of PW OAM should be
manual. That is, PW OAM detection
is manually triggered.
PW OAM
It is recommended that the SD and

SF thresholds of PW OAM take the
default value 0. The SD and SF
thresholds of PW OAM are set only
when bit error rates are used to
determine the status of PWs.

Applicable
Object

Details
Remarks
PW OAM
If PW OAM is enabled on a single

NE and PW OAM packets need to
traverse an MS-PW, set LSR ID to
be Received and PW ID to be
Received.
PW OAM
If Ethernet port OAM is required to

trigger interworking function
(IWF), configure Ethernet port
OAM on the UNI side and ensure
that the OAM protocol is negotiated
successfully.
Tunnel OAM
If a tunnel ping test is performed on

a unidirectional tunnel, the DCN
channels on the port involved must
not be shut down.
None.
7.6 Principles
This topic describes the principles of MPLS OAM.
Checking Process of MPLS OAM

Figure 7-3 shows the process of CV/FFD packet detection.
Issue 03 (2012-11-30)

241
OptiX OSN 7500 II/7500/3500/1500

7 MPLS OAM
Figure 7-3 Connectivity check of MPLS OAM

Ingress
LSR
CV/FFD
BDI
Transit
LSR
LSP
CV/FFD
Egress
LSR
BDI
The CV/FFD packet detection is performed as follows:

1.
The ingress LSR transmits a CV/FFD packet.
2.
The transit LSR transparently transmits the CV/FFD packet.
3.
The egress LSR receives the CV/FFD packet.
4.
The egress LSR compares the received information fields, such as packet types and
frequencies, with the fields recorded locally to check correctness of the packet. The egress
LSR also counts numbers of correct packets and incorrect packets during the detection
period. In this way, connectivity of a tunnel is monitored in real time.
5.
When detecting a defect on the tunnel, the egress LSR analyzes the defect type and transmits
the BDI packet that carries the defect information to the ingress LSR through the reverse
tunnel. The ingress node then can learn about the defect status in a timely manner.
NOTE
If a protection group is correctly configured, the corresponding protection switching is also triggered.
Principles of Tunnel Ping

As shown in Figure 7-4, MPLS ping can check whether a tunnel is successfully created.
Figure 7-4 Principles of tunnel ping
Ingress
LSR
Transit
LSR
Egress
LSR
MPLS Echo Request

MPLS Echo Reply
Tunnel ping works as follows:

1.
The ingress LSR transmits an MPLS echo request packet.
2.
The transit LSR forwards the MPLS echo request packet.

NOTE
If the transit LSR fails to forward the packet, it sends a reply message containing an error code.
Issue 03 (2012-11-30)

242
OptiX OSN 7500 II/7500/3500/1500

3.
7 MPLS OAM
The egress LSR processes the received MPLS echo request packet and returns an MPLS
echo reply packet.
Principles of Tunnel Traceroute

As shown in Figure 7-5, the MPLS traceroute function is used to locate a tunnel fault.
Figure 7-5 Principles of tunnel traceroute
Ingress
LSR
Transit
LSR
Egress
LSR
MPLS Echo Request

(TTL = 1)
MPLS Echo Reply
MPLS Echo Request
(TTL = 2)
MPLS Echo Reply
Tunnel traceroute works as follows:

1.
The ingress LSR transmits an MPLS echo request packet with its TTL being 1.
2.
The transit LSR processes the received MPLS echo request packet and returns an MPLS
echo reply packet.
NOTE
In this example, the transit LSR functions to terminate the MPLS echo request packet because TTL is
equal to 1. That is, the transit LSR does not transparently transmit the received packet.
3.
On reception the MPLS echo reply packet, the ingress LSR changes the value of TTL to 2
and transmits another MPLS echo request packet.
4.
The transit LSR forwards the MPLS echo request packet.

NOTE
The transit LSR functions as a transit node of the MPLS echo request packet because TTL is equal to 2.
That is, the transit LSR transparently transmits the received packet.
5.
The egress LSR processes the received MPLS echo request packet and returns an MPLS
echo reply packet.
PW Ping/Traceroute
The PW ping/traceroute function uses the MPLS echo request and MPLS echo reply packets to
validate a PW. The MPLS echo request packet carries the FEC information to be checked and
is transmitted with the other packets that also belong to this FEC along the PW. In this way, this
PW is checked.
Issue 03 (2012-11-30)

243
OptiX OSN 7500 II/7500/3500/1500

7 MPLS OAM
NOTE
The implementation of the PW ping/traceroute function is similar to the implementation of the tunnel ping/
traceroute function. Therefore, this topic does not describe the implementation process of the PW ping/
traceroute function.

MPLS OAM provides end-to-end detection methods in the MPLS network.
MPLS OAM is mainly applied to the LSP of the core layer in the PSN network. See Figure
7-6.
Figure 7-6 Application scenarios of MPLS OAM
Access Layer
Access Layer
P
PSN
CE
PE
PE
CE
CE
CE
P
Core Layer
Custom Layer
Custom Layer
LSP
Table 7-2 lists different application scenarios of the CV/FFD, Ping and Traceroute.
Table 7-2 Application scenarios of MPLS OAM detection methods
OAM Type
Usage
Application Scenario
CV/FFD
Unidirectional connectivity
check
Real-time detection of the

tunnel state
Ping
Bidirectional connectivity
check
Fault location or detection at

two ends.
Traceroute
Fault location
Tunnel route detection
7.8 Configuring the MPLS OAM

This section describes how to configure the MPLS OAM.
Issue 03 (2012-11-30)

244
OptiX OSN 7500 II/7500/3500/1500

7 MPLS OAM
7.8.1 Enabling MPLS Tunnel OAM

You need to enable the OAM function for a tunnel prior to any MPLS OAM operation.
Prerequisites
l
An MPLS tunnel must be created.
Procedure
Step 1 In the NE Explorer, select the required NE and choose Configuration > Packet
Configuration > MPLS Management > Unicast Tunnel Management from the Function
Tree.
Step 2 Click the OAM Parameters tab. In the OAM Status area, click Enabled.
successful.
Step 4 Click Close.
----End
7.8.2 Setting the MPLS Tunnel OAM Parameters

Based on different MPLS OAM parameters, the MPLS OAM operation results are different.
You need to set the MPLS OAM parameters before performing the MPLS OAM operation.
Prerequisites
l
You must enable the Tunnel OAM function.
Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > Packet Configuration > MPLS
Management > Unicast Tunnel Management from the Function Tree.
Step 2 Click the OAM Parameters tab and set the parameters.
Issue 03 (2012-11-30)

245
OptiX OSN 7500 II/7500/3500/1500

7 MPLS OAM
NOTE
Note the following during parameter settings:

l Detection Packet Period: When the Detection Packet Type is set to CV, the Detection Packet
Period is 1 s and cannot be set. When the Detection Packet Type is set to FFD, the Detection Packet
Period can be set.
l Reverse Tunnel: Send the BDI packets that carry the defect information to the ingress node so that
the ingress node can learn the defect status in time.
l When the Tunnel Type is set to Egress, you can set the SD Threshold and SF Threshold.
successful.
Step 4 Click Close.
----End
7.8.3 Starting a CV/FFD for an MPLS Tunnel

You can test the unidirectional connectivity of a tunnel by performing a CV/FFD.
Prerequisites
l
You must enable the MPLS OAM function.
Procedure
Configuration > MPLS Management > Unicast Tunnel Management from the Function
Tree.
Step 2 Click the OAM Parameters tab and select a tunnel. Click OAM Operation and choose Start
CV/FFD from the drop-down menu. The Operation Result dialog box is displayed, indicating
that the operation is successful.
NOTE
You can start a CV/FFD only for a tunnel whose Node Type is set to Ingress.
Step 3 Click Close.

----End
Issue 03 (2012-11-30)

246
OptiX OSN 7500 II/7500/3500/1500

7 MPLS OAM
7.8.4 Performing an MPLS Tunnel Ping Test

You can check whether a label switch path (LSP) is successfully created by performing an MPLS
tunnel ping test.
Prerequisites
l
Procedure
Step 2 Click the OAM Parameters tab and select a tunnel. Click OAM Operation and choose Ping
Test from the drop-down menu. The Ping Test dialog box is displayed.
NOTE
When the Node Type of the tunnel is Ingress, you can perform the ping test.
Step 3 Set the parameters.

Issue 03 (2012-11-30)

247
OptiX OSN 7500 II/7500/3500/1500

7 MPLS OAM
Step 4 Click Start Test. View the ping test result.

----End
7.8.5 Performing an MPLS Tunnel Traceroute Test

You can locate the place where a fault occurs by performing an MPLS tunnel traceroute test.
Prerequisites
l
Procedure
Step 2 Click the OAM Parameters tab and select a tunnel. Click OAM Operation and choose
Traceroute Test from the drop-down menu. The Traceroute Test dialog box is displayed.
Issue 03 (2012-11-30)

248
OptiX OSN 7500 II/7500/3500/1500

7 MPLS OAM
NOTE
To support the traceroute test, the Tunnel Type of the tunnel must be Ingress.
Step 3 Set the parameters.

Step 4 Click Start Test and view the traceroute test result.
----End
7.9 Configuring PW OAM

This topic describes how to configure PW OAM.
7.9.1 Enabling PW OAM

You need to enable the OAM function for a PW prior to any PW OAM operation.
Prerequisites
l
A PW must be created.
Procedure
Step 1 In the NE Explorer, select the required NE and then choose Configuration > Packet
Configuration > MPLS Management > PW Management from the Function Tree.
Step 2 Click the PW OAM Parameter tab. In the OAM Status area, click Enabled.
successful.
Step 4 Click Close.
----End
7.9.2 Setting the Parameters of PW OAM

You need to set the parameters of PW OAM so that you can monitor the status of a PW in real
time.
Prerequisites
l
PW OAM must be enabled.
Issue 03 (2012-11-30)

249
OptiX OSN 7500 II/7500/3500/1500

7 MPLS OAM
Procedure
Step 2 Click the PW OAM Parameter tab and set the parameters.
NOTE
l Detection Packet Period (ms): When Detection Mode is set to CV, Detection Packet Period (ms)
is always 1000 ms and cannot be changed; when Detection Mode is set to FFD, Detection Packet
Period (ms) can be set to a required value.
l When configuring Ethernet services carried by PWs, you can configure PW OAM if PW APS is
configured for the Ethernet services.
successful.
Step 4 Click Close.
----End
7.9.3 Performing a PW Ping Test

You can check the status of a PW by performing a PW ping test.
Prerequisites
l
Procedure
Step 2 Click the PW OAM Parameter tab and select a PW. Click OAM Operation and choose Ping
Test from the drop-down menu.
Step 3 In the Ping Test dialog box that is displayed, set the required parameters.
Issue 03 (2012-11-30)

250
OptiX OSN 7500 II/7500/3500/1500

7 MPLS OAM
Step 4 Click Start Test and view the ping test result.
NOTE
In the test result table, check information about the tested PW including the number of transmitted packets,
number of received packets, packet loss ratio, and delay information. The information helps you measure
the status of the PW.
----End
7.9.4 Performing a PW Traceroute Test

You can locate the place where a fault occurs by performing an PW traceroute test.
Prerequisites
l
Procedure
Step 2 Click the PW OAM Parameter tab and select a PW. Click OAM Operation and choose
Traceroute Test from the drop-down menu.
Step 3 In the Traceroute Test dialog box that is displayed, set the required parameters.
Issue 03 (2012-11-30)

251
OptiX OSN 7500 II/7500/3500/1500

7 MPLS OAM
Step 4 Click Start Test and view the traceroute test result.
----End
7.10 Configuration Case of the MPLS OAM

The configuration case of MPLS OAM describes how to configure the MPLS OAM.

The MPLS OAM is an OAM function for the tunnel. The check methods include CV/FFD,
Tunnel Ping and Tunnel Traceroute.
Networking and Requirement

In the MPLS network shown in Figure 7-7, NE1, NE2, NE3 and NE4 are the OptiX OSN 3500
NEs.
Issue 03 (2012-11-30)

252
OptiX OSN 7500 II/7500/3500/1500

7 MPLS OAM
A static tunnel, that is, Tunnel 1, is available on the path of NE1-NE2-NE4. The CV, Tunnel
Ping and Tunnel Traceroute check methods are used on Tunnel 1 through the MPLS OAM
mechanism. A static reverse tunnel, that is, Tunnel 3, is available on the path of NE4-NE2NE1. This tunnel is used to transmit the check results.
A static tunnel, that is, Tunnel 2, is available on the path of NE4-NE3-NE1. The FFD,
Tunnel Ping and Tunnel Traceroute check methods are used on Tunnel 2 through the MPLS
OAM mechanism. A static reverse tunnel, that is, Tunnel 4, is available on the path of NE1NE3-NE4. This tunnel is used to transmit the check results.
Figure 7-7 Networking diagram of the MPLS OAM
NE2
NE1
CompanyA
NE4
Company B
Forward LSP Tunnel

NE3
Reverse LSP Tunnel
Service Planning
he service shown in Figure 7-7is taken as an example.
l
NE1 initiates the CV, Tunnel Ping, and Tunnel Traceroute check. NE4 notifies NE1 of the
faults through the reverse tunnel, that is, Tunnel 3.
NE4 initiates the FFD check. NE1 notifies NE4 of the faults through the reverse tunnel,
that is, Tunnel 4.
Table 7-3 lists the configuration parameters of the MPLS OAM.

Table 7-3 Configuration parameters of the MPLS OAM
Issue 03 (2012-11-30)
Attribute
Value
NE
NE1
NE4
OAM Status
Enabled
Enabled
Detection Mode
Manual
Manual
Detection Packet Type
CV
FFD
Detection Packet Period(ms)
1000
500

253
OptiX OSN 7500 II/7500/3500/1500

7 MPLS OAM

This section describes the configuration process of the MPLS OAM in the configuration case.
Prerequisites
Procedure
Step 1 On the U2000, configure the MPLS OAM. For the configuration method, see 7.8.2 Setting the
MPLS Tunnel OAM Parameters.
The parameters of NE1 are as follows:
l OAM Status: Enabled
l Detection Mode: Manual
l Detection Packet Type: CV
l Detection Packet Period(ms): 1000
The parameters of NE4 are as follows:
l Detection Packet Type: FFD
l Detection Packet Period(ms): 500
Step 2 On NE1, enable the CV/FFD check for the tunnel. For details, see 7.8.3 Starting a CV/FFD
for an MPLS Tunnel.
Step 3 On NE4, enable the CV/FFD check for the tunnel. For details, see 7.8.3 Starting a CV/FFD
for an MPLS Tunnel.
Step 4 On NE1, perform the MPLS Tunnel Ping check. For details, see 7.8.4 Performing an MPLS
Tunnel Ping Test.
Step 5 On NE1, perform the MPLS Tunnel Traceroute check. For details, see 7.8.5 Performing an
MPLS Tunnel Traceroute Test.
----End
7.11 Configuration Example of PW OAM

This topic considers an example to describe how to configure PW OAM.
7.11.1 Description of the Example

PW OAM helps to monitor PWs in real time.

On a PSN network as shown in Figure 7-8, the Ethernet services between the NodeB and the
RNC are carried by PWs.
Issue 03 (2012-11-30)

254
OptiX OSN 7500 II/7500/3500/1500

7 MPLS OAM
A tunnel is configured between NE1 and NE2.
The tunnel contains two PWs. You can configure PW APS to protect the Ethernet services
between the NodeB and the RNC.
Figure 7-8 Networking diagram of PW OAM

PSN
PW1
NodeB
NE1
PW2
RNC
NE2
Tunnel
PW
Service Planning
The following table lists the configuration parameters of PW OAM.
Table 7-4 Configuration parameters of PW OAM
Parameter
Value
NE
NE1
NE2
OAM Status
Enabled
Enabled
Detection Mode
Manual
Manual
FFD
FFD
Detection Packet Period(ms)
3.3 ms
3.3 ms

This topic describes the configuration process of PW OAM based on the preceding example.
Prerequisites
You must be familiar with the networking, requirements, and service planning of the example.
Procedure
Step 1 Configure PW OAM. For the configuration method, see 7.9.2 Setting the Parameters of PW
OAM.
Issue 03 (2012-11-30)

255
OptiX OSN 7500 II/7500/3500/1500

7 MPLS OAM
Set the parameters of NE1 as follows:

l Detection Packet Period (ms): 3.3
Set the parameters of NE2 as follows:
l Detection Packet Period (ms): 3.3
Step 2 On NE1, perform a PW ping test. For details, see 7.9.3 Performing a PW Ping Test.
Step 3 On NE1, perform the PW traceroute test. For details, see 7.9.4 Performing a PW Traceroute
Test.
----End
7.12 Parameter Description: MPLS OAM

7.12.1 Tunnel OAM Parameters

The OAM parameters include Tunnel ID, Tunnel Name, Node Type, OAM Status, and other
parameters.
Table 7-5 lists the parameters for configuring the OAM function.
Table 7-5 Parameters for configuring the OAM function
Field
Value
Description
Tunnel ID
For example, 3
Displays the tunnel ID.
Tunnel Name
Character string
Displays the tunnel name.
Node Type
Ingress, Egress, Transit
Displays the node type.

l Ingress: ingress node
l Egress: egress node
l Transit: pass-through
node
Issue 03 (2012-11-30)

256
OptiX OSN 7500 II/7500/3500/1500

7 MPLS OAM
Field
Value
Description
OAM Status
Enabled, Disabled
Sets and displays the OAM

status.
l Enabled: OAM-related
operations can be
performed.
l Disabled: OAM-related
operations cannot be
performed.
Detection Mode
Auto-Sending, Manual
Sets and displays the

detection mode.
l Manual: The frequency
set by the user is used to
test the tunnel
connectivity.
l Auto-Sending: The
frequency of the received
packets is used to test the
tunnel connectivity.
CV, FFD
Sets the detection packet type

on the ingress node.
l CV: The detection
frequency is always the
same and is not
configurable.
l FFD: The detection
frequency is
configurable.
NOTE
If CV is selected, the system
sends one CV packet with a
length of 74 bit/s at an interval
of one second; if FFD is
selected, the system sends one
FFD packet with a length of 25
bit/s at an interval of 3.3 ms.
Issue 03 (2012-11-30)

257
OptiX OSN 7500 II/7500/3500/1500

7 MPLS OAM
Field
Value
Description
Detection Packet Period (ms)
3.3, 10, 20, 50, 100, 200, 500
Sets and displays the

detection packet period.
If Detection Packet Period
is set to FFD, the detection
packet period is
configurable. If Detection
Packet Period is set to CV,
the detection packet period is
always 1000.
It is recommended that
Detection Packet Period
(ms) be set to 3.3 to ensure
that the switching duration of
MPLS tunnel APS protection
is less than 50 ms.
Reverse Tunnel
For example, 3
Selects the reverse tunnel.
CV/FFD Status
Stop, Start
Displays the CV/FFD status.
LSP Status
Near-End Available, NearEnd Defect Available, NearEnd Defect Unavailable,

Near-End Unavailable,
Remote Available, Remote
Defect Available, Remote
Defect Unavailable, Remote
Unavailable, Initialized
Displays the LSP status.
LSP Defect Type
dServer, dLOCV,
dTTSI_Mismatch,
dTTSI_Mismerge, dExcess,
dUnknown, SD, SF, BDI,
FDI
Displays the LSP defect type.
Disable LSP Duration (ms)
0-655350
Displays the duration of the

disable status of the LSP.
Disable LSP Duration
indicates the duration when
the tunnel is unavailable.
LSP Defect Location
For example, 192.168.11.1
Displays the LSP defect

location.
LSP Defect Location
identifies the location of the
defect in the network by
using the IP address.
Issue 03 (2012-11-30)

258
OptiX OSN 7500 II/7500/3500/1500

7 MPLS OAM
Field
Value
Description
SD Threshold
0-100
Sets and displays the SD

threshold.
This parameter can be set
only for the egress node of the
tunnel.
SF Threshold
0-100
Sets and displays the SF

threshold.
only for the egress node of the
tunnel.
SD SF
Source Node
Displays the source node of

the tunnel.
Sink Node

tunnel.
7.12.2 PW OAM Parameters

The PW OAM parameters can be set for monitoring the PW status in real time. This topic
describes the parameters associated with PW OAM.
Table 7-6 PW OAM parameters
Field
Value Range
Description
PW ID
For example, 101
Displays the PW ID.
PW Type
Ethernet, Ethernet Tag

Mode, SATop, CESoPSN
The PW Type parameter is

used for identifying the type
of a service transmitted over
a PW. A PW can transmit
multiple types of services.
Default: Ethernet
Click A.9.5 PW Type for

more information.
Issue 03 (2012-11-30)
OAM Status
Enabled, Disabled
Specifies the status of PW

OAM.
Associate AC State
Enabled, Disabled
Enable the Associate AC

State to detect the working
status of PW FRR.

259
OptiX OSN 7500 II/7500/3500/1500

7 MPLS OAM
Field
Value Range
Description
Detection Mode
Auto-Sending, Manual
Specifies or displays the

detection mode.
l Manual: The
connectivity check (CC)
packets are sent at the
interval specified by the
user.
l Auto-Sending: The
connectivity check (CC)
packets are sent at the
interval of packet
receiving.
The link-layer detection of
the MPLS APS is performed
by using the MPLS OAM
function. Therefore, the
MPLS OAM parameters
related to tunnels need to be
set before the configuration
of the MPLS APS.
CV, FFD
Specifies the type of the

detection packet.
l CV: Detection packets
are sent at a fixed interval.
l FFD: Detection packets
are sent at the interval
specified by the user.
Detected Packet Period(ms)
3.3, 10, 20, 50, 100, 200, 500
If Detection Packet Type is

set to CV, Detected Packet
Period(ms) is always 1000.
If Detection Packet Type is
set to FFD, Detected Packet
Period(ms) can be set as
required.
If Detection Mode is set to
Auto-Sending, Detected
Packet Period(ms) is 1000
by default and the value
cannot be changed.
If Detection Mode is set to
Manual, Detected Packet
Period(ms) can be set to a
value from 3.3 to 500.
SD Threshold(%)
0 to 100
Default: 0
Issue 03 (2012-11-30)

Specifies or displays the SD

threshold.
260
OptiX OSN 7500 II/7500/3500/1500

7 MPLS OAM
Field
Value Range
Description
SF Threshold(%)
0 to 100
Specifies or displays the SF

threshold.
Default: 0
SDSF
LSR ID to be Received
Specifies the LSR ID to be

received.
The LSR ID to be Received
and PW ID to be Received
can be set only when OAM
Status is Disabled.
PW ID to be Received
For example, 530

NOTE
The value ranges from 1 to
4294967295.
Issue 03 (2012-11-30)
Specifies the PW ID to be
received.
Multiple PWs of the same
type cannot take the same
PW ID. Multiple PWs of
different types can take the
same PW ID.
Local Working Status
Initial, Near-End Available,

Near-End Defect Available,
Near-End Defect
Unavailable, Near-End
Unavailable
Displays the working status

of the PW at the local end.
Local PW Defect Type
Displays the local PW defect

type.
Local Disable PW Duration

(ms)
Displays the duration when

the PW is disabled at the local
end.
Local PW Defect Location
Default: 255.255.255.255
Displays the local PW defect

location.
Remote Working Status
Initial, Remote Available,

Remote-End Defect
Available, Remote-End
Defect Unavailable, RemoteEnd Unavailable
Displays the working status

of the PW at the remote end.
Remote PW Defect Type
Displays the remote PW

defect type.
Remote Disable PW
Duration(ms)
Displays the duration when

the PW is disabled at the
remote end.
Remote PW Defect Location
Default: 255.255.255.255
Displays the remote PW

defect location.

261
OptiX OSN 7500 II/7500/3500/1500

7 MPLS OAM
7.12.3 Ping Test

You need to set parameters for a ping test, starting the ping test, and stopping the ping test when
configuring a ping test.
Table 7-7 lists the parameters for a ping test.
Table 7-7 Parameters for a ping test
Field
Value
Description
Packet Count
For example, 3
Sets the count of packets.
EXP Value
0-7
Sets the EXP value.

The packet priority increases
with the EXP value.
TTL
1-255
Sets the time to live (TTL).
Transmit Interval(10ms)
10-1000
Sets the interval of

transmitting packets.
Packet Length
64-1400
Sets the length of packets.
Wait-to-Response Timeout
Time(10ms)
50-6000
Sets the wait-to-response

timeout time.
Response Mode
No Response, IPv4 UDP

Response
Sets the response mode.
Character string
Displays the test result.
Test Result
NOTE
This parameters can be
currently set to only IPv4 UDP
Response. If this parameter is
set to No Response, a timeout
message is displayed as the test
result.
7.12.4 Traceroute Test

You need to set the parameters such as Packet Length and Response Mode when configuring
the traceroute test.
Table 7-8 lists the parameters for configuring the traceroute test.
Table 7-8 Parameters for configuring the traceroute test
Field
Value
Description
EXP Value
0-7
Sets the EXP value.

The packet priority increases
with the EXP value.
TTL
Issue 03 (2012-11-30)
1-255
Sets the TTL.

262
OptiX OSN 7500 II/7500/3500/1500

7 MPLS OAM
Field
Value
Description
Packet Length
84-1400
Sets the length of packets.
Wait-to-Response Timeout
Time(10ms)
50-6000
Sets the wait-to-response

timeout time.
Response Mode
No Response, IPv4 UDP

Response
Sets the response mode.
Character string
Displays the test result.
Test Result
NOTE
You can set this parameter to
only IPv4 UDP Response. If
you set this parameter to No
Response, the test result will
time out.

7.13.1 Related Alarms

This topic describes alarms related to this feature.
Table 7-9 lists the alarms related to MPLS OAM.
Table 7-9 Alarms related to MPLS OAM
Issue 03 (2012-11-30)
Alarm Name
Description
MPLS_TUNNEL_B
DI
The MPLS_TUNNEL_BDI alarm indicates defects in the backward

direction of a tunnel. This alarm is reported when a BDI packet is
received at the receive end, indicating that the forward tunnel is faulty.
MPLS_TUNNEL_E
xcess
The MPLS_TUNNEL_Excess alarm indicates that excessive Trail

Termination Source Identifiers (TTSIs) are received. This alarm is
reported if a total of five correct CV/FFD packets or more are received
in three consecutive CV/FFD periods.
MPLS_TUNNEL_F
DI
The MPLS_TUNNEL_FDI alarm indicates defects in the forward

direction of a tunnel. This alarm is reported when a Forward Defect
Indication (BDI) packet is received, indicating that the tunnel at the
physical layer is faulty.
MPLS_TUNNEL_L
OCV
The MPLS_TUNNEL_LOCV alarm indicates the loss of tunnel

connectivity. This alarm is reported if the expected CV/FFD packet
is not received in three consecutive CV/FFD periods.
MPLS_TUNNEL_
MISMATCH
The MPLS_TUNNEL_MISMATCH alarm indicates Trail

Termination Source Identifiers (TTSIs) mismatch. This alarm is
reported if no CV/FFD packet with a correct TTSI is received in three
consecutive CV/FFD periods.

263
OptiX OSN 7500 II/7500/3500/1500

Issue 03 (2012-11-30)
7 MPLS OAM
Alarm Name
Description
MPLS_TUNNEL_
MISMERGE
The MPLS_TUNNEL_MISMERGE alarm indicates that the Trail

Termination Source Identifiers (TTSIs) are incorrectly merged. This
alarm is reported if CV/FFD packets with correct TTSIs and CV/FFD
packets with incorrect TTSIs are received in three consecutive CV/
FFD periods.
MPLS_TUNNEL_S
D
The MPLS_TUNNEL_SD alarm indicates that the tunnel signal

degrades. This alarm is reported when the packet loss ratio of the
connectivity check (CC) exceeds the SD threshold but is lower than
the SF threshold.
MPLS_TUNNEL_S
F
The MPLS_TUNNEL_SF alarm indicates that the tunnel signal

degrades severely. During the Continuity Check (CC), this alarm is
reported if the packet loss ratio exceeds the SF threshold but CC
packets are received in three consecutive periods.
MPLS_TUNNEL_U
NKNOWN
The MPLS_TUNNEL_UNKNOWN alarm indicates that certain

unknown defects exist on the tunnel. During the Continuity Check
(CC), this alarm is reported if the type and time period of the packets
that are received within a certain time (three times the period) are
different from the expected type and period.
MPLS_PW_LOCV
The MPLS_PW_LOCV is an alarm indicating the loss of PW

connectivity. This alarm is reported if the expected CV/FFD packet
is not received in three consecutive periods.
MPLS_PW_Excess
The MPLS_PW_Excess is an alarm indicating that excessive trail

termination source identifiers (TTSIs) of the PW are received. This
alarm is reported if a total of five correct CV/FFD packets or more
are received in three consecutive CV/FFD periods.
MPLS_PW_BDI
The MPLS_PW_BDI is an alarm indicating defects in the backward

direction of a PW. This alarm is reported when a BDI packet is
received at the receive end, indicating that the forward PW is faulty.
MPLS_PW_MISM
ATCH
The MPLS_PW_MISMATCH is an alarm indicating mismatch of the

TTSIs of PWs. This alarm is reported if no CV/FFD packet with a
correct TTSI (including the PW ID and NE ID) is received in three
consecutive CV/FFD periods.
MPLS_PW_MISME
RGE
The MPLS_PW_MISMERGE is an alarm indicating that the TTSIs

of PWs are incorrectly merged. This alarm is reported if CV/FFD
packets with correct TTSIs (including the PW ID and NE ID) and CV/
FFD packets with incorrect TTSIs are received in three consecutive
CV/FFD periods.
MPLS_PW_SD
The MPLS_PW_SD is an alarm indicating that the signal on a PW

degrades. This alarm is reported when the loss ratio of the CC packets
is higher than the SD threshold but is lower than the SF threshold.
MPLS_PW_SF
The MPLS_PW_SF is an alarm indicating that the signal on a PW

degrades severely. This alarm is reported when the loss ratio of the
CC packets exceeds the SF threshold.

264
OptiX OSN 7500 II/7500/3500/1500

7 MPLS OAM
Alarm Name
Description
MPLS_PW_UNKN
OWN
The MPLS_PW_UNKNOWN is an alarm indicating that certain

unknown defects exist on a PW. This alarm is reported when the types
and the cycles of the CC packets that have correct TTSIs and are
received within a certain period (three times of the cycle) are not the
expected types and cycles.
7.13.2 Related Performance Events

This topic describes performance events related to this feature.
Table 7-10 lists the performance events related to MPLS OAM.
Table 7-10 Performance events related to MPLS OAM
Performance
Event Name
Issue 03 (2012-11-30)
Description
MPLS_TUNNEL_L
S
Packet loss seconds of the MPLS service
MPLS_TUNNEL_S
LS
Severe packet loss seconds of the MPLS service
MPLS_TUNNEL_C
SLS
Consecutive severe packet loss seconds of the MPLS service
MPLS_TUNNEL_U
AS
Unavailable seconds of the MPLS service
MPLS_PW_LS
Packet loss seconds of the PW service
MPLS_PW_SLS
Severe packet loss seconds of the PW service
MPLS_PW_CSLS
Consecutive severe packet loss seconds of the PW service
MPLS_PW_UAS
Unavailable seconds of the PW service

265
OptiX OSN 7500 II/7500/3500/1500

8 HQoS
HQoS
About This Chapter

Hierarchical QoS (HQoS) is a QoS technology that controls user traffic and performs prioritybased traffic scheduling.
8.1 Introduction
With IP technology and transmission technology continues to evolve, the traditional business
model of the broadband service gradually began to be exposed, the most prominent problem is
the operator's CAPEX (Capital Expenditure) and OPEX (Operational Expenditure) growth rate
much higher than the growth rate of users, and average revenue per user APRU (Average
Revenue Per User) continued to decline, HQoS can be achieved through user-based
differentiated services, for operators to bring more value.
8.2 Basic Concepts
Before you configure the QoS policy, you need to be familiar with the basic concepts of the QoS
and the QoS policies that the OptiX OSN equipment supports.
8.3 Specifications
This section describes the capacity of the OptiX OSN equipment for supporting HQoS.
This topic describes the standards and protocols that HQoS complies with.
8.5 Availability
The HQoS function requires the support of the applicable equipment and boards.
This section describes the limitations on and precautions for HQoS in the network design phase,
8.7 Principles
You should be familiar with the realization principle of the HQoS before configuring the HQoS
function.
HQoS provides hierarchical QoS functions for Ethernet traffic, ensuring quality of Ethernet
traffic.
8.9 Configuring the HQoS
Issue 03 (2012-11-30)

266
OptiX OSN 7500 II/7500/3500/1500

8 HQoS
You can configure the HQoS to provide dedicated bandwidths, decrease the packet loss ratio,
and lower the packet transmission delay and delay jitter.
This topic considers the QoS configuration for the Ethernet service on the OptiX OSN 3500 as
an example. You can configure hierarchical QoS policies and apply these policies to the specified
Ethernet services to ensure the QoS.
8.11 Troubleshooting
Following a certain troubleshooting flow facilitates your fault locating and rectification. This
topic considers an HQoS fault on the OptiX OSN 3500 equipment as an example to describe
how to handle an HQoS fault, helping you handle HQoS faults on other types of equipment.
8.12 Parameter Description: HQoS
This topic describes the alarms and performance events that are related to this feature.
Issue 03 (2012-11-30)

267
OptiX OSN 7500 II/7500/3500/1500

8 HQoS
8.1 Introduction
With IP technology and transmission technology continues to evolve, the traditional business
model of the broadband service gradually began to be exposed, the most prominent problem is
the operator's CAPEX (Capital Expenditure) and OPEX (Operational Expenditure) growth rate
much higher than the growth rate of users, and average revenue per user APRU (Average
Revenue Per User) continued to decline, HQoS can be achieved through user-based
differentiated services, for operators to bring more value.
Definition
HQoS is a QoS technology that controls user traffic and performs priority-based traffic
scheduling at the same time. In addition, HQoS provides a perfect traffic measurement function.
Thus, a network administrator can monitor the bandwidth that each service occupies and can
allocate an appropriate bandwidth to each service based on traffic analysis.
Purpose
HQoS is developed based on the traditional QoS scheme. The equipment with the HQoS function
provides users or services with services at differentiated quality levels. The features of the HQoS
function are as follows:
l
Powerful traffic classification function

The HQoS function can classify traffic by IP address, MAC address, protocol type in IP
packets, CVLAN ID, or SVLAN ID.
More queue scheduling methods

The HQoS function can schedule V-UNI policy queues, V-UNI queues, V-UNI group
queues, PW policy queues, PW queues, and port policy queues and so on.
Refined control, thus users sharing the bandwidth
8.2 Basic Concepts

Before you configure the QoS policy, you need to be familiar with the basic concepts of the QoS
and the QoS policies that the OptiX OSN equipment supports.
8.2.1 QoS Requirements

Various services require different QoS operations depending on their respective requirements
for the bandwidth, delay, jitter, and packet loss ratio. These services can receive differentiated
treatments.
Specifications in QoS Measurement

l
Delay: indicates the time elapsed after a service is transmitted at a reference point and
before the service is received at another reference point.
Jitter: indicates the difference between the time points when packets that traverse the same
route arrive at the user receive end.
Packet loss ratio: indicates the maximum ratio of the discarded packets to the total number
of transmitted packets. Packet discarding generally results from network congestion.
Issue 03 (2012-11-30)

268
OptiX OSN 7500 II/7500/3500/1500

8 HQoS
Service Types and QoS Requirements

Table 8-1 provides the various service types and their respective QoS requirements based on
the example 3G Ethernet service.
Table 8-1 Service types and QoS requirements
Type of Service
Typical
Service
Delay
Jitter
Packet Loss
Control
information
Ethernet
protocol
packet
Packet Loss
Packet Loss
Packet Loss
Packet Loss
Packet Loss
Packet Loss
Conversatio
nal service
and signaling
service
From top to
downwards,
service
priorities are
in a
descending
order.
Ethernet
OAM packet
VoIP
Videophone
Interactive
game
Streaming
service
VOD
Not sensitive
Packet Loss
Not sensitive
Interactive
service
Web page
browsing
Not sensitive
Not sensitive
Packet Loss
Background
service
Email/Film/
MP3
downloading
Not sensitive
Not sensitive
Packet Loss
FTP service
8.2.2 DiffServ
As an end-to-end QoS control model, the DiffServ can be simply realized and easily extended.
Figure 8-1 shows the application of the DiffServ model.
Figure 8-1 Networking diagram of the DiffServ model
DS node
DS domain
Non-DS node
DS node
DS node
Non-DS node
The DiffServ (DS) domain consists of a group of network nodes (DS nodes) that provide the
same service policy and realize the same per-hop behavior (PHB).
Issue 03 (2012-11-30)

269
OptiX OSN 7500 II/7500/3500/1500

8 HQoS
The DS nodes are of two types, namely, DS edge nodes and internal DS nodes. The DS edge
node classifies the traffic that enters the DS domain. The DS edge node marks different PHB
service levels according to different types of service traffic. The internal DS node controls the
flow based on the PHB service levels.
As the node in the DS domain, the OptiX OSN equipment uses the following technologies to
perform the end-to-end QoS control.
Flow Management Scheme

l
The DiffServ is a flow management scheme based on the service type and provides the
management at a large granularity.
The operation of the DiffServ is based on the service classification.

The packets are classified into a limited range of service types other than being classified
according to the requirement of each flow.
The equipment in the network identifies the service according to the service type.
Each type of service can be managed independently. Hence, the service of a higher
priority can be processed with preference.
The DiffServ provides the architecture to allow service classification and differentiated
treatments for different types of services.
The DiffServ is related to the classification and marking mechanisms.
The DiffServ realizes the PHB.
PHB
Table 8-2 provides the service quality that corresponds to each PHB service level.
Table 8-2 PHB service level and the corresponding PHB service quality
PHB Service Level
PHB Service Quality
BE
This service level focuses on the availability, without requiring the

service forwarding quality. BE is the default PHB service level. All
DS nodes must support the BE PHB.
AF1
These service levels allow the service traffic to exceed the specified
range. These service levels ensure the forwarding quality of the traffic
within the specified range and downgrade the forwarding quality of
the traffic beyond the specified range. The traffic beyond the specified
range is not simply discarded.
These PHB service levels are applicable to the transmission of
multimedia services.
Each AF level is further classified into three discarding priorities
(colors). For example, the AF1 level can be further classified into the
following discarding priorities:
l AF11: corresponds to the green priority. The traffic of this priority
can pass normally.
l AF12: corresponds to the yellow priority. When a network
congestion occurs, the packet of this priority is discarded.
AF2
AF3
Issue 03 (2012-11-30)

270
OptiX OSN 7500 II/7500/3500/1500

8 HQoS
PHB Service Level
PHB Service Quality
AF4
l AF13: corresponds to the red priority. The packet of this priority

is first discarded.
EF
These service levels require that the rate of the traffic sent from any
DS node should not be less than the specified rate in any conditions.
These service levels simulate the forwarding effect of a virtual leased
line. In this manner, the forwarding service of low packet loss ratio,
low delay, and high bandwidth can be provided. The PHB service
levels are applicable to video services and VoIP services.
CS6
CS7
Table 8-3 lists the recommended mapping relation between the priority of the ingress packet
and the PHB service level.
Table 8-3 Mapping relation between the priority of the ingress packet and the PHB service level
Issue 03 (2012-11-30)
VLAN
Priority
DEISVLAN
Priority
DSCP
(Decimal)
MPLS EXP
Priority
PHB Service
Level
0, 8
BE
8, 10
AF11
12
AF12
14
AF13
16, 18
AF21
20
AF22
10
22
AF23
24, 26
AF31
28
AF32
11
30
AF33
32, 34
AF41
36
AF42

271
OptiX OSN 7500 II/7500/3500/1500

8 HQoS
VLAN
Priority
DEISVLAN
Priority
DSCP
(Decimal)
MPLS EXP
Priority
PHB Service
Level
12
38
AF43
5, 13
40, 46
EF
6, 14
48
CS6
7, 15
56
CS7
NOTE
In the case of the DSCP priority, if the DSCP value is not within the range specified in the previous table,
the PHB service level is BE.
Table 8-4 lists the recommended mapping relation between the priority of the egress packet and
the PHB service level.
Table 8-4 Mapping relation between the priority of the egress packet and the PHB service level
Issue 03 (2012-11-30)
PHB Service
Level
VLAN
Priority
DEISVLAN
Priority
DSCP
(Decimal)
MPLS EXP
Priority
BE
0,8
AF11
AF12
12
AF13
14
AF21
16
AF22
20
AF23
10
22
AF31
24
AF32
28
AF33
11
30
AF41
32
AF42
36
AF43
12
38
EF
40
CS6
48
CS7
56

272
OptiX OSN 7500 II/7500/3500/1500

8 HQoS
8.2.3 Traffic Classification

Traffic classification is intended to differentiate services, according to the rules specified by the
user matches the packet, the implementation of different strategies. Traffic classification
includes complex traffic classification and simple traffic classification.
The OptiX OSN equipment supports the two types of traffic classification: simple traffic
classification and complex traffic classification.
Simple Traffic Classification

Simple traffic classification is to set the mapping relationships between the priorities of the
received packets and specified PHB service levels. This method enables the packets to be
processed in a unified PHB manner when the packets pass through nodes in the DS domain.
l
Simple traffic classification is generally performed on the DS interior node. The same
simple traffic classification rule is applied to all the nodes in the DS domain.
The OptiX OSN equipment allows access of Ethernet packets, IP packets, and MPLS
packets. In addition, the OptiX OSN equipment allows mapping between the VLAN
priority and the PHB service level, between the IP DSCP and the PHB service level, and
between the MPLS EXP and the PHB service level.
Complex Traffic Classification

Complex traffic classification is based on multiple characteristics of packet information (such
as source IP, destination IP, source port, destination port, protocol type, etc.) as the matching
rules to find the mapping table to get the message corresponding to the level of service, to provide
users with more detailed, more flexible traffic division.
l
Complex traffic classification is usually applied to a DS domain edge node on the network
traffic flow to do fine control, mark the priority information carried by the packets, the
nodes within a DS domain to do as a simple traffic classification.
A complex flow supports the following QoS operations:

The flow is passed or discarded based on the Access Control List (ACL).
The flow is mapped to a new PHB service class.
In the ingress direction, the rate of the flow is restricted by means of the committed
access rate (CAR) mechanism.
In the egress direction, traffic shaping is performed on the flow.
The OptiX OSN 3500/7500/7500 II equipment supports complex traffic classification for
Ethernet packets and IP packets, providing users with a more refined and flexible traffic
classification scheme.
The OptiX OSN 1500 equipment supports complex traffic classification based on VLAN
IDs only for Ethernet packets.
8.2.4 Queue Scheduling

When network congestion occurs, the OptiX OSN equipment provides the ensured HQoS for
services at the higher level by using different queue scheduling schemes. The OptiX OSN
equipment uses two queue scheduling schemes, namely, strict-priority queuing (SP) and
weighted fair queuing (WFQ).
Issue 03 (2012-11-30)

273
OptiX OSN 7500 II/7500/3500/1500

8 HQoS
NOTE
In the case of queues of the lowest priorities (that is, queues for providing BE services), the HQoS is not
ensured. When a network congestion occurs, the OptiX OSN equipment does not schedule queues that
provide the BE service level.
SP Scheduling Algorithm
Figure 8-2 illustrates the SP scheduling algorithm.
Figure 8-2 SP queues
Packets to be
transmitted through Classification
the interface
Queue
Priority
Queue 7
Highest
Queue 6
High
Queue 5
Low
Packets
transmitted out
of the interface
Egress queue
scheduling
...
Queue 0
Lowest
The urgency of packets decreases from left to right.
In SP queue scheduling, packets are transmitted in a descending order of priority. Packets in a

high-priority queue are always transmitted first, and the packets in a lower-priority queue can
be transmitted until the high-priority becomes empty. In application, packets of key services are
placed into high-priority queues and packets of non-key services (such as email services) are
placed into lower-priority queues. As a result, the packets of key services can be always
transmitted first, and the packets of non-key services are transmitted when the data of key
services is not processed.
In SP scheduling algorithm, all resources are used to guarantee the QoS objectives of highpriority services. This indicates that the packets in lower-priority queues cannot receive any
treatments if there are always packets in high-priority queues.
NOTE
The SP scheme is used to schedule queues of higher priorities (that is, queues for providing CS7, CS6, and
EF services).
WFQ Scheduling Algorithm

Figure 8-3 illustrates the WFQ scheduling algorithm.
Issue 03 (2012-11-30)

274
OptiX OSN 7500 II/7500/3500/1500

8 HQoS
Figure 8-3 WFQ queues

Packets to be
transmitted through Classification
the interface
Queue
Packets
transmitted out
of the interface
Weight
Queue 3
50
Queue 2
30
Queue 1
10
Queue 0
10
Egress queue
scheduling
The urgency of packets decreases from left to right.
When the WFQ scheme is used, queues are scheduled in a fair manner according to the weight
allocated to each queue. Generally, more weights and bandwidths are allocated to the queues of
higher priorities, and less weights and bandwidths are allocated to queues of lower priorities.
This queue scheduling scheme ensures the packets in queues of higher priorities are forwarded
with little delay. In addition, this scheme ensures that the packets in queues of lower priorities
can be processed accordingly.
NOTE
The WFQ scheme is used to schedule queues of higher priorities (that is, queues for providing AF4, AF3,
AF2, and AF1 services).
8.2.5 Committed Access Rate

Committed access rate (CAR) is a type of traffic policing technology. When the CAR mechanism
is used, the rate of the traffic after traffic classification is assessed in a certain period (including
in the long term and in the short term); the packet whose rate does not exceed the specified value
is set to a high priority and the packet whose rate exceeds the specified value is discarded or
downgraded. The CAR restricts the traffic into the transmission network.
Hybrid MSTP provides CAR processing for a complex flow in the ingress direction. The details
are as follows:
l
When the rate of packets is equal to or lower than the preset committed information rate
(CIR), these packets are marked green and pass the CAR policing. These packets are always
forwarded first in network congestion.
When the rate of packets exceeds the preset peak information rate (PIR), these packets
whose rate is higher than the PIR are marked red and directly discarded.
When the rate of packets is higher than the CIR but is lower than the PIR, the packets whose
rate is higher than the CIR can pass the restriction but are marked yellow. Yellow packets
can be set to "discard", "pass", or "remark". If packets are set to "remark", these packets
are mapped to another specified queue with a certain priority (that is, the priority of these
packets are changed) and then forwarded.
When the rate of packets that pass the CAR restriction is equal to or lower than the CIR in
a certain period, certain packets can burst and these packets are always forwarded first in
Issue 03 (2012-11-30)

275
OptiX OSN 7500 II/7500/3500/1500

8 HQoS
network congestion. The maximum burst traffic is determined by the committed burst size
(CBS).
l
When the rate of packets that pass the CAR restriction is higher than the CIR but is equal
to or lower than the PIR, certain packets can burst and these packets are marked yellow.
The maximum burst traffic is determined by the peak burst size (PBS).
Figure 8-4 shows the traffic change after the CAR processing. The packets marked red are
directly discarded, and the packets marked yellow and green pass the CAR policing. In addition,
the packets marked yellow are processed according to the preset value.
Figure 8-4 CAR processing
8.2.6 Congestion Management

When network congestion occurs or aggregates, specific packet discarding policies are used to
ensure the QoS of services of higher priorities.
The three common packet discarding policies are as follows:
l
Tail drop policy

When the tail drop policy is used, the packets that arrive after a queue is full are discarded.
Random early detection (RED)

When the RED policy is used, the packets are discarded at random when a queue reaches
a certain length. In this manner, overall synchronization caused by the TCP slow-start
mechanism is prevented.
Weighted random early detection (WRED)

When the WRED policy is used, the queue length and priorities of packets (colors) are
considered for packet discarding. The user can configure the packet discarding as follows:
The packets of higher discarding priorities (such as red packets and yellow packets) are
first discarded. These packets are more probable to be discarded.
The OptiX OSN equipment supports the tail drop policy and the WRED policy. In addition, the
OptiX OSN equipment supports the configuration of the discarding starting point and discarding
rate of the WRED.
8.2.7 QoS Policy

The OpitX OSN equipment provides various QoS policies intended to ensure differential QoS
for different function points.
Issue 03 (2012-11-30)

276
OptiX OSN 7500 II/7500/3500/1500

8 HQoS
Establish the port QoS policy.

In the ingress direction, the port policy is used to filter the traffic at the ingress port
according to the ACL rule. The ingress port only receives or discards the traffic that matches
with the ACL rule.
In the egress direction, the usable port QoS policy is the traffic control for different PHB
forwarding types.
Establish the V-UNI ingress policy.

The V-UNI ingress policy is used to control the traffic based on services respectively in
the ingress directions.
Establish the V-UNI egress policy.

The V-UNI egress policy is used to control the traffic based on services respectively in the
egress directions.
Establish the pseudo wire (PW) policy.

The PW policy is used to control the PW traffic in the ingress direction. The equipment
does not support the QoS control over the PW traffic in the egress direction.
Establish the QinQ policy.

The QinQ policy is used to control the QinQ traffic in the ingress direction.
Establish the weighted fair queuing (WFQ) scheduling policy.

The WFQ scheduling policy is provided for different QoS control policies.
Establish the weighted random early detection (WRED) policy.
8.3 Specifications
This section describes the capacity of the OptiX OSN equipment for supporting HQoS.
Table 8-5 provides specifications associated with HQoS.
Table 8-5 Specifications associated with HQoS
Item
DiffServ
Specifications
Maximum number of
supported DiffServ (DS)
domains
PHBs
CS7
CS6
EF
AF43, AF42, AF41
AF33, AF32, AF31
AF23, AF22, AF21
AF13, AF12, AF11
BE
Applicable port types
Issue 03 (2012-11-30)
Ethernet port

277
OptiX OSN 7500 II/7500/3500/1500

Item
8 HQoS
Specifications
Types of trusted packet
priorities
CVLAN priority
SVLAN priority
DSCP values
MPLS EXP values
NOTE
l A QinQ-based NNI port only trusts
packets carrying DSCP values or SVLAN priorities.
l An MPLS-based NNI port only trusts
packets carrying MPLS EXP values.
Complex
traffic
classification
Application point
Ingress port
Traffic classification methods
Based on source IP
Based on destination IP
Based on source MAC
Based on destination MAC
Based on protocol type
Based on source port number
Based on destination port number
Based on ICMP
Based on DSCP value
Based on IP-Precedence
Based on CVLAN ID
Based on CVLAN priority
Based on SVLAN ID
Based on SVLAN priority
Based on DEI
QoS operations based on

complex traffic classification
Access control list (ACL) based on

complex traffic classification
Assigning a new PHB to a service flow
based on complex traffic classification
Assigning a new PHB to a service flow
based on complex traffic classification
Service flows based on complex traffic
classification
CAR
Queue
scheduling
Queue scheduling algorithm
SP
WFQ
SP+WFQ
Weight allocation in WFQ
Issue 03 (2012-11-30)
The default weights can be changed.

278
OptiX OSN 7500 II/7500/3500/1500

8 HQoS

This topic describes the standards and protocols that HQoS complies with.
HQoS complies with the following standards and protocols:
l
IETF RFC 2309: Recommendations on Queue Management and Congestion Avoidance in

the Internet
IETF RFC 2697: A Single Rate Three Color Marker
IETF RFC 2698: A Two Rate Three Color Marker
IETF RFC 2597: Assured Forwarding PHB Group
IETF RFC 2598: An Expedited Forwarding PHB
IEEE 802.1p: Traffic Class Expediting and Dynamic Multicast Filtering
8.5 Availability
The HQoS function requires the support of the applicable equipment and boards.
Version Support
Issue 03 (2012-11-30)
Applicable Version
OptiX OSN 1500/3500
T2000
U2000
Applicable Version
OptiX OSN 7500
U2000
Applicable Version
OptiX OSN 7500 II
U2000

279
OptiX OSN 7500 II/7500/3500/1500

8 HQoS
Hardware Support
Issue 03 (2012-11-30)
Boar
d
Type
Serv
ice
WR
ED
Poli
cy
Por
t
W
RE
D
Pol
icy
WF
Q
Pol
icy
P
W
Pol
icy
Qi
nQ
Pol
icy
VU
NI
Ing
res
s
Pol
icy
VU
NI
Egr
ess
Pol
icy
Por
t
Pol
icy
Applicable
Version
Applicable
Equipment
Q1PE
GS2
Supp
orted
Sup
por
ted
Sup
por
ted
Not
sup
por
ted
Sup
por
ted
Sup
por
ted
Sup
por
ted
Sup
por
ted
V100R009C
03 and later
OptiX OSN
1500A/
1500B
R1PE
FS8
Supp
orted
Sup
por
ted
Sup
por
ted
Not
sup
por
ted
Sup
por
ted
Sup
por
ted
Sup
por
ted
Sup
por
ted
V100R009C
03 and later
OptiX OSN
1500A/
1500B
R1PE
GS1
Supp
orted
Sup
por
ted
Sup
por
ted
Not
sup
por
ted
Sup
por
ted
Sup
por
ted
Sup
por
ted
Sup
por
ted
V100R009C
03 and later
OptiX OSN
1500A/
1500B
R1PE
F4F
Supp
orted
Sup
por
ted
Sup
por
ted
Not
sup
por
ted
Sup
por
ted
Sup
por
ted
Sup
por
ted
Sup
por
ted
V100R009C
03 and later
OptiX OSN
1500A/
1500B
N1PE
G16
Supp
orted
Not
sup
por
ted
Sup
por
ted
Sup
por
ted
Sup
por
ted
Sup
por
ted
Sup
por
ted
Sup
por
ted
V100R009C
03 and later
OptiX OSN
3500
N1PE
X1
Supp
orted
Not
sup
por
ted
Sup
por
ted
Sup
por
ted
Sup
por
ted
Sup
por
ted
Sup
por
ted
Sup
por
ted
V100R009C
03 and later
OptiX OSN
3500
N1PE
TF8
Supp
orted
Sup
por
ted
Sup
por
ted
Sup
por
ted
Sup
por
ted
Sup
por
ted
Sup
por
ted
V100R009C
03 and later
OptiX OSN
3500/7500
N1PE
G8
Supp
orted
Sup
por
ted
Sup
por
ted
Sup
por
ted
Sup
por
ted
Sup
por
ted
Sup
por
ted
V200R011C
00 and later
OptiX OSN
3500/7500
N2PE
X1
Supp
orted
Sup
por
ted
Sup
por
ted
Sup
por
ted
Sup
por
ted
Sup
por
ted
Sup
por
ted
V200R011C
00 and later
OptiX OSN
3500/7500
N1PE
X2
Supp
orted
Opt
iX
OS
N
350
0:
Not
sup
por
ted
Opt
iX
OS
Sup
por
ted
Sup
por
ted
Sup
por
ted
Sup
por
ted
Sup
por
ted
Sup
por
ted
V200R011C
00 and later
OptiX OSN
3500/7500

280
OptiX OSN 7500 II/7500/3500/1500

8 HQoS
Boar
d
Type
Serv
ice
WR
ED
Poli
cy
Por
t
W
RE
D
Pol
icy
WF
Q
Pol
icy
P
W
Pol
icy
Qi
nQ
Pol
icy
VU
NI
Ing
res
s
Pol
icy
VU
NI
Egr
ess
Pol
icy
Por
t
Pol
icy
Applicable
Version
Applicable
Equipment
N1PE
FF8
Supp
orted
N
750
0:
Sup
por
ted
Sup
por
ted
Sup
por
ted
Sup
por
ted
Sup
por
ted
Sup
por
ted
Sup
por
ted
V200R011C
00 and later
OptiX OSN
3500/7500
TNN1
EX2
Supp
orted
Sup
por
ted
Sup
por
ted
Sup
por
ted
Sup
por
ted
Sup
por
ted
Sup
por
ted
Sup
por
ted
V200R011C
01 and later
OptiX OSN
7500 II
TNN1
EG8
Supp
orted
Sup
por
ted
Sup
por
ted
Sup
por
ted
Sup
por
ted
Sup
por
ted
Sup
por
ted
Sup
por
ted
V200R011C
01 and later
OptiX OSN
7500 II
TNN1
ETM
C
Supp
orted
Sup
por
ted
Sup
por
ted
Sup
por
ted
Sup
por
ted
Sup
por
ted
Sup
por
ted
Sup
por
ted
V200R011C
01 and later
OptiX OSN
7500 II
TNN1
EFF8
Supp
orted
Sup
por
ted
Sup
por
ted
Sup
por
ted
Sup
por
ted
Sup
por
ted
Sup
por
ted
Sup
por
ted
V200R011C
02 and later
OptiX OSN
7500 II

This section describes the limitations on and precautions for HQoS in the network design phase,
Issue 03 (2012-11-30)
Applicable
Object

Details
Remarks
HQoS
It is recommended that you

configure HQoS on edge nodes
(NEs connected to RNCs or
NodeBs).
DiffServ
All NEs in a DiffServ (DS) domain

must use consistent DS rules.

281
OptiX OSN 7500 II/7500/3500/1500

Applicable
Object
8 HQoS

Details
Remarks
In general, NEs use only the default

DS domain, which indicates that all
ports belong to the default DS
domain.
The mappings defined for the

default DS domain must be
consistent with the mappings from
packet priorities to PHBs defined on
user equipment. When you define
mappings on user equipment, do not
use CS7 or CS6 if possible. This is
because NEs may use CS7 and CS6
queues to transmit Ethernet protocol
packets or inband DCN packets.
IP DSCP mapping at egress ports is

not supported. This indicates that
during IP packet forwarding, the
equipment does not change the IP
DSCP of an outgoing packet.
If the mappings defined for the

default DS domain are consistent
with the mappings defined on user
equipment and ports map packets to
PHBs based on C-VLAN priorities,
do not modify the mappings defined
for the default DS domain.

default DS domain are consistent
equipment but some or all ports map
packets to PHBs based on priorities
other than C-VLAN priorities,
change the types of the packets that
the ports trust. Typical scenarios
involved are as follows:
l For a port that supports only IPv6

packets and maps packets to
PHBs based on DSCP values,
change its trusted packet type to
IP DSCP.
l For an MPLS NNI port, change
its trusted packet type to MPLS
EXP.
l For a QinQ NNI port, change its
trusted packet type to S-VLAN
priority or IP DSCP.
Issue 03 (2012-11-30)

282
OptiX OSN 7500 II/7500/3500/1500

Applicable
Object
Complex
traffic
classification
8 HQoS

Details
Remarks

default DS domain are inconsistent
equipment, modify the mappings
defined for the default DS domain
and verify the consistency.
If two sets of PHB mappings are

required, create a DS domain.
For point-to-point transparently

transmitted Ethernet services (UNIUNI), the DS is unavailable when
their encapsulation type is set to
Null. Packets are mapped to a besteffort (BE) queue. The other QoS
functions are available.
For CES services, you can define a

PHB for each CES service. EF
(default PHB) is recommended.
For ATM services, you can define

an ATM CoS mapping table for each
ATM service. In general, use the
default ATM CoS mapping table. If
it cannot meet requirements, create
an ATM CoS mapping table.
The following operations are

available for each flow:
l A flow is passed or discarded

based on the access control list
(ACL).
l A flow is mapped to a new PHB.
l In the ingress direction, the rate
of a flow is restricted by means
of the CAR mechanism.
l In the egress direction, traffic
shaping is performed on a flow.
Complex traffic classification is
rarely applied, because operations
on flows are usually implemented
on the user equipment side. In
general, apply complex traffic
classification (if required) only on
edge nodes in a DS domain.
Issue 03 (2012-11-30)

283
OptiX OSN 7500 II/7500/3500/1500

8 HQoS
Applicable
Object

Details
Remarks
CAR
If the traffic volume needs to be

restricted, use the committed access
rate (CAR) function.
After the CAR function is enabled,

packet loss occurs if the incoming
traffic is more than the committed
traffic. Therefore, do not apply the
CAR function to services that are
sensitive to packet loss.
The CAR function for complex

flows and ingress directions of PWs
is supported.
Two CAR schemes are available:

single-rate CAR scheme and dualrate CAR scheme.
l When the single-rate CAR

scheme is applied, set both
committed information rate
(CIR) and peak information rate
(PIR) to the committed service
bandwidth.
l When the dual-rate CAR scheme
is applied, set the CIR to the
committed service bandwidth
and the PIR to a value greater
than the CIR. This indicates that
yellow packets receive a lower
PHB treatment.
Issue 03 (2012-11-30)
For flows, apply the single-rate or

dual-rate CAR scheme as required.
If the latter one is applied, it is
recommended that you set the PIR
1.5 to 2 times the value of the CIR.
The value of the committed burst

size (CBS) or peak burst size (PBS)
should be proportional to that of the
CIR or PIR respectively. It is
recommended that you set the CBS
or PBS to the volume of the traffic
that passes at the CIR or PIR within
20 to 200 ms, so that the CBS (bytes)
to CIR (kbit/s) or PBS (bytes) to PIR
(kbit/s) ratio is 2 to 20.

284
OptiX OSN 7500 II/7500/3500/1500

8 HQoS

None.
None.
8.7 Principles
You should be familiar with the realization principle of the HQoS before configuring the HQoS
function.
8.7.1 Traffic Policing

The main function of traffic policing is to supervise the rate of traffic and to ensure that the rate
of traffic does not exceed the committed rate. Specifically, if the traffic rate of a connection
exceeds the committed rate, traffic policing enables some packets to be discarded or allows
resetting of the packet priorities.
The Ethernet data board that supports QoS achieves traffic policing by using the committed
access rate (CAR) method. CAR, a bandwidth management method, is used to limit the rate of
the traffic at edge ports of a network.
After traffic classification is performed, CAR assesses the rate of the traffic in a specified period
(short term and long term) by using the token bucket scheme. Afterwards, CAR sets the packets
whose rate does not exceed the limit to high priorities, and discards or downgrades the packets
whose rate exceeds the limit. In this manner, traffic that enters a transmission network is limited.
Figure 8-5 shows how traffic policing is performed through CAR according to the token bucket
scheme.
Figure 8-5 Traffic policing process
...
Packets that need to be

transmitted from the interface
Tokens are placed

into the bucket at a
specified rate
Tokens
Packets that are transmitted

from the interface
Classification
Token bucket
Packets are
discarded
Issue 03 (2012-11-30)

285
OptiX OSN 7500 II/7500/3500/1500

8 HQoS
Packets are classified according to the preset matching rules: The packets whose traffic
performance is not defined are directly transmitted without being processed in the token bucket;
the packets that require traffic control enter the token bucket for processing.
The token bucket can be considered as a container with a certain capacity for storing tokens.
Tokens are placed into the bucket at a rate specified by the user. The user also sets the capacity
of the token bucket, so that no more tokens can be placed into the bucket when the number of
tokens is higher than the capacity of the bucket.
When packets are processed in the token bucket, the packets can pass and be transmitted out if
the token bucket has sufficient tokens to transmit the packets. In addition, the number of tokens
in the bucket decreases according to the length of the transmitted packets. When the number of
tokens in the bucket is so small that no more packets can be transmitted, the remaining packets
are discarded or marked. In this manner, traffic of certain packets is controlled.
When the token bucket has sufficient tokens, the packets that are represented by these tokens
can be transmitted, which allows transmission of the burst data in some cases. When no tokens
are available in the token bucket, packets cannot be transmitted until new tokens are generated
in the bucket. This method ensures that the traffic of packets is equal to or less than the rate at
which tokens are generated, and traffic is controlled.
The Ethernet processing board that supports QoS assesses traffic by using the single rate three
color marker (srTCM, which complies with RFC 2697) algorithm or the two rate three color
marker (trTCM, which complies with RFC 2698) algorithm. Packets are marked green, yellow,
or red according to the assessment results and then are allocated with different priorities if
discarding is required.
The srTCM algorithm is defined for burst packet size. The trTCM algorithm, however, is defined
for the burst of packet rate.
NOTE
Currently, the OptiX OSN equipment uses the trTCM algorithm.
srTCM Algorithm
Figure 8-6 illustrates the working principle of the srTCM algorithm.
Figure 8-6 srTCM algorithm
...
Tokens are placed into

the buckets at the CIR
Classification
Tc
Te
Issue 03 (2012-11-30)

286
OptiX OSN 7500 II/7500/3500/1500

8 HQoS
Parameters: committed information rate (CIR), committed burst size (CBS), and excess
burst size (EBS)
Number of token buckets: 2 (Tc and Te)
Capacities of token buckets: Tc = CBS, Te = EBS
Rates of token buckets: Vc = Ve = CIR
Tokens enter the two token buckets at the CIR. Every token represents a number of bytes. If the
packets that arrive at the buckets do not exceed the CBS, they are marked green. If the packets
that arrive at the buckets exceed the CBS but do not exceed the EBS, they are marked yellow.
If the packets that arrive at the buckets exceed the EBS, they are marked red. Red packets are
directly discarded; if network congestion occurs, yellow packets are discarded to ensure passing
of green packets. If the token buckets are full of tokens because no packets need to be transmitted
in a long time, a certain number of packets can burst. The total number of bytes contained in
these burst packets is equal to that represented by the tokens in the token buckets. That is, the
allowed number of burst bytes (namely, CBS) is determined by the sizes of the token buckets
(that is, the total quantity of tokens).
The CIR and CBS parameters are set by users.
trTCM Algorithm
Figure 8-7 illustrates the working principle of the trTCM algorithm.
Figure 8-7 trTCM algorithm
...
...
CIR
PIR
Classification
Tp
Tc
Parameters: CIR, peak information rate (PIR), CBS, and peak burst size (PBS)
Number of token buckets: 2 (Tp and Tc)
Capacities of the token buckets: Tp = PBS; Tc = CBS
Rates of the token buckets: Vp = PIR; Vc = CIR
Tokens enter the two token buckets at the PIR and CIR respectively. Each token represents a
number of bytes. When the rate of the packet exceeds the PIR, the packet is marked red. When
the rate of the packet is between the PIR and the CIR, the packet is marked yellow. When the
rate of the packet does not exceed the CIR, the packet is marked green. Red packets are discarded
directly; if network congestion occurs, yellow packets are discarded to ensure passing of green
Issue 03 (2012-11-30)

287
OptiX OSN 7500 II/7500/3500/1500

8 HQoS
packets. The allowed number of burst bytes (CBS and PBS) is determined by the size of the
token bucket.
The values of the CIR, CBS, PIR, and PBS can be set by users.
There are two coloring modes: color blind and color sensitive. During the coloring process, the
current packet color is considered in color sensitive mode but not considered in color blind mode.
8.7.2 QoS Model

When functioning as an edge DS node, the OptiX OSN equipment supports HQoS.
To improve the QoS control efficiency of the entire network, HQoS control is performed on the
edge node and simple QoS processing is performed on the interior node of a network.
When functioning as an edge DS node, the OptiX OSN 3500/7500/7500 II equipment provides
multi-layer QoS function points to achieve HQoS control.
l
Based on a port, service, PW, or QinQ link, the hierarchical scheduling mechanism
implements traffic scheduling provides more refined QoS control granularity.
Based on a port, service, PW, or QinQ link, the hierarchical flow control mechanism
implements more overall quality of services.
Configurable WFQ and WRED policies allow more flexible QoS control.
NOTE
Implementation of HQoS control on the OptiX OSN 1500 equipment is simpler than that on the OptiX
OSN 3500/7500/7500 II equipment. Figure 8-9 shows the HQoS function points provided by the OptiX
OSN 1500 equipment and corresponding QoS processing.
Figure 8-8 shows the HQoS function points provided by the OptiX OSN 3500/7500/7500 II
equipment and corresponding QoS processing.
Figure 8-8 HQoS function points provided by the OptiX OSN 3500/7500/7500 II equipment
and corresponding QoS processing
Network side
Access side
QoS function
point
QoS
processing
Port
V-UNI
Apply the PW
policy/Control
the PW
bandwidth
Apply V-UNI
ingress traffic
classification
Apply
the port
policy
Apply VUNI egress

queue
scheduling
PW/QinQ
Control
the V-UNI
group
bandwidth
Apply the
QinQ policy
Tunnel
Control
the tunnel
bandwidth
Port
Apply
the port
policy
Service flow
Figure 8-9 shows the HQoS function points provided by the OptiX OSN 1500 equipment and
corresponding QoS processing.
Issue 03 (2012-11-30)

288
OptiX OSN 7500 II/7500/3500/1500

8 HQoS
Figure 8-9 HQoS function points provided by the OptiX OSN 1500 equipment and
corresponding QoS processing
Network side
Access side
QoS function
point
V-UNI
Port
Apply V-UNI
ingress traffic
classification
QoS
processing
Apply
the port
policy
QinQ
Apply the
QinQ ingress
bandwidth
policy
Tunnel
Control
the tunnel
bandwidth
Port
Apply
the port
policy
Apply the
V-UNI
egress
policy
Service flow

HQoS provides hierarchical QoS functions for Ethernet traffic, ensuring quality of Ethernet
traffic.
As shown in Figure 8-10, several OptiX OSN NEs form a DS domain to guarantee end-to-end
QoS for the Ethernet traffic.
NOTE
This topic considers a network comprising the OptiX OSN 3500 /7500/7500 II as an example. HQoS
implemented by the OptiX OSN 1500 is simpler. Learn more about the HQoS function points on the OptiX
OSN 1500 and corresponding QoS process in 8.7.2 QoS Model.
The equipment that functions as a DS edge node provides these hierarchical QoS control
functions for Ethernet traffic:
l
Mapping relationships between service priorities and PHB service levels
Hierarchical QoS policies

V-UNI ingress policy and V-UNI egress policy
PW policy
Hierarchical bandwidth control

Bandwidth control of the V-UNI group
Tunnel bandwidth control
The OptiX OSN equipment that functions as a DS interior node provides the following
hierarchical QoS control functions for the Ethernet traffic:
l
Mapping relationships between service priorities and PHB service levels
Issue 03 (2012-11-30)

289
OptiX OSN 7500 II/7500/3500/1500

8 HQoS
Figure 8-10 Networking diagram of HQoS for Ethernet traffic

Access side
V-UNI
ingress
Port
Network side
PW Tunnel Port
V-UNI V-UNI
egress group
DiffServ domain
Tunnel
Ethernet
switch
OSN
(Edge DS node)
OSN
(Internal DS node)
OSN
(Edge DS node)
Core
switch
8.9 Configuring the HQoS

You can configure the HQoS to provide dedicated bandwidths, decrease the packet loss ratio,
and lower the packet transmission delay and delay jitter.
8.9.1 HQoS Configuration Flow

The HQoS configuration refers to the QoS configuration for the DiffServ domain. This topic
describes the flow for configuring the QoS for the DiffServ domain.
QoS Configuration Flow for the DiffServ Domain

When the equipment functions as the DiffServ edge node, the QoS configuration flow is different
from the QoS configuration flow when the equipment functions as the internal DiffServ node.
Figure 8-11 shows the QoS configuration flow for the OptiX OSN 3500/7500/7500 II equipment
that functions as the DiffServ edge node.
Figure 8-12 shows the QoS configuration flow for the OptiX OSN 1500 equipment that
functions as the DiffServ edge node.
Issue 03 (2012-11-30)

290
OptiX OSN 7500 II/7500/3500/1500

8 HQoS
Figure 8-11 QoS configuration flow for the OptiX OSN 3500/7500/7500 II equipment that
functions as the DiffServ edge node
Required
Start
Optional
Configure the DiffServ
domain
Configure the
port WRED
policy
Configure the
port policy
Configure the
WFQ policy
Configure the
V-UNI ingress
policy
Configure the
service WRED
policy
Configure the
V-UNI egress
policy
Configure the
PW policy
Configure the
QinQ policy
Configure the bandwidth

of the tunnel
Apply the port policy
Apply the V-UNI ingress/

egress pocliy

of the V-UNI group
Apply the PW/QinQ policy
End
Issue 03 (2012-11-30)

291
OptiX OSN 7500 II/7500/3500/1500

8 HQoS
Figure 8-12 QoS configuration flow for the OptiX OSN 1500 equipment that functions as the
DiffServ edge node
Start
Required
Optional
Configure the DiffServ domain
Configure the
port WRED
policy
Configure the
port policy
Configure the
WFQ policy
Configure the
V-UNI ingress/
egress policy
Configure the
CAR policy
Configure the
QinQ policy

of the tunnel
Apply the port policy
Apply
V-UNI
ingress/
Apply
the the
V-UNI
ingress/egress
egress pocliy/QinQ
policy
pocliy
Figure 8-13 shows the QoS configuration flow for the OptiX OSN equipment that functions as
the internal DiffServ node.
Issue 03 (2012-11-30)

292
OptiX OSN 7500 II/7500/3500/1500

8 HQoS
Figure 8-13 QoS configuration flow for the OptiX OSN equipment that functions as the internal
DiffServ node
Required
Start
Optional
Configure the DiffServ domain

of the tunnel
Configure and apply the

port policy
End
8.9.2 Creating the DiffServ Domain

Create the mapping relations in the DiffServ domain and configure the ports that use these
mapping relations when you create the DiffServ domain.
Prerequisites
l
The network topology must be complete.
As a node in the DiffServ domain, the equipment supports the creation of the DiffServ domain
based on the physical port. Each set of the equipment supports a maximum of eight DiffServ
domains.
A default DiffServ domain exists on the equipment. Before other DiffServ domains are created,
all the ports belong to this default DiffServ domain.
Create the DiffServ domain as follows:
l
Create the mapping relations in the DiffServ domain. The mapping relations include the
mapping relation between the priorities of user packets in both the ingress and egress
directions, and the PHB service levels.
Configure the physical ports that use the mapping relations. That is, add the physical ports
to the domain.
8.2.2 DiffServ provides the service quality that corresponds to each PHB service level.
Issue 03 (2012-11-30)

293
OptiX OSN 7500 II/7500/3500/1500

8 HQoS
Procedure
Step 1 Select the NE in the NE Explorer. Choose Configuration > Packet Configuration > QoS
Management > DiffServ Domain Management > DiffServ Domain Management from the
Function Tree.
Step 2 Click Create. When the Create DS Mapping Relation dialog box is displayed, set the following
parameters:
l Mapping relation ID, mapping relation name, and package type
l Ingress mapping relation and egress mapping relation (When no configuration operation is
performed, use the mapping relation recommended by the system.)
NOTE
By default, the equipment performs the mapping according to the CVLAN. If the mapping according
to the DEISVLAN is required, enable SVLAN DEI in the SVLAN DEI Used Flag tab page.
l Ports that use the mapping relation

Step 3 Click OK.
----End
8.9.3 Creating the Port WRED Policy (OptiX OSN 1500)

Create the WRED discarding policy based on the port. The WRED discarding policy includes
the discarding threshold and discarding ratio for packets of different colors. The port WRED
policy is applicable to the port policy.
Prerequisites
Procedure
Management > Policy Management from the Function Tree.
Step 2 Select Port WRED Policy and click New. When the Create Port WRED Policy dialog box is
displayed, set the following parameters:
l Policy ID and policy name
l Discarding policies for green, yellow, and red packets
The discarding policy includes the lower threshold for discarding, upper threshold for
discarding, and discarding policy.
NOTE
Currently, only the default port WRED policy can be created and a new port WRED policy cannot be
created.
Step 3 Click OK.

----End
8.9.4 Creating a Service WRED Policy

A service WRED policy enables a proper packet discarding policy based on the packet color
even when the buffer of the queue does not overflow. This helps to lower possibility of network
Issue 03 (2012-11-30)

294
OptiX OSN 7500 II/7500/3500/1500

8 HQoS
congestion. A service WRED policy specifies the discarding threshold and discarding
probability for packets of different colors and is applicable to the V-UNI ingress policy, V-UNI
egress policy, PW policy, and QinQ policy.
Prerequisites
Procedure
Configuration > QoS Management > Policy Management > Service WRED Policy from the
Function Tree.
Step 2 Click New. In the Create Service WRED Policy dialog box that is displayed, set the following
parameters:
l Discarding policies for green, yellow, and red packets. The discarding policy specifies the
lower threshold for discarding packets, upper threshold for discarding packets, and discarding
probability.
Step 3 Click OK.
----End
8.9.5 Creating the WFQ Scheduling Policy

The WFQ scheduling policy is used to configure the weights for scheduling queues AF1-AF4.
The WFQ scheduling policy is applicable to the V-UNI ingress, V-UNI egress policy, PW policy,
and QinQ policy.
Prerequisites
Precautions
The default WFQ scheduling policy (policy ID: 1; policy name: WFQ Default Scheduling)
cannot be created, modified, or deleted.
Procedure
Management > Policy Management > WFQ Scheduling Policy from the Function Tree.
Step 2 Click New. When the Create WFQ Policy dialog box is displayed, set the following parameters:
l Policy ID and name
l AF scheduling weight
NOTE
The sum of AF1-AF4 scheduling weights should not be more than 100.
Step 3 Click OK.

----End
Issue 03 (2012-11-30)

295
OptiX OSN 7500 II/7500/3500/1500

8 HQoS
8.9.6 Creating the Port Policy (OptiX OSN 3500/7500/7500 II)

You can configure the port policy to perform the ACL filtering for the accessed traffic at a port.
When you configure the port policy, you need to configure parameters for different CoSs and
specify the packet discarding policy (such as tail drop or WRED). Finally, you can apply the
created port policy.
Prerequisites
When you configure the port policy, set the following parameters:
l
ACL rule and ACL action

The matching flows respond according to the configured ACL actions.
Parameters for different CoSs and packet discarding policies

This provides ensured QoS for different CoSs.
Procedure
Management > Policy Management > Port Policy from the Function Tree.
Step 2 Click New. When the Create Port Policy dialog box is displayed, set the following parameters:
l CoS parameters
l Applied WFQ scheduling policy
. When the WFQ Schedule Policy dialog box is displayed, select the applied
Click
WFQ scheduling policy.
NOTE
Use the default WFQ scheduling policy (WFQ default scheduling).
l If the ACL filtering is required for the accessed traffic, click Traffic Classification
Configuration tab, click New. When the Create Traffic Classification dialog box is
displayed, set the following parameters:
Traffic classification ID
ACL action
Click Add to configure the traffic classification rule.
Click OK.
Step 3 In the Create Port Policy dialog box, click OK.
Step 4 Select the port policy that is created. Click the Applied Object tab, and then click Modify.
Step 5 When the Configure Port dialog box is displayed, specify the port that uses the policy. Click
OK.
----End
Issue 03 (2012-11-30)

296
OptiX OSN 7500 II/7500/3500/1500

8 HQoS
Related Information
Based on the port policy that is created, you can create a new port policy quickly by using the
copy function. Perform the following procedures:
1.
In the Port Policy tab page, click Copy. When the Duplicate QoS Policy is displayed,
select the policy to be copied and enter the name of the new policy. Click OK.
2.
Modify the parameters of the new policy to ensure that the new policy meets the QoS
requirement.
NOTE
When the copy function is used, the application policy information of the port cannot be duplicated.
8.9.7 Creating the Port Policy (OptiX OSN 1500)

When you configure the port policy, you need to configure parameters for different CoSs and
specify the packet discarding policy (such as tail drop or WRED) and WFQ scheduling policy.
Finally, you can apply the created port policy.
Prerequisites
l
The port WRED policy or the WFQ scheduling policy must be configured if the WRED
policy or the WFQ scheduling policy is required by the port policy.
When you configure the port policy, configure the following parameters:
l
Parameters for different CoSs and packet discarding policies. This provides ensured QoS
for different CoSs.
WFQ scheduling policy
Procedure
Step 1 In the NE Explorer, select the NE, and choose Configuration > Packet Configuration > QoS
Management > Policy Management > Port Policy from the Function Tree.
Step 2 Click New. In the Create Port Policy dialog box that is displayed, set Policy Name and Policy
ID.
. In the WFQ Scheduling Policy dialog box that is displayed, select one policy
Step 3 Click
to be applied. Click OK.
NOTE
By default, the weights of the queues AF1-AF4 in the WFQ scheduling policy are equal. Each queue is
allocated 25%. The WFQ scheduling policy can be preset for a port.
Step 4 Set the Bandwidth Limit parameter of the CoS that requires the application of the bandwidth
limit to Enabled, and set the parameters of CIR(kbit/s), PIR(kbit/s), CBS(byte), PBS(byte),
and Tail Drop Threshold(%).
Step 5 Double-click the Port WRED Policy parameter of the CoS that requires the application of the
port WRED policy. In the Port WRED Policy dialog box that is displayed, select one policy
that needs to be applied. Click OK.
Issue 03 (2012-11-30)

297
OptiX OSN 7500 II/7500/3500/1500

8 HQoS
Step 6 In the Create Port Policy dialog box, click OK.

Step 7 Select the port policy that is created. Click the Applied Object tab, and then click Modify. In
the Configure Port dialog box that is displayed, specify the corresponding board in Board and
the port at which the policy is applied. Click
. Click OK.
----End
Related Information
Based on the port policy that is created, you can create a new port policy quickly by using the
1.
In the Port Policy page. Click Copy in the lower right corner. In the Duplicate QoS
Policy dialog box that is displayed, select the policy to be copied and enter the name of the
new policy. Click OK.
2.
requirement.
NOTE
When the copy function is used, the application policy information of the port cannot be duplicated.
8.9.8 Creating the V-UNI Ingress Policy (OptiX OSN 3500/7500/7500

II)
Create the V-UNI ingress policy to classify the accessed traffic and to specify the WFQ
scheduling policy, CAR parameters, and packet discarding policy.
Prerequisites
l
The WFQ scheduling policy that is used by the V-UNI ingress policy must be configured.
The WRED policy must be configured if the WRED packet discarding policy is required
by the V-UNI ingress policy to control the flow.
When you configure the V-UNI ingress policy, configure the following parameters:
l
ACL rule, ACL action, and CAR parameters
CoS parameters
This can specify the traffic control parameters and packet discarding policies for traffic of
different QoS levels.
Procedure
Management > Policy Management > V-UNI Ingress Policy from the Function Tree.
Step 2 Click New. When the Create V-UNI Ingress Policy dialog box is displayed, set the following
parameters:
Issue 03 (2012-11-30)

298
OptiX OSN 7500 II/7500/3500/1500

8 HQoS

Click
NOTE
Use the default WFQ scheduling policy (WFQ default scheduling).
l CoS parameters and packet discarding parameters

NOTE
l The value of the CIR for the queues CS7, CS6, and EF should be equal to the value of the PIR for
these queues. The value of the CIR for the other queues should be not more than the value of the
PIR for the other queues.
l When you configure the value of the PIR for each queue, ensure that the maximum value is not
more than 100 times of the minimum value.
l The Tail Drop Threshold (256 bytes) and Service WRED Policy parameters cannot be configured
at the same time.
l Choose Traffic Classification Configuration > New. When the Create Traffic
Classification dialog box is displayed, set the following parameters:
Traffic classification ID
ACL rule (by clicking Add)
ACL action
CAR parameters (CIR, PIR)
Coloration mode
l Click OK to exit the dialog box.
Step 3 In the Create V-UNI Ingress Policy dialog box, click OK.
----End
Related Information
Based on the V-UNI ingress policy that is created, you can create a new V-UNI ingress policy
quickly by using the copy function. Perform the following procedures:
1.
In the V-UNI Ingress Policy tab page, click Copy. When the Duplicate QoS Policy is
displayed, select the policy to be copied and enter the name of the new policy. Click OK.
2.
requirement.
NOTE
When the copy function is used, the application policy information cannot be duplicated.
8.9.9 Creating the V-UNI Ingress Policy (OptiX OSN 1500)

Creating the V-UNI ingress policy can realize complex flow classification for the accessed traffic
and specify corresponding CAR parameters for the flow classification.
Prerequisites
l
Issue 03 (2012-11-30)
The CAR policy that is used by the V-UNI ingress policy must be configured.
299
OptiX OSN 7500 II/7500/3500/1500

8 HQoS
Procedure
Step 1 In the NE Explorer, select the NE, and then choose Configuration > Packet Configuration >
QoS Management > Policy Management > V-UNI Ingress Policy from the Function Tree.
Step 2 Click New. In the Create V-UNI Ingress Policy dialog box that is displayed, set the Policy
ID and Policy Name parameters.
Step 3 Click New. In the Create Traffic Classification dialog box is displayed, set the Traffic
Classification ID parameter.
Step 4 Click Add, and then set Match Type, Match Value, Wildcard, and CoS.
. In the CAR Policy dialog box that is displayed, select the CAR policy that
Step 5 Click
needs to be applied, and then click OK.
Step 6 In the Create Traffic Classification dialog box, click OK. In the Create V-UNI Ingress
Policy dialog box, click OK.
----End
Related Information
Based on the V-UNI ingress policy that is created, you can create a new V-UNI ingress policy
quickly by using the copy function. Perform the following procedures:
1.
In the V-UNI Ingress Policy page, click Copy. In the Duplicate QoS Policy dialog box
that is displayed, select the policy to be copied and enter the name of the new policy. Click
OK.
2.
requirement.
NOTE
8.9.10 Creating a V-UNI Egress Policy

A V-UNI egress policy specifies the WFQ scheduling policy for the egress traffic on the access
side and specifies the flow control parameters and packet discarding policies for different flows.
Prerequisites
l
The WFQ scheduling policy applicable to the V-UNI egress policy must be configured.
The WRED policy must be configured if the WRED packet discarding policy is required
by the V-UNI egress policy to control the flow.
When you configure a V-UNI egress policy, configure the following parameters:
l
Issue 03 (2012-11-30)

300
OptiX OSN 7500 II/7500/3500/1500

8 HQoS
Flow control parameters and packet discarding policies (such as tail drop or WRED) for
different CoSs
Procedure
Configuration > QoS Management > Policy Management > V-UNI Egress Policy from the
Function Tree.
Step 2 Click New. In the Create V-UNI Egress Policy dialog box that is displayed, set the following
parameters:
. In the WFQ Schedule Policy dialog box that is displayed, select the applied
Click
NOTE
Use the default WFQ scheduling policy (WFQ Default Scheduling).

NOTE
l The value of the CIR for queues CS7, CS6, and EF is equal to the value of the PIR for these queues.
The value of the CIR for the other queues is equal to or smaller than the value of the PIR for the
other queues.
l When you configure the value of the PIR for each queue, ensure that the maximum value is equal
to or smaller than 100 times of the minimum value.
at the same time.
Step 3 Click OK.

----End
Relation Operation
You can use the copy function to create a new V-UNI egress policy based on the created V-UNI
egress policy. The procedures are as follows:
1.
Click Copy. In the Duplicate QoS Policy dialog box that is displayed, select the policy to
be copied and then enter the new policy name. Click OK.
2.
Modify the parameters of the new policy, so that the new policy can meet the QoS
requirement.
NOTE
The copy function cannot copy the information about the applied policy.
8.9.11 Creating the PW Policy (OptiX OSN 3500/7500/7500 II)

Create the PW policy to specify the WFQ scheduling policy for the traffic on the network side
and to specify different flow control parameters and packet discarding policies (such as tail drop
or WRED) for different CoSs.
Issue 03 (2012-11-30)

301
OptiX OSN 7500 II/7500/3500/1500

8 HQoS
Prerequisites
l
The WFQ scheduling policy that is used by the PW policy must be configured.
The service WRED policy must be configured if the WRED packet discarding policy is
required by the PW policy to control the flow.
Procedure
Management > Policy Management > PW Policy from the Function Tree.
Step 2 Click New. When the Create PW Policy dialog box is displayed, set the following parameters:
Click
NOTE

NOTE
at the same time.
l The bandwidth and PW policy can be configured in the ingress direction of the PW other than in
the egress direction of the PW.
Step 3 Click OK.

----End
Related Information
Based on the PW policy that is created, you can create a new PW policy quickly by using the
1.
Click Copy. When the Duplicate QoS Policy is displayed, select the policy to be copied
and enter the name of the new policy. Click OK.
2.
requirement.
NOTE
Issue 03 (2012-11-30)

302
OptiX OSN 7500 II/7500/3500/1500

8 HQoS
8.9.12 Creating the QinQ Policy

Create the QinQ policy to specify the WFQ scheduling policy for the QinQ traffic on the network
side and to specify different flow control parameters and packet discarding policies (such as tail
drop or WRED) for different CoSs.
Prerequisites
l
The WFQ scheduling policy that is used by the QinQ policy must be configured.
The service WRED policy must be configured if the WRED packet discarding policy is
required by the QinQ policy to control the flow.
Procedure
Management > Policy Management > QinQ Policy from the Function Tree.
Step 2 Click New. When the Create QinQ Policy dialog box is displayed, set the following parameters:
Click
NOTE

NOTE
at the same time.
Step 3 Click OK.

----End
Related Information
Based on the QinQ policy that is created, you can create a new QinQ policy quickly by using
the copy function. Perform the following procedures:
1.
Click Copy. When the Duplicate QoS Policy is displayed, select the policy to be copied
and enter the name of the new policy. Click OK.
2.
requirement.
NOTE
Issue 03 (2012-11-30)

303
OptiX OSN 7500 II/7500/3500/1500

8 HQoS
8.9.13 Creating the CAR Policy (OptiX OSN 1500)

The CAR policy is mainly used at the edge of a network to limit the rate of the traffic that enters
the network, so that the rate of the traffic does not exceed the committed rate. When the traffic
rate of a connection exceeds the specified value, the packet can be discarded or the priority of
the packet can be re-set if the CAR is used.
Prerequisites
Procedure
Management > Policy Management > CAR Policy from the Function Tree.
Step 2 Click New. In the Create CAR Policy dialog box that is displayed, set the following parameters:
l CIR, PIR, CBS, and PBS
l Coloration mode and method for processing the marked packet
NOTE
The value of the PIR should not be less than the value of the CIR.
Step 3 Click OK.

----End

This topic considers the QoS configuration for the Ethernet service on the OptiX OSN 3500 as
an example. You can configure hierarchical QoS policies and apply these policies to the specified
Ethernet services to ensure the QoS.

This topic describes the networking and data planning of the example.
Several OptiX OSN NEs form a DiffServ domain, which provides ensured end-to-end QoS for
the Ethernet traffic.
The equipment that functions as the DS edge node provides hierarchical QoS control functions
for the Ethernet traffic.
l
Mapping relation between the service priority and the PHB service level
Hierarchical QoS policies

V-UNI ingress policy and V-UNI egress policy
PW policy
Hierarchical bandwidth control

Bandwidth control of the V-UNI group
Issue 03 (2012-11-30)

304
OptiX OSN 7500 II/7500/3500/1500

8 HQoS
NOTE
The bandwidths of the V-UNI group and the tunnel are configured when the service is created. For
details about how to configure the bandwidths of the V-UNI group and the tunnel, refer to the specific
topics. This topic focuses on the configuration and application of the QoS policy of each level.
The OptiX OSN equipment that functions as the internal DS node provides the following
hierarchical QoS control functions for the Ethernet traffic:
l
Mapping relation between the service priority and the PHB service level

NOTE
l The mapping relation between the service priority of the internal DS node and the PHB service level
should be consistent with the mapping relation between the service priority of the DS edge node and
the PHB service level. It is recommended that all the equipment uses the default mapping relations.
l The QoS configuration for the internal DS node is simpler than the configuration for the DS edge node.
This example describes only the QoS configuration for the DS edge node.
Figure 8-14 shows the QoS configuration for the Ethernet service.
Figure 8-14 Networking diagram of the QoS configuration for the Ethernet service
Access side
V-UNI
ingress
Port
Network side
PW Tunnel Port
V-UNI V-UNI
egress group
DiffServ domain
Tunnel
Ethernet
switch
OSN
(Edge DS node)
OSN
(Internal DS node)
OSN
(Edge DS node)
Core
switch
The OptiX OSN equipment accesses the Ethernet services (VLAN = 20, including VoIP, IPTV,
and data services) of a user to the DiffServ domain through the FE interface. In addition, the
OptiX OSN equipment provides different QoS levels for different types of services of the user.
Table 8-6 provides the requirements for the QoS configuration for the Ethernet service.
Issue 03 (2012-11-30)

305
OptiX OSN 7500 II/7500/3500/1500

8 HQoS
Table 8-6 Requirements for the QoS configuration for the Ethernet service
V-UNI Ingress Policy
V-UNI Egress Policy
PW policy
Flow classification parameters are

as follows:
l EF
l EF
l VoIP service
Network segment of the source
IP address: 129.5.1.0
PHB: EF
CIR: 2 Mbit/s
PIR: 2 Mbit/s
CIR: 2 Mbit/s
CIR: 2 Mbit/s
PIR: 2 Mbit/s
PIR: 2 Mbit/s
CBS: 120000 bytes
CBS: 120000 bytes
PBS: 10000000 bytes
PBS: 10000000 bytes
WRED: 1
WRED: 1
l AF4
l AF4
CIR: 6 Mbit/s
CIR: 6 Mbit/s
PIR: 16 Mbit/s
PIR: 16 Mbit/s
CBS: 120000 bytes
CBS: 120000 bytes
PHB: AF4
PBS: 10000000 bytes
PBS: 10000000 bytes
CIR: 6 Mbit/s
WRED: 1
WRED: 1
l IPTV service
PIR: 16 Mbit/s
l BE
l BE
CIR: 512 kbit/s
CIR: 512 kbit/s

PIR: 16 Mbit/s
PIR: 16 Mbit/s
CBS: 120000 bytes
CBS: 120000 bytes
PHB: BE
PBS: 10000000 bytes
PBS: 10000000 bytes
CIR: 512 kbit/s
WRED: 1
WRED: 1
l Data service
PIR: 16 Mbit/s
For details about the CoS
parameters, refer to the description
about the "V-UNI egress policy"
parameter.

This topic describes the configuration procedures for the example. The configuration includes
the domain configuration, and configuration and application of various QoS policies.
Prerequisites
You must be familiar with the networking and data planning of the example.
Procedure
Step 1 Configure the domain.
This example uses the default mapping relation between the service priority and the PHB service
level. Hence, no configuration is required.
l Mapping Relation ID: 1
Issue 03 (2012-11-30)

306
OptiX OSN 7500 II/7500/3500/1500

8 HQoS
l Mapping Relation Name: Default Map

NOTE
For the method for configuring the new mapping relation, see 8.9.2 Creating the DiffServ Domain.
Step 2 Configure the V-UNI ingress policy.

l Policy ID: 1
l Policy Name: V-UNI-Ingress
l WFQ Policy: Default value
l Traffic classification (ID = 1) parameters are as follows:
Traffic Classification ID: 1
ACL Action: Allowed
The ACL rule is as follows:
Match Type: Source IP; Match Value: 129.5.1.0; Wildcard: 129.5.1.255.
CAR parameters are as follows:
CoS
EF
Bandwidth Limit
Enabled
CIR
2 Mbit/s
PIR
2 Mbit/s
CBS
120000 bytes
PBS
10000000 bytes
Coloration Mode
Color Blindness
Packet Processing Mode
Default value

ACL Action: Allowed
CoS
AF4
Bandwidth Limit
Enabled
CIR
6 Mbit/s
PIR
16 Mbit/s
CBS
120000 bytes
PBS
10000000 bytes
Coloration Mode
Color Blindness
Packet Processing
Mode
Default value

ACL Action: Allowed
Issue 03 (2012-11-30)

307
OptiX OSN 7500 II/7500/3500/1500

8 HQoS
CoS
BE
Bandwidth Limit
Enabled
CIR
PIR
16 Mbit/s
CBS
120000 bytes
PBS
10000000 bytes
Coloration Mode
Color Blindness
Packet Processing
Mode
Default value
l CoS parameters are as follows:

CoS
EF
Bandwidth Limit
Enabled
CIR
2 Mbit/s
PIR
2 Mbit/s
CBS
120000 bytes
PBS
10000000 bytes
Tail Drop
WRED
service-wred
CoS
AF4
Bandwidth Limit
Enabled
CIR
6 Mbit/s
PIR
16 Mbit/s
CBS
120000 bytes
PBS
10000000 bytes
Tail Drop
WRED
service-wred
CoS
BE
Bandwidth Limit
Enabled
CIR
PIR
16 Mbit/s
CBS
120000 bytes
PBS
10000000 bytes
Tail Drop
WRED
service-wred
NOTE
For the method for configuring the V-UNI ingress policy, see 8.9.8 Creating the V-UNI Ingress Policy
(OptiX OSN 3500/7500/7500 II).
Step 3 Configure the V-UNI egress policy.

l Policy ID: 1
l Policy Name: V-UNI-Egress
Issue 03 (2012-11-30)
CoS
EF
Bandwidth Limit
Enabled
CIR
2 Mbit/s
PIR
2 Mbit/s
CBS
120000 bytes
PBS
10000000 bytes

308
OptiX OSN 7500 II/7500/3500/1500

8 HQoS
Tail Drop
WRED
service-wred
CoS
AF4
Bandwidth Limit
Enabled
CIR
6 Mbit/s
PIR
16 Mbit/s
CBS
120000 bytes
PBS
10000000 bytes
Tail Drop
WRED
service-wred
CoS
BE
Bandwidth Limit
Enabled
CIR
PIR
16 Mbit/s
CBS
120000 bytes
PBS
10000000 bytes
Tail Drop
WRED
service-wred
NOTE
For the method for configuring the V-UNI egress policy, see 8.9.10 Creating a V-UNI Egress Policy.
Step 4 Configure the PW policy.

l Policy ID: 1
l Policy Name: PW-Policy
Issue 03 (2012-11-30)
CoS
EF
Bandwidth Limit
Enabled
CIR
2 Mbit/s
PIR
2 Mbit/s
CBS
120000 bytes
PBS
10000000 bytes
Tail Drop
WRED
service-wred
CoS
AF4
Bandwidth Limit
Enabled
CIR
6 Mbit/s
PIR
16 Mbit/s
CBS
120000 bytes
PBS
10000000 bytes
Tail Drop
WRED
service-wred
CoS
BE
Bandwidth Limit
Enabled

309
OptiX OSN 7500 II/7500/3500/1500

8 HQoS
CIR
PIR
16 Mbit/s
CBS
120000 bytes
PBS
10000000 bytes
Tail Drop
WRED
service-wred
NOTE
For the method for configuring the PW policy, see 8.9.11 Creating the PW Policy (OptiX OSN
3500/7500/7500 II).
Step 5 Apply the port policy.

This example does not use the port policy. Hence, go to the next step.
NOTE
If the port policy needs to be applied, see 8.9.6 Creating the Port Policy (OptiX OSN 3500/7500/7500
II).
Step 6 Configure the tunnel.

Set the bandwidth of the tunnel to 16 Mbit/s when creating the MPLS tunnel.
NOTE
For the method for configuring the tunnel, see Configuring an MPLS Tunnel.
Step 7 Configure the Ethernet service and apply the V-UNI ingress policy, V-UNI egress policy, and
PW policy.
Apply the following policies when configuring the Ethernet service:
l V-UNI ingress policy:
Policy ID: 1
Policy Name: V-UNI-Ingress
l V-UNI egress policy
Policy ID: 1
Policy Name: V-UNI-Egress
l PW policy
Policy ID: 1
Policy Name: PW-Policy
NOTE
For the method for configuring the Ethernet service, see Configuring E-Line Services, Configuring E-LAN
Services, or Configuring E-AGGR Services.
Before applying the V-UNI Ingress and PW polices, you need to set the service bandwidth.
----End
Following a certain troubleshooting flow facilitates your fault locating and rectification. This
topic considers an HQoS fault on the OptiX OSN 3500 equipment as an example to describe
how to handle an HQoS fault, helping you handle HQoS faults on other types of equipment.
Issue 03 (2012-11-30)

310
OptiX OSN 7500 II/7500/3500/1500

8 HQoS
Fault Symptom
The common HQoS fault symptoms are as follows:
l
Actual traffic volume exceeds the bandwidth configured for a service. As a result, traffic
congestion occurs.
Services pre-empt bandwidth from each other. As a result, packet loss or bit errors occur
in the service whose bandwidth is pre-empted.
The service with a lower priority pre-empts the bandwidth allocated to the service with a
higher priority. As a result, packet loss or bit errors occur in the service with a higher
priority.
The service processing board reports the BUS_ERR alarm and therefore the service
processing capability is affected.
Possible Causes
l
Cause 1: The service processing board reports the BUS_ERR alarm and therefore the
service processing capability is affected.
Cause 2: No QoS policy is configured for the NE.
Cause 3: An incorrect QoS policy is selected during data configuration.
Cause 4: The bandwidth configured for a tunnel or PW is very low.
Cause 5: A certain board becomes faulty and as a result, the configuration data is not
successfully delivered to the board.
Troubleshooting Flow
Following a certain troubleshooting flow facilitates your fault locating and rectification.
Issue 03 (2012-11-30)

311
OptiX OSN 7500 II/7500/3500/1500

8 HQoS
Figure 8-15 Flow chart for handling an HQoS fault

Start
Does the
BUS_ERR
alarm exist?
Yes
Reseat/Replace
the board
Yes
Configure
QoS policies
Yes
Configure
new policies
Yes
Increase the
bandwidth
No
No QoS policy
configured?
No
Is an incorrect
QoS policy
configured?
No
Is the
bandwidth
configured for a
tunnel or PW
very low?
No
Do hardware
alarms exist?
Yes
Clear the
alarms
No
Is the fault
rectified?
Yes
Contact Huawei technical

support engineers
End
Procedure
Step 1 Cause 1: The service processing board reports the BUS_ERR alarm and therefore the service
processing capability is affected.
1.
Check whether the BUS_ERR alarm exists in the system.
2.
If yes, clear the alarm. For details on how to clear the alarm, see the Alarms and
Performance Events Reference.
Step 2 Cause 2: No QoS policy is configured for the NE.

1.
Check whether the NE is configured with associated QoS policies, including the V-UNI
ingress policy, V-UNI egress policy, PW policy, and QinQ policy.
2.
If no policy is configured, configure required QoS policies for the NE.
Step 3 Cause 3: An incorrect QoS policy is selected during data configuration.

Issue 03 (2012-11-30)

312
OptiX OSN 7500 II/7500/3500/1500

1.
8 HQoS
Check whether the configured QoS policies are applicable to the services. If not, configure
new policies again.
Step 4 Cause 4: The bandwidth configured for a tunnel or PW is very low.

1.
Check whether the bandwidth configured for the tunnel or PW meets the traffic
requirements. If the configured bandwidth is very low, configure the bandwidth again.
Step 5 Cause 5: A certain board becomes faulty and as a result, the configuration data is not successfully
delivered to the board.
1.
Check whether hardware alarms such as HARD_BAD exist in the system. If yes, clear the
alarms. For details on how to clear the alarms, see the Alarms and Performance Events
Reference.
Step 6 If the fault persists, contact Huawei technical support engineers to handle the fault.
----End
8.12 Parameter Description: HQoS

8.12.1 Diffserv Domain Management

Configuring the HQoS Diffserv domain management is mainly to map the services from different
queues to different Per-Hop Behaviors (PHBs).
Table 8-7 lists the parameters for Diffserv domain management.
Table 8-7 Parameters for Diffserv domain management
Field
Value
Description
Mapping Relation ID
1, 2 to 8
Sets the ID of the mapping relations.

The ID identifies a set of mapping
relations.
If the ID is set to 1, it indicates the
default Diffserv domain, which
cannot be deleted. The default
Diffserv domain, however, can be
queried. You can create, modify,
delete, and query the other seven (2
to 8) Diffserv domains.
Issue 03 (2012-11-30)

313
OptiX OSN 7500 II/7500/3500/1500

8 HQoS
Field
Value
Description
Mapping Relation Name
32 bytes
Sets the name of the mapping

relation.
The mapping relations include the
ingress mapping relation and egress
mapping relation. In the case of the
ingress mapping relation, priorities
of various user packets are mapped
into the CoS of the equipment. In the
case of the egress mapping relation,
the CoS of the equipment is mapped
into priorities of various user
packets.
CVLAN
0 to 7
Sets the priority of the CVLAN.

CVLAN indicates the client-side
VLAN. 7 indicates the highest
priority.
SVLAN
0 to 7
Sets the priority of the SVLAN.

SVLAN indicates the network-side
VLAN. 7 indicates the highest
priority.
DEISVLAN
0 to 15
Sets the priority of the DEISVLAN.

DEISVLAN indicates that a discard
priority is attached on the SVLAN.
NOTE
If mapping by DEISVLAN is required,
enable SVLAN DEI in SVLAN DEI
Used Flag.
IP DSCP
0 to 63
Sets the priority of the IP DSCP.

The DSCP section is a part of the
service type section of the IP header,
and labels the priority on packets.
MPLS EXP
0 to 7
Sets the priority of the MPLS EXP.

EXP indicates the three bits of the
MPLS packets, and carries the
Diffserv information in the MPLS.
PHB
BE, AF11, AF12,

AF13, AF21, AF22,
AF23, AF31, AF32,
AF33, AF41, AF42,
AF43, EF, CS6, CS7
The PHB parameter, per hop

behavior, indicates a forwarding
action applicable on the DS node.
This forwarding action belongs to the
per hop forwarding aggregation
defined in the DiffServ domain.
Click A.10.24 PHB (Diffserv
domain Management) for more
information.
Issue 03 (2012-11-30)

314
OptiX OSN 7500 II/7500/3500/1500

8 HQoS
Field
Value
Description
Board
For example, 5N1PEG16
Selects the board that adopts the

mapping relationships between
Diffserv domains.
Available Port
Slot number - Board

name- Port number
(customize the port
name)
Lists the ports available on the board.
For example, 5N1PEG16-1(PORT-1)

For example, 1N1PEG16
Selected Port
Slot number - Board

name- Port number
(customize the port
name)
Lists selected ports on the board.

Port
Displays selected ports.

Packet Type
cvlan, svlan, mpls-exp,

ip-dscp
The Packet Type is used to set the

packet type.
Default: -
Click A.10.25 Packet Type

(Diffserv domain Management)
for more information.
8.12.2 Service WRED Policy

The service WRED policy is to adopt the policy of discarding certain packets according to the
packet color when a queue buffer is not full, therefore minimizing congestion events on a
network.
Table 8-8 lists the parameters for a service WRED policy.
Issue 03 (2012-11-30)

315
OptiX OSN 7500 II/7500/3500/1500

8 HQoS
Table 8-8 Parameters for a service WRED policy

Field
Value
Description
Policy ID
For example, 5
The Policy ID (Policy

Management) parameter identifies
a policy.
Click A.10.8 Policy ID(Policy
information.
Automatically Assign
Checked, Unchecked
Selects whether the ID is allocated

automatically.
Policy Name
64 bytes
The Policy Name (Policy

Management) parameter specifies
the name of a policy and thus
identifies a policy. Different policies
can have the same policy name.
Click A.10.9 Policy Name (Policy
information.
Packet Color
Red, Yellow, Green
Packets may be marked red, yellow

or green. Different colors indicate
different priorities for packet
discarding. The packets marked in
red are discarded with the highest
priority.
Discard Lower Threshold

(256 bytes)
0-4095
Users can set Discard Lower

Threshold and Discard Upper
Threshold for a queue. When the
length of a queue is less than the
specified value of Discard Lower
Threshold, the packet is not
discarded. When the length of a
queue is within the range from the
Threshold to the specified value of
Discard Upper Threshold, the
weighted random early detection
(WRED) mechanism discards
packets at random. When the length
of a queue is more than the specified
value of Discard Upper
Threshold, the packet is discarded
according to the discard probability
that is set by the user.
Click A.10.22 Discard Upper
Threshold (256 bytes) (Service
WRED Policy) for more
information.
Issue 03 (2012-11-30)

316
OptiX OSN 7500 II/7500/3500/1500

8 HQoS
Field
Value
Description
Discard Upper Threshold

(256 bytes)
0-4095
Users can set Discard Lower

Threshold and Discard Upper
Threshold for a queue. When the
length of a queue is less than the
Threshold, the packet is not
discarded. When the length of a
queue is within the range from the
Threshold to the specified value of
Discard Upper Threshold, the
weighted random early detection
(WRED) mechanism discards
packets at random. When the length
of a queue is more than the specified
Threshold, the packet is discarded
according to the discard probability
that is set by the user.
Click A.10.22 Discard Upper
Threshold (256 bytes) (Service
WRED Policy) for more
information.
Discard Probability (%)
1-100
Default: 100
The Discard Probability (%)

(Service WRED Policy) parameter
specifies the ratio of the packets that
are discarded to the total number of
packets in a queue when the length of
a queue is more than the specified
Threshold.
Click A.10.23 Discard Probability
(%) (Service WRED Policy) for
more information.
8.12.3 WFQ Schedule Policy

A WFQ schedule policy is used for setting the schedule weight of queues AF1-AF4.
Table 8-9 lists the parameters for a WFQ schedule policy.
Issue 03 (2012-11-30)

317
OptiX OSN 7500 II/7500/3500/1500

8 HQoS
Table 8-9 Parameters for a WFQ schedule policy

Field
Value
Description
Policy ID
For example, 5

a policy.
information.
Checked, Unchecked

automatically.
Policy Name
64 bytes

information.
AF1 Schedule Weight(%)
1-100
Default: 25
The QoS scheduling modes include

eight queues. The scheduling
algorithm is: Schedule the CS7
queue > schedule the CS6 queue >
schedule the EF queue > schedule the
AF1-AF4 queues according to the
weights of the queues > schedule the
BE queue. The AF1 Schedule
Weight parameter indicates the
percentage of the AF1 queue to the
weight when the AF1-AF4 queues
are scheduled according to the
weight.
Click A.10.17 AF1 Schedule
Weight(%)(WFQ Schedule
Policy) for more information.
Issue 03 (2012-11-30)

318
OptiX OSN 7500 II/7500/3500/1500

8 HQoS
Field
Value
Description
1-100

weight.
Default: 25

1-100
Default: 25

weight.
1-100
Default: 25

weight.
Issue 03 (2012-11-30)

319
OptiX OSN 7500 II/7500/3500/1500

8 HQoS
8.12.4 Port Policy

Configuring a port policy focuses on setting of the parameters such as CoS, Tail Drop
Threshold (%), Port WRED Policy, and WFQ Schedule Policy.
Table 8-10 lists the parameters for a port policy.
Table 8-10 Parameters for a port policy
Field
Value
Description
Policy ID
For example, 5
Sets and displays the ID of

the policy.
Checked, Unchecked
Selects whether the ID is

allocated automatically.
Policy Name
64 bytes
Sets and displays the name

of the policy.
Traffic Classification
Bandwidth Sharing
Enabled, Disabled
Set the Traffic

Classification Bandwidth
Sharing parameter to
enable or disable the traffic
classification bandwidth
sharing.
Default: Disabled
Click A.10.13 Traffic

Classification Bandwidth
Sharing(Policy
information.
Issue 03 (2012-11-30)

320
OptiX OSN 7500 II/7500/3500/1500

8 HQoS
Field
Value
Description
CoS
CS7, CS6, EF, AF4, AF3, AF2,

AF1, BE
Defines different service

classes.
l CS6-CS7: Indicates the
highest service class.
The CoS is applicable to
transport of signaling.
l EF: Indicates fast
forwarding. The CoS is
applicable to the service
of little delay and packet
loss rate, such as the
audio and video
services.
l AF1-AF4: Indicates the
guaranteed forwarding.
The CoS is applicable to
the service that requires
a certain rate, but does
not limit the delay or
jitter.
l BE: Indicates the traffic
that need not be
processed
exceptionally.
Issue 03 (2012-11-30)
Bandwidth Limit
Enabled, Disabled
The CIR, PIR, CBS, PBS,

Tail Drop Threshold and
Port WRED Policy can be
set only when Bandwidth
Limit is set to Enabled.
CIR (kbit/s)
1000 to 10000000
Sets the committed

information rate (CIR).
only when Bandwidth
The CIR and PIR of CS7
should be the same as those
of CS6.
PIR (kbit/s)
1000 to 10000000
Sets the maximum rate for

the service to pass. This
parameter can be set only
when Bandwidth Limit is
set to Enabled.

321
OptiX OSN 7500 II/7500/3500/1500

8 HQoS
Field
Value
Description
CBS (byte)
2 to 64000
Sets the committed burst

size for the traffic to pass in
a short time. This parameter
can be set only when
Bandwidth Limit is set to
Enabled.
PBS (byte)
2 to 64000
Sets the peak burst size.

only when Bandwidth
Tail Drop Threshold (%)
0 to 100
Sets the tail drop threshold.

Tail drop threshold refers to
the percentage of the buffer
space used by a queue to the
total buffer size. When the
length of the queue exceeds
the value that is equal to the
tail drop threshold
multiplied by the buffer
size, all subsequent packets
are dropped. You can set
either Tail Drop
Threshold or Port WRED
Policy, but not both.
Port WRED Policy
Policy ID-Policy Name
After bandwidth limit is

enabled, you can select the
default port WRED policy.
For example, 1-default port

wred
If the queue length is

smaller than the lower drop
threshold, the packets are
not dropped. If the queue
length is between the lower
drop threshold and the
upper drop threshold, the
packets are randomly
discarded. If the queue
length is greater than the
upper drop threshold, all the
packets are dropped. You
can set either Tail Drop
Threshold (%) or Port
WRED Policy, but not
both.
Issue 03 (2012-11-30)

322
OptiX OSN 7500 II/7500/3500/1500

8 HQoS
Field
Value
Description
WFQ Schedule Policy
Selects the configured

WFQ policy in the
displayed dialog box.
Related parameters in the
dialog box are set in WFQ
Schedule Policy. For
details, see 8.12.3 WFQ
Schedule Policy.
For example, 1-WFQ Default

Scheduling
Board
Sets and queries the board

with the port supporting
this policy.
Available Port

(PORT-6)
Lists the ports available on

the board.
Selected Port

(PORT-6)
Lists selected ports on the

board.
Traffic Classification ID
For example, 2
Sets and displays the ID of

the traffic classification.
Traffic Classification Rule
For example, Protocol Type:

TCP
The Traffic Classification

Rule parameter indicates
the rules for classifying
service packets.
Classification Rule(Policy
information.
Permit, Deny
ACL Action
Sets the ACL of the traffic

classification.
The ACL is used to classify
the received packets to
decide whether to forward
or discard packets.
Logical Relation Between

Matched Rules
And, Or
Default: And
When multiple traffic

classification rules are set
for a flow, set the Logical
Relation Between
Matched Rules parameter
to specify the logical
relations among these
traffic classification rules.
Click A.10.15 Logical
Relation Between
Matched Rules(V-UNI
Ingress Policy) for more
information.
Issue 03 (2012-11-30)

323
OptiX OSN 7500 II/7500/3500/1500

8 HQoS
Field
Value
Description
Match Type
Source IP, Destination IP,

Source MAC Address,
Destination MAC Address,
Protocol Type, Source Port,
Destination Port, ICMP Packet
Type, DSCP Value, IPPrecedence Value, CVlan ID,
CVlan priority, SVlan ID, SVlan
priority, DEI
Each data packet has many

feature values such as the IP
address, MAC address, and
port number. These feature
values can be considered as
match types among the
Default: Source IP, Destination IP,

Source MAC Address,
Type, DSCP Value, IPPrecedence Value, CVlan ID,
priority, DEI
Match Value
Default: -
Click A.10.2 Match Type

(Policy Management) for
more information.
The Match Value
parameter indicates the
value set for a specific
match type among the
If certain bits of the match
type value (source IP
address, for example) are
consistent with the
mapping bits of the match
value of the traffic
classification rule, the
packets match with the
traffic classification rule.
Click A.10.3 Match Value
more information.
Source IP, Destination IP,

Source MAC Address,
Type, DSCP Value, IPPrecedence Value, CVLAN ID,
CVLAN Priority, SVLAN ID,
SVLAN Priority, DEI
Wildcard
The Wildcard parameter

indicates that the packets
need match only a portion
of the match values.
Click A.10.4 Wildcard
more information.
Default: -
Issue 03 (2012-11-30)
Duplicated Policy Name
For example, QoS-test
Selects the name of the

duplicated policy.
New Policy Name
For example, Test
Sets the name of the new

policy generated by
duplicating another one.

324
OptiX OSN 7500 II/7500/3500/1500

8 HQoS
8.12.5 V-UNI Ingress Policy

Configuring a V-UNI ingress policy is to classify the incoming traffic and to specify the WFQ
schedule policy, CAR parameters, CoS parameters, and packet discarding policy.
Table 8-11 lists the parameters for a V-UNI ingress policy.
Table 8-11 Parameters for a V-UNI ingress policy
Field
Value
Description
Policy ID
For example, 5

Management) parameter
identifies a policy.
Click A.10.8 Policy ID
(Policy Management)
Checked, Unchecked
Selects whether the ID is

Policy Name
64 bytes

Management) parameter
specifies the name of a
policy and thus identifies
a policy. Different
policies can have the
same policy name.
Click A.10.9 Policy
Name (Policy
information.
Traffic Classification
Bandwidth Sharing
Enabled, Disabled
Default: Disabled
Set the Traffic

Classification
Bandwidth Sharing
parameter to enable or
disable the traffic
classification bandwidth
sharing.
Classification
Bandwidth Sharing
(Policy Management)
Issue 03 (2012-11-30)

325
OptiX OSN 7500 II/7500/3500/1500

8 HQoS
Field
Value
Description
WFQ Schedule Policy
Selects the configured

WFQ policy in the
displayed dialog box.
dialog box are set in
WFQ Schedule Policy.
For details, see 8.12.3
WFQ Schedule Policy.
For example, 1-WFQ Default

Scheduling

AF1, BE
CoS
Defines different service

classes.
l CS6-CS7: Indicates
the highest service
class. The CoS is
applicable to transport
of signaling.
l EF: Indicates fast
forwarding. The CoS
is applicable to the
service of little delay
and packet loss rate,
such as the audio and
video services.
l AF1-AF4: Indicates
the guaranteed
forwarding. The CoS
is applicable to the
service that requires a
certain rate, but does
not limit the delay or
jitter.
l BE: Indicates the
traffic that need not be
processed
exceptionally.
Enable Bandwidth
Restriction
Issue 03 (2012-11-30)
Disabled, Enabled

The CIR, PIR, CBS,

PBS, Tail Drop
Threshold and Port
WRED Policy can be set
only when Bandwidth
326
OptiX OSN 7500 II/7500/3500/1500

8 HQoS
Field
Value
Description
CIR(kbit/s)
64 to 10000000, 64 as the spacing
Sets the committed

information rate (CIR).
only when Bandwidth
The CIR and PIR of CS7
should be the same as
those of CS6.
Default value: 320
PIR(kbit/s)
Default value: 320
CBS(byte)
64 to 131072
l In the CoS Configuration tab:
Default value: 64
l In the Traffic Classification
Configuration tab:
16000 to 10000000, 64 as the
spacing
PBS(byte)
64 to 16777216
l In the CoS Configuration tab:
64 to 16777216, 64 as the
spacing
Sets the maximum rate

for the service to pass.
only when Bandwidth
Sets the committed burst
size for the traffic to pass
in a short time. This
parameter can be set only
when Bandwidth Limit
is set to Enabled.
Sets the peak burst size.

only when Bandwidth
Default value: 64
l In the Traffic Classification
Configuration tab:
16000 to 10000000, 64 as the
spacing
Tail Drop Threshold (256
bytes)
0 to 4095
Sets the tail drop

threshold.
When the queue length
exceeds the tail drop
threshold, the tail packets
are discarded. Set either
Tail Drop Threshold or
Service WRED Policy,
but not both.
Issue 03 (2012-11-30)

327
OptiX OSN 7500 II/7500/3500/1500

8 HQoS
Field
Value
Description
Coloring Mode
Color-Blind, Chromatic-Sensitive
The Coloring Mode (VUNI Ingress Policy)

parameter specifies the
coloring mode of a certain
flow. Therefore, this
parameter specifies
whether the original color
of the packets in this flow
is considered when the
CAR processing is
performed on these
packets.
Default: Color-Blind
Click A.10.14 Coloring

Mode (V-UNI Ingress
Policy) for more
information.
Service WRED Policy
For example, 1-WRED policy
After bandwidth limit is

enabled, double-click the
cell to display a dialog
box where you need
select the configured
service WRED policy.
dialog box are set in
Service WRED Policy.
For details, see 8.12.2
Service WRED Policy.
When the queue length is
lower than the discard
lower threshold, no
packets are discarded.
higher than the discard
lower threshold but lower
than the discard upper
threshold, packets are
discarded randomly.
higher than the discard
upper threshold, all
packets are discarded. Set
either Tail Drop
Threshold or Service
WRED Policy, but not
both.
Traffic Classification ID
Issue 03 (2012-11-30)
For example, 2

Sets and displays the ID

of the traffic
classification.
328
OptiX OSN 7500 II/7500/3500/1500

8 HQoS
Field
Value
Description
Traffic Classification Rule
For example, Protocol Type: TCP
The Traffic
Classification Rule
rules for classifying
service packets.
Classification Rule
(Policy Management)
ACL Action
Permit, Deny
Sets the ACL of the traffic

classification. The ACL
is used to classify the
received packets to
decide whether to
forward or discard
packets.
Logical Relation Between

Matched Rules
And, Or
When multiple traffic

classification rules are set
for a flow, set the Logical
Relation Between
Matched Rules
parameter to specify the
logical relations among
these traffic classification
rules.
Default: And
Click A.10.15 Logical

Relation Between
Matched Rules(V-UNI
Ingress Policy) for more
information.
Match Type
Issue 03 (2012-11-30)
Source IP, Destination IP, Source

MAC Address, Destination MAC
Address, Protocol Type, Source
Port, Destination Port, ICMP
Packet Type, DSCP Value, IPPrecedence Value, CVlan ID,
priority, DEI
Each data packet has

many feature values such
as the IP address, MAC
address, and port number.
These feature values can
be considered as match
types among the traffic
classification rules.
Default: -
Click A.10.2 Match

Type(Policy
information.

329
OptiX OSN 7500 II/7500/3500/1500

8 HQoS
Field
Value
Description
Match Value

Packet Type, DSCP Value, IPPrecedence Value, CVlan ID,
priority, DEI
The Match Value

value set for a specific
match type among the
traffic classification
rules. If certain bits of the
match type value (source
IP address, for example)
are consistent with the
mapping bits of the match
value of the traffic
classification rule, the
packets match with the
Click A.10.3 Match
Value(Policy
information.

Packet Type, DSCP Value, IPPrecedence Value, CVLAN ID,
CVLAN Priority, SVLAN ID,
SVLAN Priority, DEI
The Wildcard parameter

indicates that the packets
need match only a portion
of the match values.
Packet Color
Red, Yellow, Green
Marks packets in red,

yellow or green. The
packets marked in red are
discarded with the
highest priority.
Processing Mode
Pass, Discard, Remark
The Processing Mode

processing mode for
packets of different
colors.
Wildcard
Default:
l Green, yellow: Pass
l Red: Discard
Click A.10.4 Wildcard

(Policy Management)
Click A.10.16
Processing Mode(VUNI Ingress Policy) for
more information.
Re-Mark CoS

AF1, BE
Re-marks the packet CoS

when Processing Mode
is set to Remark.
NOTE
OptiX OSN 1500 does not
support Re-Mark CoS.
Issue 03 (2012-11-30)

330
OptiX OSN 7500 II/7500/3500/1500

8 HQoS
Field
Value
Description
Re-Mark Color
Red, Yellow, Green, None
Re-marks color for

packets when Processing
Mode is set to Remark.
Default: None
Service ID
For example, 123
Queries the ID of the

service object to which
the policy is applied.
Interface

(PORT-3)[23]
Queries the interface to

which the policy is
applied.
V-UNI ID
For example, 1
Queries the V-UNI to

which the policy is
applied.
Selects the name of the

duplicated policy.
New Policy Name
For example, Test
Sets the name of the new

policy generated by
duplicating another one.
8.12.6 V-UNI Egress Policy

Configuring a V-UNI egress policy is to specify the WFQ schedule policy for the egress traffic
on the access side and to specify different traffic control parameters and packet discarding
policies for different traffic.
Table 8-12 lists the parameters for a V-UNI egress policy.
Table 8-12 Parameters for a V-UNI egress policy
Field
Value
Description
Policy ID
For example, 5

a policy.
information.
Issue 03 (2012-11-30)
Checked, Unchecked

automatically.

331
OptiX OSN 7500 II/7500/3500/1500

8 HQoS
Field
Value
Description
Policy Name
64 bytes

information.
WFQ Schedule Policy
For example, 1-WFQ

Default Scheduling
Selects the configured WFQ

schedule policy in the displayed
dialog box. Related parameters in the
dialog box are set in WFQ Schedule
Policy. For details, see 8.12.3 WFQ
Schedule Policy.
CoS
CS7, CS6, EF, AF4,

AF3, AF2, AF1, BE
Defines different service classes.

l CS6-CS7: Indicates the highest
service class. The CoS is
applicable to transport of
signaling.
l EF: Indicates fast forwarding.
The CoS is applicable to the
service of little delay and packet
loss rate, such as the audio and
video services.
guaranteed forwarding. The CoS
is applicable to the service that
requires a certain rate, but does
not limit the delay or jitter.
l BE: Indicates the traffic that need
not be processed exceptionally.
Issue 03 (2012-11-30)
Bandwidth Limit
Disabled, Enabled
The CIR, PIR, CBS, PBS, Tail

Drop Threshold and Port WRED
Policy can be set only when
Enabled.
CIR (kbit/s)
320 to 10000000
Sets the committed information rate

(CIR). This parameter can be set only
when Bandwidth Limit is set to
Enabled. The CIR and PIR of CS7
should be the same as those of CS6.
PIR (kbit/s)
320 to 10000000
Sets the maximum rate for the

service to pass. This parameter can
be set only when Bandwidth Limit
is set to Enabled.

332
OptiX OSN 7500 II/7500/3500/1500

8 HQoS
Field
Value
Description
CBS (byte)
64 to 131072
Sets the committed burst size for the

traffic to pass in a short time. This
parameter can be set only when
Enabled.
PBS (byte)
64 to 16777216
Sets the peak burst size. This

Enabled.

bytes)
0 to 4095
Service WRED Policy
For example, 1-WRED

policy
When the queue length exceeds the

tail drop threshold, the tail packets
are discarded. Set either Tail Drop
Threshold or Service WRED Policy,
but not both.
After bandwidth limit is enabled,
double-click the cell to display a
dialog box where you need select the
configured service WRED policy.
Related parameters in the dialog box
are set in Service WRED Policy. For
details, see 8.12.2 Service WRED
Policy.
When the queue length is lower than
the discard lower threshold, no
packets are discarded. When the
queue length is higher than the
discard lower threshold but lower
than the discard upper threshold,
packets are discarded randomly.
When the queue length is higher than
the discard upper threshold, all
packets are discarded. Set either Tail
Drop Threshold or Service WRED
Issue 03 (2012-11-30)
Service ID
For example, 123
Queries the ID of the object to which

the policy is applied.
Interface

[23]
Queries the interface to which the

policy is applied.
Selects the name of the duplicated

policy.
New Policy Name
For example, Test
Sets the name of the new policy

generated by duplicating another
one.

333
OptiX OSN 7500 II/7500/3500/1500

8 HQoS
8.12.7 PW Policy
Configuring a PW policy is to specify the WFQ schedule policy for the traffic on the network
side and to specify different traffic control parameters and packet discarding policies (such as
tail drop or WRED) for different classes of services.
Table 8-13 lists the parameters for a PW policy.
Table 8-13 Parameters for a PW policy
Field
Value
Description
Policy ID
For example, 5

Management) parameter identifies a
policy.
Management) for more information.
Checked, Unchecked

automatically.
Policy Name
64 bytes

Management) for more information.
WFQ Schedule Policy
Policy ID-Policy
Name
For example, 1-WFQ
Default Scheduling
Issue 03 (2012-11-30)

dialog box are set in WFQ Schedule
Policy. For details, see 8.12.3 WFQ
Schedule Policy.

334
OptiX OSN 7500 II/7500/3500/1500

8 HQoS
Field
Value
Description
CoS
CS7, CS6, EF, AF4,

AF3, AF2, AF1, BE

l CS6-CS7: Indicates the highest
service class. The CoS is
applicable to transport of
signaling.
l EF: Indicates fast forwarding.
The CoS is applicable to the
service of little delay and packet
loss rate,
guaranteed forwarding. The CoS
is applicable to the service that
requires a certain rate, but does
not limit the delay or jitter.
l BE: Indicates the traffic that need
not be processed exceptionally,
such as the audio and video
service traffic.
Bandwidth Limit
Enabled, Disabled

Drop Threshold and Port WRED
Policy can be set only when
Bandwidth Limit is set to Enabled.
CIR (kbit/s)
320 to 10000000
Sets the committed information rate

(CIR). This parameter can be set only
when Bandwidth Limit is set to
Enabled. The CIR and PIR of CS7
should be the same as those of CS6.
PIR (kbit/s)
320 to 10000000
Sets the maximum rate for the service

to pass. This parameter can be set
only when Bandwidth Limit is set to
Enabled.
CBS (byte)
64 to 131072
Sets the committed burst size for the

traffic to pass in a short time. This
PBS (byte)
64 to 16777216
Sets the peak burst size. This


bytes)
0 to 4095

are discarded.
Set either Tail Drop Threshold or
Service WRED Policy, but not both.
Issue 03 (2012-11-30)

335
OptiX OSN 7500 II/7500/3500/1500

8 HQoS
Field
Value
Description
Service WRED Policy
Policy ID-Policy
Name
After bandwidth limit is enabled,

Policy.
For example, 1WRED policy

packets are discarded. Set either Tail
Drop Threshold or Service WRED
PW ID
For example, 1005
Sets the ID of the object to which the

PW policy is applied.
Signal Type
Dynamic, Automatic
In the case of the dynamic PW, the

label is automatically allocated. In
the case of the static PW, the label is
manually allocated. The
configuration at the two ends of a PW
should be consistent.
PW Type
Ethernet, Ethernet Tag
PWs of different types process the

borne services differently. For
example, the PW in the Ethernet
tagged mode attaches the tag on the
services on this PW.
PW Direction
Bidirectional,
Unidirectional
In the case of one PW, two directions,

that is, the direction of entering the
network and the direction of exiting
the network, are available. The PW
Direction parameter indicates
whether the PW processes one
direction or two directions.
Click A.10.5 PW Direction(PW
Issue 03 (2012-11-30)

336
OptiX OSN 7500 II/7500/3500/1500

8 HQoS
Field
Value
Description
Direction
Ingress, Egress
The Direction (PW Policy)

parameter indicates the direction for
the policy application.
Click A.10.6 Direction (PW
For example, PW-test
The Duplicated Policy Name (PW

Policy) parameter has the same
meaning as the Policy Name
parameter and indicates the policy
based on which a new policy is
created.
Click A.10.7 Duplicated Policy
Name(PW Policy) for more
information.
New Policy Name
For example, Test
Sets the name of the new policy

generated by duplicating another
one.
8.12.8 QinQ Policy

Configuring a QinQ policy is to specify the WFQ schedule policy for the QinQ traffic on the
network side and to specify different traffic control parameters and packet discarding policies
(such as tail drop or WRED) for different classes of services.
Table 8-14 lists the parameters for a QinQ policy.
Table 8-14 Parameters for a QinQ policy
Field
Value Range
Description
Policy ID
For example, 5

a policy.
information.
Issue 03 (2012-11-30)
Checked, Unchecked
Specifies whether the ID is

automatically assigned.

337
OptiX OSN 7500 II/7500/3500/1500

8 HQoS
Field
Value Range
Description
Policy Name
A maximum of 64
bytes

information.
WFQ Scheduling Policy
For example, 1-WFQ

Default Scheduling

dialog box are set in WFQ
Scheduling Policy. For details, see
8.12.3 WFQ Schedule Policy.
CoS
CS7, CS6, EF, AF4,

AF3, AF2, AF1, BE

l CS6-CS7: indicates the highest
service class, which is mainly
involved in signaling
transmission.
l EF: indicates the expedited
forwarding of service, which is
applicable to services of low
transmission delay and low
packet loss rate, like voice and
video services.
l AF1-AF4: indicate the assured
forwarding class of service,
which is applicable to services
that require an assured rate rather
than delay or jitter limit.
l BE: is applicable to services that
need not be processed in a special
manner.
Issue 03 (2012-11-30)
Enable Bandwidth
Restriction
Disabled, Enabled

Drop Threshold (256 bytes), and
Service WRED Policy parameters
can be set only when Enable
Bandwidth Restriction is set to
Enabled.
CIR(kbit/s)
320-10000000
Also called the assured bandwidth. It

commits the information rate for the
be set only when Enable Bandwidth
Restriction is set to Enabled.The
CIR and PIR of CS7 must be the
same as those of CS6.

338
OptiX OSN 7500 II/7500/3500/1500

8 HQoS
Field
Value Range
Description
PIR(kbit/s)
320-10000000
Also called the peak bandwidth. It

specifies the maximum rate for the
be set only when Enable Bandwidth
Restriction is set to Enabled.
CBS(byte)
64-131072
Also called the extra buffer size. It

specifies the committed burst size for
the traffic to pass in a short time. This
Enable Bandwidth Restriction is
set to Enabled.
PBS(byte)
64-16777216
Also called the peak burst buffer size.

This parameter can be set only when
Enable Bandwidth Restriction is
set to Enabled.

bytes)
0-4095
Specifies the tail drop threshold.
Service WRED Policy
For example, 1-WRED

policy

are discarded. Tail Drop Threshold
(256 bytes) and Service WRED
Policy cannot be set at the same time.
After Enable Bandwidth
Restriction is set to Enabled,
Policy.
packets are discarded. Tail Drop
Threshold (256 bytes) and Service
WRED Policy cannot be set at the
same time.
Issue 03 (2012-11-30)

339
OptiX OSN 7500 II/7500/3500/1500

8 HQoS
Field
Value Range
Description
QinQ Link ID
1-4294967295
The QinQ Link ID parameter

indicates the unique identifier of a
QinQ link.
Click A.10.10 QinQ Link ID(QinQ
Physical Port ID
For example, 12
The Physical Port ID parameter

identifies the physical port that
applies the QinQ policy.
Click A.10.11 Physical Port ID
(QinQ Policy) for more information.
S-VLAN ID
1-4094
The S-VLAN ID parameter is a 12bit field, indicating the VLAN ID. If

a switch supports the 802.1Q
protocol, all packets it transmitting
contain this 12-bit field. In this case,
a packet is identified by its own
VLAN.
Click A.10.12 S-VLAN ID(QinQ
Ingress, Egress
Direction
Displays the direction of the QinQ

link.


There are no alarms that are related to the HQoS feature.

There are no performance events that are related to the HQoS feature.
Issue 03 (2012-11-30)

340
OptiX OSN 7500 II/7500/3500/1500

9 IGMP Snooping
IGMP Snooping
About This Chapter

The Internet Group Management Protocol (IGMP) Snooping function can improve bandwidth
utilization and enhance network security and reliability.
9.1 Introduction to IGMP Snooping
By snooping the IGMP packet of Layer 3, the IGMP Snooping function creates and maintains
the Layer 2 multicast function and thus prevents the multicast packets from being broadcast
among the Layer 2 equipment.
9.2 Basic Concepts
If the multicast router exists in a network, the bridge can enable the IGMP Snooping protocol
to realize the multicast function with the operation of the router.
This topic describes the standards and protocols that IGMP Snooping complies with.
9.4 Availability
The IGMP Snooping function requires the support of the applicable equipment, boards, and
software.
This section describes the limitations on and precautions for IGMP Snooping in the network
9.6 Principle Description
The IGMP Snooping creates and maintains the mapping relations between group members and
ports of the switch by snooping IGMP packets. This ensures that multicast packets are
transmitted only to the ports that are connected to multicast users.
The equipment that enables the IGMP Snooping function dynamically learns the router port,
multicast group, and group member by snooping the IGMP packets transmitted between the
multicast management router and the host. In this manner, the multicast packets are prevented
from being broadcast among the equipment at Layer 2. The IGMP Snooping has a strong
capability of managing the multicast services, such as dynamically responding to the IGMP Join/
Leave requests of customers. Hence, the IGMP Snooping is applicable to the equipment at the
access and convergence layers.
Issue 03 (2012-11-30)

341
OptiX OSN 7500 II/7500/3500/1500

9 IGMP Snooping
9.8 Configuring the IGMP Snooping

This topic describes how to configure the IGMP Snooping protocol for the packet transmission
service.
This section uses an example to describe how to plan and configure IGMP Snooping according
to network conditions.
There is no alarm or performance event relevant to the IGMP Snooping function.
9.11 Parameter Description: IGMP Snooping
Issue 03 (2012-11-30)

342
OptiX OSN 7500 II/7500/3500/1500

9 IGMP Snooping
9.1 Introduction to IGMP Snooping

By snooping the IGMP packet of Layer 3, the IGMP Snooping function creates and maintains
the Layer 2 multicast function and thus prevents the multicast packets from being broadcast
among the Layer 2 equipment.
The IGMP protocol is a multicast management protocol used between routers and hosts (such
as switches and DSLAMs) to manage the addition and deletion of a group member.
Figure 9-1 compares the process for transmitting multicast packets when the IGMP Snooping
function is enabled and the process for transmitting multicast packets when the IGMP Snooping
function is disabled.
l
If the IGMP Snooping function is disabled, the bridge broadcasts the received packets to
each host.
If the IGMP Snooping function is enabled, after receiving the multicast packet, the bridge
queries the multicast table in which the source port functions as the router port. If the
multicast group that matches the multicast address exists in the multicast table, the bridge
forwards the packet to this multicast group. If the multicast group that matches the multicast
address does not exist in the multicast table, the bridge discards the packet or broadcasts
the packet.
Figure 9-1 Application of the IGMP Snooping function in a network

Transmission of multicast packets (with the IGMP
Snooping protocol disabled)
Transmission of multicast packets (with the IGMP

Snooping protocol enabled)
Internet/
Intranet
Internet/
Intranet
Source
NE1
Host
1
NE2
Host
3
Host
2
Group member
Host
Host
5
4
Group member
NE1
Host
1
Host
Host
3
2
Group member
Source
NE2
Host
Host
4
5
Group member
Multicast management
router
Equipment that supports the
IGMP Snooping function
Bridge
Multicast packets
The advantages of the IGMP Snooping application are as follows:

l
Less network bandwidth is required.
Packets are forwarded within the range of each VLAN. Hence, the information security is
enhanced.
Issue 03 (2012-11-30)

343
OptiX OSN 7500 II/7500/3500/1500

9 IGMP Snooping
9.2 Basic Concepts

If the multicast router exists in a network, the bridge can enable the IGMP Snooping protocol
to realize the multicast function with the operation of the router.
9.2.1 Multicast Protocol

Many multimedia network applications, such as video conference, E-learning, and video on
demand (VOD) service, require the information to be transmitted from one source to multiple
destinations, that is, a one-to-many transmission mode. Simulating the one-to-many
transmission through the one-to-one mode occupies a large volume of the bandwidth because
the data traffic volume of the multimedia information is large. In addition, information flooding
is generated if the broadcast mode is used. Hence, a one-to-many multicast protocol is required.
The IP multicast protocol is developed based on the IP protocol stack. The IP multicast protocol
uses a D-class IP address to indicate a multicast group. Each multicast group corresponds to a
multicast address. The D-class IP address is the multicast address, ranging from 224.0.1.0 to
239.255.255.255. According to the multicast address, the router forwards a packet to all the IP
hosts in a multicast group. The hosts in an IP multicast group can join or leave this multicast
group at any time and at any location, without restrictions on the number of members. The
multicast router need not store the member relations of all the hosts. The router needs to store
information only about whether any host in the physical subnetwork belongs to a specific
multicast group. The host needs to store information only about the multicast groups that it joins.
IP multicast protocols are classified into two categories: the communication protocol between
multicast routers and the protocol between multicast routers, hosts, and Layer 2 switches.
l
The communication protocol between multicast routers is used to obtain the multicast
routing information. This type of protocol contains the Protocol Independent MulticastDense Mode (PIM-DM), Protocol Independent Multicast-Sparse Mode (PIM-SM), and
Distance Vector Multicast Routing Protocol (DVMRP).
The protocol between multicast routers, hosts, and Layer 2 switches is used to forward
multicast packets according to the multicast routing information. This type of protocol
contains the IGMP, IGMP Snooping, IGMP Proxy, and Cisco Group Management Protocol
(CGMP). The IGMP is a Layer 3 multicast protocol, and the IGMP Snooping, IGMP Proxy,
and CGMP are Layer 2 multicast protocols.
9.2.2 IGMP
Contained in the TCP/IP suite, the IGMP protocol is used to manage members of the IP multicast
group. The IGMP protocol creates and maintains the member relations of the multicast group
between the host and its adjacent multicast router.
The host notifies the local router of joining a specific multicast group and accepting the
information from this multicast group through the IGMP protocol. The router periodically
queries whether a member of a specific group in the LAN is activated through the IGMP protocol
(that is, whether the member of a specific multicast group still exists in the network segment),
and thus collects and maintains the member relations of groups that are connected to the router.
Through this mechanism, the multicast router creates a table, which contains the ports of the
router and members of each specific group in the subnetworks corresponding to each port. After
receiving the packet of a specific group, the router forwards the packet only to the ports that
have the members of this group.
Issue 03 (2012-11-30)

344
OptiX OSN 7500 II/7500/3500/1500

9 IGMP Snooping
9.2.3 IGMP Snooping

The IGMP Snooping function creates and maintains the mapping relations between group
members and ports of the switch by snooping IGMP packets.
The IGMP Snooping function creates and maintains the mapping relations between group
members and ports of the switch by snooping IGMP packets. After the IGMP Snooping protocol
is enabled, the bridge considers the port that receives the IGMP query packet as the router port.
When the bridge detects the response that is transmitted to the router port, the bridge adds the
port that receives the response and the router port to a specific multicast group. After receiving
the multicast packet, the bridge queries the multicast table in which the source port functions as
the router port. If the multicast group that matches the multicast address exists in the multicast
table, the bridge forwards the packet to this multicast group. If the multicast group that matches
the multicast address does not exist in the multicast table, the bridge discards the packet or
broadcasts the packet. When the bridge detects that a certain port in a multicast group does not
respond to the IGMP query packet for consecutive times the number of which exceeds the
threshold, the bridge deletes this port from the multicast group.
In addition, you need to be familiar with the following concepts that are related to the IGMP
Snooping function.
l
Enabling the IGMP Snooping protocol

If the IGMP Snooping protocol is enabled, the equipment starts to perform learning and
aging operations for router ports and multicast groups. Consequently, the multicast services
are multicast in the corresponding multicast groups.
If the IGMP Snooping protocol is disabled, the equipment stops performing learning and
aging operations on router ports and multicast groups, and deletes all the learnt dynamic
multicast groups.
Router port
The router port refers to a port that faces the multicast router. The Ethernet data boards of
the equipment consider the port that receives the IGMP query packet as the router port.
Router ports are classified into the following two categories:
Dynamic router port: It refers to a port that can receive the IGMP query packet. The
dynamic router port is based on the packets transmitted between the router and the host
and is dynamically maintained. Each dynamical router port can enable a router port
aging timer. When the timer expires, this port becomes invalid and the multicast group
that is based on this port is deleted.
Static router port: It refers to a port that a user specifies by running the configuration
command. The static router port is not aged.
Member port
The multicast group member port refers to a port that faces the host of the group member.
The Layer 2 equipment forwards multicast service packets to the member ports. The
multicast group member ports, referred to as member ports for short, are classified into the
following two categories:
Dynamic member port: It refers to a port that can receive the IGMP report packet from
the host. The dynamic member port is based on the packets transmitted between the
router and the host and is dynamically maintained. Each dynamic member port is aged
after the maximum number of non-response times is reached.
Static member port: It refers to a port that is specified through the configuration
command of a user. The static member port is not aged.
Issue 03 (2012-11-30)

345
OptiX OSN 7500 II/7500/3500/1500

9 IGMP Snooping
Aging time of the router port

As is specified in the IGMP protocol, the router needs to transmit the IGMP query packet
periodically to the host, to obtain the information indicating whether the host is in the
multicast group.
After the Ethernet data board of the equipment learns a router port in a broadcast domain,
the aging timer is started for this port. When the aging timer of this router port expires and
this port does not receive any query packet, the IGMP Snooping sub-system considers this
router port as invalid and then ages this router port.
If this router port receives the query packet (including the specific query packet) before the
aging timer expires, the aging timer of this port is re-set.
Maximum non-response times of multicast group members

The equipment needs to learn the information indicating whether a multicast group member
leaves a multicast group in a timely manner. This can prevent the service packets from
being transmitted continuously to the multicast group members that have left a multicast
group, which may exhaust the resources of the equipment and downstream equipment.
When a certain port on the equipment receives the IGMP response packet that is sent by
the host for the first time, the equipment adds this port to the corresponding multicast group
and then starts the count of non-response times for this multicast member. When the query
packet is sent to the multicast member and the response packet is not received in a required
response period, the count of non-response times for this multicast member is started. When
the count value reaches the threshold, the multicast member is considered having left the
multicast group and this multicast member is deleted. As a result, the equipment that is
connected to this port cannot receive the multicast services. If the response packet is
received before the count value of non-response times for a multicast group member port
reaches the maximum non-response times, the count value is reset.
IGMP general query packet

The IGMP general query packet refers to a packet that is transmitted by the multicast router
to the multicast group members. The IGMP general query packet is used to query which
multicast groups have members.
IGMP specific query packet

The IGMP specific query packet refers to a packet that is transmitted by the multicast router
to the multicast group members. The IGMP specific query packet is used to query whether
specific multicast groups have members.
IGMP report packet

The IGMP report packet refers to a report packet that is transmitted by a multicast group
member to the multicast router. The IGMP report packet is used to request for the joining
of a multicast group or to respond to the IGMP query packet.
IGMP leave packet

The IGMP leave packet refers to a packet that is transmitted by a multicast group member
to the multicast router when the member actively quits its group. The IGMP leave packet
is used to notify the router of a member's leave from a multicast group.

This topic describes the standards and protocols that IGMP Snooping complies with.
The IGMP Snooping complies with RFC 4541 Considerations for Internet Group Management
Protocol (IGMP) and Multicast Listener Discovery (MLD) Snooping Switches.
Issue 03 (2012-11-30)

346
OptiX OSN 7500 II/7500/3500/1500

9 IGMP Snooping
9.4 Availability
The IGMP Snooping function requires the support of the applicable equipment, boards, and
software.
Version Support
Applicable Version
OptiX OSN 1500/3500
V100R009C03
T2000
U2000
Applicable Version
OptiX OSN 7500/7500 II
U2000
Hardware Support
Applicable Board
Applicable Version
N1PEG16
l V100R009C03
OptiX OSN 3500
l V200R011C01 and later

N1PEG8
OptiX OSN 3500/7500
N1PEX1
l V100R009C03
OptiX OSN 3500

N2PEX1
OptiX OSN 3500/7500
N1PEX2
OptiX OSN 3500/7500
N1PETF8
l V100R009C03
OptiX OSN 3500/7500

N1PEFF8
OptiX OSN 3500/7500
Q1PEGS2
l V100R009C03

R1PEGS1
l V100R009C03
Issue 03 (2012-11-30)

347
OptiX OSN 7500 II/7500/3500/1500

9 IGMP Snooping
Applicable Board
Applicable Version
R1PEF4F
l V100R009C03

l V100R009C03
R1PEFS8

TNN1EX2
OptiX OSN 7500 II
TNN1EG8
OptiX OSN 7500 II
TNN1ETMC
OptiX OSN 7500 II
TNN1EFF8
OptiX OSN 7500 II

This section describes the limitations on and precautions for IGMP Snooping in the network

Applicable
Object

Details
Remarks
IGMP
Snooping
If the IGMP multicast router exists

on the interconnected Ethernet
network, enable the IGMP Snooping
protocol according to the
requirements of the router.
Otherwise, disable the IGMP
Snooping protocol.
Issue 03 (2012-11-30)
Applicable
Object

Details
Remarks
Method for
processing
unknown
multicast
packets and
multicast
aging time
Set the method for processing

unknown multicast packets and
multicast aging time according to
the requirements of the IGMP
multicast router. It is recommended
that you use the default values.

348
OptiX OSN 7500 II/7500/3500/1500

9 IGMP Snooping
None.
9.6 Principle Description

The IGMP Snooping creates and maintains the mapping relations between group members and
ports of the switch by snooping IGMP packets. This ensures that multicast packets are
transmitted only to the ports that are connected to multicast users.
The bridge processes the IGMP query packet, report packet, multicast packet, and fast-leave
packet to achieve the IGMP Snooping function.
l
After the bridge receives the IGMP general query packet or the IGMP specific query packet,
it processes this packet as follows:
1.
The bridge checks whether the port that receives the packet is already learnt as the
router port.
2.
If this port is not learnt, the bridge records this port as the router port.
3.
If the received packet is the IGMP specific query packet and the port that receives this
packet is already recorded as the router port, the bridge broadcasts this packet in the
specific multicast group and starts the timer for the maximum query response time
and if the multicast group that is specified in this packet exists. Otherwise, the bridge
broadcasts this packet in the address domain or VLAN domain of the bridge.
After the bridge receives the IGMP report packet, it processes this packet as follows:
1.
The bridge checks whether the multicast record is already learnt in the address domain
or VLAN domain of the bridge.
2.
If this multicast record is not learnt and if the multicast group does not exist, the bridge
creates the multicast group and creates the mapping relations between the router ports,
MAC multicast addresses, and multicast group members by considering this port as
the multicast member port. If this multicast record is not learnt and this port is not
contained in the multicast member ports of the multicast group, the multicast group
adds this port as the multicast member port. If this multicast record is learnt, the bridge
re-sets the count of no-response times for this multicast member.
After the bridge receives the multicast packet, it processes this packet as follows:
1.
The bridge queries the multicast table that uses the source port as the router port.
2.
If the multicast group that matches the multicast address exists in the multicast table,
the bridge forwards the packet to this multicast group.
3.
If the multicast group that matches the multicast address does not exist in the multicast
table, the bridge discards the packet or broadcasts the packet in the VLAN domain.
The bridge performs the IGMP fast-leave function as follows. After the bridge receives the
IGMP fast-leave packet, it processes this packet as follows:
1.
The member port receives an IGMP fast-leave packet from the multicast group.
2.
The bridge deletes the member port in the multicast group.
When the data port fails to respond to the query within a certain period or fails to receive a query
packet within a certain period, the multicast member and dynamic router port will age. The
bridge renews the multicast members by aging the multicast member and dynamic router port.
l
Issue 03 (2012-11-30)
The bridge processes the aging of multicast members as follows:

349
OptiX OSN 7500 II/7500/3500/1500

9 IGMP Snooping
1.
If the maximum query response time expires, the bridge adds one to the no-response
times of the multicast member.
2.
If the no-response times of a multicast member exceeds the threshold, the bridge
deletes this multicast member port.
3.
If a multicast group does not have any multicast member port, the bridge deletes this
multicast group.
Aging of the dynamic router port: The aging timer of a router port is started for each dynamic
router port. If no IGMP query packet is received in a certain period, the timer expires and
the router port becomes invalid. In addition, the multicast group that is based on this router
port is deleted.

The equipment that enables the IGMP Snooping function dynamically learns the router port,
multicast group, and group member by snooping the IGMP packets transmitted between the
multicast management router and the host. In this manner, the multicast packets are prevented
from being broadcast among the equipment at Layer 2. The IGMP Snooping has a strong
capability of managing the multicast services, such as dynamically responding to the IGMP Join/
Leave requests of customers. Hence, the IGMP Snooping is applicable to the equipment at the
access and convergence layers.
As shown in Figure 9-2, the multicast router is located at the network layer whereas NE1, NE2,
and the switches are located at the data link layer. After the IGMP protocol is enabled on the
multicast router and the IGMP Snooping protocol is enabled on NE1 and NE2, NE1 and NE2
sense the packets on the multicast router, and updates and maintains the corresponding route
table items. After receiving the multicast packets from the router, NE1 and NE2 checks their
own multicast tables and forward the packets only to the ports that have group member hosts in
the downstream, thus preventing packet broadcasting.
Issue 03 (2012-11-30)

350
OptiX OSN 7500 II/7500/3500/1500

9 IGMP Snooping
Figure 9-2 Multicast forwarding
Internet/
Intranet
Source
NE1
Host 1
NE2
Host 2
Group member
Host 3
Host 4
Group member
Host 5
Group member
Multicast packets
9.8 Configuring the IGMP Snooping

This topic describes how to configure the IGMP Snooping protocol for the packet transmission
service.
9.8.1 Setting the IGMP Snooping Parameters

The IGMP Snooping parameters include Enabled Protocol, Router Port Aging Time(min),
Maximum times of No Response from Multicast Members, Maximum Number of Multicast
Groups, and Maximum Number of Multicast Groups Member. You need to set these
parameters so that the IGMP Snooping can work normally. After setting the IGMP Snooping
parameters for the multicast service that is already created, you can set certain ports that carry
the multicast service as quickly delete member ports. The multicast user on each quickly delete
member port can switch the multicast service channel quickly.
Prerequisites
l
The E-LAN service must be created.
Issue 03 (2012-11-30)

351
OptiX OSN 7500 II/7500/3500/1500

9 IGMP Snooping
Procedure
Protocol Configuration > IGMP Snooping Configuration from the Function Tree.
Step 2 Click the Protocol Configuration tab, and then set the parameters according to the requirement.
After the setting, click Apply.
NOTE

l Enabled Protocol: This parameters specifies whether the IGMP Snooping function is enabled or
disabled.
l Router Port Aging Time(min): The value ranges from 1 to 120, and the default value is 8. This
parameter can be set when the IGMP Snooping function is enabled.
l Maximum times of No Response from Multicast Members: The value ranges from 1 to 4, and the
default value is 3. This parameter can be set when the IGMP Snooping function is enabled.
l Maximum Number of Multicast Groups: The maximum number of the OptiX OSN equipment is
1024. This parameter can be set when the IGMP Snooping function is enabled.
l Maximum Number of Multicast Groups Member: The maximum number of the OptiX OSN
equipment is 6144. This parameter can be set when the IGMP Snooping function is enabled.
Step 3 Select the multicast service that requires the setting of the quickly delete member port. The
multicast service is displayed in the lower pane.
Step 4 Set the parameters that are related to the quickly delete member port for the multicast service.
These parameters include VLAN ID, Port Type, and Port. You can modify the values doubleclicking these parameters.
NOTE
If you need to set a port that carries the multicast service as a quickly delete member port, the port must
have only one multicast service user. Otherwise, different users on the quickly delete port are mutually
affected when they receive multicast services.
Step 5 Click Apply.

----End
9.8.2 Configuring the Route Management

After you manually create the router port, the equipment can respond to the IGMP query packets
of the router through this router port. The router port is not aged automatically and always exists
unless manually deleted.
Prerequisites
l
Procedure
Step 2 Click the Route Management tab. Click New. When the Create Router Port dialog box is
displayed, set the required parameters and select the multicast router port to be added.
Issue 03 (2012-11-30)

352
OptiX OSN 7500 II/7500/3500/1500

9 IGMP Snooping
NOTE

l Service ID: This parameter specifies the ID of the service that the router port carries, that is, the ID of
the E-LAN service.
l VLAN ID: The value of the VLAN ID should be set according to the actual requirement. The value
ranges from 1 to 4094.
l Available Port: The corresponding port should be selected according to the time. The added port must
belong to the VLAN of the service.
Step 3 Click OK.

----End
9.8.3 Configuring the Route Member Port Management

When you configure the route member port, you can define the multicast range. The static
multicast member port is not aged automatically and always exists unless manually deleted.
Prerequisites
l
Procedure
Step 2 Click the Route Member Port Management tab, and then click New.
Step 3 When the Create Member Port dialog box is displayed, set the required parameters.
NOTE

l Service ID: This parameter specifies the ID of the service that the router port carries, that is, the ID of the
E-LAN service.
l VLAN ID: The value of the VLAN ID should be set according to the actual requirement. The value ranges
from 1 to 4094.
l Multicast MAC Address: The value ranges from 01-00-5E-00-01-00 to 01-00-5E-7F-FF-FF.
l Available Port: The corresponding port should be selected according to the time. The added port must
belong to the VLAN of the service.
Step 4 Click OK.

----End
9.8.4 Configuring the Packet Statistics

When you set the status of the protocol packet statistics, you can enable, disable, or clear the
packet statistics. The packet statistics data helps the user be familiar with the running status of
the multicast service.
Issue 03 (2012-11-30)

353
OptiX OSN 7500 II/7500/3500/1500

9 IGMP Snooping
Prerequisites
l
The route member port must be configured.
Procedure
Step 1 Select the NE in the NE Explorer. Choose Configuration > Ethernet Protocol
Configuration > IGMP Snooping Configuration from the Function Tree.
Step 2 Click the Packet Statistics tab, and set the parameters contained in the IGMP protocol packet
statistics.
NOTE

l Service ID: This parameter is actually the ID of the E-LAN service.
l VLAN ID: The value ranges from 1 to 4094.
l Port Type: The Port Type can be V-UNI or V-NNI. This parameter cannot be set.
l Port: The corresponding port should be selected according to the actual requirement.
l Packet Statistics Status: The value can be set to Stop, Start, or Clear. The default value is Stop.
l IGMPv1 Query Packet Count: The value of this parameter is obtained through query and this parameter
cannot be set.
cannot be set.
cannot be set.
l IGMP Leaving Packet Count: The value of this parameter is obtained through query and this parameter
cannot be set.
l IGMPv1 Member Report Packet Count: The value of this parameter is obtained through query and this
parameter cannot be set.
l Unrecognized or Unprocessed Packet Count: The value of this parameter is obtained through query and
this parameter cannot be set.
l Discarded Incorrect Packet Count: The value of this parameter is obtained through query and this
successful. Click Close.
----End

This section uses an example to describe how to plan and configure IGMP Snooping according
to network conditions.
Issue 03 (2012-11-30)

354
OptiX OSN 7500 II/7500/3500/1500

9 IGMP Snooping
9.9.1 Network Diagram

The Hybrid MSTP equipment multicasts the data packets from the router interface to the
multicast member interfaces.
As shown in Figure 9-3, the Hybrid MSTP equipment multicasts the data packets from the router
interface (3-N1PEG8-1) to the multicast member interfaces (3-N1PEG8-2, 3-N1PEG8-3 and 3N1PEG8-4).
Figure 9-3 Network diagram of IGMP Snooping
3-N1PEG8-1
3-N1PEG8-4
3-N1PEG8-2
3-N1PEG8-3
host 1
host 2
group member
group member
host 3
group member
multicast packets
9.9.2 Service Planning

data.
Table 9-1 provides the planning information about enabling the IGMP Snooping.
Issue 03 (2012-11-30)

355
OptiX OSN 7500 II/7500/3500/1500

9 IGMP Snooping
Table 9-1 Planning information about enabling the IGMP Snooping

Attribute
Description
Enabled Protocol
Enabled
Router Port Aging Time (min)
Maximum times of No Response from

Multicast Members
Maximum Number of Multicast Groups
Unlimited
Table 9-2 provides the planning information about managing the IGMP Snooping routes.
Table 9-2 Planning information about managing the IGMP Snooping routes
Attribute
Description
Service ID
101
VLAN ID
30
Selected Port
3-N1PEG8-1(PORT-1)[30]
Table 9-3 provides the planning information about managing the IGMP Snooping route member
ports
Table 9-3 Planning information about managing the IGMP Snooping route member ports
Attribute
Description
Service ID
101
VLAN ID
30
Multicast MAC Address
01-00-5E-00-01-02
Selected Port
3-N1PEG8-2(PORT-2)[30], 3-N1PEG8-3
(PORT-3)[30], 3-N1PEG8-4(PORT-4)[30]
Table 9-4 provides the planning information about packet statistics on the IGMP Snooping
Table 9-4 Planning information about packet statistics on the IGMP Snooping
Issue 03 (2012-11-30)
Attribute
Description
Packet Statistic Status
Start

356
OptiX OSN 7500 II/7500/3500/1500

9 IGMP Snooping

Prerequisites
l
Procedure
Step 1 On the U2000, set the IGMP Snooping parameters. For details, see 9.8.1 Setting the IGMP
Snooping Parameters.
Attribute
Description
Enabled Protocol
Enabled
Router Port Aging Time (min)
Maximum times of No Response from

Multicast Members
Maximum Number of Multicast Groups
Unlimited
Step 2 On the U2000, configure the route management. For details, see 9.8.2 Configuring the Route
Management.
Attribute
Description
Service ID
101
VLAN ID
30
Selected Port
3-N1PEG8-1(PORT-1)[30]
Step 3 On the U2000, configure the route member port. For details, see 9.8.3 Configuring the Route
Member Port Management.
Attribute
Description
Service ID
101
VLAN ID
30
01-00-5E-00-01-02
Selected Port
3-N1PEG8-2(PORT-2)[30], 3-N1PEG8-3
(PORT-3)[30], 3-N1PEG8-4(PORT-4)[30]
Step 4 On the U2000, configure the packet statistics status. For details, see 9.8.4 Configuring the
Packet Statistics.
Issue 03 (2012-11-30)

357
OptiX OSN 7500 II/7500/3500/1500

9 IGMP Snooping
Attribute
Description
Start
----End

There is no alarm or performance event relevant to the IGMP Snooping function.
Relevant Alarms
None.
Relevant Performance Events

None.
9.11 Parameter Description: IGMP Snooping

9.11.1 Protocol Configuration

You need to set the parameters such as Router Port Aging (min), Maximum Number of
Multicast Groups, and Maximum Number of Multicast Group Members when configuring
the IGMP Snooping protocol.
Table 9-5 lists the parameters that used for configuring the IGMP Snooping protocol.
Table 9-5 Parameters for configuring the IGMP Snooping protocol
Field
Value
Description
Service ID
Example: 5
Display the service ID.
Enabled Protocol
Disabled, Enabled
Display and set the enable

status.
Default: Disabled
Router Port Aging (min)
1-120
Default: 8
Maximum times of No
Response from Multicast
Members
Issue 03 (2012-11-30)
1-4
Default: 3

Display and set the aging

time for the multicast router
port.
Display and set the maximum
non-response times of
multicast group members.
358
OptiX OSN 7500 II/7500/3500/1500

9 IGMP Snooping
Field
Value
Description
Maximum Number of
Multicast Groups
Example: Unlimited

number of multicast groups.
The number of static
multicast groups cannot be
more than the maximum
number set by the user.
Maximum Number of
Multicast Group Members
Example: Unlimited

number of multicast groups.
The number of multicast
group members cannot be
more than the maximum
number set by the user.
Actual Multicast Count
Example: 2
Query the count of actual

multicast groups.
Actual Multicast Members

Count
Example: 3
Query the count of actual

multicast members.
VLAN ID
1 to 4094
Display the VLAN ID of the

service.
Default: 1
Port Type
V-UNI, V-NNI
Default: V-UNI
Display and set the quickly

delete member port type for
the service.
l V-UNI: user-side port.
l V-NNI: network-side
port.
Example: 21-N1PETF8-2
(PORT-2)[55]
Port
Display and set the quickly

delete member port.
9.11.2 Router Management

Configuring router management of the IGMP Snooping function is to set the parameters such
as Port Status, Port Creating Time, and Port Remainder Aging Time (min) for Ethernet
ports.
Table 9-6 lists the parameters for router management of the IGMP Snooping function.
Table 9-6 Parameters for router management of the IGMP Snooping function
Issue 03 (2012-11-30)
Field
Value
Description
Service ID
Example: 5
VLAN ID
1-4094

service.

359
OptiX OSN 7500 II/7500/3500/1500

9 IGMP Snooping
Field
Value
Description
Port Type
V-UNI, V-NNI
Display the virtual port type

correspond to the service
port.
port.
Port
(PORT-2)
Display the port.
Port Status
Dynamic, Static
Display the port status.
Port Creating Time
Example: 2008-1-31
9:58:25:0
Display the time when the

port is created.
Port Remainder Aging Time

(min)
Example: 8
Display the port remainder

aging time.
Available Port
(PORT-2)[55]
All available.
Selected Port
(PORT-2)[55]
All selected.
9.11.3 Route Member Port Management

Configuring route member port management of the IGMP Snooping function is to set the
parameters such as Multicast Group Type, Multicast Group Creating Time, and Port
Remainder Aging Times.
Table 9-7 lists the parameters for route member port management of the IGMP Snooping
function.
Table 9-7 Parameters for route member port management of the IGMP Snooping function
Issue 03 (2012-11-30)
Field
Value
Description
Service ID
Example: 5
VLAN ID
1-4094

service.
Example:
01-00-5E-00-01-00
Display the multicast MAC

address.
Multicast Group Type
Static, Dynamic
Display the multicast group

type.
Multicast Group Creating

Time
Example: 2008-1-31
10:54:7:0
Display the time when the

multicast group is created.

360
OptiX OSN 7500 II/7500/3500/1500

9 IGMP Snooping
Field
Value
Description
Port Type
V-UNI, V-NNI
Display the port type for the

service.
port.
Port
(PORT-2)
Display the port.
Port Remainder Aging Times
Example: 3
Display the port remainder

aging times.
Available Port
(PORT-2)[55]
All available.
Selected Port
(PORT-2)[55]
All selected.
9.11.4 Packet Statistics

You need to set the parameters such as Packet Statistic Status, IGMP Leaving Packet
Count, and Discarded Incorrect Packet Count when collecting the packet statistics of the
IGMP Snooping function.
Table 9-8 lists the parameters for collecting the packet statistics of the IGMP Snooping function.
Table 9-8 Parameters for collecting the packet statistics of the IGMP Snooping function
Field
Value
Description
Service ID
Example: 5
VLAN ID
1-4094

service.
Port Type
V-UNI, V-NNI
Display the port type for the

service.
port.
Issue 03 (2012-11-30)
Port
Example: 1
Display the port.
Clear, Start, Stop
Set and display the packet

statistics status.
IGMPv1 Query Packet Count
Example: 5
Display the count of the

received IGMPv1 query
packets.

361
OptiX OSN 7500 II/7500/3500/1500

Issue 03 (2012-11-30)
9 IGMP Snooping
Field
Value
Description
Example: 6

packets.
Example: 7

packets.
IGMP Leaving Packet Count
Example: 5

received IGMP packets that
leave the multicast group.
IGMPv1 Member Report

Packet Count
Example: 6

received IGMPv1 member
report packets.

Packet Count
Example: 7

report packets.

Packet Count
Example: 6

report packets.
Unrecognized or
Unprocessed Packet Count
Example: 8
Display the count of

unrecognized or unprocessed
packets.
Discarded Incorrect Packet

Count
Example: 7
Display the count of

discarded incorrect packets.

362
OptiX OSN 7500 II/7500/3500/1500

10 Link Aggregation
10
Link Aggregation
About This Chapter

With no need for hardware upgrades, link aggregation binds several Ethernet ports as a logical
port for higher link bandwidth and link reliability.
10.1 Introduction
As the Ethernet technology is widely applied in the metropolitan area network (MAN) and the
wide area network (WAN), carriers propose increasingly higher requirements on the bandwidth
and reliability of backbone links that use the Ethernet technology. Hardware upgrades can
increase Ethernet link bandwidth but also incur high expenditure. In addition, hardware upgrades
are less flexible than software upgrades. To increase bandwidth at a low expenditure and flexibly,
the link aggregation technology is developed.
10.2 Basic Concepts
This section describes the basic concepts that you need to be familiar with before you use the
link aggregation feature.
10.3 Specifications
This section describes the capacity of the OptiX OSN equipment for supporting LAG.
This section describes the standards and protocols associated with the link aggregation feature.
10.5 Availability
The LAG function requires the support of applicable NE versions and boards.
This section describes the limitations on and precautions for LAG in the network design phase,
10.7 Principles
LACP implements establishment, switchover, and switchover reversion of static LAGs.
10.8 Configuring a LAG
Configuring a LAG includes creating a LAG and setting port priorities.
10.9 Maintaining a LAG
This section describes how to query, change, and delete LAG configurations.
10.10 Configuration Example (LAG Configured to Increase Ethernet Link Bandwidth)
Issue 03 (2012-11-30)

363
OptiX OSN 7500 II/7500/3500/1500

10 Link Aggregation
This section uses an example to describe how to configure a LAG to increase Ethernet link
bandwidth.
10.11 Configuration Example (LAG Configured to Provide Link Protection)
This section uses an example to describe how to configure a LAG to provide protection for
Ethernet links.
10.12 Verifying a LAG
This topic describes how to check whether a LAG works properly by verifying the basic functions
of the LAG.
This section describes the alarms and performance events that are associated with the link
aggregation feature.
10.15 Relevant Parameters
This section describes parameters associated with LAG management.
Issue 03 (2012-11-30)

364
OptiX OSN 7500 II/7500/3500/1500

10 Link Aggregation
10.1 Introduction
As the Ethernet technology is widely applied in the metropolitan area network (MAN) and the
wide area network (WAN), carriers propose increasingly higher requirements on the bandwidth
and reliability of backbone links that use the Ethernet technology. Hardware upgrades can
increase Ethernet link bandwidth but also incur high expenditure. In addition, hardware upgrades
are less flexible than software upgrades. To increase bandwidth at a low expenditure and flexibly,
the link aggregation technology is developed.
Link aggregation has the following characteristics:
l
With no need for hardware upgrades, link aggregation binds several Ethernet ports as a
higher-bandwidth logical port.
The link backup mechanism of the link aggregation technology provides higher link
transmission reliability.
Link aggregation functions between adjacent NEs and is independent of the network
topology.
The logical link aggregating several physical links is called a link aggregation group (LAG).
NOTE
Link aggregation is also called port aggregation because each link corresponds to two specific ports at two
ends in Ethernet transmission.
As shown in Figure 10-1, two adjacent NEs are interconnected through three pairs of Ethernet
ports. Three physical Ethernet links are bound as a logical link, called a LAG.
Figure 10-1 LAG
10.2 Basic Concepts

link aggregation feature.
10.2.1 LACP
Link Aggregation Control Protocol (LACP) functions to aggregate and deaggregate Ethernet
links dynamically.
Developed based on IEEE 802.3ad, LACP performs the following functions:
l
Issue 03 (2012-11-30)
LACP provides the data switching equipment with a standard negotiation mode to form an
aggregation link. After LACP is enabled, the system automatically aggregates multiple
365
OptiX OSN 7500 II/7500/3500/1500

10 Link Aggregation
links according to its configuration and enables the aggregation link to transmit and receive
data.
l
LACP allows both ends of the aggregated link to exchange Link Aggregation Control
Protocol Data Units (LACPDUs), and therefore helps in maintaining links statuses and
implements dynamic link aggregation and deaggregation.
NOTE
For details about the LACPDU structure, see IEEE 802.3ad.
After member ports are added to a LAG, each end of the LAG sends LACPDUs to inform the
peer of its system priority, MAC address, member port priorities, port numbers, and operational
keys.
After being informed, the peer compares the information with that saved on itself, and selects
ports that can be aggregated. Then, LACP negotiation is performed to select active ports and
links.
Transmission of LACPDUs may be in either of the following modes:
l
Event-triggered transmission
A change in the state of the local system or in the local configuration triggers the generation
and transmission of a new LACPDU.
Periodic transmission
When a LAG works stably, LACPDUs are periodically transmitted telling the real-time
LAG status.
10.2.2 Link Aggregation Types

The OptiX OSN equipment supports manual link aggregation and static link aggregation.
Issue 03 (2012-11-30)
Link
Aggreg
ation
Type
Definition
Application
Scenario
Impact on Services
Manual
link
aggrega
tion
In manual link aggregation, a user

creates a link aggregation group
(LAG) and Link Aggregation
Control Protocol (LACP) is not
started if a member port is added
or deleted. The system determines
whether to aggregate a port
according to its physical status
(up or down), working mode, and
rate.
The OptiX OSN

equipment is
interconnected
with equipment
that does not
support LACP.
When the receive or

transmit direction of a
member link fails, for
example, when the fiber
connected to a receive
or transmit optical port
is cut, the service
transmit end cannot
detect the fault. As a
result, services are
interrupted.

366
OptiX OSN 7500 II/7500/3500/1500

10 Link Aggregation
Link
Aggreg
ation
Type
Definition
Application
Scenario
Impact on Services
Static
link
aggrega
tion
In static link aggregation, a user

creates a LAG and LACP is
started if a member port is added
or deleted. By running LACP, the
member port status is determined.
A static LAG has more accurate
and effective control over link
aggregation than a manual LAG.
The OptiX OSN

equipment is
interconnected
with equipment
that supports
LACP.
NOTE
Static link aggregation is recommended when interconnected equipment supports LACP.
10.2.3 Load Sharing Modes

The OptiX OSN equipment supports load sharing link aggregation and load non-sharing link
aggregation. Load sharing link aggregation helps increase link bandwidth while load non-sharing
link aggregation helps improve link reliability.
Load Sharing Link Aggregation

Each member link in a load-sharing LAG carries traffic. That is, the member links in a loadsharing LAG share the load.
To ensure load balancing over member links in a LAG, hash algorithms are used.
The hash algorithms allocate traffic based on:
l
MAC addresses, including source MAC addresses, destination MAC addresses, and source
MAC addresses plus destination MAC addresses
IP addresses, including source IP addresses, destination IP addresses, and source IP

addresses plus destination IP addresses
MPLS labels
When a member in a LAG changes or a link fails, the traffic is re-allocated automatically.
Load Non-Sharing Link Aggregation

In a load non-sharing LAG, only one member link carries traffic and the other links are in the
standby state.
Once the active link fails, the system selects a link from the standby links to take over.
Load non-sharing link aggregation can be set to revertive or non-revertive.
l
Issue 03 (2012-11-30)
When load non-sharing link aggregation is set to revertive, services are switched back to
the active link after this link is restored.
367
OptiX OSN 7500 II/7500/3500/1500

10 Link Aggregation
When load non-sharing link aggregation is set to non-revertive, services are not switched
back to the active link after this link is restored, but are still transmitted on the standby link.
10.2.4 Port Types

Member ports of a LAG are classified into master ports and standby ports.
Port Type
Definition
Master
port
Port representing a LAG

in service configuration
Standby
port
All member ports except

for the master port
Port Characteristics
Similarity
Difference
l When creating a
LAG, you need to
specify both the
master and standby
ports.
l The master/standby
state of a port does
not change once
being configured.
l The master port

represents the LAG
to participate in
service configuration
whereas standby
ports cannot
participate in service
configuration.
l A LAG has only one
master port but can
have several standby
ports.
l The master port can
quit its affiliated
LAG only after the
LAG is deleted. A
standby port can be
added to or deleted
from a LAG. After a
LAG is deleted, its
services are still
carried by the master
port.
NOTE
An Ethernet port can belong to only one LAG.
10.2.5 Priority
LAG priority includes system priority and port priority. Priority setting allows negotiation of
aggregation information between LAGs at two ends and real-time maintenance on link status.
Issue 03 (2012-11-30)

368
OptiX OSN 7500 II/7500/3500/1500

10 Link Aggregation
Priority Type
Description
Usage
System priority
Indicates the priority of a

LAG.
Applies to comparison between

interconnected LAGs at two ends. The
LAG with a higher system priority is in a
dominant position during LACP
negotiation, and aggregation information
of this LAG will be used.
NOTE
If LAGs at two ends have the same system
priority, system MAC addresses are
compared. Aggregation information of the
end with a smaller MAC address will be used.
Indicates the priority of a port

in a LAG.
Port priority
Applies to negotiation between ports in

an LAG. The port with a higher priority
is the active port. Users can change the
active port by modifying port priority.
NOTE
System priority and port priority work together to determine which ports are used to carry services with
preference. System priority prevails over port priority.
10.3 Specifications
This section describes the capacity of the OptiX OSN equipment for supporting LAG.
Table 10-1 provides specifications associated with LAG.
Table 10-1 Specifications associated with LAG
Item
Specifications
Support capability
l Number of LAGs
OptiX OSN 7500/3500: 64
OptiX OSN 1500: 16
l Number of members in a LAG
OptiX OSN 7500 II/7500/3500: 16
OptiX OSN 1500: 8
Load sharing mode
l Load sharing
l Load non-sharing
LAG type
l Static
l Manual
Issue 03 (2012-11-30)

369
OptiX OSN 7500 II/7500/3500/1500

10 Link Aggregation
Item
Specifications
WTR time (min)
1 to 30
Default value: 10
Revertive mode
l Revertive (default)
l Non-revertive
Switching time
l If a link fails bidirectionally,

switching time varies depending on LAG protection
port types.
For LAG protection between optical ports on a
board, switching time does not exceed 100 ms.
For LAG protection between optical ports on
different boards, switching time does not exceed
500 ms.
For LAG protection between electrical ports,
switching time does not exceed 2s.
l If a link fails unidirectionally,
switching time does not exceed 3s regardless of
LAG protection port types.
Switching condition (Any of the

following conditions triggers the
switching.)
l Manual aggregation:
The working port is faulty.
The working mode of port changed.
l Static aggregation:
The working mode of port changed.
The priority of port changed.
The priority of system changed.
NOTE
A unidirectional fiber cut triggers a single-ended protection switching lasting not longer than 3s when the
following conditions are met: (1) The LAG is in manual aggregation mode and the ports are full-duplex;
(2) The revertive mode of the LAG is non-revertive; (3) The load sharing mode of the LAG is non-load
sharing.
The system provides intra-board port LAG protection, which complies with the IEEE 802.3ad standard.

This section describes the standards and protocols associated with the link aggregation feature.
The following protocol is associated with the link aggregation feature:
IEEE 802.3ad: Carrier sense multiple access with collision detection (CSMA/CD) access method
and physical layer specifications
Issue 03 (2012-11-30)

370
OptiX OSN 7500 II/7500/3500/1500

10 Link Aggregation
10.5 Availability
The LAG function requires the support of applicable NE versions and boards.
Version Support
Product
Applicable Version
OptiX OSN 1500A/1500B/3500
V100R009C03
T2000
V200R007C03
Product
Applicable Version
OptiX OSN 1500A/1500B/3500/7500
U2000
Product
Applicable Version
OptiX OSN 7500 II
U2000
Hardware Support
Board
Type
Issue 03 (2012-11-30)
Link
Aggregatio
n Type
Load Sharing Mode
Port
Type
Applicable
Equipment
Sup
por
t for
Ma
nua
l
Ag
gre
gati
on
Sup
port
for
Stati
c
Aggr
egati
on
Support
for Load
Sharing
Support
for Load
NonSharing
N1PEG1
6
Yes
Yes
Yes
Yes
IP
OptiX OSN 3500
N1PEX1
Yes
Yes
Yes
Yes
IP
OptiX OSN 3500

371
OptiX OSN 7500 II/7500/3500/1500

Board
Type
Issue 03 (2012-11-30)
10 Link Aggregation
Link
Aggregatio
n Type
Load Sharing Mode
Port
Type
Applicable
Equipment
Sup
por
t for
Ma
nua
l
Ag
gre
gati
on
Sup
port
for
Stati
c
Aggr
egati
on
Support
for Load
Sharing
Support
for Load
NonSharing
N1PETF
8
Yes
Yes
Yes
Yes
IP
OptiX OSN 3500/7500
R1PEFS8
Yes
Yes
Yes
Yes
IP
OptiX OSN 1500A/

1500B
Q1PEGS
2
Yes
Yes
Yes
Yes
IP
OptiX OSN 1500A/

1500B
R1PEGS
1
Yes
Yes
Yes
Yes
IP
OptiX OSN 1500A/

1500B
R1PEF4F
Yes
Yes
Yes
Yes
IP
OptiX OSN 1500A/

1500B
N1PEG8
Yes
Yes
Yes
Yes
IP
OptiX OSN 3500/7500
N2PEX1
Yes
Yes
Yes
Yes
IP
OptiX OSN 3500/7500
N1PEX2
Yes
Yes
Yes
Yes
IP
OptiX OSN 3500/7500
N1PEFF
8
Yes
Yes
Yes
Yes
IP
OptiX OSN 3500/7500
N1EDQ4
1
Yes
No
No
Yes
VCTRUN
K
OptiX OSN 3500/7500
TNN1EX
2
Yes
Yes
Yes
Yes
IP
OptiX OSN 7500 II
TNN1EG
8
Yes
Yes
Yes
Yes
IP
OptiX OSN 7500 II
TNN1ET
MC
Yes
Yes
Yes
Yes
IP
OptiX OSN 7500 II
TNN1EF
F8
Yes
Yes
Yes
Yes
IP
OptiX OSN 7500 II

372
OptiX OSN 7500 II/7500/3500/1500

10 Link Aggregation

This section describes the limitations on and precautions for LAG in the network design phase,
Issue 03 (2012-11-30)
Applicable
Object

Details
Remarks
LAG
The member port rate and type in

one LAG must be consistent.
Otherwise, the hardware cannot
correctly perform the load sharing
hash algorithm, and consequently
packets will be discarded.
LAG
An NNI port does not support LAG.
LAG
The interconnection of a static

aggregation LAG and manual
aggregation LAG is not supported.
LAG and
ETH-OAM
The N1PEX2/N2PEX1/N1PEG8/
TNN1EX2/TNN1EG8/
TNN1ETMC/TNN1EFF8 board
does not support Ethernet service
OAM (IEEE 802.1ag) and loadsharing LAG at the same time.
LAG and QoS
When a QoS policy is applied for a

LAG, only Port Policy of the main
port can be duplicated to the slave
ports.
LAG and ELAN
When E-LAN works with LAG, a

LAG must be in load non-sharing
mode.
VCTRUNK
port on the
N1EDQ41
board
The VCTRUNK port on the

N1EDQ41 board can be configured
into only one manual aggregation
LAG in load non-sharing mode.
Aggregation
mode
A static aggregation LAG is

recommended for its high reliability.
However, when the interconnected
equipment does not support the Link
Aggregation Control Protocol
(LACP), a manual aggregation LAG
is recommended.

373
OptiX OSN 7500 II/7500/3500/1500

10 Link Aggregation
Applicable
Object

Details
Remarks
System
priority
Which port in LAGs has a higher

priority to carry services is
determined by the port priority and
the system priority of a LAG. The
system priority is considered first,
and then the port priority.
Master port
During LAG configuration, any

Ethernet port can be set to be master
port if no port is previously
configured with services; if some
ports are previously configured with
services, only one of them can be
configured into the LAG, and this
port must be set to be master port.
Slave port
A slave port can be configured into

only one LAG, and cannot be
configured with services.
Port priority
If you want to use a port to carry

services with priority, set its port
priority to a higher level.
A smaller value indicates a higher

priority level.
WTR Time
If WTR Time takes effect for a

LAG,
l The ports at both ends of the

LAG can sense link status
changes. That is, the ports at both
ends use the working mode
Auto-Negotiation.
l At both ends, the LAG is set to
the static and non-load sharing
mode.
Issue 03 (2012-11-30)
Applicable
Object

Details
Remarks
LAG
Upon the creation of a LAG, the

system will automatically
reconfigure services on the ports in
the LAG. During the
reconfiguration, services will be
transiently interrupted.

374
OptiX OSN 7500 II/7500/3500/1500

10 Link Aggregation
Applicable
Object

Details
Remarks
LAG
If the attributes of master port and

slave port in a LAG are different,
services cannot be transmitted
properly. To avoid this problem, the
system will automatically copy the
attributes of the master port to the
slave port. If the LAG is deleted, the
system will also automatically
delete the attributes of the slave port
and recover its previous attributes.
Master port
After a LAG is created, its master

port cannot be changed or deleted.
10.7 Principles
LACP implements establishment, switchover, and switchover reversion of static LAGs.
NOTE
LACP is not involved in implementation of manual link aggregation, and therefore the devices at both ends
do not exchange link aggregation control protocol data units (LACPDUs). Manual link aggregation applies
when the OptiX OSN equipment is interconnected with equipment that does not support LACP. For manual
link aggregation, LAG establishment, switchover, and switchover reversion are implemented based on the
port status, port working mode, and port rate. For details on implementation principles of manual link
aggregation, see IEEE 802.3ad.
10.7.1 LAG Establishment Process

This section describes the process of setting up a LAG.
The process of setting up a static LAG is as follows:
1.
Devices at both ends send LACPDUs to each other.
2.
Devices at both ends determine the Actor based on LACP system priorities and system IDs.
3.
Devices at both ends determine active ports (ports carrying traffic) based on the port
priorities of the Actor.
Exchanging LACPDUs Between Both Ends

As shown in Figure 10-2, you need to create a static LAG on NE1 and NE2 and add member
ports to the LAG. The member ports are enabled with LACP, and therefore NE1 and NE2 can
send LACPDUs to each other.
Issue 03 (2012-11-30)

375
OptiX OSN 7500 II/7500/3500/1500

10 Link Aggregation
Figure 10-2 Exchanging LACPDUs between both ends of a static LAG
Determining the Actor

As shown in Figure 10-3, devices at both ends receive LACPDUs from each other. Use NE2 as
an example. When NE2 receives LACPDUs from NE1, NE2 checks and records information
about NE1 and compares system priorities. If the system priority of NE1 is higher than that of
NE2, NE1 acts as the Actor and NE2 selects the ports interconnected with the active ports on
NE1 as its active ports.
If the system priority of NE1 is the same as that of NE2, the NE with a smaller system ID acts
as the Actor.
Figure 10-3 Determining the Actor
Selecting Active Ports

As shown in Figure 10-4, after devices at both ends select the Actor, both devices select active
port based on the priorities of ports on the Actor.
After active port is selected, active link in the LAG is specified and traffic is distributed across
the link.
Issue 03 (2012-11-30)

376
OptiX OSN 7500 II/7500/3500/1500

10 Link Aggregation
Figure 10-4 Selecting active ports in a static LAG
Actor
Port
priority
Port
priority
1
2
NE1
Actor
Port
priority
LAG
Active ports are
selected based
on information
at the Actor
Active Link
1
2
LAG
1
NE2
Port
priority
2
1
NE1
NE2
10.7.2 LAG Link Switchover and Reversion

This section describes the switchover process between active links and inactive links.
Switchover Conditions
In a static LAG, a link switchover is triggered if a device at one end detects one of the following
events:
l
An active link goes Down.
LACP detects a link fault.
An active port becomes unavailable.
Switchover Process
When any of the preceding trigger conditions is met, the link switchover is performed in the
following procedure:
l
For a load non-sharing LAG:

1.
The faulty link is disabled.
2.
The backup link with the highest priority is selected to replace the faulty active link.
3.
The backup link with the highest priority becomes the active link and then forwards
data.
For a load sharing LAG:

1.
Issue 03 (2012-11-30)
The faulty link is disabled.

377
OptiX OSN 7500 II/7500/3500/1500

2.
10 Link Aggregation
Traffic is re-allocated to member links based on the load sharing algorithm.
Switchover Reversion Process

For a load non-sharing static LAG that works in revertive mode, if an active port fails and
becomes an inactive port, it will work as an active port again after it recovers.
As shown in Figure 10-5, ports 1 and 2 are member ports in a static LAG, and their priorities
are 9 and 10 respectively. After port 1 fails, port 2 takes over as the active port. After port 1
recovers, port 1 works as an active port and port 2 still works as an inactive port.
Figure 10-5 Reversing a switchover (static LAG)
Port
priority
9
10
Port
priority
LAG
9
10
NE1
NE2
Active link
Standby link
NOTE
For a load non-sharing static LAG, if an active port fails and becomes an inactive port, it will work as an
active port again after it recovers. Traffic is re-allocated to member links based on the load sharing
algorithm.
Services are not switched back to a previously active link immediately after this link recovers,
but until the WTR time expires. The WTR time prevents possible frequent link status changes
from affecting service transmission on the entire LAG.
10.8 Configuring a LAG

Configuring a LAG includes creating a LAG and setting port priorities.
NOTE
The method of configuring a LAG on OptiX OSN series is similar (except for board names and slots) and
therefore this document uses OptiX OSN 3500 NEs as an example. For boards applicable to a LAG, see
the heading "Availability". For valid slots for the applicable boards, see the hardware description for a
specific OptiX OSN product.
10.8.1 Configuration Procedure

When applying the link aggregation feature, you need to create a LAG and configure the
priorities of ports in the LAG.
Figure 10-6 shows the flowchart for configuring a LAG.
Issue 03 (2012-11-30)

378
OptiX OSN 7500 II/7500/3500/1500

10 Link Aggregation
Figure 10-6 Flowchart for configuring a LAG

Required
Start
Optional
Select the link

aggregation type
Static aggregation
Manual aggregation
Select the load

sharing mode
Sharing
Non-sharing
Select an appropriate hash

algorithm
Select a LAG switchover

revertive mode
Set a WTR time
Set system priorities
Select the master and

standby ports
Set port priorities
End
Table 10-2 describes the procedures in the configuration flowchart.

NOTE
Parameter settings in Table 10-2 , excluding the system priorities, must be the same at both ends of a LAG.
Issue 03 (2012-11-30)

379
OptiX OSN 7500 II/7500/3500/1500

10 Link Aggregation
Table 10-2 Configuration procedures

Operation
Description
10.8.2
Creatin
g a LAG
Select the desired

LAG type.
Required.
Select the load

sharing mode.
Required.
A static LAG is recommended when the OptiX OSN

equipment is interconnected with equipment that supports
the LACP protocol. A manual LAG is recommended when
the OptiX OSN equipment is interconnected with
equipment that does not support the LACP protocol.
The load non-sharing mode is recommended if the LAG is

expected to provide protection for Ethernet links.
The load sharing mode is recommended if the LAG is
expected to increase link bandwidth.
Select the desired

hash algorithm.
Optional.
This parameter can be set only after Load Sharing is set
to Sharing.
The default value Automatic is recommended.
Select the LAG

switchover
revertive mode.
Optional.
This parameter can be set only after Load Sharing is set
to Non-Sharing.
If you set this parameter to Revertive, services will be
switched back to the member link with a higher priority
after it recovers from faults. A LAG switchover will cause
services to be unavailable for not more than 500 ms.
Set the WTR time.
Optional.
This parameter can be set only after Revertive Mode is set
to Revertive.
The default value 10min is recommended.
Set the system

priorities at both
ends.
Optional.
Specify master and

standby ports.
Required.
10.8.3 Setting Port Priorities
Optional.
This parameter can be set only after LAG Type is set to

Static.
Among the ports that have been configured with services,

only one port is allowed to add to a LAG and this port must
be selected as the master port.
Set higher port priorities for ports that are preferred to carry
traffic.
Issue 03 (2012-11-30)

380
OptiX OSN 7500 II/7500/3500/1500

10 Link Aggregation
10.8.2 Creating a LAG

This section describes how to create a LAG to increase Ethernet link bandwidth or improve
Ethernet link reliability between two NEs.
Prerequisites
l
Ports to be added as the master and standby ports in the LAG work in Layer 2 mode.
Ports to be added as standby ports do not carry any services.
All Ethernet ports to be added in the LAG work in full-duplex mode and at the same traffic
rate.
The LAG to be created will not contain both Ethernet ports and VCTRUNK ports.
In an inter-board LAG, the master and standby ports are provided by boards of the same
type.
Procedure
Step 1 On the Main Topology, right-click the icon of the desired NE and then choose NE Explorer
from the shortcut menu.
Step 2 In the NE Explorer, select the desired NE and choose Configuration > Packet
Configuration > Interface Management > Link Aggregation Group Management from the
Function Tree.
Step 3 Click the Link Aggregation Group Management tab.
Step 4 Click New. The Create Link Aggregation Group dialog box is displayed.
Step 5 In Attribute Settings, set LAG attributes.
Step 6 In Port Settings, set the master and standby ports.
Issue 03 (2012-11-30)

381
OptiX OSN 7500 II/7500/3500/1500

10 Link Aggregation
1.
Set Master Board and Master Port.
2.
In Available Standby Ports, specify Board to which standby ports belong.
3.
Select a standby port from Port and click
Step 7 Click Apply. In the Confirm dialog box that is displayed, click Yes.
NOTE
After a LAG is configured, services are manually reconfigured over member ports in the LAG. Therefore,
services are transiently interrupted.
Step 8 The Result dialog box is displayed, indicating that the operation is successful. Click Close.
----End
10.8.3 Setting Port Priorities

By default, all member ports in a LAG have the same port priority. By increasing the port priority
of a specific port, this port takes over with preference. If the interconnected LAG member ports
have different numbers, configure the same port priorities for these ports to ensure correct
interconnection.
Prerequisites
l
A load non-sharing static LAG has been configured. The LAG has several standby ports.
Procedure
Issue 03 (2012-11-30)

382
OptiX OSN 7500 II/7500/3500/1500

10 Link Aggregation
Function Tree.
Step 3 Click the Port Priority tab and set port priorities for the standby ports in the Port Priority
dialog box that is displayed.
Step 4 Click Apply. The Result dialog box is displayed, indicating that the operation is successful.
Click Close.
----End
10.9 Maintaining a LAG

This section describes how to query, change, and delete LAG configurations.
10.9.1 Querying LAG Configuration and Running Information

When a LAG fault occurs, query the working status of the LAG to analyze the fault causes and
locate the faulty equipment.
Prerequisites
l
LAG configurations have been completed at the opposite end.
Procedure
Function Tree.
Step 3 Click the Link Aggregation Group Management tab. Select one or more LAGs and click
Query. The query results should be consistent with the network plan.
Issue 03 (2012-11-30)

383
OptiX OSN 7500 II/7500/3500/1500

10 Link Aggregation
NOTE
l If no LAG queries have been conducted, the port statuses of all ports are Unknown.
l For an active port that is carrying traffic, the port status is Selected.
l For a backup port that does not carry traffic, the port status is Standby.
Step 4 Click the Port Priority tab. Select one or more ports and click Query. The queried port priorities
should be consistent with the network plan.
----End
10.9.2 Querying LAG Information and LACPDU Statistics

This section describes how to query LAG information and LACPDU statistics.
Prerequisites
l
LAG configurations have been completed at both the local and opposite end.
Procedure
Function Tree.
Step 3 Click the Link Aggregation Group Management tab. Right-click the desired LAG and choose
Link Aggregation Group Details or Link LACP Packet Statistics from the shortcut menu.
Step 4 In the Link Aggregation Group Details or Link LACP Packet Statistics dialog box that is
displayed, browse the query results.
Step 5 Click Cancel.
----End
10.9.3 Changing LAG Configurations

You can change LAG parameter settings except for LAG number, master port, and master board.
Issue 03 (2012-11-30)

384
OptiX OSN 7500 II/7500/3500/1500

10 Link Aggregation
Prerequisites
l
CAUTION
Modifying LAG parameter settings interrupt services.
Procedure
Function Tree.
Step 3 Change basic LAG attributes and port attributes.
1.
Click the Link Aggregation Group Management tab. Select the desired LAG and click
Modify. The Modify Link Aggregation Group dialog box is displayed.
2.
In Attribute Settings, change LAG attributes.
NOTE
l LAG No.: This parameter value cannot be changed.

l LAG Name: Changing this parameter value does not interrupt services.
l LAG Type: Changing this parameter value transiently interrupts services. Services will not be
restored until value changes are completed at both ends.
l Load Sharing: Changing this parameter value transiently interrupts services. Services will not
be restored until value changes are completed at both ends.
l Revertive Mode: Changing this parameter value does not interrupt services.
l Load Sharing Hash Algorithm: This parameter value can be changed when Load Sharing is
set to Sharing. Changing this parameter value transiently interrupts services. Services will not
be restored until value changes are completed at both ends.
Issue 03 (2012-11-30)

385
OptiX OSN 7500 II/7500/3500/1500

3.
10 Link Aggregation
In Port Settings, change port attributes.
NOTE
l Master Board and Master Port: These parameter values cannot be changed.
l Board and Port under Available Standby Ports: Changing these parameter values transiently
interrupts services. Services will not be restored until value changes are completed at both ends.
4.
Click Apply. The Result dialog box is displayed, indicating that the operation is successful.
Click Close.
Step 4 Change port priorities.

1.
Click the Port Priority tab. Double-click the Port Priority area of the desired port.
2.
Enter a new value for Port Priority.

NOTE
l For a load sharing LAG, changing port priorities does not interrupt services.
l For a load non-sharing LAG:
l If you change the port priority of the working port to a value higher than those of other ports,
services are not interrupted.
l If you change the port priority of the working port to a value lower than that of another
member port, a LAG switchover occurs and services are transiently interrupted.
3.
Click Apply. The Result dialog box is displayed, indicating that the operation is successful.
Click Close.
----End
10.9.4 Deleting a LAG

This section describes how to delete a redundant or idle LAG to release resources.
Prerequisites
l
CAUTION
Deleting a LAG interrupts services carried on the LAG.
Issue 03 (2012-11-30)

386
OptiX OSN 7500 II/7500/3500/1500

10 Link Aggregation
Procedure
Function Tree.
Step 3 Click the Link Aggregation Group Management tab. Select one or more LAGs and click
Delete. In the Confirm dialog box that is displayed, click OK.
Step 4 The Result dialog box is displayed, indicating that the operation is successful. Click Close.
----End
10.10 Configuration Example (LAG Configured to Increase

Ethernet Link Bandwidth)
This section uses an example to describe how to configure a LAG to increase Ethernet link
bandwidth.
NOTE

This section describes the service networking and planning information about a LAG configured
to increase Ethernet link bandwidth.
Service Requirements
As shown in Figure 10-7, NE1 is an OptiX OSN 3500 NE. NE1 and an RNC are interconnected
through four GE links. 4xGE services are expected to be carried between the RNC and NE1.
This means that a single GE link cannot meet the 4xGE service requirement.
Issue 03 (2012-11-30)

387
OptiX OSN 7500 II/7500/3500/1500

10 Link Aggregation
Figure 10-7 Networking application (LAG configured to increase Ethernet link bandwidth)
Solution
In this example, a load sharing LAG solution will apply. In this solution, four GE physical
Ethernet links are bundled as a 4xGE logical link to transmit the 4xGE services between NE1
and the RNC.
Service Planning
The service planning information contains the information about all the parameters required for
configuring the NE data.
NOTE
This section provides the service planning information about NE1 only. The service planning information
about the RNC should be consistent with that about NE1.
Issue 03 (2012-11-30)
Parameter
Value
LAG No.
Assign automatically (default value)
LAG Name
LAG1
LAG Type
Static (default value)
Revertive Mode
Non-revertive
Load Balancing
Sharing
Load Balancing Hash

Algorithm
Automatic (default value)
LAG Priority
32768 (default value)
Master Board
1-N1PEG8
Master Port
1 (PORT-1)
Board
1-N1PEG8

388
OptiX OSN 7500 II/7500/3500/1500

10 Link Aggregation
Parameter
Value
Selected Standby Ports
N1PEG8-2 (PORT-2)
N1PEG8-3 (PORT-3)
N1PEG8-4 (PORT-4)
Port Priority
N1PEG8-1 (PORT-1): 32768 (default value)


This section describes how to configure the LAG to increase Ethernet link bandwidth in this
example.
Prerequisites
l
You are familiar with the service networking and planning information.
Procedure
Step 1 Follow instructions in 10.8.2 Creating a LAG and create a LAG.
Parameter
Value
LAG No.
LAG Name
LAG1
LAG Type
Revertive Mode
Non-revertive
Load Balancing
Sharing
Load Balancing Hash

Algorithm
Automatic (default value)
LAG Priority
Master Board
1-N1PEG8
Master Port
1 (PORT-1)
Board
1-N1PEG8
N1PEG8-2 (PORT-2)
N1PEG8-3 (PORT-3)
N1PEG8-4 (PORT-4)
Issue 03 (2012-11-30)

389
OptiX OSN 7500 II/7500/3500/1500

10 Link Aggregation
Step 2 Follow instructions in 10.8.3 Setting Port Priorities and set port priorities.
Parameter
Value
Port Priority

Step 3 Follow instructions in 10.9.1 Querying LAG Configuration and Running Information and
query LAG configuration and running information.
----End
10.11 Configuration Example (LAG Configured to Provide

Link Protection)
This section uses an example to describe how to configure a LAG to provide protection for
Ethernet links.
NOTE

This section describes the service networking and planning information about a LAG configured
to provide protection for Ethernet links.
As shown in Figure 10-8, NE1 is an OptiX OSN 3500 NE. NE1 and an RNC are interconnected
through two GE links. 1xGE service is expected to be carried between the RNC and NE1. A
single GE link failure will not interrupt the service.
Figure 10-8 Networking application (LAG configured to provide protection for Ethernet links)
Issue 03 (2012-11-30)

390
OptiX OSN 7500 II/7500/3500/1500

10 Link Aggregation
Solution
In this example, a load non-sharing LAG solution will apply. In this solution, two GE links are
bundled as a LAG to provide 1+1 link backup and to ensure reliable transmission of the service
between the RNC and NE1.
NOTE
A load non-sharing LAG supported by the OptiX OSN equipment provides only 1+1 link backup.
Service Planning
The service planning information contains the information about all the parameters required for
configuring the NE data.
NOTE
This section provides the service planning information about NE1 only. The service planning information
about the RNC should be consistent with that about NE1.
Parameter
Value
LAG No.
LAG Name
LAG1
LAG Type
Revertive Mode
Revertive (default value)
Load Balancing
Non-Sharing
LAG Priority
WTR Time (min)
10 (default value)
Master Board
1-N1PEG8
Master Port
1 (PORT-1)
Board
1-N1PEG8
N1PEG8-2 (PORT-2)

This section describes how to configure the LAG to provide protection for Ethernet links in this
example.
Prerequisites
l
You are familiar with the service networking and planning information.
Issue 03 (2012-11-30)

391
OptiX OSN 7500 II/7500/3500/1500

10 Link Aggregation
Procedure
Step 1 Follow instructions in 10.8.2 Creating a LAG and create a LAG.
Parameter
Value
LAG No.
LAG Name
LAG1
LAG Type
Revertive Mode
Revertive (default value)
Load Balancing
Non-Sharing
LAG Priority
WTR Time (min)
10 (default value)
Master Board
1-N1PEG8
Master Port
1 (PORT-1)
Board
1-N1PEG8
N1PEG8-2 (PORT-2)
Step 2 Follow instructions in 10.9.1 Querying LAG Configuration and Running Information and
query LAG configuration and running information.
----End
10.12 Verifying a LAG

This topic describes how to check whether a LAG works properly by verifying the basic functions
of the LAG.
Prerequisites
The LAG must be configured.
NOTE
This topic considers the TDM mode as an example to describe how to verify a LAG and provides a reference
for you to verify a LAG in packet mode. The difference between LAG verification in the two modes is
with regard to the navigation path to the Link Aggregation Group Management tab page.
l In TDM mode: In the NE Explorer, select the required Ethernet board and choose Configuration >
Interface Management > Link Aggregation Group Management from the Function Tree.
l In packet mode: In the NE Explorer, select the required NE and choose Configuration > Interface
Management > Link Aggregation Group Management from the Function Tree.
Figure 10-9 shows the networking of a LAG, in which the port that is connected to link 1
functions as the main port and the port that is connected to link 2 functions as the slave port.
You can verify the LAG in the following aspects:
Issue 03 (2012-11-30)

392
OptiX OSN 7500 II/7500/3500/1500

10 Link Aggregation
After the network is faulty, the LAG enables service switching.
If the LAG is in load non-sharing mode, the LAG works properly after the parameters for
the LAG are changed.
If the LAG is in load non-sharing mode and is set to revertive, the service is switched back
to the main port after the fault on the link connected to the main port is rectified.
Figure 10-9 Networking diagram of a LAG

NE1
NE2
LAG
Link 1
Link 2
Procedure
Step 1 After the network is faulty, the LAG enables service switching.
1.
Disconnect the fiber or Ethernet cable from the main port.
2.
In the Main Topology, right-click NE1 and choose NE Explorer from the shortcut menu.
3.
In the NE Explorer, select the required Ethernet board and choose Configuration >
Interface Management > Link Aggregation Group Management from the Function
Tree.
4.
In the right pane, select the configured LAG and then click Query. Check whether the main
and slave ports work properly.
Step 2 If the LAG is in load non-sharing mode, the LAG works properly after the parameters for the
LAG are changed.
1.
2.
Tree.
3.
4.
Select the configured LAG and then click Modify. Change Load Sharing to Sharing for
NE1. Then, check whether the states of the main and slave ports are In Service.
5.
Click Apply. The Operation Result dialog box is displayed, indicating that the operation
is successful.
6.
Repeat Steps a to f to modify the parameters of the LAG on NE2.
7.
Repeat Steps a to c to query the states of the main and slave ports in the LAGs on NE1 and
NE2. The states of the main and slave ports are In Service.
Step 3 If the LAG is in load non-sharing mode and is set to revertive, the service is switched back to
the main port after the fault on the link connected to the main port is rectified.
1.
Issue 03 (2012-11-30)
393
OptiX OSN 7500 II/7500/3500/1500

10 Link Aggregation
2.
Tree.
3.
4.
Disconnect the fiber or Ethernet cable from the main port.
5.
Repeat steps a to c to query the states of the main and slave ports in the LAGs on NE1 and
NE2.
6.
Reconnect the fiber or Ethernet cable to the main port.
7.
Repeat steps a to c to query the states of the main and slave ports in the LAGs on NE1 and
NE2.
NOTE
If the main and slave ports in the LAGs on NE1 and NE2 are restored to the initial states, it indicates
that the LAGs work properly.
----End
Symptom
The common LAG faults are as follows:
l
The member ports become unavailable, because the LAG is faulty. As a result, the services
are interrupted.
Certain packets are discarded, because the member ports in the LAG become unavailable.
Possible Causes
l
The NEs at both ends of the LAG are configured incorrectly.
The member ports in the LAG work in half-duplex mode.
Loopbacks are performed on the member ports in the LAG.
The member ports in the LAG are disconnected.
Flow Chart
NOTE
This topic describes the process for rectifying a LAG fault when the LAG function is enabled in TDM
mode. This topic also provides a reference for you to rectify a LAG fault because the process for rectifying
a LAG fault when the LAG function is enabled in packet mode is similar. The differences between the
troubleshooting processes in two modes are as follows:
l The navigation path to the Link Aggregation Group Management tab page is different.
l The alarms that cause a LAG failure in the two modes are different. In packet mode, the LAG_DOWN
or LAG_MEMBER_DOWN alarm causes a LAG failure.
Issue 03 (2012-11-30)

394
OptiX OSN 7500 II/7500/3500/1500

10 Link Aggregation
Figure 10-10 Flow chart for rectifying a LAG fault
Start
The
LAG_FAIL
alarm occurs?
Yes
Handle the
alarm
No
The
configurations of
both NEs at both
ends are
incorrect?
Yes
Modify the
configurations of
both NEs
Yes
Modify the working

mode of the port to
full-duplex
No
The port works

in half-duplex
mode?
No
The
LOOP_ALM or
ETH_EFM_LOOPBACK
alarm occurs?
Yes
Release the
loopback at the port
No
The ETH_LOS or
ETH_LINK_DOWN
alarm occurs?
Yes
Rectify the connection

fault at the port to
clear the alarm
No
The fault is
rectified?
Yes
Contact Huawei
technical support
engineers to handle the
fault
Issue 03 (2012-11-30)

End
395
OptiX OSN 7500 II/7500/3500/1500

10 Link Aggregation
Procedure
Step 1 Cause 1: The NEs at both ends of the LAG are configured incorrectly.
1.
On the U2000, check whether the LAG_DOWN or LAG_MEMBER_DOWN alarm is

reported.
2.
If yes, see the Alarms and Performance Events Reference to clear the alarm. Then, check
whether the fault is rectified.
Step 2 Cause 2: The member ports in the LAG work in half-duplex mode.
1.
Check whether the member ports in the LAG work in half-duplex mode.
2.
If yes, change the working mode to full-duplex and ensure that the ports on the local and
opposite NEs work in the same mode.
Step 3 Cause 3: Loopbacks are performed on the member ports in the LAG.
1.
Check whether the LOOP_ALM or ETH_EFM_LOOPBACK alarm is reported on the

member ports in the LAG.
2.
If yes, release the loopback status to clear the LOOP_ALM or ETH_EFM_LOOPBACK

alarm.
Step 4 Cause 4: The member ports in the LAG are disconnected.

1.
Check whether the ETH_LOS or ETH_LINK_DOWN alarm is reported on the member

ports in the LAG.
2.
If yes, see the Alarms and Performance Events Reference to clear the alarm. Then, check
whether the fault is rectified.
Step 5 If the fault persists, contact the technical support engineers of Huawei.
----End

This section describes the alarms and performance events that are associated with the link
aggregation feature.

This section describes the alarms that are associated with the link aggregation feature.
Issue 03 (2012-11-30)
Name
Alarm Description
LAG_DOWN
Indicates that a LAG fails. This alarm is reported when the number of
activated members in a LAG is 0.
LAG_MEMBER
_DOWN
Indicates that a member port in a LAG fails. This alarm is reported when
a member port cannot be activated or cannot work as a backup port.

396
OptiX OSN 7500 II/7500/3500/1500

10 Link Aggregation

There are no performance events associated with the link aggregation feature.

This section describes parameters associated with LAG management.
10.15.1 LAG Management_LAG Creation

This section describes parameters associated with LAG creation.
Table 10-3 Attribute parameters
Parameter
Value Range
Description
LAG No.
OptiX OSN
7500 II: 1-128
This parameter specifies the LAG ID. This parameter can be

set only if Assign automatically is not selected.
OptiX OSN
7500/3500:
1-64
OptiX OSN
1500: 1-16
For example,
1
LAG Name
A character
string with
less than 64
characters,
which can be
letters,
numerals, and
special
characters.
This parameter specifies the LAG name.
For example,
LAG1
Issue 03 (2012-11-30)

397
OptiX OSN 7500 II/7500/3500/1500

10 Link Aggregation
Parameter
Value Range
Description
LAG Type
Static, Manual
This parameter specifies the LAG type.

Value description:
Default value:
Static
l Static: In static link aggregation, a user creates a LAG

and Link Aggregation Control Protocol (LACP) is started
if a member port is added or deleted. Member ports in a
LAG may be in selected, standby, or unselected state. The
devices at both ends exchange LACPDUs and negotiate
ports and links to be aggregated.
l Manual: In manual link aggregation, a user creates a
LAG and LACP is not started if a member port is added
or deleted. Member ports of a manual LAG may be in up
or down state. The system determines whether to perform
link aggregation depending on the physical port status (up
or down), working mode, and port rate.
Recommendations:
The devices at both ends of a LAG must use the same link
aggregation mode.
It is recommended that you set this parameter to Static
because a static LAG provides higher link reliability than a
manual LAG. Set this parameter to Manual when the OptiX
OSN equipment is interconnected with equipment that does
not support LACP. For a manual LAG, it is recommended
that you configure IEEE 802.3ah OAM to monitor the link
status and enable both ends to perform a LAG switchover
once a unidirectional fiber cut is detected.
Switch
Protocol
This parameter specifies the switchover protocol for a

manual LAG.
The OptiX OSN equipment does not support this parameter.
Switching
Mode
This parameter specifies the switchover mode for a manual

LAG.
Link
Detection
Protocol
Issue 03 (2012-11-30)
This parameter specifies whether the link monitoring

protocol is used for a manual LAG.

398
OptiX OSN 7500 II/7500/3500/1500

10 Link Aggregation
Parameter
Value Range
Description
Revertive
Mode
Revertive,
Non-revertive
This parameter specifies whether services are switched back

to member links with higher priorities after these links
recover from faults.
Impacts on the system:
Default value:
NonRevertive
If you set this parameter to Revertive, services will be

switched back to the member link with a higher priority after
it recovers from faults. A LAG switchover will cause services
to be unavailable for not more than 500 ms.
Value description:
l Revertive: Services will be switched back to the member
link with a higher priority after the link recovers from
faults.
l Non-Revertive: Services will not be switched back to the
member link with a higher priority after the link recovers
from faults. Services will be switched back only after the
member link that is carrying the services fails.
Recommendations:
For a manual LAG, if IEEE 802.3ah OAM is not used for
monitoring the LAG status and this parameter is set to
Revertive, services will be interrupted when a unidirectional
fiber cut occurs.
This parameter value must be the same at both ends of a LAG.
Association with other parameters:
This parameter can be set only after Load Sharing is set to
Non-Sharing.
Issue 03 (2012-11-30)

399
OptiX OSN 7500 II/7500/3500/1500

10 Link Aggregation
Parameter
Value Range
Description
Load
Balancing
Non-Sharing,
Sharing
This parameter specifies whether more than one port is used

to carry traffic when a LAG has several member ports.
Value description:
Default value:
Non-Sharing
l Sharing: Each member link in a LAG carries traffic. That

is, the member links in the LAG share the load. The
sharing mode increases Ethernet link bandwidth. When a
member in a LAG changes or a link fails, the traffic is reallocated automatically.
l Non-Sharing: Only one member link of a LAG carries
traffic and the other member link is in standby state. In
this case, a link hot backup mechanism is provided. When
the active link of a LAG is faulty, the system activates the
standby link to transmit service traffic.
Recommendations:
It is recommended that you set this parameter to NonSharing when a LAG is expected to provide link protection.
It is recommended that you set this parameter to Sharing
when a LAG is expected to increase link bandwidth.
For a manual LAG, both ends must use the same load sharing
mode; otherwise, services will be interrupted.
If Load Sharing is set to Sharing, Revertive Mode and
WTR Time (min) cannot be set.
Issue 03 (2012-11-30)

400
OptiX OSN 7500 II/7500/3500/1500

10 Link Aggregation
Parameter
Value Range
Description
Load
Balancing
Hash
Algorithm
Automatic,
Source MAC,
Destination
MAC, Source
and
Destination
MACs,
Source IP,
Destination IP
Address,
Source and
Destination IP
Address,
Source Port
Number,
Destination
Port Number,
Source and
Destination
Port Numbers,
MPLS Label
This parameter specifies the load sharing algorithm used at

member ports in a LAG.
Default value:
Automatic
If a LAG has several ports to carry traffic, the traffic is

allocated in different manners when this parameter is set to
different values. If this parameter is set to an appropriate
value, traffic is balanced between the member ports. If this
parameter is set to an inappropriate value, traffic balancing
between the ports fails and port bandwidth cannot be fully
used.
After the configuration data is deployed, Load Sharing
Hash Algorithm takes effect for the entire NE.
Value description:
l Automatic: Packets are allocated to member ports based
on their source and destination MAC addresses.
l Source MAC: Packets are allocated to member ports
based on their source MAC addresses.
l Destination MAC: Packets are allocated to member ports
based on their destination MAC addresses.
l Source and Destination MACs: Packets are allocated to
member ports based on their source and destination MAC
addresses.
l Source IP: Packets are allocated to member ports based
on their source IP addresses.
l Destination IP Address: Packets are allocated to
member ports based on their destination IP addresses.
l Source and Destination IP Address: Packets are
allocated to member ports based on their source and
destination IP addresses.
l Source Port Number: Packets are allocated to member
ports based on their source port numbers.
l Destination Port Number: Packets are allocated to
member ports based on their destination port numbers.
l Source and Destination Port Numbers: Packets are
allocated to member ports based on their source and
destination port numbers.
l MPLS Label: Packets are allocated to member ports
based on their MPLS labels.
The OptiX OSN equipment supports Automatic, Source
MAC, Destination MAC, and Source and Destination
MACs only.
Recommendations:
Select the appropriate hash algorithm based on differences
between received packets, enabling traffic to be balanced
over member ports. It is recommended that you set this
parameter to Automatic.
Issue 03 (2012-11-30)

401
OptiX OSN 7500 II/7500/3500/1500

Parameter
Value Range
10 Link Aggregation
Description
Ensure that both ends of a LAG use the same hash algorithm.
This parameter can be set only after Load Sharing is set to
Sharing.
LAG
Priority
0 to 65535
This parameter specifies the LAG priority at the local end.
Default:
32768

When a local LAG negotiates with an opposite LAG through
LACPDUs, both LAGs can obtain the system priorities of
each other. The LAG with the lower system priority changes
its link aggregation information to be consistent with that of
the LAG with the higher system priority. If the LAG priorities
at both ends are the same, the system MAC addresses are
compared. The LAG with the larger system MAC address
changes its link aggregation information to be consistent with
that of the LAG with the smaller system MAC address.
Recommendations:
The smaller the value, the higher the system priority.
This parameter can be set only after LAG Type is set to
Static.
Ports that are preferred to carry services are determined by
LAG Priority and Port Priority. LAG Priority precedes
Port Priority.
WTR Time
(min)
1 to 30
Default: 10
This parameter specifies the time for services to wait before

being switched from the standby link to the master link that
has recovered from faults. An appropriate WTR time
prevents possible link status changes from resulting in
frequent LAG switchovers.
Recommendations:
It is recommended that you set this parameter to 10.
This parameter can be set only after Revertive Mode is set
to Revertive.
Table 10-4 Port parameters
Issue 03 (2012-11-30)
Parameter
Value Range
Description
Master
Board
Slot ID-board
name
This parameter specifies the master board in a LAG.
For example,
4-N1PEG8
Set this parameter according to the plan.
Recommendations:

402
OptiX OSN 7500 II/7500/3500/1500

10 Link Aggregation
Parameter
Value Range
Description
Master Port
Port number
(PORTnumber)
This parameter specifies the master port in a LAG. The

master port represents the LAG. A LAG contains only one
master port. All LAG attributes, such as MAC addresses and
IP addresses, are actual the attributes of the master port. In
addition, all services carried by the LAG are configured on
the master port.
For example,
1 (PORT-1)
Recommendations:
Among all the ports to be added to a LAG, only one port is
allowed to have been configured with services and this port
must be configured as the master port; if none of these ports
is configured with services, each port can be configured as
the master port.
Board
Port
Selected
Standby
Ports
Slot ID-board
name
This parameter specifies the standby board in a LAG.
For example,
4-N1PEG8
Slot ID-board
name-port
number
(PORTnumber)
This parameter specifies the standby port in a LAG. All ports

other than the master port in a LAG are standby ports.
For example,
4-N1PEG8-2
(PORT-2)
Slot ID-board
name-port
number
(PORTnumber)
This parameter displays the selected standby ports.
Recommendations:
Standby ports may also be used to carry traffic.

Recommendations:
For example,
4-N1PEG8-2
(PORT-2)
10.15.2 LAG Management_Port Priority Setting

This section describes parameters associated with port priorities.
Issue 03 (2012-11-30)

403
OptiX OSN 7500 II/7500/3500/1500

10 Link Aggregation
Table 10-5 Parameters on the main interface

Parameter
Value Range
Description
Port
Slot ID-board
name-port
number
(PORTnumber)
This parameter displays the port whose priority can be set.
For example,
4-N1PEG8-2
(PORT-2)
Port Priority
0 to 65535
Default:
32768
This parameter specifies priorities of ports in a LAG. When

member ports of a static LAG have the same port rate and
working mode, ports with higher priorities transmit traffic
with preference. This parameter does not take effect on a
manual LAG.
Recommendations:
l The smaller the value, the higher the port priority.
l Set a higher priority for a port that is preferred to transmit
traffic.
l If the master port transmit traffic with preference, you
need to set the priority of the master port higher than
priorities of all standby ports.
l If the manually specified master port does not have the
highest port priority, the standby port with the highest
priority automatically transmits traffic.
10.15.3 LAG Management_LAG Information Query

This section describes parameters displayed in the LAG information query result.
Table 10-6 Parameters on the main interface
Parameter
Value Range
Description
LAG No.
1 to 128
This parameter displays the LAG number.
For example,
1
Local
System ID
LAG priority,
system MAC
address
This parameter displays the LAG system ID at the local end.
For example,
32768,
8-0-62-9-0-8
Issue 03 (2012-11-30)

404
OptiX OSN 7500 II/7500/3500/1500

10 Link Aggregation
Parameter
Value Range
Description
Local Port
Slot ID-board
name-port
number
(PORTnumber)
This parameter displays the local ports.
For example,
4-N1PEG8-2
(PORT-2)
Local
Logical Port
Number
For example,
3586
This parameter displays the local logical port numbers.
Local Port
Priority
For example,
32768
This parameter displays the local port priorities.
Local Port
Selection
Status
Selected,
Standby,
Unselected
This parameter displays the status of a local port.
Local Port
Service
Bearer
YES, NO
This parameter displays whether a local port carries traffic.
Reference
Port
YES, NO
This parameter displays whether a local port is a reference

port.
Local
Operation
KEY
For example,
257
This parameter displays the local LAG operation key.
Local LACP
Protocol
Flag
For example,
71
This parameter displays the LACP flag used at the local end.
Opposite
System ID
LAG priority,
system MAC
address
This parameter displays the LAG system ID at the opposite

end.
For example,
32768,
8-0-62-9-0-8
Issue 03 (2012-11-30)
Opposite
Logical Port
Number
For example,
65535
This parameter displays the opposite logical port number.
Opposite
Port Priority
For example,
32768
This parameter displays the opposite port priorities.
Opposite
Operation
KEY
For example,
256
This parameter displays the opposite LAG operation key.

405
OptiX OSN 7500 II/7500/3500/1500

Issue 03 (2012-11-30)
10 Link Aggregation
Parameter
Value Range
Description
Opposite
LACP
Protocol
Flag
For example,
72
This parameter displays the LACP flag used at the opposite

end.

406
OptiX OSN 7500 II/7500/3500/1500

11 LPT
11
LPT
About This Chapter

With LPT enabled, service protection can be provided regardless of whether faults occur on a
service access node, a service network, or both on a service access node and on a service network.
11.1 Introduction
With LPT enabled, transmission NEs detect faults on a service access node or on a service
network and instruct the devices at both ends of the service network to immediately activate a
backup network for communication.
11.2 Basic Concepts
LPT feature.
11.3 Specifications
This section describes the specifications of the LPT feature.
This section describes the standards and protocols associated with LPT.
11.5 Availability
The LPT feature requires the support of the applicable NEs, NMSs, and boards.
This section describes the limitations on and precautions for LPT in the network design phase,
11.7 Principles
This section describes LPT working principles.
11.8 Configuring LPT
This section describes how to configure point-to-point LPT and point-to-multipoint LPT.
11.9 Maintaining LPT Configurations
This section describes how to query, change, and delete point-to-point and point-to-multipoint
LPT configurations.
11.10 Configuration Example (LPT Based on an E-Line Service Exclusively Occupying a UNI
Port)
Issue 03 (2012-11-30)

407
OptiX OSN 7500 II/7500/3500/1500

11 LPT
This section uses an example to describe how to configure LPT based on an E-Line service
exclusively occupying a UNI port.
11.11 Configuration Example (LPT Based on Ethernet Services Sharing a UNI Port)
This section uses an example to describe how to configure LPT based on Ethernet services
sharing a UNI port.
11.12 Verifying LPT
To check whether the LPT is configured successfully, simulate the fault on the link where the
access node is involved and query the reported alarm.
To locate and rectify the common faults in a timely manner, you need to get familiar with the
fault symptoms and the troubleshooting flow. This topic describes how to handle common LPT
faults by using point-to-multipoint LPT as an example.
This section describes the alarms and performance events that are associated with the LPT
feature.
This section describes parameters for configuring point-to-point LPT and for configuring pointto-multipoint LPT.
Issue 03 (2012-11-30)

408
OptiX OSN 7500 II/7500/3500/1500

11 LPT
11.1 Introduction
With LPT enabled, transmission NEs detect faults on a service access node or on a service
network and instruct the devices at both ends of the service network to immediately activate a
backup network for communication.
Existing and conventional network protection schemes function when faults are found on a
service access node or on a service network.
With LPT enabled, it will instruct the devices at two ends of the service network to immediately
activate the backup network for service transmission once detecting faults on a service access
point or on a service network.
As shown in Figure 11-1, LPT-enabled NE1 and NE2 disconnect their access links from the
NodeB and the RNC if the link between NE1 and the NodeB, the link between NE2 and the
RNC, or the service network becomes faulty. The NodeB and the RNC immediately detect the
link failure between them, and switch to a backup network for communication.
Figure 11-1 Typical application of LPT
11.2 Basic Concepts

LPT feature.
Fault Detection Mechanism

After LPT is enabled, a fault is detected in either of the following ways:
l
LPT OAM
The LPT protocol components exchange LPT protocol packets between LPT NEs on a
service network and determine the status of the LPT links between the NEs based on the
negotiation result.
Issue 03 (2012-11-30)

409
OptiX OSN 7500 II/7500/3500/1500

11 LPT
PW OAM
The LPT protocol components exchange LPT protocol packets between LPT NEs on a
service network and determine the status of the LPT links between the NEs based on the
negotiation result and the statuses of PWs carried on the LPT links. The LPT protocol
components consider that LPT links are working properly only when negotiation using LPT
packets is successful and PWs are functional. If negotiation using LPT packets fails or PWs
are faulty, the LPT protocol components consider that the LPT links are faulty.
LPT Point Types

When LPT is enabled, LPT points detect system running information. There are two types of
LPT points:
l
Primary point
The primary point is the entity running the LPT protocol. The LPT protocol components
determine the LPT status based on the running status of the primary point.
Secondary point
A secondary point detects and transfers changes in the LPT port status, such as changes in
the local port status and changes in the remote point status.
NOTE
In point-to-point LPT configuration, there is one primary point and one secondary point. In point-tomultipoint LPT configuration, there are one primary point and several secondary points, which correspond
to the root node and leaf nodes in a networking topology.
Switching Modes
l
Strict mode
A primary point triggers LPT switching when all of its secondary points detect faults.
Non-strict mode
A primary point triggers LPT switching when one of its secondary points detects a fault.
NOTE
In point-to-point LPT configuration, there is only one secondary point and therefore the switching mode
does not make any difference.
11.3 Specifications
This section describes the specifications of the LPT feature.
Table 11-1 Specifications of the LPT feature
Item
Specifications
Number of NEs
supported by LPT
l OptiX OSN 7500 II/7500/3500: 96
Switching mode
l Strict mode
l OptiX OSN 1500: 16
l Non-strict mode
NOTE
The LPT switching mode is available only to point-to-multipoint LPT.
Issue 03 (2012-11-30)

410
OptiX OSN 7500 II/7500/3500/1500

11 LPT
Item
Specifications
Fault detection
mechanism
LPT OAM
PW OAM
Switching condition
l ETH_LOS
NNI side:
l ETH_LINK_DOWN
l dServer
l LSR_NO_FITED
l dLOCV
l dTTSI_Mismatch
l dTTSI_Mismerge
l dExcess
UNI side:
l ETH_LOS
l ETH_LINK_DOWN
l LSR_NO_FITED
Switching time
Faults on the access side: 3 s

Faults on the network side: 300 ms

This section describes the standards and protocols associated with LPT.
LPT complies with Huawei proprietary protocols.
11.5 Availability
The LPT feature requires the support of the applicable NEs, NMSs, and boards.
Version Support
Issue 03 (2012-11-30)
Product
Applicable Version
OptiX OSN 1500A/1500B/3500
V100R009C03
T2000
V200R007C03
Product
Applicable Version
OptiX OSN 1500A/1500B/3500/7500
U2000

411
OptiX OSN 7500 II/7500/3500/1500

11 LPT
Product
Applicable Version
OptiX OSN 7500 II
U2000
Hardware Support
Board Type
Applicable NE Version
Applicable NE
N1PEG16
OptiX OSN 3500
N1PEX1
OptiX OSN 3500
N1PETF8
OptiX OSN 3500/7500
R1PEFS8
Q1PEGS2
R1PEGS1
N1PEG8
OptiX OSN 3500/7500
N2PEX1
OptiX OSN 3500/7500
N1PEX2
OptiX OSN 3500/7500
N1PEFF8
OptiX OSN 3500/7500
R1PEF4F
TNN1EX2
OptiX OSN 7500 II
TNN1EG8
OptiX OSN 7500 II
TNN1ETMC
OptiX OSN 7500 II
TNN1EFF8
OptiX OSN 7500 II

This section describes the limitations on and precautions for LPT in the network design phase,
Issue 03 (2012-11-30)
Applicable
Object

Details
Remarks
LPT
If LPT uses PW OAM, cross-board

tunnel APS cannot be used to protect
PWE3 services on the NNI side.

412
OptiX OSN 7500 II/7500/3500/1500

11 LPT
Applicable
Object

Details
Remarks
LPT
Ensure that the OAM detection

modes of LPT at both ends are the
same.
LPT
When MS-PW coexists with LPT,

the fault detection mode of LPT can
only be set to PW OAM.

Applicable
Object

Details
Remarks
LPT
During the LPT configuration,

ensure that the UNI port works
properly. Otherwise, LPT cannot
work properly.
LPT
When LPT uses PW OAM, ensure

that PW OAM works properly.
Point-to-point
LPT
A UNI port cannot be configured in

a VLAN or enabled with DCN.
Point-to-point LPT needs to

exclusively occupy a UNI port.
Applicable
Object

Details
Remarks
LPT
When the working mode of the UNI

port with the LPT function enabled
is set to the non-auto-negotiation
mode, the LPT switching cannot be
triggered by the transmit direction
fault.
Tunnel APS
and LPT
When using the PW OAM detection

methods and Tunnel APS coupling
LPT, LPT need to bind the first
configuration of the PW.
11.7 Principles
This section describes LPT working principles.
Issue 03 (2012-11-30)

413
OptiX OSN 7500 II/7500/3500/1500

11 LPT
11.7.1 LPT State Transition

This section describes the LPT state transition process.
NOTE
The LPT state transition process is the same regardless of whether LPT uses LPT OAM or PW OAM to
detect faults.
In the LPT state transition process, common LPT faulty states are as follows:
l
Initial state: The LPT protocol components have not received LPT protocol packets.
Access-side faulty state: A port fault or link fault occurs on the local service access side.
NOTE
l If an LPT-enabled UNI port is configured in a LAG, LPT switching is triggered only when all
ports or links in the LAG are faulty.
l If an LPT-enabled UNI port is not configured in a LAG, LPT switching is triggered when the
port or its link is faulty.
Network-side faulty state: A local NNI port or link is faulty or a peer UNI port or link is
faulty.
Figure 11-2 shows the LPT state transition process.

Figure 11-2 LPT state transition
The LPT state transition process is described as follows:

1.
LPT changes from the initial state to a normal state once the LPT protocol components
receive LPT protocol packets.
2.
LPT changes from a normal state to the initial state once the LPT protocol components fail
to receive LPT protocol packets.
Issue 03 (2012-11-30)

414
OptiX OSN 7500 II/7500/3500/1500

11 LPT
3.
LPT changes from a normal state to the network-side faulty state once the LPT protocol
components detect network-side faults.
4.
LPT changes from the network-side faulty state to the wait-to-restore (WTR) state once
the LPT protocol components detect that the network-side faults have been rectified.
5.
LPT changes from the WTR state to the network-side faulty state once the LPT protocol
components detect network-side faults.
6.
LPT changes from the WTR state to the fault recovery state once the LPT protocol
components detect that access-side faults have been rectified.
7.
LPT changes from the fault recovery state to a normal state once the LPT protocol
components detect that all access-side and network-side faults have been rectified.
8.
LPT changes from the fault recovery state to the network-side faulty state once the LPT
protocol components detect network-side faults.
9.
LPT changes from the fault recovery state to the access-side faulty state once the LPT
protocol components detect access-side faults.
10. LPT changes from the access-side faulty state to the WTR state once the LPT protocol
components detect that the access-side faults have been rectified.
11. LPT changes from the WTR state to the access-side faulty state once the LPT protocol
components detect access-side faults.
12. LPT changes from the access-side faulty state to the network-side faulty state once the LPT
protocol components detect network-side faults.
13. LPT changes from a normal state to the access-side faulty state once the LPT protocol
components detect access-side faults.
14. LPT changes from the access-side faulty state to the initial state once the LPT protocol
components do not receive LPT protocol packets.
15. LPT changes from the initial state to the access-side faulty state once the LPT protocol
components receive LPT protocol packets and detect access-side faults.
11.7.2 Point-to-Point LPT Switching

This section describes the point-to-point LPT switching principles.
Point-to-Point LPT Switching Against an Access-Side Fault

l
Fault detection
Reports the link
fault alarm.
Access
node A
Service network
Service
equipment A
Broken
Disconnects the link from

access node B and reports the
LPT_CFG_CLOSEPORT alarm.
Service
equipment B
Access
node B
1.
When detecting that the link connected to access node A is faulty, service equipment A
transmits Broken packets to service equipment B.
2.
After receiving the Broken packets, service equipment B disconnects its link from access
node B and reports the LPT_CFG_CLOSEPORT alarm.
Fault recovery
Issue 03 (2012-11-30)

415
OptiX OSN 7500 II/7500/3500/1500

Stops reporting the link

fault alarm.
Access
node A
11 LPT
Restores the link to

access node B.
Service network
Non_Broken
Service
equipment A
Service
equipment B
Access
node B
1.
After detecting that the link connecting to access node A has recovered, service equipment
A stops reporting the link fault alarm and transmits Non_Broken packets to service
equipment B.
2.
After receiving the Non_Broken packets, service equipment B restores its link to access
node B.
Point-to-Point LPT Switching Against a Network-Side Fault

l
Fault detection
Service equipment A and service equipment B can detect whether the service network is
available. If the service network is unavailable, service equipment A and service equipment B
transmit Broken packets to each other. Service equipment A and service equipment B disconnect
their links from access node A and access node B and reports the LPT_CFG_CLOSEPORT
alarm.
NOTE
If the service network is unavailable only in one direction, only the equipment at one end (for example,
service equipment A) can detect the service network fault and immediately disconnect its link from access
node A. At the same time, service equipment A transmits Broken packets to service equipment B. After
receiving the Broken packets, service equipment B disconnects its link from access node B and reports the
Fault recovery
1.
When detecting that the service network has recovered, service equipment A and service
equipment B transmit Non-Broken packets to each other for notifying link recovery. In
addition, service equipment A and service equipment B restore their links to access node
A and access node B.
2.
After service equipment A and service equipment B receive Non_Broken packets from
each other or after waiting for Broken packets is timeout, service equipment A and service
Issue 03 (2012-11-30)

416
OptiX OSN 7500 II/7500/3500/1500

11 LPT
equipment B determine that the entire LPT link is functional and then activate their links
between each other.
11.7.3 Point-to-Multipoint LPT Switching

This section describes the point-to-multipoint LPT switching principles.
Point-to-Multipoint LPT Switching Against a Fault on a Convergence-Side Access

Node
l
Fault detection
Convergence side
Access side
Network side
Disconnects the link from access

node B and reports the
Reports the link
fault alarm.
Access
node A
Broken
Service
equipment A
Service
equipment B

node C and reports the
Service network
Broken
Access
node B
Service
equipment C
Access
node C
1.
When detecting that the link connected to access node A is faulty, service equipment A
transmits Broken packets to service equipment B and service equipment C.
2.
After receiving the Broken packets, service equipment B and service equipment C
disconnect their links from access node B and access node C and report
LPT_CFG_CLOSEPORT alarms.
Fault recovery
Convergence side

fault alarm.
Access
node A
Access side
Network side
Non_Broken
Service
equipment A
Service
equipment B

access node B.
Access
node B
Service network
Non_Broken
Service
equipment C

access node C.
Access
node C
1.
After detecting that the link connecting to access node A has recovered, service equipment
A stops reporting the link fault alarm and transmits Non_Broken packets to service
equipment B and service equipment C.
2.
After receiving the Non_Broken packets, service equipment B and service equipment C
restore their links to access node B and access node C and stop reporting
LPT_CFG_CLOSEPORT alarms.
Issue 03 (2012-11-30)

417
OptiX OSN 7500 II/7500/3500/1500

11 LPT
Non-Strict Point-to-Multipoint LPT Switching Against a Fault on an Access-Side

Access Node
l
Fault detection
Convergence side
Access side
Network side
Reports the link fault alarm.

node A and reports the
Access
node A
Broken
Service
equipment A
Service
equipment B
Service network
Access
node B
node C and reports the
Service
equipment C
Broken
Access
node C
1.
When detecting that the link connected to access node B is faulty, service equipment B
transmits Broken packets to service equipment A.
2.
After receiving the Broken packets, service equipment A disconnects its link from access
node A, reports the LPT_CFG_CLOSEPORT alarm, and sends Broken packets to service
equipment C.
3.
After receiving the Broken packets, service equipment C disconnects its link from access
node C and reports the LPT_CFG_CLOSEPORT alarm.
Fault recovery
Convergence side
Access side
Network side

fault alarm.
Restores the link
to access node A.
Access
node A
Service
equipment B
Non_Broken
Service
equipment A
Non_Broken
Service
network
Access
node B
access node C.
Service
equipment C
Access
node C
1.
After detecting that the link connecting to access node B has recovered, service equipment
B stops reporting the link fault alarm and transmits Non_Broken packets to service
equipment A.
2.
After receiving the Non_Broken packets, service equipment A restores its link from access
node A, stops reporting the LPT_CFG_CLOSEPORT alarm and transmits Non_Broken
packets to service equipment C.
3.
After receiving the Non-Broken packets, service equipment C restores its link to access
node C and stops reporting the LPT_CFG_CLOSEPORT alarm.
Issue 03 (2012-11-30)

418
OptiX OSN 7500 II/7500/3500/1500

11 LPT
Strict Point-to-Multipoint LPT Switching Against a Fault on an Access-Side Access

Node
l
Fault detection
Convergence side
Reports the link fault

alarm.

node A and reports the
Access
node A
Access side
Network side
Service
equipment B
Broken
Service
equipment A
Service
network
Access
node B
Reports the link fault

alarm.
Service
equipment C
Broken
Access
node C
1.
When detecting that the link connected to access node B is faulty, service equipment B
reports the link fault alarm and transmits Broken packets to service equipment A.
2.
When detecting that the link connected to access node C is faulty, service equipment C
reports the link fault alarm and transmits Broken packets to service equipment A.
3.
After receiving Broken packets from all other service equipment, service equipment A
disconnects its link from access node A and reports the LPT_CFG_CLOSEPORT alarm.
Fault recovery
Convergence side
Access side
Network side
Stops reporting the

link fault alarm.
Service
Access
Restores the
Non_Broken
equipment
B
node B
link to access
node A.
Access
Service
Service network
Stops reporting the
node A
equipment A
link fault alarm.
Non_Broken
Service
equipment C
Access
node C
1.
After detecting that the link connecting to access node B has recovered, service equipment
B stops reporting the link fault alarm and transmits Non_Broken packets to service
equipment A.
2.
After detecting that the link connecting to access node C has recovered, service equipment
C stops reporting the link fault alarm and transmits Non_Broken packets to service
equipment A.
3.
After receiving Non-Broken packets from all other service equipment, service equipment
A restores its link to access node A and stops reporting the LPT_CFG_CLOSEPORT alarm.
Non-Strict Point-to-Multipoint LPT Switching Against a Network-Side Fault

l
Issue 03 (2012-11-30)
Fault detection
419
OptiX OSN 7500 II/7500/3500/1500

11 LPT
1.
A bidirectional fault occurs on the service network between service equipment A and
service equipment B. As a result, service equipment A and service equipment B disconnect
their links from access node A and access node B and report LPT_CFG_CLOSEPORT
alarms. In addition, service equipment A transmits Broken packets to service equipment
C.
2.
After receiving the Broken packets, service equipment C disconnects its link from access
node C and reports the LPT_CFG_CLOSEPORT alarm.
NOTE
Fault recovery
1.
After detecting that the bidirectional fault on the service network has been rectified, service
equipment A and service equipment B restore their links to access node A and access node
B and stop reporting LPT_CFG_CLOSEPORT alarms. In addition, service equipment A
transmits Non-Broken packets to service equipment C.
2.
After receiving the Non-Broken packets, service equipment C restores its link to access
node C and stops reporting the LPT_CFG_CLOSEPORT alarm.
Strict Point-to-Multipoint LPT Switching Against a Network-Side Fault

l
Issue 03 (2012-11-30)
Fault detection
420
OptiX OSN 7500 II/7500/3500/1500

11 LPT
1.
service equipment B. As a result, service equipment B disconnects its link from access node
B and reports the LPT_CFG_CLOSEPORT alarm.
2.
service equipment C. As a result, service equipment C disconnects its link from access node
C and reports the LPT_CFG_CLOSEPORT alarm.
3.
After receiving Broken packets from all other service equipment, service equipment A
disconnects its link from access node A and reports the LPT_CFG_CLOSEPORT alarm.
NOTE
Fault recovery
1.
After the bidirectional fault on the service network between service equipment A and
service equipment B is rectified, service equipment B restores its link to access node B and
stops reporting the LPT_CFG_CLOSEPORT alarm.
2.
After the bidirectional fault on the service network between service equipment A and
service equipment C is rectified, service equipment C restores its link to access node C and
stops reporting the LPT_CFG_CLOSEPORT alarm.
3.
After receiving Non-Broken packets from all other service equipment, service equipment
A restores its link to access node A and stops reporting the LPT_CFG_CLOSEPORT alarm.
Issue 03 (2012-11-30)

421
OptiX OSN 7500 II/7500/3500/1500

11 LPT
11.8 Configuring LPT

This section describes how to configure point-to-point LPT and point-to-multipoint LPT.
NOTE

This section describes the procedures for configuring point-to-point LPT and for configuring
point-to-multipoint LPT.
Figure 11-3 shows the flowchart for configuring LPT.
Issue 03 (2012-11-30)

422
OptiX OSN 7500 II/7500/3500/1500

11 LPT
Figure 11-3 Flowchart for configuring LPT
Table 11-2 describes the procedures in the configuration flowchart.
Issue 03 (2012-11-30)

423
OptiX OSN 7500 II/7500/3500/1500

11 LPT
Table 11-2
Operation
11.8.2
Configuri
ng Pointto-Point
LPT
Description
Configure the
point-to-point
LPT detection
mechanism.
Required.
l The LPT OAM detection mechanism uses LPT protocol
packets to detect faults at a minimum interval of 1s.
l The PW OAM detection mechanism uses PW OAM
packets to detect faults at a minimum interval of 3.3 ms.
When using the minimum detection period of 3.3 ms, the PW
OAM detection mechanism supports faster LPT switching
but consumes more system resources than the LPT OAM
detection mechanism. Usually, the LPT OAM detection
mechanism (default value) is used. When the LPT OAM
detection mechanism cannot support a desired LPT
switching speed, the PW OAM detection mechanism is used.
NOTE
Service exclusively occupying a UNI port: One UNI port carries only
one service and the service is configured with no service VLAN ID
or VLAN ID configured for the port DCN function.
If a PW-carried E-Line service exclusively occupying a UNI port
has been configured, configure point-to-point LPT.
11.8.3
Configuri
ng PointtoMultipoin
t LPT
Configure the
primary and
secondary LPT
points.
Required.
If Primary Function Point Type is set to UNI, Secondary
Function Point Type can be set only to PW. If Primary
Function Point Type is set to PW, Secondary Function
Point Type can be set only to UNI.
NOTE
UNI-shared service: One UNI port carries one or more services and
services are differentiated by VLAN IDs.
If PW-carried Ethernet services sharing a UNI port have been
configured, configure point-to-multipoint LPT.
Configure the
switching mode
of point-tomultipoint LPT.
Issue 03 (2012-11-30)
Required.
If there are many secondary LPT points and these points carry
unimportant services, the strict LPT switching mode is
recommended to prevent a single point fault from triggering
switchover of the entire network. If there are only a few
secondary LPT points and these points carry important
services, the non-strict LPT switching mode is
recommended.

424
OptiX OSN 7500 II/7500/3500/1500

Operation
11 LPT
Description
Configure the
point-tomultipoint LPT
detection
mechanism.
Required.
l The LPT OAM detection mechanism uses LPT protocol
packets to detect faults at a minimum interval of 1s.
l The PW OAM detection mechanism uses PW OAM
packets to detect faults at a minimum interval of 3.3 ms.
When using the minimum detection period of 3.3 ms, the PW
OAM detection mechanism supports faster LPT switching
but consumes more system resources than the LPT OAM
detection mechanism. Usually, the LPT OAM detection
mechanism (default value) is used. When the LPT OAM
detection mechanism cannot support a desired LPT
switching speed, the PW OAM detection mechanism is used.
11.8.2 Configuring Point-to-Point LPT

When you configure point-to-point LPT, it is necessary to bind LPT to an UNI-NNI PW-carried
E-Line service.
Prerequisites
l
A PW-carried E-Line service exclusively occupying a UNI port has been created.
Procedure
Step 1 On the Main Topology, right-click the desired NE icon and choose NE Explorer from the
shortcut menu.
Step 2 In NE Explorer, select the desired NE from the Object Tree and choose Configuration > Packet
Configuration > LPT Management from the Function Tree.
Step 3 Click the Point-to-Point LPT tab.
Step 4 Select the desired E-Line service and click Bind.
Step 5 Set LPT Enabled to Enabled and click Apply.

----End
11.8.3 Configuring Point-to-Multipoint LPT

When you configure point-to-multipoint LPT, it is necessary to configure the primary and
secondary points.
Issue 03 (2012-11-30)

425
OptiX OSN 7500 II/7500/3500/1500

11 LPT
Prerequisites
l
PW-carried Ethernet services which each occupy partial timeslots of UNI ports have been
created.
Procedure
shortcut menu.
Step 3 Click the Point-to-Multipoint LPT tab.
Step 4 Click New. In the Create LPT dialog box that is displayed, set the desired parameters.
Step 5 Click OK.

Step 6 In Primary Function Point, set point-to-multipoint LPT attributes.
Issue 03 (2012-11-30)

426
OptiX OSN 7500 II/7500/3500/1500

11 LPT

----End
11.9 Maintaining LPT Configurations

This section describes how to query, change, and delete point-to-point and point-to-multipoint
LPT configurations.
11.9.1 Querying Point-to-Point LPT Configurations

This section describes how to query whether point-to-point LPT is bound to an E-Line service.
Prerequisites
l
Point-to-point LPT has been configured.
Procedure
shortcut menu.
Step 4 Click Query to learn whether point-to-point LPT is bound to an E-Line service.
----End
11.9.2 Changing Point-to-Point LPT Attributes

This section describes how to change point-to-point LPT attributes.
Prerequisites
l
Procedure
shortcut menu.
Issue 03 (2012-11-30)

427
OptiX OSN 7500 II/7500/3500/1500

11 LPT
Step 4 Select the desired point-to-point LPT and set LPT Enabled to Disabled.
Step 5 Change point-to-point LPT attributes.

----End
11.9.3 Deleting Point-to-Point LPT Configurations

This section describes how to unbind point-to-point LPT from an E-Line service.
Prerequisites
l
Procedure
shortcut menu.
Step 4 Select the desired point-to-point LPT and click Delete.
----End
11.9.4 Querying Point-to-Multipoint LPT Configurations

This section describes how to query whether point-to-multipoint LPT is bound to Ethernet
services.
Prerequisites
l
Point-to-multipoint LPT has been configured.
Procedure
shortcut menu.
Step 4 Click Query to learn whether point-to-multipoint LPT is bound to Ethernet services.
Issue 03 (2012-11-30)

428
OptiX OSN 7500 II/7500/3500/1500

11 LPT
----End
11.9.5 Changing Primary and Secondary Points for Point-toMultipoint LPT

This section describes how to change primary and secondary points accordingly when a bound
Ethernet service changes.
Prerequisites
l
Procedure
shortcut menu.
Step 4 Select the desired point-to-multipoint LPT and click Modify. In the dialog box that is displayed,
change primary and secondary points.
Issue 03 (2012-11-30)

429
OptiX OSN 7500 II/7500/3500/1500

11 LPT
NOTE
Changing the primary point or a secondary point transiently interrupts services.
Step 5 Click OK.

----End
11.9.6 Changing Point-to-Multipoint LPT Attributes

This section describes how to change point-to-multipoint LPT attributes.
Prerequisites
l
Procedure
shortcut menu.
Step 4 Select the desired point-to-multipoint LPT and set LPT Enabled to Disabled.
Issue 03 (2012-11-30)

430
OptiX OSN 7500 II/7500/3500/1500

11 LPT
Step 5 In Primary Function Point, change point-to-multipoint LPT attributes.
NOTE
l Recovery Time (s): Changing this parameter value does not interrupt services.
l Hold-Off Time (ms): Changing this parameter value does not interrupt services.
l Switching Mode: Changing this parameter value does not interrupt services.
l Fault Detection Mode: Changing this parameter value transiently interrupts services. Services will
not be restored until value changes are completed at both ends.
l Fault Detection Period (100 ms): Changing this parameter value does not interrupt services.

----End
11.9.7 Deleting Point-to-Multipoint LPT Configurations

This section describes how to unbind point-to-multipoint LPT from Ethernet services.
Prerequisites
l
Procedure
shortcut menu.
Step 4 Select the desired point-to-multipoint LPT and click Delete.
----End
11.10 Configuration Example (LPT Based on an E-Line

Service Exclusively Occupying a UNI Port)
This section uses an example to describe how to configure LPT based on an E-Line service
exclusively occupying a UNI port.
NOTE
Issue 03 (2012-11-30)

431
OptiX OSN 7500 II/7500/3500/1500

11 LPT

This section describes an LPT configuration example based on an E-Line service exclusively
occupying a UNI port.
As shown in Figure 11-4, an E-Line service exclusively occupying a UNI port is configured
between NE1 and NE2. This service needs to be protected against the following faults:
l
Faults on the access side (the link between the NodeB and NE1 and the link between the
RNC and NE2)
Faults on the network side (the service network between NE1 and NE2)
Figure 11-4 Network diagram for LPT based on an E-Line service exclusively occupying a UNI
port
Backup
Network
PSN
PW
NodeB
NE1
NE2
RNC
Solution
Link aggregation group (LAG) can provide protection against faults on the access side. MPLS
tunnel APS can provide protection against faults on the network side. Neither LAG nor MPLS
tunnel APS, however, can provide protection against faults on both the access side and the
network side. To protect services against faults on both the access side and the network side,
you can configure LPT based on an E-Line service exclusively occupying a UNI port.
Service Planning
The LPT parameters for NE1 and NE2 are planned as follows.
Issue 03 (2012-11-30)

432
OptiX OSN 7500 II/7500/3500/1500

11 LPT
Parameter
Value
Recovery Time (s)
1 (default value)
Hold-Off Time (ms)
Fault Detection Mode
LPT OAM
Fault Detection Period (100 ms)
10 (default value)
LPT Enabled
Enabled

This section describes how to configure LPT based on an E-Line service exclusively occupying
a UNI port.
Prerequisites
l
You are familiar with the service requirements and planning information.
Procedure
Step 1 Follow instructions in 11.8.2 Configuring Point-to-Point LPT to configure point-to-point LPT
on NE1 and NE2.
Parameter
Value
Recovery Time (s)
1 (default value)
Hold-Off Time (ms)
LPT OAM
10 (default value)
LPT Enabled
Enabled
Step 2 Follow instructions in 11.9.1 Querying Point-to-Point LPT Configurations to query the pointto-point LPT configurations on NE1 and NE2.
----End
11.11 Configuration Example (LPT Based on Ethernet

Services Sharing a UNI Port)
This section uses an example to describe how to configure LPT based on Ethernet services
sharing a UNI port.
Issue 03 (2012-11-30)

433
OptiX OSN 7500 II/7500/3500/1500

11 LPT
NOTE

This section describes an LPT configuration example based on Ethernet services sharing a UNI
port.
As shown in Figure 11-5, an Ethernet service sharing a UNI port is configured between NodeB
1 and the RNC and another is configured between NodeB 2 and the RNC. The services need to
be protected against the following faults:
l
Faults on the access side (the link between NodeB1 and NE1, the link between NodeB2
and NE2, and the link between the RNC and NE3)
Faults on the network side (the service network between NE1 and NE3 and the service
network between NE2 and NE3)
Figure 11-5 Network diagram for LPT based on Ethernet services sharing a UNI port
Backup Network
VLAN:
100
NodeB1
PSN
NE1
NodeB2
PW
VLAN:
100,200
VLAN:200
NE3
RNC
NE2
Solution
Link aggregation group (LAG) can be configured to provide protection against faults on the
access side. MPLS tunnel APS can be configured to provide protection against faults on the
Issue 03 (2012-11-30)

434
OptiX OSN 7500 II/7500/3500/1500

11 LPT
network side. Neither LAG nor MPLS tunnel APS, however, can provide protection against
faults on both the access side and the network side. To protect services against faults on both
the access side and the network side, you can configure LPT based on Ethernet services sharing
a UNI port.
Service Planning
The LPT parameters for NE1, NE2, and NE3 are planned as follows.
Parameter
NE1
NE2
NE3
Primary
Function Point
Point Type
UNI
UNI
UNI
Port
21-PETF8-1
21-PETF8-1
2-PEG8-1
Second
Function Point 1
Point Type
PW
PW
PW
Port
PW ID: 101
PW ID: 102
PW ID: 101
Second
Function Point 2
Point Type
PW
Port
PW ID: 102
Recovery Time (s)
1 (default value)
Hold-Off Time (ms)
Switching Mode
Strict Mode
LPT OAM
10 (default value)
LPT Enabled
Enabled

This section describes how to configure LPT based on Ethernet services sharing a UNI port.
Prerequisites
l
You are familiar with the service requirements and planning information.
Procedure
Step 1 Follow instructions in 11.8.3 Configuring Point-to-Multipoint LPT to configure point-tomultipoint LPT on NE1, NE2, and NE3.
Parameter
Primary
Function Point
Issue 03 (2012-11-30)
NE1
NE2
NE3
Point Type
UNI
UNI
UNI
Port
21-PETF8-1
21-PETF8-1
2-PEG8-1

435
OptiX OSN 7500 II/7500/3500/1500

Parameter
11 LPT
NE1
NE2
NE3
Second
Function Point 1
Point Type
PW
PW
PW
Port
PW ID: 101
PW ID: 102
PW ID: 101
Second
Function Point 2
Point Type
PW
Port
PW ID: 102
Recovery Time (s)
1 (default value)
Hold-Off Time (ms)
Switching Mode
Strict Mode
LPT OAM
10 (default value)
LPT Enabled
Enabled
Step 2 Follow instructions in 11.9.4 Querying Point-to-Multipoint LPT Configurations to query

point-to-multipoint LPT configurations on NE1, NE2, and NE3.
----End
11.12 Verifying LPT

To check whether the LPT is configured successfully, simulate the fault on the link where the
access node is involved and query the reported alarm.
Prerequisites
l
The Ethernet services carried by PWs must be configured.
The LPT function must be enabled for the transmission equipment at the local and opposite
ends.
NOTE
The following example illustrates the verification on point-to-multipoint LPT. Point-to-point LPT is
verified in a similar way.
As shown in Figure 11-6, disconnect the UNI-side link between the RNC and NE1, and the
NNI-side links between NE1 and NE2 and between NE1 and NE3. Check whether the
communication between the RNC and the NodeBs is in normal status. By using this method,
you can verify whether the LPT function is successfully configured.
Issue 03 (2012-11-30)

436
OptiX OSN 7500 II/7500/3500/1500

11 LPT
Figure 11-6 Networking diagram of point-to-multipoint LPT
NNI-side link
NodeB 1
PW
UNI-side link
NE 2
PSN
PW
NodeB 2
NE 1
RNC
NE 3
Backup network
NodeB 3
Procedure
Step 1 On the Main Topology, right-click the icon of the required NE and then choose NE Explorer
Step 2 In the NE Explorer, select the required NE from the Object Tree and then choose
Configuration > Packet Configuration > LPT Management from the Function Tree.
Step 3 Click the Point-to-Multipoint LPT tab. In the lower right corner, click Query. Check whether
the attributes of the primary function point and the secondary function point are correctly set.
Step 4 Disconnect the UNI-side link between the RNC and NE1.
Step 5 Query the alarm list of NE2 and NE3. If the LPT_CLOSE_PORT alarm is reported and the RNC
communicates normally with the NodeBs, you can infer that the LPT switching is successful.
Step 6 Disconnect the NNI-side links between NE1 and NE2 and between NE1 and NE3.
Step 7 Query the alarm list of NE1, NE2, and NE3. If the LPT_CLOSE_PORT alarm is reported and
the RNC communicates normally with the NodeBs, you can infer that the LPT switching is
successful.
----End
Issue 03 (2012-11-30)

437
OptiX OSN 7500 II/7500/3500/1500

11 LPT
To locate and rectify the common faults in a timely manner, you need to get familiar with the
fault symptoms and the troubleshooting flow. This topic describes how to handle common LPT
faults by using point-to-multipoint LPT as an example.
Symptom
In the case of the point-to-multipoint LPT networking as shown in Figure 11-7, the common
fault symptom is as follows: When the link or network between the RNC and the NodeBs
becomes faulty, services between the RNC and the NodeBs cannot be switched to the backup
network.
Figure 11-7 Networking diagram of point-to-multipoint LPT
NNI-side link
NodeB 1
PW
UNI-side link
NE 2
PSN
PW
NodeB 2
NE 1
RNC
NE 3
Backup network
NodeB 3
Possible Causes
l
The LPT function is disabled.
NEs on the entire network do not adopt the same switching mode. (In this example, all the
NEs are assumed to adopt the strict mode.)
The primary function point and the secondary function point are not correctly set.
Issue 03 (2012-11-30)

438
OptiX OSN 7500 II/7500/3500/1500

11 LPT
Procedure
Step 1 On the Main Topology, right-click the NE1 icon and then choose NE Explorer from the shortcut
menu.
Step 2 In the NE Explorer, select NE1 and then choose Configuration > Packet Configuration > LPT
Step 3 Click the Point-to-Multipoint LPT tab, and then clink Query.
1.
Check the value of LPT Enabled. If it is set to Disabled, set it to Enabled.
2.
Check the value of Switching Mode. If it is set to Non-strict Mode, set it to Strict
Mode.
3.
Check the value of Point Type for the primary function point. If it is set to PW, reconfigure
the point-to-multipoint LPT and set Point Type of the primary function point to UNI.
Step 4 Repeat Steps 1 to 3 to check whether the configurations of NE2 and NE3 are correct.
NOTE
Point Type of the primary function point for NE2 and NE3 must be set to PW. If Point Type is set to
UNI, reconfigure the point-to-multipoint LPT.
Step 5 If the fault persists, contact Huawei technical support engineers to rectify the fault.
----End

This section describes the alarms and performance events that are associated with the LPT
feature.

This section describes the alarms that are associated with the LPT feature.
Alarm
Description
LPT_CFG_CLOSEPORT
The LPT_CFG_CLOSEPORT alarm

indicates that LPT shuts down a local service
port. In the packet domain, when detecting
that the remote access-side port fails or the
LPT service network fails, LPT shuts down
the local access-side port and reports the

There are no performance events that are related to the LPT feature.
Issue 03 (2012-11-30)

439
OptiX OSN 7500 II/7500/3500/1500

11 LPT

This section describes parameters for configuring point-to-point LPT and for configuring pointto-multipoint LPT.
11.15.1 LPT Management_Point-to-Point LPT

This section describes parameters for configuring point-to-point LPT.
Paramet
er
Value Range
Description
Binding
Status
Unbound, Bound
This parameter displays whether point-to-point LPT

is bound to a service.
Default value: Unbound
NOTE
Before binding point-to-point LPT to a service, ensure that
the service has been configured. The default parameter
value is Unbound.
Primary
Function
Point
Slot number-board name
Second
Function
Point
Type
PW, UNI
This parameter displays the board where the primary

LPT point is located.
The primary LPT point is the entity that runs the LPT
protocol. It determines the LPT state based on the
running information at each LPT point.
Default value: PW
This parameter displays the port type of a secondary

point.
Value description:
l PW: A secondary LPT point is a PW on the
network side.
l UNI: A secondary LPT point is a UNI port.
Second
Function
Point
Issue 03 (2012-11-30)

This parameter displays the board where a secondary

A secondary point detects and transfers LPT port
status changes, such as changes in the local port status
and changes in the remote point status.

440
OptiX OSN 7500 II/7500/3500/1500

11 LPT
Paramet
er
Value Range
Description
LPT
Status
Initial, Normal, Fault at

access side, Fault on
service network,
Waiting for fault
recovery, Recovering
from fault
This parameter displays the current LPT state.

Value description:
l Initial: The LPT have not received LPT protocol
packets.
l Normal: The LPT protocol is functional.
l Fault at access side: A port fault or link fault
occurs on the access side.
l Fault on service network: A port fault or link
fault occurs on the network side.
l Waiting for fault recovery: LPT changes from
the network-side faulty state to the WTR state
once the LPT protocol components detect that the
network-side faults have been rectified. LPT
changes from the access-side faulty state to the
WTR state once the LPT protocol components
detect that the access-side faults have been
rectified.
l Recovering from fault: LPT changes from the
WTR state to a faulty recovery state once the LPT
protocol components detect that access-side faults
have been rectified. LPT changes from the fault
recovery state to a normal state once the LPT
protocol components detect that all access-side
and network-side faults have been rectified.
LPT
Enabled
Enabled, Disabled
Default value: Disabled
This parameter displays whether the LPT function is

enabled.
Value description:
l Enabled: The LPT function is enabled.
l Disabled: The LPT function is disabled.
Recovery
Time (s)
1 to 600
Default value: 1
This parameter specifies the time to wait before

services are switched from a backup network back to
a service network. An appropriate value of this
parameter prevents possible network status changes
from resulting in frequent switchovers between a
service network and a backup network.
Recommendations:
Issue 03 (2012-11-30)

441
OptiX OSN 7500 II/7500/3500/1500

11 LPT
Paramet
er
Value Range
Description
Hold-Off
Time
(ms)
0 to 10000
This parameter specifies or displays the hold-off time

for LPT switching.
Default value: 1000
Specifically, if LPT switching is triggered, the local

end instructs the opposite end to perform LPT
switching after the hold-off time elapses.
Recommendations:
It is recommended that you set this parameter to
1000.
Switchin
g Mode
Strict Mode, Non-strict

Mode
This parameter specifies the LPT switching mode.
Default value: Strict

Mode
l Strict Mode: A primary point triggers LPT

switching when all of its secondary points detect
faults.
Value description:
l Non-strict Mode: A primary point triggers LPT

switching when one of its secondary points detects
a fault.
NOTE
This parameter is available only to point-to-multipoint LPT.
Recommendations:
If there are many secondary LPT points and these
points do not carry important services, the strict LPT
switching mode is recommended to prevent a single
node fault from switching the entire network. If there
are only a few secondary LPT points and these points
carry important services, the non-strict LPT
switching mode is recommended.
Issue 03 (2012-11-30)

442
OptiX OSN 7500 II/7500/3500/1500

11 LPT
Paramet
er
Value Range
Description
Fault
Detection
Mode
LPT OAM, PW OAM
This parameter specifies the LPT fault detection

mechanism.
Default value: LPT

OAM
Value description:
l LPT OAM: The LPT protocol components
exchange LPT protocol packets between LPT NEs
on a service network and determine the status of
the LPT links between the NEs based on the
negotiation result.
l PW OAM: The LPT protocol components
exchange LPT protocol packets between LPT NEs
on a service network and determine the status of
the LPT links between the NEs based on the
negotiation result and the statuses of PWs carried
on the LPT links. If negotiation using LPT packets
fails or PWs are faulty, the LPT protocol
components consider that the LPT links are faulty.
The LPT protocol components consider that LPT
links are working properly only when negotiation
using LPT packets is successful and PWs are
functional.
Recommendations:
The LPT OAM detection mechanism uses LPT
protocol packets to detect faults at a minimum
interval of 1s. The PW OAM detection mechanism
detects faults based on PW OAM and at a minimum
interval of 3.3 ms. When using the minimum
detection period of 3.3 ms, the PW OAM detection
mechanism supports faster LPT switching but
consumes more system resources than the LPT OAM
detection mechanism.
Fault
Detection
Period
(100 ms)
3 to 100
UserSide Port
Status
CLOSE, OPEN
Default value: 10
This parameter specifies or displays the LPT fault

detection period.
Recommendations:
Default value: OPEN
This parameter displays whether the laser of an LPTenabled port is on or off.

Value description:
l OPEN: The laser of the LPT-enabled port is on.
l CLOSE: The laser of the LPT-enabled port is off.
NOTE
When the LPT protocol is functional, the parameter value
is OPEN. If a fault occurs on the network side, the laser over
the local LPT-enabled port is shut down and the parameter
value is CLOSE.
Issue 03 (2012-11-30)

443
OptiX OSN 7500 II/7500/3500/1500

11 LPT
11.15.2 LPT Management_Point-to-Multipoint LPT

This section describes parameters for configuring point-to-multipoint LPT.
Paramet
er
Value Range
Description
Primary
Function
Point
Type
UNI, PW
This parameter displays the port type of a primary

LPT point.
Default value: UNI
The primary LPT point is the entity that runs the LPT
protocol. It determines the LPT state based on the
running information at each LPT point.
In point-to-multipoint LPT configuration, there are
one primary point and several secondary points,
which correspond to the root node and leaf nodes in
a networking topology.
Value description:
l UNI: A primary LPT point is a UNI port.
l PW: A primary LPT point is a PW on the network
side.
Primary
Function
Point
Board
Slot number-board
Primary
Function
Point
Port
Slot number-board
name-port number
Primary
Function
Point
Type
PW, UNI
For example, 3N1PEG8-1 (PORT1)
Default value: PW
If Primary Function Point Type is set to UNI, this

parameter displays the board where the primary LPT
point is located.
If Primary Function Point Type is set to UNI, this
parameter displays the LPT-enabled port on the board
where the primary LPT point is located.

LPT point.
Value description:
network side.
Primary
Function
Point ID
Issue 03 (2012-11-30)
If Primary Function Point Type is set to PW, this

parameter displays the ID of the primary LPT point.

444
OptiX OSN 7500 II/7500/3500/1500

11 LPT
Paramet
er
Value Range
Description
Second
Function
Point
Type
UNI, PW

LPT point.
Default value: UNI
A secondary point detects and transfers LPT port

status changes, such as changes in the local port status
and changes in the remote point status.
In point-to-multipoint LPT configuration, there are
one primary point and several secondary points,
which correspond to the root node and leaf nodes in
a networking topology.
Value description:
network side.
Second
Function
Point
Board

This parameter displays the board where a secondary

NOTE
For other parameters, see 11.15.1 LPT Management_Point-to-Point LPT.
Issue 03 (2012-11-30)

445
OptiX OSN 7500 II/7500/3500/1500

12 MC-LAG
12
MC-LAG
About This Chapter

Multi-chassis link aggregation group (MC-LAG) is a supplement to the single-chassis link
aggregation group (SC-LAG) and allows aggregation of inter-chassis links. On a 3G bearer
network, MC-LAG can work with PW APS to implement dual-homing of E-Line or E-LAN
services when a dual-homed node becomes faulty or an AC-side link or NNI-side service fails.
12.1 Introduction
MC-LAG allows aggregating links of multiple NEs into one link aggregation group (LAG).
When a link or an NE fails, MC-LAG automatically switches the services to another available
link in the same LAG.
12.2 Basic Concepts
Learning about the basic concepts helps to further understand the MC-LAG feature.
12.3 Specifications
This section describes the capacity of the OptiX OSN equipment for supporting MC-LAG.
This topic describes the standards and protocols that MC-LAG complies with.
12.5 Availability
The MC-LAG function requires the support of the applicable equipment and boards.
This section describes the limitations on and precautions for multi-chassis link aggregation group
(MC-LAG) in the network design phase, configuration and commissioning phase, and
maintenance phase.
12.7 Principles
This section describes the principles for creating MC-LAGs and for performing the MC-LAG
protection switching using the MC-LAG implementation model.
12.8 Configuring MC-LAG
Configure MC-LAG on the dual-homed nodes that are connected to the RNC to implement dualhoming of E-Line services.
Issue 03 (2012-11-30)

446
OptiX OSN 7500 II/7500/3500/1500

12 MC-LAG
An MC-LAG can work with PW APS on the NNI side to implement dual-homing of E-Line
services. This topic describes how to configure an MC-LAG in a dual-homing scenario wherein
AC-side links transmit data.
This topic describes the alarms and performance events that are related to the MC-LAG.
12.11 Parameter Description: MC-LAG
This topic describes the parameters required for configuring MC-LAG.
Issue 03 (2012-11-30)

447
OptiX OSN 7500 II/7500/3500/1500

12 MC-LAG
12.1 Introduction
MC-LAG allows aggregating links of multiple NEs into one link aggregation group (LAG).
When a link or an NE fails, MC-LAG automatically switches the services to another available
link in the same LAG.
Definition
By means of the MC-LAG control protocol, MC-LAG allows aggregating multiple inter-chassis
data links that are connected to the same device to provide a more reliable connection.
Application
As shown in Figure 12-1, services from the NodeB are transmitted to the RNC over the PSN;
NE1 and NE2 work with the RNC to provide MC-LAG protection for services.
Figure 12-1 MC-LAG application in dual-homing
AC side
NNI side
NE1
LAG1
NE3
PW APS
A
PSN
RNC
MC-LAG
NodeB
S
LAG3
LAG2
NE2
Multi-chassis synchronous
communication
A
S
Active (carrying services)

Standby (not carrying services)
An MC-LAG consists of three parts:

l
Single-chassis (SC) LAGs on NE1 and NE2, that is, LAG1 and LAG2
An MC-LAG between NE1 and NE2
A LAG on the RNC, that is, LAG3
NE1 and NE2 communicate with each other by means of the inter-chassis synchronous
communication tunnel. Specifically, the two dual-homed NEs periodically exchange
information about the status of LAG1 and LAG2 and negotiate the active/standby status of LAG1
and LAG2 according to the fault.
Issue 03 (2012-11-30)

448
OptiX OSN 7500 II/7500/3500/1500

12 MC-LAG
Purpose
On a 3G bearer network, a fault on the AC link that connects the convergence NE and the RNC
can interrupt all the services from the NodeBs connected to the RNC. To solve this problem, a
more reliable connection between the convergence NE and the RNC is required. In actual
application, the RNC can be connected to two convergence NEs and configuration of MC-LAG
enables mutual backup of the two LAGs configured on the two convergence NEs for a highly
reliable connection.
12.2 Basic Concepts

Learning about the basic concepts helps to further understand the MC-LAG feature.
Link Aggregation Control Protocol (LACP)

Developed based on IEEE 802.3ad, the LACP protocol performs the following functions:
l
The LACP protocol provides the data switching equipment with a standard negotiation
mode to form an aggregation link. After the LACP protocol is enabled, the system
automatically aggregates multiple links according to its configuration and enables the
aggregation link to transmit and receive data.
The LACP protocol helps to maintain the status of the aggregation link after the aggregation
link is formed. When aggregation conditions change, the LACP protocol automatically
adjusts or releases the aggregation link.
LAG
A LAG allows aggregating multiple links that are attached to the same equipment to increase
bandwidth and availability of links. The aggregated links can be considered as a single logical
link.
A LAG aggregates multiple physical links to form a logical link at a higher rate. Link aggregation
functions between adjacent equipment and is independent of the network topology. Link
aggregation is also called port aggregation because one link corresponds to one port in Ethernet
transmission.
Load Sharing Modes

NOTE
MC-LAG does not support load sharing between two NEs.

Any load sharing mode mentioned in the MC-LAG feature is applicable to the SC-LAG only.
A LAG supports the following load sharing modes:

l
Loading sharing
Each member link in a LAG carries traffic. That is, the member links in the LAG share the
load. In the load sharing mode, the link bandwidth is increased. When a member in a LAG
changes or when a certain link fails, the traffic is re-allocated automatically.
Load non-sharing
Only one member link in a LAG carries traffic, and the other links in the LAG are in the
standby state. This is equivalent to a hot standby mechanism. That is, when the active link
Issue 03 (2012-11-30)

449
OptiX OSN 7500 II/7500/3500/1500

12 MC-LAG
in a LAG fails, the system chooses a link from the standby links in the LAG, and the chosen
link replaces the failed link. In this manner, the link failure does not affect services.
12.3 Specifications
This section describes the capacity of the OptiX OSN equipment for supporting MC-LAG.
Table 12-1 provides specifications associated with MC-LAG.
Table 12-1 Specifications associated with MC-LAG
Item
Specifications
Support capability
64
Load Sharing Mode
Load non-sharing
Revertive Mode
Revertive
Non-revertive
Switching Protocol
LACP protocol
Switching time
l The links of the interconnected equipment are directly

connected to each other, and the fiber is cut in both
directions. Switching time 500 ms.
connected to each other, and the fiber is cut in one
direction. In addition, the ports of the interconnected
equipment are set to the auto-negotiation mode. Switching
time 500 ms.
connected to each other, and the fiber is cut in one
direction. Switching time 3s.
Switching condition (Any

of the conditions triggers
the switching.)
l Manual aggregation:
The port working mode changes.
l Static aggregation:
The port working mode changes.
The port priority changes.
The system priority changes.

This topic describes the standards and protocols that MC-LAG complies with.
MC-LAG complies with the following standards and protocols:
Issue 03 (2012-11-30)

450
OptiX OSN 7500 II/7500/3500/1500

12 MC-LAG
IEEE 802.3ad Carrier sense multiple access with collision detection (CSMA/CD) access
method and physical layer specifications
12.5 Availability
The MC-LAG function requires the support of the applicable equipment and boards.
Version Support
Product Name
Applicable Version
OptiX OSN 3500/7500
U2000
Product Name
Applicable Version
OptiX OSN 7500 II
U2000
Hardware Support
Issue 03 (2012-11-30)
Board Type
Version
N2PEX1
OptiX OSN 3500/7500
N1PEX2
OptiX OSN 3500/7500
N1PEG8
OptiX OSN 3500/7500
N1PETF8
OptiX OSN 3500/7500
N1PEFF8
OptiX OSN 3500/7500
N1EDQ41
OptiX OSN 3500/7500
TNN1EX2
OptiX OSN 7500 II
TNN1EG8
OptiX OSN 7500 II
TNN1ETMC
OptiX OSN 7500 II
TNN1EFF8
OptiX OSN 7500 II

451
OptiX OSN 7500 II/7500/3500/1500

12 MC-LAG

This section describes the limitations on and precautions for multi-chassis link aggregation group
(MC-LAG) in the network design phase, configuration and commissioning phase, and
maintenance phase.
Issue 03 (2012-11-30)
Applicable
Object

Details
Remarks
MC-LAG
Configure MC-LAGs on two NEs.

Make sure that LAGs on the two
NEs work in the same mode: manual
mode or static mode.
MC-LAG and
SNCP
If MC-LAGs and SNCP coexist, set

working ports of SNCP and LAGs
on the same link in the initial
configuration phase; set UNEQ as a
trigger condition for SNCP
switching; set the hold-off time of
SNCP to 0s. In addition, if both MCLAG and SNCP work properly,
SNCP switching commands and
adding/deletion of an SNCP
protection group are not supported.
Load sharing
mode
MC-LAGs support load nonsharing.
Multi-chassis
Synchronizati
on Protocol
(MCSP)
channel
MCSP channels must be configured

for MC-LAGs. The MCSP channels
must be carried by bidirectional
tunnels. The hello time of MCSP
tunnels is 1s by default. The MCSP
timeout time is 10 minutes by
default. It is recommended that the
hello time and MCSP timeout time
take their default values. Otherwise,
services may be interrupted for
scores of seconds in the case of
active/standby switching of SCC
boards.
MCSP channel
A directly connected physical link is

required between two NEs to carry
the MCSP channels.
MCSP channel
The port where MCSP channels

reside must be a Layer 3 port.

452
OptiX OSN 7500 II/7500/3500/1500

12 MC-LAG
Applicable
Object

Details
Remarks
MCSP channel
If protection for an MCSP channel

is required, tunnel APS is
recommended for the tunnel that
carries the MCSP channel.
MCSP channel
Multiple MC-LAGs can share one

MCSP channel.

None.
None.
12.7 Principles
This section describes the principles for creating MC-LAGs and for performing the MC-LAG
protection switching using the MC-LAG implementation model.
Implementation Model
The MC-LAG supports only the non-load sharing mode and enables active/standby protection
for Ethernet links. Figure 12-2 shows the MC-LAG implementation model.
Figure 12-2 MC-LAG implementation model
NE1
LAG1
Active
LAG3
MCSP
Router
Standby
LAG2
NE2
Issue 03 (2012-11-30)

453
OptiX OSN 7500 II/7500/3500/1500

12 MC-LAG
LAGs on devices must:

Support both load sharing and non-load sharing modes. LAG1 and LAG2 must work
in the same mode.
Support both manual and static aggregation modes. LAG1, LAG2, and LAG3 must use
the same aggregation mode.
The Multi-chassis Synchronization Protocol (MCSP) must:

Be configured at NE1 and NE2 to create a channel for exchanging MC-LAG packets
and LAG information, ensuring fast MC-LAG switching.
Be configured with link protection such as LAG or ERPS protection to improve MCLAG reliability. If no link protection is configured for the MCSP, the MC-LAG will
fail and the MC-LAG active/standby protection will be invalid when the MCSP is
interrupted. When this occurs, NE1 and NE2 separately negotiate their working modes
with the router and work independently based on the negotiation results. In other words,
NE1 and NE2 will work in common LAG mode. To improve MC-LAG reliability, you
are advised to provide link protection such as LAG protection for the MCSP.
The MC-LAG must:

Support both revertive and non-revertive restoration modes after a fault on the active
connection is rectified. In addition, the MC-LAG and LAG3 must have the same restoration
mode.
Creating MC-LAGs
l
Creating MC-LAGs in static aggregation mode

The local MC-LAG compares the local LAG information with the peer LAG information
by exchanging MC-LAG packets with the peer MC-LAG to select the link for carrying
services. The selection process is as follows:
If the system IDs (system priority + device MAC address) of both LAG1 and LAG2 are
larger than that of LAG3, LAG3 conducts common LAG negotiation and the MC-LAG
function does not take effect.
If the system ID of either LAG1 or LAG2 is smaller than that of LAG3, MC-LAG
performs the following processing:
1.
Compares the total bandwidth of LAG1 and that of LAG2 and allocates the smaller
system ID between the system IDs of LAG1 and LAG2 to the LAG with a larger
bandwidth. By doing so, the LAG with a larger bandwidth functions as active and
the LAG with a smaller bandwidth functions as standby.
2.
Compares the system IDs of LAG1 and LAG2 if LAG1 and LAG2 have the same
total bandwidth. The LAG with a smaller system ID functions as active and the
LAG with a larger system ID functions as standby.
3.
The selected LAG determines the specific member links for carrying services
based on the priorities of its member ports and port status, and the negotiation
results with LAG3.
Creating MC-LAGs in manual aggregation mode

NOTE
In manual aggregation mode, only one member link can be configured for each LAG on the devices.
In manual aggregation mode, LAG3 cannot communicate with LAG1 or LAG2. The MC-LAG
selects the working link based on the LAG configurations on each device. Therefore, when
configuring LAG1, LAG2, and LAG3 that is separately interconnected with LAG1 and LAG2, ensure
that two interconnected LAGs select the same link to carry services.
Issue 03 (2012-11-30)

454
OptiX OSN 7500 II/7500/3500/1500

12 MC-LAG
The local MC-LAG compares the local LAG information with the peer LAG information
by exchanging MC-LAG packets with the peer MC-LAG as follows:
Compares the total bandwidth of LAG1 and that of LAG2. Ports in the LAG with a
larger bandwidth function as working and ports in the LAG with a smaller bandwidth
function as standby.
Compares the device MAC addresses if LAG1 and LAG2 have the same total
bandwidth. Ports in the LAG with a smaller MAC address function as working and ports
in the LAG with a larger MAC address function as standby.
Performing MC-LAG Switching

After MC-LAGs are created, the active connection (LAG1 for example) carries Ethernet services
and the standby connection (LAG2) does not. The local MC-LAG exchanges the status of LAG1
and LAG2 with the peer MC-LAG using MCSP packets. When LAG1 is faulty, the MA-LAG
asks NE1 and NE2 to switch services to LAG2 using MC-LAG packets. The specific process is
as follows:
l
When the LAGs on the devices work in load sharing mode:

In case of a link fault in LAG1, the MC-LAG determines whether to perform switching by
comparing the current working bandwidths of LAG1 and LAG2.
If the current working bandwidth of LAG1 is larger than that of LAG2, the MC-LAG
does not perform switching and keeps using LAG1 to forward Ethernet services.
If the current working bandwidth of LAG1 is smaller than that of LAG2, the MC-LAG
exchanges the smaller system ID between the system IDs of LAG1 and LAG2 to LAG2
to trigger MC-LAG switching and switches Ethernet services to LAG2 for forwarding.
After the link fault in LAG1 is removed, the MC-LAG determines whether to restore
LAG1 as the active connection based on the following conditions:
If the working bandwidth of LAG1 is larger than that of LAG2, the MC-LAG triggers
MC-LAG switching and restores LAG1 as the active connection.
If LAG1 has the same working bandwidth as LAG2, the MC-LAG determines
whether to restore LAG1 as the active connection based on the reversion mode
configured for LAG1.
When the LAGs on the devices work in non-load sharing mode:

Because only one link is configured for each LAG, the MC-LAG performs switching when
LAG1 is faulty.
After the link fault in LAG1 is removed, the MC-LAG determines whether to restore LAG1
as the active connection based on the following conditions:
If the working bandwidth of LAG1 is larger than that of LAG2, the MC-LAG triggers
MC-LAG switching and restores LAG1 as the active connection.
If LAG1 has the same working bandwidth as LAG2, the MC-LAG determines whether
to restore LAG1 as the active connection based on the reversion mode configured for
LAG1.
During MC-LAG switching, Ethernet services are switched to the standby connection for
forwarding.
Issue 03 (2012-11-30)

455
OptiX OSN 7500 II/7500/3500/1500

12 MC-LAG
12.8 Configuring MC-LAG

Configure MC-LAG on the dual-homed nodes that are connected to the RNC to implement dualhoming of E-Line services.
l
Before configuring MC-LAG, you must configure SC-LAGs on the dual-homed nodes.
Loading Sharing of the LAGs on the dual-homed nodes must be set to the same.
LAG Type of the LAGs on the dual-homed nodes and the RNC must be set to the same.
Revertive Mode of the MC-LAG on the dual-homed nodes must be set to the same.
It is recommended that you configure a static LAG, because it has a higher reliability.
Timeout Time of one dual-homed node must be greater than Hello Packet Sending
Interval of the other node. Generally, the two parameters on the two dual-homed nodes
are set to the same values.
On the dual-homed nodes, the tunnel in which the multi-chassis synchronization protocol
is run must be in the bidirectional tunnel that carries the multi-chassis synchronous
communication information.
12.8.1 Configuring Multi-chassis Synchronous Communication

Tunnel
The dual-homed nodes learn the working status of the peer links on the AC side and negotiate
the troubleshooting actions by means of multi-chassis synchronous communication. Before
configuring an MC-LAG, you must configure the opposite information for multi-chassis
synchronous communication on the dual-homed nodes.
Prerequisites
l
A bidirectional tunnel must be configured between the dual-homed nodes for multi-chassis
synchronous communication.
Procedure
Configuration > Synchronization Protocol Management from the Function Tree.
Step 2 Click New. In the Create Cross-Equipment Synchronization Protocol dialog box that is
displayed, set the parameters of multi-chassis synchronous communication.
Issue 03 (2012-11-30)

456
OptiX OSN 7500 II/7500/3500/1500

12 MC-LAG
NOTE
Select Automatically Assign to automatically assign Protocol Channel ID.
Step 3 Click OK. The Operation Result dialog box is displayed, indicating that the operation is
successful.
Step 4 In the Operation Result dialog box that is displayed, click Close.
Step 5 Perform Step 1 to Step 4 to set multi-chassis synchronous communication parameters on the
other dual-homed node.
----End
12.8.2 Configuring MC-LAGs

Configure an MC-LAG on the dual-homed nodes that are connected to the RNC to implement
dual-homing of E-Line services. This topic describes how to configure an MC-LAG.
Prerequisites
l
The multi-chassis synchronous communication must be configured.
The LAGs must be configured on the dual-homed nodes that are connected to the RNC.
The dual-homed NEs must house active/standby SCC boards.
Procedure
Step 1 In the NE Explorer, select the required NE, and choose Configuration > Packet
Function Tree.
Step 2 Click the Cross-Equipment Link Aggregation Groups tab.
Step 3 Click New. In the Create Cross-Equipment Link Aggregation Group dialog box that is
displayed, set the parameters of the MC-LAG.
Step 4 Click OK. The Operation Result dialog box is displayed, indicating that the operation is
successful.
Step 5 In the Operation Result dialog box, click Close.
Step 6 Perform Step 1 to Step 5 to set the MC-LAG parameters on the other dual-homed node.
----End
Issue 03 (2012-11-30)

457
OptiX OSN 7500 II/7500/3500/1500

12 MC-LAG

An MC-LAG can work with PW APS on the NNI side to implement dual-homing of E-Line
services. This topic describes how to configure an MC-LAG in a dual-homing scenario wherein
AC-side links transmit data.

This topic describes the function requirements, networking diagram, and service planning.
Requirement and Networking Diagram

An E-Line service from the NodeB needs to be transmitted to the RNC over a PSN. The service
requires dual-homing to the RNC.
As shown in Figure 12-3, NE3 receives the E-Line service from the NodeB, NE1 and NE2 are
connected to the RNC for dual-homing of the service to the RNC, and MC-LAG is configured
on the AC side for inter-chassis protection.
Figure 12-3 Networking diagram of MC-LAG in the dual-homing scenario
AC side
NNI side
NE1
NE3
LAG1
1:1
PW APS
A
PSN
MC-LAG
NodeB
S LAG3
RNC
LAG2
NE2
communication
A
S

Service Planning
Table 12-2 lists the LAG parameters of NE1 and NE2 on the AC side (RNC side).
Issue 03 (2012-11-30)

458
OptiX OSN 7500 II/7500/3500/1500

12 MC-LAG
Table 12-2 LAG parameter planning for NE1 and NE2

Parameter
NE1
NE2
LAG No.
LAG Name
LAG1
LAG2
LAG Type
Static
Static
Load Sharing
Non-Sharing
Non-Sharing
System Priority
Main Board
2-N1PEG8
2-N1PEG8
Main Port
1(PORT-1)
1(PORT-1)
Selected Slave Ports
2-N1PEG8-2(PORT-2)
2-N1PEG8-2(PORT-2)
Port Priority
2-N1PEG8-2(PORT-1): 1
2-N1PEG8-2(PORT-1): 1
2-N1PEG8-2(PORT-2): 2
2-N1PEG8-2(PORT-2): 2
Table 12-3 lists the inter-equipment synchronous communication protocol parameters of MCLAG on the AC side (RNC side).
Table 12-3 Planning of inter-chassis synchronous communication protocol parameter
Parameter
NE1, NE2
Protocol Channel ID
10
Hello Packet Sending Interval(s)
Timeout Time(s)
100
Protocol Tunnel Type
MPLS Tunnel
Tunnel
410
Table 12-4 lists the MC-LAG parameters of NE1 and NE2 on the AC side (RNC side).
Table 12-4 MC-LAG parameter planning for NE1 and NE2
Issue 03 (2012-11-30)
Parameter
NE1
NE2
Local Link Aggregation

Group ID
Peer Link Aggregation

Group ID
Cooperative Channel ID
10
10

459
OptiX OSN 7500 II/7500/3500/1500

12 MC-LAG
Parameter
NE1
NE2
Load Sharing Type
Non-load-sharing
Non-load-sharing
Restoration Mode
Revertive
Revertive

Based on the preceding example, configure the MC-LAG function as follows.
Prerequisites
l
You must be familiar with the networking, requirements, and service planning of the
example.
A bidirectional tunnel is configured between the dual-homed nodes for multi-chassis

synchronous communication.
Procedure
Step 1 Configure the multi-chassis synchronous communication function on NE1 and NE2.
1.
In the NE Explorer, select NE1, and then choose Configuration > Packet
Configuration > Synchronization Protocol Management from the Function Tree.
2.
Click New, In the Create Cross-Equipment Synchronization Protocol dialog box that
is displayed, set the parameters of multi-chassis synchronous communication.
Parameter
NE1, NE2
Protocol Channel ID
10
Hello Packet Sending Interval(s)
Timeout Time(s)
100
MPLS Tunnel
Tunnel
410
3.
Click OK. The Operation Result dialog box is displayed, indicating that the operation is
successful.
4.
In the Operation Result dialog box, click Close.
5.
Perform Step 1.1 to Step 1.4 to set the multi-chassis synchronous communication
parameters on NE2.
Step 2 Configure LAGs on NE1 and NE2.

1.
In the NE Explorer, select NE1, and choose Configuration > Packet Configuration >
Tree.
2.
Click the Link Aggregation Group Management tab.
Issue 03 (2012-11-30)

460
OptiX OSN 7500 II/7500/3500/1500

3.
12 MC-LAG
Click New. In the Create Link Aggregation Group dialog box that is displayed, set the
parameters of the LAG.
Table 12-5 lists the LAG parameters of NE1 on the AC side (RNC side).
Table 12-5 LAG parameter planning for NE1
Parameter
NE1
LAG No.
LAG Name
LAG1
LAG Type
Static
Load Sharing
Non-Sharing
System Priority
Main Board
2-N1PEG8
Main Port
1(PORT-1)
2-N1PEG8-2(PORT-2)
4.
successful.
5.
6.
Click the Port Priority tab. Set the port priorities.

Table 12-6 lists the port priorities of NE1 on the AC side (RNC side).
Table 12-6 Port priority planning for NE1
Parameter
NE1
Port Priority
2-N1PEG8-2(PORT-1): 1
2-N1PEG8-2(PORT-2): 2
7.
successful.
8.
9.
Perform Step 2.1 to Step 2.8 to configure the LAG on NE2.

Table 12-7 lists the LAG parameters of NE2 on the AC side (RNC side).
Table 12-7 LAG parameter planning for NE2
Issue 03 (2012-11-30)
Parameter
NE2
LAG No.
LAG Name
LAG2

461
OptiX OSN 7500 II/7500/3500/1500

12 MC-LAG
Parameter
NE2
LAG Type
Static
Load Sharing
Non-Sharing
System Priority
Main Board
2-N1PEG8
Main Port
1(PORT-1)
2-N1PEG8-2(PORT-2)
Port Priority
2-N1PEG8-2(PORT-1): 1
2-N1PEG8-2(PORT-2): 2
Step 3 Configure the MC-LAG on NE1 and NE2.

1.
In the NE Explorer, select NE1, and choose Configuration > Packet Configuration >
Tree.
2.
Click the Cross-Equipment Link Aggregation Groups tab.
3.
Click New. In the Create Cross-Equipment Link Aggregation Group dialog box that is
displayed, set the parameters of the MC-LAG.
Parameter
NE1
Local Link Aggregation Group ID
Peer Link Aggregation Group ID
10
Load Sharing Type
Non-load-sharing
Restoration Mode
Revertive
4.
successful.
5.
6.
Perform Step 3.1 to Step 3.5 to configure the MC-LAG on NE2.
Issue 03 (2012-11-30)
Parameter
NE2
Local Link Aggregation Group ID
Peer Link Aggregation Group ID
10
Load Sharing Type
Non-load-sharing
Restoration Mode
Revertive

462
OptiX OSN 7500 II/7500/3500/1500

12 MC-LAG
----End

This topic describes the alarms and performance events that are related to the MC-LAG.

This topic describes the alarms related to MC-LAG.
Table 12-8 lists the alarms that are related to the MC-LAG.
Table 12-8 Alarms related to MC-LAG
Alarm Name
Meaning
MCLAG_CFG_MISMATCH
The MCLAG_CFG_MISMATCH is an alarm indicating

inconsistent MC-LAG configurations. This alarm is reported
when the MC-LAG configurations at the two ends are
inconsistent.
MCSP_PATH_LOCV
The MCSP_PATH_LOCV is an alarm indicating the loss of

connectivity on the protocol channel on which synchronous crossequipment communication is achieved. This alarm is reported if
the expected Hello packet is not received on the protocol channel
in three consecutive periods.

None.
12.11 Parameter Description: MC-LAG

This topic describes the parameters required for configuring MC-LAG.
12.11.1 Synchronization Protocol Management

This topic describes the parameters that are used for synchronization protocol management.
Issue 03 (2012-11-30)

463
OptiX OSN 7500 II/7500/3500/1500

12 MC-LAG
Table 12-9 Parameters for synchronization protocol management

Field
Value Range
Description
Protocol Channel ID
1-15
The Protocol Channel ID

parameter specifies the ID of
the protocol channel when
the MCSP channel is created.
This parameter can be
For example, 1
Click A.18.1 Protocol

Channel ID for more
information.
Peer Device IP Address
NOTE
This parameter is not applicable
to an MC-LAG.
Hello Packet Sending

Interval (s)
1-10
Default: 1
Specifies the IP address of

the equipment at the opposite
end.
The Hello Packet Sending
Interval (s) parameter
specifies the interval at which
the Hello packets are
transmitted to the opposite
end to check whether the link
is normal.
Click A.18.2 Hello Packet
Sending Interval (s) for
more information.
Timeout Time (s)
30-3600
Default: 600
The Timeout Time (s)

parameter is used for
checking whether the
configuration messages time
out.
Click A.18.3 Timeout Time
(s) for more information.
MPLS Tunnel
Displays the type of the

tunnel that transmits the
protocol-compliant packets.
Tunnel
Tunnel ID (Tunnel Name)
Specifies the tunnel that

bidirectionally transmits the
protocol-compliant packets.
12.11.2 Link Aggregation Group Management

This topic describes the parameters for configuring link aggregation group (LAG) management
of Ethernet services.
Issue 03 (2012-11-30)

464
OptiX OSN 7500 II/7500/3500/1500

12 MC-LAG
Table 12-10 Parameters for configuring LAG management

Field
Value Range
Description
LAG No.
For example, 1
Displays the number of the

LAG.
NOTE
The value is an integer ranging
from 1 to 64.
LAG Name
For example, LAG1

The name contains a
maximum of 31 English
letters or 15 Chinese
characters.
LAG Type
Manual, Static
Default: Static
The value of this parameter is

assigned automatically.
LAG.
Manual indicates that the

LAG is created manually, the
Link Aggregation Control
Protocol (LACP) is disabled,
and the members in the LAG
are fixed. Manual LAGs are
easy to manage, but the
aggregation cannot be
controlled accurately or
efficiently.
Static indicates that the LAG
is created manually and the
LACP is used to check the
working status (active or
inactive) of each port in the
LAG. If working status of a
port is set to Selected, the
port can forward services.
Otherwise, the port cannot
forward services. Hence,
static LAGs can be easily
managed and used, and the
aggregation can be controlled
accurately and efficiently.
Switch Protocol
Displays the switching

protocol of the LAG.
NOTE
when LAG management is
configured.
Switch Mode
Displays the switching mode

of the LAG.
NOTE
configured.
Issue 03 (2012-11-30)

465
OptiX OSN 7500 II/7500/3500/1500

12 MC-LAG
Field
Value Range
Description
Link Trace Protocol
Displays the link trace

protocol of the LAG.
NOTE
configured.
Revertive Mode
Revertive, Non-Revertive
Default: Non-Revertive
Load Sharing
Sharing, Non-Sharing
Default: Non-Sharing
Displays the revertive mode

of the LAG.
Displays the load sharing
mode of the LAG.
If Load Sharing is set to
Non-Sharing, the equipment
does not support the setting
of Revertive Mode.
Load Sharing Hash

Algorithm
System Priority
Automatic, Source MAC,

Destination MAC, Source
and Destination MACs,
Source IP Address,
Destination IP Address,
Source and Destination IP
Addresses, Source Port
Number, Destination Port
Number, Source and
Destination Port Numbers,
MPLS Label
A proper load-sharing hash

algorithm ensures that the
compliant traffic is
transmitted over the same
link. In this manner, the
receive end always receives
the packets with the correct
frame sequence.
0 to 65535
The system priority and the

system MAC address
(namely, the MAC address of
the board) constitute the
system ID, which is used for
negotiating with the
interconnected equipment.
The equipment with a higher
priority is preferred during
selection.
Default: 32768
WTR Time(min)
1 to 30
Default: 10
Issue 03 (2012-11-30)

This parameter can be set if

Load Sharing is Sharing.
Specifies the wait-to-restore

(WTR) time when services
are switched from the
protection link to the working
link. You can set this
parameter to avoid frequent
service switching between
the working and protection
links when the links are in
unstable state.
466
OptiX OSN 7500 II/7500/3500/1500

12 MC-LAG
Table 12-11 Parameters for port priority setting

Field
Value Range
Description
Port

(PORT-1)
Port Priority
0-65535
Specifies the priority of an

Ethernet port.
Default: 32768
If other conditions (for

example, transmission rate
and working mode) are the
same, a higher-priority port
in the LAG that runs the
LACP protocol is preferred
for transmitting services.
This parameter is not
applicable to the LAG (for
example, manual LAG) that
does not run the LACP
protocol.
The smaller the value, the
higher the priority.
Issue 03 (2012-11-30)

467
OptiX OSN 7500 II/7500/3500/1500

13 MPLS PW APS
13
MPLS PW APS
About This Chapter

The PW APS uses the protection PW to protect the working PW. When the working PW is faulty,
the services are switched to the protection PW and remain unaffected.
13.1 Introduction
PW APS provides network-level protection. In PW APS, a protection PW is created to protect
the working PW once it fails. PW APS is available in three types: PW APS 1+1, PW APS 1:1,
and PW Fast Protection Switching (FPS).
13.2 Basic Concepts
Learning about the basic concepts helps to further understand the PW APS feature.
13.3 Specifications
This section describes capacity of the OptiX OSN equipment for supporting MPLS PW APS.
This topic describes the standards and protocols that PW APS complies with.
13.5 Availability
The PW APS function requires the support of the applicable equipment and boards.
This section describes the limitations on and precautions for MPLS PW APS in the network
13.7 Principles
In both PW APS 1+1 and PW APS 1:1, the protection PW protects the services on the working
PW. Specifically, when the working PW fails, services are switched to the protection PW. In
PW APS 1+1 protection, services are dually fed and selectively received; in PW APS 1:1
protection, services are singly fed and received.
13.8 Configuring PW APS
This topic describes the PW APS configuration tasks.
13.9 Configuration Example (PW APS)
This topic uses an example to describe how to configure PW APS according to network planning.
13.10 Configuration Example (PW FPS)
Issue 03 (2012-11-30)

468
OptiX OSN 7500 II/7500/3500/1500

13 MPLS PW APS
This section uses an example to describe the configuration of PW FPS according to network
planning.
This topic describes the alarms and performance events that are related to the MPLS PW APS.
13.12 Parameter Description: MPLS PW APS
This topic describes the parameters required for configuring PW APS.
Issue 03 (2012-11-30)

469
OptiX OSN 7500 II/7500/3500/1500

13 MPLS PW APS
13.1 Introduction
PW APS provides network-level protection. In PW APS, a protection PW is created to protect
the working PW once it fails. PW APS is available in three types: PW APS 1+1, PW APS 1:1,
and PW Fast Protection Switching (FPS).
Definition
PW APS 1+1 protection
Generally, the source dually transmits services to the working PW and protection PW and the
sink receives the services from the working PW. When the working PW is faulty, the sink
receives the services from the protection PW.
PW APS 1:1 protection
Generally, the source transmits services only to the working PW and the sink receives the
services from the working PW. When the working PW is faulty, the source transmits services
to the protection PW and the sink receives the services from the protection PW.
PW FPS protection
Generally, the source transmits services only to the working PW and the sink receives the
services from the working PW. When the working PW is faulty, the source transmits services
to the protection PW and the sink receives the services from the protection PW. PW FPS
generally works with the IWF function to provide end-to-end protection.
Application
Application of PW APS 1+1/1:1 protection
As shown in Figure 13-1, a PW APS protection group is configured between PE1 and PE2.
Generally, services are transmitted on the working PW. When the working PW is faulty, APS
switching occurs and the services are switched over to the protection PW.
Figure 13-1 Networking diagram of PW APS 1+1/1:1 (same source and same sink)
PSN
NodeB
PW APS
PE1
PW1
PW APS
PW2
PE2
PW3
RNC
PW4
NodeB
Working PW
Protection PW
Issue 03 (2012-11-30)

470
OptiX OSN 7500 II/7500/3500/1500

13 MPLS PW APS
In actual applications, PW APS can work with MC-LAG to provide multi-chassis protection.
As shown in Figure 13-2, PW APS protection groups are configured between PE1 and PE2 and
between PE1 and PE3. Generally, services are transmitted on the working PW. When the
working PW is faulty, APS switching occurs and the services are switched over to the protection
PW.
Figure 13-2 Networking diagram of PW APS 1+1/1:1 (same source but different sinks)
PE2
PE1
PW APS
A
PSN
MC-LAG
NodeB
RNC
S
PE3
Working PW
Protection PW
Multi-chassis synchronous communication
A
Application of PW FPS protection

As shown in Figure 13-3, a PW FPS protection group is configured on PE1, and PW OAM is
enabled on PE1, PE2, and PE3. Generally, services from PE1 are transmitted to PE2 on the
working PW and then forwarded to the RNC. When the working PW is faulty, APS switching
occurs on PE1 and the services are switched over to the protection PW. In this case, the services
from PE1 are transmitted to PE3 on the protection PW and then forwarded to the RNC. IWF is
enabled on PE2 and PE3 to transparently transmit fault information on the RNC side to PE1,
triggering PW FPS switching and realizing protection of services on the RNC side.
Figure 13-3 Networking diagram of PW FPS (same source but different sinks)
PE2
PE1
PW FPS
IWF
PSN
NodeB
IWF
RNC
S
PE3
Working PW
Protection PW
A
S
Issue 03 (2012-11-30)


471
OptiX OSN 7500 II/7500/3500/1500

13 MPLS PW APS
Purpose
PW APS provides protection for important working PWs on a network and helps to prevent
against service interruption resulting from a PW failure.
13.2 Basic Concepts

Learning about the basic concepts helps to further understand the PW APS feature.
Switching Type
With regard to the location of the protection switching, the PW APS comprises two switching
types, namely, single-ended switching and dual-ended switching.
l
When the PW APS protection group fails at one end, services are switched at the failed
end, and the other end remains unaffected. The single-ended switching is fast and stable.
After the single-ended switching occurs, services are transmitted to the protection PW, but
are received from the working PW.
When the PW APS protection group fails at one end, services are switched at both ends.
The dual-ended switching takes more time. After the dual-ended switching occurs, services
are transmitted to and received from the same PW, which facilitates service management.
Switching Protocol
PW APS uses the automatic protection switching (APS) protocol to coordinate the source and
sink to realize the functions such as protection switching, switching delay, and wait-to-restore.
The APS protocol is transmitted in the protection PW to inform both ends of the protocol state
and the switching state. The equipment at both ends switches services to the proper PW according
to the protocol state and switching state
l
The protocol state indicates whether the APS protocol of the protection group is enabled
currently.
The switching state indicates the current switching state of the APS protocol. The switching
state can be the normal state, WTR state, lockout of protection, or forced switching state.
Revertive Mode
PW APS comprises two revertive modes of protection switching, namely, revertive mode and
non-revertive mode.
l
When the NE is in switching state, the working PW becomes normal and thus the protection
switching request is cleared. During the WTR time, no other switching requests are received
and the NE releases the switching after the WTR time expires. As a result, services are
switched from the protection PW to the working PW.
In the case of the non-revertive mode, services are not switched from the protection PW to
the working PW even after the working PW is restored to normal.
Issue 03 (2012-11-30)

472
OptiX OSN 7500 II/7500/3500/1500

13 MPLS PW APS
WTR Time
The WTR time is the period after the working PW is restored to normal and before the NE
releases the switching. To prevent frequent switching events because the working PW is not
stable, it is recommended that you set the WTR time to 5 to 12 minutes.
Hold-Off Time
The hold-off time is the time between declaration of signal degrade or signal fail, and the
initialization of the protection switching algorithm. When different protection schemes are
configured at the same time, the hold-off time can avoid the conflict between them. By default,
the hold-off time of the equipment is 0s.
PW APS Binding
PW APS binding reduces the consumption of APS resources and therefore speeds up batch
service protection switching.
The dual-homing equipment needs to support a large number of PW APS protection groups. If
each protection group initiates a state machine, the resources and capacity of the equipment
cannot meet the requirements of all protection groups.
If the equipment is configured with n PW APS protection groups, APS1, APS2, ... APSn, APS1,
APS2, and APS2 can be bound together. Thus, APS1 is a PW APS protection group, APS2 and
APS3 are subordinate protection pairs. In this manner, APS1, APS2 and APS3 are an example
of PW APS binding.
The state of the subordinate protection pair is affected by the state of the PW APS protection
group.
l
When the PW switching occurs in the PW APS protection group, the PW switching also
occurs in the subordinate protection pair.
When the PW switching occurs in the subordinate protection pair changes, however, the
PW switching does not occur in the PW APS protection.
13.3 Specifications
This section describes capacity of the OptiX OSN equipment for supporting MPLS PW APS.
Table 13-1 lists specifications associated with MPLS PW APS.
Issue 03 (2012-11-30)

473
OptiX OSN 7500 II/7500/3500/1500

13 MPLS PW APS
Table 13-1 Specifications associated with MPLS PW APS

Item
Specification
Capacity
Number of supported MPLS PW APS groups:

l OptiX OSN 7500 II: 4K
l OptiX OSN 3500/7500:
N4GSCC: 1K
N6GSCC: 4K
A PW APS protection group supports 512 slave protection pairs.
The switching performance of a slave protection pair depends on
the associated PW APS protection group.
NOTE
PW APS and MPLS tunnel APS share one APS protection group.
Switching Type
l 1+1 single-ended switching

l 1+1 dual-ended switching
l 1:1 dual-ended switching
l PW FPS single-ended switching
NOTE
The OptiX OSN 3500, OptiX OSN 7500, and OptiX OSN 7500 II support
PW FPS; the OptiX OSN 1500 does not support PW FPS.
Revertive Mode
l Revertive
l Non-revertive
Switchover Restoration
Time(m)
l Restoration Mode being Revertive: 1 minute to 12 minutes

(1 minute by default)
l Restoration Mode being Non-Revertive: This parameter
can be set but the setting does not apply.
Switching Protocol
APS
NOTE
PW FPS does not support the APS protocol.
Switching Mode
l Locked switching
l Forced switching
l Automatic switching
l Manual switching
l Exercise switching
Switching Time
l For 1+1 or 1:1 PW APS: 50 ms

l For PW FPS:
NNI-side fault: 50 ms
UNI-side single-fiber fault: 4s
UNI-side dual-fiber fault: 2s
Issue 03 (2012-11-30)

474
OptiX OSN 7500 II/7500/3500/1500

13 MPLS PW APS
Item
Specification
Switching Delay Time
0s to 10s (0s by default), which can be set at a step length of 100

ms
Switching Condition
(Any of the following
conditions triggers the
switching)
l The board has a hardware or software failure.

l A cold reset is performed on the board.
l A switching command is manually issued.
l A working PW failure is detected by PW OAM.
For PW FPS, the extra switching conditions are:
l Port-associated alarm
l Ethernet port OAM alarm

This topic describes the standards and protocols that PW APS complies with.
The PW APS complies with the following standards and protocols:
l
ITU-T Recommendation Y.1720 Protection switching for MPLS networks
ITU-T Recommendation G.8131 Protection switching for transport MPLS (T-MPLS)

networks
13.5 Availability
The PW APS function requires the support of the applicable equipment and boards.
Version Support
Issue 03 (2012-11-30)
Product Name
Applicable Version
OptiX OSN 1500/3500/7500
U2000
Product Name
Applicable Version
OptiX OSN 7500 II
U2000

475
OptiX OSN 7500 II/7500/3500/1500

13 MPLS PW APS
Hardware Support
Table 13-2 Boards that support PW APS 1+1/1:1
Board Type
Version
N1PEX2
OptiX OSN 3500/7500
N2PEX1
OptiX OSN 3500/7500
N1PEG8
OptiX OSN 3500/7500
N1PETF8
OptiX OSN 3500/7500
N1PEFF8
OptiX OSN 3500/7500
R1PEFS8
Q1PEGS2
R1PEGS1
R1PEF4F
TNN1EX2
OptiX OSN 7500 II
TNN1EG8
OptiX OSN 7500 II
TNN1ETMC
OptiX OSN 7500 II
TNN1EFF8
OptiX OSN 7500 II
Table 13-3 Boards that support PW FPS
Issue 03 (2012-11-30)
Board Type
Version
N1PEX2
OptiX OSN 3500/7500
N2PEX1
OptiX OSN 3500/7500
N1PEG8
OptiX OSN 3500/7500
N1PETF8
OptiX OSN 3500/7500
N1PEFF8
OptiX OSN 3500/7500
TNN1EX2
OptiX OSN 7500 II
TNN1EG8
OptiX OSN 7500 II
TNN1ETMC
OptiX OSN 7500 II
TNN1EFF8
OptiX OSN 7500 II

476
OptiX OSN 7500 II/7500/3500/1500

13 MPLS PW APS

This section describes the limitations on and precautions for MPLS PW APS in the network
Issue 03 (2012-11-30)
Applicable
Object

Details
Remarks
PW APS
The working PW and protection PW

should not physically be on the same
path, if possible.
PW APS
1:1 PW APS improves bandwidth

utilization. Unless otherwise
specified, 1:1 PW APS works in
dual-ended revertive mode.
PW APS

wait-to-restore (WTR) time and
hold-off time take default values.
PW APS
One PW cannot be included in

multiple APS protection groups at
the same time.
Slave
protection pair
of PW APS
If multiple PWs require protection

and they have the same working trail
and protection trail, configure a PW
APS protection group for one of
these PWs and configure slave PW
protection pairs for the other PWs.
PW OAM
Enable PW OAM for the working

and protection PWs of a PW APS
protection group. Configure FFD
packets as detection packets for PW
OAM. FFD packets are usually sent
at an interval of 3.3 ms. If the frame
delay variation on a PW exceeds 3.3
ms, the transmission interval of FFD

477
OptiX OSN 7500 II/7500/3500/1500

13 MPLS PW APS
Applicable
Object

Details
Remarks
PW APS and
tunnel APS
PW APS and tunnel APS cannot be

enabled simultaneously. This
indicates that, if the tunnel that
carries the PW is configured with
tunnel APS, the PW cannot be
configured with PW APS; if the PW
is configured with PW APS, the
tunnel that carries the PW cannot be
configured with tunnel APS.
PW APS and
MS-PW
When MS-PW is configured, the

forward PW and backward PW do
not support PW OAM or PW APS.
PW APS and
E-Line service
or E-LAN
service
1+1/1:1 PW APS protects E-Line

services and E-LAN services carried
on PWs, ATM PWE3 services, and
CES services.
PW FPS
PW FPS protects only E-Line

services carried on PWs.

None.
Applicable
Object

Details
Remarks
PW FPS and
interworking
function (IWF)
When IWF works with user-side

Ethernet port OAM, the problem
due to a unidirectional fiber cut can
be handled.
l If an IWF-enabled NE
encounters a fiber cut in the
receive direction, it sends FDI
packets to trigger remote
switching.
l If an IWF-enabled NE
encounters a fiber cut in the
transmit direction, it detects
OAM alarms at the Ethernet port,
and sends FDI packets to trigger
remote switching.
Issue 03 (2012-11-30)

478
OptiX OSN 7500 II/7500/3500/1500

13 MPLS PW APS
13.7 Principles
In both PW APS 1+1 and PW APS 1:1, the protection PW protects the services on the working
PW. Specifically, when the working PW fails, services are switched to the protection PW. In
PW APS 1+1 protection, services are dually fed and selectively received; in PW APS 1:1
protection, services are singly fed and received.
13.7.1 State Model

The states of PW APS comply with the state model.
Figure 13-4 shows the transitions between the PW APS states.
Figure 13-4 Transitions between the PW APS states
LOCKOUT
The lockout
conditions
are cleared
The lockout
conditions
are met
The lockout
conditions
are cleared
The automatic/forced/manual
switching conditions are met
NR
The timer
times out
The lockout
conditions are met
SWITCH
The forced/manual
switching conditions are
cleared
The automatic
switching
The
conditions are
protection
cleared
PW fails
The automatic
conditions are met
WTR
Table 13-4 lists the four states of a PW APS protection group.

Table 13-4 PW APS protection states
Issue 03 (2012-11-30)
State
Description
Normal state (NR)
A state in which an NE works normally after the APS

protocol starts
Switch state (SWITCH)
A state in which a faulty node remains after switching is

performed
WTR state (WTR)
A state in which the original switching node remains

during the WTR time after a fault is rectified

479
OptiX OSN 7500 II/7500/3500/1500

13 MPLS PW APS
State
Description
Lockout state (LOCKOUT)
A state in which an NE is selecting the working PW after

receiving the lockout of protection command
13.7.2 PW APS 1+1 Protection

In PW APS 1+1 protection, services are dually transmitted and selectively received, to
implement protection switching. This topic describes the principles of PW APS 1+1 single-ended
protection.
The unidirectional signal flow is considered as an example.
States Before Switching

Figure 13-5 shows the signal flow from NE1 to NE2 before switching.
1.
The service access board on NE1 sends the received service signal to the working and
protection service processing boards.
2.
The working service processing board sends the service signal to the working PW, and the
protection service processing board sends the service signal to the protection PW.
3.
Based on the state machines, the working service processing board on NE2 is selected to
receive the service signal from the working PW and to send the service signal to the service
access board on NE2.
4.
The service access board on NE2 sends the service signal to the opposite equipment.
Figure 13-5 Principle of PW APS 1+1 protection (NE1 -> NE2, before switching)
NE1
NE2
Active
Access
service
Crossconnect processing
board
board
Standby
service
processing
board
Working PW
Subnet
Subnet
Protection
PW/Protocol channel
Active Service detection

service
point
processing
board
Access
Standby Crossservice connect
processing board
board
States After Switching

Figure 13-6 shows the signal flow after PW APS switching.
1.
The service detection points at the source and sink ends of the protection group monitor
the status of the link by means of PW OAM packets.
2.
When the service sink (for example, NE2) in a direction detects that a switching condition
(for example, automatic switching condition or external switching condition) is met, the
state machines of the working and protection service processing boards experience state
transitions. After the preset hold-off time elapses, the protection service processing board
Issue 03 (2012-11-30)

480
OptiX OSN 7500 II/7500/3500/1500

13 MPLS PW APS
is selected to receive the service signal from the protection PW, and the PW APS event is
reported.
Figure 13-6 Principle of PW APS 1+1 protection (NE1 -> NE2, after switching)
NE1
NE2
Active
Crossservice
connect processing
board
board
Access
Standby
service
processing
board
Working PW
Subnet
Subnet
Protection
PW/Protocol channel

service
point
processing
board
Access
Standby Crossservice
connect
processing
board
board
State Restoration After Switching

When the service detection point detects that the working PW is restored to normal, the state
machines of the working and protection service processing boards determine how to switch the
service as required by the preset revertive mode.
l
If the non-revertive mode is set, the signal flow between NE1 and NE2 does not change.
If the revertive mode is set, the signal flow between NE1 and NE2 are restored to the state
before switching.
13.7.3 PW APS 1:1 Protection

In PW APS 1:1 protection, an automatic bridge mechanism functions to implement protection
switching. This topic describes the principles of PW APS 1:1 dual-ended protection.

1.
The service access board on the access side of NE1 sends the received service signal to the
working service processing board.
2.
The active service processing board sends the service signal to the working PW.
Figure 13-7 Principle of PW APS 1:1 protection (NE1 -> NE2, before switching)
NE1
NE2
Active
Access
Cross- service
connect processing
board
board
Standby
service
processing
board
Issue 03 (2012-11-30)
Working PW
Subnet
Subnet
Protection
PW/Protocol channel


service
point
processing
board
Access

processing board
board
481
OptiX OSN 7500 II/7500/3500/1500

13 MPLS PW APS

Figure 13-8 shows the signal flow from NE1 to NE2 after switching.
1.
The service detection points at the source and sink ends of the protection group monitor
the status of the link by means of PW OAM packets.
2.
When the service sink (for example, NE2) in a direction detects that a switching condition
(for example, automatic switching condition or external switching condition) is met, the
state machines of the working and protection service processing boards experience state
transitions. After the preset hold-off time elapses, the protection service processing board
is selected to receive the service signal from the protection PW.
3.
The sink end sends the SF signal to the service source (for example, NE1) in the protection
PW.
4.
The source end bridges the working PW onto the protection PW and sends the service signal
to the protection PW.
Figure 13-8 Principle of the PW APS 1:1 dual-ended protection (NE1 -> NE2, after switching)
NE1
NE2
Active
Access
Cross- service
connect processing
board
board
Standby
service
processing
board
Working PW
Subnet
Subnet
Protection
PW/Protocol channel

service
point
processing
board
Access

processing board
board

When the service detection point detects that the working PW is restored to normal, the state
machines of the working and protection service processing boards determine how to switch the
service as required by the preset revertive mode.
l
If the revertive mode is set, the signal flow between NE1 and NE2 are restored to the state
before switching.
13.7.4 PW FPS Protection

In PW FPS protection, an automatic bridge mechanism at the source end functions to implement
protection switching. This topic describes the principles of PW FPS protection.

Issue 03 (2012-11-30)

482
OptiX OSN 7500 II/7500/3500/1500

13 MPLS PW APS
1.
The route that the services from NE1 to NE4 take is as follows: NE1 -> NE2 -> NE4.
2.
The service access board on the access side of NE1 sends the received service signal to the
active service processing board.
3.
The active service processing board of NE1 sends the service signal to the working PW.
4.
NE1, NE2, and NE3 monitor the status of the working and protection PWs by means of
PW OAM packets.
Figure 13-9 Principle of PW FPS protection (NE1 -> NE4, before switching)
NE2
Active
service
processing
board
NE1
Access
Active
service
board
board
Standby
service
processing
board
Access
Working PW
Subnet
Subnet
Protection PW
NE4
Cross-connect
board
Access
NE3
Access
Standby
service
processing
board
Access
Cross-connect
board

Figure 13-10 shows the signal flow from NE1 to NE4 after switching.
1.
On detecting a PW defect, NE2 sends a BDI packet on the reverse PW to notify NE1 of
the PW defect.
2.
On receiving the BDI packet from NE2, NE1 selects the standby service processing board
to send the service signal to the protection PW after the preset hold-off time elapses.
3.
After switching, the route that the services from NE1 to NE4 take is as follows: NE1 ->
NE3 -> NE4.
Issue 03 (2012-11-30)

483
OptiX OSN 7500 II/7500/3500/1500

13 MPLS PW APS
Figure 13-10 Principle of PW FPS protection (NE1 -> NE4, after switching)
NE2
Active
service
processing
board
NE1
Access
Active
service
board
board
Standby
service
processing
board
Access
Working PW
NE4
Subnet
Subnet
Protection PW
Cross-connect
board
Access
NE3
Access
Standby
service
processing
board
Access
Cross-connect
board

When the service detection point of NE2 detects that the working PW is restored to normal, NE1
determines how to switch the service as required by the preset PW FPS revertive mode.
l
If the revertive mode is set, the signal flow between NE1 and NE4 is restored to the state
before switching.
13.7.5 Switching Condition

In PW APS, automatic switching or external switching may be triggered by different conditions.
Automatic Switching
Automatic switching can be triggered by SF conditions. The request packet of automatic
switching is reported to the APS protocol processing module by means of interrupts. Table
13-5 lists the conditions triggering automatic switching.
Table 13-5 Conditions triggering automatic switching
Switching Condition
Priority
The board is faulty. For example, the HARD_BAD

alarm is detected.
With the same priority
The board is not in position. For example, the board is

removed or a cold reset is performed for the board.
Issue 03 (2012-11-30)

484
OptiX OSN 7500 II/7500/3500/1500

13 MPLS PW APS
Switching Condition
Priority
A fault on the data link layer of the working PW is

detected with the PW OAM function enabled.
l MPLS_PW_LOCV
l MPLS_PW_Excess
l MPLS_PW_MISMATCH
l MPLS_PW_MISMERGE
l MPLS_PW_UNKNOWN
l MPLS_PW_SF
External Switching
External switching is triggered by the switching commands issued by users. Table 13-6 lists the
conditions triggering external switching.
Table 13-6 Conditions triggering external switching
Switching Condition
Priority
Description
Clear switching
The switching
conditions are
arranged in a
descending
order or priority.
This command clears all the external

switching states, and enables the NE to
return to the idle state or automatic
switching state according to the states of
the working and protection PWs.
Lockout of protection
Regardless of the switching state, services

are locked in the working PW. In the
lockout state, services cannot be switched
even when they should be until lockout of
protection is cleared.
Forced switching
If an NE is in a switching state with a

higher priority, forced switching cannot
be performed.
Otherwise, services are switched from the
working PW to the protection PW,
regardless of whether the protection PW
works properly. In addition, services
cannot be switched to the working PW
automatically.
In revertive mode, services cannot be
forcibly switched to the working PW.
Issue 03 (2012-11-30)

485
OptiX OSN 7500 II/7500/3500/1500

Switching Condition
Manual
switching
Manual
switching to
working
13 MPLS PW APS
Priority
Description
higher priority, manual switching cannot
be performed.
protection PW to the working PW.
l If the working PW works properly,
manual switching occurs.
l If the working PW fails, manual
switching does not occur.
In revertive mode, services cannot be
manually switched to the working PW.
Manual
switching to
protection

higher priority, manual switching cannot
be performed.
working PW to the protection PW.
l If the protection PW works properly,
manual switching occurs and can be
cleared automatically.
l If the protection PW fails, manual
Exercise switching

higher priority, exercise switching cannot
be performed.
Otherwise, exercise switching occurs and
only the APS protocol is switched.
Exercise switching helps to test the
protection function of PW APS, without
interrupting services.
Switching Rules
PW APS switching complies with the following rules:
l
In a descending order of priority, the switching commands are arranged as follows: clear
switching, lockout of protection, forced switching, automatic switching, manual switching,
and exercise switching.
Higher-priority switching commands can pre-empt lower-priority switching commands,

whereas lower-priority switching commands cannot preempt higher-priority switching
commands.
13.7.6 Switching Impact

PW APS switching does not affect the system. Switching of one PW APS protection group can
be complete within 50 ms, which meets the carrier-class requirement.
Issue 03 (2012-11-30)

486
OptiX OSN 7500 II/7500/3500/1500

13 MPLS PW APS
13.8 Configuring PW APS

This topic describes the PW APS configuration tasks.
13.8.1 Configuring PW APS Protection Groups

The equipment supports PW APS. A PW APS protection group enables protection for services
in the PW.
Prerequisites
l
The tunnel carrying the working PW and protection PW must be created.
Context
PW APS can be configured for CES services, E-Line services, and E-LAN services carried by
PWs. A PW APS protection group can be created when services are initially configured or after
services are configured.
The PW APS protection group must be created on the source NE and sink NE.
NOTE
This topic considers creating a PW APS protection group for E-Line services as an example. The
configuration method provides a reference for creating PW APS protection groups for other services.
For details on how to create CES services, E-Line services, and E-LAN services, see "Configuring CES
Services", "Configuring E-Line Services", and "Configuring E-LAN Services" in the Configuration Guide
(Packet Transport Domain) .
Procedure
l
Issue 03 (2012-11-30)
When the service is configured initially, set Protection Type to PW APS, create the
working PW and protection PW, and create a PW APS protection group.
1.
In the NE Explorer, select the required NE and choose Configuration > Packet
Configuration > Ethernet Service Management > E-Line Service from the
Function Tree.
2.
Click the UNI tab and then click New.
3.
In the New E-Line Service dialog box that is displayed, set the E-Line service
parameters according to service planning. To be specific, set Direction to UNI-NNI
and Protection Type to PW APS.

487
OptiX OSN 7500 II/7500/3500/1500

13 MPLS PW APS
4.
Click Configure PW. The Configure PW dialog box is displayed.
5.
In the Basic Attributes tab, set the parameters associated with the working PW and
protection PW according to network planning.
6.
In the Protect Group tab, set the parameters associated with the PW APS protection
group.
CAUTION
It is recommended that you set Enabling Status to Disabled during the configuration
process. Enable the protocol only after the APS protection group is successfully
created on the NEs at both ends. If the APS protocol is first enabled at the local NE
and then at the opposite NE, the opposite NE may fail to receive services properly.
Issue 03 (2012-11-30)

488
OptiX OSN 7500 II/7500/3500/1500

7.
13 MPLS PW APS
Set Detection Packet Type to FFD, and Detection Packet Period(ms) to 3.3 ms for
PW OAM of the working PW and protection PW.
CAUTION
Detection Packet Period(ms) is set to 3.3 ms to ensure that the protection switching
time is within 50 ms. When the delay jitter is large on the live network, the packet
detection period of PW OAM needs to be longer than the maximum network delay
jitter. Otherwise, PW APS switching may occur frequently.
Issue 03 (2012-11-30)
8.
Click OK.
9.
Perform the preceding operations to create the PW APS protection group for the
opposite NE. Then, enable the APS protocol at both ends.
When the opposite NE is already configured with services, create the PW APS protection
group in the Protect Group tab.
1.
Function Tree.
2.
Click Query. The created E-Line services are displayed.
3.
Select the required E-Line service, and click PW APS in the Protect Group tab.
4.
Click New in the lower right corner of the pane. The Configure PW dialog box is
displayed.
489
OptiX OSN 7500 II/7500/3500/1500

13 MPLS PW APS
5.
6.
Optional: In the QoS tab, set the QoS attributes of the protection PW according to
network planning.
NOTE
When Bandwidth Limit is set to Enabled, you can set CIR(kbit/s) and PIR(kbit/s).
In the created PW policy template, click Policy.
7.
In the Protect Group tab, set the parameters associated with the PW APS protection
group.
CAUTION
It is recommended that you set Enabling Status to Disabled during the configuration
process. Enable the protocol only after the APS protection group is successfully
created on the NEs at both ends. If the APS protocol is first enabled at the local NE
and then at the opposite NE, the opposite NE may fail to receive services properly.
Issue 03 (2012-11-30)

490
OptiX OSN 7500 II/7500/3500/1500

8.
13 MPLS PW APS
Set Detection Packet Type to FFD, and Detection Packet Period(ms) to 3.3 ms for
PW OAM of the working PW and protection PW.
CAUTION
time is within 50 ms. When the delay jitter is large on the live network, the packet
detection period of PW OAM needs to be longer than the maximum network delay
jitter. Otherwise, PW APS switching may occur frequently.
9.
Click OK.
10. Perform the preceding operations to create the PW APS protection group for the
opposite NE. Then, enable the APS protocol at both ends.
----End
Result
Check whether the working PW and protection PW work properly.
1.
2.
In the PW Management tab, click Query. Then, close the Operation Result dialog box.
3.
View Local Operating Status and Remote Operating Status of the working PW and
protection PW.
Issue 03 (2012-11-30)

491
OptiX OSN 7500 II/7500/3500/1500

13 MPLS PW APS
l If the status parameters are Up, the PW works properly.

l If the status parameters are Down, the PW fails.
Follow-up Procedure
Deleting a PW APS protection group
Exercise caution when performing this operation, because the service will be unprotected after
the protection group is deleted. To delete a created PW APS protection group, do as follows:
1.
Disable the APS protocol on the NEs at both ends.
2.
Select the required E-Line service, and click PW APS in the Protect Group tab.
3.
Select the required PW APS protection group, and click Delete in the lower right corner
of the pane.
Modifying a PW APS protection group

Reset the PW APS parameters as required. If the values of the parameters at both ends are
inconsistent, the PW APS switching may fail. For the rules for setting the PW APS parameters,
see 13.12 Parameter Description: MPLS PW APS.
13.8.2 Configuring Slave Protection Pairs of PW APS

When the working PWs and protection PWs of multiple PW APS slave protection pairs share
the same source and same sink with the created PW APS protection group, you can bind the
slave protection pairs to the PW APS protection group. In this manner, the slave protection pairs
and the PW APS protection group can be synchronous in detection and switching, improving
utilization of PW OAM resources.
Prerequisites
l
The tunnel carrying the working PW and protection PW must be created.
The PW APS protection group must be created.
Context
PW APS slave protection pairs can be configured for CES services, E-Line services, E-LAN
services carried by PWs, and the PW APS slave protection pairs can be bound with the created
PW APS protection group. PW APS binding can be configured when services are initially
configured or after services are configured.
The binding of PW APS slave protection pairs requires addition of slave protection pairs to the
source NE and sink NE.
NOTE
This topic considers creating slave protection pairs for E-Line services as an example. The configuration
method provides a reference for creating slave protection pairs for other services.
For details on how to create CES services, E-Line services, and E-LAN services, see "Configuring CES
Services", "Configuring E-Line Services", and "Configuring E-LAN Services" in the Configuration Guide
(Packet Transport Plane).
Issue 03 (2012-11-30)

492
OptiX OSN 7500 II/7500/3500/1500

13 MPLS PW APS
Procedure
l
Issue 03 (2012-11-30)
When the service is configured initially, set Protection Type to Slave Protection Pair,
create the working PW and protection PW, and bind the slave protection pair with the
created the PW APS protection group.
1.
Function Tree.
2.
Click the UNI tab and then click New.
3.
Set the E-Line service parameters according to service planning. To be specific, set
Direction to UNI-NNI and Protection Type to Slave Protection Pair.
4.
5.
6.
In the Protect Group tab, select the protection group for the slave protection pair.
7.
Click OK.
When the NE is already configured with services, add the slave protection pair in the
Protect Group tab.
1.
Function Tree.
2.
3.
Select the required E-Line service, and click Slave Protection Pair in the Protect
Group tab.
4.
displayed.
493
OptiX OSN 7500 II/7500/3500/1500

13 MPLS PW APS
5.
6.
network planning.
NOTE
7.
In the Protect Group tab, select the protection group for the slave protection pair.
8.
Click OK.
----End
Result
1.
2.
3.
protection PW.
Follow-up Procedure
the slave protection pair is deleted. To delete a created slave protection pair, do as follows:
1.
Disable the APS protocol on the NEs at both ends.
2.
Select the required E-Line service, and click Slave Protection Pair in the Protect
Group tab.
Issue 03 (2012-11-30)

494
OptiX OSN 7500 II/7500/3500/1500

3.
13 MPLS PW APS
Select the required slave protection pair, and click Delete in the lower right corner of the
pane.
13.8.3 Starting the APS Protocol

After the PW APS protection group is created, you need to start the APS protocol so that the
protection group can take effect.
Prerequisites
l
Procedure
Configuration > APS Protection Management from the Function Tree.
Step 2 In the PW APS Management tab, click Query. The created PW APS protection group is
displayed.
Step 3 Right-click the PW APS protection group, and then choose Start Protocol from the shortcut
menu.
Step 4 A dialog box is displayed, indicating that the operation is successful. It shows that the value of
Protocol Status of the PW APS protection group becomes Enabled.
Step 5 In the NE Explorer of the opposite NE, perform the preceding operations to start the APS
protocol.
----End
13.8.4 Performing External Switching of PW APS

PW APS can protect services carried by the working PW. This topic describes how to perform
the external switching of PW APS.
Prerequisites
l
Procedure
Configuration > APS Protection Management from the Function Tree.
Step 2 In the PW APS Management tab, click Query. Generally, the values of Working Path
Status and Protection Path Status are Available, and the value of Switchover Status is
Normal \(No Request for Working\).
Step 3 Select the created protection group, and choose Function > Manual Switching to Protection.
In the Operation Result dialog box that is displayed, click OK.
Issue 03 (2012-11-30)

495
OptiX OSN 7500 II/7500/3500/1500

13 MPLS PW APS
Step 4 Click Query. The value of Protection Status becomes Manual Switching\(Working to
Protection\), which indicates that the service is switched to the protection PW.
----End
13.8.5 Configuring PW FPS Protection Groups

The OptiX OSN equipment supports PW FPS. PW FPS protection groups cooperate with the
interworking function (IWF) to realize end-to-end service protection.
Prerequisites
l
The MPLS tunnel carrying the working and protection PWs has been created.
E-Line services carried by PWs can be configured with PW FPS.
PW FPS protection groups only need to be created on the source NE.
A PW FPS protection group can be created when services are initially configured or after
services are configured.
Context
NOTE
For details on how to create E-Line services, see Configuring E-Line Services in the Configuration Guide
(Packet Transport Domain).
Procedure
l
Issue 03 (2012-11-30)
When the service is configured initially, set Protection Type to PW FPS, create the
working PW and protection PW, and create a PW FPS protection group.
1.
In the NE Explorer, select the desired NE, and choose Configuration > Packet
Function Tree.
2.
Click the UNI tab, and click New.
3.
In the New E-Line Service dialog box that is displayed, set the E-Line service
parameters according to service planning. Specifically, set Direction to UNI-NNI,
and Protection Type to PW FPS.

496
OptiX OSN 7500 II/7500/3500/1500

13 MPLS PW APS
4.
5.
6.
In the Protection Group tab, set the parameters associated with the PW FPS
protection group. For details, see 13.12.1 Parameter Description: PW APS .
7.
In the PW OAM tab, set Detection Packet Type to FFD and Detection Packet
Period(ms) to 3.3 ms for PW OAM of the working PW and protection PW.
CAUTION
time is within 50 ms. When the delay variation is large on the live network, the packet
detection period of the PW OAM needs to be larger than the maximum network delay
variation. Otherwise, PW FPS switching may occur frequently.
Issue 03 (2012-11-30)

497
OptiX OSN 7500 II/7500/3500/1500

8.
l
13 MPLS PW APS
Click OK. In the dialog box that is displayed, click Close.
After the E-Line services are created, create the PW FPS protection group in the Protection
Group tab.
1.
In the NE Explorer, select the desired NE, and choose Configuration > Packet
Function Tree.
2.
3.
Select the desired E-Line service, and click PW FPS in the Protection Group tab.
4.
displayed.
5.
6.
network planning.
NOTE
7.
Issue 03 (2012-11-30)
In the Protection Group tab, set the parameters associated with the PW FPS
protection group. For details, see 13.12.1 Parameter Description: PW APS .

498
OptiX OSN 7500 II/7500/3500/1500

8.
13 MPLS PW APS
In the PW OAM tab, set Detection Packet Type to FFD and Detection Packet
Period(ms) to 3.3 ms for PW OAM of the working PW and protection PW.
CAUTION
time is within 50 ms. When the delay variation is large on the live network, the packet
detection period of the PW OAM needs to be larger than the maximum network delay
variation. Otherwise, PW FPS switching may occur frequently.
9.
Click OK. In the dialog box that is displayed, click Close.
----End
Result
1.
2.
3.
protection PW.
Issue 03 (2012-11-30)

499
OptiX OSN 7500 II/7500/3500/1500

13 MPLS PW APS
Follow-up Procedure
Deleting a PW FPS Protection Group
CAUTION
the protection group is deleted.
To delete a created PW FPS protection group, perform the following steps:
1.
2.
Select the desired PW FPS protection group, and click Delete in the lower right corner of
the pane.
Modifying a PW FPS protection group

Reset the PW FPS parameters as required.
NOTE
For rules for setting the PW FPS parameters, see 13.12 Parameter Description: MPLS PW APS.
1.
2.
Reset the corresponding parameters and click Apply.
13.9 Configuration Example (PW APS)

This topic uses an example to describe how to configure PW APS according to network planning.

This topic describes the functional requirement, networking diagram, and parameter planning.

As shown in Figure 13-11, data services are configured between the NodeBs and the RNC. ELine services are configured between NE1 and NE3 and between NE4 and NE3. All the services
are configured with PW APS. NE1 and NE4 receive services from the NodeBs. The received
services are encapsulated and then transparently transmitted to NE3. NE3 decapsulates and
transmits the services to the RNC.
When the services between the NodeBs and the RNC are carried by PWs, a new tunnel must be
configured between NE2 and NE3 to carry an additional PW when a new NodeB is added.
To improve utilization of tunnel resources between NE2 and NE3, multi-segment pseudowires
(MS-PWs) are created to carry services.
Issue 03 (2012-11-30)

500
OptiX OSN 7500 II/7500/3500/1500

13 MPLS PW APS
Figure 13-11 Networking diagram of PW APS

NodeB
NE1
NodeB
PSN
NE3
RNC
NE2
NE4
Working PW
NodeB
Protection PW
The same configuration methods are used for the services and protection between NE1 and NE3,
and between NE4 and NE3. Therefore, this example describes the configurations of the services
and protection between NE1 and NE3 only.
As shown in Figure 13-12, one E-Line service, E-Line-1, is transmitted on the trail NodeB
1NE1NE2NE3. E-Line-1 is configured with a PW APS protection group named
APS1; the other E-Line service, E-Line-2, is transmitted on the trail NodeB
2NE1NE2NE3. E-Line-2 is configured with a PW APS slave protection pair that
is bound with APS1.
Figure 13-12 Networking diagram of PW APS between NE1 and NE3
NodeB 1
NE1
MS-PW11_1
MS-PW33_1
MS-PW11_2
MS-PW33_2
MS-PW22_1
MS-PW22_2
MS-PW44_1
NE2
MS-PW44_2
RNC
NE3
NodeB 2
Working PW
Protection PW
PW APS protection
PW APS slave protection pair
Table 13-7 lists the service information.
Issue 03 (2012-11-30)

501
OptiX OSN 7500 II/7500/3500/1500

13 MPLS PW APS
Table 13-7 Service Information

Service
PW and the
Tunnel That
Carries the PW
Between NE1
and NE2
Between NE2
and NE3
Protection
Attribute
E-Line-1
Working PW
MS-PW11_1
MS-PW11_2
Tunnel that carries

the working PW
MPLS Tunnel 1
MPLS Tunnel 2
PW APS
protection
group: APS1
Protection PW
MS-PW33_1
MS-PW33_2
Tunnel that carries

the protection PW
MPLS Tunnel 3
MPLS Tunnel 4
Working PW
MS-PW22_1
MS-PW22_2
Tunnel that carries

the working PW
MPLS Tunnel 1
MPLS Tunnel 2
Protection PW
MS-PW44_1
MS-PW44_2
Tunnel that carries

the protection PW
MPLS Tunnel 3
MPLS Tunnel 4
E-Line-2
Slave
protection pair
of APS1
Service Planning
NE1-NE3 are OptiX OSN 3500 NEs in this example. Table 13-8 lists the NE parameter planning.
Table 13-8 NE parameter planning
NE
LSR
ID
Port
Port Attribute
IP
Addre
ss/
Subn
et
Mask
of
Port
Functio
n
NE1
1.0.0.1
21-N1PETF8-1(PORT-1)
UNI
Interface
of ELine-1 on
the
NodeB 1
side
Interface
of ELine-2 on
the
NodeB 2
side
l Port mode:
Layer 2
l Tag: Tag
Aware
Issue 03 (2012-11-30)

502
OptiX OSN 7500 II/7500/3500/1500

NE
LSR
ID
13 MPLS PW APS
Port
Port Attribute
IP
Addre
ss/
Subn
et
Mask
of
Port
Functio
n
3-N1PEG8-1(PORT-1)
NNI
10.0.0.
1/255.
255.25
5.0
Interface
that
carries
the
working
PWs
(MSPW11_1
and MSPW22_1)
10.0.2.
1/255.
255.25
5.0
Interface
that
carries
the
protectio
n PWs
(MSPW33_1
and MSPW44_1)
10.0.0.
2/255.
255.25
5.0
Interface
that
carries
the
working
PWs
(MSPW11_1
and MSPW22_1)
10.2.2.
2/255.
255.25
5.0
Interface
that
carries
the
protectio
n PWs
(MSPW33_1
and MSPW44_1)
l Port mode:
Layer 3
l Tag: Tag
Aware
1-N1PEG8-1(PORT-1)
NE2
1.0.0.2
3-N1PEG8-1(PORT-1)
NNI
l Port mode:
Layer 3
l Tag: Tag
Aware
1-N1PEG8-1(PORT-1)
Issue 03 (2012-11-30)

503
OptiX OSN 7500 II/7500/3500/1500

NE
NE3
LSR
ID
1.0.0.3
Port
13 MPLS PW APS
IP
Addre
ss/
Subn
et
Mask
of
Port
Functio
n
3-N1PEG8-2(PORT-2)
10.0.1.
1/255.
255.25
5.0
Interface
that
carries
the
working
PWs
(MSPW11_2
and MSPW22_2)
1-N1PEG8-2(PORT-2)
10.0.3.
1/255.
255.25
5.0
Interface
that
carries
the
protectio
n PWs
(MSPW33_2
and MSPW44_2)
Interface
of ELine-1
and ELine-2 on
the RNC
side
10.0.1.
2/255.
255.25
5.0
Interface
that
carries
the
working
PWs
(MSPW11_2
and MSPW22_2)
3-N1PEG8-2(PORT-2)
Port Attribute
UNI
l Port mode:
Layer 2
l Tag: Tag
Aware
3-N1PEG8-1(PORT-1)
NNI
l Port mode:
Layer 3
l Tag: Tag
Aware
Issue 03 (2012-11-30)

504
OptiX OSN 7500 II/7500/3500/1500

NE
LSR
ID
13 MPLS PW APS
Port
Port Attribute
1-N1PEG8-1(PORT-1)
IP
Addre
ss/
Subn
et
Mask
of
Port
Functio
n
10.0.3.
2/255.
255.25
5.0
Interface
that
carries
the
protectio
n PWs
(MSPW33_2
and MSPW44_2)
Table 13-9 lists the parameter planning for tunnels carrying the PWs.
Table 13-9 Parameter planning for tunnels carrying PWs
Issue 03 (2012-11-30)
Paramet
er
Tunnel That
Carries the
Working PW
Between NE1
and NE2
Tunnel That
Carries the
Protection PW
Between NE1
and NE2
Tunnel That
Carries the
Working PW
Between NE2
and NE3
Tunnel That
Carries the
Protection PW
Between NE2
and NE3
Tunnel
ID
Tunnel
Name
NE1-NE2
working
NE1-NE2
protection
NE2-NE3
working
NE2-NE3
protection
Signaling
Type
Static
Static
Static
Static
Scheduli
ng Type
E-LSP
E-LSP
E-LSP
E-LSP
Bandwid
th
No restriction
No restriction
No restriction
No restriction
Advance
d
Attribute
of
Ingress
Node
NE1
NNI: 3N1PEG8-1
(PORT-1)
NE1
NNI: 1N1PEG8-1
(PORT-1)
NE2
NNI: 3N1PEG8-2
(PORT-2)
NE2
NNI: 1N1PEG8-2
(PORT-2)

505
OptiX OSN 7500 II/7500/3500/1500

13 MPLS PW APS
Paramet
er
Tunnel That
Carries the
Working PW
Between NE1
and NE2
Tunnel That
Carries the
Protection PW
Between NE1
and NE2
Tunnel That
Carries the
Working PW
Between NE2
and NE3
Tunnel That
Carries the
Protection PW
Between NE2
and NE3
Advance
d
Attribute
of Egress
Node
NE2
NNI: 3N1PEG8-1
(PORT-1)
NE2
NNI: 1N1PEG8-1
(PORT-1)
NE3
NNI: 3N1PEG8-1
(PORT-1)
NE3
NNI: 1N1PEG8-1
(PORT-1)
Table 13-10 lists the parameter planning for the E-Line services.
Table 13-10 Parameter planning for E-Line services
Parameter
Service Between NodeB 1 and

RNC
Service Between NodeB 2 and

RNC
Service ID
Service
Name
E-Line-1
E-Line-2
Direction
UNI-NNI
UNI-NNI
BPDU
Not transparently transmitted
Source Port
l NE1: 21-N1PETF8-1(PORT-1)
l NE3: 3-N1PEG8-1(PORT-1)
Source
VLANs
100
200
Bearer Type
PW
PW
Protection
Type
PW APS
Slave protection pair
Table 13-11 lists the parameter planning for the PWs.

Table 13-11 Parameter planning for PWs
Issue 03 (2012-11-30)
Param
eter
MS-PW 11
MS-PW 33
MS-PW 22
MS-PW 44
MSPW ID
11
33
22
44
Name
Working PW of ELine-1
Protection PW of
E-Line-1
Working PW of ELine-2
Protection PW of
E-Line-2

506
OptiX OSN 7500 II/7500/3500/1500

13 MPLS PW APS
Param
eter
MS-PW 11
MS-PW 33
MS-PW 22
MS-PW 44
Forwar
d/
Backw
ard PW
Forwar
d PW
(workin
g PW
from
NE1 to
NE2)
Backw
ard PW
(worki
ng PW
from
NE2 to
NE3)
Forwar
d PW
(protect
ion PW
from
NE1 to
NE2)
Backw
ard PW
(protec
tion
PW
from
NE2 to
NE3)
Forwar
d PW
(worki
ng PW
from
NE1 to
NE2)
Backwa
rd PW
(workin
g PW
from
NE2 to
NE3)
Forwar
d PW
(protect
ion PW
from
NE1 to
NE2)
Backw
ard PW
(protect
ion PW
from
NE2 to
NE3)
PW ID
PW
Signali
ng
Type
Static
Static
Static
Static
Static
Static
Static
Static
PW
Type
Etherne
t
Ethern
et
Etherne
t
Ethern
et
Etherne
t
Etherne
t
Etherne
t
Etherne
t
PW
Directi
on
Bidirect
ional
Bidirec
tional
Bidirect
ional
Bidirec
tional
Bidirec
tional
Bidirect
ional
Bidirec
tional
Bidirec
tional
PW
Incomi
ng
Label
16
20
30
40
50
60
70
80
PW
Outgoi
ng
Label
16
20
30
40
50
60
70
80
Tunnel
No.
1 (NE1NE2W
orking)
2
(NE2NE3W
orking)
3 (NE1NE2Pro
tection)
4
(NE2NE3Pr
otectio
n)
1 (NE1NE2W
orking)
2 (NE2NE3Wo
rking)
3 (NE1NE2Pr
otectio
n)
4 (NE2NE3Pr
otectio
n)
Peer
LSR ID
1.0.0.1
1.0.0.3
1.0.0.1
1.0.0.3
1.0.0.1
1.0.0.3
1.0.0.1
1.0.0.3
Table 13-12 lists the parameter planning for the PW APS protection groups.
Table 13-12 Parameter planning for PW APS protection groups
Issue 03 (2012-11-30)
Parameter
Protection Group of E-Line-1
Protection Type
PW APS
Slave protection pair

507
OptiX OSN 7500 II/7500/3500/1500

13 MPLS PW APS
Parameter
Protection Group ID
1 (the protection group is bound

with APS1)
Working PW ID
NE1: 1
NE1: 5
NE3: 2
NE3: 6
NE1: 3
NE1: 7
NE3: 4
NE3: 8
Protection PW ID
13.9.2 PW APS Configuration Process

Based on the example description, you can configure PW APS for E-Line-1 by performing the
following configuration operations.
Prerequisites
l
The E-Line service interface must be configured. For details on the configuration method,
see "Configuring an Ethernet Port" in the Configuration Guide (Packet Transport Plane).
The Layer 3 NNI must be configured. For details on the configuration method, see
"Configuring an Ethernet Port" in the Configuration Guide (Packet Transport Plane).
The static MPLS tunnel must be created. For details on how to configure a static MPLS
tunnel in an end-to-end manner, see "Configuring an MPLS Tunnel in an End-to-End
Mode" in the Configuration Guide (Packet Transport Plane); for details on how to
configure a static MPLS tunnel on a per-NE basis, see "Configuring an MPLS Tunnel on
a Per-NE Basis" in the Configuration Guide (Packet Transport Plane).
Context
For details on the parameter planning for the E-Line-1 service and the PW APS protection group
involved, see 13.9.1 Description of the Example.
This example focuses on the configuration method and parameters of a PW APS protection
group. For details on how to configure E-Line services, see "E-Line Services Carried by PWs"
in the Configuration Guide (Packet Transport Plane).
Procedure
Step 1 In the NE Explorer of NE1, create the E-Line-1 service from NE1 to NE3 and its PW APS
protection group. For details, see 13.8.1 Configuring PW APS Protection Groups.
1.
Create an E-Line service, and set the relevant parameters according to service planning.
For details, see Step 1 to Step 3 in "13.8.1 Configuring PW APS Protection Groups."
Set the parameters as follows:
l Set Service ID to 1.
l Set Service Name to E-Line-1.
l Set Direction to UNI-NNI.
l Set Source Port to 21-N1PETF8-1(PORT-1).
Issue 03 (2012-11-30)

508
OptiX OSN 7500 II/7500/3500/1500

13 MPLS PW APS
l Set Source VLANs to 100.

l Set Bearer Type to PW.
l Set Protection Type to PW APS.
2.
Configure PWs, and set the basic parameters of the working PW and protection PW. For
details, see Step 4 to Step 5 in "13.8.1 Configuring PW APS Protection Groups." Set
the parameters as follows:
l Set PW ID (working PW) to 1.
l Set PW ID (protection PW) to 3.
l Set PW Incoming Label/Source Port (working PW) to 16.
l Set PW Incoming Label/Source Port (protection PW) to 30.
l Set PW Outgoing Label/Source Port (protection PW) to 30.
l Set Tunnel No. (working PW) to 1(NE1-NE2Working).
l Set Tunnel No. (protection PW) to 3(NE1-NE2Protection).
l Set Peer LSR ID (working PW) to 1.0.0.2.
l Set Peer LSR ID (protection PW) to 1.0.0.2.
3.
Optional: In the QoS tab, set the parameters of QoS according to network planning. This
example does not involve QoS planning.
4.
In the Advanced Attributes tab, the parameters take the default values.
5.
In the Protection Group tab, set the parameters such as Protection Group ID and
Enabling Status. For details, see Step 6 in "13.8.1 Configuring PW APS Protection
Groups." Set the parameters as follows:
l Set Protection Group ID to 1.
l Set Enabling Status to Disabled.
l Set Protection Type to 1:1.
l Set Revertive Mode to Non-Revertive.
6.
Click OK. The protection group is created successfully.
protection group. For details, see 13.8.1 Configuring PW APS Protection Groups.
1.
For details, see Step 1 to Step 3 in "13.8.1 Configuring PW APS Protection Groups."
Set the parameters as follows:
l Set Source Port to 3-N1PEG8-1(PORT-1).
l Set Protection Type to PW APS.
2.
Issue 03 (2012-11-30)
details, see Step 4 to Step 5 in "13.8.1 Configuring PW APS Protection Groups." Set
the parameters as follows:
509
OptiX OSN 7500 II/7500/3500/1500

13 MPLS PW APS

l Set PW Outgoing Label/Source Port (protection PW) to 40.
3.
4.
5.
In the Protection Group tab, set the parameters such as Protection Group ID and
Enabling Status. For details, see Step 6 in "13.8.1 Configuring PW APS Protection
Groups." Set the parameters as follows:
l Set Protection Group ID to 1.
l Set Enabling Status to Disabled.
6.
Click OK. The protection group is created successfully.
Step 3 In the NE Explorer of NE2, create MS-PW 11 (working) and MS-PW 33 (protection) for ELine-1.
1.
Choose Configuration > Packet Configuration > MPLS Management > PW

2.
Click the MS PW tab. Click New.
3.
In the Create MS PW dialog box that is displayed, set the parameters of the working PW
of E-Line-1.
Issue 03 (2012-11-30)

510
OptiX OSN 7500 II/7500/3500/1500

13 MPLS PW APS
l Set ID to 11.
l Set Name to E-Line-1WorkingPW.
l Set Service Type to Ethernet Service.
l Set PW ID (forward PW) to 1. (The forward PW is the working PW1 from NE1 to
NE2.)
l Set PW ID (backward PW) to 2. (The backward PW is the working PW2 from NE2 to
NE3.)
l Set PW Signaling Type to Static. (In this example, the PW egress/ingress label is
manually configured.)
l Set PW Type to Ethernet.
l Set PW Incoming Label/Source Port (forward PW) to 16.
l Set PW Egress Label/Source Port (forward PW) to 16.
l Set PW Incoming Label/Source Port (backward PW) to 20.
l Set PW Egress Label/Source Port (backward PW) to 20.
l Set Tunnel Selection Mode to Manually. (In this example, the tunnel carrying PWs is
manually selected.)
l Set Tunnel No. (forward PW) to 1(NE1-NE2Working). (The tunnel carrying the
forward PW is MPLS tunnel 1 from NE1 to NE2.)
l Set Tunnel No. (backward PW) to 2(NE2-NE3Working). (The tunnel carrying the
backward PW is MPLS tunnel 2 from NE2 to NE3.)
l Set Peer LSR ID (forward PW) to 1.0.0.1. (The forward PW is the PW from NE1 to
NE2, and the Peer LSR ID is the LSR ID of NE1.)
Issue 03 (2012-11-30)

511
OptiX OSN 7500 II/7500/3500/1500

13 MPLS PW APS
l Set Peer LSR ID (backward PW) to 1.0.0.3. (The backward PW is the PW from NE2
to NE3, and the Peer LSR ID is the LSR ID of NE3.)
4.
5.
6.
Click OK. The MS-PW is created successfully.
7.
Perform the preceding operations to create the protection PW, that is, MS-PW 33.
l Set ID to 33.
l Set Name to E-Line-1ProtectionPW.
l Set PW ID (forward PW) to 3.
l Set PW ID (backward PW) to 4.
l Set Tunnel Selection Mode to Manually. (In this example, the tunnel carrying PWs is
manually selected.)
l Set Tunnel No. (forward PW) to 3(NE1-NE2Protection).
l Set Tunnel No. (backward PW) to 4(NE2-NE3Protection).
Step 4 In the NE Explorer of NE1 and NE3, start the APS protocol. For details, see 13.8.3 Starting the
APS Protocol.
Step 5 Set Detection Packet Type to FFD and Detection Packet Period(ms) to 3.3 ms for PW OAM
of the working PW and protection PW. For details, see 7.9.2 Setting the Parameters of PW
OAM.
----End
13.9.3 PW APS Slave Protection Pair Configuration Process

Based on the example description, you can configure the PW APS slave protection pair for ELine-2 by performing the following configuration operations.
Prerequisites
l
Issue 03 (2012-11-30)
The E-Line service interface must be configured. For details on the configuration method,
see "Configuring an Ethernet Port" in the Configuration Guide (Packet Transport Plane).
512
OptiX OSN 7500 II/7500/3500/1500

13 MPLS PW APS
The Layer 3 NNI must be configured. For details on the configuration method, see
"Configuring an Ethernet Port" in the Configuration Guide (Packet Transport Plane).
The static MPLS tunnel must be created. For details on how to configure a static MPLS
tunnel in an end-to-end manner, see "Configuring an MPLS Tunnel in an End-to-End
Mode" in the Configuration Guide (Packet Transport Plane); for details on how to
configure a static MPLS tunnel on a per-NE basis, see "Configuring an MPLS Tunnel on
a Per-NE Basis" in the Configuration Guide (Packet Transport Plane).
Context
For details on the parameter planning for the E-Line-2 service and PW APS slave protection
pair, see 13.9.1 Description of the Example.
This example focuses on the configuration method and parameters of a PW APS slave protection
pair. For details on how to configure E-Line services, see "E-Line Services Carried by PWs" in
the Configuration Guide (Packet Transport Plane).
Procedure
protection group. For details, see 13.8.2 Configuring Slave Protection Pairs of PW APS.
1.
For details, see Step 1 to Step 3 in "13.8.2 Configuring Slave Protection Pairs of PW
APS." Set the parameters as follows:
l Set Source Port to 21-N1PETF8-2(PORT-2).
l Set Protection Type to Slave Protection Pair.
2.
details, see Step 4 to Step 5 in "13.8.2 Configuring Slave Protection Pairs of PW
l Set PW Outgoing Label/Sink Port (protection PW) to 70.
Issue 03 (2012-11-30)

513
OptiX OSN 7500 II/7500/3500/1500

13 MPLS PW APS
3.
4.
5.
In the Protection Group tab, set the relevant parameters. For details, see Step 6 in "13.8.2
Configuring Slave Protection Pairs of PW APS." Set the parameters as follows:
l Set Protection Group ID to 1. (The working PW and protection PW of E-Line-2 share
the same source and sink as the created PW APS protection group APS1.)
6.
Click OK. The slave protection pair is created successfully.
Step 2 In the NE Explorer of NE3, create the E-Line-2 service from NE3 to NE1 and its PW APS slave
protection pair. For details, see 13.8.2 Configuring Slave Protection Pairs of PW APS.
1.
For details, see Step 1 to Step 3 in "13.8.2 Configuring Slave Protection Pairs of PW
l Set Source Port to 1-N1PEG8-1(PORT-1).
2.
details, see Step 4 to Step 5 in "13.8.2 Configuring Slave Protection Pairs of PW
l Set PW Outgoing Label/Sink Port (protection PW) to 80.
3.
4.
5.
In the Protection Group tab, set the relevant parameters. For details, see Step 6 in "13.8.2
Configuring Slave Protection Pairs of PW APS." Set the parameters as follows:
l Set Protection Group ID to 1. (The working PW and protection PW of E-Line-2 share
the same source and sink as the created PW APS protection group APS1.)
6.
Issue 03 (2012-11-30)
Click OK. The slave protection pair is created successfully.

514
OptiX OSN 7500 II/7500/3500/1500

13 MPLS PW APS
Step 3 In the NE Explorer of NE2, create MS-PW 22 (working) and MS-PW 44 (protection) for ELine-2.
1.
Choose Configuration > Packet Configuration > MPLS Management > PW

2.
Click the MS PW tab. Click New.
3.
Set the parameters of the working PW of E-Line-2.

l Set ID to 22.
l Set Name to E-Line-2WorkingPW.
l Set PW ID (forward PW) to 5. (The forward PW is the working PW5 from NE1 to
NE2.)
l Set PW ID (backward PW) to 6. (The backward PW is the working PW6 from NE2 to
NE3.)
l Set Tunnel selection mode to Manually. (In this example, the tunnel carrying PWs is
manually selected.)
l Set Tunnel No. (forward PW) to 1(NE1-NE2Working). (The tunnel carrying the
forward PW is MPLS tunnel 1 from NE1 to NE2.)
l Set Tunnel No. (backward PW) to 2(NE2-NE3Working). (The tunnel carrying the
backward PW is MPLS tunnel 2 from NE2 to NE3.)
4.
5.
6.
Click OK. The MS-PW is created successfully.
7.
Perform the preceding operations to create the protection PW, that is, MS-PW 44.
l Set ID to 44.
l Set Name to E-Line-2ProtectionPW.
l Set PW ID (forward PW) to 7.
l Set PW ID (backward PW) to 8.
Issue 03 (2012-11-30)

515
OptiX OSN 7500 II/7500/3500/1500

13 MPLS PW APS

l Set Tunnel selection mode to Manually. (In this example, the tunnel carrying PWs is
manually selected.)
l Set Tunnel No. (forward PW) to 3(NE1-NE2Protection).
l Set Tunnel No. (backward PW) to 4(NE2-NE3Protection).
----End
13.9.4 Verifying PW APS

PW APS can protect services carried by the working PW. After PW APS is configured, you
need to verify whether the configurations of PW APS are correct.
Prerequisites
l
The PW APS protection group must be created and the APS protocol must be started.
The working PW and protection PW must work properly.
Procedure
Step 1 Manually perform PW APS switching, and query the switchover status. For details, see 13.8.4
Performing External Switching of PW APS.
NOTE
When the working PW and protection PW work properly, the status is Available. When the PWs fail to
work properly, the status is Unavailable. In this case, you need handle the fault. Double-click PW ID. In
the PW Management dialog box that is displayed, check the PW running status, and rectify the fault
according to the PW status.
Step 2 Choose Configuration > Packet Configuration > Ethernet Service Management > E-Line
Service from the Function Tree.
Step 3 Select the service in the protection group, and choose Browse Current Alarms from the shortcut
menu. Check whether any service alarm is reported after protection switching.
l
If the service alarm is reported, see the Alarms And Performance Events Reference to clear
the alarm.
If no service alarm is reported, go to the next step.
Step 4 Check the service connectivity by means of the ETH-OAM function. For details, see 7.9.2
Setting the Parameters of PW OAM.
l
Issue 03 (2012-11-30)
If the service is normal, it indicates that the PW APS protection group is configured
correctly.
516
OptiX OSN 7500 II/7500/3500/1500

13 MPLS PW APS
If the service is abnormal, it indicates that the protection switching fails.
----End
Follow-up Procedure
After the verification is completed, perform Manual Switching to Working to switch the
service back to the working PW.
13.10 Configuration Example (PW FPS)

This section uses an example to describe the configuration of PW FPS according to network
planning.

This section describes the functional requirement, networking diagram, and parameter planning.

As shown in Figure 13-13, data services are configured between the NodeB and the RNC, and
reliability are required on services on the UNI side (RNC) and NNI side.
l
E-Line services are configured for NE1, NE2, and NE3 for transmitting data services
between the NodeB and RNC.
PW OAM are enabled on NE1, NE2, and NE3 for NNI service fault detection.
PW FPS is configured on NE1 for NNI service protection.
NE2 and NE3 are IWF-enabled, that is, Associate with AC Status for PW OAM is set to
enabled. Fault information on the UNI side is transparently transmitted to NE1, triggering
PW FPS switching and realizing UNI service protection.
Issue 03 (2012-11-30)

517
OptiX OSN 7500 II/7500/3500/1500

13 MPLS PW APS
Figure 13-13 Networking diagram of PW FPS

NNI side
UNI side
3-N1PEG8-1
(PORT-1)
21-N1PETF8-1
(PORT-1)
IWF
1-N1PEG8-1
(PORT-1)
3-N1PEG8-1
(PORT-1)
A
PSN
NE2
PW FPS
NodeB
NE1
IWF
3-N1PEG8-2
(PORT-2)
S
3-N1PEG8-1
(PORT-1)
RNC
1-N1PEG8-1
(PORT-1)
NE3
Working PW
Protection PW
A
As shown in Figure 13-14, one E-Line service, E-Line-1, is transmitted on the trails
NodeBNE1NE2RNC and NE3RNC.
Figure 13-14 PW FPS planning
E-Line-1
E-Line-1
PW 1
A
NE2
PW FPS
NodeB
NE1
E-Line-1
S
PW 2
RNC
NE3
E-Line service
Working PW
Protection PW
A
S

Table 13-13 lists the service information.

Issue 03 (2012-11-30)

518
OptiX OSN 7500 II/7500/3500/1500

13 MPLS PW APS
Table 13-13 Service information

Service
PW
MPLS Tunnel
Protection Attribute
E-Line-1
PW1 (working PW)
Tunnel1 (the MPLS

tunnel that carries the
working PW)
PW FPS protection
group
PW2 (protection PW)
Tunnel2 (the MPLS

tunnel that carries the
protection PW)
Service Planning
NE1, NE2, and NE3 are OptiX OSN 3500s in this example. Table 13-14 lists the NE parameter
planning.
Table 13-14 NE parameter planning
NE
LSR
ID
Port
Port Attribute
IP
Addre
ss/
Subn
et
Mask
of
Port
Functio
n
NE1
1.0.0.1
UNI
Interface
of ELine-1 on
the
NodeB
side
10.0.0.
1/255.
255.25
5.252
Interface
that
carries
working
PW1
10.0.1.
1/255.
255.25
5.252
Interface
that
carries
protectio
n PW2
Interface
of ELine-1 on
the RNC
side
l Port mode:
Layer 2
l Tag: Tag
Aware
3-N1PEG8-1(PORT-1)
NNI
l Port mode:
Layer 3
l Tag: Tag
Aware
3-N1PEG8-2(PORT-2)
NE2
1.0.0.2
1-N1PEG8-1(PORT-1)
UNI
l Port mode:
Layer 2
l Tag: Tag
Aware
Issue 03 (2012-11-30)

519
OptiX OSN 7500 II/7500/3500/1500

NE
LSR
ID
13 MPLS PW APS
Port
Port Attribute
IP
Addre
ss/
Subn
et
Mask
of
Port
Functio
n
3-N1PEG8-1(PORT-1)
NNI
10.0.0.
2/255.
255.25
5.252
Interface
that
carries
working
PW1
Interface
of ELine-1 on
the RNC
side
10.0.1.
2/255.
255.25
5.252
Interface
that
carries
protectio
n PW2
l Port mode:
Layer 3
l Tag: Tag
Aware
NE3
1.0.0.3
1-N1PEG8-1(PORT-1)
UNI
l Port mode:
Layer 2
l Tag: Tag
Aware
3-N1PEG8-1(PORT-1)
NNI
l Port mode:
Layer 3
l Tag: Tag
Aware
Table 13-15 lists the parameter planning for MPLS tunnels carrying PWs.
Table 13-15 Parameter planning for MPLS tunnels carrying PWs
Issue 03 (2012-11-30)
Parameter
MPLS Tunnel That Carries the

Working PW Between NE1 and
NE2
MPLS Tunnel That Carries

the Protection PW Between
NE1 and NE3
Tunnel ID
Tunnel Name
NE1-NE2(Tunnel1)
NE1-NE3(Tunnel2)
Signaling Type
Static CR
Static CR
Scheduling Type
E-LSP
E-LSP
Bandwidth
No restriction
No restriction
Advanced
Attribute of Ingress
Node
NE1
Out Interface: 3-N1PEG8-1
(PORT-1)
NE1
(PORT-2)
Outgoing Label: 99
Outgoing Label: 101
Reverse Incoming Label: 100

520
OptiX OSN 7500 II/7500/3500/1500

13 MPLS PW APS
Parameter
MPLS Tunnel That Carries the

Working PW Between NE1 and
NE2
MPLS Tunnel That Carries

the Protection PW Between
NE1 and NE3
Advanced
Attribute of Egress
Node
NE2
(PORT-1)
NE3
(PORT-1)
Incoming Label: 99
Incoming Label: 101
Reverse Outgoing Label: 100
Table 13-16 lists the parameter planning for the E-Line services.
Table 13-16 Parameter planning for E-Line services
Parameter
E-Line Services on NE1, NE2, and NE3
Service ID
Service Name
E-Line-1
Direction
UNI-NNI
BPDU
Source Port
Source VLANs
100
Bearer Type
PW
Protection Type
NE1: PW FPS
NE2 and NE3: Unprotected
Table 13-17 lists the parameter planning for PWs.

Table 13-17 Parameter planning for PWs
Issue 03 (2012-11-30)
Parameter
Working PWs of NE1 and

NE2
Protection PW of NE1 and

Working PW of NE3
PW ID
PW Signaling Type
Static
Static
PW Type
Ethernet
Ethernet
PW Direction
Bidirectional
Bidirectional

521
OptiX OSN 7500 II/7500/3500/1500

13 MPLS PW APS
Parameter
Working PWs of NE1 and

NE2
Protection PW of NE1 and

Working PW of NE3
PW Encapsulation Type
MPLS
MPLS
PW Incoming Label
16
17
PW Outgoing Label
16
17
Tunnel No.
1(NE1-NE2(Tunnel1))
2(NE1-NE3(Tunnel2))
Peer LSR ID
1.0.0.2
1.0.0.3
Table 13-18 lists the parameter planning for the PW FPS protection groups.
Table 13-18 Parameter planning for PW FPS protection groups
Parameter
PW FPS Protection Group on NE1
Protection Type
PW FPS
Protection Group ID
Enabling Status
Enabled
Working PW ID
Protection PW ID
Revertive Mode
Revertive Mode
Switchover WTR Time (min)
Switchover Hold-Off Time (min)
Detection Method
OAM
Table 13-19 lists the parameter planning for the PW OAM.

Table 13-19 Parameter planning for PW OAM
Parameter
Working PWs and Protection PWs of

NE1, NE2, and NE3
OAM Status
Enabled
Associate with AC Status
NE1: Disabled
NE2 and NE3: Enabled
Issue 03 (2012-11-30)
Detection Mode
Adaptive
FFD

522
OptiX OSN 7500 II/7500/3500/1500

13 MPLS PW APS
Parameter
Working PWs and Protection PWs of

NE1, NE2, and NE3
Detection Packet Period (ms)
3.3
NE1
l Working PW: 1.0.0.2
l Protection PW: 1.0.0.3
NE2 and NE3: 10.0.0.1
NE1
l Working PW: 1
l Protection PW: 2
NE2: 1
NE3: 2
13.10.2 PW FPS Configuration Process

Based on the example description, you can configure PW FPS for E-Line by performing the
following configuration operations.
Prerequisites
l
You are familiar with the networking, requirements, and service planning of the example.
Configure PW FPS as follows:

1.
Configure the LSR IDs of NE1, NE2, and NE3.
2.
Configure Ethernet ports on NE1, NE2, and NE3.
3.
Create bidirectional tunnels between NE1 and NE2, and between NE1 and NE3 in end-toend mode. For details, see Configuring a Static and Bidirectional MPLS Tunnel in End-toEnd Mode in the Configuration Guide (Packet Transport Domain).
4.
Configure UNI-NNI E-Line services for NE1, NE2, and NE3 in per-NE mode and create
a PW FPS protection group on NE1.
5.
Set OAM Status and Associate with AC Status to Enabled for the PW OAM of NE2 and
NE3.
NOTE
In the following steps, the parameters take default values unless otherwise specified.
Procedure
Step 1 Configure the LSR IDs of NE1, NE2, and NE3. For details, see Configuring LSR ID in the
Configuration Guide (Packet Transport Domain).
l NE1 LSR ID: 1.0.0.1
l NE2 LSR ID: 1.0.0.2
Issue 03 (2012-11-30)

523
OptiX OSN 7500 II/7500/3500/1500

13 MPLS PW APS
l NE3 LSR ID: 1.0.0.3

Step 2 Configure Ethernet ports on NE1, NE2, and NE3. For details, see Configuring an Ethernet Port
in the Configuration Guide (Packet Transport Domain).
NE
NE
1
NE
2
NE
3
Port
Basic
Attributes
Layer 3 Attributes
Ena
ble
Port
Port
Mod
e
Enabl
e
Tunne
l
Specif
y IP
IP
Addre
ss
IP Mask
Enab
led
Laye
r2
3-N1PEG8-1
(PORT-1)
Laye
r3
Enable
d
Manual
ly
10.0.0.
1
255.255.255.2
52
3-N1PEG8-2
(PORT-2)
Laye
r3
Enable
d
Manual
ly
10.0.1.
1
255.255.255.2
52
1-N1PEG8-1
(PORT-1)
Laye
r2
3-N1PEG8-1
(PORT-1)
Laye
r3
Enable
d
Manual
ly
10.0.0.
2
255.255.255.2
52
1-N1PEG8-1
(PORT-1)
Laye
r2
3-N1PEG8-1
(PORT-1)
Laye
r3
Enable
d
Manual
ly
10.0.1.
2
255.255.255.2
52
21-N1PETF8-1
(PORT-1)
Step 3 Create bidirectional tunnels between NE1 and NE2, and between NE1 and NE3 in end-to-end
mode. For details, see Configuring a Static and Bidirectional MPLS Tunnel in End-to-End Mode
in the Configuration Guide (Packet Transport Domain).
Issue 03 (2012-11-30)
Parameter
MPLS Tunnel Between

NE1 and NE2
MPLS Tunnel Between NE1

and NE3
Tunnel ID
Tunnel Name
NE1-NE2(Tunnel1)
NE1-NE3(Tunnel2)
Protocol Type
MPLS
MPLS
Signaling Type
Static CR
Static CR
Service Direction
Bidirectional
Bidirectional
Protection Type
Protection-Free
Protection-Free
Scheduling Type
E-LSP
E-LSP
Bandwidth
No restriction
No restriction

524
OptiX OSN 7500 II/7500/3500/1500

13 MPLS PW APS
Parameter
MPLS Tunnel Between

NE1 and NE2
MPLS Tunnel Between NE1

and NE3
Advanced Attribute
of Ingress Node
NE1
(PORT-1)
NE1
(PORT-2)
Outgoing Label: 99
Outgoing Label: 101
NE2
(PORT-1)
NE3
(PORT-1)
Incoming Label: 99
Incoming Label: 101
Advanced Attribute
of Egress Node
Step 4 Configure UNI-NNI E-Line services for NE1, NE2, and NE3 in per-NE mode and create a PW
FPS protection group on NE1.
1.
Configure UNI-NNI E-Line services on NE1 and create a PW FPS protection group on
NE1. For details, see Step 1 to Step 8 in 13.8.5 Configuring PW FPS Protection
Groups.
Table 13-20 Parameter setting for new E-Line services (NE1)
Parameter
Value
Service ID
Service Name
E-Line-1
Direction
UNI-NNI
BPDU
Source Port
Source VLANs
100
Bearer Type
PW
Protection Type
PW FPS
Table 13-21 Parameters settings for PW basic attributes (NE1)
Issue 03 (2012-11-30)
Parameter
Working PW
Protection PW
PW ID
PW Signaling Type
Static
Static
PW Type
Ethernet
Ethernet
PW Direction
Bidirectional
Bidirectional

525
OptiX OSN 7500 II/7500/3500/1500

13 MPLS PW APS
Parameter
Working PW
Protection PW
PW Encapsulation
Type
MPLS
MPLS
PW Incoming Label
16
17
PW Outgoing Label
16
17
Tunnel No.
1(NE1-NE2(Tunnel1))
2(NE1-NE3(Tunnel2))
Peer LSR ID
1.0.0.2
1.0.0.3
Table 13-22 Parameter settings for protection group (NE1)

Parameter
Value
Protection Type
PW FPS
Protection Group ID
Enabling Status
Enabled
Working PW ID
Protection PW ID
Revertive Mode
Revertive Mode
Switchover WTR Time (min)
Switchover Hold-Off Time (min)
Detection Method
OAM
Table 13-23 Parameter settings for PW OAM (NE1)
Issue 03 (2012-11-30)
Parameter
Working PW
Protection PW
OAM Status
Enabled
Enabled
Detection Mode
Adaptive
Adaptive
Detection Packet
Type
FFD
FFD
Detection Packet
Period (ms)
3.3
3.3
LSR ID to be
Received
1.0.0.2
1.0.0.3
PW ID to be
Received

526
OptiX OSN 7500 II/7500/3500/1500

2.
13 MPLS PW APS
Configure UNI-NNI E-Lines services for NE2 and NE3. For details, see Configuring UNINNI E-Line Services Carried by PWs on a Per-NE Basis in the Configuration Guide (Packet
Transport Domain).
Table 13-24 Parameter settings for new E-Line services (NE2 and NE3)
Parameter
NE2
NE3
Service ID
Service Name
E-Line-1
E-Line-1
Direction
UNI-NNI
UNI-NNI
BPDU
Source Port
1-N1PEG8-1(PORT-1)
1-N1PEG8-1(PORT-1)
Source VLANs
100
100
Bearer Type
PW
PW
Protection Type
Unprotected
Unprotected
Table 13-25 Parameters settings for PW basic attributes (NE2 and NE3)
Parameter
NE2
NE3
PW ID
PW Signaling Type
Static
Static
PW Type
Ethernet
Ethernet
PW Direction
Bidirectional
Bidirectional
PW Encapsulation
Type
MPLS
MPLS
PW Incoming Label
16
17
PW Outgoing Label
16
17
Tunnel No.
1(NE1-NE2(Tunnel1))
2(NE1-NE3(Tunnel2))
Peer LSR ID
1.0.0.2
1.0.0.3
Step 5 Set OAM Status and Associate with AC Status to Enabled for the PW OAM of NE2 and
NE3.For details, see 7.9.1 Enabling PW OAM and 7.9.2 Setting the Parameters of PW
OAM.
Issue 03 (2012-11-30)

527
OptiX OSN 7500 II/7500/3500/1500

13 MPLS PW APS
Table 13-26 Parameter settings of PW OAM (NE2 and NE3)

Parameter
NE2
NE3
OAM Status
Enabled
Enabled
Associate with AC Status
Enabled
Enabled
Detection Mode
Adaptive
Adaptive
FFD
FFD
Detection Packet Period

(ms)
3.3
3.3
10.0.0.1
10.0.0.1
----End
13.10.3 Verifying PW FPS

PW FPS can protect services carried by the working PW. After PW FPS is configured, you need
to verify whether the configurations of PW FPS are correct.
Prerequisites
l
PW FPS is configured according the configuration example.
The working PW and protection PW must work properly.
Procedure
Step 1 Manually perform PW FPS switching, and query the switchover status. For details, see 13.8.4
Performing External Switching of PW APS.
NOTE
When the working PW and protection PW work properly, the status is Available. When the PWs fail to
work properly, the status is Unavailable. In this case, you need to handle the fault. Double-click PW ID.
In the PW Management dialog box that is displayed, check the PW running status, and rectify the fault
according to the PW status.
Step 2 Choose Configuration > Packet Configuration > Ethernet Service Management > E-Line
Service from the Function Tree.
Step 3 Right-click the service in the protection group, and choose Browse Current Alarms from the
shortcut menu. Check whether any service alarm is reported after protection switching.
l
If any service alarms are reported, refer to the Alarms and Performance Events Reference
to clear the alarm.
If no service alarm is reported, go to the next step.
Step 4 Check the service connectivity by means of the ETH-OAM function. For details, see 6.3.7
Configuring Ethernet Service OAM.
Issue 03 (2012-11-30)

528
OptiX OSN 7500 II/7500/3500/1500

13 MPLS PW APS
If the service is normal, it indicates that the PW FPS protection group is configured
correctly.
If the service is abnormal, it indicates that the protection switching fails.
----End
Follow-up Procedure
After the verification is complete, perform Manual Switching to Working to switch the service
back to the working PW.

This topic describes the alarms and performance events that are related to the MPLS PW APS.

This topic describes the alarms related to PW APS.
Table 13-27 lists the alarms that are related to the PW APS.
Table 13-27 Alarms related to PW APS
Issue 03 (2012-11-30)
Alarm Name
Meaning
PWAPS_TYPE_MISMATCH
The PWAPS_TYPE_MISMATCH is an alarm indicating that the

local NE and the opposite NE are configured with different PW
protection types. This alarm is reported when the PW protection
type indicated in the received Automatic Protection Switching
(APS) frame is different from that specified on the local NE.
PWAPS_PATH_MISMATCH
The PWAPS_PATH_MISMATCH is an alarm indicating that the

local NE and the opposite NE are configured with different
working and protection paths of the PW APS protection group.
This alarm is reported when the local NE and the opposite NE are
configured with different working and protection paths of the PW
APS protection group.
PWAPS_SWITCH_FAI
L
The PWAPS_SWITCH_FAIL is an alarm indicating a switching

failure of the PW APS protection group. This alarm is reported
when the request signals in the transmitted Automatic Protection
Switching (APS) frame are different from the bridge signals in
the received APS frame and this symptom lasts for 50 ms.
PWAPS_LOST
The PWAPS_LOST is an alarm indicating that the PW Automatic

Protection Switching (APS) frames are lost. This alarm is reported
when no PW APS frame is received from the protection channel.

529
OptiX OSN 7500 II/7500/3500/1500

13 MPLS PW APS

There are no performance events that are related to the MPLS PW APS function. The abnormal
event related to the MPLS PW APS function is the reporting of the PW APS protection.
Reporting of the PW APS protection switching indicates that PW APS protection switching
occurs.
13.12 Parameter Description: MPLS PW APS

13.12.1 Parameter Description: PW APS

Table 13-28 PW APS parameter description
Field
Value
Description
Protection Group ID
1 to 1024
Specifies the ID of a
protection group.
On the OptiX OSN 1500, the

value ranges from 1 to 128.
Issue 03 (2012-11-30)
If the working PW and

protection PW of a protection
pair share the same source
and sink with the working
PW and protection PW of a
PW APS protection group.
The ID of the protection pair
takes the ID of the PW APS
protection group. That is, the
ID of a slave protection pair
takes the ID of the PW APS
protection group to which it
is bound.
Protection Type
No Protection, PW APS,
Slave Protection Pair, PW
FPS
Indicates the protection type

of the protection group.
Working PW ID
1 to 4294967295
Indicates the ID of the

working PW of the created
service.
Protection PW ID
1 to 4294967295
Indicates the ID of the

protection PW of the created
service.

530
OptiX OSN 7500 II/7500/3500/1500

13 MPLS PW APS
Field
Value
Description
Protection Mode
1+1, 1:1
When the protection type is 1

+1, services are dually
transmitted and selectively
received; when the protection
type is 1:1, services are singly
transmitted and received.
NOTE
l When Protection Type is
PW FPSor No Protection,
this parameter is grayed.
Switchover Mode
Single-ended switching,
Dual-ended switching
Indicates the switchover

mode of the protection group.
NOTE
l When Protection Mode is
1:1, Switchover Mode
always takes Dual-ended
switching
l When Protection Mode is
PW FPS or No
Protection, this parameter
is grayed.
Restoration Mode
Specifies whether the service

is switched back to the
working PW after the fault in
the working PW is rectified.
After the fault in the working
PW is rectified, the service is
switched back to the working
PW when Restoration
Mode is set to Revertive, and
the service is still transmitted
in the protection PW when
Restoration Mode is set to
Non-Revertive.
NOTE
When Protection Mode is No
Protection, this parameter is
grayed.
Issue 03 (2012-11-30)

531
OptiX OSN 7500 II/7500/3500/1500

13 MPLS PW APS
Field
Value
Description
Switchover Restoration
Time(m)
1 to 12
Specifies the switchover

restoration time.
Default value: 1
It refers to the period after the

working PW is restored to
normal and before the service
is switched from the
protection PW to the working
PW.
This parameter helps to
prevent frequent switching
events before the working
PW becomes stable.
NOTE
grayed.
Switchover Delay Time

(100ms)
0 to 100
Default value: 0
Specifies the switchover

delay time.
After the switchover delay
time is specified, switching
does not occur immediately
after the switching condition
is detected; instead,
switching occurs after the
switching condition is still
detected even when the
preset switchover delay time
elapses.
This parameter helps to
prevent unnecessary
switching due to a transient
fault.
NOTE
grayed.
Issue 03 (2012-11-30)
Enabling Status
Enabled, Disabled
Indicates the enabling status

of the protection group
protocol.
Deployment Status
Deployed, Undeployed
Indicates the current

deployment status of a PW.

532
OptiX OSN 7500 II/7500/3500/1500

13 MPLS PW APS
Field
Value
Description
Switching State
l Normal\(No Request for

Working\)
Indicates the switchover

mode of a protection group.
l Normal\(No Request for

Protection\)
l Lockout
l Forced Switching
l Invalid working PW\
(because the OAM
generates an SF alarm\)
l Invalid protection PW\
(because the OAM
l Degraded working PW\
(because the OAM
l Degraded protection PW\
(because the OAM
l Manual Switching\
(Protection to Working\)
l Manual Switching\
(Working to Protection\)
l WTR
l DNR
l Exercise Switching\
l Exercise Switching\
l Reverse Request\
l Reverse Request\
Protocol Status
Enabled, Disabled
Specifies the enabling status

of the protection protocol.
When Protocol Status is set
to Enabled, the protection
group takes effect.
Issue 03 (2012-11-30)
Working Path Status
Available, Unavailable
Indicates the status of the

working path in a protection
group.
Protection Path Status
Available, Unavailable
Indicates the status of the

protection path in a
protection group.

533
OptiX OSN 7500 II/7500/3500/1500

13 MPLS PW APS
13.12.2 Parameter Description: MS-PW

This topic describes the parameters required for configuring MS-PWs.
Table 13-29 MS-PW parameter description
Field
Value
Description
ID
1 to 4294967295
Specifies the ID of an MS-PW.

The ID of an MS-PW is globally unique.
Name
For example, mspw01
Specifies the name of an MS-PW.
MTU(byte)
46 to 9000
Specifies the maximum transmission unit of an

MS-PW.
This parameter is set according to network
planning.
Service Type
Ethernet Service, CES

Service, PTP Clock
Service, TOP Clock
Service
Specifies the type of services carried by an MSPW.
PW ID
1 to 4294967295
l The forward PW refers to the PW from the

service source to the local NE along the
service positive direction.
l The backward PW refers to the PW from the
local NE to the service sink along the positive
service direction.
PW Signaling
Type
Static
When the PW egress/ingress label is set

manually, PW Signaling Type takes Static.
PW Type
Ethernet, Ethernet
Tagged
l Ethernet: The C-VLAN tag in the user packet

is encapsulated into the PW and then
transparently transmitted to the downstream
NE.
l Ethernet tagged: After Request VLAN is set,
one more VLAN tag is added to the user
packet.
Issue 03 (2012-11-30)
PW Ingress
Label/Source
Port
16 to 1068575
Specifies the number of the PW ingress label.
PW Egress
Label/Sink
Port
16 to 1068575
Specifies the number of the PW egress label.
On the OptiX OSN

1500, the value ranges
from 16 to 32768.
The PW egress label is globally unique.
On the OptiX OSN

1500, the value ranges
from 16 to 32768.

534
OptiX OSN 7500 II/7500/3500/1500

Issue 03 (2012-11-30)
13 MPLS PW APS
Field
Value
Description
Tunnel
Selection
Mode
Manually, Auto Select
l Manually: The tunnel carrying the PW is

selected manually.
Tunnel Type
MPLS
This parameter is set according to network

planning.
Tunnel
For example, 1
Specifies the ID of the tunnel carrying the PW.
Opposite LSR
ID
For example,
10.70.71.123
Specifies the opposite LSR ID of the PW.
l Auto Select: The equipment automatically

selects a tunnel that meets the bandwidth
requirement according to the tunnel selection
policy.

535
OptiX OSN 7500 II/7500/3500/1500

14 MPLS Tunnel APS
14
MPLS Tunnel APS
About This Chapter

In the case of MPLS Tunnel APS, an MPLS tunnel is set to protect the working tunnel. In this
case, when the working tunnel fails, services are switched to the protection tunnel for
transmission and thus to realize the service protection.
14.1 Introduction to MPLS Tunnel APS
MPLS Tunnel APS is a network protection mechanism. In the case of MPLS Tunnel APS, a
protection tunnel is created to protect the working tunnel when the working tunnel fails.
14.2 Basic Concepts
Basic concepts related to the MPLS Tunnel APS protection include the switching mode,
revertive mode, wait-to-restore (WTR) time, hold-off time, and protocol state.
14.3 Specifications
This section describes the capacity of the OptiX OSN equipment for supporting MPLS tunnel
APS.
This topic describes the standards and protocols that MPLS Tunnel APS complies with.
14.5 Availability
The MPLS tunnel APS function requires the support of the applicable equipment, boards, and
software.
This section describes the limitations on and precautions for MPLS tunnel APS in the network
14.7 Principles
This topic describes the functions of MPLS Tunnel APS in terms of the basic principles,
protection attributes, protection rules, and switching impact.
To realize the MPLS Tunnel APS function, you need to configure two different tunnels with the
same source and sink but different routes. When the working tunnel is faulty, services are
switched to the protection tunnel that is previously created.
14.9 Configuring an MPLS Tunnel APS Protection Group
Issue 03 (2012-11-30)

536
OptiX OSN 7500 II/7500/3500/1500

14 MPLS Tunnel APS
You can configure a 1+1 or 1:1 MPLS tunnel APS protection group to protect MPLS tunnels.
This task requires you to configure the protection group on the source and sink NEs of the MPLS
tunnel.
14.10 MPLS Tunnel APS Configuration Case
This section describes an MPLS Tunnel APS configuration case. The configuration case covers
service planning and configuration process.
14.11 Verifying the MPLS Tunnel APS
This topic describes how to verify and ensure that the configuration data of the MPLS Tunnel
APS is correct after the MPLS Tunnel APS is configured.
This topic describes the symptom of common faults when the MPLS Tunnel APS function is
enabled and the solution to the relevant fault.
14.14 Parameter Description: MPLS Tunnel APS
This topic describes the parameters required for configuring MPLS tunnel APS.
Issue 03 (2012-11-30)

537
OptiX OSN 7500 II/7500/3500/1500

14 MPLS Tunnel APS
14.1 Introduction to MPLS Tunnel APS

MPLS Tunnel APS is a network protection mechanism. In the case of MPLS Tunnel APS, a
protection tunnel is created to protect the working tunnel when the working tunnel fails.
Purpose and Benefit

The purpose of adopting the MPLS Tunnel APS mechanism is to protect certain important
working tunnels in the network and thus preventing service interruption in the case of the tunnel
failure.
The APS mechanism can determine whether to perform switching based on detection at the
physical layer and the link layer.
l
At the physical layer, the loss of signal is detected in microseconds.
At the link layer, the detection is conducted by MPLS OAM in 10 ms. Set Detection Packet
Period to 3.3 ms so that the protection switching time is less than 50 ms.
In MPLS Tunnel APS, detection at the link layer is performed by MPLS OAM. Thus, you must
set the MPLS OAM parameters for relevant tunnels before configuring MPLS Tunnel APS.
14.2 Basic Concepts

Basic concepts related to the MPLS Tunnel APS protection include the switching mode,
revertive mode, wait-to-restore (WTR) time, hold-off time, and protocol state.
APS
The automatic protection switching (APS) protocol is used to coordinate actions of the source
and the sink in the case of bidirectional protection switching. By the APS protocol, the source
and the sink cooperate with each other to perform functions such as protection switching,
switching delay, and WTR function.
According to ITU-T Y.1720, the source and the sink both need to select channels in the APS.
In this case, the APS protocol is required for coordination. In the case of bidirectional protection
switching, the APS protocol needs to be used regardless of the revertive mode.
The APS protocol packet is always transmitted through the protection tunnel. Then, the
equipment at either end knows that the tunnel from which the APS protocol is received is the
protection tunnel of the opposite end and thus to determine whether the configuration about the
working tunnel and the protection tunnel is consistent at the two ends.
When the equipment cannot receive any APS packet, services should be always transmitted and
received from the working tunnel.
Switching Mode
MPLS Tunnel APS provides two switching modes, that is, single-ended switching and dualended switching.
In the case of single-ended switching, when one end detects a fault, it only performs switching
on the local end and does not instruct the opposite end to perform any switching.
Issue 03 (2012-11-30)

538
OptiX OSN 7500 II/7500/3500/1500

14 MPLS Tunnel APS
In the case of dual-ended switching, when one end detects a fault, it performs switching on the
local end and also instructs the opposite end to perform switching.
Single-ended switching does not require the APS protocol for negotiation and it features rapid
and stable switching.
Dual-ended switching ensures that the services are transmitted in a consistent channel, which
facilitates service management.
Revertive Mode
The MPLS Tunnel APS function supports two revertive modes, that is, revertive mode and nonrevertive mode.
In the non-revertive mode, services are not switched from the protection tunnel to the working
tunnel even the working tunnel is restored to the normal state.
In the revertive mode, services are switched from the protection tunnel to the original working
tunnel if the working tunnel is restored to the normal state within the WTR time.
WTR Time
The WTR time refers to the period from the time when the original working tunnel is restored
to the time when the services are switched from the protection tunnel to the original working
tunnel.
In certain scenarios, the state of the working tunnel is unstable. In this case, setting the WTR
time can prevent frequent switching of services between the working tunnel and the protection
tunnel.
Hold-off Time
The hold-off time refers to the period from the time when the equipment detects a fault to the
time when the switching operation is performed.
When the equipment is configured with the MPLS Tunnel APS protection and other protection,
setting the hold-off time can ensure that other protection switching operations are performed
first.
Protocol State
The protocol state indicates whether the APS protocol of the protection group is valid currently.
In the case of configuring the MPLS Tunnel APS protection, the protocol state is disabled by
default. If you enable the APS protocol at the local NE first and then the opposite NE when
configuring the MPLS Tunnel APS protection, the opposite NE may have an anomaly in
receiving services. After the MPLS Tunnel APS protection group is configured at the two ends,
start protocol.
14.3 Specifications
This section describes the capacity of the OptiX OSN equipment for supporting MPLS tunnel
APS.
Table 14-1 provides specifications associated with MPLS tunnel APS.
Issue 03 (2012-11-30)

539
OptiX OSN 7500 II/7500/3500/1500

14 MPLS Tunnel APS
Table 14-1 Specifications associated with MPLS tunnel APS

Item
Specifications
Support capability
l OptiX OSN 7500 II: 4K

l OptiX OSN 7500/3500:
N4GSCC: 1K
N6GSCC: 4K
Switching Type

Revertive Mode
l Revertive
l Non-revertive
l Revertive: 1 minute to 12 minutes, 5 minute by default.
WTR time
l Non-revertive: Switching Protocol
APS
Switching Mode
l Clear switching
l Locked switching
l Forced switching
l Automatic switching
l Manual switching
Switching Time
50 ms
Switching Delay Time
0s to 10s (0s by default), which can be set at a step length of 100

ms
Switching Condition
(Any of the following
conditions triggers the
switching)
l The board has a hardware or software failure.

l A cold reset is performed on the board.
l A switching command is manually issued.
l A working tunnel failure is detected by MPLS OAM.

This topic describes the standards and protocols that MPLS Tunnel APS complies with.
The MPLS Tunnel APS complies with ITU-T Y.1720 and ITU-T G.8131.
Issue 03 (2012-11-30)

540
OptiX OSN 7500 II/7500/3500/1500

14 MPLS Tunnel APS
14.5 Availability
The MPLS tunnel APS function requires the support of the applicable equipment, boards, and
software.
Version Support
Product Name
Applicable Version
OptiX OSN 1500/3500
T2000
U2000
Product Name
Applicable Version
OptiX OSN 1500/3500/7500
U2000
Product Name
Applicable Version
OptiX OSN 1500/3500/7500/7500 II
U2000
Hardware Support
Issue 03 (2012-11-30)
Board Type
Version
N1PEG16
OptiX OSN 3500
N1PEX1
OptiX OSN 3500
N1PETF8
OptiX OSN 3500/7500
R1PEFS8
Q1PEGS2
R1PEGS1
N1PEG8
OptiX OSN 3500/7500
N1PEX2
OptiX OSN 3500/7500

541
OptiX OSN 7500 II/7500/3500/1500

14 MPLS Tunnel APS
Board Type
Version
N2PEX1
OptiX OSN 3500/7500
N1PEFF8
OptiX OSN 3500/7500
R1PEF4F
TNN1EX2
OptiX OSN 7500 II
TNN1EG8
OptiX OSN 7500 II
TNN1ETMC
OptiX OSN 7500 II
TNN1EFF8
OptiX OSN 7500 II

This section describes the limitations on and precautions for MPLS tunnel APS in the network
Issue 03 (2012-11-30)
Applicable
Object

Details
Remarks
Tunnel APS
In an MPLS APS group, the working

tunnel and protection tunnel have
the same ingress and egress nodes.
Tunnel APS
The working tunnel and protection

tunnel should not be physically on
the same path, if possible.
Tunnel APS
If multiple MPLS tunnel APS

groups are required on a ring
network, it is recommended that half
of the working tunnels be
configured on the upper part of the
ring and the other half be configured
on the lower part of the ring. In this
way, traffic is evenly distributed,
and the network-wide switching
caused by one interrupted link can
be avoided.
Tunnel APS
1:1 tunnel APS improves bandwidth

utilization. Unless otherwise
specified, 1:1 tunnel APS works in
dual-ended revertive mode.

542
OptiX OSN 7500 II/7500/3500/1500

14 MPLS Tunnel APS
Applicable
Object

Details
Remarks
Tunnel APS

wait-to-restore (WTR) time and
hold-off time take default values.
Tunnel APS
and PW APS
PW APS and tunnel APS cannot be

enabled simultaneously. This
indicates that, if the tunnel that
carries the PW is configured with
tunnel APS, the PW cannot be
configured with PW APS; if the PW
is configured with PW APS, the
tunnel that carries the PW cannot be
configured with tunnel APS.
Tunnel APS
and PW OAM
When configuring MPLS tunnel

APS, you cannot enable the PW ping
function.
Tunnel OAM
Tunnel OAM should be enabled for

working and protection tunnels.
Configure FFD packets as detection
packets for tunnel OAM. FFD
packets are usually sent at an
interval of 3.3 ms. If the frame delay
variation on a tunnel exceeds 3.3 ms,
Issue 03 (2012-11-30)
Applicable
Object

Details
Remarks
Tunnel APS
To delete tunnel APS, the tunnel

APS groups at both ends must be
deactivated first.
Tunnel APS
The APS protocol can be enabled

only after tunnel APS groups are
configured at both ends.
Tunnel APS
and LPT
When using the PW OAM detection

methods and Tunnel APS coupling
LPT, LPT need to bind the first
configuration of the PW.

543
OptiX OSN 7500 II/7500/3500/1500

14 MPLS Tunnel APS
None.
14.7 Principles
This topic describes the functions of MPLS Tunnel APS in terms of the basic principles,
protection attributes, protection rules, and switching impact.
14.7.1 Single-Ended Switching

When tunnel APS is in single-ended switching mode, APS is not used for switching. This topic
describes the principle of tunnel APS 1+1 single-ended switching.
Before Switching
l
The ingress node and egress node send service packets over the working and protection
tunnels.
The ingress node and egress node receive service packets over the working tunnel.
Tunnel OAM detects connectivity of each tunnel.
During Switching
Figure 14-1 shows the principle of the single-ended switching, assuming a fault in the forward
working tunnel.
Figure 14-1 Principle of the 1+1 single-ended switching
Ingress
Egress
Ingress
Forward
working tunnel
Forward
protection tunnel
Reverse
working tunnel
Forward
working tunnel
Forward
protection tunnel
Switching
Reverse
protection tunnel
Service
Egress
Forward working tunnel label

Reverse working tunnel label
Reverse
working tunnel
Reverse
protection tunnel
Forward protection tunnel label

Reverse protection tunnel label
The single-ended switching is implemented as follows:

1.
When the egress node detects a switching condition, it receives service packets over the
forward protection tunnel, instead of the forward working tunnel.
2.
The states of the reverse working and protection tunnels remain unchanged.
Issue 03 (2012-11-30)

544
OptiX OSN 7500 II/7500/3500/1500

14 MPLS Tunnel APS
After Switching
If tunnel APS 1+1 single-ended switching is in revertive mode, the service in the protection
tunnel is switched back to the normal working tunnel after the WTR time elapses.
14.7.2 Dual-Ended Switching

When MPLS tunnel APS is in dual-ended switching mode, the service is switched to the forward
and reverse protection tunnels.
Before Switching
l
The ingress and egress nodes exchange APS protocol packets over the protection tunnel,
and then they are aware of the status of each other. When the working tunnel is found faulty,
the ingress and egress nodes can perform the protection switching, switching hold-off, and
wait-to-restore (WTR) functions. In this case, the request state of the APS protocol packet
should be No Request.
The MPLS OAM mechanism is used to perform unidirectional continuity checks on all the
tunnels.
During Switching
Figure 14-2 shows the principle of the dual-ended switching, assuming a fault in the forward
working tunnel.
Figure 14-2 Principle of the dual-ended switching
Ingress
Egress
Ingress
Forward
working tunnel
Forward
protection tunnel
Reverse
working tunnel
Reverse
protection
tunnel
Service
Forward
working tunnel
Egress
Forward
protection tunnel
Switching
Forward working tunnel label

Reverse working tunnel
label
Reverse
working tunnel
Reverse
protection
tunnel
Forward protection tunnel label

Reverse protection tunnel label
The dual-ended switching is implemented as follows:

1.
When the egress node detects a fault in the forward working tunnel, it is switched to the
forward protection tunnel and is bridged to the reverse protection tunnel at the same time.
l The egress node receives the service from the forward protection tunnel instead of the
forward working tunnel. In addition, the egress node sends the APS protocol packet
carrying a bridging request to the ingress node.
l The egress node modifies the MPLS tunnel that the FEC travels through. That is, the
tunnel that the FEC travels through is changed from the reverse working tunnel to the
Issue 03 (2012-11-30)

545
OptiX OSN 7500 II/7500/3500/1500

14 MPLS Tunnel APS
reverse protection tunnel. In this case, the packet in the FEC encapsulates the MPLS
label corresponding to the reverse protection tunnel so that the service can be bridged
to the reverse protection tunnel. Meanwhile, the egress node sends the APS protocol
packet carrying a switching request to the ingress node.
NOTE
l "Bridging" means that the equipment transmits the service to the protection tunnel instead of the
working tunnel.
l "Switching" means that the equipment receives the service from the protection tunnel instead of the
working tunnel.
2.
On the reception of the APS protocol packet carrying a switching request, the ingress node
performs the following operations:
l The ingress node modifies the MPLS tunnel that the FEC travels through. That is, the
tunnel that the FEC travels through is changed from the forward working tunnel to the
forward protection tunnel. In this case, the packet in the FEC encapsulates the MPLS
label corresponding to the forward protection tunnel so that the service can be bridged
to the forward protection tunnel.
l The ingress node receives the service from the reverse protection tunnel instead of the
reverse working tunnel.
3.
The service is transmitted in the forward and reverse protection tunnels.
After Switching
If MPLS tunnel APS 1:1 dual-ended switching is in revertive mode, the service is switched back
to the normal forward and reverse working tunnels after the WTR time elapses.
14.7.3 Protection Attributes

The protection attributes of MPLS Tunnel APS includes four aspects: the revertive mode, WTR
time, switching condition, and delay time.
The revertive mode of MPLS Tunnel APS consists of revertive mode and non-revertive mode.
In the revertive mode, if the working tunnel fails, services are switched to the protection tunnel.
Later, if the original working tunnel returns to normal, the services are switched back to the
original working tunnel after the WTR time; in the non-revertive mode, services are not switched
back to the original working tunnel even when the working tunnel returns to normal.
The revertive mode is realized by the cross-connect board. When the status of the tunnel changes,
the cross-connect board determines how the services are switched according to the revertive
mode.
The switching condition can be set according to the actual requirements. For example, if the
switching condition is set as SD, then an SD alarm triggers the MPLS Tunnel APS switching.
According to the attribute of switching condition, the processing board determines whether to
check the switching condition and report it to the cross-connect board. Then the cross-connect
board determines whether to perform the MPLS Tunnel APS switching. When the processing
board detects a certain automatic switching condition, it reports the switching condition to the
cross-connect board after the preset delay time elapses. The specified time is actually the delay
time for the MPLS Tunnel APS switching.
14.7.4 Switching Rules

The MPLS Tunnel APS consists of automatic switching and external switching.
Issue 03 (2012-11-30)

546
OptiX OSN 7500 II/7500/3500/1500

14 MPLS Tunnel APS
Protection Group Status of MPLS Tunnel APS

To ensure that you learn the status of a tunnel in a timely manner, FFD checks the status of the
tunnel and reports it to the cross-connect board. When the processing board detects a changed
status of MPLS Tunnel APS, the processing board reports the status to the processing module
of the cross-connect board. If the delay time is set when the tunnel status turns faulty, then the
change of status is reported to the cross-connect board after the delay time elapses. If no delay
time is set, then the change of status is reported immediately. When the tunnel status returns to
normal, then the change of status is reported to the cross-connect board after the delay time
elapses, so as to prevent the jitter of status. The MPLS Tunnel APS protection group mainly
displays the following four states:
l
Idle: It represents the normal status of a node after the protocol is activated.
Switch: It represents the status of the faulty node after the switching.
Wtr: It represents the status of the original switching node when the fault is rectified within
the WTR time.
Lockout: It represents the status when the lockout switching command is issued and
services in the tunnel are switched to the working tunnel.
Automatic Switching
Automatic switching is triggered when a certain alarm, for example, MPLS_TUNNEL_LOCV,
MPLS_TUNNEL_MISMATCH, MPLS_TUNNEL_MISMERGE,
MPLS_TUNNEL_EXCESS, or MPLS_TUNNEL_UNKOWN, is detected.
External Switching
External switching is performed when the user issues switching commands that trigger the
switching condition. Six external switching commands are as follows:
l
Clear switching: This command clears all external commands and middle status, and returns
the working and protection tunnels to the idle or automatic switching state accordingly.
Forced switching: Services are forcibly switched regardless of whatever the status of a
tunnel is.
Manual to Working: Services are switched from the protection tunnel to the working tunnel.
If the working tunnel is normal, the switching takes place. If the working tunnel is faulty
or must satisfy higher priority switching, the switching does not take place.
Manual to Protection: Services are switched from the working tunnel to the protection
tunnel. If the protection tunnel is normal, the switching takes place. If the protection tunnel
is faulty or must satisfy higher priority switching, the switching does not take place.
Exercise switching: Simulates a switching operation. It is not a real switching. This function
tests the MPLS Tunnel APS protection function and does not interrupt services.
Lockout of protection: Regardless of the switching state, services are locked over the
working MPLS Tunnel.
Switching Rules
Each switching observes the following rules:
l
Issue 03 (2012-11-30)
In a descending order of priority, the switching commands are: clear switching, lockout of
switching, forced switching, automatic switching, manual switching, and exercise
547
OptiX OSN 7500 II/7500/3500/1500

14 MPLS Tunnel APS
switching. Commands of higher priority can preempt commands of lower priority, while
the opposite is impossible.
l
In the revertive mode, the commands of forced switching to the active tunnel and manual
switching to the active tunnel are not supported.
If the current status cannot be preempted, no status or service is switched.
14.7.5 Switching Impact

This topic describes how MPLS Tunnel APS affects the system and services.
MPLS Tunnel APS does not affect the system. If you configure MPLS Tunnel APS correctly,
switching is complete within 50 ms.

To realize the MPLS Tunnel APS function, you need to configure two different tunnels with the
same source and sink but different routes. When the working tunnel is faulty, services are
switched to the protection tunnel that is previously created.
MPLS Tunnel APS 1+1 Protection

In the case of MPLS Tunnel APS 1+1 protection, a protection tunnel is used to protect the
working tunnel. The 1+1 protection adopts the dual fed and selective receiving mechanism. The
services are switched to the protection tunnel only when the working tunnel fails.
Figure 14-3 shows the MPLS Tunnel APS 1+1 protection.
Figure 14-3 MPLS Tunnel APS 1+1 protection
NE A
Working Tunnel
NE B
Protection Tunnel
There are two MPLS tunnels as shown in the Figure 14-3. Normally, services are transmitted
through the working tunnel, and the protection tunnel is used to transmit the APS protocol.
MPLS OAM performs the connectivity check for each unidirectional MPLS tunnel. The source
sends connectivity check packets periodically and the sink performs the check. Set the OAM
packet type to FFD and the sending period to 3.3 ms to ensure that the switching time is less
than 50 ms.
The switching mode of the MPLS Tunnel APS 1+1 protection includes single-ended and dualended switching.
Issue 03 (2012-11-30)

548
OptiX OSN 7500 II/7500/3500/1500

14 MPLS Tunnel APS
MPLS Tunnel APS 1:1 Protection

In the case of MPLS Tunnel APS 1:1 protection, a protection tunnel is used to protect the working
tunnel. Normally, services are transmitted through the working tunnel. The services are switched
to the protection tunnel only when the working tunnel fails.
Figure 14-4 shows the MPLS Tunnel APS 1:1 protection.
Figure 14-4 MPLS Tunnel APS 1:1 protection
Working Tunnel
NE A
NE B
Protection Tunnel
There are two MPLS tunnels as shown in the Figure 14-4. The continuous line indicates the
working tunnel and the dashed line indicates the protection tunnel. Normally, services are
transmitted through the working tunnel, and the protection tunnel is used to transmit the APS
protocol.
MPLS OAM performs the connectivity check for each unidirectional MPLS tunnel. The source
sends connectivity check packets periodically and the sink performs the check. Set the OAM
packet type to FFD and the sending period to 3.3 ms to ensure that the switching time is less
than 50 ms.
The switching mode of the MPLS Tunnel APS 1:1 protection is dual-ended switching.
Guide to Configuring the MPLS Tunnel APS Protection

Pay attention to the following when configuring the MPLS Tunnel APS protection.
l
Enable MPLS OAM of the tunnels before configuring the APS protection.
Set the MPLS OAM packet type to FFD and the sending period to 3.3 ms.
Set the APS protocol to the enabled state after the nodes at both ends are configured with
the APS protection group.
14.9 Configuring an MPLS Tunnel APS Protection Group

You can configure a 1+1 or 1:1 MPLS tunnel APS protection group to protect MPLS tunnels.
This task requires you to configure the protection group on the source and sink NEs of the MPLS
tunnel.
Prerequisites
l
The working and protection MPLS tunnels must be created.
Issue 03 (2012-11-30)

549
OptiX OSN 7500 II/7500/3500/1500

14 MPLS Tunnel APS
MPLS OAM of each MPLS tunnel in the protection group must be enabled.
Precautions
WARNING
l An NNI that is configured with the 1+1 MPLS tunnel protection cannot be configured into
a link aggregation group (LAG).
l The protection MPLS tunnel cannot carry any extra services.
Procedure
Step 1 In the NE Explorer, select the source NE of the MPLS tunnel and choose Configuration >
Packet Configuration > APS Protection Management from the Function Tree.
Step 2 Click New.
Step 3 In the New Tunnel Protection Group dialog box that is displayed, set the parameters for the
MPLS tunnel protection group and select the working and protection MPLS tunnels.
l Protection Type: You can set Protection Type to 1+1 or 1:1.

l Switching Mode: You can set Switching Mode to Single-Ended or Dual-Ended. When
Protection Type is set to 1:1, Switching Mode can be set to Dual-Ended only.
Issue 03 (2012-11-30)

550
OptiX OSN 7500 II/7500/3500/1500

14 MPLS Tunnel APS
l Revertive Mode: You can set Revertive Mode to Non-Revertive or Revertive.

l Hold-off Time (100ms): The unit is 100 ms. You can set Hold-off Time (100ms) to an
integer from 0 to 100, namely, 0 to 10 seconds.
CAUTION
When creating a protection group, set Protocol Status to Disabled. Enable the protocol only
after the configuration of the protection group is completed on the source and sink NEs.
Step 4 Click OK. The MPLS tunnel APS protection group is configured successfully.
NOTE
The bandwidth of the protection MPLS tunnel must be higher than the bandwidth of the working MPLS
tunnel. To increase the bandwidth of the working MPLS tunnel after the protection group is created, increase
the bandwidth of the protection MPLS tunnel first.
Step 5 Repeat Steps 1-4 to configure the protection group on the sink NE.
Step 6 Enable the protocol of the MPLS tunnel APS protection group.
1.
In the NE Explorer, select the source NE of the MPLS tunnel and choose Configuration
> Packet Configuration > APS Protection Management from the Function Tree.
2.
Right-click a created protection group and choose Start Protocol from the shortcut menu.
3.
A dialog box is displayed, indicating that the operation is successful. Protocol Status of
the protection group changes to Enabled.
----End
Follow-up Procedure
1.
Modifying the attributes of an MPLS tunnel APS protection group

l Change of Revertive Mode does not affect the services protected by the protection
group.
l When Revertive Mode is set to Revertive, change of WTR Time ( m) does not affect
the services protected by the protection group.
l Change of Hold-off Time (100ms) does not affect the services protected by the
protection group.
2.
Deletion of an MPLS tunnel APS protection group

An MPLS tunnel APS protection group cannot be deleted if it is configured with services.
14.10 MPLS Tunnel APS Configuration Case

This section describes an MPLS Tunnel APS configuration case. The configuration case covers
service planning and configuration process.

The case description includes the function requirements, networking diagram, and service
planning.
Issue 03 (2012-11-30)

551
OptiX OSN 7500 II/7500/3500/1500

14 MPLS Tunnel APS
Requirements and Networking Diagram

A 2 Mbit/s service is present between Node B and RNC. After the 2 Mbit/s service is
encapsulated, it is transmitted through the working tunnel NE1-NE2-NE4 as shown in Figure
14-5. Because the 2 Mbit/s service has a high requirement for safety, a protection tunnel NE1NE3-NE4 is created to protect the working tunnel. Then, the MPLS Tunnel APS 1:1 protection
is established between the two tunnels.
Figure 14-5 Networking diagram of the MPLS Tunnel APS protection
NE 2
NE 1
NE 4
PSN
Node B
RNC
NE 3
Protection Tunnel
Working Tunnel
Service Planning
In this case, the NEs are OptiX OSN 3500 equipment. NE1 and NE4 are connected to Node B
and RNC respectively through E1 interfaces. NEs are connected to each other through FE
interfaces.
NE
Working Tunnel
Protection Tunnel
NE1
Ingress Tunnel
ID
Egress Tunnel
ID
Ingress Tunnel
ID
Egress Tunnel
ID
Transit Tunnel
ID
Transit Tunnel
ID
Transit Tunnel
ID
Transit Tunnel
ID
Ingress Tunnel
ID
Egress Tunnel
ID
Ingress Tunnel
ID
Egress Tunnel
ID
NE2
NE3
NE4
Issue 03 (2012-11-30)

552
OptiX OSN 7500 II/7500/3500/1500

14 MPLS Tunnel APS
Two MPLS tunnels are created on NE1. The working tunnel is MPLS tunnel 1 whose tunnel ID
is 1 in the ingress direction and 2 in the egress direction. The protection tunnel is MPLS tunnel
2 whose tunnel ID is 3 in the ingress direction and 4 in the egress direction.
An MPLS tunnel is created on NE2 as a transmit tunnel. The positive tunnel ID is 1 and the
reverse tunnel ID is 2.
An MPLS tunnel is created on NE3 as a transmit tunnel. The positive tunnel ID is 3 and the
reverse tunnel ID is 4.
Two MPLS tunnels are created on NE 4. The working tunnel is MPLS tunnel 1 whose tunnel
ID is 1 in the ingress direction and 2 in the egress direction. The protection tunnel is MPLS
tunnel 2 whose tunnel ID is 3 in the ingress direction and 4 in the egress direction.
According to the MPLS Tunnel APS configuration principle, you must set the OAM parameters
for the two MPLS tunnels and enable the OAM function in the ingress direction of the two
tunnels before configuring the MPLS Tunnel APS protection group. Set the OAM packet type
to FFD and packet sending period to 3.3 ms.
14.10.2 Configuration Flow

This section describes the flow of configuring the MPLS Tunnel APS protection.
Prerequisites
You must have learned about the networking, requirements, and service planning.
Two tunnels for the MPLS Tunnel APS protection must be created.
Procedure
Step 1 Enable the MPLS OAM function for the two MPLS tunnels and set the OAM packet parameters.
1.
Click the NE in the NE Explorer. Choose Configuration > Packet Configuration > MPLS
2.
Click the OAM Parameters tab. Set OAM Status to Enabled for the tunnels whose tunnel
IDs are 1, 2, 3, and 4.
3.
Set Detection Packet Type to FFD and Detection Packet Period(ms) to 3.3 for the tunnels
whose tunnel IDs are 1 and 3.
4.
Click Apply. The Operation Result dialog box is displayed indicating that the operation
is successful.
5.
Click Close.
6.
Set Detection Packet Type to FFD and Detection Packet Period(ms) to 3.3 for the tunnels
with 2 and 4 as tunnel IDs on NE2. Take preceding steps as reference.
Step 2 Create an MPLS Tunnel APS protection group on NE1.

1.
Select the NE in the NE Explorer. Choose Configuration > Packet Configuration > APS
Protection Management.
2.
Click New to display the New Tunnel Protection Group dialog box. Set the parameter as
follows:
l Set Switching Mode to Dual-Ended.
Issue 03 (2012-11-30)

553
OptiX OSN 7500 II/7500/3500/1500

14 MPLS Tunnel APS
NOTE
If Protection Type is set to 1:1, Switching Mode defaults to Dual-Ended and is not for setting.
l Set Working Ingress Tunnel ID to 1.

l Set Working Egress Tunnel ID to 2.
l Set Protection Ingress Tunnel ID to 3.
l Set Protection Egress Tunnel ID to 4.
l Set Hold-off Time (100ms) to 0.
l Set Protocol Statues to Disabled.
Step 3 Create an MPLS Tunnel APS protection group on NE4. Set the parameters by following Step
2.
Step 4 Enable the APS protocol for the MPLS Tunnel APS protection group.
1.
Click the NE in the NE Explorer. Choose Configuration > Packet Configuration > APS
Protection Management.
2.
Click the Protection Group tab. Right-click the APS protection group that is already
created and choose Start Protocol from the shortcut menu.
3.
A dialog box is displayed indicating that the operation is successful. Then, Protocol
Status of the APS protection group changes to Enabled.
----End
14.11 Verifying the MPLS Tunnel APS

This topic describes how to verify and ensure that the configuration data of the MPLS Tunnel
APS is correct after the MPLS Tunnel APS is configured.
Prerequisites
l
The MPLS Tunnel APS must be configured.
You can verify the MPLS Tunnel APS function according to the following aspects:
l
If a fault is generated on the network, the MPLS Tunnel APS can still be performed
normally.
If the protection group is set to the revertive mode, the service can be switched from the
protection tunnel to the working tunnel after the WTR time expires.
All the commands that trigger manual switching can be issued correctly.
Procedure
Step 1 If a fault is generated on the network, the MPLS Tunnel APS can still be performed normally.
1.
Issue 03 (2012-11-30)
Disconnect the working fiber.

554
OptiX OSN 7500 II/7500/3500/1500

14 MPLS Tunnel APS
2.
In the Main Topology, right-click the NE that you want to verify and choose NE
Explorer from the shortcut menu.
3.
Choose Configuration > Packet Configuration > APS Protection Management in the
Function Tree. In the pane on the right side, select the protection group that you want to
verify. Then, click Function > Query Switching Status to check whether the service is
switched from the working tunnel to the protection tunnel.
Step 2 If the protection group is set to the revertive mode and if the working tunnel recovers, the service
can be switched from the protection tunnel to the working tunnel after the WTR time expires.
1.
Reconnect the fiber that is disconnected in Step 1. After the WTR time expires, click
Function > Query Switching Status to check whether Active Tunnel is the specified
Working Tunnel.
Step 3 All the commands that trigger manual switching can be issued correctly.
1.
Select the protection group that you want to verify and click Clear under Function. Then,
click Query Switching Status under Function to check whether the command is issued
successfully.
2.
Repeat the preceding steps to check whether all commands that trigger manual switching,
such as Force Switching, Manual Switching to Working, Manual Switching to
Protection, Exercise Switching, and Lockout of Protection are issued successfully.
----End
This topic describes the symptom of common faults when the MPLS Tunnel APS function is
enabled and the solution to the relevant fault.
Symptom
When the network works normally, a condition that triggers the protection switching occurs on
the working tunnel. The services, however, fail to be automatically switched from the working
tunnel to the protection tunnel. Consequently, the services are interrupted. The symptoms are as
follows:
l
The switching duration exceeds the specified value.
The MPLS Tunnel APS protection group is configured incorrectly. Thus the protection
tunnel cannot receive the APS frame. In this case, the protection fails and the following
alarms may be reported.
ETH_APS_PATH_MISMATCH
ETH_APS_TYPE_MISMATCH
ETH_APS_LOST
ETH_APS_SWITCH_FAIL
The protection tunnel is faulty and fails to provide protection. In this case, the following
alarms may be reported.
MPLS_TUNNEL_LOCV
MPLS_TUNNEL_MISMERGE
MPLS_TUNNEL_MISMATCH
MPLS_TUNNEL_EXCESS
Issue 03 (2012-11-30)

555
OptiX OSN 7500 II/7500/3500/1500

14 MPLS Tunnel APS
MPLS_TUNNEL_SD
MPLS_TUNNEL_SF
MPLS_TUNNEL_UNKNOWN
MPLS_TUNNEL_BDI
MPLS_TUNNEL_FDI
Possible Causes
l
Cause 1: The fibers or cables on the protection tunnel are connected incorrectly.
Cause 2: The OAM parameters of the working tunnel and protection tunnel are set
incorrectly.
Cause 3: The parameter values of the APS protection group at the two ends are different
from each other.
Cause 4: The MPLS Tunnel APS protocol is disabled.
Flow Chart
Figure 14-6 shows the flow chart for rectifying a fault when the MPLS Tunnel APS function is
enabled.
Issue 03 (2012-11-30)

556
OptiX OSN 7500 II/7500/3500/1500

14 MPLS Tunnel APS
Figure 14-6 Flow chart for rectifying a fault when the MPLS Tunnel APS function is enabled
Start
Are the fibers or cables

connected correctly?
No
Reconnect the fibers or

cables.
Can the APS be

performed normally?
Yes
No
Yes
Are the OAM parameters of the

working and protection
tunnels set correctly?
No
Set the working and

protection tunnels correctly.
Can the APS be

performed normally?
Yes
No
Yes
Are the parameter values of the

APS the same at the two ends?
No
Set the parameters for the

APS at the two ends
correctly.
Can the APS be

performed normally?
Yes
No
Yes
Is the MPLS APS protocol

enabled?
No
Enable the MPLS APS

protocol.
Can the APS be

performed normally?
Yes
No
Yes
Does any alarm related to

the APS occur?
Yes
See the Alarms and
Performance Events
Reference to clear the alarm.
No
Can the APS be
performed normally?
Yes
No
Conact the technical support
engineers of Huawei.
End
Procedure
l
Cause 1: The fibers or cables on the protection tunnel are connected incorrectly.
1.
Cause 2: The working tunnel and protection tunnel are set incorrectly.
1.
Issue 03 (2012-11-30)
Reconnect the fibers or cables to each port and ensure that the fibers or cables are
connected correctly.
In the Main Topology, right-click the NE that you want to configure and choose NE
557
OptiX OSN 7500 II/7500/3500/1500

14 MPLS Tunnel APS
2.
Choose Configuration > Packet Configuration > MPLS Management > Unicast
Tunnel Management in the Function Tree.
3.
Click the OAM Parameters tab, select the tunnel that realizes the MPLS Tunnel APS
function. Then, set Detection Packet Type to FFD, and set Detection Packet Period
(ms) to 3.3 or 10.
Cause 3: The parameter values of the APS protection group at the two ends are different
from each other.
1.
2.
Choose Configuration > Packet Configuration > APS Protection Management in

the Function Tree.
3.
Click Query to query whether the settings of the APS protection group are the same.
If the settings of the APS protection group are different from each other, set the
protection tunnel in the APS protection group to the same value as the working tunnel.
Cause 4: The MPLS Tunnel APS protocol is disabled.

1.
2.
Choose Configuration > Packet Configuration > APS Protection Management in

the Function Tree.
3.
Set Protocol Status to Enabled, and then click Apply.
4.
In the Operation Result dialog box that is displayed, click Close.
If the preceding operations are performed but the alarm related to the MPLS Tunnel APS
function persists, see the Alarms and Performance Events Reference to clear the alarm. If
the fault persists, contact Huawei technical support engineers for the solution.
----End


This topic describes the alarms that are related to this feature.
Table 14-2 lists the alarms related to MPLS Tunnel APS.
Table 14-2 Alarms related to MPLS Tunnel APS
Issue 03 (2012-11-30)
Alarm Name
Description
ETH_APS_LOST
The ETH_APS_LOST alarm indicates that the Automatic

Protection Switching (APS) frames are lost. This alarm is reported
when no APS frame is received from the protection channel.

558
OptiX OSN 7500 II/7500/3500/1500

Issue 03 (2012-11-30)
14 MPLS Tunnel APS
Alarm Name
Description
ETH_APS_PATH_MIS
MATCH
The ETH_APS_PATH_MISMATCH alarm indicates that the

working and protection paths of the APS protection group differ
between the two ends. This alarm is reported when the working
and protection paths at one end are different from the working and
protection paths at the other end.
ETH_APS_SWITCH_F
AIL
The ETH_APS_SWITCH_FAIL alarm indicates a protection

switching failure. This alarm is reported when the request signals
in the transmitted Automatic Protection Switching (APS) frame
are different from the bridge signals in the received APS frame
and this symptom lasts for 50 ms.
ETH_APS_TYPE_MISMATCH
The ETH_APS_TYPE_MISMATCH alarm indicates protection

scheme mismatch. This alarm is reported when the information
in the received Automatic Protection Switching (APS) frame is
different from the APS protection scheme specified at the local
end.
MPLS_TUNNEL_LOC
V
The MPLS_TUNNEL_LOCV alarm indicates the loss of tunnel

connectivity. This alarm is reported when the Ethernet port
receives the connectivity check packet with the correct TTSI
within three periods, but the packet type and period are different
from the expected values.
MPLS_TUNNEL_MISMERGE
The MPLS_TUNNEL_MISMERGE alarm indicates that the

Trail Termination Source Identifiers (TTSIs) are incorrectly
merged. This alarm is reported if CV/FFD packets with correct
TTSIs and CV/FFD packets with incorrect TTSIs are received in
three consecutive CV/FFD periods.
MPLS_TUNNEL_MISMATCH
The MPLS_TUNNEL_MISMATCH alarm indicates Trail

Termination Source Identifiers (TTSIs) mismatch. This alarm is
reported if no CV/FFD packet with a correct TTSI is received in
three consecutive CV/FFD periods.
MPLS_TUNNEL_Excess
The MPLS_TUNNEL_Excess alarm indicates that excessive

Trail Termination Source Identifiers (TTSIs) are received. This
alarm is reported if a total of five correct CV/FFD packets or more
are received in three consecutive CV/FFD periods.
MPLS_TUNNEL_SD
The MPLS_TUNNEL_SD alarm indicates that the tunnel signal

degrades. This alarm is reported when the packet loss ratio of the
connectivity check (CC) exceeds the SD threshold but is lower
than the SF threshold.
MPLS_TUNNEL_SF
The MPLS_TUNNEL_SF alarm indicates that the tunnel signal

degrades severely. During the Continuity Check (CC), this alarm
is reported if the packet loss ratio exceeds the SF threshold but
CC packets are received in three consecutive periods.

559
OptiX OSN 7500 II/7500/3500/1500

14 MPLS Tunnel APS
Alarm Name
Description
MPLS_TUNNEL_UNKNOWN
The MPLS_TUNNEL_UNKNOWN alarm indicates that certain

unknown defects exist on the tunnel. This alarm is reported when
the Ethernet port receives the connectivity check packet with the
correct TTSI within three periods and the connectivity check
packets of different types or periods.
MPLS_TUNNEL_BDI
The MPLS_TUNNEL_BDI alarm indicates defects in the

backward direction of a tunnel. This alarm is reported when a BDI
packet is received at the receive end, indicating that the forward
tunnel is faulty.
MPLS_TUNNEL_FDI
The MPLS_TUNNEL_FDI alarm indicates defects in the forward

direction of a tunnel. This alarm is reported when a Forward
Defect Indication (FDI) packet is received, indicating that the
tunnel at the physical layer of the upstream NE is faulty.

There are no performance events that are related to the MPLS tunnel APS function. The abnormal
event related to the MPLS tunnel APS function is the reporting of the tunnel APS protection.
Reporting of the tunnel APS protection switching indicates that tunnel APS protection switching
occurs.
14.14 Parameter Description: MPLS Tunnel APS

This topic describes the parameters required for configuring MPLS tunnel APS.
14.14.1 Parameters for Configuring MPLS Tunnel APS (on a Per-NE

Basis)
You need to set the necessary parameters when configuring MPLS Tunnel APS.
Table 14-3 lists the parameters for configuring MPLS Tunnel APS.
Table 14-3 Parameters for configuring MPLS Tunnel APS
Field
Value
Description
Protection Group ID
For example, 1
Displays the protection group

ID.
The system automatically
assigns the protection group
ID according to the sequence
of their creation.
Protection Type
Issue 03 (2012-11-30)
1+1, 1:1

Selects a protection type.

560
OptiX OSN 7500 II/7500/3500/1500

14 MPLS Tunnel APS
Field
Value
Description
Switching Mode
Single-Ended, Dual-Ended
Specifies the switching

policy to be adopted when a
tunnel fails.
Revertive Mode
Non-Revertive, Revertive
Specifies whether the

services are switched from
the protection Tunnel to the
working Tunnel after the
working Tunnel is restored. If
you set this parameter to
Revertive, the services can
be switched from the
protection Tunnel to the
working Tunnel. If you set
this parameter to NonRevertive, the services
cannot be switched from the
protection Tunnel to the
working Tunnel.
WTR Time(m)
1 to 12
Specifies the WTR time of

the protection group.
Default: 5
Hold-off Time(100ms)
Protocol Status
0 to 100
Default: 0
Specifies the hold-off time of

Enabled, Disabled
Specifies the protocol status.

If you set the parameter to
Enabled, the protection
group is available.
Switching Status
Clear, Forced Switching,

Manual Switching\(Working
to Protection\), Manual
Switching\(Protection to
Working\), Exercise
Switching, Lockout
Indicates the switching status

14.14.2 Parameters for Configuring MPLS Tunnel APS (in End-toEnd Mode)
This topic describes the parameters for configuring MPLS tunnel APS protection groups in endto-end mode.
Issue 03 (2012-11-30)

561
OptiX OSN 7500 II/7500/3500/1500

14 MPLS Tunnel APS
Table 14-4 Parameters for configuring MPLS tunnel APS

Field
Value Range
Description
Protection Group ID
For example, Tunnel APS 1
Specifies the name of the

protection group.
Protection Type
1+1, 1:1

protection group.
Default: 1+1
l 1:1: A protection tunnel

protects a working tunnel.
Normally, the working
tunnel carries services
and the protection tunnel
carries protocol packets.
When the working tunnel
fails, services are
switched from the
working tunnel to the
protection tunnel.
l 1+1: A protection tunnel
protects a working tunnel.
Normally, services are
transmitted on both
tunnels and selected from
either tunnel for
reception. When the
working tunnel fails,
services on the protection
tunnel are selected for
reception.
Switching Mode
Single-Ended, Dual-Ended
Default: Single-Ended
NOTE
When Protection Type is set to
1:1, Switching Mode is
defaulted to Dual-Ended and
cannot be changed.
Specifies the switching mode

l In single-ended
switching, if a fault is
detected at one end, only
the local end switches and
the opposite end is not
notified for performing a
switching.
l In dual-ended switching,
if a fault is detected at one
end, the local end
switches and the opposite
end is instructed to
perform a switching.
Issue 03 (2012-11-30)

562
OptiX OSN 7500 II/7500/3500/1500

14 MPLS Tunnel APS
Field
Value Range
Description
Working Tunnel Type
MPLS Tunnel

working tunnel.
When configuring MPLS
tunnel APS for unidirectional
tunnels, you need to select
four tunnels, which function
as the Forward Working
tunnel, Forward Protection
tunnel, Backward Working
tunnel, and Backward
Protection tunnel.
For a bidirectional tunnel,
you need to select two
tunnels, namely, the working
tunnel and protection tunnel.
Working Ingress Tunnel ID
For example, 40 (source

node: 130.0.0.12; sink node:
75.75.75.75)
Selects the ID of the working

ingress tunnel.
Working Ingress Tunnel

Name
For example, 1

working ingress tunnel.
Working Egress Tunnel ID

75.75.75.75)
Selects the ID of the working

egress tunnel.
Working Egress Tunnel

Name
For example, 1

working egress tunnel.
Protection Tunnel Type
MPLS Tunnel

protection tunnel.
Protection Ingress Tunnel ID

75.75.75.75)
Selects the ID of the

protection ingress tunnel.
Protection Ingress Tunnel

Name
For example, 1

protection ingress tunnel.
Protection Egress Tunnel ID

75.75.75.75)
Selects the ID of the

protection egress tunnel.
Protection Egress Tunnel

Name
For example, 1

protection egress tunnel.
Protocol Status
Enabled, Disabled
Specifies the protocol status.

If you set this parameter to
Enabled, the protection
group is available.
Issue 03 (2012-11-30)

563
OptiX OSN 7500 II/7500/3500/1500

14 MPLS Tunnel APS
Field
Value Range
Description
Switching Status
Non-Revertive, Revertive

services are switched from
the protection tunnel to the
working tunnel after the
working tunnel is restored. If
Revertive, the services can
be switched from the
protection tunnel to the
working tunnel. If you set this
parameter to NonRevertive, the services
cannot be switched from the
protection tunnel to the
working tunnel.
WTR Time(min)
1-12
Specifies the WTR time of

Default: 5
Hold-off Time(100ms)
0-100
Default: 0
Issue 03 (2012-11-30)

Specifies the hold-off time of

564
OptiX OSN 7500 II/7500/3500/1500

15 MS-PW
15
MS-PW
About This Chapter

Multi-segment pseudo wire (MS-PW) involves setting up static PW segments to provide edgeto-edge virtual connections and reduce the number of tunnels on the convergence ring.
15.1 Introduction
An MS-PW provides an edge-to-edge virtual connection by setting up static PW segments. The
S-PE at the tangent point of the access ring and the convergence ring swaps PW labels and
aggregates PWs. The number of tunnels on the convergence ring is reduced.
15.2 Basic Concepts
Learning about the basic concepts helps to further understand the MS-PW feature.
This topic describes the standards and protocols that MS-PW complies with.
15.4 Availability
The MS-PW function requires the support of the applicable equipment and boards.
This section describes the limitations on and precautions for MS-PW in the network design
15.6 Principles
This section describes the principles of MS-PW.
15.7 Configuring MS-PWs
Configure cross-connections for the forward and backward PWs on the S-PE node to create an
MS-PW. This helps to provide edge-to-edge virtual connections for Ethernet services.
This topic considers a configuration example to help you get familiar with the application and
configuration process of the MS-PW function in actual applications.
15.9 Verifying MS-PW
After services carried by an MS-PW are configured, you can run the PW ping command to verify
the end-to-end connectivity of the MS-PW.
Issue 03 (2012-11-30)

565
OptiX OSN 7500 II/7500/3500/1500

15 MS-PW
This topic describes the alarms and performance events that are related to the MS-PW.
15.11 MS-PW Parameters
This topic describes the parameters associated with a PW.
Issue 03 (2012-11-30)

566
OptiX OSN 7500 II/7500/3500/1500

15 MS-PW
15.1 Introduction
An MS-PW provides an edge-to-edge virtual connection by setting up static PW segments. The
S-PE at the tangent point of the access ring and the convergence ring swaps PW labels and
aggregates PWs. The number of tunnels on the convergence ring is reduced.
Definition
An MS-PW is set up between two PW terminating provider edges (T-PEs) and travels through
the PW switching provider edge (S-PE). At the S-PE, PW labels are swapped and then the MSPW is divided into two or more segments.
An MS-PW consists of multiple adjacent PW segments, and each PW segment is a point-topoint PW.
Purpose
If the equipment does not support MS-PW, Ethernet services can be transmitted over a PSN by
static MPLS tunnels.
l
At the ingress node, PW and tunnel labels are put on Ethernet packets.
At the transit node, the tunnel labels are swapped.
At the egress node, the PW and tunnel labels are stripped.
In this service model, only the tunnel labels can be swapped at the transit node. Therefore, as
shown in Figure 15-1, users must configure edge-to-edge tunnels from the NodeB to the RNC.
The number of tunnels on the convergence ring PSN2 increases sharply as the number of NodeBs
increases.
Figure 15-1 Single-segment PW networking diagram
FE
Ingress node
Node B
Transit node
FE
PSN1
Egress
node
Node B
PSN2
GE
FE
Node B
RNC
PSN3
FE
Tunnel
Node B
Issue 03 (2012-11-30)
PW

567
OptiX OSN 7500 II/7500/3500/1500

15 MS-PW
As shown in Figure 15-2, the S-PE at the tangent point of the access ring and the convergence
ring terminates the tunnels on the access rings. All the PWs on the access rings are aggregated
into one tunnel. Therefore, the number of tunnels on the convergence ring is reduced.
Figure 15-2 MS-PW networking diagram
MS-PW
FE
Node B
T-PE
PSN1
FE
Node B
T-PE
S-PE
GE
PSN2
S-PE
FE
T-PE
RNC
T-PE
Node B
PSN3
FE
T-PE
Node B
Tunnel
PW
15.2 Basic Concepts

Learning about the basic concepts helps to further understand the MS-PW feature.
PW Switching Provider Edge (S-PE)

An S-PE can terminate the tunnel labels of the tunnel packet, and switch the PW labels. An MSPW must transit an S-PE.
PW Terminating Provider Edge (T-PE)

A T-PE connects to the access link and forwards the service to the PW. It is used at both ends
of an MS-PW to terminate the PW label.
PW Segment
A PW segment is a part of the MS-PW, and is set up between two PEs. The two PEs can be two
T-PEs, two S-PEs, or one T-PE and one S-PE.
Issue 03 (2012-11-30)

568
OptiX OSN 7500 II/7500/3500/1500

15 MS-PW

This topic describes the standards and protocols that MS-PW complies with.
MS-PW complies with the following standards and protocols:
l
RFC3916 Requirements for Pseudo-Wire Emulation Edge-to-Edge (PWE3)
RFC3985 Pseudo Wire Emulation Edge-to-Edge (PWE3) Architecture
RFC4446 IANA Allocations for Pseudowire Edge to Edge Emulation (PWE3)
draft-ietf-pwe3-control-protocol-17 Pseudo wire Setup and Maintenance using the

Label Distribution Protocol
draft-martini-pwe3-pw-switching-03 Pseudo Wire Switching
draft-ietf-pwe3-cw-00 PWE3 Control Word for use over an MPLS PSN
draft-ietf-pwe3-vccv-03 Pseudo Wire Virtual Circuit Connectivity Verification

(VCCV)
draft-ietf-pwe3-ethernet-encap-10 Encapsulation Methods for Transport of Ethernet

Over MPLS Networks
draft-ietf-pwe3-atm-encap-11 Encapsulation Methods for Transport of ATM Over

MPLS Networks
draft-ietf-pwe3-cell-transport-05 PWE3 ATM Transparent Cell Transport Service
15.4 Availability
The MS-PW function requires the support of the applicable equipment and boards.
Version Support
Issue 03 (2012-11-30)
Product Name
Applicable Version
OptiX OSN 1500/3500/7500
U2000
Product Name
Applicable Version
OptiX OSN 7500 II
U2000

569
OptiX OSN 7500 II/7500/3500/1500

15 MS-PW
Hardware Support
Board Type
Version
N1PETF8
OptiX OSN 3500/7500
N1PEG8
OptiX OSN 3500/7500
N1PEX2
OptiX OSN 3500/7500
N2PEX1
OptiX OSN 3500/7500
N1PEFF8
OptiX OSN 3500/7500
N1PEX1
OptiX OSN 3500
N1PEG16
OptiX OSN 3500
R1PEFS8
Q1PEGS2
R1PEGS1
R1PEF4F
TNN1EX2
OptiX OSN 7500 II
TNN1EG8
OptiX OSN 7500 II
TNN1ETMC
OptiX OSN 7500 II
TNN1EFF8
OptiX OSN 7500 II

This section describes the limitations on and precautions for MS-PW in the network design
Issue 03 (2012-11-30)
Applicable
Object

Details
Remarks
MS-PW
The equipment supports the static

MS-PW only.
MS-PW and
LPT
MS-PW services support LPT using

PW OAM, but does not support LPT
using LPT OAM.

570
OptiX OSN 7500 II/7500/3500/1500

15 MS-PW
Applicable
Object

Details
Remarks
MS-PW and
PW APS
l For the intermediate node that is configured with the MS-PW, the
OAM function cannot be
enabled and the APS protection
cannot be configured.
l For the intermediate node that is
enabled with the OAM function
and configured with the APS
protection, the MS-PW cannot
be set up.

None.
None.
15.6 Principles
This section describes the principles of MS-PW.
An MS-PW provides an edge-to-edge virtual connection by setting up static PW segments.
See Figure 15-3.
l
PW1 carries UNI-NNI E-Line services from CE1 and PW2 carries UNI-NNI E-Line
services from CE2.
MS-PW1 consists of PW1 and PW3, and MS-PW2 consists of PW2 and PW4.
PW1 is carried by tunnel 1, PW2 is carried by tunnel 2, and PW3 and PW4 are carried by
tunnel 3.
Issue 03 (2012-11-30)

571
OptiX OSN 7500 II/7500/3500/1500

15 MS-PW
Figure 15-3 Working principle of MS-PW

MS-PW1
T-PE1
Tunnel1
CE1
Tunnel3
PW3
PW1
PW2
Tunnel2
CE2
PW4
S-PE
T-PE3
CE3
T-PE2
MS-PW2
PW
Tunnel
MS-PW functions as follows:

1.
S-PE strips the tunnel labels of tunnel 1 and tunnel 2.
2.
S-PE swaps the labels of PW1 and PW3 and the labels of PW2 and PW4. In addition, SPE creates connection relationships between PW1 and PW3 and between PW2 and PW4.
3.
E-Line services between CE1/CE2 and CE3 are transmitted in an edge-to-edge manner.
15.7 Configuring MS-PWs

Configure cross-connections for the forward and backward PWs on the S-PE node to create an
MS-PW. This helps to provide edge-to-edge virtual connections for Ethernet services.
Prerequisites
l
The tunnels carrying PWs must be configured.
PWs between the T-PE nodes and the S-PE node must be configured.
Procedure
Step 1 In the NE Explorer, select the required NE, and choose Configuration > Packet
Configuration > MPLS Management > PW Management from the Function Tree. Then,
select MS PW in the right pane.
Step 2 Click New. In the dialog box that is displayed, set the general attributes of the MS-PW.
Issue 03 (2012-11-30)

572
OptiX OSN 7500 II/7500/3500/1500

15 MS-PW
NOTE
When Tunnel selection mode is set to Auto Select, you must set Peer LSR ID. In addition, click the Forward
Tunnel selection or Backward Tunnel Selection tab, and set the priority of automatically selecting the tunnel
type.
Step 3 Click the QoS tab, and configure the QoS parameters of the MS-PW.
NOTE
l It is recommended that you set the QoS parameters to the same values for the forward and backward PWs.
l If the forward and backward PWs traverse different domains, the bandwidth limit parameter needs to take
the same value for the forward and backward PWs, but the other parameters of the QoS can take different
values for the forward and backward PWs.
Step 4 Click the Advanced Attributes tab, and configure the advanced attributes of the MS-PW.
Issue 03 (2012-11-30)

573
OptiX OSN 7500 II/7500/3500/1500

15 MS-PW
Step 5 Click Apply. In the dialog box that is displayed, click Close.
----End

This topic considers a configuration example to help you get familiar with the application and
configuration process of the MS-PW function in actual applications.

This topic describes the networking scenario wherein the MS-PW carrying services traverses
different domains.

As shown in Figure 15-4, the PWs between NE1 and NE4 and between NE2 and NE4 carry ELine services between the NodeBs and the RNC, tunnel 1 carries PW40 between NE1 and NE3,
tunnel 2 carries PW50 between NE2 and NE3, and tunnel 3 carries PW60 and PW70 between
NE3 and NE4.
MS-PW1 cross-connects PW40 (forward) with PW60 (backward) to carry E-Line services
between NE1 and NE4.
MS-PW2 cross-connects PW50 (forward) with PW70 (backward) to carry E-Line services
between NE2 and NE4.
Figure 15-4 E-Line services carried by the MS-PW
LSR ID: 1.0.0.1
NE1
PW 40
NodeB
Tunnel 1
PW 50
LSR ID: 1.0.0.3

NE3
PW 60
PW 70
Tunnel 2
NodeB
NE2
LSR ID: 1.0.0.2
MS-PW 1
Tunnel 3
MS-PW 2
NE4
LSR ID: 1.0.0.4
RNC
PW
MS-PW
Tunnel
Issue 03 (2012-11-30)

574
OptiX OSN 7500 II/7500/3500/1500

15 MS-PW
Service Planning
Table 15-1 lists the planning for the general attributes of the MS-PW.
Table 15-1 Planning for the general attributes of the MS-PW
Parameter
MS-PW1
MS-PW2
ID
Name
MS-PW1
MS-PW2
MTU (bytes)
1500
1500
Service Type
Ethernet Service
Ethernet Service
Forward/
Backward PW
Forward PW
Backward PW
Forward PW
Backward PW
PW ID
40
60
50
70
PW Signaling
Type
Static
Static
Static
Static
PW Type
Ethernet
Ethernet
Ethernet
Ethernet
PW Direction
Bidirectional
Bidirectional
Bidirectional
Bidirectional
PW Incoming
Label
20
40
30
50
PW Outgoing
Label
20
40
30
50
Tunnel
Selection Mode
Manually
Manually
Manually
Manually
Tunnel Type
MPLS
MPLS
MPLS
MPLS
Tunnel No.
Peer LSR ID
1.0.0.1
1.0.0.4
1.0.0.2
1.0.0.4
Table 15-2 lists the QoS parameter planning for the MS-PW.
Table 15-2 QoS parameter planning for the MS-PW
Issue 03 (2012-11-30)
Parameter
Forward PW
Ingress
Forward PW
Egress
Backward PW
Ingress
Backward PW
Egress
Bandwidth
Limit
Enabled
Disabled
Enabled
Disabled

575
OptiX OSN 7500 II/7500/3500/1500

15 MS-PW
Parameter
Forward PW
Ingress
Forward PW
Egress
Backward PW
Ingress
Backward PW
Egress
Policy
CIR(kbit/s)
10240
10240
CBS(kbit/s)
PIR(kbit/s)
30720
30720
PBS(kbit/s)
EXP
LSP Mode
Uniform
Uniform
Table 15-3 lists the planning for the advanced attributes of the MS-PW.
Table 15-3 Planning for the advanced attributes of the MS-PW
Parameter
Value
Control Word
Use preferred
Control Channel Type
CW
VCCV Verification Mode
Ping
Request VLAN

This topic describes how to configure MS-PW on the S-PE node (NE3).
Prerequisites
l
A network must be set up according to Figure 15-4.
E-Line services carried by PWs must be configured on the T-PE nodes (NE1, NE2, and
NE4) according to service planning.
Procedure
Step 1 In the NE Explorer, select NE3, and choose Configuration > Packet Configuration > MPLS
Management > PW Management from the Function Tree. Then, select MS PW in the right
pane.
Step 2 Click New. In the dialog box that is displayed, set the general attributes of MS-PW1.
The parameters of the general attributes of MS-PW1 are as follows.
Issue 03 (2012-11-30)

576
OptiX OSN 7500 II/7500/3500/1500

15 MS-PW
Parameter
Value in This Example
ID
Name
MS-PW1
MTU (bytes)
1500
Service Type
Ethernet
PW ID
Forward PW: 40
Backward PW: 60
PW Signaling Type
Forward/Backward PW: Static
PW Incoming Label/Source Port
Forward PW: 20
Backward PW: 40
PW Outgoing Label/Sink Port
Forward PW: 20
Backward PW: 40
Tunnel Selection Mode
Forward/Backward PW: Manually
Tunnel Type
Forward/Backward PW: MPLS
Tunnel No.
Forward PW: 1
Backward PW: 3
Peer LSR ID
Forward PW: 1.0.0.1

Backward PW: 1.0.0.4
Step 3 Click the QoS tab, and configure the QoS parameters of MS-PW1.
The QoS parameters of MS-PW1 are as follows.
Parameter
Bandwidth Limit
Forward/Backward PW Ingress: Enabled
CIR(kbit/s)
Forward/Backward PW Ingress: 10240
PIR(kbit/s)
EXP
LSP Mode
Forward/Backward PW Egress: Uniform
Step 4 Click the Advanced Attributes tab, and configure the advanced attributes of MS-PW1.
The parameters of advanced attributes of MS-PW1 are as follows.
Issue 03 (2012-11-30)
Parameter
Control Word
Use preferred
577
OptiX OSN 7500 II/7500/3500/1500

15 MS-PW
Parameter
CW
Ping
Step 5 Perform Steps 1 to 4 to configure the parameters of MS-PW2.

The settings of QoS and advanced attributes of MS-PW2 are the same as those of MS-PW1. Set
the general attributes of MS-PW2 as follows.
Parameter
ID
Name
MS-PW2
MTU (bytes)
1500
Service Type
Ethernet
PW ID
Forward PW: 50
Backward PW: 70
PW Signaling Type
Forward/Backward PW: Static
PW Incoming Label/Source Port
Forward PW: 30
Backward PW: 50
PW Outgoing Label/Sink Port
Forward PW: 30
Backward PW: 50
Tunnel Selection Mode
Forward/Backward PW: Manually
Tunnel Type
Forward/Backward PW: MPLS
Tunnel No.
Forward PW: 2
Backward PW: 3
Peer LSR ID
Forward PW: 1.0.0.4

Backward PW: 1.0.0.2
----End
15.9 Verifying MS-PW

After services carried by an MS-PW are configured, you can run the PW ping command to verify
the end-to-end connectivity of the MS-PW.
Prerequisites
l
Issue 03 (2012-11-30)
E-Line services carried by PWs must be configured according to service planning.

578
OptiX OSN 7500 II/7500/3500/1500

15 MS-PW
The MS-PW must be configured according to service planning.
The PW OAM function must be enabled.
As shown in Figure 15-5, test the connectivity between NE1 and NE4 and between NE2 and
NE4 by performing a PW ping test at NE1 and NE2.
Figure 15-5 E-Line services carried by the MS-PW
NE1
PW 40
NE3
NodeB
Tunnel 1
PW 50
PW 60
MS-PW 1
Tunnel 3
PW 70
MS-PW 2
NE4
Tunnel 2
NodeB
RNC
NE2
PW
MS-PW
Tunnel
Table 15-4 Planning for the general attributes of the PW ping test
Parameter
MS-PW1
MS-PW2
Peer PW ID
60
70
Peer IP
10.2.3.4
10.2.3.4
NOTE
l Peer PW ID refers to the PW ID of PW60 or PW70.

l Peer IP refers to the port IP address of NE4 (sink node) of tunnel 3.
l You can perform one ping test on one PW at a time.
Procedure
Step 1 In the NE Explorer, select the required NE, and then choose Configuration > Packet
Step 2 Click PW OAM Parameter and select PW40. Then, choose OAM Operation > Ping Test.
Step 3 In the Ping Test dialog box that is displayed, set the parameters of Ping Test.
Issue 03 (2012-11-30)

579
OptiX OSN 7500 II/7500/3500/1500

15 MS-PW
Parameter
Packet Count
EXP Value
TTL
255
100
Packet Length
64
Wait-to-Response Timeout Time(10ms)
300
Response Mode
IPv4 UDP Response
Peer PW ID
60
Peer IP
10.2.3.4
Step 4 Click Start Test. Check the result of the ping test.
Step 5 View the number of transmitted and received packets, packet loss ratio, and delay in the test
result list, and determine the PW status.
NOTE
When the received packets are less than the transmitted packets, it indicates that packet loss occurs.
Step 6 Select PW50 on NE1, and perform Steps 1 to 5 to perform a new ping test. Set the parameters
as follows.
TIP
Among the following parameters, only the value of Peer PW ID is different from the value that is set for
the preceding ping test.
Parameter
Packet Count
EXP Value
TTL
255
100
Packet Length
64
Wait-to-Response Timeout Time(10ms)
300
Response Mode
IPv4 UDP Response
Peer PW ID
70
Peer IP
10.2.3.4
----End
Issue 03 (2012-11-30)

580
OptiX OSN 7500 II/7500/3500/1500

15 MS-PW

This topic describes the alarms and performance events that are related to the MS-PW.

None.

None.
15.11 MS-PW Parameters

This topic describes the parameters associated with a PW.
Table 15-5 Parameters for a multi-hop PW
Field
Value Range
Description
ID
For example, 1
Specifies the ID of a multihop PW.
Service Type
Ethernet Service, CES

Service, ATM Service

service that can be
transmitted over a multi-hop
PW.
Name
For example, MS-PW1
Specifies the name of a multihop PW.
MTU(bytes)
46 to 9000
Specifies the maximum

length of the packets that can
be transmitted over a multihop PW.
For example, 9000
Deployment Status
Deployed, Undeployed
Displays the current

deployment state of a multisegment PW.
Table 15-6 General attributes of the PW
Issue 03 (2012-11-30)
Field
Value Range
Description
PW ID
For example, 1
Specifies the ID of the PW.
Enable State
Enabled, Disabled
Display the enable state of the PW.

581
OptiX OSN 7500 II/7500/3500/1500

15 MS-PW
Field
Value Range
Description
PW Signaling Type
Static
The PW Signaling Type parameter

specifies the allocation mode
(automatic or manual) of ingress and
egress nodes of a PW.
Click PW Signaling Type for more
information.
Ethernet, Ethernet
Tagged Mode,
CESoPSN, SAToP
PW Type
Displays the type of the PW.

l When Service Type is set to
Ethernet Service, PW Type can
be set to only Ethernet or
Ethernet Tagged Mode.
l When Service Type is set to CES
Service, PW Type can be set to
only CESoPSN or SAToP.
Direction
Bidirectional
Displays the direction of the PW.
PW Encapsulation Type
MPLS
Displays the encapsulation type of

the packets on the PW.
PW Ingress Label/Source
Port
For example, 17
This parameter needs to be set when

PW Signaling Type is set to Static.
NOTE
The value ranges from
16 to 32768, in step of
2048.
For the OptiX OSN
1500, the maximum
value is 2048. For the
OptiX OSN 3500/7500,
the maximum value is
32768.
PW Egress Label/Sink Port
For example, 18
NOTE
The value ranges from
16 to 32768, in step of
2048.
This parameter needs to be set when

PW Signaling Type is set to Static.
For the OptiX OSN

1500, the maximum
value is 2048. For the
OptiX OSN 3500/7500,
the maximum value is
32768.
Issue 03 (2012-11-30)
Opposite LSR ID
For example,
10.70.71.123
Specifies the LSR ID of the PW at the

remote end.
Local Working Status
Example: Up
Display the local working status of

the PW.
Remote Working Status
Example: Down
Display the remote working status of

the PW.

582
OptiX OSN 7500 II/7500/3500/1500

15 MS-PW
Field
Value Range
Description
Compositive Working
Status
Up, Down
Display the compositive working

status of the PW.
Compositive Working Status is up
only when Local Working Status
and Remote Working Status are
up.
Tunnel Type
MPLS
Displays the type of the tunnel that

carries the PW.
Tunnel
For example, 43
A created tunnel needs to be selected.

If no tunnel is available, no PW can
be created.
Deployment Status
Deployed,
Undeployed
Displays the current deployment

state of a PW.
Tunnel Automatic
Selection Policy
For example: Static

MPLS Tunnel
Display the tunnel automatic

selection policy.
Table 15-7 QoS parameters for a multi-hop PW

Field
Value Range
Description
Bandwidth Limit
Enabled, Disabled
Displays the bandwidth limit.

If Bandwidth Limit is
enabled, the committed
information rate (CIR) and
peak information rate (PIR)
can be set.
Policy
Issue 03 (2012-11-30)
For example, 5

Displays the QoS policy ID

of the PW.
583
OptiX OSN 7500 II/7500/3500/1500

15 MS-PW
Field
Value Range
Description
Committed Information Rate

(Kbit/s)
1024-10000000, Unlimited
The Committed
Information Rate (Kbit/s)
parameter specifies the CIR
of the queue. The packets
whose rates are less than the
CIR can be forwarded. When
the rate of the packets is not
more than the CIR, all
messages can be forwarded.
If the rate of the packets is
more than the CIR, some
packets are discarded
according to a certain packet
discarding policy.
Default: 4294967295
(FFFFFFFFFF is invalid)
Click A.10.26 Committed

Information Rate (Kbit/s)
-
CBS(byte)
The CBS(byte) parameter

specifies the committed burst
size.
NOTE
to a multi-hop PW.
Peak Information Rate (kbit/

s)
64-10000000
Default: 4294967295
The Peak Information Rate

(kbit/s) parameter specifies
the maximum rate of services
allowed by the PIR.
Click A.10.28 Peak
Information Rate (kbit/s)
PIR(Kbit/s)
The PIR(Kbit/s) parameter

specifies the maximum rate
of services allowed, also
called the peak information
rate (PIR).
NOTE
to a multi-hop PW.
EXP
0, 1, 2, 3, 4, 5, 6, 7, None
Default: None
The EXP parameter specifies

the field in the MPLS packets
for identifying the priority of
these MPLS packets.
Click A.10.30 EXP for more
information.
Issue 03 (2012-11-30)

584
OptiX OSN 7500 II/7500/3500/1500

15 MS-PW
Field
Value Range
Description
LSP Mode
Pipe, Uniform
The LSP Mode parameter

specifies the mode in which
the MPLS network processes
packet priorities.
Default: Uniform
Click A.10.31 LSP Mode for

more information.
Table 15-8 Advanced attributes of a multi-hop PW

Field
Value Range
Description
PW ID
Example: 5
Display the PW ID.
Control Word
No Use, Used First
The Control Word

parameter specifies the PW
control word usage policy.
Default: -
Click A.8.1 Control Word

None, CW
Default: CW
The Control Channel Type

parameter specifies the type
of channels for transmitting
VCCV packets.
Click A.8.2 Control
Channel Type for more
information.
None, Ping
Default: Ping
The VCCV Verification

Mode parameter specifies
the verification mode of
VCCV packets.
Click A.8.3 VCCV
Verification Mode for more
information.
Request VLAN
NOTE
For the OptiX OSN equipment,
this parameter is not applicable
to a multi-hop PW.
TP ID
Issue 03 (2012-11-30)
1 to 65535

The Request VLAN

parameter specifies the ETH
request VLAN.
The parameter value for the

local equipment must be the
same as that for the
connected equipment.
585
OptiX OSN 7500 II/7500/3500/1500

16
16 Packet-based linear MSP
Packet-based linear MSP
About This Chapter

The packet-based linear MSP scheme is applicable to a point-to-point physical network,
providing MS-layer protection for the service between two points.
16.1 Introduction to Packet-based linear MSP
The packet-based linear MSP uses the MSOH bytes K1 and K2 to implement automatic
protection switching and thus to protect services. OptiX OSN equipment supports 1+1 and 1:1
packet-based linear MSP.
16.2 Basic Concepts
The packet-based linear MSP scheme uses the K1 and K2 bytes in the MSOH to transfer
switching requests and thus to implement automatic protection switching. Different types of
packet-based linear MSP are available with regard to the protection scheme, switching mode,
and revertive mode.
16.3 Specifications
This section describes the capacity of the OptiX OSN equipment for supporting packet-based
linear MSP specifications.
This topic describes the standards and protocols that linear MSP complies with.
16.5 Availability
The packet-based linear MSP function requires the support of the applicable equipment and
boards.
This section describes the limitations on and precautions for packet-based linear MSP in the
16.7 Principles
Packet-based linear MSP uses the K1 and K2 bytes in the MSOH of an SDH frame to transmit
the protocol information and thus to control the receive and transmit trails of the service. In this
manner, packet-based linear MSP provides protection for the MS-layer service. Generally,
packet-based linear MSP is classified into 1+1 packet-based linear MSP and 1:N packet-based
linear MSP.
Issue 03 (2012-11-30)

586
OptiX OSN 7500 II/7500/3500/1500

Packet-based linear MSP protects channelized STM-1 services between Hybrid MSTP devices
and RNC devices.
16.9 Creating Packet-Based Linear MSP
To protect the services transmitted on a point-to-point chain network, create packet-based linear
MSP on the packet plane.
16.10 Verifying Packet-Based Linear MSP
After a network is configured with Packet-Based linear MSP, services in the working path of
the Packet-Based linear MSP group can be protected.
This topic describes the alarms and performance events that are related to Packet-Based Linear
MSP.
Issue 03 (2012-11-30)

587
OptiX OSN 7500 II/7500/3500/1500

16.1 Introduction to Packet-based linear MSP

The packet-based linear MSP uses the MSOH bytes K1 and K2 to implement automatic
protection switching and thus to protect services. OptiX OSN equipment supports 1+1 and 1:1
packet-based linear MSP.
1+1 Packet-based linear MSP

1+1 packet-based linear MSP requires one working path and one protection path. At the source
end, the service is dually fed to the working path and protection path. At the sink end, the service
is received from the working path. When the working path becomes faulty, the service is received
from the protection path. Figure 16-1 shows the application of 1+1 packet-based linear MSP.
Figure 16-1 1+1 Packet-based linear MSP
NE A
NE B
Working path
Protection path
Protection
switching
NE A
Working path
NE B
Protection path
1:1 Packet-based linear MSP

1:1 packet-based linear MSP requires one working path and one protection path. Common
services are transmitted in the working path. When the working path becomes faulty, the service
in this path is switched to the protection path. Figure 16-2 shows the application of 1:1 packetbased linear MSP.
NOTE
The extra traffic can not be transmitted in the protection path.
Issue 03 (2012-11-30)

588
OptiX OSN 7500 II/7500/3500/1500

Figure 16-2 1:1 Packet-based linear MSP

NE A
Working path
NE B
Common
service
Common
service
Protection path
Protection switching
NE A
Common
service
Working path
NE B
Common
service
Protection path
Purpose
The packet-based linear MSP scheme uses the MSOH bytes K1 and K2 to implement automatic
protection switching once the working path fails, and thus to protect services.
16.2 Basic Concepts

The packet-based linear MSP scheme uses the K1 and K2 bytes in the MSOH to transfer
switching requests and thus to implement automatic protection switching. Different types of
packet-based linear MSP are available with regard to the protection scheme, switching mode,
and revertive mode.
Meanings of K Bytes
Table 16-1 provides the meanings of K bytes in the MSOH.
Table 16-1 Meanings of K bytes (linear MSP)
Issue 03 (2012-11-30)
K Byte
Meaning
K1 (bits 1 to 4)
The four bits carry the bridging request code. Table 16-2 provides
the meanings of the four bits.

589
OptiX OSN 7500 II/7500/3500/1500

K Byte
Meaning
K1 (bits 5 to 8)
The four bits indicate the number of the service signal to which
the bridging request corresponds. 0 represents the null signal,
1-14 represent normal service signals, and 15 represents the extra
service signal (applicable only to the 1:N mode).
K2 (bits 1 to 4)
The four bits carry the number of the service signal that bridges
the local end and the path. The value range of the four bits is the
same as the four bits (bits 5 to 8) of K1.
K2 (bit 5)
This bit indicates the protection mode. 1 represents the 1:N mode.
0 represents the 1+1 mode.
K2 (bits 6 to 8)
The three bits indicate the status. 000 represents the idle state,
111 represents the MS-AIS state, and 110 represents the MS-RDI
state.
NOTE
The OptiX OSN equipment supports 1:1 packet-based linear MSP.
Table 16-2 Bridging request code
Issue 03 (2012-11-30)
K1 (bits 1 to bit 4)
Meaning
1111
Lockout of protection path
1110
Forced switching
1101
Failure of the high-priority signal
1100
Failure of the low-priority signal
1011
Degradation of the high-priority signal
1010
Degradation of the low-priority signal
1001
Unused
1000
Manual switching
0111
Unused
0110
WTR
0101
Unused
0100
Exercise switching
0011
Unused
0010
Reverse request
0001
Non-revertive
0000
No request
590
OptiX OSN 7500 II/7500/3500/1500

NOTE
A reverse request assumes the priority of the bridging request to which it responds.
Protection Type
With regard to the protection scheme, packet-based linear MSP is available in the following
types: 1+1 packet-based linear MSP and 1:1 packet-based linear MSP.
l
1+1 packet-based linear MSP

1+1 packet-based linear MSP requires one working path and one protection path. At the
source end, the service is dually fed to the working path and protection path. At the sink
end, the service is received from the working path. When the working path becomes faulty,
the service is received from the protection path.
1:1 packet-based linear MSP

1:1 packet-based linear MSP requires one working path and one protection path. Common
services are transmitted in the working path. When the working path becomes faulty, the
service in this path is switched to the protection path.
With regard to the switching mode, packet-based linear MSP is available in the following types:
single-ended switching and dual-ended switching.
l
Single-ended switching
When one end detects a fault, protection switching occurs at the faulty end only, and the
other end remains the same.
Dual-ended switching
When one end detects a fault, protection switching occurs at both ends at the same time,
no matter whether the other end is faulty.
With regard to the revertive mode, packet-based linear MSP is available in the following types:
revertive mode and non-revertive mode.
l
Revertive mode
When an NE is in the switching state, the NE releases the switching and returns to the
normal state if the working path is restored to normal and this state lasts for a certain period.
The period after the working path is restored to normal and before the NE releases the
switching is called the WTR time. To prevent frequent switching events due to the unstable
working path, it is recommended that you set the WTR. In revertive mode, the working
path is restored to normal within the WTR time and the service is switched from the
protection path back to the working path.
Non-revertive mode
When an NE is in the switching state, the NE remains the current state unchanged even if
the working path is restored to normal, and the service is not switched from the protection
path back to the working path.
Issue 03 (2012-11-30)

591
OptiX OSN 7500 II/7500/3500/1500

Linear MSP Switching State
Issue 03 (2012-11-30)
Switchi
ng State
Description
Channel
Bearing
Services
Force to
Standby
Forces the service to switch from the working channel to the

protection channel. This switching is performed regardless of
the protection channel state, unless the protection channel is
satisfying a higher priority bridging request.
Protection
channel
Force to
Active
Switches the services from the protection channel to the

working channel if the working channel is normal. No
switching occurs if the working channel has an SF condition,
or a higher priority switching has occurred.
Working
channel
Switch
upon
Signal
Failure
Indicates that service is switched to the protection channel when

the SF condition is generated in the working channel and the
protection channel has no higher priority switching request.
Protection
channel
Signal
FailProtecti
on
Switches the service back to the working channel, when the

signal failure (SF) condition is generated in the protection
channel and the working channel has no higher priority
switching request.
Working
channel
Switch
upon
Signal
Degrada
tion
Indicates that services are switched to the protection channel

when the SD condition is generated in the working channel and
the protection channel has no higher priority switching request.
Protection
channel
Signal
Degrade
Protecti
on
Switches the service back to the working channel, when the

signal degrade (SD) condition is generated in the protection
channel and the working channel has no higher priority
switching request.
Working
channel
Manual
to
Standby
Switches the services from the working channel to the

protection channel if the protection channel is normal. No
switching occurs if the protection channel has an SF condition,
Protection
channel
Manual
to Active
Switches the services from the protection channel to the

working channel if the working channel is normal. No
switching occurs if the working channel has an SF condition,
Working
channel
WaitToRestore
Switches the service back to the working channel within the

wait-to-restore (WTR) time, when the SD or SF condition in
the working channel clears.
Protection
channel
Exercise
Simulates a protection switching, but no real switching is

carried out. The command is issued and the multiplex section
protection function of the network is tested without affecting
the service.
Working
channel

592
OptiX OSN 7500 II/7500/3500/1500

Switchi
ng State
Description
Channel
Bearing
Services
NonRevertiv
e
Switchin
g
Indicates that the service remains in the protection channel after

the SF condition in the working channel clears.
Protection
channel
Idle
Indicates that services are working in the working channel, and

both the working and protection channels are normal.
Working
channel
Unknow
n
Indicates that the switching status is unknown. You can learn

about the current status by querying it.
Lockout
Indicates that services are locked in the working channel and

no protection switching can be performed.
Working
channel
16.3 Specifications
This section describes the capacity of the OptiX OSN equipment for supporting packet-based
linear MSP specifications.
Table 16-3 provides specifications associated with packet-based linear MSP.
Table 16-3 Specifications associated with packet-based linear MSP
Item
Specifications
Support capability
20
Protection Type

Revertive Type
l Revertive
l Non-revertive
l Revertive: 6 s to 720 s, 600 s by default.
WTR Time
l Non-revertive: Switching Protocol
l 1+1 single-ended switching: not required

l 1+1 dual-ended switching: APS protocol
l 1:1 dual-ended switching: APS protocol
Issue 03 (2012-11-30)
Switching Time
50 ms
Hold-Off Time
0 s to 10 s (0 s by default)

593
OptiX OSN 7500 II/7500/3500/1500

Item
Specifications
Switching Condition
(Any of the Following
conditions Triggers the
Switching.)
l R_LOS
l R_LOF
l MS_AIS
l B2_EXC
l B2_SD (optional)
l Forced switching
l Manual switching
l Clear switching
l Lockout switching

This topic describes the standards and protocols that linear MSP complies with.
Linear MSP complies with the following standards and protocols:
l
ITU-T G.841: Types and characteristics of SDH network protection architectures
ITU-T G.842: Cooperation of the SDH network protection structure
16.5 Availability
The packet-based linear MSP function requires the support of the applicable equipment and
boards.
Version Support
Issue 03 (2012-11-30)
Product Name
Applicable Version
OptiX OSN 3500/7500
U2000
Product Name
Applicable Version
OptiX OSN 7500 II
U2000

594
OptiX OSN 7500 II/7500/3500/1500

Hardware Support
Board Type
Version
N1CQ1
OptiX OSN 3500/7500
TNN1CO1
OptiX OSN 7500 II
TNN1AFO1
OptiX OSN 7500 II

This section describes the limitations on and precautions for packet-based linear MSP in the

Applicable
Object

Details
Remarks
Packet-based
linear MSP
Packet-based linear MSP can be set

in two ways: 1+1 and 1:N. 1:N
packet-based linear MSP can only
be 1:1 packet-based linear MSP.
Packet-based
linear MSP
No extra traffic can be configured in

the protection channel in a 1:1
packet-based linear MSP group.
Packet-based
linear MSP
and ATM
PWE3
1+1 packet-based linear MSP is

recommended for the optical ports
on the TNN1AFO1 board.

None.
None.
16.7 Principles
Packet-based linear MSP uses the K1 and K2 bytes in the MSOH of an SDH frame to transmit
the protocol information and thus to control the receive and transmit trails of the service. In this
manner, packet-based linear MSP provides protection for the MS-layer service. Generally,
packet-based linear MSP is classified into 1+1 packet-based linear MSP and 1:N packet-based
linear MSP.
Issue 03 (2012-11-30)

595
OptiX OSN 7500 II/7500/3500/1500

Packet-based linear MSP is generally triggered by the following conditions:

l Fault on a board: fault on a key board (for example, power-off or offline of a line board)
l Signal fail (SF): R_LOS, R_LOF, MS_AIS, B2_EXC
l Signal degrade (SD): B2_SD
NOTE
Any of the preceding conditions can trigger the packet-based linear MSP switching. This topic mainly
considers the fault in the protection path as an example to describe how to trigger the packet-based linear
MSP switching.
1+1 Packet-based linear MSP

When the signal in the working path fails, the single-ended switching of 1+1 packet-based linear
MSP is implemented as follows:
1.
2.
3.
4.
5.
Before the switching, the source end sends service signals to the working path and the
protection path. The sink end selects the service signal from the working path.
When detecting that the signal in the working path fails, the line board at the sink end in a
certain direction (NE A) reports the SF event to the system control board.
The system control finds that the signal in the working path fails and that the signal in the
protection path is normal, it instructs the cross-connect board to complete the crossconnection between the protection path and the service sink.
NE A receives the service signal from the protection path.
NE B receives the service signal from the working path.
When the signal in the working path fails, the dual-ended switching of 1+1 packet-based linear
MSP is implemented as follows:
1.
2.
3.
4.
5.
Before the switching, the source end sends service signals to the working path and the
protection path. The sink end selects the service signal from the working path.
When detecting that the signal in the working path fails, the sink end in a certain direction
(NE A) sends the K bytes to the source end (NE B) through the protection path (the request
type is "signal fail").
NE B sends the K bytes to NE A also through the protection path (the request type is "reverse
request").
NE A receives the service signal from the protection path.
NE B also receives the service signal from the protection path.
Figure 16-3 Realization principle of 1+1 Packet-based linear MSP (before the switching)
NE B
Working
path
NE A
Protection
path
Working
path
Protection
path
Common service
Issue 03 (2012-11-30)

596
OptiX OSN 7500 II/7500/3500/1500

Figure 16-4 Realization principle of 1+1 Packet-based linear MSP (after the switching, in singleended mode)
NE B
Working
path
NE A
Protection
path
Working
path
Protection
path
Common service
Figure 16-5 Realization principle of 1+1 Packet-based linear MSP (after the switching, in dualended mode)
NE B
Working
path
NE A
Protection
path
Working
path
Protection
path
Common service
1:N Packet-based linear MSP

When the signal in the working path fails, the switching of 1:1 packet-based linear MSP is
implemented as follows:
1.
Issue 03 (2012-11-30)
Before the switching, the source end and the sink end send and receive normal service
signals in the working path, and can not send and receive extra service signals in the
protection path.
597
OptiX OSN 7500 II/7500/3500/1500

2.
When detecting that the signal in the working path fails, the sink end in a certain direction
(NE A) sends the K bytes to the source end (NE B) through a path between NE A and NE
B (the request type is "signal fail").
3.
NE B bridges the normal service signals into the protection path and sends the K bytes to
NE A through a path between NE A and NE B (the request type is "reverse request").
4.
NE A receives normal service signals from the protection path and bridges the normal
service signals into the protection path.
5.
NE B receives the normal service signals from the protection path.
Figure 16-6 Realization principle of 1:1 Packet-based linear MSP (before the switching)
NE B
Working
path
NE A
Protection
path
Working
path
Protection
path
Common service
Figure 16-7 Realization principle of 1:1 Packet-based linear MSP (after the switching)
NE B
Working
path
NE A
Protection
path
Working
path
Protection
path
Common service

Packet-based linear MSP protects channelized STM-1 services between Hybrid MSTP devices
and RNC devices.
1+1 packet-based linear MSP and 1:1 packet-based linear MSP have similar applications; that
is, both protection types use the protection path to protect the service in the working path.
Issue 03 (2012-11-30)

598
OptiX OSN 7500 II/7500/3500/1500

Figure 16-8 Application of linear MSP

Channelized STM-1 Services
PSN
21-CQ1-1
3-PEG8
NE1
21-CQ1-2
RNC
NOTE
l In Figure 16-8, NE1 is an OptiX OSN 3500 NE. Other products have the same service configurations
and differ only in boards' valid slots. For slots valid for the boards that a product supports, see the
hardware description of the product.
l For details on the boards that an RNC device supports, see specific RNC documents.
As shown in Figure 16-8, TDM links are present between NE1 and the RNC; NE1 is connected
to the RNC through its CQ1 board. The STM-1 services that the RNC receives are transmitted
to NE1 through the CQ1 board and further to the PSN through the PEG8 board. To protect the
channelized STM-1 services between NE1 and the RNC, linear MSP needs to be configured on
both NE1 and the RNC.
NOTE
For details on how to configure the STM-1 services that are transmitted from the RNC to NE1 through the
CQ1 board and further to the PSN through the PEG8 board, see the configuration guide (packet transport
domain). On NE1, configure packet-based linear MSP; on the RNC, configure linear MSP. For
configurations on the RNC, see specific RNC documents.
1+1 packet-based linear MSP: Normally, common services are transmitted in the working
path and protection path, and are received from the working path. When the working path
between NE1 and the RNC fails, services are received from the protection path.
1:1 packet-based linear MSP: Normally, common services are transmitted in the working
path. When the working path between NE1 and the RNC fails, the services in the working
path are switched to the protection path.
16.9 Creating Packet-Based Linear MSP

To protect the services transmitted on a point-to-point chain network, create packet-based linear
MSP on the packet plane.
Prerequisites
l
Services must not be configured on the port where the protection channel exists.
Procedure
Step 1 In the NE Explorer, select the NE from the Object Tree and then choose Configuration > Packet
Configuration > Packet-Based Linear MS from the Function Tree.
Step 2 Click Create. The system displays the Create a Linear Multiplex Section dialog box.
Step 3 Set the attributes of the linear MSP group.
Issue 03 (2012-11-30)

599
OptiX OSN 7500 II/7500/3500/1500

NOTE
l The protection type can be set to 1+1 or 1:N. When the protection type is set to 1:N, 1:1 protection is
supported.
l When the protection type is set to 1:1, the extra traffic is not carried over the protection path.
Step 4 Click OK.

Step 5 Select the created protection group and click Start Protocol. Then, the protection group takes
effect.
Step 6 Optional: Select the created protection group and click Stop Protocol. Then, the protection
protocol stops.
NOTE
The APS protocol triggers protection switching when a fault occurs only after the APS protocol is started.
After you click Stop Protocol, the APS protocol cannot trigger protection switching when a fault occurs
because the APS protocol is not started.
----End
Follow-up Procedure
l
Modification of the parameters of packet-based linear MSP

Modification of the parameters of a packet-based linear MSP protection group does not
affect the carried services. The modified parameters take effect only in the case of protection
switching.
l
Issue 03 (2012-11-30)
Deletion of a packet-based linear MSP protection group

600
OptiX OSN 7500 II/7500/3500/1500

Before deleting a packet-based linear MSP protection group, check whether the service is
transmitted on the working channel. If the service is transmitted on the protection channel,
switch the service to the working channel and then delete the packet-based linear MSP
protection group.
After a packet-based linear MSP protection group is deleted, the carried services are not
protected and therefore are affected.
16.10 Verifying Packet-Based Linear MSP

After a network is configured with Packet-Based linear MSP, services in the working path of
the Packet-Based linear MSP group can be protected.
Prerequisites
l
The Packet-Based linear MSP must be created and configured on the U2000.
Tools, Equipment, and Materials

U2000
Procedure
Step 1 Check the switching status of the Packet-Based Linear MSP protection group under test.
1.
On the Main Topology of the U2000, right-click the NE configured with Packet-Based
Linear MSP. Choose NE Explorer from the shortcut menu to display the NE Explorer
window.
2.
In the Function Tree of NE Explorer, choose Configuration > Packet Configuration >
Packet-based Linear MS.
3.
Click Query and choose Query Protection Group from the shortcut menu to refresh the
configuration of protection groups on the NE.
4.
Click Query and choose Query Switching Status from the shortcut menu. Then, check
West Switching Status of the working and protection units in the protection group under
test. West Switching Status of both units should be Idle.
Step 2 Disable the working port of the LMSP protection group under test.
1.
In NE Explorer, select the board configured with the LMSP protection and choose
Configuration > Packet Configuration > Interface Management > SDH Interface from
the Function Tree.
2.
On the General Attributes tab, select the working port in the Packet-Based Linear MSP
protection group and set Laser Interface Enabling Status to Close.
Step 3 Check the switching status. If West Switching Status of either the working unit or protection
unit is Switching, it indicates a successful switching.
Step 4 Disable the working port of the Packet-Based Linear MSP protection group under test with
reference to Step 2.
Step 5 Revert the services to the working tunnel of the LMSP protection group.
l
Issue 03 (2012-11-30)
If Revertive Mode of the Packet-Based Linear MSP protection group is set to Revertive,
the services are reverted to the working tunnel when WTR expires.
601
OptiX OSN 7500 II/7500/3500/1500

If Revertive Mode of the Packet-Based Linear MSP protection group is set to NonRevertive, select the protection group and click the Inter-Board Mapping Relation tab,
right-click Protection Unit in Protection Unit, and choose Manual Switching to
Working from the shortcut menu.
----End

This topic describes the alarms and performance events that are related to Packet-Based Linear
MSP.

This topic describes the alarms that are related to Packet-Based Linear MSP.
Table 16-4 lists the alarms that are related to Packet-Based Linear MSP.
Table 16-4 Alarms related to Packet-Based Linear MSP
Alarm Name
Meaning
CES_APS_MAN
UAL_STOP
The CES_APS_MANUAL_STOP is an alarm indicating that the CES

MSP protocol is manually stopped. This alarm is reported when the CES
MSP protocol is manually stopped.
CES_APS_FAIL
The CES_APS_FAIL is an alarm indicating the CES MSP switching

failure. This alarm is reported when CES MSP switching fails.
CES_APS_INDI
The CES_APS_INDI is an alarm indicating the MSP state of the CES

service. This alarm is reported when the MSP configured for the CES
service is in the switching state.
CES_K1_K2_M
The CES_K1_K2_M is an alarm indicating the mismatch between the

K1 byte and the K2 byte. This alarm is reported when the path numbers
indicated in the transmitted K1 byte and the received K2 byte are
inconsistent and the inconsistency lasts for a period of time (160 ms by
default).
CES_K2_M
The CES_K2_M is an alarm indicating that a mismatched K2 byte is

detected. When the protection scheme used at the opposite end, which
is indicated by bit 5 of the received K2 byte, is different from the
protection scheme used at the local end for a period (2s by default), the
CES_K2_M alarm is reported.
CES_MS_APS_I
NDI_EX
The CES_MS_APS_INDI_EX is an extended indication alarm of the

MSP switching status. The alarm is reported when MSP switching is
performed, indicating that the service is in switched state.

There are no performance events that are related to Packet-Based Linear MSP.
Issue 03 (2012-11-30)

602
OptiX OSN 7500 II/7500/3500/1500

Issue 03 (2012-11-30)

603
OptiX OSN 7500 II/7500/3500/1500

17
17 Power Consumption Control
Power Consumption Control
About This Chapter

The power consumption control function enables users to manage the power consumption of
high power-consuming data boards and thus ensures the normal operation of the equipment.
17.1 Overview
The power consumption control function helps users manage the power consumption of high
power-consuming data boards and thus ensures the normal operation of the equipment.
17.2 Availability
The power consumption control function requires the support of the applicable equipment,
boards, and software.
17.3 Principles
Users can manage the power consumption of high power-consuming data boards by using the
power consumption control function. When the maximum power consumption of an NE fails to
meet the power consumption requirement of the actual configuration, the boards that support
the power consumption control function fail to work normally.
17.4 Setting the NE Power Consumption Threshold
After the NE power consumption threshold is set, if the NE power consumption crosses the
threshold, the U2000 displays a prompt to inform you of the situation. In this manner, the NE
can be protected from the damage that results from excessive power consumption.
17.5 Querying the Power Consumption of NEs and Boards
After querying the power consumption of NEs and boards, if you find that the power
consumption of NEs exceeds the threshold, you should replace these high power-consuming
boards with low power-consuming boards, or remove some unused boards.
This topic describes the alarms and performance events that are related to the power consumption
control function.
Issue 03 (2012-11-30)

604
OptiX OSN 7500 II/7500/3500/1500

17.1 Overview
The power consumption control function helps users manage the power consumption of high
power-consuming data boards and thus ensures the normal operation of the equipment.
Definition
The power consumption of an NE contains the following two types:
l
Physical power consumption: refers to the sum of the power consumption of all the physical
boards configured on the NE.
Logical power consumption: refers to the sum of the power consumption of all the logical
boards configured on the NE.
The logical board of any board cannot be created when the physical power consumption or the
logical power consumption of an NE exceeds the maximum power consumption.
NOTE
For details about the power consumption values of equipment subracks and boards, see Hardware
Description.
Purpose
The power consumption of equipment boards (specially, data boards) is constantly increasing.
When an NE is configured with maximum number of large power-consuming data boards, the
power board of the NE may fail to support the actual power consumption of the NE, thus resulting
in the abnormal operation of the NE. To prevent this, users can manage the power consumption
of the large power-consuming data boards by using the power control function.
17.2 Availability
The power consumption control function requires the support of the applicable equipment,
Version Support
Issue 03 (2012-11-30)
Applicable Version
OptiX OSN 1500/2500/3500/7500
V100R007 and later
T2000
U2000
Applicable Version
OptiX OSN 3500 II
V100R009 and later
T2000

605
OptiX OSN 7500 II/7500/3500/1500

Applicable Version
U2000
Applicable Version
OptiX OSN 7500 II
U2000
Hardware Support
l
The NG-SDH equipment series support the power consumption control function.
The boards that support the power consumption control function on the NG-SDH
equipment series are as follows:
Applicable Board
Applicable Version
N1EMS4
V100R007 and later
OptiX OSN 1500A/1500B/

2500/3500/3500 II/7500
N1EGS4
V100R007 and later

2500/3500/3500 II/7500
N3EGS4
V100R007 and later

2500/3500/3500 II/7500
N1EAS2
V100R008 and later
OptiX OSN 3500/3500 II/

7500
17.3 Principles
Users can manage the power consumption of high power-consuming data boards by using the
power consumption control function. When the maximum power consumption of an NE fails to
meet the power consumption requirement of the actual configuration, the boards that support
the power consumption control function fail to work normally.
NOTE
When the actual power consumption of an NE exceeds its permissible maximum power consumption, the
logical boards for all the newly inserted boards cannot be created successfully.
The board that supports the power consumption control function may be in either of the following
two states:
l
Issue 03 (2012-11-30)
Low power consumption state: In this state, service chips of the board are not initialized,
and the board cannot work normally. In this case, the board makes a request to the NE
software for entering the high power consumption state.

606
OptiX OSN 7500 II/7500/3500/1500

High power consumption state: In this state, all the service chips of the board are initialized,
and the board can work normally.
Figure 17-1 shows the migration between the low power consumption state and the high power
consumption state of a board.
Figure 17-1 Migration of power consumption states
Successful
board addition
Low power
consumption
state
Cold resetting
of the board
High power
consumption
state
Successful
board deletion
If a board can be successfully added, the NE software issues a command to enable it to enter the
high power consumption state. In this case, the board enters the high power consumption state.
After the service chips of the boards are initialized, the board starts to work normally.
If a board is being deleted or is not configured, or if a cold reset is performed on a board, the
board remains in the low power consumption state.
17.4 Setting the NE Power Consumption Threshold

After the NE power consumption threshold is set, if the NE power consumption crosses the
threshold, the U2000 displays a prompt to inform you of the situation. In this manner, the NE
can be protected from the damage that results from excessive power consumption.
Prerequisites
Procedure
Step 1 Choose Configuration > NE Batch Configuration > Power Management from the Main
Menu.
Step 2 In the Object Tree, select one or more NEs and click
Step 3 In the NE Power Consumption Threshold(W) field, set the NE power consumption threshold.
NOTE
A default value is set in the NE Power Consumption Threshold(W) field for each type of NE. It is
recommended that you do not modify the value.
Step 4 Click Apply to display the Operation Result dialog box.

Issue 03 (2012-11-30)

607
OptiX OSN 7500 II/7500/3500/1500

Step 5 Click Close.

----End
17.5 Querying the Power Consumption of NEs and Boards

After querying the power consumption of NEs and boards, if you find that the power
consumption of NEs exceeds the threshold, you should replace these high power-consuming
boards with low power-consuming boards, or remove some unused boards.
Prerequisites
Procedure
Step 1 Choose Configuration > NE Batch Configuration > Power Management from the Main
Menu.
Step 2 Query the power consumption according to the requirement.
l
Query the NE power consumption as follows.

1.
Click the NE Power tab.
2.
In the Object Tree, select one or more NEs and click
3.
Click Query to display the query result.
Query the board power consumption as follows.

1.
Click the Board Power tab.
2.
In the Object Tree, select one or more boards and click
3.
Click Query to display the query result.
----End

This topic describes the alarms and performance events that are related to the power consumption
control function.

This topic describes the alarms that are related to the power consumption control function.
Table 17-1 Alarms related to the power consumption control function
Issue 03 (2012-11-30)
Alarm Name
Meaning
BD_AT_LOWPOWER
The board works in the low power

consumption state.

608
OptiX OSN 7500 II/7500/3500/1500

Alarm Name
Meaning
NE_POWER_OVER
The power consumption of the NE crosses the

threshold.

None.
Issue 03 (2012-11-30)

609
OptiX OSN 7500 II/7500/3500/1500

18
18 Protection Solutions for a 3G Bearer Network
Protection Solutions for a 3G Bearer

Network
About This Chapter

To meet the requirements of a 3G bearer network, Huawei provides a variety of protection
schemes to ensure reliable operation of equipment. In addition, Huawei provides a complete set
of protection solutions applicable to some typical network topologies.
18.1 RNC Dual-Homing
In RNC dual-homing, two dual-homed nodes are connected to the same radio network controller
(RNC) through their own UNI-side links, so that the services on the mobile bearer network can
be protected. On a mobile bearer network comprised of the OptiX Hybrid MSTP equipment, the
dual-homing method protects the E-LAN services through MC-LAG when a dual-homed node,
UNI-side link of a dual-homed node, or NNI-side service of a dual-homed node fails.
18.2 Cross-Domain Protection
The OptiX OSN equipment can be deployed in two domains (TDM domain and packet domain)
to transmit EoS services from an SDH network to a packet network. Different service protection
schemes are required in the two domains.
18.3 Protection Solutions for Typical Network Topologies
The Hybrid MSTP equipment provides multiple protection combinations applicable to possible
typical topologies on a 3G bearer network for reliable end-to-end transmission.
Issue 03 (2012-11-30)

610
OptiX OSN 7500 II/7500/3500/1500

18.1 RNC Dual-Homing

In RNC dual-homing, two dual-homed nodes are connected to the same radio network controller
(RNC) through their own UNI-side links, so that the services on the mobile bearer network can
be protected. On a mobile bearer network comprised of the OptiX Hybrid MSTP equipment, the
dual-homing method protects the E-LAN services through MC-LAG when a dual-homed node,
UNI-side link of a dual-homed node, or NNI-side service of a dual-homed node fails.
18.1.1 Scenario Description

On a mobile bearer network, an RNC provides stringent requirements for service reliability.
Therefore, if the OptiX Hybrid MSTP equipment functioning as the convergence node is
interconnect with the RNC, two sets of the OptiX Hybrid MSTP equipment are required in dualhoming configuration. In addition, an MC-LAG is configured to work with the E-LAN
configuration to achieve RNC dual-homing.
Figure 18-1 shows a typical network topology for RNC dual-homing. E-Line services from the
NodeB are transmitted to the RNC over the packet switched network (PSN). NE2 and NE3 are
dual-homed nodes, but NE1 is not.
Figure 18-1 Typical network topology for RNC dual-homing
UNI side
NNI side
NE2
NE1
PW
APS/Tunnel
APS
NodeB
E-LAN
Tunnel
APS
A
MC-LAG
E-LAN
NE3
Dual-homed node
Non-dual-homed node
communication channel
Signal flow
Working channel
Active link (carrying services)
Protection channel
Standby link
(carrying no services)
Tunnel
Issue 03 (2012-11-30)

611
OptiX OSN 7500 II/7500/3500/1500

Details about the RNC dual-homing protection solution are as follows:

l
Service type on the non-dual-homing nodes: E-Line
NNI-side protection scheme: 1:1 MPLS tunnel APS/PW APS/PW FPS
Service type on the dual-homed nodes: E-LAN
UNI-side protection scheme: MC-LAG
Protection objects: NNI-side service channels, dual-homed nodes, and links on the UNI
side of dual-homed nodes
MPLS tunnel APS/PW APS/PW FPS and MC-LAG are independent of each other and then the
faults on the NNI side and on the UNI side can be processed separately. Therefore, efficiency
of protection switching and service reliability are improved.
Working Principle
As shown in Figure 18-2, E-Line services from the NodeB are transmitted to the RNC over the
PSN; NE1, NE2, and NE3 work with the RNC to achieve dual-homing protection of E-LAN
services.
Figure 18-2 RNC dual-homing
UNI side
NNI side
NE2
NE1
W
E-LAN
PW APS/MPLS
tunnel APS
NodeB
RNC
LAG1 A
MC-LAG
E-LAN
S
LAG3
LAG2
NE3
Dual-homed node
Non-dual-homed node
Signal flow
Working channel
Protection channel
Standby link
The RNC dual-homing protection solution consists of the NNI-side MPLS tunnel APS/PW
APS/PW FPS and the UNI-side MC-LAG between the dual-homed nodes.
Issue 03 (2012-11-30)

612
OptiX OSN 7500 II/7500/3500/1500

On the NNI side, a 1:1 MPLS tunnel APS/PW APS/PW FPS protection group is configured
on NE1.
On the UNI side, a LAG (LAG1) is configured on NE2 and a LAG (LAG2) is configured
on NE3 to form an MC-LAG between NE2 and NE3. In addition, a LAG (LAG3) is
configured on the RNC.
Meanwhile, E-LAN services are configured on the two dual-homed nodes (NE2 and NE3), and
UNI-NNI E-Line services are configured on NE1.
Normally, on the NNI side, services are carried on the working channel in the MPLS tunnel
APS/PW APS/PW FPS protection group; on the UNI side, MC-LAG functions to select either
of NE2 or NE3 as the active equipment for service forwarding. For example, if NE2 is selected
as the main equipment, services are carried by LAG1. Generally, the working channel in the
MPLS tunnel APS/PW APS/PW FPS protection group on the NNI side and the working link in
the MC-LAG protection group on the UNI side are specified to ensure that the working channel
on the NNI side and the working link on the UNI side are connected to the same dual-homed
node. Figure 18-2 shows the signal flow.
l
The UNI-Side Link Connected to the Working Node of the Dual-Homed Nodes Fails
The Working Channel Within the PSN Fails
The Working Node of the Dual-Homed Nodes Fails

NOTE
The following paragraphs and figures describe the working principle of the RNC dual-homing protection
solution when PW APS is configured on the NNI side. When MPLS tunnel APS is configured on the NNI
side, the working principle is similar.
Scenario 1: The UNI-Side Link Connected to the Working Node of the Dual-Homed
Nodes Fails
As shown in Figure 18-3, when the UNI-side link (LAG1) connected to the working node of
the dual-homed nodes fails, the protection switching is implemented as follows:
l
When the RNC detects a fault on the UNI-side working link (LAG1) that carries services,
the services are switched to the UNI-side protection link (LAG2). The services from the
RNC are transmitted to the protection port in the MC-LAG (port A on NE3).
Within the PSN, PW APS switching is not triggered. On NE3, the services are broadcast
within the E-LAN and then the services are transmitted to NE2 over the MC-link. Within
the packet network, the services are still carried by the working PW (PW1).
Issue 03 (2012-11-30)

613
OptiX OSN 7500 II/7500/3500/1500

Figure 18-3 Fault on the UNI-side link connected to the working node of the dual-homed nodes
NE2
A
NE1
PW1
E-LAN
PW APS
NodeB
LAG1
E-LAN
PW2
RNC
S
MC-LAG LAG3
A
A LAG2
NE3
Dual-homed node
Non-dual-homed node
Signal flow
Working PW
Protection PW

Standby link
A
S
Figure 18-3 shows the signal flow after the protection switching.
After the faulty link recovers, the way that services are restored is similar to the preceding
switching process.
Scenario 2: The Working Channel Within the PSN Fails

As shown in Figure 18-4, when the working PW (PW1) within the PSN is faulty, the protection
switching is implemented as follows:
l
When NE1 detects a fault on the working PW (PW1) by means of the PW OAM mechanism,
NE1 triggers PW APS switching. Services are switched to the protection PW (PW2).
Switching in the MC-LAG is not triggered. On NE3, the services are broadcast within the
E-LAN and then the services are transmitted to NE2 over the MC-link. On the UNI side,
services are still transmitted through the working port (port A on NE2) in the MC-LAG
group.
Issue 03 (2012-11-30)

614
OptiX OSN 7500 II/7500/3500/1500

Figure 18-4 Fault on the PSN

NE2
NE1
PW1
A
P
LAG1
E-LAN
PW APS
NodeB
PW2
MC-LAG
W
RNC
A
LAG3
E-LAN
A
LAG2
NE3
Dual-homed node
Non-dual-homed node
Service direction
Working PW
Protection PW

Standby link
A
S
After faulty PW recovers, the way that services are restored is similar to the preceding switching
process.
Scenario 3: The Working Node of the Dual-Homed Nodes Fails

As show in Figure 18-5, when the working node (NE2) of the dual-homed nodes is faulty, the
NNI-side working PW, MC-link, and UNI-side link connected to the working node are faulty
at the same time. In this scenario, the protection switching is implemented as follows:
l
When NE1 detects a fault on the working PW (PW1) by means of the PW OAM mechanism,
NE1 triggers the PW APS switching. Services are switched to the protection PW (PW2).
NE3 bidirectionally bridges the protection PW (PW2) onto the UNI-side protection link
(LAG2).
When the RNC detects a fault on the UNI-side working link (LAG1) that carries services,
the services are switched to the UNI-side protection link (LAG2).
Issue 03 (2012-11-30)

615
OptiX OSN 7500 II/7500/3500/1500

Figure 18-5 Fault on the working node of the dual-homed nodes

NE2
A LAG1
NE1
PW1
E-LAN
PW APS
NodeB
PW2
LAG3
MC-LAG
W
RNC
S
A
E-LAN
LAG2
A
NE3
Dual-homed node
Non-dual-homed node
Signal flow
Working PW
Protection PW

Standby link
A
S
After faulty node recovers, the way that services are restored is similar to the preceding switching
process.
CAUTION
The current protection solution cannot protect services when the following combinations of
faults occur:
l The UNI-side link fails after the MC-link is faulty: On the UNI side, the switching process
in the MC-LAG is similar to that as described in scenario 1. After the switching in the MCLAG, however, the services from the RNC are transmitted to the protection port (port A on
NE3). The MC-link is faulty, and as a result, the services fail to be transmitted to the working
channel (PW1) within the PSN.
l A fault occurs on the PSN after the MC-link is faulty: When a fault occurs on the PSN, the
PW APS switching is triggered and then the services are carried on the protection PW (PW2).
The UNI-side link works properly, and therefore the services are still carried by the working
port (port A on NE2). The MC-link is faulty, and as a result, the services received at PW2
fail to be transmitted to the NE where the working port in the MC-LAG group resides.
Issue 03 (2012-11-30)

616
OptiX OSN 7500 II/7500/3500/1500


To achieve RNC dual-homing, MPLS tunnel APS/PW APS/PW FPS, MC-LAG, and LAG
protection schemes are configured based on E-LAN services.
Figure 18-6 shows the process for configuring RNC dual-homing.
Figure 18-6 Configuration process for RNC dual-homing
Start
1. Configure E-LAN
services on the
dual-homed nodes
2. Configure E-Line
services on the
non-dual-homed nodes
3. Configure protection
on the UNI side
a. Configure the multichassis synchronous

b. Configure an
MC-LAG
4. Configure 1:1 MPLS

tunnel APS/PW APS
on the NNI side
End
Table 18-1 describes the operations in the configuration procedure for RNC dual-homing
protection.
Table 18-1 Flowchart for configuring RNC dual-homing
St
ep
Procedure
Description
Configuring E-LAN services on

the dual-homed nodes
Configure E-LAN services on the two dualhomed nodes, and bridge the UNIs, NNIs, and the
ports on the MC-link.
The multi-chassis synchronous communication
tunnel and the MC-link are carried by the same
physical link.
Issue 03 (2012-11-30)
Configuring E-Line services on the

non-dual-homed nodes

617
OptiX OSN 7500 II/7500/3500/1500

St
ep
Procedure
Configuri
ng
protection
on the
UNI side
Description
Configuring the
multi-chassis
synchronous
communication
channel
The dual-homed nodes transmit the information

about the working status of its connected UNI-link
to each other over the multi-chassis synchronous
communication channel. In addition, the dualhomed nodes negotiate the troubleshooting
actions through multi-chassis synchronous
communication.
Configure the information for multi-chassis
synchronous communication on the dual-homed
nodes before you configure an MC-LAG.
Configuring an MCLAG
1. Configure a LAG on each of the two dualhomed nodes.

2. Configure an MC-LAG for the two dualhomed nodes.
Configuring 1:1 MPLS tunnel

APS/PW APS/PW FPS on the NNI
side
l MPLS tunnel APS is applicable to services in

a tunnel. After protection switching, all the
services in the working tunnel are switched.
l PW APS/PW FPS is applicable to services on
a PW. After protection switching, all the
services on the working PW are switched.
l Configure MPLS tunnel OAM prior to MPLS
tunnel APS or PW OAM prior to PW APS/PW
FPS.
l MPLS tunnel APS and PW APS/PW FPS
cannot exist at the same tunnel.
CAUTION
When MPLS tunnel APS is configured on the NNI side,
the PWs in the working tunnel and in the protection
tunnel that connect the two dual-homed nodes and the
non-dual-homed node must be the same.
When a switching action is being performed on a cosourced but not co-sinked PW APS group, the NEs in
the group will report the PWAPS_LOST alarm.When
PW FPS and IWF are enabled at the same time, this
alarm will not be reported.
18.2 Cross-Domain Protection

The OptiX OSN equipment can be deployed in two domains (TDM domain and packet domain)
to transmit EoS services from an SDH network to a packet network. Different service protection
schemes are required in the two domains.
Issue 03 (2012-11-30)

618
OptiX OSN 7500 II/7500/3500/1500

18.2.1 Scenario Description

On a 3G mobile bearer network, some sets of the OptiX OSN equipment can convert the EoS
services from an SDH network to packet services by using the EoD board, and then transmit the
packet services to a packet ring in the upstream direction. At the level-1 convergence nodes,
cross-domain protection is required.
Figure 18-7 shows a scenario wherein EoS services are transmitted over two intersecting
domains. The EoS services from the NodeB are first transmitted in the TDM domain, and then
converged at NE2 and NE3. Afterwards, the EoS services are converted by the EoD boards on
the convergence nodes NE2 and NE3 to packet services and then are transmitted to the packet
domain in the upstream direction. Finally, the packet services are sent to the RNC.
NOTE
Figure 18-7 illustrates how the EoS services from only one NodeB are converged at NE2 and NE3. This
serves as an example for your easy understanding. On a live network, multi-level convergence of EoS
services is common, but the scenario in each time of convergence is similar.
Figure 18-7 Transmission of services between domains

Node
B
5-EDQ41 NE2
3-PEG8-1
7-SL1
RNC
3-PEG8-2
2-EFS4
TDM
domain
NE4
3-PEG8-3
3-PEG8-2
Packet
domain
3-PEG8-1
12-SL1
NE1
3-PEG8-1
5-EDQ41
3-PEG8-2
NE3
As shown in Figure 18-8, the following protection schemes can be configured for the services
that traverse two domains:
l
At NE4, configure SNCP to protect the EoS services from the NodeB.
At the convergence nodes NE2 and NE3, configure LAGs and an MC-LAG to protect crossdomain services in the TDM domain and packet domain respectively.
At NE1, NE2 and NE3, configure MPLS tunnel OAM or PW OAM. At NE1, configure
MPLS tunnel APS or PW APS to protect the packet services.
NOTE
MPLS tunnel APS and PW APS cannot exist at the same time. In this topic, configuration of MPLS tunnel
APS serves as an example. You can also select PW APS according to actual requirements.
Issue 03 (2012-11-30)

619
OptiX OSN 7500 II/7500/3500/1500

Figure 18-8 Protection for services traversing two domains

E-LAN services
NodeB
SNCP
MPLS tunnel
OAM (PW
OAM)
LAG
EPL services
MC-LAG NE2
NE4
RNC
E-Line
services
MPLS tunnel
APS (PW APS)
NE1
LAG
NE3
MPLS tunnel
OAM (PW
OAM)
E-LAN services

To achieve cross-domain protection, the EoD board is used and SNCP, MC-LAG, and MPLS
tunnel APS/PW APS are configured.
Table 18-2 shows the process for configuring cross-domain protection.
Figure 18-9 Flowchart for configuring cross-domain protection
Start
1.Configuring
Configure network
1.
network
ports
5. Configure
MPLS tunnels
2.2.Configuring
servicesinin
Configure services
the TDM domain
6. Configure
an MC-LAG
3. Configure SNCP
in the TDM domain
7. Configure MPLS
tunnel APS in the packet
domain
4. Configure LAGs
8.8.Configuring
servicesinin
Configure services
the packet domain
End
Issue 03 (2012-11-30)

620
OptiX OSN 7500 II/7500/3500/1500

NOTE
Configurations of services in the TDM domain, services in the packet domain, and cross-domain protection
do not need to be performed in a strict sequence. In the figure, the sequence numbers are used to facilitate
description.
Table 18-2 Flowchart for configuring cross-domain protection

Ste
p
Procedure
Description
Configuring
network ports
Configure the following parameters:

l Network ports in the TDM domain
Ethernet external ports
Ethernet internal ports
l Network ports in the packet domain
General attributes of Ethernet ports
Layer 3 attributes of Ethernet ports
Configuring
services in the
TDM domain
Generally, configure Ethernet private line (EPL) services in the TDM

domain. In the configuration process, specify such information as the
service source and sink.
Configuring
SNCP for the
services in the
TDM domain
Configure SNCP to enable the services in the TDM domain to be

transmitted in the specified timeslots on the transmission lines and
provide 1+1 protection for these services.
Configuring
LAGs
Configure LAGs at the VCTRUNK ports of the EDQ41 board on the

cross-domain NE.
NOTE
The EDQ41 board supports only the manual LAG in load non-sharing mode.
Configuring
MPLS tunnels
Configure an MPLS tunnel on a per-NE basis or in an end-to-end

manner. Set the tunnel ID, service name, tunnel label, ingress node,
egress node, and transit node according to the network planning.
NOTE
MPLS tunnels are not configured on the EDQ41 board.
Configuring
an MC-LAG
Specify the multi-chassis protocol communication tunnel when

configuring an MC-LAG on the cross-domain NE.
NOTE
The multi-chassis protocol communication tunnel is used to transmit protocol
synchronization messages between NEs.
Issue 03 (2012-11-30)

621
OptiX OSN 7500 II/7500/3500/1500

Ste
p
Procedure
Description
Configuring
protection in
the packet
domain
Configure MPLS tunnel APS or PW APS for packet services n the

packet domain.
l MPLS tunnel APS is applicable to services in a tunnel. After
protection switching, all the services in the working tunnel are
switched.
l PW APS is applicable to services on a PW. After protection
switching, only the services on the working PW are switched.
l Configure MPLS tunnel OAM prior to MPLS tunnel APS or PW
OAM prior to PW APS.
l MPLS tunnel APS and PW APS cannot exist at the same time.
NOTE
MPLS tunnel APS and PW APS are not configured on the EDQ41 board.
Configuring
services in the
packet domain
Configure E-LAN services on the cross-domain NE, and configure

E-Line services on the terminal NE.
NOTE
If you configure PW APS in the packet domain, set Protection Type to PW
APS when creating E-Line services carried by PWs.
18.3 Protection Solutions for Typical Network Topologies

The Hybrid MSTP equipment provides multiple protection combinations applicable to possible
typical topologies on a 3G bearer network for reliable end-to-end transmission.
18.3.1 Protection for a Typical Network Involving Overlapped

TDM Domain and Packet Domain
Hybrid MSTP equipment can construct a packet network over an original TDM network. This
topic describes a typical protection solution in this scenario.
Protection Solution
Figure 18-10 shows a protection solution for a network wherein the TDM domain and the packet
domain overlap. Generally, NE1 is an OptiX OSN 1500 or OptiX 155/622H (OptiX Metro 1000)
NE; NE2, NE3, and NE4 are OptiX OSN 3500/7500/7500 II NEs.
NOTE
The TDM network can be configured with MSP or SNCP, and no details are provided. This topic describes
the protection solution applicable to the packet network.
A packet network generally uses the RNC dual-homing method for protection. For details, see
18.1 RNC Dual-Homing. The protection solution is configured as follows:
l
On the NNI side, MPLS tunnel APS or PW APS is configured.
On the UNI side 2, LAGs and an MC-LAG are configured.
Issue 03 (2012-11-30)

622
OptiX OSN 7500 II/7500/3500/1500

Figure 18-10 A network wherein two domains overlap

NNI side
UNI side 1
UNI side 2
NE3
/
LSP
king
r
o
W
PW
E1
BTS
BSC
NE2
FE
NodeB
NE1
Pro
tect
ion
PW LSP/
RNC
NE4
TDM network
Packet switched
network
Working Principle
As shown in Figure 18-11, services are present between the NodeB and the RNC.
l
NNI side
Working path: NE1-NE2-NE3; protection path: NE1-NE2-NE4
UNI side 2
Working path: NE3-RNC; protection path: NE4-RNC
Figure 18-11 Faults on the network wherein two domains overlap

NNI side
UNI side 1
UNI side 2
NE3
/
LSP
king
Wor W
P
E1
BTS
BSC
2
NE2
FE
NodeB
NE1
Pro
tect
ion
PW LSP/
RNC
NE4
TDM network
Packet switched
network
Issue 03 (2012-11-30)

623
OptiX OSN 7500 II/7500/3500/1500

In normal situations, the signal flow between the NodeB and the RNC is as follows: NodeBNE1-NE2-NE3-RNC. When a fault occurs on the network, the signal flow changes as follows:
l
A fault on the working path on the NNI side (only at fault point 1)
On the NNI side, services are switched to the protection path; on the UNI side 2, services
are still transmitted over the working path.
The signal flow is as follows: NodeB-NE1-NE2-NE4-NE3-RNC.
A fault on the working path on the UNI side 2 (only at fault point 2)
On the NNI side, services are still transmitted over the working path; on the UNI side 2,
services are switched to the protection path.
Faults on the working paths both on the NNI side and the UNI side 2 (at fault points 1 and
2)
are switched to the protection path.
The signal flow is as follows: NodeB-NE1-NE2-NE4-RNC.
NOTE
l When any fault occurs on the working path on the NNI side, the protection switching process is similar.
This topic describes the protection switching process when a fault occurs at fault point 1 for your
reference.
l When a fault occurs on the protection path, services are not affected or switched. No details are
provided.
Restriction and Impact

On the NNI side, MPLS tunnel APS or PW APS can be configured.
18.3.2 Protection Solution for a Hybrid Network Consisting of

Hybrid MSTP Equipment and Routers
After being deployed on a Layer 2 network, sets of Hybrid MSTP equipment can be connected
to the RNC via routers. This application enhances scalability of networks based on the powerful
Layer 3 capabilities of routers. This topic describes typical protection solutions in this scenario.
Figure 18-12 shows another protection solution when sets of Hybrid MSTP equipment and
routers comprise a network. Generally, NE1 is an OptiX OSN 1500 or OptiX 155/622H (OptiX
Metro 1000) NE; NE2 and NE3 are OptiX OSN 3500/7500/7500 II NEs; NE2 and NE3 are
interconnected with routers.
PWs are configured between sets of Hybrid MSTP equipment for service transmission and then
are terminated on NE2 and NE3. After that, services are transmitted to the routers over a Layer
2 network.
The routers may not be strongly compatible with the Hybrid MSTP equipment. This solution is
applicable when devices of different vendors are interconnected with the Hybrid MSTP
equipment.
In this solution, the network consisting of only the Hybrid MSTP equipment is protected by
MPLS tunnel APS or PW APS/PW FPS.
Issue 03 (2012-11-30)

624
OptiX OSN 7500 II/7500/3500/1500

NOTE
The network between the routers and the RNC requires a protection solution applicable to Layer 3 networks,
and no details are provided. If using Huawei routers, see the user manuals of the routers for configuration
methods.
Figure 18-12 Protection solution
NE1
FE
Main LSP/PW
L3
L2
PWE3
Router 1
NE3
NodeB
St
an
db
y
VRRP
LS
P/
PSN
PW
MPLS tunnel APS/

PW APS
NE2
RNC
Router 2
Working Principle
l
Packet switched network (PSN) (consisting of NE1, NE2, and NE3)

Working path: NE1-NE3; protection path: NE1-NE2
Layer 2 network (consisting of NE2, NE3, Router 1, and Router 2)

Working path: NE3-Router1; protection path: NE2-Router2.
NOTE
This topic describes only the protection switching between the Hybrid MSTP equipment, and no details
about the protection switching between the routers and the RNC are provided.
Figure 18-13 Faults on the hybrid network consisting of Hybrid MSTP equipment and routers
NE1
FE
Main LSP/PW
L3
L2
PWE3
Router 1
NE3
NodeB
St
an
db
y
VRRP
LS
P/
PSN
PW
MPLS tunnel APS/

PW APS
Issue 03 (2012-11-30)
NE2

RNC
Router 2
625
OptiX OSN 7500 II/7500/3500/1500

In normal situations, the signal flow between the NodeB and the RNC is as follows: NodeBNE1-NE3-Router1-RNC. When a fault occurs on the network, the signal flow changes as
follows:
l
A fault on the working path on the PSN (only at fault point 1)

Within the PSN, services are switched to the protection path; within the Layer 2 network,
services are still transmitted on the working path
The signal flow is as follows: NodeB-NE1-NE2-NE3-Router1-RNC.
A fault on the working path on the Layer 2 network (only at fault point 2)
Within the PSN, services are still transmitted on the working path; within the Layer 2
network, services are switched to the protection path.
The signal flow is as follows: NodeB-NE1-NE3-NE2-Router2-Router1-RNC.
NOTE
When NE1, NE2, and NE3 are configured with PW APS/PW FPS protection, enable the IWF function
on NE2 and NE3. In this case, when a fault occurs at fault point 2, the system inserts an FDI packet
to the PW between NE3 and NE1 to trigger PW APS/PW FPS. After PW APS/PW FPS is performed,
Faults on the working paths both on the PSN and the Layer 2 network (at fault points 1 and
2)
Within the PSN network, services are switched to the protection path; within the Layer 2
network, services are switched to the protection path.
The signal flow is as follows: NodeB-NE1-NE2-Router2-Router1-RNC.

On the PSN, MPLS tunnel APS or PW APS/PW FPS can be configured.

Hybrid MSTP Equipment and PTN Equipment
Hybrid MSTP equipment can be used together with PTN equipment on a network. In this manner,
equipment on the live network can be fully utilized, and the network is capable of ALL-IP
evolution. This topic describes a typical protection solution in this scenario.
Protection Solution
Figure 18-14 shows a protection solution when Hybrid MSTP equipment and PTN equipment
comprise a network. Generally, NE1 is an OptiX PTN 910/950 NE; NE2, NE3, and NE4 are
OptiX OSN 3500/7500/7500 II NEs.
In this solution, the RNC dual-homing method is used. For details, see 18.1 RNC DualHoming. The protection solution is configured as follows:
l
On the NNI side, MPLS Tunnel APS or PW APS is configured.
Issue 03 (2012-11-30)

626
OptiX OSN 7500 II/7500/3500/1500


UNI side 1
NNI side 1
UNI side 2
NE4
king
Wor
FE
/PW
LSP
NE2
NodeB
NE1
RNC
Prot
ectio
n LS
P/PW
NE3
Hybrid MSTP
equipment
PTN
equipment
Working Principle
l
NNI side
Working path: NE1-NE2-NE4; protection path: NE1-NE2-NE3.
UNI side 2
Figure 18-15 Faults on the hybrid network consisting of Hybrid MSTP equipment and PTN
equipment
UNI side 1
NNI side
1
/PW
LSP
g
n
i
k
Wor
FE
NodeB
UNI side 2
NE4
NE2
NE1
Prot
ectio
n LS
RNC
P/PW
NE3
Hybrid MSTP
equipment
PTN
equipment
Issue 03 (2012-11-30)

627
OptiX OSN 7500 II/7500/3500/1500

In normal situations, the signal flow between NodeB and the RNC is as follows: NodeB-NE1NE2-NE4-RNC. When a fault occurs on the network, the signal flow changes as follows:
l
A fault on the working path on the NNI side (only at fault point 1)
are still transmitted on the working path.
A fault on the working path on the UNI side 2 (at only fault point 2)
On the NNI side, services are still transmitted on the working path; on the UNI side 2,
Faults on the working paths both on the NNI side and the UNI side 2 (at fault points 1 and
2)
The signal flow is as follows: NodeB-NE1-NE2-NE3-RNC.
NOTE
l When any fault occurs on the working path on the NNI side, the service protection switching is similar.
reference.
provided.

On the NNI side, MPLS tunnel APS or PW APS can be configured.

Hybrid MSTP Equipment and RTN Equipment
Hybrid microwave equipment can be used at the tail of a network for access of services, and
Hybrid MSTP equipment can be used to construct networks at the core and convergence layers.
This application minimizes the fiber resources required at the tail. In this scenario, you can refer
to the following protection scheme. This topic describes a typical protection solution in this
scenario.
Protection Solution
Figure 18-16 shows a protection solution when Hybrid MSTP equipment and RTN equipment
comprise a network. Generally, NE1 is an OptiX PTN 910 or OptiX RTN 950 NE; NE2 is an
OptiX OSN 1500 or OptiX 155/622H (OptiX Metro 1000) NE; NE3, NE4, and NE5 are OptiX
OSN 3500/7500/7500 II NEs.
1:1 MPLS tunnel APS or 1:1 PW APS is used on the NNI side 1.
The RNC dual-homing method is used for protecting the network between the Hybrid MSTP
equipment and the RNC. For details, see 18.1 RNC Dual-Homing.
l
On the NNI side 2, MPLS tunnel APS or PW APS is configured.
Issue 03 (2012-11-30)

628
OptiX OSN 7500 II/7500/3500/1500


UNI side 1
NNI side 1
Working LSP/
PW
NE1
FE
NE2
NNI side 2
/
LSP
king
r
o
W
PW
NE3
Protecti
NodeB
UNI side 2
NE4
on LSP
/P
RNC
Protection
LSP/PW
NE5
Hybrid MSTP
equipment
RTN
equipment
Working Principle
NOTE
On the NNI side 1, the RTN equipment is interconnected with the Hybrid MSTP equipment, 1:1 MPLS
tunnel APS or 1:1 PW APS is configured to protect the interconnection between the RTN equipment and
the Hybrid MSTP equipment.If a fault occurs on the working path on the NNI side 1, the signal flow on
the NNI side 2 is not affected. Therefore, this topic focuses on the signal flow on the NNI side 1 and UNI
side 2.
NNI side 2
Working path: NE2-NE3-NE4; protection path: NE2-NE3-NE5
UNI side 2
Issue 03 (2012-11-30)

629
OptiX OSN 7500 II/7500/3500/1500

Figure 18-17 Faults on the hybrid network consisting of Hybrid MSTP equipment and RTN
equipment
UNI side 1
NNI side 1
Working LSP/
PW
FE
NE1
NE2
NNI side 2
1
kin
Wor
P/PW
g LS
NE3
Protecti
NodeB
UNI side 2
NE4
RNC
on LSP
/PW
Protection LSP/
PW
NE5
Hybrid MSTP
equipment
RTN
equipment
In normal situations, the signal flow between the NodeB and the RNC is as follows: NodeBNE1-NE2-NE3-NE4-RNC. When a fault occurs on the network, the signal flow changes as
follows:
l
A fault on the working path on the NNI side 2 (only at fault point 1)
On the NNI side 2, services are switched to the protection path; on the UNI side 2, services
are still transmitted on the working path.
The signal flow is as follows: NodeB-NE1-NE2-NE3-NE5-NE4-RNC.
A fault on the working path on the UNI side 2 (only at fault point 2)
On the NNI side 2, services are still transmitted on the working path; on the UNI side 2,
The signal flow is as follows: NodeB-NE1-NE2-NE3-NE4-NE5-RNC.
Faults on the working paths both on the NNI side 2 and the UNI side 2 (at fault points 1
and 2)
On the NNI side 2, services are switched to the protection path; on the UNI side 2, services
NOTE
l When any fault occurs on the working path on the NNI side, the service protection switching is similar.
reference.
provided.

On the NNI side, MPLS tunnel APS or PW APS can be configured. On the NNI side 1, only 1:1
MPLS tunnel APS or 1:1 PW APS can be configured.
Issue 03 (2012-11-30)

630
OptiX OSN 7500 II/7500/3500/1500

19 RMON
19
RMON
About This Chapter

By using the remote monitoring (RMON) function, you can transmit network monitoring data
between different network sections.
19.1 Introduction to RMON
19.2 Basic Concepts
The RMON function is supported on the U2000. The monitoring of the performance and alarms
of Ethernet boards that support the RMON function can be realized by using the RMON function.
This topic describes the standards and protocols that RMON complies with.
19.4 Availability
The RMON function requires the support of the applicable equipment and boards.
This section describes the limitations on and precautions for RMON in the network design phase,
This topic considers project R as an example to describe the application of the RMON function
in the actual networking.
19.7 Configuring the RMON
This topic describes how to configure the RMON for the packet transmission service.
If the Ethernet service is interrupted or the performance degrades, you can enable the RMON
function on the U2000 and enable other functions such as the MPLS OAM function to locate
the position where the service is interrupted or the performance degrades.
This topic describes the alarms and performance events that are related to the RMON function.
Issue 03 (2012-11-30)

631
OptiX OSN 7500 II/7500/3500/1500

19 RMON
19.1 Introduction to RMON

Currently, the management of the Ethernet performance for transmission products is relevantly
simple. In the case of the management of Ethernet ports, the management of the performance
data of the ports is required. In addition, when the network is becoming more complex, a method
for managing network sections is required. Thus, the RMON technology emerges, with the
following advantages provided:
l
All statistics data is saved at the agent and the out-of-service operation on the manager is
supported.
History data is saved for the fault diagnosis.
Errors are detected and reported.
Detailed data is provided.
Multiple management stations are supported.
Based on the preceding purposes, the RMON function defines a serial of statistic formats and
functions to realize the data exchange between the control stations and detection stations that
comply with the RMON standards. To meet the requirements of different networks, the RMON
function provides flexible detection modes and control mechanism. In addition, the RMON
function provides error diagnosis, and planning and information receiving of the performance
events of the entire network.
19.2 Basic Concepts

The RMON function is supported on the U2000. The monitoring of the performance and alarms
of Ethernet boards that support the RMON function can be realized by using the RMON function.
The RMON function is realized through the following four modules.
19.2.1 SNMP
Currently, the Simple Network Management Protocol (SNMP) is the most widely used network
management protocol in the network. The SNMP is used to ensure transport of the management
information between any two nodes in the network. This facilitates the network administrator
to retrieve information, modify information, locate a fault, perform fault diagnosis, plan capacity,
and generate a report on any node in the network.
Architecture of the SNMP

The SNMP is divided into the network management station (NMS) and the agent.
l
NMS
The NMS is a workstation where the client program is running.
The NMS can send the request packets to the agent. After receiving these request
packets, the agent performs corresponding operations according to the packet types,
generates the response packets, and send the response packets to the NMS.
l
Issue 03 (2012-11-30)
Agent
632
OptiX OSN 7500 II/7500/3500/1500

19 RMON
The agent is server software that is running on the network equipment. It is embedded
in the Ethernet unit.
When an exception occurs in the equipment or the state of the equipment changes (for
example, the equipment restarts), the agent sends the Trap packet to the NMS and reports
the event to the NMS.
The transmission of SNMP packets is based on the connectionless transport layer UDP. Hence,
the equipment can be connected to a wide variety of equipment without a block.
MIB
The management information base (MIB) refers to the managed variables in SNMP packets that
are used to describe the managed objects in the equipment. The SNMP uses the architecture
naming solution to uniquely identify each managed object in the equipment. The overall
architecture is like a tree. The nodes on the tree indicate the managed objects. Each node can be
uniquely identified by a path starting from the root. The MIB is used to describe the architecture
of the tree and is the collection of the definitions of the standard variables of the monitored
network equipment.
NOTE
The OptiX OSN equipment uses Huawei proprietary MIB. For contents that the third-party system
monitored based on SNMP, consult field Huawei engineers.
19.2.2 Ethernet Statistics Group

Through the Ethernet statistics group, you can query the current statistics data of the real-time
performance of Ethernet ports.
19.2.3 Ethernet History Control Group

Through the history control group, you can set the method for obtaining the history data of each
Ethernet port, the number of items that are saved for each statistics value, and the enabling status
of the performance monitoring. You need to set the history table type and the value can be 30
seconds, 30 minutes, or a customized period. In the case of a customized period, you need to set
the sampling period.
19.2.4 Ethernet History Group

The Ethernet history group stores the statistics data of the Ethernet performance in a certain
history period. In this case, you can query the statistics data of an Ethernet port in a certain
history period. For the Ethernet history group, the performance items supported are the same as
those of the Ethernet statistics group.
19.2.5 Ethernet Alarm Group

The alarm group realizes the alarm function, in which alarm events are reported. It needs to
provide the functions of setting or querying alarm events. Alarm setting items include the alarm
reporting mode, upper or lower threshold of alarms, sampling interval, and enable/disable of the
monitoring status.
Issue 03 (2012-11-30)

633
OptiX OSN 7500 II/7500/3500/1500

19 RMON

This topic describes the standards and protocols that RMON complies with.
RMON complies with RFC 1757 and RFC 2819.
19.4 Availability
The RMON function requires the support of the applicable equipment and boards.
Version Support
Applicable Version
OptiX OSN 1500/2500/3500/7500
V100R006 and later
T2000
U2000
Applicable Version
OptiX OSN 3500 II
V100R009 and later
T2000
U2000
Applicable Version
OptiX OSN 7500 II
U2000
Hardware Support (TDM Mode)
Issue 03 (2012-11-30)
Applicable Board
Applicable Version
N1EMS4
V100R006 and later

2500/3500/3500 II/7500
N1EGS4
V100R006 and later

2500/3500/3500 II/7500
N3EGS4
V100R007 and later

2500/3500/3500 II/7500

634
OptiX OSN 7500 II/7500/3500/1500

Issue 03 (2012-11-30)
19 RMON
Applicable Board
Applicable Version
N1EFS4
V100R006 and later

2500/3500/3500 II/7500
N2EFS4
V100R006 and later

2500/3500/3500 II/7500
N2EFS0
V100R006 and later
OptiX OSN 1500B/

2500/3500/3500 II/7500
N4EFS0
V100R006 and later
OptiX OSN 1500B/

2500/3500/3500 II/7500
N2EGS2
V100R006 and later

2500/3500/3500 II/7500
N1EAS2
V100R008 and later
OptiX OSN 3500/7500
N1EGT2
V100R006 and later

2500/3500/3500 II/7500
R1EFT4
V100R006 and later

2500
N1EFT8
V100R006 and later

2500/3500/3500 II/7500
N1EFT8A
V100R006 and later

2500/3500/3500 II/7500
N2EMR0
V100R006 and later

2500/3500/3500 II/7500
N2EGR2
V100R006 and later

2500/3500/3500 II/7500
N3EFS4
V100R006 and later

2500/3500/3500 II/7500
N3EGS2
V100R006 and later

2500/3500/3500 II/7500
N4EGS4
V100R007 and later

2500/3500/3500 II/7500
N2EGT2
V100R006 and later

2500/3500/3500 II/7500
N5EFS0
V100R006 and later
OptiX OSN 1500B/

2500/3500/3500 II/7500
N1EFS0A
V100R009 and later
OptiX OSN 1500B/

2500/3500/3500 II/7500
N1EMS2
V100R009 and later

2500/3500/3500 II/7500

635
OptiX OSN 7500 II/7500/3500/1500

19 RMON
Hardware Support (Packet Mode)

Applicable Board
Applicable Version
N1PEG16
OptiX OSN 3500
N1PEX1
OptiX OSN 3500
N1PETF8
OptiX OSN 3500/7500
R1PEFS8
Q1PEGS2
R1PEGS1
N1PEG8
OptiX OSN 3500/7500
N2PEX1
OptiX OSN 3500/7500
N1PEX2
OptiX OSN 3500/7500
N1PEFF8
OptiX OSN 3500/7500
N1EDQ41
OptiX OSN 3500/7500
R1PEF4F
TNN1EX2
OptiX OSN 7500 II
TNN1EG8
OptiX OSN 7500 II
TNN1ETMC
OptiX OSN 7500 II
TNN1EFF8
OptiX OSN 7500 II

This section describes the limitations on and precautions for RMON in the network design phase,
Issue 03 (2012-11-30)

636
OptiX OSN 7500 II/7500/3500/1500

19 RMON

Applicable
Object

Details
Remarks
Management
group
l When you need to monitor the

current performance of a port in
real time, select the statistics
group.
l When you need to monitor

specific performance items of a
port in a long term, select the
alarm group.
l When you need to perform a
statistical analysis on the
performance of a port over a past
period of time, select the history
group and history control group.
Statistical
object
l To measure the performance of

an Ethernet port or ATM trunk
port, take the Ethernet port or
ATM trunk port as a statistical
object.

an MPLS tunnel, take the MPLS
tunnel as a statistical object.
an MPLS PW, take the MPLS
PW as a statistical object.
l To measure the performance of a
CES/ATM/Ethernet service,
take the CES/ATM/Ethernet
service as a statistical object.
Issue 03 (2012-11-30)

637
OptiX OSN 7500 II/7500/3500/1500

19 RMON
Applicable
Object

Details
Remarks
Statistics
l When you need to analyze the

exceptions occurred on a port,
select the following statistical
items: fragments, undersize
packets received, FCS errors,
pause frames received, pause
frames transmitted, and others.

traffic on a port, select the
following statistical items: bytes
received, bytes transmitted, and
others.
information on packet
transmitting and packet
receiving on a port, select the
following statistical items:
packets received, packets
transmitted, and others.
types of the transmitted and
received packets on a port, select
the following statistical items:
unicast packets received, unicast
packets transmitted, multicast
packets received, multicast
packets transmitted, broadcast
packets received, broadcast
packets transmitted, and others.

None.
None.

This topic considers project R as an example to describe the application of the RMON function
in the actual networking.
Issue 03 (2012-11-30)

638
OptiX OSN 7500 II/7500/3500/1500

19 RMON
Project Description
Project R uses the chain networking that consists of station A, station B, station C, station D,
and station E. Figure 19-1 shows the networking diagram of project R. For example, in the case
of a unidirectional service, station E needs to monitor the Ethernet services on station A.
Figure 19-1 Networking diagram of project R
Station C
Station D
Station A
Ethernet
Board
Ethernet
Board
Station B
Station E
Smartbits
In the case of project R, an Ethernet service GE1 exists between station A and station E. You
can enable the RMON function to realize the remote monitoring between station E and station
A. By querying the RMON performance of the corresponding Ethernet service board on station
E, you can learn the information, such as the service performance and alarms, of the Ethernet
board on the transmit end (that is, station A).
19.7 Configuring the RMON

This topic describes how to configure the RMON for the packet transmission service.
19.7.1 Browsing the History Group Performance of an Ethernet Port

The history group performance includes the statistics about the Ethernet performance of a certain
period in the past. You can learn about the Ethernet performance data of an Ethernet port by
browsing the history group performance.
Prerequisites
l
You must be an NM user with NE monitor authority or higher.
The Ethernet service must be configured.
The parameters of the performance monitoring must be set.
Procedure
Step 1 Select the corresponding Ethernet board in the NE Explorer. Choose Performance > RMON
Performance from the Function Tree.
Step 2 Click the History Group tab.
Step 3 Select the object from the drop-down list of Object. Set the range of the performance to be
browsed, Ended From, To, History Table Type, and Display Mode.
Issue 03 (2012-11-30)

639
OptiX OSN 7500 II/7500/3500/1500

19 RMON
Step 4 Click Query, and the information about the history group performance of the Ethernet port is
displayed.
----End
19.7.2 Browsing the Statistics Group Performance of an Ethernet

Port
You can learn about the real-time statistics about an Ethernet port by browsing the statistics
group performance of the Ethernet port.
Prerequisites
l
The Ethernet service must be configured.
The parameters of the performance monitoring must be set.
Procedure
Step 1 Select the corresponding Ethernet board in the NE Explorer. Choose Performance > RMON
Performance from the Function Tree.
Step 2 Click the Statistics Group tab.
Step 3 Select the object from the drop-down list of Object. Set the range of performance to be browsed,
Query Conditions, and Display Mode.
Step 4 Click Start. The information about the statistics group performance of the Ethernet port is
queried and then displayed.
----End
19.7.3 Customizing the RMON Performance Attribute Template

You can set the RMON performance quickly by customizing the RMON performance attribute
template.
Prerequisites
Context
The equipment supports the RMON performance monitoring for the physical port and the service
object. Hence, you can customize the RMON performance attribute template for the physical
port and the service object.
Procedure
Step 1 Select the NE in the NE Explorer. Use the following method to display the interface for browsing
the performance of the physical port or the service object.
Issue 03 (2012-11-30)

640
OptiX OSN 7500 II/7500/3500/1500

19 RMON
Type (Example)
Entry
Unicast Tunnel
Choose Configuration > Packet Configuration > MPLS

Management > Unicast Tunnel Management. Right-click
one or several Tunnels, and choose Browse Performance from
the shortcut menu.
Ethernet service
Choose Configuration > Packet Configuration > Ethernet

Service. Select one Ethernet service type. Right-click one or
several Ethernet services and choose Browse Performance
Link aggregation group
Choose Configuration > Packet Configuration > Interface

Management > Link Aggregation Group Management.
Right-click one or several link aggregation groups and choose
Browse Performance from the shortcut menu.
NOTE
If you need to display the interface for browsing the performance of other service objects, refer to the
examples listed in the table to find the proper entry.
Step 2 Click the RMON Setting tab.

Step 3 Click Event and set the parameters related to the event.
Step 4 Click Close. The setting is complete.
----End
19.7.4 Configuring an RMON History Control Group

You can determine the method for obtaining and saving the history data by configuring an
RMON history control group.
Prerequisites
Procedure
Step 1 Select the NE in the NE Explorer. Choose Performance > RMON History Control Group
from the Function Tree.
Step 2 Set parameters that are related to 30-Second, 30-Minute, Custom Period 1, and Custom Period
2.
NOTE
l The sampling period of the 30-Second and 30-Minute is fixed.

l Set the sampling period of Custom Period 1 and Custom Period 2 by setting the Period Length
parameter.
Step 3 Click Apply. A dialog box is displayed, indicating that the operation is successful.
Issue 03 (2012-11-30)

641
OptiX OSN 7500 II/7500/3500/1500

19 RMON
Step 4 Click Close.

----End

If the Ethernet service is interrupted or the performance degrades, you can enable the RMON
function on the U2000 and enable other functions such as the MPLS OAM function to locate
the position where the service is interrupted or the performance degrades.

This topic considers the OptiX OSN 3500 to form a network for the E-Line service as an example.
If a normal alarm-based method fails to locate a fault, you can enable the RMON function to
locate the fault in a data service.
Networking Diagram
An E-Line service that is carried by the pseudo wire (PW) is taken as an example, as shown in
Figure 19-2.
l
User A1 accesses NE1 through 21-PETF8-1, and User B1 accesses NE1 through 21PETF8-2.
User A2 accesses NE2 through 21-PETF8-1, and User B2 accesses NE2 through 21PETF8-2.
User A1 and User A2 need to communicate with each other. User B1 and User B2 to
communicate with each other.
Figure 19-2 Networking diagram for the E-Line service carried by the PW
UNI for A1:21-PETF8-1
UNI for B2:21-PETF8-2
UNI for A2:21-PETF8-1

UNI for B2:21-PETF8-2
PSN
User A2
User A1
NE 1
NE2
User B2
User B1
NNI:3-PEG16-1
NNI:3-PEG16-1
Unicast tunnel
PW
Issue 03 (2012-11-30)

642
OptiX OSN 7500 II/7500/3500/1500

19 RMON
Symptom
The data service between User A1 and User A2 becomes abnormal (the service is interrupted
or certain packets are lost).

When the service is interrupted or the signal degrades, you can enable the RMON function on
the U2000 locate the fault.
Prerequisites
Procedure
Step 1 Configure the Ethernet services that are carried by the PW. For details, see Configuration
Example: E-Line Services Carried by PWs.
Step 2 Refer to 19.7.4 Configuring an RMON History Control Group to enable the RMON function
of monitoring the performance in the history control groups.
The parameters for the history control group are set as follows:
l History table type: 30 seconds
l Monitored objects: NE
l Number of items: 50 (16 by default)
Step 3 Refer to 19.7.3 Customizing the RMON Performance Attribute Template to enable the
RMON function of monitoring the performance of the service.
The parameters are set as follows:
l History table type: 30 seconds
l Monitored objects: V-UNI, PW
l Monitoring status: Enabled
CAUTION
To query the statistics of the PW performance, you need to set the QoS policy for the PW.
Step 4 Refer to 19.7.1 Browsing the History Group Performance of an Ethernet Port and 19.7.2
Browsing the Statistics Group Performance of an Ethernet Port to query the performance
of the V-UNI on the Ethernet board at the same period.
Step 5 Analyze the RMON performance and check whether the data is proper.
l If the PAUSE frame exists, proceed to Step Step 7.
l If the FCS error exists, see the description of the handling of the FCS error performance event
in Alarms and Performance Events Reference.
l If the collision or fragment exists, see the description of the handling of the collision
performance event in Alarms and Performance Events Reference.
Issue 03 (2012-11-30)

643
OptiX OSN 7500 II/7500/3500/1500

19 RMON
l If the problem is about the maximum transmission unit (MTU), set the MTU to a proper
value.
1.
In the NE Explorer, select the Ethernet board. Choose Configuration > Ethernet
Service Management > E-Line Service in the Function Tree.
2.
Select the service and set MTU (bytes) to a proper value.
Step 6 Check the relation of the traffic between the ports on the Ethernet board.
l If the input traffic is equal to the output traffic, it indicates that the fault does not occur on
the board but may occur at the interconnection point between Huawei equipment and the
equipment of the customer. Enable the ping function to check the link between Huawei
equipment and the equipment of the customer.
l If the input traffic is not equal to the output traffic, it indicates that the fault occurs on Ethernet
board. Check the relation of the traffic between the V-UNI of the Ethernet board and the
corresponding PW to determine the board where the fault (congestion or signal degrade)
occurs.
Step 7 Enable the ping function to check whether the fault occurs on the link between Huawei equipment
and the interconnected data communication equipment.
----End

This topic describes the alarms and performance events that are related to the RMON function.
19.9.1 Statistics of RMON basic performance (packet domain)
Issue 03 (2012-11-30)
Name of a Performance
Entry
Description
Unit
Collisions/ETHCOL
The best estimate of the total

number of collisions on this
Ethernet segment.
times(times/s)
FCS and Alignment Errors/

ETHCRCALI
The total number of packets

packets(packets/s)
received that had a length
(excluding framing bits,
butincluding FCS octets) of
between 64 and 1518 octets,
inclusive, but had either a bad
Frame Check Sequence
(FCS) with an integral
number of octets (FCS Error)
or a bad FCS with a nonintegral number of octets
(Alignment Error).

644
OptiX OSN 7500 II/7500/3500/1500

Issue 03 (2012-11-30)
19 RMON
Entry
Description
Unit
Drop Events/ETHDROP
The total number of events in

which packets were dropped
by the probe due to lack of
resources. Note that this
number is not necessarily the
number of packets dropped; it
is just the number of times this
condition has been detected.
times(times/s)
Fragments/ETHFRG

received that were less than
64 octets in length (excluding
framing bits but including
FCS octets) and had either a
bad Frame Check Sequence
(FCS)with an integral number
of octets (FCS Error) or a bad
FCS with a non-integral
number of octets (Alignment
Error).
packets(packets/s)
Errored oversize packets

received/ETHJAB

packets(packets/s)
received that were longer than
1518 octets (excluding
framing bits, but including
FCS octets), and had either a
bad Frame Check Sequence
(FCS) with an integral
number of octets (FCS Error)
or a bad FCS with a nonintegral number of octets
(Alignment Error).
Broadcast Packets
Received/RXBRDCAST
The total number of good

packets received that were
directed to the broadcast
address. Note that this does
not include multicast packets.
packets(packets/s)
Multicast Packets Received/

RXMULCAST

directed to a multicast
address. Note that this
number does not include
packets directed to the
broadcast address.
packets(packets/s)

645
OptiX OSN 7500 II/7500/3500/1500

Issue 03 (2012-11-30)
19 RMON
Entry
Description
Unit
Octets Received/
RXOCTETS
The total number of octets of

data (including those in bad
packets) received on the
network (excluding framing
bits but including FCS
octets).
Byte(Byte/s)
Packets (1024-1518 bytes)

received/RXPKT1024

(including bad packets)
received that were between
1024 and 1518 octets in
length inclusive (excluding
FCS octets).
packets(packets/s)

received/RXPKT128

128 and 255 octets in length
inclusive (excluding framing
octets).
packets(packets/s)

received/RXPKT256

octets).
packets(packets/s)

received/RXPKT512

octets).
packets(packets/s)
Packets (64 bytes) received/

RXPKT64

received that were 64 octets in
length (excluding framing
octets).
packets(packets/s)

646
OptiX OSN 7500 II/7500/3500/1500

19 RMON
Entry
Description
Unit

received/RXPKT65

octets).
packets(packets/s)
Oversize packets received/

ETHOVER

received that were longer than
1518 octets (excluding
FCS octets) and were
otherwise well formed.
packets(packets/s)
Undersized packets
received/ETHUNDER

received that were less than
64 octets long (excluding
packets(packets/s)
Packets received /RXPKTS

(including bad packets,
broadcast packets, and
multicast packets) received.
packets(packets/s)
19.9.2 Statistics of RMON extended performance (packet domain)
Issue 03 (2012-11-30)
Abbreviation
Description
Unit
Control Frames Received/

RXCTLPKTS
A count of MAC Control

frames received on this
interface with an opcode
indicating the special
operation.
frames(frames/s)
Control Frames
Transmitted/TXCTLPKTS

frames transmitted on this
indicating the special
operation.
frames(frames/s)
Packets transmitted/
TXPKTS

(including bad packets,
broadcast packets, and
multicast packets)
transmitted.
packets(packets/s)

647
OptiX OSN 7500 II/7500/3500/1500

Issue 03 (2012-11-30)
19 RMON
Abbreviation
Description
Unit
Broadcast packets
transmitted /TXBRDCAST

that higher-level protocols
requested be transmitted, and
which were addressed to a
broadcast address at this sublayer, including those that
were discarded or not sent.
packets(packets/s)
Multicast packets
transmitted /TXMULCAST

which were addressed to a
multicast address at this sublayer, including those that
were discarded or not sent.
For a MAC layer protocol,
this includes both Group and
Functional addresses.
packets(packets/s)

transmitted/TXPKT1024

transmitted that were between
1024 and 1518 octets in
FCS octets).
packets(packets/s)


octets).
packets(packets/s)


octets).
packets(packets/s)


octets).
packets(packets/s)

648
OptiX OSN 7500 II/7500/3500/1500

Issue 03 (2012-11-30)
19 RMON
Abbreviation
Description
Unit
Packets (64 bytes) received/

TXPKT64

transmitted that were 64
octets in length (excluding
FCS octets).
packets(packets/s)

transmitted/TXPKT65

octets).
packets(packets/s)
Bytes transmitted /
TXOCTETS

data (including those in bad
packets) transmitted on the
octets).
Byte(Byte/s)
Bad Octets Received/

RXBBAD

bad packets received on the
octets).
Byte(Byte/s)
Good Octets Received/

RXBGOOD

good packets received on the
octets).
Byte(Byte/s)
Bad Octets Transmitted/

TXBBAD

bad packets transmitted on
the network (excluding
FCS octets).
Byte(Byte/s)
Good Octets Transmitted/

TXBGOOD

good packets transmitted on
the network (excluding
FCS octets).
Byte(Byte/s)
Packets Received and

Transmitted (64 Octets in
Length)/PKT64

received and transmitted that
were 64 octets in length
(excluding framing bits but
including FCS octets).
packets(packets/s)

649
OptiX OSN 7500 II/7500/3500/1500

Issue 03 (2012-11-30)
19 RMON
Abbreviation
Description
Unit

Transmitted (65127 Octets
in Length)/PKT65

reveived and transmitted that
were between 65 and 127
octets in length inclusive
packets(packets/s)

in Length)/PKT128

packets(packets/s)

Transmitted (256511
Octets in Length)/PKT256

packets(packets/s)

Transmitted (256511

packets(packets/s)

Transmitted (10241518

packets(packets/s)

Transmitted (1519MTU

were between 1519 and
MTUoctets in length
octets).
packets(packets/s)

650
OptiX OSN 7500 II/7500/3500/1500

19 RMON
Abbreviation
Description
Unit
Pause Frames Received/

RXPAUSE

frames received on this
indicating the PAUSE
operation.
frames(frames/s)
Alignment Errors/ETHALI
A count of frames received on

a particular interface that are
not an integral number of
octets in length and do not
pass the FCS check.
frames(frames/s)
FCS Errors/ETHFCS
A count of frames received on

a particular interface that are
an integral number of octets in
length but do not pass the FCS
check. This count does not
include frames received with
frame-too-long or frame-tooshort error.
frames(frames/s)
Packets Received (1519

MTU Octets in Length)/
RXPKT1519

1519 and MTU octets in
FCS octets).
packets(packets/s)
Packets Transmitted (1519

MTU Octets in Length)/
TXPKT1519
Issue 03 (2012-11-30)
packets(packets/s)
Utilization/ETHUTILIZ
The percent utilization of the

ethernet segment on a scale of
0 to 100 percent. If greater
precision is desired, the
Packets Received and Octets
Received should be sampled
before and after a common
interval. The differences in
the sampled values are Pkts
and Octets, respectively, and
the number of seconds in the
interval is Interval.
Unicast Packets Received/

RXUNICAST

directed to a unicast address.
packets(packets/s)

651
OptiX OSN 7500 II/7500/3500/1500

19 RMON
Abbreviation
Description
Unit
Unicast Packets
Transmitted/TXUNICAST

which were not addressed to a
multicast or broadcast
address at this sub-layer,
including those that were
discarded or not sent.
packets(packets/s)
Oversize Packets
Transmitted/TXETHOVER
OThe total number of packets

transmitted that were longer
than 1518 octets (excluding
packets(packets/s)
PORT_RX_BYTES_AVAI
LABILITY
Port bandwidth availability
19.9.3 Statistics of specific events of RMON performance (packet

domain)
Issue 03 (2012-11-30)
Abbreviation
Description
Unit
Alignment Errors/
ETHALI
A count of frames
received on a particular
interface that are not an
integral number of octets
in length and do not pass
the FCS check.
frames(frames/s)
Carrier Sense Errors/

ETHCARERR
The number of times that

the carrier sense
condition was lost or
never asserted when
attempting to transmit a
frame on a particular
interface.
times(times/s)
Excessive Collisions/
ETHEXCCOL
A count of frames for

which transmission on a
particular interface fails
due to excessive
collisions.
frames(frames/s)

652
OptiX OSN 7500 II/7500/3500/1500

Issue 03 (2012-11-30)
19 RMON
Abbreviation
Description
Unit
FCS Errors/ETHFCS
A count of frames
received on a particular
interface that are an
integral number of octets
in length but do not pass
the FCS check. This count
does not include frames
received with frame-toolong or frame-too-short
error.
frames(frames/s)
Late Collisions/
ETHLATECOL
The number of times that

a collision is detected on
a particular interface later
than one slot time into the
transmission of a packet.
times(times/s)
Multiple Collision
Frames/ETHMULCOL
A count of successfully
transmitted frames on a
particular interface for
which transmission is
inhibited by more than
one collision.
frames(frames/s)
Single Collision Frames/

ETHUNICOL
A count of successfully
transmitted frames on a
particular interface for
which transmission is
inhibited by exactly one
collision.
frames(frames/s)

in Length)/PKT64
The total number of

packets (including bad
packets) received and
transmitted that were 64
octets in length
(excluding framing bits
but including FCS
octets).
packets(packets/s)

Transmitted (65~127
Octets in Length)/
PKT65
The total number of

packets) reveived and
transmitted that were
between 65 and 127
but including FCS
octets).
packets(packets/s)

653
OptiX OSN 7500 II/7500/3500/1500

Issue 03 (2012-11-30)
19 RMON
Abbreviation
Description
Unit

Transmitted (128~255
Octets in Length)/
PKT128
The total number of

between 128 and 255
but including FCS
octets).
packets(packets/s)

Transmitted (256~511
Octets in Length)/
PKT256
The total number of

between 256 and 511
but including FCS
octets).
packets(packets/s)

Transmitted(512~1023
Octets in Length)/
PKT512
The total number of

between 512 and 1023
but including FCS
octets).
packets(packets/s)

Transmitted
(1024~1518 Octets in
Length)/PKT1024
The total number of

between 1024 and 1518
but including FCS
octets).
packets(packets/s)

Transmitted
(1519~MTU Octets in
Length)/PKT1519
The total number of

between 1519 and
MTUoctets in length
inclusive (excluding
FCS octets).
packets(packets/s)

654
OptiX OSN 7500 II/7500/3500/1500

Issue 03 (2012-11-30)
19 RMON
Abbreviation
Description
Unit
Deferred Transmissions/
TXDEFFRM
A count of frames for

which the first
transmission attempt on a
particular interface is
delayed because the
medium is busy. The
count does not include
frames involved in
collisions.
frames(frames/s)
Drop Events at
Transmission Direction/
TXETHDROP
The total number of

events in which packets
were dropped by the
probe due to lack of
resources at transmission
direction. Note that this
number is not necessarily
the number of packets
dropped; it is just the
number of times this
condition has been
detected.
times(times/s)
Pause Frames
Transmitted/TXPAUSE

frames transmitted on this
indicating the PAUSE
operation.
frames(frames/s)

655
OptiX OSN 7500 II/7500/3500/1500

20 Clock Solution
20
Clock Solution
About This Chapter

Clock synchronization involves frequency synchronization and time synchronization.
Frequency Synchronization
The OptiX OSN equipment supports the following frequency synchronization solutions:
l
SDH clock synchronization
Synchronous Ethernet clock
CES ACR
IEEE 1588v2 clock synchronization
The first two solutions are implemented at the physical layer, and the last two solutions are
implemented using software protocols at a non-physical layer.
Time Synchronization
Time synchronization is realized based on frequency synchronization. The OptiX OSN
equipment supports the IEEE 1588v2 time synchronization.
20.1 SDH Clock Synchronization
A stable clock ensures normal operation of an NE. To obtain a stable clock, adhere to certain
configuration principles.
20.2 IEEE 1588v2 Time Synchronization and Clock Synchronization
The equipment that complies with IEEE 1588v2 can realize the frequency and time
synchronization. The IEEE 1588v2 protocol ensures time synchronization at the microsecond
level.
20.3 Synchronous Ethernet Clock
The synchronous Ethernet clock is a technology that recovers the clock from the bit stream on
the Ethernet link.
20.4 CES ACR
This chapter describes the CES ACR feature.
Issue 03 (2012-11-30)

656
OptiX OSN 7500 II/7500/3500/1500

20 Clock Solution
20.1 SDH Clock Synchronization

A stable clock ensures normal operation of an NE. To obtain a stable clock, adhere to certain
configuration principles.
20.1.1 Clock
Clock synchronization on the entire network helps to transmit services normally.
Definition
SDH clock synchronization is a technology of frequency synchronization at the physical layer
that is supported by all line boards. The system directly extracts clock signals from SDH signals,
and transmits the clock signals to each board, therefore implementing the transfer of clock
information.
Purpose
Clock synchronization ensures that all the digital devices on a communications network work
at the same nominal frequency, and therefore minimizes the impacts of slips, burst bit errors,
phase jumps, jitters, and wanders on digital communications systems. Clock synchronization
also minimizes pointer justifications on SDH devices. Therefore, clock synchronization is the
precondition and basis for the normal operation of a network.

Before clock configuration, you need to be familiar with the basic concepts.
20.1.2.1 Clock Synchronization

Maintaining clock synchronization among the NEs of a network helps to prevent pointer
justification events, jitters and bit errors. All NEs trace the same clock reference source through
a specific clock synchronization path, thus achieving the networkwide synchronization.
Methods of Clock Synchronization

Clock synchronization is available in two methods: pseudo synchronization and master/slave
synchronization.
l
Pseudo synchronization means that the clocks of the NEs are totally independent of each
other. The clocks, however, are of high precision and stability. Normally, cesium clocks
are used. Thus, pseudo synchronization is maintained among the clocks although
frequencies and phases of the clocks are not exactly the same.
Master/Slave synchronization means that the clock of an NE works as the high-precision

clock source and the other NEs trace the clock of the NE. A lower-level NE traces the clock
of a higher-level NE, and similarly clock synchronization is maintained among all the NEs.
Working Modes of the Clock

Currently, master/slave synchronization is used in most scenarios. The master clock with high
precision and high stability transmits clock signals to the slave clocks, and similarly to the lowerIssue 03 (2012-11-30)

657
OptiX OSN 7500 II/7500/3500/1500

20 Clock Solution
level clocks. In this way, clock synchronization is maintained on the entire network. In maser/
slave synchronization, the working modes of the slave clock are as follows:
l
Tracing mode: It is the normal working mode. In this mode, the local clock is synchronized
with the input reference clock signals.
NOTE
The nodes that have clock tracing relationships between each other comprise a clock subnet.
Holdover mode: When all timing reference signals are lost, the slave clock enters into the
holdover mode. In this mode, the slave clock takes timing reference from the last frequency
information saved before the loss of timing reference signals. This mode can be used to
cope with an interruption of external timing signals lasting many days. The holdover mode
is available in two types: permanent holdover and 24-hour holdover.
Free-run mode: When all timing reference signals are lost, the slave clock enters the freerun mode if the slave clock loses the configuration data about the timing reference signals
or the slave clock fails to enter the holdover mode.
Types of Clock Sources

Based on the source of clock signals, clock sources are classified into five categories.
l
External clock source: 2M timing signals from the external clock interface of an NE
Line clock source: timing signals extracted from optical signals that are received by the
line board
Tributary clock source: timing signals extracted from optical signals that are received by
the tributary board
Internal clock source: internal timing source (available for each NE) that an NE uses when
the external source is lost
Microwave clock source: timing signals extracted from received microwave signals
20.1.2.2 SSM Protocol and Clock ID

The synchronization status message (SSM) protocol and clock ID are used for clock protection.
S1 Byte
The S1 byte is located in row 9, column 1 in the multiplex section overhead in an SDH frame
structure. The lower four bits (bits 5-8) of the S1 byte are allocated to transport a synchronization
status of an NE, which is referred to as the synchronization status message byte (SSMB). Table
20-1 shows the meaning of clock quality that the SSMB stands for. The smaller the SSMB value,
the higher the quality of the clock source that the SSMB represents.
In a clock network, the node that is connected to an external clock extracts a reference timing
source from the BITS equipment, writes an SSMB to bits 5-8 of S1 byte, and transports the
SSMB to downstream nodes. In this way, the SSMB is output. A downstream node extracts the
timing source from a line signal, and obtains the clock quality level from bits 5-8 of S1 byte. In
this way, the downstream node often determines whether the current clock source is effective
and transmits back 0xf to the upstream node through bits 5-8 of S1 byte. 0xf means the returned
clock source is unavailable. This prevents two nodes from tracing the timing source mutually.
Each node obtains the quality of all clock sources from the S1 byte, and chooses to trace a clock
source according to the preset priority level.
Issue 03 (2012-11-30)

658
OptiX OSN 7500 II/7500/3500/1500

20 Clock Solution
Table 20-1 SSM allocation

Bit 5-bit 8 of S1 byte
SDH Synchronization Quality Level
0000
The synchronization quality is unknown (the

existing synchronous network).
0001
Retained
0010
G.811 clock signal
0011
Retained
0100
SSU-ANote 1
0101
Retained
0110
Retained
0111
Retained
1000
SSU-BNote 1
1001
Retained
1010
Retained
1011
Synchronous equipment timing source

(SETS) signal
1100
Retained
1101
Retained
1110
Retained
1111
Not used for synchronization
Note 1: The "G.812 Transit Exchange" and "G.812 Local Clock" terms are used in the previous
version of ITU-T Recommendations. In the new version of ITU-T G.812, the clock definition
is changed to synchronization supply unit (SSU). The SSU is available in A and B types. The
SSU-A corresponds to the "G.812 Transit Exchange" and the SSU-B corresponds to the "G.
812 Local Clock" that is previously used.
SSM Protocol
In the case that the S1 byte is enabled for clock protection, the concept of clock ID is introduced.
That is, clock protection is extended based on the original SSM protocol. In this manner, the
extended SSM protocol is developed.
The standard SSM protocol is a network synchronization management mechanism. It uses bits
5-8 of S1 byte to exchange the quality information of clock sources between nodes. This ensures
that the equipment automatically selects the clock source of the highest quality and priority, to
prevent an interlock of clocks. The standard SSM protocol improves the performance of a
synchronous network, and realizes synchronization of different network architectures in an easy
manner. The standard SSM protocol applies to the interconnection of equipment from different
vendors.
Issue 03 (2012-11-30)

659
OptiX OSN 7500 II/7500/3500/1500

20 Clock Solution
In the case of the extended SSM protocol, Huawei introduces the concept of clock ID based on
the standard SSM protocol. The extended SSM protocol uses bits 1-4 of S1 byte as the unique
ID of a clock source and transmits the clock ID with an SSM. After a node receives the S1 byte,
the node verifies the clock ID (bits 1-4) to determine whether the clock is locally sent. If the
clock is locally sent, the node considers the clock unavailable. This prevents a timing loop. The
extended SSM protocol is mainly used to realize the interconnection of HUAWEI transmission
equipment.
Clock ID
A clock ID uses bits 1-4 of S1 byte, and the value range is 0x0 to 0xf. Basically, a clock ID is
used to distinguish the clock information between local and other nodes, to prevent a node from
tracing the clock signal that is locally sent and comes from the negative direction. Hence, a
timing loop is prevented.
A value of 0 indicates that a clock ID is invalid. Hence, the clock ID takes the default value 0
when the clock ID is not required. When enabling the extended SSM protocol, an NE does not
select the clock source whose ID is 0 as the current clock source.
A clock ID is a tag set for a reference timing source. The clock sources at the same quality level
that carry different IDs mean different timing signals and are the same in priority level.
Set the clock ID according to the following principles:
l
Allocate a clock ID to each external BITS.
Allocate a clock ID to the internal clock source of each node that has an external BITS.
Allocate a clock ID to the internal clock source of each node that enters another ring network
from one chain or ring network.
Allocate a clock ID to the line clock source of the node that enters another ring network
from one chain or ring network, when the line clock source is available.
20.1.2.3 Clock Protection

Clock protection ensures that each node traces the correct clock source even when a fault occurs
on a network.
When an optical path is interrupted or a node fails, the services are switched to the protection
path. In this case, a timing source also selects a new route so that the entire network continues
to trace the timing reference. This process is called clock protection. In other words, clock
protection is a process during which a new route for tracing another timing reference is selected.
In Figure 20-1, NE4 traces the clock that is from NE3. If this clock is lost, NE4 can automatically
switch to trace the clock that is from NE5. When automatic protection switching occurs in a
clock, the new clock source may come from the same timing reference as the lost clock source
or may come from the timing reference of less good quality (for example, the standby BITS).
Clock protection switching is performed based on the following principles:
l
When the clock source priority is set, the NE selects the clock source based on the priority
table if the SSM protocol is disabled. If the SSM protocol is enabled, however, the NE
selects the clock source with the best quality as the synchronization source, and sends the
synchronization status message bit (SSMB) to downstream NEs.
If multiple clock sources at the same quality level exist, the NE selects the clock source at
the highest priority level as the synchronization source, and sends the SSMB to downstream
NEs.
Issue 03 (2012-11-30)

660
OptiX OSN 7500 II/7500/3500/1500

20 Clock Solution
If NE B traces the clock source that is output from NE A, the clock of NE B is an unavailable
source for NE A.
If the extended SSM protocol is enabled, the NE does not select the clock that has the same
ID as the local clock or the clock whose ID is 0, to function as the synchronization source.
Protection Switching When the SSM Protocol Is Disabled

When the SSM protocol is disabled, protection switching is performed based on the priority
table. To be specific, the valid clock source with the highest priority is chosen as the system
clock source (that is, current clock source).
In Figure 20-1, NE1 is connected to the BITS. In normal cases, other NEs remain synchronized
with NE1.
Figure 20-1 Clock synchronization
BITS
NE1
11
NE2
11
8
11
8
NE3
NE6
11
11
NE5
11
NE4
Clock Signal Flow
Table 20-2 provides the clock source priorities for the NEs.
Table 20-2 Clock source priority table and traced clock source
Issue 03 (2012-11-30)
NE
Clock Source Priority

Table
Traced Clock Source
NE1
BITS, clock source on the

board in slot 8, clock source
on the board in slot 11, and
internal clock source
BITS
NE2
Clock source on the board in

slot 8, clock source on the
board in slot 11, and internal
clock source

slot 8
NE3

clock source

slot 8

661
OptiX OSN 7500 II/7500/3500/1500

20 Clock Solution
NE

Table
Traced Clock Source
NE4

clock source

slot 8
NE5

clock source

slot 11
NE6

clock source

slot 11
As shown in Figure 20-2, when a fiber cut occurs between NE1 and NE6, NE6 fails to receive
clock signals from NE1 and then, according to the clock priority table, chooses to trace the clock
source on the board in slot 8. Therefore, interlocked clocks are generated between NE5 and NE6.
Figure 20-2 Clock tracing upon fiber cut when the SSM protocol is disabled
BITS
BITS
NE1
NE1
11 8
NE2
NE3
NE6
11
8
11
11
8
11
8
NE5
11
11
NE2
11
11
11
NE3
11
NE6
NE5
8 11
NE4
NE4
Clock Signal Flow
Clock Signal Flow
When the SSM protocol is disabled, protection switching provides limited functions and easily
causes interlocked clocks. In a system where standard SSM protocol is enabled, however, such
problems do not occur.
Protection Switching in a System Where Standard SSM Protocol Is Enabled

In a system where the standard SSM protocol is enabled, the working principles of clock
protection switching are as follows:
Issue 03 (2012-11-30)

662
OptiX OSN 7500 II/7500/3500/1500

20 Clock Solution
An NE selects the clock source whose quality is the best and priority is the highest as the
system clock source.
Each NE transmits the 0xff message to the system clock source. The message indicates that
the clock source is unavailable.
As shown in Figure 20-1, the clock tracing relationship in a system where the standard SSM
protocol is enabled is different from that in a non-SSM system.
When a fiber cut occurs between NE1 and NE6, the clock tracing relationship on the entire
network changes. As shown in Figure 20-3, NE5 transmits the 0xff message to NE6 because
NE5 traces the clock source of NE6. When detecting that the clock source on the board in slot
11 is lost, NE6 sets its internal clock source as the clock source and transmits the clock signals
to NE5 through the S1 byte. After receiving the clock signals from NE6, NE5 starts to select a
new clock source because the clock signals from NE5 degrade. According to the clock priority
table, NE5 selects the clock source on the board in slot 8 as the system clock source and sends
NE6 the clock quality information through the S1 byte. After receiving the S1 byte, NE6 chooses
to trace the clock source on the board in slot 8. In this manner, clock tracing relationship is
established on the entire network.
Figure 20-3 Clock tracing upon fiber cut in a system where standard SSM protocol is enabled
BITS
BITS
NE1
NE1
11 8
NE2
NE3
NE6
11
8
11
11
8
11
8
11
NE5
11
NE2
11
11
11
NE3
11
NE6
NE5
8 11
NE4
NE4
Clock Signal Flow
If the clock tracing relationship is configured as shown in Figure 20-4, all the NEs involved
trace the clock sources in one direction only.
Issue 03 (2012-11-30)

663
OptiX OSN 7500 II/7500/3500/1500

20 Clock Solution
Figure 20-4 Unidirectional clock tracing
BITS
NE1
11
NE2
11
8
11
8
NE3
NE6
11
11
NE5
8
11
NE4
Clock Signal Flow
When the BITS is faulty, a timing loop is generated, as shown in Figure 20-5. When the BITS
is faulty, NE1 chooses to trace the clock signals received by the board in slot 8, because NE1
and NE6 send each other the S1 byte (containing information about the BITS clock). Therefore,
a timing loop is generated on the entire network.
Figure 20-5 Clock tracing upon faulty BITS in a system where standard SSM protocol is enabled
BITS
NE1
NE1
11 8
NE2
NE3
NE6
11
8
11
11
8
11
8
11
NE5
11
NE2
11
11
11
NE3
11
NE6
NE5
8 11
NE4
NE4
Clock Signal Flow
Issue 03 (2012-11-30)

664
OptiX OSN 7500 II/7500/3500/1500

20 Clock Solution
According to the preceding analysis, the standard SSM protocol prevents the generation of
interlocked clocks but cannot prevent the generation of timing loops. The extended SSM
protocol, however, prevents the generation of timing loops.
Protection Switching in an Extended SSM System

In a system where the extended SSM protocol is enabled, the working principles of clock
protection switching are as follows:
l
An NE selects the clock source whose quality is the best and priority is the highest as the
system clock source. In addition, the clock source must be provided by NEs other than the
NE itself.
Each NE transmits the 0xff message to the system clock source. The message indicates that
the clock source is unavailable.
The most significant four bits of the S1 byte are used to identify the clock source ID.
When the clock tracing relationship is shown in Figure 20-4 and the extended SSM protocol is
enabled, a timing loop is not generated even though the BITS is faulty. As shown in Figure
20-6, NE1 broadcasts its internal clock source to the neighbor NEs after determining not to trace
the clock source of the board in slot 8 and determining that the quality of the clock from NE2 is
not good. Thus, all the NEs on the network trace the internal clock source of NE1.
Figure 20-6 Clock tracing in an extended SSM system in the case of faulty BITS
BITS
NE1
NE1
11 8
NE2
NE3
NE6
11
8
11
11
8
11
8
11
NE5
11
NE2
11
11
11
NE3
11
NE6
NE5
8 11
NE4
NE4
Clock Signal Flow
The extended SSM protocol is a proprietary protocol of Huawei. It effectively prevents the
generation of timing loops by using clock ID.
20.1.2.4 Tributary Retiming

By using the tributary retiming technology, a received tributary signal can be calibrated based
on the clock signal of the SDH equipment, so that the tributary signal can meet the requirement
of a timing reference when it is output.
Issue 03 (2012-11-30)

665
OptiX OSN 7500 II/7500/3500/1500

20 Clock Solution
Working Principle of Tributary Retiming

Figure 20-7 shows the working principle of tributary timing.
The process is described as follows: The phase-locked loop (PLL) recovers clock f1 from the
received tributary signal. The data in the tributary signal is recovered free of errors through the
desynchronization process and then stored into the retiming buffer. Finally, the SDH equipment
clock (SEC) f0, which is synchronous with the digital synchronization network, reads the data
in the tributary signal. In this manner, the output tributary signal carries a good timing reference,
which provides a timing reference for the equipment of synchronous services.
Figure 20-7 Working principle of tributary retiming
Extracted clock (f0)
SDH clock source

SEC
PLL
f1
Extracted clock (f1)
Desynchronization
Retiming buffer
Input tributary signal
f0
Output tributary signal
Application of Tributary Retiming

The tributary retiming function helps PDH signals travel through a transmission network with
or without retiming.
l
Issue 03 (2012-11-30)
Figure 20-8 shows how PDH signals are transmitted over an SDH transmission network
without retiming. The reference frequency f1 of equipment 1 at the transmit end locks on
f0 to prevent periodical slips. When PDH signals are adapted into the SDH transmission
network, pointer justifications cause phase jumps of output PDH signals, and frequency f1
of the output PDH signals becomes asynchronous with f0. As a result, the frequency of
output signals cannot be used as a timing reference for equipment 2 (a digital stored program
control switch, for example).

666
OptiX OSN 7500 II/7500/3500/1500

20 Clock Solution
Figure 20-8 An SDH transmission network without retiming

SDH transmission
network
PRC
f1
Synchronous
service
equipment 1
f0
f1
f0
S
S
SDH
MUX
SDH
MUX
f1
Synchronous
service
equipment 2
U
The frequency of tributary signal
cannot be used as the synchronous
clock of equipment 2
f1:frequency of the PDH signal
f0: frequency of the SDH timing reference
S: synchronization
U: desynchronization
R: retiming
PRC:SDH reference clock
Figure 20-9 shows how PDH signals are transmitted over an SDH transmission network
with retiming. The reference frequency f1 of equipment 1 at the transmit end locks on f0
to prevent periodical slips. At the network output end, a local timing reference f0 is provided
to absorb wanders and jitters generated in the pointer justification process. Thus, the
frequency of output tributary signals f1 remains synchronous with f0 and equipment 2 can
extract the output tributary signals for synchronization purpose.
Figure 20-9 An SDH transmission network with retiming

Transmission network
PRC
f0
f0
U
S
Synchronous
service
equipment 1
f1
S
S
SDH
MUX
SDH
MUX
U
U
U
f0
SEC
f0
Synchronous
service
equipment 2
The frequency of tributary signal can

be used as the synchronous clock of
equipment 2
f1:frequency of the PDH signal
f0: frequency of the SDH timing reference
S: synchronization
U: desynchronization
R: retiming
PRC:SDH reference clock
SEC: synchronous equipment clock
Issue 03 (2012-11-30)

667
OptiX OSN 7500 II/7500/3500/1500

20 Clock Solution

This topic describes the standards and protocols that clocks comply with.
Clocks comply with the following standards and protocols:
l
ITU-T G.810: Definitions and terminology for synchronization networks
ITU-T G.811: Timing characteristics of primary reference clocks
ITU-T G.812: Timing requirements of slave clocks suitable for use as node clocks in
synchronization networks
ITU-T G.781: Synchronization layer functions
20.1.4 Availability
The SDH clock synchronization function requires the support of the applicable equipment,
Version Support
Applicable Version
OptiX OSN 1500/2500/3500/7500
V100R003 and later
T2000
V200R002 and later
U2000
Applicable Version
OptiX OSN 3500 II
V100R009 and later
T2000
U2000
Applicable Version
OptiX OSN 7500 II
U2000
Hardware Support
Issue 03 (2012-11-30)
Applicable Board
Applicable Version
SDH Boards
V100R003 and later
OptiX OSN
1500/2500/3500/3500 II/
7500/7500 II

668
OptiX OSN 7500 II/7500/3500/1500

20 Clock Solution
Applicable Board
Applicable Version
PDH Boards
V100R003 and later
OptiX OSN
1500/2500/3500/3500 II/
7500/7500 II
Microwave Intermediate
Frequency (IF) Board
V100R009 and later
OptiX OSN
1500/2500/3500/3500 II/
7500
N1CQ1
OptiX OSN 3500/7500
N1MD75
OptiX OSN 3500/7500
N1MD12
OptiX OSN 3500/7500
R1ML1
OptiX OSN 1500
TNN1AFO1
OptiX OSN 7500 II
TNN1CO1
OptiX OSN 7500 II
TNN1D75E
OptiX OSN 7500 II
TNN1D12E
OptiX OSN 7500 II
20.1.5 Principles
Clock synchronization is implemented through processes of selection of the clock source,
extraction of the clock signal, and transmission of the clock signal on an SDH network.
As shown in Figure 20-10, clock synchronization of an SDH network is implemented as follows:
l
A master clock is specified, and then the clocks of the other NEs on this network use this
clock as a reference. As shown in Figure 20-10, the clock of NE1 is specified as the master
clock.
The clock signal of BITS is sent to NE1 through the external clock interface.
NE1 places this clock signal into the STM-N signal and then transmits the STM-N signal
to its neighbors, NE2 and NE6.
In the case of the other NEs on the network, each NE collects the clock signals that are
received by all the local boards, and compares the priority and quality of the clock signal,
thus to select an optimal clock source.
After the NE extracts the clock, the PLL traces the optimal clock source and locks on its
phase. Then, the system clock is synchronized with the optimal clock source.
The NE sends the system clock to the downstream NE through the line board. In this
manner, the clock signal can be transmitted downstream.
Issue 03 (2012-11-30)

669
OptiX OSN 7500 II/7500/3500/1500

20 Clock Solution
Figure 20-10 Clock synchronization

BITS
NE1
11
NE2
11
8
NE3
NE6
8
11
11
11
NE5
11
NE4
Clock Signal Flow
20.1.6 Configuring Clocks

A clock is the basis for the normal running of NEs. You must configure clocks for all NEs prior
to configuring services. In addition, you need to configure clock protection for complex
networks.
20.1.6.1 Guidelines on Clock Configuration

When you configure clocks, follow certain guidelines to achieve a satisfactory result of clock
tracing.
General Guidelines
When you configure clocks, follow the general guidelines:
l
At the backbone layer and convergence layer, adopt clock protection and configure the
active and standby reference clock sources to perform switching if necessary. At the access
layer, generally, configure one reference clock source at the central station and enables the
other stations to trace the clock of the central station.
The central node or high-reliability node provides the clock source.
When the building integrated timing supply system (BITS) or another external clock device
with high precision is available, an NE can trace the external clock source. If no BITS or
another external clock device with high precision is available, an NE can trace the line
clock source. The internal clock can work as the clock source with the lowest priority. If a
line clock source needs to be traced, ensure that the clock tracing route must be the shortest.
The details are provided as follows:
In the case of a ring network consisting of less than six NEs, these NEs can trace the
reference clock source in one direction.
In the case of a ring network consisting of six or more NEs, ensure that these NEs trace
the reference clock source in the shortest path. That is, in the case of a network consisting
of N NEs, a half of the NEs trace the reference clock source in one direction and the
other half of NEs trace the reference clock source in the other direction. (If N is an odd
number, the intermediate NE can trace the reference clock source in either of the
directions.)
Issue 03 (2012-11-30)

670
OptiX OSN 7500 II/7500/3500/1500

20 Clock Solution
Properly plan the clock synchronization network, to prevent interlocked clocks and clock
loops.
Use the clock extracted from STM-N signals to work as the inter-office clock. In this case,
do not use the tributary signal for timing.
If multiple NEs form a long chain, clock compensation is required. Otherwise, wanders are
generated in the clock signal after it is transmitted over several stations. ITU-T G.781
specifies that clock compensation is required if 20 or more NEs form a long chain.
Considering the transmission distance of fibers, clock compensation is performed in actual
application if more than 10 NEs form a long chain.
Guidelines on Usage of the SSM Protocol

To determine whether the SSM protocol is enabled for reasons of clock switching, follow certain
guidelines. In the case of clock switching,
l
If the NE needs to select a clock source only based on the preset clock priorities and does
not consider the quality of clock sources, the SSM protocol can be disabled. In this case,
the clock network can be unidirectional but cannot adopt a ring topology.
If the NE needs to automatically select a clock source that is of the highest quality and with
the highest priority, the standard SSM protocol needs to be enabled. If the clock network
consists of Huawei equipment and third-party equipment, only the standard SSM protocol
can be enabled and the extended SSM protocol cannot be enabled. After the standard SSM
protocol is enabled, the clock network can be bidirectional but cannot adopt the ring
topology.
If the NE needs to automatically select a clock source that is of the highest quality and with
the highest priority and the clock network consists of only Huawei equipment, the extended
SSM protocol can be enabled. With the concept of clock ID introduced, the extended SSM
protocol effectively prevents timing loops on the clock network. After the extended SSM
protocol is enabled, the clock network can be bidirectional and adopt a ring topology;
however, the clock network cannot be intersecting or tangent with other networks.
Guidelines on Clock Subnet Configuration

When you configure a clock subnet, follow certain guidelines:
l
All the NEs that trace the same clock source should be divided into the same clock subnet.
The clock tracing chain cannot be excessively long, so it is recommended that a subnet
contain not more than 20 NEs. Otherwise, clock precision may decline.
If an NE implements protection based on the SSM protocol, it must be contained in the

clock subnet. Otherwise, the SSM protocol fails to be enabled and therefore incorrect clock
tracing and switching occurs.
20.1.6.2 Clock Configuration Process

This topic describes the clock configuration procedure based on a flow chart.
The details of the clock configuration procedure vary with the situation. See Figure 20-11,
Figure 20-12, and Figure 20-13.
Issue 03 (2012-11-30)

671
OptiX OSN 7500 II/7500/3500/1500

20 Clock Solution
Figure 20-11 Configuration flow when SSM protocol is disabled

Required
Optional
Set sw itching
conditions for
clock sources
Set the clock

source priority
Set the clock

source
reversion
View the clock

synchronization
status
Sw itch a clock
source
Figure 20-12 Configuration flow when standard SSM protocol is enabled

Required
Optional
Set the clock

source priority
Set the clock

source
protection
Set switching
conditions for
clock sources
Set the clock

source
reversion
View the clock

synchronization
status
Set the clock

source quality
Set the phase-locked

source for external
clock output
Switch a clock
source
Enable the standard

SSM protocol
Set the affiliated clock

subnet for the NE
Figure 20-13 Configuration flow when extended SSM protocol is enabled

Required
Optional
Set the clock

source priority
Set the clock

source
protection
Set switching
conditions for
clock sources
Set the clock

source
reversion
View the clock

synchronization
status
Set the clock

source quality
Set the phase-locked

source for external
clock output
Switch a clock
source
Enable the extended

SSM protocol
Set the affiliated clock
subnet for the NE
Set the ID for clock
NOTE
l The horizontal direction of the figure shows the three stages when you use the U2000 to configure
clocks.
l The vertical direction of the figure shows the relations between tasks at each stage.
20.1.6.3 Viewing Clock Synchronization Status

If the clocks between NEs in the network are not synchronous, the pointer justification, bit error,
even service interruption may occur on NE. Using the U2000, you can be aware of and monitor
the synchronization status of the NE clocks.
Prerequisites
Issue 03 (2012-11-30)

672
OptiX OSN 7500 II/7500/3500/1500

20 Clock Solution
Procedure
Step 1 In the NE Explorer, select an NE and choose Configuration > Clock > Physical Layer
Clock > Clock Synchronization Status from the Function Tree.
NOTE
To view the clock synchronization status of NEs in batches, choose Configuration > Batch Clock
Operation from the Main Menu. Then, click the Clock Synchronization Status tab. In the Object Tree,
select the target NEs and click
Step 2 Click Query. You can see the clock synchronization status information uploaded from the NE.
----End
20.1.6.4 Configuring NE Clock Sources

Before configuring services, you must configure the NE clock source and specify the priority
level to ensure that correct clock tracing relationships are created for all the NEs in the network.
Prerequisites
To implement clock protection, you must configure at least two traceable clock sources for the
equipment. Usually, the tributary clock is not used as the clock source for the equipment.
After you set the clock sources for all the NEs, query the networkwide clock tracing status again.
Procedure
Clock > Clock Source Priority from the Function Tree.
Step 2 Click Query to query the existing clock source.

Step 3 Click Create. In the Add Clock Source dialog box, select a new clock source and click OK.
Step 4 Optional: If an external clock source is selected, select External Clock Source Mode based
on the type of external clock signals. In the case 2 Mbit/s clocks, specify Synchronous Status
Byte to deliver SSM messages.
or
to adjust its priority level. The clock
Step 5 Select a clock source, and click
sources are arranged in descending order. The clock source on top is preferred for the NE.
Issue 03 (2012-11-30)

673
OptiX OSN 7500 II/7500/3500/1500

20 Clock Solution
NOTE
Internal clock sources have the lowest priority because of their low precision.
Step 6 Click Apply. In the Operation Result dialog box, click Close.
NOTE
If the clock tracing relationship changes because of change in the clock source, the Prompt dialog box is
displayed, asking you whether to refresh the clock tracing relationship. Click OK. If you select Disable
Prompting Next Time, no prompt is displayed even when the clock tracing relationship changes.
Step 7 Optional: If you select the line clock as the phase-locked source, you need to specify the priority
table for the phase-locked sources. Click the Priority Table for Phase-Locked Sources of 1st
External Clock Output tab, and then click Create. In the dialog box that is displayed, select
the phase-locked source, and click OK.
Step 8 Click Apply. In the dialog box that is displayed, click Close.
----End
20.1.6.5 Configuring the Clock Source Protection

On a complicated clock network, you need to configure the clock protection for all NEs. After
you set the clock source and specify the clock priority level for the NEs, you can enable the
standard SSM or extended SSM protocol to prevent the NEs from tracing an incorrect clock
source. This is how the clocks are protected.
Prerequisites
Procedure
Clock > Clock Subnet Configuration from the Function Tree.
Step 2 Click the Clock Subnet tab. Click Query to query the existing parameter settings.
Step 3 Select Start Standard SSM Protocol or Start Extended SSM Protocol.
NOTE
The same SSM protection protocol must be used for the same clock protection subnet.
Issue 03 (2012-11-30)

674
OptiX OSN 7500 II/7500/3500/1500

20 Clock Solution
Step 4 Set the subnet number of the clock subnet that the NE belongs to.
NOTE
Allocate the same subnet number to NEs tracing the same clock source.
Step 5 Optional: If the extended SSM protocol is enabled, set the clock ID of the clock source.
Step 7 Optional: If the clock ID is specified for the line clock of an NE, click the Clock ID Status tab,
and set the Enabled Status to Enabled. Click Apply. In the Operation Result dialog box, click
Close.
----End
20.1.6.6 Configuring Switching Conditions for Clock Sources

If the traceable clock source of an NE is line clock, you can customize switching conditions for
the clock source, so that the NE can switch to another clock when the clock source fails. In this
manner, services are less affected.
Prerequisites
Procedure
Clock > Clock Source Switching from the Function Tree. Click the Clock Source Switching
Condition tab.
Step 2 Click Query to query the existing parameter settings.
Step 3 Double-click the parameter column and set the alarms and performance events that are to be
used as the clock source switching conditions to Yes.
----End
20.1.6.7 Configuring the Clock Source Reversion

When there are multiple clock sources for an NE, set the clock sources to automatic reversion
mode, so that the deteriorated clock source can automatically become the traceable timing
reference after it is restored.
Prerequisites
Issue 03 (2012-11-30)

675
OptiX OSN 7500 II/7500/3500/1500

20 Clock Solution
Procedure
Clock > Clock Source Switching from the Function Tree. Click the Clock Source Reversion
Parameter tab.
NOTE
To set the clock source reversion for multiple NEs in batches, choose Configuration > Batch Clock
Operation from the Main Menu. Click the Clock Source Reversion Parameter tab. In the Object Tree,
select the desired NEs and click
Step 2 Double-click and set the reversion mode and the WTR time.
NOTE
Do not set Clock Source WTR Time ( min) to 0. Otherwise, switching occur repeatedly when the clock
is unstable.
----End
20.1.6.8 Configuring the Phase-Locked Source for External Clock Output

When a clock signal passes through 14 or more NEs, frequency offset and drift may occur. As
a result, the clock signal transmitted to the downstream NE is degraded. To prevent clock signal
degrade, you need to set a 2M phase-locked source to optimize the clock signal. In the case of
the NG-SDH equipment, you can set external clock attributes of the 2M phase-locked source.
Prerequisites
Procedure
Clock > Phase-Locked Source Output by External Clock from the Function Tree.
Step 3 Set the parameters manually, such as External Clock Output Mode When 2M Output
Synchronous Source Is Invalid and Clock Source Threshold.
Step 5 Optional: In the case of the NG-SDH equipment, you can also set the external clock attributes
of the 2M phase-locked source. Click the 2M Phase-Locked Source External Clock
Attributes tab and set the parameters manually such as External Clock Output Switch,
External Clock Output Mode, and External Clock Output Timeslot. Click Apply. In the
Operation Result dialog box, click Close.
----End
Issue 03 (2012-11-30)

676
OptiX OSN 7500 II/7500/3500/1500

20 Clock Solution
Example
As shown in Figure 20-14, N NEs comprise a long transmission chain and the external BITS1
equipment is used as the clock synchronization source. After the transmission over several NEs,
the BITS1 clock signals are degraded to a certain extent. In this case, you can output the BITS1
signals from NEm that requires clock quality compensation to the local BITS2 equipment for
compensating the signals. Then, after the compensation, the clock signals are transmitted from
the BITS2 equipment to NEm, to function as the clock synchronization source of the downstream
equipment. The 2M phase-locked source of NEm should be the input clock source of the west
line board, and the clock synchronization source should be the BITS2 PRC input externally.
Figure 20-14 Typical application
BITS1
BITS2
west
NE1
east
west
west
NEm
NEn
C lock S ignal Flow
To make sure that the BITS2 equipment receives clock signals from NEm correctly, you need
to set the output external clock of NEm. Perform the settings based on the parameters of the
BITS2 equipment and make sure that the settings on NEm are consistent with the settings on
the BITS2 equipment.
20.1.6.9 Setting the Clock Source Quality

In a complex clock network, there may be some unknown clock sources. You can uniformly
define these clock sources as unavailable clocks so that NEs do not trace wrong clock sources.
The NE obtains their quality information automatically for clock sources that are allocated to
an NE. You need to define the quality level of clock sources only during test and maintenance.
Prerequisites
Procedure
Clock > Clock Subnet Configuration from the Function Tree. Click the Clock Quality tab.
Issue 03 (2012-11-30)

677
OptiX OSN 7500 II/7500/3500/1500

20 Clock Solution
Step 3 Click the Clock Source Quality tab and set Configuration Quality to a desired level.
NOTE
Generally, use the default Automatic Extraction.
Step 5 If the quality level of a clock source is zero, you can specify the level manually. Click the Manual
Setting of 0 Quality Level tab and set Manual Setting of 0 Quality Level to a required level.
NOTE
To set the clock source quality for multiple NEs in batches, choose Configuration > Batch Clock
Operation from the Main Menu. Click the Manual Setting of 0 Quality Level tab. In the Object Tree,
select the target NEs and click
----End
20.1.6.10 Configuring the SSM Output

If the standard SSM or extended SSM protocol is enabled, the clock signals carry SSM messages
automatically. You can prevent clock sources from sending SSM messages to other clock
subnets. This helps you to ensure that the equipment on different clock subnets do not affect
each other at the edge of clock networks.
Prerequisites
Procedure
Step 1 In the NE Explorer, select the NE and choose Configuration > Clock > Physical Layer
Clock > Clock Subnet Configuration from the Function Tree. Click the SSM Output
Control tab.
Step 2 Set the Control Status of the clock source.
Issue 03 (2012-11-30)

678
OptiX OSN 7500 II/7500/3500/1500

20 Clock Solution
----End
20.1.6.11 Checking the Clock Switching Status

Clock failure may interrupt services. To detect failure of the clock source in time, you need to
check the clock switching status.
Prerequisites
l
The reference clock source must be set.
Procedure
Clock > Clock Source Switching from the Function Tree.
Step 2 Click the Clock Source Switching tab, and click Query to query the current switching status
of the current clock source.
Step 3 In the Operation Result dialog box, click Close.

----End
Issue 03 (2012-11-30)

679
OptiX OSN 7500 II/7500/3500/1500

20 Clock Solution
20.1.6.12 Switching a Clock Source

When the traceable clock source in a network deteriorates, NEs may not be able to execute a
switch on the clock source. You need to manually switch the clock source to prevent clock
deterioration from affecting the normal running of NEs.
Prerequisites
l
The clock source must be created.
Precautions
CAUTION
Performing clock source switching may cause service interruption.
Procedure
Clock > Clock Source Switching from the Function Tree. Click the Clock Source
Switching tab.
Step 2 Click Query to query the current switching status of a clock source.
Step 3 Optional: If the Lock Status is Lock, right-click and choose Release Lockout.
Step 4 Right-click the clock source that you want to switch and select a switching operation.
NOTE
Before switching the clock source, make sure that the target clock source is created in the priority table
and that the target clock source is not locked and that is of a good quality.
Issue 03 (2012-11-30)

680
OptiX OSN 7500 II/7500/3500/1500

20 Clock Solution
Step 5 Optional: To restore the automatic clock source selection mode, right-click the switched clock
source and choose Clear Switching.
----End
20.1.7 Configuring Clocks When the SSM Protocol Is Not Enabled

If the SSM protocol is not enabled, it indicates that the S1 byte is not used. In this case, the clock
source is selected and switched according to the sequence in the priority list. The clock source
with the highest priority functions as the tracing source.
20.1.7.1 Sample Networking

If the SSM protocol is not enabled, the clock protection switching is performed on each NE
according to the preset clock source priority list only when the clock source of a higher level is
lost.

Take the following two networking scenarios as examples:
l
In the network, no external clock equipment is available and all the NEs are synchronized
with the internal clock source of a certain NE. As shown in Figure 20-15, NE2 to NE6 are
synchronized with the internal clock source of NE1. The clock signal flow in the following
figure shows the tracing situation of the clock signal when the network is normal.
In the network, the external clock equipment is available and all the NEs are synchronized
with this external clock source. As shown in Figure 20-16, NE1 to NE6 are synchronized
with the external clock source BITS. The clock signal flow in the following figure shows
the tracing situation of the clock signal when the network is normal.
Issue 03 (2012-11-30)

681
OptiX OSN 7500 II/7500/3500/1500

20 Clock Solution
Figure 20-15 Networking without any external clock equipment

NE1
11
8
NE2
NE3
NE6
11
11
11
11
NE5
8
8
11
NE4
Clock Signal Flow
11
Issue 03 (2012-11-30)
Board Slot Number

682
OptiX OSN 7500 II/7500/3500/1500

20 Clock Solution
Figure 20-16 Networking with one external clock equipment

BITS
NE1
11
8
NE2
NE3
8
NE6
11
11
11
8
11
8
NE5
11
NE4
Clock Signal Flow
11
Board Slot Number
20.1.7.2 Configuring Clocks When No External Equipment Is Available

When no external clock equipment is available, the internal clock source of an NE can be used
as the clock reference of the entire network, and thus all the other NEs are synchronized with
this internal clock source. In this case, you only need to perform related configurations to make
the NEs trace the clock reference.
Procedure
Step 1 Configure the clock source priority for each NE. For details, see Configuring NE Clock Sources.
Set the following parameter for NE1:
l Clock Source: Internal Clock Source
Set the following parameter for NE2 to NE4:
Issue 03 (2012-11-30)

683
OptiX OSN 7500 II/7500/3500/1500

20 Clock Solution
l Clock Source: line source provided by the optical interface of the upstream NE that is
connected to the line board in slot 8, Internal Clock Source
Set the following parameter for NE5 and NE6:
connected to the line board in slot 11, Internal Clock Source
----End
20.1.7.3 Configuring Clocks When One Set of External Clock Equipment Is

Available
When one set of external clock equipment is available, all the NEs in the network take it as a
clock reference with high priority for tracing.
Procedure
On NE1, set the following parameters:
l Clock Source: external clock source 1 (BITS), internal clock source
l External Clock Source Mode
On NE2 to NE4, set the following parameters:
connected to the line board in slot 8, internal clock source
On NE5 and NE6, set the following parameters:
connected to the line board in slot 11, internal clock source
----End
20.1.8 Configuring Clocks When the Standard SSM Protocol Is

Enabled
In the case of the hybrid networking of the equipment from Huawei and other vendors, the
equipment from other vendors does not support the extended SSM protocol. Therefore, you can
enable only the standard SSM protocol when the SSM protocol is required.
20.1.8.1 Sample Description

After the standard SSM protocol is started, an NE performs protection switching on clock sources
according to the information of clock quality level provided by the S1 byte. If the clock sources
are at the same quality level, the NE performs protection switching according to the clock source
priority list. That is, the NE selects the clock source that has the highest quality and priority and
is not locked from the available clock sources as the traceable clock source for the local station.

The following networking scenario is taken as an example. Two sets of external clock equipment
exist in the network, and all NEs are synchronized with the active external clock source. When
Issue 03 (2012-11-30)

684
OptiX OSN 7500 II/7500/3500/1500

20 Clock Solution
the NE cannot trace the active clock source, the NE switches to the standby clock source. See
Figure 20-17. NE1 through NE6 are all synchronized with the external clock source BITS1.
The clock signal flow in the following figure shows the tracing situation of the clock signal when
the network is normal.
Figure 20-17 Starting the standard SSM protocol
BITS1
BITS1 Clock Source

11-Slot Clock Source
Internal Clock Source
11
8-Slot Clock Source

NE1
NE2
NE6
11

11
11
8-Slot Clock Source

8-Slot Clock Source


NE3
11
NE5
8-Slot Clock Source

11
8-Slot Clock Source

NE4
BITS2 Clock Source

BITS2

Clock Source Priority List
8-Slot Clock Source

Clock Signal Flow

11
Board Slot Number
Service Planning
In this scenario, all NEs are divided to clock subnet 1. The mode of all external clock equipment
is 2 Mbit/s, and the timeslot is SA4.
The two external clock devices provide clock signals of the same level.
20.1.8.2 Configuring Clocks

When the SSM protocol is enabled, during clock configuration, you should consider not only
the priority but also the quality level of the clock source, to make sure that the NEs trace the
clock source of the best quality and the highest priority.
Issue 03 (2012-11-30)

685
OptiX OSN 7500 II/7500/3500/1500

20 Clock Solution
Procedure
l Clock Source: external clock source 1 that connects to the BITS1 equipment, optical interface
that connects to the upstream NE through the line board in slot 11, internal clock source
l External Clock Source Mode: 2 Mbit/s
l Synchronous Status Byte: SA4
l Clock Source: optical interface that connects to the upstream NE through the line board in
slot 8, optical interface that connects to the downstream NE through the line board in slot
11, internal clock source
11, external clock source 1 that connects to the BITS2 equipment, internal clock source
Step 2 Enable the standard SSM protocol for each NE. For details, see Configuring the Clock Source
Protection.
l Protection Status: Start Standard SSM Protocol
Step 3 Configure the affiliated clock subnet of each NE. For details, see Configuring the Clock Source
Protection.
l Affiliated Subnet: 1
----End
20.1.9 Configuring Clocks When the Extended SSM Protocol Is

Enabled
The extended SSM protocol supports functions of the standard SSM protocol, and can also be
used to solve certain problems about timing loop. In the case of a network comprising the
equipment from Huawei only, the extended SSM protocol is recommended.
20.1.9.1 Sample Networking

After the enabling of the extended SSM protocol, the clock quality class, priority, and ID can
be determined. When receiving the clock signal with the ID, a node checks if the clock signal
Issue 03 (2012-11-30)

686
OptiX OSN 7500 II/7500/3500/1500

20 Clock Solution
is transmitted by itself. If the clock signal is transmitted by itself, the node considers the clock
source unavailable. In this way, the timing loop is prevented.

Take the following network scenario as an example:
l
In the network, two sets of external clock equipment are available and all the NEs are
synchronized with the primary external clock source. When the primary external clock
source cannot be traced, a clock switching is performed so that the NEs trace the secondary
clock source. As shown in Figure 20-18, NE1 to NE6 are synchronized with the primary
external clock source BITS1. The clock signal flow in the following figure shows the tracing
situation of the clock signal when the network is normal.
In the network, two sets of external clock equipment are available and all the NEs are
synchronized with the primary external clock source. When the primary external clock
source cannot be traced, a clock switching is performed so that the NEs trace the secondary
clock source. In addition, this link is long. To make sure that the downstream NEs can trace
clock signals with high quality after a long distance of transmission, clock compensation
is required on the NEs of the link. As shown in Figure 20-19, NE1 to NE18 are synchronized
with the primary external clock source BITS1. BITS3 is used for clock compensation.
BITS2 works as the protection clock source. The clock signal flow in the following figure
shows the tracing situation of the clock signal when the network is normal.
Issue 03 (2012-11-30)

687
OptiX OSN 7500 II/7500/3500/1500

20 Clock Solution
Figure 20-18 Ring network

BITS1
BITS1 Clock Source

8-Slot Clock Source
NE1
11
8-Slot Clock Source

NE2
NE6
11
8-Slot Clock Source

11
11
8-Slot Clock Source
NE3
11
8-Slot Clock Source
NE5

11
8-Slot Clock Source

NE4
BITS2 Clock Source

BITS2

Clock source priority list
8-Slot Clock Source

Clock signal flow

11
Board slot number
Figure 20-19 Long chain

BITS1
BITS3
NE1
BITS1 Clock Source
8-Slot Clock Source
11
11
11
BITS2
11
11
11
NE2
NE8
NE9
NE10
NE17
NE18

8-Slot Clock Source

8-Slot Clock Source
BITS3 Clock Source

8-Slot Clock Source

8-Slot Clock Source

8-Slot Clock Source

BITS2 Clock Source

8-Slot Clock Source
Clock Source Priority List
Clock Signal Flow

11
Issue 03 (2012-11-30)

Board Slot Number
688
OptiX OSN 7500 II/7500/3500/1500

20 Clock Solution
Service Planning
In the case of the ring network:
l
all the NEs are divided to clock subnet 1. The mode of all external clock equipment is 2
Mbit/s, and the timeslot is SA4.
The two external clock devices provide clock signals of the same level.
In the case of the long chain, all the NEs are divided to clock subnet 1. The mode of all external
clock equipment is 2 Mbit/s, and the timeslot is SA4.
20.1.9.2 Configuring a Ring Network

After enabling the extended SSM protocol, you need to allocate IDs for clock sources in the
network according to configuration principles.
Procedure
that connects to the upstream NE through the line board in slot 8, optical interface that
connects to the downstream NE through the line board in slot 11, internal clock source
that connects to the upstream NE through the line board slot 8, optical interface that connects
to the downstream NE through the line board in slot 11, internal clock source
Protection.
Step 3 Enable the extended SSM protocol for each NE. For details, see Configuring the Clock Source
Protection.
Issue 03 (2012-11-30)

689
OptiX OSN 7500 II/7500/3500/1500

20 Clock Solution
l Protection Status: Start Extended SSM Protocol

Step 4 Configure the clock ID for each clock source. For details, see Configuring the Clock Source
Protection.
l Clock Source ID: Set the clock source ID of the BITS1 equipment to 1 and the clock ID of
the internal clock source to 3.
l Clock Source ID: Set the clock source ID of the BITS2 equipment to 2 and the clock ID of
the internal clock source to 4.
NOTE
The clock source ID can be set to any value within the permitted range.
----End
20.1.9.3 Configuring a Long Transmission Chain

By compensating clock signals, you can keep all the NEs in a long transmission chain
synchronized with the clock source of high quality.
Procedure
Set the following parameters for NE1:
Set the following parameter for NE2 to NE8 and NE10 to NE17:
that connects to the upstream NE through the line board in slot 11, optical interface that
connects to the downstream NE through the line board in slot 8, internal clock source
Protection.
Issue 03 (2012-11-30)

690
OptiX OSN 7500 II/7500/3500/1500

20 Clock Solution

Step 3 Enable the extended SSM protocol for each NE. For details, see Configuring the Clock Source
Protection.
Step 4 Configure the clock ID for each clock source. For details, see Configuring the Clock Source
Protection.
l Clock Source ID: Set the clock source ID of the BITS1 equipment to 1 and the ID of the
internal clock source to 3.
l Clock Source ID: Set the clock source ID of the BITS3 equipment to 2.
l Clock source ID of BITS2: 4
Clock Source ID of Internal Clock Source: 5
NOTE
Step 5 Configure the priority table for the 2M phase-locked clock sources of NE9.
1.
In the NE Explorer, select NE9 and choose Configuration > Clock > Physical Layer
Clock > Clock Source Priority from the Function Tree. In the pane on the right side, click
the Priority Table for Phase-Locked Sources of 1st External Clock Output tab.
2.
Click Create. In the Add Clock Source dialog box that is displayed, select the clock
sources for the boards in slot 1 and slot 3, and then click OK.
3.
Click Apply. In the Operation Result dialog box that is displayed, click Close.
Step 6 Configure the tracing mode of the 2M phase-locked loop for NE9. For details, see Configuring
the Phase-Locked Source for External Clock Output.
Set the following parameters:
l External Clock Output Mode when 2M Output Synchronization Source Is Invalid: Shut off
l Input and Output Impedance of External Clock Source 1: Consistent with the same parameter
on the BITS3 equipment.
l Input and Output Mode of External Clock Source 1: Consistent with the same parameter on
the BITS3 equipment.
----End
20.1.10 Troubleshooting
Following a certain troubleshooting flow can facilitate fault locating and rectification.
Issue 03 (2012-11-30)

691
OptiX OSN 7500 II/7500/3500/1500

20 Clock Solution
Symptom
When the network operates normally, the clock synchronization path is interrupted and the clock
protection switching fails. As a result, a large number of pointer justifications occur on the related
NEs
Impact on System
The failure in the clock protection switching may cause pointer justifications and service
interruptions.
Possible Causes
l
Cause 1: The fibers connections on the board are incorrect.
Cause 2: The configuration of the clock tracing mode of the NE is incorrect.
Cause 3: The configuration of the clock protection switching protocol of the entire network
is incorrect.
Cause 4: The configuration of the external clock source of the NE is incorrect.
Cause 5: The hardware is faulty.
Cause 6: The extended synchronization status message (SSM) protocol is disabled or the
clock ID of the clock source is absent.

l
U2000
Procedure
Step 1 Cause 1: The fibers connections on the board are incorrect. As a result, the protection
switching fails.
1.
See the protection principles to check whether the fibers connections at the faulty point are
correct.
If...
Then...
The fibers connections are incorrect
Re-connect the fibers. Check whether the

services are restored. If the services are not
restored, check whether the fault is due to
other causes.
The fibers connections are correct
Check whether the fault is due to other

causes.
Step 2 Cause 2: The configuration of the clock tracing mode of the NE is incorrect. As a result,
the protection switching fails.
1.
Issue 03 (2012-11-30)
See the protection principles to check whether the clock tracing mode of the NE is correct.

692
OptiX OSN 7500 II/7500/3500/1500

20 Clock Solution
If...
Then...
The configuration of the clock tracing

mode of the NE is incorrect
Change the tracing mode of the clocks on

the entire network. Check whether the
other causes.
The configuration of the clock tracing

mode of the NE is correct

causes.
Step 3 Cause 3: The configuration of the clock protection switching protocol of the entire network
is incorrect. As a result, the protection switching fails.
1.
2.
Check whether the related NEs are added to the clock protection subnets.
If...
Then...
Certain NEs have not been added to the

clock protection subnets
Add these NEs to the corresponding clock

protection subnets. Check whether the
services recover. If the services do not
recover, proceed to the next step.
All NEs have been added to the clock

protection subnets
Proceed to the next step.
Check whether the clock protection switching protocol of related NEs is enabled.
If...
Then...
The clock protection switching protocol of

certain NEs has not been enabled
Enable the clock protection switching

protocol of related NEs. Check whether the
other causes.
The clock protection switching protocol of

the entire network has been enabled

causes.
Step 4 Cause 4: The configuration of the external clock source of the NE is incorrect. As a result,
the protection switching fails.
1.
Issue 03 (2012-11-30)
Check whether the external clock source outputs clock signals.

If...
Then...
The external clock source does not output

clock signals
Change the external clock source to make

sure that the output of the clock signals is
normal. Check whether the services
recover. If the services do not recover,
proceed to the next step.

693
OptiX OSN 7500 II/7500/3500/1500

2.
3.
20 Clock Solution
If...
Then...
The external clock source outputs clock

signals
Check whether the external clock source carries the SSMB information.
If...
Then...
The external clock source does not carry

the SSMB information
Set the SSMB information manually.

Check whether the services recover. If the
services do not recover, proceed to the next
step.
The external clock source carries the

SSMB information
Check whether the external clock source is configured with the s1 byte correctly.
If...
Then...
The external clock source is not configured

with the s1 byte correctly
Re-configure the s1 byte. Check whether

the services are restored. If the services are
not restored, check whether the fault is due
to other causes.
The external clock source is configured

with the s1 byte correctly

causes.
Step 5 Cause 5: The hardware is faulty. As a result, the protection switching fails.
1.
Check the working state of the board.
2.
Replace the faulty board.
3.
Check whether the services are restored. If the services are not restored, check whether the
fault is due to other causes.
Step 6 Cause 6: The extended SSM protocol is disabled or the clock ID of the clock source is
absent.
1.
Check whether the extended SSM protocol is enabled.

If...
Then...
The extended SSM protocol is disabled or

the clock ID of the clock source is absent
Enable the SSM protocol and set the clock

ID of the clock source. Check whether the
services are restored. If not, check whether
the fault is due to other causes.
The extended SSM protocol is enabled or

the clock ID of the clock source is specified
Check whether the services are restored. If

not, check whether the fault is due to other
causes.
----End
Issue 03 (2012-11-30)

694
OptiX OSN 7500 II/7500/3500/1500

20 Clock Solution
Related Information
In the case of clock protection, the direction of each NE clock source must match the fibers
connections. That is, the eastbound/westbound fibers must be connected correctly. When the
clock protection fails, check whether the fiber connections of each NE on the entire network
match the settings of the clock source.

20.1.11.1 Related Alarms

This topic describes all alarms related to clocks.
Table 20-3 lists alarms related to clocks.
Table 20-3 Alarms related to clocks
Alarm Abbreviation
Alarm Full Name
CLK_NO_TRACE_MODE
Clock entering non-tracing running mode
EXT_SYNC_LOS
Loss of external clock source
FSELECT_STG
Forced selection of clock unit
LTI
Loss of time information
R_LOC
Receive loss of clock
S1_SYN_CHANGE
Clock source switching in the S1 byte mode
SYNC_F_M_SWITCH
Manual or forced switching of clock source
SYNC_LOCKOFF
Clock source locked out
OOL
Phase-locked loop out of lock
SYN_BAD
Synchronization clock source degrade
SYNC_C_LOS
Loss of synchronization source level
20.1.11.2 Related Performance Events

This topic describes all performance events related to clocks.
Table 20-4 lists all performance events related to clocks.
Issue 03 (2012-11-30)

695
OptiX OSN 7500 II/7500/3500/1500

20 Clock Solution
Table 20-4 Performance events related to clocks

Performance Event Abbreviation
Performance Event Full Name
AUPJCHIGH
Administrative Unit Pointer Justification

Count HIGH
AUPJCLOW
Administrative Unit Pointer Justification

Count LOW
AUPJCNEW
Administrative Unit Pointer justification

count NEW
20.1.12 Parameter Description

This section describes the parameters for configuring the SDH clock synchronization.
20.1.12.1 Managing External Clock Sources

To use an external clock as the clock source, you need to set the relevant parameters such as the
output mode, output timeslot, and output threshold of the external clock source.
Table 20-5 lists the parameters for configuring the output phase-locked source table of an
external clock.
Table 20-5 Parameters for configuring the output phase-locked source table of an external clock
Issue 03 (2012-11-30)
Field
Value Range
Description
NE Name
For example, NE1
Displays the name of the NE.

696
OptiX OSN 7500 II/7500/3500/1500

20 Clock Solution
Field
Value Range
Description
NE Synchronous Clock
Output<2M Phase-Locked
Source>
Default value: Internal Clock

Source
Specifies the output of the

2M phase-locked clock
source.
You can select an internal
clock source or a line clock
source. In normal cases,
select Internal Clock
Source. If the 2M phaselocked clock source is used
for amplifying the clock
source through repeaters, the
clock signals that have
certain frequency deviation
and drift can be optimized
under the assistance of the
other local synchronous
clock source. In this case, this
parameter needs to be set
according to the clock level,
and you need to select the
other clock source (for
example, Line Clock
Source) as the 2M phaselocked clock source.
Issue 03 (2012-11-30)
Output Impedance of
External Clock Source 1
75 ohms, 120 ohms
Output Impedance of
75 ohms, 120 ohms
Output Mode of External

Clock Source 1
2 Mbit/s, 2 MHz

Clock Source 2
2 Mbit/s, 2 MHz
Default value: 75 ohms
Default value: 2 Mbit/s

The NE can provide two

clocks for external outputs.
You need to specify the
output impedance of external
clock 1.
clock 2.
output mode of external
clock 1.
clock 2.
697
OptiX OSN 7500 II/7500/3500/1500

20 Clock Solution
Field
Value Range
Description
Clock Source Threshold
No Threshold Value, G.813

SDH Equipment Timing
Source (SETS) Signal, G.812
Lock Clock Signal, G.812
Transit Clock Signal, G.811
Clock Signal
Specifies the synchronous

source threshold of the 2M
synchronous output clock
source.
The synchronous source
threshold is used for clock
protection based on the S1
byte. The clock system of the
NE considers the value of this
parameter as the base of the
clock output quality. The
clock system of the NE can
output clock signals only
when the clock quality
exceeds the specified
threshold.
Click A.27.7 Clock Source
Threshold for more
information.
Table 20-6 lists the parameters for configuring the 2M phase-locked source attributes of an
external clock.
Table 20-6 Parameters for configuring the 2M phase-locked source attributes of an external
clock
Field
Value Range
Description
2M Phase-Locked Source
Number
For example, NE350-2M

phase-locked source 1

external clock source output
of the NE.
External Clock Output

Switch
Open, Close
Specifies the output switch of

the external clock source.
External Clock Output Mode
2 MHz, 2 Mbit/s
Specifies the mode used for

the external clock source to
output 2M clock signals.
Click A.27.1 External Clock

Output Mode for more
information.
Issue 03 (2012-11-30)

698
OptiX OSN 7500 II/7500/3500/1500

20 Clock Solution
Field
Value Range
Description

Timeslot
SA4, SA5, SA6, SA7, SA8,

ALL
Specifies the timeslot used by

the SSM in the output 2M
clock signals.
Default value: All
For example, if you set this

parameter to SA4, the SSM is
transmitted by the fourth bit
of the eight bits in the first
timeslot (TS0) of four
consecutive even frames. If
SA5, the SSM is transmitted
by the fifth bit of the eight bits
in the timeslot (TS0) of four
consecutive even frames.
You can set this parameter
only in 2 Mbit/s output mode.
Output Timeslot for more
information.
External Source Output
Threshold
Fail Condition
Threshold Disabled, Not

Inferior to G.813 SETS
Signal, Not Inferior to G.812
Local Clock Signal, Not
Inferior to G.812 Transit
Clock Signal, Not Inferior to
G.811 Clock Signal
Specifies the quality standard

for the output of the external
clock source. If the quality
value is less than the
threshold, the external clock
source stops outputting clock
signals.
Default value: Threshold

Disabled
Click A.27.3 External

Source Output Threshold
AIS, LOF, AIS OR LOF, No

Failure Condition
Specifies the condition used

for determining whether the
source is faulty. If you set this
parameter to AIS OR LOF,
the AIS or LOF alarm may
cause failure in the 2M
phase-locked clock source.
Default value: No Failure

Condition
Click A.27.4 2M PhaseLocked Source Fail

Condition for more
information.
Issue 03 (2012-11-30)

699
OptiX OSN 7500 II/7500/3500/1500

20 Clock Solution
Field
Value Range
Description
Fail Action
2M Output S1 Byte
Unavailable, Send AIS, Shut
Down Output
Specifies the operations to be

performed when the 2M
phase-locked clock source is
faulty. If the 2M phaselocked clock source is faulty,
the external clock outputs the
signals according to the
setting of this parameter.
Default value: Shut Down

Output
Click A.27.5 2M PhaseLocked Source Fail Action

20.1.12.2 Configuring Clock Protection and Restoration

You need to configure necessary protection for the clock so that the NE can be synchronized
normally.
Table 20-7 lists the parameters for configuring clock protection and restoration.
Table 20-7 Parameters used for configuring clock protection and restoration
Field
Value Range
Description
NE Name
For example, NE1
Higher Priority Clock Source

Reversion Mode
Auto-Revertive, NonRevertive
When the quality of a higherpriority clock source

degrades, the NE
automatically switches the
clock source to a lowerpriority clock source. If you
set this parameter to AutoRevertive, the NE
clock source to the higherpriority clock source when
this higher-priority clock
source restores. If you set this
parameter to NonRevertive, the NE does not
automatically switch the
source restores.
Click A.27.12 Higher
Priority Clock Source
Reversion Mode for more
information.
Issue 03 (2012-11-30)

700
OptiX OSN 7500 II/7500/3500/1500

20 Clock Solution
Field
Value Range
Description
Clock Source WTR Time

(min.)
0 to 12
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
prevent the operations that
are performed by the clock
selector due to transient clock
signal restoration.
Default value: 5

WTR Time for more
information.
Clock Source
For example, Internal Clock

Source

clock source.
AIS Alarm Generated
Yes, No

switching condition is
enabled. If the AIS alarm is
reported, the NE considers
that the corresponding clock
source is faulty.
Default value: No
Click A.27.9 AIS Alarm

Generated for more
information.
B1 BER Threshold-Crossing
Generated
Yes, No
Default value: No

enabled. If a B1 thresholdcrossing event is reported, the
NE considers that the
corresponding clock source
is faulty.
Click A.27.10 B1 BER
Threshold-Crossing
Generated for more
information.
RLOS, RLOF and OOF

Alarms Generated
Yes
Displays whether the

enabled. If the R_LOS,
R_LOF, or OOF alarm is
source is faulty.
By default, this parameter is
set to yes and cannot be
changed.
Issue 03 (2012-11-30)

701
OptiX OSN 7500 II/7500/3500/1500

20 Clock Solution
Field
Value Range
Description
CV Threshold-Crossing
Generated
Yes, No

enabled. If a CV thresholdcrossing event is reported, the
is faulty.
CV Threshold
Displays the CV threshold.
B2-EXC Alarm Generated
Yes, No

enabled. If the B2-EXC
alarm is reported, the NE
considers that the
is faulty.
Click A.27.11 B2-EXC
Alarm Generated for more
information.
Effective Status
Valid, Invalid
Specifies whether the clock

source is valid. This
parameter is used for query
only.
Lock Status
Lock, Unlock
Specifies whether a
switching operation is
allowed.
Click A.27.15 Lock Status
(Clock) for more
information.
Switching Source
For example, 11-N2SL16-1

(SDH-1)
Displays the clock source to

be traced by the NE after the
switching.
Switching Status
Forced Switching, Manual

Switching, Normal
Displays the switching status

20.1.12.3 Clock Quality and Status Management

You can manage the quality and status of a clock to ensure the stability and precision of the
clock source that is currently traced.
Table 20-8 lists the parameters that are used for managing the quality and status of a clock.
Issue 03 (2012-11-30)

702
OptiX OSN 7500 II/7500/3500/1500

20 Clock Solution
Table 20-8 Parameters for managing the quality and status of a clock
Field
Value Range
Description
NE Name
For example, NE1
NE Clock Working Mode
Normal Mode, Holdover

Mode, Free-Run Mode
Displays the current working

mode of the clock board on
the NE. This parameter is
used for query only.
Normal Mode: The
reference clock source is
input for clock
synchronization in the actual
service condition.
Holdover Mode: When all
the timing reference clock
sources are lost, the clock
works on the basis of the
stored frequency
information.
Free-Run Mode: The clock
works by using the internal
crystal oscillator.
Click A.27.20 NE Clock
Working Mode for more
information.
S1 Byte Synchronization
Quality Information
For example, NA
Displays the S1 byte

information in the clock
signal of the current NE. This
only.
Click A.27.19 S1 Byte
Synchronization Quality
Information for more
information.
S1 Byte Clock Synchronous

Source
For example, NA
Displays the clock source

that is traced by the clock of
the current NE. This
only.
The relevant information can
be displayed only when the
S1 byte is used. That is, the
clock protection function is
enabled. Similarly, the
relevant information can be
displayed only when you
click Query. Otherwise, only
NA is displayed.
Issue 03 (2012-11-30)

703
OptiX OSN 7500 II/7500/3500/1500

20 Clock Solution
Field
Value Range
Description
Synchronous Source
For example, External Clock

Source1

only.
In normal cases, the
synchronous source is the
clock source of the highest
priority. If the synchronous
source fails to be traced, the
clock source of a lower
priority is traced.
Click A.27.17 Synchronous
Source for more
information.
Data Output Method in

Holdover Mode
Normal Data Output Mode,

Keep the Latest Data
Displays the data output

method.
Click A.27.27 Data Output
Method in Holdover Mode
Clock Source Quality
Unknown Synchronization
Quality, 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, NA
After the SSM protocol is

started, the NE parses the
SSM code according to the
S1 byte of each clock source
to obtain the quality
information of the clock
source. If the NE fails to
parse the SSM code, you
need to manually set the
quality of the clock source.
Quality for more
information.
20.1.12.4 Retiming Management

This topic describes the parameters that are used for setting the retiming clock source and the
retiming mode.
Table 20-9 lists the parameters that are used for retiming.
Issue 03 (2012-11-30)

704
OptiX OSN 7500 II/7500/3500/1500

20 Clock Solution
Table 20-9 Parameters used for retiming

Field
Value Range
Description
Retiming Mode
Normal, Retiming Mode of

Tributary Clock, Retiming
Mode of Cross-Connect
Clock
Default value: Normal
The Retiming Mode

parameter specifies whether
the retiming clock, tributary
clock, or cross-connect
(external) clock is used.
Click A.27.29 Retiming
20.2 IEEE 1588v2 Time Synchronization and Clock

Synchronization
The equipment that complies with IEEE 1588v2 can realize the frequency and time
synchronization. The IEEE 1588v2 protocol ensures time synchronization at the microsecond
level.
20.2.1 Introduction to the IEEE 1588v2 Time Synchronization and

Clock Synchronization
The IEEE 1588 standard, which is generally called the precision time protocol (PTP), is a
precision clock synchronization protocol for networked measurement and control systems. The
equipment that complies with IEEE 1588 meets the requirement for the time synchronization
precision at the microsecond level.
IEEE 1588v2 Protocol

To realize time synchronization, IEEE reviewed and approved the IEEE 1588 standard in 2002.
The IEEE 1588 standard is available in two versions, namely, IEEE 1588 V1 and IEEE 1588v2.
Currently, the IEEE 1588v2 protocol is used.
The objective of this standard is to specify a protocol to synchronize independent clocks running
on separate nodes of a distributed measurement and control system to a high degree of accuracy
and precision. The clocks communicate with each other over a communication network. The
IEEE 1588v2 protocol forms the network into a tree topology according to the clock priority
levels to facilitate the management. The protocol generates a master/slave relationship among
the clocks in the system. Each node on the subnet has a clock. Within a given subnet of a network,
there will be a single master clock. All clocks ultimately derive their time from a clock known
as the grandmaster clock (GMC). The majority of the clocks that are distributed in the PTP
system are boundary clocks (BCs) and ordinary clocks (OCs). The OC is a clock with only one
PTP port for time synchronization or clock synchronization. The BC is a clock with more than
one PTP port, each of which provides access to a separate PTP communication path and can be
use to transfer the time information.
Clock synchronization and time synchronization realized by using the IEEE 1588v2 protocol is
a technical revolution and innovation for the telecommunications IP network.
The IEEE 1588v2 clock meets the clock synchronization and time synchronization requirements
of the NodeBs and RNCs on the 3G network.
Issue 03 (2012-11-30)

705
OptiX OSN 7500 II/7500/3500/1500

20 Clock Solution
Clock Synchronization and Time Synchronization

Synchronization means that the frequencies or phases of two or more signals maintain a certain
relation. To be more specific, within a valid instance, the phase difference or frequency
difference between two or more signals remains in the permitted range. Synchronization is
classified into clock synchronization and time synchronization.
l
The clock synchronization refers to the frequency synchronization. In the case of clock
synchronization, the frequencies of the signals trace the reference frequency. The start time
of the signals can be different.
Time synchronization refers to the frequency and phase synchronization.
IEEE 1588v2 Time Synchronization and Clock Synchronization

The IEEE 1588v2 time synchronization realizes the time synchronization at the microsecond
level, based on the frequency synchronization.
The IEEE 1588v2 clock synchronization realizes the frequency synchronization by using the
IEEE 1588v2 packets.

This topic describes the basic concepts that the IEEE 1588v2 protocol involves and the bearer
mode of the IEEE 1588v2 packets.
20.2.2.1 Clock Architecture and Models

This topic describes the concepts related to the clock architecture and clock models in the IEEE
1588v2 protocol.
Clock Models
The equipment supports two models of IEEE 1588v2 clock:
l
Ordinary clock (OC): The OC equipment provides only one port that supports the extraction
of the IEEE 1588v2 packets. The OC equipment can work as the clock equipment that is
synchronized with the upstream clock. The OC equipment obtains the clock packets through
the port that supports the extraction of the IEEE 1588v2 packets and recovers the clock.
The OC equipment can also work as the master clock equipment. In this case, the OC
equipment accesses the external time through the external clock interface and transmits the
external clock to the downstream node through the port that supports the extraction of the
IEEE 1588v2 packets.
Boundary clock (BC): The BC equipment provides several ports that support the extraction
of the IEEE 1588v2 packets. The BC equipment can also work as the master clock
equipment or the slave clock equipment. The BC equipment transmits the clock packets to
the downstream node through several ports whereas the OC equipment transmits the clock
packets to the downstream node only through one port.
Clock Architecture
Figure 20-20 shows the architecture of the IEEE 1588v2 clock.
Issue 03 (2012-11-30)

706
OptiX OSN 7500 II/7500/3500/1500

20 Clock Solution
Figure 20-20 Architecture of the IEEE 1588v2 clock

BITS
BC
BC
Master
Slave
BC
Slave
Master Master
OC
Slave
OC
Master
Slave
20.2.2.2 Bearer Mode of IEEE 1588v2 Packets

The IEEE 1588v2 packets can be encapsulated in the Ethernet data packets for transmission.
The three main bearer modes are IEEE 1588v2 packets in Ethernet data packets, IEEE 1588v2
packets in Ethernet data packets with VLAN tags, and IEEE 1588v2 packets in IP data packets.
IEEE 1588v2 Packets in Ethernet Data Packets

The IEEE 1588v2 packets can be encapsulated in the Ethernet data packets for transmission.
The three main bearer modes are IEEE 1588v2 packets in Ethernet data packets without VLAN
tags, IEEE 1588v2 packets in Ethernet data packets with VLAN tags, and IEEE 1588v2 packets
in IP data packets.
Issue 03 (2012-11-30)

707
OptiX OSN 7500 II/7500/3500/1500

20 Clock Solution
Figure 20-21 IEEE 1588v2 packets in Ethernet data packets
Six bytes
DMAC
Six bytes
SMAC
Two bytes
Ethernet type
Ethernet header
44 to 64 bytes
Protocol type
IEEE 1588 V2 payload

Payload
Four bytes
FCS
Six bytes
DMAC
Six bytes
SMAC
Ethernet header
Four bytes
Two bytes
VLAN
Ethernet type
44 to 64 bytes
Protocol type
IEEE 1588 V2 payload

Payload
Four bytes
Issue 03 (2012-11-30)
FCS

708
OptiX OSN 7500 II/7500/3500/1500

20 Clock Solution
6 Byte
DMAC
6 Byte
SMAC
2 Byte
EthernetType
12 Byte
IP header
4 Byte
SA_IP
4 Byte
DA_IP
2 Byte
SPN
2 Byte
DPN
Ethernet header
IP header
UDP header
2 Byte
UDP _Len
2 Byte
UDP_checksum
Payload
44-64 Byte
4 Byte
1588 payload
FCS
This section describes the capacity of the OptiX OSN equipment for supporting IEEE 1588v2
time and clock synchronization.
Table 20-10 provides specifications associated with IEEE 1588v2 time and clock
synchronization.
Issue 03 (2012-11-30)

709
OptiX OSN 7500 II/7500/3500/1500

20 Clock Solution
Table 20-10 Specifications associated with IEEE 1588v2 time and clock synchronization
Item
Specifications
Support capability
Number of ports: 16
Precision in the case of single hop
30 ns
Precision in the case of 30 stations
1 us

This topic describes the standards and protocols that IEEE 1588v2 complies with.
IEEE 1588v2 complies with the following standards and protocols:
l
IEEE 1588v2: IEEE Standard for a Precision Clock Synchronization Protocol for
Networked Measurement and Control Systems
20.2.5 Availability
The IEEE 1588v2 clock synchronization function requires the support of the applicable
equipment, boards, and software.
Version Support
Issue 03 (2012-11-30)
Applicable Version
OptiX OSN 1500/3500
T2000
U2000
Applicable Version
OptiX OSN 7500
U2000
Applicable Version
OptiX OSN 7500 II
U2000

710
OptiX OSN 7500 II/7500/3500/1500

20 Clock Solution
Hardware Support
Issue 03 (2012-11-30)
Classifica
tion of the
Boards
Applicabl
e Board
Applicable Version
Packet
processing
board
N1PEG8
OptiX OSN 3500/7500
Packet
processing
board
N2PEX1
OptiX OSN 3500/7500
Packet
processing
board
N1PEX2
OptiX OSN 3500/7500
Packet
processing
board
R1PEFS8
Packet
processing
board
Q1PEGS2
Packet
processing
board
R1PEGS1
Packet
processing
board
R1PEF4F
Packet
processing
board
TNN1EX2
OptiX OSN 7500 II
Packet
processing
board
TNN1EG8
OptiX OSN 7500 II
Packet
interface
board
N1PEFF8
OptiX OSN 3500/7500
Packet
interface
board
N1PETF8
OptiX OSN 3500/7500
Packet
interface
board
TNN1ETM
C
OptiX OSN 7500 II
Auxiliary
board
N1AUX
OptiX OSN 3500

711
OptiX OSN 7500 II/7500/3500/1500

Issue 03 (2012-11-30)
20 Clock Solution
Classifica
tion of the
Boards
Applicabl
e Board
Applicable Version
Auxiliary
board
T1EOW
OptiX OSN 7500
Auxiliary
board
R1EOW
Crossconnect
board and
system
control
board
N1PSXCS
OptiX OSN 3500
Crossconnect
board and
system
control
board
N2PSXCS
A
OptiX OSN 3500
Crossconnect
board and
system
control
board
T1PSXCS
A
OptiX OSN 7500
Crossconnect
board and
system
control
board
R1PCXLN
Crossconnect
board and
system
control
board
N4GSCC
OptiX OSN 3500/7500
Crossconnect
board and
system
control
board
N6GSCC
OptiX OSN 3500/7500

712
OptiX OSN 7500 II/7500/3500/1500

20 Clock Solution
Classifica
tion of the
Boards
Applicabl
e Board
Applicable Version
Crossconnect
board and
system
control
board
TNN1PSX
CS
OptiX OSN 7500 II
Crossconnect
board and
system
control
board
N3PSXCS
A
OptiX OSN 3500
NOTE
The external time input and output interface of an OptiX OSN 7500 II is on the TNN1PSXCS board, and that
of an OptiX OSN 1500, OptiX OSN 3500, or OptiX OSN 7500 is on the auxiliary board.

This section describes the limitations on and precautions for IEEE 1558v2 time and clock
synchronization in the network design phase, configuration and commissioning phase, and
maintenance phase.
Issue 03 (2012-11-30)
Applicable
Object

Details
Remarks
IEEE 1588v2
time and clock
synchronizatio
n
The OptiX OSN

1500/3500/7500/7500 II uses
algorithms to achieve frequency
synchronization between
neighboring nodes. Frequency
needs to be restored node by node
and cannot traverse unknown
networks.
Frequency
synchronizatio
n
It is recommended that the packet

transmission frequency is higher
than or equal to 128 frames per
second. Otherwise, frequency
restoration is affected.

713
OptiX OSN 7500 II/7500/3500/1500

20 Clock Solution
Applicable
Object

Details
Remarks
Time
synchronizatio
n
If an NE is interconnected with other

equipment through a 10GE port, set
the clock ID to be received at the
port to the peer clock ID.
Clock working
modes
The OptiX OSN

1500/3500/7500/7500 II supports
the BC/OC mode but not the TC
mode.
IEEE 1588v2
time and clock
synchronizatio
n and SDH
clock
synchronizatio
n
The SDH clock synchronization

function will be unavailable after the
function is enabled.
TNN1EG8 and
N1PEG8
Only GE optical interfaces of the

TNN1EG8 and N1PEG8 support the
function.
Issue 03 (2012-11-30)
Applicable
Object

Details
Remarks
IEEE 1588v2
time and clock
synchronizatio
n
Set SYNC to -8 and Delay_Req of

the N1PEX2/TNN1EX2 board to
-4.
IEEE 1588v2
time and clock
synchronizatio
n
Enable the IEEE 1588v2 clock

synchronization function only when
active and standby system control
and cross-connect boards are
upgraded and both support the IEEE
1588v2 clock synchronization
function.

714
OptiX OSN 7500 II/7500/3500/1500

20 Clock Solution
Applicable
Object

Details
Remarks
IEEE 1588v2
time and clock
synchronizatio
n
The OptiX OSN 3500 cannot

provide external time signals (1PPS
+TOD) after its SCC board is reset
(cold or warm), and starts to provide
external time signals when the SCC
board works properly. Therefore,
the equipment that uses the time
signals provided by the OptiX OSN
3500 may fail to work properly
when no time signal is received from
the OptiX OSN 3500.
20.2.7 Realization Principle

Realizing the time and clock synchronization by using the IEEE 1588v2 protocol involves
establishing the master/slave relationships among clocks and synchronizing the clock
information.
20.2.7.1 Establishing the Master/Slave Relationship

Establishing the master/slave relationship involves determining the master/slave state of each
port of the OC and BC equipment in a PTP system based on the BMC algorithm results.
BMC Algorithm
The best master clock (BMC) algorithm consists of the following parts:
l
Data set comparison algorithm: determines the optimal clock source according to the
quality of the clock of the Announce packets that are received at each port.
Topology comparison algorithm: During the data set comparison algorithm, if the GM IDs
of the Announce packets received by two clock sources are the same, the IEEE 1588v2
protocol considers that Announce packets received by the two clock sources are from the
same reference clock source. In this case, the optimal clock source can be specified by
comparing the topological routes. Hence, the topology comparison algorithm is used. The
topology comparison algorithm is related to the networking topology. It determines the
optimal clock source according to the number of hops across which the Announce packets
travel. When the hops across which the Announce packet that contains the clock source
travels are fewer, the quality of the clock source is higher.
State decision algorithm: determines the port state according to the data set comparison
algorithm result and topology comparison algorithm result.
Port State
The PTP defines nine port states, namely, PTP_INITIALIZING, PTP_FAULTY,
PTP_DISABLED, PTP_LISTENING, PTP_PRE_MASTER, PTP_MASTER, PTP_PASSIVE,
PTP_SLAVE, and PTP_UNCALIBRATED. The PTP_INITIALIZING, PTP_FAULTY, and
Issue 03 (2012-11-30)

715
OptiX OSN 7500 II/7500/3500/1500

20 Clock Solution
PTP_DISABLED states are non-working states. The PTP_MASTER, PTP_PASSIVE, and

PTP_SLAVE states are the working states. The PTP_LISTENING, PTP_PRE_MASTER, and
PTP_UNCALIBRATED states are the intermediate states (transient states). The three working
states are described as follows:
l
PTP_MASTER: The clock port that is in the PTP_MASTER state provides the clock source
to the downstream equipment.
PTP_PASSIVE: The clock port that is in the PTP_PASSIVE state is not the master clock
port and is not synchronized with the master clock.
PTP_SLAVE: The clock port that is in the PTP_SLAVE state works as a downstream port
and receives the clock information from the upstream port. The port that is in the
PTP_SLAVE state is synchronized with the clock port that is in the PTP_MASTER state
on the same time path.
Procedure for Establishing the Master/Slave Relationship

The local equipment establishes the master/slave relationships based on the Announce packets
from other equipment, the port data sets, BMC algorithm, and the state machines associated with
the clock ports. Generally, the local equipment establishes the master/slave relationships in the
following procedure:
1.
Receives and authenticates the Announce packets from other clock ports.
2.
Determines the recommended port state by using the BMC algorithm.
3.
Updates the port data sets according to the decision point that is used in the state decision
algorithm and is in the recommended state.
4.
Determines the actual master/slave state of the port by using the state machine associated
with the port and establishes the master/slave relationships, according to the recommended
state and state decision event.
This topic considers the following ring network that comprises three NEs as an example to
describe the process of establishing the master/slave relationships.
As shown in Figure 20-24, node A, node B, and node C construct a ring network. Node A is
connected to node B through port A1 and is connected to node C through port A2. Node B is
connected to node A through port B2 and is connected to node C through port B1. Node C is
connected to node A through port C1 and is connected to node B through port C2. Node A is
assumed as the reference clock source.
Figure 20-24 Working principle diagram of the BMC algorithm
A
A2
A1
M
B2
S
M
B
B1
Issue 03 (2012-11-30)
C1
C2

716
OptiX OSN 7500 II/7500/3500/1500

20 Clock Solution
Node A is assumed as the reference clock source. Hence, port A1 and port A2 change to
the master state first.
After port B1 and port B2 receive the IEEE 1588v2 packets, the equipment compares the
GM IDs contained in the IEEE 1588v2 packets. After determining that the GM IDs are the
same, the equipment compares the routes of the packets received by port B1 and port B2.
After determining that the route along which the packets travel to port B2 is shorter than
the route along which the packets travel to port B1, the equipment selects port B2 as the
slave clock port and selects port B1 as the master clock port.
After port C1 and port C2 receive the IEEE 1588v2 packets, the equipment compares the
GM IDs contained in the IEEE 1588v2 packets. After determining that the GM IDs are the
same, the equipment compares the routes of the packets received by port C1 and port C2.
After determining that the route along which the packets travel to port C1 is shorter than
the route along which the packets travel to port C2, the equipment selects port C1 as the
slave clock port and selects port C2 as the master clock port. In addition, the NE ID of node
B (namely, the opposite NE of port C2) is smaller than the NE ID of node C. Hence, port
C2 changes to the passive state.
20.2.7.2 Clock Information Synchronization

This topic describes the realization principle for synchronizing the clock information.
Types of Protocol Packets

The IEEE 1588v2 protocol defines the following types of packets:
l
Announce packet: used to establish the master/slave synchronization architecture.
Sync packets: used to generate the synchronization request.
Delay_Req and Pdelay_Req packets: used by the requesting clock to generate the delay
measurement request. The Delay_Req is used in the case of E2E TC model and the
Pdelay_Req is used in the case of P2P TC model.
Delay_Resp and Pdelay_Resp packets: used to respond to the delay measurement request
generated by the requesting clock. The Delay_Resp is used in the case of E2E TC model
and the Pdelay_Resp used in the case of P2P TC model.
Management packet: used to query and update the PTP data sets for clock maintenance and
also used to customize, initialize, and troubleshoot a PTP system. The Management packet
is used between the management node and the clock equipment.
Signaling packet: used between the clock equipment to realize communication for special
purposes. For example, the Signaling packet can be used to negotiate the rate of the unicast
messages between the master clock and the slave clock.
The Sync, Delay_Req, and Delay_Resp packets are used to generate and transfer the timing
information that is synchronized by using the Delay_Req/Delay_Resp mechanism and is
required by the OC and BC equipment.
The Pdelay_Req and Pdelay_Resp packets are used to measure the link delay between the two
clock ports that realize the Pdelay mechanism. The OC and BC equipment is synchronized by
using the timing information in the Sync packets and the link delay information.
NOTE
The Pdelay mechanism measures the point-to-point transmission time, namely, link delay, between two
communication ports that support the Pdelay mechanism.
Issue 03 (2012-11-30)

717
OptiX OSN 7500 II/7500/3500/1500

20 Clock Solution
Delay Measurement Mechanism

Ports on the equipment support the E2E and P2P delay measurement mechanisms.
l
End-to-end (E2E): end-to-end delay measurement mechanism
Peer-to-peer (P2P): point-to-point delay measurement mechanism
The E2E port and P2P port use different delay measurement mechanisms and hence cannot be
used at the same time on the same communication path. That is, two neighboring ports on the
same time path must be of the same delay mechanism, namely, E2E or P2P. When the time path
is changed, the E2E mechanism recalculates the end-to-end resident time and the transmission
time delay whereas the P2P mechanism calculates the transmission delay and resident time on
the changed time path only.
Process of Synchronizing the Clock Information in the E2E Delay Measurement

Mechanism
The E2E delay measurement mechanism measures the average path delay between a pair of
master and slave clock ports. For the synchronization principles in the E2E delay measurement
mechanism, see Figure 20-25.
Figure 20-25 Process of synchronizing the clock information in the E2E delay measurement
mechanism
Slave clock
Master clock
t1
t-ms
Data obtained
by the slve clock
Sync
t2
t1, t2
t3
t1, t2, t3
t-sm
t4
Delay_Req
Delay_Resp
t1, t2, t3, t4
The time synchronization process is as follows:

1.
The master clock transmits a synchronization packet to the slave clock. The master clock
adds timestamp t1 into the synchronization packet and the slave clock extracts timestamp
t1 from the synchronization packet and records the receipt time of the Sync packet, namely,
t2.
2.
The slave clock sends the Delay_Req message to the master clock. The slave clock records
the accurate transmit time of the Delay_Req message, namely, t3. The master clock records
the accurate receipt time of the Delay_Req message, namely, t4.
Issue 03 (2012-11-30)

718
OptiX OSN 7500 II/7500/3500/1500

3.
20 Clock Solution
The master clock returns a Delay_Resp message to the slave clock. The Delay-Resp
message contains the accurate receipt timestamp t4 of the Delay_Req message. The slave
clock can calculate the transmission delay (delay) and time offset (offset) between the
master and slave clocks according to the timestamps t1, t2, t3, and t4. The formula for
calculating the t_ms values of the master and slave nodes are as follows: t_ms = t2 - t1 =
offset + ms_delay and t_sm = t4 - t3 = -offset + sm_delay. If the t_ms values of the master
and slave nodes are the same, that is, if ms_delay = sm_delay = delay, offset = (t_ms t_sm)/2 = (t2-t1-t4+t3)/2 and delay = (t_ms+t_sm)/2 = (t2 - t1 + t4 - t3)/2.
Process of Synchronizing the Clock Information in the P2P Delay Measurement

Mechanism
The P2P delay measurement mechanism does not require the master/slave relationship between
the measured two ports. That is, the P2P delay measurement mechanism can measure the delay
between any two ports that support the P2P mechanism. For the synchronization principles in
the P2P delay measurement mechanism, see Figure 20-26.
Figure 20-26 Process of synchronizing the clock information in the P2P delay measurement
mechanism
Data obtained
by the
requesting clock
t1
Responding
clock
Requesting
clock
t1
t-ms
Pdelay_Req
t2
t3
t-sm
t1, t3-t2, t4
t4
Pdelay_Resp
(including t3-t2)
The time synchronization process is as follows:

1.
The requesting clock sends a delay request to the responding clock. The requesting clock
adds timestamp t1 into the delay request packet and the responding clock extracts timestamp
t1 from the delay request packet and records the receipt time of the delay request packet,
namely, t2.
2.
The responding clock returns a delay response packet to the requesting clock. The delay
response packet contains the value t3 - t2, namely, the difference between the accurate time
that the responding clock sends the delay response packet and the receipt time of the delay
request packet. The requesting clock records the accurate receipt time of the delay response
packet, namely, t4.
Issue 03 (2012-11-30)

719
OptiX OSN 7500 II/7500/3500/1500

3.
20 Clock Solution
The requesting clock can calculate the transmission delay (delay) of the master responding
clock according to the values of t1, t3 - t2, and t4. The calculation result shows that the path
delay of the requesting clock is the same as the path delay of the responding clock, namely,
delay = ms_delay = sm_delay =[(t2 - t1) + (t4 - t3)]/2 = [(t4 - t1) - (t3 - t2)]/2.
20.2.8 Application Scenarios of the IEEE 1588v2 Time

Synchronization and Clock Synchronization
The IEEE 1588v2 time synchronization and clock synchronization technologies can be used to
realize the frequency and time synchronization.
The wireless equipment that adopts the frequency synchronization (namely, clock
synchronization) is deployed on the existing network. For example, the GSM equipment is
deployed on a 2G network and the WCDMA FDD equipment is deployed on a 3G network.
Figure 20-27 shows the application scenarios of the IEEE 1588v2 clock synchronization
technology.
Figure 20-27 Networking diagram (clock synchronization)
PRC
PRC
~
Clock information
Clock information
Intermediate equipment
for time synchronization
B
10 Gbit/s ring
Convergence layer
2.5 G chain
622 Mbit/s
chain
155 Mbit/s
chain
G
Access layer
Slave equipment for

time synchronization
Slave equipment for

Slave equipment for

OptiX OSN equipment
OptiX Metro 1000

Clock information
Issue 03 (2012-11-30)

720
OptiX OSN 7500 II/7500/3500/1500

20 Clock Solution
The intermediate NEs A and B, which comply with IEEE 1588v2, receive the clock signals from
the clock source PRC through the external clock interfaces and transmit the clock signals to NEs
E, F, and G, and then to the wireless equipment.
20.2.9 Configuring the IEEE 1588v2 Time Synchronization and

Clock Synchronization
This topic describes how to configure the IEEE 1588v2 time synchronization on the NMS.
20.2.9.1 Setting the NE Parameters

To enable the PTP protocol, you need to set the NE parameters.
Prerequisites
Precautions
CAUTION
The clock frequency synchronization can be realized by configuring the IEEE 1588 V2 time
synchronization or the traditional clock synchronization. When the IEEE 1588 V2 time
synchronization and the traditional clock synchronization are configured at the same time, only
the IEEE 1588 V2 time synchronization works. To realize the frequency synchronization by
configuring the IEEE 1588 V2 clock, you need to set Protocol Frequency Tracing to
Enabled.
Procedure
Step 1 In the NE Explorer, select the NE and choose Configuration > Clock > PTP Clock > Basic
Clock Configuration from the Function Tree.
Step 2 In the window on the right, click the NE Parameter Configuration tab and set the relevant
parameters.
Issue 03 (2012-11-30)

721
OptiX OSN 7500 II/7500/3500/1500

20 Clock Solution
NOTE
In this window, you can click Query to query parameters of NE Parameter Configuration.
is successful.
Step 4 Click Close.
----End
20.2.9.2 Configuring the Encapsulation Type of IEEE 1588 V2 Packets on the Data
Board
You need to configure the encapsulation type of IEEE 1588 V2 packets so that a data board can
transmit the IEEE 1588 V2 packets.
Prerequisites
l
The data board that supports the transmission of the IEEE 1588 V2 packets must be created.
Procedure
Step 1 In the NE Explorer, select the NE and choose Configuration > Clock > PTP Clock > Basic
Clock Configuration from the Function Tree.
Step 2 Click the Configuration of the Protocol 1588 Packet on the Data Board tab in the window
on the right. Set Encapsulation Type, Whether to Detect the VLAN Tag, and VLAN ID for
the data board.
NOTE
The data ports support the IEEE 1588 V2 function only when working in full-duplex mode. If the port
mode is set to full duplex for the port on the user equipment and to auto-negotiation for the port on this
data board, auto-negotiation fails.
is successful.
Step 4 Click Close.
----End
20.2.9.3 Setting the Attributes of the External Clock Interface for an NE

To use an NE as the input equipment of the external clock, you need to set the relevant attributes
of the external clock interface.
Prerequisites
Issue 03 (2012-11-30)

722
OptiX OSN 7500 II/7500/3500/1500

20 Clock Solution
Procedure
Step 1 In the NE Explorer, select the NE and choose Configuration > Clock > PTP Clock > Clock
Interface Configuration from the Function Tree.
Step 2 In the window on the right, click the External Clock Interface Configuration tab and set the
relevant parameters of the external clock interface for an NE.
CAUTION
l In this window, you can click Query to query the parameters in External Clock Interface
Configuration.
l Two BITSs are connected to a ring and the working/protection relationship exists between
the two BITSs. If the attribute settings of the two BITSs are the same, certain NEs on the
ring trace one BITS and the rest NEs trace the other BITS. That is, the working/protection
relationship does not exist between the two BITSs. To prevent this problem, set the attributes
of the two BITSs to different values.
l The OptiX OSN 7500 II supports the setting of Interface Mode of an external time interface.
Interface Mode includes External clock port, External time input port, and External
time output port.
is successful.
Step 4 Click Close.
----End
20.2.9.4 Configuring the Clock Source Priority Table for an NE

The clock source priority table is a group of clock sources that are defined for the IEEE 1588
V2 time synchronization and clock synchronization functions. Only these clock sources can be
used as the interfaces for realizing the IEEE 1588 V2 time synchronization and clock
synchronization. The clock sources are not differentiated by priority in this table. The NE
automatically selects the clock source with the highest quality as the transmission interface.
Issue 03 (2012-11-30)

723
OptiX OSN 7500 II/7500/3500/1500

20 Clock Solution
Prerequisites
l
The board that can be configured as the clock source must be created.
Procedure
Step 2 In the window on the right, click the Clock Source Priority Table tab. Click New.
Step 3 Optional: In the New Time Source dialog box that is displayed, select the time source and click
Confirm.
Step 4 Optional: In the Clock Source Priority Table tab, select the clock source to be deleted and
click Delete.
NOTE
The internal clock source cannot be deleted.
is successful.
Step 6 Click Close.
Step 7 Click Query in the Clock Source Priority Table tab to check the Switching Mode of Clock
Source ID currently traced, Main clock ID currently traced, and Time Resource.
Step 8 Click Close in the Operation Result dialog box that is displayed.
----End
20.2.9.5 Querying the Current Clock Tracing Source

The NMS provides the function of querying the clock source that an NE currently traces. By
using this function, you can learn the clock tracing status of the network.
Prerequisites
l
The clock source priority table must be configured.
Issue 03 (2012-11-30)

724
OptiX OSN 7500 II/7500/3500/1500

20 Clock Solution
Procedure
Step 2 In the window on the right, click the Clock Source Priority Table tab. Click Query.
Step 3 The Operation Result dialog box is displayed, Click Close.
----End
20.2.9.6 Configuring the Clock Interface

The IEEE 1588 V2 time synchronization and clock synchronization require high timing
precision. The time offset cannot be more than 1 us or less than -1 us. Hence, you need to set
the attributes of the clock interfaces on the source and sink clock sources so that an NE can verify
the time that is received.
Prerequisites
l
The board that can be configured as the clock source must be created.
Procedure
Step 2 In the window on the right, click the Clock Interface Configuration tab and set the relevant
parameters.
NOTE
Peer Clock Source ID to Be Received should be set to the same as the clock ID at the opposite end.
is successful.
Step 4 Click Close.
----End

The IEEE 1588v2 time synchronization or clock synchronization functions are mainly used in
scenarios wherein the high-precision time or clock synchronization is required. This topic
considers the synchronization of the 3G wireless base station by transmitting the IEEE 1588v2
clock as an example to describe how to configure the IEEE 1588v2 time synchronization.
Issue 03 (2012-11-30)

725
OptiX OSN 7500 II/7500/3500/1500

20 Clock Solution
20.2.10.1 Example Description

This topic considers a ring-with-chain topology as an example to describe how to transmit the
IEEE 1588v2 protocol packets, thus realizing the IEEE 1588v2 time synchronization and clock
synchronization.
Configuration Networking
As shown in Figure 20-28, NE1 accesses the IEEE 1588v2 packets and transmits the IEEE
1588v2 packets to the wireless base station through NE3. After the wireless base station receives
the IEEE 1588v2 time information, the time of the wireless base station is synchronized with
the time of the entire network.
Figure 20-28 Networking diagram (transmission of the IEEE 1588v2 time)
1588 MASTER
RNC
NE1
NE2
1588 SLAVE
NE3
NodeB
Cable
Fiber
Board Layout of Each NE

Figure 20-29 shows the board layouts of NE1 and NE2.
Issue 03 (2012-11-30)

726
OptiX OSN 7500 II/7500/3500/1500

20 Clock Solution
Figure 20-29 Board layouts of NE1, NE2, and NE3

S S S S S S S S S
2 3 3 3 3 3 3 3 3
9 0 1 2 3 4 5 6 7
PIU
AUX
S
2
8
FAN
S S S S S S S S
1 1 1 1 1 1 1 1
1 2 3 4 5 6 7 8
PEG8
SL64
PEG8
S
1
0
PSXCS
S S S S S S S S S
1 2 3 4 5 6 7 8 9
FAN
PSXCS
FAN
GSCC
GSCC
PIU
S S S S S S S S S
1 2 2 2 2 2 2 2 2
9 0 1 2 3 4 5 6 7
NE Configuration Mapping Table

Table 20-11 lists the values of the parameters of NE Parameter Configuration for NE1, NE2,
and NE3.
Table 20-11 NE parameters
Issue 03 (2012-11-30)
Parameter
NE1
NE2
NE3
PTP Protocol Status
Enabled
Enabled
Enabled
Clock Working Mode
BC
BC
BC
Clock Source Port
Local Clock Source

ID(Hexadecimal)
Domain Code for the

Clock Source
Quality Level of the

Clock Source
52
146
146
Quality Accuracy of
the Clock Source
34
40
40
Clock Drift Rate
12
12

727
OptiX OSN 7500 II/7500/3500/1500

20 Clock Solution
Parameter
NE1
NE2
NE3
Local Clock Source

Type
PTP
INTERNAL_OSCILLATOR
INTERNAL_OSCILLATOR

1

2
NE Time
Message Multicast
Mode
Multicast Mode
Multicast Mode
Multicast Mode
Time Calibration
Enabled
Enabled
Enabled
Protocol Frequency
Tracing
Enabled
Enabled
Enabled
Table 20-12 lists the parameters of External Clock Interface Configuration for NE1 and NE3.
Table 20-12 Parameters of the external clock interface
Issue 03 (2012-11-30)
Parameter
NE1
NE3
External Clock Input
Enabled
Enabled
Enabled
Enabled
External Clock Source ID

(Hexadecimal)
11
13
Clock Source Type
GPS
INTERNAL_OSCILLATOR
Clock Level
187
Clock Accuracy
32
45
Clock Source Priority 1
255
255
Adjustment Mode in Receive

Direction
Length(m)
Length(m)
Adjustment Value in Receive

Direction
100
1000
Adjustment Direction in
Receive Direction
Positive
Negative
Adjustment Mode in
Transmit Direction
Length(m)
Length(m)

728
OptiX OSN 7500 II/7500/3500/1500

20 Clock Solution
Parameter
NE1
NE3
Adjustment Value in
Transmit Direction
100
1000
Transmit Direction
Positive
Negative
Electrical Features of Serial

Port
rs232
rs232
Electrical Features of 1 pps
rs422
rs422
Table 20-13 lists the values of Time Resource in Clock Source Priority Table for NE1, NE2,
and NE3.
Table 20-13 Clock source Priority table
NE
Time Resource
NE1
Internal clock source, external clock source 1
NE2
Internal clock source, 3-PEG8-1(Port-1), 15-PEG8-1(Port-1)
NE3
Internal clock source, 3-PEG8-1(Port-1), 15-PEG8-1(Port-1)
Table 20-14 lists the values of the parameters of Clock Interface Configuration for NE2 and
NE3.
Table 20-14 Clock port configuration table
Issue 03 (2012-11-30)
Time
Resource
Time
Port
Delay
Announce Packet
Receiving Timeout
Coefficient
Fiber
Deviation
Mode
Fiber
Deviatio
n
Directio
n
Fiber
Devia
tion
NE2-3-PEG8-1
(Port-1)
P2P
length(m)
positive
direction
NE2-15PEG8-1
(Port-1)
P2P
length(m)
positive
direction
NE3-3-PEG8-1
(Port-1)
P2P
length(m)
positive
direction
NE3-15PEG8-1
(Port-1)
P2P
length(m)
positive
direction

729
OptiX OSN 7500 II/7500/3500/1500

20 Clock Solution
20.2.10.2 Configuration Process

According to the example description, configure the IEEE 1588v2 time synchronization and
clock synchronization functions on NE1, NE2, and NE3.
Prerequisites
l
The boards on each NE must be created according to Figure 20-29.
The networking must be complete according to Figure 20-28.
Procedure
Step 1 Configure NE1.
1.
According to 20.2.9.1 Setting the NE Parameters, set the parameters in NE Parameter

Configuration of NE1. For detailed configuration parameters, refer to Table 20-11.
2.
According to 20.2.9.3 Setting the Attributes of the External Clock Interface for an
NE, set the parameters in External Clock Interface Configuration of NE1. For detailed
configuration parameters, refer to Table 20-12.
3.
According to 20.2.9.4 Configuring the Clock Source Priority Table for an NE, set the
parameters in Clock Source Priority Table of NE1. For detailed configuration parameters,
refer to Table 20-13.

1.
According to 20.2.9.1 Setting the NE Parameters, set the parameters in NE Parameter

2.
According to 20.2.9.4 Configuring the Clock Source Priority Table for an NE, set the
parameters in Clock Source Priority Table of NE2. For detailed configuration parameters,
refer to Table 20-13.
3.
According to 20.2.9.6 Configuring the Clock Interface, set Clock Interface


1.
According to 20.2.9.1 Setting the NE Parameters, set NE Parameter Configuration of

NE3. For detailed configuration parameters, refer to Table 20-11.
2.
According to 20.2.9.3 Setting the Attributes of the External Clock Interface for an
NE, set External Clock Interface Configuration of NE3. For detailed configuration
parameters, refer to Table 20-12.
3.
According to 20.2.9.4 Configuring the Clock Source Priority Table for an NE, set Clock
Source Priority Table of NE3. For detailed configuration parameters, refer to Table
20-13.
4.
According to 20.2.9.6 Configuring the Clock Interface, set Clock Interface

----End
20.2.11 Verifying the IEEE 1588 V2 Time Synchronization and Clock

Synchronization
You need to check whether the IEEE 1588 V2 time synchronization and clock synchronization
functions are normal.
Issue 03 (2012-11-30)

730
OptiX OSN 7500 II/7500/3500/1500

20 Clock Solution
Prerequisites
l
The IEEE 1588 V2 clock synchronization function must be configured.
Context
When the IEEE 1588 V2 time synchronization and clock synchronization functions are normal,
each port of the clock source of the NE runs the BMC algorithm independently and automatically
evaluates the time packets received on each port of the clock source to determine the clock source
to be traced. When the clock information of the current clock tracing source is downgraded, the
NE runs the BMC algorithm and automatically switches to the clock source with the second
highest priority that is defined in the clock source priority table. This indicates that the IEEE
1588 V2 time synchronization and clock synchronization functions are normal.
Procedure
Step 2 In the window on the right, click the Clock Source Priority Table tab. Click Query to query
the values of Clock source ID currently Traced and Main clock ID currently Traced.
Step 3 Optional: When the NE traces an external clock source, click the External Clock Interface
Configuration tab and set the Clock level, Clock accuracy, Clock source priority 1, Clock
source priority 2 parameters to larger values, thus downgrading the external clock source.
CAUTION
After the external clock source is downgraded, the NE switches to trace another clock source.
In this case, the time synchronization in the entire time domain is affected. Exercise caution
when no standby external clock source is configured for the time domain.
Step 4 Repeat Step 2. If the value of Clock source ID currently Traced or Main clock ID currently
Traced is changed, this indicates that the IEEE 1588 V2 time synchronization and clock
synchronization functions are normal.
Step 5 After the verification, restore the modified parameters to the original values.
----End
20.2.12 Routine Maintenance

You need to check the performance of the IEEE 1588v2 time synchronization and clock
synchronization functions periodically.
Prerequisites
Issue 03 (2012-11-30)

731
OptiX OSN 7500 II/7500/3500/1500

20 Clock Solution
Procedure
Step 1 According to 20.2.9.3 Setting the Attributes of the External Clock Interface for an NE, check
whether the parameter settings in External Clock Interface Configuration of the NE comply
with the network planning. For parameters of External Clock Interface Configuration, see
20.2.15.5 External Clock Interface Configuration.
Step 2 According to 20.2.9.4 Configuring the Clock Source Priority Table for an NE, check whether
the parameter settings in Clock Source Priority Table of the NE comply with the network
planning. Check whether the values of Clock source ID currently traced and Main clock ID
currently traced of the NE are correct. For parameters of Clock Source Priority Table, see
20.2.15.2 Clock Source Priority Table.
Step 3 According to 20.2.9.6 Configuring the Clock Interface, check whether the parameter settings
in Clock Interface Configuration of the NE comply with the network planning. For parameters
of Clock Interface Configuration, see 20.2.15.4 Clock Interface Configuration.
----End
This topic describes how to rectify the fault that the clock source cannot be automatically
switched to a standby clock source when the current tracing clock is downgraded.
Prerequisites
Context
The possible causes of the failure of the clock source switching are as follows:
l
The parameter settings of the IEEE 1588v2 clock are incorrect.
The standby clock source is not available.
Figure 20-30 shows the troubleshooting process.
Issue 03 (2012-11-30)

732
OptiX OSN 7500 II/7500/3500/1500

20 Clock Solution
Figure 20-30 Flowchart for troubleshooting the failure of the automatic switching of the clock
source
Start
Whether the parameters

of the high precision time are
correctly configured?
No
Whether
to switch to the standby
clock source?
Modify parameters
Yes
No
Yes
Whether the
standby clock source
is available?
No
Add the available standby

clock source
Whether to
switch to the standby clock
source?
Yes
No
Yes
Contact Huawei engineers

to resolve the clock
source switching failure
End
Procedure
Step 1 Cause 1: The parameter settings of the IEEE 1588v2 clock are incorrect.
1.
Check whether the settings of the parameters in NE Parameter Configuration are correct.
Ensure that PTP protocol status is set to Enabled.
2.
Check whether the standby clock source is set in Clock Source Priority Table. Ensure
that the standby clock source is set in Clock Source Priority Table.
3.
Optional: If the standby clock source is External clock source 2, check whether the setting
of External Clock Interface 2 is correct. Ensure that the parameters of External Clock
Interface 2 are set correctly.
Step 2 Cause 2: The standby clock source is not available.

1.
Check current alarms to determine whether any alarms that are related to the standby clock
source exist. If yes, handle the alarms.
2.
Optional: If the standby clock source is an internal clock of an upstream NE, check whether
the settings of the parameters in NE Parameter Configuration of the upstream NE are
correct.
----End

This topic describes alarms and performance events that are related to this feature.
Issue 03 (2012-11-30)

733
OptiX OSN 7500 II/7500/3500/1500

20 Clock Solution

This topic describes the alarms related to the IEEE 1588v2 time synchronization and clock
synchronization.
Table 20-15 lists the alarms that are related to the IEEE 1588v2 time synchronization and clock
synchronization. For the detailed information of the related alarms, see the Alarms and
Table 20-15 Alarms related to High Precision Time Transmission
Alarm Name
Full Name
TIME_NO_TRACE_MODE
Loss of the clock tracing source
TIME_LOS
Loss of the clock source
TIME_FORCE_SWITCH
Forced switching of the clock source
EXT_TIME_LOC
Loss of the external clock source
TIME_NOT_SUPPORT
IEEE 1588v2 time synchronization and clock

synchronization function not supported by
the board

There are no performance events that are related to the IEEE 1588v2 time synchronization and
clock synchronization.
20.2.15 Parameter Description: IEEE 1588v2 Time Synchronization

and Clock Synchronization
20.2.15.1 NE Parameters
You need to set the NE parameters for achieving the IEEE 1588v2 time synchronization and
clock synchronization.
Table 20-16 lists the NE parameters.
Table 20-16 NE parameters
Issue 03 (2012-11-30)
Field
Value Range
Description
PTP Protocol Status
Enabled, Disabled
Specifies whether the PTP high precision time

transmission protocol is enabled on the NE.

734
OptiX OSN 7500 II/7500/3500/1500

20 Clock Solution
Field
Value Range
Description
Clock Working
Mode
BC, OC
l The OC equipment provides only one PTP

port and is used at the edge of a network.
l The BC equipment provides multiple PTP
ports and is used on the intermediate node of
a network.
Local Clock Source

ID(Hexadecimal)
For example,
00094e2d000000
00
Specifies Local clock source ID.
NOTE
The parameter
value ranges from
0 to 0xfffffffe.
Issue 03 (2012-11-30)
Domain Code for

the Clock Source
0, 4 to 127
Specifies Domain code for the clock source.

The NEs in a clock source domain trace the same
master clock.
Quality Level of the

Clock Source
6, 7, 13, 14, 52, 58,

68 to 122, 133 to
170, 216 to 232,
187, 193, 248
The smaller the value is, the higher the quality of

the clock is.
Quality Accuracy
of the Clock Source
32 to 49
The smaller the value is, the higher the precision

of the clock is.
Clock Drift Rate
0 to 65535
The smaller the value is, the smaller the clock

drift is, which indicates that the signals of the
clock are of higher quality.
Local Clock Source

Type
ATOMIC_CLOC
K, GPS,
TERRESTRIAL_
RADIO, PTP,
NTP,
HAND_SET,
OTHER,
INTERNAL_OS
CILLATOR
Specifies the type of the local clock source.
Clock Source
Priority 1
0 to 255
The smaller the value is, the higher the priority of

the clock is.
Clock Source
Priority 2
0 to 255
The smaller the value is, the higher the priority of

the clock is. When the Clock source priority 1
values of the clock sources are the same, you can
determine the priority of the clock sources
according to the Clock source priority 2 values.
NE Time
None
None.

735
OptiX OSN 7500 II/7500/3500/1500

20 Clock Solution
Field
Value Range
Description
Message Multicast
Mode
Multicast Mode,
Partially Multicast
Mode
Specifies the value of Message Multicast

Mode.
Time Calibration
Enabled, Disabled
Specifies the value of Time Calibration.
Protocol Frequency
Tracing
Enabled, Disabled
Specifies the value of Protocol Frequency

Tracing.
20.2.15.2 Clock Source Priority Table

You need to set the parameters such as Time Resource, Switching Mode, Clock source ID
currently traced, and Main clock ID currently traced when configuring the clock source
priority table.
Table 20-17 lists the parameters associated with configuring the clock source priority table.
Table 20-17 Parameters associated with configuring the clock source priority table
Field
Value
Description
Time Resource

(PORT-1)
Specifies the name of Time

Resource.
Switching Mode
Specifies the status of Switching

Mode.
NOTE
This parameter is not applicable to
setting of the priority table of the clock
source.
Clock source ID
currently traced

(PORT-1)
Specifies the name of Clock

source ID currently traced.
Main clock ID
currently traced
For example, 000900090007ff01
Specifies the ID of the NE where

the current clock tracing source is
located.
20.2.15.3 Configuration of the IEEE 1588v2 Packet on the Data Board

You need to set the parameters such as Encapsulation Type of the Protocol 1588 Packet on
the Data Board and Whether the VLAN Tag of the Protocol 1588 Packet is Detected on the
Data Board when configuring the IEEE 1588v2 packet on the data board.
Table 20-18 lists the parameters associated with configuring the IEEE 1588v2 packet on the
data board.
Issue 03 (2012-11-30)

736
OptiX OSN 7500 II/7500/3500/1500

20 Clock Solution
Table 20-18 Parameters associated with configuring the IEEE 1588v2 packet on the data board
Field
Value
Description
Encapsulation Type of the Protocol

1588 Packet on the Data Board
EthernetII IEEE 802.3, IP
Specifies the protocol

and standard that are
used for the
encapsulation of data
packets.
Whether the VLAN Tag of the

Protocol 1588 Packet is Detected on
the Data Board
The VLAN tag is not

permitted, The VLAN tag is
required

data packets that
encapsulate the time
information permit
the adding and
detection of VLAN
tags.
VLAN ID
Integer between 1 and 4095
Specifies the VLAN

ID.
20.2.15.4 Clock Interface Configuration

You need to set the necessary parameters such as Time Port Delay, Announce Packet
Receiving Timeout Coefficient, and Port PTP Status when configuring a time port.
Table 20-19 lists the parameters associated with configuring a time port.
Table 20-19 Parameters associated with configuring a time port
Field
Value
Description
Time Resource
For example, NE2-15N1PEG8-1(PORT-1)
Specifies the name of the clock

source.
Time Port Delay
E2E, P2P
E2E is applicable to a chain

network. P2P is applicable to a
mesh network.
NOTE
The N1PEX2 and N2PEX1 boards
do not support the P2P time port
delay.
Announce Packet
Receiving Timeout
Coefficient
Issue 03 (2012-11-30)
2 to 8

If several continuous Announce

packets are lost, the timeout
occurs. The value of the timeout
coefficient is the nth power of
Announce packets (n refers to
the preset value of this
parameter).
737
OptiX OSN 7500 II/7500/3500/1500

20 Clock Solution
Field
Value
Description
Port PTP Status
INITIALIZING, FAULTY,
DISABLED, LISTENING,
PRE_MASTER, MASTER,
PASSIVE, UNCALIBRATED,
SLAVE
Specifies the actual status of the

port of the clock source.
Fiber Deviation Mode
time(ns), length(m)
Specifies the mode that is used

to measure the deviation.
Fiber Deviation
Direction
positive direction, negative

direction
Specifies the direction in which

the fiber is adjusted.
Fiber Deviation
0 to 14562
Specifies the value of the fiber

deviation.
0 to 65529
l When the mode of fiber

deviation is length(m), the
value of the fiber deviation
is 0 to 14562.
l When the mode of fiber
deviation is time(ns), the
value of the fiber deviation
is 0 to 65529.
PTP protocol Message
Type
delay_req, announce, sync,

pdelay_req
Specifies the type of the time

packet.
PTP protocol Message

Send Index
The value varies according to

the PTP packet type.
Specifies the coefficient of the

interval of transmitting time
packets.
l In the case of Announce

packets: -4 to 4. Default
value: -3
l In the case of sync packets:
-8 to 1. Default value: -4
NOTE
To configure the IEEE 1588v2
clock synchronization, you must
set this parameter to -7 or a value
less than -7 for sync packets.
l In the case of delay_req and

pdelay_req packets: -4 to 4.
Default value: 0
20.2.15.5 External Clock Interface Configuration

You need to set the necessary parameters such as Clock Source Type, Clock Level, and Clock
Accuracy when configuring an external time interface.
Table 20-20 lists the parameters associated with configuring an external time interface.
Issue 03 (2012-11-30)

738
OptiX OSN 7500 II/7500/3500/1500

20 Clock Solution
Table 20-20 Parameters associated with configuring an external time interface
Issue 03 (2012-11-30)
Field
Value
Description
External Clock Input
Enabled, Disabled
Specifies the status of External

clock input.
Enabled, Disabled
Specifies the status of External

clock output.
External Clock Source ID

(Hexadecimal)
0 to 0xffffffffffffffff
Specifies the ID of the external

clock source.
Clock Source Type
ATOMIC_CLOCK,
GPS,
TERRESTRIAL_RADIO, PTP, NTP,
HAND_SET,
OTHER,
INTERNAL_OSCILLATOR
Specifies the value of Clock source

type.
Clock Level
6, 7, 13, 14, 52, 58, 68

to 122, 133 to 170, 216
to 232, 187, 193, 248,
255
The smaller the value is, the higher

the quality of the clock is.
Clock Accuracy
32 to 49

the precision of the clock is.
0 to 255
The smaller this value is, the higher

the priority of the clock is.
0 to 255

the priority of the clock is. When the
Clock source priority 1 values of
the clock sources are the same, you
can determine the priority of the
clock sources according to the
Clock source priority 2 values.
Adjustment Mode in Receive

Direction
Time(ns), Length(m)
This parameter indicates the

adjustment mode that is used to
measure the length of the cables in
the receive direction.
Adjustment Value in Receive

Direction
Integer between 0 and

300

adjustment length of the external
cables in the receive direction.

739
OptiX OSN 7500 II/7500/3500/1500

20 Clock Solution
Field
Value
Description
Receive Direction
Positive, Negative
When the cables in the receive

direction are longer than the cables
in the transmit direction, the value
of this parameter needs to be set to
Positive. When the cables in the
receive direction are shorter than
the cables in the transmit direction,
the value of this parameter needs to
be set to Negative.
Adjustment Mode in
Transmit Direction
Time(ns), Length(m)

adjustment mode that is used to
measure the length of the cables in
the transmit direction.
Adjustment Value in
Transmit Direction
Integer between 0 and

300

adjustment length of the external
cables in the transmit direction.
Transmit Direction
Positive, Negative
When the cables in the receive

direction are longer than the cables
in the transmit direction, the value
of this parameter needs to be set to
Positive. When the cables in the
receive direction are shorter than
the cables in the transmit direction,
the value of this parameter needs to
be set to Negative.
Electrical Features of Serial

Port
rs232, rs442
Codes the time information by

using the ASCII character codes
through the RS232/RS422 serial
communication port and the baud
rate is 9600 bit/s.
Electrical Features of 1 pps
ttl, rs442
Indicates the second pulse signal,

whose rising edge marks the
accurate start of each second.
20.3 Synchronous Ethernet Clock

The synchronous Ethernet clock is a technology that recovers the clock from the bit stream on
the Ethernet link.
20.3.1 Introduction
The synchronous Ethernet clock is a technology that extracts the clock from the serial bit stream
on the Ethernet line, and transmits data through the extracted clock to realize the transfer of
clocks.
Issue 03 (2012-11-30)

740
OptiX OSN 7500 II/7500/3500/1500

20 Clock Solution
Definition
The synchronous Ethernet clock is a technology of frequency synchronization over the physical
layer. The system directly extracts the clock signal from the serial bit stream on the Ethernet
line, and transmits the data to each board by using the clock signal to realize the transfer of clock
information.
Purpose
As the network is increasingly based on the Ethernet transfer technology, the large-scale network
at the carrier-class level requires the synchronous Ethernet to transmit the clock and introduces
the networkwide synchronous timing transmission idea of the SDH system to the Ethernet
design. Thus, the clock signal can be transmitted from the core to the edge by using the Ethernet
physical layer, to provide ensured timing for various real-time services.

Learning about the basic concepts helps to further understand the synchronous Ethernet clock
feature.
SSM Byte
The synchronous status message (SSM) byte is located on the twenty-eighth byte of the Ethernet
frame. The higher four bits of this byte represent the clock ID, and the lower four bits of this
byte represent the clock quality. These bits represent the clock quality in the same way as the
S1 byte of the SDH network. That is, when the value of the lower four bits of the SSM byte is
smaller, the clock source quality is higher. Table 20-21 lists the represented clock quality.
Table 20-21 Mapping between the SSM and the clock quality
Issue 03 (2012-11-30)
Bits 5-8 of the SSM Byte
Description of the Clock Quality Grade
0000
Synchronization quality unknown (existing

synchronous network)
0001
Reserved
0010
ITU-T G.811 clock signal
0011
Reserved
0100
SSU-Aa
0101
Reserved
0110
Reserved
0111
Reserved
1000
SSU-Ba
1001
Reserved
1010
Reserved
1011
SDH equipment timing source (SETS) signal

741
OptiX OSN 7500 II/7500/3500/1500

20 Clock Solution
Bits 5-8 of the SSM Byte
Description of the Clock Quality Grade
1100
Reserved
1101
Reserved
1110
Reserved
1111
Not used for synchronization
a: The "G.812 Transit Exchange" and "G.812 Local Clock" terms are used in the previous version
of ITU-T Recommendations. In the new version of ITU-T G.812, the clock definition is changed
to synchronization supply unit (SSU) that is available in types A and B.
The clock ID is bits 1-4 of the SSM byte, and takes a value of 0x0-0xf. Basically, the clock ID
is used to distinguish the clock information about the local node from the clock information
about another node, to prevent a node from tracing the clock signal that is locally transmitted
and comes from the negative direction. In this manner, a timing loop is prevented.
When the clock ID is 0, it indicates that the clock ID is invalid. Thus, the clock ID is 0 when the
ID is not set for a clock source. When the extended SSM protocol is enabled, the NE does not
select the clock source whose ID is 0 as the current clock source.
The clock ID is a tag that is set for a reference timing source. The clock sources at the same
quality level that carry different IDs mean different timing signals and are the same in priority
level and other aspects.
SSM Protocol
SSM protocols are classified into the standard SSM protocol and the extended SSM protocol.
l
The standard SSM protocol is a mechanism of network synchronization management. It

uses bits 5-8 of the SSM byte to exchange the quality information about clock sources
between nodes. This ensures that the equipment automatically selects the clock source of
the highest quality and priority level, to prevent an interlock of clocks. The standard SSM
protocol improves the performance of a synchronous network, and realizes synchronization
of different network topologies in an easy manner. The standard SSM protocol applies to
the interconnection of devices of different vendors.
In the case of the extended SSM protocol, Huawei introduces the idea of the clock ID based
on the standard SSM protocol. The extended SSM protocol uses bits 1-4 of the SSM byte
as the unique ID of a clock source, and transports the clock ID with an SSM. After a node
receives the SSM byte, the node verifies the clock ID (bits 1-4) to determine whether the
clock is locally transmitted. If yes, the node considers the clock source cannot be used.
Thus, a timing loop is prevented. The extended SSM protocol is mainly used for the
interconnection of transmission devices of Huawei.
This section describes the capacity of the OptiX OSN equipment for supporting synchronous
Ethernet clocks.
Table 20-22 provides specifications associated with synchronous Ethernet clocks.
Issue 03 (2012-11-30)

742
OptiX OSN 7500 II/7500/3500/1500

20 Clock Solution
Table 20-22 Specifications associated with synchronous Ethernet clocks

Item
Specifications
Support capability
Number of ports: 64
Clock frequency accuracy (24 hours)
1 ppm
Synchronization precision
Complies with ITU-T G.

8262.

This topic describes the standards and protocols that the synchronous Ethernet clock complies
with.
The synchronous Ethernet clock complies with the following standards and protocols:
l
ITU-T G.810: Definitions and terminology for synchronization networks
ITU-T G.811: Timing characteristics of primary reference clocks
ITU-T G.812: Timing requirements of slave clocks suitable for use as node clocks in
synchronization networks
ITU-T G.8261: Timing and synchronization aspects in packet networks
20.3.5 Availability
The synchronous Ethernet clock feature requires the support of the applicable equipment and
boards.
Version Support
Issue 03 (2012-11-30)
Product Name
Applicable Version
OptiX OSN 1500/3500
V100R009C03
T2000
V200R007C03
Product Name
Applicable Version
OptiX OSN 1500/3500/7500
U2000
Product Name
Applicable Version
OptiX OSN 7500 II
U2000

743
OptiX OSN 7500 II/7500/3500/1500

20 Clock Solution
Hardware Support
Issue 03 (2012-11-30)
Board
Type
Whether to
Support the
Extended
SSM Protocol
Applicable
Equipment
Version
N1PEG16
Yes
V100R009C03
and later
OptiX OSN 3500
N1PEX1
Yes
V100R009C03
and later
OptiX OSN 3500
N1PETF8
Yes
V100R009C03
and later
OptiX OSN 3500/7500
R1PEFS8
Yes
V100R009C03
and later
Q1PEGS2
Yes
V100R009C03
and later
R1PEGS1
Yes
V100R009C03
and later
N1PEG8
Yes
V200R011C00
and later
OptiX OSN 3500/7500
N2PEX1
Yes
V200R011C00
and later
OptiX OSN 3500/7500
N1PEX2
Yes
V200R011C00
and later
OptiX OSN 3500/7500
N1PEFF8
Yes
V200R011C00
and later
OptiX OSN 3500/7500
R1PEF4F
Yes
V200R011C00
and later
TNN1EX
2
Yes
V200R011C01
and later
OptiX OSN 7500 II
TNN1EG
8
Yes
V200R011C01
and later
OptiX OSN 7500 II
TNN1ET
MC
Yes
V200R011C01
and later
OptiX OSN 7500 II
TNN1EFF
8
Yes
V200R011C02
and later
OptiX OSN 7500 II

744
OptiX OSN 7500 II/7500/3500/1500

20 Clock Solution

This section describes the limitations on and precautions for synchronous Ethernet clock in the

Applicable
Object

Details
Remarks
Synchronous
Ethernet clock
If a clock extracting from an

Ethernet port is configured as a
clock source, enable the
synchronous Ethernet function on
the Ethernet port.
Synchronous
Ethernet clock
To enable synchronous Ethernet on

a port, you only need to add the clock
from the port into the clock source
priority table.
Synchronous
Ethernet clock
A synchronous Ethernet port

supports standard SSM and
extended SSM.
TNN1EG8 and
N1PEG8
Only GE optical interfaces of the

TNN1EG8 and N1PEG8 support the
synchronous Ethernet clock
function.

None.
None.
20.3.7 Principles
This topic describes the principles for realizing the synchronous Ethernet clock function.
20.3.7.1 Protocol Data Unit of the Synchronous Ethernet Clock

The synchronous Ethernet clock is a technology of frequency synchronization at the physical
layer. To be specific, the SSM byte carrying the clock source quality information is encapsulated
into an Ethernet frame, and the system directly extracts the clock signal from the serial bit stream
on the Ethernet line to realize the transfer of clocks.
Figure 20-31 shows the position of the SSM byte in an Ethernet frame.
Issue 03 (2012-11-30)

745
OptiX OSN 7500 II/7500/3500/1500

20 Clock Solution
Figure 20-31 Protocol data unit of the synchronous Ethernet clock

Octets
6
MAC Destination Address
MAC Source Address
Slow Protocol Ethertype
Slow Protocol Subtype
ITU-OUI
ITU Subtype
Version and Event flag
Reserved
TLV
SSM
64-1490
4
Data and Padding

Frame Check Sequence
MAC Destination Address: is always set to 0x01-80-C2-00-00-02, which indicates the

multicast address of the slow protocol.
MAC Source Address: indicates the MAC address of the port at the transmit end.
Slow Protocol Ethertype: is always set to 0x8809, which indicates the type of the slow
protocol.
Slow Protocol Subtype: is always set to 0x0A, which indicates that the type of the slow
protocol is the synchronous Ethernet clock.
ITU-OUI: is always set to 0x00-19-A7, which indicates the unique ID of the protocol type
of the synchronous Ethernet clock.
ITU-Subtype: is always set to 0x0001, which indicates the subtype of the protocol type of
the synchronous Ethernet clock.
Version and Event Flag: The higher four bits of this byte indicate the protocol version; the
fifth bit indicates the event flag (When the value of the SSM byte is changed, the value of
this bit is set to 1); the lower three bits are reserved.
Reserved: is a reserved field. Generally, it takes the value of all 0s.
TLV: is the type length field.
SSM: The first four bits indicate the clock ID, and the last four bits indicate the quality of
the clock source information.
Issue 03 (2012-11-30)

746
OptiX OSN 7500 II/7500/3500/1500

20 Clock Solution
Data/Pad Field: is the data and padding field.
Frame Check Sequence: indicates the frame check.
20.3.7.2 Process for Realizing the Synchronous Ethernet Clock

The synchronous Ethernet clock is a technology of the clock frequency synchronization at the
Ethernet physical layer. The system can directly extract the clock signal from the serial bit stream
on the Ethernet line, and transmit the clock signal to each board to realize the transfer of clocks.
The synchronous Ethernet formed by the equipment can realize the synchronization at the
Ethernet physical layer. Figure 20-32 shows the networking of the synchronous Ethernet clock.
Figure 20-32 Process for realizing the synchronous Ethernet clock
BSC
RNC
BITS
GE ring
FE
Clock
information
NodeB
OptiX OSN equipment
BSC
RNC
BITS
Optical fiber
Clock information
The clock signal is transmitted between NEs over the synchronous Ethernet as follows:
1.
The BITS transmits the clock signal to the NE on the synchronous Ethernet through the
external clock interface.
2.
Through the synchronous Ethernet interface, the data board that supports the synchronous
Ethernet clock function extracts the clock signal from the serial bit stream on the Ethernet
physical-layer line and then selects a clock source.
Issue 03 (2012-11-30)

747
OptiX OSN 7500 II/7500/3500/1500

3.
4.
20 Clock Solution
After the NE extracts the clock, the clock phase-locked loop traces the optimal clock source
and locks its phase. Then, the system clock is synchronized with the optimal clock source.
Finally, the NE transmits the system clock to the NodeB, BSC, or RNC through the
synchronous Ethernet interface of the data board. In this manner, the clock signal is
transmitted downstream on the synchronous Ethernet.

The synchronous Ethernet clock mainly realizes the frequency synchronization of the data
network, and lays a foundation for the IEEE 1588v2 time synchronization.
The networking and application of the synchronous Ethernet clock is shown in Figure 20-33:
The PRC transmits the clock signal to NE A and NE B through the external clock interface, and
NE A and NE B transmit the clock synchronization information to the downstream NE C and
NE D. Then, NE D transmits the clock synchronization information from the convergence ring
to an NE at the access layer. Finally, the NE at the access layer transmits the clock
synchronization information to each base station on the network. In this manner, the clock
synchronization of the entire network is achieved.
Figure 20-33 Realization process of the synchronous Ethernet clock
Clock source
PRC
~
Clock source
PRC
~
Clock
information
Clock
synchronization
intermediate
equipment
2.5 Gbit/s
chain
622 Mbit/s
chain
Clock
synchronization
intermediate
equipment
B
GE
ring
Clock
synchronization
intermediate
equipment
Clock
synchronization
intermediate
equipment
Clock
information
Clock
synchronization
intermediate
equipment
155 Mbit/s
chain
Clock
synchronization
intermediate
equipment
Convergence
layer
Clock
synchronization
intermediate
equipment
Clock
synchronization
intermediate
equipment
Clock
synchronization
slave equipment
Clock
synchronization
slave equipment
Access
layer
Clock
synchronization
slave equipment
OptiX OSN equipment
OptiX 155/622H equipment

Clock information
Issue 03 (2012-11-30)

748
OptiX OSN 7500 II/7500/3500/1500

20 Clock Solution
20.3.9 Configuring Synchronous Ethernet Clocks

An Ethernet can operate stably with the help of synchronous Ethernet clocks. Therefore,
configure synchronous Ethernet clocks for each NE prior to the configuration of data services.
In the case of a complex network, you also need to configure Ethernet clock protection.
20.3.9.1 Configuring NE Clock Sources

Before configuring data services, you must configure NE clock sources and specify the priority
levels to ensure that correct clock tracing relationships are created for all the NEs on a network.
Prerequisites
To achieve clock protection, you must configure at least two traceable clock sources for an NE.
After you configure clock sources for all NEs, query the network-wide clock tracing status again.
Procedure
Configuration > Clock > Physical Layer Clock > Clock Source Priority from the Function
Tree.
Step 2 Click Query to query the existing clock sources.
Step 3 Click Create. In the Add Clock Source dialog box that is displayed, select a new clock source.
Click OK.
Step 4 Optional: If an external clock source is selected, select External Clock Source Mode based
on the type of external clock signals. In the case of 2 Mbit/s clocks, specify Synchronous Status
Byte that functions to transfer the clock quality information.
Step 5 Select a clock source and click
or
to adjust its priority.
NOTE
Internal clock sources have the lowest priority due to their low precision.
Issue 03 (2012-11-30)

749
OptiX OSN 7500 II/7500/3500/1500

20 Clock Solution
Step 6 Click Apply.

NOTE
If the clock tracing relationship changes because of any change in the clock source, the Warning dialog
box is displayed, asking you whether to refresh the clock tracing relationship. In this case, click OK.
----End
20.3.9.2 Configuring Protection for Clock Sources

All the NEs on a complex clock network need to be configured with clock protection. After you
set clock sources and specify their priorities for an NE, start the standard SSM protocol or
extended SSM protocol to ensure that the NE always traces a correct clock source.
Prerequisites
Procedure
Configuration > Clock > Physical Layer Clock > Clock Subnet Configuration from the
Function Tree.
Step 2 Click the Clock Subnet tab. Then, click Query to query the parameter settings.
Step 3 Select Start Standard SSM Protocol or Start Extended SSM Protocol.
NOTE
Select the same type of SSM protocol for the NEs that belong to the same clock subnet.
Step 4 Set a subnet ID for the clock subnet to which the NE belongs.
NOTE
The NEs that trace the same clock source are allocated with the same clock subnet ID.
Step 5 Optional: If the extended SSM protocol is enabled, you need to set Clock Source ID.
Step 6 Click Apply. In the Operation Result dialog box that is displayed, click Close.
----End

Synchronous Ethernet clocks support the standard SSM protocol and the extended SSM protocol.
When a network comprises only Huawei equipment, it is recommended that you use the extended
Issue 03 (2012-11-30)

750
OptiX OSN 7500 II/7500/3500/1500

20 Clock Solution
SSM protocol. This topic considers the extended SSM protocol as an example to describe how
to configure synchronous Ethernet clocks.
20.3.10.1 Description of the Example

The extended SSM protocol allows an NE to consider the clock ID as well as the clock quality
level and clock priority when determining an available clock source. On the receipt of a clock
signal with an ID, an NE checks the source of the signal. If the clock signal is found transmitted
from this NE, it is considered as unavailable. This method helps an NE identify a clock signal
transmitted from itself even after the clock signal is transmitted over several NEs. Therefore,
occurrence of timing loops is prevented.
As shown in Figure 20-34, clocks of all the NEs on the ring network are synchronized with the
BITS (external clock equipment).
l
The mode of the external clock equipment is 2 Mbit/s, and the timeslot is SA4.
All the NEs belong to clock subnet 1.
The clock source priority of each NE is set according to the clock source priority list
provided in Figure 20-34.
Figure 20-34 Networking diagram of synchronous Ethernet clocks

BITS
BITS clock source

3-PEG16-2 clock source
Internal clock source
3-PEG16-1
3-PEG16-2
NE1
3-PEG16-2
3-PEG16-1
NE2
NE4
3-PEG16-1

3-PEG16-2
NE3
3-PEG16-2

3-PEG16-1

Node B
Clock source priority list
Clock signal flow

After the extended SSM protocol is enabled, you need to allocate IDs for clock sources of each
NE according to configuration principles.
Issue 03 (2012-11-30)

751
OptiX OSN 7500 II/7500/3500/1500

20 Clock Solution
Procedure
Step 1 Configure the clock source priority for each NE. For details, see 20.3.9.1 Configuring NE Clock
Sources.
l Clock Source: external clock source 1 that is connected to the BITS, 3-PEG16-2 optical port
that is connected to an upstream NE, 3-PEG16-1 optical port that is connected to a
downstream NE, and internal clock source.
l Clock Source: 3-PEG16-2 optical port that is connected to an upstream NE, 3-PEG16-1
optical port that is connected to a downstream NE, and internal clock source.
Set the following parameters for NE3 and NE4:
l Clock Source: 3-PEG16-1 optical port that is connected to an upstream NE, 3-PEG16-2
optical port that is connected to a downstream NE, and internal clock source.
Step 2 Configure the affiliated clock subnet of each NE. For details, see 20.3.9.2 Configuring
Protection for Clock Sources.
Step 3 Enable the extended SSM protocol for each NE. For details, see 20.3.9.2 Configuring
Protection for Clock Sources.
Step 4 Configure the clock ID for each clock source. For details, see 20.3.9.2 Configuring Protection
for Clock Sources.
Set the following parameters for NE1 to NE4.
NE
Clock Source
Clock Source ID
NE1
BITS
3-PEG16-2
3-PEG16-1
3-PEG16-2
3-PEG16-1
3-PEG16-1
3-PEG16-2
NE2
NE3
Issue 03 (2012-11-30)

752
OptiX OSN 7500 II/7500/3500/1500

NE
NE4
20 Clock Solution
Clock Source
Clock Source ID
3-PEG16-1
3-PEG16-2
NOTE
----End
20.3.11 Verifying Synchronous Ethernet Clocks

Verify configured synchronous Ethernet clocks to ensure that they work properly.
Prerequisites
l
Synchronous Ethernet clocks must be configured.
Procedure
Step 1 In the NE Explorer, select the NE from the Object Tree and then choose Configuration >
Clock > Physical Layer Clock > Clock Source Priority from the Function Tree.
Step 2 Click the System Clock Source Priority List tab in the pane on the right. Then, click Query
to query the priority sequence of the clock sources.
Clock > Physical Layer Clock > Clock Subnet Configuration from the Function Tree.
Step 4 Click the Clock Subnet tab in the pane on the right. Then, click Query to query the IDs of the
clock sources.
Clock > Physical Layer Clock > Clock Source Switching from the Function Tree.
Step 6 Click the Clock Source Switching tab in the pane on the right. Then, click Query to query the
statuses of the clock sources.
NOTE
If the value of Switching of a clock source is Normal, the synchronous Ethernet clock is configured
successfully.
----End
Issue 03 (2012-11-30)

753
OptiX OSN 7500 II/7500/3500/1500

20 Clock Solution
Fault Symptom
The common faults regarding the synchronous Ethernet clock are as follows:
A clock source cannot be properly switched and the quality of clock is low.
Possible Causes
l
The connection at the port fails.
An alarm associated with the synchronous Ethernet clock function occurs on the network.
Figure 20-35 Flow chart for handling a synchronous Ethernet clock fault
Start
Does the
connection at
the port fail?
Yes
Handle the fault
No
Does an alarm
associated with the
synchronous Ethernet
clock occurs?
Yes
Clear the alarm
No
No
Is the fault
rectified?
Yes

support engineers
End
Procedure
Step 1 Cause 1: The connection at the port fails.
1.
Issue 03 (2012-11-30)
Check whether the ETH_LOS or ETH_LINK_DOWN alarm occurs at the port.

754
OptiX OSN 7500 II/7500/3500/1500

2.
20 Clock Solution
If yes, clear the alarm and then check whether the fault is rectified. For details on how to
clear the alarm, see the Alarms and Performance Events Reference.
Step 2 Cause 2: An alarm associated with the synchronous Ethernet clock occurs on the network.
1.
Check whether any alarm associated with the synchronous Ethernet clock occurs on the
network. For details, see 20.3.13.1 Relevant Alarms.
2.
If yes, clear the alarm. For details on how to clear the alarm, see the Alarms and
----End

This topic describes the alarms and performance events that are related to the synchronous
Ethernet clock feature.

This topic describes the alarms that are related to the synchronous Ethernet clock feature.
Table 20-23 lists all the alarms that are related to the synchronous Ethernet clock feature.
Table 20-23 Alarms related to the synchronous Ethernet clock feature
Alarm Name
Meaning
CLK_NO_TRACE_MODE
The clock does not work in the tracing mode.
EXT_SYNC_LOS
The external clock source is lost.
LTI
The synchronous clock source is lost.
S1_SYN_CHANGE
The clock sources are switched when the S1

byte mode is adopted.
SYNC_F_M_SWITCH
The clock sources are switched manually or

forcibly.
SYNC_LOCKOFF
The clock source is locked.
SYNC_C_LOS
The SYNC_C_LOS is an alarm indicating the

loss of synchronization source level.
SYN_BAD
The SYN_BAD indicates the

synchronization clock source degrades.
OOL
The OOL is an alarm indicating that the

phase-locked loop is out of lock.

There are no performance events that are related to the synchronous Ethernet clock feature.
Issue 03 (2012-11-30)

755
OptiX OSN 7500 II/7500/3500/1500

20 Clock Solution
20.3.14 Parameter Description: Synchronous Ethernet Clock

This section describes the parameters for configuring the synchronous Ethernet clock.
20.3.14.1 Managing External Clock Sources

To use an external clock as the clock source, you need to set the relevant parameters such as the
output mode, output timeslot, and output threshold of the external clock source.
Table 20-24 lists the parameters for configuring the output phase-locked source table of an
external clock.
Table 20-24 Parameters for configuring the output phase-locked source table of an external
clock
Field
Value Range
Description
NE Name
For example, NE1
NE Synchronous Clock
Output<2M Phase-Locked
Source>
Default value: Internal Clock

Source
Specifies the output of the

source.
You can select an internal
clock source or a line clock
source. In normal cases,
select Internal Clock
Source. If the 2M phaselocked clock source is used
for amplifying the clock
source through repeaters, the
clock signals that have
certain frequency deviation
and drift can be optimized
under the assistance of the
other local synchronous
clock source. In this case, this
parameter needs to be set
according to the clock level,
and you need to select the
other clock source (for
example, Line Clock
Source) as the 2M phaselocked clock source.
Output Impedance of
Issue 03 (2012-11-30)
75 ohms, 120 ohms



clock 1.
756
OptiX OSN 7500 II/7500/3500/1500

20 Clock Solution
Field
Value Range
Description
Output Impedance of
75 ohms, 120 ohms

clock 2.

Clock Source 1
2 Mbit/s, 2 MHz

Clock Source 2
2 Mbit/s, 2 MHz
Clock Source Threshold
No Threshold Value, G.813

SDH Equipment Timing
Source (SETS) Signal, G.812
Lock Clock Signal, G.812
Transit Clock Signal, G.811
Clock Signal

clock 1.
clock 2.
Specifies the synchronous
source threshold of the 2M
synchronous output clock
source.
The synchronous source
threshold is used for clock
protection based on the S1
byte. The clock system of the
NE considers the value of this
parameter as the base of the
clock output quality. The
clock system of the NE can
output clock signals only
when the clock quality
exceeds the specified
threshold.
Threshold for more
information.
Table 20-25 lists the parameters for configuring the 2M phase-locked source attributes of an
external clock.
Table 20-25 Parameters for configuring the 2M phase-locked source attributes of an external
clock
Issue 03 (2012-11-30)
Field
Value Range
Description
Number
For example, NE350-2M

phase-locked source 1

external clock source output
of the NE.

757
OptiX OSN 7500 II/7500/3500/1500

20 Clock Solution
Field
Value Range
Description

Switch
Open, Close
Specifies the output switch of

the external clock source.
External Clock Output Mode
2 MHz, 2 Mbit/s
Specifies the mode used for

the external clock source to
output 2M clock signals.

Output Mode for more
information.
Timeslot
SA4, SA5, SA6, SA7, SA8,

ALL
Default value: All
Specifies the timeslot used by

the SSM in the output 2M
clock signals.
For example, if you set this
parameter to SA4, the SSM is
transmitted by the fourth bit
of the eight bits in the first
timeslot (TS0) of four
consecutive even frames. If
SA5, the SSM is transmitted
by the fifth bit of the eight bits
in the timeslot (TS0) of four
consecutive even frames.
You can set this parameter
only in 2 Mbit/s output mode.
Output Timeslot for more
information.
External Source Output

Threshold
Issue 03 (2012-11-30)
Threshold Disabled, Not

Inferior to G.813 SETS
Signal, Not Inferior to G.812
Local Clock Signal, Not
Inferior to G.812 Transit
Clock Signal, Not Inferior to
G.811 Clock Signal
Specifies the quality standard

for the output of the external
clock source. If the quality
value is less than the
threshold, the external clock
source stops outputting clock
signals.
Default value: Threshold

Disabled
Click A.27.3 External

Source Output Threshold

758
OptiX OSN 7500 II/7500/3500/1500

20 Clock Solution
Field
Value Range
Description
Fail Condition
AIS, LOF, AIS OR LOF, No

Failure Condition
Specifies the condition used

for determining whether the
source is faulty. If you set this
parameter to AIS OR LOF,
the AIS or LOF alarm may
cause failure in the 2M
phase-locked clock source.
Default value: No Failure

Condition
Click A.27.4 2M PhaseLocked Source Fail

Condition for more
information.
Fail Action
2M Output S1 Byte
Unavailable, Send AIS, Shut
Down Output
Default value: Shut Down
Output
Specifies the operations to be

performed when the 2M
phase-locked clock source is
faulty. If the 2M phaselocked clock source is faulty,
the external clock outputs the
signals according to the
setting of this parameter.
Click A.27.5 2M PhaseLocked Source Fail Action
20.3.14.2 Configuring Clock Protection and Restoration

You need to configure necessary protection for the clock so that the NE can be synchronized
normally.
Table 20-26 lists the parameters for configuring clock protection and restoration.
Table 20-26 Parameters used for configuring clock protection and restoration
Issue 03 (2012-11-30)
Field
Value Range
Description
NE Name
For example, NE1

759
OptiX OSN 7500 II/7500/3500/1500

20 Clock Solution
Field
Value Range
Description
Higher Priority Clock Source

Reversion Mode
Auto-Revertive, NonRevertive
When the quality of a higherpriority clock source

degrades, the NE
clock source to a lowerpriority clock source. If you
set this parameter to AutoRevertive, the NE
source restores. If you set this
parameter to NonRevertive, the NE does not
automatically switch the
source restores.
Click A.27.12 Higher
Priority Clock Source
Reversion Mode for more
information.
Clock Source WTR Time

(min.)
0 to 12
Default value: 5
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
prevent the operations that
are performed by the clock
selector due to transient clock
signal restoration.
WTR Time for more
information.
Clock Source
Issue 03 (2012-11-30)
For example, Internal Clock

Source


clock source.
760
OptiX OSN 7500 II/7500/3500/1500

20 Clock Solution
Field
Value Range
Description
AIS Alarm Generated
Yes, No

enabled. If the AIS alarm is
source is faulty.
Default value: No
Click A.27.9 AIS Alarm

Generated for more
information.
B1 BER Threshold-Crossing
Generated
Yes, No
Default value: No

enabled. If a B1 thresholdcrossing event is reported, the
is faulty.
Click A.27.10 B1 BER
Threshold-Crossing
Generated for more
information.
RLOS, RLOF and OOF

Alarms Generated
Yes
Displays whether the

enabled. If the R_LOS,
R_LOF, or OOF alarm is
source is faulty.
By default, this parameter is
set to yes and cannot be
changed.
Issue 03 (2012-11-30)
CV Threshold-Crossing
Generated
Yes, No

enabled. If a CV thresholdcrossing event is reported, the
is faulty.
CV Threshold
Displays the CV threshold.

761
OptiX OSN 7500 II/7500/3500/1500

20 Clock Solution
Field
Value Range
Description
B2-EXC Alarm Generated
Yes, No

enabled. If the B2-EXC
alarm is reported, the NE
considers that the
is faulty.
Click A.27.11 B2-EXC
Alarm Generated for more
information.
Effective Status
Valid, Invalid
Specifies whether the clock

source is valid. This
only.
Lock Status
Lock, Unlock
Specifies whether a
switching operation is
allowed.
Click A.27.15 Lock Status
(Clock) for more
information.
Switching Source
For example, 11-N2SL16-1

(SDH-1)
Displays the clock source to

be traced by the NE after the
switching.
Switching Status
Forced Switching, Manual

Switching, Normal
Displays the switching status

20.3.14.3 Clock Quality and Status Management

You can manage the quality and status of a clock to ensure the stability and precision of the
clock source that is currently traced.
Table 20-27 lists the parameters that are used for managing the quality and status of a clock.
Table 20-27 Parameters for managing the quality and status of a clock
Issue 03 (2012-11-30)
Field
Value Range
Description
NE Name
For example, NE1

762
OptiX OSN 7500 II/7500/3500/1500

20 Clock Solution
Field
Value Range
Description
NE Clock Working Mode
Normal Mode, Holdover

Mode, Free-Run Mode
Displays the current working

mode of the clock board on
the NE. This parameter is
used for query only.
Normal Mode: The
reference clock source is
input for clock
synchronization in the actual
service condition.
Holdover Mode: When all
the timing reference clock
sources are lost, the clock
works on the basis of the
stored frequency
information.
Free-Run Mode: The clock
works by using the internal
crystal oscillator.
Click A.27.20 NE Clock
Working Mode for more
information.
S1 Byte Synchronization
Quality Information
For example, NA
Displays the S1 byte

information in the clock
signal of the current NE. This
only.
Click A.27.19 S1 Byte
Synchronization Quality
Information for more
information.
S1 Byte Clock Synchronous

Source
For example, NA

only.
The relevant information can
be displayed only when the
S1 byte is used. That is, the
clock protection function is
enabled. Similarly, the
relevant information can be
displayed only when you
click Query. Otherwise, only
NA is displayed.
Issue 03 (2012-11-30)

763
OptiX OSN 7500 II/7500/3500/1500

20 Clock Solution
Field
Value Range
Description
Synchronous Source
For example, External Clock

Source1

only.
In normal cases, the
synchronous source is the
clock source of the highest
priority. If the synchronous
source fails to be traced, the
clock source of a lower
priority is traced.
Click A.27.17 Synchronous
Source for more
information.
Data Output Method in

Holdover Mode
Normal Data Output Mode,

Displays the data output

method.
Click A.27.27 Data Output
Method in Holdover Mode
Clock Source Quality
Quality, 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, NA
After the SSM protocol is

started, the NE parses the
SSM code according to the
S1 byte of each clock source
to obtain the quality
information of the clock
source. If the NE fails to
parse the SSM code, you
need to manually set the
quality of the clock source.
Quality for more
information.
20.3.14.4 Retiming Management

This topic describes the parameters that are used for setting the retiming clock source and the
retiming mode.
Table 20-28 lists the parameters that are used for retiming.
Issue 03 (2012-11-30)

764
OptiX OSN 7500 II/7500/3500/1500

20 Clock Solution
Table 20-28 Parameters used for retiming

Field
Value Range
Description
Retiming Mode

Mode of Cross-Connect
Clock
Default value: Normal
The Retiming Mode

parameter specifies whether
the retiming clock, tributary
clock, or cross-connect
(external) clock is used.
Click A.27.29 Retiming
20.4 CES ACR

This chapter describes the CES ACR feature.
20.4.1 Introduction
This section provides the definition of CES ACR and describes its purpose.
Definition
CES ACR is a function that uses the adaptive clock recovery (ACR) technology to recover clock
synchronization information carried by CES packets. In the standard CES ACR solution, the
source end (Master) considers the local clock as the timestamp in the Real-time Transport
Protocol (RTP) packet header and encapsulates it in the CES packet; the sink end (Slave) recovers
the clock according to the timestamp in the packet. In this manner, signal impairment during the
transmission is prevented.
The OptiX OSN 7500 II adopts the enhanced timestamp clock solution. That is, clocks can be
recovered based on SN in CES packets rather than timestamps in RTP packet headers. See
Figure 20-36.
Issue 03 (2012-11-30)

765
OptiX OSN 7500 II/7500/3500/1500

20 Clock Solution
Figure 20-36 Enhanced CES ACR clock solution
Master
Slave
SN
E1
Processing
SN
CES
CES
Processing
E1
Primary
reference
clock
PSN
E1
BTS
E1
CES
PE1
PE2
BSC
SN: Sequnce Number
Purpose
In the packet domain, enhanced CES ACR is mainly used to transparently transmit E1 clocks
in the PSN. For details, see 20.4.2.2 Enhanced CES ACR Clock Synchronization Solution.

This section describes the basic concepts associated with CES ACR.
20.4.2.1 CES ACR Clock Domain

A product supports a limited number of ACR clocks, and therefore the ACR clock domain
mechanism is introduced on the Hybrid MSTP. Specifically, one ACR clock domain represents
an ACR clock supported by the board, and each E1 port or CES service with CES ACR enabled
must belong to an ACR clock domain.
Figure 20-37 shows the application of a CES ACR clock domain. Assuming that Slave receives
eight co-sourced CES services from Master, the E1 ports corresponding to the eight CES services
all belong to ACR1. ACR1 selects one service from the eight CES services (for example, CES
service 1 corresponding to port 1), and recovers the ACR clock from the selected service. Then,
the ACR clock is used for all the E1 ports that belong to ACR1.
Issue 03 (2012-11-30)

766
OptiX OSN 7500 II/7500/3500/1500

20 Clock Solution
Figure 20-37 CES ACR clock domain
Slave
CES
ACR1
CES packet
processing
CES
Clock
recovery
E1
E1
20.4.2.2 Enhanced CES ACR Clock Synchronization Solution

The enhanced CES ACR clock synchronization solution uses sequence numbers (SNs) in CES
packets to recover service clocks. With this solution, clocks are transparently transmitted on a
PSN.
In the packet domain, enhanced CES ACR, as a clock synchronization solution, is mainly used
in the following scenarios:
l
All the clocks on the PSN are not synchronous.
All the clocks on the PSN are synchronous, but the clocks on the PSN are not synchronized
with the clock of the incoming service.
Figure 20-38 is a typical application example of the enhanced CES ACR clock synchronization
solution.
Issue 03 (2012-11-30)

767
OptiX OSN 7500 II/7500/3500/1500

20 Clock Solution
Figure 20-38 Typical application example of the enhanced CES ACR clock synchronization
solution
SN
E1
Processing
SN
CES
CES
Processing
E1
Primary
reference
clock
PSN
E1
BTS
CES
PE1
(Slave)
E1
PE2
(Master)
BSC
SN: Sequnce Number
In this example, the clock of the BSC needs to be transparently transmitted to the BTS along
with the CES service, but the clock of PE1 is not synchronous with the clock of PE2. In this
case, PE2 (Master) extracts the clock of the BSC from the E1 port, and controls the transmission
interval of CES packets according to the extracted clock. PE1 (Slave) recovers the clock of the
BSC according to the SN in the received CES packet, and transmits the recovered clock to the
BTS through the E1 port. In this manner, the clock of the BTS is synchronized with the clock
of BSC.
NOTE
l If the clock of PE1 is synchronous with the clock of PE2 but the two clocks are asynchronous with the
reference clock of the BSC, the enhanced CES ACR clock synchronization solution can also be used
to transmit the clock of the BSC.
l If the clock of PE1 is synchronous with the clock of PE2 and the two clocks are also synchronous with
the reference clock of the BSC, CES retiming is used to transmit the clock of the BSC.
20.4.2.3 Standard CES ACR Clock Synchronization Solution

The standard CES ACR clock synchronization solution uses timestamps in CES packets to
recover the system clock. With this solution, clocks of the NEs on both ends of a PSN are
synchronized.
In the packet domain, CES ACR is mainly used in the following scenario as a standard clock
synchronization solution: The clocks on a PSN are not synchronous, and NEs requiring clock
synchronization transmit CES services to each other.
Figure 20-39 is a typical application example of the standard CES ACR clock synchronization
solution.
Issue 03 (2012-11-30)

768
OptiX OSN 7500 II/7500/3500/1500

20 Clock Solution
Figure 20-39 Typical application example of the standard CES ACR clock synchronization
solution
System
clock
System
clock
Time
stamp
E1
TDM
network
E1
BTS
NE3
Processing
Time
stamp
CES CES
PSN
E1
NE4
Processing
E1
CES
PE1
(Slave)
E1
Primary
reference
clock
PE2
(Master)
BSC
TDM transmission equipment

In this example, the clock of PE2 is synchronous with the clock of the BSC, and PE2 needs to
provide a synchronization clock for PE1, as well as NE3 and NE4 on the downstream TDM
network. In this case, PE2 (Master) adds a timestamp to the CES service according to its system
clock. PE1 (Slave) recovers the ACR clock according to the timestamp in the CES service, and
uses the ACR clock as its system clock. NE3 and NE4 on the downstream TDM network trace
the clock of PE1. In this manner, clocks of the NEs are synchronized.

This section describes the standards and protocols associated with CES ACR.
The following standards and protocols are associated with CES ACR:
l
ITU-T G.8261: Timing and Synchronization aspects in Packet Networks
IETF RFC 4197: Requirements for Edge-to-Edge Emulation of Time Division Multiplexed
(TDM) Circuits over Packet Switching Networks
IETF RFC 4553: Structure-Agnostic Time Division Multiplexing (TDM) over Packet
(SAToP)
IETF RFC 5086: Structure-Aware Time Division Multiplexed (TDM) Circuit Emulation
Service over Packet Switched Network (CESoPSN)
20.4.4 Availability
The CES ACR function requires the support of the applicable equipment, boards, and software.
Version Support
Issue 03 (2012-11-30)
Applicable Version
OptiX OSN 1500/3500/7500

769
OptiX OSN 7500 II/7500/3500/1500

20 Clock Solution
Applicable Version
U2000
Applicable Version
OptiX OSN 7500 II
U2000
Hardware Support
Applicable Board
Applicable Version
TNN1CO1
OptiX OSN 7500 II
TNN1D75E
OptiX OSN 7500 II
TNN1D12E
OptiX OSN 7500 II
N1CQ1
OptiX OSN 7500/3500
N1MD12
OptiX OSN 7500/3500
N1MD75
OptiX OSN 7500/3500
R1ML1

This section describes the limitations on and precautions for CES ACR in the network design
Issue 03 (2012-11-30)
Applicable
Object

Details
Remarks
CES ACR
CES ACR is used to transparently

transmit CES E1 clocks.
CES ACR
The quality of CES ACR clocks

meets requirements only if the delay
variation of a PSN network is within
a specified range.

770
OptiX OSN 7500 II/7500/3500/1500

20 Clock Solution
Applicable
Object

Details
Remarks
CES ACR
CES E1 services for which CES

ACR is enabled can be based on
either E1 services or Fractional E1
services. CES services can be
encapsulated in SAToP or
CESoPSN mode.
CES ACR
The OptiX OSN 7500 II supports

only the enhanced CES ACR. The
OptiX OSN 7500, OptiX OSN 3500,
and OptiX OSN 1500 support only
the standard CES ACR.
CES ACR
The TNN1CO1, TNN1D75E, and

TNN1D12E must work with the
TNN1EG8.
CES ACR
The N1CQ1, N1MD12, and

N1MD75 must work with the
N1PEG8.
Master NE
Set the clock mode to Line Clock

Mode for E1 ports that transparently
transmit clocks on a Master NE.
The TNN1CO1 and N1CQ1 can

only be set as Master of the CES
ACR.
Slave NE
l Add ports that need to output

ACR clocks into a clock domain.
l A clock domain must bind the

clock of a CES service
corresponding to an E1 port
within the clock domain as the
primary clock.
l Set the clock mode to Slave
Mode for ports that output ACR
clocks.

None.
None.
Issue 03 (2012-11-30)

771
OptiX OSN 7500 II/7500/3500/1500

20 Clock Solution
20.4.6 Principles
In the enhanced timestamp solution, enhanced CES ACR uses SN carried by CES packets to
recover time information.
Implementation on Master
Figure 20-40 shows the ACR implementation process on Master.
Figure 20-40 Implementation process on Master
Master
E1 line clock
E1
CES
Encapsualting Transmitting
packets
packets
Master extracts clock frequency information from an E1 signal, and transmit a CES packet based
on the clock frequency information.
Implementation on Slave
Figure 20-41 shows the ACR implementation process on Slave.
Issue 03 (2012-11-30)

772
OptiX OSN 7500 II/7500/3500/1500

20 Clock Solution
Figure 20-41 Implementation process on Slave
Slave
ACR clock
Generating
timestamps
Recording
arrival
time
CES
Local
timestamp
SN
Receiving Decapsualting E1
packets
packets
ACR clock
computing
module
ACR
clock
E1
Buffer
1.
The clock module uses the ACR clock to count tick values at a certain frequency.
2.
The clock module records the tick value corresponding to the arrival time of each CES
packet, and outputs the tick values to the ACR clock computing module.
3.
Slave decapsulates the CES services and recovers the SNs of the CES packets. Then, Slave
outputs the SNs to the ACR clock computing module.
4.
The ACR clock computing module recovers the ACR clock based on the tick values, SNs,
and packet loading time.
The ACR clock computing principles are as follows.
l Assume that the tick value increases by 1 every 10 us and that the packet loading time
is 1000 us.
l Assume that the tick value corresponding to the arrival time of previous packet is t1,
and that the tick value corresponding to the arrival time of current packet is t2.
l If the SNs of two packets are consecutive, the packet loading time is 1000 us. Then, the
tick difference should be 100 when the ACR clock is synchronized with the E1 clock
that is extracted on Master.
l If t2 - t1 < 100, the ACR clock frequency is lower than that of the E1 clock extracted
on Master. In this case, the ACR clock computing module will increase the ACR clock
frequency. If t2 - t1 > 100, the ACR clock frequency is higher than that of the E1 clock
extracted on Master. In this case, the ACR clock computing module will decrease the
ACR clock frequency. By increasing or decreasing the ACR clock frequency, the
difference of t2 minus t1 is always 100.
5.
Issue 03 (2012-11-30)
After the CES packet on Slave is recovered to an E1 bit stream, it is written into the First
In, First Out (FIFO) queue. Then, the E1 signal is read from the FIFO queue based on the
ACR clock. As a result, the output E1 signal contains the ACR clock information (that is,
the ACR clock is synchronized with the E1 clock of Master). In this manner, the E1 clock
is transparently transmitted.
773
OptiX OSN 7500 II/7500/3500/1500

20 Clock Solution

Configurations of CES ACR at master equipment are different from those at slave equipment.
NOTE
For enhanced CES ACR, Sequence Number Mode must be set to a same value for CES services configured at
master equipment and slave equipment.
Table 20-29 provides the procedure for configuring CES ACR.

Table 20-29 Procedure for configuring CES ACR
St
ep
Operation
Description
20.4.8.1 Configuring the Primary

Clock for an ACR Clock Domain
Required.
Configure the primary clock for an ACR clock
domain. Set the major parameters as follows.
Set CES Service corresponding to ACR Clock
Source.
20.4.8.2 Configuring Ports Using

the Clock Domain
Required by a slave PE.
Setting Advanced Attributes of E1

Ports
Required.
NOTE
For details, refer to "Configuring E1
Ports" in Configuration Guide (Packet
Transport Domain).
Group the E1 ports with the same clock source and

from the same Master into one clock domain.
On Master, set Clock Mode of a port inputting E1

clocks to System Clock Mode. On Slave, set
Clock Mode of a port inputting E1 clocks to Slave
Mode.
20.4.8 Configuring CES ACR

This topic describes CES ACR configuration tasks.
20.4.8.1 Configuring the Primary Clock for an ACR Clock Domain

An ACR clock domain can use the clock extracted from a CES service as its primary clock.
Prerequisites
l
CES services are configured.
Context
NOTE
l An ACR clock domain can bind only the CES services from the E1 ports on a local board.
l A maximum of four ACR clock domains can bind CES services.
Issue 03 (2012-11-30)

774
OptiX OSN 7500 II/7500/3500/1500

20 Clock Solution
Procedure
Step 1 In the NE Explorer, select the required NE from the Object Tree.
Step 2 Choose Configuration > Clock > ACR Clock from the Function Tree.
Step 3 In CES Service, select an CES service for primary clock extraction.
Step 4 Click Apply. Then, close the dialog box that is displayed.
----End
20.4.8.2 Configuring Ports Using the Clock Domain

An CES E1 port can transmit the clock information in the system clock domain or CES ACR
clock domain.
Prerequisites
l
Context
NOTE
l E1 ports output clocks from the system clock domain by default. Therefore, it is unnecessary to set
application ports to the system clock domain if system clocks are to be used.
l An ACR clock domain can only be applied to the E1 ports on a local board.
l The E1 ports corresponding to the primary clock for an ACR clock domain must be added to the ACR
clock domain.
l The four ACR clock domains can bind the CES services either from the former 16 E1 ports or from
the latter 16 E1 ports on a local board. That is, the four ACR clock domains cannot simultaneously
bind the CES services from the former 16 E1 ports and from the latter 16 E1 ports on a local board.
Procedure
Step 1 In the NE Explorer, select the required NE from the Object Tree.
Step 2 Choose Configuration > Clock > Clock Domain from the Function Tree.
Step 3 Click New.
Step 4 Configure the parameters of the Create Clock Domain Port tab according to planning
information.
1.
In Clock Domain, select the relevant ACR clock domain.
2.
In Clock Domain Board, select the board where the ACR clock domain resides.
3.
Set the application ports to the ACR clock domain.
Issue 03 (2012-11-30)
a.
In Board, select a board that uses the ACR clock domain.
b.
In Available Port, select the ports that transmit CES services.
c.
Click
, add the ports that transmit CES services to Selected Port.

775
OptiX OSN 7500 II/7500/3500/1500

20 Clock Solution
Step 5 Click Apply. Then, close the dialog box that is displayed.
----End

This section uses an example to describe how to plan and configure CES ACR according to
network conditions.
20.4.9.1 Network Diagram

This section describes the networking information about the NEs.
As shown in Figure 20-42, CES services need to transparently transmit clocks from the BSC to
BTS1 and BTS2, but the clocks of NE1 and NE2 are not synchronous. Therefore, NE1 and NE2
need to be configured with CES ACR.
As a Slave, NE1 recovers clocks based on the SN information in the CES packets that are received
by 35-N1D12E-1 port, and transmits the clocks to 35-N1D12E-2 port. In this way, the clocks
of BTS1 and BTS2 are synchronized with the clock of the BSC.
Figure 20-42 Network diagram of CES ACR
CES Service: CES_BTS1
BTS1
CES Service: CES_BSC1

PSN
E1
E1
CES
E1
E1
NE1
(Slave)
BTS2
35-N1D12E-1 (to BTS1)

35-N1D12E-2 (to BTS2)
NE2
(Master)
BSC
35-N1D12E-1 (to BSC)

35-N1D12E-2 (to BSC)
CES Service: CES_BTS2
CES Service: CES_BSC2
20.4.9.2 Service Planning

data.
Planning Information About the Primary Clock for the ACR Clock Domain on
Slave
Table 20-30 provides the planning information about the primary clock for ACR clock domain
1 on NE 1 (Slave).
Issue 03 (2012-11-30)

776
OptiX OSN 7500 II/7500/3500/1500

20 Clock Solution
Table 20-30 Planning information about the primary clock for ACR clock domain
Attribute
Description
ACR Clock Source
15-N1EG8-ACR1
CES Service
CES_BTS1
Planning Information About the ACR Clock Domain on Slave

Table 20-31 provides the planning information about the ACR clock domain on NE1 (Slave).
Table 20-31 Planning information about the ACR clock domain
Attribute
Description
Clock Domain
CES ACR1 Clock Domain
Clock Domain Board
15-N1EG8
Board
35-N1D12E
Selected Port
35-N1D12E-1(CES_BTS1)
Planning Information About the Advanced Attributes of E1 Ports on Master and

Slave
Table 20-32 provides the planning information about the advanced attributes of E1 ports on
NE1 (Slave) and NE2(Master).
Table 20-32 Planning information about the advanced attributes of E1 ports
Attribute
Description
Clock Mode
NE1(35-N1D12E-1, 35N1D12E-2)
NE2(35-N1D12E-1)
Slave Mode
Line Clock Mode

Prerequisites
l
Issue 03 (2012-11-30)

777
OptiX OSN 7500 II/7500/3500/1500

20 Clock Solution
Procedure
Step 1 In the NE Explorer, select the required NE1 from the Object Tree.
Step 2 Configure a primary clock in the CES ACR clock domain for NE1 (Slave).
1.
Choose Configuration > Clock > ACR Clock from the Function Tree.
2.
In CES Service, select an CES service for primary clock extraction.
3.
Attribute
Description
ACR Clock Source
15-N1EG8-ACR1
CES Service
CES_BTS1
Click Apply. Then, close the dialog box that is displayed.
Step 3 On NE1 (Slave), configure the ports that use the CES ACR clock domain.
1.
Choose Configuration > Clock > Clock Domain from the Function Tree.
2.
Click New, The Create Clock Domain Port dialog box is displayed.
3.
In Clock Domain, select the relevant ACR clock domain.
4.
In Clock Domain Board, select the board where the ACR clock domain resides.
5.
Set the application ports to the ACR clock domain.

a.
In Board, select a board that uses the ACR clock domain.
b.
In Available Port, select the ports that transmit CES services.
c.
Click
, add the ports that transmit CES services to Selected Port.
Attribute
Description
Clock Domain
CES ACR1 Clock Domain
Clock Domain Board
15-N1EG8
Board
35-N1D12E
Selected Port
6.
Step 4 Configure Advanced Attributes of the ports inputting E1 clocks on NE2 (Master) and NE1
(Slave).
1.
In the NE Explorer, select the NE from the Object Tree and choose Configuration > Packet
Configuration > Interface Management > PDH Interface from the Function Tree.
2.
Click the Advanced Attributes tab.
3.
Select the required port and set the parameters for its advanced attributes.
Issue 03 (2012-11-30)

778
OptiX OSN 7500 II/7500/3500/1500

20 Clock Solution
Table 20-33 Planning information about the advanced attributes of E1 ports

Attribute
Clock Mode
4.
Description
NE1(35-N1D12E-1, 35N1D12E-2)
NE2(35-N1D12E-1)
Slave Mode
Line Clock Mode
----End

This topic describes the alarms and performance events that are related to the CES ACR feature.

This topic describes the alarms related to CES ACR.
Table 20-34 lists the alarms that are related to the CES ACR.
Table 20-34 Alarms related to CES ACR
Alarm Name
Meaning
CES_ACR_LOCK_AB
N
The CES_ACR_LOCK_ABN is an alarm indicating that the CES

ACR clock is locked abnormally. This alarm is reported when the
configured CES ACR clock is untraced or is traced but unlocked.

None.
20.4.11 Parameter Description: CES ACR

This topic describes the parameters required for configuring CES ACR.
20.4.11.1 ACR Clocks

This section describes parameters for an ACR clock.
Table 20-35 lists the parameters for an ACR clock.
Issue 03 (2012-11-30)

779
OptiX OSN 7500 II/7500/3500/1500

20 Clock Solution
Table 20-35 Parameters for an ACR clock

Field
Value
Description
ACR Clock
Source
Board ID-board nameACR clock ID
Displays the ACR clock domain.
For example, 1-N1EG8ACR1

CES Service
Displays or specifies the master CES service that

the ACR clock source uses.
Track Mode
Track, Keep, Free
This field shows the current working mode of the

clock function board on the NE.
l Track: It is the normal working mode and
indicates that the clock is synchronized with
the input reference clock source under the
actual service conditions.
l Keep: Indicates that the clock works with the
stored frequency information as the timing
reference after all the timing references are
lost.
l Free: Indicates that the clock works through
the internal oscillator.
Lock Status
Lock, Unlock
Display the lock status of the clock.
20.4.11.2 Clock Domain

This section describes the parameters for a clock domain.
Table 20-36 lists the parameters for an ACR clock.
Table 20-36 Parameter for a clock domain
Field
Value
Description
Clock
Domain
System Clock Domain,

CES ACR1 Clock
Domain, CES ACR2
Clock Domain
Displays the clock domain.
Clock
Domain
Board
Slot ID-board name

For example, 2-N1EG8
Displays the board where the clock domain is

located.
Clock Port

name
Displays the ports that are bound to a clock

domain.
For example, 28N1D75E-1
Issue 03 (2012-11-30)

780
OptiX OSN 7500 II/7500/3500/1500

20 Clock Solution
20.4.11.3 Creating a Clock Domain

This section describes the parameters for creating a clock domain.
Table 20-37 lists the parameters for creating a clock domain.
Table 20-37 Parameter for creating a clock domain
Field
Value
Description
Clock
Domain
System Clock Domain,

CES ACR1 Clock
Domain, CES ACR2
Clock Domain
Specifies the clock domain to be bound.

information.
Default: System Clock

Domain
Clock
Domain
Board
Slot ID-board name
Board
Slot ID-board name
Specifies the board where the port is located.
For example, 28-N1D75E

information.

name
Displays the ports that are not bound to a clock

domain.
Available
Port
For example, 2-N1EG8
Specifies the board where the clock domain is

located.
information.

Selected Port

name
Displays the ports that are bound to a clock

domain.
Issue 03 (2012-11-30)

781
OptiX OSN 7500 II/7500/3500/1500

21 Outband DCN
21
Outband DCN
About This Chapter

This chapter describes the outband DCN feature.
21.1 Introduction to the DCN
A data communication network (DCN) provides communication channels for the NEs that are
managed in a centralized manner to manage and maintain the NEs remotely. From a broad sense,
a network for data communication can be called a DCN. In this document, the DCN refers to a
data communication network especially for network management in the transmission domain.
21.2 HWECC Solution
The HWECC protocol stack is developed by Huawei based on the DCC or extended channels
for the communication between NEs.
21.3 IP over DCC Solution
The NEs use unified DCCs to transmit the data of the TCP/IP protocol by using the IP over DCC
solution. In this way, the U2000 can manage NEs. The IP over DCC solution applies to a network
that is comprised of the OptiX transmission equipment and the third-party equipment that
supports the IP over DCC function. This solution can also be applied to a network that is
comprised of only the OptiX transmission equipment.
21.4 OSI over DCC Solution
The NEs use unified DCCs to transmit the data of the OSI protocol by using the OSI over DCC
solution. In this way, the U2000 can manage NEs. The OSI over DCC solution applies to a
network that is comprised of the OptiX equipment and the third-party equipment that supports
the OSI over DCC function.
21.5 Hybrid Networking Solution of DCC Transparent Transmission
When interworking with the third-party equipment, the OptiX equipment can transparently
transmit the OAM information of the third-party equipment through the DCC physical channel
so that the third-party equipment can traverse the Huawei DCN to communicate with the NMS
of the third party; the OAM information of the OptiX equipment can also be transparently
transmitted by the DCC physical channel of the third-party equipment so that the OptiX
equipment can communicate with the U2000.
21.6 Transparent Transmission of DCC Bytes Through the External Clock Interface
Transparent transmission of DCC bytes through the external clock interface refers to a solution
in which the external clock interface is used to embed the DCC bytes to a specified E1 service
Issue 03 (2012-11-30)

782
OptiX OSN 7500 II/7500/3500/1500

21 Outband DCN
that traverses a third-party network. When this solution is used, the transmission bandwidth of
one E1 service is occupied. The solution can be used if management messages need to traverse
third-party equipment but none of OSI over DCC, IP over DCC, and DCC transparent
transmission is supported.
21.7 DCN Maintenance
This chapter describes the troubleshooting, maintenance cases, and relevant alarms and
performance events of the DCN.
Issue 03 (2012-11-30)

783
OptiX OSN 7500 II/7500/3500/1500

21 Outband DCN
21.1 Introduction to the DCN

A data communication network (DCN) provides communication channels for the NEs that are
managed in a centralized manner to manage and maintain the NEs remotely. From a broad sense,
a network for data communication can be called a DCN. In this document, the DCN refers to a
data communication network especially for network management in the transmission domain.
21.1.1 DCN Composition

DCNs are classified into internal DCNs and external DCNs.
Both the U2000 and NEs are nodes of a DCN. The DCN between the U2000 and NEs is called
the external DCN, and the DCN between NEs is called the internal DCN, as shown in Figure
21-1.
Figure 21-1 DCN composition
NMS
External DCN
Internal DCN
Router
LAN switch
OptiX optical transmission equipment
External DCN
On an actual network, the U2000 and NEs may be located on different floors of a building,
or in different buildings, or even in different cities. Hence, an external DCN that is
Issue 03 (2012-11-30)

784
OptiX OSN 7500 II/7500/3500/1500

21 Outband DCN
comprised of the data communication equipment, such as LAN switches and routers, is
required to connect the U2000 and the NEs. As the external DCN involves knowledge of
data communication, no detailed description is provided in this document. The DCN
mentioned in this document refers to the internal DCN, unless otherwise specified.
l
Internal DCN
On an internal DCN, the equipment uses the DCC bytes in overheads as physical channels
of the DCN.
21.1.2 Huawei DCN Solution

For various networking modes of the transmission equipment, the OptiX transmission equipment
of Huawei provides multiple DCN solutions.
HWECC Solution
When the networking is comprised of only the OptiX transmission equipment, the HWECC
solution is preferred.
In this solution, NEs transmit the data that supports the HWECC protocol through DCCs. The
solution features easy configuration and convenient application. As the HWECC protocol is a
proprietary protocol, the management problems cannot be solved when the networking is
comprised of both the OptiX equipment and the third-party equipment.
For details on the HWECC solution, see HWECC Solution.
IP over DCC Solution

When the networking is comprised of both the OptiX transmission equipment and the third-party
equipment that supports the IP over DCC function, the IP over DCC solution is preferred. The
IP over DCC solution can also be applied when the networking is comprised of only the OptiX
transmission equipment.
In the IP over DCC solution, NEs transmit the data that supports the TCP/IP protocol through
DCCs. As the TCP/IP protocol is a standard protocol, the management problems are solved when
the networking is comprised of both the OptiX equipment and the third-party equipment. The
configuration of the IP over DCC solution is more complicated than that of the HWECC solution.
For details on the IP over DCC solution, see IP over DCC Solution.
OSI over DCC Solution

When the networking is comprised of both the OptiX transmission equipment and the third-party
equipment that supports the OSI over DCC function, the OSI over DCC solution is preferred.
In the OSI over DCC solution, NEs transmit the data that supports the OSI protocol through
DCCs. As the OSI protocol is a standard protocol, the management problems are solved when
the networking is comprised of both the OptiX equipment and the third-party equipment. The
configuration of the OSI over DCC solution, however, is more complicated than the
configurations of the HWECC solution and the IP over DCC solution.
For details on the OSI over DCC solution, see OSI over DCC Solution.
Issue 03 (2012-11-30)

785
OptiX OSN 7500 II/7500/3500/1500

21 Outband DCN
DCC Transparent Transmission Solution

When the networking is comprised of the OptiX transmission equipment and the third-party
equipment that does not support the IP over DCC function or the OSI over DCC function, this
solution is adopted.
In the solution, vendors use different DCCs to transmit data. Therefore, the management
problems are solved when the networking is comprised of both the OptiX equipment and the
third-party equipment. As the NMS of a vendor can manage only the NEs of the vendor, there
is a great limitation.
For details on the DCC transparent transmission solution, see Hybrid Networking Solution of
DCC Transparent Transmission.
DCC Transparent Transmission Through the External Clock Interface Solution

When PDH transmission or a network that does not support transparent transmission of DCC
bytes exists on the transmission path of NM messages, use the DCC transparent transmission
through the external clock interface solution.
In this solution, DCC bytes are loaded into the timeslots of the E1 service that are provided by
the external clock interface, and the third-party equipment transmits the E1 service as a common
E1 service. When this solution is used, the transmission bandwidth of one E1 service is occupied.
For details on the DCC transparent transmission through the external clock interface solution,
see Transparent Transmission of DCC Bytes Through the External Clock Interface.
21.2 HWECC Solution

The HWECC protocol stack is developed by Huawei based on the DCC or extended channels
for the communication between NEs.
21.2.1 Solution Overview

This topic describes the basic concepts and networking of the HWECC solution.
21.2.1.1 Basic Concepts

The HWECC protocol stack is a proprietary protocol stack of Huawei. It is the most applicable
and advanced ECC communication solution for Huawei transmission equipment. The HWECC
protocol stack identifies NEs by IDs and creates routes automatically, which is easy to use.
HWECC Protocol
ITU-T G.784 defines the architecture of the ECC protocol stack based on the OSI seven-layer
reference model. The HWECC protocol stack is based on the ECC protocol stack.
The HWECC protocol consists of four layers: physical layer (DCC), media access layer, network
layer, and transmission layer. See Figure 21-2.
Issue 03 (2012-11-30)

786
OptiX OSN 7500 II/7500/3500/1500

21 Outband DCN
Figure 21-2 Architecture of the HWECC protocol stack

Application layer
Presentation layer
Session layer
Transport layer
Transport layer
Network layer
Network layer
Media access
layer
Data link layer
Physical layer
Physical layer
HW ECC
protocol stack
OSI model
Physical layer
The main function of the physical layer is to control physical channels. The physical layer
performs the following functions:
Receives and sends data over the physical channels, including receiving data from
physical channels and transferring the data to the upper layer.
Receives the data frames transferred from the upper layer and sends them to physical
channels.
The channels at the physical layer include DCC channels and extended ECC channels. The
physical layer can process the data frame with a maximum of 1024 bytes.
Media access layer

The media access layer is also called the medium access control (MAC) layer. The main
function of the MAC layer is to activate or close physical DCCs between the physical layer
and the network layer. The MAC layer shields the diversity of the physical networks and
provides the uniform service upwards (point-to-point physical channel). The MAC layer
Establishes and maintains the MAC connection between adjacent NEs.
When there is a reachable physical channel between two adjacent NEs, the MAC layer
establishes a MAC connection between the NEs. Each MAC connection includes the
address of the opposite NE, the ID of the physical channel, the connection timer, and
other information.
Provides the data communication service.
The MAC layer receives the data frame transferred from the physical layer. If the
destination address is the local station, the MAC layer transfers the data frame to the
network layer. Otherwise, the MAC layer discards the data frame.
The MAC layer sends the data frame from the network layer. If the destination address
of the data frame has a MAC connection, the MAC layer sends the data frame to the
Issue 03 (2012-11-30)

787
OptiX OSN 7500 II/7500/3500/1500

21 Outband DCN
corresponding physical channel in the physical layer through the MAC connection.
Otherwise, the MAC layer discards the data frame.
l
Network layer
The main function of the network layer is to provide the route addressing for data frames
and the route management for the DCC communication network. The network layer
Establishes and maintains ECC routes.
Each route item includes the following information: address of the destination NE,
address of the transfer NE, transfer distance (the number of passed transfer NEs), route
priority (The priority value ranges from 1 to 7. The priority of an automatically
established route is 4 by default. The system always selects the route with the highest
priority.), and mode (0 represents the automatic route and 1 represents the manual route).
Provides the data communication service.
The network layer receives the packet transferred from the MAC layer. If the destination
address of the packet is the local station, the network layer transfers the packet to the
transport layer. Otherwise, the network layer requests the MAC layer to transfer the
packet to the transfer station according to the route item that matches the destination
address in the network layer routing table.
The network layer sends the packet from the transport layer. The network layer requests
the MAC layer to transfer the packet to the transfer station according to the route item
that matches the destination address of the packet in the network layer routing table.
Transport layer
The main function of the transport layer (L4 layer) is to provide the end-to-end
communication service for the upper layer. As the communication between the OptiX
equipment and the U2000 is controlled by the end-to-end connection-oriented service in
the application layer, the L4 layer provides only the end-to-end connectionless
communication service, that is, transparent data transfer service.
NOTE
In the HWECC protocol stack, the NE address used by each layer is the ID of the NE. The NE ID has 24
bits. The highest eight bits represent the subnet ID (or the extended ID) and the lowest 16 bits represent
the basic ID. For example, if the ID of an NE is 0x090001, the subnet ID of the NE is 9 and the basic ID
is 1.
Extended HWECC
The physical layer of the ECC is DCC, whose data is transmitted based on the fiber. In certain
cases, the network or NE may be independent and there is no DCC channel to the gateway NE
(no fiber connection). The extended ECC refers to the ECC protocol stack that is loaded on the
TCP/IP protocol stack. That is, the HWECC protocol stack is carried through the extended
channel (such as Ethernet) instead of the DCC channel to meet the requirements of special
scenarios. The difference between the extended ECC and the ECC is that the physical layer of
the ECC is the DCC channel and that of the extended ECC is an extended channel (such as
Ethernet channel). Figure 21-3 shows the networking environment with the extended ECC.
Issue 03 (2012-11-30)

788
OptiX OSN 7500 II/7500/3500/1500

21 Outband DCN
Figure 21-3 Networking environment with the extended ECC
NMS
Network cable
HUB1
GNE1
NE6
NE2
NE5
NE3
HUB2
NE4
NE12
NE7
NE8
NE9
NE11
NE10
Fiber
Subnet 1
Subnet 2
Supporting Capability
HWECC uses the D1-D3 bytes as the physical transmission path. The D4-D12 or D1-D12 bytes
can also be used.
NOTE
HWECC supports the communication by using fibers or Ethernet cables. When no optical path is available
between nodes, set the extended ECC by using Ethernet cables.
21.2.1.2 Networking
The HWECC protocol supports various networking modes. NEs can be connected through
optical interfaces or Ethernet ports for ECC communication. In certain situations, the HWECC
protocol supports transparent transmission of the OAM information from the third-party
equipment.
The HWECC protocol has the following typical applications depending on the networking.
Networking That Involves Only Huawei Equipment

Figure 21-4 shows the networking that involves only Huawei equipment.
Issue 03 (2012-11-30)

789
OptiX OSN 7500 II/7500/3500/1500

21 Outband DCN
Figure 21-4 Networking that involves only Huawei equipment
NMS
HUB1
Network cable
GNE1
NE6
NE2
NE5
NE3
NE12
NE7
HUB2
NE8
NE9
NE4
NE11
NE10
Fiber
Subnet 2
Subnet 1
When the network management information is transmitted between Huawei optical network
equipment, there must be a gateway NE that communicates with the U2000. The U2000 is
connected to the gateway NE through Ethernet. Hence, you can test, manage and maintain the
entire network. The U2000 improves the quality of services (QoS) on the network and lowers
the expenditure for maintenance. This ensures the rational use of network resources. Nongateway NEs are connected to the gateway NE through the ECC. This realizes the information
transmission between the U2000 and the non-gateway NEs. In addition, the extended ECC
communication between NEs can be performed through network interfaces, such as NE6 and
NE7.
Networking That Involves Huawei Equipment and Third-Party Equipment

Figure 21-5 shows the networking that involves Huawei equipment and third-party equipment.
Figure 21-5 Networking that involves Huawei equipment and third-party equipment
Third-party NM
HUB
NE
Third-party
equipment
NE
NE
NE
NE
NE
Huawei
equipment
NE
NE
NE
NE
For such networking, the OAM information of the third-party equipment should travel through
Huawei equipment, which provides the function to transparently transmit the DCC. During the
Issue 03 (2012-11-30)

790
OptiX OSN 7500 II/7500/3500/1500

21 Outband DCN
transmission, Huawei equipment does not analyze the data. To realize the DCC transparent
transmission, perform the corresponding configuration at each NE along the data transmitting
trail.
21.2.2 Availability
The HWECC solution requires the support of the applicable equipment, boards, and software.
Version Support
Applicable Version
OptiX OSN 1500/2500/3500/7500
V100R003 and later
T2000
V200R002 and later
U2000
Applicable Version
OptiX OSN 3500 II
V100R009 and later
T2000
U2000
Applicable Version
OptiX OSN 7500 II
U2000
Hardware Support
Issue 03 (2012-11-30)
Applicable Board
Applicable Version
N4GSCC
OptiX OSN 3500/7500
N6GSCC
OptiX OSN 3500/7500
N1PSXCS
OptiX OSN 3500
N2PSXCSA
OptiX OSN 3500
T1PSXCSA
OptiX OSN 7500
R1PCXLN
TNN1PSXCS
OptiX OSN 7500 II

791
OptiX OSN 7500 II/7500/3500/1500

21 Outband DCN
Applicable Board
Applicable Version
TNN1SCA
OptiX OSN 7500 II
N1SXCSA
OptiX OSN 3500
N3PSXCSA
OptiX OSN 3500
21.2.3 Relation with Other Features

It is recommended that you adopt only one of the following solutions to build a DCN: HWECC
solution, IP over DCC solution, or OSI over DCC solution.
If you combine the HWECC solution with other solutions to build a network, note the following
points:
l
The HWECC protocol stack of NEs can communicate with the IP protocol stack.
The HWECC protocol stack of NEs can communicate with the OSI protocol stack in the
same area of the Layer 1.
It is recommended that you adopt the HWECC protocol to manage the OptiX equipment
if DCC bytes are used to transparently transmit NM messages when the OptiX equipment
is interworked with the third-party equipment.
21.2.4 Principles
The HWECC solution is implemented by establishing ECC routes and transferring messages.
In addition, the ECC protocol stack can also flow over extended ECC channels to meet the special
requirements in certain scenarios.
21.2.4.1 Establishing ECC Routes

The HWECC solution adopts the shortest path first algorithm to establish ECC routes.
In this context, the shortest path refers to the path with minimum number of stations. The
following describes how an NE establishes ECC routes:
1.
The physical layer of an NE maintains the status information of the DCC to which each
line port corresponds.
2.
The MAC layer of the NE establishes the MAC connection between the NE and the adjacent
NE.
The steps are as follows:
3.
a.
The NE broadcasts the connection request frame (MAC_REQ) to the adjacent NE in

a periodical manner.
b.
After receiving the MAC_REQ, the adjacent NE returns the connection response
frame (MAC_RSP).
c.
If the MAC_RSP is received within the specified time, the NE establishes a MAC
connection between the NE and the adjacent NE.
The network layer of the NE establishes the network layer routing table.
The steps are as follows:
Issue 03 (2012-11-30)

792
OptiX OSN 7500 II/7500/3500/1500

21 Outband DCN
a.
According to the status of the MAC connection, the NE establishes an initial network
layer routing table.
b.
The NE broadcasts its routing table to the adjacent NE in a periodical manner through
the routing response message.
c.
The adjacent NE updates its network layer routing table according to the received
routing response message and the shortest path first algorithm.
d.
At the next route broadcasting time, the NE broadcasts its current network layer
routing table to the adjacent NE.
Figure 21-6 Networking example for establishing ECC routes

NE1
NE2
NE5
NE3
NE4
The following describes how to establish ECC routes between NEs. The network shown in
Figure 21-6 is provided as an example.
1.
The physical layer of each NE maintains the status information of the DCC to which each
line port corresponds. The physical layer of each NE detects that there are two available
DCCs.
2.
The MAC layer of the NE establishes the MAC connection between the NE and the adjacent
NE.
NE1 is considered as an example to describe how to establish the MAC connection.
3.
a.
NE1 broadcasts the frame MAC_REQ to NE2 and NE5 in a periodical manner through
its two available DCCs. The frame MAC_REQ contains the ID of NE1.
b.
After receiving the frame MAC_REQ, NE2 and NE5 return their respective
MAC_RSP frames. The frame MAC_RSP from NE2 contains the ID of NE2 and the
frame MAC_RSP from NE5 contains the ID of NE5.
c.
After receiving the MAC_RSP frames, NE1 establishes a MAC connection between
NE1 and NE2 and a MAC connection between NE1 and NE5 according to the NE ID,
DCC that reports the frame, and other information.
The network layer of the NE establishes the network layer routing table.
NE1 is considered as an example to describe how to establish the network layer routing
table.
Issue 03 (2012-11-30)
a.
According to the status of the MAC connection, NE1 establishes an initial network
layer routing table. In the routing table, there are two routes, one to NE2 and one to
NE5.
b.
NE1 broadcasts its routing table to adjacent NEs in a periodical manner through the
routing response message.
793
OptiX OSN 7500 II/7500/3500/1500

21 Outband DCN
c.
After receiving the routing response message from NE1, NE2 and NE5 update their
respective network layer routing tables. After the update, there is a route to NE5 in
the network layer routing table of NE2, and the transfer NE is NE1. There is a route
to NE2 in the network layer routing table of NE5, and the transfer NE is also NE1.
d.
Similarly, NE1 also adds the routes to NE3 and NE4 in its NET layer routing table
according to the routing response messages from NE2 and NE5. There are two routes
between NE1 and NE3. The distance of the route whose transfer NE is NE2 is 1 and
the distance of the route whose transfer NE is NE5 is 2. Hence, according to the shortest
path first principle, only the route whose transfer NE is NE2 is retained in the network
layer routing table. The routes to NE4 are processed in the same way as those to NE3.
e.
If the DCC between NE1 and NE2 becomes faulty, the MAC connection between NE1
and NE2 fails. In this case, NE1 updates the routes to NE2 and NE3 in its network
layer routing table according to the routing response message from NE5. Hence, the
routes to NE2 and NE3 are re-established. In this way, the ECC route is protected.
21.2.4.2 Transferring Messages

In the HWECC solution, the messages between NEs are transferred at the network layer of the
NEs.
Figure 21-7 illustrates how the HWECC solution transfers the messages originated from the
U2000 to a destination NE.
The implementation principle is as follows:
1.
The U2000 transfers application layer messages to the gateway NE through the TCP
connection between them.
2.
The gateway NE extracts the messages from the TCP/IP protocol stack and reports the
messages to the application layer.
3.
The application layer of the gateway NE queries the address of the destination NE in the
messages. If the address of the destination NE is not the same as the address of the local
station, the gateway NE queries the core routing table of the network layer according to the
address of the destination NE to obtain the corresponding route and the communication
protocol stack of the transfer NE. As the communication protocol stack of the transfer NE
in Figure 21-7 is HWECC, the gateway NE transfers the messages to the transfer NE
through the HWECC stack.
4.
After receiving the packet that encapsulates the messages, the network layer of the transfer
NE queries the address of the destination NE of the packet. If the address of the destination
NE is not the same as the address of the local station, the transfer NE queries the network
layer routing table according to the address of the destination NE to obtain the
corresponding route and then transfers the packet.
5.
After receiving the packet, the network layer of the destination NE reports the packet to
the application layer through the Layer 4 because the address of the destination NE of the
packet is the same as the address of the local station. The application layer functions
according to the message sent from the U2000.
Issue 03 (2012-11-30)

794
OptiX OSN 7500 II/7500/3500/1500

21 Outband DCN
Figure 21-7 Implementation principle of message transferring (HWECC)

Application
Application
Application
TCP
TCP
L4
IP
IP
NET
NET
NET
MAC
MAC
MAC
Ethernet
Ethernet
DCC
DCC
DCC
Transfer NE
Destination NE
NMS
L4
Gateway NE
NOTE
The core routing table synthesizes the transport layer routing tables of all communication protocol stacks.
Each route item includes the following information:
l
ID of the destination NE
Address of the transfer NE
Communication protocol stack of the transfer NE
Transfer distance
21.2.4.3 Extended ECC

The extended ECC refers to the ECC protocol stack that is loaded on the TCP/IP protocol stack.
That is, the HWECC protocol stack is carried through the extended channel (such as Ethernet)
instead of the DCC channel to meet the requirements of special scenarios.
The difference between the extended ECC and the ECC is that the physical layer of the ECC is
the DCC channel and that of the extended ECC is an extended channel (such as Ethernet channel).
As shown in Figure 21-8, subnet 1 and subnet 2 are independent networks that are connected
with a HUB instead of a fiber. The NEs of subnet 2 are managed by the gateway NE of subnet
1.
Figure 21-8 Networking that involves only Huawei equipment
NMS
Network cable
HUB1
GNE1
NE6
NE2
NE5
NE3
NE4
HUB2
NE12
NE7
NE8
NE9
NE11
NE10
Fiber
Subnet 1
Issue 03 (2012-11-30)

Subnet 2
795
OptiX OSN 7500 II/7500/3500/1500

21 Outband DCN
The extended ECC establishes the MAC connection of adjacent NEs through the TCP
connection. The ECC can be extended in the automatic mode or the manual mode.
The implementation principle of the automatic ECC extension is as follows:
1.
Each NE obtains the IP addresses of other NEs that are on the same Ethernet through the
address resolution protocol (ARP).
2.
The NE with the largest IP address automatically functions as the server and detects the
TCP requests from the clients.
3.
Other NEs automatically function as clients and send TCP connection requests to the server.
4.
After receiving the TCP connection request from a client, the server establishes the
corresponding TCP connection.
5.
The NEs use the TCP connection as a MAC connection to realize ECC communication.
The implementation principle of the manual ECC extension is basically the same as that of the
automatic ECC extension. The difference is that in the manual mode, the server, clients, and
connection port numbers are manually specified.
21.2.5 Planning Guide

When using the HWECC solution, plan the parameters of an ECC network according to the
situation of the network.
21.2.5.1 Planning Guidelines

This topic provides guidelines on how to plan the HWECC solution.
When planning the DCN, comply with the following principles:
l
When the equipment interworks with other Huawei optical network equipment, the
HWECC or IP over DCC protocol is recommended. The entire DCN network must use the
same communication protocol.
When the equipment interworks with the third-party equipment, select the protocol that is
supported by the third-party equipment, that is, the IP over DCC protocol or the OSI over
DCC.
When the equipment interworks with the third-party equipment, select the DCC bytes to
transparently transmit services if the third-party equipment does not support the IP over
DCC protocol or the OSI over DCC protocol.
Regardless of the communication protocol you select to build the DCN network, properly
set the DCN network scale and divide the network according to the network condition to
ease impact of the large network scale.
The DCN network should be configured as a ring to ensure the reliability of the network
communication. Therefore, the routes can be protected when a fiber is cut or any anomaly
occurs on the NE. If fibers of the equipment do not form a ring, extra DCN channels should
be established to realize a ring network and to protect routes.
The management information from the U2000 to ordinary NEs must be forwarded by the
gateway NE. When creating an NE on the U2000, you need to specify the gateway NE first. In
the network-wide planning, select the gateway NE based on the actual networking and the
communication protocol.
Issue 03 (2012-11-30)

796
OptiX OSN 7500 II/7500/3500/1500

21 Outband DCN
When planning the gateway NEs, comply with the following principles:
l
Correctly set the IP address and subnet mask for the gateway NE.
Only the NE connected to the U2000 through the network cable can be configured as a
gateway NE.
There should not be too many gateway NEs on a network. Otherwise, the network
performance may be affected. It is recommended that the number of gateway NEs managed
by an NMS does not exceed 100. If the number exceeds 100, use extended ECC to combine
the gateway NEs.
Each gateway NE can manage no more than 100 NEs, and it is recommended that the
maximum number should be 50.
Usually, multiple independent NEs in a network topology (for example, the NEs in a ring
network) should be connected to the same gateway NE.
In the actual networking, the gateway NE has the largest traffic volume. To ensure stable
communication, select the equipment with strong ECC processing capability as the gateway
NE. The gateway NE and other NEs should form a star network, to reduce the traffic volume
of other NEs.
To ensure the reliability of the connection between the network and the U2000, select an
NE as the secondary gateway NE by using the same standard for selecting an NE as the
primary gateway NE. In addition, the secondary gateway NE can also manage certain NEs.
In this way, the two gateway NEs back up each other to enhance the network stability.
When planning NE IDs, comply with the following principles:

l
An NE ID must be unique on the DCN network.
An NE ID is a 24-bit binary digit, and is divided into high order 8 bits and low order 16
bits. The high order 8 bits represent the extended ID (default to 9). It is also called subnet
number, because it identifies a subnet. The value of a subnet number cannot be 0 or
0xFF. The low order 16 bits represent the basic ID. The value cannot be 0 or greater than
or equal to 0xBFEF.
On a ring network, the IDs of NEs should be incremented by one along the direction of the
primary ring.
On a ring network, it is recommended to configure the IDs of all the NEs at a station, and
then configure the IDs of all the NEs at the next station.
In the case of a complex network, divide the network into rings and chains. Set the IDs of
the NEs on the ring to numbers from 1 to N, and the IDs of the NEs on the chain to numbers
starting from N+1.
When planning IP addresses, comply with the following principles:

l
An IP address is used in the communication between a gateway NE and the U2000. Hence,
a gateway NE requires an IP address. In addition, the NE that requires the extended ECC
function should be provided with an IP address.
The NE IP address does not need to be manually set and varies with NE IDs. The format
of an IP address is 129.E.A.B. The second number E is the extended ID of the NE, which
does not vary with the NE IDs. The default value is 9. The third number A and fourth number
B are the high order 8 bits and low order 8 bits of an NE ID. When the NE IP address is
manually set, the mapping between the IP address and NE ID does not exist.
By default, the subnet IP address is 129.9.0.0 and subnet mask is 255.255.0.0.
When planning HWECC, comply with the following principles:

Issue 03 (2012-11-30)

797
OptiX OSN 7500 II/7500/3500/1500

21 Outband DCN
If the OptiX OSN 3500 or another type of OptiX equipment series is used as the gateway
NE of a network, the number of NEs on each HWECC subnet should not exceed 200, and
it is recommended that the maximum number should be 100.
Configure the HWECC subnet as a ring to ensure that routes can be protected when a fiber
is cut or any anomaly occurs on the NE.
Do not enable the ECC communication between different HWECC subnets.

Do not use network cables or fibers to establish the direct physical connection between
any NEs in two HWECC subnets.
Use the U2000 to disable the ECC communication between NEs in different HWECC
subnets.
The OptiX equipment allocates ECC channels to the interfaces on each board automatically.
Disable unnecessary ECC channels considering that the number of ECC channels on the
equipment is limited.
NOTE
Before allocating ECC channels, see Outband DCN to query the DCC resource allocation mode. To
query the actual situation of ECC channels, see Querying and Allocating DCC Resources.
The number of NEs managed by a gateway NE is limited. Therefore, multiple gateway NEs
are required when the number of NEs is large.
In the application where the extended ECC communication is required, the manually
extended ECC is recommended. Do not use the automatically extended ECC, so that the
bandwidth between NEs using extended ECC for communication is saved.
When the number of Huawei devices that use the extended ECC communication exceeds
four, the manually extended ECC communication must be used.
When configuring the manually extended ECC, configure one or more NEs as the server
and other NEs as the client. One server NE can have a maximum of seven client NEs. If
the number of client NEs managed by a server NE exceeds eight, select a client NE as the
server NE for the remaining client NEs. In this case, the client NE functions as a client and
a server at the same time. The rest may be deduced by analogy. The port numbers of the
server NEs must be different.
21.2.5.2 Planning Example

This topic uses an example to describe how to plan the HWECC solution.
Issue 03 (2012-11-30)

798
OptiX OSN 7500 II/7500/3500/1500

21 Outband DCN
Figure 21-9 Networking example for the HWECC solution
NE203
NE204
NE202
NE201
NE103
NE101
NE102
NMS
NE104
NE106
OptiX optical transmission equipment

Quidway 2501
Hub
Fiber
Network cable
2 Mbit/s channel
Figure 21-9 shows a transmission network that is comprised of only the OptiX equipment. To
plan the HWECC, do as follows:
1.
More than 80 sets of optical transmission equipment are present on the network. Thus,
divide this ECC network into two ECC subnets according to the equipment type.
2.
Select NE101 and NE201, which are located in the middle of the optical transmission
service, as gateway NEs.
3.
As shown in this figure, the U2000 and NE101 are located at the same place, and NE201
is located at another place. In this case, set up an external DCN connecting the U2000 and
NE201 by using a router Quidway 2501.
Issue 03 (2012-11-30)

799
OptiX OSN 7500 II/7500/3500/1500

4.
21 Outband DCN
Allocate IDs and IP addresses for all the NEs according to the situation of the network, as
shown in Figure 21-10.
Figure 21-10 Allocation of IDs/IP addresses for all NEs

9-203
129.9.0.203
0.0.0.0
9-204
129.9.0.204
0.0.0.0
11.0.0.1/16
9-201
11.0.0.201
11.0.0.1
9-202
129.9.0.202
0.0.0.0
9-103
129.9.0.103
0.0.0.0
10.0.0.1/16
9-101
10.0.0.101
0.0.0.0
10.0.0.100/16
9-104
129.9.0.104
0.0.0.0
9-106
129.9.0.106
0.0.0.0
9-102
129.9.0.102
0.0.0.0
Extended ID-Basic ID
IP address
Gateway
21.2.6 Configuring HWECC

Plan the DCC resource properly according to the configuration principle of the HWECC and
configure the HWECC by following the specified process to ensure the effective supervision of
the U2000 on the NEs.

After NEs are created on the NMS, configure the HWECC solution according to the
configuration process.
Figure 21-11 shows the configuration process of the HWECC solution.
Issue 03 (2012-11-30)

800
OptiX OSN 7500 II/7500/3500/1500

21 Outband DCN
Figure 21-11 Configuration process of the HWECC solution

Start
1
Configure IDs and IP
addresses for NEs
2
Configure DCCs for
NEs
Extended ECC
required?
Yes
Configure extended
ECCs
Dividing the
network into
ECC subnets
required?
4
No
No
Yes
Divide the network
into ECC subnets
Configuring
No
DCC transparent
transmission
required?
Yes
Configure DCC
transparent transmission
6
Query ECC routes

on the gateway NE
End
Issue 03 (2012-11-30)

801
OptiX OSN 7500 II/7500/3500/1500

21 Outband DCN
Table 21-1 Description of the configuration process of the HWECC solution

Remarks
Description
Configure the network-wide data, including NE IDs and the NE IP

addresses. In certain cases, you need to set the subnet masks and default
gateways as required by the external DCN.
l The NE ID and IP address are set when an NE is created. For the
configuration process, see the Configuration Guide.
l To change the ID of an NE, see Changing the ID of an NE.
l To change the IP address of an NE, see Setting Communication
Parameters of an NE.
l Set Channel Type to D1-D3 for the SDH port.

l Set Protocol Type to HWECC for the line port.
l When the ECC network is divided, set the enabling status of the DCC
between ECC subnets to Disabled.
l For details on the configuration process, see Configuring DCCs.
l Set ECC Extended Mode to Specified mode.

l Set Port for the NE that functions as the server.
l Set Opposite IP and Port for the NE that functions as the client. The
value of Opposite IP is the same as the IP address of the server, and
the value of Port is the same as the value set for the server.
l For details on the configuration process, see Configuring the
Extended ECC.
l Divide a network into multiple ECC subnets if the number of NEs

on the network exceeds 50.
l Divide the network into multiple ECC subnets by setting the DCC
status of the optical interface that is on the boundary NE of one subnet
and is directly connected to the equipment on another subnet to
Disabled.
l For details on the configuration process, see Dividing a Network into
Multiple ECC Subnets.
l Select the overhead bytes to be transparently transmitted as required.

l For details on the configuration process, see Configuring DCC
Transparent Transmission.
l Ensure that the gateway NE has an ECC route to each of its managed
non-gateway NEs.
l Ensure that the gateway NE has no ECC routes to NEs on the other
ECC subnets.
l Ensure that the ECC route uses the shortest path.
l For details on how to query ECCs, see Querying the ECC Routes of
an NE.
Issue 03 (2012-11-30)

802
OptiX OSN 7500 II/7500/3500/1500

21 Outband DCN
21.2.6.2 Changing the ID of an NE

You can use the U2000 to adjust the original planning and change the ID of an NE.
Prerequisites
l
The user must log in to the NE.
Procedure
Step 1 Select an NE in the NE Explorer. Choose Configuration > NE Attribute from the Function
Tree.
Step 2 Click Modify NE ID. The Modify NE ID dialog box is displayed.
Step 3 Enter New ID and New Extended ID. Click OK.

Step 4 Then click OK in the displayed dialog box.
NOTE
l After the operation, the communication between the U2000 and the NE is interrupted.
l After you change the ID of the NE, the original configuration information may be lost and thus the
protection and other features fail to work normally.
----End
Follow-up Procedure
After you change the ID of the NE, a warm reset is performed on the SCC board. In this case,
you need to log in to the NE again after a certain period.
21.2.6.3 Setting Communication Parameters of an NE

The communication parameters of an NE include the IP address of the NE, extended ID, gateway
IP, subnet mask, and NSAP address. You can use the U2000 to set the communication
parameters.
Prerequisites
l
Issue 03 (2012-11-30)

803
OptiX OSN 7500 II/7500/3500/1500

21 Outband DCN
Procedure
Step 1 Select an NE from the Object Tree in the NE Explorer. Choose Communication >
Communication Parameters from the Function Tree.
Step 2 Set the communication parameters of the NE according to the network planning.
Step 3 Click Apply.

----End
21.2.6.4 Configuring DCCs

To meet the NM requirements of a complicated network, it is necessary to set the channel type,
enable/disable status, and protocol type of the DCC according to the network planning.
Prerequisites
l
Context
The NE uses D1-D3 as DCC by default and allows the DCC communication.
Issue 03 (2012-11-30)

804
OptiX OSN 7500 II/7500/3500/1500

21 Outband DCN
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Communication > DCC
Step 2 Click the DCC Rate Configuration tab. Then, click New. The system displays the dialog box.
Set the Port, Channel Type, Protocol Type and LAPD Role fields.
Step 3 Click OK, and then click OK in the Operation Result dialog box.
Step 4 Optional: Click Query to query DCCs.
Step 5 Optional: Select the required DCC, and modify the parameters according to Table 21-2. Then,
click Apply to finish the modification.
Step 6 Optional: Select the required DCC, and click Delete to delete the DCC.
NOTE
When the board is configured with TPS, the DCCs on the working board are automatically copied to the
protection board. Therefore, the DCCs on the protection board cannot be deleted.
----End
Example
Table 21-2 Parameters
Issue 03 (2012-11-30)
Parameter
Value Range
Default Value
Description
Port
Line ports, external

clock interface

805
OptiX OSN 7500 II/7500/3500/1500

21 Outband DCN
Parameter
Value Range
Default Value
Description
Channel Type
D1-D1, D1-D3, D4D12
D1-D1
It is recommended
that you use the
default value except
in the following
cases:
l When the IP over
DCC solution or
OSI over DCC
solution is
applied, set
Channel Type of
the SDH line
ports to the same
value as the
Channel Type of
third-party
network.
l When the DCC
transparent
transmission
solution is
applied, the
Channel Type of
the SDH line
ports cannot
conflict with the
channel type of
the third-party
network.
Protocol Type
HWECC, IP, OSI,

Auto
IP
It is recommended
that you use the
in the following
cases:
l When the
HWECC solution
is applied, set
Protocol Type to
HWECC.
l When the OSI
over DCC
solution is
applied, set
Protocol Type to
OSI.
Issue 03 (2012-11-30)

806
OptiX OSN 7500 II/7500/3500/1500

21 Outband DCN
Parameter
Value Range
Default Value
Description
LAPD Role
Network, User
Network
l This parameter is
valid only when
Protocol Type is
set to OSI.
l Set LAPD Role
to User at one end
of a DCC and to
Network at the
other end of the
DCC.
21.2.6.5 Dividing a Network into Multiple ECC Subnets

When the number of NEs on a network exceeds 50, you need to divide the network into multiple
ECC subnets to prevent broadcast storms.
Prerequisites
l
Context
You can divide an SDH network into multiple ECC subnets by deleting DCC channels D1-D3
of the optical interface that is on the boundary NE of one subnet and is directly connected to the
equipment on another subnet.
Procedure
Step 1 In the NE Explorer, select the required NE and then choose Communication > DCC
Step 2 Click the DCC Rate Configuration tab, right-click DCC channels D1-D3 of the optical
interface that is directly connected to the equipment on another subnet, and select Delete.
----End
21.2.6.6 Configuring the Extended ECC

If no optical fiber connections are available between NEs, use Ethernet ports on the NEs to
achieve extended ECC communication. By default, NEs use automatic extended ECC
communication. If more than four NEs are connected to one hub, the NEs need to use manual
extended ECC communication.
Prerequisites
l
Issue 03 (2012-11-30)
The equipment must be installed according to the planning. The connections of the cables
and fibers are correct.
807
OptiX OSN 7500 II/7500/3500/1500

21 Outband DCN
The NE must be created on the U2000. The communication between the U2000 and the
NE must be normal.
The communication between NEs must be normal.
Context
When configuring the extended ECC, configure one or multiple NEs as the servers and other
NEs as the clients. One server NE can have a maximum of seven client NEs. If the number of
client NEs managed by a server NE exceeds eight, select a client NE as the server NE for the
remaining client NEs. In this case, the client NE functions as a client and a server at the same
time. The rest may be deduced by analogy. The port numbers of the server NEs must be different.
CAUTION
l The ECC extended mode of the remote NEs must be modified first, and that of the gateway
NE must be modified last.
l The extended ECC communication is avoided between the subnet gateway NEs.
l Do not set the gateway NE to the server. The NE closest to the gateway NE is recommended
to be the server NE.
CAUTION
l When setting the ECC extended mode remotely, strictly comply with the required setting
sequence. Otherwise, the communication between the U2000 and the NE where the
communication with the U2000 stops cannot be restored automatically. In this case, on-site
resetting is required. Hence, when setting the ECC extended mode remotely, work out the
ECC setting plan in advance to ensure that the settings are correct.
Procedure
Step 1 Setting the client NE
1.
In the status figure of the optical NE (ONE), right-click the server NE that is defined in the
ECC configuration plan and select the NE Explorer.
2.
Choose Communication > ECC Management from the left-hand Function Tree.
3.
Click Refresh to check the current ECC mode of the NE.
Issue 03 (2012-11-30)

808
OptiX OSN 7500 II/7500/3500/1500

21 Outband DCN
4.
Set ECC Extended Mode to Specified mode in the right-hand Functional Panel.
5.
In the Set Client area, enter the IP address of the server NE in the Opposite IP field. Then
enter a port number in the Port field.
NOTE
The port number is used by the local NE for communication with the server NE. The port number
cannot be the same as the value of the Port field in the Set Server area.
6.
Click Apply on the Set Client page.
7.
The Operation Result dialog box is displayed, indicating that the operation is successful.
Click Close.
NOTE
l The IP addresses of NEs cannot be repeated and must be within the same subnet.
l The client NE can be the server NE of the next lower level. At that time, the client port and the server
port of the local NE cannot be the same. For specific procedure, see "Setting the Server NE."
l The port number must be within the range from 1601 to 1699, for example, 1610.
Step 2 Setting the server NE

1.
Log in to the U2000.
2.
Double-click the ONE icon, and the status figure of the ONE is displayed.
3.
Right-click the subrack NE and select the NE Explorer.

NOTE
The subrack NE is selected as the server NE when the client NE is set.
4.
Choose Communication > ECC Management from the left-hand Function Tree.
5.
Click Refresh to check the current ECC mode of the NE.
6.
Set ECC Extended Mode to Specified mode in the right-hand Functional Panel.
7.
Enter the port number in the Port field of the Set Server area. The port number must be
the same as the port number you enter in the Port field of the Set Client area of the client
NE.
NOTE
l The port number is used by the local NE for communication with the client NE.
l The port number of the server NE must be the same as the port number of the client NE.
8.
Click Apply on the Set Server page.
9.
The Operation Result dialog box is displayed, indicating that the operation is successful.
Click Close.
----End
Issue 03 (2012-11-30)

809
OptiX OSN 7500 II/7500/3500/1500

21 Outband DCN
21.2.6.7 Configuring DCC Transparent Transmission

The OptiX equipment supports the DCC transparent transmission function. With this function,
the equipment can transparently transmit NM messages when the OptiX equipment is used
together with other equipment to form a network and can also transparently transmit the
management messages between ECC subnets.
Prerequisites
l
NE must be normal.
Procedure
Step 2 Click the DCC Transparent Transmission Management tab.
Step 3 Click New. The system displays the Create DCC Transparent Transmission Byte dialog box.
Step 4 Set the parameters of the DCC transparent transmission byte.
----End
Parameters
Issue 03 (2012-11-30)
Parameter
Value Range
Default Value
Description
Source Timeslot/
Port
Line ports

810
OptiX OSN 7500 II/7500/3500/1500

21 Outband DCN
Parameter
Value Range
Default Value
Description
Transparent
Transmission of
Overhead Byte at
Source Port
D1, D2, D3, D4, D5,

D6, D7, D8, D9,
D10, D11, D12, E1,
E2, X1, X2, X3, X4
D1
l Only one
overhead byte can
be selected at a
time.
l X1, X2, X3, and
X4 represent the
self-defined
overhead bytes
that are used
when
asynchronous
data services are
transmitted.
l The overhead
byte must not be a
used byte (for
example, the byte
used by a DCC
that is in use).
Sink Timeslot/Port
Line ports
Transparent
Transmission of
Overhead Byte at
Sink Port
D1, D2, D3, D4, D5,

D6, D7, D8, D9,
D10, D11, D12, E1,
E2, X1, X2, X3, X4
D1
l Only one
overhead byte can
be selected at a
time.
l The overhead
byte must not be a
used byte (for
example, the byte
used by a DCC
that is in use).
l Generally,
Transparent
Transmission of
Overhead Byte
at Sink Port is set
to the same value
as Transparent
Transmission of
Overhead Byte
at Source Port.
These two
parameters,
however, can be
set to different
values.
Issue 03 (2012-11-30)

811
OptiX OSN 7500 II/7500/3500/1500

21 Outband DCN
21.2.6.8 Querying and Allocating DCC Resources

NEs transmit the management information to one another by transmitting the D byte. The D byte
mode matches different path types (various path rates and the number of paths should be
provided). The DCC resources need to be allocated according to the network management
requirements. When changing the allocated DCC resources, you need to query the current
available DCC resources of the NEs.
Prerequisites
The user must log in to the U2000.
The U2000 must be properly connected to the equipment.
You must be an NM user with "NE and network monitor" authority or higher.
Impact on System
When a warm reset is performed on the SCC board, the specified path mode becomes available.
This operation may affect the service.

U2000
Precautions
NOTE
Before changing the DCC path mode, you need to query the allocation information about the DCC path.
If the number of allocated DCC paths of a certain type is more than the number of DCC paths of the type
in the new DCC path mode, you must disable the optical interfaces that are not required to release the DCC
path resources.
NOTE
Before changing the DCC path mode, you need to check whether the type and number of currently used
DCC paths are available in the new DCC path mode. If the type and number of currently used DCC paths
are not available, you can change the path mode only after you delete the paths that are unavailable.
CAUTION
You cannot delete the paths at the optical interfaces that work with the other NEs to form a core
route.
CAUTION
The path rates at the optical interfaces that are interconnected between adjacent NEs should be
consistent with each other. If the path rates are inconsistent with each other, the NEs cannot be
monitored.
Issue 03 (2012-11-30)

812
OptiX OSN 7500 II/7500/3500/1500

21 Outband DCN
Procedure
Step 1 In the Workbench view, double-click Main Topology to display the main topology.
Step 2 Right-click the NE in the Main Topology and choose NE Explorer.
Step 3 Select Communication > DCC Management from the Function Tree.
Step 4 On the DCC Rate Configuration tab, click Query to display information such as whether the
current NE is allocated the DCC resources and the channel type.
Step 5 On the DCC Resources Allocation tab, click Query to display information such as DCC Path
Mode, Resource Usage.
Step 6 Optional: On the DCC Rate Configuration tab, select the DCC path to be deleted, and then
click Delete.
Step 7 Optional: On the DCC Rate Configuration tab, select the optical interface to be disabled, and
then set Enabled/Disabled to Disabled.
CAUTION
Do not disable the optical interfaces that are used with the other NEs to form a core route.
Step 8 Click the DCC Rate Configuration tab and click New. In the displayed dialog box, set
Port,Channel Type, and Protocol Type.
Step 10 Allocate the DCC resources. In the DCC Resource Allocation dialog box, click Allot. The
DCC Resource Allocation dialog box is displayed.
. Click OK. The Confirm
Step 11 In the left pane, select a proper DCC Path Mode. Click
dialog box is displayed twice. Click OK. In the Operation Result dialog box, click Close.
----End
21.2.6.9 Querying the ECC Routes of an NE

By querying ECC routes, you can verify whether the ECC configuration is correct and whether
the DCC communication is normal.
Prerequisites
l
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Communication > NE ECC
Link Management from the Function Tree.
Step 2 Click Refresh and the ECC routes of the NE is displayed in the NE ECC Link Management
Table.
Issue 03 (2012-11-30)

813
OptiX OSN 7500 II/7500/3500/1500

21 Outband DCN
Step 3 Check whether the ECC routes and their parameters in NE ECC Link Management Table are
the same as the planned information.
Step 4 Optional: Click Add Manual Route to add manual ECC routes of the NE.
----End
21.2.7 Application Example Based on HWECC

This topic takes an example to describe the method of configuring the HWECC solution.
Context
For the parameters in this example, see the example in Planning Guide.
The example provides the configurations of only the typical NEs, including NE101, NE102,
NE104, NE106, and NE201.
Configuration of the extended ECC and DCC transparent transmission is not required.
Procedure
Step 1 Set IDs of the NEs. For details on operations, see Changing the ID of an NE.
NE
Extended ID
NE ID
NE101
101
NE102
102
NE103
103
NE104
104
NE106
106
NE201
201
Step 2 Set IP addresses of the NEs. For details on operations, see Setting Communication Parameters
of an NE.
Issue 03 (2012-11-30)
NE
IP Address
Subnet Mask
Default Gateway
NE101
10.0.0.101
255.255.255.0
0.0.0.0 (default
value)
NE102
129.9.0.102
255.255.255.0
0.0.0.0 (default
value)
NE103
129.9.0.103
255.255.255.0
0.0.0.0 (default
value)

814
OptiX OSN 7500 II/7500/3500/1500

21 Outband DCN
NE
IP Address
Subnet Mask
Default Gateway
NE104
129.9.0.104
255.255.255.0
0.0.0.0 (default
value)
NE106
129.9.0.106
255.255.255.0
0.0.0.0 (default
value)
NE201
11.0.0.201
255.255.255.0
11.0.0.1
Step 3 Configure DCCs of the NEs. For details on operations, see Configuring DCCs.
l Set the protocol type that the DCC uses to HWECC for all the line ports of the NEs.
l Set the channel type to D1-D3 for all the SDH ports on the NEs.
Step 4 Query ECC routes at NE101 and NE201. For details on operations, see Querying the ECC Routes
of an NE.
l At NE101, the routes to NE102, NE103, NE104, and NE106 are queried.
l At NE201, the routes to NE202, NE203, and NE204 are queried.
----End
21.3 IP over DCC Solution

The NEs use unified DCCs to transmit the data of the TCP/IP protocol by using the IP over DCC
solution. In this way, the U2000 can manage NEs. The IP over DCC solution applies to a network
that is comprised of the OptiX transmission equipment and the third-party equipment that
supports the IP over DCC function. This solution can also be applied to a network that is
comprised of only the OptiX transmission equipment.

This topic describes the basic concepts and networking of the IP over DCC solution.

The IP over DCC solution uses the technology in which the TCP/IP protocol is supported on the
DCC.
The DCC is used to transmit the OAM information between transmission equipment. The
protocol stacks used in the DCC communication by different vendors are not fully compatible
(for example, the OptiX equipment uses the HWECC proprietary protocol). Therefore,
additional overheads or service resources are occupied for DCC information transparent
transmission in the networking of equipment from different vendors. The IP over DCC solution,
however, supports the TCP/IP protocol without occupying additional overheads or service
resources. If the equipment of other vendors supports the IP over DCC technology, the
management channels can be interconnected.
IP over DCC Protocol Stack

The IP over DCC protocol consists of five layers, as shown in the following figure.
Issue 03 (2012-11-30)

815
OptiX OSN 7500 II/7500/3500/1500

21 Outband DCN
Figure 21-12 Architecture of the IP over DCC protocol stack
Routing protocol
OSPF
Transport layer
TCP/UDP
Network layer
IP
PPP
Data link layer

Ethernet
Physical layer
DCC
Physical layer
The main function of the physical layer is to provide channels for data transmission for the
data end equipment.
Physical channels are classified into the following two categories:
DCC channel: The SDH-frame DCC bytes or the OTN-frame GCC bytes are used as
the channels for the communication between NEs.
Ethernet physical channel: The NE provides the Ethernet physical channel through the
Ethernet NM port or the NE cascading port.
Data link layer

The main function of the data link layer is to provide reliable data transmission on physical
links.
In the case of DCCs, the NE adopts the PPP protocol to realize the data link layer function.
The PPP protocol complies with RFC 1661.
Network layer
The main function of the network layer is to specify the network layer address for a
network entity and to provide the transferring and addressing functions.
The NE adopts the IP and the matching ARP and ICMP to realize the network layer
functions.
Transport layer
The main function of the transport layer is to provide the end-to-end communication service
for the upper layer. The NE supports the connection-oriented TCP and the connectionlessoriented UDP.
Routing protocols
Routing protocols belong to the scope of the application layer. The NE supports Open
Shortest Path First (OSPF).
The OSPF protocol is a dynamic routing protocol that is based on the link status. The OSPF
protocol divides an autonomous system into several areas. Route nodes exchange routing
information in an area. The route nodes at the edge of an area make summary and exchange
Issue 03 (2012-11-30)

816
OptiX OSN 7500 II/7500/3500/1500

21 Outband DCN
information with the routers in other areas. Areas are identified by area IDs. The area ID
has the same format as the IP address.
Currently, the OSPF protocol of the OptiX equipment supports only the routes within an
area and does not support the routes between areas. Hence, the gateway NE and all its
managed non-gateway NEs must be in the same OSPF area. By default, the line port of the
OptiX equipment is enabled with the OSPF protocol but the Ethernet port is not enabled
with the OSPF protocol. Hence, to form a network through the Ethernet port, you need to
modify the OSPF setting of the NE.
In addition to the dynamic routing protocol, the NE supports static routes. Static routes are
manually configured routes. Static routes have a higher priority than dynamic routes. When
there is a route conflict, the equipment selects static routes.
Access Modes
In the IP over DCC solution, there are two modes for the U2000 to access an NE, namely, gateway
mode and direct connection mode.
l
Gateway Mode
In the gateway mode, the U2000 accesses a non-gateway NE through the gateway NE. The
gateway NE queries the core routing table of the application layer according to the ID of
the NE to be accessed to obtain the corresponding route.
The core routing table synthesizes the transport layer routing tables of all communication
protocol stacks. Each route item includes the following:
Transfer distance
Direct Connection Mode

In the direct connection mode, the U2000 accesses an NE as the gateway NE. All transfer
NEs on the access path query the IP routing table of the network layer according to the IP
address of the NE to be accessed to obtain the corresponding route.
The IP routing table is based on routing protocols. It includes both dynamic routes generated
by routing protocols and static routes configured by operators. Each route item includes
the following:
Destination IP address
Subnet mask
IP address of the gateway
Interface
OSPF
The Open Shortest Path First (OSPF) protocol is a dynamic routing protocol that is based on the
link status. NEs update their routing tables dynamically through the OSPF protocol. The OSPF
protocol divides an autonomous domain into several areas and updates the routes in the areas or
between areas. Generally, the gateway NE and the non-gateway NEs that are managed by the
gateway NE are in the same OSPF area.
Issue 03 (2012-11-30)

817
OptiX OSN 7500 II/7500/3500/1500

21 Outband DCN
21.3.1.2 Networking
The application of the IP protocol enables the hybrid networking of Huawei equipment and
equipment of other vendors. The typical networking modes of the DCN based on the IP over
DCC communication are described as follows.
NM information transparently transmitted by the third-party equipment

The NM information of the OptiX equipment is transmitted transparently through IP over DCC
by the third party equipment, as shown in Figure 21-13.
Figure 21-13 NM information transparently transmitted by the third party equipment (IP)
Third party
equipment
IP Over DCC
Third party
equipment
NM information of the third-party equipment is transparently transmitted

The NM information of the third party is transmitted transparently through IP over DCC by the
OptiX equipment, as shown in Figure 21-14.
Figure 21-14 NM information of the third-party equipment is transparently transmitted (IP)
Third party
equipment
Third party
equipment
IP Over DCC
Third party
equipment
Third party
equipment
Issue 03 (2012-11-30)

818
OptiX OSN 7500 II/7500/3500/1500

21 Outband DCN
21.3.2 Availability
The IP over DCC solution requires the support of the applicable equipment, boards, and software.
Version Support
Applicable Version
OptiX OSN 1500/2500/3500/7500
V100R003 and later
T2000
V200R002 and later
U2000
Applicable Version
OptiX OSN 3500 II
V100R009 and later
T2000
U2000
Applicable Version
OptiX OSN 7500 II
U2000
Hardware Support
Issue 03 (2012-11-30)
Applicable Board
Applicable Version
N4GSCC
OptiX OSN 3500/7500
N6GSCC
OptiX OSN 3500/7500
N1PSXCS
OptiX OSN 3500
N2PSXCSA
OptiX OSN 3500
T1PSXCSA
OptiX OSN 7500
R1PCXLN
TNN1PSXCS
OptiX OSN 7500 II
TNN1SCA
OptiX OSN 7500 II

819
OptiX OSN 7500 II/7500/3500/1500

21 Outband DCN
Applicable Board
Applicable Version
N1SXCSA
OptiX OSN 3500
N3PSXCSA
OptiX OSN 3500

It is recommended that you adopt only one of the following solutions to form a DCN: HWECC
If you combine the IP over DCC solution with other solutions to build a network, note the
following points:
l
The IP protocol stack of NEs can communicate with the HWECC protocol stack.
The IP protocol stack of NEs cannot communicate with the OSI protocol stack.
If DCC bytes are used to transparently transmit NM messages when the OptiX equipment
is used together with the third-party equipment to form a network, you can adopt the IP
protocol stack to manage the OptiX equipment. It is, however, recommended that you use
the HWECC protocol.
21.3.4 Principles
This topic describes how an NE transfers messages depending on the mode in which the
U2000 accesses an NE. The implementation principles in different modes vary slightly from
each other.
Gateway Mode
Figure 21-15 illustrates how the IP over DCC solution transfers the messages originating from
the U2000 to a non-gateway NE when the U2000 adopts the gateway mode to access the NE.
Figure 21-15 Implementation principle of message transferring (gateway mode)
Application
Application
Application
TCP
TCP
TCP
IP
IP
IP
IP
IP
PPP
PPP
PPP
DCC
DCC
DCC
Transfer NE
Destination NE
Ethernet
NMS
TCP
Ethernet
Gateway NE

Issue 03 (2012-11-30)

820
OptiX OSN 7500 II/7500/3500/1500

21 Outband DCN
1.
The U2000 transfers application layer messages to the gateway NE through the TCP
2.
The gateway NE extracts the messages from the TCP/IP protocol stack and reports the
3.
The network layer of the gateway NE queries the address of the destination NE in the
in Figure 21-15 is IP, the gateway NE transfers the messages to the transfer NE through
the IP protocol stack.
4.
NE queries the destination IP address of the packet. If the destination IP address is not the
NE IP address of the local station, the transfer NE queries the IP routing table according
to the destination IP address to obtain the corresponding route, and then transfers the packet.
5.
the application layer through the transport layer because the destination IP address of the
packet is the NE IP address of the local station. The application layer acts according to the
message sent from the U2000.

Figure 21-16 illustrates how the IP over DCC solution transfers the messages originating from
the U2000 to a destination NE when the U2000 adopts the direct connection mode to access the
NE.
Figure 21-16 Implementation principle of message transferring (direct connection mode)
Application
Application
TCP
TCP
IP
Ethernet
IP
IP
IP
PPP
PPP
PPP
DCC
DCC
DCC
Transfer NE
Destination NE
Ethernet
T2000
Transfer NE
The original gateway NE in the direct connection mode acts as an ordinary transfer NE and the
message transferring is implemented at the network layer. This is different from the gateway
mode.
21.3.5 Network Planning

When using the IP over DCC solution, plan the parameters of a DCN according to the situation
of the network.
Issue 03 (2012-11-30)

821
OptiX OSN 7500 II/7500/3500/1500

21 Outband DCN

This topic provides guidelines on how to plan the IP over DCC solution.
This guide focuses on the differences between planning the IP over DCC solution and planning
the HWECC solution. For the same parts, such as planning the external DCNs, NE IDs, gateway
NEs, and network division, see Planning Guide.
When planning the IP over DCC, comply with the following principles:
IP over DCC is used to manage NEs when the OptiX equipment interworks with the third-party
equipment that supports the IP over DCC function, or when only Huawei transmission equipment
is involved in the networking. The principles for planning IP over DCC are as follows:
l
When the U2000 is used to manage NEs, the number of non-gateway NEs accessed through
one gateway NE should not exceed 100, and it is recommended that the maximum number
should be 50.
The gateway NE and the non-gateway NEs that are managed by the gateway NE must be
in the same OSPF area.
The number of NEs in an OSPF area cannot exceed 100.
Plan static routes when the U2000 and the gateway NE or the NEs that need to be directly
accessed by the U2000 cannot be interconnected through the dynamic route at the network
layer.
When planning IP addresses, comply with the following principles:

l
Each NE should be configured with a unique IP address.
Configure the IP addresses of standard class A, B or C for NEs. That is, the IP address of
an NE ranges from 1.0.0.1 to 223.255.255.254. The broadcast IP address, network IP
address, and IP address such as 127.x.x.x, however, should be excluded. The subnet
addresses such as 192.168.x.x and 192.169.x.x should also be excluded.
The IP address should be used together with the subnet mask. The subnet mask of variable
length is supported.
When an NE accesses the U2000 using the static routing protocol, use different IP subnets
for the gateway NE and non-gateway NEs.
Two networks connected through Ethernet should be classified into different IP subnets to
avoid that certain NEs fail to access the U2000 when the network is divided into domains.
When planning the DCC, comply with the following principles:

l
If the network is comprised of only the OptiX equipment, it is recommended that you use
bytes D1 to D3 in SDH frames as DCCs.
If the network is comprised of both OptiX equipment and the third-party SDH equipment,
use the DCC bytes that are used by the third-party equipment (for example, bytes D1 to D3
or D4 to D12) as DCCs.

This topic uses an example to describe how to plan the IP over DCC solution.
Issue 03 (2012-11-30)

822
OptiX OSN 7500 II/7500/3500/1500

21 Outband DCN
Figure 21-17 Networking example for the IP over DCC solution

NE105
NE106
NE208
Third-party
NMS
NE207
NE104
NMS
NE101
NE103
NE102
Third-party transmission equipment

OptiX transmission equipment
Quidway 2501
Fiber link
Network cable
Hub
Fiber
2 Mbit/s channel
Figure 21-18 shows a transmission network that is comprised of both OptiX equipment and the
third-party equipment that supports the IP over DCC feature. The steps to plan the DCN are as
follows:
1.
Select NE101 that is the closest to the U2000 as the gateway NE.
2.
As the third-party equipment uses the DCC bytes D1 to D3, it is not required to modify the
DCCs of the NEs.
3.
Allocate IDs and IP addresses for all the NEs according to the situation of the network. The
subnet mask of all the NEs is 255.255.0.0.
Issue 03 (2012-11-30)

823
OptiX OSN 7500 II/7500/3500/1500

21 Outband DCN
Figure 21-18 Allocation of IDs and IP addresses to all NEs

9-108
200.0.0.108
0.0.0.0
10.0.0.1/16
9-105
200.1.0.105
0.0.0.0
9-106
200.1.0.106
0.0.0.0
10.0.0.100/16
9-104
100.0.0.105
0.0.0.0
100.1.0.1/16
100.1.0.100/16
9-101
100.1.0.101
0.0.0.0
9-107
200.0.0.107
0.0.0.0
9-103
100.0.0.103
0.0.0.0
9-102
100.0.0.102
0.0.0.0
30.0.0.1/16
30.0.0.4/16
30.0.0.2/16
IP address
Gateway
30.0.0.3/16
4.
Plan IP routes.
l As the number of NEs is smaller than 64 and all the NEs support the OSPF protocol,
configure all the NEs to the same OSPF area.
l The U2000 and the gateway NE (NE101) are in the same Ethernet segment. The gateway
NE can obtain the routes to all other NEs through the OSPF protocol. Therefore, the
U2000 can access any NE in the gateway mode, and you do not need to set any route.
l As there are routers between the third-party NMS and NE101, using only dynamic routes
cannot achieve the connection between the third-party equipment and the U2000.
Therefore, set static routes on NE101, NE102, the U2000 server, and the routers.
21.3.6 Configuring IP over DCC

Plan the DCC resource properly according to the configuration principle of the IP over DCC
and configure the IP over DCC by following the specified process to ensure the effective
supervision of the U2000 on the NEs.

The configuration of the IP over DCC solution must comply with the process.
Figure 21-19 shows the configuration process of the IP over DCC solution.
Issue 03 (2012-11-30)

824
OptiX OSN 7500 II/7500/3500/1500

21 Outband DCN
Figure 21-19 Configuration process of the IP over DCC solution

Start
1
Modify IDs and IP

addresses for NEs
2
Configure DCCs for
NEs
3
Check the IP routes
of the gateway NE
4
Querying the OSPF

Protocol Status
IP static routes
required?
No
Yes
Add IP static routes
End
Table 21-3 Description of the configuration process of the IP over DCC solution
Number
Description
Configure the network-wide data, including the NE IDs and the NE IP

addresses. In certain cases, you need to set the subnet masks and default
gateways according to the external DCN.
l The NE ID and IP address are set when an NE is created. For the
configuration process, see the Configuration Guide.
l To change the IP address of an NE, see Setting Communication Parameters
of an NE.
Issue 03 (2012-11-30)

825
OptiX OSN 7500 II/7500/3500/1500

21 Outband DCN
Number
Description
l The DCC protocol type of the line port should be set to IP.
l The DCC channel type of the SDH port should be the same as that of the
third-party equipment. If the network is comprised of only the OptiX
equipment, set the DCC type to D1-D3.
l For the configuration process, see Configuring DCCs.
l In the normal situation, a gateway NE should have the routes to all the
non-gateway NEs that are managed by the gateway NE and the route to
the U2000.
l For the querying process, see Querying IP Routes.
l If certain routes are unavailable, contact Huawei engineers to adjust the

OSPF protocol parameters used by the NEs. Make sure that the OSPF
function is available to all the NEs.
l For the querying process of the OSPF protocol, see Querying the OSPF
Protocol Status.
See Configuring the IP Static Route for an NE to add static IP routes.

Except for the requirement that the U2000 access the NEs on the entire
network through the gateway NE, to meet the upper layer application
requirement of accessing remote NEs based on the IP network layer, the proxy
ARP function must be enabled on the gateway NE and a static route must be
configured on each remote NE to the U2000. For the process of enabling the
proxy ARP, see Enabling the Proxy ARP.

Prerequisites
l
Procedure
Tree.
Issue 03 (2012-11-30)

826
OptiX OSN 7500 II/7500/3500/1500

21 Outband DCN

NOTE
----End
Follow-up Procedure

parameters.
Prerequisites
l
Procedure
Issue 03 (2012-11-30)

827
OptiX OSN 7500 II/7500/3500/1500

21 Outband DCN
Step 3 Click Apply.

----End

Prerequisites
l
Context
Procedure
Issue 03 (2012-11-30)

828
OptiX OSN 7500 II/7500/3500/1500

21 Outband DCN
NOTE
----End
Example
Issue 03 (2012-11-30)
Parameter
Value Range
Default Value
Description
Port

clock interface

829
OptiX OSN 7500 II/7500/3500/1500

21 Outband DCN
Parameter
Value Range
Default Value
Description
Channel Type
D1-D1, D1-D3, D4D12
D1-D1
It is recommended
that you use the
in the following
cases:
l When the IP over
DCC solution or
OSI over DCC
solution is
applied, set
Channel Type of
the SDH line
ports to the same
value as the
Channel Type of
third-party
network.
l When the DCC
transparent
transmission
solution is
applied, the
Channel Type of
the SDH line
ports cannot
conflict with the
channel type of
the third-party
network.
Protocol Type
HWECC, IP, OSI,

Auto
IP
It is recommended
that you use the
in the following
cases:
l When the
HWECC solution
is applied, set
Protocol Type to
HWECC.
l When the OSI
over DCC
solution is
applied, set
Protocol Type to
OSI.
Issue 03 (2012-11-30)

830
OptiX OSN 7500 II/7500/3500/1500

21 Outband DCN
Parameter
Value Range
Default Value
Description
LAPD Role
Network, User
Network
l This parameter is
valid only when
Protocol Type is
set to OSI.
l Set LAPD Role
to User at one end
of a DCC and to
Network at the
other end of the
DCC.
21.3.6.5 Querying IP Routes

By querying IP routes, you can verify whether the configuration of the IP over DCC feature is
correct and whether the DCC communication is normal.
Prerequisites
l
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Communication > IP Stack
Protocol Management from the Function Tree. Click the IP Route Management tab.
Step 2 Check whether the IP routes and their parameters in the routing table are the same as the planning
information.
----End
21.3.6.6 Querying the OSPF Protocol Status

Enable the OSPF protocol so that the routing information on the gateway NE can be
automatically diffused to other NEs.
Prerequisites
l
Context
The OSPF protocol is enabled by default.
Issue 03 (2012-11-30)

831
OptiX OSN 7500 II/7500/3500/1500

21 Outband DCN
Procedure
Step 1 Select an NE in the NE Explorer. Choose Communication > IP Stack Protocol
Management from the Function Tree. Click the OSPF Parameter Settings tab.
Step 2 Click Query to check if the OSPF protocol status is normal.
----End
Follow-up Procedure
If the OSPF protocol is incorrect, contact Huawei engineers to adjust the OSPF protocol
parameters used by the NEs.
21.3.6.7 Enabling the Proxy ARP

If you enable proxy ARP for a gateway NE, the gateway NE can answer ARP requests for other
non-gateway NEs, so that you can set IP addresses of NEs of the same network in the same
network segment.
Prerequisites
l
Context
When the U2000 and the gateway NE are directly connected through LAN and the IP addresses
of the U2000 and the gateway NE are in the same network segment, when the remote NEs
connect to the gateway NE through fibers, and when the IP addresses of the remote NEs, the
gateway NE, and the U2000 are in the same subnet, there are requirements that the U2000
accesses the NEs on the entire network through the gateway NE and the upper layer application
requirement of accessing remote NEs based on the IP network layer. To meet the upper layer
application requirement of accessing remote NEs based on the IP network layer, you need to
enable the proxy ARP of the gateway NE.
Procedure
Step 1 Select an NE in the NE Explorer. Choose Communication > IP Stack Protocol
Management from the Function Tree. Click the Proxy ARP tab.
Step 2 Optional: Click Query.
Step 3 Select Enabled from the drop-down list.
Step 4 Click Apply. Click Close in the Operation Result dialog box.
----End
Follow-up Procedure
After you enable proxy ARP, you need to create a static route for each NE.
Issue 03 (2012-11-30)

832
OptiX OSN 7500 II/7500/3500/1500

21 Outband DCN
21.3.6.8 Configuring the IP Static Route for an NE

When dynamic routes fail to meet the planning requirements, create the corresponding static IP
routes manually.
Prerequisites
l
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Communication > IP Stack
Protocol Management from the Function Tree. Click the IP Route Management tab.
Step 2 Click New. The system displays the Create an IP Route dialog box.
Step 3 Set the parameters of the static IP route.
Step 4 Click OK.

----End
Parameters
Issue 03 (2012-11-30)
Parameter
Value Range
Default Value
Description
Destination IP
Address
You can set this

parameter to an IP
address or an IP
address range.
Subnet Mask
This parameter
specifies the subnet
mask of the set
Destination IP
Address.
Gateway IP Address
This parameter
specifies the IP
address of the
gateway to which the
set Destination IP
Address
corresponds, that is,
the next-hop address.

833
OptiX OSN 7500 II/7500/3500/1500

21 Outband DCN
NOTE
The created static route has a lower priority than a dynamic route.
21.3.7 Application Example for Hybrid Networking Based on IP

over DCC
This topic takes an example to describe the method of configuring the IP over DCC solution.
Precautions
NOTE
l For the parameters in this example, see the example in Network Planning.
l This example provides only the configurations of the typical NEs: NE101, NE102, NE105, and NE106.
l The following steps are provided to configure the functions one by one. This is for convenience of
description. In an actual configuration, perform the configuration for the NEs one by one.
Procedure
Step 1 Set the IDs of the NEs. See the Configuration Guide.
NE
Extended ID
NE ID
NE101
101
NE102
102
NE105
105
NE106
106
Step 2 Set the IP address information for the NEs. See the Configuration Guide.
NE
IP Address
Subnet Mask
Default Gateway
NE101
100.1.0.101
255.255.255.0
0.0.0.0 (default
value)
NE102
100.0.0.102
255.255.255.0
0.0.0.0 (default
value)
NE105
200.1.0.105
255.255.255.0
0.0.0.0 (default
value)
NE106
200.1.0.106
255.255.255.0
0.0.0.0 (default
value)
Step 3 Set the DCCs for the NEs. See Configuring DCCs.
l Set the DCC protocol type of all the line ports of all NEs to IP(default value).
l Set the channel type of all SDH microwave ports of all NEs to D1-D3.
Issue 03 (2012-11-30)

834
OptiX OSN 7500 II/7500/3500/1500

21 Outband DCN
Step 4 Query the IP routes of NE101. See Querying IP Routes.

l The IP address of each non-gateway NE (for example, 100.0.0.102, 200.1.0.105, and
200.1.0.106) should have corresponding IP routes.
l The IP address of the U2000 server (10.1.0.100) should have corresponding routes.
l The IP address of the third-party equipment (for example, 30.0.0.4) should have
corresponding IP routes.
NOTE
If certain routes are unavailable, request Huawei engineers to adjust the parameters of the OSPF protocol used
by the NEs.
Step 5 Set an IP static route at both NE101 and NE102. See Configuring the IP Static Route for an NE.
l The parameters of the IP static route at NE101 are as follows:
Destination address: 10.0.0.0
Subnet mask: 255.255.0.0
Gateway: 100.1.0.1
l The parameters of the IP static route at NE102 are as follows:
Destination address: 10.0.0.0
Subnet mask: 255.255.0.0
Gateway: 100.1.0.101
NOTE
Set the corresponding route on both the NMS of the third-party equipment and the router.
----End
Result
1.
All NEs can be successfully created.
21.4 OSI over DCC Solution

The NEs use unified DCCs to transmit the data of the OSI protocol by using the OSI over DCC
solution. In this way, the U2000 can manage NEs. The OSI over DCC solution applies to a
network that is comprised of the OptiX equipment and the third-party equipment that supports
the OSI over DCC function.

This topic describes the basic concepts and networking of the OSI over DCC solution.

The OSI over DCC solution uses the technology in which the OSI protocol is supported on the
DCC.
The DCC is used to transmit the OAM information between transmission equipment. Due to
history reasons, the protocol stacks used in the DCC communications by different vendors are
not fully compatible (for example, Huawei equipment uses the HWECC proprietary protocol).
Issue 03 (2012-11-30)

835
OptiX OSN 7500 II/7500/3500/1500

21 Outband DCN
Therefore, additional overheads or service resources are occupied for DCC information
transparent transmission in the networking of equipment from different vendors. The OSI over
DCC solution, however, supports the OSI protocol without occupying additional overheads or
service resources. If the equipment of other vendors supports the OSI over DCC technology, the
management channels can be interconnected.
OSI over DCC Protocol Stack

The OSI over DCC protocol consists of five layers, in which the session layer, representation
layer, and application layer are unified as the application layer and use proprietary protocols, as
shown in Figure 21-20.
Figure 21-20 Architecture of the OSI over DCC protocol stack
Application layer
Qx/MML/SWDL
Transport layer
TP4
Network layer
IS-IS/ES-IS/CLNP
LAPD
Data link layer

Ethernet
Physical layer
DCC
Physical layer
The main function of the physical layer is to provide channels for data transmission, for the data
end equipment.
Physical channels are classified as follows:
l
DCC channel
DCC channels use the DCC bytes in SDH frames or the GCC bytes in OTN frames as the
channels for the communication among NEs.
Ethernet physical channel

The NE provides the Ethernet physical channel through the Ethernet NM port or the NE
cascading port.
Data link layer

The main function of the data link layer is to provide reliable data transmission on physical links.
In the case of DCCs, the NE adopts the LAPD protocol to realize the data link layer function.
The LAPD protocol complies with ITU-T Q.921.
When using the LAPD protocol, you must set the LAPD role. In the case of the two ends of a
DCC, set the LAPD role to Network at one end and to User at the other end.
Issue 03 (2012-11-30)

836
OptiX OSN 7500 II/7500/3500/1500

21 Outband DCN
Network layer
The main function of the network layer is to specify the network layer address for a network
entity and to provide the transferring and addressing functions.
The NE adopts the ISO-defined connectionless network service (CLNS) to realize the network
layer function. The CLNS is comprised of the following three protocols:
l
Connectionless network protocol (CLNP)

The CLNP protocol complies with ISO 8473. It has functions similar to the IP in the TCP/
IP protocol stack. In the CLNP protocol, the network service access point (NSAP) works
as the network layer address.
The NSAP functions as the IP address in the IP protocol. The address format of the NSAP
is shown in Figure 21-21.
Figure 21-21 Format of the NSAP address
IDP
DSP
Higher order DSP
AFI
IDI+pad
DFI
ORG
RES
RD
Area
Area address
1
System ID
9
10
11
12
13
14
15
16
17
NSEL
18
19
20
The NE uses the simplified NSAP address. The simplified NSAP address includes only the
following three parts:
Area ID
The area ID refers to the area address shown in Figure 21-21 and has one to thirteen
bytes. The area ID is used to address the routes between areas. The NSAPs of the NEs
in the same L1 route area must have the same area ID but those in the same L2 route
area can have different area IDs. You can manually set the area ID. The default value
of the area ID is 0x47000400060001.
System ID
The System ID refers to the system ID shown in Figure 21-21 and has six bytes. The
System ID is used to address the routes within an area. The value of the first three bytes
of the System ID of the OptiX equipment is always 0x08003E. The last three bytes are
the NE ID.
NSEL
The NSEL refers to the port ID of the network layer protocol. It has one byte. The NSEL
of the OptiX equipment is always 0x1D.
l
IS-IS protocol
In the CLNS, NEs are classified into intermediate systems (IS) and end systems (ES)
according to the NE role. The IS is equivalent to the router in the TCP/IP protocol stack
and the ES is equivalent to the host.
The IS-IS protocol is a dynamic routing protocol between two ISes. It complies with ISO
10589 and functions as the OSPF protocol in the TCP/IP protocol stack. The IS-IS protocol
supports the L1 and L2 layered routes. The NE whose role is L1 cannot be a neighbor of
Issue 03 (2012-11-30)

837
OptiX OSN 7500 II/7500/3500/1500

21 Outband DCN
an NE in a different area and is involved only in the routes in its own area. It issues a default
route that points to its closest L2 NE and accesses other areas through the default route.
The NE whose role is L2 can be a neighbor of the L2 NE in a different area and can also
be involved in the routes in the backbone area. The backbone area is formed by consecutive
L2 NEs. In other words, the L2 NEs in the backbone area must be consecutive (connected).
In the network as shown in Figure 21-22, as the L2 NEs in the backbone area are not
consecutive, the NEs in area 4 are isolated from the NEs in other areas. By default, the role
of the OptiX equipment is L1.
Figure 21-22 Layered routes of IS-IS protocol routes (L2 not consecutive)
OSI DCN
L1
L2
NMS
Area 2
Area 3
Area 1
Backbone
Area 4
NOTE
L2 NEs are classified into two categories, the NE with only the L2 role and the NE with both the L2 role
and the L1 role. Generally, an L2 NE has the L1 role.
ES-IS protocol
The ES-IS protocol is a dynamic routing protocol between the ES and the IS. It complies
with ISO 9542 and functions as the ARP and ICMP protocols in the TCP/IP protocol stack.
Transport layer
The main function of the transport layer is to provide the end-to-end communication service for
the upper layer. The NE adopts the TP4 protocol to realize the transport layer function. The TP4
protocol complies with ISO 8073. It has functions similar to the TCP in the TCP/IP protocol
stack.
Issue 03 (2012-11-30)

838
OptiX OSN 7500 II/7500/3500/1500

21 Outband DCN
Access Mode
In the OSI over DCC solution, there are two modes for the U2000 to access an NE, namely,
gateway mode and direct connection mode.
l
Gateway mode
In the gateway mode, the U2000 accesses a non-gateway NE through the gateway NE. The
gateway NE queries the core routing table of the application layer according to the ID of
the NE to be accessed to obtain the corresponding route.
protocol stacks. Each route item includes the following:
Transfer distance
Direct connection mode

In the direct connection mode, the U2000 accesses an NE as the gateway NE. All transfer
NEs on the access path query the L1 routing table and L2 routing table of the network layer
according to the NSAP address of the NE to be accessed to obtain the corresponding route.
The L1 routing table and the L2 routing table are based on the IS-IS protocol.
Each route item in the L1 routing table includes the following:
Destination system ID
Cost
Adjacency No.
Each route item in the L2 routing table includes the following:
Destination area ID
Cost
Adjacency No.
NOTE
The adjacency No. is the ID of an LAPD connection. You can query the link adjacency table of the
data link layer to obtain the mapping relation between the adjacency No. and the LAPD connection.
In the OSI over DCC solution, the U2000 can access any NE by using the direct connection
mode, that is, the U2000 can consider any NE as the gateway NE. To improve the
communication efficiency, there should not be a lot of NEs that are accessed in the direct
connection mode in a network.
LAPD Role at the Optical Interfaces

The DCCs of the optical interfaces of the OSI protocol stack comply with the LAPD protocol
defined in Q.921. You need to set the LAPD roles for the interconnected optical interfaces with
one being network, the other being user. The optical interfaces refer to the optical interface of
the equipment and that of the interconnected equipment. Regardless whether the equipment
interconnected with Huawei equipment or equipment of other vendors, configure the equipment
according to the configuration of the interconnected equipment.
TP4 Protocol
The TP4 protocol is located at the transport layer of the OSI protocol stack. The function of the
TP4 protocol is similar to the function of the TCP protocol of the IP of the protocol family.
Issue 03 (2012-11-30)

839
OptiX OSN 7500 II/7500/3500/1500

21 Outband DCN
Through the TP4 protocol, a reliable communication connection between two nodes can be
established to process the problems, such as loss, repetition, and juggling of data packets caused
by network fault.
21.4.1.2 Networking
The OSI over DCC protocol is used in the hybrid networking of Huawei equipment and other
equipment that supports the OSI protocol. The typical networking modes of the DCN based on
the OSI over DCC protocol are described as follows.
NM information transparently transmitted by the third-party equipment

The NM information of the Huawei OptiX equipment is transparently transmitted by the third
party equipment through OSI over DCC, as shown in Figure 21-23. Huawei equipment is located
at the network edge, and the third party equipment is located on the backbone network. The
management information data between Huawei U2000 and equipment need be forwarded by the
third party equipment. In this case, at least one gateway NE must be used in each subnet formed
by Huawei equipment.
Figure 21-23 Transparent transmission of NM information by the third party equipment (OSI)
OSI
protocal stack
Third party
equipment
OSI
protocal stack
OSI Over DCC
Third party
equipment
OSI
protocal stack
NM information of the third-party equipment is transparently transmitted

The NM information of the third party equipment is transparently transmitted by the Huawei
OptiX equipment, as shown in Figure 21-24. Huawei equipment is located on the backbone
network, and the third party equipment is located at the network edge. The management
information data between the third party NM and equipment need be forwarded by Huawei
equipment.
NOTE
In practical application, the networking is more complex, and hybrid networking of equipment from
different suppliers at the network edge and in the backbone networks is frequently adopted.
Issue 03 (2012-11-30)

840
OptiX OSN 7500 II/7500/3500/1500

21 Outband DCN
Figure 21-24 Transparent transmission of NM information of the third party equipment (OSI)
Third party
equipment
Third party
equipment
OSI
protocal stack
OSI
protocal stack
OSI Over DCC
Third party
equipment
OSI
protocal stack
Third party
equipment
21.4.2 Availability
The OSI over DCC solution requires the support of the applicable equipment, boards, and
software.
Version Support
Issue 03 (2012-11-30)
Applicable Version
OptiX OSN 1500/2500/3500/7500
V100R003 and later
T2000
V200R002 and later
U2000
Applicable Version
OptiX OSN 3500 II
V100R009 and later
T2000
U2000
Applicable Version
OptiX OSN 7500 II
U2000

841
OptiX OSN 7500 II/7500/3500/1500

21 Outband DCN
Hardware Support
Applicable Board
Applicable Version
N4GSCC
OptiX OSN 3500/7500
N6GSCC
OptiX OSN 3500/7500
N1PSXCS
OptiX OSN 3500
N2PSXCSA
OptiX OSN 3500
T1PSXCSA
OptiX OSN 7500
R1PCXLN
TNN1PSXCS
OptiX OSN 7500 II
TNN1SCA
OptiX OSN 7500 II
N1SXCSA
OptiX OSN 3500
N3PSXCSA
OptiX OSN 3500

It is recommended that you adopt only one of the following solutions to form a DCN: HWECC
If you combine the OSI over DCC solution with other solutions to build a network, note the
following points:
l
The OSI protocol stack of NEs can communicate with the HWECC protocol stack only in
the same area of the L1 layer.
The OSI protocol stack of NEs cannot communicate with the IP protocol stack.
If DCC bytes are used to transparently transmit NM messages when the OptiX equipment
is used together with the third-party equipment to form a network, you can adopt the OSI
protocol stack to manage the OptiX equipment. It is, however, recommended that you use
the HWECC protocol.
21.4.4 Principles
This topic describes how an NE transfers messages depending on the mode in which the
U2000 accesses an NE. The implementation principles in different modes vary slightly from
each other.
Gateway Mode
Figure 21-25 illustrates how the OSI over DCC solution transfers U2000 messages to a nongateway NE when the U2000 adopts the gateway mode to access the NE.
Issue 03 (2012-11-30)

842
OptiX OSN 7500 II/7500/3500/1500

21 Outband DCN
Figure 21-25 Implementation principle of message transferring (gateway mode)

Application
TP4
ES-IS/CLNP
Ethernet
NMS
Application
TP4
Application
TP4
TP4
IS-IS/CLNP
IS-IS/CLNP
LAPD
LAPD
LAPD
DCC
DCC
DCC
Transfer NE
Destination NE
ES-IS/CLNP IS-IS/CLNP
Ethernet
Gateway NE

1.
As an ES, the U2000 first detects the gateway NE through the ES-IS routing protocol,
establishes a TP4 connection, and finally transfers application layer messages to the
gateway NE through the TP4 connection.
2.
The gateway NE extracts the messages from the OSI protocol stack and reports the
3.
The network layer of the gateway NE queries the address of the destination NE in the
in Figure 21-25 is OSI, the gateway NE transfers the messages to the transfer NE through
the OSI protocol stack.
4.
NE queries the destination NSAP address of the packet. If the NSAP address is not the
same as the address of the local station, the transfer NE queries the L1 routing table or the
L2 routing table according to the destination NSAP address to obtain the corresponding
route, and then transfers the packet.
5.
the application layer through the transport layer because the destination NSAP address of
the packet is the same as the address of the local station. The application layer acts according
to the message sent from the U2000.

Figure 21-26 illustrates how the OSI over DCC solution transfers U2000 messages to a
destination NE when the U2000 adopts the direct connection mode to access the NE.
Issue 03 (2012-11-30)

843
OptiX OSN 7500 II/7500/3500/1500

21 Outband DCN
Figure 21-26 Implementation principle of message transferring (direct connection mode)

Application
Application
TP4
TP4
ES-IS/CLNP
IS-IS/CLNP
IS-IS/CLNP
LAPD
LAPD
LAPD
DCC
DCC
DCC
IS-IS/ES-IS/CLNP
Ethernet
Ethernet
NMS
Transfer NE
Transfer NE
Destination NE
The original gateway NE in the direct connection mode acts as an ordinary transfer NE and the
message transferring is implemented at the network layer. This is different from the gateway
mode.

When using the OSI over DCC solution, plan the parameters of a DCN according to the situation
of the network.

This topic provides guidelines on how to plan the OSI over DCC solution.
This guide focuses on the differences between planning the OSI over DCC solution and planning
the HWECC solution. For the same parts, for example, for planning the NE ID and network
division, see Planning Guide.
When planning the OSI over DCC, comply with the following principles:
l
Only the node at the end of a network can be configured as an ES. The limited route
resources of an ES affect the network expansion. Therefore, it is not suggested to configure
the equipment as an ES. The U2000 works as an ES.
L1-IS is the default node type of Huawei products. It supports only intra-area routing (Level
1 routing).
If inter-area routing (Level 2 routing) is required, set the network node type of the equipment
to L2-IS. L2-IS maintains two routing tables at the same time: one is used for intra-area
routing and the other for inter-area routing.
The OptiX equipment supports IS-IS Level 2 routing. When the OSI communication
protocol is used, you need to divide the network into areas according to the network size.
The number of areas, also the number of Level 2 NEs, on the entire DCN cannot exceed
32. A gateway NE is a Level 2 NE. The number of NEs in the same area cannot exceed 50.
Configure the DCN as a ring to ensure that routes can be protected when a fiber is cut or
any anomaly occurs on the NE.
When the OptiX equipment interworks with the third-party equipment, comply with the
design principles for the third-party equipment as well during network planning.
When planning NSAP area addresses and layered routes, comply with the following principles:
Issue 03 (2012-11-30)

844
OptiX OSN 7500 II/7500/3500/1500

21 Outband DCN
The OSI protocol supports layered routing function. It uses the SYS ID of the system to achieve
intra-area routing, and uses the AREA ID to achieve inter-area routing. In the DCN planning,
divide the network into areas properly and decide the number of NEs in each area according to
the network topology.
If the number of NEs in a network is smaller than 50, you do not need to divide the network into
areas. In this case, set the node type of all NEs to L1-IS, and set the AREA IDs in the NSAP
area addresses of all NEs to the same value.
In the case of a large-scale network, comply with the following principles to divide the network:
l
Divide the DCN into several areas to manage.
Set several NEs in each area to L2-IS. Two NEs in each area are recommended because
the two can be of mutual backup.
In the DCN, all L2 equipment must be arranged in a continuous manner.
When planning gateway NEs, comply with the following principles:

l
When OSI over DCC is used to establish a DCN, the TP4 connection is required between
the U2000 and the gateway NE. The management data that the U2000 sends to non-gateway
NEs is forwarded by the gateway NE. When creating a gateway NE on the U2000, enter
the NE ID and the NSAP address. When creating a non-gateway NE, enter the NE ID and
specify a gateway NE for the NE.
When all nodes in the DCN network run the OSI protocol stack, do not configure all NEs
as gateway NEs. Configure certain NEs as gateway NEs. Configure the other NEs as nongateway NEs and specify a gateway NE for a non-gateway NE. The number of non-gateway
NEs under one gateway NE should not exceed 100, and it is recommended that the
maximum number should be 50. Otherwise, the gateway NE is overloaded, and the
performance of the U2000 is decreased.
Configure an NE that is close to the U2000 as a gateway NE. In this case, the communication
between the U2000 and the gateway NE requires fewer overheads and provides higher
efficiency.
When dividing a network to support layered routes, configure one or several NEs in each
area as gateway NEs. When creating a non-gateway NE, specify a gateway NE in the local
area for the NE.
To ensure the reliable communication between the U2000 and non-gateway NE, a backup
gateway NE is generally specified for a non-gateway NE.
When planning DCCs, comply with the following principles:

l
If the network is comprised of only the OptiX equipment, it is recommended that you use
bytes D1 to D3 in SDH frames as DCCs.
If the network is comprised of both OptiX equipment and the third-party SDH equipment,
use the DCC bytes that are used by the third-party equipment (for example, bytes D1 to D3
or D4 to D12) as DCCs.
For the two ends of a DCC, set the LAPD role to User at one end and to Network at the
other end.

This topic uses an example to describe how to plan the OSI over DCC solution.
Issue 03 (2012-11-30)

845
OptiX OSN 7500 II/7500/3500/1500

21 Outband DCN
Figure 21-27 Networking example for the OSI over DCC solution
NE302
NE303
Third-party
NMS
NE304
NE301
NE101
OSI DCN
NMS
NE102
NE201
NE202

Fiber link
Fiber
Network cable
third-party equipment that supports the OSI over DCC feature. The steps to plan the DCN are
as follows:
1.
Plan network areas according to the situation of the network.

Considering the number of the NEs, divide the entire DCN into three areas to make the
number of the NEs in each area smaller than 32. In addition, set the four NEs on the central
ring as L2 NEs to ensure that each area has an L2 NE and the L2 NEs are consecutive.
Issue 03 (2012-11-30)

846
OptiX OSN 7500 II/7500/3500/1500

21 Outband DCN
Figure 21-28 Allocation of NE areas

AREA ID: 0x394F1200
Area 3
Third-party
NMS
OSI DCN
L2
NMS
L2
L2
L2
Area 2
Area 1
AREA ID: 0x394F1190
2.
AREA ID: 0x394F1210
Select the gateway NE.

Select NE101, NE201, and NE301 as the gateway NEs to manage the OptiX NEs in their
own areas.
3.
Select the router that supports the OSI protocol stack to form the external DCN.
4.
Plan DCCs.
l As the third-party equipment uses the DCC bytes D1 to D3, it is not required to modify
the DCCs of the NEs.
l Set the LAPD role of each DCC to Network at the end nearer to the U2000 and to
User at the other end of the DCC.
21.4.6 Configuring OSI over DCC

Plan the DCC resource properly according to the configuration principle of the OSI over DCC
and configure the OSI over DCC by following the specified process to ensure the effective
supervision of the U2000 on the NEs.

The configuration of the OSI over DCC solution must comply with the process.
Figure 21-29 shows the configuration process of the OSI over DCC solution.
Issue 03 (2012-11-30)

847
OptiX OSN 7500 II/7500/3500/1500

21 Outband DCN
Figure 21-29 Configuration process of the OSI over DCC solution

Start
1
Configure IDs and

NSAP addresses
for NEs
2
Configure DCCs for
NEs
3
Configure node
types for NEs
4
Configure
communication
protocols and LAPD
roles for optical
interfaces
Query routing
information
6
Create OSI gateway
NEs
End
Table 21-5 Description of the configuration process of the OSI over DCC solution
Remarks
Description
Configure the network-wide data, including the NE IDs and the NE NSAP
addresses.
l The NE ID is set when an NE is created. For the configuration process,
see the Configuration Guide.
l For the process of configuring the NSAP address of an NE, see Setting the
NSAP Address of an NE.
The DCC protocol type of the line port should be set to OSI.
l The DCC channel type of the port should be the same as that of the thirdparty equipment. If the network is comprised of only the OptiX equipment,
set the DCC type to D1-D3.
Issue 03 (2012-11-30)

848
OptiX OSN 7500 II/7500/3500/1500

21 Outband DCN
Remarks
Description
You can set the node type to ES, L1-IS, or L2-IS for an NE according to the
network planning. For the configuration process, see Setting the Node Type
for an NE.
l If the currently enabled protocol is different from the planned one, you
can configure protocol on the U2000.
l For the two ends of a DCC, set the LAPD role to User at one end and to
Network at the other end. For the configuration process, see Configuring
the Communication Protocol Stack and LAPD Role for an Optical
Interface.
l The L1 routing table of the L1 NE has the routes to all the NEs in the area.
l The L1 routing table of the L2 NE has the routes to all the NEs in the area.
The L2 routing table of the L2 NE has the routes to other L2 NEs.
l The gateway NE has the route to the U2000 or the routes to the L2 NEs
that are in the same area as the U2000.
l The gateway NE has the routes to all non-gateway NEs.
l For the querying process, see Query Routing Information.
After configuring the preceding communication parameters and the

communication between nodes is normal, create the OSI gateway NE through
the TP4 connection mode by using the U2000. For the configuration process,
see Query Routing Information.

Prerequisites
l
Procedure
Tree.
Issue 03 (2012-11-30)

849
OptiX OSN 7500 II/7500/3500/1500

21 Outband DCN

NOTE
----End
Follow-up Procedure

parameters.
Prerequisites
l
Procedure
Issue 03 (2012-11-30)

850
OptiX OSN 7500 II/7500/3500/1500

21 Outband DCN
Step 3 Click Apply.

----End
21.4.6.4 Setting the NSAP Address of an NE

Set the NSAP area address of an NE according to the networking planning. The NSAP area
addresses of equipment in the same Level 1 area must be the same. The NSAP address
information can be set on the U2000.
Prerequisites
l
Context
If the U2000 establishes a TP4 connection with an NE, after you modify the NSAP area address
that was previously set according to network planning, the communication between the
U2000 and the gateway NE is interrupted. Therefore, you need to re-create the communication.
You can use the U2000 to create a TCP connection with an NE, set the NSAP area address for
the NE, and then modify the connection mode between the U2000 and the NE to TP4.
Issue 03 (2012-11-30)

851
OptiX OSN 7500 II/7500/3500/1500

21 Outband DCN
Procedure
Step 1 Select an NE in the NE Explorer. Choose Communication > Communication Parameters
Step 2 Set the NSAP Address.
Step 3 Click Apply and then click OK in the Warning dialog box that is displayed twice. Click
Close in the Operation Result dialog box.
----End

Prerequisites
l
Context
Procedure
Issue 03 (2012-11-30)

852
OptiX OSN 7500 II/7500/3500/1500

21 Outband DCN
NOTE
----End
Example
Parameter
Value Range
Default Value
Description
Port

clock interface
Channel Type
D1-D1, D1-D3, D4D12
D1-D1
It is recommended
that you use the
in the following
cases:
l When the IP over
DCC solution or
OSI over DCC
solution is
applied, set
Channel Type of
the SDH line
ports to the same
value as the
Channel Type of
third-party
network.
l When the DCC
transparent
transmission
solution is
applied, the
Channel Type of
the SDH line
ports cannot
conflict with the
channel type of
the third-party
network.
Issue 03 (2012-11-30)

853
OptiX OSN 7500 II/7500/3500/1500

21 Outband DCN
Parameter
Value Range
Default Value
Description
Protocol Type
HWECC, IP, OSI,

Auto
IP
It is recommended
that you use the
in the following
cases:
l When the
HWECC solution
is applied, set
Protocol Type to
HWECC.
l When the OSI
over DCC
solution is
applied, set
Protocol Type to
OSI.
LAPD Role
Network, User
Network
l This parameter is
valid only when
Protocol Type is
set to OSI.
l Set LAPD Role
to User at one end
of a DCC and to
Network at the
other end of the
DCC.
21.4.6.6 Setting the Node Type for an NE

Based on the network planning, you can set the node type to ES, L1 IS or L2 IS for an NE. For
easy expansion of the network, avoid the ES type.
Prerequisites
l
Context
For easy network expansion, the ES type is not recommended.
The setting takes effect only after the NE is reset.
Procedure
Step 1 Select an NE in the NE Explorer. Choose Communication > OSI Management from the
Function Tree.
Issue 03 (2012-11-30)

854
OptiX OSN 7500 II/7500/3500/1500

21 Outband DCN
Step 2 Click the Network Layer Parameters tab.

Step 3 Double-click Configuration Role and select a node type from the drop-down list.
Step 4 Click Apply and click OK in the Confirm dialog box.

Step 5 Click Close in the Operation Result dialog box.
----End
Issue 03 (2012-11-30)

855
OptiX OSN 7500 II/7500/3500/1500

21 Outband DCN
Parameters
Parameter
Value Range
Default Value
Description
Configuration Role
L2, L1, ES
L1
l The NE whose
Configuration
Role is set to L1
cannot be a
neighbor of an
NE in a different
area and is
involved only in
the routes in its
own area. It
issues a default
route that points
to its closest L2
NE and accesses
other areas
through the
default route.
l The NE whose
Configuration
Role is set to L2
can be a neighbor
of the L2 NE in a
different area and
can also be
involved in the
routes in the
backbone area.
The backbone
area is formed by
consecutive L2
NEs. That is, the
L2 NEs in the
backbone area
must be
consecutive
(connected).
21.4.6.7 Configuring the Communication Protocol Stack and LAPD Role for an
Optical Interface
If the protocol that is enabled for the optical interface of the NE by default is different from the
planned one, you can configure the protocol on the U2000.
Prerequisites
l
Issue 03 (2012-11-30)

856
OptiX OSN 7500 II/7500/3500/1500

21 Outband DCN
Procedure
Step 1 Select an NE in the NE Explorer. Choose Communication > DCC Management from the
Function Tree. Click the DCC Rate Configuration tab.
Step 2 Optional: Click Query. Click Close in the Operation Result dialog box.
Step 3 Select the optical interface that you want to set and click Delete. Click Yes in the Hint dialog
box. Click Close in the Operation Result dialog box.
Step 4 Click New and set the DCC parameters, protocol type, and LAPD role according to the network
planning in the dialog box that is displayed. For details, see Configuring DCCs.
Step 5 Click OK. Click Close in the Operation Result dialog box.
----End
21.4.6.8 Query Routing Information

By querying OSI routes, you can verify whether the configuration of the OSI over DCC feature
is correct and whether the DCC communication is normal.
Prerequisites
l
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Communication > OSI
Step 2 Click the Routing Table tab.
Step 3 Check whether the information in Link Adjacency Table meets the planning requirements.
Step 4 Click the L1 Routing tab to check whether the information of the L1 routes is correct.
Step 5 Click the L2 Routing tab to check whether the information of the L2 routes is correct.
----End
Follow-up Procedure
If the routing information of the node is incorrect, check the preceding configuration.
21.4.6.9 Creating an OSI Gateway NE

After configuring the communication parameters and the communication between nodes is
normal, create the OSI gateway NE through the TP4 connection mode by using the U2000.
Prerequisites
l
Issue 03 (2012-11-30)

857
OptiX OSN 7500 II/7500/3500/1500

21 Outband DCN
Procedure
Step 1 Choose Administration > DCN Management from the Main Menu. Click the GNE tab.
Step 2 Right-click a gateway NE and choose Modify GNE from the shortcut menu.
Step 3 In the Modify GNE dialog box, select OSI Gateway from the Gateway Type drop-down list,
and then enter NSAP Address.
Step 4 Click OK and then click Close in the Operation Result dialog box.
----End
21.4.7 Application Example for Hybrid Networking Based on OSI

over DCC
This topic takes an example to describe the method of configuring the OSI over DCC solution.
Precautions
NOTE
l This example provides only the configurations of the typical NEs: NE101, NE201, NE301, and NE302.
Procedure
Step 1 Set the IDs of the NEs. See Configuration Guide to create an NE.
Issue 03 (2012-11-30)
NE
Extended ID
NE ID
NE101
101
NE201
201
NE301
301
NE302
302

858
OptiX OSN 7500 II/7500/3500/1500

21 Outband DCN
Step 2 Set the NSAP address information for the NEs. See Setting the NSAP Address of an NE.
NE
NSAP Address
NE101
394F1190
NE201
394F1210
NE301
394F1200
NE302
394F1220
l Set Protocol for all the line ports of all the NEs to OSI.
l Set Channel Type for all the ports of all the NEs to D1-D3.
l Set the LAPD role to Network for the end of a DCC that is nearer to the U2000, and the
LAPD role to User for the other end of the DCC.
Step 4 Configure the CLNS roles for the NEs. See Setting the Node Type for an NE.
l The CLNS role of NE201 and NE302 is L1 (default value).
l The CLNS role of NE101 and NE301 is L2.
Step 5 Query the OSI routes. See Query Routing Information.
l In the L1 routing table, NE101, NE201, NE301, and NE302 have the routes to all the NEs
that are in their respective areas.
l In the L2 routing table, NE101 and NE301 have the routes to other L2 NEs.
----End
Result
All NEs can be successfully created. The communication between the U2000 and NEs is normal.
21.5 Hybrid Networking Solution of DCC Transparent

Transmission
When interworking with the third-party equipment, the OptiX equipment can transparently
transmit the OAM information of the third-party equipment through the DCC physical channel
so that the third-party equipment can traverse the Huawei DCN to communicate with the NMS
of the third party; the OAM information of the OptiX equipment can also be transparently
transmitted by the DCC physical channel of the third-party equipment so that the OptiX
equipment can communicate with the U2000.

In general, the transmission equipment uses only bytes D1 to D3 as DCCs and does not use other
DCC bytes. Based on this feature, the DCC transparent transmission solution adopts different
DCCs to transmit the NM messages of different vendors to achieve the communication between
NM messages.
Issue 03 (2012-11-30)

859
OptiX OSN 7500 II/7500/3500/1500

21 Outband DCN
When DCC bytes are used to transparently transmit NM messages, there are two networking
scenarios:
l
The OptiX equipment is at the edge of a network.
The OptiX equipment is in the center of a network.
OptiX Equipment at the Edge of a Network

The two situations for this networking scenario are as follows:
l
The third-party equipment uses bytes D1 to D3 as DCCs.

In this case, the OptiX equipment uses bytes D4 to D12 as DCCs. In addition, you need to
add a route to transparently transmit bytes D4 to D12 in the transmission network of the
third-party equipment.
Figure 21-30 DCC transparent transmission solution when the OptiX equipment is at the
edge of a network (1)
D4-D12
D4-D12
D4-D12
D4-D12
D4-D12
D4-D12
OptiX equipment
Third-party
equipment

In this case, the OptiX equipment still uses bytes D1 to D3 as DCCs. In addition, you need
to add a route to transparently transmit bytes D1 to D3 in the transmission network of the
third-party equipment.
Issue 03 (2012-11-30)

860
OptiX OSN 7500 II/7500/3500/1500

21 Outband DCN
Figure 21-31 DCC transparent transmission solution when the OptiX equipment is at the
edge of a network (2)
D1-D3
D1-D3
D1-D3
D1-D3
D1-D3
D1-D3
Third-party
equipment
OptiX equipment
OptiX Equipment in the Center of a Network

The two situations for this networking scenario are as follows:
l

In this case, the OptiX equipment uses bytes D4 to D12 as DCCs. In addition, you need to
add a route to transparently transmit bytes D1 to D3.
Figure 21-32 DCC transparent transmission solution when the OptiX equipment is in the
center of a network (1)
D1-D3
D1-D3
D1-D3
D1-D3
D1-D3
D1-D3
OptiX equipment
Issue 03 (2012-11-30)
Third-party
equipment

861
OptiX OSN 7500 II/7500/3500/1500

21 Outband DCN

In this case, the OptiX equipment still uses bytes D1 to D3 as DCCs. In addition, you need
to add a route to transparently transmit bytes D4 to D12.
Figure 21-33 DCC transparent transmission solution when the OptiX equipment is in the
center of a network (2)
D4-D12
D4-D12
D4-D12
D4-D12
D4-D12
D4-D12
OptiX equipment
Third-party
equipment
21.5.2 Availability
The DCC transparent transmission solution requires the support of the applicable equipment,
Version Support
Issue 03 (2012-11-30)
Applicable Version
OptiX OSN 1500/2500/3500/7500
V100R003 and later
T2000
V200R002 and later
U2000
Applicable Version
OptiX OSN 3500 II
V100R009 and later
T2000
U2000

862
OptiX OSN 7500 II/7500/3500/1500

21 Outband DCN
Applicable Version
OptiX OSN 7500 II
U2000
Hardware Support
Applicable Board
Applicable Version
N4GSCC
OptiX OSN 3500/7500
N6GSCC
OptiX OSN 3500/7500
N1PSXCS
OptiX OSN 3500
N2PSXCSA
OptiX OSN 3500
T1PSXCSA
OptiX OSN 7500
R1PCXLN
TNN1PSXCS
OptiX OSN 7500 II
TNN1SCA
OptiX OSN 7500 II
N1SXCSA
OptiX OSN 3500
N3PSXCSA
OptiX OSN 3500

If you adopt the DCC transparent transmission solution to communicate NM messages when
the OptiX equipment is used together with the third-party equipment to form a network, you can
use any of the HWECC protocol stack, IP protocol stack, and OSI protocol stack to manage the
OptiX equipment. It is recommended that you use the HWECC protocol stack.
21.5.4 Principles
The OptiX equipment realizes the transparent transmission of DCC through the overhead crossconnect matrix.
In the receive direction:
1.
Issue 03 (2012-11-30)
The line board extracts the overhead bytes such as DCC bytes from the received SDH
signals, forms a 2.048 Mbit/s overhead signal stream, and sends the overhead signal stream
to the overhead cross-connect matrix of the SCC board through the overhead bus.

863
OptiX OSN 7500 II/7500/3500/1500

21 Outband DCN
2.
The overhead cross-connect matrix transports the DCC bytes that the NE uses to the CPU
and directly transports the DCC bytes that are to be transparently transmitted, to the
overhead bus of the corresponding line board.
3.
The CPU processes the NM messages carried by the DCC bytes according to the protocol
stack of the DCCs.
In the transmit direction:

1.
The CPU of the SCC board encapsulates the NM messages into the DCC bytes according
to the protocol stack and transmits the DCC bytes to the overhead cross-connect matrix of
the SCC board.
2.
The overhead cross-connect matrix combines the DCC bytes sent from the CPU and other
overhead bytes (including the DCC bytes sent from the other line boards and orderwire
bytes) to form a 2.048 Mbit/s overhead signal stream, and then transmits the overhead signal
stream to the corresponding line board.
3.
The line board extracts the overhead signal from the overhead signal stream, inserts the
overhead signal into the SDH signal, and sends the SDH signal to other NEs.
Figure 21-34 illustrates how an NE uses bytes D1 to D3 as DCCs to transparently transmit bytes
D4 to D12.
Figure 21-34 Implementation principle of the DCC transparent transmission
D4-D12
Overhead
bus
SDH
signal
Overhead crossconnect matrix

D1-D3
Overhead
bus
SDH
signal
CPU
Line
board
SCC
board
Line
board

When using the DCC transparent transmission solution, plan the parameters of a DCN according
to the situation of the network.

This topic provides guidelines on how to plan the DCC transparent transmission solution.
This guide focuses on the differences between planning the DCC transparent transmission
solution and planning the HWECC solution. For the same parts, for example, for planning the
gateway NE and external DCN, see Planning Guide.
When planning the DCC, comply with the following principles:
Issue 03 (2012-11-30)

864
OptiX OSN 7500 II/7500/3500/1500

21 Outband DCN
If the third-party equipment uses bytes D1 to D3 as DCCs, the port of the OptiX NE uses
bytes D4 to D12 as DCCs.
If the third-party equipment uses bytes D4 to D12 as DCCs, the port of the OptiX NE uses
bytes D1 to D3 as DCCs.

This topic uses an example to describe how to plan the DCC transparent transmission solution.
Figure 21-35 Networking example for the DCC transparent transmission solution
Third-party
NMS
NE1
NE4
NMS
NE2
NE3

Network cable
Fiber
third-party equipment that supports the DCC transparent transmission feature. The procedure
for planning the DCN is as follows:
1.
Plan DCCs.
As the third-party equipment uses bytes D1 to D3 as DCCs, the OptiX NE uses bytes D4
to D12 as DCCs.
2.
Issue 03 (2012-11-30)
Allocate IDs to the NEs and configure the IP address for the gateway NE.

865
OptiX OSN 7500 II/7500/3500/1500

21 Outband DCN
Figure 21-36 Allocate IDs and IP addresses to all NEs
Third-party
NMS
NMS
9-1
10.0.0.1
0.0.0.0
9-4
129.9.0.4
0.0.0.0
9-2
129.9.0.2
0.0.0.0
9-3
129.9.0.3
0.0.0.0
IP address
Gateway
3.
Configure NE1, NE2, NE3, and NE4 to transparently transmit bytes D1 to D3.
21.5.6 Configuring DCC Transparent Transmission

Plan the DCC resource properly according to the configuration principle of the DCC transparent
transmission solution and configure the DCC transparent transmission by following the specified
process.

The configuration of the DCC transparent transmission solution must comply with the process.
Issue 03 (2012-11-30)

866
OptiX OSN 7500 II/7500/3500/1500

21 Outband DCN
Figure 21-37 Configuration process of the DCC transparent transmission solution

Start
1
Set IDs and IP

addresses for NEs
Configure
DCCs for NEs
3
Set DCC transparent
transmission
4
Query ECC routes at
the gateway NE
End
Table 21-7 Description of the configuration process of the DCC transparent transmission
solution
Number
Description
l When setting the IP address information for the gateway NE, you may
need to set the default gateway in addition to setting the IP address and
subnet mask, according to the situation of the external DCN.
l For the process of configuring the ID of an NE, see Changing the ID of an
NE.
l For the process of configuring the IP address of an NE, see Setting
Communication Parameters of an NE.
l The DCC protocol type of the line port should be set to HWECC.
l When the third-party equipment uses bytes D1 to D3 as DCCs, set the
DCC channel type of the SDH port to D4-D12.
l When the third-party equipment uses bytes D4 to D12 as DCCs, set the
DCC channel type of the SDH port to D1-D3.
l Set the DCC transparent transmission bytes used by the third-party

equipment for all the NEs on the planned route.
l For the configuration process, see Configuring DCC Transparent
Transmission.
Issue 03 (2012-11-30)

867
OptiX OSN 7500 II/7500/3500/1500

21 Outband DCN
Number
Description
l There is an ECC route between the gateway NE and each of its managed
non-gateway NEs.
l For the querying process, see Querying the ECC Routes of an NE.

Prerequisites
l
Procedure
Tree.

NOTE
----End
Follow-up Procedure

parameters.
Issue 03 (2012-11-30)

868
OptiX OSN 7500 II/7500/3500/1500

21 Outband DCN
Prerequisites
l
Procedure
Step 3 Click Apply.

----End

Prerequisites
l
Issue 03 (2012-11-30)

869
OptiX OSN 7500 II/7500/3500/1500

21 Outband DCN
Context
Procedure
NOTE
----End
Example
Issue 03 (2012-11-30)
Parameter
Value Range
Default Value
Description
Port

clock interface

870
OptiX OSN 7500 II/7500/3500/1500

21 Outband DCN
Parameter
Value Range
Default Value
Description
Channel Type
D1-D1, D1-D3, D4D12
D1-D1
It is recommended
that you use the
in the following
cases:
l When the IP over
DCC solution or
OSI over DCC
solution is
applied, set
Channel Type of
the SDH line
ports to the same
value as the
Channel Type of
third-party
network.
l When the DCC
transparent
transmission
solution is
applied, the
Channel Type of
the SDH line
ports cannot
conflict with the
channel type of
the third-party
network.
Protocol Type
HWECC, IP, OSI,

Auto
IP
It is recommended
that you use the
in the following
cases:
l When the
HWECC solution
is applied, set
Protocol Type to
HWECC.
l When the OSI
over DCC
solution is
applied, set
Protocol Type to
OSI.
Issue 03 (2012-11-30)

871
OptiX OSN 7500 II/7500/3500/1500

21 Outband DCN
Parameter
Value Range
Default Value
Description
LAPD Role
Network, User
Network
l This parameter is
valid only when
Protocol Type is
set to OSI.
l Set LAPD Role
to User at one end
of a DCC and to
Network at the
other end of the
DCC.
21.5.6.5 Configuring DCC Transparent Transmission

The OptiX equipment supports the DCC transparent transmission function. With this function,
the equipment can transparently transmit NM messages when the OptiX equipment is used
together with other equipment to form a network and can also transparently transmit the
management messages between ECC subnets.
Prerequisites
l
NE must be normal.
Procedure
Step 2 Click the DCC Transparent Transmission Management tab.
Step 3 Click New. The system displays the Create DCC Transparent Transmission Byte dialog box.
Step 4 Set the parameters of the DCC transparent transmission byte.
----End
Issue 03 (2012-11-30)

872
OptiX OSN 7500 II/7500/3500/1500

21 Outband DCN
Parameters
Parameter
Value Range
Default Value
Description
Source Timeslot/
Port
Line ports
Transparent
Transmission of
Overhead Byte at
Source Port
D1, D2, D3, D4, D5,

D6, D7, D8, D9,
D10, D11, D12, E1,
E2, X1, X2, X3, X4
D1
l Only one
overhead byte can
be selected at a
time.
l X1, X2, X3, and
X4 represent the
self-defined
overhead bytes
that are used
when
asynchronous
data services are
transmitted.
l The overhead
byte must not be a
used byte (for
example, the byte
used by a DCC
that is in use).
Sink Timeslot/Port
Issue 03 (2012-11-30)
Line ports

873
OptiX OSN 7500 II/7500/3500/1500

21 Outband DCN
Parameter
Value Range
Default Value
Description
Transparent
Transmission of
Overhead Byte at
Sink Port
D1, D2, D3, D4, D5,

D6, D7, D8, D9,
D10, D11, D12, E1,
E2, X1, X2, X3, X4
D1
l Only one
overhead byte can
be selected at a
time.
l The overhead
byte must not be a
used byte (for
example, the byte
used by a DCC
that is in use).
l Generally,
Transparent
Transmission of
Overhead Byte
at Sink Port is set
to the same value
as Transparent
Transmission of
Overhead Byte
at Source Port.
These two
parameters,
however, can be
set to different
values.
21.5.6.6 Querying the ECC Routes of an NE

By querying ECC routes, you can verify whether the ECC configuration is correct and whether
the DCC communication is normal.
Prerequisites
l
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Communication > NE ECC
Link Management from the Function Tree.
Step 2 Click Refresh and the ECC routes of the NE is displayed in the NE ECC Link Management
Table.
Step 3 Check whether the ECC routes and their parameters in NE ECC Link Management Table are
the same as the planned information.
Issue 03 (2012-11-30)

874
OptiX OSN 7500 II/7500/3500/1500

21 Outband DCN
Step 4 Optional: Click Add Manual Route to add manual ECC routes of the NE.
----End
21.5.7 Application Example for Hybrid Networking Based DCC

Transparent Transmission
This topic takes an example to describe the method of configuring the DCC transparent
transmission solution.
Precautions
NOTE
l This example provides only the configurations of the typical NEs: NE1 and NE3.
Procedure
Step 1 Set the IDs of the NEs. See Changing the ID of an NE.
l NE1
NE ID: 1; extended ID: 9
l NE3
NE ID: 3; extended ID: 9
Step 2 Set the IP address information for NE1. See Setting Communication Parameters of an NE.
l IP address: 10.0.0.1
l Subnet mask: 255.255.0.0
l Default gateway: 0.0.0.0 (default value)
l Set the DCC protocol type of all the line ports of all NEs to HWECC.
l Set the DCC channel type of all SDH ports of all NEs to D4-D12.
Step 4 Configure the transparent transmission between bytes D1 to D3 of the west line port of an NE
and bytes D1 to D3 of the east line port of the NE. Perform the configuration for all NEs. See
Configuring DCC Transparent Transmission.
Step 5 Query the ECC routes on NE1. See Querying the ECC Routes of an NE.
NE1 should have ECC routes to NE2, NE3, and NE4.
----End
Issue 03 (2012-11-30)

875
OptiX OSN 7500 II/7500/3500/1500

21 Outband DCN
21.6 Transparent Transmission of DCC Bytes Through the

External Clock Interface
in which the external clock interface is used to embed the DCC bytes to a specified E1 service
that traverses a third-party network. When this solution is used, the transmission bandwidth of
one E1 service is occupied. The solution can be used if management messages need to traverse
third-party equipment but none of OSI over DCC, IP over DCC, and DCC transparent
transmission is supported.
21.6.1 Solution Description

Transparent transmission of DCC bytes through the external clock interface supports two access
modes for networking: direct access and indirect access.
in which the external clock interface is used to embed the DCC bytes to certain timeslots of a
specified E1 service that traverses a third-party network as long as this third-party network can
transmit the E1 service. In this manner, the DCC bytes are transmitted transparently.
Transparent transmission of DCC bytes through the external clock interface supports two access
modes for networking:
l
Direct access mode

The E1 service enters the third-party network directly through the external clock interface
provided by an NE.
Indirect access mode

The E1 service enters the third-party network through the SDH interface provided by the
third-party network.
Direct Access Mode

Figure 21-38 shows the networking based on transparent transmission of DCC bytes through
the external clock interface in direct access mode. NE1 and NE2 at the two ends provide two
external clock interfaces, and the third-party network provides two E1 interfaces for NE1 and
NE2 that are connected to the third-party network through E1 cables. The third-party network
regards the E1 service as an ordinary service and transmits it transparently. In this manner, the
DCC bytes are transmitted transparently between the two NEs.
Issue 03 (2012-11-30)

876
OptiX OSN 7500 II/7500/3500/1500

21 Outband DCN
Figure 21-38 Networking based on transparent transmission of DCC bytes through the external
clock interface in direct access mode
External clock
interface
External clock
interface
E1 interface
E1 interface
DCC bytes
Third-party network
E1 cable
DCC bytes
E1 cable
NE1
NE2
Indirect Access Mode

Figure 21-39 shows the networking based on transparent transmission of DCC bytes through
the external clock interface in indirect access mode. The third-party network provides two SDH
interfaces for NE1 and NE2 at the two ends. The external interfaces on NE1 and NE2 are
connected through E1 cables to the E1 interfaces on a tributary board. Then, the crossconnections between the E1 services and the tributary board are configured so that the E1 services
enter the third-party network through the SDH interfaces. The third-party network regards the
E1 service as an ordinary service and transmits it transparently. In this manner, the DCC bytes
are transmitted transparently between the two NEs.
Figure 21-39 Networking based on transparent transmission of DCC bytes through the external
clock interface in indirect access mode
E1 interface
E1 interface
SDH interface
SDH interface
E1 cable
DCC bytes
E1 cable
SDH interface
SDH interface
Third-party network
NE1
DCC bytes
NE2
External clock interface
External clock interface
21.6.2 Availability
The DCC transparent transmission through the external interface solution requires the support
of the applicable equipment and boards.
Issue 03 (2012-11-30)

877
OptiX OSN 7500 II/7500/3500/1500

21 Outband DCN
Version Support
Applicable Version
OptiX OSN 1500/2500
V100R003 and later
T2000
V200R002 and later
U2000
Applicable Version
OptiX OSN 3500 II
V100R009 and later
T2000
U2000
Hardware Support
Applicable Board
Applicable Version
R1PCXLN
Remarks
On the OptiX OSN 1500, the AUX board provides the external clock interface.
21.6.3 Relationship with Other Features

When transparent transmission of DCC bytes through the external clock interface is adopted, if
Huawei OptiX equipment is interconnected with third-party equipment, the HWECC, IP over
DCC, or OSI over DCC protocol stack can be used to manage the OptiX equipment. It is
recommended that you use HWECC.
21.6.4 Principles
The OptiX equipment uses the overhead processing unit and the CPU to transparently transmit
DCC bytes through the external clock interface.
In the receive direction:
1.
The external clock interface regards the received E1 services as 2.048 Mbit/s overhead
signals, and sends them over the overhead bus to the overhead processing unit.
2.
The overhead processing unit sends the DCC bytes that the local NE uses to the CPU.
3.
The CPU processes the network management messages carried by the DCC bytes according
to the protocol stack for the DCC.
In the transmit direction:

Issue 03 (2012-11-30)

878
OptiX OSN 7500 II/7500/3500/1500

21 Outband DCN
1.
The CPU encapsulates the network management messages into the DCC bytes according
to the protocol stack for the DCC, and sends them to the overhead processing unit.
2.
The overhead processing unit combines the DCC bytes received from the CPU and other
overhead bytes (such as overhead bytes for orderwire and synchronous/asynchronous data
services) into 2.048 Mbit/s overhead signals, and sends them to the external clock interface.
3.
The external clock interface sends the 2.048 Mbit/s overhead signals as E1 services to a
peripheral device.
Figure 21-40 shows the mechanism of transparent transmission of DCC bytes through the
external clock interface. As shown in the figure, the D1-D3 bytes are used to carry network
management messages.
Figure 21-40 Mechanism of transparent transmission of DCC bytes through the external clock
interface
E1 services
External
clock
interface
Auxiliary
board
Overhead
bus
Overhead
processing
unit
D1D3
CPU
SCC

When transparent transmission of DCC bytes through the external clock interface is adopted,
the DCN parameters should be planned according to the networking situation.

This topic provides guidelines on how to plan the DCC transparent transmission through the
external clock interface solution.
1.
Planning of the access mode:

l If the third-party network provides the E1 interface for the OptiX equipment, use the
direct access mode.
l If the third-party network provides the SDH interface for the OptiX equipment, use the
indirect access mode.
2.
Issue 03 (2012-11-30)
Planning of the DCC byte for carrying the network management messages:
879
OptiX OSN 7500 II/7500/3500/1500

21 Outband DCN
The two NEs at the two ends should use the same DCC bytes that are transmitted
transparently over the third-party network. The D1-D3 bytes are recommended.
3.
Planning of transmission of E1 services that carry the DCC bytes over the third-party
network:
The two NEs at the two ends should use the same DCC bytes. The DCC bytes are transmitted
transparently over the third-party network between the two NEs. The D1-D3 bytes are
recommended.

This topic uses an example to describe how to plan the DCC transparent transmission through
the external clock interface solution.
Figure 21-41 shows an example of networking for planning transparent transmission of DCC
bytes through the external clock interface. The third-party network provides an E1 interface for
NE1 and an SDH interface for NE2. The process of the planning is as follows:
1.
Plan the access mode.

NE1 is directly connected to the third-party network, and NE2 is indirectly connected to
the third-party network.
2.
Plan the DCC byte for carrying the network management messages.
The D1-D3 bytes are used to transmit network management messages between NE1 and
NE2.
3.
Plan transmission of E1 services that carry the DCC bytes over the third-party network.
Between NE1 and the third-party network, the DCC bytes travel over an E1 cable. Between
NE2 and the third-party network, the DCC bytes travel over a fiber.
l The E1 services that carry the DCC bytes of NE1 travel from NE1 to the third-party
network through the external clock interface and over the E1 cable.
l The E1 services are transmitted transparently over the third-party network.
l The E1 services that carry the DCC bytes of NE2 travel from NE2 through the external
clock interface and over the E1 cable to the tributary board where the E1 services are
encapsulated into a VC-12 that is transmitted to the third-party network.
Figure 21-41 Example of networking for planning transparent transmission of DCC bytes
through the external clock interface
E1 interface
SDH interface
NM
DCC bytes
E1 cable
SDH interface
E1 interface
Third-party network
DCC bytes
E1 cable
NE1
NE2
External clock
interface
Issue 03 (2012-11-30)

External clock
interface
880
OptiX OSN 7500 II/7500/3500/1500

21 Outband DCN
21.6.6 Configuring Transparent Transmission of DCC Bytes

Through the External Clock Interface
Plan the DCC resource properly according to the configuration principle of the Transparent
Transmission of DCC Bytes Through the External Clock Interface solution and configure the
Transparent Transmission of DCC Bytes Through the External Clock Interface by following the
specified process.

Before you configure transparent transmission of DCC bytes through the external clock
interface, you need to set the DCC of the external clock interface. Then, determine whether to
configure cross-connections for E1 services according to the access mode.
Figure 21-42 shows the process of configuring transparent transmission of DCC bytes through
the external clock interface.
Figure 21-42 Configuration process of the DCC transparent transmission through the external
clock interface solution
Start
Set the DCC of

the external clock
interface
Indirect
access mode
adopted?
No
Yes
Configure
cross-connections
for E1 services
End
Issue 03 (2012-11-30)

881
OptiX OSN 7500 II/7500/3500/1500

21 Outband DCN
Table 21-9 Description of the configuration process of the DCC transparent transmission
through the external clock interface solution
Procedure
Notes
l Set Enabled Status of the external clock interface to Enabled.

l It is recommended that you set Channel Type to D1-D3.
l It is recommended that you set Protocol Type to HWECC.
l For details on the configuration process, see Configuring DCCs.
l Configure bidirectional cross-connections between the SDH
interface and the E1 interface that is connected to the external
clock interface.
NOTE
Configure cross-connections for the E1 service only when the indirect
access mode is adopted.
l For details on the configuration process, see Configuring a CrossConnection for E1 Services.

Prerequisites
l
Context
Procedure
Issue 03 (2012-11-30)

882
OptiX OSN 7500 II/7500/3500/1500

21 Outband DCN
NOTE
----End
Example
Issue 03 (2012-11-30)
Parameter
Value Range
Default Value
Description
Port

clock interface

883
OptiX OSN 7500 II/7500/3500/1500

21 Outband DCN
Parameter
Value Range
Default Value
Description
Channel Type
D1-D1, D1-D3, D4D12
D1-D1
It is recommended
that you use the
in the following
cases:
l When the IP over
DCC solution or
OSI over DCC
solution is
applied, set
Channel Type of
the SDH line
ports to the same
value as the
Channel Type of
third-party
network.
l When the DCC
transparent
transmission
solution is
applied, the
Channel Type of
the SDH line
ports cannot
conflict with the
channel type of
the third-party
network.
Protocol Type
HWECC, IP, OSI,

Auto
IP
It is recommended
that you use the
in the following
cases:
l When the
HWECC solution
is applied, set
Protocol Type to
HWECC.
l When the OSI
over DCC
solution is
applied, set
Protocol Type to
OSI.
Issue 03 (2012-11-30)

884
OptiX OSN 7500 II/7500/3500/1500

21 Outband DCN
Parameter
Value Range
Default Value
Description
LAPD Role
Network, User
Network
l This parameter is
valid only when
Protocol Type is
set to OSI.
l Set LAPD Role
to User at one end
of a DCC and to
Network at the
other end of the
DCC.
21.6.6.3 Configuring a Cross-Connection for E1 Services

To add E1 services from a tributary board to a line board or to drop the E1 services from the line
board to the tributary board, cross-connections for the E1 services should be configured so that
the E1 services can be transmitted over an SDH network.
Prerequisites
l
Procedure
Step 1 Click the NE in the NE Explorer, and choose Configuration > SDH Service Configuration
Step 2 Click New, and set the necessary parameters in the Create SDH Service dialog box displayed.
Issue 03 (2012-11-30)

885
OptiX OSN 7500 II/7500/3500/1500

21 Outband DCN
Step 3 Click OK.

----End
21.6.7 Example of Hybrid Networking Based on Transparent

Transmission of DCC Bytes Through the External Clock Interface
On a hybrid network based on transparent transmission of DCC bytes through the external clock
interface, two NEs of an operator are connected to a third-party network through an E1 interface
and an SDH interface respectively.
Prerequisites
l
The physical network topology must be created.
The external clock interface planned for transparent transmission of DCC information must
not be used as a clock signal interface.
The signal mode of the external clock must be set to 2 Mbit/s.
You must be an NM user with "NE and network operator" authority or higher.
For the parameters in this example, see the example in Network Planning.
Context
Procedure
l Set Channel Type to D1-D3.
l Set Protocol Type to HWECC.
Step 2 Configure cross-connections for E1 services on NE2. See Configuring a Cross-Connection for
E1 Services.
----End
21.7 DCN Maintenance

This chapter describes the troubleshooting, maintenance cases, and relevant alarms and
performance events of the DCN.
When the DCN is faulty, the U2000 is unreachable. This topic describes the troubleshooting of
common DCN faults.
21.7.1.1 A Single NE Being Unreachable

This topic describes the symptoms, impact, and possible causes of a single unreachable network
element (NE). In addition, this topic describes the required tools, precautions, and procedures
for rectifying the fault.
Issue 03 (2012-11-30)

886
OptiX OSN 7500 II/7500/3500/1500

21 Outband DCN
Symptom
On the U2000, a single NE is unreachable and the other NEs of the same site are reachable.
Impact on System
The unreachable NE cannot be managed.
Possible Causes
l
Cause 1: The password for an NE user is incorrect.
Cause 2: The hardware is faulty.
Cause 3: The system control board is faulty.
Cause 4: The IP address or the ID of the NE is incorrectly set.
Cause 5: The fibers are faulty.
Cause 6: The data communications channel (DCC) of the optical interface is disabled.
Cause 7: The NE software fails.
Cause 8: The network size is too large, and the embedded control channel (ECC)
communication between NEs exceeds the processing capability of the NEs.
Cause 9: The D1-D3 bytes for DCC communication are deleted.

l
U2000 LCT
U2000
Procedure
Step 1 Cause 1: The password for an NE user is incorrect.
1.
Check whether the entered password is correct. If the password is incorrect, enter the correct
password.
2.
Check whether the NE recovers. If the NE does not recover, check whether the fault occurs
due to other causes.
Step 2 Cause 2: The hardware is faulty. As a result, the NE is unreachable.

1.
2.
Issue 03 (2012-11-30)
Check whether the external power supply device is working in the normal state.
If...
Then...
The external power supply device is faulty
Refer to Service Interruptions Caused by

Power Supply Failures to rectify the fault
of the external power supply device. Check
whether the NE recovers. If the NE does
not recover, proceed to the next step.
The external power supply device is

working in the normal state
Check whether the power board is working in the normal state.

887
OptiX OSN 7500 II/7500/3500/1500

3.
21 Outband DCN
If...
Then...
The power board is faulty
Replace the faulty board. Check whether

the NE recovers. If the NE does not
The power board is working in the normal

state
Log in to the NE through the U2000 LCT.

If...
Then...
You fail to log in to the NE through the

U2000 LCT
The SCC board or CXL board of the NE is

faulty. Replace the faulty board. Check
whether the NE recovers. If the NE does
not recover, check whether the fault occurs
You successfully log in to the NE through

the U2000 LCT
Check whether the fault occurs due to other

causes.
Step 3 Cause 3: The system control board is faulty.

1.
Reset the system control board. Then, check whether the services are restored. If the
services are not restored, check whether the fault occurs due to other causes.
2.
Replace the faulty board. Then, check whether the services are restored. If the services are
not restored, check whether the fault occurs due to other causes.
Step 4 Cause 4: The IP address or the ID of the NE is incorrectly set. As a result, the NE is
unreachable.
1.
Log in to the NE through the U2000 LCT and restore the original IP address and ID of the
NE according to the record.
2.
Step 5 Cause 5: The fibers are faulty. As a result, the NE is unreachable.

1.
Use the optical time domain reflectometer (OTDR) meter to test the fiber. Analyze the line
attenuation curve displayed by the meter to determine whether fiber cut occurs on the line.
For how to use the meter, see the OTDR user guide.
If...
Then...
Fiber cut occurs on the line
Replace the faulty fiber. Then, check

whether the service is restored. If not,
check whether the fault occurs due to other
causes.
Fiber cut does not occur on the line

causes.
Step 6 Cause 6: The DCC of the optical interface is disabled.

Issue 03 (2012-11-30)

888
OptiX OSN 7500 II/7500/3500/1500

1.
21 Outband DCN
Check whether the DCC of the optical interface is disabled or enabled.

If...
Then...
The DCC of the optical interface is

disabled
Enable the DCC of the optical interface.

Then, check whether the NE recovers. If
not, proceed to the next step.
The DCC of the optical interface is

enabled

causes.
Step 7 Cause 7: The NE software fails. As a result, the NE is unreachable.

1.
Browse alarms and determine the board that reports the alarm.
2.
Load the NE software to the board, and perform a warm reset on the board. Then, check
whether the alarm is cleared.
3.
Check whether the NE recovers. If not, proceed to other causes.
Step 8 Cause 8: The network size is too large, and the ECC communication between NEs exceeds
the processing capability of the NEs.
1.
Check the number of NEs at a single station. When multiple devices are connected through
a hub (or by means of inter-subrack cascading ports) and communicate with each other by
using the extended ECC function of the network port, it is recommended that you enable
automatic extended ECC function for not more than four devices connected to the same
hub and that you enable the manual extended ECC function if more than four devices are
connected to the same hub, to prevent ECC storms.
2.
Contact Huawei technical support engineers to check whether the data communication
network (DCN) communication between NEs exceeds the processing capability of the NEs.
3.
Step 9 Cause 9: The D1-D3 bytes for DCC communication are deleted.
1.
Ensure that the DCC function is enabled for NEs.
2.
Ensure that the DCC channel mode is D1-D3.
3.
Check whether the services are restored. If the services are not restored, contact Huawei
technical support engineers.
----End
Related Information
None.
21.7.1.2 All NEs of the Subnet Being Unreachable

This topic describes the symptoms, impact, and possible causes of all network elements (NEs)
of the subnet unreachable. In addition, this topic describes the required tools, precautions, and
procedures for rectifying the fault.
Symptom
On the U2000, all NEs of a certain subnet are unreachable.
Issue 03 (2012-11-30)

889
OptiX OSN 7500 II/7500/3500/1500

21 Outband DCN
Impact on System
The unreachable NEs cannot be managed.
Possible Causes
l
Cause 1: The password for an NE user is incorrect.
Cause 2: The gateway NE is faulty.
Cause 3: The network cables connections between the gateway NE and the hub are
interrupted or the hub ports are faulty.
Cause 4: The IP addresses or the IDs of the gateway NE is changed by mistake.
Cause 5: The fibers are faulty or connected improperly.
Cause 6: The system control board of the gateway NE is faulty.
Cause 7: The network size is too large, and the embedded control channel (ECC)
communication between NEs exceeds the processing capability of the NEs.

l
U2000 LCT
Cable testing meter
Procedure
Step 1 Cause 1: The password for an NE user is incorrect.
1.
Check whether the entered password is correct. If the password is incorrect, enter the correct
password.
2.
Step 2 Cause 2: The gateway NE is faulty, and there is no standby gateway NE. As a result, the
NEs are unreachable.
1.
2.
Issue 03 (2012-11-30)
Check whether the external power supply device is working in the normal state.
If...
Then...
The external power supply device is faulty
See Service Interruptions Caused by Power

Supply Failures to rectify the fault of the
external power supply device. Check
whether the NEs recover. If the NEs do not
The external power supply device is

working in the normal state
Check whether the power board is working in the normal state.

If...
Then...
The power board is faulty
Replace the faulty power board. Check


890
OptiX OSN 7500 II/7500/3500/1500

3.
4.
21 Outband DCN
If...
Then...
The power board is working in the normal

state
Log in to the NEs through the U2000 LCT.

If...
Then...
You fail to log in to the NEs through the

U2000 LCT
The system control boards of the NEs are

faulty. Replace the faulty boards. Check
recover, check whether the fault occurs due
to other causes.
You log in to the NEs through the U2000

LCT successfully

causes.
Check whether the Ethernet port fails.

If...
Then...
The Ethernet port fails
Replace the board where the Ethernet port

resides. Check whether the NE recovers. If
the NE does not recover, proceed to other
causes.
The Ethernet port works normally
Proceed to other causes.
Step 3 Cause 3: The network cables connections between the gateway NE and the hub are
interrupted or the hub ports are faulty. As a result, the NE is unreachable.
1.
2.
Issue 03 (2012-11-30)
Check whether the network cables between the gateway NE and the hub are connected
improperly.
If...
Then...
The network cables between the gateway

NE and the hub are connected improperly
Connect the network cables between the

NE and the hub properly. Check whether
the NEs recover. If the NEs do not recover,
The network cables between the gateway

NE and the hub are connected properly
Use the cable testing meter to check whether the network cables are normal.
If...
Then...
The network cables are faulty
Replace the network cables. Check


891
OptiX OSN 7500 II/7500/3500/1500

3.
21 Outband DCN
If...
Then...
The network cables are normal
Check whether the hub ports are faulty.

If...
Then...
The hub ports are faulty
Replace the faulty ports or replace the hub.

Check whether the NEs recover. If the NEs
do not recover, check whether the fault
occurs due to other causes.
The hub ports are working in the normal

state

causes.
Step 4 Cause 4: The IP addresses or the IDs of the gateway NE is changed by mistake. As a result,
the NE is unreachable.
1.
Log in to the NE through the U2000 LCT and restore the original IP addresses and IDs of
the NEs according to the record.
2.
Check whether the NEs recover. If the NEs do not recover, check whether the fault occurs
Step 5 Cause 5: The fibers are faulty or connected improperly. As a result, the NEs are
unreachable.
1.
Use the optical time domain reflectometer (OTDR) meter to test the fiber. Analyze the line
attenuation curve displayed by the meter to determine whether fiber cut occurs on the line.
For how to use the meter, see the OTDR user guide.
If...
Then...
Fiber cut occurs on the line
Replace the faulty fiber. Then, check

whether the service is restored. If not,
Fiber cut does not occur on the line
2.
Connect the optical fibers correctly according to the network design.
3.
Check whether the NEs recover. If the NEs do not recover, check whether the fault occurs
Step 6 Cause 6: The system control board of the gateway NE is faulty.

1.
Reset the system control board. Then, check whether the services are restored. If the
services are not restored, proceed to the next step.
2.
Replace the faulty system control board, and check whether the services are restored. If the
services are not restored, check whether the fault occurs due to other causes.
Step 7 Cause 7: The network size is too large, and the ECC communication between NEs exceeds
the processing capability of the NEs.
1.
Issue 03 (2012-11-30)
Check the number of NEs at a single station. When multiple devices are connected through
a hub (or by means of inter-subrack cascading ports) and communicate with each other by
892
OptiX OSN 7500 II/7500/3500/1500

21 Outband DCN
using the extended ECC function of the network port, it is recommended that you enable
automatic extended ECC function for not more than four devices connected to the same
hub and that you enable the manual extended ECC function if more than four devices are
connected to the same hub, to prevent ECC storms.
2.
Contact Huawei technical support engineers to check whether the data communication
network (DCN) communication between NEs exceeds the processing capability of the NEs.
3.
----End
Related Information
To prevent all NEs of the subnet from becoming unreachable due to the fault of the gateway NE,
it is recommended to install a backup gateway NE in the subnet.
21.7.1.3 NEs Being Unreachable Frequently

This topic describes the symptoms, impact, and possible causes of frequently unreachable NEs.
In addition, this topic describes the required tools, precautions, and procedures for rectifying the
fault.
Symptom
Symptom 1: NEs are frequently unreachable to the NMS.
Symptom 2: NEs become unreachable after they are logged in for a while.
Impact on System
The unreachable NEs cannot be managed.
Possible Causes
l
Cause 1: The IP addresses or IDs of the NEs conflict.
Cause 2: The scale of the network is over-large, and the ECC communication between NEs
exceeds the processing capability of the NEs.
Cause 3: On the network, more than one user logs in to the NE.
Cause 4: The SCC board is faulty.

l
U2000
Procedure
Step 1 Cause 1: The IP addresses or IDs of the NEs conflict. As a result, the NEs are unreachable
frequently.
1.
Issue 03 (2012-11-30)
Check whether the IP addresses or IDs of the NEs conflict with those of other NEs or
devices on the network.
893
OptiX OSN 7500 II/7500/3500/1500

21 Outband DCN
If...
Then...
The IP addresses or IDs of the NEs conflict

with those of other NEs or devices on the
network
Re-plan and re-configure the IP addresses

and IDs of the NEs. Check whether the NEs
recover. If the NEs do not recover, check
whether the fault is due to other causes.
The IP addresses or IDs of the NEs do not

conflict with those of other NEs or devices
on the network

causes.
Step 2 Cause 2: The scale of the network is over-large, and the ECC communication between NEs
exceeds the processing capability of the NEs. As a result, the NEs are unreachable
frequently.
1.
Check whether the scale of the network is very large. If it is very large, divide the network
appropriately into subnets.
2.
Check the number of the NEs at a single site. When multiple devices are connected through
the hub (or inter-subrack cascading) and communicate with each other through the extended
ECC function of the network port, it is recommended that on the same hub, a maximum of
four devices be enabled with the automatically extended ECC function; the extended ECC
function can be enabled for a maximum of four devices that are connected to the same hub
to avoid the ECC storm.
3.
Check whether the number of NEs managed by the gateway NE exceeds the DCC
processing capability of the SCC board. If it exceeds, replace the SCC board with a more
powerful SCC board.
4.
Check whether the NEs recover. If the NEs do not recover, check whether the fault is due
to other causes.
Step 3 Cause 3: On the network, more than one user logs in to the NE. As a result, the NE is
unreachable frequently.
1.
Re-plan the users that can log in to the NE.
2.
Check whether the NE recovers. If the NE does not recover, check whether the fault is due
to other causes.
Step 4 Cause 4: The SCC board is faulty. As a result, the NE is unreachable frequently.
1.
Perform a cold reset on the SCC board or reseat the SCC board.
2.
Check whether the NE recovers. If the NE does not recover, replace the faulty board.
3.
Check whether the NE recovers. If the NE does not recover, check whether the fault is due
to other causes.
----End
Related Information
None
21.7.2 Maintenance Cases

This topic describes the typical cases of maintaining the DCN on the existing network.
For cases concerning a DCN fault, see the following:
Issue 03 (2012-11-30)

894
OptiX OSN 7500 II/7500/3500/1500

21 Outband DCN
MC-B8 Communication Between Equipment and NMS Fails After Standby CXL Board Is
Switched to Main Mode
MC-B9 Fibers Are Not Connected Between Equipment but ECC Communication Between
Equipment Is Available
MC-B10 ECC Communication Is Available Between Two Isolated Rings
MC-B18 ECC Connection Is Interrupted When SCC Board Is Upgraded
MC-B26 Fault in Standby XCE Board Results in Abnormal Communication of AUX board
in Extended Subrack
MC-B29 Adding Boards Fails Due to Incorrect Use of EXT Port on AUX Board
MC-B31 Anomalies Occur After Main Subrack Becomes Extended Subrack
MC-B60 Excessive NEs on the ECC Network Causes an ECC Storm on the Entire Network
After the Route Changes
MC-B66 ECC Storm Occurs when Active/Standby Switching of SCC Boards Is Triggered
by Removing SCC Board on OptiX OSN 3500
MC-B70 The NE Becomes Unreachable for the NMS After the Active/Standby Switching
Because the NE ID and IP Address of the Standby System Control Board Are Changed
MC-B76 Communication Anomaly Occurs Between the Equipment and the NMS Due to
the Setting of the Firewall

There is no alarm or performance event relevant to the DCN feature.
Issue 03 (2012-11-30)

895
OptiX OSN 7500 II/7500/3500/1500

22
22 Inband DCN Solution
Inband DCN Solution
About This Chapter

The U2000 communicates with NEs and manages and maintains network nodes by means of a
DCN. On the DCN, the U2000 and NEs can be considered as nodes, which are connected by
means of Ethernet or DCC physical channels.
22.1 Overview of the Inband DCN
The inband DCN refers to the networking mode that uses the service path provided by the
managed equipment to realize the management of the network equipment. In this mode, the
network management information is transmitted on the service path of the equipment.
22.2 Basic Concepts
This topic describes the basic concepts that are related to the inband DCN, including the protocol
stacks that the inband DCN supports and the methods for the NMS to access the NE.
These standards and protocols are Huawei proprietary protocols.
22.4 Availability
The inband DCN function requires the support of the applicable equipment, boards, and
software.
This section describes the limitations on and precautions for inband DCN in the network design
22.6 Principles
DCN packets carry management information for the U2000 to manage equipment. To achieve
the DCN function, DCN channels must be set up between the U2000 and NEs to transmit DCN
packets.
When no special DCN is available for transmitting network management information, you can
perform the networking in the inband DCN mode.
22.8 Configuring the Inband DCN
Generally, you need not construct a dedicated management and control DCN network during
the network planning process. You can use partial bandwidth on the service network to construct
the management DCN.
Issue 03 (2012-11-30)

896
OptiX OSN 7500 II/7500/3500/1500

22.9 Configuration Case of the Inband DCN

The configuration case of the inband DCN describes the networking mode of the DCN and the
configuration method.
22.10 Verifying the Configuration of the Inband DCN
This topic describes how to determine whether the specified inband DCN works properly by
verifying the basic functions of the inband DCN.
22.12 Parameter Description: Inband DCN
Issue 03 (2012-11-30)

897
OptiX OSN 7500 II/7500/3500/1500

22.1 Overview of the Inband DCN

The inband DCN refers to the networking mode that uses the service path provided by the
managed equipment to realize the management of the network equipment. In this mode, the
network management information is transmitted on the service path of the equipment.
Objectives and Benefits

The inband DCN, which does not require extra equipment, has the feature of easy and flexible
networking. With the application of the inband DCN, a network need not be set up for the DCN,
which reduces the operation expenditure.
Functions and Features

Inband DCN manages network equipment information using service channels provided by the
managed equipment. In this mode, management information is encapsulated into Ethernet
frames and transmitted with services over service channels. A unified and fixed VLAN ID is
used to distinguish management data from service data.
Networking and Application

Inband DCN is used when no independent DCN network is provided to transmit network
management information. As shown in Figure 22-1, DCN data and service data are transmitted
over the same service channel and distinguished by VLAN ID.
Figure 22-1 Inband DCN networking diagram
NMS
MPLS Tunnel
Ethernet Link
Service
DCN information
Issue 03 (2012-11-30)

898
OptiX OSN 7500 II/7500/3500/1500

22.2 Basic Concepts

This topic describes the basic concepts that are related to the inband DCN, including the protocol
stacks that the inband DCN supports and the methods for the NMS to access the NE.
22.2.1 Protocol Stack

The inband DCN supports the HW ECC and IP protocol stacks, which are optimized based on
traditional protocol stacks.
HW ECC Protocol Stack

The HW ECC is a proprietary protocol of Huawei. The HW ECC protocol stack is optimized
based on the architecture of the ECC protocol defined in the OSI seven layer reference model.
The HW ECC solution is widely used by Huawei transmission equipment and is mature. Figure
22-2 shows the architecture of the HW ECC protocol stack.
Figure 22-2 Architecture of the HW ECC protocol stack
Application layer
Presentation layer
Session layer
Transport layer
Network layer
Network layer
Media access
layer
Data link layer
Physical layer
Physical layer
HW ECC
protocol
Transport layer
OSI model
Physical Layer
The main function of the physical layer is to control the physical channel, and receive and
transmit the data in the physical channel. The physical layer performs the following
functions:
The physical layer receives the data in the physical channel and transfers the data to the
upper layer.
The physical layer receives the data frame transferred from the upper layer and sends
it to the physical channel.
l
Issue 03 (2012-11-30)
Media Access Layer

899
OptiX OSN 7500 II/7500/3500/1500

The main function of the media access layer (MAC layer) is to activate or close physical
the DCCs between the physical layer and the network layer. The MAC layer performs the
following functions:
The MAC layer receives the data frame transferred from the physical layer. If the
destination address is the same as the address of the local station, the MAC layer
transfers the data frame to the network layer. Otherwise, the MAC layer discards the
data frame.
The MAC layer sends the data frame from the network layer. If the destination address
of the data frame has a MAC connection, the MAC layer sends the data frame to the
corresponding physical channel at the physical layer through the MAC connection.
Otherwise, the MAC layer discards the data frame.
l
Network Layer
The main function of the network layer (NET layer) is to provide the route addressing
function for data frames and the route management (including the route creation and
maintenance) function for the ECC network.
The NET layer receives the packet transferred from the MAC layer. If the destination
address of the packet is the same as the address of the local station, the NET layer
transfers the packet to the transport layer. Otherwise, the NET layer requests the MAC
layer to transfer the packet to the transfer station according to the routing entry that
matches the destination address in the NET layer routing table.
The NET layer sends the packet from the transport layer. The NET layer requests the
MAC layer to transfer the packet to the transfer station according to the routing entry
that matches the destination address of the packet in the NET layer routing table.
Transport Layer
for the upper layer. The communication between the OptiX equipment and the NMS is
controlled by the end-to-end connection-oriented service at the application layer. Hence,
the transport layer provides only the end-to-end connectionless communication service,
namely, transparent data transfer service.
IP Protocol Stack
Figure 22-3 shows the architecture of the IP protocol stack.
Figure 22-3 Architecture of the IP protocol stack
Routing protocol
OSPF
Transport layer
TCP/UDP
Network layer
IP
Data link layer

Physical layer
Issue 03 (2012-11-30)
PPP
Ethernet
PPPoE
FE/GE

900
OptiX OSN 7500 II/7500/3500/1500

Physical Layer
The main function of the physical layer is to provide channels for data transmission for the
data end equipment. The Ethernet physical channel provided by the FE or GE interface
functions as the channel on the physical layer.
Data Link Layer

The main function of the data link layer is to provide reliable data transmission for physical
links. The PPP and PPPoE protocols are used to realize the function of the data link layer.
The PPPoE protocol is used to create the point-to-point connection, to create the PPP
interface for the PPP protocol, and to encapsulate the PPP packet into the MAC frame
for transmission to the opposite end.
The PPP protocol controls the creation, removal, and monitoring of the link, coordinates
the format and type of the carried network layer data packet, and adopts the handshake
mechanism to guarantee the safe transmission of the packet.
Network Layer
The main function of the network layer is to specify the network layer address for a network
entity and to provide the transferring and addressing functions.
The NE uses the IP protocol and the corresponding ARP and ICMP protocols to realize the
network layer functions.
Transport Layer
for the upper layer.
The NE supports the connection-oriented TCP protocol and the connectionless-oriented
UDP protocol.
Routing Protocols
Routing protocols belong to the scope of the application layer. The NE supports Open
Shortest Path First (OSPF).
The OSPF protocol is a dynamic routing protocol based on the link status. The OSPF
protocol divides an autonomous system (AS) into several areas. Route nodes exchange
routing information in an area. The route nodes at the edge of an area make a summary and
exchange information with the routers in other areas. Areas are identified by area IDs. The
area ID has the same format as the IP address.
Currently, the OSPF protocol used by the OptiX equipment supports only the routes within
an area and does not support the routes between areas. Hence, the gateway NE and all its
managed non-gateway NEs must be in the same OSPF area. By default, the OSPF protocol
is enabled for the line port of the OptiX equipment but is disabled for the Ethernet port.
Hence, to form a network through the Ethernet port, you need to modify the OSPF setting
of the NE.
In addition to the dynamic routing protocol, the NE supports static routes. Static routes
refer to the routes that are manually configured. Static routes have a higher priority than
dynamic routes. When there is a route conflict, the equipment always selects static routes
first.
22.2.2 Access Methods

In the inband DCN solution, there are two methods for the NMS to access an NE: access through
the gateway and direct access.
Issue 03 (2012-11-30)

901
OptiX OSN 7500 II/7500/3500/1500

Access Through the Gateway

Through this method, the NMS accesses a non-gateway NE through the gateway NE. The
gateway NE queries the core routing table of the application layer according to the ID of the NE
to be accessed to obtain the corresponding route.
protocol stacks. Each routing entry includes the following items:
l
Transfer distance
Direct Access Method

Through this method, the NMS accesses an NE as the gateway NE. All transfer NEs on the
access path query the IP routing table of the network layer according to the IP address of the NE
to be accessed to obtain the corresponding route.
The IP routing table is based on routing protocols. It includes both dynamic routes generated
according to routing protocols and static routes configured by operators. Each routing entry
includes the following items:
l
Destination IP address
Subnet mask
IP address of the gateway
Interface
When the NMS directly accesses an NE, there must be an IP route between the NMS and the
NE.
22.2.3 Access Control

NEs directly access the network management system (NMS) through an Ethernet service port
enabled with the access control function.
Figure 22-4 shows a typical application scenario for the access control function. The PSN
network not only transmits Ethernet service packets but also transmits DCN packets between
the NMS and gateway NE. The access control function is enabled for an Ethernet service port
on the gateway NE.
Issue 03 (2012-11-30)

902
OptiX OSN 7500 II/7500/3500/1500

Figure 22-4 Access control

NMS
Inband DCN
packets
Packet
Switch
Network
LAN switch
Router
FE/GE
Access
enabled
Ethernet
service packets
After the access control function is enabled on an Ethernet service port on the gateway NE:
l
The Ethernet service port can function as a network management port.
The IP address of this network management port can be specified based on network
requirements but cannot be in the same network segment with IP addresses of NEs.
DCN packets transmitted or received by this network management port carry VLAN IDs
used on the inband DCN. Therefore, the VLAN tags need to be stripped off by a device
(for example, the LAN switch in the figure) before the DCN packets reach the NMS.
The NMS can communicate with the gateway NE using the IP address of this network
management port.

These standards and protocols are Huawei proprietary protocols.
22.4 Availability
The inband DCN function requires the support of the applicable equipment, boards, and
software.
Version Support
Issue 03 (2012-11-30)
Applicable Version
OptiX OSN 1500/3500
T2000
U2000

903
OptiX OSN 7500 II/7500/3500/1500

Applicable Version
OptiX OSN 7500
U2000
Applicable Version
OptiX OSN 7500 II
U2000
Hardware Support
Applicable Board
Applicable Version
N1PEG16
OptiX OSN 3500
N1PEX1
OptiX OSN 3500
N1PETF8
OptiX OSN 3500/7500
R1PEFS8
Q1PEGS2
R1PEGS1
N1PEG8
OptiX OSN 3500/7500
N2PEX1
OptiX OSN 3500/7500
N1PEX2
OptiX OSN 3500/7500
N1PEFF8
OptiX OSN 3500/7500
R1PEF4F
TNN1EX2
OptiX OSN 7500 II
TNN1EG8
OptiX OSN 7500 II
TNN1ETMC
OptiX OSN 7500 II
TNN1EFF8
OptiX OSN 7500 II

This section describes the limitations on and precautions for inband DCN in the network design
Issue 03 (2012-11-30)

904
OptiX OSN 7500 II/7500/3500/1500


Applicable
Object

Details
Remarks
VLAN ID and
bandwidth
l On one subnet (composed of one

GNE and the non-GNEs under
its control), the management
VLAN IDs of all NEs must be the
same.
l The management VLAN ID used

for the inband DCN must be
different from the VLAN ID
carried by Ethernet services. It is
recommended that the
management VLAN ID take the
default value.
l The inband DCN bandwidth can
be determined based on the
number of NEs on a subnet. It is
recommended that the inband
DCN bandwidth take the default
value.
Inband DCN
channel
l When equipment performs DCN

communication through FE/GE/
10GE ports, you need to enable
the inband DCN function on the
FE/GE/10GE ports.
l It is recommended that the

number of inband DCN channels
between two NEs should not
exceed two.
Issue 03 (2012-11-30)

905
OptiX OSN 7500 II/7500/3500/1500

Applicable
Object

Details
Remarks
Protocol type
l NEs on an inband DCN subnet

use the same protocol.
l When the inband DCN needs to

work with another DCN
solution, such as the HWECC
solution or IP over DCC
solution, it is recommended that
the inband DCN uses the same
protocol as that used by the
interworking DCN solution.
l It is recommended that you use
IP protocols if only the inband
DCN solution is used.
l When an inband DCN subnet
uses IP protocols, OSPF
parameters for each NE take the
default values. This ensures that
the OSPF protocol functions
properly on the NEs in the same
OSPF area.
NE IP address
l Set NE IP addresses for the most

simplified route settings.
l The IP address, subnet mask, and

default gateway of a GNE must
meet the planning requirements
of the external DCN.
l Set the IP addresses of nonGNEs based on their NE IDs.
NOTE
l The IP address of a non-GNE is
0x81000000 + NE ID. For example,
if the NE ID is 0x090001, set the IP
address to 129.9.0.1.
l By default, the subnet mask is
255.255.0.0.
Issue 03 (2012-11-30)

906
OptiX OSN 7500 II/7500/3500/1500

Applicable
Object

Details
Remarks
Access control
l When a GNE needs to

communicate with the NMS
through an Ethernet service port,
enable the access control
function on this service port.
l The IP address of the service port

with the access control function
enabled cannot be in the same
network segment as that of the
NMS.
l When being transmitted/
received at the service port with
the access control function
enabled, the DCN packet is
tagged with a VLAN ID that is
used by the inband DCN.
Therefore, before the DCN
packet arrives at the NMS, the
VLAN ID needs to be stripped
off by equipment (for example, a
LAN switch).
l It is recommended that the NMS
communicates with the GNE
through the IP address of the
service port on which the access
control function is enabled.
Issue 03 (2012-11-30)

907
OptiX OSN 7500 II/7500/3500/1500

Applicable
Object

Details
Remarks
DCN (inband
DCN using IP
protocols)
l The more NEs are on a DCN

subnet, the more CPU resources
are used.
l Plan the number of NEs on one

DCN subnet based on the
network status. It is
recommended that a DCN subnet
have not more than 120 NEs. The
maximum number of NEs on a
DCN subnet is 150.
selected point for connecting to
the external DCN be the central
node of a start network or the NE
that connects to most DCCs.
l One OSPF area that contains
OptiX NEs has a maximum of 64
NEs.
l If a DCN subnet has more than
64 NEs, it is recommended that
you divide the DCN subnet into
several independent subnets and
disable DCCs across these
subnets.
64 NEs and cannot be divided, it
is recommended that you divide
the DCN subnet into several
OSPF areas. The NMS
communicates with the GNEs in
each OSFP area through static
routes.
NOTE
If a network consists of OptiX NEs
and third-party NEs that support
multiple OSPF areas, you may
configure the third-party NEs as
area border routers (ABRs) and
divide the network into multiple
OSPF areas. In this scenario, you do
not need to configure static routes.
l If a DCN subnet contains only

one OSPF area, it is
recommended that you configure
the NE connected to the external
DCN as a GNE and the other NEs
as non-gateway NEs.
Issue 03 (2012-11-30)

908
OptiX OSN 7500 II/7500/3500/1500

Applicable
Object

Details
Remarks
l If a DCN subnet contains

multiple OSPF areas, configure
a GNE for each OSPF area and
the other NEs as non-gateway
NEs. It is recommended that you
configure the NE that is
connected to the external DCN
or closest to the connection point
as a GNE.
DCN (inband
DCN using the
HWECC
protocol)
l The more NEs are on a DCN

subnet, the more CPU resources
are used. As a result, the ECC
routes are less stable, even
resulting in vibration of ECC
routes. On a network with
complex topology and poor
quality, this situation is more
likely to occur.
l Plan the number of NEs on one

DCN subnet based on the
network status. It is
recommended that a DCN subnet
have not more than 120 NEs. The
maximum number of NEs on a
DCN subnet is 150.
selected GNE be the central node
of a star network, or the NE that
connects to most DCCs.
120 NEs, it is recommended that
you increase GNEs to divide the
network into multiple ECC
subnets.
l Disable the DCCs across DCN
subnets.
l Maintain the existing ECC route
protection when you divide a
DCN network.
l It is recommended that you set an
active and standby GNEs for a
DCN subnet.
Issue 03 (2012-11-30)

909
OptiX OSN 7500 II/7500/3500/1500

Applicable
Object

Details
Remarks
Inband DCN
traversing a
third-party
network
Inband DCN packets can pass

through the L2 network as L2
packets. In this case, the VLAN ID
of the inband DCN must be different
from that of the L2 network.

None.
None.
22.6 Principles
DCN packets carry management information for the U2000 to manage equipment. To achieve
the DCN function, DCN channels must be set up between the U2000 and NEs to transmit DCN
packets.
22.6.1 Message Transfer in the HW ECC Protocol Stack

In the HW ECC solution, the messages between NEs are transferred at the NET layer of the NEs.
Figure 22-5 illustrates how the message is transferred in the HW ECC protocol stack.
The realization principle is as follows:
1.
The NMS transfers the application layer message to the gateway NE through the TCP
2.
The gateway NE extracts the message from the TCP/IP protocol stack and reports the
message to the application layer.
3.
The application layer of the gateway NE queries the address of the destination NE in the
message. If the address of the destination NE is not the same as the address of the local
station, the gateway NE queries the core routing table of the application layer according to
the address of the destination NE to obtain the corresponding route and the communication
protocol stack of the transfer NE.
4.
On the packet that encapsulates the message is received, the NET layer of the transfer NE
queries the address of the destination NE of the packet. If the address of the destination NE
is not the same as the address of the local station, the transfer NE queries the NET layer
routing table according to the address of the destination NE to obtain the corresponding
route and then transfers the packet.
5.
After the packet is received, the NET layer of the destination NE reports the packet to the
application layer through the L4 layer because the address of the destination NE of the
packet is the same as the address of the local station. The application layer performs
operations according to the message sent from the NMS.
Issue 03 (2012-11-30)

910
OptiX OSN 7500 II/7500/3500/1500

Figure 22-5 Message transfer in the HW ECC protocol stack

Application
Application
Application
TCP
TCP
L4
IP
IP
NET
NET
NET
MAC
MAC
MAC
Ethernet
Ethernet
FE/GE
FE/GE
FE/GE
Transfer NE
Destination NE
NMS
Gateway NE
L4
NOTE
The MAC refers to the media access layer, NET refers to the network layer, and L4 refers to the transport
layer.
22.6.2 Message Transfer in the IP Protocol Stack

When the IP protocol stack is used, the way NEs forward packets varies with the way the network
management system (NMS) accesses NEs.
Access Through a Gateway NE

Figure 22-6 illustrates how packets are forwarded using the IP protocol stack when the NMS
accesses NEs through a gateway NE.
The process is as follows:
1.
The NMS forwards application-layer packets to the gateway NE through the TCP/IP
2.
The gateway NE extracts the packets from the TCP/IP protocol stack and transmits them
to the application layer.
3.
The application layer of the gateway NE processes the packets according to the destination
address.
4.
Issue 03 (2012-11-30)
a.
If the destination address differs from the address of the local station, the gateway NE
queries the corresponding route from the application-layer core routing table
according to the destination address.
b.
The gateway NE encapsulates the packets into Ethernet data frames, adds VLAN IDs
to identify the packets as DCN packets, and forwards the DCN packets to the
corresponding port.
The transfer NE processes the Ethernet data packets according to their VLAN IDs.
a.
Data packets with management VLAN IDs are transmitted to the upper layer as DCN
packets for protocol processing. Data packets with non-management VLAN IDs are
forwarded as service packets.
b.
The network layer of the transfer NE parses the destination IP address of the DCN
packets. If the destination IP address differs from the IP address of the local station,
911
OptiX OSN 7500 II/7500/3500/1500

the transfer NE queries the corresponding route from the routing table generated by
the OSPF protocol and forwards the packets to the corresponding port.
5.
After receiving the Ethernet data packets, the destination NE transmits the DCN packets
with management VLAN IDs to the upper layer for protocol processing. The destination
IP address of the DCN packets is the IP address of the local station. Hence, the DCN packets
are transmitted from the transport layer to the application layer. The application layer
performs operations according to messages carried in the packets from the NMS.
Figure 22-6 Packet forwarding using the IP protocol stack (access through a gateway NE)
Application
Application
Application
TCP
TCP
TCP
IP
IP
IP
IP
IP
PPP
PPP
PPP
PPPoE
PPPoE
PPPoE
FE/GE
FE/GE
FE/GE
Transfer NE
Destination NE
Ethernet
Ethernet
NMS
TCP
Gateway NE
NOTE
FE or GE links function as the physical channels to forward data.
Direct Access
Figure 22-7 illustrates how packets are forwarded using the IP protocol stack when the NMS
accesses NEs directly.
Figure 22-7 Packet forwarding using the IP protocol stack (direct access)
Application
Application
TCP
TCP
IP
IP
Ethernet
NMS
Ethernet
IP
IP
PPP
PPP
PPP
PPPoE
PPPoE
PPPoE
FE/GE
FE/GE
FE/GE
Transfer NE
Destination NE
Transfer NE
In this access mode, the gateway NE functions as an ordinary NE and forwards packets at the
network layer.
Issue 03 (2012-11-30)

912
OptiX OSN 7500 II/7500/3500/1500


When no special DCN is available for transmitting network management information, you can
perform the networking in the inband DCN mode.
In Figure 22-8, the management information and service information of the DCN use the same
service channel. The management information and service information are distinguished by
VLAN ID.
Figure 22-8 Application of inband DCN
NMS
MPLS Tunnel
Ethernet Link
Service
DCN information
22.8 Configuring the Inband DCN

Generally, you need not construct a dedicated management and control DCN network during
the network planning process. You can use partial bandwidth on the service network to construct
the management DCN.
22.8.1 Setting the VLAN ID and Bandwidth Used by the Inband

DCN
The equipment communicates with the NMS through the inband DCN. The network
management information is transmitted with the service information, and the equipment adds
the default VLAN ID into the management information. You can adjust the bandwidth of the
inband DCN according to the actual requirements.
Issue 03 (2012-11-30)

913
OptiX OSN 7500 II/7500/3500/1500

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

U2000
l
If the default VLAN ID of the DCN conflicts with the VLAN ID used by the service, change
the VLAN ID of the DCN manually. Ensure that all the DCN channels use the same VLAN
ID.
If the DCN packets do not use all the available bandwidth, the idle bandwidth can be shared
with the service packets.
It is recommended that you change the VLAN ID of the DCN on the non-gateway NEs
before changing the VLAN ID of the DCN on the gateway NE. Otherwise, the non-gateway
NEs may be unreachable to the NMS.
Procedure
Step 1 In the NE Explorer, select an NE and choose Communication > DCN Management from the
Function Tree.
Step 2 Click the Bandwidth Management tab and set the parameters.
NOTE
l If you click Default, the corresponding parameter automatically takes the default value.
l Generally, the default VLAN ID is recommended. When the VLAN ID used by a service conflicts with
the VLAN ID used by a DCN channel, you can define another VLAN ID for the DCN channel. Ensure
that the VLAN ID of the DCN channel is the same as the VLAN IDs of the other DCN channels.
Step 3 Click Apply.

----End
22.8.2 Setting the NMS Access Parameters

In the case of the traditional DCN network, the equipment accesses the NMS through the SCC
board. The OSN equipment can also access the NMS through the network interface of an Ethernet
board. When the OSN equipment accesses the NMS through the network interface of an Ethernet
board, the OSN equipment can communicate with the NMS only after you set the NMS access
parameters for the Ethernet board.
Prerequisites

U2000
Issue 03 (2012-11-30)

914
OptiX OSN 7500 II/7500/3500/1500

NOTE
l You need to set the NMS access parameters only when the equipment accesses the NMS by using an
Ethernet service board.
l By default, Enabled Status is Disabled.
CAUTION
When the DCN port is interconnected with the NMS, the IP address of the NMS computer and
the IP address of the NNI on the equipment cannot be in the same network segment.
Procedure
Function Tree.
Step 2 Click the Access Control tab and set the parameters.
Step 3 Click Apply.

----End
22.8.3 Configuring the DCN Function of a Port

The NM information can be transported through the inband DCN only when the DCN function
is enabled for the ports at both ends of a link.
Prerequisites

U2000
Procedure
Function Tree.
Step 2 Click the Port Settings tab.
Step 3 In the corresponding Enabled Status field of the related port, select Enabled.
Issue 03 (2012-11-30)

915
OptiX OSN 7500 II/7500/3500/1500

NOTE
When you configure an Ethernet service that exclusively occupies a port, disable the DCN function of the
port.
Step 4 Click Apply.

----End
22.8.4 Configuring the Protocol Stack Used by the Inband DCN

Inband DCN packets can be transmitted by using the IP or HWECC protocol.
Prerequisites

U2000
Procedure
Function Tree.
Step 2 Click the Protocol Settings tab. Set Protocol Type of the corresponding port.
NOTE
Protocol Type is set to the IP protocol by default. The HWECC protocol is an internal protocol of Huawei.
For communications between the OptiX OSN equipment, the IP protocol or the HWECC protocol can be
used. For communications between the OptiX OSN equipment and the PTN equipment or the third-party
equipment, only the IP protocol can be used.
Step 3 Click Apply.

----End
22.9 Configuration Case of the Inband DCN

The configuration case of the inband DCN describes the networking mode of the DCN and the
configuration method.

To plan a service is to design the details of a service to be created according to the service
requirements. Service planning provides guidelines for service configuration. The service
planning covers details such as the networking, requirements, and configuration data.
Issue 03 (2012-11-30)

916
OptiX OSN 7500 II/7500/3500/1500


As shown in Figure 22-9, the NMS exchange information is carried by the service channel of
the equipment.
l
NE1 and NE3 are connected to the NMS through the NE2. The network management
information and service information share the channel for transport.
The IP address of gateway NE is 129.9.0.1, the IP address of NMS is 129.9.0.10.
Figure 22-9 Inband networking application

NMS
129.9.0.10
NE 2
NE 1 5-N1PEG16-1
(Port1)
129.9.0.2
5-N1PEG16-2
(Port2)
129.9.0.1
5-N1PEG16-1
(Port1)
5-N1PEG16 -1
(Port1)
Fiber
NE 3
129.9.0.3
Ethernet link
Service Planning
The engineering planning department should plan the engineering according to the related
requirements, and output detailed planning information. Figure 22-9 is considered as an example
to show the service planning. Table 22-1 shows how to plan the parameters for the inband DCN
configuration.
Issue 03 (2012-11-30)

917
OptiX OSN 7500 II/7500/3500/1500

Table 22-1 Planning of the parameters for the inband DCN configuration
Attribute
Value
Station
NE1
NE2
NE3
Ethernet
Board
VLAN ID
4094
4094
4094
Bandwidth
(kbps)
512
512
512
Port
Settings
Enabled
Status
Enabled
Enabled
Enabled
Protocol
Settings
Protocol
Type
IP
IP
IP
Bandwidth
Manageme
nt

This topic describes the configuration process of the inband DCN in the configuration case.
Prerequisites
l
Procedure
Step 1 Set the communication parameters for each NE by using the U2000. For details, see Setting
Communication Parameters of an NE.
The communication parameters for NE1 are as follows:
l Subnet Mask: 255.255.0.0
Step 2 Set NE2 as GNE for NE1 and NE3, For the configuration method, see Changing the GNE for
NEs.
Step 3 Configure the bandwidth of the inband DCN on NE1, NE2, and NE3 by using the U2000. For
the configuration method, see Setting the VLAN ID and Bandwidth Used by the Inband DCN.
The parameters related to the bandwidth of inband DCN of each NE are set as follows:
Issue 03 (2012-11-30)

918
OptiX OSN 7500 II/7500/3500/1500

l Ethernet board VLAN ID: 4094

l Bandwidth (kbps): 512
Step 4 Configure the status of ports used by each NE by using the U2000. For the configuration method,
see Configuring the DCN Function of a Port.
The ports used by NE1, NE2, NE3, and NE4, and the enabling state of the ports are as follows:
l On NE1, set 5-N1PEG16-1(PORT-1) to Enabled.
l On NE2, set 5-N1PEG16-1(PORT-1) and 5-N1PEG16-2(PORT-2) to Enabled.
l On NE3, set 5-N1PEG16-1(PORT-1) to Enabled.
Step 5 Configure the protocol stack used by the inband DCN of each NE by using the U2000, set the
type of protocol as IP protocol. For the configuration method, see Configuring the Protocol Stack
Used by the Inband DCN.
NOTE
After you complete the preceding steps, log in to each NE by using the U2000 to ensure that communication
is normal.
----End
22.10 Verifying the Configuration of the Inband DCN

This topic describes how to determine whether the specified inband DCN works properly by
verifying the basic functions of the inband DCN.
Prerequisites
The inband DCN must be configured.
You can perform the verification according to the following aspects:
l
On the U2000, create a non-gateway NE. After being created successfully, the non-gateway
NE is reachable to the U2000 and can upload data to the U2000 normally.
On the U2000, query the DCN management data of the non-gateway NE to check whether
the configuration data of the inband DCN is correct.
After you change the settings of the parameters for the NE, such as the DCN protocol mode,
the DCN network communications is normal.
Procedure
Step 1 On the U2000, create a non-gateway NE. After being created successfully, the non-gateway NE
can log in to and upload data to the U2000 normally.
NOTE
In the case of new equipment, set Gateway Type to Non-Gateway, and then set Affiliated Gateway to
the gateway NE on the inband DCN.
Step 2 On the U2000, query the DCN management data of the non-gateway NE to check whether the
configuration data of the inband DCN is correct.
1.
Issue 03 (2012-11-30)
Choose System > DCN Management from the Main Menu.

919
OptiX OSN 7500 II/7500/3500/1500

2.
Click the NE tab.
3.
Click Refresh and check whether the Communication Status of the non-gateway NE is
Normal.
Step 3 After you change the settings of the parameters for the NE, such as the DCN protocol mode, the
DCN network communications is normal.
NOTE
On the network where inband DCN communication is performed, the parameters of all the NEs must be
the same. You need to change the parameters such as the DCN protocol mode of non-gateway NEs before
changing the parameters such as the DCN protocol mode of the gateway NEs.
1.
2.
In the NE Explorer, select the NE that you want to configure. Then, choose
Configuration > Communication > DCN Management.
3.
Modify the parameters such as Bandwidth (Kbps) and Protocol Type.
4.
Click Apply. Then, the Operation Result dialog box is displayed, indicating that the
operation is successful.
----End
Symptom
The common faults regarding the inband DCN are as follows:
l
The communication between the U2000 and NEs is interrupted, and the NE icons on the
U2000 become unavailable.
No response is returned after a command is issued on the U2000. If the wait time before a
response lasts more than 2 minutes, it indicates that the communication between the
U2000 and an NE is interrupted.
Part of the query result on the U2000 is lost.
Impact on System
l
After the communication between an NE and the U2000 is interrupted, the NEs that
communicate with the U2000 through the NE also become unreachable, if they fail to
connect to the U2000 by means of other methods. The other NEs, however, are not affected.
Possible Causes
l
Cause 1: The physical link between the faulty NE and the U2000 is disconnected.
Cause 2: The ports of the faulty NE on the inband DCN are disabled.
Cause 3: The DCN VLAN IDs of the NEs at both ends are not the same.
Cause 4: The NEs at both ends of an optical fiber use different protocols.
Cause 5: The faulty NE fails to obtain DCN packets due to loss of received signals or
extremely low receive optical power.
Issue 03 (2012-11-30)

920
OptiX OSN 7500 II/7500/3500/1500

Cause 6: A certain board is faulty.
Cause 7: No response is returned for inband DCN packets, because the SCC board on the
faulty NE is being reset or active/standby protection switching occurs on another board.
Cause 8: The bandwidth of the inband DCN channel is extremely low or other services
preempt the bandwidth of the inband DCN channel.
NOTE
When handling a fault regarding the inband DCN, do as follows:

l
If communication between NEs and the U2000 is interrupted, rectify the fault on the gateway NE
prior to the fault on the non-gateway NE.
If the communication between NEs and the U2000 is normal, rectify the fault on the non-gateway
NE prior to the fault on the gateway NE. This method ensures that the unaffected NEs can keep
communicating with the U2000 during the troubleshooting process.

U2000
Issue 03 (2012-11-30)

921
OptiX OSN 7500 II/7500/3500/1500

Figure 22-10 Flow chart for handling an inband DCN fault

Start
Check whether the

NE icon is dimmed.
Yes
The communication
between the T2000 and
the NE is interrupted.
Is the physical link

disconnected?
Yes
Reconnect the
Ethernet cable or
fiber.
No
Yes
Enable the port
on the DCN.
Is the port on the

DCN disabled?
No
Yes
Clear the alarm

related to the optical
power, fiber, or cable.
Is the received
signal lost?
No
No
Is the board
faulty?
No response is
returned for the
Yes
command on the
T2000.
The SCC board is

being reset.
Yes
Replace the board.
Wait until the SCC

board is reset.
No
Is the information
queried on the
T2000 lost?
Yes
The bandwidth
of the DCN path
is very low.
Increase the bandwidth of the

DCN path or degrade the
priority of other services.
No
Is the fault
rectified?
Yes

support engineers.
End
Procedure
Step 1 Cause 1: The physical link between the faulty NE and the U2000 is disconnected.
1.
Check whether the Ethernet cable or fiber of the faulty NE is disconnected from the port.
If yes, reconnect it.
Step 2 Cause 2: The ports of the faulty NE on the inband DCN are disabled.
1.
Issue 03 (2012-11-30)
Check whether the DCN function of the port that is connected to the fiber is enabled by
default. If not, connect the fiber to a port whose DCN function is enabled by default.

922
OptiX OSN 7500 II/7500/3500/1500

2.
Check whether the DCN access function is enabled for the ports at both ends of the link.
If not, enable DCN access function for the ports.
Step 3 Cause 3: The DCN VLAN IDs of the NEs at both ends are not the same.
1.
Check whether the DCN VLAN ID of the local NE is the same as the DCN VLAN ID of
the opposite NE. If not, change the DCN VLAN ID of the local NE to the DCN VLAN ID
of the opposite NE.
Step 4 Cause 4: The NEs at both ends of an optical fiber use different protocols.
1.
Check whether the local NE uses the same protocol as the opposite NE. If not, change the
protocol that the local NE uses to the same as the opposite NE does.
Step 5 Cause 5: The faulty NE fails to obtain DCN packets due to loss of received signals or extremely
low receive optical power.
1.
Check whether alarms such as ETH_LOS, and ETH_LINK_DOWN are reported on the
board that is configured with the inband DCN channel. If yes, see the Alarms and
Performance Events Reference to clear these alarms.
Step 6 Cause 6: A certain board is faulty.

1.
Query whether the HARD_BAD alarm is reported on the board that is configured with the
inband DCN channel. If yes, see the Alarms and Performance Events Reference to clear
the alarm.
Step 7 Cause 7: No response is returned for inband DCN packets, because the SCC board on the faulty
NE is being reset or active/standby protection switching occurs on another board.
1.
Check whether the PROG indicator on the system control and communication (SCC) board
blinks in green color. If yes, it indicates that the SCC board is being reset. When the PROG
indicator is steady green, it indicates that the SCC board completes resetting. Then, the NE
is automatically reconnected to the DCN.
2.
If no response is returned for DCN packets, check whether active/standby protection

switching occurs on another board, which results in rerouting of DCN packets.
3.
If active/standby protection switching occurs on a certain board, the NE automatically

responds to DCN packets after rerouting of DCN packets is completed.
Step 8 Cause 8: The bandwidth of the inband DCN channel is extremely low or other services preempt
the bandwidth of the DCN channel.
1.
If the number of services that are configured for the port exceeds the specified value, part
of the query result may be lost. To solve the problem, you need to increase the bandwidth
of the inband DCN channel properly. For details, see Setting the VLAN ID and Bandwidth
Used by the Inband DCN.
----End
22.12 Parameter Description: Inband DCN

22.12.1 Bandwidth Management

This topic describes the parameters, such as VLAN ID and Bandwidth (kbps) of a board, for
configuring in-band DCN bandwidth management.
Issue 03 (2012-11-30)

923
OptiX OSN 7500 II/7500/3500/1500

Table 22-2 lists the parameters for configuring in-band DCN bandwidth management.
Table 22-2 Parameters for configuring in-band DCN bandwidth management
Field
Value
Description
Ethernet Board VLAN ID
2 to 4094
Sets the VALN ID used by

the DCN. Set this parameter
when the U2000 and NE are
connected by the Ethernet
board, or the NEs are
connected to each other by
the Ethernet board.
Default: 4094
Generally, set this parameter

to the default VLAN ID. If
the VLAN ID of a service
conflicts with the VLAN ID
of a DCN channel, you can
specify a VLAN ID. The
VLAN IDs of all the DCN
channels on a network,
however, must be the same.
Bandwidth (Kbit/s)
64 to 2048
Default: 512
Sets the bandwidth used by

the DCN. Set this parameter
when the U2000 and NE are
connected by the Ethernet
board, or the NEs are
connected to each other by
the Ethernet board.
22.12.2 Access Control

This topic describes the parameters, such as IP Address and Subnet Mask of a port, for
configuring in-band DCN access control.
Table 22-3 lists the parameters for configuring in-band DCN access control.
Table 22-3 Parameters for configuring in-band DCN access control
Issue 03 (2012-11-30)
Field
Value
Description
Port Name
For example, 21-N1PETF8-1

(PORT-1)
Displays the Ethernet port

that can receive the NMS
information.

924
OptiX OSN 7500 II/7500/3500/1500

Field
Value
Description
Enabled Status
Enabled, Disabled
Enables or disables the port.
Default value: Disabled
l Enabled: The
management information
of the U2000 can be
received through this
port.
l Disabled: The
management information
of the U2000 cannot be
received through this
port.
IP Address
Default value: 0.0.0.0

Subnet Mask
For example, 255.255.255.0

Default value: 0.0.0.0
Sets the IP address of the

port.
Sets the subnet mask of the
port.
22.12.3 Port Settings

This topic describes the parameters, such as Enabled Status, for configuring an in-band DCN
port.
Table 22-4 lists the parameters for configuring an in-band DCN port.
Table 22-4 Parameters for configuring an in-band DCN port
Field
Value
Description
Port Name
For example, 21-N1ETF8-1

(PORT-1)
Displays the ports used for

transmitting management
information between NEs.
DCN Enabled Status
Enabled, Disabled
Enables or disables a port.
Default value: Enabled
l Enabled: Management
information between NEs
can be transmitted
through this port.
l Disabled: Management
information between NEs
cannot be transmitted
through this port.
OSPF Enabled Status
Enabled, Disabled
OPQ LSA Enabled Status
Enabled, Disabled
Issue 03 (2012-11-30)

Enables or disables the OSPF

protocol.
Enables or disables the
opaque LSA.
925
OptiX OSN 7500 II/7500/3500/1500

22.12.4 Protocol Settings

This topic describes the parameters for configuring the in-band DCN protocol.
Table 22-5 lists the parameters for configuring the in-band DCN protocol.
Table 22-5 Parameters for configuring the in-band DCN protocol
Field
Value
Description
Port Name
(PROT-1)
Display the Ethernet port that

can access the NMS
information.
Protocol Type
IP, HWECC
Set the type of protocol used

by DCN.
Default value: IP

22.13.1 Related Alarms

This topic describes alarms related to this feature.
Table 22-6 lists the alarms related to inband DCN.
Table 22-6 Alarms related to inband DCN
Alarm Name
Description
DCN_FAIL
The DCN_FAIL alarm indicates that an outband/

inband DCN channel fails. The DCN_FAIL alarm is
reported at the receive end when a fiber cut occurs or
the DCN mode is set to different values for the ports at
the local and opposite ends.
DCNSIZE_OVER
The DCNSIZE_OVER alarm indicates an over-sized

DCN network. This alarm is reported when the SCC
board on the gateway NE (GNE) detects excessive nonGNEs on a DCN subnet (the default threshold is 180).
22.13.2 Related Performance Events

There is no performance events related to the Inband DCN.
Issue 03 (2012-11-30)

926
OptiX OSN 7500 II/7500/3500/1500

A List of Parameters
List of Parameters
This topic describes all the parameters for configuring and querying the common boards and
functions on the U2000. Each parameter is described in terms of the description, impact on the
system, values, configuration guidelines, and relationship with other parameters.
A.1 Ethernet Port Associated Parameters (Packet Mode)
Before configuring an Ethernet service, you need to set the parameters associated with Ethernet
ports.
A.2 Ethernet Port Associated Parameters (TDM Mode)
Before configuring an Ethernet service, you need to configure the relevant parameters for
Ethernet ports.
A.3 Ethernet Service Associated Parameters (Packet Mode)
This topic describes the parameters for configuring Ethernet services.
A.4 CES Service Associated Parameters
This topic describes the parameters for configuring CES services.
A.5 Data Service Associated Parameters (TDM Mode)
This topic describes the parameters for configuring Ethernet services and SAN services.
A.6 ETH OAM Associated Parameters (Packet Mode)
This topic describes the parameters that are used for enabling the ETH-OAM function.
A.7 ETH-OAM Associated Parameters (TDM Mode)
This topic describes the parameters for configuring the ETH-OAM function.
A.8 PW Associated Parameters
This topic describes the parameters for configuring PW services.
A.9 PW APS Protection Associated Parameters (Packet Mode)
This topic describes the parameters for configuring PW APS protection.
A.10 HQoS Associated Parameters
This topic describes the parameters that are used for enabling the HQoS function.
A.11 QoS Associated Parameters
This topic describes the parameters for configuring the QoS function
A.12 ATM Interface Associated Parameters (Packet Mode)
This topic describes the parameters for configuring ATM interface.
Issue 03 (2012-11-30)

927
OptiX OSN 7500 II/7500/3500/1500

A.13 ATM/IMA Services Associated Parameters (Packet Mode)

This topic describes the parameters for configuring ATM/IMA services.
A.14 ATM OAM Associated Parameters (Packet Mode)
This topic describes the parameters for configuring ATM OAM.
A.15 ATM/IMA Associated Parameters (TDM Mode)
This topic describes the parameters for configuring the ATM/IMA function.
A.16 RPR Associated Parameters
This topic describes the parameters for configuring the RPR function.
A.17 LAG Associated Parameters (TDM Mode)
This topic describes the parameters that are used for enabling the LAG function.
A.18 MC-LAG Associated Parameters
This topic describes the parameters for configuring MC-LAG protection.
A.19 LAG/DLAG Associated Parameters (TDM Mode)
This topic describes the parameters for configuring a link aggregation group (LAG) and a
distributed link aggregation group (DLAG).
A.20 STP/RSTP Associated Parameters
This topic describes the parameters for configuring the Spanning Tree Protocol (STP) and the
Rapid Spanning Tree Protocol (RSTP).
A.21 LCAS Associated Parameters
This topic describes the parameters for configuring the LCAS function.
A.22 Packet LPT Associated Parameters
This topic describes the parameters for configuring the link state pass through (LPT) function
in packet services.
A.23 LPT Associated Parameters (TDM Mode)
This topic describes the parameters for configuring the LPT function.
A.24 IGMP Snooping Associated Parameters
This topic describes the parameters for configuring the IGMP Snooping function.
A.25 Test Frame Associated Parameters
This topic describes the parameters for configuring the Ethernet service test function.
A.26 Orderwire Associated Parameters
This topic describes the parameters for configuring the orderwire function.
A.27 Clock Associated Parameters
To synchronize the clocks on a network, you need to set the parameters that are associated with
clocks.
A.28 Protection Associated Parameters
This topic describes the parameters for configuring multiplex section protection (MSP),
subnetwork connection protection (SNCP), board protection switching (BPS), and path
protection switching (PPS).
A.29 Other Parameters
This topic describes the parameters related to PDH interfaces and SDH interfaces.
Issue 03 (2012-11-30)

928
OptiX OSN 7500 II/7500/3500/1500

A.1 Ethernet Port Associated Parameters (Packet Mode)

Before configuring an Ethernet service, you need to set the parameters associated with Ethernet
ports.
A.1.1 MAC Loopback(Ethernet Interface)

Description
The MAC Loopback (Ethernet Interface) parameter specifies the MAC loopback state at an
Ethernet port. Port loopback setting is applied to locating faults only.
Impact on the System

MAC loopback is a function of diagnosing faults. It may affect the services configured at the
port. If the loopback state is set to Inloop or Outloop, the services at the port may be interrupted.
Values
Valid Values
Default Value
Non-Loopback, Inloop, Outloop
Non-Loopback
The following table lists descriptions of each value.

Value
Description
Non-Loopback
Indicates the normal state. If the equipment works normally, you

do not need to set the MAC loopback.
Inloop
Loops back the services from the cross-connection side to the

cross-connection side within the equipment at the local end.
Outloop
At the local equipment, the incoming services of an Ethernet port

are looped back at the MAC layer and output to this Ethernet
port.
Configuration Guidelines
To set the MAC loopback, decide the loopback direction according to the service direction when
you locate the faults.
Relationship with Other Parameters

None.
Issue 03 (2012-11-30)

929
OptiX OSN 7500 II/7500/3500/1500

Related Information
Loopb
ack
Point
Meaning
Diagram
MAC
Loopba
ck
The Ethernet service is

looped from the MAC layer
of the Ethernet port.
A.1.2 PHY Loopback(Ethernet Interface)

Description
The PHY Loopback parameter indicates the loopback status of the physical layer of an Ethernet
port. This parameter is an advanced attribute of the Ethernet port.

As a fault diagnosis function, setting PHY loopback affects the services configured on the port.
In the case of loopback, services on the port are interrupted.
Values
Value Range
Default Value
Non-Loopback, Inloop, Outloop
Non-Loopback
Issue 03 (2012-11-30)
Value
Description
Non-Loopback
Indicates the normal status. When the equipment is operating normally,

loopback is not required.
Inloop
At the local equipment, the outgoing services of an Ethernet port are

looped back at the physical layer and input to this Ethernet port.
Outloop
At the local equipment, the incoming services of an Ethernet port are

looped back at the physical layer and output to this Ethernet port.

930
OptiX OSN 7500 II/7500/3500/1500

The PHY loopback is mainly used to locate a fault. When setting this parameter, determine the
loopback type according to the service flow direction.

None.
Related Information
Loopb
ack
Point
Loopback Point
PHY
loopbac
k
The Ethernet service is

looped from the physical
layer of the Ethernet port.
Diagram
A.1.3 Enable Port(Ethernet Interface)

Description
The Enable Port parameter sets whether the Ethernet port is usable.

When services are available on the Ethernet port, setting this port to disabled interrupts the
services.
Values
Value Range
Default Value
Enabled, Disabled.
Enabled
Issue 03 (2012-11-30)
Value
Description
Enabled
The port is usable.
Disabled
The port is unusable.

931
OptiX OSN 7500 II/7500/3500/1500

When a port is used for transmitting services, enable this port first.

None.
A.1.4 Encapsulation Type(Ethernet Interface)

Description
The Encapsulation Type parameter sets the link layer encapsulation type of the port, and
specifies the link layer encapsulation type that can be identified by this port.
Values
Value Range
Default Value
Null, 802.1Q, QinQ
For details, see configuration guidelines.

Value
Description
Null
No link layer is available, or the link layer encapsulation is

not processed.
802.1Q
In the Layer 2 mode, the encapsulation type of the Ethernet

port is 802.1Q by default.
QinQ
When the Ethernet port is used for QinQ Link, the port
attribute should be set to Layer 2, and the encapsulation type
should be set to QinQ. In addition, QinQ Type Domain of
the two interconnected Ethernet ports should be set to the
same value.
Currently, the encapsulation type of the Ethernet port can be set. In addition, the encapsulation
type can be switched only when the port does not carry services.
In the Layer 2 mode, the encapsulation type of the Ethernet port can be Null, 802.1Q, and
QinQ. In the Layer 3 mode, the encapsulation type of the Ethernet port, which is fixed to
802.1Q, cannot be set.

None.
Issue 03 (2012-11-30)

932
OptiX OSN 7500 II/7500/3500/1500

Related Information
For details, see the Port Mode parameter.
A.1.5 Working Mode(Ethernet Interface)

Description
Set the Working Mode parameter to set the working mode of the Ethernet port on the board.
The Working Mode parameter indicates the maximum transmission rate and communication
mode of a port.

If the working modes of interconnected Ethernet ports are inconsistent, the services are not
available or have a severe packet loss problem.
Values
Value Range
Default Value
10M Half-Duplex, 10M Full-Duplex, AutoNegotiation, 100M Half-Duplex, 100M FullDuplex, 1000M Full-Duplex, 10G Full-Duplex
LAN, 10G Full-Duplex WAN
Auto-Negotiation
Issue 03 (2012-11-30)
Value
Description
10M Half-Duplex
The maximum transmission rate of the port is 10 Mbit/s and the

communication mode is half-duplex.
10M Full-Duplex

communication mode is full-duplex.
Auto-Negotiation
The port uses the protocol to automatically specify the best

working mode that matches the opposite port for communication.
100M Half-Duplex
communication mode is half-duplex.
100M Full-Duplex
1000M Full-Duplex
10G Full-Duplex LAN
The maximum transmission rate of the port is 10 Gbit/s and the

communication mode is full-duplex. The port type is 10G BaseSR/LR/ER/ZR and the port is used as an Ethernet port to connect
LAN equipment that functions as the DHCP server.

933
OptiX OSN 7500 II/7500/3500/1500

Value
Description
10G Full-Duplex WAN
The maximum transmission rate of the port is 10 Gbit/s and the

communication mode is full-duplex. The port type is 10G BaseSW/LW/EW/ZW and the port is used as an SDH port to connect
WAN access equipment that functions as the DHCP client host.
The Auto-Negotiation working mode is recommended. If the communication fails and the
working mode of the port is set to Auto-Negotiation, you need specify the working mode of the
port according to the working mode of the interconnected port.
If the working mode of the port is set to any other mode instead of Auto-Negotiation, the working
mode of the interconnected port should be the same. Otherwise, the communication is not
available.
In the case of equipment interconnection, set the communication modes of the interconnected
ports to full-duplex.

None.
Related Information
None.
A.1.6 Max Frame Length(byte) for an Ethernet Port

Description
The Max Frame Length(byte) parameter sets the maximum length of the data packets allowed
to be received by the Ethernet port.

After this parameter is set, all the data packets of a length longer than this parameter are
discarded.
Values
Value Range
Default Value
64-9600
1620
The maximum data packet length has a filtering mechanism, through which this parameter is set
to filter the data packets received on the Ethernet port of a length longer than a certain length.
Issue 03 (2012-11-30)

934
OptiX OSN 7500 II/7500/3500/1500

When setting this parameter, consider the length of the data packets transmitted from the opposite
end. If the parameter value is less than the length of the data packets transmitted from the opposite
end, this link cannot normally transmit service packets.

l
The maximum data packet length defines the maximum bytes in a packet that is allowed
by an Ethernet port. All packets whose packet length is larger than the maximum data packet
length will be discarded by the Ethernet port.
The service MTU defines the maximum data packet length allowed by a service. All packets
whose length is larger than the MTU will be discarded.
When both the maximum data packet length and the service MTU are configured, the
smaller value takes effect.
A.1.7 Enable Tunnel(Ethernet Interface)

Description
The Enable Tunnel(Ethernet Interface) parameter sets the MPLS enabling state of the port.
When Enable Tunnel is set to Enabled, it indicates that the port can identify and process the
MPLS label.

If the MPLS is disabled, the services on the port are interrupted.
Values
Value Range
Default Value
Enabled, Disabled
Enabled

Value
Description
Enabled
The MPLS is enabled.
Disabled
The MPLS is disabled.
When the services are configured, the MPLS should not be disabled.

None.
Issue 03 (2012-11-30)

935
OptiX OSN 7500 II/7500/3500/1500

Related Information
The MPLS is a standard routing and switching technology platform, which supports various
high layer protocols and services.
The MPLS uses short and fixed-length tags to encapsulate various link layer packets. Based on
the IP routing and control protocol, the MPLS provides switching to the connection at the
network layer.
A.1.8 Specify IP(Ethernet Interface)

Description
The Specify IP parameter, set by port, indicates the method of specifying the IP address
parameter of a specified port.

The IP address parameter of the port is the prerequisite for MPLS service creation. If the current
IP address parameter is invalid, the services cannot be created.
Values
Value Range
Default Value
Manually, Unspecified
Unspecified

Value
Description
Manually
Indicates the IP parameter of the specified port. If the IP

address parameter is valid, specify an IP address to the current
port. If the IP address is invalid, release the IP address of the
current port.
Unspecified
Indicates that the IP address of the port is not specified.
None.

The IP address parameter can be configured only when the port is in the Layer 3 mode.
Issue 03 (2012-11-30)

936
OptiX OSN 7500 II/7500/3500/1500

A.2 Ethernet Port Associated Parameters (TDM Mode)

Before configuring an Ethernet service, you need to configure the relevant parameters for
Ethernet ports.
A.2.1 Port Attribute (Ethernet Port)

Description
The Port Attribute (Ethernet Port) parameter specifies the position of a port in the network.
Different port attributes support different packets.

The system operation is not affected.
Values
Board Name
Valid Values
Default Value
N2EMR0, N2EGR2,
N4EFS0, N5EFS0,
N2EFS4, N3EFS4,
N2EGS2, N3EGS2,
N1EFS0A, N1EFS0,
N2EFS0, N1EFS4,
N2EFS4, N1EMR0,
N2EMR0, N5EFS0
PE, P
PE
N1EMS4, N1EGS4,
N3EGS4, N4EGS4,
N1EAS2
UNI, C-Aware, S-Aware
UNI
N1EMS2
PE, P, C-Aware, S-Aware
PE
Issue 03 (2012-11-30)
Value
Description
PE
Indicates Provider Edge (PE), which refers to the edge port

of the service provider. A PE port (the default MPLS
encapsulation type is invalid) can transmit or receive standard
Ethernet packets.
Indicates Provider (P), which refers to the port in the core

network of the service provider. A P port can transmit or
receive the data packets with the MPLS labels (the default
TAG attribute is invalid).
937
OptiX OSN 7500 II/7500/3500/1500

Value
Description
UNI
Indicates the interface between CE and PE. This port

processes the packets with TAG attributes specified in IEEE
802.1Q. Moreover, this port identifies and processes the
VLAN IDs of the received packets according to the supported
Tag Aware, Access or Hybrid.
C-Aware
A C-Aware (C-VLAN Aware) port in the network is located

in the position as the UNI port at the client access side. This
port identifies and processes the VLAN (C-VLAN) in the
packets. If the value of QinQ TYPE is valid, this port treats
the outer labels of the packets as C-VLAN.
S-Aware
An S-Aware (S-VLAN Aware) port in the network is located

in the position as the interface on the network side. This port
identifies and processes the VLAN (S-VLAN) in the packets.
If the value of QinQ TYPE is valid, this port treats the outer
labels of the packets as S-VLAN.
The port attribute depends on the port position in the network and the service. For this reason,
select a proper port attribute as required. Generally, select the default value.
l
For the MPLS service, select P for the port that transmits or receives packets with MPLS
labels.
For the QinQ service, select C-Aware or S-Aware for the port. Connecting to the port of
the client network, a C-Aware port identifies and processes the packets with C-VLAN
labels. Connecting to the port at the network side, an S-Aware port identifies and processes
the packets with S-VLAN tags. The configuration examples are described as follows:
Add the S-VLAN tag to the service from Port A to Port B, and remove the S-VLAN
tag from the service from Port B to Port A. Then select C-Aware for Port A, and SAware for Port B.
Configure a service from Port A to Port B to transparently transmit the C-VLAN tags
at the client side. Then select C-Aware for Ports A and B.
Configure a service from Port A to Port B to transparently transmit the S-VALN tags
at the network side. Then select S-Aware for Ports A and B.
Configure a service from Port A to Port B to switch the C-VLAN tags at the client side.
Then select C-Aware for Ports A and B.
Configure a service from Port A to Port B to switch the S-VALN tags at the network
side. Then select S-Aware for Ports A and B.

None.
Related Information
According to the position and role of the equipment in the networking, there are three types of
equipment: CE, PE (U-PE & N-PE), and P. Client Edge (CE) indicates the equipment at the
Issue 03 (2012-11-30)

938
OptiX OSN 7500 II/7500/3500/1500

client side. Provider Edge (PE) indicates the edge equipment at the network side. Provider (P)
indicates the intermediate node at the network side.
A.2.2 Enable Port (Ethernet Port Attribute)

Description
The Enable Port (Ethernet Port Attribute) parameter specifies whether packets can be
transmitted or received at an Ethernet port.

If a port is disabled, it cannot transmit or receive packets. In this case, the service is unavailable.
Values
Valid Values
Default Value
Enabled, Disabled
Disabled

Value
Description
Enabled
The port can transmit or receive packets.
Disabled
The port cannot transmit or receive packets.
l
If the port does not bear a service, set the port attribute to Disabled.
If the port bears services, set the port attribute to Enabled.
A.2.3 Max. Frame Length (Ethernet Port Attribute)

Description
The Max. Frame Length (Ethernet Port Attribute) parameter specifies the maximum frame
length that is supported at an Ethernet port.

If the packet length exceeds the specified maximum frame length, the packets are discarded.
Alternatively, the packet length is minimized to the specified frame length. This parameter takes
effect only when the packet enters the port rather than when the packet that exits the port.
Issue 03 (2012-11-30)

939
OptiX OSN 7500 II/7500/3500/1500

Values
Board Name
Valid Values
Default Value
Unit
N1EGS4, N3EGS4
1518-9216, in step
length of 2
1522
Byte
N1EMS4, N4EGS4
1518-9216, in step
length of 1
1522
Byte
N1EFT8, N1EFT8A,
R1EFT4
1518-1535, in step
length of 1
1522
Byte
N1EGT2, N1EAS2,
N2EMR0, N2EGR2,
N4EFS0, N5EFS0,
N2EFS4, N3EFS4,
N2EGS2, N3EGS2,
N1EFS0A, N1EMS2
1518-9600, in step
length of 1
1522
Byte
Set this parameter as required. Generally, select the default value, unless otherwise specified.

None.
A.2.4 Non-Autonegotiation Flow Control Mode (Ethernet Port

Attribute)
Description
The Non-Autonegotiation Flow Control Mode (Ethernet Port Attribute) specifies the flow
control mode adopted when an Ethernet port works in non-auto-negotiation mode.

Values
Valid Values
Default Value
Disabled, Enable Symmetric Flow Control,

Send Only, Receive Only
Disable

Issue 03 (2012-11-30)

940
OptiX OSN 7500 II/7500/3500/1500

Value
Description
Disable
Indicates that the port disables the flow control function.
Enable Symmetric Flow

Control
Indicates that the port can transmit PAUSE frames and

process the received PAUSE frames.
Send Only
Indicates that the port sends the PAUSE frame only.
Receive Only
Indicates that the port can only process the received PAUSE
frames.
This parameter is meaningful only when you configure the EPL service. You can select the value
as required.

None.
A.2.5 Autonegotiation Flow Control Mode (Ethernet Port Attribute)

Description
The Autonegotiation Flow Control Mode (Ethernet Port Attribute) specifies the flow control
mode adopted when an Ethernet port works in auto-negotiation mode.

If the negotiation result is to enable the flow control function, the PAUSE frame is transmitted
to the upstream port.
Values
Board Name
Valid Values
Default Value
N1EMS4, N1EGS4,
N3EGS4, N1EAS2
Enable Symmetric/
Dissymmetric Flow Control
Enable Symmetric/
N2EMR0, N2EGR2,
N1EFS0, N2EFS0, N4EFS0,
N2EGS2, N3EGS2,
N1EFS0A, N1EMS2
Disabled
Disabled
Enable Dissymmetric Flow

Control
Control
Enable Symmetric/
Issue 03 (2012-11-30)

941
OptiX OSN 7500 II/7500/3500/1500

Board Name
Valid Values
Default Value
N4EGS4
Disabled
Enable Symmetric/

Control
Control
Enable Symmetric/

Value
Description
Disabled
Indicates that the port disables the flow control function.

Control
Indicates that the port only transmits flow control frames, but
does not process the received flow control frames.

Control
Indicates that the port can transmit PAUSE frames and

process the received PAUSE frames.
Enable Symmetric/
Indicates that the symmetric/dissymmetric flow control mode

is decided by the auto-negotiation result.
For the N1EMS4, N1EGS4, N3EGS4, N1EAS2 boards, this parameter is valid only when you
configure the EPL service.
Generally, set this parameter to Enable Symmetric/Dissymmetric Flow Control, unless
otherwise specified.
A.2.6 MAC Loopback (Ethernet Port Attribute)

Description
The MAC Loopback (Ethernet Port Attribute) parameter specifies the MAC loopback state
at an Ethernet port. Port loopback setting is applied to locating faults only.

MAC loopback is a function of diagnosing faults. It may affect the services configured at the
port. If the loopback state is set to Inloop, the services at the port may be interrupted.
Issue 03 (2012-11-30)

942
OptiX OSN 7500 II/7500/3500/1500

Values
Valid Values
Default Value
Non-Loopback, Inloop
Non-Loopback

Value
Description
Non-Loopback
Indicates the normal state. If the equipment works normally,

you do not need to set the MAC loopback.
Inloop

None.

None.
A.2.7 PHY Loopback (Ethernet Port Attribute)

Description
The PHY Loopback (Ethernet Port Attribute) parameter specifies the PHY loopback state at
an Ethernet port. Port loopback setting is applied to locating faults only.

PHY loopback is a function of diagnosing faults. It may affect the services configured at the
port. If the loopback state is set to Inloop, the services at the port may be interrupted.
Values
Valid Values
Default Value
Non-Loopback, Inloop
Non-Loopback
Issue 03 (2012-11-30)

943
OptiX OSN 7500 II/7500/3500/1500

Value
Description
Non-Loopback
Indicates the normal state. If the equipment works normally,

you do not need to set the PHY loopback.
Inloop

None.

None.
A.2.8 QinQ Type Area

Description
The QinQ Type Area parameter indicates the VLAN protocol used by the packet that is
transmitted by QinQ.
The default value 0x8100 of this parameter is the protocol type that is specified by the related
standard. The original equipment of other vendors may use 0x88A8 or 0x9100 to represent the
VLAN protocol. To realize the interconnection with the original equipment, the user should set
this parameter accordingly.

l
If QinQ Type Area is set to 0x8100 at the local end, QinQ Type Area must be set to
0x8100 at the opposite end. Otherwise, services are unavailable.
If QinQ Type Area is set to a value other than 0x8100 from 0x600 to 0xFFFF at the local
end, QinQ Type Area must be set to 0x8100 or to the same value at the opposite end.
Otherwise, services are unavailable.
Values
Value Range
Default Value
0x600-0xFFFF
0x8100
Set this parameter according to the supported value of QinQ Type Area of the opposite
equipment.
Issue 03 (2012-11-30)

944
OptiX OSN 7500 II/7500/3500/1500

A.2.9 Loop Detection (Ethernet Port Attribute)

Description
The Loop Detection (Ethernet Port Attribute) parameter specifies the function of reporting
the self-loop alarms after one of the following loopback cases is detected.
l
For the external physical interface of the board, the transmit direction is connected to the
receive direction by a fiber.
The two external physical ports on the board are cross-connected to each other through
fibers.
The cross-connection is created on the same VCTRUNK of the board.
The cross-connection is created between different VCTRUNKs of the board.

After the self-loop check function is enabled for a port, the specified self-loop check packets are
transmitted from the port. One packet is transmitted each second.
Values
Valid Values
Default Value
Enabled, Disabled
Disabled
To check the self-loop port, select Enabled.

The loop port shut-down function takes effect only after the loop check function is enabled.
A.2.10 Loop Port Shutdown (Ethernet Port Attribute)

Description
The Loop Port Shutdown (Ethernet Port Attribute) parameter is set to disable the self-loop
port after a self-loop port is detected if the loop port shutdown function is enabled. After the
self-loop port is shut down, the self-loop port only transmits or receives the self-loop detection
packets rather than any other packets. If the port is not a self-loop port, it starts to work again.

If a port enables the loop port shut-down function, the IEEE 802.3ah protocol blocks the port
once the port is detected to be a self-loop port. In this case, the services at the port are interrupted.
All the packets based on the upper-level protocol are discarded.
Issue 03 (2012-11-30)

945
OptiX OSN 7500 II/7500/3500/1500

Values
Valid Values
Default Value
Enabled, Disabled
Enabled
To block a self-loop port, select Enabled. Otherwise, select Disabled.

The loop port shutdown function takes effect only after the IEEE 802.3ah protocol and the loop
detection function are enabled.
A.2.11 Traffic Threshold(Mpbs)(External Ethernet Port Attribute)

Description
The Traffic Threshold(Mpbs) (External Ethernet Port Attribute) parameter specifies the
data flow threshold at external physical ports.

If the data flow at external physical ports is greater than the specified threshold, the
FLOW_OVER alarm is generated.
Values
Valid Values
Default Value
Unit
0-100 (FE), 0-1000 (GE), in

step length of 1
100 (FE), 1000 (GE)
Mbps
Generally, select the value according to the bandwidth.

None.
A.2.12 Broadcast Packet Suppression Threshold (Ethernet Interface

Attributes)
Description
The Broadcast Packet Suppression Threshold(Ethernet Interface Attributes) parameter
allocates the specified bandwidth to the broadcast packets. The bandwidth is allocated on the
Issue 03 (2012-11-30)

946
OptiX OSN 7500 II/7500/3500/1500

basis of the traffic proportion at the port. If the bandwidth allocated to the broadcast packets
reaches the specified threshold, the port discards the broadcast data packets that are received.

l
If less bandwidth is allocated to the broadcast packets, some necessary broadcast services
are affected.
If excessive bandwidth is allocated to the broadcast packets, excessive broadcast packets

may enter the network. Consequently, the network running is affected.
Values
Value Range
Default Value
1-10
You can set this parameter according to the percentage of the traffic at the port. The value 10
means that the whole bandwidth is allocated to the port.
Generally, use the default value.

None.
A.2.13 Enabling Broadcast Packet Suppression (Ethernet Interface

Attributes)
Description
The Enabling Broadcast Packet Suppression (Ethernet Interface Attributes) parameter
specifies whether to enable the function for a port to suppress the broadcast packets and to control
the traffic of the broadcast data packets that enter the port. If the broadcast packet suppression
function is enabled, and if the broadcast traffic exceeds the specified threshold value, the
broadcast packets that enter the port are discarded.

If Enabling Broadcast Packet Suppression is set to Enabled, the port can effectively suppress
the traffic of the broadcast packets by using the statistic function of the network processor on
the board.
Values
Issue 03 (2012-11-30)
Value Range
Default Value
Enabled, Disabled
Disabled

947
OptiX OSN 7500 II/7500/3500/1500

You can set this parameter according to whether to control the traffic of the broadcast packets.

None.
A.2.14 Zero-Flow Monitor (Ethernet Interface Attributes)

Description
The Zero-Flow Monitor parameter specifies whether the traffic on a port is monitored.

After the zero traffic monitoring function is enabled, the port can report the zero traffic alarm
after the state of zero traffic lasts for a certain period. Hence, the user can check whether the
service is interrupted due to the fault on the equipment side.
Values
Value Range
Default Value
Enabled, Disabled
Disabled

Value
Description
Enabled
The zero traffic monitoring function is enabled on the port.
Disabled
The zero traffic monitoring function is disabled on the port.
Set this parameter according to the actual requirement of the user. Set this parameter to
Enabled if the traffic on a port needs to be monitored.
A.2.15 Port Traffic Threshold Time Window(Min)

Description
The Port Traffic Threshold Time Window(Min) parameter specifies the duration for a
VCTRUNK or an IP port to monitor the traffic after the zero traffic monitoring function of the
port is enabled.
Issue 03 (2012-11-30)

948
OptiX OSN 7500 II/7500/3500/1500


If the value of this parameter is too large, the port may fail to report the zero traffic alarm. If the
value of this parameter is too small, the jitter due to the zero traffic alarm may occur on the port.
Values
Value Range
Default Value
Unit
1-30
min
The user can set this parameter according to the actual service requirement.
A.2.16 Jumbo Frame Type

Description
Jumbo Frame Type specifies the value of the jumbo frame type on an Ethernet port. The jumbo
frame indicates the oversized Ethernet frame, whose maximum length is 65535 bytes. The
Ethernet service board determines whether the Ethernet frame is a jumbo frame according to the
value of the jumbo frame type.

Values
Value Range
Default Value
0 to 65535
34928
The value of this parameter must be the same as the value of the accessed jumbo frame type.
Otherwise, the Ethernet board does not consider the frame as a jumbo frame.

The maximum transmission unit (MTU) parameter is used for the Ethernet port. If the length of
Ethernet frames is greater than the length of the jumbo frame, the Ethernet port discards these
Ethernet frames. If the length of Ethernet frames is smaller than the length of the jumbo frame
but is greater than the MTU, the Ethernet port discards the Ethernet frames whose length is
greater than the MTU. If the length of Ethernet frames is smaller than the MTU, the Ethernet
port does not discard the received Ethernet frames.
Issue 03 (2012-11-30)

949
OptiX OSN 7500 II/7500/3500/1500

A.2.17 Default VLAN ID (Ethernet Port Attribute)

Description
The Default VLAN ID (Ethernet Port Attribute) parameter specifies the default VLAN ID
of a port.

Values
Valid Values
Default Value
1-4095
Allocate the default VLAN ID according to the networking plan of the service carrier.

l
If Tag is set to Access for a port, packets without VLAN IDs are added with the default
VLAN IDs when they enter the port. After these packets are transmitted from the port, their
VLAN IDs are peeled off.
If Tag is set to Hybrid for a port, packets without VLAN IDs are added with the default
VLAN IDs when they enter the port. After these packets are transmitted from the port, the
VLAN IDs are peeled off if they are the same as the default VLAN IDs. Otherwise, these
packets are directly transmitted.
If Tag is set to Tag Aware for a port, packets without VLAN IDs are discarded before they
enter the port. Otherwise, these packets are directly transmitted.
A.2.18 VLAN Priority (Ethernet Port Attribute)

Description
The VLAN Priority (Ethernet Port Attribute) parameter specifies the priority of the default
VLAN ID of a port. It indicates the priority of the service quality.

Values
Issue 03 (2012-11-30)
Valid Values
Default Value
0-7

950
OptiX OSN 7500 II/7500/3500/1500

Set the VLAN priority according to the service requirements and the allocation of the service
carrier.

None.
A.2.19 Entry Detection (Ethernet Port Attribute)

Description
The Entry Detection (Ethernet Port Attribute) parameter specifies whether to identify the tag
labels in the data packets.

The entry detection function can be disabled in the port-based services only. If the entry detection
function is disabled, you may fail to configure other VLAN-based services.
Values
Valid Values
Default Value
Enabled, Disabled
Enabled

Value
Description
Enabled
The port checks the Tag label. In this case, the Tag attribute
of the port is valid.
Disabled
The port does not check the tag label. In this case, the Tag
attribute of the port is invalid.
l
To transmit the data packet transparently, the user can disable the entry detection function.
To forward the data packet according to the contents of the data packet, the user can enable
the entry detection function.

None.
Issue 03 (2012-11-30)

951
OptiX OSN 7500 II/7500/3500/1500

A.2.20 Tag Identifier

Description
Tag Identifier indicates that the Ethernet port supports IEEE 802.1Q Ethernet packets that
contain VLAN tags. You can set three attributes to differentiate the packets from each other so
that these packets can be transmitted efficiently.

Values
Value Range
Default Value
Access, Tag Aware, Hybrid
Tag Aware
The following table lists the description of each value.

Value
Description
Access
A port receives only the packets that do not

contain VLAN tags. After receiving the packets,
the port adds the default VLAN tag (PVID) to
these packets. When the packets are transmitted
from the port, the VLAN tags are stripped off the
packets.
Tag Aware
A port receives only the packets that contain

VLAN tags and discards the packets that do not
contain VLAN tags. When the packets are
transmitted from the port, they are directly
forwarded to the next port.
Hybrid
A port can receive all the packets regardless of

VLAN tags. After receiving the packets that do
not contain VLAN tags, the port adds the default
VLAN tag (PVID) to these packets. When the
packets are transmitted from the hybrid port, the
egress port determines whether the VLAN tags
contained in the packets are the same as the
PVID. If yes, the egress port strips the VLAN
tags off the packets and then forwards these
packets. Otherwise, the egress port directly
forwards these packets.
The tag attributes are configured for MAC ports and VCTRUNK ports. Hence, the VCTRUNK
ports at both ends of the trunk link can be configured with the tag attributes. In the case of a link,
Issue 03 (2012-11-30)

952
OptiX OSN 7500 II/7500/3500/1500

the services are available only when the parameters of the tag attributes are the same for the
VCTRUNK ports on the source and sink ports. No requirements are proposed for the tag
attributes of MAC ports.

l
If Tag is set to Access for a port, packets without VLAN IDs are added with the default
VLAN IDs when they enter the port. After these packets are transmitted from the port, their
VLAN IDs are peeled off.
If Tag is set to Hybrid for a port, packets without VLAN IDs are added with the default
VLAN IDs when they enter the port. After these packets are transmitted from the port, the
VLAN IDs are peeled off if they are the same as the default VLAN IDs. Otherwise, these
packets are directly transmitted.
If Tag is set to Tag Aware for a port, packets without VLAN IDs are discarded before they
enter the port. Otherwise, these packets are directly transmitted.
For C-Aware and S-Aware ports, the tag attribute cannot be set.
Related Information
Mapping relationship between the packets handled by the port and the tag identifiers
Packet Type
Attribute of the Ingress

Port
Handling Method
Ethernet packets that contain

tags
Tag aware
The port transmits these

packets.
Access
The port discards these

packets.
Hybrid

packets.
Tag aware
The port discards these

packets.
Access

packets after adding the
default VLAN ID to these
packets.
Hybrid

packets after adding the
default VLAN ID to these
packets.
Ethernet packets that do not

contain tags
A.2.21 Mapping Protocol

Description
The Mapping Protocol parameter specifies the mapping protocol of the VCTRUNK port.
Issue 03 (2012-11-30)

953
OptiX OSN 7500 II/7500/3500/1500


The Mapping Protocol parameter of the VCTRUNK is the basic setting of the VCTRUNK port.
If the parameter value is different from that of Mapping Protocol for the VCTRUNK of the
interconnected equipment, the service is interrupted.
Values
Table A-1 shows the value range of each type of board.
Table A-1 The mapping protocol supported by each type of board
Board Name
Value Range
Default Value
N1EMS4, N1EGS4, N3EGS4,

N4EGS4, N1EFT8, N1EFT8A,
N1EGT2, N2EGT2, R1EFT4
l GFP
GFP
N4EFS0, N5EFS0, N2EFS4, N3EFS4,

N2EGS2, N3EGS2, N1EAS2,
N1EFS0A, N1EMS2
GFP
GFP
N2EMR0, N2EGR2
l GFP
GFP
l LAPS
l HDLC
l LAPS

Value
Description
GFP
Uses the GFP protocol to encapsulate the data of the

VCTRUNK port.
LAPS
Uses the LAPS protocol to encapsulate the data of the

VCTRUNK port.
HDLC
Uses the HDLC protocol to encapsulate the data of the

VCTRUNK port.
The value of Mapping Protocol for VCTRUNK of the local equipment must be the same as
that of Mapping Protocol for the VCTRUNK of the interconnected equipment.

None.
Issue 03 (2012-11-30)

954
OptiX OSN 7500 II/7500/3500/1500

A.2.22 Scramble
Description
The Scramble parameter specifies whether to scramble the payload area of the encapsulation
protocol and the scramble mode.

If the value of Scramble for the VCTRUNK of the local equipment is different from that of
Scramble for the VCTRUNK of the interconnected equipment, the service is interrupted.
Values
Table A-2 Scramble supported by each type of board
Board Name
Value Range
N4EFS0, N2EFS4, N2EGS2,

N1EFT8, N1EFT8A, N1EGT2,
R1EFT4, N1EMS4, N1EGS4,
N3EGS4, N4EGS4, N1EAS2,
N1EFS0A, N1EMS2, N5EFS0,
N3EFS4, N3EGS2, N2EGT2
l Unscramble
N2EMR0, N2EGR2
Scramble mode[X43+1]
l Scramble mode[X43+1]
Default
Value
Scramble mode
[X43+1]
Scramble mode
[X43+1]

Value
Description
Unscramble
Does not scramble the payload area.
Scramble mode[X43+1]
Scrambles the payload area in [X43+1] mode.
The value of Scramble for VCTRUNK must be the same as that of Scramble for the VCTRUNK
of the interconnected equipment.

For the N4EFS0, N2EFS4, N2EGS2, N1EFT8, N1EFT8A, N1EGT2 or R1EFT4 board, if
Mapping Protocol is set to LAPS, Scramble can be set to Unscramble or Scramble mode
[X43+1] only.
Issue 03 (2012-11-30)

955
OptiX OSN 7500 II/7500/3500/1500

A.2.23 Set Inverse Value for CRC

Description
The Set Inverse Value for CRC parameter specifies whether to set an inverse value for the
CRC field of the HDLC or LAPS protocol.

If the value of Set Inverse Value for CRC for the VCTRUNK of the local equipment is different
from that of Set Inverse Value for CRC for the VCTRUNK of the interconnected equipment,
the service is interrupted.
Values
Value Range
Default Value
Yes, No
Yes

Value
Description
Yes
Sets an inverse value for the CRC field.
No
Does not set an inverse value for the CRC field.
The value of Set Inverse Value for CRC for VCTRUNK of the local equipment must be the
same as that of Set Inverse Value for CRC for the VCTRUNK of the interconnected equipment.

This parameter takes effect only when Mapping Protocol is set to LAPS or HDLC.
A.2.24 Check Field Length

Description
The Check Field Length parameter specifies the length of the CRC field of the mapping
protocol.

If Mapping Protocol is set to HDLCor LAPS, and if the value of Check Field Length is
different from that for the interconnected VCTRUNKs at the two ends, the service is interrupted.
Issue 03 (2012-11-30)

956
OptiX OSN 7500 II/7500/3500/1500

Values
Table A-3 The length of the CRC field supported by each type of board
Mapping
Protocol
Value Range
Default Value
N4EFS0, N5EFS0,
N2EFS4, N3EFS4,
N2EGS2, N3EGS2,
N1EFS0A, N1EMS2,
N1EAS2
GFP
l FCS32
FCS32
N1EMS4, N1EGS4,
N3EGS4, N4EGS4,
N1EGT2, N2EGT2
GFP
Board Name
N2EMR0, N2EGR2,
N1EGT2, N1EFT8,
N1EFT8A, R1EFT4
l No
l FCS32
FCS32
l No
LAPS
FCS32
HDLC
FCS32
GFP
l FCS32
FCS32
l No
LAPS
FCS32

Value
Description
No
The protocol frame does not contain the CRC field. Only the
GFP protocol supports this option.
FCS32
The CRC field of the protocol frame contains 32 bits.
If Mapping Protocol is set to HDLC or LAPS, the value of Check Field Length must be
consistent for the interconnected VCTRUNKs at the two ends.

If Mapping Protocol is set to HDLC or LAPS, select FCS32 only.
A.2.25 FCS Calculated Bit Sequence

Description
The FCS Calculated Bit Sequence parameter specifies the sequence of storing the bits in the
CRC field of the mapping protocol.
Issue 03 (2012-11-30)

957
OptiX OSN 7500 II/7500/3500/1500


If the value of FCS Calculated Bit Sequence for the VCTRUNK of the local equipment is
different from that of FCS Calculated Bit Sequence for the VCTRUNK of the interconnected
equipment, the service is interrupted.
Values
Table A-4 FCS calculated bit sequence supported by each type of boards
Board Name
N1EMS4, N1EGS4,
N3EGS4, N4EGS4,
N1EGT2, N2EGT2
Mapping
Protocol
Value Range
Default Value
GFP
Big endian
l Mapping Protocol:
GFP
l FCS Calculated Bit
Sequence: Big endian
l LAPS
Little endian
l HDLC
l Mapping Protocol:
GFP
N2EMR0, N2EGR2
GFP
Big endian
l Mapping Protocol:
GFP
LAPS
Little endian
Big endian
l Mapping Protocol:
GFP
N4EFS0, N5EFS0,
N2EFS4, N3EFS4,
N2EGS2, N3EGS2,
N1EFS0A, N1EMS2,
N1EAS2
GFP
Big endian
N1EFT8, N1EFT8A,
R1EFT4
l GFP
Big endian
l LAPS
Little endian
l Mapping Protocol:
GFP
l HDLC
l Mapping Protocol:
GFP
Issue 03 (2012-11-30)
Value
Description
Big endian
Stores the FCS field based on Big endian.

958
OptiX OSN 7500 II/7500/3500/1500

Value
Description
Little endian
Stores the FCS field based on Little endian.
The value of FCS Calculated Bit Sequence for the VCTRUNK of the local equipment must
the same as that of FCS Calculated Bit Sequence for the VCTRUNK of the interconnected
equipment.

None.
A.2.26 Extension Header Option

Description
The Extension Header Option parameter specifies whether Mapping Protocol of the GFP
protocol supports the extension header.

For the N1EFT8, N1EFT8A, R1EFT4 or N1EAS2 board, if the value of Extension Header
Option is inconsistent for the VCTRUNK ports of the interconnected equipment at the two ends,
the service is interrupted. Moreover, the FCS_ERR alarm is reported.
Values
Table A-5 Extension header option supported by each type of board
Board Name
Value Range
Default Value
N4EFS0, N2EFS4,
N2EGS2, N1EFT8,
N1EFT8A, N1EGT2,
N2EGT2, R1EFT4,
N1EAS2, N2EMR0,
N2EGR2
l Yes
No
N1EMS4, N1EGS4,
N3EGS4, N4EGS4,
N5EFS0, N3EFS4,
N3EGS2, N1EFS0A,
N1EMS2
No
l No
No

Issue 03 (2012-11-30)

959
OptiX OSN 7500 II/7500/3500/1500

Value
Description
Yes
Supports the extension header.
No
Does not support the extension header.
Select the value according to whether the GFP protocol is required to support the extension
header.

This parameter takes effect only when Mapping Protocol is set to GFP.
A.3 Ethernet Service Associated Parameters (Packet Mode)

This topic describes the parameters for configuring Ethernet services.
A.3.1 PW Signaling Type(PW Management)

Description
The PW Signaling Type (PW Management) parameter can query the signaling type of a PW.
The signaling can be of the dynamic or static type. In the case of the dynamic PW, the services
are available after the signaling negotiation is successful. In the case of the static PW, the
signaling negotiation is not required. Currently, the OptiX OSN equipment supports only the
static PW.

This parameter does not affect the system operation.
Values
Value Range
Default Value
Static
Issue 03 (2012-11-30)
Value
Description
Static
Indicates that the PW is statically created.

960
OptiX OSN 7500 II/7500/3500/1500

None.

None.
A.3.2 Bearer Type (E-Line Service)

Description
The Bearer Type (E-Line Service) parameter specifies the bearer type for different types of
Ethernet services. The value of this parameter can be set to Port, PW, or QinQ Link.

Values
Value Range
Default Value
Port, PW, QinQ Link

Value
Description
PW
The bearer is the PW, and the PW ID needs to be specified.
Port
The bearer is the physical port, and the slot ID and port
number needs to be specified.
QinQ Link
The bearer is the QinQ link, and the QinQ link ID needs to be
specified.
l
The bearer of the E-Line service V-NNI can be the PW, port, or QinQ link.
The bearer of the E-LAN service V-NNI can be the PW, port, or QinQ link.
The bear of the E-AGGR service V-NNI can be the PW or port.
A.3.3 PW ID(E-Line Service)

Description
The PW ID parameter identifies the PW.
Issue 03 (2012-11-30)

961
OptiX OSN 7500 II/7500/3500/1500


Values
Value Range
Default Value
1-4294967295
None.

None.
A.3.4 BPDU
Description
The BPDU parameter sets whether the service needs transparently transmit the bridge protocol
data unit (BPDU) packets. The BPDU is the information transmitted between bridges. It is used
to switch information between bridges, and then the spanning tree of the network is computed.

If the BPDU transparent transmission identifier of the Ethernet service of an NE is enabled, the
port where the service V-UNI resides cannot process the BPDU packets. After the BPDU
transparent transmission is enabled, the BPDU packets are transmitted.
Values
Value Range
Default Value
Transparently Transmitted, Not

Transparently Transmitted
Not Transparently Transmitted
Issue 03 (2012-11-30)
Value
Description
Transparently Transmitted
BPDU packets are transparently transmitted to and processed

on the opposite NE instead of being terminated on the local
NE.

962
OptiX OSN 7500 II/7500/3500/1500

Value
Description
Not Transparently
Transmitted
BPDU packets are processed as service packets, which are

processed differently according to port attributes. When the
port attribute is Tag Aware, BPDU packets are discarded
because they do not carry any VLAN IDs.
If the BPDU packets need be transparently transmitted to the opposite end of the network, set
the BPDU to Transparently Transmitted during the service creation.
If the BPDU packets need be processed on the local NE as service packets for computing the
network spanning tree, set the BPDU to Not Transparently Transmitted during the service
creation.

None.
A.3.5 MTU(bytes)(E-Line Service)

Description
The MTU(bytes) parameter indicates the maximum transmitted packet length, which is the
length of the packet payload.

If the length of the packet payload exceeds the value set by the MTU, the packets are discarded
during the forwarding.
Values
Value Range
Default Value
Unit
46-9000
1500
Byte
MTU(bytes) should not be less than the maximum length of the user packet payload. Otherwise,
the packets whose length exceeds the service MTU are discarded. Hence, MTU(bytes) should
be set to a value larger than the maximum length of the user packet payload.

The value of MTU(bytes) and Max Frame Length(byte) of the port can be separately
configured.
Issue 03 (2012-11-30)

963
OptiX OSN 7500 II/7500/3500/1500

A.3.6 Static MAC Address (E-LAN Service)

Description
The Static MAC Address parameter indicates the packet forward MAC address that is manually
configured for the E-LAN service. This MAC address is not automatically aged. When the
destination MAC address is the same as this MAC address, the packets are directly forwarded.

Values
Value Range
Default Value
VLAN ID, MAC Address, Egress Interface
The following table lists the values of the sub-parameters.

Parameter
Value Range
Default Value
VLAN ID
1 to 4094
MAC Address
00-00-00-00-00-01 to FFFF-FF-FF-FF-FE
Egress Interface
For example, 13N1PEG16-2(Port-2)[10]
The static MAC address can be set as a unicast address, rather than as a multicast or broadcast
address.

None.
Related Information
When the E-LAN service works in IVL mode, packets are forwarded based on the VLAN and
MAC address.
When the E-LAN service works in SVL mode, packets are forwarded based on the MAC address.
Issue 03 (2012-11-30)

964
OptiX OSN 7500 II/7500/3500/1500

A.3.7 Self-Learning MAC Address (E-LAN Service)

Description
The Self-Learning MAC Address (E-LAN Service) parameter indicates that the MAC address
is obtained by the board through self-learning.

Querying the MAC address does not affect the system. Clearing the MAC address clears the
original unicast forwarding trails. In this case, the port broadcasts the received packets whose
MAC address is the deleted MAC address, and forwards these packets when the port learns the
deleted MAC address again.
Values
Value Range
Default Value
VLAN ID, MAC Address,

Egress Interface

Parameter
Value Range
Default Value
VLAN ID
1-4094
MAC Address
00-00-00-00-00-01 to FFFF-FF-FF-FF-FE
Egress Interface
For example, 13N1PEG16-2(Port-2)[10]

Parameter
Description
VLAN ID
Indicates the VLAN ID that is learnt by the board.
MAC Address
Indicates the MAC address that is learnt by the board.
Egress Interface
Indicates the egress interface that is learnt by the board.
Configure the parameter according to the service configuration information.
Issue 03 (2012-11-30)

965
OptiX OSN 7500 II/7500/3500/1500


When the E-LAN service works in IVL mode, packets are forwarded based on the VLAN and
MAC address.
When the E-LAN service works in SVL mode, packets are forwarded based on the MAC address.
Related Information
None.
A.3.8 Aging Time (min)(E-LAN Service)

Description
Set the Aging Time (min) parameter to set the aging time of the learnt MAC address. The Aging
Time (min) parameter indicates that the MAC address is automatically aged after the timing is
set.

When the Aging Time (min) parameter is reset, the MAC addresses learnt before the resetting
remains aged according to the original aging time, and the MAC addresses learnt after the
resetting are aged according to the current aging time. When the aging time is up, the original
unicast E-LAN services are broadcast.
Values
Value Range
Default Value
Unit
1-640
Minute as the unit and one as the

spacing.
Set the aging time of MAC addresses according to the user requirements. The minimum time is
one minute.

None.
Related Information
None.
Issue 03 (2012-11-30)

966
OptiX OSN 7500 II/7500/3500/1500

A.3.9 Default Forwarding Priority

Description
The Default Forwarding Priority parameter indicates the forwarding priority that the NE sets
to the user packets on the V-UNI side by default.
The OptiX OSN NE forwards and schedules packets according to the priorities of the packets.
The forwarding priorities supported by the OptiX OSN NE include CS7, CS6, EF, AF4, AF3,
AF2, AF1, and BE (arranged from the highest priority to the lowest).

Values
Value Range
Default Value
BE, AF1, AF2, AF3, AF4, EF, CS6, CS7,

NONE
BE

Value
Description
BE
By default, the user packets on the V-UNI side are set to BE.
AF1
By default, the user packets on the V-UNI side are set to AF1.
AF2
AF3
AF4
EF
By default, the user packets on the V-UNI side are set to EF.
CS6
By default, the user packets on the V-UNI side are set to CS6.
CS7
By default, the user packets on the V-UNI side are set to CS7.
NONE
The priority of the user packets on the V-UNI side is set according to the
mapping relationship in the DS domain.
CS7: Indicates the highest forwarding priority, for delivering the control packets (very important
protocol packets) in the network.
CS6: Indicates the priority that is lower than CS7, for delivering the control packets (important
protocol packets) in the network.
Issue 03 (2012-11-30)

967
OptiX OSN 7500 II/7500/3500/1500

EF: Indicates the expedited forwarding priority that is lower than CS6, for the low delay services
(for example, voice services).
AF4: Indicates the assured forwarding priority 4, whose forwarding priority is lower than EF.
AF3: Indicates the assured forwarding priority 3, whose forwarding priority is lower than AF4.
BE: Indicates the best effort forwarding priority that is the lowest forwarding priority, for the
services without QoS in the network.

If a certain V-UNI does not use the V-UNI ingress policy, the packets on the V-UNI are
forwarded according to Default Forwarding Priority. If the V-UNI ingress policy is used, the
packets that do not match the Traffic classification of this policy are forwarded according to
Default Forwarding Priority.
A.3.10 Default Packet Relabeling Color(E-LAN Service)

Description
The Default Packet Relabeling Color indicates the color that the NE sets to the user packets
on the V-UNI side by default.
On a PTN NE, the packet color indicates the priority for discarding the packet. The packet colors
are red, yellow, and green. The red packet has the highest discard priority, and thus is discard
first in the case of congestion. The green packet has the lowest discard priority. The yellow
packet has the middle discard priority.

None.
Values
Value Range
Default Value
Red, Yellow, Green, None
Green
Issue 03 (2012-11-30)
Value
Description
Red
The user packets on the V-UNI side are set as red.
Yellow
The user packets on the V-UNI side are set as yellow.
Green
The user packets on the V-UNI side are set as green.

968
OptiX OSN 7500 II/7500/3500/1500

Value
Description
None.
The priority of the user packets on the V-UNI side is set

according to the mapping relationship of the DS domain.
The user packets of a higher priority should be marked green. The user packets of a lower priority
should be marked red. The user packets of a medium priority should be marked yellow.

If a certain V-UNI does not use the V-UNI ingress policy, the packets on the V-UNI are marked
according to Default Packet Relabeling Color. If the V-UNI ingress policy is used, the packets
that do not match the Traffic classification of this policy should be marked according to Default
Packet Relabeling Color.
A.3.11 Split Horizon Group ID(E-LAN Service)

Description
The Split Horizon Group ID parameter identifies the split horizon group.

Values
Split Horizon Group ID
Value Range
Default Value
None.

None.
Related Information
None.
Issue 03 (2012-11-30)

969
OptiX OSN 7500 II/7500/3500/1500

A.3.12 Split Horizon Group Member (E-LAN Service)

Description
The Split Horizon Group Member parameter indicates the logical port member in a split
horizon group.

The member ports added to the same split horizon group cannot communicate with each other.
Values
Value Range
Default Value
Slot number - board - port number - VLANs
One service can be configured with only one split horizon group.

None.
Related Information
None.
A.3.13 Source Interface Type(E-AGGR Service)

Description
Set the Source Interface Type parameter to set the source interface type of the VLAN switching
table for the E-AGGR service. This parameter can be set to V-UNI or V-NNI.

Set the source interface type of the E-AGGR service as the same as the opposite logical interface
type.
Values
Value Range
Default Value
V-UNI, V-NNI

Issue 03 (2012-11-30)

970
OptiX OSN 7500 II/7500/3500/1500

Value
Description
V-UNI
Indicates that the source interface is a V-UNI interface.
V-NNI
Indicates that the source interface is a V-NNI interface.
The logical interface type of the source interface of the VLAN switching table for the E-AGGR
service can be set to V-UNI or V-NNI. The interconnected logical interfaces, however, should
be of the same type.

None.
Related Information
None.
A.3.14 Sink Interface Type(E-AGGR Service)

Description
Set the Sink Interface Type parameter to set the sink interface type of the VLAN switching
table for the E-AGGR service. This parameter can be set to V-UNI or V-NNI.

Set the sink interface type of the E-AGGR service same as the opposite logical interface type.
Otherwise, the E-AGGR service is not available.
Values
Value Range
Default Value
V-UNI, V-NNI
Issue 03 (2012-11-30)
Value
Description
V-UNI
Indicates that the sink interface is a V-UNI interface.
V-NNI
Indicates that the sink interface is a V-NNI interface.

971
OptiX OSN 7500 II/7500/3500/1500

The logical interface type of the sink interface of the VLAN switching table for the E-AGGR
service can be set to V-UNI or V-NNI. The interconnected logical interfaces, however, should
be of the same type.

None.
Related Information
None.
A.4 CES Service Associated Parameters

This topic describes the parameters for configuring CES services.
A.4.1 Packet Loading Time (us)

Description
The Packet Loading Time (us) parameter specifies the packet loading duration.
The efficiency of packet loading can be improved after the packet loading time is set.

The packet loading time affects the number of frames of E1 signals in each packet.
Values
Value Range
Default Value
Unit
125-5000
1000
us
The value of the packet loading time ranges from 125 to 5000 in steps of 125.
The default bandwidth for a PW that transmits an CES service is 3 Mbit/s. If Packet Loading
Time (us) is set to 125 or 250, and if RTP Header is set to Enable Huawei RTP or Enable a
Standard RTP, the bandwidth for a PW is 4 Mbit/s.

The packet loading time is closely related to the jitter compensation buffering time. The jitter
compensation buffering time must be greater than double packet loading time.
Issue 03 (2012-11-30)

972
OptiX OSN 7500 II/7500/3500/1500

Before changing the parameter value of a PW, you need to ensure that the PW is not bound with
the service. After the change, you need to bind the PW with the service, and then check whether
the parameter value is changed.
Related Information
If the default value of the packet loading time is 1000 ms/packet, because the rate of E1 signals
is 8000 frames/s, the number of the frames in each packet is: 8000 frames/s * 1000 ms/packet
= 8 frames.
A.4.2 RTP Header

Description
The RTP Header parameter specifies whether the RTP header function is enabled.
The RTP header is used to load clock signals.
Figure A-1 RPT Header Format
(M) to 0.
Payload type (PT):
l
The PE on the upstream PW can detect exceptional packets according to the received PT
value.
The sequence number must be the same as the serial number in the CESoPSN control word.
l
Issue 03 (2012-11-30)
973
OptiX OSN 7500 II/7500/3500/1500



The adaptive clock recover (ACR) is supported only when the RTP header is enabled.
Values
Value Range
Default Value
Disable, Enable the Huawei RTP, Enable

a Standard RTP
Disable

Value
Description
Disable
Indicates that the RTP is disabled.
Enable Huawei RTP
Indicates that the Huawei RTP is enabled.
Enable a Standard RTP
Indicates that a standard RTP is enabled.
The default bandwidth for a PW that transmits an CES service is 3 Mbit/s. If Packet Loading
Time (us) is set to 125 or 250, and if RTP Header is set to Enable Huawei RTP or Enable a
Standard RTP, the bandwidth for a PW is 4 Mbit/s.

A.4.3 Jitter Compensation Buffering Time (us)

Description
The Jitter Compensation Buffering Time (us) parameter specifies the size of the jitter buffer.
The jitter compensation buffering time is configured to absorb jitters on the network side.

The jitter compensation buffering time affects the delay of services.
Issue 03 (2012-11-30)

974
OptiX OSN 7500 II/7500/3500/1500

If the jitter compensation buffering time is set, the subsequent operations are performed after
the system has received packets for more than a half of the jitter compensation buffering time.
Values
Value Range
Default Value
Unit
125-64000
8000
us
The value of the jitter compensation buffering time ranges from 125 to 64000 in steps of 125.

The packet loading time is closely related to the jitter compensation buffering time. The jitter
compensation buffering time must be greater than double packet loading time.
Related Information
The principle of delays on the network side and jitters are as follows.
Total delays of CES services include:
l
TDM transmission time (can be neglected)
Packet encapsulation duration (packet loading duration)
Packet processing and forwarding duration
Packet transmission duration on Ethernet links
Assume that the interval between the arrival time of packet 1 and packet 2 is T. Encapsulation
of packet 1 is completed at t(0). After t1, packet 1 is processed and forwarded to the opposite
end. Encapsulation of packet 2 begins at t(0) and is completed after tp. Then, after t2, packet 2
is processed and forwarded to the opposite end. T = (tp + t2) - t1 = tp + (t2 - t1), that is,
transmission time difference between packet 1 and 2 equals the sum of packet loading time and
transmission time of the packets 1 and 2.
The interval between the arrival time of two packets is called jitters on the network side.
The more serious the delay jitter on the network side, the more system resource occupied to
smooth the jitters.
The working principle of the jitter buffer is as follows.
The jitter buffer is in the egress direction (from the network side to the TDM side) of the link.
Packets are transmitted on the network side and received periodically on the TDM side. The
packets received on the network side are burst packets, E1 services received on the TDM side
are constant data streams.
If the jitter compensation buffering time is set, after the system has received packets for a half
of the jitter compensation buffering time, the subsequent operations are performed. The attributes
Issue 03 (2012-11-30)

975
OptiX OSN 7500 II/7500/3500/1500

of a jitter buffer include depth and delay. When configuring advanced attributes of PW on the
NMS, the jitter compensation buffering time is the depth of a jitter buffer. If the depth of a jitter
buffer is 8000 ms, the subsequent operations are performed after the jitter buffer has received
packets for 4000 ms. Therefore, even the packets from the network side haves jitters, the jitter
buffer stabilizes the downstream data streams.
The jitter compensation buffering time varies with network conditions. If the delays or jitters of
a network are large, the jitter compensation buffering time needs to be set to a greater value, and
therefore, the delay of the link is prolonged. If the network-side performance is stable with a
fixed delay, the size of the jitter buffer can be adjusted to approach the packet loading time to
decrease the delay of the link, In this manner, the delay of the entire link is increased to greater
than maximum interval between the arrival time of packet 1 and packet 2.
A.4.4 Clock Mode

Description
The Clock Mode parameter specifies the re-timing mode of a port.
The E1 signal can be output with the 2M clock from cross-connect boards or upstream services,
instead of the clock from the internal phase-locked loop, as the reference clock. If the tributary
clock is of inferior quality, this parameter is set to use the external clock from the cross-connect
board for tributary re-timing.

The clock mode affects the reference clock for outputting E1 signals.
Values
Value Range
Default Value
Master Mode, Slave Mode, Line Clock Mode
Master Mode

Value
Description
Master Mode
Indicates that the internal clock is adopted.
Slave Mode
Indicates that the clock from ACR is adopted.
Line Clock Mode
Indicates that the clock from line boards is

adopted.
None.
Issue 03 (2012-11-30)

976
OptiX OSN 7500 II/7500/3500/1500


Only the slave mode supports the adaptive clock recover (ACR) function.
The parameters of a PW can be modified before the PW is bound with services, but can be
verified after the PW is bound with services.
A.5 Data Service Associated Parameters (TDM Mode)

This topic describes the parameters for configuring Ethernet services and SAN services.
A.5.1 Operation Type (EPL Service)

Description
The Operation Type (EPL Service) parameter specifies whether to add, strip, translate or
transparently transmit VLAN labels for service packets at a port when Service Type is set to
EVPL(QinQ).

After you select an operation type, the system performs the relevant operation.
Values
Board Name
Valid Values
Default Value
N1EMS4,
N1EGS4,
N3EGS4,
N4EGS4
l For bidirectional services, the options are as

follows:
Add S-VLAN
Add S-VLAN
Transparently Transmit C-VLAN
Transparently Transmit S-VLAN
Translate C-VLAN
Translate S-VLAN
l For unidirectional services, the options are as
follows:
Add S-VLAN
Add S-VLAN and C-VLAN
Strip C-VLAN
Strip S-VLAN
Strip S-VLAN and C-VLAN
Transparently transmit C-VLAN
Transparently transmit S-VLAN
Translate C-VLAN
Translate S-VLAN
Issue 03 (2012-11-30)

977
OptiX OSN 7500 II/7500/3500/1500

Board Name
Valid Values
Default Value
N1EAS2
l For bidirectional services, the options are as

follows:
Add S-VLAN
Add S-VLAN
Translate S-VLAN
l For unidirectional services, the options are as
follows:
Add S-VLAN
Strip S-VLAN
Translate S-VLAN
Issue 03 (2012-11-30)
Value
Description
Add S-VLAN
Indicates that the one layer of S-VLAN label is added to the

processed packets in the service.
Translate S-VLAN
If the source S-VLAN labels of the packets processed in the

service are translated into the sink S-VLAN labels, the source
S-VLAN label must be different from the sink S-VLAN label.
Transparently transmit SVLAN
Forwards the service packets according to the port or S-VLAN.

After the packets are processed in the service, the S-VLAN
labels in the packets are not changed.
Translate C-VLAN
If the source C-VLAN labels of the packets processed in the

service are translated into the sink C-VLAN labels, the source
C-VLAN labels must be different from the sink C-VLAN labels.
Transparently transmit CVLAN
Forwards the service packets according to the port or C-VLAN.

After the packets are processed in the service, the C-VLAN
labels in the packet are not changed.
Add S-VLAN and CVLAN
Indicates that the C-VLAN and S-VLAN labels are added to the
packets processed in the service.
Strip C-VLAN
Strips the C-VLAN label.
Strip S-VLAN
Strips the S-VLAN label.
Strip S-VLAN and CVLAN
Strips the S-VLAN and C-VLAN labels.

978
OptiX OSN 7500 II/7500/3500/1500

Select a proper item according to network planning and service model.

None.
A.5.2 Service Type (EPL Service)

Description
The Service Type (EPL Service) parameter specifies the Ethernet private line service type.

Values
Board Name
Valid Values
Default Value
N1EFT8, N1EFT8A, N1EGT2,

N2EGT2, R1EFT4
EPL
EPL

N2EGS2, N3EGS2, N2EMR0,
N2EGR2, N1EFS0A, N1EMS2
EPL, Transit(MPLS), EVPL

(MPLS)
EPL

N4EGS4, N1EAS2
EPL, EVPL(QinQ)
EPL

Value
Description
EPL
Indicates the transparent transmission service or the VLAN

private line service.
Transit(MPLS)
Indicates the Ethernet virtual private line service of switching

MPLS labels.
EVPL(QinQ)
Indicates the Ethernet QinQ virtual private line service.
EVPL(MPLS)
Indicates the Ethernet virtual private line service of adding or

deleting MPLS labels.
Select a service type as required.
Issue 03 (2012-11-30)

979
OptiX OSN 7500 II/7500/3500/1500


None.
A.5.3 Encapsulation Format of P Port (Network Attributes)

Description
Encapsulation Format of P Port (Network Attributes) indicates that the board supports
receiving of data packets in the MPLS encapsulation format and normal Ethernet data packets.
The port needs to process different types of packets in different ways, so you need to set the port
to a PE port or a P port. The PE port is not configured with the encapsulation format, while the
P port is configured with the encapsulation format. The P port indicates a port for connecting
the equipment of the network provider, so the P port receives data packets in the MPLS
encapsulation format. You can set the packet encapsulation format of the P port by running the
configuration command.

If the encapsulation format of the data packet that enters the port is inconsistent with the
configured encapsulation format of the port, the data packet is discarded.
Values
Value Range
Default Value
MartinioE, stack VLAN
MartinioE

Value
Description
MartinioE
Figure A-2 shows the encapsulation format of

MartinioE.
Stack VLAN
Figure A-3 shows the encapsulation format of

Stack VLAN.
The user can choose an encapsulation format according to the requirements of the service.
Different encapsulation formats support different types of data packets. When the encapsulation
format is inconsistent with the type of the receive data packet, the data packet is discarded. When
configuring services, the user needs to make sure that the encapsulation format of the port is
consistent with the type of the data packet that is transmitted by the interconnected equipment.

None.
Issue 03 (2012-11-30)

980
OptiX OSN 7500 II/7500/3500/1500

Related Information
Figure A-2 Encapsulation format of MartinioE
DA SA
0x8847
Tunnel
VC
Ethernet Data
N
Figure A-3 Encapsulation format of Stack VLAN
DA SA
0x8100
VLAN
VLAN TAG L3Data
A.5.4 C-VLAN and S-VLAN

Description
The C-VLAN and S-VLAN parameter specifies the two types of VLAN tags defined in the
QinQ service and IEEE 802.1ad. C-VLAN is taken as the client VLAN tag. S-VLAN is taken
as the service VLAN tag. C-VLAN Tag (C-TAG) indicates the VLAN tag on the client side,
and S-VLAN Tag (S-TAG) indicates the VLAN tag at the service layer of the carrier.
DMAC
SMAC
S-VLAN
C-VLAN
Data
FCS
6 bytes
6 bytes
4 bytes
4 bytes
4 bytes

Values
Valid Values
Default Value
Empty, 1-4095
Empty
Issue 03 (2012-11-30)

981
OptiX OSN 7500 II/7500/3500/1500

Value
Description
Empty
Indicates that the port does check the C-VLAN/S-VLAN. The

services are forwarded according to the port.
1-4095
Indicates that the port checks the C-VLAN/S-VLAN. The

services are forwarded according to the port and C-VLAN/SVLAN.
Select the value according to the network. Generally, select C-VLAN and S-VLAN allocated
by the carrier.

None.
A.5.5 VLAN ID (For Creation of Ethernet Virtual Private Lines)

Description
VLAN ID-- stands for virtual local area network identifier. If port+VLAN is selected in the
policy of using a port, you can select different VLAN IDs (1-4095) to represent different Ethernet
services.

Values
Value Range
Default Value
1 to 4095
l
The value range is relevant to the encapsulation format of the P port (Per-NE configuration).
In the case of Martinio E, the value ranges from 16 to 1023. In the case of stack VLAN,
the value ranges from 1 to 4095.
The VLAN IDs at both ends of a link must be the same. In the case of different Ethernet
services, you can set the VLAN ID to different values.

This parameter is valid only when you set "Flow Type" to "Port+VLAN".
Issue 03 (2012-11-30)

982
OptiX OSN 7500 II/7500/3500/1500

A.5.6 MAC Address Aging Time / Aging Time Unit

Description
The MAC Address Aging Time parameter specifies the valid duration of a dynamically learnt
MAC address in the MAC address table.
During the specified aging time:
l
If no more packets are received from this MAC address, the MAC address is deleted from
the MAC address table.
If more packets are received from this MAC address, reset the aging time of the MAC
address.
The aging time includes two parts: aging time value and aging time unit.

The parameter value may affect the forwarding efficiency of the EPLAN or EVPLAN service.
l
Extremely long aging time results in expiration of the MAC address table in the board. In
this case, the board makes an incorrect decision to filter or forward packets. Consequently,
the forwarding efficiency is affected.
Extremely short aging time results in frequent refreshing of the MAC address table. In this
case, the destination addresses fail to be found in the MAC address table for the large
quantity of received data packets. The board has to broadcast these data packets to all the
ports. Consequently, the forwarding efficiency is greatly affected.
Values
The value range of the aging time value is as follows:
Value Range
Default Value
1-120
The value range of the aging time unit is as follows:

Value Range
Default Value
Min, Hour, Day
Min
The parameter value may affect the forwarding efficiency of the EPLAN or EVPLAN service.
Generally, use the default value.
For example, to set the aging time to 20 days, set the aging time to 20, and then set the aging
time unit to Day.
Issue 03 (2012-11-30)

983
OptiX OSN 7500 II/7500/3500/1500


None.
A.5.7 Hub/Spoke (Ethernet LAN Service)

Description
Hub/Spoke (Ethernet LAN Service) is used to separate packets between the logical ports in the
network bridge.
In the same VB VLAN filter or plain bridge:
l
Communication is available between ports configured with Hub.
Communication is available between a port configured with Spoke and a port configured
with Hub.
Communication is unavailable between ports both configured with Spoke.

If Hub/Spoke is set improperly, services may be interrupted or packets may be forwarded to a
wrong user.
Values
Value Range
Default Value
Hub, Spoke
Hub
Set this parameter according to the isolation domain range of the user.
For example, to make communication available between the headquarters and branch but
unavailable between the branches, Hub is set for the headquarters, and Spoke is set for the
branches. In this case, communication is available between the headquarters and any one of the
branches but unavailable between any two of the branches.

None.
A.5.8 Actual MAC Address Table Capacity (Ethernet LAN Service)

Description
Actual MAC Address Table Capacity (Ethernet LAN Service) indicates different meanings
for different Ethernet service processing boards.
Issue 03 (2012-11-30)

984
OptiX OSN 7500 II/7500/3500/1500

For the N4EFS0 and N2EFS4, this parameter indicates the number of MAC addresses that
are dynamically learnt from a VB logical port or VLAN filter. The MAC addresses in the
static MAC address table and forbidden MAC addresses are not included.
For the N1EMS4, N1EGS4 and N3EGS4, this parameter indicates the number of MAC
addresses that are dynamically learnt from a VLAN filter. The MAC addresses in the static
MAC address table and forbidden MAC addresses are not included.
For the N2EMR0 and N2EGR2, this parameter indicates the number of MAC addresses
that are dynamically learnt from a VB logical port. The MAC addresses in the static MAC
address table and forbidden MAC addresses are not included.
For the N1EAS2, this parameter indicates the number of dynamic MAC addresses that are
queried in the VLAN filter.

This parameter is for query only and the system operation is not affected.
Values
For example, for the N1EMS4, N1EGS4 and N3EGS4, if the port dynamically learns five MAC
addresses, the actual capacity of the MAC address is five.
None.

None.
A.5.9 Specified MAC Address Table Capacity (Ethernet LAN

Service)
Description
Specified MAC Address Table Capacity (Ethernet LAN Service) indicates the maximum
number of MAC addresses that are dynamically learnt from the VB logical port or the VLAN
filter. In excess of the maximum number, the source MAC address of the packet that enters the
logical port is not learnt and the packet is discarded.

When the number of addresses reaches the Specified MAC Address Table Capacity value, the
packet that is not listed in the MAC address table is not learnt and forwarded.
Issue 03 (2012-11-30)

985
OptiX OSN 7500 II/7500/3500/1500

Values
Board Name
Value Range
Default Value
Description
N4EFS0, N2EFS4,
N1EFS0A,
N1EMS2, N3EFS4,
N3EGS2, N5EFS0
l No Limit
No Limit
No Limit indicates
that the MAC
address capacity is
16384.
l 0-16384
0-16384 indicates the

allowable size of the
MAC address table,
which specifies
MAC Address
Table Capacity of
the VB logical port or
VLAN filter.
N1EMS4, N1EGS4,
N3EGS4, N4EGS4
l No Limit
No Limit
l 0-129535
No Limit indicates
that the MAC
address capacity is
129535.
0-129535 indicates
the allowable size of
the MAC address
table, which
specifies MAC
Address Table
Capacity of the
VLAN filter.
N2EMR0, N2EGR2
l No Limit
No Limit
l 0-65535
No Limit indicates
that the MAC
address capacity is
65535.
0-65535 indicates the
allowable size of the
MAC address table,
which specifies
MAC Address
Table Capacity of
the VB logical port.
The user can specify this parameter for the VB logical port or VLAN filter as required.

For the N4EFS0, N2EFS4, N1EMS4, N1EGS4, N3EGS4, N2EMR0 and N2EGR2, this capacity
is related to the number of MAC addresses that are dynamically learnt only. The MAC addresses
in the static MAC address table and forbidden MAC addresses are not included.
Issue 03 (2012-11-30)

986
OptiX OSN 7500 II/7500/3500/1500

A.5.10 Bridge Learning Mode (Ethernet LAN Service)

Description
Bridge Learning Mode (Ethernet LAN Service) indicates how the bridge learns the MAC
address. Bridge Learning Mode is classified into the shared VLAN learning and independent
VLAN learning modes. The shared VLAN learning mode indicates learning and forwarding
based on the MAC address. The independent VLAN learning mode indicates learning and
forwarding based on the VLAN and MAC address.

The independent VLAN learning mode realizes the functions of broadcast packet constraint and
virtual workgroup and ensures that the data are transmitted safely on the network.
The shared VLAN learning mode indicates the MAC address that is learnt by this VLAN
interface is shared by all the other VLAN interfaces, which reduces the safety of data packets.
Values
Value Range
Default Value
IVL, SVL
IVL (The bridge type is

compliant with IEEE 802.1q
or IEEE 802.1ad), SVL (The
bridge type is compliant with
IEEE 802.1d)

Value
Description
SVL
Indicates that in the shared VLAN learning mode, the

bridge learns all the data messages based on the MAC
address.
IVL
Indicates that in the independent VLAN learning mode,

data packets of different VLAN interfaces are not
associated.
The user can set the parameter according to the networking requirements.

None.
Issue 03 (2012-11-30)

987
OptiX OSN 7500 II/7500/3500/1500

A.5.11 Self-learning MAC Address (Ethernet LAN Service)

Description
Self-learning MAC Address (Ethernet LAN Service) indicates the starting MAC address for
the batch query in the address table. The starting MAC address can be the first one in the address
table, or the one where the last query ends.

Values
Value Range
Default Value
First Page, Previous Page,

Next Page
First Page

Value
Description
First Page
Indicates physical position 0 in the entire address table. There

are at most 20 MAC addresses on every page.
Previous Page
Indicates querying the page that precedes the page where the
last query ends.
Next Page
Indicates querying the page that follows this page where the last
query ends.
Normally the first page is the one where the first batch query starts, and the one where the second
query starts is the next page.

None.
A.5.12 Tunnel
Description
Tunnel indicates the tunnel ID of this node. a tunnel ID is specified for every new EVPL (MPLS)
or Transit (MPLS) service.
Issue 03 (2012-11-30)

988
OptiX OSN 7500 II/7500/3500/1500

When the port encapsulation format is MartinioE, the Tunnel flag is the outer flag
encapsulated in MPLS format that identifies a service with the VC flag.
When the encapsulation format of the port is Stack VLAN, the Tunnel flag is the outer
flag encapsulated in VMAN format.

Values
Board Name
Value Range
Default Value
N5EFS0, N3EGS2, N3EFS4,

N2EMR0, N2EGR2, N1EFS0A,
N1EMS2
l 0-4095 (Stack VLAN)
N2EFS0, N4EFS0, N2EGS2,

N2EFS4
l 0-4095 (Stack VLAN)
l 16-1023 (MartinioE)
-
l 16-1048575
(MartinioE)
The user can set this parameter within the value range as required. The Tunnel value of different
services at the same node, however, cannot be the same.

None.
A.5.13 VC
Description
VC indicates the VC number of the node. A VC number is specified for every new EVPL (MPLS)
service.
l
When the port encapsulation format is MartinioE, the VC flag is the inner flag of the MPLS
encapsulation format and identifies a service with the tunnel flag.
When the port encapsulation format is Stack VLAN, VC is not required.

Values
Issue 03 (2012-11-30)
Value Range
Default Value
16-1023

989
OptiX OSN 7500 II/7500/3500/1500

You can set this parameter to any value within the value range according to the requirements of
the user. The VC values of different services at the same node, however, cannot be the same.

None.
A.5.14 Operation Type(IEEE 802.1ad Bridge)

Description
The Operation Type parameter specifies the mode that the port on the 802.1ad bridge uses to
process the ingress packet.

Different operation types have different effects. Set this parameter according to the actual
networking condition.
Values
Value Range
Default Value
Add S-VLAN base for Port, Add SVLAN base for Port and C-VLAN,
Mount Port, Mount Port and base for
Port and S-VLAN
Add S-VLAN base for Port
Issue 03 (2012-11-30)
Value
Description
Add S-VLAN base for Port
Indicates that the S-VLAN is added to all the

ingress packets.
Add S-VLAN base for Port and CVLAN
Indicates that the S-VLAN is added to the

packets that carry the specified C-VLAN.
Mount Port
Indicates the port mounting and an arbitrary SVLAN.
Mount Port and base for Port and SVLAN
Indicates the mounting based on port+SVLAN. In this case, the S-VLAN needs to be
specified.

990
OptiX OSN 7500 II/7500/3500/1500

Set this parameter according to the actual requirement of the user.
A.5.15 Bridge Type

Description
The Bridge Type parameter is applicable only to the EGS4, EMS4, and EAS2 boards that
support the 802.1ad bridge. In the case of the OptiX NG-SDH equipment series of a version
earlier than V100R008, you only need to select the bridge mode (pure bridge or virtual bridge)
to configure the VB. The 802.1d bridge supports the pure bridge and virtual bridge. To identify
the pure bridge and virtual bridge defined previously, VBs are currently classified into three
types, namely, 802.1d, 802.1q, and 802.1ad.

Various types of bridges realize different functions and require different configurations. An
incorrect selection of the bridge type fails to realize the expected functions.
Values
Value Range
Default Value
802.1d, 802.1q, 802.1ad
802.1q
Issue 03 (2012-11-30)
Value
Description
802.1d
The 802.1d bridge is actually the pure bridge defined previously.

In contrast with the virtual bridge type supported by the board,
the 802.1d bridge forwards data based on the MAC address.
When the 802.1d bridge is used, the complex VLAN
management is not required and the management that is similar
to the Layer 2 switch is easier. A customer and a 802.1d bridge
set up the one-to-one relationship. The VLAN is managed by the
customer independently, which does not require the cooperation
of the carrier.
802.1q
The 802.1q bridge is actually the virtual bridge defined

previously. The 802.1q bridge forwards data based on VLAN
+MAC. A customer and a VLAN set up the one-to-one
relationship. Services of different VLANs are isolated.

991
OptiX OSN 7500 II/7500/3500/1500

Value
Description
802.1ad
The 802.1ad bridge supports the pure bridge and virtual bridge.
That is, the 802.1ad bridge forwards data based on VLAN+MAC
or the MAC address. The application of the 802.1ad bridge can
realize the service switch between the carrier and its users and
can isolate services of different users. In addition, the 802.1ad
bridge can identify the voice service and data service, which
improves the quality of the voice service.
Set this parameter according to the actual service condition of the user.
A.5.16 SAN Service Type

Description
The SAN Service Type parameter specifies the service type at a board service port. This
parameter decides the service type, port transmission rate, and communication mode.

If the service type is different from that of the interconnected equipment, the service is
unavailable.
Values
Valid Values
Default Value
FC service, FCION service,

ESCON service, DVB-ASI
service, SD-SDI service,
HD-SDI service, Invalid
service
Invalid service
NOTE
For the FCION, ESCON, DVB-ASI SD-SDI, and HD-SDI services,
each service maps a rate. For the FC service, select FC100 or
FC200.
Issue 03 (2012-11-30)
Value
Description
FCION service
Rate: 1.062 Gbit/s
ESCON service
Rate: 200 Mbit/s
DVB-ASI service
Rate: 270 Mbit/s
SD-SDI service
Rate: 270Mbit/s
HD-SDI service
Rate: 1.485Gbit/s

992
OptiX OSN 7500 II/7500/3500/1500

Value
Description
FC service
l FC100 Rate: 1.062 Gbit/s

l FC200 Rate: 2.125 Gbit/s
Select a proper service type as required.

None.
A.5.17 Concatenation Level (SAN)

Description
The Concatenation Level (SAN) parameter specifies the VC level that can be bound with a
VCTRUNK port.

If the specified service rate exceeds the rate of concatenated VCTRUNKs, the service is
unavailable. Otherwise, the service is available, but the bandwidth is wasted. Examples are
provided as follows:
If the service rate is set to VC4-4C, the FICON, FC100 or FC200 service is unavailable.
If the service rate is set to VC4-8C, the FC200 service is unavailable.
Values
Valid Value
Default Value
VC4-4C, VC4-8C, VC4-16C
l
To converge DVB-ASI services or ESCON services or SD-SDI services, select VC4-4C.
To converge FICON services or FC100 services, select VC4-8C.
To converge FC200 services or HD-SDI services, select VC4-16C.

None.
Issue 03 (2012-11-30)

993
OptiX OSN 7500 II/7500/3500/1500

A.5.18 Enabled Flow Control of FC Port

Description
The Enabled Flow Control of FC Port parameter is valid for the FC100 and FC200 services
only. After this parameter is set, the transmission rate is not affected within the distance of 3000
km (for the FC100 service) or 1500 km (for the FC200 service). This parameter specifies whether
the distance expansion function is enabled.

l
If Enabled Flow Control of FC Port is set to Disabled, the service rate in the link is
affected when the FC100 or FC200 service is transmitted over a long distance. For example,
if the CREDIT value is 20 for the storage equipment, and if the storage equipment is more
than 50 km away from the SAN board, the service rate is greatly decreased. When the
distance is between 20 km (for the FC200 service) or 40 km (for the FC100 service), the
buffer of the storage equipment is used up.
If Enabled Flow Control of FC Port is set to Enabled, the service rate in the link is not
affected when the FC100 or FC200 service is transmitted in a long distance.
If the settings of the equipment are inconsistent at the two ends, the flow control function
is disabled, and the service is also unavailable.
Values
Valid Values
Default Value
Enabled, Disabled
Enabled

Value
Description
Enabled
Enables the flow control function.
Disabled
Disables the flow control function.
The Enabled Flow Control of FC Port parameter must be consistent with each other for the
interconnected equipment at the two ends.

None.
Issue 03 (2012-11-30)

994
OptiX OSN 7500 II/7500/3500/1500

A.5.19 Initial Value of CREDIT at the Client Side

Description
The Initial Value of CREDIT at the Client Side parameter specifies the initial credit value for
the boards at the client side. The value 1 maps the transmission distance of 2 km (for the FC100
service) and 1 km (for the FC200 service).

The FC100 service is transmitted in the link and the transmission distance is 10 km at the client
side.
l
If the parameter value is less than 5, the service rate in the link is low.
If the parameter value is not less than 5, the service rate in the link is close to the line speed.
side.
l
If the parameter value is not less than 10, the service rate in the link is close to the line
speed.
NOTE
If the credit value is large, the system is not affected. Generally, set it to the maximum value.
Values
Valid Values
Default Value
0-20
20
The value indicates the buffer size.
1.
The credit values at the client side should be consistent with each other for the
interconnected equipment at the two ends. In this case, the uplink rate is consistent with
the downlink rate.
2.
This parameter is decided by the transmission distance at the client side. For the FC100
service, the value 0.5 maps the transmission distance of 1 km. For the FC200 service, the
value 1 maps the transmission distance of 1 km.
3.
Generally, set it to 20.

None.
Issue 03 (2012-11-30)

995
OptiX OSN 7500 II/7500/3500/1500

A.5.20 Initial Value of CREDIT at the WAN Side

Description
The Initial Value of CREDIT at the WAN Side parameter specifies the initial credit value for
the boards at the WAN side. The value 1 maps the transmission distance of 2 km (for the FC100
service) and 1 km (for the FC200 service).

side.
l
speed.
side.
l
speed.
NOTE
If the credit value is large, the system is not affected. Generally, set it to the maximum value.
Values
Valid Values
Default Value
0-1500
1500
The value indicates the buffer size.
1.
The credit values at the WAN side need to be consistent with each other for the
interconnected equipment at the two ends. In this case, the uplink rate is consistent with
the downlink rate.
2.
This parameter is decided by the transmission distance at the WAN side. For the FC100
service, the value 0.5 maps the transmission distance of 1 km. For the FC200 service, the
value 1 maps the transmission distance of 1 km.
3.
Generally, set it to 1500.

None.
Issue 03 (2012-11-30)

996
OptiX OSN 7500 II/7500/3500/1500

A.6 ETH OAM Associated Parameters (Packet Mode)

This topic describes the parameters that are used for enabling the ETH-OAM function.
A.6.1 CC Test Transmit Period(Ethernet Service OAM

Management)
Description
The source end MEP constructs the CC frames, and then transmits them periodically to the
destination MEP. After the destination MEP receives the CCM messages from the source end,
the CC check function of the source MEP is directly started. Within a certain period (3.5 times
of the transmission period), if the destination MEP does not receive the CC packets from the
source end, an alarm is automatically reported. The CC Test Transmit Period parameter
indicates the transmission period of the unidirectional connectivity check.

After the CC check is started, a portion of the bandwidth on the port is used.
Values
Value Range
Default Value
3.33ms, 10ms, 100ms, 1s, 10s, 1m, 10m
1s
It is recommended that you use three period values, that is, 3.33 ms for protection switching,
100 ms for performance check, and 1s for connectivity check. The configuration should comply
with user requirements. If the fast check is required, set to 3.33 ms. Hence, the fault can be
detected quickly. The bandwidth used, however, descends with the period value.
A.6.2 Maintenance Domain Level(Ethernet Service OAM

Management)
Description
The Maintenance Domain Level parameter indicates the level of the maintenance domain
(MD). The MD level restricts the usage scope of the OAM.

In one MD, the OAM packets at the same MD level can be normally transmitted and received.
The OAM packets at a higher MD level are not processed, but are transparently transmitted. The
OAM packets at a lower MD level are directly discarded.
Issue 03 (2012-11-30)

997
OptiX OSN 7500 II/7500/3500/1500

Values
Value Range
Default Value
0-7
The following table lists descriptions of each value. You can also define the maintenance scope
for an MD level as required.
Value
Description
Operator
Operator
Operator
Service Provider
Service Provider
Customer
Customer
Customer
"0" indicates the lowest MD level and "7" the highest MD level. The parameter level defines
the maintenance scope of the OAM operations.

None.
Related Information
Before setting this parameter, obtain the information about the MD.
A.6.3 CC Status(Ethernet Service OAM Management)

Description
The CC Status parameter indicates whether the CC check function of this MEP is activated.

If the CC is activated, the bandwidth is used. Otherwise, the bandwidth is not used.
Issue 03 (2012-11-30)

998
OptiX OSN 7500 II/7500/3500/1500

Values
Value Range
Default Value
Active, Inactive
Active
If the check is needed, select Active. Otherwise, select Inactive.
A.6.4 Service Name(Ethernet Service OAM Management)

Description
The Service Name parameter indicates the type of the service to be detected by the OAM during
the creation of an MA.

Values
Value Range
Default Value
A character string of not more than 64

characters
None.

None.
A.6.5 Service Type(Ethernet Service OAM Management)

Description
The Service Type parameter indicates the type of the service to be detected by the OAM during
the creation of an MA.

Issue 03 (2012-11-30)

999
OptiX OSN 7500 II/7500/3500/1500

Values
Value Range
Default Value
E-Line, E-LAN, E-AGGR

Value
Description
E-Line
Indicates the Ethernet private line service.
E-LAN
Indicates the Ethernet private network service.
E-AGGR
Indicates the Ethernet aggregation service.
None.

None.
Related Information
None.
A.6.6 Activation Status(Ethernet Service OAM Management)

Description
The Activation Status parameter indicates whether to send the CC packet. The CC packet refers
to service connectivity checking packet.

When the activation status is "Active", the NE where the maintenance association end point
(MEP) is located starts to send the CC packet and the receive end, that is, the NE where the
remote maintenance association end point (RMEP) is located checks whether the CC packet is
received. If the receive end fails to receive the CC packet, the receive end reports corresponding
alarms.
For example, if the receive ends fails to receive the CC packet within 3.5 cycles, the receive end
reports the ETH_CFM_LOC alarm. If the attributes of the received CC packet are inconsistent
with the attributes of the packet in the maintenance association (MA) of the maintenance domain
(MD), the receive end reports the Mismerge alarm.
When the activation status is "Inactive", the NE where the MEP is does not send any CC packet
and the NE where the RMEP is does not check for an alarm.
Issue 03 (2012-11-30)

1000
OptiX OSN 7500 II/7500/3500/1500

Values
Value Range
Default Value
Active, Inactive
Active

Value
Description
Active
Indicates that the NE where the MEP is starts to send the CC

packet and the receive end, that is, the NE where the RMEP
is checks whether the CC packet is received. If the receive end
fails to receive the CC packet, the receive end reports
corresponding alarms.
Inactive
Indicates that the NE where the MEP is does not send any CC
packet and the NE where the RMEP is does not check for an
alarm.
The activation status is "Active" after the MEP is created on the NE and the service connectivity
can be checked. The activation status can also be set to "Inactive".

None.
Related Information
Before setting this parameter, obtain the information about the MD, MA, MEP and RMEP.
A.6.7 Transmitted Packet Count(Ethernet Service OAM

Management)
Description
The Transmitted Packet Count parameter indicates the number of the transmitted loopback
message (LBM).

Issue 03 (2012-11-30)

1001
OptiX OSN 7500 II/7500/3500/1500

Values
Value Range
Default Value
1-255
The time taken ascends with the number of transmitted packets.

None.
Related Information
None.
A.6.8 Transmitted Packet Length(Ethernet Service OAM

Management)
Description
The Transmitted Packet Length parameter indicates the length of the transmitted loopback
message (LBM).

Values
Value Range
Default Value
64-1400
64
The default value is 64. Packets of different lengths may have different connectivity test results.

None.
Related Information
None.
Issue 03 (2012-11-30)

1002
OptiX OSN 7500 II/7500/3500/1500

A.6.9 Transmitted Packet Priority (Ethernet Service OAM

Management)
Description
The Transmitted Packet Priority (Ethernet Service OAM) parameter indicates the VLAN
priority in the Ethernet service OAM protocol packets transmitted by the equipment.

Values
Value Range
Default Value
0-7
Value 0 indicates the lowest priority, and value 7 indicates the highest priority. By default, value
7, the highest priority, is used.

None.
Related Information
None.
A.6.10 Destination Maintenance Point MAC Address(Ethernet

Service OAM Management)
Description
The Destination Maintenance Point MAC Address parameter indicates the MAC address of
the port where the destination maintenance point (MP) is located.

Values
Issue 03 (2012-11-30)
Value Range
Default Value
Any valid destination unicast MAC address

1003
OptiX OSN 7500 II/7500/3500/1500

Indicates the MAC address of the port where the destination MP is located.

None.
Related Information
None.
A.6.11 Response Maintenance Point ID(Ethernet Service OAM

Management)
Description
The Response Maintenance Point ID parameter identifies the response MP according to the
MAC address.

Values
Value Range
Default Value
Indicates the MAC address of the port.
Indicates the MAC address of the port where the response MP is located.

None.
Related Information
None.
A.6.12 Hop Count(Ethernet Service OAM Management)

Description
The hop count, also called time to live (TTL), is carried with the OAM packets. The Hop
Count parameter indicates the connection from the response MP to the source MP. On the trail
from the source MP to the destination MP, the hop count for the packets decreases by one when
Issue 03 (2012-11-30)

1004
OptiX OSN 7500 II/7500/3500/1500

the packets pass through each maintenance intermediate point (MIP). For example, the packets
pass through one MIP and reach the response MP, the returned hop count is 1. The maximum
value of the Hop Count parameter is 64. If the packets pass through 64 MPs and fail to reach
the response MP, the OAM packets are discarded. In this case, value "/" is returned.

Values
Value Range
Default Value
1-64, /
The Hop Count parameter cannot be set. When the loopback test (LT) is complete, a value is
returned. When the OAM packets pass through 64 MPs and fail to reach the response MP, the
"/" value is returned.

None.
Related Information
None.
A.6.13 Test Result(Ethernet Service OAM Management)

Description
The Test Result parameter indicates the trail information about the link connection from the
source maintenance point to the destination maintenance point during the LT test. If the trail
from the source maintenance point to the destination maintenance point cannot be obtained, the
operation failure information is reported. If the trail from the source maintenance point to the
destination maintenance point transits the intermediate equipment or destination equipment, the
operation success information is reported.

Values
Issue 03 (2012-11-30)
Value Range
Default Value
Character string

1005
OptiX OSN 7500 II/7500/3500/1500

None.
A.7 ETH-OAM Associated Parameters (TDM Mode)

This topic describes the parameters for configuring the ETH-OAM function.
A.7.1 MP ID (Ethernet OAM)

Description
The MP ID (Ethernet OAM) specifies the flag that uniquely identifies a maintenance point.
The bytes from higher bits to lower bits are respectively described here. The first byte indicates
the network number. The second byte indicates the number of the node in the local network.
The third and forth bytes indicate the ID of the maintenance point on the network node. The
maintenance point ID must be unique in the entire network.

Values
Valid Values
Default Value
00-00-0001 to FF-FF-FF00
00-00-0001
The maintenance point ID must be unique in the entire network. Moreover, the U2000 can check
whether the maintenance point ID is duplicate.

None.
A.7.2 Maintenance Point Type (Ethernet OAM)

Description
The Maintenance Point Type (Ethernet OAM) specifies the maintenance point type defined
in IEEE 802.1ag. MEP stands for Maintenance association End Point, and MIP stands for
Maintenance association Intermediate Point.

Issue 03 (2012-11-30)

1006
OptiX OSN 7500 II/7500/3500/1500

Values
Valid Values
Default Value
MEP, MIP
MEP
None.

None.
A.7.3 CC Status (Ethernet OAM)

Description
The CC Status (Ethernet OAM) parameter specifies whether to activate the connectivity check
(CC) function at a maintenance point.

After the CC function is activated, the maintenance point starts the CC. If the check is initially
successful, the EX_ETHOAM_CC_LOS alarm is reported if a CC failure occurs later.
Values
Valid Values
Default Value
Activate, Inactivate
Inactivate
To start the connectivity check, activate the CC function at a maintenance endpoint.
To stop the connectivity check, deactivate the CC function.

The CC function can be activated at a maintenance endpoint only.
A.7.4 CC Activate Flag

Description
The CC Activate Flag parameter specifies whether the CC function is enabled. This function
helps users check the link connectivity.
Issue 03 (2012-11-30)

1007
OptiX OSN 7500 II/7500/3500/1500


When the CC function is enabled, a CC cell is inserted every second if no user cells are
transmitted from the CC source end. In this case, the CC_LOC alarm is reported if no user cells
or CC cells are received at the CC sink end within a period ranging from 3s to 4s.
Values
Value Range
Default Value
Deactivate, Source activate,

Sink activate, Source + sink
activate
Deactivate

Value
Description
Deactivate
Indicates that the CC function is disabled.
Source activate
Indicates that the local end with the CC function enabled

functions as the source end, that is, the end that initiates the
CC test by inserting the CC cell.
Sink activate
Indicates that the local end with the CC function enabled

functions as the sink end, that is, the end that determines the
normal connectivity by receiving the CC cell.
Source + sink activate
Indicates that the CC function is enabled at the source end

and at the sink end. That is, the local end inserts the CC cell
to initiate the CC check for the opposite end and receives the
CC cell and user cell inserted by the opposite end. In this case,
the local end functions as the sink end and source end.
A.7.5 Test Result (LB and LT Test)

Description
The Test Result (LB and LT Test) parameter specifies the result derived from the LB or LT
test each time.

Issue 03 (2012-11-30)

1008
OptiX OSN 7500 II/7500/3500/1500

Values
Valid Values
Default Value
Succeeded, Failed
None.

None.
A.7.6 Responding MP Type (Ethernet LT Test)

Description
The Responding MP Type (Ethernet LT Test) parameter specifies the type of the responding
maintenance point in each LT test.

Values
Valid Values
Default Value
MEP, MIP, Unknown
Unknown
None.

The responding maintenance point must return the type, which is specified when this
maintenance point is created.
A.7.7 Hop Count (Ethernet LT Test)

Description
The Hop Count (Ethernet LT Test) parameter specifies the number of hops from the
maintenance source endpoint to a maintenance intermediate point, namely, the number of
responding intermediate points from the maintenance source point to a certain responding point.
Issue 03 (2012-11-30)

1009
OptiX OSN 7500 II/7500/3500/1500

As shown in Figure A-4, MEP1 and MEP2 are the maintenance endpoints. MIP1, MIP2, MIP3
and MIP4 are the maintenance intermediate points. In this case, the number of hops from MEP1
to MEP2 is 5, and that from MEP1 to MIP3 is 3.
Figure A-4 An example of number of hops

Values
If the value of Hop Count is 2, there are two hops.
None.

None.
A.7.8 Send Mode (Ping Test)

Description
The Send Mode parameter specifies the transmission mode of the ping packet.

Values
Value Range
Default Value
Burst Mode, Continue Mode
Burst Mode

Issue 03 (2012-11-30)

1010
OptiX OSN 7500 II/7500/3500/1500

Value
Description
Burst Mode
Indicates that a certain number of ping packets are

transmitted at one time.
Continue Mode
Indicates that ping packets are continuously transmitted.
To check whether the link communication is available, set this parameter to Burst Mode to
transmit several ping packets at one time. To locate the fault on the link, set this parameter to
Continue Mode to continuously transmit ping packets.
A.7.9 Packet Length (Ping Test)

Description
The Packet Length (Ping Test) parameter specifies the maximum length of the Ping packets if
the Ping operation is initiated at a maintenance endpoint.

Values
Valid Values
Default Value
Unit
64
Byte
Set this parameter according to the expected frame length.

None.
A.7.10 Timeout (Ping Test)

Description
The Timeout (Ping Test) parameter specifies the waiting period in which no response message
is received from the opposite end after a maintenance point initiates the Ping test. In this case,
the maintenance point regards that the Ping test fails. This waiting period is called the Ping
timeout time.
Issue 03 (2012-11-30)

1011
OptiX OSN 7500 II/7500/3500/1500


After initiating the Ping test, the maintenance point returns a Ping timeout message if it fails to
receive the response message from the opposite end when the Ping timeout time is reached.
Values
Valid Values
Default Value
Unit
Second
Set this parameter to a lower value if the requirement is high for the response time.
Set this parameter to a higher value if the requirement is low for the response time.

The values of Timeout and Ping Attempts decides the longest duration required to perform the
Ping test.
A.7.11 Time To Live

Description
The Time To Live parameter specifies the time to live. Currently, the Ping or performance test
is carried out in the equipment that is directly connected. For this reason, this parameter is always
set to 128.

Values
Valid Values
Default Value
Unit
Second
None.

None.
Issue 03 (2012-11-30)

1012
OptiX OSN 7500 II/7500/3500/1500

A.7.12 Delay
Description
The Delay parameter specifies the hold-off period from the time when packets are transmitted
to the time when packets are received in each OAM Ping or performance test.

Values
Valid Values
Default Value
Unit
0-Timeout time
ms
None.

The delay involves the minimum delay and the maximum delay. For details, refer to A.7.14
Max. Delay and A.7.15 Min. Delay.
A.7.13 Average Delay

Description
The Average Delay parameter specifies the average delay in each OAM Ping or performance
test.

This parameter shows the overall responding speed of the opposite end.
Values
In each Ping test, set the number of Ping attempts to 4. The actual test results are as follows:
For the first Ping attempt, the delay is 100 ms.
For the second Ping attempt, the delay is 200 ms.
For the third Ping attempt, the delay is 300 ms.
The forth Ping attempt fails because of timeout.
In this case, the average delay is as follows:
Average delay = (100 + 200 + 300) / 3 = 200 ms
Issue 03 (2012-11-30)

1013
OptiX OSN 7500 II/7500/3500/1500

None.

For the description of Delay, refer to A.7.12 Delay.
A.7.14 Max. Delay

Description
The Max. Delay parameter specifies the maximum delay in each Ping or performance test.

Values
Valid Values
Default Value
Unit
0-Timeout time
ms
None.

None.
A.7.15 Min. Delay

Description
The Min. Delay parameter specifies the minimum delay in each Ping or performance test.

Values
Issue 03 (2012-11-30)
Valid Values
Default Value
Unit
0-Timeout time
ms

1014
OptiX OSN 7500 II/7500/3500/1500

None.

None.
A.7.16 Detect Attempts

Description
The Detect Attempts parameter specifies the detection attempts for performing performance
detection defined in IEEE 802.1ag.

If the value of Detection Count is larger, the test result is more accurate in each performance
detection test. In this case, more system resources are used, and longer time is consumed.
Values
Valid Values
Default Value
Unit
Attempt
Set this parameter to a proper value according to the test accuracy and the system resource used
in the test.

None.
A.7.17 Send Direction (Ethernet Test)

Description
Send Direction (Ethernet Test) indicates the transmit direction of the test packet.

Values
Issue 03 (2012-11-30)
Value Range
Default Value
SDH Direction, /

1015
OptiX OSN 7500 II/7500/3500/1500


Value
Description
SDH Direction, /
Indicates that the test packet is transmitted from the

VC trunk port to the SDH side.
Indicates that the parameter is invalid.

This parameter is valid and displayed as SDH Direction only when Send Mode is set to Burst
Mode or Continue Mode. This parameter is displayed as / when Send Mode is set to
Disabled.
A.7.18 Error Frame Monitor Window(ms)

Description
The Error Frame Monitor Window(ms) parameter specifies the period during which the
number of error frames received at the port exceeds the specified upper threshold. In this case,
a link event alarm is reported.

After you set the Error Frame Monitor Threshold and Error Frame Monitor Window
(ms) parameters, a link event alarm is reported if the actual number of error frames in the link
exceeds the specified threshold.
Values
Valid Values
Default Value
Unit
1000
ms
Set this parameter according to the actual port rate and the monitoring period.
Make sure that the value of Error Frame Monitor Threshold is not greater than the maximum
number of frames received at the port within the time specified in Error Frame Monitor
Window (ms).

To set Error Frame Monitor Window (ms), set Error Frame Monitor Threshold. Moreover,
set Port Rate. For details, refer to the description of the Error Frame Period Window
(Frame) parameter.
Issue 03 (2012-11-30)

1016
OptiX OSN 7500 II/7500/3500/1500

A.7.19 Error Frame Monitor Threshold (Entries)

Description
The Error Frame Monitor Threshold (Entries) parameter specifies the upper threshold of
error frames received at the port. In this case, a link event alarm is reported.

After you set the Error Frame Monitor Threshold and Error Frame Monitor Window
(ms) parameters, a link event alarm is reported if the actual number of error frames in the link
Values
Valid Values
Default Value
Unit
1-4294967295 (in step length of 1)
Frame
If higher link performance is required, set the threshold to a lower value. Otherwise, set the
threshold to a higher value.
Make sure that the value of Error Frame Monitor Threshold is not greater than the maximum
number of frames received at the port within the time specified in Error Frame Monitor
Window (ms).

To set Error Frame Monitor Threshold, set Error Frame Monitor Window (ms). Moreover,
set Port Rate. For details, refer to the description of the Error Frame Period Window (Frame)
parameter.
A.7.20 Error Frame Period Window (Frame)

Description
The Error Frame Period Window (Frame) parameter specifies the received N frames in which
the number of error frames reach the specified upper threshold. In this case, a link event alarm
is reported.

After you set the Error Frame Period Window (Frame) and Error Frame Period Threshold
(Frame) parameters, a link event alarm is reported if the number of error frames received within
a certain period reaches the specified upper threshold.
Issue 03 (2012-11-30)

1017
OptiX OSN 7500 II/7500/3500/1500

Values
Valid Values
Default Value
Unit
Maxpps/10-Maxpps*60, in step length

of 1
Maxpps
Frame
Set this parameter according to the actual data frame transmission rate and the frames. If the
data transmission rate is high, set this parameter to a higher value. Otherwise, set this parameter
to a lower value.

The value range depends on the port rate.
Related Information
Maxpps: indicates the maximum number of frames per second.
Specifically,
l
If the port rate is 10 Mbit/s, the Maxpps value is 14880.
If the port rate is 10 Gbit/s, the Maxpps value is 14880000.
According to the rule of Maxpps/10 < Error Frame Period Window < Maxpps*60, you know
the value range of the Error Frame Period Window (Frame) parameter for a certain port rate.
A.7.21 Error Frame Monitor Threshold (Frame)

Description
The Error Frame Monitor Threshold (Frame) parameter specifies the received N frames in
which the number of error frames reach the specified upper threshold. In this case, a link event
alarm is reported.

After you set the Error Frame Period Window (Frame) and Error Frame Period Threshold
(Frame) parameters, a link event alarm is reported if the number of error frames received within
a certain period reaches the specified upper threshold.
Values
Issue 03 (2012-11-30)
Valid Values
Default Value
Unit
Frame

1018
OptiX OSN 7500 II/7500/3500/1500

None.

None.
A.7.22 Error Frame Second Window(s)

Description
The Error Frame Second Window(s) parameter specifies the error frame second when any
error frames are received at the port within one second. If the error frame seconds within a certain
time period reach the specified upper threshold, link event alarms are reported. The time period
in which error frames are received is called the error frame second window.

After you set the Error Frame Second Window (s) and Error Frame Second Threshold (s)
parameters, link event alarms are reported if the actual error frame seconds in the link reach the
specified upper threshold.
Values
Valid Values
Default Value
Unit
60
Second
Set this parameter according to the monitoring time period.
Make sure that the value of Error Frame Second Window (s) is not less than that of Error
Frame Second Threshold (s).

Set the Error Frame Second Window (s) parameter together with the Error Frame Second
Threshold (s) parameter.
A.7.23 Error Frame Second Threshold(s)

Description
The Error Frame Second Threshold(s) parameter specifies the second during which error
frames are received at the port. If the error frame seconds within a certain time period reach the
specified upper threshold, a link event alarm is reported. The upper threshold is called the error
frame second threshold.
Issue 03 (2012-11-30)

1019
OptiX OSN 7500 II/7500/3500/1500


After you set the Error Frame Second Threshold (s) parameter, link event alarms are reported
if the actual error frame seconds in the link reach the specified upper threshold.
Values
Valid Values
Default Value
Unit
Second
None.

None.
A.7.24 Enable OAM Protocol

Description
The Enable OAM Protocol parameter specified whether the end-to-end OAM protocol
(namely, the IEEE 802.3ah protocol) is enabled at a port.

Values
Valid Values
Default Value
Enabled, Disabled
Disabled
None.

None.
Issue 03 (2012-11-30)

1020
OptiX OSN 7500 II/7500/3500/1500

A.7.25 OAM Working Mode

Description
The OAM Working Mode parameter specifies a negotiation mode defined in IEEE 802.3ah. It
involves two modes: Passive and Active.

Before IEEE 802.3ah is enabled, the local and opposite ends fail to negotiate with each other if
OMA Working Mode is set to Passive.
Values
Valid Values
Default Value
Active, Passive
Active
Value
Description
Active
Indicates that a port actively transmits the IEEE 802.3 ah

packets.
Passive
Indicates a port transmits the IEEE 802.3 ah packets to

the opposite end only after receiving IEEE 802.3 ah
packets from the opposite end.
None.

None.
A.7.26 Remote Alarm Support for Link Event

Description
The Remote Alarm Support for Link Event parameter specifies whether to report the detected
link events (for example, Error Frame Period Threshold, Error Frame Monitor
Threshold, and Error Frame Second Threshold) to the opposite end.

After the Remote Alarm Support for Link Event parameter is set to Enabled, link event alarms
are displayed in the opposite equipment if any link events occur.
Issue 03 (2012-11-30)

1021
OptiX OSN 7500 II/7500/3500/1500

Values
Valid Values
Default Value
Enabled, Disabled
Enabled
None.

None.
A.7.27 Unidirectional Operation

Description
The Unidirectional Operation parameter specifies the hardware capability. If a port fails at the
receive end, but can transmit data frames at the transmit end, it has the capability of performing
unidirectional operations. Otherwise, it does not have the capability of performing unidirectional
operations.
The unidirectional operation function specified in IEEE 802.3ah refers to whether the hardware
performs unidirectional operations if it has the capability of performing unidirectional
operations.
If the hardware does not have the capability of performing unidirectional operations, the
unidirectional operation function specified in IEEE 802.3ah is unavailable.

After the Unidirectional Operation parameter is set to Enabled, IEEE 802.3ah packets are still
transmitted to the opposite end if the receive end is faulty.
Values
Valid Values
Default Value
Enabled, Disabled
Disabled
If the hardware has the capability of performing unidirectional operations and supports
unidirectional software operations, generally, set Unidirectional Operation to Enabled.

This parameter depends on whether the port hardware has the capability of performing
unidirectional operations.
Issue 03 (2012-11-30)

1022
OptiX OSN 7500 II/7500/3500/1500

A.7.28 Loopback Status (OAM Parameter)

Description
The Loopback Status (OAM Parameter) parameter specifies whether a port on the board is
in the loopback state. If yes, the port is in the Initiate Loopback at Local or Respond Loopback
of Remote state.

Values
Valid Values
Default Value
Initiate Loopback at Local, Respond

Loopback of Remote, Non-Loopback
Non-Loopback

Value
Description
Non-Loopback
Indicates that the port is not in the loopback state defined

in IEEE 802.3ah.
Initiate Loopback at Local
Indicates that the local end can transmit the loopback

packets to the remote end.
Respond Loopback of Remote
Indicates that the local end can respond to the loopback

packets from the remote end.
None.

None.
A.8 PW Associated Parameters

This topic describes the parameters for configuring PW services.
Issue 03 (2012-11-30)

1023
OptiX OSN 7500 II/7500/3500/1500

A.8.1 Control Word

Description
The Control Word parameter specifies the PW control word usage policy.
The control word is the 4-byte encapsulation packet header. The control word is used to identify
the packet sequence or function as stuffing bits.

Values
Value Range
Default Value
No Use, Used First

Value
Description
No use
Indicates that the control word is not used.
Used First
Indicates that the control word is

recommended.
None.

Related Information
Figure A-5 CW structure of CESoPSN
Issue 03 (2012-11-30)

1024
OptiX OSN 7500 II/7500/3500/1500

Figure A-6 CW structure of SAToP
Compared with the CESoPSN, the M bit is changed into the RSV bit and the RSV bit is set to
the value 0 in the SAToP.
A.8.2 Control Channel Type

Description
The Control Channel Type parameter specifies the type of channels for transmitting VCCV
packets.
VCCV packets are exchanged between PEs to verify connectivity of PWs.

Values
Value Range
Default Value
None, CW
CW

Value
Description
None
Indicates that the control word is not used to

indicate the VCCV control channel information.
CW
Indicates that the control word is used to indicate

the VCCV control channel information.
None.

Issue 03 (2012-11-30)

1025
OptiX OSN 7500 II/7500/3500/1500

A.8.3 VCCV Verification Mode

Description
The VCCV Verification Mode parameter specifies the verification mode of VCCV packets.

Values
Value Range
Default Value
None, Ping
Ping

Value
Description
None
Indicates that the VCCV function is

disabled.
Ping
Indicates that the VCCV function is

performed in Ping mode.
None.

A.8.4 Request VLAN

Description
The Request VLAN parameter specifies the ETH request VLAN.
When the PW is in Ethernet tagged mode, the PW adds the request VLAN tag to the packets
that do not carry any VLAN tag from the opposite end.
In the case of static PW, the local equipment adds the VLAN tag to the packets when before PW
encapsulation. In the case of the dynamic PW, the opposite equipment adds the VLAN tag to
the packets before PW encapsulation if the local equipment cannot add the VLAN tag.
Issue 03 (2012-11-30)

1026
OptiX OSN 7500 II/7500/3500/1500


Values
Value Range
Default Value
1-4095, Non-specified
Non-specified
When the Request VLAN parameter is set to Non-specified, the packets with tags are transmitted
transparently, and the packets without tags are added with 0 VLAN tags.

You need to set the PW Type parameter to Ethernet Tagged Mode.
A.8.5 Overall Operating Status

Description
The Overall Operating Status parameter specifies the running status of a PW.

Values
Value Range
Default Value
Up, Down
Up
Issue 03 (2012-11-30)
Value
Description
Up
Indicates that the Local Working Status and Remote Working

Status are Up.
Down
Indicates that the Local Working Status or Remote Working

Status is Down.

1027
OptiX OSN 7500 II/7500/3500/1500

Dynamic supports Down and Static supports Up.

None.
A.8.6 Associate AC State

Description
The Associate AC State parameter specifies whether to detect the working status of a pseudo
wire (PW) user-network interface (UNI) port (namely, checking whether a fault occurs on a
service PW).

If this parameter is set to Enabled, the equipment can detect the working status of a PW UNI
port. If a fault on a service PW is detected, the opposite NE reports the MPLS_PW_FDI alarm.
Values
Value Range
Default Value
Enabled, Disabled
Disabled

Value
Description
Enabled
Indicates that the equipment can detect the working status of

a PW UNI port. If a fault on a service PW is detected, the
opposite NE reports the MPLS_PW_FDI alarm.
Disabled
Indicates that the equipment does not detect the working

status of a PW UNI port.
When checking whether a fault occurs on a service PW, set this parameter to Enabled.

This parameter is available only when the protection type is set to PW APS.
Related Information
None.
Issue 03 (2012-11-30)

1028
OptiX OSN 7500 II/7500/3500/1500

A.8.7 Max.Concatenated Cell Count

Description
The Max.Concatenated Cell Count parameter specifies the maximum number of concatenated
asynchronous transfer mode (ATM) cells.

Values
Value Range
Default Value
1-31
10
If Max.Concatenated Cell Count is set to 1, the concatenation function is disabled.

Before changing the settings of PW-related parameters, ensure that the PW is not bound with
any services. After changing the settings of PW-related parameters, bind the PW with services
before checking whether this parameter is successfully set.
A.9 PW APS Protection Associated Parameters (Packet

Mode)
This topic describes the parameters for configuring PW APS protection.
A.9.1 Protection Mode

Description
The Protection Mode parameter specifies the protection type of a PW APS protection group.

Values
Issue 03 (2012-11-30)
Value Range
Default Value
1+1, 1:1
1+1

1029
OptiX OSN 7500 II/7500/3500/1500


Value
Description
1+1
The service is dually transmitted to the working and protection

channels at the transmit end and selectively received at the receive
end.
1:1
The service is transmitted to the working or protection channel and

is received from the working or protection channel based on the
status of the protection group.
When you create a protection group in 1:1 protection mode, the protection channel cannot be
configured with extra services. For this reason, the actual applications of 1+1 and 1:1 protection
groups are the same, except for the configuration.

None.
A.9.2 Protection Mode

Description
The Protection Mode parameter specifies a protection scheme of services transmitted on pseudo
wires (PWs) based on the service network.

None.
Values
Value Range
Default Value
PW APS, Slave Protection

Pair, Unprotected
No Protection
Issue 03 (2012-11-30)
Value
Description
PW APS
Indicates a network protection mechanism. If the working PW

is faulty, services are automatically switched from the
working PW to the protection PW.
1030
OptiX OSN 7500 II/7500/3500/1500

Value
Description
Slave Protection Pair
Adds a slave PW automatic protection switching (APS)

protection pair to the existing PW APS protection group for
increase of operation, administration and maintenance
(OAM) resource utilization if the PW that has the same source
and sink needs to be configured with protection.
Unprotected
Indicates that no protection is available for services.
Set this parameter according to the service network. For example:
l
For an NE, set this parameter to PW APS.
If the working and protection PWs that transmit the existing services on an NE have the
same source and sink, set this parameter to Slave Protection Pair.
If services do not need to be protected, set this parameter to No Protection.

None.
Related Information
None.
A.9.3 Switchover Status

Description
The Switchover Status parameter specifies the current status of a protection group. If protection
switching occurs, this parameter also shows the switching causes.

Issue 03 (2012-11-30)

1031
OptiX OSN 7500 II/7500/3500/1500

Values
Value Range
Default Value
Working in working tunnel, Working in protection tunnel,

The current status is forcibly locked, Forcibly switching
status and working in the protection tunnel, Invalid
working tunnel\(because the OAM generates an SF
alarm), Invalid protection tunnel\(because the OAM
generates an SF alarm), Invalid working tunnel\(because
the OAM generates an SD alarm), Invalid protection
tunnel\(because the OAM generates an SD alarm), This
status is displayed while manually switching to the
working tunnel, This status is displayed while manually
switching to the protection channel, In restoration mode,
the working tunnel does not work and switches to the
protection tunnel. Then, the working tunnel works and
services automatically switch to the working tunnel.
Before WTR reaches, this status remains, The switching
is not required, This status is nearly displayed while
practising switching, This status is displayed while
practising switching, This status is remotely displayed
while practising switching.
Issue 03 (2012-11-30)
Value
Description
Working in working
tunnel
No switching request is received. Services are transmitted on the

working tunnel, and the protection tunnel is in standby state.
Working in protection
tunnel
No switching request is received. Services are transmitted on the

protection tunnel, and the working tunnel is in standby state.
The current status is

forcibly locked
Services are transmitted on the working tunnel all the time, and the
protection tunnel is in standby state.
Forcibly switching
status and working in
the protection tunnel
Services are forcibly switched from the working tunnel to the

protection tunnel. The working tunnel remains in standby state
regardless of whether the protection tunnel is available or not.
Invalid working tunnel\

(because the OAM
generates an SF alarm)
The OAM function detects an SF alarm on the working tunnel,

indicating that the working tunnel fails. Services are transmitted
on the protection tunnel, and the working tunnel is in standby state.
Invalid protection
tunnel\(because the
OAM generates an SF
alarm)
The OAM function detects an SF alarm on the protection tunnel,

indicating that the protection tunnel fails. Services are transmitted
on the working tunnel, and the protection tunnel is in standby state.
Invalid working tunnel\

(because the OAM
generates an SD alarm)
The OAM function detects an SD alarm on the working tunnel,

indicating that signal degrade occurs. Services are transmitted on
the working tunnel, and the protection tunnel is in standby state.

1032
OptiX OSN 7500 II/7500/3500/1500

Issue 03 (2012-11-30)
Value
Description
Invalid protection
tunnel\(because the
OAM generates an SD
alarm)
The OAM function detects an SD alarm on the protection tunnel,

indicating that signal degrade occurs. Services are transmitted on
the protection tunnel, and the working tunnel is in standby state.
This status is displayed

while manually
switching to the
working tunnel
Services are manually switched from the protection tunnel to the

working tunnel.

while manually
switching to the
protection channel
Services are manually switched from the working tunnel to the

protection tunnel.
In restoration mode, the

working tunnel does not
work and switches to
the protection tunnel.
Then, the working
tunnel works and
services automatically
switch to the working
tunnel. Before WTR
reaches, this status
remains. The switching
is not required.
If APS protection is in revertive mode, before being switched from

the protection tunnel to the working tunnel, services are in waiting
status within the WTR time after the fault on the working tunnel is
rectified. The services are currently transmitted on the protection
tunnel, and the working tunnel is in standby state.
The switching is not

required
If APS protection is in non-revertive mode, services are not

switched from the protection tunnel to the working tunnel after the
fault on the working tunnel is rectified. The services are currently
transmitted on the protection tunnel, and the working tunnel is in
standby state.
This status is nearly

displayed while
practising switching.
The system simulates the condition for triggering a switching

action, but does not issue a command to trigger a real switching
action. Practicing switching tests APS protection performance of
MPLS PWs without interrupting services. The services are
currently transmitted on the working tunnel, and the protection
tunnel is in standby state.

while practising
switching.
The system simulates the condition for triggering a switching

action, but does not issue a command to trigger a real switching
action. Practicing switching tests APS protection performance of
MPLS PWs without interrupting services. The services are
currently transmitted on the protection tunnel, and the working
This status is remotely

displayed while
A reverse request for protection switching is received. Services are

currently transmitted on the working tunnel, and the protection

1033
OptiX OSN 7500 II/7500/3500/1500

Value
Description
This status is remotely

displayed while
A reverse request for protection switching is received. Services are

currently transmitted on the protection tunnel, and the working
Protection switching is triggered when any of the following conditions is met: SF, external
switching commands, and WTR expiry.

None.
A.9.4 Protocol Status

Description
The Protocol Status parameter specifies whether the APS protocol of the current protection
group is enabled.

Values
Value Range
Default Value
Disabled, Enabled
Disabled

Value
Description
Disabled
Indicates that the APS protocol is disabled.
Enabled
Indicates that the APS protocol is enabled.
If the APS protocol of the local NE is Enabled before the APS protocol of the opposite NE is
Enabled, an exception may occur when the opposite NE receives the services. It is recommended
that the APS protocol be enabled after the MPLS APS protection group is configured for both
ends.
When you configure the MPLS APS protection, the default protocol status is Disabled.
Issue 03 (2012-11-30)

1034
OptiX OSN 7500 II/7500/3500/1500


None.
A.9.5 PW Type
Description
The PW Type parameter is used for identifying the type of a service transmitted over a PW. A
PW can transmit multiple types of services.

Values
Value Range
Default Value
Ethernet, Ethernet Tag Mode, SATop,

CESoPSN
Ethernet
Issue 03 (2012-11-30)
Value
Description
Ethernet
This item is used when an Ethernet service is created. No

S_VLAN tag is added to the service packets.
Ethernet Tag
Mode
This item is used when an Ethernet service is created. S_VLAN

tags are added to the service packets.
SATop
This item is used when a CES service is created. It stands for

Structure-Agnostic TDM over Packet. In SAToP mode, the
equipment does not sense any format in the TDM signals.
Instead, it regards TDM signals as bit flows at a constant rate,
and therefore the entire bandwidth of TDM signals is emulated.
The overheads and payloads in TDM signals are transparently
transmitted.
CESoPSN
This item is used when a CES service is created. It stands for

Structure-aware TDM Circuit Emulation Service over Packet
Switched Network. In CESoPSN mode, the equipment senses
the frame structures, frame alignment modes, and timeslots in
the TDM circuits. The equipment processes the overheads in and
extracts the payloads from the TDM frames. Then, the equipment
loads timeslots to these payloads in a specific sequence. As a
result, the services in each timeslot are fixed and visible in
packets.

1035
OptiX OSN 7500 II/7500/3500/1500

When creating a PW, select the PW type based on the type of the service bound with the PW.

None.
A.10 HQoS Associated Parameters

This topic describes the parameters that are used for enabling the HQoS function.
A.10.1 Traffic Classification Rule(Policy Management)

Description
The Traffic Classification Rule parameter indicates the rules for classifying service packets.
The necessary parameters should be set for Traffic Classification Rule, that is, Match Type
(required), Logical Relation Between Matched Rules, Match Value (required), and
Wilcard (optional).

Values
Set the traffic classification rule in the following formats:
[Match Type : Match Value : Wilcard]
And Logical Relation Between Matched Rules (the matched packets should meet all the traffic
classification rules)
[Match Type : Match Value : Wilcard] & [Match Type : Match Value : Wilcard] &...& [Match
Type : Match Value : Wilcard]
Or Logical Relation Between Matched Rules: (the matched packets should meet one of the
traffic classification rule)
[Match Type : Match Value : Wilcard] | [Match Type : Match Value : Wilcard] |...| [Match Type :
Match Value : Wilcard]
The traffic classification rules are applicable only to the port policy or V-UNI ingress policy.
The character string of the match rule (match type, match value, and wilcard included) can
contain a maximum of 128 bytes.

None.
Issue 03 (2012-11-30)

1036
OptiX OSN 7500 II/7500/3500/1500

Related Information
Currently, the equipment cannot identify the IPv6 packets.
For details on how to set this parameter, see the description of the Match Type, Match
Value, Wilcard, and Logical Relation Between Matched Rules parameters.
A.10.2 Match Type(Policy Management)

Description
Each data packet has many feature values such as the IP address, MAC address, and port number.
These feature values can be considered as match types among the traffic classification rules.

Values
Value Range
Default Value
Source IP, Destination IP, Source MAC

Address, Destination MAC Address,
Protocol Type, Source Port, Destination Port,
ICMP Packet Type, DSCP Value, IPPrecedence Value, CVlan ID, CVlan priority,
SVlan ID, SVlan priority, DEI

Value
Description
Source IP
The source IP address is matched.

The traffic classification rule that the source IP address matches is in the
format of [Source IP : Source IP Value : Wilcard].
For example, [Source IP : 192.168.1.1 : 0.0.0.255].
Destination IP
The destination IP address is matched.

The traffic classification rule that the destination IP address matches is
in the format of [Destination IP : Destination IP Value : Wilcard].
For example, [Destination IP : 192.168.1.2 : 0.0.0.0].
Source MAC
Address
The source MAC address is matched.

The traffic classification rule that the source MAC address matches is
in the format of [Source MAC Address : Source MAC Address Value :
Wilcard].
For example, [Source MAC Address : 00-e0-fc-54-aa-59 :
00-00-00-00-00-00].
Issue 03 (2012-11-30)

1037
OptiX OSN 7500 II/7500/3500/1500

Value
Description
Destination MAC
Address
The destination MAC address is matched.
The traffic classification rule that the destination MAC address matches
is in the format of [Destination MAC Address : Destination MAC
Address Value : Wilcard].
For example, [Destination MAC Address : 00-e0-fc-54-ab-59 :
00-00-00-00-00-00].
The protocol type is matched.
Protocol Type
The traffic classification rule that the protocol type matches is in the
format of [Protocol Type : Protocol Type Value].
For example, [Protocol Type : icmp].
Source Port
The source port is matched (available when the protocol type is TCP and
UDP).
The traffic classification rule that the source port matches is in the format
of [Source Port : Source Port Value : Wilcard].
For example, [Source Port : 23 : 23].
Destination Port
The destination port is matched (available when the protocol type is TCP
and UDP).
The traffic classification rule that the destination port matches is in the
format of [Destination Port : Destination Port Value : Wilcard].
For example, [Destination Port : 80 : 80].
ICMP Packet
Type
The ICMP packet type is matched (available when the protocol type is
ICMP).
The traffic classification type that the ICMP packet type matches is in
the format of [ICMP Packet Type : ICMP Packet Type Value].
For example, [ICMP Packet Type : echo].
DSCP Value
The DSCP value is matched.

The traffic classification rule that the DSCP value matches is in the
format of [DSCP Value : Value of DSCP : Wilcard].
For example, [DSCP Value : 7 : 7].
IP-Precedence
Value
The IP-Precedence Value is matched.

The traffic classification rule that the IP-precedence value matches is in
the format of [IP-Precedence Value : Value of IP-Precedence : Wilcard].
For example, [IP-Precedence Value : 6 : 6].
CVlan ID
The CVlan ID is matched.

The traffic classification rule that the CVlan ID matches is in the format
of [CVlan ID : CVlan ID Value : Wilcard].
For example, [CVlan ID : 100 : 120].
Issue 03 (2012-11-30)

1038
OptiX OSN 7500 II/7500/3500/1500

Value
Description
CVlan priority
The CVlan priority is matched.
The traffic classification rule that the CVlan priority matches is in the
format of [CVlan priority : CVlan priority Value : Wilcard].
For example, [CVlan priority : 4 : 6].
SVlan ID
The SVlan ID is matched.

The traffic classification rule that the SVlan ID matches is in the format
of [SVlan ID : SVlan ID Value : Wilcard].
For example, [SVlan ID : 100 : 120].
SVlan priority
The SVlan priority is matched.

The traffic classification rule that the SVlan priority matches is in the
format of [SVlan priority : SVlan priority Value : Wilcard].
For example, [SVlan priority : 5 : 6].
DEI
The DEI is matched.

The traffic classification rule that the DEI matches is in the format of
[DEI : DEI Value].
For example, [DEI : 1].
To process different service packets accordingly (make ACL for packets, apply different
scheduling priorities or discard polices), perform traffic classification for the packets according
to the varied feature values of packets. The feature value that can distinguish the packets
according to requirements is adopted to classify the packets.
For example, user A and user B access to a port. The network should provide services of different
QoS for the two users. Hence, the packets of user A and user B should be distinguished at the
port.
The analysis shows the following:
In the case of the service packets of user A, the prefix of the source IP address is 192.168.1.0
and the subnet mask is 255.255.255.0.
In the case of the service packets of user B, the prefix of the source IP address is 192.168.2.0
and the subnet mask is 255.255.255.0.
The packets of user A can be distinguished from the packets of user B according to the source
IP address. Hence, two traffic classification rules should be set at the port.
[Source IP : 192.168.1.0 : 0.0.0.255]
[Source IP : 192.168.2.0 : 0.0.0.255]

None.
Issue 03 (2012-11-30)

1039
OptiX OSN 7500 II/7500/3500/1500

Related Information
For the setting of this parameter, see the description of the Traffic Classification Rule, Match
Value, Wilcard, and Logical Relation Between Matched Rules parameters.
A.10.3 Match Value(Policy Management)

Description
The Match Value parameter indicates the value set for a specific match type among the traffic
classification rules. If certain bits of the match type value (source IP address, for example) are
consistent with the mapping bits of the match value of the traffic classification rule, the packets
match with the traffic classification rule.

Values
Value Range
Default Value

ICMP Packet Type, DSCP Value, IPPrecedence Value, CVlan ID, CVlan priority,
SVlan ID, SVlan priority, DEI

Value
Description
Source IP
Indicates the source IP value when the source IP address matches

the traffic classification rule.
Destination IP
Indicates the destination IP value when the destination IP address

matches the traffic classification rule.
Source MAC Address
Indicates the source MAC address value when the source MAC
address matches the traffic classification rule.
For example, 00-0f-ef-54-aa-00
Destination MAC
Address
Indicates the destination MAC address value when the destination

MAC address matches the traffic classification rule.
For example, 00-0f-ef-54-ab-00
Issue 03 (2012-11-30)

1040
OptiX OSN 7500 II/7500/3500/1500

Value
Description
Protocol Type
Indicates the protocol type value when the protocol type matches the
Protocol type range: tcp, udp, icmp, igmp
Source Port
Indicates the source port value when the source port (available when
the protocol type is TCP and UDP) matches the traffic classification
rule.
The source port value ranges from 0 to 65535.
Destination Port
Indicates the destination port value when the destination port

(available when the protocol type is TCP and UDP) matches the
The destination port value ranges from 0 to 65535.
ICMP Packet Type
Indicates the ICMP packet type value when the ICMP packet type
(available whether protocol type is ICMP) matches the traffic
classification rule.
Value range of ICMP packet type:
echo
echo-reply
fragmentneed-DFset
host-redirect
host-tos-redirect
host-unreachable
information-reply
information-request
net-redirect
net-tos-redirect
net-unreachable
parameter-problem
port-unreachable
protocol-unreachable
reassembly-timeout
source-quench
source-route-failed
timestamp-reply
timestamp-request
ttl-exceeded
DSCP Value
Indicates the value of DSCP when the DSCP value matches the
traffic classification value.
The DSCP value ranges from 0 to 63.
Issue 03 (2012-11-30)

1041
OptiX OSN 7500 II/7500/3500/1500

Value
Description
IP-Precedence Value
Indicates the value of IP-Precedence when the IP-Precedence value

matches the traffic classification value.
The IP-Precedence value ranges from 0 to 7.
CVlan ID
Indicates the value of CVlan ID when the CVlan ID matches the

The CVlan ID value ranges from 0 to 4095.
CVlan priority
Indicates the value of CVlan priority when the CVlan priority

The CVlan priority value ranges from 0 to 7.
SVlan ID
Indicates the value of SVlan ID when the SVlan ID matches the

The SVlan ID vale ranges from 0 to 4095.
SVlan priority
Indicates the value of SVlan priority when the SVlan priority

The SVlan priority value ranges from 0 to 7.
DEI
Indicates the value of DEI when the DEI matches the traffic
classification value.
The DEI value can be 0 or 1.
The match value of each match type should be within the valid range.

None.
Related Information
For details on how to set this parameter, see the description of the Traffic Classification
Rule, Match Type, Wilcard, and Logical Relation Between Matched Rules parameters.
A.10.4 Wildcard(Policy Management)

Description
The Wildcard parameter indicates that the packets need match only a portion of the match
values. The number of digits of the wildcard is consistent with the number of digits of the match
value. After the wildcard is converted to the binary format, digit 0 in the match value should be
matched, but digit 1 need not be considered. In the user packets, if the value of the digit in the
Match Type that the user need consider is equal to the value of the corresponding digit in the
match value. In this case, the user packets match the flow classification rule. Otherwise, the user
packets do not match the flow classification rule.
Issue 03 (2012-11-30)

1042
OptiX OSN 7500 II/7500/3500/1500

When the wildcard is set to all "0"s, it indicates that the packets should strictly match the match
value.
NOTE
The digits of the wildcard, user packet match type value, and match type value indicate the digits after the
values of the wildcard, user packet match type value, and match type are converted to the binary format.
The following example helps you understand the parameter.

l
If the Match Type is Source IP, the match value is 192.168.1.100. In this case, if the
wildcard is 0.0.0.255, it indicates that all the packets whose source IP address starting from
192.168.1. comply with the flow classification rule.
If the Match Type is CVLAN Priority, the match value is 7 (the corresponding binary
value is 111). In this case, if the wildcard is 6 (the corresponding binary value is 110), it
indicates that the packets whose CVLAN priorities are 7, 5, 3, and 1 (the corresponding
binary values are 111, 101, 011, and 001) comply with the flow classification rule.

Values
Value Range
Default Value

ICMP Packet Type, DSCP Value, IPPrecedence Value, CVLAN ID, CVLAN
Priority, SVLAN ID, SVLAN Priority, DEI

Match Type
Description
Source IP
Indicates the wildcard value when the source IP address matches.

For example, 0.0.0.255.
Destination IP
Indicates the wildcard value when the destination IP address

matches. For example, 0.0.255.255.
Source MAC Address
Indicates the wildcard value when the source MAC address

matches.
For example, 00-00-00-00-00-ff.
Destination MAC
Address
Indicates the wildcard value when the destination MAC address

matches.
For example, 00-00-00-00-0f-ff.
Protocol Type
Issue 03 (2012-11-30)
Indicates no wildcard.
1043
OptiX OSN 7500 II/7500/3500/1500

Match Type
Description
Source Port
Indicates the wildcard value when the source port matches.

Value range: 0-65535.
Destination Port
Indicates the wildcard value when the destination port matches.

ICMP Packet Type
DSCP Value
Indicates the wildcard value when the DSCP value matches.

Value range: 0-63.
IP-Precedence Value
Indicates the wildcard value when the IP-Precedence value

matches.
Value range: 0-7.
CVLAN ID
Indicates the wildcard value when the CVLAN ID matches.

CVLAN Priority
Indicates the wildcard value when the CVLAN priority matches.

Value range: 0-7.
SVLAN ID
Indicates the wildcard value when the SVLAN ID matches.

SVLAN Priority
Indicates the wildcard value when the SVLAN priority matches.

Value range: 0-7.
DEI
The wildcard value of each match type should be within its own valid range. When the wildcard
is set to all "0"s, it indicates that the packets should strictly match the match value.

None.
Related Information
For details on how to set this parameter, see the description of the Traffic Classification
Rule, Match Type, Match Value, and Logical Relation Between Matched Rules parameters.
Issue 03 (2012-11-30)

1044
OptiX OSN 7500 II/7500/3500/1500

A.10.5 PW Direction(PW Policy)

Description
In the case of one PW, two directions, that is, the direction of entering the network and the
direction of exiting the network, are available. The PW Direction parameter indicates whether
the PW processes one direction or two directions.

If the PW is set to unidirectional, the PW processes the packets in only one direction. If the user
services are bidirectional, the packets in another direction cannot be processed.
Values
Value Range
Default Value
Bidirectional, Unidirectional

Value
Description
Bidirectional
The PW processes packets in two directions, that is, the

directions of entering and exiting the network.
Unidirectional
The PW processes packets that only enter or only exit the

network.
If the PW need to process packets in two directions, that is, the directions of entering and exiting
the network, the value should be set to bidirectional. Otherwise, the value should be set to
unidirectional. Generally, in the case of the broadcast PW, the value should be set to
unidirectional. In the case of unicast PW, the value should be set to bidirectional.
A.10.6 Direction (PW Policy)

Description
The Direction (PW Policy) parameter indicates the direction for the policy application.

Issue 03 (2012-11-30)

1045
OptiX OSN 7500 II/7500/3500/1500

Values
Value Range
Default Value
Ingress, Egress

Value
Description
Ingress
Indicates that the policy application direction is uplink, that

is, from the UNI to the NNI.
Egress
Indicates that the policy application direction is downlink,

that is, from the NNI to the UNI.
None.
A.10.7 Duplicated Policy Name(PW Policy)

Description
The Duplicated Policy Name (PW Policy) parameter has the same meaning as the Policy
Name parameter and indicates the policy based on which a new policy is created.

You can apply a specified policy to the original policy. As a result, the service scheduling policy
of the original policy is changed by duplicating the service scheduling policy of the specified
policy.
Values
The Duplicated Policy Name parameter should contain letters or numbers or both with a
maximum length of 64 characters. The characters \ or / are not contained.
For changing the current policy, you can directly duplicate the existed policy that satisfies the
requirement to the current policy. In this case, no extra setting is required for the current policy.
A.10.8 Policy ID(Policy Management)

Description
The Policy ID (Policy Management) parameter identifies a policy.
Issue 03 (2012-11-30)

1046
OptiX OSN 7500 II/7500/3500/1500


Values
Policy Type
Value Range
Port policy
0-100
V-UNI ingress policy
0-2000
V-UNI egress policy
0-2000
PW policy
0-2000
QinQ policy
0-2000
0-256
Port WRED policy
0-7
Service WRED policy
0-127
The IDs of policies of different types can be repeated, whereas the IDs of policies of the same
type must be unique.
A.10.9 Policy Name (Policy Management)

Description
The Policy Name (Policy Management) parameter specifies the name of a policy and thus
identifies a policy. Different policies can have the same policy name.

Values
The policy name should contain letters or numbers or both with a maximum length of 64
characters. The characters \ or / are not supported.
Different policies can have the same policy name.
Issue 03 (2012-11-30)

1047
OptiX OSN 7500 II/7500/3500/1500

A.10.10 QinQ Link ID(QinQ Policy)

Description
The QinQ Link ID parameter indicates the unique identifier of a QinQ link.

Values
Value Range
Default Value
1-4294967295
The QinQ Link ID parameter identifies a unique QinQ link. Hence, do not set the same ID for
different QinQ links.
A.10.11 Physical Port ID(QinQ Policy)

Description
The Physical Port ID parameter identifies the physical port that applies the QinQ policy.

Values
Slot number - board name - port number (PORT - number).
None.
A.10.12 S-VLAN ID(QinQ Policy)

Description
The S-VLAN ID parameter is a 12-bit field, indicating the VLAN ID. If a switch supports the
802.1Q protocol, all packets it transmitting contain this 12-bit field. In this case, a packet is
identified by its own VLAN.
Issue 03 (2012-11-30)

1048
OptiX OSN 7500 II/7500/3500/1500


Values
Value Range
Default Value
1-4094
When creating the QinQ, you should define the port and S-LVAN ID. The port and S-LAN ID
cannot be occupied by other services. Moreover, the S-LVAN ID must be set within the valid
range.
A.10.13 Traffic Classification Bandwidth Sharing(Policy

Management)
Description
Set the Traffic Classification Bandwidth Sharing parameter to enable or disable the traffic
classification bandwidth sharing.
Flow Classification of V-UNI Ingress Policy includes the preset Committed Information
Rate. When packets on multiple V-UNIs that use this policy match this Flow Classification, if
Traffic Classification Bandwidth Sharing is enabled, the total bandwidth of these flows is
restrained by the CIR set by Flow Classification. If Traffic Classification Bandwidth
Sharing is disabled, on each V-UNI, the flows that match Flow Classification are restrained
by the CIR set by Flow Classification.

Values
Value Range
Default Value
Enabled, Disabled
Disabled
Issue 03 (2012-11-30)
Value
Description
Disabled
It indicates that the traffic classification bandwidth sharing is

disabled.
1049
OptiX OSN 7500 II/7500/3500/1500

Value
Description
Enabled
It indicates that the traffic classification bandwidth sharing is

enabled.
This parameter is set according to service requirements.
For example, packets on multiple V-UNIs that use a certain V-UNI Ingress Policy match Flow
Classification of this policy. In addition, the service packets of these flows have the same service
features, such as the same destination IP address. In this case, if these service packets need share
the CIR bandwidth set in Flow Classification of this policy, set Traffic Classification
Bandwidth Sharing to Enabled.

When configuring Flow Classification of V-UNI Ingress Policy, set Bandwidth Limit to
Enabled. In addition, the CIR of Flow Classification should be configured. In this case, Traffic
Classification Bandwidth Sharing is valid.
Related Information
For the setting of this parameter, see Traffic Classification Rule.
A.10.14 Coloring Mode (V-UNI Ingress Policy)

Description
The Coloring Mode (V-UNI Ingress Policy) parameter specifies the coloring mode of a certain
flow. Therefore, this parameter specifies whether the original color of the packets in this flow
is considered when the CAR processing is performed on these packets.

Values
Value Range
Default Value
Color-Blind, Chromatic-Sensitive
Color-Blind
Issue 03 (2012-11-30)

1050
OptiX OSN 7500 II/7500/3500/1500

Value
Description
Color-Blind
Indicates the color blindness mode. The CAR is directly

performed for the user packets, which are marked according
to the CAR result.
Chromatic-Sensitive
Indicates the color sensitive mode. In this mode, the original

color of the packet is considered when the CAR processing is
performed. Hence, the green packet is marked green and the
red packet is marked red as preference. In addition, after the
CAR processing is performed, the result is compared with the
original color of the packet and then the packet is marked with
the darker color. The darkness of packet colors in a
descending order is as follows: red, yellow, and green.
After the upstream DS domain marks the service packets accessed into the local DS domain, on
the ingress node of the local DS domain, if the coloration result of the upstream DS domain need
be considered, Chromatic-Sensitive is applicable to the Traffic Classification that matches
the service packets. Otherwise, Color-Blind is applicable.

When the service packets from the upstream DS domain enter the ingress node of the local DS
domain, the color of packets is obtained according to the mapping relation between the packet
priority and color, which is defined in the local DS domain mapping relation. If Coloring
Mode is set to Chromatic-Sensitive, the color of service packets from the upstream DS domain
should be restored. Ensure that the mapping relations of the service packets in the upstream DS
domain and local DS domain are consistent.
A.10.15 Logical Relation Between Matched Rules(V-UNI Ingress

Policy)
Description
When multiple traffic classification rules are set for a flow, set the Logical Relation Between
Matched Rules parameter to specify the logical relations among these traffic classification rules.

Values
Issue 03 (2012-11-30)
Value Range
Default Value
And, Or
And

1051
OptiX OSN 7500 II/7500/3500/1500


Value
Description
And
The packet matches the flow only when the packet matches
each traffic classification rule.
Or
The packet matches the flow when the packet matches one of
the traffic classification rules.
None.

Before setting the Logical Relation Between Matched Rules parameter, set the Traffic
Classification Rule correctly.
A.10.16 Processing Mode(V-UNI Ingress Policy)

Description
The Processing Mode parameter indicates the processing mode for packets of different colors.

Values
Value Range
Default Value
Pass, Discard, Remark
l Green, yellow: Pass

l Red: Discard
Issue 03 (2012-11-30)
Value
Description
Pass
Indicates transparently transmitting or directly forwarding the

packet.
Discard
Indicates discarding the packet.
Remark
Indicates remarking the packet with a different color.

1052
OptiX OSN 7500 II/7500/3500/1500

When a network congestion occurs or the color of the packet needs adjusting, packets of different
colors can be configured with different processing modes.
A.10.17 AF1 Schedule Weight(%)(WFQ Schedule Policy)

Description
The QoS scheduling modes include eight queues. The scheduling algorithm is: Schedule the
CS7 queue > schedule the CS6 queue > schedule the EF queue > schedule the AF1-AF4 queues
according to the weights of the queues > schedule the BE queue. The AF1 Schedule Weight
parameter indicates the percentage of the AF1 queue to the weight when the AF1-AF4 queues
are scheduled according to the weight.

Values
Value Range
Default Value
Unit
1-100
25
The bigger the value of the AF1 scheduling weight, the higher is scheduling priority of the AF1
queue. In this case, when the bandwidth is insufficient, the packet loss ratio is smaller. Reversely,
the smaller the value of the AF1 scheduling weight, the lower is the scheduling priority of the
AF1 queue. In this case, when the bandwidth is insufficient, the packet loss ratio is bigger.

The sum of values of AF1, AF2, AF3, and AF4 scheduling weights cannot exceed 100.

Description

Issue 03 (2012-11-30)

1053
OptiX OSN 7500 II/7500/3500/1500

Values
Value Range
Default Value
Unit
1-100
25
The bigger the value of the AF2 scheduling weight, the higher is the scheduling priority of the
AF2 queue. In this case, when the bandwidth is insufficient, the packet loss ratio is smaller.
Reversely, the smaller the value of the AF2 scheduling weight, the lower is the scheduling
priority of the AF2 queue. In this case, when the bandwidth is insufficient, the packet loss ratio
is bigger.

The sum of values of the AF2, AF1, AF3, and AF4 scheduling weights cannot exceed 100.

Description

Values
Value Range
Default Value
Unit
1-100
25
is bigger.

Issue 03 (2012-11-30)

1054
OptiX OSN 7500 II/7500/3500/1500


Description

Values
Value Range
Default Value
Unit
1-100
25
is bigger.

A.10.21 Discard Lower Threshold (256 bytes) (Service WRED

Policy)
Description
Users can set Discard Lower Threshold and Discard Upper Threshold for a queue. When the
length of a queue is less than the specified value of Discard Lower Threshold, the packet is
not discarded. When the length of a queue is within the range from the specified value of Discard
Lower Threshold to the specified value of Discard Upper Threshold, the weighted random
early detection (WRED) mechanism discards packets at random. When the length of a queue is
more than the specified value of Discard Upper Threshold, the packet is discarded according
to the discard probability that is set by the user.

Issue 03 (2012-11-30)

1055
OptiX OSN 7500 II/7500/3500/1500

Values
Value Range
Default Value
Unit
0-4095
l Red: 1024
256 bytes
l Yellow: 1536
l Green: 2048
When the value of Discard Lower Threshold is smaller, the length of a queue is shorter. The
value of Discard Lower Threshold must not be more than the value of Discard Upper
Threshold.

None.
A.10.22 Discard Upper Threshold (256 bytes) (Service WRED

Policy)
Description
Users can set Discard Lower Threshold and Discard Upper Threshold for a queue. When the
length of a queue is less than the specified value of Discard Lower Threshold, the packet is
not discarded. When the length of a queue is within the range from the specified value of Discard
Lower Threshold to the specified value of Discard Upper Threshold, the weighted random
early detection (WRED) mechanism discards packets at random. When the length of a queue is
more than the specified value of Discard Upper Threshold, the packet is discarded according
to the discard probability that is set by the user.

If Discard Upper Threshold is set to 0, all the packets in this queue are discarded and thus all
the services of this queue are interrupted.
Values
Value Range
Default Value
Unit
0-4095
l Red: 3072
256 bytes
l Yellow: 3584
l Green: 4095
The value of Discard Upper Threshold cannot be less than the value of Discard Lower
Threshold.
Issue 03 (2012-11-30)

1056
OptiX OSN 7500 II/7500/3500/1500


None.
A.10.23 Discard Probability (%) (Service WRED Policy)

Description
The Discard Probability (%) (Service WRED Policy) parameter specifies the ratio of the
packets that are discarded to the total number of packets in a queue when the length of a queue
is more than the specified value of Discard Upper Threshold.

Values
Value Range
Default Value
Unit
1-100
100
The maximum discard probability can be 100%, which indicates that all the packets in a queue
are discarded when the length of the queue is more than the specified value of Discard Upper
Threshold.
A.10.24 PHB (Diffserv domain Management)

Description
The PHB parameter, per hop behavior, indicates a forwarding action applicable on the DS node.
This forwarding action belongs to the per hop forwarding aggregation defined in the DiffServ
domain.

Issue 03 (2012-11-30)

1057
OptiX OSN 7500 II/7500/3500/1500

Values
Value Range
Default Value
BE, AF11, AF12, AF13, AF21, AF22, AF23, AF31,

AF32, AF33, AF41, AF42, AF43, EF, CS6, CS7
The CoS defines different service

classes:
l CS6-CS7: Highest service
classes applicable to transport of
the signaling.
l EF: Fast forwarding, applicable
to the service traffic with the
shortest delay and low packet
loss ratio, such as the audio
service and video service.
l AF1-AF4: Applicable to the
service traffic that requires a
certain rate, but not a certain
delay or jitter.
l BE: Applicable to the service
traffic that does not require
special processing.
When the equipment in different DS domains is interconnected, the mapping relationship in the
egress direction needs to be configured so that the CoS information can be mapped into the
priority bit of the packet.

None.
A.10.25 Packet Type (Diffserv domain Management)

Description
The Packet Type is used to set the packet type.

Values
Value Range
Default Value
cvlan, svlan, mpls-exp, ip-dscp

Issue 03 (2012-11-30)

1058
OptiX OSN 7500 II/7500/3500/1500

Value
Description
cvlan
Specifies the priority information of the C-VLAN packet.
svlan
Specifies the priority information of the S-VLAN packet.

When the DEI is disabled, the CoS mapping is performed only
according to the priority of the S-VLAN packet. When the
DEI is enabled, the DEI bit also indicates the priority. That
is, four bits of a packet indicate the priority.
ip-dscp
Specifies the DSCP domain of the IP packet.
mpls-exp
Specifies the EXP information of the MPLS packet.
The value setting depends on the packet type.
A.10.26 Committed Information Rate (Kbit/s)

Description
The Committed Information Rate (Kbit/s) parameter specifies the CIR of the queue. The
packets whose rates are less than the CIR can be forwarded. When the rate of the packets is not
more than the CIR, all messages can be forwarded. If the rate of the packets is more than the
CIR, some packets are discarded according to a certain packet discarding policy.

Values
Value Range
Default Value
Unit
1024-10000000,
Unlimited
4294967295
kbit/s
The greater CIR, the higher rate of the traffic, and the more packets forwarded.
It is recommended that the rate of the packets is not more than the CIR.

The CIR is not more than the PIR in each queue.
The CIR equals to the PIR in CS7, CS6, and EF queues.
Issue 03 (2012-11-30)

1059
OptiX OSN 7500 II/7500/3500/1500

If the policy is applied to function points, such as PW, port, VUNI, and QINQ, you need to
ensure that the sum of the CIRs in the policies applied to the function point is not more than the
CIR of the function point.
A.10.27 Committed Burst Size (byte)

Description
The Committed Burst Size (byte) parameter specifies the committed burst size.
When the bandwidth is insufficient, some packets cannot be forwarded. Therefore, a buffer is
required to store these packets for forwarding when the bandwidth is sufficient. CBS is the size
of the buffer. When the size of the stored packets is less than the CBS, all these packets can be
forwarded.

Values
Value Range
Default Value
Unit
64-10000000
4294967295
byte
If the CBS is small, the buffer easily overflows and some packets are discarded when the
bandwidth is insufficient.
The greater the CBS is, the more packets can be buffered when the bandwidth is insufficient,
and the less the packet loss ratio is. The greater the CBS, the more serious the delay jitter when
packets are forwarded.
For the OptiX OSN equipment, the CBS is reserved and cannot be set.

None.
A.10.28 Peak Information Rate (kbit/s)

Description
The Peak Information Rate (kbit/s) parameter specifies the maximum rate of services allowed
by the PIR.

Issue 03 (2012-11-30)

1060
OptiX OSN 7500 II/7500/3500/1500

Values
Value Range
Default Value
Unit
64-10000000
4294967295
(kbit/s)
It is recommended that the PIR be not less than the CIR.

None.
A.10.29 Peak Burst Size (byte)

Description
The Peak Burst Size (byte) parameter specifies the size of the PBS.
When the bandwidth is insufficient and the CBS buffer is full, the packets that cannot be stored
in the CBS buffer are stored in the PBS buffer. When the PBS buffer is full, the extra packets
are discarded. The packets stored in the PBS buffer may also fail to be forwarded. The packets
whose rates are more than the CIR and less than the PIR attempt to preempt the remaining
bandwidth. The packets are forwarded only when they preempt the remaining bandwidth.

Values
Value Range
Default Value
Unit
64-10000000
4294967295
byte
Although the packets in the PBS buffer may also fail to be forwarded, the PBS buffer decreases
the packet loss ratio.
The greater the PBS, the less the packet loss ratio, and the more serious the delay jitter when
packets are forwarded.
Issue 03 (2012-11-30)

1061
OptiX OSN 7500 II/7500/3500/1500


None.
A.10.30 EXP
Description
The EXP parameter specifies the field in the MPLS packets for identifying the priority of these
MPLS packets.
E-LSP is used to set the EXP. 77 is the highest priority.

Values
Value Range
Default Value
0, 1, 2, 3, 4, 5, 6, 7, None
None
Issue 03 (2012-11-30)
Value
Description
The values 0-7 correspond to the eight levels of the CoS policy.
The value 0 corresponds to BE.
The value 1 corresponds to AF1.
The value 5 corresponds to EF.
The value 6 corresponds to CS6.
The value 7 corresponds to CS7.

1062
OptiX OSN 7500 II/7500/3500/1500

The higher the value of the EXP parameter, the higher the priority of the packets.

None.
A.10.31 LSP Mode

Description
The LSP Mode parameter specifies the mode in which the MPLS network processes packet
priorities.
When a label is allocated to a PW, the CoS policy of the packets may be changed. Therefore, it
is necessary to determine whether the CoS policy of the packets needs to be restored when the
PW label is stripped from the packets. The LSP Mode parameter specifies whether the CoS
policy of the packets needs to be restored.

Values
Value Range
Default Value
Pipe, Uniform
Uniform

Value
Description
Pipe
Indicates that the CoS policy of the packets need not to be restored
when the tunnel labels are peeled off.
Uniform
Indicates that the CoS policy of the packets need to be restored

when the tunnel labels are peeled off.
None.

None.
Issue 03 (2012-11-30)

1063
OptiX OSN 7500 II/7500/3500/1500

A.11 QoS Associated Parameters

This topic describes the parameters for configuring the QoS function
A.11.1 Flow Type (Flow Configuration)

Description
The Flow Type(Flow Configuration) parameter specifies Flow Type of the flow in the Ethernet
data board. This parameter decides the method of binding the service with the flow.

If the Flow Type parameter is set incorrectly, that is, the flow classification method is incorrect,
the (Bound CAR or Bound CoS) parameter may fail to meet the expected result. For the effects
of CAR and CoS, refer to the relevant description.
Values
Board Name
Value Range
Default Value
N1EMS4, N1EGS4,
N3EGS4
l Port Flow
Port Flow
l Port+VLAN Flow
l Port+SVLAN Flow
N4EFS0, N5EFS0,
N2EFS4, N3EFS4,
N2EGS2, N3EGS2,
N2EMR0, N2EGR2
l Port Flow
N1EFS0A,
N1EMS2, N4EGS4
l Port Flow
Port Flow
l Port+VLAN Flow
l Port+VLAN+Priority
Port Flow
l Port+VLAN Flow
l Port+VLAN+Priority
l Port+SVLAN Flow
N1EAS2
l Port Flow
Port Flow
l Port+VLAN Flow
l Port+SVLAN Flow
l Port+CVLAN+SVLAN Flow
Issue 03 (2012-11-30)
Value
Description
Port Flow
All the packets entering the specified port are

regarded as one flow.
1064
OptiX OSN 7500 II/7500/3500/1500

Value
Description
Port+VLAN Flow
All the packets that enter the specified port, and

whose Tag VID is consistent with the specified VID,
are regarded as one flow.
Port+VLAN+Priority
All the packets that enter from the specified port, and
whose VLAN Tag VID and priority are consistent
with the specified VID and priority, are regarded as
one flow.
Port+SVLAN Flow
whose SVLAN VID is consistent with the specified
VID, are regarded as one flow.
Port+CVLAN+SVLAN Flow
whose SVLAN VID and CVLAN VID are consistent
with the specified VID, are regarded as one flow.
Based on the required QoS and service type, set a proper value for Flow Type.

None.
A.11.2 Bound CAR (Flow Configuration)

Description
The Bound CAR (Flow Configuration) parameter specifies the method of binding a flow with
a CAR ID and querying the CAR ID bound with the flow. One flow can be bound with one CAR
ID only. The CAR takes effect only after the flow is bound with the CAR.

The CAR-based flow rate can take effect only after the flow is bound with the enabled CAR
policy.
Values
Value Range
Default Value
Created CAR ID
The created flow can be bound with the created CAR policy only. For this reason, you can select
the value from the created CAR ID.
Issue 03 (2012-11-30)

1065
OptiX OSN 7500 II/7500/3500/1500


A flow can be bound with the CAR only after the flow and CAR are created.
A.11.3 Bound CoS (Flow Configuration)

Description
The Bound CoS (Flow Configuration) parameter specifies the method of binding a flow with
a CoS ID and querying the CoS ID bound with the flow. A flow can be bound with one CoS ID
only. The CoS policy can be used to divide the packet priority after the flow is bound with the
CoS.

The flow packets can be divided into different priorities based on the CoS rules only after the
flow is bound with the CoS.
Values
Value Range
Default Value
Created CoS ID
The created flow can be bound with the created CoS policy only. For this reason, you can select
the value from the created CoS ID.

A flow can be bound with the CoS only after the flow and CoS are created.
A.11.4 CAR ID (CAR Configuration)

Description
The CAR ID (CAR Configuration) parameter specifies the ID of a committed access rate
(CAR). After a CAR is created, it needs to be specified with a CAR ID.

Values
The value ranges for each type of board is as follows:
Issue 03 (2012-11-30)

1066
OptiX OSN 7500 II/7500/3500/1500

Board Name
Value Range
Default Value

N4EGS4
1-4095

N3EFS4, N2EGS2, N3EGS2,
N1EFS0A, N1EMS2,
N1EAS2, N2EMR0, N2EGR2
1-2048
You can set this parameter to any value within the value range as required. Each CAR has a
unique CAR ID.

None.
A.11.5 CAR Enabled/Disabled (CAR Configuration)

Description
The CAR Enabled/Disabled (CAR Configuration) parameter specifies whether a CAR can
limit the traffic volume.

After the CAR is enabled and bound with a flow, the traffic volume of the flow is limited
depending on the value of the CAR parameter. If the transmitted traffic is greater than the
specified value, the excessive traffic is discarded.
Values
Valid Value
Default Value
Enabled, Disabled
Disabled
Issue 03 (2012-11-30)
Value
Description
Disabled
A CAR is created, but does not take effect.
Enabled
A CAR is created, and takes effect.

1067
OptiX OSN 7500 II/7500/3500/1500

You can set this parameter to Enabled or Disabled, depending on whether the CAR is required
to limit the traffic volume.

A CAR can limit the traffic of a flow only when it is set to Enabled and bound with a flow.
A.11.6 Committed Information Rate (CAR Configuration)

Description
The Committed Information Rate (CAR Configuration) parameter specifies the committed
information rate (CIR) of the committed access rate (CAR). It specifies the minimum guarantee
bandwidth of a flow.

After the CAR is enabled and bound with a flow, the committed bandwidth of the flow is
guaranteed. If the traffic volume is greater than the guarantee bandwidth, the transmission of
excessive traffic cannot be guaranteed.
Values
Board Name
Value Range
Default
Value
Unit
N1EAS2
An integer of 0-10485760, in step

length of 64
kbit/s
N1EMS4, N1EGS4,
N3EGS4, N4EGS4

length of 64
kbit/s
N4EFS0, N5EFS0,
N2EFS4, N3EFS4,
N2EGS2, N3EGS2,
N2EMR0, N2EGR2,
N1EFS0A,
N1EMS2

length of 64
kbit/s
Based on the actual QoS requirement, set a proper value for Committed Information Rate.
Generally, the value of Committed Information Rate is not less than the expected average rate
for transmitting the flow.

You can set Committed Information Rate of a CAR only after creating the CAR.
Issue 03 (2012-11-30)

1068
OptiX OSN 7500 II/7500/3500/1500

A.11.7 Committed Burst Size (CAR Configuration)

Description
The Committed Burst Size (CAR Configuration) parameter specifies the maximum
guaranteed data volume of a flow, which can be transmitted within a certain period.

After the CAR is enabled and bound with a flow, if the volume of burst data in the flow is less
than the value of Committed Burst Size, the burst data can be guaranteed for transmission.
Otherwise, they cannot be guaranteed for transmission.
Values
Board Name
Value Range
Default Value
Unit
N1EAS2
0-2048
Kbyte
N4EFS0, N5EFS0,
N2EFS4, N3EFS4,
N2EGS2, N3EGS2,
N1EFS0A, N1EMS2,
N2EMR0, N2EGR2
0-128
Kbyte
N1EMS4, N1EGS4,
N3EGS4, N4EGS4
0-32
Kbyte
Based on the actual QoS requirements, set a proper value for Committed Burst Size.
Generally, the value of Committed Burst Size is not less than the possible size of expected
burst data flow to be transmitted.

You can set Committed Burst Size of a CAR only after creating the CAR.
A.11.8 Peak Information Rate (CAR Configuration)

Description
The Peak Information Rate (CAR Configuration) parameter specifies the peak information
rate (PIR) of the committed access rate (CAR). It specifies the allowed maximum rate of a flow.

After the CAR is enabled and bound with a flow, the flow rate is limited according to the peak
bandwidth of the CAR parameter.
Issue 03 (2012-11-30)

1069
OptiX OSN 7500 II/7500/3500/1500

If the traffic volume is greater than the value of Peak Information Rate, the excessive traffic
is discarded.
Values
Board Name
Value Range
Default Value
Unit
N1EAS2
An integer of 0-10485760, in
step length of 64
kbit/s
N1EMS4,
N1EGS4, N3EGS4,
N4EGS4

length of 64
kbit/s
N4EFS0, N5EFS0,
N2EFS4, N3EFS4,
N2EGS2, N3EGS2,
N2EMR0,
N2EGR2,
N1EFS0A,
N1EMS2

length of 64
kbit/s
Based on the actual QoS requirement, you can set a proper value for Peak Information Rate.
The value of Peak Information Rate should not be less than the guarantee bandwidth.
Generally, the value of Peak Information Rate is not greater than the expected maximum rate
of transmitting the flow.

You can set Peak Information Rate for a CAR only after creating the CAR.
A.11.9 Maximum Burst Size (CAR Configuration)

Description
The Maximum Burst Size (CAR Configuration) parameter specifies the maximum excessive
data volume of a flow, which can be transmitted within a certain period.

After the CAR is enabled and bound with a flow, if the burst data volume of the flow is greater
than the value of Maximum Burst Size, the excessive data is discarded.
Issue 03 (2012-11-30)

1070
OptiX OSN 7500 II/7500/3500/1500

Values
Board Name
Value Range
Default
Value
Unit
N1EAS2
0-2048
kbyte

N4EGS4
0-32
kbyte

N3EFS4, N2EGS2, N3EGS2,
N2EMR0, N2EGR2, N1EFS0A,
N1EMS2
kbyte
Based on the actual requirement of QoS, you can set a proper value for Maximum Burst
Size.
Generally, the value of Maximum Burst Size is not greater than the size of burst data flow to
be transmitted.

You can set Maximum Burst Size of a CAR only after creating the CAR.
A.11.10 CoS ID (CoS Configuration)

Description
The CoS ID (CAR Configuration) parameter specifies the ID of a class of service (CoS). When
a CoS is created, it needs to be specified with a unique CoS ID.

Values
The value ranges for each type of board is as follows:
Issue 03 (2012-11-30)
Board Name
Value Range
Default Value
N1EAS2, N3EGS2, N1EMS4,

N1EGS4, N3EGS4, N4EGS4
1-65535

N3EFS4, N2EGS2, N1EFS0A,
N1EMS2, N2EMR0, N2EGR2
1-8192

1071
OptiX OSN 7500 II/7500/3500/1500

You can set this parameter to any value in the value range as required. A CoS maps a CoS ID.

None.
A.11.11 CoS Type (CoS Configuration)

Description
The CoS Type (CoS Configuration) parameter specifies the type of CoS of the flow in the
Ethernet data board. This parameter decides the method adopted to classify the flow in the
Ethernet data board.

If CoS Type is set incorrectly, packets cannot be correctly dispatched to a proper queue.
Values
Board Name
Value Range
Default Value
N1EAS2, N2EFS0,
N2EGS2
Simple, VLAN priority
Simple
N1EMS4, N1EGS4,
N3EGS4, N4EGS4,
N5EFS0, N3EFS4,
N3EGS2, N2EMR0,
N2EGR2, N1EFS0A,
N1EMS2, N2EFS4,
N4EFS0
Simple, VLAN priority, IPTOS, DSCP
Simple
Issue 03 (2012-11-30)
Value
Description
Simple
Assigns the CoS Priority based on the flow.
VLAN priority
Assigns the CoS Priority based on the VLAN priority.
IPTOS
Assigns the CoS Priority based on the TOS field in the IP

packet header.
DSCP
Assigns the CoS Priority based on the DSCP field in the IP

packet header.

1072
OptiX OSN 7500 II/7500/3500/1500

Based on the requirements of QoS, set a proper value for CoS Type.

None.
A.11.12 CoS Priority (CoS Configuration)

Description
The CoS Priority (CoS Configuration) parameter classifies packets into different levels based
on the CoS type, and maps these packets into different CoS priorities. The packets of higher
priorities are first processed.

The packets of higher priorities are transmitted before those of lower priorities. Moreover, better
service quality is available.
Values
For the CoS of the simple type, follow Table A-6 to set a simple CoS Priority.
Table A-6 CoS priority of the simple type
Data Board
CoS
Parameter
Value Range of
CoS Parameter
Value Range of
CoS Priority
Default Value
of CoS
Priority
N4EFS0,
N2EFS4,
N2EGS2,
N1EFS0A,
N1EMS2,
N1EAS2,
N3EGS2,
N3EGS4,
N4EGS4
Invalid
Invalid
0-7
N5EFS0,
N1EMS4,
N1EGS4
Invalid
Invalid
0-3
N3EFS4
Invalid
Invalid
0-1
N2EMR0,
N2EGR2
Invalid
Invalid
A/B/C
For the CoS of the VLAN Priority type, follow Table A-7 to set the mapping from VLAN
Priority to CoS Priority.
Issue 03 (2012-11-30)

1073
OptiX OSN 7500 II/7500/3500/1500

Table A-7 CoS priority of the VLAN Priority type

Data Board
CoS
Parameter
Value Range of
CoS Parameter
Value Range of
CoS Priority
Default Value
of CoS
Priority
N4EFS0,
N2EFS4,
N2EGS2,
N1EFS0A,
N1EMS2
User priority
in VLAN
0-7
0-7
Value range of
the mapping
CoS priority: -
N1EAS2
User priority
in VLAN
0-7
0-7
The same as that

of VLAN
priority
N3EGS2
User priority
in VLAN
0-7
0-7
N5EFS0,
N1EMS4,
N1EGS4,
N3EGS4,
N4EGS4
User priority
in VLAN
0-7
0-3
N3EFS4
User priority
in VLAN
0-7
0-1
N2EMR0,
N2EGR2
User priority
in VLAN
0-7
A/B/C
For the CoS of the IPTOS type, follow Table A-8 to set the mapping from IPTOS Priority to
CoS Priority.
Table A-8 CoS priority of the IPTOS type
Issue 03 (2012-11-30)
Data Board
CoS
Parameter
Value Range of
CoS Parameter
Value Range of
CoS Priority
Default Value
of CoS
Priority
N4EFS0,
N2EFS4,
N2EGS2,
N1EFS0A,
N1EMS2,
N3EGS2
IPTOS
0000-1111 (in
binary)
0-7
N5EFS0,
N1EMS4,
N1EGS4,
N3EGS4,
N4EGS4
IPTOS
0000-1111 (in
binary)
0-3

1074
OptiX OSN 7500 II/7500/3500/1500

Data Board
CoS
Parameter
Value Range of
CoS Parameter
Value Range of
CoS Priority
Default Value
of CoS
Priority
N3EFS4
IPTOS
0000-1111 (in
binary)
0-1
N2EMR0,
N2EGR2
IPTOS
0000-1111 (in
binary)
A/B/C
For the CoS of the DSCP type, follow Table A-9 to set the mapping from DSCP Priority to
CoS Priority.
Table A-9 CoS priority of the DSCP type
Data Board
CoS
Parameter
Value Range of
CoS Parameter
Value Range of
CoS Priority
Default Value
of CoS
Priority
N4EFS0,
N2EFS4,
N2EGS2,
N1EFS0A,
N1EMS2,
N3EGS2
DSCP
000000-111111 (in
binary)
0-7
N5EFS0,
N1EMS4,
N1EGS4,
N3EGS4,
N4EGS4
DSCP
000000-111111 (in
binary)
0-3
N3EFS4
DSCP
000000-111111 (in
binary)
0-1
N2EMR0,
N2EGR2
DSCP
000000-111111 (in
binary)
A/B/C
Based on the requirements, you can map the packets into different queues by setting CoS
Priority.
If CoS Type is set to VLAN Priority, IPTOS or DSCP, generally, you can map the packets
into the proper CoS Priority according to the priority information contained in the packets.
At the application layer, if a service (for example, VOIP, video conference, video conferencing
call, and video on demand) has higher requirements for QoS, set a higher priority for the service
to get better bandwidth and service guarantee. To ensure good bandwidth multiplexing, be sure
to avoid a larger ratio of real-time services in the network. For a service (for example, Internet
access, E-Mail, and FTP) that has lower requirements for QoS, set a lower priority for the service
to provide better bandwidth sharing and contention mechanism.
Issue 03 (2012-11-30)

1075
OptiX OSN 7500 II/7500/3500/1500

For the N1EAS2 board, queue 7 has the absolute priority. That is, if queue 7 is congested, all
the queues must wait. Generally, queue 7 is used for the protocol or management packets of light
traffic. The remaining bandwidth is allocated in proportion for other queues. Queue 0 has the
lowest priority. For a higher priority, no bandwidth is used if no service is available.

None.
A.11.13 Shaping
Description
Shaping indicates the flow shaping function of all the four queues of every port on the N1EMS4,
N1EGS4, N3EGS4. or N4EGS4. This parameter includes the guaranteed bandwidth and capacity
of extra burst cache.
For the N1EAS2, every port has eight queues, and every queue has flow shaping function. The
parameter to set includes the guaranteed bandwidth and peak bandwidth.

If the guaranteed bandwidth of the parameter is excessively high, the shaping effect is not good.
If the capacity of extra burst cache is large, more burst packets can be cached but the delay of
the cached packets at the port increases.
Values
Name
Value Range
Default Value
Port List
l Indicates that every port of the N1EMS4,

N1EGS4, N3EGS4, N4EGS4, and N5EFS0 has
four queues.
l The N1EAS2: Every port has eight queues.

Status
l Enabled
Disabled
l Disabled
CIR
l The N1EMS4, N1EGS4, N3EGS4 and

N4EGS4: An integer between 0-2499968. The
step length is 64 and the unit is kbit/s.
l The N1EAS2: An integer between 0-10485760.

The step length is 64 and the unit is kbit/s.
DCBS
l The N1EMS4, N1EGS4, N3EGS4, and

N4EGS4: 0-32 (kbyte)
l The N1EAS2: Not configurable

PIR
l The N1EMS4, N1EGS4 and N3EGS4: Not

configurable
l The N1EAS2: An integer between 0-10485760.

The step length is 64 and the unit is kbit/s.
Issue 03 (2012-11-30)

1076
OptiX OSN 7500 II/7500/3500/1500

Name
Value Range
Default Value
DMBS
l The N1EMS4, N1EGS4 and N3EGS4: Not

configurable
l The N1EAS2: Not configurable
The user can set this parameter according to the actual bandwidth rate of the output port.

None.
A.12 ATM Interface Associated Parameters (Packet Mode)

This topic describes the parameters for configuring ATM interface.
A.12.1 ATM Cell Payload Scrambling(ATM Interface

Management)
Description
The ATM Cell Payload Scrambling (ATM Interface Management) parameter specifies
whether to scramble the payload of cells on asynchronous transfer mode (ATM) links.

Different settings of this parameter for ports at both ends of an inverse multiplexing for ATM
(IMA) link result in unavailable services.
Values
Value Range
Default Value
Enabled, Disabled
Enabled
Set this parameter to the same value for the equipment at the local and opposite ends. That is, if
scrambling is performed on the payload of cells transmitted by the equipment at the opposite
end, the payload of cells transmitted by the equipment at the local end must also be scrambled.
Generally, set this parameter to the default value (Enabled).

None.
Issue 03 (2012-11-30)

1077
OptiX OSN 7500 II/7500/3500/1500

Related Information
Scrambling is another type of coding technology that is commonly used for serial link
transmission. The purpose of scrambling is to suppress consecutive "1" bits and consecutive "0"
bits to facilitate extraction of clock signals from line signals. Line signals are scrambled only.
Therefore, the rate of SDH line signals is the same as that of standard signals at SDH electrical
interface, and this does not add extra optical power penalty to the laser at the transmit end.
An ATM cell is the basic carrier for transmitting ATM information. An ATM cell, which consists
of only 53 bytes, is divided into a 5-byte header and a 48-byte payload.
A.12.2 Min.VPI(ATM Interface Management)

Description
The Min.VPI parameter specifies the minimum virtual path identifier (VPI) value of the
permanent virtual paths (PVPs) and permanent virtual channels (PVCs) that are applicable to a
selected board.

The VPI value specifies the valid range of VPIs and identifies the number of available VPIs at
a port. You can change the number of VPIs to a proper value based on the requirements of the
port.
Setting this parameter results in re-creation of the deleted connections to the selected board. As
a result, service packets are lost.
Values
Value Range
Default Value
UNI port: 0-255; NNI port:

0-4095
Set this parameter according to the VPI values required for a port. For example, if a port needs
to converge 500 PVCs and if each PVC has a unique VPI, 500 VPIs are required for service
identification. Therefore, ensure that the offset value between the maximum number of VPIs
and the minimum number of VPIs is greater than 500.
For the TNN1D75E and TNN1D12E boards, this parameter cannot be set to the minimum
number of VPIs. That is, the number of VPIs is not limited.
For the TNN1AFO1 board, the sum of the minimum numbers of VPIs of all ports is less than
4096.

None.
Issue 03 (2012-11-30)

1078
OptiX OSN 7500 II/7500/3500/1500

Related Information
The operations on an ATM network are similar to a call connection process. Before a
conversation, a virtual channel connection (VCC), which is identified with a VPI/a virtual
channel identifier (VCI), must be set up between the source end and the destination end.
l
VPI: stands for virtual path identifier.
VCI: stands for virtual channel identifier.
VP switching: changes only VPI values and transparently transmits VCI values in the
switching process.
VC switching: changes VPI values and VCI values in the switching process.
PVP: stands for permanent virtual path.
PVC: stands for permanent virtual channel.
A.12.3 Min.VCI(ATM Interface Management)

Description
The Min.VCI parameter specifies the minimum virtual channel identifier (VCI) value for
permanent virtual channels (PVCs) that are applicable to a selected board.

The VCI value specifies the valid range of VCIs and identifies the number of available VCIs at
a port. You can change the number of VCIs to a proper value based on the requirements of the
port.
Setting this parameter results in re-creation of the deleted connections to the selected board. As
a result, service packets are lost.
Values
Value Range
Default Value
0-65535
65535
Set this parameter according to the number of VCIs required for a port. For example, if a port
needs to converge 500 PVCs and if each PVC has a unique VCI, 500 VCIs are required for
service identification. Therefore, ensure that the offset value between the maximum number of
VCIs and the minimum number of VCIs is greater than 500.
For the TNN1D75E and TNN1D12E boards, this parameter cannot be set to the minimum
number of VCIs. That is, the number of VCIs is not limited.
This parameter can be set to other values only when the number of VPIs that are applicable to
VCCs at a port is not 65535.
Issue 03 (2012-11-30)

1079
OptiX OSN 7500 II/7500/3500/1500


None.
Related Information
conversation, a virtual channel connection (VCC), which is identified with a virtual path
identifier (VPI)/a VCI, must be set up between the source end and the destination end.
l
switching process.
A.12.4 VCC-Supported VPI Count(ATM Interface Management)

Description
The VCC-Supported VPI Count parameter specifies the number of virtual path identifiers
(VPIs) available for a permanent virtual channel (PVC) connection at a port. That is, only the
specified number of VPIs can be adopted for establishment of a PVC connection regardless of
the specified VPI value. In other circumstances, the specified number of VPIs can be adopted
for establishment of a permanent virtual path (PVP) connection.

This parameter limits the number of VPIs that can be used for establishment of a VC connection,
and therefore affects allocation of system resources. In practice, you need to set this parameter
based on services.
Values
Board Name
Value Range
Default Value
TNN1AFO1
0-256, 65535
65535
Set this parameter according to the number of VCIs required for each VPI at a port.
For example, if 50 PVCs need to be established at a port and if each PVC has a unique VPI, 50
VPIs are required for service identification. Therefore, set the number of VPIs available for VC
switching to 50. The value 65535 indicates that the number of VPIs for establishment of a VC
connection is not limited.
If any connections are available at a port, this parameter is unavailable.
Issue 03 (2012-11-30)

1080
OptiX OSN 7500 II/7500/3500/1500


The number of VPIs for a VCC must be less than the offset value between the maximum number
and the minimum number of VPIs.
Related Information
conversation, a virtual channel connection (VCC), which is identified with a VPI/a VCI, must
be set up between the source end and the destination end.
l
switching process.
A.13 ATM/IMA Services Associated Parameters (Packet

Mode)
This topic describes the parameters for configuring ATM/IMA services.
A.13.1 IMA Transit Frame Length

Description
The IMA Transit Frame Length parameter specifies the length of an inverse multiplexing for
ATM (IMA) frame transmitted by the equipment at the local end. That is, this parameter specifies
the number of asynchronous transfer mode (ATM) cells in an IAM frame.
An IMA frame contains an IMA control protocol (ICP) cell for negotiation of the IMA control
protocol and transmission of information.

None.
Values
Issue 03 (2012-11-30)
Value Range
Default Value
32, 64, 128, 256
128

1081
OptiX OSN 7500 II/7500/3500/1500

The TNN1D75E and TNN1D12E boards support the IMA function. Therefore, set the length of
IMA frames to be the same as that of the IMA frames for the interconnected boards.
For example, if IMA groups on two NEs are connected to each other, set the length of IMA
frames transmitted at both the local and opposite ends to 128.

None.
Related Information
None.
A.13.2 IMA Symmetry Mode

Description
The IMA Symmetry Mode parameter specifies the configuration and operation mode of inverse
multiplexing for ATM (IMA) links in an IMA group.

Different symmetrical modes determine the unidirectional conductivity of an IMA link (that is,
only one receive or transmit direction is available for an IMA link).
Values
Value Range
Default Value

Operation, Symmetrical Mode and
Asymmetrical Operation, Asymmetrical
Mode and Asymmetrical Operation

Operation
Issue 03 (2012-11-30)
Value
Description
Symmetrical Mode
and Symmetrical
Operation
Indicates that all links in the IMA group are configured with the
capabilities of receiving and transmitting services in two directions
when you configure an IMA group (in symmetrical configuration
mode). If services on a link are simultaneously interrupted in the
receive and transmit directions, this link is bidirectionally unavailable
(in symmetrical operation mode).

1082
OptiX OSN 7500 II/7500/3500/1500

Value
Description
Symmetrical Mode
and Asymmetrical
Operation
Indicates that all links in the IMA group are configured with the
capabilities of receiving and transmitting services in two directions
when you configure an IMA group (in symmetrical configuration
mode). If services on a link are interrupted in one direction but available
in the other direction, this link is unidirectionally available (in
asymmetrical operation mode).
Asymmetrical
Mode and
Asymmetrical
Operation
Indicates that some links in the IMA group are configured with only
the capabilities of receiving and transmitting services in one direction
when you configure an IMA group (in asymmetrical configuration
mode). If services on a link are interrupted in one direction but available
in the other direction, this link is unidirectionally available (in
asymmetrical operation mode).
For the TNN1D75E and TNN1D12E boards, this parameter can be set only to Symmetrical
Mode and Symmetrical Operation.

If IMA Symmetry Mode is set to Symmetrical Mode and Symmetrical Operation,
Minimum Number of Active Transmitting Links must be equal to Minimum Number of
Active Receiving Links.
Related Information
None.
A.13.3 Maximum Delay Between Links(ms)(IMA Group

Management)
Description
The Maximum Delay Between Links(ms) parameter specifies the maximum delay tolerance
between links in an inverse multiplexing for ATM (IMA) group. That is, this parameter specifies
the allowed maximum difference between the maximum delay value and the minimum delay
value of all links in an IMA group. If the maximum difference exceeds the specified value, the
equipment reports the lODS alarm for a link who has the largest offset value compared with the
average delay value of all links in the MA group. Then, the equipment removes the alarmed link
from the IMA group.

This parameter determines the allowed maximum difference between the maximum delay value
and the minimum delay value of all links. If delay variation of all links in an IMA group is great,
set delay tolerance to a large value to avoid removal of a link whose delay value is great from
the IMA group. If some links that have great delay values are not removed from the IMA group,
Issue 03 (2012-11-30)

1083
OptiX OSN 7500 II/7500/3500/1500

the transmit and receive rates of the IMA group decrease, and the transmission delay of the IMA
group may increase.
Values
Value Range
Default Value
1-120
25
Set this parameter properly according to the requirements for link delay and service delay.
It is recommended that you take the default value.

None.
Related Information
None.
A.13.4 Minimum Number of Active Transmitting Links(IMA

Group Management)
Description
The Minimum Number of Active Transmitting Links parameter specifies the lower threshold
of active links in the transmit direction in an inverse multiplexing for ATM (IMA) group to
maintain proper operation of the IMA group.
An incorrect setting of this parameter may result in service interruption. If the number of active
links in the transmit direction of an IMA group is less than the bandwidth specified for boards
but equal to or greater than the specified minimum number of active links, the IMA group
functions properly. If the number of active links in the transmit direction of an IMA group is
less than the specified minimum number of active links, services of the IMA group are
interrupted.
Values
Issue 03 (2012-11-30)
Value Range
Default Value
1-16

1084
OptiX OSN 7500 II/7500/3500/1500

Set the minimum number of active links, depending on the equipment at the opposite end. For
example, 10 active links are currently available, the total bandwidth is 20 Mbit/s, and the
interconnected equipment requires a minimum of 15 Mbit/s bandwidth. To meet the preceding
requirements, set the minimum number of active links to 8. If the minimum number of active
links is less than 8, the bandwidth is less than 15 Mbit/s. As a result, services in the IMA group
are interrupted.
For the TNN1D75E and TNN1D12E boards, configure a maximum of 16 IMA links for an IMA
group due to hardware constraints. Therefore, the minimum number of active links in the transmit
direction cannot be more than 16.

This parameter takes effect only after an IMA group is configured. If the IMA group is enabled,
Minimum Number of Active Transmitting Links cannot be set to a value greater than the
number of links in the existing IMA group.
Related Information
None.
A.13.5 Minimum Number of Active Receiving Links(IMA Group

Management)
Description
The Minimum Number of Active Receiving Links parameter specifies the lower threshold of
active links in the receive direction in an inverse multiplexing for ATM (IMA) group to maintain
proper operation of the IMA group.

An incorrect setting of this parameter may result in service interruption. If the number of active
links in the receive direction of an IMA group is less than the bandwidth specified for boards
but equal to or greater than the specified minimum number of active links, the IMA group
functions properly. If the number of active links in the receive direction of an IMA group is less
than the specified minimum number of active links, services in the IMA group are interrupted.
Values
Value Range
Default Value
1-16
Set the minimum number of active links, depending on the equipment at the opposite end. For
the TNN1D75E and TNN1D12E boards, configure a maximum of 16 IMA links for an IMA
Issue 03 (2012-11-30)

1085
OptiX OSN 7500 II/7500/3500/1500

group due to hardware constraints. Therefore, the minimum number of active links in the receive
direction cannot be more than 16.
You can specify the minimum number of active links based on the actual service transmission.
For example, 10 active links are currently available, the total bandwidth is 20 Mbit/s, and the
interconnected equipment requires a minimum of 15 Mbit/s bandwidth. To meet the preceding
requirements, set the minimum number of active links to 8. If the minimum number of active
links is less than 8. the bandwidth is less than 15 Mbit/s. As a result, services in the IMA group
are interrupted.

This parameter takes effect only after an IMA group is configured. If the IMA group is enabled,
the minimum number of active links in the receive direction cannot be set to a value greater than
the number of existing links in the IMA group.
Related Information
None.
A.13.6 Clock Mode(IMA Group Management)

Description
The Clock Mode parameter specifies the clock mode for operations of an inverse multiplexing
for ATM (IMA) group.

In an IMA group, all links can trace the same clock source, and a link can also use a separate
clock source. The clock mode of an IMA group determines the method of selecting a clock
source in the IMA group for signal transmission.
Values
Value Range
Default Value
CTC Mode, ITC Mode
CTC Mode
Issue 03 (2012-11-30)
Value
Description
CTC Mode
Indicates the common transmit clock (CTC) mode in which the same
clock source is used for all links in an IMA group.
ITC Mode
Indicates the independent transmit clock (ITC) mode in which the

transmit clock on a link in an IMA group is independently derived
from a clock source.

1086
OptiX OSN 7500 II/7500/3500/1500

The clock modes must be the same at both ends of an IMA group.

None.
Related Information
None.
A.13.7 Near-End Group Status(IMA Group Status)

Description
The Near-End Group Status parameter displays the status of an inverse multiplexing for ATM
(IMA) group at the local end.

Values
Value Range
Default Value
Start-Up, Start-Up-ACK, Config-Aborted,

Insufficient-Links, Operational
Start-Up
Issue 03 (2012-11-30)
Value Range
Description
Start-Up
Indicates that the equipment at the local end

starts up and waits for startup of the
equipment at the opposite end.
Start-Up-ACK
Indicates the waiting state of the IMA group,

which is displayed after the equipment at the
local and opposite ends starts up.
Config-Aborted
Indicates that the parameter settings for the

equipment at the local and opposite ends do
not match.
Insufficient-Links
Indicates that the parameter settings for the

equipment at the local and opposite ends
match, but no sufficient link resource is
available.

1087
OptiX OSN 7500 II/7500/3500/1500

Value Range
Description
Operational
Indicates that the IMA group is enabled and

sufficient link resources are available.
None.

This parameter shows the IMA negotiation status on the NE side. If an IMA group is set to
Enabled, the status of the IMA group cannot be queried.
Related Information
None.
A.13.8 Differential Delay Check Status(IMA Link States)

Description
The Differential Delay Check Status parameter displays the result returned when you query
the statuses of inverse multiplexing for ATM (IMA) links.

Values
Value Range
Default Value
Unknown, Valid, Invalid
Unknown
Issue 03 (2012-11-30)
Value
Description
Unknown
Indicates that the delay value of links is not computed. If an IAM group
is configured or if the equipment at the local end cannot receive
information from links at the opposite end, the delay on links cannot
be computed.
Valid
Indicates that the loss of delay synchronization (LODS) alarm is not

reported on links.
Invalid
Indicates that the LODS alarm is reported on links.

1088
OptiX OSN 7500 II/7500/3500/1500

None.

None.
Related Information
None.
A.13.9 Connection Type(Per-NE ATM Service Management)

Description
The Connection Type parameter specifies the type of an asynchronous transfer mode (ATM)
connection.

Values
Value Range
Default Value
PVP, PVC, Port Transparent
UNIs-NNI: PVC, UNI-UNI: PVP

Value
Description
PVP
Transmits services that contain the same

virtual path identifier (VPI) but different
virtual channel identifiers (VCIs).
PVC
Transmits services that contain the same VPI

and VCI.
Port Transparent
Transparently transmits all services

regardless of their VPIs and VCIs without
establishment of connections.
If services that contain the same VPI need to be converged at a port, set this parameter to
PVP.
Issue 03 (2012-11-30)

1089
OptiX OSN 7500 II/7500/3500/1500

If services that contain the same VPI and VCI need to be transmitted, set this parameter to
PVC. A permanent virtual channel (PVC) and a permanent virtual path (PVP) are virtual
transmission paths, but a PVC is contained in a PVP.

None.
Related Information
A PVC and a PVP are virtual transmission paths, but a PVC is contained in a PVP.
l
switching process.
A.13.10 Uplink Policy(Per-NE Configuration for ATM

Connections)
Description
The Uplink Policy parameter specifies the traffic policy ID in a specified direction of an
asynchronous transfer mode (ATM) connection. For user-network interface (UNI) - networknetwork interface (NNI) services, the specified direction is from the UNI side to the pseudo wire
(PW). For UNI - UNI services, the specified direction is from the source UNI port to the
destination UNI port.

Setting the uplink policy of an asynchronous transfer mode (ATM) connection determines the
traffic policy (such as scheduling priority, leaky bucket processing, shaping, and UNI scheduling
priority) in a specified direction of an ATM connection. An incorrect setting of this parameter
may result in packet loss and failed assurance for higher-priority services.
Values
Value Range
Default Value
1-256
An uplink policy determines the traffic parameters and QoS parameters in a specified direction
of an ATM connection. An uplink policy is also used for setting the forwarding priority of QoS
parameters of a network, based on the characteristics of data transmitted on the ATM connection.
For services that require high transmission quality, select an ATM policy that is preferred to
ensure proper data transmission.
Issue 03 (2012-11-30)

1090
OptiX OSN 7500 II/7500/3500/1500


None.
Related Information
None.
A.13.11 Downlink Policy(Per-NE Configuration for ATM

Connections)
Description
The Downlink Policy parameter specifies the traffic policy ID in a specified direction of an
asynchronous transfer mode (ATM) connection. For user-network interface (UNI) - networknetwork interface (NNI) services, the specified direction is from the pseudo wire (PW) to the
UNI side. For UNI-UNI services, the specified direction is from the source UNI port to the
destination UNI port.

Setting the downlink policy of an ATM connection determines the traffic policy (such as
scheduling priority, leaky bucket processing, shaping, and UNI scheduling priority) in a
specified direction of an ATM connection. An incorrect setting of this parameter may result in
packet loss and failed assurance for higher-priority services.
Values
Value Range
Default Value
1-256
None.
A downlink policy determines the traffic parameters and QoS parameters in a specified direction
of an ATM connection. A downlink policy is also used for setting the forwarding priority of
QoS parameters of a network, based on the characteristics of data transmitted on the ATM
connection. For services that require high transmission quality, select an ATM policy that is
preferred to ensure proper data transmission.

None.
Related Information
None.
Issue 03 (2012-11-30)

1091
OptiX OSN 7500 II/7500/3500/1500

A.13.12 CoS Mapping(Per-NE Configuration for CoS Mapping)

Description
The CoS Mapping parameter specifies the priories of packets based on the class of service (CoS)
for mapping between packets and CoS priorities. For different priorities of packets, different
services are available.

Compared with lower-priority packets, higher-priority packets are preferred for transmission in
better service-quality mode.
Values
Value
Default Value
2-8
1(DefaultAtmCosMap)
The ATM service class mapping table specifies mapping between ATM services and CoS
priorities to provide differentiated assurance of service quality. You can adopt the default or
user-defined ATM service class mapping table. You can define a maximum of seven ATM
service class mapping tables.

None.
Related Information
None.
A.13.13 Traffic Service(ATM Policy)

Description
The Traffic Service parameter specifies the sub-type of a service type. That is, multiple traffic
types are available for each type of service. A traffic type specifies the traffic parameters that
can be set, the methods of handling cells whose cell loss priority (CLP) values are 0 and 1, and
the supported functions (such as cell labeling).

A change of QoS parameter settings may result in packet loss.
For example, different types of services have different parameters for the traffic type. For a
constant bit rate (CBR) service, five traffic types can be configured. In practice, if a small number
of burst services whose transmission rate is greater than the peak cell rate (PCR), extra cells are
absolutely discarded for the NoClpNoScr traffic type, and therefore services are transiently
Issue 03 (2012-11-30)

1092
OptiX OSN 7500 II/7500/3500/1500

interrupted. For the other four types of services, a certain amount of buffer size is allocated, and
the burst services whose transmission rates are greater than the PCR are discarded only when
they exceed the buffer size.
Values
For different service types, available traffic types are different.
Service Type
Value Range
Default Value
CBR
NoClpNoScr
NoClpNoScr
ClpNoTaggingNoScr
ClpTaggingNoScr
ClpTransparentNoScr
NoClpNoScrCdvt
rt-VBR
ClpTransparentScr
ClpTransparentScr
NoClpScrCdvt
ClpNoTaggingScrCdvt
ClpTaggingScrCdvt
nrt-VBR
NoClpScr
NoClpScr
ClpNoTaggingScr
ClpTaggingScr
UBR
NoTrafficDescriptor
NoTrafficDescriptor
NoClpNoScr
NoClpTaggingNoScr
NoClpNoScrCdvt
UBR+
atmNoTrafficDescriptorMcr
atmNoTrafficDescriptorMcr
atmNoClpMcr
atmNoClpMcrCdvt
For CBR services, this parameter is set as follows:
Issue 03 (2012-11-30)

1093
OptiX OSN 7500 II/7500/3500/1500

Traffic
Type
CDVT
Supporte
d
Handlin
g Cells
With
CLPs
Being 0
and 1
Different
ly
Cell
Labeling
Supporte
d
PCR
Supporte
d
MBS
Supporte
d
SCR
Supporte
d
NoClpNo
Scr
No
No
No
Yes
No
No
ClpNoTag
gingNoScr
No
Yes
No
Yes
No
No
ClpTaggin
gNoScr
No
Yes
Yes
Yes
No
No
ClpTransp
arentNoSc
r
Yes
No
No
Yes
No
No
NoClpNo
ScrCdvt
Yes
No
No
Yes
No
No
For rt-VBR services, this parameter is set as follows:

Traffic
Type
CDVT
Suppor
ted
Handli
ng Cells
With
CLPs
Being 0
and 1
Differe
ntly
Cell
Labelin
g
Suppor
ted
PCR
Suppor
ted
MCR
Suppor
ted
MBS
Suppor
ted
SCR
Suppor
ted
ClpTran
sparentS
cr
Yes
No
No
Yes
No
Yes
Yes
NoClpSc
rCdvt
Yes
No
No
Yes
No
Yes
Yes
ClpNoT
aggingS
crCdvt
Yes
Yes
No
Yes
No
Yes
Yes
ClpTaggingScr
Cdvt
Yes
Yes
Yes
Yes
No
Yes
Yes
For nrt-VBR services, this parameter is set as follows:

Issue 03 (2012-11-30)

1094
OptiX OSN 7500 II/7500/3500/1500

Traffic
Type
CDVT
Suppor
ted
Handli
ng Cells
With
CLPs
Being 0
and 1
Differe
ntly
Cell
Labelin
g
Suppor
ted
PCR
Suppor
ted
MCR
Suppor
ted
MBS
Suppor
ted
SCR
Suppor
ted
NoClpSc
r
No
No
No
Yes
No
Yes
Yes
ClpNoT
aggingS
cr
No
Yes
No
Yes
No
Yes
Yes
ClpTagg
ingScr
No
Yes
Yes
Yes
No
Yes
Yes
For UBR services, this parameter is set as follows:

Traffic
Type
CDVT
Suppor
ted
Handli
ng Cells
With
CLPs
Being 0
and 1
Differe
ntly
Cell
Labelin
g
Suppor
ted
PCR
Suppor
ted
MCR
Suppor
ted
MBS
Suppor
ted
SCR
Suppor
ted
NoTraffi
cDescrip
tor
No
No
No
No
No
No
No
NoClpN
oScr
No
No
No
Yes
No
No
No
NoClpT
aggingN
oScr
Yes
Yes
Yes
Yes
No
No
No
NoClpN
oScrCdv
t
Yes
No
No
Yes
No
No
No
For UBR+ services, this parameter is set as follows:
Issue 03 (2012-11-30)

1095
OptiX OSN 7500 II/7500/3500/1500

Traffic
Type
CDVT
Suppor
ted
Handli
ng Cells
With
CLPs
Being 0
and 1
Differe
ntly
Cell
Labelin
g
Suppor
ted
PCR
Suppor
ted
MCR
Suppor
ted
MBS
Suppor
ted
SCR
Suppor
ted
atmNoTr
afficDes
criptorM
cr
No
No
No
No
Yes
No
No
atmNoCl
pMcr
No
No
No
Yes
Yes
No
No
atmNoCl
pMcrCd
vt
Yes
Yes
Yes
Yes
Yes
No
No
NOTE
l CDVT: stands for cell delay variation tolerance.

l CLP: stands for cell loss priority in an ATM cell header.
l Cell labeling: sets the CLP of a cell that does not comply with the specified traffic parameters to 1. If
network congestion occurs, a cell whose CLP is 1 is immediately discarded. Therefore, you need to
select a service type based on the network type and service characteristics.

This parameter is available only when Service Type is selected.
Related Information
None.
A.13.14 Clp01Pcr(cell/s)(ATM Policy)

Description
The Clp01Pcr(cell/s) parameter specifies the peak cell rate of a service whose cell loss priority
(CLP) in the asynchronous transfer mode (ATM) cell header is 1 or 0.
In this parameter, Pcr stands for peak cell rate, which is the maximum transmission rate of a cell
flow.

An incorrect setting of this parameter may result in packet loss.
Issue 03 (2012-11-30)

1096
OptiX OSN 7500 II/7500/3500/1500

Values
Value Range
Default Value
Unit
90-149078
None.
Cell/s
The parameter value must be not larger than the physical bandwidth of an ATM port or an inverse
multiplexing for ATM (IMA) group.
For example, the bandwidth (based on the number of ATM cells) of one E1 in an IAM group is
derived from the formula: (30 8 8000) / (53 8) ((M-1) / M) x (2048 / 2049).
l
The expression 30 8 8000 represents the bandwidth of an E1 service in an IMA group.

The value 30 represents 30 of the 32 timeslots in an E1 (if 31 timeslots are used, change
the value from 30 to 31.)
The expression 538 represents the number of bits in an ATM cell.
The letter M indicates the frame length of an IMA group. According to the MA protocol,
an IMA control protocol (ICP) cell is inserted to every M-1 user cells. An ICP cell, which
is not a user cell, is used for transmission of IMA protocol information. In practice, the ICP
cell needs to be removed from the available bandwidth. The expression 2048 / 2049
indicates that one more ICP cell needs to be inserted to every 2048 cells.
If the frame length (M) of an IMA group is 128, the maximum number of cells derived
from the preceding formula is 4490 (rounded off to an integer). Therefore, the Clp0Pcr
value specified for an IMA group in which only one E1 service is available needs to be not
more than 4490.
If the IMA protocol is disabled for the E1 service, the bandwidth is derived from the
formula: (30 8 8000) / (53 8).

The value 30 represents 30 of the 32 timeslots in an E1 service in an IMA group. (If only
10 timeslots are used, change the value from 30 to 10.)
If the transmission rate at a port of AFO1 is STM-1, the bandwidth (based on the number
of ATM cells) is 149760 (rounded off to an integer).

None.
Related Information
According to ATM Forum, ATM traffic is currently controlled by two-level token buckets.
Generally, a level-1 token bucket limits the PCR, and a level-2 token bucket limits the sustainable
cell rate (SCR). The two-level token buckets adopt the GCRA algorithm to control the traffic.
Issue 03 (2012-11-30)

1097
OptiX OSN 7500 II/7500/3500/1500

Figure A-7 Dual token bucket model

Parameters for a level-1
leaky bucket:
PCR
CDVT
CLP1
CLP0
SCR0
CLP0+1
CLP0+1
CLP0
Conforming
cells
Parameters for a
level-2 leaky bucket:
SCR
BT+CDVT
Non-conforming cells
Figure A-8 Structure of the ATM UNI cell header in the dual token bucket model
GFC (4)
VPI (4)
VPI (4)
VCI (4)
VCI (8)
VCI (4)
PT (3)
CLP (1)
HEC (8)
A.13.15 Clp01Scr(cell/s)(ATM Policy)

Description
The Clp01Pcr(cell/s) parameter specifies the substainable cell rate of a service whose cell loss
priority (CLP) in the asynchronous transfer mode (ATM) cell header is 1 or 0.
In this parameter, Scr stands for sustainable cell rate, which is an average cell transmission rate
for a long time.
Issue 03 (2012-11-30)

1098
OptiX OSN 7500 II/7500/3500/1500


Values
Value Range
Default Value
Unit
90-149078
None.
Cell/s
l

The value 30 represents 30 of the 32 timeslots in an E1 service in an IMA group (if 31
timeslots are used, change the value from 30 to 31.)
The expression 53 8 represents the number of bits in an ATM cell.
The letter M indicates the frame length of an IMA group. According to the IMA protocol,
an ICP cell is inserted to every M-1 user cells. An IMA control protocol (ICP) cell, which
more than 4490.
formula: (30 8 8000) / (53 8).


The parameter value must be not larger than the maximum cell transmission rate.
Related Information
Generally, a level-1 token bucket limits the peak cell rate (PCR), and a level-2 token bucket
limits the SCR. The two-level token buckets adopt the GCRA algorithm to control the traffic.
Issue 03 (2012-11-30)

1099
OptiX OSN 7500 II/7500/3500/1500


leaky bucket:
PCR
CDVT
CLP1
CLP0
SCR0
CLP0+1
CLP0+1
CLP0
Conforming
cells
Parameters for a
SCR
BT+CDVT
GFC (4)
VPI (4)
VPI (4)
VCI (4)
VCI (8)
VCI (4)
PT (3)
CLP (1)
HEC (8)
A.13.16 Clp0Pcr(cell/s)(ATM Policy)

Description
The Clp0Pcr(cell/s) parameter specifies the peak cell rate of a service whose cell loss priority
(CLP) in the asynchronous transfer mode (ATM) cell header is 0.
In this parameter, Pcr stands for peak cell rate, which is the maximum transmission rate of a cell
flow.
Issue 03 (2012-11-30)

1100
OptiX OSN 7500 II/7500/3500/1500


Values
Value Range
Default Value
Unit
90-149078
None.
Cell/s
l

more than 4490.
formula: (30 8 8000) / (53 8).


None.
Related Information
Generally, a level-1 token bucket limits the PCR, and a level-2 token bucket limits the sustainable
cell rate (SCR). The two-level token buckets adopt the GCRA algorithm to control the traffic.
Issue 03 (2012-11-30)

1101
OptiX OSN 7500 II/7500/3500/1500


leaky bucket:
PCR
CDVT
CLP1
CLP0
SCR0
CLP0+1
CLP0+1
CLP0
Conforming
cells
Parameters for a
SCR
BT+CDVT
GFC (4)
VPI (4)
VPI (4)
VCI (4)
VCI (8)
VCI (4)
PT (3)
CLP (1)
HEC (8)
A.13.17 Clp0Scr(cell/s)(ATM Policy)

Description
The Clp0Scr(cell/s) parameter specifies the substainable cell rate of a service whose cell loss
priority (CLP) in the asynchronous transfer mode (ATM) cell header is 0.
In this parameter, Scr stands for sustainable cell rate, which is an average cell transmission rate
for a long time.
Issue 03 (2012-11-30)

1102
OptiX OSN 7500 II/7500/3500/1500


Values
Value Range
Default Value
Unit
90-149078
None.
Cell/s
l

The value 30 represents 30 of the 32 timeslots in an E1 (if 31 timeslots are used, change
the value from 30 to 31.)
value specified for an MA group in which only one E1 service is available needs to be not
more than 4490.
formula: (30 8 8000) / (53 8).


This parameter value must be not larger than the maximum cell transmission rate.
Related Information
limits the SCR. The two-level token buckets adopt the GCRA algorithm to control the traffic.
Issue 03 (2012-11-30)

1103
OptiX OSN 7500 II/7500/3500/1500


leaky bucket:
PCR
CDVT
CLP1
CLP0
SCR0
CLP0+1
CLP0+1
CLP0
Conforming
cells
Parameters for a
SCR
BT+CDVT
GFC (4)
VPI (4)
VPI (4)
VCI (4)
VCI (8)
VCI (4)
PT (3)
CLP (1)
HEC (8)
A.13.18 Clp01Mcr(cell/s)(ATM Policy)

Description
The Clp01Mcr(cell/s) parameter specifies the minimum transmission rate of cells whose cell
loss priority (CLP) in the asynchronous transfer mode (ATM) cell header is 1 or 0.
In this parameter, Mcr stands for the minimum cell rate, which is the minimum transmission
rate of a cell flow.
Issue 03 (2012-11-30)

1104
OptiX OSN 7500 II/7500/3500/1500


Values
Value Range
Default Value
Unit
566-32664
None.
Cell/s
l

an ICP cell is inserted to every M-1 user cells. An ICP cell, which is not a user cell, is used
for transmission of IMA protocol information. In practice, the ICP cell needs to be removed
from the available bandwidth. The expression 2048 / 2049 indicates that one more ICP cell
needs to be inserted to every 2048 cells.
more than 4490.
formula: (30 8 8000) / (53 8).


The parameter value must be not larger than the maximum transmission rate of a cell flow.
Related Information
limits the sustainable cell rate (SCR). The two-level token buckets adopt the GCRA algorithm
to control the traffic.
Issue 03 (2012-11-30)

1105
OptiX OSN 7500 II/7500/3500/1500


leaky bucket:
PCR
CDVT
CLP1
CLP0
SCR0
CLP0+1
CLP0+1
CLP0
Conforming
cells
Parameters for a
SCR
BT+CDVT
GFC (4)
VPI (4)
VPI (4)
VCI (4)
VCI (8)
VCI (4)
PT (3)
CLP (1)
HEC (8)
A.13.19 Max.Cell Burst Size(cell)(ATM Policy)

Description
The Max.Cell Burst Size(cell) parameter specifies the maximum number of cells that are
continuously transmitted on an asynchronous transfer mode (ATM) path of a variable bit rate
(VBR) service at a rate of r (SCR < r <PCR).
In this parameter, MBS stands for the maximum burst size.
Issue 03 (2012-11-30)

1106
OptiX OSN 7500 II/7500/3500/1500


None.
Values
Value Range
Default Value
Unit
2-200000
None.
cell
The greater the parameter value, the deeper the level-2 token bucket on the ATM path, and the
better performance the service for burst cells. Therefore, if conditions are allowed, you can set
the maximum burst size to a greater value.

None.
Related Information
Token bucket algorithm: The equipment constantly monitors the rate of burst cells. If the rate
of burst cells exceeds the specified value (1/I), the equipment computes and accumulates the
offset value between the theoretical arrival time of cells and the actual arrival time of cells. If
the accumulated offset value is within the specified value (1/I), the equipment considers that the
cells are conforming cells. If the accumulated offset value exceeds the specified value (L), the
equipment considers that the cells are non-conforming cells, which are handled according to the
methods specified in the contract. That is, non-conforming cells are discarded (based on the CLP
values or regardless of the CLP values) or added with tagging labels.
l
For a level-1 token bucket, the value I is 1/PCR, and the value L is CDVT. If the rate of
burst cells exceeds the specified PCR value, the equipment computes and accumulates the
offset value between the theoretical arrival time of cells and the actual arrival time of cells.
If the accumulated offset value exceeds the specified value L (the CDTV value for a level-1
token bucket), the cells are discarded.
For a level-2 token bucket, the value I is 1/SCR, and the value L is derived from the formula:
BT + CDVT. The equipment performs the same operations as those for a level-1 token
bucket, except that the parameters are different. The value BT is derived from the formula:
(MBS - 1)(1/SCR - 1/PCR).
A.13.20 Cell Delay Variation Tolerance(0.1us)(ATM Policy)

Description
The Cell Delay Variation Tolerance(0.1us) parameter specifies the burst cell tolerance of an
asynchronous transfer mode (ATM) connection.
Issue 03 (2012-11-30)

1107
OptiX OSN 7500 II/7500/3500/1500

In this parameter, CDVT stands for cell delay variation tolerance.

If the actual arrival time of a cell is later than the theoretical arrival time, the cell is considered
as a burst cell. The number of burst cells is measured according to the offset value between the
actual arrival time and the theoretical arrival time of cells. If the total number of consecutive
burst cells exceeds the CDVT value for a token bucket of the service, extra cells are discarded.
Values
Value Range
Default Value
Unit
7 to 13300000
None.
0.1us
The greater the parameter value, the better performance the service for burst cells. If conditions
are allowed, you can set CDVT to a large value to minimize packet loss.

None.
Related Information
Token bucket algorithm: The equipment constantly monitors the rate of burst cells. If the rate
of burst cells exceeds the specified value (1/I), the equipment computes and accumulates the
offset value between the theoretical arrival time of cells and the actual arrival time of cells. If
the accumulated offset value is within the specified value (1/I), the equipment considers that the
cells are conforming cells. If the accumulated offset value exceeds the specified value (L), the
equipment considers that the cells are non-conforming cells, which are handled according to the
methods specified in the contract. That is, non-conforming cells are discarded (based on the cell
loss priority (CLP) values or regardless of the CLP values) or added with tagging labels.
l
For a level-1 token bucket, the value I is 1/PCR, and the value L is CDVT. If the rate of
burst cells exceeds the specified PCR value, the equipment computes and accumulates the
offset value between the theoretical arrival time of cells and the actual arrival time of cells.
If the accumulated offset value exceeds the specified value L (the CDTV value for a level-1
token bucket), the cells are discarded.
For a level-2 token bucket, the value I is 1/SCR, and the value L is derived from the formula:
BT + CDVT. The equipment performs the same operations as those for a level-1 token
bucket, except that the parameters are different. The value BT is derived from the formula:
(MBS - 1)(1/SCR - 1/PCR).
Issue 03 (2012-11-30)

1108
OptiX OSN 7500 II/7500/3500/1500

A.13.21 UPC/NPC(ATM Policy)

Description
The UPC/NPC parameter specifies the user-network interface (UNI) traffic parameters based
on usage parameter control (UPC) and network parameter control (NPC).

None.
Values
Value Range
Default Value
Disabled, Enabled
Disabled
The traffic monitoring function is classified into UPC and NPC by interface position.
The UPC function is available for UNI-NNI interfaces, whereas the NPC function is available
for NNI-NNI interfaces. The UPC and NPC functions are similar and used for processing nonconforming packets during a communication (for example, the number of burst packets exceeds
the specified value).
The UPC and NPC functions process packets in three modes: transmitting conforming packets;
labeling non-conforming packets (setting the CLP field in the packets to the value 1) and
lowering their forwarding priorities; and discarding non-conforming packets immediately.

If the UPC and NPC functions are disabled, that is, if the token bucket protocol is disabled, the
flow control function does not take effect for services.
Related Information
According to asynchronous transfer mode (ATM) Forum, ATM traffic is currently controlled
by two-level token buckets. Generally, a level-1 token bucket limits the peak cell rate ( PCR),
and a level-2 token bucket limits the sustainable cell rate (SCR). The two-level token buckets
adopt the GCRA algorithm to control the traffic.
Issue 03 (2012-11-30)

1109
OptiX OSN 7500 II/7500/3500/1500


leaky bucket:
PCR
CDVT
CLP1
CLP0
SCR0
CLP0+1
CLP0+1
CLP0
Conforming
cells
Parameters for a
SCR
BT+CDVT
A.14 ATM OAM Associated Parameters (Packet Mode)

This topic describes the parameters for configuring ATM OAM.
A.14.1 Connection Direction

Description
The Connection Direction parameter specifies whether to enable the asynchronous transfer
mode (ATM) operation, administration and maintenance (OAM) function at the source or sink
end of a connection.

Values
Value Range
Default Value
Source, Sink
Source
Select a proper direction of the connection as required at the end where ATM OAM cells are
identified and processed.
Issue 03 (2012-11-30)

1110
OptiX OSN 7500 II/7500/3500/1500


None.
Related Information
An ATM connection has a source end and a sink end. When setting the segment point and
endpoint attributes, specify the direction of the ATM connection. That is, specify whether to set
the segment and end attributes for the source or sink end of the ATM connection.
Figure A-18 Setting a segment point
A segment
point is set.
Connection ID = 1
Source end
Sink end
NE
After you specify the segment and end points in a direction of an ATM connection for an NE,
the NE can identify and process ATM OAM cells in the receive direction of the port where the
segment and end points are specified. For example, as shown in Figure A-18, if a segment point
is specified for the source end of connection 1, the NE can identify and process ATM OAM cells
transmitted between two segment points in the receive direction at the source end.
A.14.2 Segment and End Attribute

Description
The Segment and End Attribute parameter specifies the type of an operation, administration
and maintenance (OAM) maintenance point. For different segment and end attributes, different
ranges of asynchronous transfer mode (ATM) OAM cells are processed.

Values
Value Range
Default Value
Non segment and Endpoint, Segment point,

Endpoint, Segment and Endpoint
Non segment and Endpoint

Issue 03 (2012-11-30)

1111
OptiX OSN 7500 II/7500/3500/1500

Value
Description
Non segment and

Endpoint
Indicates that ATM OAM cells are not terminated.
Endpoint
Identifies, processes, and terminates the ATM OAM cells whose

OAM maintenance points are set to the segment attribute.
Segment point
Identifies, processes, and terminates the ATM OAM cells whose

OAM maintenance points are set to the end attribute, but identifies
and discards the ATM OAM cells whose OAM maintenance points
are set to the segment attribute.
Segment and
Endpoint
Identifies, processes, and terminates all ATM OAM cells.
According to different OAM maintenance segments, as shown in Figure A-19, set the segment
and end attributes properly.
Figure A-19 Schematic diagram of a maintenance segment
1
End
2
Seg
3
Inner
4
Inner
5
Seg + End
Segment
User 1
End to end
User 2
1.
When enabling the ATM OAM function for a maintenance segment, set the endpoint
attribute for the boundary of the maintenance segment. For example, as shown in Figure
A-19, separately set the endpoint attribute for points 1 and 2 of the maintenance segment
of user 1.
2.
You can divide a maintenance segment into different maintenance sub-segments to

facilitate management. When dividing a maintenance area into different maintenance subsegments, set the segment attribute for both ends of a maintenance sub-segment. For
example, as shown in Figure A-19, if the sub-segment between points 2 and 5 is considered
as a maintenance sub-segment, separately set the segment point attribute for points 2 and
5 of the maintenance sub-segment.
Issue 03 (2012-11-30)

1112
OptiX OSN 7500 II/7500/3500/1500

3.
When working as an end point and a segment point at the same time, a point needs to be a
segment-end point, such as point 5 shown in Figure A-19.

None.
Related Information
An ATM connection has a source end and a sink end. When setting the segment point and
endpoint attributes, specify the direction of the ATM connection. That is, specify whether to set
the segment and end attributes for the source or sink end of the ATM connection.
Figure A-20 Setting a segment point
A segment
point is set.
Connection ID = 1
Source end
Sink end
NE
After you specify the segment and end points in a direction of an ATM connection for an NE,
the NE can identify and process ATM OAM cells in the receive direction of the port where the
segment and end points are specified. For example, as shown in Figure A-20, if a segment point
is specified for the source end of connection 1, the NE can identify and process ATM OAM cells
transmitted between two segment points in the incoming direction at the source end.
A.14.3 Country Code(Hexadecimal Code)

Description
The Country Code(Hexadecimal Code) parameter specifies the values of bytes 2 and 3 in the
loopback location identifier (LLID).

Values
Issue 03 (2012-11-30)
Value Range
Default Value
[2BYTE]00 00-ff ff
[2BYTE]00 00

1113
OptiX OSN 7500 II/7500/3500/1500

The binary coded decimal (BCD) is used for a country code. For example, 0x0086 is used for
China, 0x0001 for U.S.A., and 0x0044 for U. K.
The default value is 0x0000, which is recommended.

None.
Related Information
According to ITU-T I.610, an LLID is specified in multiple coding methods and the first byte
of the LLID is used to identify the coding method.
In the GUI interface of a network management system, an LLID is specified in coding method
2 (the first byte is 0x01) described in ITU-T I.610, and a window is available for setting the other
15 bytes.
The sequence and meaning of each filed are described as follows:
2-byte country code (the BCD is defaulted to be 0x0086) + 2-byte network code (the BCD is
defaulted to 0x0000) + 11-byte NE code (the first four bytes are defaulted to be an NE ID, and
the last seven bytes are defaulted to be 0s)
CAUTION
After being specified, an NE code that is different from an NE ID (that is, the first four bytes
are not the same as an NE ID, and the other seven bytes are not 0s) remains unchanged regardless
of the NE ID.
A.14.4 Network Code(Hexadecimal Code)

Description
The Network Code(Hexadecimal Code) parameter specifies the values of bytes 4 and 5 in the

Values
Issue 03 (2012-11-30)
Value Range
Default Value
[2BYTE]00 00-ff ff
[2BYTE]00 00

1114
OptiX OSN 7500 II/7500/3500/1500

The binary coded decimal (BCD) is used for a network code. You can set a network code as
required within the specified value range.
The default network code is 0x0000. It is recommended that you set the network code to 0x0000.

None.
Related Information
15 bytes.
CAUTION
of the NE ID.
A.14.5 NE Code(Hexadecimal Code)

Description
The NE Code(Hexadecimal Code) parameter specifies the values of bytes 6 through 16 in the

Values
Issue 03 (2012-11-30)
Value Range
Default Value
[11BYTE]00 00 00 00 00 00 00 00 00 00 00ff ff ff ff ff ff ff ff ff ff ff
4-byte NE ID + 7-byte 0s

1115
OptiX OSN 7500 II/7500/3500/1500

If an NE on a network has a unique LLID, set the values of the 11 bytes as required.
The first four bytes are defaulted to be a network ID, and the last seven bytes are 0s. It is
recommended that you set the network code to the default value.

None.
Related Information
15 bytes.
CAUTION
of the NE ID.
A.15 ATM/IMA Associated Parameters (TDM Mode)

This topic describes the parameters for configuring the ATM/IMA function.
A.15.1 VCTRUNK Port (ATM Bound Path Management)

Description
The VCTRUNK Port (ATM Bound Path Management) parameter identifies the ATM ports.
One VCTRUNK can be bound with multiple SDH timeslots of the same level.

Values
For N1ADQ1/N1ADL4 boards:
Issue 03 (2012-11-30)

1116
OptiX OSN 7500 II/7500/3500/1500

Valid Values
Default Value
VCTRUNK1-VCTRUNK16
UNI

Value
Description
VCTRUNK1-4
Indicates the VCTRUNKs that can be bound with VC4-xv

only.
VCTRUNK5-16
Indicates the VCTRUNKs that can be bound with VC3-xv or

VC4-xv.
For N1IDQ1/N1IDL4 boards:

Valid Values
Default Value
VCTRUNK1-VCTRUNK70
UNI

Value
Description
VCTRUNK1-VCTRUNK66

or VC4-xv.
VCTRUNK67VCTRUNK70

only.
For N1IDQ1A and N1IDL4A boards:

Valid Values
Default Value
VCTRUNK1-VCTRUNK98
UNI
Issue 03 (2012-11-30)
Value
Description
VCTRUNK1-VCTRUNK94
Indicates the VCTRUNKs that can be bound with the VC12xv or VC4-xv.

1117
OptiX OSN 7500 II/7500/3500/1500

Value
Description
VCTRUNK95VCTRUNK98
Indicates the VCTRUNKs that can be bound with the VC4xv only.
Principles of binding internal ports (VCTRUNK):
For N1ADQ1 and N1ADL4 boards:
Port Number
Binding Level
Path Number
VCTRUNK1-4
VC4-xv
1-4
VCTRUNK5-16
VC4-xv
5-8
VCTRUNK5-16
VC3-xv
13-24
Port Number
Binding Level
Path Number
VCTRUNK1-66
VC4-xv
1-4
VCTRUNK1-66
VC12-xv
1-63
VCTRUNK67-70
VC4-xv
5-8

Port Number
Binding Level
Path Number
VCTRUNK1-94
VC4-xv
1-4
VCTRUNK1-94
VC12-xv
1-189
VCTRUNK95-98
VC4-xv
5-8
NOTE
For the IDQ1 or IDL4, if the binding level is VC12-xv, 16 ports at the VC-12 level can be bound. The path
number is allocated from 1 to 63 on the NMS.
For the IDQ1A or IDL4A, if the binding level is VC12-xv, 93 ports at the VC-12 level can be bound. The
path number is allocated from 1 to 189 on the NMS.

None.
Issue 03 (2012-11-30)

1118
OptiX OSN 7500 II/7500/3500/1500

A.15.2 Level (ATM Bound Path Management)

Description
The Level (ATM Bound Path Management) parameter specifies the VC level that can be
bound to VCTRUNK ports.
For N1ADQ1/N1ADL4 boards, the level can be VC4-xv or VC3-xv; for N1IDQ1/N1IDL4
boards, the level can be VC4-xv or VC12-xv.

If this parameter is set improperly, the service may fail.
Values
For N1ADQ1/N1ADL4 boards:
Valid Value
Default Value
VC3-xv, VC4-xv
VC3-xv

Valid Value
Default Value
l VC12-xv
VC12-xv
l VC4-xv
For N1IDQ1A/N1IDL4A boards:

Valid Value
Default Value
VC12-xv, VC4-xv
VC12-xv
Principles of binding internal ports (VCTRUNK):
Issue 03 (2012-11-30)
Port Number
Binding Level
Path Number
VCTRUNK1-4
VC4-xv
1-4
VCTRUNK5-16
VC4-xv
5-8

1119
OptiX OSN 7500 II/7500/3500/1500

Port Number
Binding Level
Path Number
VCTRUNK5-16
VC3-xv
13-24
Port Number
Binding Level
Path Number
VCTRUNK1-66
VC4-xv
1-4
VCTRUNK1-66
VC12-xv
1-63
VCTRUNK67-70
VC4-xv
5-8
For N1IDQ1A/N1IDL4A boards:

Port Number
Binding Level
Path Number
VCTRUNK1-94
VC4-xv
1-4
VCTRUNK1-94
VC12-xv
1-189
VCTRUNK95-98
VC4-xv
5-8

None.
A.15.3 Direction (ATM Bound Path Management)

Description
The Direction (ATM Bound Path Management) parameter specifies the direction of a
connection to be set up at a VCTRUNK port. The direction can beUplink, Downlink and
Bidirectional.

If this parameter is set improperly, only unidirectional communication is achieved in a
bidirectional service.
Values
Issue 03 (2012-11-30)
Valid Values
Default Value
Bidirectional, Uplink, Downlink
Bidirectional

1120
OptiX OSN 7500 II/7500/3500/1500


Value
Description
Uplink
The uplink ATM connection of the port is available. That is,

the ATM connection is from the optical interface side to the
cross-connection side.
Downlink
The downlink ATM connection of the port is available. That

is, the ATM connection is from the cross-connection side to
the optical interface side.
Bidirectional
The ATM connection of the port is available bidirectionally.
An end-to-end connection is bound with VCTRUNKs in both directions, because the end-toend ATM connection is bidirectional.
A multicast connection can be bound with a VCTRUNK in one direction, because the multicast
ATM connection is unidirectional.

None.
A.15.4 Port (ATM Port Management)

Description
The Port (ATM Port Management) parameter specifies identities of the external and internal
ports on the ATM or IMA board.

Values
Value Range
Default Value
l External ports 1-4
UNI
l Internal ports 1-16

Issue 03 (2012-11-30)

1121
OptiX OSN 7500 II/7500/3500/1500

Value
Description
External ports 1-4
Indicates the external ports on the N1ADQ1 or N1ADL4

board, which are numbered from 1 to 4 in the top down order.
Note that only one external port is available on the N1ADL4
board.
Internal ports 1-4
Indicates the VCTRUNKs that can be bound only with VC4xv.
Internal ports 5-16
Indicates the VCTRUNKs that can be bound with VC3-xv or

VC4-xv.
For N1IDQ1 and N1IDL4 boards:

Value Range
Default Value
UNI

Value
Description
External ports 1-4
Indicates the external ports on the N1IDQ1 or N1IDL4 board,

which are numbered from 1 to 4 in the top down order. Note
only one external port is available on the N1IDL4 board.
Internal ports 1-66

or VC4-xv.
Internal ports 67-70
Indicates the VCTRUNKs that can be bound only with VC4xv.

Value Range
Default Value
UNI
Issue 03 (2012-11-30)

1122
OptiX OSN 7500 II/7500/3500/1500

Value
Description
External ports 1-4
Indicates the external ports on the N1IDQ1A or N1IDL4A

board, which are numbered from 1 to 4 in the top down order.
Note that only one external port is available on the N1IDL4A
board.
Internal ports 1-94
Indicates the VCTRUNKs that can be bound with the VC12xv or VC4-xv.
Indicates the VCTRUNKs that can be bound only with the

VC4-xv.
Principles of binding internal ports (VCTRUNKs):
Port Number
Binding Level
Path Number
Internal ports 1-4
VC4-xv
1-4
Internal ports 5-16
VC4-xv
5-8
Internal ports 5-16
VC3-xv
13-24
For N1IDQ1 and N1IDL4 boards:

Port Number
Binding Level
Path Number
Internal ports 1-66
VC4-xv
1-4
Internal ports 1-66
VC12-xv
1-63
VC4-xv
5-8
Issue 03 (2012-11-30)
Port Number
Binding Level
Path Number
Internal ports 1-94
VC4-xv
1-4
Internal ports 1-94
VC12-xv
1-189
VC4-xv
5-8

1123
OptiX OSN 7500 II/7500/3500/1500


None.
A.15.5 Port Type (ATM Port Management)

Description
The Port Type (ATM Port Management) parameter specifies ATM ports, which are classified
into UNI and NNI ATM ports. The maximum number of VPI bits in a cell header for a UNI port
is different from that for a NNI port.

Values
Valid Value
Default Value
UNI, NNI
UNI

Value
Description
UNI
The maximum number of VPI bits is 8.
NNI
The maximum number of VPI bits is 12.
If the number of VPIs received at a port is large (for example, greater than 255), select NNI to
increase the number of VPI bits. As a result, more VPIs are available.

None.
A.15.6 Max. VPI Bits

Description
The Max. VPI Bits parameter specifies the maximum number of available VPIs at a port.
Issue 03 (2012-11-30)

1124
OptiX OSN 7500 II/7500/3500/1500


The number of VPI bits determines the number of available VPIs. It shows the number of
available VPIs at a port. This number can be increased or decreased, depending on the VPIs
required at the port.
Values
Value Range
Default Value
Unit
UNI port: 1-8
bits
NNI port: 1-12
NOTE
The IDQ1A and IDL4A boards do not support this parameter.
Max. VPI Bits refers to the number of bits in the valid VPI fields in a cell header that a port
supports. The VPI value and the value of Max. VPI Bits have the following relationship: VPI
= 2Bits-1.

This parameter is invalid if a service connection is set up at the port.
A.15.7 Max. VCI Bits

Description
The Max. VCI Bits parameter specifies the maximum number of available virtual channel
identifiers (VCIs) at a port.

The number of VCI bits specifies the number of available VCIs. It shows the number of available
VCIs at a port. This number can be increased or decreased, depending on the VCIs required at
the port.
Values
Value Range
Default Value
Unit
6-16
bits
NOTE
The IDQ1A and IDL4A boards do not support this parameter.
Issue 03 (2012-11-30)

1125
OptiX OSN 7500 II/7500/3500/1500

Max. VCI Bits refers to the number of bits in the valid VCI fields in the cell header that a port
supports. The VCI value and the value of Max. VCI Bits have the following relationship: VCI
= 2Bits-1.

A.15.8 Max. VPC

Description
The Max. VPC parameter specifies the maximum number of permanent virtual paths (PVPs)
that can be set up at a port.

Values
Value Range
Default Value
Unit
0-4096
224
Piece
NOTE
The N1IDQ1A and N1IDL4A boards do not support this parameter.
None.

None.
A.15.9 Max. VCC

Description
The Max. VCC parameter specifies the maximum number of permanent virtual connections
(PVCs) that can be set up at a port.

Issue 03 (2012-11-30)

1126
OptiX OSN 7500 II/7500/3500/1500

Values
Value Range
Default Value
Unit
1-8192
3072
Piece
NOTE
None.

None.
A.15.10 VPC Configured

Description
The VPC Configured parameter specifies the number of permanent virtual paths (PVPs) that
have been set up at a port.

Values
Board Name
Value Range
Default Value
Unit
N1IDQ1A,
N1IDL4A
0-4000
Number
N1ADQ1, N1ADL4,
N1IDQ1, N1IDL4
0-4096
Number
For example, two PVPs have been set up and activated at internal port 1. In this case, the number
of configured VPCs is 2.
None.

None.
Issue 03 (2012-11-30)

1127
OptiX OSN 7500 II/7500/3500/1500

A.15.11 VCC Configured

Description
The VCC Configured parameter specifies the number of PVCs that have been set up at a port.

Values
Value Range
Default Value
Unit
0-8192
Number
For example, two PVCs have been set up and activated at internal port 1. In this case, the number
of configured VCCs is 2.
None.

None.
A.15.12 Number of VPI that Supports VCC

Description
The Number of VPI that Supports VCC parameter specifies the number of VPIs supporting
PVCs at a port. That is, only the VPIs specified by this parameter can be used to set up VC
connections, regardless of the number of VPI bits. Other VPIs can be used to set up only VP
connections.

Because this parameter specifies the number of VPIs that can be used to set up VC connections,
the system resource allocation is affected. Therefore, set this parameter based on the actual
service configurations.
Values
Issue 03 (2012-11-30)
Value Range
Default Value
Unit
32
Number

1128
OptiX OSN 7500 II/7500/3500/1500

NOTE
Set this parameter based on the number of VCIs required for each VPI at each port. For example,
if 50 PVCs need to be set up at a port and the VPI is different for each PVC, 50 VPIs are required
to differentiate the PVCs. In this case, set the number of VPIs that support VC label switching
to 50.

The value of the Number of VPI that Supports VCC parameter must be smaller than the
number of VPIs derived from the MAX. VPI Bits parameter.
A.15.13 UPC/NPC Enabled/Disabled

Description
The UPC/NPC Enabled/Disabled parameter specifies user parameter control or network
parameter control. It indicates whether to enable the flow control function, namely, whether the
flow parameters for the connection are valid.

Other service connections at the same port may be affected.
For example, a VC-4 port (total bandwidth of 353207 cells/s) involves two connections: variable
bit rate (VBR) service and unspecified bit rate (UBR) service. The peak cell rate (PCR) of the
VBR service is set to 100000 cells/s, and the UPC/NPC function is enabled. If the transmission
rate of the UBR service connection is 253207 cells/s, and if the UPC/NPC function is enabled,
the VBR service flow does not exceed the rate of 100000 cells/s. If the VBR service flow exceeds
the rate of 100000 cells/s, the excessive cells are discarded. If the UPC/NPC function is disabled,
the VBR service is not limited. In this case, the VBR service flow can exceed the rate of 100000
cells/s. The excessive cells preempt the bandwidth of the UBR service, because the VBR service
is of higher priority. Consequently, the UBR service cells are discarded.
Values
Valid Values
Default Value
Enabled, Disabled
Enabled
Issue 03 (2012-11-30)

1129
OptiX OSN 7500 II/7500/3500/1500

Value
Description
Enabled
The flow parameters are valid. In this case, the system

controls the flow based on the flow parameters, for example,
discarding cells or labeling cells.
Disabled
The flow parameters are invalid, except for PCR of the CBR
service. In this case, the system provides the guaranteed
bandwidth. Moreover, the system grooms the unguaranteed
services based on the service priority.
The value is not limited. Instead, it is selected according to the networking environment and the
application scenario. Generally, select Enabled for important voice services and signaling
services if the flow needs to be strictly controlled. Select Disabled for connectionless services
if service burst and grooming are allowed.
A.15.14 Positive UPC/NPC(ATM Service Management)

Description
The Positive UPC/NPC parameter specifies whether the flow control function is enabled and
whether the flow parameters used for setting up a connection function. UPC and NPC stand for
user parameter control/network parameter control respectively.

The setting of this parameter for one service connection affects other service connections on the
same port. For example, a VC-4 port (with a total bandwidth of 353207 cells/s) has two
connections, namely, a VBR service and a UBR service. The PCR of the VBR service is set to
100000 cells/s, and the UPC/NPC function is enabled. If the transmission rate of the UBR service
is 253207 cells/s, the rate of the VBR service traffic cannot exceed 100000 cells/s because the
UPC/NPC function is enabled. If the rate of the VBR service exceeds 100000 cells/s, the
excessive cells are discarded. If the UPC/NPC function is disabled, the VBR service is not
limited. In this case, the rate of the VBR service can exceed 100000 cells/s. The excessive cells
preempt the bandwidth of the UBR service because the VBR service is of a higher priority.
Consequently, the UBR service cells are discarded.
Values
Valid Value
Default Value
Enable, Disable
Enable
Issue 03 (2012-11-30)

1130
OptiX OSN 7500 II/7500/3500/1500

Value
Description
Enable
Indicates that the flow parameters function. In this case, the

system controls the flow based on the flow parameters. For
example, the system discards cells or labels cells.
Disable
Indicates that the flow parameters does not function. In this

case, the system provides the guaranteed bandwidth and
schedules the unguaranteed services based on the service
priority.
Select a proper value according to the networking environment and application scenario.
Generally, set this parameter to Enable for services that require strict flow control. Set this
parameter to Disable for services that allow service burst and grooming.
A.15.15 ID (ATM Traffic Management)

Description
The ID (ATM Traffic Management) parameter specifies a traffic ID. An ID is allocated for
each type of traffic.

The value of this parameter is automatically allocated on the U2000. When an ATM connection
is configured, services may be discarded or interrupted if the services are allocated with an
incorrect ID. The ID is service-specific. For example, when wireless base stations are
interconnected, a voice service from the opposite station is of the CBR type. If the UBR service
type is selected to set up the connection, some calls may be dropped in case of heavy traffic.
The bandwidth is guaranteed for CBR services, but not for UBR services.
Values
Value
Range
Default
Value
1-2048
Description
This parameter is related to the number of created connections.
When a connection is created, a traffic is added to the traffic list.
To set up a connection, you can either select a created connection
from the ATM traffic table, or input the traffic ID for the created
connection.
Select a traffic type required for the connection from the ATM traffic table.
Issue 03 (2012-11-30)

1131
OptiX OSN 7500 II/7500/3500/1500


This parameter is valid only when an ATM traffic is created.
A.15.16 Traffic Type (ATM Traffic Management)

Description
The Traffic Type (ATM Traffic Management) parameter specifies sub-types of a service type.
Each service has multiple traffic types. The traffic type specifies the traffic parameters that can
be set, for example, processing the cells whose priority is 0 or 1 in different ways, and whether
to enable the labeling function.

If this parameter is incorrectly set, some packets may be discarded.
Traffic parameters depend on the traffic type. Use the CBR service as an example. The CBR
service has two traffic types: NoClpNoScr and NoClpNoScrCdvt. For the NoClpNoScr CBR
service, only PCR can be set. For the NoClpNoScrCdvt CBR service, both PCR and CDTV can
be set. In practical applications, if there is a small amount of service at a rate higher than the
PCR, all excessive cells are discarded for the NoClpNoScr CBR service. Consequently, the
service is transiently interrupted. For the NoClpNoScrCdvt CBR service, a buffer space is
allocated. When a transient burst event occurs, the cells are not discarded.
Values
The following table lists the available traffic types for each service type.
Service Type
Traffic Type
Default Value
CBR
l NoClpNoScr
NoClpNoScr
l ClpNoTaggingNoScr
l ClpTaggingNoScr
l ClpTransparentNoScr
l NoClpNoScrCdvt
rt-VBR
l ClpTransparentScr
ClpTransparentScr
l NoClpScrCdvt
l ClpNoTaggingScrCdvt
l ClpTaggingScrCdvt
nrt-VBR
l NoClpScr
NoClpScr
l ClpNoTaggingScr
l ClpTaggingScr
UBR
l NoTrafficDescriptor
NoTrafficDescriptor
l NoClpNoScr
l NoClpTaggingNoScr
l NoClpNoScrCdvt
Issue 03 (2012-11-30)

1132
OptiX OSN 7500 II/7500/3500/1500

Service Type
Traffic Type
Default Value
UBR+
l NoTrafficDescriptorMcr
NoTrafficDescriptorMcr
l NoClpMcr
l NoClpMcrCdvt
For CBR services:
Traffic
Type
CDVT
Process
ing
Cells
with
CLP of 0
and 1 in
Differe
nt Ways
Labelin
g Cells
PCR
MCR
MBS
SCR
NoClpN
oScr
Not
supporte
d
No
No
Not
supporte
d
Not
supporte
d
Not
supporte
d
Not
supporte
d
ClpNoT
aggingN
oScr
Not
supporte
d
Yes
No
Not
supporte
d
Not
supporte
d
Not
supporte
d
Not
supporte
d
ClpTagg
ingNoSc
r
Not
supporte
d
Yes
Yes
Not
supporte
d
Not
supporte
d
Not
supporte
d
Not
supporte
d
ClpTran
sparentN
oScr
Supporte
d
No
No
Not
supporte
d
Not
supporte
d
Not
supporte
d
Not
supporte
d
NoClpN
oScrCdv
t
Supporte
d
No
No
Not
supporte
d
Not
supporte
d
Not
supporte
d
Not
supporte
d
For rt-VBR services:
Issue 03 (2012-11-30)

1133
OptiX OSN 7500 II/7500/3500/1500

Traffic
Type
CDVT
Process
ing
Cells
with
CLP of 0
and 1 in
Differe
nt Ways
Labelin
g Cells
PCR
MCR
MBS
SCR
ClpTrans
parentSc
r
Supporte
d
No
No
Supporte
d
Not
supporte
d
Supporte
d
Supporte
d
NoClpSc
rCdvt
Supporte
d
No
No
Supporte
d
Not
supporte
d
Supporte
d
Supporte
d
ClpNoTa
ggingScr
Cdvt
Supporte
d
Yes
No
Supporte
d
Not
supporte
d
Supporte
d
Supporte
d
ClpTaggingScrC
dvt
Supporte
d
Yes
Yes
Supporte
d
Not
supporte
d
Supporte
d
Supporte
d
For nrt-VBR services:

Traffic
Type
CDVT
Process
ing
Cells
with
CLP of 0
and 1 in
Differe
nt Ways
Labelin
g Cells
PCR
MCR
MBS
SCR
NoClpSc
r
Not
supporte
d
No
No
Supporte
d
Not
supporte
d
Supporte
d
Supporte
d
ClpNoTa
ggingScr
Not
supporte
d
Yes
No
Supporte
d
Not
supporte
d
Supporte
d
Supporte
d
ClpTaggi
ngScr
Not
supporte
d
Yes
Yes
Supporte
d
Not
supporte
d
Supporte
d
Supporte
d
For UBR services:
Issue 03 (2012-11-30)

1134
OptiX OSN 7500 II/7500/3500/1500

Traffic
Type
CDVT
Processing
Cells with
CLP of 0 and
1 in
Different
Ways
Labeli
ng
Cells
PCR
MCR
MBS
SCR
NoTraff
icDescri
ptor
Not
supporte
d
No
No
Not
supporte
d
Not
supporte
d
Not
supporte
d
Not
supporte
d
NoClpN
oScr
Not
supporte
d
No
No
Support
ed
Not
supporte
d
Not
supporte
d
Not
supporte
d
NoClpT
aggingN
oScr
Support
ed
Yes
Yes
Support
ed
Not
supporte
d
Not
supporte
d
Not
supporte
d
NoClpN
oScrCd
vt
Support
ed
No
No
Support
ed
Not
supporte
d
Not
supporte
d
Not
supporte
d
For UBR+ services:

Traffic
Type
CDVT
Labeli
ng
Cells
Processin
g Cells
with CLP
of 0 and 1
in
Different
Ways
PCR
hether
to
Suppor
t MCR
MBS
SCR
NoTraffi
cDescrip
torMcr
Not
supporte
d
No
No
Not
supporte
d
Support
ed
Not
supporte
d
Not
supporte
d
NoClpM
cr
Not
supporte
d
No
No
Support
ed
Support
ed
Not
supporte
d
Not
supporte
d
NoClpM
crCdvt
Support
ed
No
No
Support
ed
Support
ed
Not
supporte
d
Not
supporte
d
Note: Cell labeling means that setting the cell loss priority (CLP) of the cells that do not meet
the traffic parameters to 1. In case of network congestion, the cells with CLP of 1 are first
discarded.
Select a service type based on the network type and service configurations.
Issue 03 (2012-11-30)

1135
OptiX OSN 7500 II/7500/3500/1500

NOTE
Only the IDQ1A and IDL4A boards support UBR+ services.

This parameter is valid only when the Service Type parameter is set.
A.15.17 Service Type (ATM Traffic Management)

Description
The Service Type (ATM Traffic Management) parameter specifies a service type provided
by the ATM technology. Available service types are CBR services, rt-VBR services, nrt-VBR
services, UBR services, and UBR+ services. The services of different types differ from each
other in the reserved bandwidth, service priority, and transmission delay.

If this parameter is set incorrectly, services may be unavailable, or the cells may be discarded.
For example, when a mobile phone makes a call, the call request signal is important and needs
to be transmitted in the most reliable CBR service. In such a case, if the UBR service is selected,
the call may fail to be connected during the peak hours. For application scenarios for each service
type, see "Values" and "Configuration Guidelines" in this topic.
Values
Valid Value
Default Value
CBR, rt-VBR, nrt-VBR, UBR, UBR+
NOTE
Only the IDQ1A and IDL4A boards support UBR+ services.

Value
Description
CBR
Indicates the constant bit rate.

On the user side (namely, for the service applicant), the CBR service is
sensitive to the delay variation of the service data flow. For this reason,
the network is required to transmit data at a constant rate. On the network
side (namely, for the service provider), the CBR service must be allocated
with a fixed static bandwidth within the connection period. Moreover,
the CBR service must be of the highest priority. The CBR service features
stable service data flow. On the user side, data is transmitted periodically
at a constant rate. The service burst event seldom occurs. The circuit
emulation service and the voice service are typical examples. When
applying for the CBR service from the network side, you must specify
the PCR parameter.
Issue 03 (2012-11-30)

1136
OptiX OSN 7500 II/7500/3500/1500

Value
Description
rt-VBR
Indicates the real-time variable bit rate.
The rt-VBR service is sensitive to the delay and delay variation of the
data flow. The voice and interactive video services are the typical
applications, which are similar to the CBR service. Some burst events
are allowed for the rt-VBR service. At different time segments, the data
rate may be different at the source end. Moreover, static bandwidth is not
allowed for the rt-VBR service on the network side (namely, the service
provider). Instead, the rt-VBR service runs in statistical multiplexing
mode. When applying for the rt-VBR service from the network side, you
must specify the parameters such as peak cell rate (PCR), sustainable cell
rate (SCR), maximum burst size (MBS), and cell delay variation
tolerance (CDVT).
Indicates the non-real-time variable bit rate.
nrt-VBR
Compared with the rt-VBR service, the nrt-VBR service has lower
requirements for the real-time feature and it has lower priority than the
rt-VBR service when service data is processed on the network side. The
other features, such as burstness, statistical multiplexing, and service
parameters, are almost the same as those of the rt-VBR service.
Indicates the unspecified bit rate.
UBR
The UBR service is also applicable to the scenarios where realtimeness

and burst events are not highly required. You can require only the best
effort of the network side to provide the service. When applying for the
UBR service, you do not need to specify the service quality parameters.
The network side does not guarantee the UBR service. In the case of
network congestion, the UBR cells are discarded first. Services such as
FTP and E-mail are the typical applications of the UBR service.
The UBR+ service supports the setting of the MCR parameter. There are
UBR+ services on many NodeBs. The UBR+ services are configured
with the MCR. When the service rate does not exceed the configured
MCR, the normal service transmission is ensured. The features of the
UBR+ service other than the MCR are the same as the features of the
UBR service.
UBR+
Each service has its application scenario. Moreover, the service may be affected because of the
network environment and the interconnected equipment. The following table lists application
scenarios for each service type.
Issue 03 (2012-11-30)

1137
OptiX OSN 7500 II/7500/3500/1500

ATM Service
Service Category
Service Type
Application
CBR
Category A
Voice service
Conference call
Audio transmission
(broadcast)
Audio library
Voice mails
Video
Video conference
call
Video transmission
Video on demand
rt-VBR
Category B
Voice service
Voice mails
Conference calls
based on voice
packets
Video
Visual graph and text

NTSC TV
HDTV TV
nrt-VBR
Category C
Data
Air interface
reservation
Banking service
Frame relay network
interconnection
UBR
Category C or D
Data
E-mail service
File transmission
Database browse
Remote terminal
access
UBR+
Category C or D
Data
E-mail service
File transmission
Database browsing
Remote terminal
access

None.
Issue 03 (2012-11-30)

1138
OptiX OSN 7500 II/7500/3500/1500

A.15.18 PCR (ATM Traffic Management)

Description
The PCR (ATM Traffic Management) parameter specifies the peak cell rate (PCR), which
indicates the upper threshold of the service rate. That is, if the specified PCR threshold is
exceeded because the service rate bursts for a long time, excessive packets are discarded.

If this parameter is set improperly, some cells may be discarded. For example,
a wireless base station accesses a voice service, and the CBR service is selected to set up the
connection. In such a case, a correct PCR setting is important. If this parameter is set to a small
value, the bandwidth is not enough. Calls may fail to be set up and the service is unavailable. If
this parameter is set to a large value, other voice services may fail to use the available bandwidth,
and some cells are discarded. Consequently, some calls are interrupted.
Values
Value Range
Default Value
Unit
5-1412828
90
cells/s
For other boards:

Valid Values
Default Value
Unit
90-1412828
90
Cells/s
Generally, set PCR according to service configurations on the interconnected equipment.
Different services are used in different scenarios. The details are as follows:
l
For CBR services, PCR equals the reserved bandwidth. If the UPC/NPC function is enabled,
the traffic is controlled according to the PCR value. That is, the excessive packets are
discarded.
For VBR services, if the UPC/NPC function is enabled, excessive packets are discarded
when the service rate exceeds the PCR. If the UPC/NPC function is disabled, this parameter
is meaningless. That is, the traffic rate can exceed the specified PCR. In such a case, PCR
is set only for the reserved bandwidth computation.
For UBR services, the bandwidth depends on the available physical bandwidth of a port.
For UBR services, PCR is set to determine the maximum rate only.
Issue 03 (2012-11-30)

1139
OptiX OSN 7500 II/7500/3500/1500


Except for PCR of CBR services, the PCR parameter is valid only when the UPC/NPC function
is enabled.
A.15.19 SCR (ATM Traffic Management)

Description
The SCR (ATM Traffic Management) parameter specifies the sustainable cell rate (SCR).
Excessive cells are labeled or discarded, depending on the traffic type.

If this parameter is set improperly, certain cells may be discarded or labeled. For example,
SCR is set to label or discard excessive cells. The labeled cells are discarded in the case of
congestion. Therefore, SCR is a mechanism of avoiding congestion. For the traffic whose cells
are not labeled (see A.15.16 Traffic Type (ATM Traffic Management)), excessive cells are
also discarded.
Values
Value Range
Default Value
Unit
5-1412828
90
cells/s
Value Range
Default Value
Unit
90-1412828
90
cells/s
For other boards:
Generally, set SCR based on service configurations of the interconnected equipment. Different
services are deployed in different scenarios. Details are as follows:
l
For CBR services, SCR does not need to be set.
For UBR services, SCR does not need to be set.
For VBR services, there are two cases as follows:

If the UPC/NPC function is enabled and the service rate exceeds the specified PCR,
excessive cells are discarded or labeled.
If the UPC/NPC function is disabled, this parameter is meaningless. That is, the service
rate can exceed the specified SCR. When this occurs, SCR is set to compute the reserved
bandwidth only.
Issue 03 (2012-11-30)

1140
OptiX OSN 7500 II/7500/3500/1500


The SCR parameter is valid only when the UPC/NPC function is enabled.
A.15.20 MBS
Description
The MBS parameter specifies the maximum number of cells that can be transmitted over the
connection and that burst continuously based on the peak cell rate. This parameter is set to
increase the capability of a system to respond to transient cell burst events, and to enhance the
anti-jitter performance of a service.

The parameter value affects the anti-jitter performance of a service that bursts transiently.
Values
Value Range
Default Value
Unit
Cells
Generally, set this parameter to a large value to prevent cells from being discarded in case of a
transient burst event. The recommended value is 100000.

The MBS parameter is valid only when the UPC/NPC function is enabled.
Related Information
If the UPC/NPC function is enabled, this parameter allows transient burst of a service. The PCR
is similar to a container at constant size. The MBS and cell delay variation tolerance (CDVT)
help to increase the container size. When the transient traffic entering the container increases,
the increased size of the container takes effect. If the transient traffic keeps increasing, an
overflow occurs.
l
If this parameter is set for the opposite equipment, set it to the same value for the local
equipment.
If this parameter is not set for the opposite equipment, set it to the integer part of {1+L/(1/
SCR-1/PCR) } for the local equipment. Letter L indicates the CDVT, representing the
maximum tolerance range for a cell to reach the destination in advance if MBS is set to an
expected value.
If the UPC/NPC function is disabled, this parameter is meaningless.
Issue 03 (2012-11-30)

1141
OptiX OSN 7500 II/7500/3500/1500

A.15.21 CDVT
Description
The CDVT parameter specifies the upper threshold of the cell sending interval. This parameter
is set to increase the capability of a system to respond to transient cell burst events, and to enhance
the anti-jitter performance of a service.

The parameter value affects the anti-jitter performance of a service that bursts transiently.
l
If this parameter is set to a small value, certain cells may be discarded in case of a service
burst event.
If this parameter is set to a large value, the system is not affected. Generally, set it to the
maximum value.
Values
Value Range
Default Value
Unit
0.7-1330000, in step length

of 0.1
0.7
ms
In most cases, set it to the maximum value.

The CDVT parameter is valid only when the UPC/NPC function is enabled. For different service
types and different traffic types, the CDVT values are different. For details, refer to A.15.16
Traffic Type (ATM Traffic Management).
Related Information
Fix the PCR value of the level-1 leaky bucket, and estimate the CDVT value. After passing the
level-1 leaky buckets, the data flow is of burst nature, and the average rate is the PCR. Generally,
the data traffic is transmitted at intervals of PCR, 0, PCR, 0, and so on. The CDVT value needs
to be set to meet the following condition:
CDVT<1-424*(MBS-1) (1/SCR-1/PCR)
(SCR and PCR are expressed in bit/s. 424 bits / cell = 53 bytes/cell*8 bits/byte)
A.15.22 Open Flow Frame Discarding Flag

Description
The Open flow frame discarding flag parameter is set for services at the AAL5 layer only.
AAL5 is a frame structure at the ATM adaptation layer. In this structure, multiple ATM cells
Issue 03 (2012-11-30)

1142
OptiX OSN 7500 II/7500/3500/1500

are encapsulated into one AAL5 frame to provide functions (for example, signaling and routing)
of the upper-layer services. If the AAL5 service bandwidth exceeds the bandwidth on the port
or the specified bandwidth, excessive packets are discarded according to the AAL5 data frame.
One AAL5 data frame may contain multiple ATM cells.

Other AAL-layer services may be interrupted. For example,
if the traffic of other services (such as AAL0 services or AAL2 services) exceeds the bandwidth
on the port or the specified bandwidth, the system may discard all the cells because it fails to
find the frame trailer of the AAL5 service. Although the service traffic is restored normally, the
services cannot be restored.
Values
Valid Values
Default Value
Yes, No
No
Select Yes or No based on the encapsulation type at the ATM adaptation layer. Generally, select
No.
Enable this flag only when the service is at the AAL5 layer.
If any service at other adaptation layers is available, do not enable this flag.

None.
A.15.23 Positive Traffic Descriptor

Description
The Positive Traffic Description parameter specifies the flow used by an ATM connection, in
the aspects of service type, flow type, settings of the relevant parameters (PCR, SCR, MBS, and
CDVT), and flow frame discarding flag.

Improper setting of this parameter may result in a service loss or service interruption. Different
service types are used in different scenarios. Assume that the equipment is interconnected with
Node B. If the voice service transmitted from the opposite equipment is of the CBR type and
the service created on the local equipment is of the UBR type, the call may drop during traffic
peak hours. This is because that the bandwidth for the CBR service is fully guaranteed whereas
the bandwidth for a UBR service is not guaranteed.
Issue 03 (2012-11-30)

1143
OptiX OSN 7500 II/7500/3500/1500

Values
Value Range
Default Value
1-2048
This parameter depends on the created flow. When a flow is created, it is added to the flow table.
To set up a connection, you can select a created flow from the flow table, or enter the ID of the
created flow.

This parameter is valid only when the ATM flow is created.
A.15.24 Connection ID (ATM Service Management)

Description
The Connection ID (ATM Service Management) parameter specifies IDs of the working and
protection links in a protection group.

Values
For IDQ1A/IDL4A boards:
Value Range
Default Value
1-32768
For other boards:

Value Range
Default Value
1-8192
Set this parameter to a value within the value range.

None.
Issue 03 (2012-11-30)

1144
OptiX OSN 7500 II/7500/3500/1500

A.15.25 Connection Type (ATM Service Management)

Description
The Connection Type (ATM Service Management) parameter specifies whether the setup
connection is a PVP or a PVC. Each PVC transmits services that are marked with unique VPI
and VCI only. Each PVP transmits all services with the same VPI over the connection. That is,
the connection transmits all services with different VCIs over the connection with the same VPI,
regardless of VCI.

Values
Valid Value
Default Value
PVP, PVC
PVC

Value
Description
PVP
Each PVP transmits all services marked with VCI with the
same VPI over the connection.
PVC
Each PVC transmits services marked with unique VPI and

VCI only.
To converge services of the same VPI at a port, select PVP.
To transmit services marked with unique VPI and VCI only, select PVC.
As shown in Figure A-21, PVC and PVP are both virtual transmission paths. PVC is, however,
contained in PVP. A PVC is a channel, but a PVP is a path. PVCs in the PVP are used to transmit
services.
Figure A-21 Relation between PVC and PVP
Issue 03 (2012-11-30)

1145
OptiX OSN 7500 II/7500/3500/1500

A.15.26 Spread Type (ATM Service Management)

Description
The Spread Type (ATM Service Management) parameter specifies the spread type of the setup
connections, including unicast connection (p2p), multicast root connection (p2mpRoot), and
multicast leaf connection (p2mpLeaf).

Values
Board Name
Valid Value
Default Value
N1IDQ1A, N1IDL4A
p2p
p2p
N1ADL4, N1DQ1, N1IDL4,

N1IDQ1
p2p, p2mpRoot, p2mpLeaf
p2p

Value
Description
p2p
Provides an end-to-end connection from one port to another port.
p2mpRoot
Provides a root connection for multicast services from one point to

multiple points. The branches of the root connection are the leaf
connections, for example, the black lines shown in the figure.
IDQ1
VCTRUNK
VCTRUNK
MAC Port
VCTRUNK
VCTRUNK
VCTRUNK
Issue 03 (2012-11-30)

1146
OptiX OSN 7500 II/7500/3500/1500

Value
Description
p2mpLeaf
Provides leaf connections for p2mp multicast services. The leaf nodes
are multicast over the root connection, for example, the blue lines shown
in the figure.
The p2p connection is used for communication from a segment to an end, for example, phone
calls and Internet access services. The p2mpRoot and p2mpLeaf connections are used for
multicast communication, for example, IPTV services and broadcast services.
A unicast service is a bidirectional service, but a multicast service is a unidirectional service.
The application scenarios are respectively described in Figure A-22and Figure A-23.
Figure A-22 Multicast service
Issue 03 (2012-11-30)

1147
OptiX OSN 7500 II/7500/3500/1500

Figure A-23 Unicast service
p2p: To set up a point-to-point bidirectional connection, select p2p.

p2mpRoot: To set up a p2mp unidirectional multicast connection, set up a root connection for
multicast services. In this case, select p2mpRoot.
p2mpLeaf: To set up a p2mp unidirectional multicast connection, and to set up leaf connections
for multicast services after the root connection is set up, select p2mpLeaf.
Related Information
To set up a multicast connection, set up a root connection for multicast services, and then set up
multiple leaf connections that have the same source but different sinks. These leaf connections
are multicast to different ports (spatial multicast) or the same port (logical multicast). A multicast
service is a unidirectional service.
A.15.27 VPI and VCI (ATM Service Management)

Description
The VPI and VCI (ATM Service Management) parameter indicates virtual path identity and
virtual channel identity, which are used to respectively identify virtual paths and virtual channels
inside a virtual path. A VPI and a VCI are used to identify a virtual connection. VPI and VCI in
the cell header constitute routing information of a cell.

If this parameter is set improperly, services may be unavailable. Figure A-24 shows an example.
Issue 03 (2012-11-30)

1148
OptiX OSN 7500 II/7500/3500/1500

Figure A-24 Schematic diagram of an example

VPI=76
VCI=19,26,39
VPI in
76
VPC
ATM
Node1
VPI=69
VCI=34,48
VPL
VPI out
53
VPI=53
VCI=19,26,39
VPL
VPI=76
VCI=19,26,39
ATM
Node3
VPI in
53
VPI out
76
IN
OUT
VPI-69 VPI-77
VCI-34 VCI-22
VCI-48 VCI-26
VCC
VPI=77
VCI=22,26
ATM
Node2
VPI in
77
22
VPI out
31
33
VPI=31
The sink VPI/VCI of ATM Node1 must be the same as the source VPI/VCI of ATM Node2.
(VPI = 77, VCI = 22, 26). Otherwise, ATM Node2 may fail to identify the data (VPI in the cell
header is not 53. Alternatively, VCI in the cell header is not 22 or 26) received from ATM Node1.
ATM Node2 can identify the cells whose VPI is 77 and whose VCI is 22 or 26 only. In other
words, a service between different nodes is transmitted on the basis of the same VPI and VCI.
Values
Issue 03 (2012-11-30)
Parameter
Value
Value
Range
Default
Value
VPI
0-4095
Description
Switches VPI labels between nodes. Note that
values 0-4095 are subject to the maximum
configuration. By default, set this parameter to a
value ranging from 0 to 255. You can adjust the
value range by setting Port Type and Max. VPI
Bits. Port resources are specified. If this parameter
is set to a large value for a port, set it to a small
value for other ports. For the configuration method,
refer to Relationship with Other Parameters in this
topic.

1149
OptiX OSN 7500 II/7500/3500/1500

Parameter
Value
Value
Range
Default
Value
VCI
32-65535
Description
Switches VCI labels between nodes. Note that
values 32-65535 are subject to the maximum
configuration. By default, set this parameter to a
value ranging from 32 to 127 (Max. VCI Bits is 7
bits). You can adjust the value range by setting
Max. VCI Bits. Port resources are specified. If this
parameter is set to a large value for a port, set it to
a small value for other ports. For the configuration
method, refer to Relationship with Other
Parameters in this topic.
NOTE
For the N1IDQ1A or N1IDL4A board, the value range of the VPI parameter is not determined by setting
the Max. VPI Bits parameter. Instead, the actual value range of the VPI parameter is determined by setting
it to a specific value range (for example, from 1 to 1000). The value of the VCI parameter ranges from 32
to 65535, and this value range cannot be modified.
This parameter identifies connections only regardless of requirements. Note that the specified
VPI must be consistent with the VPI of the downstream or upstream service on the node to ensure
that the labels are switched correctly in the case of multipoint transmission. An example is shown
in Impact on the System in this topic.

The VPI value range depends on Port Type and Max. VPI Bits.
l
If Port Type is set to UNI, Max. VPI Bits of the port can be set to 8 only. In this case, set
VPI to a value ranging from 0 to 255.
If Port Type is set to NNI, Max. VPI Bits of the port can be set to 12. In this case, set
VPI to a value ranging from 0 to 4095.
The VCI value range depends on Max. VCI Bits of the port.
l
If the value of Max. VCI Bits is increased, set VCI to a larger value range.
If Max. VCI Bits is set to 16, set VCI to a value ranging from 32 to 65535.
A.15.28 Positive Service Status(ATM Service Management)

Description
The Positive Service Status parameter indicates the current status of a positive ATM service.
Positive refers to the direction from the source to the sink of an ATM connection.
Issue 03 (2012-11-30)

1150
OptiX OSN 7500 II/7500/3500/1500


When this parameter is set to Up, the ATM service is normal. Otherwise, the service is
interrupted.
Values
Valid Value
Default Value
Up, Down
Up

Value
Description
Up
Indicates that the service is normal.
Down
Indicates that the service is interrupted.
There are no specific principles for setting this parameter because it is used for querying.
A.15.29 Positive Service Failure Reason(ATM Service

Management)
Description
The Positive Service Failure Reason parameter indicates the cause of a positive service failure.
Positive refers to the direction from the source to the sink of an ATM connection.

When this parameter is set to OK, the service is normal. Otherwise, the service is interrupted.
Values
Valid Value
Default Value
OK, LCD, AIS, CCLOC
OK
Issue 03 (2012-11-30)
Value
Description
OK
Indicates that the positive service is normal.

1151
OptiX OSN 7500 II/7500/3500/1500

Value
Description
CCLOC
Indicates that the service is interrupted because the user cell

or the CC cell is not received within a period ranging from 3s
to 4s after the CC sink is configured.
AIS
Indicates that the positive service is interrupted because AIS

signals are received.
LCD
Indicates that the positive service is interrupted because LCD

is received.
There are no specific principles for setting this parameter because this parameter is used for
querying.
A.15.30 Source/Sink Switching Cause

Description
The Source/Sink Switching Cause parameter specifies a condition that triggers switching of
an ATM protection pair.

Values
Valid Value
Default Value
Idle, Protection Route Signal Fail, Working

Route SF, Non-Revertive, Wait-To-Restore,
Manual to Active, Manual to Standby,
Freeze, Lockout, Force to Standby
Idle
Issue 03 (2012-11-30)
Value
Description
Idle
Indicates that the working channel and the protection pair are normal.
Protection Route
Signal Fail
Indicates that a failure in the working channel triggers switching.
Working Route SF
Indicates that the protection channel fails but switching does not occur.
Force to Standby
Indicates that services are manually switched from the working channel
to the protection channel when both channels are normal.

1152
OptiX OSN 7500 II/7500/3500/1500

Value
Description
Non-Revertive
Indicates that the working channel is restored to normal and the

protection channel remains normal. The protection group is in nonrevertive mode.
Wait-To-Restore
Indicates that the working channel is restored to normal and the

protection channel remains normal. The protection group is in revertive
mode. In this case, services are waiting to be restored to the working
channel. The duration of the waiting time is determined by the
restoration time of the working channel.
Manual to Active
Indicates that services are switched from the protection channel to the
working channel.
Manual to Standby
Indicates that services are switched from the working channel to the
protection channel.
Freeze
Indicates that the status of the protection pair is frozen.
Lockout
Indicates the protection lockout of the protection pair.
This parameter is used for querying.
A.15.31 Protection Type (ATM Service Management)

Description
The Protection Type (ATM Service Management) parameter specifies whether an ATM
connection is configured with 1+1 or 1:1 protection.

Values
For IDQ1A/IDL4A boards:
Valid Value
Default Value
1:1
1:1
For other boards:
Issue 03 (2012-11-30)
Valid Value
Default Value
1+1, 1:1
1+1
1153
OptiX OSN 7500 II/7500/3500/1500

Select a value according to the protection type specified by users.

None.
Related Information
1+1 protection: Uses the dual-fed and selective receiving mechanism.
Figure A-25 shows the normal status.
Figure A-25 Normal status
Working entity
Service data
Protection entity
Source node protection domain
Destination node protection domain
Figure A-26 shows the switching status.

Figure A-26 Switching status
Working entity
Service data
Protection entity
1:1 Protection: Adopts the redundant connection protection mechanism.

Working service data

Extra service data
Issue 03 (2012-11-30)
Working entity
Protection entity

1154
OptiX OSN 7500 II/7500/3500/1500


Working entity
Extra service data
Protection entity
A.15.32 Switching Direction (ATM Service Management)

Description
The Switching Direction (ATM Service Management) parameter specifies whether the
switching occurs at one end (source or sink), or at both ends (namely, both the source and sink
ends) simultaneously.

Values
Valid Value
Default Value
Source + Sink, Source, Sink
Sink
l
If two P2P ATM connections have the same source but different sinks, select Sink.
If two P2P ATM connections have the same sink but different sources, select Source.
If two P2P ATM connections have different sources and sinks, select Source + Sink.

None.
A.15.33 Switching Status (ATM Service Management)

Description
The Switching Status (ATM Service Management) parameter specifies the status of an ATM
protection group. It identifies whether switching occurs or whether the protection protocol stops.

Issue 03 (2012-11-30)

1155
OptiX OSN 7500 II/7500/3500/1500

Values
Valid Value
Default Value
Stop, Normal, Switch

Value
Description
Stop
Indicates that the protection protocol stops or the protection

pair is not added.
Normal
Indicates the normal status.
Switch
Indicates the switching status.
None.

None.
A.15.34 Switching Type (ATM Service Management)

Description
The Switching Type (ATM Service Management) parameter specifies whether a bidirectional
ATM connection is switched at both ends when a protection switching event occurs.

Values
Valid Value
Default Value
Single-Ended, Dual End
Single-Ended
Select a proper value according to the protection type specified by users.
Issue 03 (2012-11-30)

1156
OptiX OSN 7500 II/7500/3500/1500


None.
Related Information
The 1+1 protection is used as an example to describe differences between single-ended
protection and dual-ended protection.
In single-ended protection, if the working link fails in one direction, services are switched from
the working link to the protection link only in this direction. Switching does not occur in another
direction.
Working entity
Service data
Protection entity

Working entity
Service data
Protection entity
Dual-ended protection means that a switching event occurs automatically in another direction
if it occurs in one direction. In this case, a bidirectional service is completely switched to the
protection link.

Extra service data
Issue 03 (2012-11-30)
Working entity
Protection entity

1157
OptiX OSN 7500 II/7500/3500/1500


Working entity
Extra service data
Protection entity
A.15.35 Revertive Mode (ATM Service Management)

Description
The Revertive Mode (ATM Service Management) parameter specifies whether a service is
switched to the original working link after the working link is restored to normal.

Values
Valid Value
Default Value
Revertive
Select a proper value, depending on whether the ATM service needs to be switched to the original
working link.

None.
A.15.36 Pause Time(0-100) *100 ms (ATM Service Management)

Description
The Pause Time(0-100) *100 ms (ATM Service Management) parameter specifies the period
from the time when a fault is detected to the time when switching occurs in the ATM protection
group. It is used for ATM protection. If a link is restored to normal within the hold-off time,

Issue 03 (2012-11-30)

1158
OptiX OSN 7500 II/7500/3500/1500

Values
Value Range
Default Value
Unit
(0-100)*100, in step length of

1
100
ms
Select a proper value according to requirements.

None.
A.15.37 WTR Time(0-30min) (ATM Service Management)

Description
The WTR Time(0-30min) (ATM Service Management) parameter specifies the period from
the time when the original working link is restored to normal to the time when services are
switched from the protection link back to the original working link.

Values
Value Range
Default Value
Unit
12
min
Set this parameter properly based on the actual network conditions.

This parameter is valid only when A.15.35 Revertive Mode (ATM Service Management) is
set to Revertive.
A.15.38 External Command (ATM Protection Group)

Description
The External Command (ATM Protection Group) parameter specifies the external command
operations in 1+1 or 1:1 protection switching of ATM connections.
Issue 03 (2012-11-30)

1159
OptiX OSN 7500 II/7500/3500/1500


The switching state may be changed. Moreover, some cells may be discarded in the switching
process.
Values
Value Range
Default Value
Clear, Freeze, Lockout of

Protection, Force to Standby,
Manual to Active, Manual to
Standby, Stop Protection
Controller, Start Protection
Controller
Clear

Value
Description
Clear
Clears all the external commands.
Freeze
Freezes the protection group. After the Freeze command is

issued, the protection group keeps the current state, which is
not changed any more.
Lockout of Protection
Locks the protection connection. That is, forcibly switches to

the working connection.
Force to Standby
Forcibly switches to the protection connection.
Manual to Active
Manually switches to the working connection.
Manual to Standby
Manually switches to the protection connection.
Stop Protection Controller
Disables the functions of the protection controller.
Start Protection Controller
Enables the functions of the protection controller.
Select the value according to the switching operation to be performed.

This parameter is valid only after the protection group is added.
Issue 03 (2012-11-30)

1160
OptiX OSN 7500 II/7500/3500/1500

A.15.39 IMA Group Number

Description
The IMA Group Number parameter specifies that each IMA group is allocated with a unique
number for identification. To query the IMA group status and link status, set this parameter.

Values
IDQ1A/IDL4A:
Value Range
Default Value
1-93
IDQ1/IDL4:
Value Range
Default Value
1-32
When you create IMA groups, the IMA group number is automatically allocated by the
U2000. The number of IMA groups for the IDQ1 or IDL4 cannot be more than 16, and the
number of IMA groups for the IDQ1A or IDL4A cannot be more than 93.

None.
A.15.40 IMA Protocol Version

Description
The IMA Protocol Version parameter specifies the version number of the IMA protocol adopted
at the local end. The IMA protocol has two versions: IMA1.0 and IMA1.1.

The IMA protocol version of the interconnected equipment must be consistent. Otherwise, the
IMA service may fail to interwork.
Issue 03 (2012-11-30)

1161
OptiX OSN 7500 II/7500/3500/1500

Values
Valid Values
Default Value
1.0, 1.1
1.1
The IMA protocol version for the interconnected equipment should be consistent at the two ends.

None.
A.15.41 IMA Transmit Frame Length

Description
The IMA Transmit Frame Length parameter specifies the length of one IMA frame transmitted
by the local equipment. That is, how many ATM cells are contained in one IMA frame. An IMA
frame can contain 32, 64, 128 or 256 ATM cells. Moreover, each IMA frame contains an IMA
control protocol cell (ICP), which is used to negotiate the IMA protocol and to transmit
information.

If the value of IMA Transmit Frame Length for the interconnected equipment at one end is
inconsistent with that at another end, the IMA negotiation may fail.
Values
Valid Values
Default Value
32, 64, 128, 256
128
IMA Transmit Frame Length should be consistent with that of the interconnected board.

None.
A.15.42 IMA Group Configuration Mode

Description
The IIMA Group Configuration Mode parameter specifies the configuration and working
modes of the links in an IMA group. These configuration and working modes are Symmetrical
Issue 03 (2012-11-30)

1162
OptiX OSN 7500 II/7500/3500/1500

Mode and Symmetrical Operation, Symmetrical Mode and Asymmetrical Operation and
Asymmetrical Mode and Asymmetrical Operation.

The configuration decides whether an IMA link is of unidirectional conductivity. For examples,
see Principle of Selecting Values.
Values
Valid Values
Default Value

Operation, Symmetrical Mode and
Asymmetrical Operation,
Asymmetrical Mode and Asymmetrical
Operation
Symmetrical Mode and Symmetrical Operation

Value
Description

Symmetrical Operation
Indicates that each link in an IMA group is configured to be

capable of transmitting and receiving packets in two
directions (namely, symmetrical mode). When the IMA group
works normally, if a link is interrupted in the transmit or
receive direction, it is interrupted accordingly in another
direction. That is, this link is bidirectionally unavailable (this
is called symmetric operation).


capable of transmitting and receiving packets in two
directions (namely, symmetrical mode). When the IMA group
works normally, if a link is interrupted in the transmit or
receive direction, it works normally in another direction. That
is, this link is unidirectionally available (this is called
asymmetric operation).
Asymmetrical Mode and


capable of transmitting or receiving packets only in one
direction (namely, asymmetrical mode). When the IMA
group works normally, if a link is interrupted in the transmit
or receive direction, it works normally in another direction.
That is, this link is unidirectionally available (this is called
asymmetric operation).
Select the value according to the following application scenarios.
Figure A-33 shows the asymmetrical mode and symmetrical operation.
Issue 03 (2012-11-30)

1163
OptiX OSN 7500 II/7500/3500/1500

Figure A-33 Schematic diagram of symmetrical mode and symmetrical operation
Figure A-34 shows the asymmetrical mode and asymmetrical operation.

Figure A-34 Schematic diagram of symmetrical mode and asymmetrical operation
Figure A-35 shows the asymmetrical mode and asymmetrical operation.
Issue 03 (2012-11-30)

1164
OptiX OSN 7500 II/7500/3500/1500

Figure A-35 Schematic diagram of asymmetrical mode and asymmetrical operation
If the two directions of an E1 link in the IMA group are in both transmit or both receive directions,
the IMA group fails to negotiate.

None.
A.15.43 Minimum Number of Active Links

Description
The Minimum Number of Active Links parameter specifies the minimum threshold of the
active links required in an IMA group for normal running of the IMA group.

If the parameter value is set improperly, the services may be interrupted. If the number of active
links in an IMA group is not less than the value of Minimum Number of Active Links, the
IMA group works normally. Otherwise, the services of the IMA group are interrupted.
Values
Valid Values
Default Value
0-32
Set this parameter according to the minimum number of active links supported by the opposite
equipment.
Alternatively, set the value according to the actual capability of the services. For example, there
are 10 active links, and the total bandwidth is 20 Mbit/s. In this case, the interconnected
Issue 03 (2012-11-30)

1165
OptiX OSN 7500 II/7500/3500/1500

equipment provides the bandwidth of at least 15 Mbit/s. Then set Minimum Number of Active
Links to 8. If the number of links is less than 8, the bandwidth is less than 15 Mbit/s. In this
case, the services of the IMA group are interrupted.

This parameter is valid only after IMA Group is set.
A.15.44 IMA Group Status

Description
The IMA Group Status parameter specifies the status of the IMA group state machine. By
referring to this state, you can diagnose the faults of the IMA group protocol.

Values
Valid Values
Default Value
Not Configured, Start-Up, Start-Up-Ack, Config-Aborted,

Insufficient-Links, Blocked, Operational
Issue 03 (2012-11-30)
Value
Description
Not Configured
Displays this state if the IMA group does not exist.
Start-Up
Displays this state if the IMA group state machine is started

at the local end, and waits for being started at the opposite
end.
Start-Up-Ack
This is a transitional state. After the IMA group state

machine is started at the two ends, the IMA group changes
to the Start-up-Ack state.
Config-Aborted
Displays this state if the parameters adopted at the local end

do not match those at the opposite end.
Insufficient-Links
Displays this state if the parameters at the local end match

those at the opposite end, but the link resources are
insufficient.
Blocked
Indicates that the IMA group is blocked. To maintain an

IMA group, you can block it.
Operational
Displays this state if the IMA group is not suppressed and

the link resources are sufficient.

1166
OptiX OSN 7500 II/7500/3500/1500

None.

None.
A.15.45 Protocol Mode (IMA1.0 Mode)

Description
The Protocol Mode parameter indicates the management mode of the IMA 1.0 protocol. The
management modes of the IMA 1.0 protocol contain ITU-T mode and European mode.

This parameter affects the negotiation between the two ends of an IMA group. If the
configurations of the two ends are different, the negotiation may fail and hence the service is
affected.
Values
Value Range
Default Value
ITUT Mode, European

Mode
ITUT Mode

Value
Description
ITUT Mode
Indicates that the ITU-T mode is used.
European Mode
Indicates that the European mode is used.
The IMA 1.0 management mode cannot interwork with the IMA 1.1 management mode.
Ensure that the configurations of the two ends of an IMA group are the same when you select
the IMA 1.0 management mode. In addition, IMA Transmit Frame Length must be set to 128;
IMA Group Configuration Mode must be set to Symmetrical Mode And Symmetrical
Operation.
Issue 03 (2012-11-30)

1167
OptiX OSN 7500 II/7500/3500/1500

A.15.46 Enable/Disable Cell Payload Scramble

Description
The Enable/Disable Cell Payload Scramble parameter specifies whether to scramble the
payload of the cells in the E1 link.

Values
Valid Values
Default Value
Enabled, Disabled
Enabled
Select the value according to the equipment at the opposite end. Generally, select Enabled.

None.
A.15.47 Link Frame Format

Description
The Link Frame Format parameter specifies whether the frames in the E1 link are in dual frame
format or multiframe format.

Values
Valid Values
Default Value
E1 Dual Frame, E1 CRC-4 Multiframe
E1 CRC-4 Multiframe
Issue 03 (2012-11-30)

1168
OptiX OSN 7500 II/7500/3500/1500

Value
Description
E1 Dual Frame
Indicates that an E1 dual frame consists of ITU-T G.704 basic

frames (32 bytes form one ITU-T G.704 basic frame), and its
name is decided by the frame delimitation method. ITU-T G.
706 specifies the framing method of alternating E1 FAS and
E1 NFAS frame flow. For this reason, an E1 dual frame is
regarded as a multiframe that consists of two ITU-T G.704
basic frames. An E1 dual frame is formed for delimitation.
E1 CRC-4 Multiframe
Indicates that an E1 CRC-4 multiframe consists of 16 ITU-T

G.704 basic frames. An E1 CRC-4 multiframe is defined in
ITU-T G.706. It carries the CRC information and the line
monitoring information. An E1 CRC-4 multiframe flow is
first delimitated in dual frame format. After the dual frame is
framed correctly, the CRC-4 multiframe is framed.
Currently, E1 dual frames are almost not used. Instead, E1 CRC-4 multiframes are used in most
cases. For this reason, select E1 CRC-4 Multiframe.

None.
A.15.48 Connection Direction (ATM Segment End Attribute)

Description
The Connection Direction (ATM Segment End Attribute) parameter is based on one node.
Figure A-36 shows the forward and backward of node B.
Figure A-36 An example of connection direction
Forward
Backward

Issue 03 (2012-11-30)

1169
OptiX OSN 7500 II/7500/3500/1500

Values
Valid Values
Default Value
Forward, Backward

Value
Description
Forward
Indicates the direction from the source port to the sink port.
Backward
Indicates the direction from the sink port to the source port.
None.

None.
A.15.49 Segment and End Attribute (ATM Segment End Attribute)

Description
The Segment and End Attribute (ATM Segment End Attribute) parameter specifies the
OAM maintenance point type. For different segment and end attributes, OAM cells are processed
in different segments.

Values
Valid Values
Default Value
Non segment and Endpoint, Segment point, Endpoint, Segment

and Endpoint
Non segment and

Endpoint
Issue 03 (2012-11-30)
Value
Description
Non segment and Endpoint
Indicates not to terminate OAM cells.

1170
OptiX OSN 7500 II/7500/3500/1500

Value
Description
Segment point
Indicates terminating OAM cells between two segment points

only.
Endpoint
Indicates terminating OAM cells between two end points

only.
Indicates terminating OAM cells between two segment points

and between two end points.
According to different OAM maintenance segments, as shown in Figure A-37, set the segment
and end point attribute properly.
Figure A-37 Schematic diagram of the maintenance segment
end
seg
inner
inner
seg+end
segment
user1
end to end
user2
To maintain the entire ATM connection, select Endpoint for the two ends of the connection.
To maintain one segment of the entire ATM connection, select Segment point for the two
ends of the segment to be maintained.
If the endpoint overlaps the segment point, select Segment and Endpoint.
CAUTION
l For a protection link that is added into the 1+1 source or 1+1 sink protection group, do not
select Segment and Endpoint. Moreover, the CC function cannot be enabled.
l For a connection that is added into the protection group, do not select Segment.

None.
Issue 03 (2012-11-30)

1171
OptiX OSN 7500 II/7500/3500/1500

A.15.50 LLID
Description
The LLID parameter specifies the loopback location. It contains 15 bytes.

Values
Field
Valid Values
Default Value
Description
Country Code
(Hexadecimal Code)
2 bytes
[2 bytes] 0000
Indicates the country code.
Network Code
(Hexadecimal Code)
2 bytes
[2 bytes] 0000
Indicates the network

code.
NE Code
(Hexadecimal Code)
11 bytes
4-byte NE ID + 7byte all 0s
Indicates the NE code.
Generally, select the default value.
Related Information
Loopback Test:
1.
To start the LB test, issue a command at the initiating point.
2.
For the segment LB test, the loopback point may be the intermediate point or the segment
point. Regardless of the destination LLID, the seg-LB cells are captured at the segment
point. For this reason, the seg_LB test cannot be carried out across different segment points.
3.
For the end-to-end LB test, the loopback point must be the endpoint rather than the middle
point. Likewise, regardless of the destination LLID, the e-t-e_LB cells are captured at the
endpoint. For this reason, the e-t-e_LB test cannot also be carried out across different
segment points.
LLID:
Indicates the coding mode of LLID. In practice, the APC LLID can be set to any value. For the
Qx or NE-board interface, the LLID can contain 16 bytes. For the U2000 server and client, the
window is designed according to the second codiong mode (0x01) specified in ITU-T I.610. For
this reason, you can enter 15 bytes, which consist of 2-byte country code (the default value is
0000 in the case of hexadecimal system), 2-byte network code (the default value is 0000 in the
case of BCD code pattern), and 11-byte NE code (by default, the first four bytes indicate the NE
ID. Enter 0 for the last seven bytes). If you set the LLID, and if the NE code is different from
the NE ID, the LLID does not change although the NE ID is changed.
Issue 03 (2012-11-30)

1172
OptiX OSN 7500 II/7500/3500/1500

A.15.51 Maximum Ingress Bandwidth

Description
The Maximum Ingress Bandwidth parameter specifies the maximum ingress bandwidth that
a port on the ATM board supports.

During service configuration, ensure that total bandwidth of the configured services does not
exceed the value of this parameter. Otherwise, the system prompts that the verification fails. If
the maximum ingress bandwidth of each optical port on the N1IDQ1 board is 353207 cell/s, the
total bandwidth of the configured services at the port should not be greater than 353207 cell/s.
Values
Value Range
Default Value
4528-1412828 cell/s
The maximum ingress bandwidth of each external optical port on the N1IDQ1 and N1ADQ1
boards is 353207 cell/s. The maximum ingress bandwidth of each external optical port on the
N1IDL4 and N1ADL4 boards is 1412828 (353207x4) cell/s.
For internal ATM ports, the maximum ingress bandwidth depends on the type of the bound
services and number of the services. If VCTRUNK1 is bound with two VC-12s, the maximum
ingress bandwidth is 9056 (4528x2) cells/s. If VCTRUNK1 is bound with four VC-4s, the
maximum ingress bandwidth is 1412828 (353207x4) cell/s.
Plan properly before configuring or using a board to ensure that the ingress bandwidth of each
port does not exceed the permitted value range.
A.15.52 Maximum Egress Bandwidth

Description
The Maximum Egress Bandwidth parameter specifies the maximum egress bandwidth that a
port on the ATM board supports.

During service configuration, ensure that the total bandwidth of the configured services does
not exceed the value of this parameter. Otherwise, the system prompts that the verification fails.
If the maximum egress bandwidth of each optical port on the N1IDQ1 board is 353207 cell/s,
the total bandwidth of the configured services at the port should not be greater than 353207 cell/
s.
Issue 03 (2012-11-30)

1173
OptiX OSN 7500 II/7500/3500/1500

Values
Value Range
Default Value
4528-1412828 cell/s
The maximum egress bandwidth of each external optical port on the N1IDQ1 and N1ADQ1
boards is 353207 cell/s. The maximum egress bandwidth of each external optical port on the
N1IDL4 and N1ADL4 boards is 1412828 (353207x4) cell/s.
For internal ATM ports, the maximum ingress bandwidth depends on the type of the bound
services and number of the services. If VCTRUNK1 is bound with two VC-12s, the maximum
egress bandwidth is 9056 (4528x2) cells/s. If VCTRUNK1 is bound with four VC-4s, the
maximum egress bandwidth is 1412828 (353207x4) cell/s.
Plan properly before configuring or using a board to ensure that the egress bandwidth of each
port does not exceed the permitted value range.
A.16 RPR Associated Parameters

This topic describes the parameters for configuring the RPR function.
A.16.1 RPR Node ID

Description
The Node ID parameter indicates the ID of a node in the resilient packet ring (RPR). In the RPR,
each node has a unique ID to facilitate RPR management and packet forwarding.

Values
Value Range
Default Value
1-255
In the same RPR, each node must have a unique ID. IDs of nodes in different RPRs can be
allocated separately.
When planning a network, you need to uniformly plan IDs for nodes in the RPR. For a new
project, node IDs increase in an ascending order in the direction of ring 0.
Issue 03 (2012-11-30)

1174
OptiX OSN 7500 II/7500/3500/1500

After you configure services, node IDs cannot be modified. Otherwise, the following results
may be caused:
l
Some packets in a service that is forwarded at the local node are lost for up to 50 ms.
The service whose destination node is the local node may be unavailable. When this occurs,
you need to reconfigure the service according to the new ID of the local node.

None.
A.16.2 RPR Protocol

Description
The RPR Protocol parameter specifies whether to enable the resilient packet ring (RPR)
protocol for a node in the RPR. If the RPR protocol is enabled, you can use the RPR features to
forward and protect a service.
As a new MAC protocol defined in IEEE 802.17, RPR is designed to optimize the transmission
of data packets, and to serve as the Ethernet standard that is fairly shared by the transmission
media bandwidth. The RPR technology integrates many advantages, such as high bandwidth
usage and multi-service access in the Ethernet network, and wide bandwidth and powerful selfhealing capability in the optical network. As a result, the RPR technology features dual-ring
structure, spatial reuse mechanism, flexible granularity of service bandwidth, dynamic sharing
and allocation of bandwidth, statistical multiplexing, support for various service levels,
automatic identification of network topology, and protection switching based on the source route.

After you switch the status of the RPR protocol, the services forwarded from the node are
interrupted transiently. The packets are lost for up to 50 ms.
A node whose RPR protocol is disabled cannot add or drop any service.
Values
Valid Value
Default Value
Enabled, Disabled
Disabled
Issue 03 (2012-11-30)
Value
Description
Enabled
Enables the RPR protocol. In this case, a node is added to the

RPR network.
Disabled
Disables the RPR protocol. In this case, a node is deleted from

the RPR network.

1175
OptiX OSN 7500 II/7500/3500/1500

l
To configure a RPR network, enable the RPR protocol for all the nodes in the RPR.
For a node that adds or drops a service, you must enable the RPR protocol.
For a node that does not add or drop a service at the moment, generally, you also need to
enable the RPR protocol.
If a node with the RPR protocol disabled needs to add or drop services, enabling the RPR protocol
at this moment may result in a service interruption for 50 ms. If a node does not need to add or
drop a service, disable the RPR protocol to shorten the time for the node to learn the topology
and to minimize service interruption time due to a change in the RPR network topology
accordingly.
If some services are available in the RPR network, enable or disable the RPR protocol on the
node only when you make sure that this operation does not affect any service in the network.

Before enabling the RPR protocol, set Node ID for the local node. Otherwise, the RPR protocol
cannot be enabled.
A.16.3 RPR Node Protection Slow Timer Value(ms)

Description
The Protection Slow Timer Value(ms) parameter specifies the three timers in the resilient
packet ring (RPR) protocol. The three timers are fast, slow and wait-to-restore (WTR). The fast
timer and slow timer specify the interval of transmitting topology protection (TP) messages in
an RPR.
If any protection information is changed, the fast timer transmits eight TP messages. Then, the
changed protection information is advertised to all other nodes in the RPR network at the earliest
time. After the fast timer transmits the eight TP messages, the slow timer is used to transmits
the TP message so that the bandwidth occupancy is minimized.

Values
Board Name
Value Range
Default Value
Unit
N1EMR0
50-10000, in a step length of

50 ms
1000
ms
100-1000, in step length of

100 ms
100
ms
(Not produced any

more)
N2EGR2, N2EMR0
Issue 03 (2012-11-30)

1176
OptiX OSN 7500 II/7500/3500/1500

For the slow timer on each node, the default value is the same. Generally, use the default value.
If any requirements are proposed by customers, set the slow timer to a proper value, depending
on the board software version. The value should not exceed, however, the range allowed in
practice.

This parameter is valid only when RPR Protocol is set to Enabled.
A.16.4 RPR ATD Timer Value(s)

Description
The ATD Timer Value(s) parameter specifies the interval of transmitting the attribute discovery
(ATD) message. It is also called a topology timing value.
After the RPR network is configured, each node in the network actively broadcasts its
information using the topology discovery protocol to discover the RPR topology. The
information is transmitted through ATD messages and is used with topology and protection (TP)
messages to maintain the RPR network topology. TP messages are used to transmit a real-time
and urgent topology message. ATD messages are used to transmit a non-real-time topology
message.

If the RPR network runs properly, the system operation is not affected after you modify the
setting of ATD Timer Value.
Values
Value Range
Default Value
Unit
Second
Generally, use the default value. If any requirement is proposed by customers, you can set ATD
Timer Value to a proper value based on the RPR network status. The value of ATD Timer
Value, however, cannot exceed the range allowed in practice.

A.16.5 RPR Protection Mode

Description
The Protection Mode parameter specifies the protection mode of a node in the RPR network.
That is, it specifies how to protect services upon a fault in the RPR network. Three modes are
Issue 03 (2012-11-30)

1177
OptiX OSN 7500 II/7500/3500/1500

available to protect services in the RPR network. For details, see "Related Information" in this
topic.

After the setting of Protection Mode is modified, all the services that pass through the node are
interrupted for up to 50 ms.
If the protection mode is set to Steering, the service interruption time can be less than 50 ms
when there are 16 or less nodes on the ring.
Values
Valid Value
Default Value
Wrapping, Steering, Wrap and Steering
Steering

Value
Description
Steering
Changes the service route to protect the RPR network. In this case,
less bandwidth is used, but more time is taken to respond, and more
packets are discarded in case of a switching event.
Wrapping
Switches the loop to protect services in the RPR network. In this case,
less time is taken to respond, fewer packets are discarded in case of
a switching event, but some bandwidth is wasted.
Wrap and Steering
Switches the loop and changes the service route to protect services
in the RPR network. This mode integrates the advantages such as
short response time in Wrapping mode and optimized transmission
path in Steering mode.
Configure a proper protection mode for every node in the RPR network based on the service
characteristics and actual requirements. The protection modes for all the nodes in the same RPR
network must be compatible with each other. If not, an alarm is generated and services are not
protected in the way as expected by customers. Use the default setting, unless otherwise
specified.
You can set this parameter based on the compatibility of the protection mode. The Wrapping
mode is compatible with the Wrap and Steering mode. The Wrapping mode or the Wrap and
Steering mode, however, is incompatible with the Steering mode. For example, you can set
Protection Mode to Steering or Wrapping for all the nodes in the RPR network. You can also
set Protection Mode to Wrapping for some nodes, and to Wrap and Steering for other nodes.
You can also set Protection Mode to Steering for some nodes, and to Wrapping or Wrap and
Steering for other nodes.
Issue 03 (2012-11-30)

1178
OptiX OSN 7500 II/7500/3500/1500


Related Information
Steering: Steers the loop to protect services in the RPR network.
This mode is the default mode for all the nodes. If a part of the RPR is faulty, the information
that contains faulty point and fault type is transmitted to each node. The topology is changed
accordingly. The source node only needs to directly transmit the data to the destination node
based on the new topology. The data that has been transmitted to the faulty point is discarded at
the point. In Steering mode, the bandwidth usage is improved to transmit data over an optimal
route, but the switching time is long. After the topology becomes stable, you need to determine
a new route based on the new topology.
Figure A-38 and Figure A-39 respectively shows the network status before a fiber cut and after
the Steering mode is adopted for protection.
Figure A-38 Network before a fiber cut
Figure A-39 Network after the Steering mode is configured
Node 2 transmits packets to node 6. Normally, the service flow is in the direction of s2 -> s3 > s4 -> s5 -> s6. If the fiber between nodes 3 and 4 is cut, the topology is updated to optimize
the route. In this case, the service flow is in the direction of s2 -> s1 -> s7 -> s6.
Wrapping: Wraps the route to protect services in the RPR network.
This mode is optional. If a point on the RPR ring is faulty, the node close to the faulty point
automatically loops back to connect ring 0 with ring 1. In Wrapping mode, the switching time
is short to minimize the frame loss resulted from the fault. The bandwidth usage, however, is
low.
Figure A-40 and Figure A-41 respectively shows the network status before a fiber cut and after
the Wrapping mode is adopted for protection.
Issue 03 (2012-11-30)

1179
OptiX OSN 7500 II/7500/3500/1500

Figure A-40 Network before a fiber cut
Figure A-41 Network after the Wrapping mode is configured
Node 2 transmits packets to node 6. Normally, the service flow is in the direction of s2 -> s3 > s4 -> s5 -> s6. If the fiber between nodes 3 and 4 is cut, it is switched on nodes 3 and 4. In this
case, the service flow is in the direction of s2 -> s3 -> s2 -> s1 -> s7-> s6 -> s5 -> s4 -> s5 ->
s6.
Wrap and Steering: Wraps and then steers the route for protection.
Wraps and then steers the route for protection. This mode integrates the advantages such as the
short response time in the Wrapping mode and the optimal route in the Steering mode. In Wrap
and Steering mode, the route is wrapped to avoid loss of more packets, and then the route is
steered for protection after the new topology becomes stable.
A.16.6 RPR Hold-off Time(ms)

Description
The Hold-off Time(ms) parameter specifies the time to wait for switching (namely, hold-off
time) after the signal fail (SF) or signal degrade (SD) condition is detected in the RPR network.
l
After the time specified in Hold-off Time expires, switching occurs in the RPR network
if the SF or SD condition persists.
Switching does not occur in the RPR network if the SF or SD condition is cleared.

Values
Issue 03 (2012-11-30)
Value Range
Default Value
Unit
0-200, in a step length of 10
ms

1180
OptiX OSN 7500 II/7500/3500/1500

l
If no SDH protection scheme (for example, MSP or SNCP) is configured, use the default
value to avoid loss of more packets within the hold-off time in the RPR network.
If any SDH protection scheme (for example, MSP or SNCP) is configured, make sure that
the hold-off time is longer than the time for all the SDH protection switching. For example,
the hold-off time is set to 50 ms. In this case, the SDH protection schemes have the priority
to be implemented. If the SDH protection schemes fail, the RPR switching is implemented
for protection.

A.16.7 RPR Protection Restoration Mode

Description
The Protection Restoration Mode parameter specifies whether to switch the node to the normal
state and to groom the service in the loop as a normal service after a node in the SF/SD state
detects that the SF/SD condition is cleared.

l
If the service in the RPR network is not switched, or if the forced switching (FS) or manual
switching (MS) occurs, the system operation is not affected after you modify the setting.
In the case of switching based on SF or SD on the node:

If this parameter is set to Enabled, the node switches to the normal state when it has
detected that the SF or SD condition is cleared, and grooms the service in the loop as a
normal service. During the period of service restoration, some packets are lost for up to
50 ms.
If this parameter is set to Disabled, the node is always in the switching state. In this
case, the service is not switched to the working path, no service packets are lost, but the
bandwidth utilization is decreased.
Values
Valid Value
Default Value
Enabled, Disabled
Enabled
Issue 03 (2012-11-30)
Value
Description
Enabled
If the working path recovers after service switching, the node changes to the
normal state and the service is switched back to the working path.

1181
OptiX OSN 7500 II/7500/3500/1500

Value
Description
Disabled
If the working path recovers after service switching, the node does not change
its state. Instead, it keeps in the WTR state all the time and the service is not
switched back to the working path.
The node changes to the WTR state only when it recovers from the SD or SF condition. For this
reason, this parameter takes effect only when the node recovers from the SD or SF condition,
but does not take effect when the node recovers from the FS or MS condition.
The default value is Enabled. Use the default value, unless otherwise specified. In this case,
although some packets are lost transiently when the link recovers, less bandwidth is used and
service forwarding efficiency is improved.

A.16.8 RPR Protection Wait-to-restore(s)

Description
The Protection Wait-to-restore(s) parameter specifies the time for the RPR network to change
to the wait-to-restore state and keep in this state for some time (namely, the protection wait-torestore time). When an RPR network recovers from a fault, it does not immediately switch to
the normal state. Instead, it keeps in the switching state. If no fault is detected within the waitto-restore time, the node changes from the WTR state to the normal state, and grooms services
in the loop as normal services.

The value of Protection Wait-to-restore determines the time for restoring a service to the
normal state. It does not affect the system running.
Values
Value Range
Default Value
Unit
0-1440, in a step length of 1
10
Second
Generally, use the default value. If any requirements are proposed by customers, you can set
Protection Wait-to-restore to a proper value according to the requirements and RPR network
status. The value of Protection Wait-to-restore cannot exceed the range allowed in practice.
Issue 03 (2012-11-30)

1182
OptiX OSN 7500 II/7500/3500/1500


This parameter is valid only when RPR Protocol and Protection Restoration Mode are set to
Enabled.
A.16.9 RPR Send link weight

Description
The Send link weight parameter specifies the weight of the send link of an RPR node. It is
classified into the weight of the eastern send link and that of the western send link. The weight
value is valid only for the services whose priority is B_EIR or C. It is invalid for the services
whose priority is A0, A1 or B_CIR. It decides the bandwidth of adding a service whose priority
is B_EIR or C to the ring.
For the services whose priority is B_EIR or C, the fairness algorithm is used to derive the
bandwidth of each service according to the weight value when the RPR is congested. For
example, the traffic rate is 1 Gbit/s respectively for services A and B whose priority is C. If
services A and B pass an RPR network at a rate of 1 Gbit/s, and if their weight value is in
proportion of 7:3, the bandwidth proportion for services A and B is 700 Mbit/s : 300 Mbit/s.

This parameter is invalid if the RPR network is not congested. After the parameter value is
modified, the system operation is not affected.
If the RPR network is congested, and if the parameter value is changed, the traffic of the services
whose priority is B_EIR and C is affected in the RPR network. The greater the weight value,
the heavier the traffic added to the RPR.
Values
Value Range
Default Value
1-255
NOTE
The greater the value, the greater the weight.
Use the default value, unless otherwise specified. That is, if the weight is the same for each node,
the bandwidth of the service in the RPR network is consistent. Otherwise, set the weight value
based on the required bandwidth. The wight values can be separately set for 0 ring and 1 ring.

Issue 03 (2012-11-30)

1183
OptiX OSN 7500 II/7500/3500/1500

A.16.10 RPR Used and Reserved bandwidth of priority A

Description
The Used bandwidth of priority A parameter is divided into two parts: reserved bandwidth of
priority, which is called A0 bandwidth, and the remaining bandwidth, which is called A1
bandwidth. A0 bandwidth is the allocated reserved bandwidth and cannot be reclaimed by other
nodes. Although the local node does not transmit the services whose priority is A, this bandwidth
must be reserved. A1 bandwidth is the allocated committed bandwidth and can be reclaimed by
the services of other priorities, as shown in Table A-10.
Table A-10 RPR service priority
Service Priority
Prior
ity
Applica
tion
SubPriority
Bandwi
dth
Guarant
eed or
Not
Jitter
Bandwid
th Type
Bandwid
th SubType
Adopt
the
Fairne
ss
Algor
ithm
or Not
Realtime
service
A0
Yes
Low
Preallocated
Reserved
No
A1
Yes
Low
Nearreal-time
service
B-CIR
Yes
Middle
Preallocated
Reclaimab
le
B-EIR
No
Wider
Used
randomly
Reclaimab
le
Besteffort
delivery
Service Quality
Yes
The bandwidth is used for the RPR node whose service priority is A. It limits the traffic of the
services whose priority is A in the loop. If the traffic of priority A has the bandwidth that exceeds
the A0 bandwidth, they are transmitted by the A1 bandwidth. If the traffic of priority A has the
bandwidth that exceeds the A1 bandwidth, it is discarded.

The A0 bandwidth is irreclaimable. The proportion of total A0 bandwidth cannot be extremely
large in the RPR network. Otherwise, the bandwidth utilization is affected. If the total A0
bandwidth in the RPR network exceeds the total bandwidth in the RPR network, the services of
priority B or C fail to be transmitted because no bandwidth is available in the RPR network.
Values
The parameter values for A0 and A1 bandwidth are the same and are as follows:
Issue 03 (2012-11-30)

1184
OptiX OSN 7500 II/7500/3500/1500

Value Range
Default Value
Unit
0-Maximum bandwidth in a single ring,

in step length of 1 Mbps
Mbps
The A0 bandwidth can be set within the bandwidth range in the RPR network, but cannot exceed
the bandwidth of the services whose priority is A. The proportion of the total A0 bandwidth
cannot be extremely large in the RPR network. Otherwise, the bandwidth utilization is decreased.
If no service of priority A is available in the RPR network, generally, set the bandwidth to 0 for
the service of priority A. If any service of priority A is available, generally, set the A bandwidth
to 0, and set the bandwidth to the A1 bandwidth for all the services of priority A.

A.16.11 RPR Used bandwidth of priority B-CIR(Mbps)

Description
The RPR Used bandwidth of priority B-CIR(Mbps) parameter specifies the committed
bandwidth for the nodes whose service priority is A in the RPR network. It is also called the
B_CIR bandwidth. If the traffic of priority B has the bandwidth that exceeds the B_CIR
bandwidth, it is transmitted by the B_CIR bandwidth.

Values
Value Range
Default Value
Unit
0-Maximum bandwidth in a single ring,

in step length of 1 Mbps
Mbps
You can plan the B_CIR bandwidth for each node in the RPR network based on the transmitted
near-real-time service traffic. If no service of priority B is available to the nodes in the RPR
network, generally, set the B_CIR bandwidth to 0. The B-CIR bandwidth should not exceed the
total bandwidth in the RPR network.

Issue 03 (2012-11-30)

1185
OptiX OSN 7500 II/7500/3500/1500

A.16.12 RPR Circle Name

Description
The Circle Name parameter specifies the ring number to distinguish the two rings from each
other, including 0 Ring and 1 Ring.
The RPR network is of a topology that consists of two rings in different directions. The external
ring is named Outer Ring (namely, 0 ring), and the internal ring is named Inner Ring (namely,
1 ring). Figure A-42 shows the topology of the RPR network.
Figure A-42 Topology of the RPR network
S1
0 Ring
S2
1 Ring
RPR Network
S0
S3
S5
S4
OptiX NE

Values
Value Range
Default Value
0 Ring, 1 Ring
Issue 03 (2012-11-30)
Value
Description
0 Ring
Indicates the outer ring of the RPR network.
1 Ring
Indicates the inner ring of the RPR network.

1186
OptiX OSN 7500 II/7500/3500/1500

None.

None.
A.16.13 RPR Node Reachability

Description
Reachability indicates the reachability from this node to another RPR node.
l
If the reachability of 0 Ring (or 1 Ring) is Reachable, no fault occurs on the link between
this node and another node on 0 Ring (or 1 Ring). Services of this node can be directly
forwarded to another node on 0 Ring (or 1 Ring).
If the reachability of 0 Ring (or 1 Ring) is Unreachable, a fault occurs on the link between
this node and another node on 0 Ring (or 1 Ring). Services between this node and another
node are unavailable on 0 Ring (or 1 Ring).

Values
Value Range
Default Value
Reachable, Unreachable
Unreachable

Value
Description
Reachable
Indicates that the link between this node and another node on 0 Ring (or
1 Ring) is available.
Unreachable
Indicates that the link between this node and another node on 0 Ring (or
1 Ring) is unavailable.
None.

None.
Issue 03 (2012-11-30)

1187
OptiX OSN 7500 II/7500/3500/1500

A.16.14 RPR Node Hop

Description
RPR node hop indicates the hop from this node to another RPR node. That is, this parameter
indicates the number of nodes from this node to the destination node.
Services are transmitted in the shortest path of the ring network by default. That is, after 0 ring
hop and 1 ring hop between this node and the destination node are compared, the ring ID with
the smallest hop count is chosen as the transmission direction of the service.

Values
Value Range
Default Value
0-255
255 (Indicates an invalid hop.)
When a node is unreachable, the value 255 is displayed indicating that the node hop is invalid.
None.

None.
A.16.15 RPR Adjacent node ID

Description
adjacent node ID indicates adjacent node ID of this node. Every node has two adjacent nodes,
that is, East adjacent node ID and West adjacent node ID.

Values
Issue 03 (2012-11-30)
Value Range
Default Value
1-255

1188
OptiX OSN 7500 II/7500/3500/1500

None.

None.
A.16.16 RPR Node Direction

Description
RPR Node Direction indicates Direction of the RPR node, including East and West to distinct
two directions of the node.
The RPR network is classified into the dual-ring topology. The outer ring is 0 Ring, and the
inner ring is 1 Ring. Figure A-43 shows the ring network topology.
Figure A-43 RPR network topology
S1 East
West
0 Ring
West
S2
East
1 Ring
East
West
RPR Network
S0
S3
S4
S5
West
East
West
East
West
East
OptiX NE
Every node on the RPR network has two directions. East indicates the transmit direction of 0
Ring and the receive direction of 1 Ring, and West indicates the receive direction of 0 Ring and
transmit direction of 1 Ring. Services on 0 Ring are transmitted from West to East, and services
on 1 Ring are transmitted from East to West.

None.
Values
Issue 03 (2012-11-30)
Value Range
Default Value
East, West

1189
OptiX OSN 7500 II/7500/3500/1500


Value
Description
East
East of the node indicates the transmit direction of 0 Ring and the receive
direction of 1 Ring.
West
West of the node indicates the receive direction of 0 Ring and the transmit
direction of 1 Ring.
None.

None.
A.16.17 ECHO Path ID (RPR Node Information)

Description
The ECHO Path ID parameter specifies the ID of the path used for the ECHO function. The
ECHO function is one of the RPR OAM functions. It is used to monitor the connection between
two nodes in the RPR network and to locate any fault.
For the ECHO function, 16 paths are always available on each node. After you configure the
ECHO path ID, a node can initiate the connectivity test for other 16 nodes at the same time.

Values
This parameter is for query only. Each node always has 16 ECHO paths, which are numbered
from 1 to 16.
None.

None.
A.16.18 ECHO Working Mode (RPR Node Information)

Description
ECHO Working Mode indicates the working mode of the ECHO channel, used for determining
whether the ECHO function the ECHO channel is enabled.
Issue 03 (2012-11-30)

1190
OptiX OSN 7500 II/7500/3500/1500

The RPR OAM function is used for the configuration management, fault management and
performance management on the RPR network. The ECHO function is an RPR OAM function,
used for connection monitoring and fault localization of the two nodes on the ring network.
The ECHO frame is an OAM request or response frame. That is, an ECHO request frame is
transmitted from the source address to the destination address. The destination address receives
and resolves the request frame, and then transmits an ECHO response frame to the request node.
The request node analyzes the link connection situation according to the received response
frame.

The value of this parameter has no impact on normal services. After the ECHO function is
enabled, the ECHO frame, however, occupies a small amount of bandwidth of the ring network
and some CPU resources.
Values
Value Range
Default Value
Start, Stop, Clear
Stop

Value
Description
Start
Indicates that the ECHO function of this ECHO channel is enabled. That is, the
source node starts to transmit an ECHO request frame to the destination node.
Stop
Indicates that the ECHO function of this ECHO channel is disabled. That is, the
source node stops transmitting an ECHO request frame to the destination node.
Clear
Indicates that the statistics information about this ECHO channel is cleared. The
statistics information includes the number of ECHO messages that are
transmitted, the number of ECHO messages that are processed successfully, the
number of ECHO messages that are processed unsuccessfully, and whether the
LOC and dLoc alarms are detected.
This parameter is used to determine whether the ECHO function the ECHO channel is enabled.
To test the link connectivity between the two nodes, you need to enable the ECHO function of
the ECHO channel after configuring the parameters of the channel. After the test, disabling the
ECHO function of the ECHO channel to avoid wasting the bandwidth of the ring network and
the CPU recourses.
You are recommended to disable the ECHO function before clearing the statistics information
about the ECHO channel.
Issue 03 (2012-11-30)

1191
OptiX OSN 7500 II/7500/3500/1500


None.
A.16.19 ECHO Request Loop (RPR Node Information)

Description
ECHO Request Loop indicates the transmission direction of the ECHO request frame of the
ECHO channel.

Values
Value Range
Default Value
0 Ring, 1 Ring, Default

Directionality
Default Directionality

Value
Description
0 Ring
Indicates transmitting the ECHO request frame from 0 Ring after the ECHO
function of the ECHO channel is enabled.
1 Ring
Indicates transmitting the ECHO request frame from 1 Ring after the ECHO
Default
Directiona
lity
Indicates that the protocol automatically chooses the shortest path as the transmit
direction of the ECHO request frame.
The ECHO frame is used to test the link connection situation between the two nodes. The user
can specify the transmit direction of the ECHO request frame according to the test requirements.

This parameter is valid only when Working Mode of the ECHO channel is set to Start.
Issue 03 (2012-11-30)

1192
OptiX OSN 7500 II/7500/3500/1500

A.16.20 ECHO Response Loop (RPR Node Information)

Description
ECHO Request Loop indicates the transmission direction of the ECHO response frame of the
ECHO channel.

The value of this parameter has no impact on normal services. After the ECHO function is
enabled, the ECHO frame, however, occupies a small amount of bandwidth of the ring network
and some CPU resources.
Values
Value Range
Default Value
0 Ring, 1 Ring, Default Directionality,

Backward
Default Directionality

Value
Description
0 Ring
Indicates transmitting the ECHO response frame from 0 Ring after the ECHO
1 Ring
Indicates transmitting the ECHO response frame from 1 Ring after the ECHO
Default
Directiona
lity
Indicates that the protocol automatically chooses the shortest path as the transmit
direction of the ECHO response frame.
Backward
Indicates transmitting the ECHO response frame from the direction that is
opposite to the request direction after the ECHO function of the ECHO channel
is enabled.
can specify the transmit direction of the ECHO response frame according to the test
requirements.

Issue 03 (2012-11-30)

1193
OptiX OSN 7500 II/7500/3500/1500

A.16.21 ECHO Frame Service Type (RPR Node Information)

Description
ECHO Frame Service Type indicates the transmission priority of the ECHO frame on the ring
network.

Values
Value Range
Default Value
A0, A1, B, C
A0

Value
Description
A0
Indicates that the ECHO frame is transmitted with priority A0 on the ring
network and occupies bandwidth A (including bandwidths A0 and A1).
A1
Indicates that the ECHO frame is transmitted with priority A1 on the ring
network and occupies bandwidth A (including bandwidths A0 and A1).
Indicates that the ECHO frame is transmitted with priority B on the ring network
and occupies bandwidth B (including bandwidths B_CIR and B_EIR).
Indicates that the ECHO frame is transmitted with priority C on the ring network
and occupies bandwidth C.
can specify ECHO Frame Service Type according to the test requirements. For example, to
test the connectivity of service A0, the user sets ECHO Frame Service Type to A0.

A.16.22 Is ECHO Path Protected (RPR Node Information)

Description
Is Path Protected indicates the protection type of the ECHO frame and is used to determine
how to handle the ECHO frame in the case of a loop switching.
Issue 03 (2012-11-30)

1194
OptiX OSN 7500 II/7500/3500/1500

When the ECHO frame is set to Yes, if the protection status is set to Wrapping or Wrap
and Steering, the ECHO request frame or the response frame that is transmitted in the
channel is switched when the frame passes through a node in the protection switching status;
if the protection status is set to Steering, the ECHO request frame or the response frame
that is transmitted in the channel is discarded when the frame passes through a node in the
protection switching status.
If the ECHO frame is set to NO, the ECHO request or response frame that is transmitted
in the channel is discarded when it passes through a node in the switching status.

Values
Value Range
Default Value
Yes, No
No

Value
Description
Yes
Indicates the ECHO frame is protected.
No
Indicates the ECHO frame is unprotected.
The user can specify Is Path Protected according to the test requirements.

A.16.23 ECHO T1 Transmit Period (RPR Node Information)

Description
ECHO T1 Transmit Period indicates the transmit period of the ECHO frame that is tagged with
time T1. The ECHO frame is classified into the request frame and response frame. If the user
enables an ECHO channel at the NE, an ECHO request frame is transmitted in the channel every
T1.

The occupied bandwidth and CPU resources increase with the decrease in the value of T1
Transmit Period.
Issue 03 (2012-11-30)

1195
OptiX OSN 7500 II/7500/3500/1500

Values
Value Range
Default Value
Unit
100
ms
The user can modify the value of this parameter according to the ring network situation. The
modification should not go beyond the value range.

A.16.24 ECHO T2 Response Time (RPR Node Information)

Description
ECHO T2 Response Time indicates the response timeout of the ECHO frame that is marked
with time T2.

If the node fails to receive the response frame within time T2 after transmitting the ECHO frame,
the node reports the dLoc alarm.
Values
Value Range
Default Value
Unit
100
ms
The user can modify the value of this parameter according to the ring network situation. The
modification should not go beyond the value range.

Issue 03 (2012-11-30)

1196
OptiX OSN 7500 II/7500/3500/1500

A.16.25 Number of Echo Messages Received (RPR Node

Information)
Description
Number of Echo Messages Received indicates the number of ECHO messages that the node
receives. From the time when the node enables the ECHO function, the parameter value increases
by one every time the node receives an ECHO response frame.

Values
For example, the value 100 indicates that the node receives 100 ECHO messages.
None.

None.
A.16.26 Successfully Processed (RPR Node Information)

Description
Successfully Processed indicates the number of ECHO messages that are successfully processed
by the node. The NE starts to count when the ECHO function is enabled at the source node.
After the node transmits an ECHO request frame, the parameter value increases by 1 if the node
receives a correct ECHO response frame within the specified response time.

Values
For example, the parameter value "100" indicates that the node receives 100 ECHO messages
that are processed successfully.
None.

None.
Issue 03 (2012-11-30)

1197
OptiX OSN 7500 II/7500/3500/1500

A.16.27 Unsuccessfully Processed (RPR Node Information)

Description
Unsuccessfully Processed indicates the number of ECHO messages that are unsuccessfully
processed by the node. The parameter value is counted when the ECHO function is enabled at
the source node. After the node transmits an ECHO request frame, the parameter value increases
by 1 if the node fails to receive a correct ECHO response frame within the specified response
time.

Values
For example, the parameter value 100 indicates that the node receives 100 ECHO messages that
are processed unsuccessfully.
None.

None.
A.16.28 dLoc Detected (RPR Node Information)

Description
dLoc Detected indicates an alarm for a link failure. That is, this parameter specifies that the link
communications may be abnormal.
This parameter is used to query whether the node detects the dLoc alarm when the ECHO
function is enabled at the source node. When the node transmits an ECHO request frame, the
node reports the dLoc alarm if the node fails to receive a correct ECHO response frame within
time T2. The node clears this dLoc alarm after the node receives a correct ECHO response frame.

Values
Value Range
Default Value
Yes, No
No

Issue 03 (2012-11-30)

1198
OptiX OSN 7500 II/7500/3500/1500

Value
Description
Yes
Indicates that the node detects the dLoc alarm.
No
Indicates that the node does not detect any dLoc alarm.
None.

None.
A.16.29 Loc Detected (RPR Node Information)

Description
Loc Detected indicates that the link communications is severely abnormal.
This parameter is used to query whether the node detects an LOC alarm when the ECHO function
is enabled at the source node. When the node detects a dLOC alarm, and if the dLOC alarm
persists two seconds, the node reports an LOC alarm. If the node does not receive any dLOC
alarm for 10 seconds, the LOC alarm is cleared.

Values
Value Range
Default Value
Yes, No
No

Value
Description
Yes
Indicates that the node detects an LOC alarm.
No
Indicates that the node does not detect any LOC alarm.
None.
Issue 03 (2012-11-30)

1199
OptiX OSN 7500 II/7500/3500/1500


None.
A.16.30 RPR Node Protection Status

Description
The RPR Node Protection Status parameter specifies the protection request status of the link
in the current direction of the RPR network. The eastern and western RPR nodes respectively
have a protection status.
After the RPR protocol is enabled for a node, it continuously checks the status of the links in
the RPR network. After the RPR protocol checks any protection request status such as signal
fail (SF), signal degrade (SD), forced switching (FS) or manual switching (MS), the current
direction of the RPR network is set to the proper protection status. In the case of the forced
switching or manual switching, if no protection requests are detected or the protection request
is cleared, this direction of the RPR network is set to IDLE. In the case of SF or SD, if no
protection requests are detected or the protection request is cleared, this direction of the RPR
network is set to IDLE when the WTR time expires.

Values
Value Range
Default Value
Force Switching, SF, SD, Manual Switching,

Wait-to-Restore, Idle
Idle
Issue 03 (2012-11-30)
Value
Description
Force
Switching
Indicates that the RPR node is in the forced switching status.
SF
Indicates that the RPR node is in the automatic switching status resulted from
the signal fail (SF) condition.
SD
Indicates that the RPR node is in the automatic switching status resulted from
the signal degrade (SD) condition.
Manual
Switching
Indicates that the RPR node is in the manual switching status.
Wait-toRestore
Indicates that the RPR node is in the Wait-to-Restore status.
Idle
Indicates that the RPR node is in the Idle status.

1200
OptiX OSN 7500 II/7500/3500/1500

These switching request signals have the priorities from high to low: FS, SF, SD, MS, WTR,
IDLE. The FS and SF have the highest and equal priorities. That is, FS and SF can preempt
switching signals of each other. The switching signals of higher priorities can preempt the
switching signals of lower priorities. The switching schemes whose priority is higher than SF
can be used to protect the RPR network at the same time. The switching schemes whose priority
is lower than SF should not be used in the RPR network at the same time. The switching request
of higher priorities contends the switching request of lower priorities. The RPR node can change
to the WTR status only when it recovers from the SD or SF status.
None.

None.
A.16.31 RPR Node Switching Status

Description
The RPR Node Switching Status parameter specifies the switching status of an RPR node. In
the eastern and western directions of a node, a switching status is available to show whether the
link in the current direction of the RPR network is normal.

Values
Value Range
Default Value
Not switched, Switched
Not switched

Value
Description
Not switched
Indicates that the node is not in the switching status in this direction.
Switched
Indicates that the node is in the switching status in this direction.
None.

None.
Issue 03 (2012-11-30)

1201
OptiX OSN 7500 II/7500/3500/1500

A.16.32 RPR Node Accumulated Protection Times

Description
The Accumulated Protection Times parameter specifies the accumulated protection count of
a node, which is also called accumulated switching count. The count starts after the RPR protocol
is enabled on the node. The count is added by 1 when the switching occurs once. The accumulated
protection count in the eastern direction of the node is separate from that in the western direction
of the node.

Values
For example, if the displayed value is 10, the accumulated protection count is 10 after the RPR
protocol is enabled on the node.
None.

None.
A.16.33 RPR Node Accumulated Protection Time

Description
The Accumulated Protection Time parameter specifies the accumulated protection time. The
count starts after the RPR protocol is enabled on the node. When a switching occurs, the duration
from the start time to the end time is recorded. This parameter value is derived from accumulation
of all the duration. The accumulated protection time in the eastern direction of the node is
separate from that in the western direction of the node.

Values
For example, if the displayed value is 10, the accumulated protection duration is 10 seconds
after the RPR protocol is enabled on the node.
None.
Issue 03 (2012-11-30)

1202
OptiX OSN 7500 II/7500/3500/1500


None.
A.16.34 RPR Node Last Switch Request

Description
The Last Switch Request parameter specifies the last switching request of a node.

Values
Value Range
Default Value
Force Switching, Manual Switching, Idle
Idle

Value
Description
Force Switching
Indicates that the last switching request issued to the node is a forced
switching.
Manual Switching
Indicates that the last switching request issued to the node is a

manual switching.
Idle
Indicates that no switching request is issued to the node. This is the

default value.
None.

None.
A.16.35 RPR Switch Request

Description
RPR Switch Request indicates the type of a protection request that is issued to the node,
including Force Switching, Manual Switching and Clear. This operation can be performed on
the east node and west node of this node.
Issue 03 (2012-11-30)

1203
OptiX OSN 7500 II/7500/3500/1500


When the user issues a switching request to the node, the services that are forwarded by this
node are interrupted transiently with a packet loss time less than 50 ms.
If the protection mode is set to Steering, the service interruption time can be less than 50 ms
when the number of nodes on the ring is not more than 16.
Values
Value Range
Default Value
Force Switching, Manual Switching, Clear

Value
Description
Force Switching
When adding a node to the ring network, you need to protect the current
services. Because the link is normal, a switching cannot be performed
automatically but can be performed forcibly only. This protection
request is with the highest priority and cannot be preempted by other
protection requests on the ring network.
Manual Switching
Indicates performing a switching in 0 Ring or 1 Ring. But services can

be switched back when a more severe link failure occurs on the ring
network.
Clear
Indicates clearing the forced switching and manual switching.
Usually, the protection request is required only when the network topology changes. The user
can determine whether to issue the switching request to the node according to the actual situation.
If the user allows the switching request to be preempted by the SF/SD, a manual switching
request is issued. Make sure that all switchings at this node are cleared after all the operations
are completed.

A.17 LAG Associated Parameters (TDM Mode)

This topic describes the parameters that are used for enabling the LAG function.
Issue 03 (2012-11-30)

1204
OptiX OSN 7500 II/7500/3500/1500

A.17.1 LAG Type(Link Aggregation Group Management)

Description
The LAG Type parameter can be set to Manual or Static. In the case of the manual LAG, the
LACP protocol is not enabled. In the case of the static LAG, the LACP protocol is enabled and
protocol packets are exchanged. The protocol state machine determines whether the port can
carry services.

As the LACP protocol is not enabled for the manual LAG, the LAG Type parameter should be
set to Manual for the interconnected ports. In addition, the Load Sharing and Revertive
Mode parameters should be set as the same for the interconnected ports. Otherwise, the working
ports do not belong to the same link and services are interrupted.
If the manual LAG works in the full-duplex mode and a unidirectional fiber cut occurs, the
services are interrupted.
When a static LAG is initially created, the services are interrupted until the two ends negotiate
and determine a port that can carry the services.
Values
Value Range
Default Value
Manual, Static
Static

Value
Description
Manual
The LACP protocol is not enabled. The link status, rate, and
duplex mode of a port determine whether the port can carry
services.
Static
The LACP protocol is enabled and protocol packets are

exchanged. The protocol state machine determines whether
the port can carry services.
If the user does not require the LACP protocol, set the LAG Type parameter to Manual.
If the user requires the LACP protocol and the two ends use the LACP protocol, set the LAG
Type parameter to Static.

None.
Issue 03 (2012-11-30)

1205
OptiX OSN 7500 II/7500/3500/1500

Related Information
None.
A.17.2 Revertive Mode(Link Aggregation Group Management)

Description
In the case of the link aggregation group (LAG) that does not share the load, the Revertive
Mode parameter specifies whether the services are switched after the original working port
recovers. Revertive and Non-Revertive are available for this parameter.

If the Revertive Mode parameter is set to Revertive, the services are switched after the port
with the highest priority recovers. During the switching, the services are transiently interrupted
for not more than 3s.
Values
Value Range
Default Value
Non-Revertive

Value
Description
Revertive
After the original working port recovers, the services are

switched to this port.
Non-Revertive
After the original working port recovers, the services are not
switched.
To switch the services only when the service-carried port fails, set the Revertive Mode
parameter to Non-Revertive.
To ensure that only the port with the highest priority carry services whenever the port is fine,
set the Revertive Mode parameter to Revertive.

The Revertive Mode parameter is valid only when the Load Sharing parameter is set to NonSharing.
Related Information
None.
Issue 03 (2012-11-30)

1206
OptiX OSN 7500 II/7500/3500/1500

A.17.3 Load Sharing(Link Aggregation Group Management)

Description
The Load Sharing parameter indicates whether multiple ports are allowed to carry the services
at the same time when multiple ports in the aggregation group can be used.

In Non-Sharing mode, only the port with the highest priority in the link aggregation group
carries the service and the other port functions as backup port.
In Sharing mode, multiple ports can carry the services at the same time.
When manually configuring the aggregation group, ensure that the load sharing modes at both
ends are same. Otherwise, certain service packets are lost.
Values
Value Range
Default Value
Non-Sharing

Value
Description
Non-Sharing
Indicates that only one port carries the services. Only one
slave port can be configured.
Sharing
Indicates that multiple ports are allowed to carry the services

at the same time. A maximum of 15 slave ports can be added.
When manually configuring the aggregation group, configure the load sharing modes at the two
ends to the same. Otherwise, certain service packets are lost.

None.
Related Information
None.
Issue 03 (2012-11-30)

1207
OptiX OSN 7500 II/7500/3500/1500

A.17.4 Load Sharing Hash Algorithm(Link Aggregation Group

Management)
Description
The Encapsulation Type parameter indicates the traffic distribution algorithm for different
ports in the aggregation group.

If multiple ports in the aggregation group can carry the services, the traffic distribution effect
varies with the Hash algorithms configured. If the Hash algorithm is properly configured, the
traffic on each port is evenly distributed. Otherwise, the traffic is not evenly distributed, and the
port bandwidth cannot be fully used.
Values
Value Range
Default Value
Automatic, Source MAC, Destination MAC,

Source and Destination MACs
Automatic

Value
Description
Automatic
The traffic is distributed among ports according to the source and

destination MACs of the packets.
Source MAC
The traffic is distributed among ports according to the source

MAC of the packets.
Destination MAC
The traffic is distributed among ports according to the destination

MAC of the packets.
Source and Destination

MACs
The traffic is distributed among ports according to the source and

destination MACs of the packets.
To evenly distribute the traffic on each port as possible, select a proper Hash algorithm according
to different packets on the ports.

This parameter is valid only when Load Sharing is set to Non-Sharing.
Issue 03 (2012-11-30)

1208
OptiX OSN 7500 II/7500/3500/1500

A.17.5 System Priority(Link Aggregation Group Management)

Description
The System Priority parameter indicates the priority level of a link aggregation group (LAG).
This parameter affects the working state of the member ports in the LAG.

When the LAG at the local end negotiates with the LAG at the opposite end by using the LACP
packets, the LAGs can obtain the system priority information of each other. The result computed
by the selection logic of the LAG with the higher priority is considered as the common result
for both LAGs. If the two LAGs have the same system priority, the system MAC addresses of
the two LAGs are compared. The LAG with the lower MAC address is adopted.
The system priority increases as the value decreases.
Values
Value Range
Default Value
0-65535, 1 as the spacing
32768
To adopt the result computed by the selection logic of a static LAG, set a higher system priority
for this static LAG.

The System Priority (Link Aggregation) parameter is valid only when the LAG Type
parameter is set to Static.
Related Information
None.
A.17.6 Main Port(Link Aggregation Group Management)

Description
The Main Port parameter indicates the LAG member port available for creating services. Each
LAG has only one main port.

Issue 03 (2012-11-30)

1209
OptiX OSN 7500 II/7500/3500/1500

Values
Value Range
Default Value
For example, 3-PEG16-1(PORT-1)
Every Ethernet port on the NE can be used as the main port.
The main port and the slave port must be of the same type. The rate of the main port must be
the same as the rate of the slave port.

None.
Related Information
None.
A.17.7 Main Port Status(Link Aggregation Group Management)

Description
The Main Port Status parameter indicates the port status computed by the selection logic for
the LAG.

If one port is in the out-of-service state, the service cannot be loaded on this port.
If a port is in the in-service state, the service can be loaded on this port.
Values
Value Range
Default Value
In Service, Out of Service
Unknown
Issue 03 (2012-11-30)
Value
Description
In Service
Indicates that the port can be added to an LAG and can carry
the service.
Out of Service
Indicates that the port cannot be added to an LAG and cannot

carry the service.

1210
OptiX OSN 7500 II/7500/3500/1500

This parameter is used for query only. No rule is specified for selecting a value.

In the case of the static LAG, the LACP protocol is used. The port status depends on the port
working mode, port working rate, port priority, and LAG priority.
In the case of the manual LAG, the LACP protocol is not used. The port status depends on the
port working mode and port working rate.
Related Information
None.
A.17.8 Port Priority(Link Aggregation Group Management)

Description
The Port Priority parameter indicates the priority of the Ethernet port. If other attributes, such
as the port rate and port working mode, are the same, in the LAG member ports that enable the
LACP protocol, the port with a higher priority carries services first. This parameter is invalid
for the LAG (manual LAG, for example) that does not run the LACP protocol.

Values
Value Range
Default Value
0-65535
32768
The port priority increases as the value decreases.
To make a port carry services with priority, set the priority of the port to a higher value.

In a LAG, which port has the priority to carry services is jointly determined by Port Priority
and System Priority of the LAG, and is first determined by System Priority.
For example, as shown in Figure A-44, the non-load sharing static LAG is created between NE
A and NE B.
Issue 03 (2012-11-30)

1211
OptiX OSN 7500 II/7500/3500/1500

Figure A-44 Non-load sharing static LAG is created between NE A and NE B
NEA
Port 1
Working
Port 1
NEB
Port 2
Port 2
Protection
LAGa
LAG b
Each port of LAG a and LAG b meets the requirements of carrying services. System Priority
of LAG a is higher than System Priority of LAG b. In LAG a, Port Priority of port1 is higher
than Port Priority of port2. In LAG b, Port Priority of port2 is higher than Port Priority of
port 1.
In this case, in LAG a, port1 is the working port, port2 protects port1, and port2 does not share
the service traffic. The protection relation in LAG b is the same as the protection relation in LAG
a, because System Priority of LAG a is higher than System Priority of LAG b. That is, in LAG
b, port1 is the working port, port2 protects port1, and port2 does not share the service traffic,
even if Port Priority of port2 is higher than Port Priority of port1 in LAG b.
Related Information
For the setting of this parameter, see System Priority.
A.18 MC-LAG Associated Parameters

This topic describes the parameters for configuring MC-LAG protection.
A.18.1 Protocol Channel ID

Description
The Protocol Channel ID parameter specifies the ID of the protocol channel when the MCSP
channel is created. This parameter can be allocated automatically.

Issue 03 (2012-11-30)

1212
OptiX OSN 7500 II/7500/3500/1500

Values
Value Range
Default Value
1-15
You need to enter this parameter when creating MCSP channels. This parameter also can be

None.
A.18.2 Hello Packet Sending Interval (s)

Description
The Hello Packet Sending Interval (s) parameter specifies the interval at which the Hello
packets are transmitted to the opposite end to check whether the link is normal.

Values
Value Range
Default Value
Unit
1-10
Second
This parameter must be set according to the network planning and requirements. Generally, the
smaller the value of this parameter, the shorter the interval (s) for transmitting Hello packets to
the opposite end, and the faster the speed of detecting whether the link is normal.

None.
A.18.3 Timeout Time (s)

Description
The Timeout Time (s) parameter is used for checking whether the configuration messages time
out.
Issue 03 (2012-11-30)

1213
OptiX OSN 7500 II/7500/3500/1500

When the value of Timeout Time (s) of received Hello messages exceeds the specified threshold,
the opposite end is faulty and the relevant alarm is reported.

Values
Value Range
Default Value
Unit
30-3600
600
Second
You need to set this parameter according to the network planning and requirement. This
parameter is related to the Hello Interval parameter set on the opposite end. The smaller the
value of this parameter, the faster the speed of detecting a fault on the link.

None.
A.19 LAG/DLAG Associated Parameters (TDM Mode)

This topic describes the parameters for configuring a link aggregation group (LAG) and a
distributed link aggregation group (DLAG).
A.19.1 Port Priority (Link Aggregation)

Description
The Port Priority (Link Aggregation) parameter specifies the priority of the ports in the link
aggregation group of the LACP protocol. The port priority can be set. It indicates the priority
level of a port to be aggregated. If a port is of higher priority, this port is preferred to carry the
services. If a link aggregation group (for example, manual aggregation group) does not run the
LACP protocol, it does not take effect after the port priority is set.

If other conditions (for example, port rate, and port working mode) are the same, a port of higher
priority is preferred to carry the services.
Values
Issue 03 (2012-11-30)
Valid Values
Default Value
32768

1214
OptiX OSN 7500 II/7500/3500/1500

If the value of Port Priority is smaller, the priority is higher.
When using a port to carry the services, set Port Priority to a smaller value. Otherwise, set Port
Priority to a greater value.

The member port state in the link aggregation group is decided according to these parameters,
such as port working mode, port working rate, whether the port receives LACP packets, port
priority, and LAG priority.
A.19.2 System Priority (Link Aggregation)

Description
The System Priority (Link Aggregation) parameter specifies the priority level of a link
aggregation group. It may affect the working state of the member ports in the link aggregation
group.

When the link aggregation groups at the local and opposite ends negotiate with each other by
sending LACP packets, they can get the system priority of the link aggregation groups from each
other. The result selected at the end of higher priority is taken as the result for the two ends. If
the system priority of the link aggregation group is the same at the two ends, the system MAC
addresses are compared. A MAC address is used if it is of lower value.
If the value of System Priority is smaller, the system priority of the link aggregation group is
higher.
Values
Valid Values
Default Value
32768
To take the result selected by the static link aggregation group as the actual value, set System
Priority to a smaller value.

The member port state in the link aggregation group is decided according to these parameters,
such as port working mode, port working rate, whether the port receives LACP packets, port
priority, and system priority.
Issue 03 (2012-11-30)

1215
OptiX OSN 7500 II/7500/3500/1500

A.19.3 Slave Port (Link Aggregation)

Description
The Slave Port (Link Aggregation) parameter specifies that a link aggregation group is
manually created rather than being automatically created by the system. A link aggregation group
contains main ports and slave ports. The slave ports in a link aggregation group are fixed. Unless
they are manually modified, the system does not automatically add them to or delete them from
the link aggregation group.

A main port can be added to the link aggregation group, regardless of the service. A slave port
can be, however, added to the link aggregation group only if no services are available. After
being added to the link aggregation group, a slave port cannot be configured with any services.
Values
Board Name
Value Range
Default Value
N1EAS2
PORT1-PORT2
VCTRUNK1-VCTRUNK34
N1EGS4, N3EGS4, N4EGS4
PORT1-PORT4
N1EMS4
PORT1-PORT20

Value
Description
Available Slave Ports
Indicates the number of the physical port that can be set

to the slave port.
Indicates the number of the physical port that is already

set to the slave port.
Add the relevant slave port to the link aggregation group as required. The maximum number of
slave ports differs with the board type.
Board
Issue 03 (2012-11-30)
Maximum Number of Slave Ports

Sharing
Non-Sharing
N1EAS2
23
N1EGS4, N3EGS4,
N4EGS4
15

1216
OptiX OSN 7500 II/7500/3500/1500

Board
Maximum Number of Slave Ports
N1EMS4
Sharing
Non-Sharing
15

A port can be aggregated only when the maximum frame length is consistent.
Moreover, all the ports in the link aggregation group must be on the same processing board or
on the relevant interface board.
A.19.4 Status (Link Aggregation)

Description
The Status (Link Aggregation) parameter specifies the state, which is derived from logical
computation, of each member ports in a link aggregation group.

When a port is not configured with services, this port can be added to a link aggregation group.
If this port is in service in this link aggregation group, this port can share the service. If this port
is out of service in this link aggregation group, this port cannot share the service.
When a port is already configured with services, this port cannot be added to a link aggregation
group and cannot share the service.
Values
Valid Values
Default Value
Unknown, In Service, Out of Service
Unknown
Value
Description
Unknown
Indicates that the link aggregation group is not queried.
In Service
Indicates that the port can carry the service.
Out of Service
Indicates that the port cannot carry the service.
This parameter is used for query only. No rules are provided for selecting a value.
Issue 03 (2012-11-30)

1217
OptiX OSN 7500 II/7500/3500/1500


l
For static link aggregation, the LACP protocol is used. The member port state in the link
aggregation group is decided by these parameters, such as port working mode, port working
rate, port priority, and link aggregation group priority.
For manual link aggregation, the LCAP protocol is not used. The member port state in the
link aggregation group is not related to these parameters, such as port working mode and
port working rate.
A.19.5 Branch Port

Description
The Branch Port parameter specifies that a link aggregation group is created manually rather
than automatically. A link aggregation group consists of main ports and branch ports. Branch
ports in a link aggregation group are fixed. Unless they are manually modified, the system does
not automatically add them to or delete them from a link aggregation group.

Regardless of services, a main port can be added to a link aggregation group. A branch port can
be added to a link aggregation group only when it is not configured with any services. After
being added to a link aggregation group, a branch port cannot be configured with any services.
Values
Board Name
Valid Values
Default Value
N2EGR2, N2EGS2,
N3EGS2
PORT1-PORT2
N2EFS4, N3EFS4
PORT1-PORT4
N2EFS0, N4EFS0, N5EFS0
PORT1-PORT8
N2EMR0
PORT1-PORT13
N1EFS0A
PORT1-PORT16
N1EMS2
PORT1-PORT18
Issue 03 (2012-11-30)
Value
Description
Available Branch Port
Indicates the number of the physical port that can be set

to a branch port.
Selected Branch Port
Indicates the number of the physical port that is already

set to a branch port.

1218
OptiX OSN 7500 II/7500/3500/1500

Add a relevant branch port to a link aggregation group as required.

Ports can be added to a link aggregation group only when their physical attributes are consistent
with each other, including Working Mode, Flow Control Mode and Max. Packet Length.
The link aggregation function can be configured only when the broadcast packet suppression
function is disabled. All the ports in a link aggregation group must be on the same processing
board or on the relevant interface board.
A.19.6 Load Sharing(Ethernet Link Aggregation)

Description
The Load Sharing parameter specifies the load sharing mode of an aggregation group.

Different load sharing modes have different effects. In load sharing mode, the ports in the
aggregation group can share the service. In load non-sharing mode, only one port in the
aggregation group can carry the service and the other port provides protection.
Values
Value Range
Default Value
Sharing

Value
Description
Sharing
Indicates that the ports in the aggregation group share the

service.
Non-Sharing
Indicates that the ports in the aggregation group do not share

the service. Only one port in the aggregation group carries the
service.
If the bandwidth needs to be increased and several ports need to be enabled to share the service,
select the load sharing mode. If only one port needs to carry the service and protection is required
for this port, select the load non-sharing mode.
Issue 03 (2012-11-30)

1219
OptiX OSN 7500 II/7500/3500/1500

A.19.7 Revertive Mode (DLAG)

Description
The Revertive Mode (DLAG) parameter specifies whether to switch a service back to the main
board that recovers from a fault.
l
If the service needs to be switched back to the main board, set Revertive Mode to
Revertive.
If a service need not be switched back to the main board and is still transmitted at the slave
board, set Revertive Mode to Non-Revertive.

If Revertive Mode is set to Revertive, the service is switched back to the main board that
recovers from a fault.
For each switching event, the transient interruption time of the service is less than three seconds.
Values
Valid Values
Default Value
Revertive
l
To avoid frequent switching and to switch the service only when the working board port
fails, select Non-Revertive.
If the user requires that the main port carries the service if it works normally, select
Revertive.

None.
A.19.8 Main Port Priority (DLAG)

Description
The Main Port Priority (DLAG) parameter specifies the priority of the main port in a distributed
link aggregation group (DLAG). A port of higher priority is preferred to carry the services.

If other conditions (such as port rate and port working mode) are the same, modifying the port
priority may cause service switching and interruption.
Issue 03 (2012-11-30)

1220
OptiX OSN 7500 II/7500/3500/1500

Values
Valid Values
Default Value
0-65535
32768
To enable a port to be preferred to carry the services, set Port Priority to a smaller value.
Otherwise, set Port Priority to a greater value.
For a DLAG, to enable the main port to be preferred to carry the services, set the priority of the
main port in the DLAG higher than that of the slave port.

A DLAG uses the LACP. The working state of a member port in a link aggregation group is
decided by these parameters such as port working mode, port rate, port priority, and link
aggregation group priority.
If Revertive Mode is set to Non-Revertive, the set port priority does not take effect.
A.19.9 Slave Port Priority (DLAG)

Description
The Slave Port Priority (DLAG) parameter specifies the priority of the slave port in a DLAG.
The priority is specified in the LACP. A port of higher priority is preferred to carry the services.

If other conditions (such as port rate and port working mode) are the same, modifying the port
priority may cause service switching and interruption.
Values
Valid Values
Default Value
0-65535
32768
To enable a port to be preferred to carry the services, set Port Priority to a smaller value.
Otherwise, set Port Priority to a greater value.
For a DLAG, to enable the slave port to be preferred to carry the services, set the priority of the
slave port in the DLAG higher than that of the main port.
Issue 03 (2012-11-30)

1221
OptiX OSN 7500 II/7500/3500/1500


A DLAG uses the LACP. The working state of a member port in a link aggregation group is
decided by these parameters such as port working mode, port rate, port priority, and link
aggregation group priority.
If Revertive Mode is set to Non-Revertive, the set port priority does not take effect.
A.20 STP/RSTP Associated Parameters

This topic describes the parameters for configuring the Spanning Tree Protocol (STP) and the
Rapid Spanning Tree Protocol (RSTP).
A.20.1 Protocol Enabled (Spanning Tree)

Description
Protocol Enabled (Spanning Tree) indicates whether the spanning tree protocol is enabled on
the VB.

After the protocol is enabled and when the computation of the spanning tree is performed
according to the protocol type (STP/RSTP), the network topology changes and services are
interrupted temporarily.
Values
Value Range
Default Value
Enabled, Disabled
Disabled
The user can set this parameter according to the actual service requirement.

This parameter can be set only when the VB is created and Protocol Type is selected.
Related Information
The rapid spanning tree protocol (RSTP) can realize all the functions of the spanning tree. Similar
to the STP, the RSTP avoids temporary loops. Different from the STP, the RSTP shortens the
time delay at the ports from blocking to forwarding, restores the network connectivity more
rapidly, and provides better services.
Issue 03 (2012-11-30)

1222
OptiX OSN 7500 II/7500/3500/1500

A.20.2 Protocol Type (Spanning Tree Protocol)

Description
Protocol Type (Spanning Tree) indicates that the Ethernet data board of the OptiX OSN
equipment supports two spanning tree protocols, that is, the spanning tree protocol (STP) and
the rapid spanning tree Protocol (RSTP).
l
The STP is a Layer 2 management protocol that avoids Layer 2 loops by selectively
blocking redundant network links and supports the link backup.
The RSTP develops from the STP and shortens the convergence time.

If this parameter is changed incorrectly, a network topology oscillation may occur and services
are severely affected.
Values
Value Range
Default Value
STP, RSTP
RSTP
The RSTP and STP can be configured at the same time. The RSTP is compatible with the STP.
It is recommended that you use the default value RSTP.

None.
A.20.3 VB Priority (Bridge Parameters)

Description
VB Priority (Bridge Parameters) indicates the fixed parameters of the bridge, used for
selecting the role of the bridge and computing the topology of the spanning tree. As the value
of the parameter decreases, the VB priority increases and the bridge is more likely to be selected
as a root bridge.

Changing the value of VB Priority may affect the selection of a root bridge, which may finally
affect the entire network topology.
Issue 03 (2012-11-30)

1223
OptiX OSN 7500 II/7500/3500/1500

Values
Value Range
Default Value
32768
Set this parameter according to what role the user expects the bridge to play in the spanning tree
topology.

None.
A.20.4 Max Age(s)

Description
The Max Age(s) parameter specifies the maximum life cycle of the configuration message. A
configuration message contains the message aging time and maximum aging time of the
message. The maximum life cycle of the configuration message is equivalent to the maximum
aging time of the message.

If the message aging time exceeds the maximum aging time of the message, the received message
is discarded and the port that receives the message becomes a designated port.
Values
Value Range
Default Value
Unit
6-40
20
When you set the value of this parameter, ensure that the following requirement is met:
2 x (Hello Time + 1) Max Age 2 x (Forward Delay - 1)

This parameter is related to the Hello Time and Forward Delay parameters. For details, refer
to the principles for setting these parameters.
Issue 03 (2012-11-30)

1224
OptiX OSN 7500 II/7500/3500/1500

A.20.5 Hello Time(s) (Spanning Tree)

Description
The Hello Time(s) parameter specifies the transmission period of the message.
The bridge time consists of the following parts: forward delay of the bridge, handshake time of
the bridge, maximum bridge aging time, and message aging time (0). The Hello Time parameter
is equivalent to the bridge handshake time.

This parameter ensures the stable operation of the STP.
Values
Value Range
Default Value
Unit
1-10
2 x (Hello Time + 1) Max Age 2 x (Forward Delay - 1)

This parameter is related to the Max Age and Forward Delay parameters. For details, refer to
the principles for setting these parameters.
A.20.6 Forward Delay(s) (Spanning Tree)

Description
The Forward Delay(s) parameter specifies the delay of the port state migration.
This parameter is actually a timer that is used by the ports in the listening state and in the learning
state to control the migration from the listening state to the learning state and the migration from
the learning state to the forwarding state. The timer is started when the port enters the listening
state. When the timer expires, the port automatically migrates to the learning state and the timer
is started again. When the timer expires the second time, the port automatically migrates to the
forwarding state and the timer is stopped.

The restoration time of the service from the learning state to the forwarding state is affected.
Issue 03 (2012-11-30)

1225
OptiX OSN 7500 II/7500/3500/1500

Values
Value Range
Default Value
Unit
4-30
15
2 x (Hello Time + 1) Max Age 2 x (Forward Delay - 1).

This parameter is related to the Hello Time and Max Age parameters. For details, refer to the
principles for setting these parameters.
A.20.7 TxHoldCount(per second) (Spanning Tree)

Description
The TxHoldCount(per second) parameter enables the transmission state machine of the port
to specify the maximum transmission rate of the BPDU packet.

This parameter ensures that the number of the BPDU packets transmitted within a period of hello
time does not exceed the preset value.
Values
Value Range
Default Value
1-10 times/s
Set this parameter according to the actual requirement of the user. It is recommended that you
use the default value.
A.20.8 Root Path Cost

Description
Each bridge has the root path cost. The root path cost of the root bridge is equal to 0. In the case
of non-root bridges, the root path cost of each bridge is equal to the sum of path cost values of
each port on the other bridges that a non-root bridge passes when the bridge receives the frame
from the root bridge along the minimum cost path. The path cost of each port can be managed.
The network segment in each LAN has the root path cost. The root path cost of the network
segment is equal to the root path cost of the bridge whose cost is the smallest among all the
Issue 03 (2012-11-30)

1226
OptiX OSN 7500 II/7500/3500/1500

bridges that are connected to the network segment through the bridge ports. In this case, the
bridge whose cost is the smallest is selected as the designated bridge. If the root path cost values
of two or more bridges are the same and the smallest, the bridge with a higher priority is selected
as the root bridge.
In the case of non-root bridges, the root path cost of each bridge is equal to the sum of path cost
values of each port on the other bridges that a non-root bridge passes when the bridge receives
the frame from the root bridge along the minimum cost path. That is, the value of the root path
cost is the sum of the path cost values of all bridges.

The root path cost can determine the designated bridge and the service flow in the STP.
Values
Based on the protocol, the value of this parameter is calculated according to the network
topology. This parameter is used for querying.
There are no principles for setting the value of this parameter because this parameter is used for
querying.
A.20.9 Hold Count (Spanning Tree)

Description
The Hold Count parameter indicates the maximum number of BPDUs that are actually
transmitted within a period of hello time.

The system is not affected because this parameter is used to check the counter of the BPDU
packet.
Values
This parameter is used for querying.
There are no principles for setting the value of this parameter because this parameter is used for
querying.
A.20.10 Port ID
Description
The Port ID parameter contains 16 bits, which show the port priority and the unique port number
in the bridge. The first eight bits indicate the port priority, and the later eight bits indicate the
port number. The port ID represents the priority in the spanning tree. If the value of the port ID
is smaller, the port priority in the bridge is higher. To enable the RSTP to be compatible with
Issue 03 (2012-11-30)

1227
OptiX OSN 7500 II/7500/3500/1500

the STP, the port priority is represented by eight bits, of which the later four bits are 0 for easy
management.

This parameter is for query only. The system is not affected.
Values
The parameter value is in decimal system. For example, Port ID = 32769.

You can change the parameter value by setting the port priority. In this case, however, the
topology of the spanning tree may be rearranged.
If the port priority is smaller, the port ID is smaller. When the port priorities are the same, the
port ID is smaller if the port number is smaller.
A.20.11 Port Path Cost

Description
The Port Path Cost parameter is used for computation of the spanning tree state machine. Based
on the port path cost, you can compute the root path cost at the port of the switch. Each bridge
has a root path cost, namely, the cost of the path from the root bridge to the local bridge. The
path cost of each port can be set through the management module. For a root bridge, the root
path cost is 0. For Port Path Cost, the recommended values, which are decided by the MAC
type and the transmission rate.are shown in Table A-11. The recommended values for RSTP
are the same as those for STP.
Table A-11 Recommended values of the port path cost
Issue 03 (2012-11-30)
Parameter
Link Speed
Recommende
d value
Recommende
d range
Range
Path Cost
<=100 Kb/s
200000000
20000000-2000
00000
1-200000000
1 Mb/s
20000000
2000000-20000
0000
1-200000000
10 Mb/s
2000000
200000-200000
00
1-200000000
100 Mb/s
200000
20000-2000000
1-200000000
1 Gb/s
20000
2000-200000
1-200000000
10 Gb/s
2000
200-20000
1-200000000
100 Gb/s
200
20-2000
1-200000000
1 Tb/s
20
2-200
1-200000000

1228
OptiX OSN 7500 II/7500/3500/1500

Parameter
Link Speed
Recommende
d value
Recommende
d range
Range
10 Tb/s
1-20
1-200000000

After this parameter is modified, the protocol conducts the computation again based on the
modified value. Consequently, the network topology may be changed.
Values
Board Name
Value Range
Default Value
N4EFS0, N2EFS4,
N2EGS2, N2EMR0,
N2EGR2, N1EMS4,
N1EGS4, N3EGS4,
N1EAS2
1-200000000
l 19 (FE port)
l 4 (GE port)
l 2 (VCTRUNK, 10 GE
and RPR ports)
If the port rate is greater, the port path cost is smaller. Generally, use the default value.

None.
A.20.12 Designated Path Cost

Description
The Designated Path Cost parameter is applicable to the port and is used for the state machine
calculation of the spanning tree. Based on the port path cost, you can calculate the root path cost
of the port of the switch. The root path cost is equal to 0 in the case of a root bridge. In the case
of other bridges, the root path cost of the bridge refers to the path cost from the root bridge to
this bridge. The root path cost is the sum of the minimum root path cost of the port on this bridge
and the path cost of this port. The path cost of each port can be set through the management
module. Table A-12 shows the recommended values of the port path cost. The values are
generally related to the MAC type and transmission rate.
Table A-12 Recommended values of the port path cost
Issue 03 (2012-11-30)
Parameter
Link Speed
Recommende
d value
Recommende
d range
Range
Path Cost
<=100 Kb/s
200000000
20000000-2000
00000
1-200000000

1229
OptiX OSN 7500 II/7500/3500/1500

Parameter
Link Speed
Recommende
d value
Recommende
d range
Range
1 Mb/s
20000000
2000000-20000
0000
1-200000000
10 Mb/s
2000000
200000-200000
00
1-200000000
100 Mb/s
200000
20000-2000000
1-200000000
1 Gb/s
20000
2000-200000
1-200000000
10 Gb/s
2000
200-20000
1-200000000
100 Gb/s
200
20-2000
1-200000000
1 Tb/s
20
2-200
1-200000000
10 Tb/s
1-20
1-200000000

This parameter affects the calculation of the root path cost based on the STP and hence affects
the service flow in the spanning tree.
Values
Value Range
Default Value
1-65535

Value
Description
1-65535
Indicates the cost required by the transmission of the bridge port.
If the port rate is greater, the designed path cost is smaller. It is recommended that you use the
default value.
A.20.13 Designated Root Bridge Priority

Description
The Designated Root Bridge Priority parameter indicates the priority of the root bridge that
is selected based on the STP. The selection is based on the bridge IDs in a network. A bridge
Issue 03 (2012-11-30)

1230
OptiX OSN 7500 II/7500/3500/1500

ID consists of the priority and MAC address of the bridge. The bridge whose ID is the smallest
is selected as the root bridge in this network.

This parameter is used for querying. It indicates the priority of the current root bridge and may
change in the case of a spanning tree topology change.
Values
Value Range
Default Value
0-65535
32768
There are no specific principles for setting the value of this parameter because this parameter is
used for querying.
A.20.14 Designated Bridge Priority(Spanning Tree)

Description
The Designated Bridge Priority parameter indicates the priority of each bridge during the
selection of the root bridge based on the STP. The bridge priority is a part of the bridge ID. A
bridge ID consists of the bridge priority and MAC address of the bridge. The bridge whose ID
is the smallest is selected as the root bridge in the network.

If the priority of a bridge is higher, the probability is higher that the bridge is selected as the root
bridge.
Values
Value Range
Default Value
0-61440
32768
If the value of the parameter is smaller, the priority of the bridge is higher. Set this parameter
according to the actual network condition.
A.20.15 Designated Bridge MAC Address (Spanning Tree)

Description
The Designated Bridge MAC Address parameter indicates the MAC address of a bridge.
Issue 03 (2012-11-30)

1231
OptiX OSN 7500 II/7500/3500/1500

To ensure that the bridge protocols operate normally, the following requirements should be met:
l
The multicast MAC address must be unique and be identified by all the bridges in the LAN.
The multicast MAC address identifies the protocol entities of a bridge that is connected to
different and individual physical network segments.
Each bridge has a unique ID in the entire LAN.
Ports on a bridge have port IDs, which are different from each other. Ports IDs of different
bridges are different. The values of these IDs can be assigned independently. The values
can also be used by other bridges.
Each bridge must provide the values of the parameters that are described previously or
provide the mechanism for assigning values for these parameters.

The MAC address of a bridge affects the priority of the bridge.
Values
Value Range
Default Value
unicast mac address
00-00-00-00-00-00
It is recommended that you use the default value.
A.20.16 Protocol Enabled (Port Parameter of Spanning Tree)

Description
The Protocol Enabled parameter specifies whether the STP is enabled for a port.
The STP is used in the loop network. This protocol realizes routing redundancy by adopting a
certain algorithm and breaks the loop network into a loop-free tree network. Hence, the
application of this protocol can prevent the packets from increasing and cycling in an endless
manner in the loop network.
The RSTP is developed based on the STP, which transmits spanning tree information through
configuration messages and conducts the calculation according to the priorities. The RSTP
reduces the delay when the root port and designated port enters the forwarding state to a great
extent, and hence reduces the time required for stabilizing the network topology.

The RSTP can realize all the functions of the STP. Compared with the STP, however, the RSTP
can restore the connectivity of the network more quickly, which can provide better services for
the user. This is because the RSTP reduces the delay when a port migrates from the blocking
state to the forwarding state without causing temporary loops.
Issue 03 (2012-11-30)

1232
OptiX OSN 7500 II/7500/3500/1500

Values
Value Range
Default Value
Enabled, Disabled
Disabled

Value
Description
Enabled
Indicates that the STP is enabled on the local port and that this
port is involved in the calculation.
Disabled
Indicates that the STP is disabled on the local port and this
port is not involved in the calculation.
Set this parameter according to the networking condition. If the topology calculation requires a
VB, enable the STP for this VB. Otherwise, the STP is disabled for all VBs.
The STP of a port can be enabled or disabled only after the STP is enabled for a VB.
A.20.17 Admin Edge Attribute

Description
Edge ports are directly connected to the terminal equipment and are not connected to any bridge
in a network. The Admin Edge Attribute parameter is important in the RSTP. The status of
these ports does not affect the topology of the entire network, and does not result in any loop.
Hence, after the bridge protocol is enabled, these ports can change to the forwarding status
without any delay.

If you set the ports that are directly connected to the terminal equipment as edge ports, the
convergence time of the RSTP is minimized, and the system reliability is enhanced.
Values
Value Range
Default Value
Enabled, Disabled
Disabled
You can set this parameter based on the network topology.
Issue 03 (2012-11-30)

1233
OptiX OSN 7500 II/7500/3500/1500


None.
A.20.18 Edge Port Status (Spanning Tree)

Description
The Edge Port Status parameter specifies whether a bridge port is an edge port. Edge ports are
directly connected to the terminal equipment and are no longer connected to any bridges. This
parameter is important in the RSTP. The status of these ports does not affect the connectivity of
the entire network, and does not cause any loops. Hence, these ports can enter the forwarding
state without any delay after the bridge starts.

After this parameter is enabled, convergence time of the RSTP is reduced and thus the reliability
of the system is improved.
Values
Value Range
Default Value
Enabled, Disabled
Disabled

Value
Description
Enabled
Indicates that the edge port function is enabled. In this case,

the port can enter the forwarding state directly without any
delay during the calculation process of the state machine.
Disabled
Indicates that the edge port function is disabled.
The user can set this parameter according to the network topology to reduce the delay in the case
of a state migration of the network edge port.
A.20.19 VB Port Priority

Description
The VB Port Priority parameter is the key part of the port ID for the spanning tree feature of
the OptiX OSN equipment. The port ID consists of the port priority and the unique port number
in the bridge. The port number is fixed and cannot be set. The port ID contains 16 bits, of which
the first eight bits indicate the port priority and the later eight bits indicate the port number.
For computation based on the spanning tree, a port with a smaller specified port priority is
preferred as the root port if the other conditions of this port are the same as conditions of the
Issue 03 (2012-11-30)

1234
OptiX OSN 7500 II/7500/3500/1500

other ports. In the same bridge, if the overhead of the root path is the same for multiple ports,
compare the specified bridge IDs, and then compare the specified port IDs.

The priority value of the VB port affects the selection of the root port of the downstream bridge
and the selection of the designated port. Consequently, the entire network topology is changed.
Values
Value Range
Default Value
128
The value of VB Port Priority must be an integer multiplied by 16. If the value is smaller, the
priority is higher. You can set the value based on the requirement of the user.
A.20.20 VB Port Status

Description
The VB Port Status parameter specifies that a bridge port processes the data packets based on
the port status computed by the spanning tree protocol.

Values
Valid Values
Default Value
Discarding, Forwarding,
Learning
Forwarding
Issue 03 (2012-11-30)
Value
Description
Discarding
In this state, the port cannot receive or forward service

packets.
Forwarding
In this state, the port can receive and forward service

packets.

1235
OptiX OSN 7500 II/7500/3500/1500

Value
Description
Learning
In this state, the port can receive but cannot forward

service packets. The port learns the source MAC
addresses contained in the received service packets so that
the port is ready for entering the forwarding state.

None.
A.20.21 Point to Point Attributes(External Ethernet Port Attributes)

Description
The Point to Point Attributes (External Ethernet Port Attributes) parameter specifies the
mode of connecting Ethernet ports to the external equipment. According to this parameter, the
spanning tree protocol (STP) decides whether to rapidly transit the port state from discarding to
forwarding.

If the connection is in shared media mode and if the port is not defined as an edge port, the STP
cannot rapidly transit the port state. After the STP updates the network topology, the service
restoration time becomes longer.
Values
Valid Values
Default Value
Adaptive connection, Shared media, Link

connection
Adaptive connection
Issue 03 (2012-11-30)
Value
Description
Adaptive connection
If the port is a full-duplex port or a VCTRUNK port, and if

the port has the point-to-point attribute, the port state can be
transited rapidly.
Shared media
If the port has the non-point-to-point attribute, the port state

cannot be transited rapidly.
Link connection
If the port has the point-to-point attribute, the port state can
be transited rapidly.

1236
OptiX OSN 7500 II/7500/3500/1500

If the port connection mode is known, select Shared media or Link connection. Otherwise,
select Adaptive connection.

None.
A.21 LCAS Associated Parameters

This topic describes the parameters for configuring the LCAS function.
A.21.1 Enabling LCAS

Description
The Enabling LCAS parameter can increase or decrease the SDH network capacity without
affecting the service. The capacity is automatically decreased if a member fails, and is
automatically increased if the member recovers.

As a bidirectional protocol, the LCAS can work normally only when some bandwidth is available
in the bidirectional physical paths. If the bandwidth is available in the unidirectional physical
paths only, the LCAS may fail to correctly adjust the bandwidth.
Values
Value Range
Default Value
Enabled, Disabled
Disabled

Value
Description
Disabled
Disables the LCAS protocol.
Enabled
Enables the LCAS protocol.
You can set Enabling LCAS as required.

None.
Issue 03 (2012-11-30)

1237
OptiX OSN 7500 II/7500/3500/1500

A.21.2 LCAS Mode

Description
The LCAS Mode parameter specifies the sequence for the sink end to respond to the MST and
Rs_Ack messages received from the source end.

Values
Value Range
Default Value
Huawei Mode, Standard

Mode
Huawei Mode

Value
Description
Huawei Mode
Inverts the RS_Ack message, and then transmits the MST

message.
Standard Mode
Transmits the MST message, and then Inverts the RS_Ack

message.
To set the LCAS mode, follow the principles:
l
If the interconnected equipment at the two ends are Huawei equipment, select Huawei
Mode.
If Huawei equipment is interconnected to a third-party equipment, set the interconnected

equipment to the same mode according to the mode supported by the third-party equipment.

None.
A.21.3 Hold off Time(ms) (LCAS)

Description
The Hold off Time(ms)(LCAS) parameter is also called HO Procedure Timer Duration. It
specifies HO Procedure Timer Duration of the LCAS protocol. If the LCAS coexists with
another network-level protection scheme (for example, MSP or SNCP), you can set this
parameter to postpone the LCAS switching.
Issue 03 (2012-11-30)

1238
OptiX OSN 7500 II/7500/3500/1500


The LCAS switching time is affected.
For example, if both the MSP and the LCAS are available in a network, set the LCAS hold off
time to 2000 ms. If the network fails, only the MSP switching occurs, but the LCAS switching
does not occur.
Values
Value Range
Default Value
Unit
0, 2000-10000
2000
ms
The User can set this parameter according to the expected hold off time of LCAS switching.

This parameter is valid only when Enabling LCAS is set to Enabled.
A.21.4 WTR Time(s) (LCAS)

Description
The WTR Time(s) parameter is also called WTR Procedure Timer Duration. It specifies
WTR Procedure Timer Duration of the LCAS protocol. Set this parameter to avoid impact
caused by the alarm jitter on the link status.

The fault recovery time of the LCAS protocol is affected. After the network recovers from a
fault, the LCAS protocol can recover only after a WTR duration.
Values
Value Range
Default Value
Unit
0-720
300
Second
The User can set this parameter according to the expected WTR duration of LCAS recovery.

Issue 03 (2012-11-30)

1239
OptiX OSN 7500 II/7500/3500/1500

A.21.5 TSD (LCAS)

Description
The TSD (LCAS) parameter specifies the B3 or BIP error status of a VCTRUNK member. TSD
stands for trail signal degrade. When this parameter is set to Enabled and if a VCTRUNK
member has excessive B3 or BIP bit errors, the LCAS protocol regards that this member fails
and deletes it from the available members. If this parameter is set to Disabled, the LCAS protocol
does not monitor the status of the B3 or BIP bit errors of a VCTRUNK member.

Values
Value Range
Default Value
Enabled, Disabled
Disabled
You can set whether to enable the TSD as required.

A.21.6 Minimum Number of Members in the Transmit Direction

Description
When the LCAS is enabled, the LCAS_PLCT alarm is reported if certain members in the transmit
direction fail and the number of valid members is smaller than a certain value. The Minimum
Number of Members in the Transmit Direction parameter specifies the certain number of the
valid members in the transmit direction.

When the LCAS is enabled, failure in certain paths does not affect the service in the case of
sufficient bandwidths. The user can set this parameter to enable the reporting of the LCAS_PLCT
alarm only when the number of the valid members in the transmit direction is smaller than a
certain value.
Values
Issue 03 (2012-11-30)
Value Range
Default Value
2-256
256

1240
OptiX OSN 7500 II/7500/3500/1500

A.22 Packet LPT Associated Parameters

This topic describes the parameters for configuring the link state pass through (LPT) function
in packet services.
A.22.1 Binding Status

Description
The Binding Status parameter specifies whether the LP function is bound with a service.

Values
Value Range
Default Value
Unbound, Bound
Unbound

Value
Description
Bound
Indicates that the LTP function is already bound with the service.
Unbound
Indicates that the LTP function is not bound with the service.
You need to configure a service before setting the binding status between the LTP function and
the service. This parameter is defaulted to Unbound.

Before binding a service, you need to enable the LPT function.
A.22.2 Primary Function Point

Description
The Primary Function Point parameter displays the port ID, board and slot ID of the primary
function point.
Issue 03 (2012-11-30)

1241
OptiX OSN 7500 II/7500/3500/1500

The primary function point is the master mode that operates the LPT protocol and determines
the LPT protocol status based on the operating information. The secondary function point senses
or transmits the status change information, such as the status change of a port or a remote node.
The point-to-multipoint LPT includes a primary function point and multiple second function
points, which respectively correspond to the root and leaves in the topology.

Values
Value Range
Default Value
Slot ID-Board-Port ID

Value
Description
Slot ID-BoardPort ID
Indicates the port ID, board and slot ID of the primary function
point.
None.

None.
A.22.3 Secondary Function Point Type

Description
The Secondary Function Point Type parameter specifies the type of the port of the secondary
function point when you configure point-to-point LPT.

Values
Issue 03 (2012-11-30)
Value Range
Default Value
PW, UNI

1242
OptiX OSN 7500 II/7500/3500/1500


Value
Description
PW
Indicates the type of the PW on the NNI side.
UNI
Indicates the type of the PW on the UNI side.
In packet mode, LPTs are classified as point-to-point LPT and point-to-multipoint LPT. NEs
are classified as Primary Function Point and Secondary Function Point. The Secondary
Function Point Type can be set only when you configure the point-to-point LPT.

Secondary Function Point Type must match with Primary Function Point Type.
A.22.4 Secondary Function Point

Description
The Secondary Function Point parameter displays the port, board, and slot ID of the secondary
function point.
The primary function point is the master node that operates the LPT protocol and determines
the LPT protocol status based on the operating information. The secondary function point senses
or transmits the status change information, such as the status change of a port or a remote node.
The point-to-multipoint LPT includes a primary function point and multiple secondary function
points, which respectively correspond to the root and leaves in the topology.

Values
Value Range
Default Value
Slot ID-Board-Port
Issue 03 (2012-11-30)
Value
Description
Slot ID-BoardPort
Indicates the port, board, and slot ID of the secondary function

point.

1243
OptiX OSN 7500 II/7500/3500/1500

None.

None.
A.22.5 Fault Detection Mode

Description
The Fault Detection Mode parameter specifies the mode to detect the LPT link status.

Values
Value Range
Default Value
LPT OAM, PW OAM
LPT OAM

Value
Description
LPT OAM
Indicates that the LPT protocol suite negotiates and determines

the LPT link status according to the protocol packets.
PW OAM
Indicates that the LPT protocol suite determines the LPT link
status according to the protocol packets and the PW OAM status
reported by a certain board. The LPT protocol suite regards that
the LPT link is in good status only when both the negotiation
status of the protocol packets and the PW OAM status are normal.
If the LPT detection modes differ at both ends, the LPT fails to work normally.

You need to enable the PW OAM function before configuring the PW OAM detection mode.
Issue 03 (2012-11-30)

1244
OptiX OSN 7500 II/7500/3500/1500

A.22.6 User-Side Port Status

Description
The User-Side Port Status parameter specifies the status of the laser on the LPT enabling port
on the user side.

Values
Value Range
Default Value
CLOSE, OPEN
OPEN

Value
Description
OPEN
Indicates that the laser on the LPT enabling port is opened.
CLOSE
Indicates that the laser on the LPT enabling port is closed.
When the LPT protocol works normally, OPEN is displayed. When a fault occurs on the network
side, the OptiX OSN equipment shuts down the laser on the local end and reports CLOSE.

None
A.23 LPT Associated Parameters (TDM Mode)

This topic describes the parameters for configuring the LPT function.
A.23.1 LPT
Description
The LPT parameter specifies whether the link state pass through (LPT) function is enabled. The
LPT is a technology developed by Huawei to increase the speed of the link state response.
Through the LPT protocol, the faults on the service access point and in the intermediate network
can be detected and reported.
Issue 03 (2012-11-30)

1245
OptiX OSN 7500 II/7500/3500/1500


When the LPT function is enabled, the faults on the service access point and in the intermediate
network can be detected and reported. For example, the service access point can be informed of
the fault in the intermediate network and thus can handle the fault accordingly (switch the service
to the backup link). When the LPT function is disabled, the link fault in the intermediate network
is not reported to the service access point.
Values
Value Range
Default Value
Yes, No
No

Value
Description
Yes
Indicates that the LPT function is enabled.
No
Indicates that the LPT function is disabled.
Set this parameter according to the actual requirement of the user. Set this parameter to Yes if
the LPT function is required.
A.23.2 Bearer Mode

Description
The Bearer Mode parameter specifies the frame format of the LPT protocol packet for
transmission. Three bearer modes are available, namely, GFP (HUAWEI), Ethernet, and GFP
(CSF).

All the equipment on the service access point and in the intermediate network should use the
same LPT bearer mode. Otherwise, the LPT function cannot work normally.
Values
Value Range
Default Value
GFP(HUAWEI), Ethernet, GFP(CSF)
GFP(HUAWEI)

Issue 03 (2012-11-30)

1246
OptiX OSN 7500 II/7500/3500/1500

Value
Description
GFP(HUAWEI)
Indicates the frame format specially used by Huawei.
Ethernet
Indicates the Ethernet frame format.
GFP(CSF)
Indicates the standard CSF frame format.
Set this parameter according to the actual requirement of the user. Ensure that the configurations
of the two interconnected ports are consistent.
A.23.3 Port-Type Port Hold-Off Time(ms)

Description
The Port-Type Port Hold-Off Time(ms) parameter specifies the interval for the PORT to
transmit the LPT fault information after it receives the information.

The greater the hold-off time of the PORT, the slower is the transmission of fault information
between networks.
Values
Value Range
Default Value
Unit
0-100000
ms
A.23.4 VCTRUNK Port Hold-off Time(ms)

Description
The VCTRUNK-Type Port Hold-off Time(ms) parameter specifies the interval for the
VCTRUNK port to transmit the LPT fault information after it receives the information.

The greater the hold-off time of the VCTRUNK port, the slower is the transmission of fault
information between networks.
Issue 03 (2012-11-30)

1247
OptiX OSN 7500 II/7500/3500/1500

Values
Value Range
Default Value
Unit
0-100000
ms
A.24 IGMP Snooping Associated Parameters

This topic describes the parameters for configuring the IGMP Snooping function.
A.24.1 Protocol Enable (IGMP Snooping Protocol)

Description
IGMP Snooping is a Layer-2 multicast protocol. If the IGMP Snooping is supported, an Ethernet
board can detect the IGMP packets that are transmitted between IP multicast routers or switches
and IP multicast hosts, and then check the detected IGMP packets. After being successfully
checked, these packets are transmitted transparently. An Ethernet board retrieves the registration
information of the multicast group from the checked IGMP packets. Moreover, it configures the
relevant functions to generate route ports and multicast groups. The multicast service packets
are forwarded according to the multicast group information.
This parameter specifies whether to enable the IGMP Snooping protocol within the specified
virtual bridge (VB).

l
If the IGMP Snooping protocol is enabled, the Ethernet physical port captures and analyzes
the received IGMP packets. Then the Ethernet physical port registers the multicast
information to generate the router port and the multicast group. Finally the Ethernet physical
port transparently transports the packets.
If the IGMP Snooping protocol is disabled, the Ethernet physical port does not analyze the
received IGMP packets. Instead, the Ethernet physical port broadcasts the IGMP packets
as ordinary multicast packets.
Values
Valid Values
Default Value
Enabled, Disabled
Disabled

Issue 03 (2012-11-30)

1248
OptiX OSN 7500 II/7500/3500/1500

Value
Description
Enabled
If the IGMP Snooping protocol is enabled, multicast groups

and router ports can be generated.
Disabled
If the IGMP Snooping protocol is disabled, multicast groups

and router ports cannot be generated.
l
To create and maintain a multicast service, select Enabled.
Otherwise, select Disabled.
A.24.2 Multicast Aging Time

Description
The Multicast Aging Time parameter specifies the aging time of the router port in the multicast
group. The time is learnt by the board port.
This parameter decides the valid time of the router port in the multicast group. Within the aging
time period, if the router port is learnt again, its aging time is reset. Otherwise, when the aging
time expires, the relevant router port in the multicast group is aged. After the router port is aged,
the whole multicast group is deleted if no other router ports exist in the multicast group.

The parameter value may affect the forwarding efficiency of the EVPLAN service.
l
If the aging time is long, and if the multicast MAC address table in the board fails to be
updated in time, the board forwards the service packets incorrectly. Consequently, the
forwarding efficiency is decreased.
If the aging time is short, the multicast MAC address table may be updated rapidly.
Moreover, a great number of received multicast service packets fail to be found in the MAC
address table. Consequently, the board broadcasts these data packets to all the ports. As a
result, the forwarding efficiency is also decreased.
Values
Valid Values
Default Value
Unit
Min
Generally, select the default value, unless otherwise specified. Otherwise, set the value according
to the requirements. Do not set the value beyond the range allowed by the board.
Issue 03 (2012-11-30)

1249
OptiX OSN 7500 II/7500/3500/1500


None.
A.25 Test Frame Associated Parameters

This topic describes the parameters for configuring the Ethernet service test function.
A.25.1 Frames to Send

Description
Frames to Send indicates the number of test packets to be transmitted. With this parameter
enabled, the system transmits a test packet at the intervals of certain period of time until the
number of transmitted test packets reaches the specified value.

Values
Value Range
Default Value
Unit
0-255
Unit
The user can set the number of test packets to be transmitted as required.

This parameter is valid only when Send Mode is set to Burst Mode.
A.25.2 Status
Description
Status indicates the transmit status of the current test frames at the port. This parameter is
displayed as the current test status after you configure Send Mode and Frames to Send and
then click Apply.

Issue 03 (2012-11-30)

1250
OptiX OSN 7500 II/7500/3500/1500

Values
Value Range
Default Value
Sending, Finished Sending

Value
Description
Sending
Indicates that the port is currently transmitting the test frames.
Finished Sending
Indicates that the port finishes transmitting the test frames.
None.

None.
A.25.3 Counter of Frames Sent

Description
Counter of Frames Sent indicates the number of test frames that are transmitted by the VC
trunk port in the Ethernet test. This parameter value is accumulative. The value indicates the
total number of test frames that are transmitted from last time when the parameter value is cleared
to this time when the value is queried.

This parameter is for query only and does not affect the system operation.
Values
For example, the parameter value 5indicates that the port transmits five test frames.
None.

None.
Issue 03 (2012-11-30)

1251
OptiX OSN 7500 II/7500/3500/1500

A.25.4 Counter of Received Response Test Frame

Description
Counter of Received Response Test Frame indicates the number of response test frames that
are received by the VC trunk port in the Ethernet test. This parameter value is accumulative.
The value indicates the total number of response test frames that are received from last time
when the parameter value is cleared to this time when the value is queried.

Values
For example, the parameter value 5indicates that this port receives five response test frames.
None.

None.
A.25.5 Counter of Test Frames to Receive

Description
Counter of Test Frames to Receive indicates the number of test frames that are received by
the VC trunk port in the Ethernet test. This parameter value is accumulative. The value indicates
the total number of test frames that are transmitted from last time when the parameter value is
cleared to this time when the value is queried.

Values
For example, the parameter value 5indicates that the port receives five test frames.
None.

None.
Issue 03 (2012-11-30)

1252
OptiX OSN 7500 II/7500/3500/1500

A.25.6 Bearer Mode (Ethernet Test)

Description
Bearer Mode (Ethernet Test) indicates the transmit path of the test frame. Different bearer
modes correspond to different types of test frames. If the bearer mode of the received test frame
is inconsistent with the bearer mode of this port, the test frame is discarded directly.

Values
Board Name
Value Range
Default Value

N2EGS2, N3EGS2, N2EGT2,
N1EFS0A, N1EMS2, N1EAS2
l /
N1EMS4, N1EGS4, N1EFT8, 1EFT8A,

N1EGT2, R1EFT4, N3EGS4, N4EGS4
GFP
l GFP
l Ethernet
GFP

Value
Description
Indicates that the bearer mode is unknown.
GFP
Indicates that the test frame is transmitted as a GFP management

frame.
Ethernet
Indicates that the test frame is transmitted as an Ethernet frame.
The Bearer Mode values of the test frame at the two ends of the SDH link must be consistent
so that the test frame can function properly.

None.
A.25.7 Send Mode (Ethernet Test)

Description
Send Mode(Ethernet Test) is used to set the test frame and the transmit mode of the test frame.
The test frame is used for simulating packet transmission to check whether the link is normal.
Issue 03 (2012-11-30)

1253
OptiX OSN 7500 II/7500/3500/1500


Values
Valid Values
Default Value
Disabled, Burst Mode, Continue Mode
Disabled

Value
Description
Disabled
Indicates the test is not performed.
Burst Mode
Indicates that the system transmits a test frame every one

second. The test ends after a specified number of test frames
are transmitted.
Continue Mode
Indicates that the system continuously transmits test frames

with a frequency of 1 frame per second.
Set this parameter according to the requirements of the test.
l
To perform the test continuously, set the parameter to Continue Mode.
To stop the test, set the parameter to Disabled.

None.
A.26 Orderwire Associated Parameters

This topic describes the parameters for configuring the orderwire function.
A.26.1 Call Waiting Time(s)

Description
The Call Waiting Time(s) parameter specifies the timeout period of searching an orderwire
route. If the period of searching an orderwire route exceeds the specified value, the orderwire
phone changes to the busy tone status.

Issue 03 (2012-11-30)

1254
OptiX OSN 7500 II/7500/3500/1500

Values
Valid Values
Default Value
Unit
1-9
For all the network elements (NEs) that communicate with each other over the orderwire phone,
this parameter must be set to the same value.
l
If the number of NEs is less than 30, usually, set the value to 5 seconds.
If the number of NEs is not less than 30, usually, set the value to 9 seconds.
Generally, set it to the default value (namely, 9 seconds).
A.26.2 Conference Call

Description
The Conference Call parameter specifies the phone numbers of network-wide orderwire calls.

Values
Valid Values
Default Value
100-99999999
999
l
For orderwire conference calls on each node of the same subnet, the phone number must
be the same.
The length of an orderwire conference call number can be set as required. The value range
is 3-8.
The length of an orderwire conference call number must be consistent with that of the
addressing call number.

None.
Issue 03 (2012-11-30)

1255
OptiX OSN 7500 II/7500/3500/1500

A.26.3 Phone
Description
The Phone parameter specifies the phone numbers of orderwire addressing calls. An addressing
call refers to a point-to-point call.

Values
Valid Values
Default Value
100-99999999
101
l
The phone numbers of orderwire addressing calls cannot be duplicate within the same
subnet.
The length of an orderwire call number can be set as required. The value range is 3-8.
Within the same orderwire network, the length of orderwire call numbers must be consistent
for each node.
The length of phone numbers used to make orderwire addressing calls must be consistent
with that of conference call numbers.

If the length of an orderwire phone number is set to another value, the orderwire addressing call
number is changed to the default phone number that maps the length.
For example, if the length of a phone number is set to contain three digits, the addressing call
number is changed to the default number 101. If the length of the phone number is set to contain
four digits, the addressing call number is changed to the default number 1001, and the rest may
be deduced by analogy.
A.26.4 Available Orderwire Port

Description
The Available Orderwire Port parameter specifies whether the optical interface is used to make
orderwire calls.

Issue 03 (2012-11-30)

1256
OptiX OSN 7500 II/7500/3500/1500

Values
Valid Values
Default Value
Available Orderwire Port
Bid-BidType-PortID

Value
Description
Bid-BidType-PortID
Indicates the available optical interface of a board in a slot,

which is used to set orderwire calls.
l Bid indicates the slot number of the board used to set
orderwire calls.
l BidType indicates the name of the board used to set
orderwire calls.
l PortID indicates the number of the optical interface on the
board used to set orderwire calls.
For example, to set optical interface 1 on the N2SL16 board
in slot 7, select 7-N2SL16-1.
None.

For the OptiX NG-SDH V100R003 and later versions, dynamically allocate the orderwire bytes.
To make addressing calls or conference calls, add the optical interface from Available
Orderwire Port to Selected Orderwire Port.
A.26.5 Available Conference Call Port

Description
The Available Conference Call Port parameter specifies whether the optical interface is used
to make conference calls.

Values
Issue 03 (2012-11-30)
Valid Values
Default Value
Available Orderwire Port
Bid-BidType-PortID

1257
OptiX OSN 7500 II/7500/3500/1500


Value
Description
Bid-BidType-PortID

The NG-SDH equipment supports the function of automatically releasing the ring of an
orderwire conference call. For this reason, when the NG-SDH equipment is interconnected to
each other, do not set this parameter when you make an orderwire conference call. When the
NG-SDH equipment is interconnected to other equipment (for example, the OptiX OSN 9500),
you can make orderwire conference calls only after Selected Conference Call Port is selected
for the interconnected optical ports.

None.
A.26.6 Subnet No. Length

Description
The Subnet No. Length parameter specifies the length of the subnet number of the orderwire
subnets if the entire network is divided into multiple orderwire subnets.

Values
Valid Values
Default Value
1, 2
Issue 03 (2012-11-30)
Value
Description
Indicates that the subnet number contains one digit. Value

range: 0-9
Indicates that the subnet number contains two digits. Value

range: 0-99

1258
OptiX OSN 7500 II/7500/3500/1500

Select the value according to the number of orderwire subnets.
l
If the number of orderwire subnets is less than 10, set Subnet No. Length to 1.
If the number of orderwire subnets is greater than 10, set Subnet No. Length to 2.

None.
A.26.7 Subnet (Subnet No. for the Optical Interface)

Description
The Subnet (Subnet No. for the Optical Interface) parameter specifies the subnet number of
the orderwire phone connected to the optical interface.

Values
Valid Values
Default Value
0-99
If the subnet number is set to 1, the value range is 0-9.
If the subnet number length is set to 2, the value range is 10-99.
For the optical ports in the same orderwire subnet, the subnet number must be the same.

If the subnet number length is changed, to avoid conflict between the subnet number length and
the number length of the subnet connected to the optical port, the system automatically clears
all the specified numbers of the subnets connected to the optical port. All the subnet numbers
mapping the optical ports are empty.
A.26.8 No.(F1 Data Port)

Description
The No. (F1 Data Port) parameter specifies the numbers of the F1 data ports that have the same
direction.
Issue 03 (2012-11-30)

1259
OptiX OSN 7500 II/7500/3500/1500


Values
Valid Values
Default Value
1-88

Value
Description
1-60
Supported by the OptiX OSN 3500.
1-88
Supported by the OptiX OSN 7500.
NOTE
The OptiX OSN 1500A and the OptiX OSN 1500B do not support the F1 data ports that have the same
direction.
None.

None.
A.26.9 Data Channel (F1 Data Port)

Description
The Data Channel (F1 Data Port) parameter specifies the uplink and downlink ports that pass
through the F1 data.

After the data channel is cancelled, the services that pass through the F1 data port are interrupted.
Values
Issue 03 (2012-11-30)
Valid Values
Default Value
F1, Bid-BidType-PortID

1260
OptiX OSN 7500 II/7500/3500/1500


Value
Description
F1
Indicates the F1 data port of the NE.
Bid-BidType-PortID
Indicates a port that can be used to set a slot of the F1 data

port.
When using the F1 data port, you need to configure its route. That is, set the 64 Kbit/s data being
added to or dropped from the NE, or passing through the NE.

You can correctly set the F1 data ports that have the same direction only when the F1 port is not
set to Transparent ECC Overhead Transmission.
A.26.10 Overhead Byte (Broadcast Data Port)

Description
The Overhead Byte (Broadcast Data Port) parameter specifies the number of the overhead
bytes, which are used to transmit orderwire broadcast data services, in the SDH frame header.

Values
Valid Values
Default Value
SERIAL1, SERIAL2,
SERIAL3, SERIAL4
SERIAL1
Issue 03 (2012-11-30)
Value
Description
SERIAL1
Indicates the S1 byte in the SDH frame header.
SERIAL2
SERIAL3

1261
OptiX OSN 7500 II/7500/3500/1500

Value
Description
SERIAL4
Select the value according to the configuration.

If the S1 byte, the S2 byte, the S3 byte, the S4 byte, or an optical interface is set to transparently
transmit DCC overhead, the broadcast data port may fail to be set.
A.26.11 Working Mode (Broadcast Data Port)

Description
The Working Mode (Broadcast Data Port) parameter specifies the working mode of the local
interface at which broadcast data services are added or dropped.

Values
Value
Valid Values
RS232, RS422

Value
Description
RS232
Indicates an asynchronous transmission mode, in which no

handshake signal is available. An NE operating in RS232
mode can communicate with an NE operating in RS232 or
RS422 mode directly; in this case, data transmission is
transparent and the maximum rate is 19.2 kbit/s.
RS422
RS422 port specifications differ from RS232 port

specifications only in that an RS422 port can become an
RS232 port by means of hardware jumpers.
Select the value according to the interface.
Issue 03 (2012-11-30)

1262
OptiX OSN 7500 II/7500/3500/1500


None.
A.26.12 Broadcast Data Source (Broadcast Data Port)

Description
The Broadcast Data Source (Broadcast Data Port) parameter specifies the source of the
orderwire broadcast data service.

Values
Valid Values
Default Value
No Data, SERIALx, BidBidType-PortID

Value
Description
No Data
Clears all the broadcast data services.
SERIALx
Indicates the local broadcast data port.

For example, SERIAL1.
Bid-BidType-PortID
Indicates a port that is used to set a slot of the F1 data port.


If the S1 byte, the S4 byte, or an optical interface is set to transparently transmit DCC overhead,
the broadcast data service may fail to be set.
Issue 03 (2012-11-30)

1263
OptiX OSN 7500 II/7500/3500/1500

A.26.13 Broadcast Data Sink (Broadcast Data Port)

Description
The Broadcast Data Sink (Broadcast Data Port) parameter specifies the sink of the orderwire
broadcast data service.

Values
Valid Values
Default Value
SERIALx, Bid-BidTypePortID

Value
Description
SERIALx
Indicates the local broadcast data port,

for example, SERIAL1.
Bid-BidType-PortID
Indicates a port that is used to set a slot of the F1 data port.


If the S1 byte, the S4 byte, or an optical interface is set to transparently transmit DCC overhead,
the broadcast data service may fail to be set.
A.27 Clock Associated Parameters

To synchronize the clocks on a network, you need to set the parameters that are associated with
clocks.
Issue 03 (2012-11-30)

1264
OptiX OSN 7500 II/7500/3500/1500

A.27.1 External Clock Output Mode

Description
The External Clock Output Mode parameter sets the output mode of the external clock source
to 2 Mbit/s or 2 MHz.

Modifying the output mode of the external clock source may result in switching between clock
sources, which may result in bit errors in services.
Values
Valid Value
Default Value
l 2 MHz
2 Mbit/s
l 2 Mbit/s

Value
Description
2 MHz
Indicates that the output mode of the external clock source is

2 MHz. That is, the external clock source outputs 2 MHz clock
signals.
2 Mbit/s
Indicates that the output mode of the external clock source is

2 Mbit/s.
Input modes of the two channels of external clock signals can be set to 2 MHz or 2 Mbit/s. The
default input mode is 2 Mbit/s. In practical application, make sure that the output mode matches
the input mode on the receive end.

None.
Related Information
None.
A.27.2 External Clock Output Timeslot

Description
The External Clock Output Timeslot parameter sets the timeslot for transmitting the S1 byte
of the external clock source. The external clock source transmits the S1 byte through a certain
Issue 03 (2012-11-30)

1265
OptiX OSN 7500 II/7500/3500/1500

timeslot. After starting the SSM protocol, make sure that the timeslot for receiving the S1 byte
is consistent with the timeslot for transmitting the S1 byte so that the S1 byte can be received
correctly.

When the SSM protocol is enabled on NEs, setting the S1 byte may result in switching between
clock sources. This may generate bit errors in services when clock jitters occur.
Values
Valid Value
Default Value
l SA4
All versions
l SA5
l SA6
l SA7
l SA8
l All versions

Value
Description
SA4
Indicates that the S1 byte is transmitted through the SA4

timeslot of the external clock port.
SA5

SA6

SA7

SA8

All versions
Indicates that the S1 byte is transmitted through all timeslots

of the external clock port.
None.

This parameter is valid only when the External Clock Output Mode parameter is set to 2 Mbit/
s.
Issue 03 (2012-11-30)

1266
OptiX OSN 7500 II/7500/3500/1500

Related Information
None.
A.27.3 External Source Output Threshold

Description
The External Source Output Threshold parameter sets the output quality threshold for the
external clock source. When output quality of the external clock source is inferior to the
threshold, the action specified for a 2M phase-locked source failure is invoked to control the
external clock source output.

Values
Valid Value
Default Value
Threshold Disabled, Not Inferior to G.

813 SETS Signal, Not Inferior to G.812
Local Clock Signal, Not Inferior to G.
812 Transit Clock Signal, Not Inferior
to G.811 Clock Signal
Threshold Disabled
Issue 03 (2012-11-30)
Value
Description
Threshold Disabled
Indicates that the external source quality threshold is

disabled.
Not Inferior to G.813 SETS Signal
Indicates that the external clock source becomes

invalid when its output quality is inferior to the quality
defined in G.813.
Not Inferior to G.812 Local Clock

Signal

invalid when its output quality is inferior to the clock
quality of local nodes defined in G.812.
Not Inferior to G.812 Transit Clock

Signal

invalid when its output quality is inferior to the clock
quality of transit nodes defined in G.812.
Not Inferior to G.811 Clock Signal

invalid when its output quality is inferior to the quality
defined in G.811.

1267
OptiX OSN 7500 II/7500/3500/1500

The output quality of the external clock source should not be inferior to the specified quality
threshold. Therefore, the quality threshold should be set to a value that is inferior to or equal to
the output clock quality of NEs.

This parameter is valid only when the Protection Status parameter is set to Start Standard
SSM Protocol.
Related Information
None.
A.27.4 2M Phase-Locked Source Fail Condition

Description
The 2M Phase-Locked Source Fail Condition parameter sets a failure condition for the 2M
phase-locked source.

Values
Valid Value
Default Value
l No Failure Condition
No Failure Condition
l AIS
l LOF
l AIS OR LOF
Issue 03 (2012-11-30)
Value
Description
No Failure Condition
Indicates that no failure condition is set. The 2M phase-lock

source remains valid when an AIS or LOF alarm occurs in the
external clock signal.
AIS
Indicates that the 2M phase-lock source becomes invalid

when an AIS alarm occurs in the external clock signal.
LOF

when an LOF alarm occurs in the external clock signal.
1268
OptiX OSN 7500 II/7500/3500/1500

Value
Description
AIS OR LOF

when an AIS or LOF alarm occurs in the external clock signal.
A failure condition can be set as required.

None.
Related Information
None.
A.27.5 2M Phase-Locked Source Fail Action

Description
The 2M Phase-Locked Source Fail Action parameter specifies the action to be invoked in the
case of a 2M phase-locked source failure. When the reference clock signal for locking external
clock output is invalid or the quality if inferior to the threshold, the specific action is invoked to
control the external clock output by either shutting down the output or inserting an AIS alarm.

Values
Valid Value
Default Value
l Shut Down Output
Shut Down Output
l Send AIS
l 2M Output S1 Byte
Unavailable
Issue 03 (2012-11-30)
Value
Description
Shut Down Output
Indicates that the external clock signal output is shut down.
Send AIS
Indicates that the external clock sends all "1"s signals.

1269
OptiX OSN 7500 II/7500/3500/1500

Value
Description
2M Output S1 Byte
Unavailable
Indicated that the S1 byte sent by the external clock is invalid.

That is, the external clock sends 0x0f.
When the 2M phase-locked source is invalid, the output action can be set as required. When the
External Clock Output Mode parameter is set to 2 MHz, the external clock signal output is
shut down no matter what action is set.

None.
Related Information
None.
A.27.6 Clock Source Priority Sequence (1 Is the Highest)

Description
The Clock source priority sequence(1 is the highest) parameter specifies the priority level of
a certain clock source in the system clock priority table.

When the SSM protocol is disabled or the extended SSM protocol is enabled, the current trace
clock source may be changed if the clock source priority sequence is changed. As a result, bit
errors may occur in the service or the service may be interrupted transiently.
Values
Value Range
Default Value
1, 2, 3
Issue 03 (2012-11-30)
Value
Description
Indicates that this clock source is at the highest priority level

in the system clock priority table.
Indicates that this clock source is at the second highest priority

level in the system clock priority table.
1270
OptiX OSN 7500 II/7500/3500/1500

Value
Description
Indicates that this clock source is at the third highest priority

level in the system clock priority table.
This parameter specifies the priority level of a certain clock source in the system clock priority
table. The value ranges from 1 to N. N represents the total number of clock sources in the system
clock priority table. Generally, the internal clock source is at the lowest priority level.
For example, there are four clock sources in the system clock priority table: one external clock
source, one line clock source, one tributary clock source, and one internal clock source. The
priority level of the external clock source is set to 1, the priority level of the line clock source is
set to 2, the priority level of the tributary clock source is set to 3 (the priority levels of the external
clock source, line clock source, and tributary clock source cannot be the same), and the priority
level of the internal clock source is always set to 4.
In the actual application, this parameter is set according to the specific networking situation.
A.27.7 Clock Source Threshold

Description
The Clock Source Threshold parameter indicates the lower quality threshold of 2M external
clock source. When the clock quality level of the external clock source that is selected from the
2M phase-locked source priority table is inferior to the threshold, the 2M phase-locked source
becomes invalid, and the action specified for 2M phase-locked source failure is invoked to
control the external clock source output.

Values
Value Range
Default Value
l No Threshold Value
No Threshold Value
l G.813 SETS Signal

l G.812 Lock Clock Signal
l G.812 Transit Clock Signal
l G.811 Clock Signal

Issue 03 (2012-11-30)

1271
OptiX OSN 7500 II/7500/3500/1500

Value
Description
No Threshold Value
Threshold disabled
G.813 SETS Signal
Indicates that the lower threshold is not inferior to the

G.813 SETS signal.
G.812 Lock Clock Signal

G.812 lock clock signal.
G.812 Transit Clock Signal

G.812 transit clock signal.
G.811 Clock Signal

G.811 clock signal.
In actual application, the output quality threshold of external clock source should be determined
according to the quality information about the NE clock and the opposite NE.

None.
Related Information
None.
A.27.8 Protection Status

Description
The Protection Status parameter indicates the working mode of the clock protocol for a clock
subnet.

The algorithm adopted by the system to select a clock source varies with the parameter value.
Values
Issue 03 (2012-11-30)
Value Range
Default Value
Start Extended SSM Protocol,

Start Standard SSM Protocol,
Stop SSM Protocol
Stop SSM Protocol

1272
OptiX OSN 7500 II/7500/3500/1500

The protection status of the entire clock subnet should be consistent. To avoid a clock tracing
loop on a ring or mesh network, it is recommended that you set this parameter to Start Extended
SSM Protocol.

None.
Related Information
As a mechanism adopted by the synchronous network for synchronization management, the
standard SSM protocol is loaded in the lower four bits of the S1 byte. The standard SSM protocol
allows nodes to exchange the quality information of clock sources. Hence, the SSM protocol
enables the system to automatically select the clock source with the highest priority and also
avoids a timing loop. The standard SSM protocol is applicable to interconnection with the
equipment of other suppliers.
Based on the standard SSM protocol, the extended SSM protocol presents a concept of clock
source ID. The higher four bits of the S1 byte indicate a unique clock source ID, which is
transmitted with the SSM. When receiving the S1 byte, a node checks the clock source ID to
see whether the clock source derives from itself. If the clock source derives from the node, the
node considers the clock source as unavailable. In this manner, a clock inter-lock loop is avoided
when the clock tracing path is configured as a ring. The extended SSM protocol is applicable to
the interconnection of transmission equipment from Huawei.
When the SSM protocol is disabled, the clock source is selected according to the priority table.
A.27.9 AIS Alarm Generated

Description
The AIS Alarm Generated parameter specifies whether an AIS alarm is a condition for
triggering the switching of clock sources.

Values
Value Range
Default Value
l Yes
No
l No

Issue 03 (2012-11-30)

1273
OptiX OSN 7500 II/7500/3500/1500

Value
Description
Yes
Indicates that an AIS alarm is the sufficient condition to

trigger clock source switching.
No
Indicates that an AIS alarm is not a condition for triggering

clock source switching.
It is recommended to set the AIS alarm as the condition for triggering clock source switching
in actual application to ensure system performance.

None.
Related Information
None.
A.27.10 B1 BER Threshold-Crossing Generated

Description
The B1 BER Threshold-Crossing Generated parameter specifies whether a B1 BER thresholdcrossing alarm is a condition for triggering clock source switching. B1 BER Threshold-Crossing
alarm is an index for measuring the performance of clock source signals.

Values
Value Range
Default Value
l Yes
No
l No
Issue 03 (2012-11-30)
Value
Description
Yes
Indicates that a B1 BER threshold-crossing alarm is the

sufficient condition for triggering clock source switching.
1274
OptiX OSN 7500 II/7500/3500/1500

Value
Description
No
Indicates that a B1 BER threshold-crossing alarm is not the

condition for triggering clock source switching.
A B1 BER threshold-crossing alarm indicates that the transmitted signal and the clock in the
signal are being interfered. Therefore, this parameter can be set as a condition for triggering
clock source switching in actual application to ensure system performance.

None.
Related Information
None.
A.27.11 B2-EXC Alarm Generated

Description
The B2-EXC Alarm Generated parameter specifies whether a B2-EXC alarm is a condition
for triggering clock source switching. B2-EXC alarm is an index for measuring the performance
of clock source signals.

Values
Value Range
Default Value
l Yes
No
l No
Issue 03 (2012-11-30)
Value
Description
Yes
Indicates that a B2-EXC alarm is the sufficient condition for

triggering clock source switching.
No
Indicates that a B2-EXC alarm is not the condition for

triggering clock source switching.

1275
OptiX OSN 7500 II/7500/3500/1500

A B2-EXC alarm indicates that the transmitted signal and the clock in the signal are being
interfered. Therefore, this parameter can be set as a condition for triggering clock source
switching in actual application to ensure system performance.

None.
Related Information
None.
A.27.12 Higher Priority Clock Source Reversion Mode

Description
The Higher Priority Clock Source Reversion Mode parameter specifies whether to switch
from the lower-priority clock source back to the higher-priority clock source after the higherpriority clock source is restored to normal.

If the conditions for clock source switching are excessively strict, jitters may occur in the
monitoring results of the clock status. If the auto-revertive mode is selected, the frequent
switching of clock sources may affect the service.
Values
Value Range
Default Value
l Non-Revertive
Auto-Revertive
l Auto-Revertive

Value
Description
Non-Revertive
Indicates that the higher-priority clock source cannot be

selected automatically after it is restored to normal.
Auto-Revertive
Indicates that the higher-priority clock source is selected

automatically after it is restored to normal.
If the conditions for clock source switching are properly set and the switching of clock sources
can be guaranteed, the Auto-Revertive mode can be selected to improve clock quality.
Otherwise, the Non-Revertive mode is recommended to avoid clock jitters.
Issue 03 (2012-11-30)

1276
OptiX OSN 7500 II/7500/3500/1500


None.
Related Information
None.
A.27.13 Clock Source WTR Time

Description
The Clock Source WTR Time parameter specifies the wait-to-restore (WTR) time when the
Higher Priority Clock Source Reversion Mode parameter is set to Auto-Revertive. When a
clock source is restored to its valid status, the system does not regard it as a valid source
immediately but verifies the validity of the clock source in a specific period of time. The system
regards the clock source as a valid source only if the clock source remains valid during the
specific period of time. This specific period of time is called the WTR time of the clock source.

Insufficient WTR time may result in wrong judgments on clock source restoration and clock
status jitters, which may interrupt the service.
Values
Value Range
Default Value
0-12
The WRT time is counted in minutes. The shorter the WTR time is, the faster the clock is
recovered, and the higher the average clock quality is. On the other hand, the shorter the WTR
time is, the more likely the clock jitters are caused due to unstable clock signals. Therefore, do
not set the WTR time to 0 in actual application.

The setting of the WTR time is valid only when the Higher Priority Clock Source Reversion
Mode parameter is set to Auto-Revertive.
Related Information
None.
Issue 03 (2012-11-30)

1277
OptiX OSN 7500 II/7500/3500/1500

A.27.14 Switching Status (Clock)

Description
The Switching Status (Clock) parameter indicates the current switching status of a clock source
in the clock priority table.

Values
Value Range
Default Value
l Normal
Normal
l Forced Switching
l Manual Switching

Value
Description
Normal
Indicates that the clock source in the clock priority table is in

the normal trace status.
Forced Switching

the forced switching status.
Manual Switching

the manual switching status.
None.

None.
Related Information
None.
Issue 03 (2012-11-30)

1278
OptiX OSN 7500 II/7500/3500/1500

A.27.15 Lock Status (Clock)

Description
The Lock Status (Clock) parameter indicates the lock status of a clock source in the priority
table.

Values
Value Range
Default Value
l Lock
Unlock
l Unlock

Value
Description
Lock
Indicates that a certain channel of clock source in the priority

table is in the lock status where the switching of clock sources
is not allowed.
Unlock
Indicates that a certain channel of clock source in the priority

table is in the unlock status where the switching of clock
sources is allowed.
None.

None.
Related Information
None.
A.27.16 Clock Source ID

Description
The Clock Source ID parameter specifies the clock source ID information that is transmitted
in the four most significant bits of the overhead S1 byte to avoid timing loops. This parameter
works in the extended SSM protocol mode.
Issue 03 (2012-11-30)

1279
OptiX OSN 7500 II/7500/3500/1500


Values
Value Range
Default Value
l 1-15
None
l None.
In actual application where the extended SSM protocol is enabled, the clock source IDs should
be set as required by network planning to ensure that the ID is network-wide unique.

This parameter is valid only when the extended SSM protocol is enabled.
Related Information
None.
A.27.17 Synchronous Source

Description
The Synchronous Source parameter indicates the synchronous clock source that is being traced.
The synchronous clock source here refers to a certain clock source contained in the system clock
priority table.

Values
Value Range
Default Value
Clock Source in System Clock

Priority Table
None
Issue 03 (2012-11-30)

1280
OptiX OSN 7500 II/7500/3500/1500

Value
Description
Clock Source in System

Clock Priority Table
Indicates that the system clock priority table contains the

tributary clock sources, line clock sources, external clock
sources, and internal clock sources.
None.

None.
Related Information
None.
A.27.18 Synchronous Status Byte

Description
The Synchronous Status Byte parameter sets the timeslot for carrying SSM information in the
external clock source. The SSM information can be received from the external clock port only
when a timeslot is set correctly. The timeslot for receiving the S1 byte ranges from SA4 to SA8.

If the synchronous status byte of the external clock source cannot be set correctly as required,
the NEs may fail to receive the clock quality information correctly and the NE clock may be out
of synchronization.
Values
Value Range
Default Value
l SA4
SA4
l SA5
l SA6
l SA7
l SA8
Issue 03 (2012-11-30)
Value
Description
SA4
Indicates that timeslot slot 0 is used for receiving the S1 byte.

1281
OptiX OSN 7500 II/7500/3500/1500

Value
Description
SA5
SA6
SA7
SA8
The timeslot for receiving the S1 byte is set for external clock source only. The timeslot can be
set to SA4, SA5, SA6, SA7 or SA8. The default timeslot is SA6. In actual application, make
sure that the specified timeslot for receiving the S1 byte is the timeslot for carrying the SSM
information in the external clock source. That is, the specified timeslot for receiving the S1 byte
is the transmit timeslot of the opposite NE.

None.
Related Information
None.
A.27.19 S1 Byte Synchronization Quality Information

Description
The S1 Byte Synchronization Quality Information parameter indicates the synchronization
quality information in the S1 byte that is output by the current traced synchronous source. The
S1 byte defined by the ITUT is used to transmit the quality information about the clock sources.
It indicates the quality information of 16 types of synchronous sources with bits 5-8 of the S1
byte in the section overhead. With this quality information and certain switching protocols, the
automatic protection switching of the synchronization clock can be realized in the synchronous
network.

Issue 03 (2012-11-30)

1282
OptiX OSN 7500 II/7500/3500/1500

Values
Value Range
Default Value
l Synchronous Source
Unavailable
None
l Quality Unknown
l G.811 Reference Clock
l G.812 Transit Clock
l G.812 Local Clock
l SDH equipment timing
source (SETS) signal

Value
Description
Synchronous Source
Unavailable
Indicates that the SSM protocol is disabled and the S1 byte

synchronization quality information output by the
synchronous source is not available.
Quality Unknown
Indicates that the SSM protocol is started but the S1 byte

synchronous source is unknown.
G.811 Reference Clock
Indicates that the SSM protocol is started and the S1 byte

synchronous source is the G.811 reference clock.
G.812 Transit Clock

synchronous source is the G.812 transit clock.
G.812 Local Clock

synchronous source is the G.812 local clock.
SDH equipment timing

Indicates that the SSM protocol is enabled and the S1 byte

synchronous source is the synchronous equipment timing
source (SETS) clock.
None.

None.
Issue 03 (2012-11-30)

1283
OptiX OSN 7500 II/7500/3500/1500

Related Information
None.
A.27.20 NE Clock Working Mode

Description
The NE Clock Working Mode parameter sets the current working mode of the system clock
to the normal, holdover or free-run mode.

Values
Value Range
Default Value
l Normal Mode
l Holdover Mode
l Free-Run Mode

Value
Description
Normal Mode
Indicates that the NE clock works in the tracing mode. That is, the
NE clock traces and locks the working mode of its upper-level
clock.
Holdover Mode
Indicates that the NE clock works in the holdover mode. That is,
in this mode, the NE clock uses the frequency information that is
stored before all timing reference signals are lost as its timing
reference.
Free-Run Mode
Indicates that the NE clock works in the free-run mode. That is,
the internal oscillator works in this mode when all external timing
reference signals are lost.
None.

None.
Issue 03 (2012-11-30)

1284
OptiX OSN 7500 II/7500/3500/1500

Related Information
None.
A.27.21 Clock Source Quality

Description
The Clock Source Quality parameter specifies the clock source quality information. Such
information is extracted from the S1 byte of individual clock sources according to the SSM
encoding rules after the SSM protocol is enabled. If the clock quality information cannot be
extracted, this parameter needs to be set manually.

Values
Value Range
Default Value
l Automatic Extraction
Automatic Extraction
l G.811 Clock Signal

l G.812 Transit Clock Signal
l G.812 Local Clock Signal
l G.813 SDH Equipment
Timing source (SETS)
Signal
l Unknown Synchronization
Quality

Value
Description
Automatic Extraction
Indicates that the clock quality information is extracted

automatically according to the encoding rules compliant
with the SSM protocol.
G.811 Clock Signal
Indicates that the clock source quality is manually set to the

G.811 clock signal.
G.812 Transit Clock Signal

G.812 transit clock signal.
G.812 Local Clock Signal

G.812 local clock signal.
G.813 SDH Equipment Timing Indicates that the clock source quality is manually set to the
source (SETS) Signal
SETS clock signal.
Issue 03 (2012-11-30)

1285
OptiX OSN 7500 II/7500/3500/1500

Value
Description
Quality
Indicates a message that is set in the negative direction of

the selected synchronization source to avoid direct mutual
locking of two adjacent NEs.
This parameter is usually set to Automatic Extraction. When the equipment is interconnected
to an NE from another manufacturer that complies with a different protocol, the clock source
quality can be specified manually.

The clock quality information is valid only when the SSM protocol is enabled.
Related Information
None.
A.27.22 S1 Byte Received

Description
The S1 Byte Received parameter indicates the value of the S1 byte of the current traced source
in the system clock priority table.

Values
Value Range
Default Value
l SDH equipment timing

Synchronous Source
Unavailable
l G.812 Local Clock

l Synchronous Source
Unavailable
Issue 03 (2012-11-30)

1286
OptiX OSN 7500 II/7500/3500/1500

Value
Description
SDH equipment timing

Indicates that the clock quality of the current traced source is

0x0b.
G.812 Local Clock

0x08.
G.812 Transit Clock

0x04.

0x02.
Synchronous Source
Unavailable

0x0f.
None.

None.
Related Information
None.
A.27.23 Line Port (Clock)

Description
The Line Port (Clock) parameter specifies the output port of SSM quality information about
the line clock source and external clock source available in the existing system. This output port
can transmit the quality information about the clock source by sending the S1 byte to the
downstream NE.

Values
Value Range
Default Value
l Line Clock Source Port
l External Clock Source Port

Issue 03 (2012-11-30)

1287
OptiX OSN 7500 II/7500/3500/1500

Value
Description
Line Clock Source Port
Indicates that only the port on the line board where both
physical board and logical board have been configured
properly can be used as the output port of SSM quality
information.
External Clock Source Port
Indicates that only the port on the board with external clock
interfaces where both physical board and logical board have
been configured properly can be used as the output port of
SSM quality information.
None.

None.
Related Information
The standard SSM protocol mode, also called as QL_ENABLE mode in the Recommendation
G.781, is a universal switching mode of clock source. In this standard SSM protocol mode, when
a clock source becomes invalid, the system automatically traces the clock source of the highest
quality in the clock priority table according to the quality information contained in the SSM
protocol. If two clock sources are both of the highest quality, the clock source of a higher priority
is selected.
A.27.24 Control Status (Clock)

Description
The Control Status (Clock) parameter specifies whether the line port can transmit the quality
information about the clock source by sending the S1 byte to the downstream NE. By setting
this parameter, the transmission of the S1 byte through the ports of the clock source can be
enabled or disabled.

Modifying the Control Status (Clock) parameter may cause loss of clock quality information
transmitted to the downstream NE. Therefore, the clock of the downstream NE may be
asynchronous with the clocks of other NEs in the synchronous network.
Values
Value Range
Default Value
l Enable
Enable
l Disabled
Issue 03 (2012-11-30)

1288
OptiX OSN 7500 II/7500/3500/1500


Value
Description
Enable
Indicates that the transmission of the S1 byte through the

corresponding line port is enabled.
Disabled
Indicates that the transmission of the S1 byte through the

corresponding line port is disabled.
The Control Status (Clock) parameter can be set to an enabled or disabled status as required.
The status is enabled by default. In actual application, if the output clock source on the line board
is valid, the transmission of the S1 byte through line port is allowed so that the clocks of the NEs
in the entire synchronous network are synchronous.

None.
Related Information
The standard SSM protocol mode, also called QL_ENABLE mode in the G.781, is a universal
switching mode of the clock source. In this standard SSM protocol mode, when a clock source
becomes invalid, the system automatically traces the clock source of the highest quality in the
clock priority table according to the quality information contained in the SSM protocol. If two
clock sources are both of the highest quality, the clock source of a higher priority is selected.
A.27.25 Line Port (Clock ID)

Description
The Line Port (Clock ID) parameter sets clock source ID in the S1 byte for the interconnection
and isolation between different clock subnets. In the extended SSM protocol mode, the four most
significant bits of the S1 byte are used for identifying the clock source ID to improve the clock
protection performance in the SDH network and to effectively avoid the timing loop. The clock
source ID is output by the line port only. The external clock cannot output the clock source ID.

Values
Issue 03 (2012-11-30)
Value Range
Default Value

1289
OptiX OSN 7500 II/7500/3500/1500


Value
Description
Indicates that only the port on the line board where both
physical board and logical board have been configured
properly can be used as the output port of the clock source ID.
None.

None.
Related Information
None.
A.27.26 Enabled Status (Clock ID)

Description
Then Enabled Status (Clock ID) parameter is used to enable or disable the output of the clock
source ID for the interconnection and isolation between different subnets. In the extended SSM
protocol mode, the four most significant bits of the S1 byte are used for identifying the clock
source ID to improve the clock protection performance in the SDH network and to effectively
avoid the timing loop. This parameter is used to enable or disable the output of the clock source
ID. The output of the clock source ID by internal clock source cannot be disabled. This parameter
is invalid for external clock, because the external clock cannot output the clock source ID.

In a system where the extended SSM protocol is adopted, modifying the Enable Status (Clock
ID) parameter may result in clock tracing loop, which may make the originally synchronous
clock sources asynchronous.
Values
Value Range
Default Value
l Enabled
Enabled
l Disabled.

Issue 03 (2012-11-30)

1290
OptiX OSN 7500 II/7500/3500/1500

Value
Description
Enabled
Indicates that the output of clock source ID through

corresponding line ports is allowed.
Disabled.
Indicates that the output of clock source ID through

corresponding line ports is forbidden.
The Enabled Status (Clock ID) parameter can be set to an enable of disabled status as required.
The status is enabled by default. In actual application, as long as the extended SSM protocol is
started and the output clock source on the line board is valid, it is allowed to output clock source
ID in the four most-significant bits of the S1 byte through line ports. This can ensure clock
synchronization among the NEs in the entire synchronous network and prevent the occurrence
of timing loops.

There are three working modes of the SSM protocol: the disabled, standard and extended SSM
protocol modes. This parameter is valid only when the extended SSM protocol mode is adopted
by the current clock of the NEs.
Related Information
None.
A.27.27 Data Output Method in Holdover Mode

Description
The Data Output Method in Holdover Mode parameter specifies whether the data is output
normally or the latest data is kept when the NE clock is in the holdover mode.

Values
Value Range
Default Value
l Normal Data Output Mode
Normal Data Output Mode
l Keep the Latest Data

Issue 03 (2012-11-30)

1291
OptiX OSN 7500 II/7500/3500/1500

Value
Description
Normal Data Output Mode
Indicates the normal data output mode. The duration of this

output mode is determined by the phase lock. This data output
mode can continue for a maximum of 24 hours.
Indicates that the latest phase-locked data is kept. This data

output mode is a forced holdover mode.
The Keep the Latest Data mode is a forced holdover mode. Therefore, the clock accuracy is not
high. In actual application, the Normal Data Output mode is recommended.

The NE clock can work in three modes: the trace, holdover, and free-run modes. This parameter
is valid only when the NE clock is working in the holdover mode.
Related Information
None.
A.27.28 Manual Setting of 0 Quality Level

Description
The Manual Setting of 0 Quality Level parameter specifies the 0 quality level that is not
provided in the SSM protocol. Users can add this parsing rule to specify the quality level
represented by 0.

Issue 03 (2012-11-30)

1292
OptiX OSN 7500 II/7500/3500/1500

Values
Value Range
Default Value
l Do Not Use For

Synchronization
Do Not Use For Synchronization

l G.812 Local Clock
l SETS Clock
l Between G.811 Reference
Clock and G.812 Transit
Clock
l Between G.812 Transit
Clock and G.812 Local
Clock
l Between G.812 Local Clock
and synchronous
equipment timing source
(SETS)
Issue 03 (2012-11-30)
Value
Description
Do Not Use For

Synchronization
Indicates a message that is set in the negative direction of

the selected synchronization source to avoid direct mutual
locking of two adjacent NEs.
Indicates that the clock signal complies with the G.811

protocol.
G.812 Transit Clock
Indicates that the transit exchange clock signal complies

with the G.812 protocol.
G.812 Local Clock
Indicates that the local office signal complies with the G.

812 protocol.
SETS Clock
Indicates the synchronous equipment timing source

(SETS).
Between G.811 Reference

Clock and G.812 Transit Clock
Indicates that the specified quality level is inferior to the

quality level of the G.811 reference clock signal but is
superior to the quality level of the G.812 transit clock
signal.
Between G.812 Transit Clock

and G.812 Local Clock

quality level of the G.812 transit clock signal but is superior
to the quality level of the G.812 local clock signal.

1293
OptiX OSN 7500 II/7500/3500/1500

Value
Description
Between G.812 Local Clock

and synchronous equipment
timing source (SETS)

quality level of the G.812 local clock signal but is superior
to the quality level of the synchronous equipment timing
source (SETS) clock signal.
In actual application, this parameter can be set according to the quality information about specific
NE clocks.

The setting of this parameter is valid only when the SSM protocol is enabled.
Related Information
None.
A.27.29 Retiming Mode

Description
The Retiming Mode parameter specifies whether the retiming clock, tributary clock, or crossconnect (external) clock is used.

If the downstream board that corresponds to this board provides the clock source for the
downstream NE, the selection of the user affects the precision of the downstream NE.
Values
Value Range
Default Value

Mode of Cross-Connect Clock
Normal
Issue 03 (2012-11-30)
Value
Description
Normal
Indicates that the retiming clock is not used.
Retiming Mode of Tributary

Clock
Indicates that the tributary clock is used as the retiming

clock.

1294
OptiX OSN 7500 II/7500/3500/1500

Value
Description
Retiming Mode of CrossConnect Clock
Indicates that the cross-connect (external) clock is used as

the retiming clock.
Select the proper clock according to the actual networking planning of the user.
This parameter is applicable to the PQ1 and PQM boards. When the PQM board functions as
the protection board, the function of setting the retiming mode is unavailable.
A.28 Protection Associated Parameters

This topic describes the parameters for configuring multiplex section protection (MSP),
subnetwork connection protection (SNCP), board protection switching (BPS), and path
protection switching (PPS).
A.28.1 Switching Mode (MSP)

Description
The Switching Mode parameter specifies the switching mode of the linear MSP.

Values
Value Range
Default Value
Single-Ended Switching, DualEnded Switching
Single-Ended Switching
Issue 03 (2012-11-30)
Value
Description
Single-Ended Switching
Indicates that the transmit end continues to transmit

signals to the broken fiber after the switching occurs at
the faulty end.
Dual-Ended Switching
Indicates that the transmit end does not transmit signals

to the broken fiber after the switching occurs at the
transmit end and at the receive end.

1295
OptiX OSN 7500 II/7500/3500/1500

In the case of the 1+1 MSP, you can set this parameter to Single-Ended Switching or DualEnded Switching. In the case of the 1:N MSP, you can set this parameter to Dual-Ended
Switching only.
A.28.2 Initiation Condition (SNCP)

Description
The Initiation Condition parameter specifies the condition for monitoring the switching of the
SNCP pair.

Values
Value Range
Default Value
TIM, EXC, SD, UNEQ
EXC, SD

Value
Description
TIM
Indicates whether the HP_TIM alarm is monitored.
EXC
Indicates whether the B3_EXC alarm is monitored.
SD
Indicates whether the B3_SD alarm is monitored.
UNEQ
Indicates whether the HP_UNEQ alarm is monitored.
A.28.3 Group Type (SNCP)

Description
The Group Type parameter specifies the grouping type of the SNCP services.

If switching occurs on any of several bound SNCP pairs, switching occurs on all the SNCP pairs.
Issue 03 (2012-11-30)

1296
OptiX OSN 7500 II/7500/3500/1500

Values
Value Range
Default Value
Null, Virtual Concatenation

Grouping
Null

Value
Description
Null
Virtual Concatenation Grouping
Indicates that the user needs to bind SNCP pairs.
To bind SNCP pairs, the user needs to set this parameter to Virtual Concatenation
Grouping for these SNCP pairs.

The levels and attributes of the SNCP pairs to be bound must be the same. In addition, these
SNCP pairs should be in the activated state.
A.28.4 Configure SNCP Tangent Ring

Description
If an NE is a tangent node on the SNCP ring, you can configure an SNCP group that has the
same source but different sinks for the NE after this function is enabled.

Values
Value Range
Default Value
Selected, Deselected
Deselected
Issue 03 (2012-11-30)

1297
OptiX OSN 7500 II/7500/3500/1500

Value
Description
Selected
Specifies an SNCP group that has the same source but

different sinks.
Deselected
Specifies an SNCP group that has the same source and same
sink.
When configuring SNCP for a tangent node on the SNCP ring, you can select the Configure
SNCP Tangent Ring check box.

None.
A.28.5 Source(Sink)Timeslot Range(e.g.1,3-6)

Description
The Source(Sink)Timeslot Range(e.g.1,3-6) parameter indicates the timeslot or timeslot range
of a configured service.

Values
The value range varies according to the specified service type.
Service Type
Value Range
VC-4
VC-3
1 to 3
VC-12
1 to 63
Enter multiple consecutive timeslots in the format of Start timeslot number-End timeslot
number. Enter multiple inconsecutive timeslots in the format of ts1, ts2, .... You can enter the
timeslots in a combination of the two formats.

None.
Issue 03 (2012-11-30)

1298
OptiX OSN 7500 II/7500/3500/1500

A.28.6 Switching Status (BPS)

Description
The Switching Status (BPS) parameter shows the status of BPS switching.

Values
Valid Value
Default Value
Forced Switch Request, Auto Switching,

Idle, Unknown
Auto Switching

Value
Description
Forced Switch Request
Indicates that services in a protection group are forcibly

switched by using switching commands.
Auto Switching
Indicates the switching status of the protection group, which

results from the faulty Ethernet board.
Idle
Indicates that the working and protection boards are normal.
Unknown
Indicates that the switching status is unknown. You can learn

about the current status through a query.
None.

None.
A.28.7 Switching Status (PPS)

Description
The Switching Status (PPS) parameter specifies the status of PPS switching.

Issue 03 (2012-11-30)

1299
OptiX OSN 7500 II/7500/3500/1500

Values
Value Range
Default Value
Forced Switching(Protection to Working), Forced

Switching(Working to Protection), Normal
Normal

Value
Description
Normal
Indicates the status when no switching is required, namely,

the normal status.
Forced Switching(Protection
to Working)
Forcibly switches the service from the working path to the

protection path. The switching is implemented regardless of
the status of the protection path, unless the protection path
meets the bridging requirement of higher priority.
Forced Switching(Working
to Protection)
Forcibly switches the service from the protection path to the

working path. The switching is implemented regardless of the
status of the working path, unless the working path meets the
bridging requirement of higher priority.
None.

None.
A.28.8 External Switching Command Type (BPS)

Description
External Switching Command Type (BPS) indicates forcibly switching services in the BPS
protection group to the working board or protection board by running the external switching
command.

If the working board and protection board are normal, a forced switching may lead to a transient
service interruption. If either one of the working board and protection board is faulty, a forced
switching may lead to a service interruption.
Issue 03 (2012-11-30)

1300
OptiX OSN 7500 II/7500/3500/1500

Values
Value Range
Default Value
Forced Switching to Working, Forced

Switching to Protection, Clear Switching

Value
Description
Forced Switching to
Working
Indicates forcibly switching services from the protection

board to working board. This switching neglects the status of
the working channel, unless the working channel meets the
request of a bridge with a higher priority.
Forced Switching to
Protection
Indicates forcibly switching services from the working board

to protection board. This switching neglects the status of the
protection channel, unless the protection channel meets the
request of a bridge with a higher priority.
Clear Switching
Indicates clearing the current switching status.
Set this parameter as required.

None.
A.28.9 External Switching Command Type (PPS)

Description
External Switching Command Type (PPS) indicates forcibly switching services in the PPS
protection group to the working board or protection board by running the external switching
command.

If the working port and protection port are normal, a forcible switching may lead to a transient
service interruption. If either one of the working board and protection board is faulty, a forcible
switching may lead to a service interruption.
Issue 03 (2012-11-30)

1301
OptiX OSN 7500 II/7500/3500/1500

Values
Value Range
Default Value
Query Protection Group Status, Forced

Switch to Working, Forced Switch to
Protection, Manual Switch to Working,
Manual Switch to Protection, Lockout of
Protection, Clear

Value
Description
Query Protection Group

Status
Indicates querying the status of the protection group.
Forced Switch to Working
Indicates forcibly switching the service from the protection

channel to the working channel. This switching neglects the
status of the working channel, unless the working channel
meets the request of a bridge with a higher priority.
Forced Switch to Protection
Indicates forcibly switching the service from the working

channel to the protection channel. The switching does not
consider the status of the protection channel, unless the
protection channel runs an external switching command of a
higher priority.
Manual Switch to Working
Indicates manually switching the service from the protection

channel to the working channel. If the working channel is
normal, a switching is triggered. If the working channel fails
or is satisfying the switching request of a bridge with a higher
priority, a switching is not triggered.
Manual Switch to Protection
Indicates manually switching the service from the working

channel to the protection channel. If the protection channel is
normal, a switching is triggered. If the protection channel fails
or is satisfying the switching request of a bridge with a higher
priority, a switching is not triggered.
Lockout of Protection
The priority of the lockout of protection is lower than the

priority of the forced switching and the priority of the manual
switching. The lockout of protection can only lock the current
automatic switching status.
Clear
Indicates clearing the current switching status.
Set this parameter as required.
Issue 03 (2012-11-30)

1302
OptiX OSN 7500 II/7500/3500/1500


None.
A.29 Other Parameters

This topic describes the parameters related to PDH interfaces and SDH interfaces.
A.29.1 E1/T1 Interconnection

Description
The E1/T1 Interconnection parameter specifies whether the frame structure is checked and
indicates the checking mode, in the case of an E1/T1 interconnection.

The local NE and downstream NE are not affected.
Values
Value Range
Default Value
Transparent transmission,
Interconnection monitored,
Interconnection unmonitored
Transparent transmission

Value
Description
Transparent transmission
Indicates that the frame structure is transparently

transmitted.
Interconnection unmonitored
Indicates that the frame structure is not monitored in the

case of an E1/T1 interconnection.
Interconnection monitored
Indicates that the frame structure is monitored in the case

of an E1/T1 interconnection.
When the service is of the E1 type, the setting of Interconnection unmonitored and
Interconnection monitored is not supported. When the service is of the T1 type, the setting of
Transparent transmission is not supported. When the service is changed from T1 to E1, the
value of this parameter is automatically changed to Transparent transmission.
This parameter is applicable to the PQM board.
Issue 03 (2012-11-30)

1303
OptiX OSN 7500 II/7500/3500/1500

A.29.2 T1 Frame Structure

Description
The T1 Frame Structure parameter specifies whether the structure of the T1 frame is set to
Unframed or whether the D4, ESF, SLC96, F4, or M13 frame structure is monitored.

Values
Value Range
Default Value
Unframed, D4, ESF, SLC96, F4, M13
Unframed

Value
Description
Unframed
Indicates that the frame format is not monitored in transparent

transmission mode.
D4
Indicates the structure of the T1 frame.
ESF
SLC96
F4
M13
In transparent transmission mode, this parameter is valid when the frame is set to be monitored
and the service is of the T1 type. In this case, the frame format is the format of the accessed
service. If you need not monitor the frame format when the frame format is monitored, set this
parameter to Unframed.
In interconnection unmonitored mode, this parameter is valid and used to define the frame format
of the output service.
In interconnection monitored mode, this parameter is valid. In this case, the port monitors the
accessed service and defines the frame format of the output service according to the frame format
specified by this parameter.
Issue 03 (2012-11-30)

1304
OptiX OSN 7500 II/7500/3500/1500


None.
A.29.3 E1 Frame Structure

Description
The E1 Frame Structure parameter specifies whether the structure of the E1 frame is set to
Framed, Unframed or whether the PCM30, PCM31, PCM30CRC, or PCM31CRC frame
format is monitored.

Values
Value Range
Default Value
Framed, Unframed, PCM30,

PCM31, PCM30CRC,
PCM31CRC
Unframed
Issue 03 (2012-11-30)
Value
Description
Framed
Indicates that the frame format is monitored in

transparent transmission mode.
Unframed
Indicates that the frame format is not monitored in

transparent transmission mode.
PCM30
Indicates the structure of the E1 signal. 30 timeslots are

available for users, that is, TS1-TS15 and TS17-TS31.
Timeslot TS16 is used to transmit signaling. This type
of structure does not provide the CRC check.
PCM31

Timeslot TS16 does not transmit signaling. This type of
structure does not provide the CRC check.
PCM30CRC

Timeslot TS16 is used to transmit signaling. This type
of structure provides the CRC check.

1305
OptiX OSN 7500 II/7500/3500/1500

Value
Description
PCM31CRC

Timeslot TS16 does not transmit signaling. This type of
structure provides the CRC check.
In transparent transmission mode, this parameter is valid when the frame is set to be monitored
and the service is of the E1 type. In this case, the frame format is the format of the accessed
service. If you need to monitor the frame format when the frame format is not monitored, set
this parameter to Unframed.
In interconnection unmonitored mode, this parameter is valid and used to define the frame format
of the output service.
In interconnection monitored mode, this parameter is valid. In this case, the port monitors the
accessed service and defines the frame format of the output service according to the frame format
specified by this parameter.

None.
A.29.4 Service Mode

Description
The Service Mode parameter indicates the actual working mode of the board that supports the
M13/E13 function.

Values
Value Range
Default Value
Normal Mode, MUX

Mode, Server Mode
Normal Mode
Issue 03 (2012-11-30)

1306
OptiX OSN 7500 II/7500/3500/1500

Value
Description
Normal Mode
Indicates that the processing mode of the tributary board is

consistent with the processing mode of the board that does not
provide the M13/E13 function. For example, in normal mode,
the E1 service is added to or dropped from the N2PQ1 board and
the cross-connection at the VC-12 level is configured.
MUX Mode
Indicates that three VC-3 cross-connections are configured. E1

signals are received or transmitted on the first 48 channels of the
interface board. Each VC-3 cross-connection corresponds to 16
E1 signals.
Server Mode
Indicates that the tributary board does not drop any service, but
realizes the conversion between E1 and E3 signals only.
Select a proper value according to the actual requirement of the user.
This parameter is applicable to the N2PQ1, R2PD1, N2PQ3, N2PD3, N2PL3, and N2PL3A
boards.
A.29.5 Service Type

Description
The Service Type parameter specifies the service type of PDH signals.

Values
Value Range
Default Value
E13, M13
E13
Issue 03 (2012-11-30)
Value
Description
E13
Indicates the structure of the PDH frame.
M13
Indicates the structure of the PDH frame.

1307
OptiX OSN 7500 II/7500/3500/1500

Set this parameter to E13 when you need to convert E1 signals to E3 signals or convert E3 signals
to E1 signals. Set this parameter to M13 when you need to convert T1 signals to T3 signals or
convert T3 signals to T1 signals.
This parameter is applicable to the N2PQ1, N2PQ3, N2PL3, N2PL3A, N2PD3, and R2PD1
boards that are used on the OptiX NG-SDH equipment series.
A.29.6 Service Frame Format

Description
The Service Frame Format parameter specifies whether the tributary board monitors the frame
format of the signal. This parameter determines whether the frame format of the signal is
monitored only, and does not affect services. If the frame format of the service transmitted from
the opposite end is inconsistent with the frame format of the service at the local end or if the
service transmitted from the opposite end does not have any frame format, a large number of
LFA/RFA alarms are reported.

When you set the frame format of the service supported by the board to Unframe, the system
is not affected if the framing mode set on the U2000 is inconsistent with the framing mode of
the board. When you set the frame format of the service supported by the board to Frame, alarms
indicating inconsistent frame formats may be reported on the U2000 if the framing mode set on
the U2000 is inconsistent with the framing mode of the board.
Values
Value Range
Default Value
Unframe, Frame
Unframe

Value
Description
Unframe
Indicates that the tributary board does not monitor the frame
format of the signal.
Frame
Indicates that the tributary board monitors the frame format of

the signal.
This parameter is applicable to the N2PQ1, N2PQ3, N2PL3, N2PL3A, N2PD3, and R2PD1
boards that are used on the OptiX NG-SDH equipment series.
Issue 03 (2012-11-30)

1308
OptiX OSN 7500 II/7500/3500/1500

A.29.7 Connection Mode (NE Attribute)

Description
The Connection Mode (NE Attribute) parameter indicates the connection mode between a
gateway NE and the U2000. If the gateway NE is connected to the U2000 based on IP, two
connection modes are available between them, namely, common mode, and security SSL mode.

The connection mode between the NE and the U2000 determines whether the NE and U2000
can communicate normally and securely with each other.
Values
Value Range
Default Value
Common, Security SSL
Common

Value
Description
Common
Indicates that the connection between the NE

and the U2000 is not encrypted.
Security SSL
Indicates that the connection between the NE

and the U2000 is encrypted.
If the communication environment between the NE and the U2000 is secure, the common mode
can be used. If the security requirement for the in-between communication is high, the security
SSL mode can be used to prevent packet interception.

This parameter is valid only when Gateway Type is set to Gateway and Protocol is set to IP.
Related Information
None.
A.29.8 Enable Tandem Connection at the Source

Description
The Enable Tandem Connection at the Source parameter specifies whether the tandem
connection monitoring (TCM) function at the source end is enabled.
Issue 03 (2012-11-30)

1309
OptiX OSN 7500 II/7500/3500/1500


Values
Value Range
Default Value
Disabled, Enabled
Disabled

Value
Description
Disabled
Indicates that the TCM function is disabled.
Enabled
Indicates that the TCM function is enabled.
Set this parameter according to the actual requirement of the user. If the TCM function is
required, set this parameter to Enabled.
Only the N2 board series in the SDH board category support the setting of this parameter because
only these boards support the TCM function.

None.
A.29.9 APId to be Sent at the Source

Description
The APId to be Sent at the Source parameter indicates the N1 byte to be sent based on the
number of calculated bit errors.

The system is not affected because this function is used for testing.
Values
Issue 03 (2012-11-30)
Value Range
Default Value
A 16-byte string
[CRC Check] HuaWei SBS

1310
OptiX OSN 7500 II/7500/3500/1500

Set this parameter according to the actual requirement of the user. It is recommended that you
use the default value.
A.29.10 Optimize Higher Order Pass-Through

Description
The Optimize Higher Order Pass-Through parameter indicates that the lower order services
that do not necessarily require lower order cross-connection resources can use higher order crossconnections, therefore reducing the usage of lower order cross-connection resources.

If you enable the higher order pass-through optimization function, the services may be
interrupted transiently, and the service interruption lasts for 50 ms.
Values
Value Range
Default Value
Enabled, Disabled
Disabled

Value
Description
Enabled
Indicates that the higher order pass-through optimization

function is enabled. In this case, the lower order services that
do not necessarily require lower order cross-connection
resources can use higher order cross-connections.
Disabled
Indicates that the lower order services occupy lower order

cross-connection resources.
If lower order cross-connection resources are insufficient, you can enable the higher order paththrough function to configure more lower order services.

None.
Issue 03 (2012-11-30)

1311
OptiX OSN 7500 II/7500/3500/1500

B Glossary
Glossary
Numerics
1+1 backup
A backup method in which two components mirror each other. If the active component
goes down, the standby component takes over services from the active component to
ensure that the system service is not interrupted.
1:N protection
An architecture that has N normal service signals, N working SNCs/trails, and one
protection SNC/trail. It may have one extra service signal.
3G
See 3rd Generation.
3R
reshaping, retiming, regenerating
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
A/D
analog/digit
AAA
See Authentication, Authorization and Accounting.
AAL
See ATM Adaptation Layer.
AAL2
ATM Adaptation Layer Type 2
AAL5
ATM Adaptation Layer Type 5
ABR
See available bit rate.
ACAP
See adjacent channel alternate polarization.
ACH
associated channel header
ACL
See access control list.
ACL rule
A rule for controlling the access of users.
ADM
add/drop multiplexer
AF
See assured forwarding.
AGC
automatic gain control
Issue 03 (2012-11-30)

1312
OptiX OSN 7500 II/7500/3500/1500

B Glossary
AIO
asynchronous input/output
AIS
alarm indication signal
AIS insertion
Insertion of AIS in a channel with excessive errors to indicate that it is unavailable. For
a line board, it can be set whether to insert AIS when there are excessive errors in the
B1, B2 and B3 bytes. For tributary board at the E1/T1 level, it can be set whether to
insert AIS when there are excessive errors in BIP-2. For tributary board at the E3 level
or higher, it can be set whether to insert AIS when there are excessive errors in the B3
byte.
ALS
See automatic laser shutdown.
AM
See adaptive modulation.
AMI
See alternate mark inversion.
ANSI
See American National Standards Institute.
APD
See avalanche photodiode.
APID
access point identifier
APS
automatic protection switching
APS 1+1 protection
A protection architecture that comprises one protection facility and one working facility
and performs switchover by using the Automatic Protection Switching (APS) protocol.
Normally, signals are sent only over the working facility. If an APS switchover event is
detected by the working facility, services are switched over to the protection facility.
ARP
See Address Resolution Protocol.
AS
See autonomous system.
ASCII
American Standard Code for Information Interchange
ASK
amplitude shift keying
ATM
asynchronous transfer mode
ATM Adaptation
Layer (AAL)
An interface between higher-layer protocols and Asynchronous Transfer Mode (ATM).

The AAL provides a conversion function to and from ATM for various types of
information, including voice, video, and data.
ATM protection group Logically bound ATM VP network/subnetwork connections that share the same physical
transmission channel. In the VP Group (VPG), a pair of VP connections (working
connection and its protective connection) is used for monitoring the automatic protection
switching, called monitoring connections (APS VPCs). If the monitoring connections
switch over, the whole VPG will switch over to quicken the ATM protection switching
(as quick as the protection switching of the SDH layer).
ATPC
See automatic transmit power control.
AU
See administrative unit.
AUG
See administrative unit group.
AWG
arrayed waveguide grating
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.
Issue 03 (2012-11-30)

1313
OptiX OSN 7500 II/7500/3500/1500

B Glossary
American National
Standards Institute
(ANSI)
An organization that defines U.S standards for the information processing industry.
ANSI participates in defining network protocol standards.
Authentication,
Authorization and
Accounting (AAA)
A mechanism for configuring authentication, authorization, and accounting security

services. Authentication refers to the verification of user identities and the related
network services; authorization refers to the granting of network services to users
according to authentication results; and accounting refers to the tracking of the
consumption of network services by users.
access
A link between the customer and the telecommunication network. Many technologies,
such as the copper wire, optical fiber, mobile, microwave and satellite, are used for
access.
access control list

(ACL)
A list of entities, together with their access rights, which are authorized to have access
to a resource.
access layer
A layer that connects the end users (or last mile) to the ISP network. The access layer
devices are cost-effective and have high-density interfaces. In an actual network, the
access layer includes the devices and cables between the access points and the UPEs.
access point
Any entity that has station functionality and provides access to the distribution services,
via the wireless medium (WM) for associated stations.
accumulation
The sum of the service usage, consumption, and recharge fees of a subscriber.
active link
A link in the link aggregation group, which is connected to the active interface.
active mode
A working mode of EFM OAM. The discovery and remote loopback can only be initiated
by the interface in the active mode.
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.
adjacency
A portion of the local routing information which pertains to the reachability of a single
neighbor ES or IS over a single circuit. Adjacencies are used as input to the Decision
Process for forming paths through the routing domain. A separate adjacency is created
for each neighbor on a circuit, and for each level of routing (i.e. level 1 and level 2) on
a broadcast circuit.
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.
adjacent concatenation A situation where the virtual containers (VC) to carry concatenated services in SDH are
consecutive in terms of their service in the frame structures, so that they use the same
path overhead (POH).
administrative unit
(AU)
The information structure which provides adaptation between the higher order path layer
and the multiplex section layer. It consists of an information payload (the higher order
VC) and an AU pointer which indicates the offset of the payload frame start relative to
the multiplex section frame start.
administrative unit
group (AUG)
One or more administrative units occupying fixed, defined positions in an STM payload.
An AUG consists of AU-4s.
Issue 03 (2012-11-30)

1314
OptiX OSN 7500 II/7500/3500/1500

B Glossary
advanced ACL
An ACL that defines ACL rules based on the source addresses, target addresses, protocol
type, such as TCP source or target port, the type of the ICMP protocol, and message
codes.
aggregated link
Multiple signaling link sets between two nodes.
aging time
The time to live before an object becomes invalid.
air interface
The interface between the cellular phone set or wireless modem (usually portable or
mobile) and the active base station.
alarm
A message reported when a fault is detected by a device or by the network management

system during the process of polling devices. Each alarm corresponds to a recovery
alarm. After a recovery alarm is received, the status of the corresponding alarm changes
to cleared.
alarm box
A device that reflects the status of an alarm in visual-audio mode. The alarm box notifies
you of the alarm generation and alarm severity after it is connected to the Signaling
Network Manager server or client and the related parameters are set.
alarm cascading
The shunt-wound output of the alarm signals of several subracks or cabinets.
alarm correlation
analysis
A process to analyze correlated alarms. For example, if alarm 2 is generated within five
seconds after alarm 1 is generated, and it complies with the conditions defined in the
alarm correlation analysis rule, you can either mask the alarm or raise the level of alarm
2 according to the behavior defined in the alarm correlation rule.
alarm filtering
An alarm management method. Alarms are detected and reported to the NMS system,
and whether the alarm information is displayed and saved is decided by the alarm filtering
status. An alarm with the filtering status set to "Filter" is not displayed and saved on the
NMS, but is monitored on the NE.
alarm indication
A function that indicates the alarm status of an NE. On the cabinet of an NE, there are
four indicators in different colors indicating the current alarm status of the NE. When
the green indicator is on, the NE is powered on. When the red indicator is on, a critical
alarm is generated. When the orange indicator is on, a major alarm is generated. When
the yellow indicator is on, a minor alarm is generated. The ALM alarm indicator on the
front panel of a board indicates the current status of the board.
alarm inversion mode
A mode for an NE that indicates whether the port is automatically restored to the normal
status after the service is accessed or the fault is removed. There are three alarm inversion
modes: normal, revertible and non-revertible.
alarm notification
When an error occurs, the performance measurement system sends performance alarms
to the destination (for example, a file and/or fault management system) designated by
users.
alarm suppression
An alarm management method. Alarms that are set to be suppressed are not reported
from NEs any more.
alternate mark
inversion (AMI)
A synchronous clock encoding technique which uses bipolar pulses to represent logical
1 values.
analog signal
A signal in which information is represented with a continuously variable physical

quantity, such as voltage. Because of this constant changing of the wave shape with
regard to its passing a given point in time or space, an analog signal might have a virtually
indefinite number of states or values. This contrasts with a digital signal that is expressed
as a square wave and therefore has a very limited number of discrete states. Analog
signals, with complicated structures and narrow bandwidth, are vulnerable to external
interference.
Issue 03 (2012-11-30)

1315
OptiX OSN 7500 II/7500/3500/1500

B Glossary
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.
attack
An attempt to bypass security controls in a system with the mission of using that system
or compromising it. An attack is usually accomplished by exploiting a current
vulnerability.
attenuation
Reduction of signal magnitude or signal loss, usually expressed in decibels.
attenuator
A device used to increase the attenuation of an Optical Fiber Link. Generally used to
ensure that the signal at the receive end is not too strong.
automatic laser
shutdown (ALS)
A technique (procedure) to automatically shutdown the output power of laser transmitters

and optical amplifiers to avoid exposure to hazardous levels.
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
(AS)
A network set that uses the same routing policy and is managed by the same technology
administration department. Each AS has a unique identifier that is an integer ranging
from 1 to 65535. The identifier is assigned by IANA. An AS can be divided into areas.
availability
A capability of providing services at any time. The probability of this capability is called
availability.
available bit rate (ABR) A kind of service categories defined by the ATM forum. ABR only provides possible
forwarding service and applies to the connections that does not require the real-time
quality. It does not provide any guarantee in terms of cell loss or delay.
avalanche photodiode
(APD)
A semiconductor photodetector with integral detection and amplification stages.

Electrons generated at a p/n junction are accelerated in a region where they free an
avalanche of other electrons. APDs can detect faint signals but require higher voltages
than other semiconductor electronics.
average delay
A performance indicator indicating the average RTT of multiple ping operations or other
probe operations. It is expressed in milliseconds.
B
B-ISDN
See broadband integrated services digital network.
BA
booster amplifier
BBE
background block error
BC
boundary clock
BCD
binary coded decimal
BDI
See backward defect indication.
BDI packet
A packet used to notify the upstream LSR of the failure event which has occurred on the
downstream LSR through the reverse LSP. The BDI packet can be used in the 1:1/N
protective switchover service.
BE
See best effort.
BER
bit error rate
Issue 03 (2012-11-30)

1316
OptiX OSN 7500 II/7500/3500/1500

B Glossary
BFD
See Bidirectional Forwarding Detection.
BGP
Border Gateway Protocol
BIP
See bit interleaved parity.
BIP-8
See bit interleaved parity-8.
BIP-X
bit interleaved parity-X
BITS
See building integrated timing supply.
BMC
best master clock
BNC
See bayonet-neill-concelman.
BPDU
See bridge protocol data unit.
BPS
board protection switching
BSC
See base station controller.
BSS
base station subsystem
BTS
base transceiver station
BWS
backbone wavelength division multiplexing system
Bidirectional
Forwarding Detection
(BFD)
A simple Hello protocol, similar to the adjacent detection in the route protocol. Two
systems periodically send BFD detection messages on the channel between the two
systems. If one system does not receive the detection message from the other system for
a long time, you can infer that the channel is faulty. Under some conditions, the TX and
RX rates between systems need to be negotiated to reduce traffic load.
backbone network
A network that forms the central interconnection for a connected network. The
communication backbone for a country is WAN. The backbone network is an important
architectural element for building enterprise networks. It provides a path for the exchange
of information between different LANs or subnetworks. A backbone can tie together
diverse networks in the same building, in different buildings in a campus environment,
or over wide areas. Generally, the backbone network's capacity is greater than the
networks connected to it.
backplane
An electronic circuit board containing circuits and sockets into which additional
electronic devices on other circuit boards or cards can be plugged.
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.
backward defect
indication (BDI)
A function that the sink node of a LSP, when detecting a defect, uses to inform the
upstream end of the LSP of a downstream defect along the return path.
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.
base station area
An area of radio coverage consisting of cells served by one or more Base Transceiver
Stations (BTSs) in the same base station site.
Issue 03 (2012-11-30)

1317
OptiX OSN 7500 II/7500/3500/1500

B Glossary
base station controller

(BSC)
A logical entity that connects the BTS with the MSC in a GSM/CDMA network. It
interworks with the BTS through the Abis interface, the MSC through the A interface.
It provides the following functions: radio resource management, base station
management, power control, handover control, and traffic measurement. One BSC
controls and manages one or more BTSs in an actual network.
baseband
A form of modulation in which the information is applied directly onto the physical
transmission medium.
bayonet-neillconcelman (BNC)
A connector used for connecting two coaxial cables.
bearer
An information transmission path with defined capacity, delay and bit error rate.
bearer network
A network used to carry the messages of a transport-layer protocol between physical

devices.
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.
best-effort service
A unitary and simple service model. Without being approved, but after notifying the
network, the application can send any number of packets at any time. The network tries
its best to send the packets, but delay and reliability cannot be ensured. Best-Effort is
the default service model of the Internet. It can be applied to various networks, such as
FTP and E-Mail. It is implemented through the First In First-Out (FIFO) queue.
bit error
An incompatibility between a bit in a transmitted digital signal and the corresponding

bit in the received digital signal.
bit interleaved parity

(BIP)
A method of error monitoring. With even parity an X-bit code is generated by equipment
at the transmit end over a specified portion of the signal in such a manner that the first
bit of the code provides even parity over the first bit of all X-bit sequences in the covered
portion of the signal, the second bit provides even parity over the second bit of all X-bit
sequences within the specified portion, and so on. Even parity is generated by setting the
BIP-X bits so that there is an even number of 1s in each monitored partition of the signal.
A monitored partition comprises all bits which are in the same bit position within the Xbit sequences in the covered portion of the signal. The covered portion includes the BIPX.
bit interleaved parity-8 Consists of a parity byte calculated bit-wise across a large number of bytes in a
transmission transport frame. Divide a frame is into several blocks with 8 bits (one byte)
(BIP-8)
in a parity unit and then arrange the blocks in matrix. Compute the number of "1" or "0"
over each column. Then fill a 1 in the corresponding bit for the result if the number is
odd, otherwise fill a 0.
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.
bound path
A parallel path with several serial paths bundled together. It improves the data throughput
capacity.
Issue 03 (2012-11-30)

1318
OptiX OSN 7500 II/7500/3500/1500

B 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.
bridge protocol data

unit (BPDU)
The data messages that are exchanged across the switches within an extended LAN that
uses a spanning tree protocol (STP) topology. BPDU packets contain information on
ports, addresses, priorities and costs and ensure that the data ends up where it was
intended to go. BPDU messages are exchanged across bridges to detect loops in a
network topology. The loops are then removed by shutting down selected bridges
interfaces and placing redundant switch ports in a backup, or blocked, state.
bridging
The action of transmitting identical traffic on the working and protection channels
simultaneously.
broadband integrated A standard defined by the ITU-T to handle high-bandwidth applications, such as voice.
services digital network It currently uses the ATM technology to transmit data over SONNET-based circuits at
(B-ISDN)
155 to 622 Mbit/s or higher speed.
broadcast
A means of delivering information to all members in a network. The broadcast range is

determined by the broadcast address.
broadcast address
A network address in computer networking that allows information to be sent to all nodes
on a network, rather than to a specific network host.
broadcast domain
A group of network stations that receives broadcast packets originating from any device
within the group. The broadcast domain also refers to the set of ports between which a
device forwards a multicast, broadcast, or unknown destination frame.
building integrated
timing supply (BITS)
In the situation of multiple synchronous nodes or communication devices, one can use
a device to set up a clock system on the hinge of telecom network to connect the
synchronous network as a whole, and provide satisfactory synchronous base signals to
the building integrated device. This device is called BITS.
built-in WDM
A function which integrates some simple WDM systems into products that belong to the
OSN series. That is, the OSN products can add or drop several wavelengths directly.
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
CAC
See connection admission control.
CAR
committed access rate
CAS multiframe
A multiframe set up based on timeslot 16. Each CAS multiframe contains 16 E1 PCM
frames. Among the 8 bits of timeslot 16 in the first frame, the first 4 bits are used for
multiframe synchronization. The multiframe alignment signal (MFAS) for
synchronization is 0000. The last 4 bits are used as the not multiframe alignment signal
(NMFAS). The NMFAS is XYXX. For the other 15 frames, timeslot 16 is used to
transmit exchange and multiplexing (E&M) signaling corresponding to each timeslot.
CBR
See constant bit rate.
CBS
See committed burst size.
CC
See continuity check.
Issue 03 (2012-11-30)

1319
OptiX OSN 7500 II/7500/3500/1500

B Glossary
CCDP
See co-channel dual polarization.
CCS
See Common Channel Signaling.
CDVT
cell delay variation tolerance
CE
See customer edge.
CES
See circuit emulation service.
CFM
connectivity fault management
CFR
cell fill rate
CIR
committed information rate
CIST
See Common and Internal Spanning Tree.
CLEI
common language equipment identification
CLK
clock card
CLNP
connectionless network protocol
CLP
See cell loss priority.
CMI
coded mark inversion
CO
central office
CPU
See central processing unit.
CR
connection request
CRC
See cyclic redundancy check.
CRC-4 multiframe
A multiframe recommended by ITU-T G.704 and set up based on the first bit of timeslot
0. The CRC-4 multiframe is different from the CAS multiframe in principle and
implementation. Each CRC-4 multiframe contains 16 PCM frames. Each CRC-4
multiframe consists of two CRC-4 sub-multiframes. Each CRC-4 sub-multiframe is a
CRC-4 check block that contains 2048 (256 x 8) bits. Bits C1 to C4 of a check block can
check the previous check block.
CSA
Canadian Standards Association
CSES
consecutive severely errored second
CSF
Client Signal Fail
CSMA/CD
See carrier sense multiple access with collision detection.
CST
See common spanning tree.
CTC
common transmit clock
CV
connectivity verification
CV packet
A type of packet that is generated at the frequency of 1/s on the source end LSR of an
LSP, and is terminated on the destination end LSR of the LSP. A CV packet is transmitted
from the source end LSR to the destination LSR along the LSP. A CV packet contains
the unique identifier (TTSI) of the LSP so that all types of abnormalities on the path can
be detected.
CW
control word
CWDM
See coarse wavelength division multiplexing.
Issue 03 (2012-11-30)

1320
OptiX OSN 7500 II/7500/3500/1500

Common Channel
Signaling (CCS)
B Glossary
A signaling system used in telephone networks that separates signaling information from
user data. A specified channel is exclusively designated to carry signaling information
for all other channels in the system.
Common and Internal The single spanning tree jointly calculated by STP and RSTP, the logical connectivity
Spanning Tree (CIST) using MST bridges and regions, and MSTP. The CIST ensures that all LANs in the
bridged local area network are simply and fully connected.
Coordinated Universal The world-wide scientific standard of timekeeping. It is based upon carefully maintained
Time (UTC)
atomic clocks and is kept accurate to within microseconds worldwide.
cabinet
Free-standing and self-supporting enclosure for housing electrical and/or electronic

equipment. It is usually fitted with doors and/or side panels which may or may not be
removable.
cable distribution plate A component, which is used to arrange cables in order.

cable tie
A tape used to bind cables.
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.
cell loss priority (CLP) A field in the ATM cell header that determines the probability of a cell being dropped
if the network becomes congested. Cells with CLP = 0 are insured traffic, which is
unlikely to be dropped. Cells with CLP = 1 are best-effort traffic, which might be
dropped.
central processing unit The computational and control unit of a computer. The CPU is the device that interprets
(CPU)
and executes instructions. The CPU has the ability to fetch, decode, and execute
instructions and to transfer information to and from other resources over the computer's
main data-transfer path, the bus.
centralized alarm
The alarms of all the hosts connecting to the Operation and Maintenance Unit (OMU).
channel
A telecommunication path of a specific capacity and/or at a specific speed between two

or more locations in a network. Channels can be established through wire, radio
(microwave), fiber or a combination of the three. The amount of information transmitted
per second in a channel is the information transmission speed, expressed in bits per
second. For example, b/s, kb/s, Mb/s, Gb/s, and Tb/s.
channel spacing
The center-to-center difference in frequency or wavelength between adjacent channels

in a WDM device.
check criteria
A set of rules for checking and analyzing device echo information. The check criteria
for an alarm collection item need to be set through the configuration file.
circuit emulation
service (CES)
A function with which the E1/T1 data can be transmitted through ATM networks. At the
transmission end, the interface module packs timeslot data into ATM cells. These ATM
cells are sent to the reception end through the ATM network. At the reception end, the
interface module re-assigns the data in these ATM cells to E1/T1 timeslots. The CES
technology guarantees that the data in E1/T1 timeslots can be recovered to the original
sequence at the reception end.
Issue 03 (2012-11-30)

1321
OptiX OSN 7500 II/7500/3500/1500

B Glossary
clock selection
An algorithm used for selecting the best clock for clock synchronization. For different
peers (multiple servers or peers configured for a client), a peer sends clock
synchronization packets to each server or passive peer. After receiving the response
packets, it uses the clock selection algorithm to select the best clock.
clock source
A device that provides standard time for the NTP configuration.
clock synchronization
Also called frequency synchronization. The signal frequency traces the reference
frequency, but the start point does not need to be consistent.
clock tracing
The method to keep the time on each node synchronized with a clock source in a network.
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.
coarse wavelength
division multiplexing
(CWDM)
A signal transmission technology that multiplexes widely-spaced optical channels into

the same fiber. CWDM widely spaces wavelengths at a spacing of several nm. CWDM
does not support optical amplifiers and is applied in short-distance chain networking.
collision
A condition in which two packets are being transmitted over a medium at the same time.
Their interference makes both unintelligible.
committed burst size

(CBS)
A parameter used to define the capacity of token bucket C, that is, the maximum burst
IP packet size when the information is transferred at the committed information rate.
This parameter must be larger than 0. It is recommended that this parameter should be
not less than the maximum length of the IP packet that might be forwarded.
common spanning tree A single spanning tree that connects all the MST regions in a network. Every MST region
(CST)
is considered as a switch; therefore, the CST can be considered as their spanning tree
generated with STP/RSTP.
composite service
An aggregation of a series of services relevant to each other.
conference
An IP multimedia session that have two or more participants. Each conference has a
focus and can be identified uniquely.
congestion
An extra intra-network or inter-network traffic that results in a decrease in network

service efficiency.
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.
connection
An association of transmission channels or telecommunication circuits, switching and

other functional units set up to provide for the transfer of signals between two or more
network points, to support a single communication.
connection admission
control (CAC)
A control process in which the network takes actions in the call set-up phase (or call renegotiation phase) to determine which connection request is admitted.
connection point
A reference point where the output of a trail termination source or a connection is bound
to the input of another connection, or where the output of a connection is bound to the
input of a trail termination sink or another connection. The connection point is
characterized by the information which passes across it. A bidirectional connection point
is formed by the association of a contradirectional pair.
connectionless
Pertaining to a method of data presentation. The data has a complete destination address
and is delivered by the network on a best-effort basis, independent of other data being
exchanged between the same pair of users.
Issue 03 (2012-11-30)

1322
OptiX OSN 7500 II/7500/3500/1500

B Glossary
constant bit rate (CBR) A kind of service categories defined by the ATM forum. CBR transfers cells based on
the constant bandwidth. It is applicable to service connections that depend on precise
clocking to ensure undistorted transmission.
container
A set of hardware or software devices. In software domain, it refers to the environment

variables and processes. In hardware domain, it refers to a type of topology node that
contains nodes, usually refers to one device with multiple frames; each node stands for
a frame.
continuity check (CC)
Ethernet CFM can detect the connectivity between MEPs. The detection is achieved after
MEPs transmit Continuity Check Messages (CCMs) periodically.
control VLAN
A VLAN that transmits only protocol packets.
control channel
The channel used to transmit digital control information from the base station to a cell
phone or vice-versa.
convergence layer
A "bridge" between the access layer and the core layer. The convergence layer provides
the convergence and forwarding functions for the access layer. It processes all the traffic
from the access layer devices, and provides the uplinks to the core layer. Compared with
the access layer, the convergence layer devices should have higher performance, fewer
interfaces and higher switching rate. In the real network, the convergence layer refers to
the network between UPEs and PE-AGGs.
cooling system
The system that controls or influences climate by decreasing the air temperature only.
core layer
A layer that functions as the backbone of high speed switching for networks and provides
high speed forwarding communications. It has a backbone transmission structure that
provides high reliability, high throughput, and low delay. The core layer devices must
have a good redundancy, error tolerance, manageability, adaptability, and they support
dual-system hot backup or load balancing technologies. In a real network, the core layer
includes the IP/MPLS backbone network consisting of NPEs and backbone routers.
correlation
The similarities when two random processes vary with time.
corruption
The alteration of the information in IMS networks for the purpose of deception. For
example, attackers corrupt the correct charging information to evade being charged.
cross-connection
The connection of channels between the tributary board and the line board, or between
line boards inside the NE. Network services are realized through the cross-connections
of NEs.
crossover cable
A twisted pair patch cable wired in such a way as to route the transmit signals from one
piece of equipment to the receive signals of another piece of equipment, and vice versa.
crystal oscillator
An oscillator that produces electrical oscillations at a frequency determined by the

physical characteristics of a piezoelectric quartz crystal.
customer edge (CE)
A part of BGP/MPLS IP VPN model. It provides interfaces for direct connection to the
Service Provider (SP) network. A CE can be a router, switch, or host.
cutover
To migrate the data of an application system to another application system, which then
provides services.
Issue 03 (2012-11-30)

1323
OptiX OSN 7500 II/7500/3500/1500

cyclic redundancy
check (CRC)
B Glossary
A procedure used in checking for errors in data transmission. CRC error checking uses
a complex calculation to generate a number based on the data transmitted. The sending
device performs the calculation before transmission and includes it in the packet that it
sends to the receiving device. The receiving device repeats the same calculation after
transmission. If both devices obtain the same result, it is assumed that the transmission
was error free. The procedure is known as a redundancy check because each transmission
includes not only data but extra (redundant) error-checking values.
D
D/A
digital-analog converter
DB
database
DC
direct current
DC-C
See DC-return common (with ground).
DC-I
See DC-return isolate (with ground).
DC-return common
(with ground) (DC-C)
A power system, in which the BGND of the DC return conductor is short-circuited with
the PGND on the output side of the power supply cabinet and also on the line between
the output of the power supply cabinet and the electric equipment.
DC-return isolate (with A power system, in which the BGND of the DC return conductor is short-circuited with
ground) (DC-I)
the PGND on the output side of the power supply cabinet and is isolated from the PGND
on the line between the output of the power supply cabinet and the electric equipment.
DCC
See data communications channel.
DCE
See data circuit-terminating equipment.
DCF
data communication function
DCM
See dispersion compensation module.
DCN
See data communication network.
DDF
digital distribution frame
DDN
See digital data network.
DHCP
See Dynamic Host Configuration Protocol.
DLAG
See distributed link aggregation group.
DM
See delay measurement.
DNI
dual node interconnection
DRDB
dynamic random database
DS interior node
A DS node located at the center of a DS domain. It is a non-DS boundary node.
DS node
A DS-compliant node, which is subdivided into DS boundary node and ID interior node.
DSCP
differentiated services code point
DSL
See digital subscriber line.
DSLAM
See digital subscriber line access multiplexer.
DSP
digital signal processing
DTE
See data terminal equipment.
Issue 03 (2012-11-30)

1324
OptiX OSN 7500 II/7500/3500/1500

B Glossary
DTR
data terminal ready
DVB
digital video broadcasting
DVB-ASI
digital video broadcast-asynchronous serial interface
DVMRP
See Distance Vector Multicast Routing Protocol.
DWDM
See dense wavelength division multiplexing.
Distance Vector
Multicast Routing
Protocol (DVMRP)
An Internet gateway protocol mainly based on the RIP. The protocol implements a typical
dense mode IP multicast solution. The DVMRP protocol uses IGMP to exchange routing
datagrams with its neighbors.
Dynamic Host
A client-server networking protocol. A DHCP server provides configuration parameters
Configuration Protocol specific to the DHCP client host requesting, generally, information required by the host
(DHCP)
to participate on the Internet network. DHCP also provides a mechanism for allocation
of IP addresses to hosts.
data backup
A method that is used to copy key data to the standby storage area, to prevent data loss
in the case of damage or failure in the original storage area.
data circuitThe equipment that provides the signal conversion and coding between the data terminal
terminating equipment equipment (DTE) and the line. A DCE is located at a data station. The DCE may be
(DCE)
separate equipment, or an integral part of the DTE or intermediate equipment. The DCE
may perform other functions that are normally performed at the network end of the line.
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.
data flow
A process that involves processing the data extracted from the source system, such as
filtering, integration, calculation, and summary, finding and solving data inconsistency,
and deleting invalid data so that the processed data meets the requirements of the
destination system for the input data.
data mapping
An algorithm that is used to convert the data between heterogeneous data models.
data restoration
A method for retrieving data that is lost due to damage or misoperations.
data terminal
equipment (DTE)
A user device composing the UNI. The DTE accesses the data network through the DCE
equipment (for example, a modem) and usually uses the clock signals produced by DCE.
datagram
A kind of protocol data unit (PDU) which is used in Connectionless Network Protocol
(CLNP), such as IP datagram, UDP datagram.
defect
A limited interruption in the ability of an item to perform a required function.
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.
demodulation
In communications, the means by which a modem converts data from modulated carrier
frequencies (waves that have been modified in such a way that variations in amplitude
and frequency represent meaningful information) over a telephone line. Data is converted
to the digital form needed by a computer to which the modem is attached, with as little
distortion as possible.
Issue 03 (2012-11-30)

1325
OptiX OSN 7500 II/7500/3500/1500

B Glossary
dense wavelength
division multiplexing
(DWDM)
The technology that utilizes the characteristics of broad bandwidth and low attenuation
of single mode optical fiber, employs multiple wavelengths with specific frequency
spacing as carriers, and allows multiple channels to transmit simultaneously in the same
fiber.
designated port
A port defined in the STP protocol. On each switch that runs the STP protocol, the traffic
from the root bridge is forwarded to the designated port. The subnet connected to the
STP switch receives the data traffic from the root bridge. All the ports on the root bridge
are designated ports. On each subnet, there is only one designated port. When a network
topology is stable, only the root port and the designated port forward traffic. Other nondesignated ports are in the blocking state, and they receive STP packets, but does not
forward user traffic.
destruction
A process during which the information and resources in a network are changed
unexpectedly and the meanings of the information and resources are deleted or changed.
digital data network

(DDN)
A high-quality data transport tunnel that combines the digital channel (such as fiber
channel, digital microwave channel, or satellite channel) and the cross multiplex
technology.
digital modulation
A method that controls the changes in amplitude, phase, and frequency of the carrier
based on the changes in the baseband digital signal. In this manner, the information can
be transmitted by the carrier.
digital network
A telecommunication network where information is first converted into distinct

electronic pulses and then transmitted to a digital bit stream.
digital signal
A signal in which information is represented by a limited number of discrete states

number of discrete states (for example, high and low voltages) rather than by fluctuating
levels in a continuous stream, as in an analog signal. In the pulse code modulation (PCM)
technology, the 8 kHz sampling frequency is used and a byte contains 8 bits in length.
Therefore, a digital signal is also referred to as a byte-based code stream. Digital signals,
with simple structures and broad bandwidth, are easy to shape or regenerate, and are not
easily affected by external interference.
digital subscriber line

(DSL)
A technology for providing digital connections over the copper wire or the local
telephone network. DSL performs data communication over the POTS lines without
affecting the POTS service.

access multiplexer
(DSLAM)
A network device, usually situated in the main office of a telephone company that
receives signals from multiple customer Digital Subscriber Line (DSL) connections and
puts the signals on a high-speed backbone line using multiplexing techniques.
dispersion
The dependence of refraction on the wavelength of light. Different wavelengths are

transmitted in an optical medium at different speeds. Wavelengths reach the end of the
medium at different times. As a result, the light pulse spreads and the dispersion occurs.
dispersion
compensation module
(DCM)
A module, which contains dispersion compensation fibers to compensate for the

dispersion of transmitting fiber.
distributed link
aggregation group
(DLAG)
A board-level port protection technology used to detect unidirectional fiber cuts and to
negotiate with the opposite end. Once a link down failure occurs on a port or a hardware
failure occurs on a board, the services can automatically be switched to the slave board,
achieving 1+1 protection for the inter-board ports.
domain
A logical subscriber group based on which the subscriber rights are controlled.
Issue 03 (2012-11-30)

1326
OptiX OSN 7500 II/7500/3500/1500

B Glossary
dotted decimal notation A format of IP address. IP addresses in this format are separated into four parts by a dot
"." with each part is in the decimal numeral.
download
To obtain data from an upper-layer device or the server.
downstream
In an access network, the direction of transmission toward the subscriber end of the link.
dual-ended switching
A protection operation method which takes switching action at both ends of the protected
entity (for example, "connection", "path"), even in the case of a unidirectional failure.
dual-polarized antenna An antenna intended to simultaneously radiate or receive two independent radio waves
orthogonally polarized.
E
E-Aggr
See Ethernet aggregation.
E-LAN
See Ethernet local area network.
E-Line
See Ethernet line.
EA
encryption algorithm
EBS
See excess burst size.
ECC
See embedded control channel.
EDFA
See erbium-doped fiber amplifier.
EEPROM
See electrically erasable programable read-only memory.
EF
See expedited forwarding.
EFCI
explicit forward congestion indication
EFM
Ethernet in the First Mile
EFM OAM
Ethernet in the first mile OAM
EIA
See Electronic Industries Alliance.
EIR
See excess information rate.
EMC
See electromagnetic compatibility.
EMI
See electromagnetic interference.
EMS
element management system
EPD
early packet discard
EPL
See Ethernet private line.
EPLAN
See Ethernet private LAN service.
ERPS
Ethernet ring protection switching
ESC
See electric supervisory channel.
ESCON
See enterprise system connection.
ESD
electrostatic discharge
ESN
See equipment serial number.
ETS
European Telecommunication Standards
ETSI
See European Telecommunications Standards Institute.
Issue 03 (2012-11-30)

1327
OptiX OSN 7500 II/7500/3500/1500

B Glossary
EVC
Ethernet virtual connection
EVPL
See Ethernet virtual private line.
EVPLAN
See Ethernet virtual private LAN service.
EXP
See experimental bits.
Electronic Industries
Alliance (EIA)
An association based in Washington, D.C., with members from various electronics

manufacturers. It sets standards for electronic components. RS-232-C, for example, is
the EIA standard for connecting serial components.
EoD
See Ethernet over dual domains.
Ethernet
A LAN technology that uses Carrier Sense Multiple Access/Collision Detection. The
speed of an Ethernet interface can be 10 Mbit/s, 100 Mbit/s, 1000 Mbit/s or 10000 Mbit/
s. An Ethernet network features high reliability and is easy to maintain.
Ethernet aggregation
(E-Aggr)
A type of Ethernet service that is based on a multipoint-to-point EVC (Ethernet virtual

connection).
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).
Ethernet over dual

domains (EoD)
A type of boards. EoD boards bridge the PSN and TDM networks, enabling Ethernet
service transmission across PSN and TDM networks.
Ethernet private LAN

service (EPLAN)
A type of Ethernet service provided by SDH, PDH, ATM, or MPLS networks. This
service is carried over a dedicated bridge and point-to-multipoint connections.
Ethernet private line

(EPL)
A type of Ethernet service that is provided with dedicated bandwidth and point-to-point
connections on an SDH, PDH, ATM, or MPLS server layer network.
Ethernet virtual
private LAN service
(EVPLAN)
service is carried over a shared bridge and point-to-multipoint connections.
Ethernet virtual
private line (EVPL)
service is carried over a shared bridge and point-to-point connections.
European
Telecommunications
Standards Institute
(ETSI)
A standards-setting body in Europe. Also the standards body responsible for GSM.
eSFP
enhanced small form-factor pluggable
egress
The egress LER. The group is transferred along the LSP consisting of a series of LSRs
after the group is labeled.
electric supervisory
channel (ESC)
A technology that implements communication among all the nodes and transmission of
monitoring data in an optical transmission network. The monitoring data of ESC is
introduced into DCC service overhead and is transmitted with service signals.
electrically erasable
A type of EPROM that can be erased with an electrical signal. It is useful for stable
programable read-only storage for long periods without electricity while still allowing reprograming. EEPROMs
memory (EEPROM)
contain less memory than RAM, take longer to reprogram, and can be reprogramed only
a limited number of times before wearing out.
Issue 03 (2012-11-30)

1328
OptiX OSN 7500 II/7500/3500/1500

B 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.
electromagnetic
interference (EMI)
Any electromagnetic disturbance that interrupts, obstructs, or otherwise degrades or

limits the effective performance of electronics/electrical equipment.
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.
emergency
maintenance
A type of measure taken to quickly rectify an emergency fault to recover the proper
running of the related system or device and to reduce losses.
encapsulation
A technology for layered protocols, in which a lower-level protocol accepts a message

from a higher-level protocol and places it in the data portion of the lower-level frame.
Protocol A's packets have complete header information, and are carried by protocol B
as data. Packets that encapsulate protocol A have a B header, an A header, followed by
the information that protocol A is carrying. Note that A could equal to B, as in IP inside
IP.
engineering label
A mark on a cable, a subrack, or a cabinet for identification.
enterprise system
connection (ESCON)
A path protocol which connects the host with various control units in a storage system.
It is a serial bit stream transmission protocol. The transmission rate is 200 Mbit/s.
entity
A part, device, subsystem, functional unit, equipment, or system that can be considered
individually.
equalization
A method of avoiding selective fading of frequencies. Equalization can compensate for

the changes of amplitude frequency caused by frequency selective fading.
equipment serial
number (ESN)
A string of characters that identify a piece of equipment and ensures correct allocation
of a license file to the specified equipment. It is also called "equipment fingerprint".
erbium-doped fiber
amplifier (EDFA)
An optical device that amplifies the optical signals. The device uses a short length of
optical fiber doped with the rare-earth element Erbium and the energy level jump of
Erbium ions activated by pump sources. When the amplifier passes the external light
source pump, it amplifies the optical signals in a specific wavelength range.
error tolerance
The ability of a system or component to continue normal operation despite the presence
of erroneous inputs.
event
Anything that takes place on the managed object. For example, the managed object is
added, deleted, or modified.
excess burst size (EBS) A parameter related to traffic. In the single rate three color marker (srTCM) mode, the
traffic control is achieved by the token buckets C and E. Excess burst size is a parameter
used to define the capacity of token bucket E, that is, the maximum burst IP packet size
when the information is transferred at the committed information rate. This parameter
must be larger than 0. It is recommended that this parameter should be not less than the
maximum length of the IP packet that might be forwarded.
excess information rate The bandwidth for excessive or burst traffic above the CIR; it equals the result of the
(EIR)
actual transmission rate without the safety rate.
exercise switching
Issue 03 (2012-11-30)
An operation to check whether the protection switching protocol functions properly. The
protection switching is not really performed.

1329
OptiX OSN 7500 II/7500/3500/1500

B Glossary
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".
experimental bits
(EXP)
A field in the MPLS packet header, three bits long. This field is always used to identify
the CoS of the MPLS packet.
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.
external cable
The cables and optical fibers which are used for connecting electrical interfaces and
optical interfaces of one cabinet to interfaces of other cabinets or peripherals.
external links
The links between the current Web site and other Web sites. Generally, external links
refer to links from other Web sites to the current Web site.
extract
To read the data required by the destination system from the source system.
F
F1 byte
The user path byte, which is reserved for the user, but is typically special for network
providers. The F1 byte is mainly used to provide the temporary data or voice path for
special maintenance objectives. It belongs to the regenerator section overhead byte.
FC
See fiber channel.
FDB
flash database
FDD
See frequency division duplex.
FDDI
See fiber distributed data interface.
FDI
See forward defect indication.
FDI packet
See forward defect indication packet.
FDV
See frame delay variation.
FE
See fast Ethernet.
FE port
See fast Ethernet port.
FEC
See forward error correction.
FFD
fast failure detection
FFD packet
A path failure detection method independent from CV. Different from a CV packet, the
frequency for generating FFD packets is configurable to satisfy different service
requirements. By default, the frequency is 20/s. An FFD packet contains information the
same as that in a CV packet. The destination end LSR processes FFD packets in the same
way for processing CV packets.
FICON
See Fiber Connect.
FIFO
first in first out queuing
FLR
See frame loss ratio.
FPGA
See field programmable gate array.
FPS
See fast protection switching.
Issue 03 (2012-11-30)

1330
OptiX OSN 7500 II/7500/3500/1500

B Glossary
FR
See frame relay.
FRU
field replaceable unit
FTN
FEC to NHLFE
FTP
File Transfer Protocol
Fiber Connect
(FICON)
A new generation connection protocol which connects the host to various control units.
It carries single byte command protocol through the physical path of fiber channel, and
provides higher rate and better performance than ESCON.
fairness
A feature in which for any link specified in a ring network, the source node is provided
with certain bandwidth capacities if the data packets transmitted by the source node are
constrained by the fairness algorithm.
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).
fast Ethernet port (FE

port)
The port that provides a rate of 100 Mbit/s.
fast protection
switching (FPS)
A type of pseudo wire automatic protection switching (PW APS). When the working
PW is faulty, the source transmits services to the protection PW and the sink receives
the services from the protection PW. FPS generally works with the interworking function
(IWF) to provide end-to-end protection for services.
fault
A failure to implement the function while the specified operations are performed. A fault
does not involve the failure caused by preventive maintenance, insufficiency of external
resources or intentional settings.
fault alarm
A type of alarm caused by hardware and/or software faults, for example, board failure,
or by the exception that occurs in major functions. After handling, a fault alarm can be
cleared, upon which the NE reports a recovery alarm. Fault alarms are of higher severity
than event alarms.
fault detection
The process of determining that a fault has occurred.
fault notification
A process wherein a fault is notified. For example, when a fault occurs on the local
interface, the local interface notifies the peer of the fault through OAMPDUs. The local
interface then records the fault in the log, and reports it to the NMS.
feeder
1. A radio frequency transmission line interconnecting an antenna and a transmitter or

receiver. 2. For an antenna comprising more than one driven element, a radio frequency
transmission Line interconnecting the antenna input and a driven element.
fiber channel (FC)
A high-speed transport technology used to build storage area networks (SANs). Fiber
channel can be on the networks carrying ATM and IP traffic. It is primarily used for
transporting SCSI traffic from servers to disk arrays. Fiber channel supports single-mode
and multi-mode fiber connections. Fiber channel signaling can run on both twisted pair
copper wires and coaxial cables. Fiber channel provides both connection-oriented and
connectionless services.
Issue 03 (2012-11-30)

1331
OptiX OSN 7500 II/7500/3500/1500

B Glossary
fiber distributed data

interface (FDDI)
A standard developed by the American National Standards Institute (ANSI) for highspeed fiber-optic local area networks (LANs). FDDI provides specifications for
transmission rates of 100 megabits (100 million bits) per second on networks based on
the token ring network.
fiber trough
A trough that is used for routing fibers.
fiber/cable
General name of optical fiber and cable. It refers to the physical entities that connect the
transmission equipment, carry transmission objects (user information and network
management information) and perform the transmission function in the transmission
network. The optical fiber transmits optical signal, while the cable transmits electrical
signal. The fiber/cable between NEs represents the optical fiber connection or cable
connection between NEs. The fiber/cable between SDH NEs represents the connection
relationship between NEs. At this time, the fiber/cable is of optical fiber type.
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.
firewall
A combination of a series of components set between different networks or network

security domains. By monitoring, limiting, and changing the data traffic across the
firewall, it masks the interior information, structure and running state of the network as
much as possible to protect the network security.
fixed bandwidth
The bandwidth that is fully reserved and is allocated periodically in a GPON system to
ensure the quality of cell transmission. If a T-CONT is provided with a fixed bandwidth
and does not transmit cells, the OLT can still allocate/assign the fixed bandwidth.
Therefore, idle cells are transmitted to the upstream OLT from the ONU/ONT.
flash memory
A type of special electrically erasable programmable read-only memory (EEPROM) and

can be erased and rewritten in blocks at a time instead of only one byte. The data stored
in flash memory will not be lost if the flash memory is powered off.
flooding
A type of incident, such as insertion of a large volume of data, that results in denial of
service.
flow
An aggregation of packets that have the same characteristics. On the network

management system or NE software, flow is a group of classification rules. On boards,
it is a group of packets that have the same quality of service (QoS) operation.
flow queue
The same type of services of a user is considered one service flow. HQoS performs queue
scheduling according to the services of each user. The service flows of each user are
classified into four FQs, namely, CS, EF, AF, and BE. CS is assigned a traffic shaping
percentage for Priority Queuing (PQ); EF, AF, and BE are assigned weights for Weighted
Fair Queuing (WFQ). The preceding two scheduling modes occupy a certain bandwidth
each; they can act at the same time without interfering each other.
forward defect
indication (FDI)
A packet generated and traced forward to the sink node of the LSP by the node that first
detects defects. It includes fields to indicate the nature of the defect and its location. Its
primary purpose is to suppress alarms being raised at affected higher level client LSPs
and (in turn) their client layers.
forward defect
A packet that responds to the detected failure event. It is used to suppress alarms of the
indication packet (FDI upper layer network where failure has occurred.
packet)
Issue 03 (2012-11-30)

1332
OptiX OSN 7500 II/7500/3500/1500

B Glossary
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.
fragmentation
A process of breaking a packet into smaller units when transmitting over a network node
that does not support the original size of the packet.
frame delay variation

(FDV)
A measurement of the variations in the frame delay between a pair of service frames,
where the service frames belong to the same CoS instance on a point to point ETH
connection.
frame loss ratio (FLR) A ratio, is expressed as a percentage, of the number of service frames not delivered
divided by the total number of service frames during time interval T, where the number
of service frames not delivered is the difference between the number of service frames
arriving at the ingress ETH flow point and the number of service frames delivered at the
egress ETH flow point in a point-to-point ETH connection.
frame relay (FR)
A packet-switching protocol used for WANs. Frame relay transmits variable-length

packets at up to 2 Mbit/s over predetermined, set paths known as PVCs (permanent
virtual circuits). It is a variant of X.25 but sacrifices X.25's error detection for the sake
of speed.
free-run mode
An operating condition of a clock, the output signal of which is strongly influenced by

the oscillating element and not controlled by servo phase-locking techniques. In this
mode the clock has never had a network reference input, or the clock has lost external
reference and has no access to stored data, that could be acquired from a previously
connected external reference. Free-run begins when the clock output no longer reflects
the influence of a connected external reference, or transition from it. Free-run terminates
when the clock output has achieved lock to an external reference.
frequency division
duplex (FDD)
An application in which channels are divided by frequency. In an FDD system, the uplink
and downlink use different frequencies. Downlink data is sent through bursts. Both
uplink and downlink transmission use frames with fixed time length.
full rate
A type of data transmission rate. The service bandwidth can be 9.6 kbit/s, 4.8 kbit/s, or
2.4 kbit/s.
fully loaded
A state that indicates that all slots of a piece of equipment are in use, that is, the equipment
has no vacant slots.
fuse
A safety device that protects an electric circuit from excessive current, consisting of or
containing a metal element that melts when current exceeds a specific amperage, thereby
opening the circuit.
G
G-ACH
generic associated channel header
GAL
generic associated channel header label
GCC
general communication channel
GCRA
generic cell rate algorithm
GE
See gigabit Ethernet.
GFC
generic flow control
GFP
See Generic Framing Procedure.
GNE
See gateway network element.
Issue 03 (2012-11-30)

1333
OptiX OSN 7500 II/7500/3500/1500

B Glossary
GPS
See Global Positioning System.
GRE
See Generic Routing Encapsulation.
GSM
See Global System for Mobile Communications.
GTS
See generic traffic shaping.
GUI
graphical user interface
Generic Framing
Procedure (GFP)
A framing and encapsulation method which can be applied to any data type. It has been
standardized by ITU-T SG15.
Generic Routing
Encapsulation (GRE)
A mechanism for encapsulating any network layer protocol over any other network. GRE
is used for encapsulating IP datagrams tunneled through the Internet. GRE serves as a
Layer 3 tunneling protocol and provides a tunnel for transparently transmitting data
packets.
Global Positioning
System (GPS)
A global navigation satellite system. It provides reliable positioning, navigation, and

timing services to worldwide users.
Global System for

Mobile
Communications
(GSM)
The second-generation mobile networking standard defined by European

Telecommunications Standards Institute (ETSI). It is aimed at designing a standard for
global mobile phone networks. The standard allows a subscriber to use a phone globally.
GSM consists of three main parts: mobile switching subsystem (MSS), base station
subsystem (BSS), and mobile station (MS).
gain
The difference between the optical power from the input optical interface of the optical
amplifier and the optical power from the output optical interface of the jumper fiber,
which expressed in dB.
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.
general flow control
A flow control that is applicable to the A interface, C/D interface, and trunks and can be
achieved by integrating multiple function modules. It is adopted when the traffic is heavy,
or location update and authentication of multiple subscribers are performed after the
system restarts. It can efficiently prevent system breakdown caused by link congestion
or CPU overload.
generic traffic shaping A traffic control measure that proactively adjusts the output speed of the traffic. This is
(GTS)
to adapt the traffic to network resources that can be provided by the downstream router
to avoid packet discarding and congestion.
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.
ground terminal
A connection terminal on a communication device. It is used to connect the device with

ground cables, maintaining a tight connection between the device and the grounding
electrode.
Issue 03 (2012-11-30)

1334
OptiX OSN 7500 II/7500/3500/1500

B Glossary
H
HCS
higher order connection supervision
HD-SDI
See high definition-serial digital interface signal.
HDB3
high density bipolar of order 3 code
HDLC
High-Level Data Link Control
HDTV
See high definition television.
HEC
See header error control.
HPA
high order path adaptation
HPT
higher order path termination
HQoS
See hierarchical quality of service.
HSDPA
See High Speed Downlink Packet Access.
HSI
high-speed Internet
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.
hang up
A call processing mode used by an attendant to end the conversation with a user.
hardware loopback
A connection mode in which a fiber jumper is used to connect the input optical interface
to the output optical interface of a board to achieve signal loopback.
header error control

(HEC)
A field within the ATM frame whose purpose is to correct any single bit error in the cell
Header and also to detect any multi-bit errors. It actually performs a CRC check in the
first four header bits and also at the receiving end.
hello packet
The commonest packet which is periodically sent by a router to its neighbors. It contains
information about the DR, Backup Designated Router (BDR), known neighbors and
timer values.
hierarchical quality of
service (HQoS)
A type of QoS that controls the traffic of users and performs the scheduling according
to the priority of user services. HQoS has an advanced traffic statistics function, and the
administrator can monitor the usage of bandwidth of each service. Hence, the bandwidth
can be allocated reasonably through traffic analysis.
high definition
television (HDTV)
A type of TV that is capable of displaying at least 720 progressive or 1080 interlaced

active scan lines. It must be capable of displaying a 16:9 image using at least 540
progressive or 810 interlaced active scan lines.
high definition-serial
digital interface signal
(HD-SDI)
High definition video signal transported by serial digital interface.
historical performance The performance data that is stored in the history register or that is automatically reported
data
and stored on the NMS.
hop
Issue 03 (2012-11-30)
A network connection between two distant nodes. For Internet operation a hop represents
a small step on the route from one main computer to another.

1335
OptiX OSN 7500 II/7500/3500/1500

hot patch
B Glossary
A patch that is used to repair a deficiency in the software or add a new feature to a program
without restarting the software and interrupting the service. For the equipment using the
built-in system, a hot patch can be loaded, activated, confirmed, deactivated, deleted, or
queried.
I
IANA
See Internet Assigned Numbers Authority.
IC
See integrated circuit.
ICC
ITU carrier code
ICMP
See Internet Control Message Protocol.
ICP
IMA Control Protocol
IDU
See indoor unit.
IEEE
See Institute of Electrical and Electronics Engineers.
IETF
See Internet Engineering Task Force.
IF
See intermediate frequency.
IGMP
See Internet Group Management Protocol.
IGMP snooping
A multicast constraint mechanism running on a layer 2 device. This protocol manages

and controls the multicast group by listening to and analyzing Internet Group
Management Protocol (IGMP) packets between hosts and Layer 3 devices. In this
manner, the spread of the multicast data on layer 2 network can be prevented efficiently.
IGP
See Interior Gateway Protocol.
ILM
incoming label map
IMA
See inverse multiplexing over ATM.
IMA frame
A control unit in the IMA protocol. It is a logical frame defined as M consecutive cells,
numbered 0 to M-l, transmitted on each of the N links in an IMA group.
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.
IPA
See intelligent power adjustment.
IPTV
See Internet Protocol television.
IPv4
See Internet Protocol version 4.
IPv6
See Internet Protocol version 6.
IS-IS
See Intermediate System to Intermediate System.
ISDN
integrated services digital network
ISO
International Organization for Standardization
ISP
See Internet service provider.
Issue 03 (2012-11-30)

1336
OptiX OSN 7500 II/7500/3500/1500

B Glossary
IST
internal spanning tree
ITC
independent transmit clock
ITU
See International Telecommunication Union.
ITU-T
See International Telecommunication Union-Telecommunication Standardization

Sector.
IWF
Interworking Function
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.
Interior Gateway
Protocol (IGP)
A routing protocol that is used within an autonomous system. The IGP runs in smallsized and medium-sized networks. The commonly used IGPs are the routing information
protocol (RIP), the interior gateway routing protocol (IGRP), the enhanced IGRP
(EIGRP), and the open shortest path first (OSPF).
Intermediate System to A protocol used by network devices (routers) to determine the best way to forward
Intermediate System
datagram or packets through a packet-based network.
(IS-IS)
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 Assigned
Numbers Authority
(IANA)
A department operated by the IAB. IANA delegates authority for IP address-space

allocation and domain-name assignment to the NIC and other organizations. IANA also
maintains a database of assigned protocol identifiers used in the TCP/IP suite, including
autonomous system numbers.
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 Group
Management Protocol
(IGMP)
One of the TCP/IP protocols for managing the membership of Internet Protocol multicast
groups. It is used by IP hosts and adjacent multicast routers to establish and maintain
multicast group memberships.
Issue 03 (2012-11-30)

1337
OptiX OSN 7500 II/7500/3500/1500

B Glossary
Internet Protocol
television (IPTV)
A system in which video is transmitted in IP packets. Also called "TV over IP", IPTV
uses streaming video techniques to deliver scheduled TV programs or video-on-demand
(VOD). Unlike transmitting over the air or through cable to a TV set, IPTV uses the
transport protocol of the Internet for delivery and requires either a computer and software
media player or an IPTV set-top box to decode the images in real time.
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.
Internet service
provider (ISP)
An organization that offers users access to the Internet and related services.
inbound
Data transmission from the external link to the router for the routers that support the
NetStream feature.
indicator
Description of a performance feature collected from the managed devices by the

performance collector.
indoor unit (IDU)
The indoor unit of the split-structured radio equipment. It implements accessing,

multiplexing/demultiplexing, and intermediate frequency (IF) processing for services.
input jitter tolerance
The maximum amplitude of sinusoidal jitter at a given jitter frequency, which, when
modulating the signal at an equipment input port, results in no more than two errored
seconds cumulative, where these errored seconds are integrated over successive 30second measurement intervals.
insertion loss
The loss of power that results from inserting a component, such as a connector, coupler,
or splice, into a previously continuous path.
integrated circuit (IC)
A combination of inseparable associated circuit elements that are formed in place and
interconnected on or within a single base material to perform a microcircuit function.
intelligent power
adjustment (IPA)
A mechanism used to reduce the optical power of all the amplifiers in an adjacent
regeneration section in the upstream to a safety level if the system detects the loss of
optical signals on the link. If the fiber is broken, the device performance degrades, or the
connector is not plugged well, the loss of optical signals may occur. With IPA,
maintenance engineers will not be hurt by the laser sent out from the slice of broken
fiber.
interleaving
A process of systematically changing the bit sequence of a digital signal, usually as part
of the channel coding, in order to reduce the influence of error bursts that may occur
during transmission.
intermediate frequency The transitional frequency between the frequencies of a modulated signal and an RF
(IF)
signal.
inverse multiplexing
over ATM (IMA)
Issue 03 (2012-11-30)
A technique that involves inverse multiplexing and de-multiplexing of ATM cells in a

cyclical fashion among links grouped to form a higher bandwidth logical link whose rate
is approximately the sum of the link rates.

1338
OptiX OSN 7500 II/7500/3500/1500

B Glossary
J
jitter
Short waveform variations caused by vibration, voltage fluctuations, and control system
instability.
jumper
A connection wire for connecting two pins.
K
K byte
A general designation of K1 byte and K2 byte in the SDH.
L
L2 switching
The switching based on the data link layer.
L2VPN
Layer 2 virtual private network
LACP
See Link Aggregation Control Protocol.
LACPDU
Link Aggregation Control Protocol data unit
LAG
See link aggregation group.
LAN
See local area network.
LAPS
Link Access Protocol-SDH
LB
See loopback.
LBM
See loopback message.
LBR
See loopback reply.
LC
Lucent connector
LCAS
See link capacity adjustment scheme.
LCN
local communications network
LCT
local craft terminal
LDP
Label Distribution Protocol
LED
See light emitting diode.
LER
See label edge router.
LIFO
See last in first out.
LIU
logical interface unit
LL
logical link
LLC
See logical link control.
LLID
local loopback ID
LM
See loss measurement.
LOC
loss of continuity
LOM
loss of multiframe
LOP
loss of pointer
LOS
See loss of signal.
Issue 03 (2012-11-30)

1339
OptiX OSN 7500 II/7500/3500/1500

B Glossary
LP
lower order path
LPA
low order path adaptation
LPF
See low-pass filter.
LPT
link-state pass through
LSP
See label switched path.
LSR
See label switching router.
LT
linktrace
LTM
See linktrace message.
LTR
See linktrace reply.
LU
line unit
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
A short identifier that is of fixed length and local significance. It is used to uniquely
identify the FEC to which a packet belongs. It does not contain topology information. It
is carried in the header of a packet and does not contain topology information.
label distribution
Packets with the same destination address belong to an FEC. A label out of an MPLS
label resource pool is allocated to the FEC. LSRs record the relationship of the label and
the FEC. Then, LSRs sends a message and advertises to upstream LSRs about the label
and FEC relationship in message. The process is called label distribution.
label edge router (LER) A device that sits at the edge of an MPLS domain, that uses routing information to assign
labels to datagrams and then forwards them into the MPLS domain.
label space
Value range of the label allocated to peers.
label switched path

(LSP)
A sequence of hops (R0...Rn) in which a packet travels from R0 to Rn through label

switching mechanisms. A label-switched path can be chosen dynamically, based on
common routing mechanisms or through configuration.
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.
laser
A component that generates directional optical waves of narrow wavelengths. The laser
light has better coherence than ordinary light. The fiber system takes the semi-conductor
laser as the light source.
last in first out (LIFO) A play mode of the voice mails, the last voice mail is played firstly.
layer
Issue 03 (2012-11-30)
A concept used to allow the transport network functionality to be described hierarchically

as successive levels; each layer being solely concerned with the generation and transfer
of its characteristic information.

1340
OptiX OSN 7500 II/7500/3500/1500

B Glossary
license
A permission that the vendor provides for the user with a specific function, capacity, and
duration of a product. A license can be a file or a serial number. Usually the license
consists of encrypted codes. The operation authority granted varies with the level of the
license.
light emitting diode

(LED)
A display and lighting technology used in almost every electrical and electronic product
on the market, to from a tiny on/off light to digital readouts, flashlights, traffic lights and
perimeter lighting. LEDs are also used as the light source in multimode fibers, optical
mice and laser-class printers.
line rate
The maximum packet forwarding capacity on a cable. The value of line rate equals the
maximum transmission rate capable on a given type of media.
linear MSP
linear multiplex section protection
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.
link capacity
adjustment scheme
(LCAS)
LCAS in the virtual concatenation source and sink adaptation functions provides a
control mechanism to hitless increase or decrease the capacity of a link to meet the
bandwidth needs of the application. It also provides a means of removing member links
that have experienced failure. The LCAS assumes that in cases of capacity initiation,
increases or decreases, the construction or destruction of the end-to-end path is the
responsibility of the network and element management systems.
link monitoring
A mechanism for an interface to notify the peer of the fault when the interface detects
that the number of errored frames, errored codes, or errored frame seconds reaches or
link protection
Protection provided by the bypass tunnel for the link on the working tunnel. The link is
a downstream link adjacent to the point of local repair (PLR). When the PLR fails to
provide node protection, the link protection should be provided.
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.
load balancing
The distribution of activity across two or more servers or components in order to avoid
overloading any one with too many requests or too much traffic.
load sharing
A device running mode. Two or more hardware units can averagely share the system
load based on their processing capabilities when they are operating normally. When a
hardware unit fails, the other units fulfill the tasks of the faulty unit on the precondition
for guaranteeing system performance, for example, few call loss.
loading
A process of importing information from the storage device to the memory to facilitate
processing (when the information is data) or execution (when the information is
program).
local MEP
An MEP of a device on a network enabled with Ethernet CFM.
Issue 03 (2012-11-30)

1341
OptiX OSN 7500 II/7500/3500/1500

B Glossary
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).
logical interface
An interface that does not exist physically and comes into being through configuration.
It can also exchange data.
logical link control

(LLC)
According to the IEEE 802 family of standards, Logical Link Control (LLC) is the upper
sublayer of the OSI data link layer. The LLC is the same for the various physical media
(such as Ethernet, token ring, WLAN).
loopback (LB)
A troubleshooting technique that returns a transmitted signal to its source so that the
signal or message can be analyzed for errors. The loopback can be a inloop or outloop.
loopback message
(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.
low-pass filter (LPF)
A filter designed to transmit electromagnetic frequencies below a certain value, while

excluding those of a higher frequency.
lower subrack
The subrack close to the bottom of the cabinet that contains several subracks.
lower threshold
A lower performance limit which when exceeded by a performance event counter will
trigger a threshold-crossing event.
M
MA
maintenance association
MAC
See Media Access Control.
MAC address
A link layer address or physical address. It is six bytes long.
MAC address aging
A function that deletes MAC address entries of a device when no packets are received
from this device within a specified time period.
MADM
multiple add/drop multiplexer
MAN
See metropolitan area network.
MBS
maximum burst size
MCF
message communication function
MCR
minimum cell rate
MD
See maintenance domain.
MDP
message dispatch process
Issue 03 (2012-11-30)

1342
OptiX OSN 7500 II/7500/3500/1500

B Glossary
ME
See maintenance entity.
MEG
maintenance entity group
MEL
maintenance entity group level
MEP
See maintenance entity group end point.
MFAS
See multiframe alignment signal.
MIP
See maintenance entity group intermediate point.
MLD
See multicast listener discovery.
MP
maintenance point
MPID
maintenance point identification
MPLS
See Multiprotocol Label Switching.
MPLS TE
multiprotocol label switching traffic engineering
MPLS VPN
See multiprotocol label switching virtual private network.
MPLS-TP
See transport profile for multiprotocol label switching.
MS
multiplex section
MSA
multiplex section adaptation
MSB
most significant bit
MSOH
multiplex section overhead
MSP
See multiplex section protection.
MST
See multiplex section termination.
MST region
See Multiple Spanning Tree region.
MSTI
See multiple spanning tree instance.
MSTP
See Multiple Spanning Tree Protocol.
MTBF
See mean time between failures.
MTIE
maximum time interval error
MTTR
See mean time to repair.
MTU
See maximum transmission unit.
MUX
See multiplexer.
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.
Multicast Routing
Protocol
A protocol used to set up and maintain multicast routes, and to correctly and effectively
forward multicast packets. The multicast route is used to set up a loop-free transmission
path from the source to multiple receivers, that is, the multicast distribution tree.
Issue 03 (2012-11-30)

1343
OptiX OSN 7500 II/7500/3500/1500

B Glossary
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.
Multiple Spanning
Tree region (MST
region)
A region that consists of switches that support the MSTP in the LAN and links among
them. Switches physically and directly connected and configured with the same MST
region attributes belong to the same MST region.
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.
main topology
A basic component of a human-machine interface. It is the default client interface of the

NMS and intuitively displays the structure of a network, NEs on the network, subnets in
the network as well as the NE communication and running status, reflecting the overall
network running status.
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).
maintenance entity
(ME)
An ME consists of a pair of maintenance entity group end points (MEPs), two ends of a
transport trail, and maintenance association intermediate points (MIPs) on the trail.
maintenance entity
An end point of a MEG, which is able to initialize and stop the transmission of OAM
group end point (MEP) data packets for fault management and performance monitoring.
maintenance entity
group intermediate
point (MIP)
An intermediate point in a MEG, which is able to forward OAM packets and respond to
some OAM packets, but unable to initiate the transmission of OAM packets or perform
any operations on network connections.
management
information
The information that is used for network management in a transport 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.
measurement period
The interval for NEs to report measurement results to the Network Management System
(NMS).
medium
A physical medium for storing computer information. A medium is used for data
duplication and keeping the data for some time. Original data can be obtained from a
medium.
Issue 03 (2012-11-30)

1344
OptiX OSN 7500 II/7500/3500/1500

B Glossary
member
A basic element for forming a dimension according to the hierarchy of each level. Each
member represents a data element in a dimension. For example, January 1997 is a typical
member of the time dimension.
metropolitan area
network (MAN)
A network that interconnects users with computer resources in a geographic area or

region larger than that covered by even a large LAN but smaller than the area covered
by an WAN. The term is applied to the interconnection of networks in a city into a single
larger network (which may then also offer efficient connection to a wide area network).
It is also used to mean the interconnection of several local area networks by bridging
them with backbone lines. The latter usage is also sometimes referred to as a campus
network.
microwave
The portion of the electromagnetic spectrum with much longer wavelengths than infrared
radiation, typically above about 1 mm.
mirroring
The duplication of data for backup or to distribute network traffic among several
computers with identical data.
monitor link
A port association solution developed as a supplementary to smart link.
monitoring
A method that an inspector uses to inspect a service agent. By monitoring a service agent,
an inspector can check each detailed operation performed by the service agent during
the conversation and operate the GUI used by the service agent. The inspector helps the
service agent to provide better service.
mounting
An auxiliary or associated condition or component of a device.
mounting ear
A piece of angle plate with holes in it on a rack. It is used to fix network elements or
components.
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.
multicast listener
discovery (MLD)
A protocol used by an IPv6 router to discover the multicast listeners on their directly
connected network segments, and to set up and maintain member relationships. On IPv6
networks, after MLD is configured on the receiver hosts and the multicast router to which
the hosts are directly connected, the hosts can dynamically join related groups and the
multicast router can manage members on the local network.
multiframe alignment
signal (MFAS)
A distinctive signal inserted in every multiframe or once in every n multiframes, always

occupying the same relative position within the multiframe, and used to establish and
maintain multiframe alignment.
multiple spanning tree A type of spanning trees calculated by MSTP within an MST Region, to provide a simply
instance (MSTI)
and fully connected active topology for frames classified as belonging to a VLAN that
is mapped to the MSTI by the MST Configuration. A VLAN cannot be assigned to
multiple MSTIs.
multiplex section
protection (MSP)
A function, which is performed to provide capability for switching a signal between and
including two multiplex section termination (MST) functions, from a "working" to a
"protection" channel.
multiplex section
termination (MST)
A function, which is performed to generate the MSOH during the process of forming an
SDH frame signal and terminates the MSOH in the reverse direction.
multiplexer (MUX)
Equipment which combines a number of tributary channels onto a fewer number of

aggregate bearer channels, the relationship between the tributary and aggregate channels
being fixed.
Issue 03 (2012-11-30)

1345
OptiX OSN 7500 II/7500/3500/1500

B Glossary
multiplexing
A procedure by which multiple lower order path layer signals are adapted into a higher
order path or the multiple higher order path layer signals are adapted into a multiplex
section.
multiprotocol label
switching virtual
private network
(MPLS VPN)
An Internet Protocol (IP) virtual private network (VPN) based on the multiprotocol label
switching (MPLS) technology. It applies the MPLS technology for network routers and
switches, simplifies the routing mode of core routers, and combines traditional routing
technology and label switching technology. It can be used to construct the broadband
Intranet and Extranet to meet various service requirements.
N
N+1 protection
A radio link protection system composed of N working channels and one protection
channel.
NAS
network access server
NC
See NTP client.
NE ID
An ID that indicates a managed device in the network. In the network, each NE has a
unique NE ID.
NGN
See next generation network.
NHLFE
next hop label forwarding entry
NLP
normal link pulse
NM
network management
NMC
network management center
NNI
network-to-network interface
NP
See network processor.
NPC
See network parameter control.
NPE
network provider edge
NRT-VBR
non-real-time variable bit rate
NRZ
non-return to zero
NRZ code
non-return-to-zero code
NRZI
non-return to zero inverted
NSAP
See network service access point.
NSF
non-stop forwarding
NTP
Network Time Protocol
NTP client (NC)
A bottom-level device in the time synchronization network. An NTP client obtains time
from its upper-level NTP server without providing the time synchronization service.
Compared with the top-level NTP server, the middle-level NTP server sometimes is
called an NTP client.
network layer
Layer 3 of the seven-layer OSI model of computer networking. The network layer
provides routing and addressing so that two terminal systems are interconnected. In
addition, the network layer provides congestion control and traffic control. In the TCP/
IP protocol suite, the functions of the network layer are specified and implemented by
IP protocols. Therefore, the network layer is also called IP layer.
Issue 03 (2012-11-30)

1346
OptiX OSN 7500 II/7500/3500/1500

network parameter
control (NPC)
B Glossary
During communications, UPC is implemented to monitor the actual traffic on each virtual
circuit that is input to the network. Once the specified parameter is exceeded, measures
will be taken to control. NPC is similar to UPC in function. The difference is that the
incoming traffic monitoring function is divided into UPC and NPC according to their
positions. UPC locates at the user/network interface, while NPC at the network interface.
network processor (NP) An integrated circuit which has a feature set specifically targeted at the networking
application domain. Network Processors are typically software programmable devices
and would have generic characteristics similar to general purpose CPUs that are
commonly used in many different types of equipment and products.
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 service
A service that needs to be enabled at the network layer and maintained as a basic service.
network service access A network address defined by ISO, through which entities on the network layer can
point (NSAP)
access OSI network services.
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.
next generation
network (NGN)
A packet-based network aimed to address requirement of various services. It adopts an

integrated and open network framework. In NGN, services are separated from call
control; call control is separated from bearer. In this way, services are independent of
network. NGN can provide various services, such as voice services, data services,
multimedia services or the integration of several services.
noise figure
A measure of degradation of the signal-to-noise ratio (SNR), caused by components in

a radio frequency (RF) signal chain. The noise figure is defined as the ratio of the output
noise power of a device to the portion thereof attributable to thermal noise in the input
termination at standard noise temperature T0 (usually 290 K). The noise figure is thus
the ratio of actual output noise to that which would remain if the device itself did not
introduce noise. It is a number by which the performance of a radio receiver can be
specified.
non-GNE
See non-gateway network element.
non-gateway network
element (non-GNE)
A network element that communicates with the NM application layer through the
gateway NE application layer.
O
O&M
operation and maintenance
OA
optical amplifier
OADM
See optical add/drop multiplexer.
OAM
See operation, administration and maintenance.
OAMPDU
operation, administration and maintenance protocol data unit
OAU
See optical amplifier unit.
OC
ordinary clock
OCP
optical channel protection
Issue 03 (2012-11-30)

1347
OptiX OSN 7500 II/7500/3500/1500

B Glossary
OCS
optical core switching
ODF
optical distribution frame
ODU
See outdoor unit.
OFS
out-of-frame second
OHA
overhead access
OHP
overhead processing
OLT
optical line terminal
ONU
See optical network unit.
OPEX
operating expense
OPU
optical channel payload unit
OSC
See optical supervisory channel.
OSI
See open systems interconnection.
OSN
optical switch node
OSNR
See optical signal-to-noise ratio.
OSPF
See Open Shortest Path First.
OTDR
See optical time domain reflectometer.
OTM
optical terminal multiplexer
OTN
optical transport network
OTU
See optical transponder unit.
OTUk
optical channel transport unit-k
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.
offline
Pertaining to the disconnection between a device or a service unit and the system or the
network, or no running of a device and service unit.
online
A state indicating that a computer device or program is activated and is ready for
operations, and can communicate with a computer or can be controlled by the computer.
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.
Issue 03 (2012-11-30)

1348
OptiX OSN 7500 II/7500/3500/1500

B Glossary
optical add/drop
multiplexer (OADM)
A device that can be used to add the optical signals of various wavelengths to one channel
and drop the optical signals of various wavelengths from one channel.
optical amplifier unit

(OAU)
A board that is mainly responsible for amplifying optical signals. The OAU can be used
in both the transmitting direction and the receiving direction.
optical attenuator
A passive device that increases the attenuation in a fiber link. It is used to ensure that the
optical power of the signals received at the receive end is not extremely high. It is
available in two types: fixed attenuator and variable attenuator.
optical connector
A component normally attached to an optical cable or a piece of apparatus to provide

frequent optical interconnection/disconnection of optical fibers or cables.
optical fiber
A thin filament of glass or other transparent material, through which a signal-encoded

light beam may be transmitted using total internal reflection.
optical interface
A component that connects several transmit or receive units.
optical network unit

(ONU)
A form of Access Node that converts optical signals transmitted via fiber to electrical
signals that can be transmitted via coaxial cable or twisted pair copper wiring to
individual subscribers.
optical signal-to-noise
ratio (OSNR)
The ratio of signal power and noise power in a transmission link. OSNR is the most
important index of measuring the performance of a DWDM system. OSNR = signal
power/noise power.
optical splitter
A passive component, which is used for splitting and sending optical power to multiple
ONUs connected by an optical fiber. In a GPON system that consists of the OLT, ONU,
splitter, and optical fibers, according to the split ratio, the optical signal over the optical
fiber connected to the OLT is splitted into multiple channels of optical signals and send
each channel to each ONU. Split ratio determines how many channels of optical signals
an optical fiber can be split to.
optical supervisory
channel (OSC)
A technology that uses specific optical wavelengths to realize communication among

nodes in optical transmission network and transmit the monitoring data in a certain
channel.
optical time domain

reflectometer (OTDR)
A device that sends a very short pulse of light down a fiber optic communication system
and measures the time history of the pulse reflection to measure the fiber length, the light
loss and locate the fiber fault.
optical transponder
unit (OTU)
A device or subsystem that converts the accessed client signals into the G.694.1/G.694.2compliant WDM wavelength.
orderwire
A channel that provides voice communication between operation engineers or

maintenance engineers of different stations.
outdoor unit (ODU)
The outdoor unit of the split-structured radio equipment. It implements frequency

conversion and amplification for radio frequency (RF) signals.
P
P2MP
point-to-multipoint
P2P
See point-to-point service.
PA
power amplifier
PADR
PPPoE active discovery request
PBS
See peak burst size.
Issue 03 (2012-11-30)

1349
OptiX OSN 7500 II/7500/3500/1500

B Glossary
PCB
See printed circuit board.
PCM
See pulse code modulation.
PCR
See peak cell rate.
PCS
physical coding sublayer
PDH
See plesiochronous digital hierarchy.
PDU
See power distribution unit.
PE
See provider edge.
PGND cable
A cable which connects the equipment and the protection grounding bar. Usually, one
half of the cable is yellow, whereas the other half is green.
PHB
See per-hop behavior.
PIM-DM
Protocol Independent Multicast - Dense Mode
PIM-SM
Protocol Independent Multicast - Sparse Mode
PKT
partition knowledge table
PLL
See phase-locked loop.
PM
performance monitoring
PMD
polarization mode dispersion
POH
path overhead
POS
See packet over SDH/SONET.
PPD
partial packet discard
PPI
PDH physical interface
PPP
Point-to-Point Protocol
PPPoE
Point-to-Point Protocol over Ethernet
PPS
port protection switching
PQ
See priority queuing.
PRBS
See pseudo random binary sequence.
PRC
primary reference clock
PSD
See power spectrum density.
PSN
See packet switched network.
PSTN
See public switched telephone network.
PSU
power supply unit
PT
payload type
PTI
payload type indicator
PTN
packet transport network
PTP
Precision Time Protocol
PVC
permanent virtual channel
PVID
See port default VLAN ID.
Issue 03 (2012-11-30)

1350
OptiX OSN 7500 II/7500/3500/1500

B Glossary
PVP
See permanent virtual path.
PW
See pseudo wire.
PWE3
See pseudo wire emulation edge-to-edge.
packet discarding
A function of discarding the packets from unknown VLAN domain or broadcast packets.
Packet Discarding is used to prevent the situation where unknown packets or broadcast
packets use the bandwidth on a link, improving the reliability of service transmission.
packet forwarding
An action performed by a router to forward a received datagram, where the destination

IP address does not match the IP address of the router, to another router or destination
host on the router list.
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 over SDH/

SONET (POS)
A MAN and WAN technology that provides point-to-point data connections. The POS
interface uses SDH/SONET as the physical layer protocol, and supports the transport of
packet data (such as IP packets) in MAN and WAN.
packet rate
The number of bits or bytes passed within a specified time. It is expressed in bits/s or
bytes/s.
packet switched
network (PSN)
A telecommunications network that works in packet switching mode.
packet switching
A network technology in which information is transmitted by means of exchanging

packets and the bandwidth of a channel can be shared by multiple connections.
paired slots
Two slots of which the overheads can be passed through by using the bus on the
backplane.
parity bit
A check bit appended to an array of binary digits to make the sum of all the binary digits,
including the check bit, always odd or always even.
parity check
A method for character level error detection. An extra bit is added to a string of bits,
usually a 7-bit ASCII character, so that the total number of bits 1 is odd or even (odd or
even parity). Both ends of a data transmission must use the same parity. When the
transmitting device frames a character, it counts the numbers of 1s in the frame and
attaches the appropriate parity bit. The recipient counts the 1s and, if there is parity error,
may ask for the data to be retransmitted.
parts replacement
A maintenance operation of removing a faulty part or a part to be examined from a

running device and then installing a new part.
passive mode
A working mode of EFM OAM. An interface in the passive mode cannot initiate the
discovery and remote loopback.
patch
An independent software unit used for fixing the bugs in software.
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.
peak cell rate (PCR)
The maximum rate at which an ATM connection can accept cells.
peer
BGP speakers that exchange information with each other.
Issue 03 (2012-11-30)

1351
OptiX OSN 7500 II/7500/3500/1500

B 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).
performance alarm
An alarm generated when the actual result of a measurement entity equals the predefined
logical expression for threshold or exceeds the predefined threshold.
performance
parameters
The performance parameters identify some indexes to scale the general performance of
the system. The indexes include the number of managed nodes, number of supported
clients and log database capacity. The parameters are sorted into static parameters,
dynamic parameters and networking bandwidth parameters.
performance register
The memory space for performance event counts, including 15-min current performance
register, 24-hour current performance register, 15-min historical performance register,
24-hour historical performance register, UAT register and CSES register. The object of
performance event monitoring is the board functional module, so every board functional
module has a performance register. A performance register is used to count the
performance events taking place within a period of operation time, so as to evaluate the
quality of operation from the angle of statistics.
performance threshold A limit for generating an alarm for a selected entity. When the measurement result
reaches or exceeds the preset alarm threshold, the performance management system
generates a performance alarm.
permanent virtual path Virtual path that consists of PVCs.
(PVP)
phase
The relative position in time within a single period of a signal.
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.
physical link
The link between two physical network elements (NEs). When the user creates NEs or
refreshes the device status, the system automatically creates the physical link according
to the topology structure information on the device. The remark information of a physical
link can be modified, but the physical link cannot be deleted.
ping
A method used to test whether a device in the IP network is reachable according to the
sent ICMP Echo messages and received response messages.
ping test
A test that is performed to send a data packet to the target IP address (a unique IP address
on the device on the network) to check whether the target host exists according to the
data packet of the same size returned from the target host.
plesiochronous digital
hierarchy (PDH)
A multiplexing scheme of bit stuffing and byte interleaving. It multiplexes the minimum
rate 64 kit/s into the 2 Mbit/s, 34 Mbit/s, 140 Mbit/s, and 565 Mbit/s rates.
point-to-point service
(P2P)
A service between two terminal users. In P2P services, senders and recipients are
terminal users.
Issue 03 (2012-11-30)

1352
OptiX OSN 7500 II/7500/3500/1500

B Glossary
pointer
An indicator whose value defines the frame offset of a virtual container with respect to
the frame reference of the transport entity on which this pointer is supported.
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.
policy template
A template that is used to define the calculation rules of a charging event, for example,
rating, debiting and accumulating. A policy template may contain the parameters to be
instantiated. They can be used when the attributes of the condition judgment, calculation
method, and action functions are carried out.
polling
A mechanism for the NMS to query the agent status and other data on a regular basis.
port default VLAN ID

(PVID)
A default VLAN ID of a port. It is allocated to a data frame if the data frame carries no
VLAN tag when reaching the port.
port priority
The priority that is used when a port attaches tags to Layer 2 packets. Packets received
on ports with higher priorities are forwarded preferentially.
power adjustment
A method for dynamically and properly assigning power according to the real-time status
of a wireless network. When an AP runs under an AC for the first time, the AP uses its
maximum transmit power. When getting reports from its neighbors (that is, other APs
that are detected by the AP and managed by the same AC), the AP determines to increase
or decrease its power according to the report conclusion.
power box
A direct current power distribution box at the upper part of a cabinet, which supplies
power for the subracks in the cabinet.
power control
A process in which the MS or BS uses certain rules to adjust and control the transmit
power according to the change in the channel condition and the power of the received
signal.
power distribution unit A unit that performs AC or DC power distribution.

(PDU)
power module
A module that provides power supply to other boards or modules.
power off
An operation that switches off devices during upgrade or expansion.
power on
To start up a computer; to begin a cold boot procedure; to turn on the power
power spectrum
density (PSD)
The power layout of random signals in the frequency domain.
printed circuit board

(PCB)
A board used to mechanically support and electrically connect electronic components

using conductive pathways, tracks, or traces, etched from copper sheets laminated onto
a non-conductive substrate.
priority queuing (PQ)
A queue scheduling algorithm based on the absolute priority. According to the PQ

algorithm, services of higher priorities are ensured with greater bandwidth, lower
latency, and less jitter. Packets of lower priorities must wait to be sent till all packets of
higher priorities are sent. In this manner, services of higher priorities are processed earlier
than others.
Issue 03 (2012-11-30)

1353
OptiX OSN 7500 II/7500/3500/1500

B Glossary
private line
A line, such as a subscriber cable and trunk cable, which are leased by the
telecommunication carrier and are used to meet the special user requirements.
protection path
A specific path that is part of a protection group and is labeled protection.
provider edge (PE)
A device that is located in the backbone network of the MPLS VPN structure. A PE is
responsible for managing VPN users, establishing LSPs between PEs, and exchanging
routing information between sites of the same VPN. A PE performs the mapping and
forwarding of packets between the private network and the public channel. A PE can be
a UPE, an SPE, or an NPE.
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 (PW)
An emulated connection between two PEs for transmitting frames. The PW is established
and maintained by PEs through signaling protocols. The status information of a PW is
maintained by the two end PEs of a PW.
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.
public switched
telephone network
(PSTN)
A telecommunications network established to perform telephone services for the public

subscribers. Sometimes it is called POTS.
pulse
A variation above or below a normal level and a given duration in electrical energy.
pulse code modulation A method of encoding information in a signal by changing the amplitude of pulses.
(PCM)
Unlike pulse amplitude modulation (PAM), in which pulse amplitude can change
continuously, pulse code modulation limits pulse amplitudes to several predefined
values. Because the signal is discrete, or digital, rather than analog, pulse code
modulation is more immune to noise than PAM.
Q
QA
Q adaptation
QAM
See quadrature amplitude modulation.
QPSK
See quadrature phase shift keying.
QinQ
A layer 2 tunnel protocol based on IEEE 802.1Q encapsulation. It add a public VLAN
tag to a frame with a private VLAN tag to allow the frame with double VLAN tags to
be transmitted over the service provider's backbone network based on the public VLAN
tag. This provides a layer 2 VPN tunnel for customers and enables transparent
transmission of packets over private VLANs.
QoS
See quality of service.
quadrature amplitude
modulation (QAM)
Both an analog and a digital modulation scheme. It conveys two analog message signals,
or two digital bit streams, by changing (modulating) the amplitudes of two carrier waves,
using the amplitude-shift keying (ASK) digital modulation scheme or amplitude
modulation (AM) analog modulation scheme. These two waves, usually sinusoids, are
out of phase with each other by 90 and are thus called quadrature carriers or quadrature
components hence the name of the scheme.
Issue 03 (2012-11-30)

1354
OptiX OSN 7500 II/7500/3500/1500

B Glossary
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
RADIUS
See Remote Authentication Dial-In User Service.
RAI
remote alarm indication
RDI
remote defect indication
RED
See random early detection.
REG
See regenerator.
REI
remote error indication
RF
See radio frequency.
RIP
See Routing Information Protocol.
RMEP
remote maintenance association end point
RNC
See radio network controller.
ROPA
See remote optical pumping amplifier.
RP
rendezvous point
RPR
resilient packet ring
RS232
A asynchronous transfer mode that does not involve hand-shaking signal. It can
communicate with RS232 and RS422 of other stations in point-to-point mode and the
transmission is transparent. Its highest speed is 19.2kbit/s.
RS422
The specification that defines the electrical characteristics of balanced voltage digital
interface circuits. The interface can change to RS232 via the hardware jumper and others
are the same as RS232.
RSL
See received signal level.
RSOH
regenerator section overhead
RSSI
See received signal strength indicator.
RST
regenerator section termination
RSTP
See Rapid Spanning Tree Protocol.
RTN
radio transmission node
RTP
See Real-Time Transport Protocol.
Issue 03 (2012-11-30)

1355
OptiX OSN 7500 II/7500/3500/1500

B Glossary
Rapid Spanning Tree

Protocol (RSTP)
An evolution of the Spanning Tree Protocol, providing for faster spanning tree
convergence after a topology change. The RSTP protocol is backward compatible with
the STP protocol.
Real-Time Transport
Protocol (RTP)
A type of host-to-host protocol used in real-time multimedia services such as Voice over
IP (VoIP) and video.
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.
RoHS
restriction of the use of certain hazardous substances
Routing Information
Protocol (RIP)
A simple routing protocol that is part of the TCP/IP protocol suite. It determines a route
based on the smallest hop count between source and destination. RIP is a distance vector
protocol that routinely broadcasts routing information to its neighboring routers and is
known to waste bandwidth.
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.
radio propagation
model
An empirical mathematical formulation for the characterization of radio wave

propagation as a function of frequency, distance and other conditions. A single model is
usually developed to predict the behavior of propagation for all similar links under
similar constraints.
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.
rate limiting
A traffic management technology used to limit the total rate of packet sending on a
physical interface or a Tunnel interface. Rate limiting is directly enabled on the interface
to control the traffic passing the interface.
real-time variable bit

rate (rt-VBR)
A parameter intended for real-time applications, such as compressed voice over IP

(VoIP) and video conferencing. The rt-VBR is characterized by a peak cell rate (PCR),
sustained cell rate (SCR), and maximum burst size (MBS). You can expect the source
device to transmit in bursts and at a rate that varies with time.
reboot
To start the system again. Programs or data will be reloaded to all boards.
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).
recognition
Consumer awareness of having seen or heard an advertising message.
Issue 03 (2012-11-30)

1356
OptiX OSN 7500 II/7500/3500/1500

B Glossary
reference clock
A kind of stable and high-precision autonous clock providing frequencies for other clocks
for reference.
reflectance
The ratio of the reflected optical power to the incident optical power.
regeneration
The process of receiving and reconstructing a digital signal so that the amplitudes,
waveforms and timing of its signal elements are constrained within specified limits.
regenerator (REG)
A piece of equipment or device that regenerates electrical signals.
relay
An electronic control device that has a control system and a system to be controlled. The
relay of the telepresence system is used to control the power of telepresence equipment
and is controlled by the telepresence host.
remote optical
pumping amplifier
(ROPA)
A remote optical amplifier subsystem designed for applications where power supply and
monitoring systems are unavailable. The ROPA subsystem is a power compensation
solution to the ultra-long distance long hop (LHP) transmission.
reservation
An action that the charging module performs to freeze a subscriber's balance amount,
free resources, credits, or quotas before the subscriber uses services. This action ensures
that the subscriber has sufficient balance to pay for services.
resistance
The ability to impede (resist) the flow of electric current. With the exception of
superconductors, all substances have a greater or lesser degree of resistance. Substances
with very low resistance, such as metals, conduct electricity well and are called
conductors. Substances with very high resistance, such as glass and rubber, conduct
electricity poorly and are called nonconductors or insulators.
resource sharing
A physical resource belonging to two or more protection subnetworks.
response
A message that is returned to the requester to notify the requester of the status of the
request packet.
robustness
The ability of a system to maintain function even with changes in internal structure or
external environment.
rollback
A return to a previous condition through cancellation of a certain operation.
root alarm
An alarm directly caused by anomaly events or faults in the network. Some lower-level
alarms always accompany a root alarm.
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.
router
A device on the network layer that selects routes in the network. The router selects the
optimal route according to the destination address of the received packet through a
network and forwards the packet to the next router. The last router is responsible for
sending the packet to the destination host. Can be used to connect a LAN to a LAN, a
WAN to a WAN, or a LAN to the Internet.
routing
The determination of a path that a data unit (frame, packet, message) traverses from
source to destination.
routing protocol
A formula used by routers to determine the appropriate path onto which data should be
forwarded.
rt-VBR
See real-time variable bit rate.
Issue 03 (2012-11-30)

1357
OptiX OSN 7500 II/7500/3500/1500

B Glossary
S1 byte
A byte to transmit network synchronization status information. On an SDH network,

each NE traces hop by hop to the same clock reference source through a specific clock
synchronization path, realizing synchronization on the entire network. If a clock
reference source traced by an NE is missing, this NE will trace another clock reference
source of a lower level. To implement protection switching of clocks in the whole
network, the NE must learn about clock quality information of the clock reference source
it traces. Therefore, ITU-T defines S1 byte to transmit network synchronization status
information. It uses the lower four bits of the multiplex section overhead S1 byte to
indicate 16 types of synchronization quality grades. Auto protection switching of clocks
in a synchronous network can be implemented using S1 byte and a proper switching
protocol.
SAN
storage area network
SAToP
Structure-Agnostic Time Division Multiplexing over Packet
SC
square connector
SCR
sustainable cell rate
SD
See signal degrade.
SD trigger flag
A signal degrade trigger flag that determines whether to perform a switching when SD
occurs. The SD trigger flag can be set by using the network management system.
SD-SDI
See standard definition-serial digital interface signal.
SDH
See synchronous digital hierarchy.
SDP
serious disturbance period
SDRAM
See synchronous dynamic random access memory.
SELV
safety extra-low voltage
SEMF
synchronous equipment management function
SES
severely errored second
SETS
SDH equipment timing source
SF
See signal fail.
SFP
small form-factor pluggable
SFTP
See Secure File Transfer Protocol.
SHDSL
See single-pair high-speed digital subscriber line.
SMSR
side mode suppression ratio
SNC
subnetwork connection
SNCMP
subnetwork connection multipath protection
SNCP
subnetwork connection protection
SNCTP
subnetwork connection tunnel protection
SNMP
See Simple Network Management Protocol.
SNR
See signal-to-noise ratio.
SOH
section overhead
SONET
See synchronous optical network.
Issue 03 (2012-11-30)

1358
OptiX OSN 7500 II/7500/3500/1500

B Glossary
SPE
See superstratum provider edge.
SSL
See Secure Sockets Layer.
SSM
See Synchronization Status Message.
SSMB
synchronization status message byte
SSU
synchronization supply unit
STD
system target decoder
STP
Spanning Tree Protocol
SVC
switched virtual connection
Secure File Transfer

Protocol (SFTP)
A network protocol designed to provide secure file transfer over SSH.
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.
security
Protection of a computer system and its data from harm or loss. A major focus of
computer security, especially on systems accessed by many people or through
communication lines, is preventing system access by unauthorized individuals.
security service
A service, provided by a layer of communicating open systems, which ensures adequate

security of the systems or of data transfer.
self-healing
A function of establishing a replacement connection by network without the network

management connection function. When a connection failure occurs, the replacement
connection is found by the network elements and rerouted depending on network
resources available at that time.
serial port
An input/output location (channel) that sends and receives data to and from a computer's
CPU or a communications device one bit at a time. Serial ports are used for serial data
communication and as interfaces with some peripheral devices, such as mice and printers.
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.
service level
The level of service quality of an evaluated party in a specified period, determined by

an evaluating party.
service protection
A measure that ensures that services can be received at the receive end.
Issue 03 (2012-11-30)

1359
OptiX OSN 7500 II/7500/3500/1500

B Glossary
session
A logical connection between two nodes on a network for the exchange of data. It
generally can apply to any link between any two data devices. A session is also used
simply to describe the connection time.
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).
signaling
The information exchange concerning the establishment and control of a

telecommunication circuit and the management of the network.
single-ended switching A protection operation method that takes switching action only at the affected end of the
protected entity (for example, trail, subnetwork connection), in the case of a
unidirectional failure.
single-pair high-speed
(SHDSL)
A symmetric digital subscriber line technology developed from HDSL, SDSL, and
HDSL2, which is defined in ITU-T G.991.2. The SHDSL port is connected to the user
terminal through the plain telephone subscriber line and uses trellis coded pulse
amplitude modulation (TC-PAM) technology to transmit high-speed data and provide
the broadband access service.
single-polarized
antenna
An antenna intended to radiate or receive radio waves with only one specified
polarization.
slicing
Dividing data into the information units proper for transmission.
smooth upgrade
Process of upgrading the system files without service interruption
span
The physical reach between two pieces of WDM equipment. The number of spans
determines the signal transmission distance supported by a piece of equipment and varies
according to transmission system type.
standard definitionserial digital interface

signal (SD-SDI)
Standard definition video signal transported by serial digital interface.
static ARP
A protocol that binds some IP addresses to a specified gateway. The packet of these IP
addresses must be forwarded through this gateway.
static route
A route that cannot adapt to the change of network topology. Operators must configure
it manually. When a network topology is simple, the network can work in the normal
state if only the static route is configured. It can improve network performance and ensure
bandwidth for important applications. Its disadvantage is as follows: When a network is
faulty or the topology changes, the static route does not change automatically. It must
be changed by the operators.
statistical multiplexing A multiplexing technique whereby information from multiple logical channels can be
transmitted across a single physical channel. It dynamically allocates bandwidth only to
active input channels, to make better use of available bandwidth and allow more devices
to be connected than with other multiplexing techniques.
Issue 03 (2012-11-30)

1360
OptiX OSN 7500 II/7500/3500/1500

B Glossary
steering
A protection switching mode defined in ITU-T G.8132, which is applicable to packetbased T-MPLS ring networks and similar to SDH transoceanic multiplex section
protection (MSP). In this mode, the switching is triggered by the source and sink nodes
of a service.
stress
The force, or combination of forces, which produces a strain; force exerted in any
direction or manner between contiguous bodies, or parts of bodies, and taking specific
names according to its direction, or mode of action, as thrust or pressure, pull or tension,
shear or tangential stress.
subnet
A type of smaller networks that form a larger network according to a rule, for example,
according to different districts. This facilitates the management of the large network.
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.
superstratum provider Core devices that are located within a VPLS full-meshed network. The UPE devices that
edge (SPE)
are connected with the SPE devices are similar to the CE devices. The PWs set up
between the UPE devices and the SPE devices serve as the ACs of the SPE devices. The
SPE devices must learn the MAC addresses of all the sites on UPE side and those of the
UPE interfaces that are connected with the SPE. SPE is sometimes called NPE.
suppress
To forbid the printing of the paper bill of an account that meets certain conditions during
the bill run.
suspension
A specific state in the life cycle of a subscriber. A subscriber in this state can neither
make calls nor receive calls.
switching capacity
The backplane bandwidth or switching bandwidth. The switching capacity is the

maximum data that can be processed by the interface processor of a switch and the data
bus. The backplane bandwidth indicates the overall data switching capability of a switch,
in Gbit/s.
switching priority
A priority of a board that is defined for protection switching. When several protected
boards need to be switched, a switching priority should be set for each board. If the
switching priorities of the boards are the same, services on the board that fails later cannot
be switched. Services on the board with higher priority can preempt the switching
resources of that with lower priority.
synchronous digital
hierarchy (SDH)
A transmission scheme that follows ITU-T G.707, G.708, and G.709. It defines the
transmission features of digital signals such as frame structure, multiplexing mode,
transmission rate level, and interface code. SDH is an important part of ISDN and BISDN. It interleaves the bytes of low-speed signals to multiplex the signals to high-speed
counterparts, and the line coding of scrambling is used only for signals. SDH is suitable
for the fiber communication system with high speed and a large capacity since it uses
synchronous multiplexing and flexible mapping structure.
synchronous dynamic A new type of DRAM that can run at much higher clock speeds than conventional
random access memory memory. SDRAM actually synchronizes itself with the CPU's bus and is capable of
running at 100 MHz, about three times faster than conventional FPM RAM, and about
(SDRAM)
twice as fast as EDO DRAM or BEDO DRAM. SDRAM is replacing EDO DRAM in
computers.
synchronous optical
network (SONET)
Issue 03 (2012-11-30)
A high-speed network that provides a standard interface for communications carriers to

connect networks based on fiber optical cable. SONET is designed to handle multiple
data types (voice, video, and so on). It transmits at a base rate of 51.84 Mbit/s, but
multiples of this base rate go as high as 2.488 Gbit/s.

1361
OptiX OSN 7500 II/7500/3500/1500

B Glossary
T
TCA
See threshold crossing alarm.
TCI
tag control information
TCM
tandem connection monitor
TCN
topology change notification
TCP
See Transmission Control Protocol.
TCP/IP
Transmission Control Protocol/Internet Protocol
TDC
tunable dispersion compensator
TDM
See time division multiplexing.
TE
terminal equipment
TFTP
See Trivial File Transfer Protocol.
TIM
trace identifier mismatch
TLV
See type-length-value.
TM
See terminal multiplexer.
TMN
See telecommunications management network.
TOD
time of day
TPID
tag protocol identifier
TPS
See tributary protection switching.
TPS protection
The equipment level protection that uses one standby tributary board to protect N
tributary boards. When a fault occurs on the working board, the SCC issues the switching
command, and the payload of the working board can be automatically switched over to
the specified protection board and the protection board takes over as the working board.
After the fault is rectified, the service is automatically switched to the original board.
TSD
trail signal degrade
TTI
trail trace identifier
TTL
See time to live.
TTSI
See trail termination source identifier.
TU
tributary unit
TU-LOP
tributary unit loss of pointer
TUG
tributary unit group
Tc
committed rate measurement interval
Telnet
A standard terminal emulation protocol in the TCP/IP protocol stack. Telnet allows users
to log in to remote systems and use resources as if they were connected to a local system.
Telnet is defined in RFC 854.
ToS
type of service
Issue 03 (2012-11-30)

1362
OptiX OSN 7500 II/7500/3500/1500

B Glossary
Transmission Control
Protocol (TCP)
The protocol within TCP/IP that governs the breakup of data messages into packets to
be sent using Internet Protocol (IP), and the reassembly and verification of the complete
messages from packets received by IP. A connection-oriented, reliable protocol (reliable
in the sense of ensuring error-free delivery), TCP corresponds to the transport layer in
the ISO/OSI reference model.
Trivial File Transfer

Protocol (TFTP)
A small and simple alternative to FTP for transferring files. TFTP is intended for
applications that do not need complex interactions between the client and server. TFTP
restricts operations to simple file transfers and does not provide authentication. TFTP is
small enough to be contained in ROM to be used for bootstrapping diskless machines.
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.
tangent ring
A concept borrowed from geometry. Two tangent rings have a common node between
them. The common node often leads to single-point failures.
telecommunications
management network
(TMN)
A protocol model defined by ITU-T for managing open systems in a communications

network. An architecture for management, including planning, provisioning, installation,
maintenance, operation and administration of telecommunications equipment, networks
and services.
terminal multiplexer
(TM)
A device used at a network terminal to multiplex multiple channels of low rate signals
into one channel of high rate signals, or to demultiplex one channel of high rate signals
into multiple channels of low rate signals.
threshold
An amount, limit or level on a scale. Changes will occur with a threshold reached.
threshold alarm
The alarm occurs when the monitored value exceeds the threshold.
threshold crossing
alarm (TCA)
An alarm generated when a threshold is crossed.
throughput
The maximum transmission rate of the tested object (system, equipment, connection,
service type) when no packet is discarded. Throughput can be measured with bandwidth.
throughput capability
The data input/output capability of the data transmission interface.
time division
multiplexing (TDM)
A multiplexing technology. TDM divides the sampling cycle of a channel into time slots
(TSn, n=0, 1, 2, 3), and the sampling value codes of multiple signals engross time slots
in a certain order, forming multiple multiplexing digital signals to be transmitted over
one channel.
time to live (TTL)
A technique used in best-effort delivery systems to prevent packets that loop endlessly.
The TTL is set by the sender to the maximum time the packet is allowed to be in the
network. Each router in the network decrements the TTL value when the packet arrives,
and discards any packet if the TTL counter reaches zero.
timer
Symbolic representation for a timer object (for example, a timer object may have a
primitive designated as T-Start Request). Various MAC entities utilize timer entities that
provide triggers for certain MAC state transitions.
timestamp
The current time of an event that is recorded by a computer. By using mechanisms such
as the Network Time Protocol (NTP), a computer maintains accurate current time,
calibrated to minute fractions of a second.
Issue 03 (2012-11-30)

1363
OptiX OSN 7500 II/7500/3500/1500

B Glossary
token bucket algorithm The token bucket is a container for tokens. The capacity of a token bucket is limited, and
the number of tokens determines the traffic rate of permitted packets. The token bucket
polices the traffic. Users place the tokens into the bucket regularly according to the preset
rate. If the tokens in the bucket exceed the capacity, no tokens can be put in. Packets can
be forwarded when the bucket has tokens, otherwise they cannot be transferred till there
are new tokens in the bucket. This scheme adjusts the rate of packet input.
topology
The configuration or layout of a network formed by the connections between devices on

a local area network (LAN) or between two or more LANs.
topology discovery
A technique to accurately determine the exact layout of a network using a few

assumptions about the network architecture and simple tools.
trTCM
See two rate three color marker.
traceroute
A program that prints the path to a destination. Traceroute sends a sequence of datagrams
with the time-to-live (TTL) set to 1,2, and so on, and uses ICMP time exceeded messages
that return to determine routers along the path.
traffic
The product of the number of calls made and received and the average duration of each
call in a measurement period.
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 policy
A full set of QoS policies formed by association of traffic classification and QoS actions.
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.
traffic statistics
An activity of measuring and collecting statistics of various data on devices and

telecommunications networks. With the statistics, operators can be aware of the
operating status, signaling, users, system resource usage of the devices or networks. The
statistics also help the operators manage the device operating, locate problems, monitor
and maintain the networks, and plan the networks.
trail management
function
A network level management function of the network management system. This function
enables you to configure end-to-end services, view graphic interface and visual routes
of a trail, query detailed information of a trail, filter, search and locate a trail quickly,
manage and maintain trails in a centralized manner, manage alarms and performance
data by trail, and print a trail report.
trail termination source A TTSI uniquely identifies an LSP in the network. A TTSI is carried in the connectivity
identifier (TTSI)
verification (CV) packet for checking the connectivity of a trail. If it matches the TTSI
received by the sink point, the trail has no connectivity defect.
transaction
A business between a carrier and customer, such as payment and account adjustment.
transfer
A process of transferring the account balance of an account to another account.
transit
A packet is transmitted along an LSP consisting of a series of LSRs after the packet is
labeled. The intermediate nodes are named transits.
transit node
All the nodes except the master node on an RRPP ring.
transmission delay
The period from the time when a site starts to transmit a data frame to the time when the
site finishes the data frame transmission. It consists of the transmission latency and the
equipment forwarding latency.
Issue 03 (2012-11-30)

1364
OptiX OSN 7500 II/7500/3500/1500

B Glossary
transmit power control A technical mechanism used within some networking devices in order to prevent too
much unwanted interference between different wireless networks.
transparent
transmission
A process during which the signaling protocol or data is not processed in the content but
encapsulated in the format for the processing of the next phase.
transport profile for

multiprotocol label
switching (MPLS-TP)
MPLS-TP is an extension to MPLS in terms of forwarding, OAM, reliability, NMS and

control plane protocol standardized by IETF to provide sufficient transport functionality.
tray
A component that can be installed in the cabinet for holding chassis or other devices.
tributary loopback
A fault can be located for each service path by performing loopback to each path of the
tributary board. There are three kinds of loopback modes: no loopback, outloop, and
inloop.
tributary protection
switching (TPS)
A function that uses a standby tributary processing board to protect N tributary

processing boards.
trunk
Physical communications line between two offices. It transports media signals such as
speech, data and video signals.
trunk link
A link used to transport VLAN communication between two switches.
trunk port
A switch port used to connect to other switches. The trunk port can connect to only the
trunk link. Only VLANs allowed to pass through a trunk port can be configured on the
trunk port.
tunnel
A channel on the packet switching network that transmits service traffic between PEs.
In VPN, a tunnel is an information transmission channel between two entities. The tunnel
ensures secure and transparent transmission of VPN information. In most cases, a tunnel
is an MPLS tunnel.
tunnel ID
A group of information, including the token, slot number of an outgoing interface, tunnel
type, and location method.
twisted pair cable
A type of cable that consists of two independently insulated wires twisted around one
another for the purposes of canceling out electromagnetic interference which can cause
crosstalk. The number of twists per meter makes up part of the specifications for a given
type of cable. The greater the number of twists is, the more crosstalk is reduced.
two rate three color

marker (trTCM)
An algorithm that meters an IP packet stream and marks its packets based on two rates,
Peak Information Rate (PIR) and Committed Information Rate (CIR), and their
associated burst sizes to be either green, yellow, or red. A packet is marked red if it
exceeds the PIR. Otherwise it is marked either yellow or green depending on whether it
exceeds or does not exceed the CIR.
type-length-value
(TLV)
An encoding type that features high efficiency and expansibility. It is also called CodeLength-Value (CLV). T indicates that different types can be defined through different
values. L indicates the total length of the value field. V indicates the actual data of the
TLV and is most important. TLV encoding features high expansibility. New TLVs can
be added to support new features, which is flexible in describing information loaded in
packets.
U
UART
universal asynchronous receiver/transmitter
UAS
unavailable second
Issue 03 (2012-11-30)

1365
OptiX OSN 7500 II/7500/3500/1500

B Glossary
UAT
See unavailable time event.
UBR
unspecified bit rate
UBR+
Unspecified Bit Rate Plus
UDP
See User Datagram Protocol.
UNI
See user-to-network interface.
UPC
See usage parameter control.
UPE
user-end provider edge
UPI
user payload identifier
UPM
uninterruptible power module
UPS
uninterruptible power supply
UTC
See Coordinated Universal Time.
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.
unknown multicast
packet
A packet for which no forwarding entry is found in the multicast forwarding table.
uplink
A transmission channel through which radio signals or other signals are transmitted to
the central office.
uplink tunnel
GTP Tunnel from the Mobile Node to the SGSN.
upload
An operation to report some or all configuration data of an NE to the NMS. The

configuration data then covers the configuration data stored at the NMS side.
upper limit
The maximum consumption amount that a carrier sets for a subscriber in a bill cycle. If
the consumption amount if a subscriber exceeds the maximum consumption amount that
the carrier sets, the OCS still deducts the maximum consumption amount that the carrier
sets.
upstream
In an access network, the direction that is far from the subscriber end of the link.
upstream board
A board that provides the upstream transmission function. Through an upstream board,
services can be transmitted upstream to the upper-layer device.
usage parameter
control (UPC)
During communications, UPC is implemented to monitor the actual traffic on each virtual
circuit that is input to the network. Once the specified parameter is exceeded, measures
will be taken to control. NPC is similar to UPC in function. The difference is that the
incoming traffic monitoring function is divided into UPC and NPC according to their
positions. UPC locates at the user/network interface, while NPC at the network interface.
Issue 03 (2012-11-30)

1366
OptiX OSN 7500 II/7500/3500/1500

user-to-network
interface (UNI)
B Glossary
The interface between user equipment and private or public network equipment (for
example, ATM switches).
V
V-NNI
virtual network-network interface
V-UNI
See virtual user-network interface.
V.24
The physical layer interface specification between DTE and DCE defined by the ITUT. It complies with EIA/TIA-232.
VAS
See value-added service.
VB
virtual bridge
VBR
See variable bit rate.
VC trunk
See virtual container trunk.
VCC
See virtual channel connection.
VCCV
virtual circuit connectivity verification
VCG
See virtual concatenation group.
VCI
virtual channel identifier
VCTRUNK
A virtual concatenation group applied in data service mapping, also called the internal
port of a data service processing board.
VIP
very important person
VLAN
virtual local area network
VLAN mapping
A technology that enables user packets to be transmitted over the public network by
translating private VLAN tags into public VLAN tags. When user packets arrive at the
destination private network, VLAN mapping translates public VLAN tags back into
private VLAN tags. In this manner, user packets are correctly transmitted to the
destination.
VLAN mapping table
One of the properties of the MST region, which describes mappings between VLANs
and spanning tree instances.
VLAN stacking
A technology that adds a VLAN tag to each incoming packet. The VLAN stacking
technology implements transparent transmission of C-VLANs in the ISP network to
realize the application of Layer 2 Virtual Private Network (VPN).
VP
See virtual path.
VPI
See virtual path identifier.
VPLS
See virtual private LAN service.
VPN
virtual private network
VRRP
See Virtual Router Redundancy Protocol.
VSI
virtual switch interface
Issue 03 (2012-11-30)

1367
OptiX OSN 7500 II/7500/3500/1500

B Glossary
Virtual Router
Redundancy Protocol
(VRRP)
A protocol used for multicast or multicast LANs such as an Ethernet. A group of routers
(including an active router and several backup routers) in a LAN is regarded as a virtual
router, which is called a backup group. The virtual router has its own IP address. The
host in the network communicates with other networks through this virtual router. If the
active router in the backup group fails, one of the backup routers in this backup group
becomes active and provides routing service for the host in the network.
VoIP
See voice over IP.
value-added service
(VAS)
A service provided by carriers and service providers (SPs) together for subscribers based
on voice, data, images, SMS messages, and so on. Communication network technologies,
computer technologies, and Internet technologies are used to provide value-added
services.
variable bit rate (VBR) One of the traffic classes used by ATM (Asynchronous Transfer Mode). Unlike a
permanent CBR (Constant Bit Rate) channel, a VBR data stream varies in bandwidth
and is better suited to non real time transfers than to real-time streams such as voice calls.
virtual channel
connection (VCC)
A VC logical trail that carries data between two end points in an ATM network. A pointto-multipoint VCC is a set of ATM virtual connections between two or multiple end
points.
virtual circuit
A channel or circuit established between two points on a data communications network

with packet switching. Virtual circuits can be permanent virtual circuits (PVCs) or
switched virtual circuits (SVCs) .
virtual concatenation
group (VCG)
A group of co-located member trail termination functions that are connected to the same
virtual concatenation link
virtual container trunk The logical path formed by some cascaded VCs.
(VC trunk)
virtual fiber
The fiber that is created between different devices. A virtual fiber represents the optical
path that bears SDH services in a WDM system.
virtual path (VP)
A bundle of virtual channels, all of which are switched transparently across an ATM
network based on a common VPI.
virtual path identifier

(VPI)
The field in the Asynchronous Transfer Mode (ATM) cell header that identifies to which
virtual path the cell belongs.
virtual private LAN

service (VPLS)
A type of point-to-multipoint L2VPN service provided over the public network. VPLS
enables geographically isolated user sites to communicate with each other through the
MAN/WAN as if they are on the same LAN.
virtual user-network
interface (V-UNI)
A virtual user-network interface, works as an action point to perform service

classification and traffic control in HQoS.
voice over IP (VoIP)
An IP telephony term for a set of facilities used to manage the delivery of voice
information over the Internet. VoIP involves sending voice information in a digital form
in discrete packets rather than by using the traditional circuit-committed protocols of the
public switched telephone network (PSTN).
voltage drop
The voltage developed across a component or conductor by the flow of current through
the resistance or impedance of that component or conductor.
W
WAN
Issue 03 (2012-11-30)
See wide area network.

1368
OptiX OSN 7500 II/7500/3500/1500

B Glossary
WCDMA
See Wideband Code Division Multiple Access.
WDM
wavelength division multiplexing
WFQ
See weighted fair queuing.
WLAN
See wireless local area network.
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.
Wideband Code
Division Multiple
Access (WCDMA)
A standard defined by the ITU-T for the third-generation wireless technology derived
from the Code Division Multiple Access (CDMA) technology.
wait to restore (WTR)
The number of minutes to wait before services are switched back to the working line.
wavelength
The distance between successive peaks or troughs in a traveling wave, that is, the distance
over which a wave is transmitted within a vibration period.
wavelength protection
group
Data for describing the wavelength protection structure. Its function is similar to that of
the protection subnet for SDH NEs. The wavelength path protection can work only with
the correct configuration of the wavelength protection group.
weighted fair queuing

(WFQ)
A fair queue scheduling algorithm based on bandwidth allocation weights. This

scheduling algorithm allocates the total bandwidth of an interface to queues, according
to their weights and schedules the queues cyclically. In this manner, packets of all priority
queues can be scheduled.
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.
wireless local area

network (WLAN)
A hybrid of the computer network and the wireless communication technology. It uses
wireless multiple address channels as transmission media and carriers out data interaction
through electromagnetic wave to implement the functions of the traditional LAN.
working path
A path allocated to transport the normal traffic.
working service
A specific service that is part of a protection group and is labeled working.
wrapping
A protection switching mode defined in ITU-T G.8132, which is applicable to packetbased T-MPLS ring networks and similar to SDH two-fiber bidirectional multiplex
section protection (MSP). In this mode, the switching is triggered by the node that detects
a failure. For details, see ITU-T G.841.
X
X.21
Issue 03 (2012-11-30)
ITU-T standard for serial communications over synchronous digital lines. It is mainly
used in Europe and Japan.

1369
OptiX OSN 7500 II/7500/3500/1500

X.25
B Glossary
A data link layer protocol. It defines the communication in the Public Data Network
(PDN) between a host and a remote terminal.
Y
Y.1731
Issue 03 (2012-11-30)
The OAM protocol introduced by the ITU-T. Besides the contents defined by
IEEE802.1ag, ITU-T Recommendation Y.173 also defines the following combined
OAM messages: Alarm Indication Signal (AIS), Remote Defect Indication (RDI),
Locked Signal (LCK), Test Signal, Automatic Protection Switching (APS), Maintenance
Communication Channel (MCC), Experimental (EXP), and Vendor Specific (VSP) for
fault management and performance monitoring, such as frame loss measurement (LM),
and delay measurement (DM).

1370

OSN 7500 II&amp;7500&amp;3500&amp;1500 V200R011C02 Feature Description (Packet Transport Domain) 03

Enviado por

Dados do documento

Direitos autorais

Formatos disponíveis

Compartilhar este documento

Compartilhar ou incorporar documento

Opções de compartilhamento

Você considera este documento útil?

Este conteúdo é inapropriado?

Direitos autorais:

Formatos disponíveis

OSN 7500 II&amp;7500&amp;3500&amp;1500 V200R011C02 Feature Description (Packet Transport Domain) 03

Enviado por

Direitos autorais:

Formatos disponíveis

OptiX OSN 7500 II/7500/3500/1500

Feature Description (Packet

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 OSN 7500 II/7500/3500/1500

About This Document

About This Document

OptiX OSN 7500 II

OptiX OSN 7500

OptiX OSN 3500

OptiX OSN 1500

Installation and Commissioning Engineer

Data Configuration Engineer

Huawei Proprietary and Confidential

OptiX OSN 7500 II/7500/3500/1500

About This Document

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

Indicates a tip that may help you solve a problem or save

Provides additional information to emphasize or supplement

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

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

Updates in Issue 03 (2012-11-30) Based on Product Version V200R011C02

"SNMP" is added in "RMON".

"Feature Dependency and Limitation" is modified in "Link Aggregation".

Updates in Issue 02 (2011-10-26) Based on Product Version V200R011C02

Huawei Proprietary and Confidential

OptiX OSN 7500 II/7500/3500/1500

About This Document

"Availability" is optimized for each feature.

T2PSXCSA is deleted in "Availability" of "HWECC Solution", "Hybrid Networking

The "PW FRR" is modified to "PW FPS".

Updates in Issue 01 (2011-07-15) Based on Product Version V200R011C02

"Specifications" is added for each feature.

Updates in Issue 02 (2011-04-15) Based on Product Version V200R011C01

"MPLS Basics" is added in "Packet Features".

"PWE3 Basics" is added in "Packet Features".

"IMA" is added in "Packet Features".

"ETH PWE3" is added in "Packet Features".

"PW FPS Protection" is added in "MPLS PW APS".

"TDM PWE3" is added in "Packet Features".

"CES ACR" is added in "Clock Solution".

Updates in Issue 01 (2011-01-25) Based on Product Version V200R011C01

OptiX OSN 7500 II is added.

"ATM PWE3" is added in "Packet Features".

"ATM Traffic Management" is added in "Packet Features".

"ATM OAM" is added in "O&M Solutions".

"IGMP Snooping" is added in "Packet Features".

"Packet-based linear MSP" is added in "Packet Features".

"Protection Solutions for a 3G Bearer Network" is added.

Updates in Issue 02 (2010-11-01) Based on Product Version V200R011C00

Huawei Proprietary and Confidential

OptiX OSN 7500 II/7500/3500/1500

"MPLS PW APS" is optimized.

"MPLS OAM" is optimized.

About This Document

Updates in Issue 01 (2010-07-20) Based on Product Version V200R011C00

Huawei Proprietary and Confidential

OptiX OSN 7500 II/7500/3500/1500

Huawei Proprietary and Confidential

OptiX OSN 7500 II/7500/3500/1500

OSN 7500 II&7500&3500&1500 V200R011C02 Feature Description (Packet Transport Domain) 03

OSN 7500 II&7500&3500&1500 V200R011C02 Feature Description (Packet Transport Domain) 03