RTN 620 Feature Description (V100R005C00 - 05)

OptiX RTN 620 Radio Transmission System V100R005C00
Feature Description
Issue Date 05 2010-10-30
HUAWEI TECHNOLOGIES CO., LTD.
Copyright Huawei Technologies Co., Ltd. 2010. 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 the warranty of any kind, express or implied.
Huawei Technologies Co., Ltd.

Address: Huawei Industrial Base Bantian, Longgang Shenzhen 518129 People's Republic of China http://www.huawei.com support@huawei.com
Website: Email:
Issue 05 (2010-10-30)
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.
OptiX RTN 620 Radio Transmission System Feature Description
About This Document
About This Document

Related Versions
The following table lists the product versions related to this document. Product Name OptiX RTN 620 iManager U2000 Version V100R005C00 V100R002C00
Intended Audience
This document describes the main features of the OptiX RTN 620 radio transmission system. It provides readers a comprehensive knowledge on the functionality, principle, configuration, and maintenance of the product features. This document is intended for: l l l l Network Planning Engineer Installation and Commissioning Engineer Data Configuration Engineer System Maintenance Engineer
Symbol Conventions
The symbols that may be found in this document are defined as follows. Symbol Description Indicates a hazard with a high level of risk, which if not avoided, will result in death or serious injury. Indicates a hazard with a medium or low level of risk, which if not avoided, could result in minor or moderate injury.
Issue 05 (2010-10-30)
iii
About This Document
Symbol
Description Indicates a potentially hazardous situation, which if not avoided, could result in equipment damage, data loss, performance degradation, or unexpected results. Indicates a tip that may help you solve a problem or save time. Provides additional information to emphasize or supplement important points of the main text.
GUI Conventions
The GUI conventions that may be found in this document are defined as follows. Convention Boldface > Description 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 05 (2010-10-30) Based on Product Version V100R005C00

This document is the fifth release of the V100R005C00 version. The following table lists the updates in this document. Update 7 1+1 HSB 8 1+1 FD 9 1+1 SD Description The descriptions of the trigger conditions for automatic HSB switching are modified.
iv
Issue 05 (2010-10-30)
About This Document

This document is the fourth release of the V100R005C00 version. The following table lists the updates in this document. Update Description Fixed the known bugs.

This document is the third release of the V100R005C00 version. The following table lists the updates in this document. Update 7.6 Planning Guidelines Description Modified the suggestion for using reverse switching.

This document is the second release of the V100R005C00 version. The following table lists the updates in this document. Update 14.8 Configuration Procedure Description The note attached to step 3 in table "Procedure for configuring SNCP services" is modified. Description of the networking scenarios is optimized. The revertive mode is changed to nonrevertive in section "Planning Guidelines of LAGs in the case of 1+1 Protection". The following changes are made to this document: l The revertive mode is changed to revertive in table 1. l The LAG type is changed to manual and revertive mode is changed to nonrevertive in table 2. 24.9.2 Service Planning In the case of NE1, the LAG type is changed to manual and revertive mode is changed to non-revertive.
v
23.9.1 Networking Diagram 24.7 Planning Guidelines
24.8 Configuration Procedure
Issue 05 (2010-10-30)
About This Document
Update 25.6.2 Point-to-Multipoint Service
Description The diagram of locating a fault in section "LPT for Ethernet Port-Shared Ethernet Services" is modified. The following changes are made to this document: l The CBS and MBS specifications are deleted. l The description of the weight allocation of WRR specification is modified.
26.3 Specifications
28.2 Specifications
The following description is added: When the FE/GE port actually works in the 10BASE-T mode, it does not support synchronous Ethernet clocks.

This document is the first release of the V100R005C00 version.
vi
Issue 05 (2010-10-30)
Contents
Contents
About This Document...................................................................................................................iii 1 Introduction to the DCN...........................................................................................................1-1
1.1 Composition of the DCN.................................................................................................................................1-2 1.2 Huawei DCN Solution....................................................................................................................................1-3 1.3 Protocol Converter Solution............................................................................................................................1-5
2 HWECC Solution.......................................................................................................................2-1
2.1 Introduction.....................................................................................................................................................2-3 2.2 Basic Concepts................................................................................................................................................2-4 2.2.1 HW ECC Protocol Stack........................................................................................................................2-4 2.2.2 Extended ECC........................................................................................................................................2-7 2.3 Specifications................................................................................................................................................2-10 2.4 Reference Standards and Protocols...............................................................................................................2-11 2.5 Availability....................................................................................................................................................2-11 2.6 Principles.......................................................................................................................................................2-12 2.6.1 Establishing ECC Routes.....................................................................................................................2-13 2.6.2 Packet Transfer.....................................................................................................................................2-14 2.6.3 Extended ECC......................................................................................................................................2-15 2.7 Planning Guidelines......................................................................................................................................2-16 2.8 Configuration Flow.......................................................................................................................................2-18 2.9 Configuration Example.................................................................................................................................2-20 2.9.1 Networking Diagram............................................................................................................................2-20 2.9.2 Service Planning...................................................................................................................................2-21 2.9.3 Configuration Process..........................................................................................................................2-22 2.10 Task Collection...........................................................................................................................................2-25 2.11 Relevant Alarms and Events.......................................................................................................................2-25 2.12 FAQs...........................................................................................................................................................2-25
3 IP over DCC Solution................................................................................................................3-1

3.1 Introduction.....................................................................................................................................................3-3 3.2 Basic Concepts................................................................................................................................................3-3 3.2.1 IP over DCC Protocol Stack...................................................................................................................3-4 3.2.2 Access Modes.........................................................................................................................................3-7 3.3 Specifications..................................................................................................................................................3-7 Issue 05 (2010-10-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. vii
Contents
3.4 Reference Standards and Protocols.................................................................................................................3-9 3.5 Availability......................................................................................................................................................3-9 3.6 Principles.......................................................................................................................................................3-10 3.7 Planning Guidelines......................................................................................................................................3-11 3.8 Configuration Flow.......................................................................................................................................3-16 3.9 Configuration Example.................................................................................................................................3-17 3.9.1 Networking Diagram............................................................................................................................3-18 3.9.2 Service Planning...................................................................................................................................3-18 3.9.3 Configuration Process..........................................................................................................................3-19 3.10 Task Collection...........................................................................................................................................3-22 3.11 Relevant Alarms and Events.......................................................................................................................3-23 3.12 FAQs...........................................................................................................................................................3-23
4 OSI over DCC Solution.............................................................................................................4-1

4.1 Introduction.....................................................................................................................................................4-3 4.2 Basic Concepts................................................................................................................................................4-3 4.2.1 OSI over DCC Protocol Stack................................................................................................................4-4 4.2.2 NMS Access Modes...............................................................................................................................4-8 4.3 Specifications..................................................................................................................................................4-8 4.4 Reference Standards and Protocols...............................................................................................................4-10 4.5 Availability....................................................................................................................................................4-10 4.6 Principles.......................................................................................................................................................4-11 4.7 Planning Guidelines......................................................................................................................................4-12 4.8 Configuration Flow.......................................................................................................................................4-13 4.9 Configuration Example.................................................................................................................................4-15 4.9.1 Networking Diagram............................................................................................................................4-15 4.9.2 Service Planning...................................................................................................................................4-16 4.9.3 Configuration Process..........................................................................................................................4-17 4.10 Task Collection...........................................................................................................................................4-19 4.11 Relevant Alarms and Events.......................................................................................................................4-19 4.12 FAQs...........................................................................................................................................................4-20
5 DCC Transparent Transmission Solution.............................................................................5-1

5.1 Introduction.....................................................................................................................................................5-2 5.2 Specifications..................................................................................................................................................5-4 5.3 Availability......................................................................................................................................................5-5 5.4 Principles.........................................................................................................................................................5-5 5.5 Planning Guidelines........................................................................................................................................5-6 5.6 Configuration Procedure.................................................................................................................................5-7 5.7 Configuration Example...................................................................................................................................5-8 5.7.1 Networking Diagram..............................................................................................................................5-8 5.7.2 Service Planning.....................................................................................................................................5-9 5.7.3 Configuration Process..........................................................................................................................5-10 5.8 Task Collection.............................................................................................................................................5-12 viii Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 05 (2010-10-30)
Contents
5.9 Relevant Alarms and Events.........................................................................................................................5-12 5.10 FAQs...........................................................................................................................................................5-12
6 DCC Transparent Transmission Through the External Clock Interface Solution........6-1

6.1 Introduction.....................................................................................................................................................6-3 6.2 Specifications..................................................................................................................................................6-4 6.3 Availability......................................................................................................................................................6-5 6.4 Principles.........................................................................................................................................................6-5 6.5 Planning Guidelines........................................................................................................................................ 6-6 6.6 Configuration Procedure.................................................................................................................................6-6 6.7 Configuration Example...................................................................................................................................6-7 6.7.1 Networking Diagram..............................................................................................................................6-7 6.7.2 Service Planning.....................................................................................................................................6-8 6.7.3 Configuration Process............................................................................................................................6-8 6.8 Task Collection............................................................................................................................................... 6-9 6.9 Relevant Alarms and Events.........................................................................................................................6-10 6.10 FAQs...........................................................................................................................................................6-10
7 1+1 HSB........................................................................................................................................7-1
7.1 Introduction.....................................................................................................................................................7-3 7.2 Basic Concepts................................................................................................................................................7-3 7.2.1 System Configuration.............................................................................................................................7-4 7.2.2 Protection Type......................................................................................................................................7-6 7.2.3 Switching Condition...............................................................................................................................7-6 7.2.4 Switching Impact....................................................................................................................................7-9 7.3 Specifications................................................................................................................................................7-10 7.4 Availability....................................................................................................................................................7-10 7.5 Principles.......................................................................................................................................................7-11 7.5.1 SDH/PDH Radio..................................................................................................................................7-11 7.5.2 Hybrid Radio........................................................................................................................................7-13 7.6 Planning Guidelines......................................................................................................................................7-16 7.7 Configuration Procedure...............................................................................................................................7-16 7.8 Configuration Example.................................................................................................................................7-17 7.8.1 Networking Diagram............................................................................................................................7-17 7.8.2 Service Planning...................................................................................................................................7-18 7.8.3 Configuration Process..........................................................................................................................7-19 7.9 Task Collection.............................................................................................................................................7-20 7.10 Relevant Alarms and Events.......................................................................................................................7-20 7.11 FAQs...........................................................................................................................................................7-21
8 1+1 FD...........................................................................................................................................8-1
8.1 Introduction.....................................................................................................................................................8-3 8.2 Basic Concepts................................................................................................................................................8-4 8.2.1 System Configuration.............................................................................................................................8-4 Issue 05 (2010-10-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. ix
Contents
OptiX RTN 620 Radio Transmission System Feature Description 8.2.2 Protection Type......................................................................................................................................8-7 8.2.3 Switching Conditions.............................................................................................................................8-8 8.2.4 Switching Impact..................................................................................................................................8-11
8.3 Specifications................................................................................................................................................8-11 8.4 Availability....................................................................................................................................................8-12 8.5 Principles.......................................................................................................................................................8-13 8.5.1 SDH/PDH Radio..................................................................................................................................8-13 8.5.2 Hybrid Radio........................................................................................................................................8-15 8.6 Planning Guidelines......................................................................................................................................8-19 8.7 Configuration Procedure...............................................................................................................................8-19 8.8 Configuration Example.................................................................................................................................8-20 8.8.1 Networking Diagram............................................................................................................................8-20 8.8.2 Service Planning...................................................................................................................................8-21 8.8.3 Configuration Process..........................................................................................................................8-22 8.9 Task Collection.............................................................................................................................................8-23 8.10 Relevant Alarms and Events.......................................................................................................................8-24 8.11 FAQs...........................................................................................................................................................8-24
9 1+1 SD...........................................................................................................................................9-1
9.1 Introduction.....................................................................................................................................................9-3 9.2 Basic Concepts................................................................................................................................................9-4 9.2.1 System Configuration.............................................................................................................................9-4 9.2.2 Protection Type......................................................................................................................................9-6 9.2.3 Switching Condition...............................................................................................................................9-7 9.2.4 Switching Impact..................................................................................................................................9-11 9.3 Specifications................................................................................................................................................9-11 9.4 Availability....................................................................................................................................................9-11 9.5 Principles.......................................................................................................................................................9-12 9.5.1 SDH/PDH Radio..................................................................................................................................9-13 9.5.2 Hybrid Radio........................................................................................................................................9-15 9.6 Planning Guidelines......................................................................................................................................9-19 9.7 Configuration Procedure...............................................................................................................................9-20 9.8 Configuration Example.................................................................................................................................9-20 9.8.1 Networking Diagram............................................................................................................................9-20 9.8.2 Service Planning...................................................................................................................................9-21 9.8.3 Configuration Process..........................................................................................................................9-22 9.9 Task Collection.............................................................................................................................................9-23 9.10 Relevant Alarms and Events.......................................................................................................................9-24 9.11 FAQs...........................................................................................................................................................9-24
10 Cross-Polarization Interference Cancellation...................................................................10-1

10.1 Introduction.................................................................................................................................................10-3 10.2 Basic Concepts............................................................................................................................................10-4 10.2.1 CCDP and XPIC.................................................................................................................................10-4 x Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 05 (2010-10-30)
Contents
10.2.2 System Configuration.........................................................................................................................10-5 10.3 Specifications..............................................................................................................................................10-6 10.4 Availability..................................................................................................................................................10-6 10.5 Principles.....................................................................................................................................................10-8 10.6 Planning Guidelines....................................................................................................................................10-9 10.7 Configuration Procedure.............................................................................................................................10-9 10.8 Configuration Example.............................................................................................................................10-10 10.8.1 Networking Diagram........................................................................................................................10-10 10.8.2 Service Planning...............................................................................................................................10-12 10.8.3 Configuration Process......................................................................................................................10-14 10.9 Task Collection.........................................................................................................................................10-16 10.10 Relevant Alarms and Events...................................................................................................................10-16 10.11 FAQs.......................................................................................................................................................10-16
11 N+1 Protection........................................................................................................................11-1
11.1 Introduction.................................................................................................................................................11-3 11.2 Basic Concepts............................................................................................................................................11-4 11.2.1 System Configuration.........................................................................................................................11-4 11.2.2 Protection Type..................................................................................................................................11-7 11.2.3 Switching Condition...........................................................................................................................11-8 11.2.4 Switching Impact..............................................................................................................................11-10 11.3 Specifications............................................................................................................................................11-10 11.4 Reference Standards and Protocols...........................................................................................................11-10 11.5 Availability................................................................................................................................................11-11 11.6 Principles...................................................................................................................................................11-11 11.6.1 2+1 Protection Configuration...........................................................................................................11-11 11.6.2 3+1 Protection Configuration...........................................................................................................11-13 11.7 Planning Guidelines..................................................................................................................................11-15 11.8 Configuration Procedure...........................................................................................................................11-15 11.9 Configuration Example.............................................................................................................................11-17 11.9.1 Networking Diagram........................................................................................................................11-17 11.9.2 Service Planning...............................................................................................................................11-19 11.9.3 Configuration Process......................................................................................................................11-22 11.10 Task Collection.......................................................................................................................................11-25 11.11 Relevant Alarms and Performance Events..............................................................................................11-25 11.12 FAQs.......................................................................................................................................................11-26
12 Automatic Transmit Power Control...................................................................................12-1

12.1 Introduction.................................................................................................................................................12-2 12.2 Specifications..............................................................................................................................................12-3 12.3 Availability..................................................................................................................................................12-3 12.4 Principles.....................................................................................................................................................12-4 12.5 Planning Guidelines....................................................................................................................................12-5 12.6 Configuration Procedure.............................................................................................................................12-6 Issue 05 (2010-10-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. xi
Contents
12.7 Configuration Example...............................................................................................................................12-6 12.7.1 Networking Diagram..........................................................................................................................12-7 12.7.2 Service Planning.................................................................................................................................12-7 12.7.3 Configuration Process........................................................................................................................12-8 12.8 Task Collection...........................................................................................................................................12-8 12.9 Relevant Alarms and Events.......................................................................................................................12-9 12.10 FAQs.........................................................................................................................................................12-9
13 Adaptive Modulation............................................................................................................13-1
13.1 Introduction.................................................................................................................................................13-2 13.2 Specifications..............................................................................................................................................13-3 13.3 Availability..................................................................................................................................................13-4 13.4 Principles.....................................................................................................................................................13-4 13.5 Planning Guidelines....................................................................................................................................13-6 13.6 Configuration Procedure.............................................................................................................................13-7 13.7 Configuration Example...............................................................................................................................13-7 13.7.1 Networking Diagram..........................................................................................................................13-7 13.7.2 Service Planning.................................................................................................................................13-7 13.7.3 Configuration Process........................................................................................................................13-8 13.8 Task Collection...........................................................................................................................................13-9 13.9 Relevant Alarms and Events.......................................................................................................................13-9 13.10 FAQs.........................................................................................................................................................13-9
14 Subnetwork Connection Protection................................................................................... 14-1

14.1 Introduction.................................................................................................................................................14-3 14.2 Basic Concepts............................................................................................................................................14-3 14.2.1 Protection Type..................................................................................................................................14-4 14.2.2 SNCP Service Pair.............................................................................................................................14-4 14.2.3 Hold-Off Time....................................................................................................................................14-5 14.2.4 Switching Conditions.........................................................................................................................14-7 14.2.5 Switching Impact..............................................................................................................................14-11 14.3 Specifications............................................................................................................................................14-11 14.4 Reference Standards and Protocols...........................................................................................................14-12 14.5 Availability................................................................................................................................................14-12 14.6 Principles...................................................................................................................................................14-13 14.7 Planning Guidelines..................................................................................................................................14-14 14.8 Configuration Procedure...........................................................................................................................14-15 14.9 Configuration Example.............................................................................................................................14-16 14.9.1 Networking Diagram........................................................................................................................14-16 14.9.2 Service Planning...............................................................................................................................14-17 14.9.3 Configuration Process......................................................................................................................14-19 14.10 Task Collection.......................................................................................................................................14-23 14.11 Relevant Alarms and Events...................................................................................................................14-24 14.12 FAQs.......................................................................................................................................................14-24 xii Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 05 (2010-10-30)
Contents
15 Linear MSP..............................................................................................................................15-1
15.1 Introduction.................................................................................................................................................15-3 15.2 Basic Concepts............................................................................................................................................15-4 15.2.1 Protection Type..................................................................................................................................15-5 15.2.2 Meanings of K Bytes..........................................................................................................................15-6 15.2.3 Switching Conditions.........................................................................................................................15-7 15.2.4 Switching Impact..............................................................................................................................15-10 15.3 Specifications............................................................................................................................................15-10 15.4 Reference Standards and Protocols...........................................................................................................15-11 15.5 Availability................................................................................................................................................15-11 15.6 Principles...................................................................................................................................................15-11 15.6.1 1+1 Linear MSP...............................................................................................................................15-12 15.6.2 1:N Linear MSP...............................................................................................................................15-13 15.7 Planning Guidelines..................................................................................................................................15-14 15.8 Configuration Procedure...........................................................................................................................15-15 15.9 Configuration Example.............................................................................................................................15-15 15.9.1 Networking Diagram........................................................................................................................15-16 15.9.2 Service Planning...............................................................................................................................15-16 15.9.3 Configuration Process......................................................................................................................15-17 15.10 Task Collection.......................................................................................................................................15-18 15.11 Relevant Alarms and Events...................................................................................................................15-18 15.12 FAQs.......................................................................................................................................................15-19
16 Two-Fiber Bidirectional Ring MSP....................................................................................16-1

16.1 Introduction.................................................................................................................................................16-3 16.2 Basic Concepts............................................................................................................................................16-4 16.2.1 Protection Type..................................................................................................................................16-5 16.2.2 Meanings of Byte K...........................................................................................................................16-5 16.2.3 Switching Conditions.........................................................................................................................16-7 16.2.4 Switching Impact................................................................................................................................16-9 16.3 Specifications..............................................................................................................................................16-9 16.4 Reference Standards and Protocols...........................................................................................................16-10 16.5 Availability................................................................................................................................................16-10 16.6 Principles...................................................................................................................................................16-10 16.7 Planning Guidelines..................................................................................................................................16-12 16.8 Configuration Procedure...........................................................................................................................16-13 16.9 Configuration Example.............................................................................................................................16-13 16.9.1 Networking Diagram........................................................................................................................16-13 16.9.2 Service Planning...............................................................................................................................16-14 16.9.3 Configuration Process......................................................................................................................16-14 16.10 Task Collection.......................................................................................................................................16-16 16.11 Relevant Alarms and Events...................................................................................................................16-16 16.12 FAQs.......................................................................................................................................................16-16 Issue 05 (2010-10-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. xiii
Contents
17 Ethernet over SDH/PDH.......................................................................................................17-1

17.1 Introduction.................................................................................................................................................17-3 17.2 Basic Concepts............................................................................................................................................17-6 17.2.1 Encapsulation and Mapping Protocols...............................................................................................17-6 17.2.2 Virtual Concatenation........................................................................................................................ 17-7 17.2.3 LCAS..................................................................................................................................................17-8 17.3 Specifications..............................................................................................................................................17-8 17.4 Reference Standards and Protocols...........................................................................................................17-10 17.5 Availability................................................................................................................................................17-11 17.6 Working Principle.....................................................................................................................................17-12 17.6.1 Encapsulation and Mapping.............................................................................................................17-12 17.6.2 Virtual Concatenation......................................................................................................................17-16 17.6.3 LCAS................................................................................................................................................17-18 17.7 Planning Guidelines..................................................................................................................................17-22 17.8 Configuration Procedure...........................................................................................................................17-23 17.9 Configuration Example.............................................................................................................................17-26 17.10 Task Collection.......................................................................................................................................17-26 17.11 Relevant Alarms and Events...................................................................................................................17-26 17.12 FAQs.......................................................................................................................................................17-28
18 VLAN........................................................................................................................................18-1
18.1 Introduction.................................................................................................................................................18-3 18.2 Basic Concepts............................................................................................................................................18-4 18.2.1 Frame Format.....................................................................................................................................18-4 18.2.2 TAG Attribute....................................................................................................................................18-5 18.3 Specifications..............................................................................................................................................18-6 18.4 Reference Standards and Protocols.............................................................................................................18-6 18.5 Availability..................................................................................................................................................18-7 18.6 Principles.....................................................................................................................................................18-7 18.7 Planning Guidelines.................................................................................................................................... 18-7 18.8 Configuration Procedure.............................................................................................................................18-8 18.9 Configuration Example.............................................................................................................................18-21 18.10 Task Collection.......................................................................................................................................18-21 18.11 Relevant Alarms and Events...................................................................................................................18-22 18.12 FAQs.......................................................................................................................................................18-22
19 QinQ.........................................................................................................................................19-1
19.1 Introduction.................................................................................................................................................19-3 19.2 Basic Concepts............................................................................................................................................19-4 19.2.1 Frame Format.....................................................................................................................................19-4 19.2.2 Network Attributes.............................................................................................................................19-5 19.2.3 Application of the QinQ Technology in Private Line Services..........................................................19-6 19.2.4 Application of the QinQ Technology in 802.1ad Bridge Services.....................................................19-9 19.3 Specifications............................................................................................................................................19-11 xiv Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 05 (2010-10-30)
Contents
19.4 Reference Standards and Protocols...........................................................................................................19-12 19.5 Availability................................................................................................................................................19-12 19.6 Principles...................................................................................................................................................19-13 19.7 Planning Guidelines..................................................................................................................................19-15 19.8 Configuration Procedure...........................................................................................................................19-16 19.9 Configuration Example.............................................................................................................................19-29 19.10 Task Collection.......................................................................................................................................19-29 19.11 Relevant Alarms and Events...................................................................................................................19-30 19.12 FAQs.......................................................................................................................................................19-30
20 Layer 2 Switching................................................................................................................... 20-1

20.1 Introduction.................................................................................................................................................20-3 20.2 Basic Concepts............................................................................................................................................20-4 20.2.1 Bridge.................................................................................................................................................20-4 20.2.2 Hub/Spoke..........................................................................................................................................20-6 20.2.3 Managing a MAC Address Table.......................................................................................................20-7 20.3 Specifications..............................................................................................................................................20-7 20.4 Reference Standards and Protocols.............................................................................................................20-8 20.5 Availability..................................................................................................................................................20-8 20.6 Principles.....................................................................................................................................................20-9 20.7 Planning Guidelines..................................................................................................................................20-10 20.8 Configuration Procedure...........................................................................................................................20-10 20.9 Configuration Example.............................................................................................................................20-31 20.10 Task Collection.......................................................................................................................................20-31 20.11 Relevant Alarms and Events...................................................................................................................20-32 20.12 FAQs.......................................................................................................................................................20-32
21 Ethernet Ring Protection Switching...................................................................................21-1

21.1 Introduction.................................................................................................................................................21-3 21.2 Basic Concepts............................................................................................................................................21-4 21.2.1 Protection Instance.............................................................................................................................21-5 21.2.2 Protection Type..................................................................................................................................21-6 21.2.3 R-APS Message..................................................................................................................................21-6 21.2.4 R-APS Timer......................................................................................................................................21-8 21.2.5 Switching Condition...........................................................................................................................21-9 21.2.6 Switching Impact..............................................................................................................................21-10 21.3 Specifications............................................................................................................................................21-11 21.4 Reference Standards and Protocols...........................................................................................................21-11 21.5 Availability................................................................................................................................................21-12 21.6 Principles...................................................................................................................................................21-12 21.7 Planning Guidelines..................................................................................................................................21-15 21.8 Configuration Procedure...........................................................................................................................21-16 21.9 Configuration Example.............................................................................................................................21-17 21.9.1 Networking Diagram........................................................................................................................21-17 Issue 05 (2010-10-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. xv
Contents
OptiX RTN 620 Radio Transmission System Feature Description 21.9.2 Service Planning...............................................................................................................................21-18 21.9.3 Configuration Process......................................................................................................................21-19
21.10 Task Collection.......................................................................................................................................21-20 21.11 Relevant Alarms and Events...................................................................................................................21-20 21.12 FAQs.......................................................................................................................................................21-21
22 STP............................................................................................................................................22-1
22.1 Introduction.................................................................................................................................................22-3 22.2 Basic Concepts............................................................................................................................................22-4 22.3 Specifications..............................................................................................................................................22-7 22.4 Reference Standards and Protocols.............................................................................................................22-7 22.5 Availability..................................................................................................................................................22-8 22.6 Principles.....................................................................................................................................................22-8 22.7 Planning Guidelines..................................................................................................................................22-10 22.8 Configuration Procedure...........................................................................................................................22-11 22.9 Configuration Example.............................................................................................................................22-11 22.9.1 Networking Diagram........................................................................................................................22-12 22.9.2 Service Planning...............................................................................................................................22-12 22.9.3 Configuration Process......................................................................................................................22-14 22.10 Task Collection.......................................................................................................................................22-15 22.11 Relevant Alarms and Events...................................................................................................................22-15 22.12 FAQs.......................................................................................................................................................22-15
23 IGMP Snooping......................................................................................................................23-1
23.1 Introduction.................................................................................................................................................23-3 23.2 Basic Concepts............................................................................................................................................23-4 23.3 Specifications..............................................................................................................................................23-5 23.4 Reference Standards and Protocols.............................................................................................................23-6 23.5 Availability..................................................................................................................................................23-6 23.6 Principles.....................................................................................................................................................23-7 23.7 Planning Guidelines.................................................................................................................................... 23-8 23.8 Configuration Procedure.............................................................................................................................23-8 23.9 Configuration Example...............................................................................................................................23-9 23.9.1 Networking Diagram..........................................................................................................................23-9 23.9.2 Service Planning...............................................................................................................................23-10 23.9.3 Configuration Process......................................................................................................................23-10 23.10 Task Collection.......................................................................................................................................23-11 23.11 Relevant Alarms and Events...................................................................................................................23-11 23.12 FAQs.......................................................................................................................................................23-11
24 Link Aggregation Group......................................................................................................24-1

24.1 Introduction.................................................................................................................................................24-3 24.2 Basic Concepts............................................................................................................................................24-3 24.2.1 LAG Types.........................................................................................................................................24-4 xvi Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 05 (2010-10-30)
Contents
24.2.2 Port Types.......................................................................................................................................... 24-5 24.2.3 Switching Conditions.........................................................................................................................24-5 24.2.4 Switching Impact................................................................................................................................24-6 24.3 Specifications..............................................................................................................................................24-6 24.4 Reference Standards and Protocols.............................................................................................................24-7 24.5 Availability..................................................................................................................................................24-7 24.6 Principles.....................................................................................................................................................24-7 24.7 Planning Guidelines....................................................................................................................................24-9 24.8 Configuration Procedure...........................................................................................................................24-10 24.9 Configuration Example.............................................................................................................................24-11 24.9.1 Networking Diagram........................................................................................................................24-11 24.9.2 Service Planning...............................................................................................................................24-12 24.9.3 Configuration Process......................................................................................................................24-12 24.10 Task Collection.......................................................................................................................................24-13 24.11 Relevant Alarms and Events...................................................................................................................24-13 24.12 FAQs.......................................................................................................................................................24-13
25 Link State Pass Through.......................................................................................................25-1

25.1 Introduction.................................................................................................................................................25-3 25.2 Basic Concepts............................................................................................................................................25-4 25.2.1 LPT Bearer Mode...............................................................................................................................25-5 25.2.2 Hold-Off Time....................................................................................................................................25-5 25.3 Specifications..............................................................................................................................................25-7 25.4 Reference Standards and Protocols.............................................................................................................25-7 25.5 Availability..................................................................................................................................................25-8 25.6 Principles.....................................................................................................................................................25-8 25.6.1 Point-to-Point Service........................................................................................................................25-9 25.6.2 Point-to-Multipoint Service..............................................................................................................25-10 25.7 Planning Guidelines..................................................................................................................................25-12 25.8 Configuration Procedure...........................................................................................................................25-13 25.9 Configuration Example.............................................................................................................................25-13 25.9.1 Networking Diagram........................................................................................................................25-14 25.9.2 Service Planning...............................................................................................................................25-14 25.9.3 Configuration Process......................................................................................................................25-15 25.10 Task Collection.......................................................................................................................................25-16 25.11 Relevant Alarms and Events...................................................................................................................25-17 25.12 FAQs.......................................................................................................................................................25-17
26 QoS............................................................................................................................................26-1
26.1 Introduction.................................................................................................................................................26-3 26.2 Basic Concepts............................................................................................................................................26-4 26.2.1 Traffic Classification..........................................................................................................................26-5 26.2.2 CoS.....................................................................................................................................................26-5 26.2.3 CAR....................................................................................................................................................26-6 Issue 05 (2010-10-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. xvii
Contents
OptiX RTN 620 Radio Transmission System Feature Description 26.2.4 Traffic Shaping...................................................................................................................................26-7 26.2.5 Queue Scheduling..............................................................................................................................26-8 26.2.6 QoS Model.......................................................................................................................................26-11
26.3 Specifications............................................................................................................................................26-12 26.4 Reference Standards and Protocols...........................................................................................................26-14 26.5 Availability................................................................................................................................................26-14 26.6 Principles...................................................................................................................................................26-15 26.6.1 CAR..................................................................................................................................................26-16 26.6.2 Traffic Shaping.................................................................................................................................26-17 26.7 Planning Guidelines..................................................................................................................................26-18 26.8 Configuration Procedure...........................................................................................................................26-19 26.9 Configuration Example.............................................................................................................................26-20 26.9.1 Networking Diagram........................................................................................................................26-20 26.9.2 Service Planning...............................................................................................................................26-23 26.9.3 Configuration Process......................................................................................................................26-31 26.10 Task Collection.......................................................................................................................................26-38 26.11 Relevant Alarms and Events...................................................................................................................26-38 26.12 FAQs.......................................................................................................................................................26-38
27 ETH-OAM................................................................................................................................27-1
27.1 Introduction.................................................................................................................................................27-3 27.2 Basic Concepts............................................................................................................................................27-4 27.2.1 IEEE 802.1ag OAM Management.....................................................................................................27-4 27.2.2 IEEE 802.1ag OAM Operation..........................................................................................................27-7 27.2.3 IEEE 802.3ah OAM Operation..........................................................................................................27-8 27.3 Specifications............................................................................................................................................27-10 27.4 Reference Standards and Protocols...........................................................................................................27-11 27.5 Availability................................................................................................................................................27-11 27.6 Principles...................................................................................................................................................27-12 27.6.1 IEEE 802.1ag OAM.........................................................................................................................27-12 27.6.2 IEEE 802.3ah OAM.........................................................................................................................27-16 27.7 Planning Guidelines..................................................................................................................................27-25 27.8 Configuration Procedure...........................................................................................................................27-26 27.8.1 IEEE 802.1ag OAM.........................................................................................................................27-26 27.8.2 IEEE 802.3ah OAM.........................................................................................................................27-29 27.9 Configuration Example (IEEE 802.1ag OAM).........................................................................................27-30 27.9.1 Networking Diagram........................................................................................................................27-31 27.9.2 Service Planning...............................................................................................................................27-31 27.9.3 Configuration Process......................................................................................................................27-34 27.10 Configuration Example (IEEE 802.3ah OAM).......................................................................................27-36 27.10.1 Networking Diagram......................................................................................................................27-36 27.10.2 Service Planning.............................................................................................................................27-37 27.10.3 Configuration Process....................................................................................................................27-38 xviii Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 05 (2010-10-30)
Contents
27.11 Task Collection.......................................................................................................................................27-39 27.11.1 Task Collection (IEEE 802.1ag OAM)..........................................................................................27-39 27.11.2 Task Collection (IEEE 802.1ah OAM)..........................................................................................27-40 27.12 Relevant Alarms and Events...................................................................................................................27-40 27.13 FAQs.......................................................................................................................................................27-41
28 Synchronous Ethernet...........................................................................................................28-1
28.1 Introduction.................................................................................................................................................28-3 28.2 Specifications..............................................................................................................................................28-3 28.3 Reference Standards and Protocols.............................................................................................................28-4 28.4 Availability..................................................................................................................................................28-4 28.5 Principles.....................................................................................................................................................28-4 28.6 Planning Guidelines.................................................................................................................................... 28-5 28.7 Configuration Procedure.............................................................................................................................28-6 28.8 Configuration Example...............................................................................................................................28-6 28.8.1 Networking Diagram..........................................................................................................................28-6 28.8.2 Service Planning.................................................................................................................................28-7 28.8.3 Configuration Process........................................................................................................................28-7 28.9 Task Collection........................................................................................................................................... 28-8 28.10 Relevant Alarms and Events.....................................................................................................................28-8 28.11 FAQs......................................................................................................................................................... 28-8
29 Remote Monitoring................................................................................................................29-1
29.1 Introduction.................................................................................................................................................29-3 29.2 Basic Concepts............................................................................................................................................29-3 29.2.1 SNMP.................................................................................................................................................29-3 29.2.2 RMON Management Groups.............................................................................................................29-4 29.2.3 List of RMON Alarm Entries.............................................................................................................29-5 29.2.4 List of RMON Performance Entries...................................................................................................29-6 29.3 Specifications............................................................................................................................................29-10 29.4 Reference Standards and Protocols...........................................................................................................29-11 29.5 Availability................................................................................................................................................29-11 29.6 Principles...................................................................................................................................................29-12 29.7 Planning Guidelines..................................................................................................................................29-13 29.8 Configuration Procedure...........................................................................................................................29-13 29.9 Configuration Example.............................................................................................................................29-14 29.9.1 Networking Diagram........................................................................................................................29-15 29.9.2 Fault Analysis...................................................................................................................................29-15 29.9.3 Troubleshooting Flow......................................................................................................................29-15 29.10 Task Collection.......................................................................................................................................29-16 29.11 Relevant Alarms and Events...................................................................................................................29-17 29.12 FAQs.......................................................................................................................................................29-17
A Task Collection.........................................................................................................................A-1
Issue 05 (2010-10-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. xix
Contents
A.1 Managing NEs...............................................................................................................................................A-3 A.1.1 Creating NEs by Using the Search Method..........................................................................................A-3 A.1.2 Creating NEs by Using the Manual Method........................................................................................ A-5 A.1.3 Logging In to an NE.............................................................................................................................A-7 A.1.4 Configuring Logical Boards.................................................................................................................A-9 A.1.5 Changing NE IDs...............................................................................................................................A-10 A.1.6 Changing NE Names..........................................................................................................................A-11 A.1.7 Synchronizing NE Time.....................................................................................................................A-11 A.1.8 Localizing NE Time...........................................................................................................................A-17 A.2 Configuring Performance Monitoring Status of NEs..................................................................................A-19 A.3 Managing Communication..........................................................................................................................A-20 A.3.1 Setting NE Communication Parameters.............................................................................................A-21 A.3.2 Configuring DCCs..............................................................................................................................A-23 A.3.3 Configuring the Extended ECC..........................................................................................................A-25 A.3.4 Configuring DCC Transparent Transmission.....................................................................................A-27 A.3.5 Creating Static IP Routes....................................................................................................................A-29 A.3.6 Setting Parameters of the OSPF Protocol...........................................................................................A-30 A.3.7 Enabling the ARP Proxy....................................................................................................................A-31 A.3.8 Configuring the CLNS Role...............................................................................................................A-31 A.3.9 Querying OSI Tunnel.........................................................................................................................A-32 A.3.10 Querying ECC Routes......................................................................................................................A-33 A.3.11 Querying IP Routes..........................................................................................................................A-33 A.3.12 Querying OSI Routes.......................................................................................................................A-34 A.4 Configuring Service Access of NEs ...........................................................................................................A-34 A.4.1 Configuring LCT Access to NEs........................................................................................................A-34 A.4.2 Configuring Ethernet Access to NEs..................................................................................................A-35 A.4.3 Configuring Serial Interface Access to NEs.......................................................................................A-36 A.5 Managing Radio Links................................................................................................................................A-37 A.5.1 Creating an IF 1+1 Protection Group.................................................................................................A-39 A.5.2 Creating an XPIC Workgroup............................................................................................................A-42 A.5.3 Configuring the IF/ODU Information of a Radio Link......................................................................A-46 A.5.4 Setting the Hybrid/AM Attribute........................................................................................................A-51 A.5.5 Creating an N+1 Protection Group.....................................................................................................A-53 A.5.6 Creating REGs....................................................................................................................................A-55 A.5.7 Configuring the ATPC function.........................................................................................................A-57 A.5.8 Setting Parameters of IF Interfaces....................................................................................................A-60 A.5.9 Setting Parameters of ODU Interfaces...............................................................................................A-64 A.5.10 Querying ATPC Adjustment Records..............................................................................................A-67 A.5.11 Querying History Transmit Power and Receive Power ...................................................................A-68 A.5.12 Querying the AM Status...................................................................................................................A-68 A.5.13 Querying the IF 1+1 Protection Status.............................................................................................A-69 A.5.14 Querying the IF N+1 Protection Status............................................................................................A-69 xx Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 05 (2010-10-30)
Contents
A.5.15 Performing IF 1+1 Protection Switching.........................................................................................A-70 A.5.16 Performing IF N+1 Protection Switching.........................................................................................A-70 A.5.17 Starting/Stopping the N+1 Protection Protocol................................................................................A-71 A.6 Managing MSP............................................................................................................................................A-72 A.6.1 Configuring Ring MSP.......................................................................................................................A-72 A.6.2 Configuring Linear MSP....................................................................................................................A-76 A.6.3 Querying the Status of Ring MSP......................................................................................................A-80 A.6.4 Querying the Status of Linear MSP....................................................................................................A-80 A.6.5 Performing Ring MSP Switching.......................................................................................................A-81 A.6.6 Performing Linear MSP Switching....................................................................................................A-81 A.6.7 Starting/Stopping the Ring MSP Protocol..........................................................................................A-82 A.6.8 Starting/Stopping the Linear MSP Protocol.......................................................................................A-82 A.7 Managing TDM Services............................................................................................................................A-83 A.7.1 Creating Cross-Connections of Point-to-Point Services ...................................................................A-84 A.7.2 Creating Cross-Connections for SNCP Services................................................................................A-87 A.7.3 Inserting TU_AIS...............................................................................................................................A-91 A.7.4 Setting the Automatic Switching Conditions of SNCP Services ......................................................A-92 A.7.5 Deleting Cross-Connections...............................................................................................................A-94 A.7.6 Converting Normal Services into SNCP Services..............................................................................A-94 A.7.7 Converting SNCP Services to Normal Services.................................................................................A-98 A.7.8 Querying TDM Services.....................................................................................................................A-98 A.7.9 Performing SNCP Protection.............................................................................................................A-99 A.7.10 Querying the Protection Status of SNCP Services...........................................................................A-99 A.8 Managing Clocks.......................................................................................................................................A-100 A.8.1 Configuring Clock Sources..............................................................................................................A-100 A.8.2 Configuring Protection for Clock Sources.......................................................................................A-102 A.8.3 Modifying Clock Output Parameters................................................................................................A-108 A.8.4 Changing Conditions for Clock Source Switching..........................................................................A-110 A.8.5 Modifying the Recovery Parameter of the Clock Source.................................................................A-111 A.8.6 Querying the Clock Synchronization Status.....................................................................................A-112 A.9 Managing ERPS Protection.......................................................................................................................A-113 A.9.1 Creating ERPS Instances..................................................................................................................A-113 A.9.2 Setting Parameters of the Ethernet Ring Protocol............................................................................A-115 A.9.3 Querying the Status of the Ethernet Ring Protection Switching Protocol........................................A-122 A.10 Managing the STP...................................................................................................................................A-123 A.10.1 Configuring the Spanning Tree Protocol........................................................................................A-123 A.10.2 Setting the Parameters of Spanning Tree Protocol ........................................................................A-124 A.10.3 Querying the Running Information About the Spanning Tree Protocol........................................A-128 A.11 Managing the IGMP Snooping................................................................................................................A-129 A.11.1 Configuring the IGMP Snooping Protocol.....................................................................................A-129 A.11.2 Modifying the Aging Time of a Multicast Table Item...................................................................A-131 A.11.3 Querying the Running Information of the IGMP Snooping Protocol............................................A-132 Issue 05 (2010-10-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. xxi
Contents
A.12 Managing LAGs .....................................................................................................................................A-133 A.12.1 Creating a LAG..............................................................................................................................A-133 A.12.2 Setting the Port Priority..................................................................................................................A-141 A.12.3 Querying the Protocol Information of the LAG.............................................................................A-144 A.13 Managing the QoS...................................................................................................................................A-144 A.13.1 Creating a Flow..............................................................................................................................A-145 A.13.2 Creating the CAR...........................................................................................................................A-148 A.13.3 Creating the CoS.............................................................................................................................A-151 A.13.4 Binding the CAR/CoS....................................................................................................................A-154 A.13.5 Configuring the Traffic Shaping for Egress Port Queues............................................................... -155 A A.13.6 Configuring Port Shaping...............................................................................................................A-157 A.13.7 Configuring the CoS of the IFH2 Board........................................................................................A-158 A.13.8 Configuring the Queue Scheduling Mode......................................................................................A-159 A.14 Using the IEEE 802.1ag OAM ...............................................................................................................A-162 A.14.1 Creating MDs.................................................................................................................................A-163 A.14.2 Creating MAs.................................................................................................................................A-164 A.14.3 Creating MPs..................................................................................................................................A-166 A.14.4 Performing a CC Test.....................................................................................................................A-169 A.14.5 Performing an LB Check ...............................................................................................................A-169 A.14.6 Performing a Link Trace Check.....................................................................................................A-171 A.14.7 Activating the AIS..........................................................................................................................A-173 A.14.8 Performing a Ping Test ..................................................................................................................A-174 A.14.9 Performing Performance Detection................................................................................................A-176 A.15 Using the IEEE 802.3ah OAM................................................................................................................A-178 A.15.1 Enabling the OAM Auto-Discovery Function...............................................................................A-178 A.15.2 Enabling the Link Event Notification.............................................................................................A-180 A.15.3 Modifying the Parameters of the OAM Error Frame Monitoring Threshold ................................A-183 A.15.4 Performing the Remote Loopback..................................................................................................A-185 A.15.5 Enabling the Self-Loop Detection .................................................................................................A-187 A.16 Using RMON...........................................................................................................................................A-188 A.16.1 Browsing the Performance Data in the Statistics Group of an Ethernet Port.................................A-189 A.16.2 Configuring an Alarm Group for an Ethernet Port.........................................................................A-190 A.16.3 Configuring a History Control Group............................................................................................A-191 A.16.4 Browsing the Performance Data in the History Group of an Ethernet Port...................................A-192 A.17 Configuring LPT.....................................................................................................................................A-193 A.17.1 Configuring LPT for Point-to-Point Services.................................................................................A-193 A.17.2 Configuring LPT for Point-to-Multipoint Services........................................................................A-195 A.18 Configuring Ethernet Ports......................................................................................................................A-197 A.18.1 Configuring External Ethernet Ports..............................................................................................A-198 A.18.2 Configuring the Internal Port of the Ethernet Board......................................................................A-206 A.18.3 Configuring Ethernet Ports of the IFH2 Board..............................................................................A-215 A.18.4 Modifying the Type Field of Jumbo Frames..................................................................................A-217 xxii Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 05 (2010-10-30)
Contents
A.18.5 Modifying the Type Field of QinQ Frames....................................................................................A-218 A.18.6 Dynamically Increasing/Decreasing the VCTRUNK Bandwidth..................................................A-219 A.19 Configuring Ethernet Services................................................................................................................A-221 A.19.1 Creating Ethernet Private Line Services.........................................................................................A-222 A.19.2 Creating Ethernet LAN Services....................................................................................................A-227 A.19.3 Modifying the Mounted Port of a Bridge.......................................................................................A-232 A.19.4 Creating the VLAN Filtering Table...............................................................................................A-235 A.19.5 Creating QinQ Private Line Services.............................................................................................A-237 A.19.6 Creating IEEE 802.1ad Bridge-Based EVPLAN Services ............................................................A-245 A.19.7 Deleting an Ethernet Private Line Service.....................................................................................A-250 A.19.8 Creating an Ethernet LAN Service.................................................................................................A-250 A.20 Managing the MAC Address Table.........................................................................................................A-251 A.20.1 Creating a Static MAC Address Entry...........................................................................................A-251 A.20.2 Creating a Blacklist Entry of a MAC Address...............................................................................A-253 A.20.3 Setting the Aging Time of a MAC Address Table Entry...............................................................A-254 A.20.4 Querying or Deleting a Dynamic MAC Address...........................................................................A-256 A.20.5 Querying the Actual Capacity of a MAC Address Table...............................................................A-257 A.21 Testing Ethernet Services........................................................................................................................A-257 A.21.1 Testing Ethernet Services by Using the LB Function....................................................................A-258 A.21.2 Testing Ethernet Services by Using the Ping Function..................................................................A-259 A.21.3 Testing Ethernet Services by Using Laptops..................................................................................A-261
B Glossary......................................................................................................................................B-1
B.1 0-9..................................................................................................................................................................B-2 B.2 A-E.................................................................................................................................................................B-2 B.3 F-J................................................................................................................................................................B-11 B.4 K-O..............................................................................................................................................................B-16 B.5 P-T................................................................................................................................................................B-22 B.6 U-Z...............................................................................................................................................................B-30
Issue 05 (2010-10-30)
xxiii
Figures
Figures
Figure 1-1 DCN....................................................................................................................................................1-2 Figure 1-2 RS-232/Ethernet protocol converter solution.....................................................................................1-6 Figure 1-3 64k/Ethernet protocol converter solution...........................................................................................1-6 Figure 1-4 E1/Ethernet protocol converter solution (in the case that all the edge equipment is in the same domain) ...............................................................................................................................................................................1-7 Figure 1-5 E1/Ethernet protocol converter solution (in the case that all the edge equipment is in multiple domains and the PTP E1/Ethernet protocol converter is used on the NM side)..................................................................1-8 Figure 1-6 E1/Ethernet protocol converter solution (in the case that all the edge equipment is in multiple domains and the PTP E1/Ethernet protocol converter is used on the NM side)..................................................................1-8 Figure 1-7 E1/Ethernet protocol converter solution (shared E1).........................................................................1-9 Figure 1-8 E1/Ethernet protocol converter solution (shared BTS service channel)...........................................1-10 Figure 1-9 Hybrid Use Solution of Protocol Converters ...................................................................................1-11 Figure 2-1 Networking diagram of HWECC.......................................................................................................2-3 Figure 2-2 Architecture of the HW ECC protocol stack .....................................................................................2-4 Figure 2-3 Networking for the extended ECC (using a network cable)...............................................................2-7 Figure 2-4 Networking for the extended ECC (using a hub)...............................................................................2-8 Figure 2-5 Networking for the extended ECC (using network cables to connect NEs in series)........................2-8 Figure 2-6 Extended ECC network (multi-level extended ECC).......................................................................2-10 Figure 2-7 Networking example for establishing ECC routes ..........................................................................2-13 Figure 2-8 Realization principle of message transfer (HWECC).......................................................................2-15 Figure 2-9 Networking diagram of the HWECC solution.................................................................................2-21 Figure 2-10 Allocation of IDs/IP addresses for all the NEs...............................................................................2-22 Figure 3-1 Networking diagram of IP over DCC.................................................................................................3-3 Figure 3-2 IP over DCC protocol stack architecture............................................................................................3-4 Figure 3-3 Application example of the proxy ARP.............................................................................................3-6 Figure 3-4 Realization principle of message transfer (gateway mode)..............................................................3-10 Figure 3-5 Realization principle of message transfer (direct connection mode)................................................3-11 Figure 3-6 Planning Example of NE IPs and Routes on a Network That Consists Of the OptiX Equipment and Has Only One OSPF Area..........................................................................................................................................3-12 Figure 3-7 Planning Example of NE IPs and Routes on a Network That Consists Of Various Equipment and Has Only One OSPF Area..........................................................................................................................................3-13 Figure 3-8 Planning Example of NE IPs and Routes on a Network That Consists Of Various Equipment and Has Multiple OSPF Areas..........................................................................................................................................3-15 Figure 3-9 Networking diagram.........................................................................................................................3-18 Figure 3-10 Allocation of IDs/IP addresses for all the NEs...............................................................................3-19 Issue 05 (2010-10-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. xxv
Figures
OptiX RTN 620 Radio Transmission System Feature Description Figure 4-1 Networking diagram of OSI over DCC..............................................................................................4-3
Figure 4-2 OSI over DCC protocol stack architecture.........................................................................................4-4 Figure 4-3 Format of the NSAP address..............................................................................................................4-5 Figure 4-4 Layered routes of IS-IS protocol routes (L2 not consecutive)...........................................................4-6 Figure 4-5 Application example of the OSI tunnel..............................................................................................4-7 Figure 4-6 Realization principle of message transferring (gateway mode).......................................................4-11 Figure 4-7 Realization principle of message transferring (direct connection mode).........................................4-12 Figure 4-8 Networking diagram.........................................................................................................................4-16 Figure 4-9 Allocation of NE areas.....................................................................................................................4-17 Figure 5-1 DCC transparent transmission solution when the OptiX equipment is at the edge of a network (1) ...............................................................................................................................................................................5-2 Figure 5-2 DCC transparent transmission solution when the OptiX equipment is at the edge of a network (2) ...............................................................................................................................................................................5-3 Figure 5-3 DCC transparent transmission solution when the OptiX equipment is in the center of a network (1) ...............................................................................................................................................................................5-3 Figure 5-4 DCC transparent transmission solution when the OptiX equipment is in the center of a network (2) ...............................................................................................................................................................................5-4 Figure 5-5 Realization principle of the DCC transparent transmission ..............................................................5-6 Figure 5-6 Networking diagram of the DCC transparent transmission solution..................................................5-9 Figure 5-7 Allocation of IDs/IP addresses for all the NEs.................................................................................5-10 Figure 6-1 Networking example for the DCC transparent transmission through the external clock interface solution (direct access mode)..............................................................................................................................................6-3 Figure 6-2 Networking example for the DCC transparent transmission through the external clock interface solution (indirect access mode)...........................................................................................................................................6-4 Figure 6-3 Realization principle of the DCC transparent transmission through the external clock interface ...............................................................................................................................................................................6-6 Figure 6-4 Networking example for the DCC transparent transmission through the external clock interface solution ...............................................................................................................................................................................6-8 Figure 7-1 1+1 HSB protection............................................................................................................................7-3 Figure 7-2 Typical configuration of 1+1 HSB (OptiX RTN 620).......................................................................7-4 Figure 7-3 Typical configuration of 1+1 HSB (OptiX RTN 620).......................................................................7-5 Figure 7-4 1+1 HSB realization principle (before the switching, in the transmit direction).............................7-11 Figure 7-5 1+1 HSB realization principle (before the switching, in the receive direction)...............................7-12 Figure 7-6 1+1 HSB realization principle (after the switching, in the receive direction)..................................7-12 Figure 7-7 1+1 HSB realization principle (after the switching, in the transmit direction)................................7-13 Figure 7-8 1+1 HSB realization principle (before the switching, in the transmit direction).............................7-13 Figure 7-9 1+1 HSB realization principle (before the switching, in the receive direction)...............................7-14 Figure 7-10 1+1 HSB realization principle (after the switching, in the receive direction)................................7-15 Figure 7-11 1+1 HSB realization principle (after the switching, in the transmit direction)..............................7-15 Figure 7-12 1+1 HSB protection networking diagram.......................................................................................7-17 Figure 8-1 1+1 FD protection...............................................................................................................................8-3 Figure 8-2 Typical configuration 1 of 1+1 FD (OptiX RTN 620).......................................................................8-5 Figure 8-3 Typical configuration 2 of 1+1 FD (OptiX RTN 620).......................................................................8-5 Figure 8-4 Typical configuration 1 of one 1+1 FD (OptiX RTN 620)................................................................8-6 xxvi Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 05 (2010-10-30)
Figures
Figure 8-5 Typical configuration 2 of 1+1 FD (OptiX RTN 620).......................................................................8-7 Figure 8-6 1+1 FD realization principle (before the switching, in the transmit direction)................................8-13 Figure 8-7 1+1 FD realization principle (before the switching, in the receive direction)..................................8-14 Figure 8-8 1+1 FD HSB realization principle (after the switching, in the receive direction)............................8-14 Figure 8-9 1+1 FD HSM realization principle (after the switching, in the receive direction)...........................8-15 Figure 8-10 1+1 FD realization principle (before the switching, in the transmit direction)..............................8-15 Figure 8-11 1+1 FD realization principle (before the switching, in the receive direction)................................8-16 Figure 8-12 1+1 HSB realization principle (after the switching, in the transmit direction)..............................8-17 Figure 8-13 1+1 FD HSB realization principle (after the switching, in the receive direction)..........................8-18 Figure 8-14 1+1 FD HSM realization principle (after the switching, in the receive direction).........................8-19 Figure 8-15 1+1 FD protection networking diagram.........................................................................................8-21 Figure 9-1 1+1 SD protection...............................................................................................................................9-3 Figure 9-2 Typical configuration of 1+1 SD (OptiX RTN 620)..........................................................................9-5 Figure 9-3 Typical configuration of 1+1 SD (OptiX RTN 620)..........................................................................9-6 Figure 9-4 1+1 SD realization principle (before the switching, in the transmit direction)................................9-13 Figure 9-5 1+1 SD realization principle (before the switching, in the receive direction)..................................9-13 Figure 9-6 1+1 SD HSB realization principle (after the switching, in the receive direction)............................9-14 Figure 9-7 1+1 SD HSB realization principle (after the switching, in the transmit direction)..........................9-14 Figure 9-8 1+1 SD HSM realization principle (after the switching, in the receive direction)...........................9-15 Figure 9-9 1+1 SD realization principle (before the switching, in the transmit direction)................................9-15 Figure 9-10 1+1 SD realization principle (before the switching, in the receive direction)................................9-16 Figure 9-11 1+1 SD HSB realization principle (after the switching, in the receive direction)..........................9-17 Figure 9-12 1+1 SD HSB realization principle (after the switching, in the transmit direction)........................9-18 Figure 9-13 1+1 SD HSM realization principle (after the switching, in the receive direction).........................9-19 Figure 9-14 1+1 SD protection networking diagram.........................................................................................9-21 Figure 10-1 Channel configuration in ACAP mode (without the application of the XPIC technology)...........10-3 Figure 10-2 Channel configuration in CCDP mode (with the application of the XPIC technology)................10-3 Figure 10-3 Single-polarization transmission....................................................................................................10-4 Figure 10-4 CCDP transmission.........................................................................................................................10-4 Figure 10-5 Typical configuration of XPIC.......................................................................................................10-5 Figure 10-6 Typical XPIC configuration (1+1 protection configuration)..........................................................10-7 Figure 10-7 Working principle of XPIC............................................................................................................10-8 Figure 10-8 Networking diagram.....................................................................................................................10-11 Figure 10-9 Board configurations....................................................................................................................10-11 Figure 11-1 N+1 protection................................................................................................................................11-3 Figure 11-2 Typical configuration of one 2+1 protection group........................................................................11-5 Figure 11-3 Typical channel configuration of one 2+1 protection group..........................................................11-5 Figure 11-4 Typical configuration of one 3+1 protection group........................................................................11-7 Figure 11-5 Typical channel configuration of one 3+1 protection group..........................................................11-7 Figure 11-6 Working principle of 2+1 protection (before the switching)........................................................11-12 Figure 11-7 Working principle of 2+1 protection (after the switching)...........................................................11-12 Figure 11-8 Working principle of the 3+1 protection (before the switching)..................................................11-13 Issue 05 (2010-10-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. xxvii
Figures
OptiX RTN 620 Radio Transmission System Feature Description Figure 11-9 Working principle of the 3+1 protection (after the switching).....................................................11-14 Figure 11-10 Networking diagram...................................................................................................................11-18 Figure 11-11 Board configuration diagram......................................................................................................11-19 Figure 12-1 Relationship between the RSL and TSL.........................................................................................12-2 Figure 12-2 Realization principle of the ATPC.................................................................................................12-4
Figure 12-3 Networking diagram.......................................................................................................................12-7 Figure 13-1 Adaptive modulation......................................................................................................................13-3 Figure 13-2 AM switching (before the switching).............................................................................................13-5 Figure 13-3 AM switching (after the switching)................................................................................................13-6 Figure 13-4 Networking diagram of the AM function.......................................................................................13-7 Figure 14-1 Subnetwork connection protection.................................................................................................14-3 Figure 14-2 SNCP service pair...........................................................................................................................14-4 Figure 14-3 An application scenario wherein 1+1 SD and SNCP coexist.........................................................14-5 Figure 14-4 Traffic flow after an SNCP switching and a 1+1 HSB switching..................................................14-6 Figure 14-5 Traffic flow after a revertive SNCP switching...............................................................................14-6 Figure 14-6 Traffic flow after a 1+1 HSB switching when the hold-off time is set..........................................14-7 Figure 14-7 SNCP working principle (before a switching).............................................................................14-14 Figure 14-8 SNCP working principle (after a switching)................................................................................14-14 Figure 14-9 Networking diagram of an SNCP ring ........................................................................................14-17 Figure 14-10 Timeslot allocation diagram (TDM services on a TDM radio ring network) ...........................14-17 Figure 15-1 1+1 linear MSP...............................................................................................................................15-3 Figure 15-2 1:N linear MSP...............................................................................................................................15-4 Figure 15-3 Working principle of 1+1 linear MSP (before a switching).........................................................15-12 Figure 15-4 Working principle of 1+1 linear MSP (after a switching, in single-ended mode).......................15-12 Figure 15-5 Working principle of 1+1 linear MSP (after a switching, in dual-ended mode)..........................15-13 Figure 15-6 Working principle of 1:1 linear MSP (before a switching)..........................................................15-14 Figure 15-7 Working principle of 1:1 linear MSP (after a switching).............................................................15-14 Figure 15-8 Networking diagram of linear MSP .............................................................................................15-16 Figure 16-1 Two-fiber bidirectional MSP ring..................................................................................................16-4 Figure 16-2 Principle of a two-fiber bidirectional MSP ring (before switching).............................................16-11 Figure 16-3 Principle of a two-fiber bidirectional MSP ring (after switching)................................................16-11 Figure 16-4 Two-fiber bidirectional MSP ring................................................................................................16-14 Figure 17-1 Application scenario 1 of EoS........................................................................................................17-3 Figure 17-2 Application scenario 2 of EoS........................................................................................................17-4 Figure 17-3 Application scenario 1 of EoPDH..................................................................................................17-5 Figure 17-4 Application scenario 2 of EoPDH..................................................................................................17-6 Figure 17-5 Structure of the GFP frame ..........................................................................................................17-13 Figure 17-6 GFP type field format...................................................................................................................17-14 Figure 17-7 VC-3-Xv/VC-4-Xv multiframe and sequence indicator...............................................................17-17 Figure 17-8 Position of the N x 2048 kbit/s signals in the concatenation overhead........................................17-18 Figure 17-9 Capacity adjustment process (addition of a member)...................................................................17-20 Figure 17-10 Capacity adjustment process (deletion of a member).................................................................17-20 xxviii Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 05 (2010-10-30)
Figures
Figure 17-11 Capacity adjustment process (one member link restored after a failure)...................................17-21 Figure 18-1 Networking diagram of the VLAN application..............................................................................18-3 Figure 18-2 Format of a tagged frame................................................................................................................18-4 Figure 19-1 Application of QinQ in EVPL services..........................................................................................19-3 Figure 19-2 Format of the Ethernet frame with only a C-TAG.........................................................................19-4 Figure 19-3 Format of the Ethernet frame with a C-TAG and an S-TAG ........................................................19-5 Figure 19-4 Format of the Ethernet frame with only an S-TAG........................................................................19-5 Figure 19-5 EVPL (QinQ) services..................................................................................................................19-13 Figure 19-6 EVPLAN (802.1ad Bridge) Service Example..............................................................................19-14 Figure 20-1 Application of Layer 2 switching...................................................................................................20-3 Figure 20-2 802.1d bridge and 802.1q bridge....................................................................................................20-4 Figure 20-3 802.1ad bridge................................................................................................................................20-5 Figure 21-1 Implementation of ERPS................................................................................................................21-4 Figure 21-2 Protection instance of ERPS...........................................................................................................21-5 Figure 21-3 Frame format of an R-APS message..............................................................................................21-7 Figure 21-4 Frame format of the R-APS specific information...........................................................................21-7 Figure 21-5 Working principle of ERPS (in the case of a fault on a non-RPL link)....................................... 21-13 Figure 21-6 Working principle of ERPS (in the case of a fault on an RPL)....................................................21-14 Figure 21-7 Networking diagram.....................................................................................................................21-18 Figure 22-1 Networking diagram of the STP/RSTP application.......................................................................22-4 Figure 22-2 Networking diagram.....................................................................................................................22-12 Figure 23-1 Transmission of multicast packets (with the IGMP Snooping protocol disabled).........................23-3 Figure 23-2 Transmission of multicast packets (with the IGMP Snooping protocol enabled)..........................23-4 Figure 23-3 Networking diagram.....................................................................................................................23-10 Figure 24-1 Link aggregation group..................................................................................................................24-3 Figure 24-2 Application of the LACP protocol..................................................................................................24-8 Figure 24-3 LAG networking diagram.............................................................................................................24-12 Figure 25-1 Networking diagram of point-to-point LPT...................................................................................25-3 Figure 25-2 Networking diagram of point-to-multipoint LPT...........................................................................25-4 Figure 25-3 Coexisting LPT and 1+1 HSB........................................................................................................25-5 Figure 25-4 Traffic flow after LPT switching and 1+1 HSB switching............................................................25-6 Figure 25-5 Traffic flow after the revertive LPT switching...............................................................................25-6 Figure 25-6 Traffic flow after the 1+1 HSB switching when the hold-off time is set.......................................25-7 Figure 25-7 Networking diagram of LPT ........................................................................................................25-14 Figure 26-1 FIFO queue.....................................................................................................................................26-3 Figure 26-2 Queues with different priorities......................................................................................................26-3 Figure 26-3 CAR processing..............................................................................................................................26-7 Figure 26-4 Traffic shaping................................................................................................................................26-8 Figure 26-5 Queues with different priorities......................................................................................................26-8 Figure 26-6 WRR scheduling algorithm............................................................................................................26-9 Figure 26-7 SP+WRR scheduling algorithm....................................................................................................26-10 Figure 26-8 QoS processing.............................................................................................................................26-11 Issue 05 (2010-10-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. xxix
Figures
OptiX RTN 620 Radio Transmission System Feature Description Figure 26-9 Basic principle of the token bucket algorithm..............................................................................26-16
Figure 26-10 Basic principle of the algorithm that is used by the CAR..........................................................26-17 Figure 26-11 Basic principle of the algorithm that is used by the traffic shaping...........................................26-18 Figure 26-12 Networking diagram (EPVL service based on the VLAN)........................................................26-20 Figure 27-1 ETH-OAM solution........................................................................................................................27-3 Figure 27-2 Logical diagram of MD layers........................................................................................................27-6 Figure 27-3 IEEE 802.1ag OAMPDU.............................................................................................................27-12 Figure 27-4 CC diagram...................................................................................................................................27-14 Figure 27-5 LB test diagram............................................................................................................................27-14 Figure 27-6 LT test diagram.............................................................................................................................27-15 Figure 27-7 IEEE 802.3ah OAMPDU.............................................................................................................27-17 Figure 27-8 Packet format of the information OAMPDU...............................................................................27-19 Figure 27-9 Packet format of the event notification OAMPDU......................................................................27-23 Figure 27-10 Packet format of the loopback control OAMPDU.....................................................................27-24 Figure 27-11 Networking diagram of IEEE 802.1ag OAM.............................................................................27-31 Figure 27-12 Information about the MPs that belong to different VLANs......................................................27-32 Figure 27-13 Networking diagram of IEEE 802.3ah OAM.............................................................................27-37 Figure 28-1 Application of synchronous Ethernet in a wireless access network...............................................28-3 Figure 28-2 Realization principle of synchronous Ethernet ..............................................................................28-5 Figure 28-3 Networking diagram of synchronous Ethernet...............................................................................28-7 Figure 28-4 Networking diagram.......................................................................................................................28-7 Figure 29-1 Networking diagram.....................................................................................................................29-15 Figure A-1 Networking diagram for testing Ethernet services........................................................................A-258 Figure A-2 Networking diagram for testing Ethernet services........................................................................A-260 Figure A-3 Networking diagram for testing Ethernet services........................................................................A-261
xxx
Issue 05 (2010-10-30)
Tables
Tables
Table 2-1 Specifications of HWECC.................................................................................................................2-11 Table 2-2 Hardware and version support...........................................................................................................2-12 Table 2-3 Configuration flow for the HWECC solution....................................................................................2-18 Table 3-1 Specifications of IP over DCC.............................................................................................................3-8 Table 3-2 Hardware and version support.............................................................................................................3-9 Table 3-3 Configuration flow for the IP over DCC solution..............................................................................3-16 Table 4-1 Specifications of OSI over DCC..........................................................................................................4-9 Table 4-2 Hardware and version support...........................................................................................................4-10 Table 4-3 Configuration flow for the OSI over DCC solution...........................................................................4-13 Table 5-1 Specifications of DCC transparent transmission..................................................................................5-4 Table 5-2 Hardware and version support.............................................................................................................5-5 Table 5-3 Configuration flow for the DCC transparent transmission solution....................................................5-7 Table 6-1 Specifications of DCC transparent transmission through the external clock interface........................6-4 Table 6-2 Hardware and version support.............................................................................................................6-5 Table 6-3 Procedure for configuring the solution of transparently transmitting DCCs through the external clock interface.................................................................................................................................................................6-7 Table 7-1 Trigger conditions of the 1+1 HSB switching ....................................................................................7-6 Table 7-2 Trigger conditions of the automatic 1+1 HSB switching.....................................................................7-9 Table 7-3 Specifications of 1+1 HSB.................................................................................................................7-10 Table 7-4 Hardware and version support...........................................................................................................7-10 Table 7-5 Configuration procedure of 1+1 HSB................................................................................................7-16 Table 7-6 IF planning information.....................................................................................................................7-18 Table 7-7 RF planning information....................................................................................................................7-18 Table 8-1 Trigger conditions of the 1+1 FD HSB switching...............................................................................8-8 Table 8-2 Trigger conditions of the automatic HSB switching............................................................................8-9 Table 8-3 Trigger conditions of the automatic HSM switching.........................................................................8-10 Table 8-4 Specifications of 1+1 FD...................................................................................................................8-11 Table 8-5 Hardware and version support...........................................................................................................8-12 Table 8-6 Configuration procedure of 1+1 FD...................................................................................................8-20 Table 8-7 IF planning information.....................................................................................................................8-21 Table 8-8 RF planning information....................................................................................................................8-22 Table 9-1 Trigger conditions of the 1+1 SD HSB switching...............................................................................9-7 Table 9-2 Trigger conditions of the automatic HSB switching............................................................................9-9 Table 9-3 Trigger conditions of the automatic HSM switching.........................................................................9-10 Issue 05 (2010-10-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. xxxi
Tables
OptiX RTN 620 Radio Transmission System Feature Description Table 9-4 Specifications of 1+1 SD...................................................................................................................9-11 Table 9-5 Hardware and version support...........................................................................................................9-12 Table 9-6 Configuration procedure of 1+1 SD...................................................................................................9-20 Table 9-7 IF planning information.....................................................................................................................9-21 Table 9-8 RF planning information....................................................................................................................9-22 Table 10-1 Specifications of XPIC.....................................................................................................................10-6 Table 10-2 Hardware and version support.........................................................................................................10-6 Table 10-3 Procedure for configuring XPIC links.............................................................................................10-9 Table 10-4 Basic information about radio links...............................................................................................10-12 Table 10-5 Power and ATPC information........................................................................................................10-13 Table 10-6 Configuration information about 1+1 HSB protection groups......................................................10-13 Table 10-7 Configuration information about XPIC.........................................................................................10-14 Table 11-1 Switching conditions of the N+1 protection....................................................................................11-8 Table 11-2 Specifications of N+1 protection...................................................................................................11-10 Table 11-3 Hardware and version support.......................................................................................................11-11 Table 11-4 Configuration procedure of 2+1 protection....................................................................................11-16 Table 11-5 Configuration procedure of 3+1 protection....................................................................................11-16 Table 11-6 Basic information about radio links...............................................................................................11-20 Table 11-7 Power and ATPC information........................................................................................................11-20 Table 11-8 Information about N+1 (N = 3) protection.....................................................................................11-21 Table 11-9 Cross-connect configuration information about the primary NE...................................................11-21 Table 11-10 REG configuration information about the secondary NE............................................................11-22 Table 11-11 Cross-connect configuration information about the primary NE.................................................11-24 Table 12-1 Specifications of ATPC....................................................................................................................12-3 Table 12-2 Hardware and version support.........................................................................................................12-3 Table 12-3 Configuration procedure of ATPC...................................................................................................12-6 Table 12-4 ATPC information............................................................................................................................12-8 Table 13-1 Specifications of AM.......................................................................................................................13-3 Table 13-2 Hardware and version support.........................................................................................................13-4 Table 13-3 Configuration procedure of AM.......................................................................................................13-7 Table 13-4 AM information...............................................................................................................................13-8 Table 14-1 SNCP switching conditions..............................................................................................................14-7 Table 14-2 Trigger conditions of an automatic SNCP switching (VC-4 services)............................................14-9 Table 14-3 Trigger conditions of an automatic SNCP switching (VC-3/VC-12 services)..............................14-10 Table 14-4 Trigger conditions of an automatic SNCP switching (E1 services transmitted over the Hybrid microwave)........................................................................................................................................................14-11 Table 14-5 Specifications of SNCP..................................................................................................................14-12 Table 14-6 Hardware and version support.......................................................................................................14-13 Table 14-7 Procedure for configuring SNCP services.....................................................................................14-15 Table 14-8 SNCP..............................................................................................................................................14-19 Table 15-1 Meanings of K bytes (linear MSP)...................................................................................................15-6 Table 15-2 Bridge request code..........................................................................................................................15-6 Table 15-3 Trigger conditions of a linear MSP switching.................................................................................15-8
xxxii
Issue 05 (2010-10-30)
Tables
Table 15-4 Specifications of linear MSP..........................................................................................................15-10 Table 15-5 Configuration procedure for a linear MSP service.........................................................................15-15 Table 15-6 Linear MSP....................................................................................................................................15-16 Table 16-1 Meanings of byte K (two-fiber bidirectional ring MSP)..................................................................16-5 Table 16-2 Bridging request code......................................................................................................................16-6 Table 16-3 Switching conditions of two-fiber bidirectional ring MSP..............................................................16-7 Table 16-4 Specifications of two-fiber bidirectional ring MSP.........................................................................16-9 Table 16-5 Hardware and version support.......................................................................................................16-10 Table 16-6 Configuration procedure for a ring MSP service...........................................................................16-13 Table 16-7 Information about ring MSP..........................................................................................................16-14 Table 17-1 Specifications of EoS/EoPDH..........................................................................................................17-9 Table 17-2 Hardware and version support (EoS).............................................................................................17-11 Table 17-3 Hardware and version support (EoPDH).......................................................................................17-11 Table 17-4 UPI values of the client management frame..................................................................................17-15 Table 17-5 LCAS CTRL words........................................................................................................................17-19 Table 17-6 Configuration procedure of EoS....................................................................................................17-24 Table 17-7 Configuration procedure of EoPDH...............................................................................................17-25 Table 18-1 Processing of data frames based on different TAG attributes..........................................................18-5 Table 18-2 Specifications of VLANs.................................................................................................................18-6 Table 18-3 Hardware and version support.........................................................................................................18-7 Table 18-4 Procedures for configuring VLAN-based EVPL services...............................................................18-9 Table 18-5 Procedure for configuring IEEE 802.1q bridge-based EVPLAN services....................................18-15 Table 19-1 Private line services between C-Aware ports...................................................................................19-7 Table 19-2 Private line services between a C-aware port and an S-aware port.................................................19-7 Table 19-3 Private line services between S-Aware ports...................................................................................19-8 Table 19-4 VLAN tag operations of C-Aware ports........................................................................................19-10 Table 19-5 VLAN tag operations of S-Aware ports.........................................................................................19-11 Table 19-6 Specifications of QinQ...................................................................................................................19-11 Table 19-7 Hardware and version support.......................................................................................................19-13 Table 19-8 Procedures for configuring QinQ-based EVPL services................................................................19-17 Table 19-9 Procedure for configuring IEEE 802.1ad bridge-based EVPLAN services...................................19-23 Table 20-1 List of bridges..................................................................................................................................20-5 Table 20-2 Specifications of Layer 2 switching.................................................................................................20-7 Table 20-3 Hardware and version support.........................................................................................................20-8 Table 20-4 Procedure for configuring IEEE 802.1d bridge-based EPLAN services.......................................20-11 Table 20-5 Procedure for configuring IEEE 802.1q bridge-based EVPLAN services....................................20-18 Table 20-6 Procedure for configuring IEEE 802.1ad bridge-based EVPLAN services...................................20-25 Table 21-1 Description of each field in the R-APS specific information...........................................................21-7 Table 21-2 Trigger conditions of ERPS.............................................................................................................21-9 Table 21-3 Specifications of ERPS..................................................................................................................21-11 Table 21-4 Hardware and version support.......................................................................................................21-12 Table 21-5 Procedure for configuring ERPS....................................................................................................21-17 Issue 05 (2010-10-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. xxxiii
Tables
OptiX RTN 620 Radio Transmission System Feature Description Table 21-6 Configuration information about the ERPS protection instance....................................................21-18 Table 21-7 Configuration information about the ERPS protocol parameters..................................................21-19 Table 22-1 Specifications of STP/RSTP............................................................................................................22-7 Table 22-2 Hardware and version support.........................................................................................................22-8 Table 22-3 Procedure for configuring the STP/RSTP......................................................................................22-11 Table 22-4 Protocol information......................................................................................................................22-12 Table 22-5 Information about bridge parameters.............................................................................................22-13 Table 22-6 Information about port parameters.................................................................................................22-13 Table 23-1 Specifications of IGMP Snooping...................................................................................................23-5 Table 23-2 Hardware and version support.........................................................................................................23-6 Table 23-3 Procedure for configuring IGMP Snooping.....................................................................................23-9 Table 24-1 Switching conditions........................................................................................................................24-5 Table 24-2 Specifications of LAGs....................................................................................................................24-6 Table 24-3 Hardware and version support.........................................................................................................24-7 Table 24-4 Procedure for configuring a LAG connected to the customer equipment......................................24-10 Table 24-5 Procedure for configuring a LAG connected to the IF board in 1+1 protection configuration ...........................................................................................................................................................................24-11 Table 24-6 LAG information............................................................................................................................24-12 Table 25-1 Specifications of LPT.......................................................................................................................25-7 Table 25-2 Hardware and version support.........................................................................................................25-8 Table 25-3 Procedure for configuring LPT for Point-to-Point Services..........................................................25-13 Table 25-4 Procedure for configuring LPT for Point-to-Multipoint Services..................................................25-13 Table 25-5 LPT configuration information of NE1..........................................................................................25-15 Table 25-6 LPT configuration information of NE2..........................................................................................25-15 Table 25-7 LPT configuration information of NE3..........................................................................................25-15 Table 26-1 Specifications of QoS.....................................................................................................................26-12 Table 26-2 Hardware and version support (QoS).............................................................................................26-15 Table 26-3 Procedure for configuring QoS for the EMS6 and EFP6 boards...................................................26-19 Table 26-4 Procedure for configuring QoS for the IFH2 board.......................................................................26-20 Table 26-5 QoS requirement............................................................................................................................26-21 Table 26-6 Connections of Ethernet links (NE1).............................................................................................26-21 Table 26-7 Connections of Ethernet links (NE2).............................................................................................26-21 Table 26-8 Connections of Ethernet links (NE3).............................................................................................26-22 Table 26-9 Connections of Ethernet links (NE4).............................................................................................26-22 Table 26-10 Connections of Ethernet links (NE5)...........................................................................................26-23 Table 26-11 Connections of Ethernet links (NE6)...........................................................................................26-23 Table 26-12 Information about the VLAN-based EVPL service (NE1)..........................................................26-23 Table 26-13 Information about the VLAN-based EVPL service (NE2)..........................................................26-24 Table 26-14 Information about the VLAN-based EVPL service (NE3)..........................................................26-24 Table 26-15 Information about the VLAN-based EVPL service (NE4)..........................................................26-25 Table 26-16 Information about VLAN-based EVPL service (NE5)................................................................26-25 Table 26-17 Flow (NE1)...................................................................................................................................26-26 Table 26-18 Flow (NE2)...................................................................................................................................26-26
xxxiv
Issue 05 (2010-10-30)
Tables
Table 26-19 Flow (NE3)...................................................................................................................................26-26 Table 26-20 Flow (NE4)...................................................................................................................................26-27 Table 26-21 Flow (NE5)...................................................................................................................................26-27 Table 26-22 CAR (services accessed from BTS1 to NE2)..............................................................................26-27 Table 26-23 CAR (services accessed from BTS2 and BTS3 to NE4).............................................................26-28 Table 26-24 CAR (services accessed from BTS4 to NE5)..............................................................................26-28 Table 26-25 CoS attributes of the EMS6 boards..............................................................................................26-28 Table 26-26 CoS parameters of the EMS6 boards...........................................................................................26-29 Table 26-27 CoS operations on the IFH2 board...............................................................................................26-29 Table 26-28 Queue scheduling on the EMS6 board.........................................................................................26-30 Table 27-1 IEEE 802.1ag ETH-OAM operations and application scenarios.....................................................27-7 Table 27-2 IEEE 802.3ah ETH-OAM operations and application scenarios.....................................................27-9 Table 27-3 Specifications of ETH-OAM (IEEE 802.1ag)...............................................................................27-10 Table 27-4 Specifications of ETH-OAM (IEEE 802.3ah)...............................................................................27-10 Table 27-5 Hardware and version support.......................................................................................................27-11 Table 27-6 Mapping relationships between OAM Type values and types of OAM packets (in the case of a standard MP)....................................................................................................................................................................27-13 Table 27-7 Mapping relationships between Code values and OAM packet types...........................................27-17 Table 27-8 Details of an OAM configuration byte...........................................................................................27-20 Table 27-9 Mapping relationships between OAM working modes and OAM capabilities.............................27-21 Table 27-10 Procedure for configuring IEEE 802.1ag OAM...........................................................................27-27 Table 27-11 Procedure for configuring IEEE 802.3ah OAM...........................................................................27-29 Table 27-12 Information about the MD...........................................................................................................27-32 Table 27-13 Information about the MA...........................................................................................................27-32 Table 27-14 Information about the MEP..........................................................................................................27-33 Table 27-15 Information about the MIP...........................................................................................................27-33 Table 27-16 Information about the LT test......................................................................................................27-33 Table 27-17 OAM parameters..........................................................................................................................27-37 Table 27-18 Error frame monitoring information in OAM..............................................................................27-38 Table 28-1 Specifications of synchronous Ethernet...........................................................................................28-3 Table 28-2 Hardware and version support.........................................................................................................28-4 Table 28-3 Configuration procedure for synchronous Ethernet.........................................................................28-6 Table 29-1 List of RMON alarm entries............................................................................................................29-6 Table 29-2 List of RMON performance entries.................................................................................................29-6 Table 29-3 Specifications of RMON................................................................................................................29-10 Table 29-4 Hardware and version support.......................................................................................................29-11 Table 29-5 Configuration procedure of RMON...............................................................................................29-14 Table A-1 Parameters..........................................................................................................................................A-8 Table A-2 Parameters........................................................................................................................................A-10 Table A-3 Parameters........................................................................................................................................A-13 Table A-4 Parameters of the standard NTP server............................................................................................A-15 Table A-5 Parameters of the access control rights............................................................................................A-16 Table A-6 Parameters of the NTP key management.........................................................................................A-16 Issue 05 (2010-10-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. xxxv
Tables
OptiX RTN 620 Radio Transmission System Feature Description Table A-7 Parameters........................................................................................................................................A-18 Table A-8 Parameters........................................................................................................................................A-22 Table A-9 Parameters........................................................................................................................................A-24 Table A-10 Parameters......................................................................................................................................A-26 Table A-11 Parameters......................................................................................................................................A-28 Table A-12 Parameters......................................................................................................................................A-30 Table A-13 Parameters......................................................................................................................................A-32 Table A-14 Parameters......................................................................................................................................A-37 Table A-15 Parameters......................................................................................................................................A-40 Table A-16 Parameters......................................................................................................................................A-43 Table A-17 Parameters......................................................................................................................................A-47 Table A-18 Parameters......................................................................................................................................A-52 Table A-19 Parameters......................................................................................................................................A-55 Table A-20 Parameters......................................................................................................................................A-57 Table A-21 Parameters......................................................................................................................................A-58 Table A-22 Parameters......................................................................................................................................A-61 Table A-23 Parameters......................................................................................................................................A-65 Table A-24 Parameters......................................................................................................................................A-74 Table A-25 Parameters......................................................................................................................................A-77 Table A-26 Parameters......................................................................................................................................A-85 Table A-27 Parameters......................................................................................................................................A-88 Table A-28 Parameters......................................................................................................................................A-93 Table A-29 Parameters......................................................................................................................................A-96 Table A-30 Parameter Description: Clock Subnet Setting_Clock Subnet......................................................A-105 Table A-31 Parameter Description: Clock Subnet Setting_Clock Quality ....................................................A-106 Table A-32 Parameter Description: Clock Subset Setting_SSM Output Control ..........................................A-108 Table A-33 Parameter Description: Clock Subset Setting_Clock ID Enabling Status ..................................A-108 Table A-34 Parameters....................................................................................................................................A-112 Table A-35 Parameters....................................................................................................................................A-114 Table A-36 Parameters....................................................................................................................................A-116 Table A-37 Parameters....................................................................................................................................A-164 Table A-38 Parameters....................................................................................................................................A-165 Table A-39 Parameters....................................................................................................................................A-167 Table A-40 Parameters....................................................................................................................................A-170 Table A-41 Parameters....................................................................................................................................A-172 Table A-42 Parameters....................................................................................................................................A-173 Table A-43 Parameters....................................................................................................................................A-175 Table A-44 Parameters....................................................................................................................................A-177 Table A-45 Parameters....................................................................................................................................A-179 Table A-46 Parameters....................................................................................................................................A-182 Table A-47 Parameters....................................................................................................................................A-184 Table A-48 Parameters....................................................................................................................................A-186
xxxvi
Issue 05 (2010-10-30)
Tables
Table A-49 Parameters....................................................................................................................................A-188 Table A-50 Parameters....................................................................................................................................A-189 Table A-51 Parameters....................................................................................................................................A-190 Table A-52 Parameters....................................................................................................................................A-191 Table A-53 Parameters....................................................................................................................................A-192 Table A-54 Parameters of the point-to-point LPT...........................................................................................A-194 Table A-55 Parameters of aggregation points.................................................................................................A-196 Table A-56 Parameters of access points..........................................................................................................A-197 Table A-57 Parameters for the basic attributes................................................................................................A-199 Table A-58 Parameters for flow control..........................................................................................................A-202 Table A-59 Parameters for the TAG attributes................................................................................................A-203 Table A-60 Parameters for the network attributes...........................................................................................A-204 Table A-61 Parameters for the advanced attributes.........................................................................................A-205 Table A-62 Methods used by ports to process data frames.............................................................................A-206 Table A-63 Parameters for the TAG attributes................................................................................................A-209 Table A-64 Parameters for encapsulation or mapping....................................................................................A-210 Table A-65 Parameters for the network attributes...........................................................................................A-211 Table A-66 Parameters for the LCAS.............................................................................................................A-212 Table A-67 Parameters for bound paths..........................................................................................................A-213 Table A-68 Parameters for the advanced attributes.........................................................................................A-214 Table A-69 Methods used by ports to process data frames.............................................................................A-214 Table A-70 Parameters for the basic attributes................................................................................................A-216 Table A-71 Parameters for flow control..........................................................................................................A-216 Table A-72 Parameters on the main interface.................................................................................................A-224 Table A-73 Parameters of port attributes.........................................................................................................A-226 Table A-74 Parameters of bound paths...........................................................................................................A-227 Table A-75 Parameters on the main interface.................................................................................................A-230 Table A-76 Parameters of service mounting...................................................................................................A-231 Table A-77 Parameters of bound paths...........................................................................................................A-231 Table A-78 Methods used by ports to process data frames.............................................................................A-235 Table A-79 Parameters on the main interface.................................................................................................A-239 Table A-80 Parameters of port attributes.........................................................................................................A-243 Table A-81 Parameters of bound paths...........................................................................................................A-244 Table A-82 Parameters on the main interface.................................................................................................A-247 Table A-83 Parameters of service mounting...................................................................................................A-248 Table A-84 Parameters of bound paths...........................................................................................................A-249
Issue 05 (2010-10-30)
xxxvii
1 Introduction to the DCN
1
About This Chapter
Introduction to the DCN
The network management system (NMS) establishes communication with a transmission network element (NE) through the data communication network (DCN) to manage and maintain the NE. 1.1 Composition of the DCN In a DCN, both the NMS and NE are nodes of the DCN. The DCN between the NMS and NEs is called the external DCN, and the DCN between NEs is called the internal DCN. 1.2 Huawei DCN Solution The OptiX transmission equipment of Huawei provides multiple DCN solutions for a variety of networks that comprise the transmission equipment. 1.3 Protocol Converter Solution To use the protocol converter solution, the corresponding protocol converter is selected according to the bearing capacity of the equipment in the center of the network.
Issue 05 (2010-10-30)
1-1
1.1 Composition of the DCN

In a DCN, both the NMS and NE are nodes of the DCN. The DCN between the NMS and NEs is called the external DCN, and the DCN between NEs is called the internal DCN. Figure 1-1 DCN
NMS
External DCN
Internal DCN
Router
LAN switch
OptiX optical transmission equipment
OptiX radio transmission equipment
External DCN
In an actual network, the NMS 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 comprises the data communication equipment such as LAN switches and routers is required to connect the NMS 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.
1-2 Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 05 (2010-10-30)
Internal DCN
In an internal DCN, an NE uses the DCC bytes of the overhead as the physical channels of the DCN. l l l l l l When the D1 byte of the PDH microwave overhead is used, a bandwidth of 64 kbit/s can be provided for the DCN. When D1-D3 bytes of the PDH microwave overhead are used, a bandwidth of 192 kbit/s can be provided for the DCN. When D1-D3 bytes of the SDH regenerator section overhead (RSOH) are used, a bandwidth of 192 kbit/s can be provided for the DCN. When D4-D12 bytes of the SDH multiplex section overhead (MSOH) are used, a bandwidth of 576 kbit/s can be provided for the DCN. When D1-D12 bytes of the SDH section overhead are used, a bandwidth of 768 kbit/s can be provided for the DCN. When D1-D3 bytes of the Hybrid microwave overhead are used, a bandwidth of 192 kbit/ s can be provided for the DCN.
NOTE
l In the PDH microwave frame or Hybrid microwave frame, the DCC bytes are defined by Huawei. l In the SDH microwave frame, the defined DCC bytes comply with the SDH overhead specifications.
1.2 Huawei DCN Solution

The OptiX transmission equipment of Huawei provides multiple DCN solutions for a variety of networks that comprise the transmission equipment.
HW ECC Solution
When the network comprises only the OptiX transmission equipment, the HW ECC solution is the first choice. With the HW ECC solution, NEs transmit the data that supports the HW ECC protocol through DCCs. It is easy to configure the solution and convenient to apply the solution. The network management problem cannot be solved when the network comprises the OptiX equipment and the third-party equipment because the HW ECC protocol is a private protocol. For details on the HW ECC solution, see 2 HWECC Solution.
IP over DCC Solution

When the network comprises the OptiX transmission equipment and the third-party equipment that supports the IP over DCC function, the IP over DCC solution is the first choice. The IP over DCC solution can also be applied when the network comprises only the OptiX transmission equipment. With the IP over DCC solution, NEs transmit the data that supports the TCP/IP protocol through DCCs. As the TCP/IP is a standard protocol stack, the network management problem is solved when the network comprises the OptiX equipment and the third-party equipment. The configuration, however, is more complicated than the HW ECC solution. For details on the IP over DCC solution, see 3 IP over DCC Solution.
Issue 05 (2010-10-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 1-3

NOTE
If the equipment located in the center of the network supports the IP over DCC function and the third-party equipment located at the edge of the network supports NM message transmission through the Ethernet, the IP over DCC solution can be used to realize the DCN communication of the equipment at the edge of a network.
OSI over DCC Solution

When the network comprises the OptiX transmission equipment and the third-party equipment that supports the OSI over DCC function, the OSI over DCC solution is the first choice. With the OSI over DCC solution, NEs transmit the data that supports the open system interconnection (OSI) protocol through DCCs. As the OSI protocol is a standard protocol, the network management problem is solved when the network comprises the OptiX equipment and the third-party equipment. The configuration, however, is more complicated than both the HW ECC solution and the IP over DCC solution. For details on the OSI over DCC solution, see 4 OSI over DCC Solution.
NOTE
If the equipment located in the center of the network supports the OSI over DCC function and the third-party equipment located at the edge of the network supports NM message transmission through the Ethernet, the OSI over DCC solution can be used to realize the DCN communication of the equipment at the edge of a network.
DCC Transparent Transmission Solution

When the network comprises the OptiX transmission equipment and the third-party SDH equipment that does not support the IP over DCC function or the OSI over DCC function, use DCC bytes to transparently transmit data. With the DCC transparent transmission solution, vendors use different DCCs to transmit data. Hence, the network management problem is solved when the equipment of the vendor is used together with the third-party equipment to form a network. There is a limitation, however, because the NMS of a vendor can manage only the NEs of the same vendor. For details on the DCC transparent transmission solution, see 5 DCC Transparent Transmission Solution.
DCC Transparent Transmission Through the External Clock Interface Solution

When a PDH network 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. With the DCC transparent transmission through the external clock interface solution, DCC bytes are loaded into the timeslots of the E1 provided by the external clock interface and the thirdparty equipment transmits the E1 as an ordinary E1 service. When this solution is adopted, the transmission bandwidth of an E1 service needs to be occupied and the NEs connected to Huawei's NMS must be the OptiX equipment. For details on the DCC transparent transmission through the external clock interface solution, see 5 DCC Transparent Transmission Solution.
Protocol Converter Solution

This solution is adopted when none of the preceding solutions can be used to realize the NM message transmission.
With this solution, on one side of the equipment at the edge of the network or the NM side of the equipment at the edge of the management network, the protocol converter is used to convert the NM message carried by the Ethernet into a service that can be transparently transmitted by the equipment in the center of the network, such as the RS-232 asynchronous data service, 64 kbit/s synchronous data service, Nx64 bit/s data service (this service can be carried by E1). In this manner, the DCN communication of the equipment at the edge of the network is realized. This solution is widely applicable but requires the protocol converter, which increases the cost. For details on the protocol converter solution, see section 1.3 Protocol Converter Solution.
NOTE
When the equipment at the edge of the network carries the NM message by using the RS-232 asynchronous data service, the protocol converter solution can be used for the DCN communication. By using the protocol converters of other types, the asynchronous data service can be converted into a service that can be transparently transmitted by the equipment in the center of the network, such as the 64 kbit/s synchronous data service and Nx64 bit/s data service.
1.3 Protocol Converter Solution

To use the protocol converter solution, the corresponding protocol converter is selected according to the bearing capacity of the equipment in the center of the network.
NOTE
The following part considers the situation that the third-party equipment is the central equipment and the OptiX RTN equipment is the edge equipment of the network as an example. In fact, if the OptiX RTN equipment is the central equipment of the network, the protocol converter solution can also be used to provide the DCN for the third-party equipment.
Principle for Selecting a Protocol Converter

l When the equipment in the center of the network supports the RS-232 asynchronous data service transmission, the RS-232/Ethernet protocol converter is the first choice for realizing the DCN communication. When the equipment in the center of the network supports the 64 kbit/s synchronous data service transmission, the 64k/Ethernet protocol converter is the first choice for realizing the DCN communication. When the equipment in the center of the network does not support the synchronous data service or asynchronous data service transmission, the E1/Ethernet protocol converter is the first choice for realizing the DCN communication. When the equipment at the edge of the network belongs to multiple domains and the number of synchronous/asynchronous services of the equipment in the center of the network cannot support the DCN transmission of the equipment at the edge of the network in each domain, a solution of using multiple protocol converters is adopted for DCN transmission.
NOTE
The principle for selecting a protocol converter is based on the situation that the DCN communication needs to be provided for only a small amount of edge equipment. If there is a large amount of edge equipment, whether the bandwidth provided by the protocol converter can meet the requirement of the communication between the NE and the NMS needs to be considered. In this case, it is recommended that you use the E1/Ethernet protocol converter.
RS-232/Ethernet Protocol Converter Solution

With this solution, the edge equipment side and the NM side of the edge equipment converts the NM message carried by the Ethernet into the RS-232 asynchronous data service by using the
RS-232/Ethernet protocol converter, and the central equipment transparently transmits the data service, as shown in Figure 1-2. In this manner, the DCN transmission of the edge equipment is realized. With regard to the edge equipment, the RS-232/Ethernet protocol converter and the central equipment are external DCN, which realizes the DCN communication between the NMS and the gateway NE. Figure 1-2 RS-232/Ethernet protocol converter solution
NMS
RS-232/Ethernet Converter
Central netw ork
RS-232/Ethernet Converter
Edge netw ork
Ethernet link
RS-232 link
Radio link
NOTE
The OptiX RTN 620 supports direct NMS access through the RS-232 serial port. Hence, when the OptiX RTN 620 is the edge equipment and the central equipment supports the RS-232 asynchronous data service transmission, the protocol converter is not necessary. Instead, the serial ports of the NMS and the NE can be directly connected to the asynchronous data interface of the central equipment.
64k/Ethernet Protocol Converter Solution

With this solution, the edge equipment side and the NM side of the edge equipment converts the NM message carried by the Ethernet into the 64 kbit/s synchronous data service in compliance with ITU-T G.703 by using the 64k/Ethernet protocol converter, and the central equipment transparently transmits the data service, as shown in Figure 1-3. In this manner, the DCN transmission of the edge equipment is realized. To the edge equipment, the 64k/Ethernet protocol converter and the central equipment function as external DCN, which realizes the DCN communication between the NMS and the gateway NE. Figure 1-3 64k/Ethernet protocol converter solution
NMS
64k/Ethernet Converter
Central netw ork
Edge netw ork
Ethernet link
64kbps link
Radio link
1-6
Issue 05 (2010-10-30)
E1/Ethernet Protocol Converter Solution

With this solution, the edge equipment side and the NM side of the edge equipment converts the NM message carried by the Ethernet into the Nx64 kbit/s (N = 1-32) data service that can be transmitted by E1 by using the E1/Ethernet protocol converter, and the central equipment transparently transmits the E1 service. In this manner, the DCN transmission of the edge equipment is realized. To the edge equipment, the E1/Ethernet protocol converter and the central equipment are external DCN, which realizes the DCN communication between the NMS and the gateway NE.
NOTE
If the central equipment supports the bypass E1 service, the bypass E1 is preferred to transmit the NM message of the edge equipment.
E1/Ethernet protocol converters are classified into four types: point-to-point, concentrated, serially connected, and channelized. When all the edge equipment is in the same domain, the point-to-point E1/Ethernet protocol converter can be used on the NM side and the edge equipment side to establish a DCN channel, as shown in Figure 1-4. When all the edge equipment is in multiple domains, the point-to-point E1/Ethernet protocol converter can be used to create DCN channels, and then the LAN switch aggregates the services to the NMS, as shown in Figure 1-5. If the required DCN channels are more than five, the concentrated E1/Ethernet protocol converter is used rather than the point-topoint E1/Ethernet protocol converter on the NM side, as shown in Figure 1-6. Figure 1-4 E1/Ethernet protocol converter solution (in the case that all the edge equipment is in the same domain)
n x 64kbps
n x 64kbps
NMS
Central network E1/Ethernet E1/Ethernet Converter (PTP type) Converter (PTP type) Edge network
Ethernet link
E1 link
Radio link
Issue 05 (2010-10-30)
1-7
Figure 1-5 E1/Ethernet protocol converter solution (in the case that all the edge equipment is in multiple domains and the PTP E1/Ethernet protocol converter is used on the NM side)
Edge netw ork1
NMS E1/Ethernet Converter 1 (PTP type)
E1/Ethernet Converter 1 (PTP type)
LAN sw itch E1/Ethernet Converter n (PTP type)
Edge netw ork n
Central netw ork
E1/Ethernet Converter n (PTP type)
Ethernet link
E1
Radio link
Figure 1-6 E1/Ethernet protocol converter solution (in the case that all the edge equipment is in multiple domains and the PTP E1/Ethernet protocol converter is used on the NM side)
Edge network1
NM S
E1/Ethernet Converter 1 (PTP type)
LAN switch E1/Ethernet Converter (concentrate type)
Edge network n
Central network
E1/Ethernet Converter n (PTP type)
Ethernet link
E1
Radio link
The E1/Ethernet protocol solution is adopted in two special scenarios: shared E1 and shared BTS service channel.
Shared E1 When the edge equipment is large in scale and the network needs to be divided into several sub-networks, the shared E1 solution can be adopted. With this solution, the serially connected E1/Ethernet protocol converter on the gateway NE side in each sub-network is used to aggregate Nx64 kbit/s synchronous data services for DCN communication; the channelized and concentrated E1/Ethernet protocol converter on the NM side of the edge equipment is used to demultiplex the Nx64 kbit/s synchronous data services in the E1 and to convert these services into corresponding Ethernet data, as shown in Figure 1-7. Compared with the PTP E1/Ethernet protocol converter solution that is used in each subnetwork to establish the DCN channel, the shared E1 solution saves transmission resources but increases cost in protocol converters. Figure 1-7 E1/Ethernet protocol converter solution (shared E1)
NMS E1/Ethernet Converter (concentratet ype) E1/Ethernet Converter (cascade type) TS 1-12 TS 1-12 GNE 1 Central netw ork Edge subnetw ork 1 TS 1-8 E1/Ethernet Converter (cascade type) TS 1-4 TS 1-8
LAN sw itch
TS 1-4 GNE 3 Edge subnetw ork3 E1/Ethernet Converter (PTP type) E1 GNE 2 Edge subnetw ork 2
Ethernet link
Radio link
NOTE
l The sub-network at the end of the network is not involved in the E1 aggregation. Hence, the costeffective PTP E1/Ethernet protocol converter can be used for such a sub-network. l In this figure, the gateway NE in each sub-network uses four timeslots in the E1 to transmit NM messages. Specifically, timeslots 1-4 on sub-network 3, timeslots 5-8 on sub-network 2, and timeslots 9-12 on sub-network 1 are occupied.
Shared BTS service channel This solution is adopted when the transmission network carries the BTS service and both BSC and BTS support the 64 kbit/s timeslot scheduling function (that is, fractional E1 function). In this solution, the BTS is connected to the sub E1 port on the PTP E1/Ethernet protocol converter, and the services from the BTS are transparently transmitted to the BSC through the main E1 port; the gateway NE is connected to the FE port on the PTP E1/ Ethernet protocol converter, and the NMS message is transmitted in the Nx64 kbit/s idle timeslot of the main E1 port. BSC uses the fractional E1 function to demultiplex Nx64kbit/ s data services from each BTS service E1, and aggregates the data services in one E1 for
Issue 05 (2010-10-30)
1-9
transmission to the channelized and concentrated E1/Ethernet protocol converter. The protocol converter demultiplexes Nx64kbit/s data services in the E1 and converts these services into corresponding Ethernet data for transmission to the NMS, as shown in Figure 1-8. Figure 1-8 E1/Ethernet protocol converter solution (shared BTS service channel)
BTS Sub E1 Main E1 NM S E1/Ethernet Converter (PTP type) BTS TS 1-3 LAN switch E1/Ethernet BSC Converter (concentratet ype) Sub E1 Main E1 E1/Ethernet Converter (PTP type) BTS Sub E1 Main E1 E1/Ethernet Converter (PTP type) Ethernet link E1 GNE 3 Edge network 3 GNE 2 Edge network 2 GNE 1 Edge network 1
Radio link
Back haul link
NOTE
In this figure, the gateway NE in each domain uses the idle timeslot 30 in the BTS service E1 to transmit the NM message. BSC demultiplexes the three timeslots from the BTS service E1, schedules the services to TS1-TS3 in the E1 that is connected to the channelized and concentrated E1/Ethernet protocol converter.
Hybrid Use Solution of Protocol Converters

This solution is a hybrid of the preceding solutions. With this solution, the auxiliary channel capacity of the central equipment can be used to the greatest extent, and less service bandwidths are occupied. As shown in Figure 1-9, the central equipment supports one RS-232 asynchronous data service and one 64 kbit/s synchronous data service, and the edge equipment is located in three domains. Hence, the three domains use the RS-232/Ethernet protocol converter, 64k/ Ethernet protocol converter, and E1/Ethernet protocol converter respectively to establish DCN communication links. Then, the LAN switch aggregates the services to the NMS.
1-10
Issue 05 (2010-10-30)
Figure 1-9 Hybrid Use Solution of Protocol Converters
NMS
RS-232/ Ethernet Converter
RS-232/ GNE 1 Ethernet Converter Edge netw ork 1
LAN sw itch
64k/Ethernet GNE 2 Converter Edge netw ork 2 Central netw ork
E1/Ethernet Converter (PTP ype)
E1/Ethernet Converter (PTP type) Ethernet link RS-232 link
GNE 3 Edge netw ork 3
Radio link 6kbps link E1
Issue 05 (2010-10-30)
1-11
2 HWECC Solution
2
About This Chapter
This chapter describes the HWECC solution.
HWECC Solution
2.1 Introduction This section provides the definition of HWECC and describes its purpose. 2.2 Basic Concepts This section describes the basic concepts that you should be familiar with before using HWECC. 2.3 Specifications This section describes the specifications of HWECC. 2.4 Reference Standards and Protocols This section describes the standards and protocols associated with HWECC. 2.5 Availability This section describes the support required by the application of HWECC and its dependency. 2.6 Principles This section describes the principles of the HWECC solution. 2.7 Planning Guidelines Follow certain planning guidelines when you plan HWECC. 2.8 Configuration Flow The configuration of the HWECC solution consists of two parts, namely, the configuration of communications data at the near end and the creation of NEs on the NMS. 2.9 Configuration Example This section uses an example to describe how to plan and configure the HWECC solution according to network conditions. 2.10 Task Collection This section provides the hyperlinks of the operation tasks associated with the HWECC feature. 2.11 Relevant Alarms and Events The HWECC solution does not involve any alarm or event. 2.12 FAQs
2 HWECC Solution
This section provides the answers to the questions that are frequently raised when the HWECC solution is used.
2-2
Issue 05 (2010-10-30)
2 HWECC Solution
2.1 Introduction
This section provides the definition of HWECC and describes its purpose.
Definition
HWECC is a DCN solution provided by Huawei. In this solution, the NMS manages NEs by using network management messages that are encapsulated in the HWECC protocol stack. In the case of HWECC, network management messages are encapsulated in the proprietary HWECC protocol stack for transmission. Thus, this solution can be used when the network is comprised of only the OptiX equipment that supports the HWECC protocol stack. Figure 2-1 shows how network management messages are transmitted by using HWECC. Network management messages encapsulated in compliance with the HWECC protocol stack can be transmitted through DCCs carried by optical fibers or microwave, or can be transmitted over the Ethernet between Ethernet NM interfaces or between NE cascading interfaces. Figure 2-1 Networking diagram of HWECC
Message HWECC DCC
Message HWECC DCC
Message HWECC ETH
Message HWECC DCC
NMS
Message HWECC DCC Message HWECC DCC
OptiX optical transmission equipment Radio link Fiber
OptiX radio transmission equipment
Ethernet link
Purpose
HWECC is preferred as the DCN solution when the network is comprised of only the OptiX equipment that supports the HWECC protocol stack.
Issue 05 (2010-10-30)
2-3
2 HWECC Solution
2.2 Basic Concepts

This section describes the basic concepts that you should be familiar with before using HWECC. 2.2.1 HW ECC Protocol Stack ITU-T G.784 defines the architecture of the ECC protocol stack based on the OSI seven layer reference model. The HW ECC protocol stack is based on the ECC protocol stack. 2.2.2 Extended ECC The HW ECC protocol supports the use of the Ethernet as extended channels for ECC transmission. Hence, when there is no DCC between two or more NEs, connect the Ethernet NM ports or NE cascading ports of the NEs to realize communication through extended ECCs.
2.2.1 HW ECC Protocol Stack

ITU-T G.784 defines the architecture of the ECC protocol stack based on the OSI seven layer reference model. The HW ECC protocol stack is based on the ECC protocol stack.
Architecture of the HW ECC protocol stack

Figure 2-2 Architecture of the HW ECC protocol stack
Application layer Presentation layer Session layer Transport layer Network layer Media access layer Physical layer HW ECC protocol stack Transport layer Network layer Data link layer Physical layer
OSI model
Physical Layer
The main function of the physical layer is to control physical channels. The physical layer performs the following functions: l Maintains the status of the physical channel. The physical layer maintains the status information of the DCC to which each line port corresponds. The status information includes the following:
2 HWECC Solution
Port enabled state Used overhead byte Link status information l Provides the data communication service. The physical layer receives the data of the physical channel and transfers the data to the upper layer. The physical layer receives the data frames transferred from the upper layer and sends them to the physical channels. Physical channels are classified into the following two categories: l DCC channel DCC channels use the DCC bytes in SDH frames or PDH microwave frames as the channels for the communication among NEs. In the HW ECC solution: SDH line ports generally use bytes D1 to D3 as DCC channels. When the IF1A/B board transmits 16xE1 or higher-capacity PDH microwave signals, the IF1A/B board always uses bytes D1 to D3 as DCC channels. When the IF1A/B board transmits PDH microwave signals less than 16xE1, the IF1A/ B board always uses byte D1 as the DCC channel. The microwave ports of the IF0A/B board and IDU 605 always use bytes D1 to D3 as DCC channels. When the IFH2 board transmits Hybrid microwave signals, the IFH2 board always uses bytes D1 to D3 that are defined by Huawei as DCC channels. l Extended channel The extended channel uses the Ethernet between the Ethernet NM interfaces or between the NE cascade interfaces as the communication path between NEs. The method of transmitting the ECC on the extended channel is called the extended ECC. For details about the extended ECC, see 2.2.2 Extended ECC.
Media Access Layer

The main function of the media access layer (MAC layer) is to activate or close physical DCCs between the physical layer and the network layer. The MAC layer performs the following functions: l 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. The MAC connection has the following characteristics: A MAC connection exists between any two adjacent NEs that can communicate through the ECC. A MAC connection is a bidirectional connection. There is only one MAC connection between any two adjacent NEs that can communicate through the ECC, even if many ports of the two NEs that support the DCC are interconnected. The physical channel of the current MAC connection is also the current ECC route. l
Issue 05 (2010-10-30)
Provides the data communication service.

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 2-5
2 HWECC Solution
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 corresponding physical channel in the physical layer through the MAC connection. Otherwise, the MAC layer discards the data frame.
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 function for the DCC communication network. The NET layer performs the following functions: l Establishes and maintains ECC routes. The NET layer establishes and maintains the NET layer routing table. 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.) Mode (0 represents the automatic route and 1 represents the manual route) l Provides the data communication service. The NET layer receives the packet transferred from the MAC layer. If the destination address of the packet is 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 route item 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 route item that matches the destination address of the packet in the NET 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 NMS 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 HW ECC 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.
2-6
Issue 05 (2010-10-30)
2 HWECC Solution
2.2.2 Extended ECC

The HW ECC protocol supports the use of the Ethernet as extended channels for ECC transmission. Hence, when there is no DCC between two or more NEs, connect the Ethernet NM ports or NE cascading ports of the NEs to realize communication through extended ECCs.
Networking Mode
There are two networking modes for the extended ECC: l Using the network cable Use a network cable to directly connect the Ethernet NM ports or NE cascading ports of the two NEs. l Using the hub Use a hub or other data communication equipment to connect the Ethernet NM ports of related NEs. Figure 2-3 Networking for the extended ECC (using a network cable)
NMS
Network cable
Radio link
Issue 05 (2010-10-30)
2-7
2 HWECC Solution
Figure 2-4 Networking for the extended ECC (using a hub)

NMS
Hub
Network cable
Radio link
The Ethernet NM port and the NE cascading port are equivalent to two ports on a hub. Hence, you can use network cables to connect NEs in series. This type of connection is equivalent to the hub connection. Figure 2-5 Networking for the extended ECC (using network cables to connect NEs in series)
NMS
Network cable
Radio link
2-8
Issue 05 (2010-10-30)
2 HWECC Solution
CAUTION
l If you use a hub to connect NEs or use network cables to connect NEs in series, there must be no network loop in the Ethernet. Otherwise, a broadcast storm occurs and the SCC board is reset repeatedly. l As both the Ethernet NM port and the NE cascading port have the MDI and MDI-X adaptive capability, either a straight through cable or a crossover cable can be used as the network cable for the extended ECC. l The OptiX RTN NEs can transmit network management information with the other OptiX NEs through extended ECCs.
Extension Mode
There are two extension modes for the extended ECC: l Automatic mode In an Ethernet, the NE with the largest IP address is automatically considered as the server and other NEs are automatically considered as clients. The NEs automatically establish TCP connections between the server and clients and also establish corresponding MAC connections according to the TCP connections. In the automatic mode, the server and clients need not be manually specified. The maximum number of NEs (including the servers and clients) for the extended ECC in automatic mode is 4. l Specified mode In the manual mode, NEs establish TCP connections between the server and clients according to the server, clients, IDs of connecting ports, which are set manually, and other information that is entered manually. Then, the NEs establish corresponding MAC connections according to the TCP connections. In specified mode, a server can be connected to up to seven clients. When the accessed NEs are more than seven, the multi-level extended ECC mode can be used to access more NEs. Figure 2-6 shows an example of the multilevel extended ECC. Server 1 is connected to seven clients, namely, Client 11-Client 17. Meanwhile, Client 17 functions as Server 2 and is connected to seven clients, namely, Client 21-Client 27. When the multi-level extended ECC is used, the IDs of the connected ports in the extended ECCs cannot be the same.
Issue 05 (2010-10-30)
2-9
2 HWECC Solution
Figure 2-6 Extended ECC network (multi-level extended ECC)
NMS Client 21 Hub Client 22 Server 1
Client 11 Client 12 Client 17 and Server 1
Client 23
NOTE
The NE starts the automatic extended ECC by default.
2.3 Specifications
This section describes the specifications of HWECC.
2-10
Issue 05 (2010-10-30)
2 HWECC Solution
Table 2-1 Specifications of HWECC Item Number of DCCs Specifications The number of DCCs is determined by the microwave/line type. l STM-1/STM-4 or SDH radio supports 12 DCC bytes, that is, D1-D12. The equipment supports three modes: D1-D3, D4-D12, and D1-D12. l When transmitting 16xE1 signals or higher-capacity PDH microwave signals, the IF1A/B board always uses Huaweidefined bytes D1-D3 as DCCs. l When transmitting PDH microwave signals less than 16xE1 signals, the IF1A/ B board always uses Huawei-defined byte D1 as the DCC channel. l The IF0A/B board always uses Huaweidefined bytes D1-D3 as DCCs. l When transmitting Hybrid microwave signals, the IFH2 board uses Huaweidefined bytes D1-D3 as DCCs. Extended ECC Supports two extended ECC modes: automatic extended ECC mode and extended ECC mode. The default mode is the automatic extended ECC mode. Supported With the DCN bandwidth of 192 kbit/s, it is recommended that an ECC subnet has not more than 120 NEs. The maximum number of NEs on an ECC subnet is 150 (only for the OptiX RTN 620 V100R005).
DCC transparent transmission Scale of the ECC subnet
2.4 Reference Standards and Protocols

This section describes the standards and protocols associated with HWECC. As a proprietary protocol of Huawei, the HWECC protocol is based on ECC protocol stack defined in ITU-T G.784 Synchronous Digital Hierarchy (SDH) management.
2.5 Availability
This section describes the support required by the application of HWECC and its dependency.
Issue 05 (2010-10-30)
2-11
2 HWECC Solution
Hardware and Version Support

Table 2-2 Hardware and version support Feature HWECC Applicable Board SCC IF1A/IF1B IF0A/IF0B IFX IFH2 SL1/SD1 SLE/SDE SL4 Applicable Hardware Version All the versions All the versions All the versions All the versions All the versions All the versions All the versions All the versions Applicable Product Version V100R001 and later V100R001 and later V100R002 and later V100R002 and later V100R003 and later V100R001 and later V100R001 and later V100R002 and later
Feature Dependency
When the HWECC solution is used with other DCN solutions, pay attention to the relations between the HWECC solution and other DCN solutions. l l l The HWECC protocol stack of NEs can communicate with the IP protocol stack of IP over DCC. The HWECC protocol stack of NEs can communicate with the OSI protocol stack in the same area on the L1 layer. If DCC bytes are used to transparently transmit NM messages when the OptiX equipment is used with the third-party equipment to form a network, it is recommended that you adopt the HWECC protocol to manage the OptiX equipment. If DCC bytes are used to transparently transmit NM messages through the external clock interface when the OptiX equipment is used with third-party equipment to form a network, it is recommended that you adopt the HWECC protocol to manage the OptiX equipment. If the protocol manager is used to transparently transmit NM messages, it is recommended that you adopt the HWECC protocol to manage the OptiX equipment.
2.6 Principles
This section describes the principles of the HWECC solution. 2.6.1 Establishing ECC Routes The HW ECC 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. 2.6.2 Packet Transfer In the HWECC solution, the messages between NEs are transferred in the NET layer of the NEs. 2.6.3 Extended ECC
2 HWECC Solution
The extended ECC realizes the MAC connection between adjacent NEs by using the TCP connection.
2.6.1 Establishing ECC Routes

The HW ECC 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. 2. The physical layer of an NE maintains the status information of the DCC to which each line port corresponds. The MAC layer of the NE establishes the MAC connection between the NE and the adjacent NE. The steps are as follows: (1) The NE broadcasts the connection request frame (MAC_REQ) to the adjacent NE in a periodical manner. (2) After receiving the MAC_REQ, the adjacent NE returns the connection response frame (MAC_RSP). (3) If the MAC_RSP is received within the specified time, the NE establishes a MAC connection between the NE and the adjacent NE. 3. The NET layer of the NE establishes the NET layer routing table. The steps are as follows: (1) According to the status of the MAC connection, the NE establishes an initial NET layer routing table. (2) The NE broadcasts its routing table to the adjacent NE in a periodical manner through the routing response message. (3) The adjacent NE updates its NET layer routing table according to the received routing response message and the shortest path first algorithm. (4) At the next route broadcasting time, the NE broadcasts its current NET layer routing table to the adjacent NE. Figure 2-7 Networking example for establishing ECC routes
NE1 NE2 NE5
NE3
NE4
Issue 05 (2010-10-30)
2-13
2 HWECC Solution
The following describes how to establish ECC routes between NEs. The network shown in Figure 2-7 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. (1) 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. (2) 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. (3) 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. 3. The NET layer of the NE establishes the NET layer routing table. NE1 is considered as an example to describe how to establish the NET layer routing table. (1) According to the status of the MAC connection, NE1 establishes an initial NET layer routing table. In the routing table, there are two routes, one to NE2 and one to NE5. (2) NE1 broadcasts its routing table to adjacent NEs in a periodical manner through the routing response message. (3) After receiving the routing response message from NE1, NE2 and NE5 update their respective NET layer routing tables. After the update, there is a route to NE5 in the NET layer routing table of NE2, and the transfer NE is NE1. There is a route to NE2 in the NET layer routing table of NE5, and the transfer NE is also NE1. 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 NET layer routing table. The routes to NE4 are processed in the same way as those to NE3. (4) 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 NET 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.
2.6.2 Packet Transfer

In the HWECC solution, the messages between NEs are transferred in the NET layer of the NEs. Figure 2-8 illustrates how the HWECC solution transfers the messages originating from the NMS to a destination NE.
2-14
Issue 05 (2010-10-30)
2 HWECC Solution
Figure 2-8 Realization principle of message transfer (HWECC)

Application TCP IP Application TCP IP L4 NET MAC Ethernet Ethernet DCC T2000 Gateway NE DCC Transfer NE DCC Destination NE NET MAC Application L4 NET MAC
The realization principle is as follows: 1. 2. 3. The NMS transfers application layer messages to the gateway NE through the TCP connection between them. The gateway NE extracts the messages from the TCP/IP protocol stack and reports the messages to the application layer. 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 application 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 2-8 is HWECC, the gateway NE transfers the messages to the transfer NE through the HWECC stack. After receiving the packet that encapsulates the messages, 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. After receiving the packet, 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 functions according to the message sent from the NMS.
NOTE
4.
5.
The core routing table synthesizes the transport layer routing tables of all communication protocol stacks. Each route item includes the following: l ID of the destination NE l Address of the transfer NE l Communication protocol stack of the transfer NE l Transfer distance
2.6.3 Extended ECC

The extended ECC realizes the MAC connection between adjacent NEs by using the TCP connection.
2 HWECC Solution
Automatic Mode
The realization principle is as follows: 1. 2. 3. 4. 5. Each NE obtains the IP addresses of other NEs that are in the same Ethernet through the address resolution protocol (ARP). The NE with the largest IP address automatically functions as the server and detects the TCP requests from the clients. Other NEs automatically function as clients and send TCP connection requests to the server. After receiving the TCP connection request from a client, the server establishes the corresponding TCP connection. The NEs use the TCP connection as a MAC connection to realize ECC communication.
Specified Mode
The realization principle of the specified mode is basically the same as the realization principle of the automatic mode. The difference is that in the specified mode, the server, clients, and IDs of connecting ports are manually specified.
2.7 Planning Guidelines

Follow certain planning guidelines when you plan HWECC.
Planning Guidelines for GNEs

l l It is recommended that the selected GNE be the closest NE to the NMS, the central node of a start network, or the NE that accesses most DCC. Set an active GNE and a standby GNE for an ECC subnet, if possible.
NOTE
An ECC subnet is an ECC network comprised of a GNE and non-GNEs that communicate with the NMS through the GNE. An ECC network consists of one or more ECC subnets.
Planning Guidelines for External DCN

l l l For stability and security of external DCN, it is recommended that you do not use the office LAN or Internet as the transmission channels of external DCN. It is recommended that the bandwidth of external DCN should not be lower than the DCC bandwidth on the network. The link at 256 kbit/s already meets the requirements. It is recommended that the channels of external DCN be provided by other networks (not a monitored network). If the external DCN uses the channel provided by the data processing board, consider the risk when the external DCN uses the service channel provided by the monitored network. Active and standby DCN routes or GNEs should be provided for external DCN if possible.
Planning Guidelines for NE IDs

l l The NEs on one DCN must have unique IDs. If each NE on one DCN can be allocated a unique basic ID, do not use different extended IDs.
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 05 (2010-10-30)
2-16
2 HWECC Solution
Make a rule in allocating NE IDs on a newly-built network. Allocate NE IDs in the anticlockwise direction on a ring network. Allocate NE IDs from the core to the edges on a chain or tree network.
Allocate unused IDs to the NEs that are added on an existing network.
Planning Guidelines for IP Addresses of NEs

l l l Set the IP addresses of GNEs, subnet masks, and default GNEs as required by the planning of external DCN. Set the IP addresses of the NEs with extended ECC on the same network segment. Set the IP address of non-GNEs according to their NE IDs.
NOTE
l The IP address of non-GNEs should be 0x81000000+ID. For example, if the ID of an NE is 0x090001, set the IP address of the NE to 129.9.0.1. l By default, the subnet mask is 255.255.0.0.
Planning Guidelines for Extended ECC

l l l l l l l If a site holds multiple OptiX NEs without any DCC, achieve extended ECC by connecting the Ethernet NM interfaces or NE cascading interfaces. If you use hubs or network cables for extended ECC networking, never form an Ethernet loop. If you use hubs for extended ECC networking, do not connect the hubs to other equipment. Set the IP addresses of the NEs with extended ECC on the same network segment. Extended ECC is automatically enabled on NEs. In this case, an extended ECC subnet consists of a maximum of four NEs (including the server and all clients). It is recommended that you disable the extended ECC function on GNEs. When an extended ECC subnet consists of more than four NEs (including the server and all clients), enable extended ECC in a specified manner. If an extended ECC subnet consists of more than seven NEs, specify levels for the subnet to ensure that each server is connected to a maximum of seven clients. When you enable extended ECC in a specified manner, it is recommended that you select the NE closest to the NMS as the server of TCP connections and the other NEs on the same subnet as clients. Then, set the port ID to any number between 1601 and 1699. In an extended ECC subnet of multiple levels, each group takes a unique port ID.
Planning Guidelines for ECC Subnets

l With the DCN bandwidth of 192 kbit/s, it is recommended that an ECC subnet has not more than 120 NEs. The maximum number of NEs on an ECC subnet is 150 (only for the OptiX RTN 620 V100R005). When the number of NEs on an ECC network exceeds 120, it is recommended that you increase GNEs to divide the network into multiple ECC subnets. The DCCs between ECC subnets must be disabled. Maintain the existing ECC route protection when you divide an ECC network.
l l l
Issue 05 (2010-10-30)
2-17
2 HWECC Solution
2.8 Configuration Flow

The configuration of the HWECC solution consists of two parts, namely, the configuration of communications data at the near end and the creation of NEs on the NMS. Table 2-3 Configuration flow for the HWECC solution Step 1 Operation A.1.5 Changing NE IDs Remarks Required. Set the parameters as follows: l Set ID to be the NE ID according to the planning of the DCN. l If the special extended ID is required for the NE according to the planning of the DCN, change Extended ID. 2 A.3.1 Setting NE Communication Parameters Required. Set the parameters as follows: l For the GNE, set IP Address and Subnet Mask according to the planning of the external DCN. l For the GNE, set Gateway IP Address if the external DCN requires that the default gateway is configured for the NE. l For the non-GNE, it is recommended that you set IP Address to 0x81000000 + NE ID. That is, if the NE ID is 0x090001, set IP Address to 129.9.0.1. Set Subnet Mask to 255.255.0.0. 3 A.3.2 Configuring DCCs Required when the NE is connected to other ECC subnets. Set the parameters as follows: l Set Enabled Status to Disabled for the port that is connected to other ECC subnets. l Adopt the default values for the other parameters. In the other cases, all the parameters take the default values.
2-18
Issue 05 (2010-10-30)
2 HWECC Solution
Step 4
Operation A.3.3 Configuring the Extended ECC
Remarks Required when the number of NEs accessed through the extended ECC is more than four. Set the parameters as follows: l Set Extended Mode to Specified Mode. l Set Port for the NE that is planned as a server and the port ID is a number from 1601 to 1699. It is recommended that you set Port to 1602. l Set Opposite IP and Port for the NE that is planned as a client. That is, set Opposite IP to the IP address of the server and set Port to the same as Port of the server.
NOTE When the number of NEs accessed through the extended ECC is more than eight, you need to configure multiplelevel extended ECC.
Required for the GNE. Set the parameters as follows: l Set Extended Mode to Specified Mode. l Adopt the default values for the other parameters.
NOTE This operation is performed to disable the automatic extended ECC function of the GNE.
In the other cases, all the parameters take the default values. 5 A.3.4 Configuring DCC Transparent Transmission When the ECC route protection function is affected due to the division of the ECC subnet, D1 to D3 bytes can be passed through over other ECC subnets through this operation. In this manner, the ECC route protection function is guaranteed. Perform this operation only on the GNE. In normal cases: l There is an ECC route between the GNE and each of its managed non-GNEs. l There is no ECC route between the GNE and each NE on other ECC subnets. l ECC routes follow the shortest path first principle. 7 Creating NEs on the centralize d NMS A.1.2 Creating NEs by Using the Manual Method It is recommended that you create NEs on the centralized NMS by using this method when you need to add one or more NEs on a large-scale network.
A.3.10 Querying ECC Routes
Issue 05 (2010-10-30)
2-19
2 HWECC Solution
Step
Operation A.1.1 Creating NEs by Using the Search Method
Remarks In other cases, this method is preferred.
NOTE
If the centralized NMS is U2000 instead of Web LCT, the NEs need to be created on the U2000. For the information on how to create NEs on the U2000, see the Feature Description (U2000).
2.9 Configuration Example

This section uses an example to describe how to plan and configure the HWECC solution according to network conditions. 2.9.1 Networking Diagram This section describes the networking information about the NEs. 2.9.2 Service Planning The service planning information contains the information about all the parameters required for configuring the NE data. 2.9.3 Configuration Process This section describes the procedure of data configuration.
2.9.1 Networking Diagram

This section describes the networking information about the NEs. In the networking diagram shown in Figure 2-9, the OptiX optical transmission equipment and the OptiX radio transmission equipment form a network. On the network, the sets of OptiX optical transmission equipment and OptiX radio transmission equipment are more than 40. The centralized NMS can manage all the OptiX equipment on the network.
2-20
Issue 05 (2010-10-30)
2 HWECC Solution
Figure 2-9 Networking diagram of the HWECC solution

NE205
NE203 NE204 NE202 NE103
NE101
NE201 NE102
NMS NE104
NE105
OptiX optical transmission equipment OptiX radio transmission equipment
Router Radio link Fiber
LAN sw itch Netw ork cable
2.9.2 Service Planning

The service planning information contains the information about all the parameters required for configuring the NE data. l There are more than 40 sets of optical transmission equipment and more than 40 sets of radio transmission equipment on the network. Hence, the ECC network is divided into two ECC subnets according to the type of equipment. Select the central node NE101 of the optical transmission service and the central node NE202 of the radio transmission service as GNEs. The NMS and NE101 are located at the same place and NE202 is located at another place. Therefore, you need to construct the external DCN between the NMS and NE202 through a router or protocol converter. Allocate IDs and IP addresses for all the NEs according to the conditions of the network.
l l
Issue 05 (2010-10-30)
2-21
2 HWECC Solution
Figure 2-10 Allocation of IDs/IP addresses for all the NEs

9-205 129.9.0.205 0.0.0.0 9-204 129.9.0.204 0.0.0.0
9-203 129.9.0.203 0.0.0.0 11.0.0.1/16
9-202 11.0.0.202 11.0.0.1
9-201 129.9.0.201 0.0.0.0 10.0.0.1/16 9-101 10.0.0.101 0.0.0.0 9-102 129.9.0.102 0.0.0.0 9-103 129.9.0.103 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
Extended ID-Basic ID IP address Gateway
Plan the extended ECC. There is no DCC between NE203 and NE204 or between NE203 and NE205. Therefore, you need to use network cables to connect the Ethernet NE port and the NE cascading port to extend the ECC. The extended ECC function works in the automatic mode. NE101 and NE202 function as GNEs. Therefore, you need to disable the extended ECC function on these NEs.
Divide the ECC network. Shut down the DCC channels of the east and west ports on the ring of NE201 so that the DCC between two ECC subnets is disconnected. Set the D1 to D3 bytes so that they can be passed through on NE201. In this manner, the ECC route protection function is not affected.
2.9.3 Configuration Process

This section describes the procedure of data configuration.
Context
NOTE
In this configuration example, only the configuration information about NE201, NE202, and NE203 is provided.
Procedure
Step 1 See A.1.5 Changing NE IDs and change the NE ID. The values for the related parameters are provided as follows.
2 HWECC Solution
Parameter
Value Range NE201 NE202 202 9 (default value) NE203 203 9 (default value)
New ID New Extended ID
201 9 (default value)
Step 2 See A.3.1 Setting NE Communication Parameters and set the communication parameters of the NE. The values for the related parameters are provided as follows. Parameter Value Range NE201 IP Address Gateway IP Address Subnet Mask 129.9.0.201 0.0.0.0 (default value) 255.255.0.0 (default value) NE202 11.0.0.202 11.0.0.1 255.255.0.0 (default value) NE203 129.9.0.203 0.0.0.0 (default value) 255.255.0.0 (default value)
Step 3 See A.3.2 Configuring DCCs and configure the DCC. The values for the related parameters are provided as follows. Parameter Value Range East and West Ports on the Ring (NE201) Enabled/Disabled Channel Type Disabled Other Microwave/ Line Ports (NE201) All the Microwave/Line Ports (NE202 and NE203) Enabled (default value) D1 (default value of the PDH microwave port whose capacity is smaller than 16 E1s) D1-D3 (default values of other ports) HWECC (default value)
Enabled (default value) D1 (default value of the PDH microwave port whose capacity is smaller than 16 E1s) D1-D3 (default values of other ports)
Protocol Type
HWECC (default value)
Step 4 See A.3.3 Configuring the Extended ECC and configure the extended ECC. The values for the related parameters are provided as follows.
2 HWECC Solution
Parameter
Value Range NE201 NE202 Specified mode 1601 (default value) 0.0.0.0 (default value) 1601 (default value) NE203 Auto mode (default value) -
ECC Extended Mode Port (on the server side) Opposite IP (on the client side) Port (on the client side)
Auto mode (default value) -
Step 5 See A.3.4 Configuring DCC Transparent Transmission and configure the transparent transmission of the DCC byte on NE201. Parameter Source Timeslot/ Port Transparent Transmission of Overhead Bytes at Source Port Sink Timeslot/Port Value Range Related parameter values of west ports on the ring D1 Related parameter values of west ports on the ring D2 Related parameter values of west ports on the ring D3
Related parameter values of east ports on the ring D1
Transparent Transmission of Overhead Bytes at Sink Port
Step 6 See A.3.10 Querying ECC Routes and query the ECC route on NE101 and NE210. The expected results are as follows: l The routes to all the OptiX optical transmission NEs can be queried on NE101 whereas the routes to NE201 and NE202 cannot be queried. l The routes to all the OptiX radio transmission NEs can be queried on NE202 whereas the routes to NE101 and NE102 cannot be queried. Step 7 See A.1.1 Creating NEs by Using the Search Method and create NEs in the search mode on the centralized NMS. The search domains include the following: l The search network segment when the IP address of the GNE is 10.0.0.101 l The search network segment when the IP address of the GNE is 11.0.0.201

NOTE
2 HWECC Solution
The IP address 11.0.0.201 of NE202 and the IP address of the centralized NMS are not in the same network segment. Therefore, you need to configure static routes on both the NMS and the corresponding router before creating NEs, to ensure that the TCP/IP communication between them is normal.
In normal cases, all the NEs can be created on the centralized NMS. ----End
2.10 Task Collection

This section provides the hyperlinks of the operation tasks associated with the HWECC feature.
Related Tasks
A.1.1 Creating NEs by Using the Search Method A.1.2 Creating NEs by Using the Manual Method A.1.5 Changing NE IDs A.3.1 Setting NE Communication Parameters A.3.2 Configuring DCCs A.3.3 Configuring the Extended ECC A.3.4 Configuring DCC Transparent Transmission A.3.10 Querying ECC Routes
2.11 Relevant Alarms and Events

The HWECC solution does not involve any alarm or event.
2.12 FAQs
This section provides the answers to the questions that are frequently raised when the HWECC solution is used. Q: Why does the NMS always fail to log in to an NE? A: Common causes are as follows: l l l The communication connection between the NMS and the GNE is faulty. To locate the fault, run the ping or tracert command on the NMS server. The ECC route between the GNE and a non-GNE is faulty. To locate the fault, check the ECC route between the GNE and the non-GNE. NE IDs conflict.
Q: Why does the NMS frequently fail to log in to NEs? A: Common causes are as follows:
2 HWECC Solution
l l l
The NMS is faulty. In this case, the NMS generally fails to log in to all the NEs. The IP addresses of GNEs conflict. In this case, the NMS generally fails to log in to all the NEs on an ECC subnet. An ECC subnet is of an excessively large scale. In this case, the NMS generally fails to log in to the NEs that access multiple DCCs.
Q: Why does the system control and communication board on the GNE or the NE that uses the extended ECC frequently reset? A: Common causes are as follows: l l Unknown equipment is connected to the LAN to which the NE is connected, resulting in a conflict between the NE and the equipment. A loop (especially a loop between the Ethernet NM port and the NE cascading port) occurs in the LAN to which the NE is connected, resulting in a network storm.
Q: What hazards will an ECC subnet of an excessively large scale bring? A: Main hazards are as follows: l l l l l The stability of the ECC route is poor, the convergence time is long, and even the oscillate of the ECC route occurs. The remote loading is slow. The alarms reported to the NMS are lost. The NMS cannot log in to certain NEs. The control boards of certain NEs reset abnormally.
2-26
Issue 05 (2010-10-30)
3 IP over DCC Solution
3
About This Chapter
IP over DCC Solution
This chapter describes the IP over DCC solution. 3.1 Introduction This section provides the definition of IP over DCC and describes its purpose. 3.2 Basic Concepts This section describes the basic concepts that you should be familiar with before using IP over DCC. 3.3 Specifications This section describes the specifications of IP over DCC. 3.4 Reference Standards and Protocols This section describes the standards and protocols associated with IP over DCC. 3.5 Availability This section describes the support required by the application of the IP over DCC solution and its dependency. 3.6 Principles This section describes the principles of the IP over DCC solution. 3.7 Planning Guidelines Follow certain planning guidelines when you plan IP over DCC. 3.8 Configuration Flow The configuration of the IP over DCC solution consists of two parts, that is, the configuration of communications data at the near end of the NE and the creation of the NE on the NMS. 3.9 Configuration Example This section uses an example to describe how to plan and configure the IP over DCC solution according to network conditions. 3.10 Task Collection This section provides the hyperlinks of the operation tasks associated with the IP over DCC feature. 3.11 Relevant Alarms and Events
The IP over DCC solution does not involve any alarm or event. 3.12 FAQs This section provides the answers to the questions that are frequently raised when the IP over DCC solution is used.
3-2
Issue 05 (2010-10-30)
3.1 Introduction
This section provides the definition of IP over DCC and describes its purpose.
Definition
HWECC is a DCN solution provided by Huawei. In this solution, the NMS manages NEs by using network management messages that are encapsulated in the standard IP protocol stack. Figure 3-1 shows how network management messages are transmitted by using the IP over DCC solution. Different manufacturers' network management messages encapsulated in the IP protocol stack can be transmitted through DCCs carried by optical fibers or microwave, or can be transmitted over the Ethernet between Ethernet NM interfaces or between NE cascading interfaces. Figure 3-1 Networking diagram of IP over DCC
g Ms rty pa ck 3rd P sta I C DC
3rd-party Msg IP stack ETH Third-party NMS
g Ms ptiX ack O st IP C DC
3rd-party Msg IP stack DCC
OptiX NMS
OptiX Msg IP stack ETH
OptiX M sg IP stack DCC
3rd-part y Msg IP stack DCC
3rd-party Msg IP stack ETH
OptiX equipment Ethernet link Fiber
Third-party equipment Radio link
Purpose
IP over DCC is preferred as the DCN solution when the network is comprised of the OptiX equipment and the third-party equipment that supports IP over DCC. In addition, this solution can be used when the equipment in the center of the network needs to provide a network management message transmission path over IP for NEs at the edge of the network.
3.2 Basic Concepts

This section describes the basic concepts that you should be familiar with before using IP over DCC. 3.2.1 IP over DCC Protocol Stack
The IP over DCC adopts the architecture of the standard TCP/IP protocol stack. 3.2.2 Access Modes In the IP over DCC solution, there are two modes for the T2000 to access an NE, namely, gateway mode and direct connection mode.
3.2.1 IP over DCC Protocol Stack

The IP over DCC adopts the architecture of the standard TCP/IP protocol stack.
Protocol Stack Architecture

Figure 3-2 IP over DCC protocol stack architecture
Routing protocol Transport layer Network layer Data link layer Ethernet Physical layer DCC OSPF/RIP TCP/UDP IP PPP
Physical Layer
The main function of the physical layer is to provide data transmission channels for the data end equipment. Physical channels are classified into the following categories: l DCC channel DCCs use the DCC bytes in SDH frames, PDH or Hybrid microwave frames as the channels for communication between NEs. In the IP over DCC solution: If the network is only comprised of the OptiX equipment, it is recommended that you use bytes D1 to D3 in SDH frames as DCCs. If the OptiX equipment is connected to the third-party equipment by using the SDH line, it is recommended that you use the DCC bytes that the third-party equipment uses (for example, bytes D1 to D3 or D4 to D12) as DCCs. In the PDH microwave frame, one or three DCC bytes in the frame can always be used as DCCs. In the Hybrid microwave frame, three DCC bytes in the frame can always be used as DCCs. l Ethernet physical channel The NE provides the Ethernet physical channel through the Ethernet NM port or the NE cascade port.
3-4
Issue 05 (2010-10-30)
Data Link Layer

The main function of the data link layer is to provide reliable data transmission on physical links. For DCCs, the NE applies 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 applies 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 connectionless-oriented UDP.
Routing Protocols
Routing protocols belong to the content of the application layer. The NE supports two routing protocols, namely, the open shortest path first (OSPF) protocol and routing information protocol (RIP). By default, the NE uses the OSPF protocol. The RIP protocol is used only when the interconnected third-party equipment does not support the OSPF protocol. The OSPF protocol is a dynamic routing protocol based on 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 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 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 nongateway NEs must be in the same OSPF area. By default, the microwave or 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. In the case of the OptiX RTN 600 of the current version, dynamic routes have a higher priority than static routes. When there is a route conflict, the equipment always first selects dynamic routes.
Proxy ARP
The OptiX equipment supports the proxy ARP as a supplement to the routing protocol. The proxy ARP enables the NEs in the same network segment but different domains to communicate with each other. To realize communication between such NEs, the source NE sends the ARP broadcast packet to address the route to the destination NE. The NE with the proxy ARP function enabled checks the routing table after sensing the ARP broadcast packet. If the routing table contains the destination address that the ARP broadcast packet looks for, the NE returns an ARP spoofing packet, which enables the NE that sends the ARP broadcast packet to consider that the MAC address of the NE that returns the ARP spoofing packet is the MAC address of the
destination NE. In this manner, the packet that is to be sent to the destination NE is first sent to the NE with the proxy ARP function enabled and then forwarded to the destination NE. Figure 3-3 is an application example that shows how to use the proxy ARP function to realize communication between the third-party NE and the third-party NMS. In this example, the thirdparty NMS and the third-party GNE (that is, NE4) are in the same network segment (130.9.0.0). In addition, the third-party NMS and NE4 are accessed to the OptiX transmission network through the LAN. Hence, the IP addresses of NE1 and NE3 that are connected to the third-party NMS and NE4 are also in the 130.9.0.0 network segment. To realize communication between the third-party NMS and NE4, you need to enable the proxy ARP function for NE1 and NE3. In addition, on NE1, you need to configure a static route to the third-party NMS; on NE3, you need to configure a route to NE4. Figure 3-3 Application example of the proxy ARP
ARP proxy enabled NE 1 Third-party NMS NE 2 ARP proxy enabled NE 3 NE 4 NE 5
130.9.0.100
130.9.0.1
129.9.0.2
130.9.0.3
130.9.0.4
130.9.0.5
OptiX equipment Ethernet link
The corresponding routes in this figure are as follows: l l The OptiX transmission network uses the IP over DCC solution and all the NEs are in the same OSPF domain. Hence, routes exist between NE1, NE2, and NE3. The OSPF protocol diffuses the local route of the NE in the OSPF domain. Hence, NE1 owns the routes that are owned by NE4, and NE4 owns the routes that are owned by the third-party NMS. The IP addresses of the third-party NMS and NE4 are in the 130.9.0.0 network segment. Hence, when communicating with NE4, the third-party NMS broadcasts the ARP packet that addresses routes to NE4. The routing table contains the routes to NE4, so NE1 with the ARP function enabled sends an ARP spoofing packet to the third-party NMS so that the third-party NMS sends the packet to NE1 instead of NE4. Then, NE1-NE3 forward the packet according to the routing table. Finally, the packet arrives at NE4. In the same manner, the packet can be transmitted from NE4 to the third-party NMS over the proper routes.
3-6
Issue 05 (2010-10-30)

NOTE
l A static route must be configured between NE1 and NE3. Otherwise, NE1 and NE3 can own local routes only to the 130.9.0.0 network segment. That is, NE3 does not own a route of the third-party NMS and NE1 does not own a local route of NE1. l If the third-party NMS owns a static route to NE4 (the IP address of the gateway is the IP address of NE1) and NE4 owns a route to the third-party NMS (the IP address of the gateway is the IP address of NE3), NE1 and NE3 do not require the proxy ARP function.
3.2.2 Access Modes

In the IP over DCC solution, there are two modes for the T2000 to access an NE, namely, gateway mode and direct connection mode.
Gateway Mode
In the gateway mode, the T2000 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: l l l l ID of the destination NE Address of the transfer NE Communication protocol stack of the transfer NE Transfer distance
Direct Connection Mode

In the direct connection mode, the T2000 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: l l l l Destination IP address Subnet mask IP address of the gateway Interface
When the T2000 adopts the direct connection mode to access an NE, there must be an IP route between the T2000 and the NE. In the IP over DCC solution, the T2000 can access any NE by using the direct connection mode, that is, it can consider any NE as the gateway NE. To improve the communication efficiency, however, there should not be a lot of NEs that are accessed in the direct connection mode in a network.
3.3 Specifications
This section describes the specifications of IP over DCC.
The OptiX RTN 620 supports the following specifications of IP over DCC. Table 3-1 Specifications of IP over DCC Item Number of DCCs Specifications The number of DCCs is determined by the microwave/line type. l STM-1/STM-4 or SDH radio supports 12 DCC bytes, that is, D1-D12. The equipment supports three modes: D1-D3, D4-D12, and D1-D12. l When transmitting 16xE1 signals or higher-capacity PDH microwave signals, the IF1A/B board always uses Huaweidefined bytes D1-D3 as DCCs. l When transmitting PDH microwave signals less than 16xE1 signals, the IF1A/ B board always uses Huawei-defined byte D1 as the DCC channel. l The IF0A/B board always uses Huaweidefined bytes D1-D3 as DCCs. l When transmitting Hybrid microwave signals, the IFH2 board uses Huaweidefined bytes D1-D3 as DCCs. OSPF route Supported Currently, the OSPF protocol supports only the routes within an area and does not support the routes between areas. Thus, the gateway NE and all its non-gateway NEs must be in the same OSPF area. On the SDH line and radio link, the OSPF protocol is always enabled. On the Ethernet NM interface, the OSPF protocol can be enabled or disabled. static route Supported In the case of the OptiX RTN 620 of the current version, dynamic routes have a higher priority than static routes. When there is a route conflict, the equipment always selects dynamic routes first. ARP proxy Scale of the ECC subnet Supported With the DCN bandwidth of 192 kbit/s, it is recommended that an ECC subnet has not more than 120 NEs. The maximum number of NEs on an ECC subnet is 150 (only for the OptiX RTN 620 V100R005).
3-8
Issue 05 (2010-10-30)

This section describes the standards and protocols associated with IP over DCC. The following standards and protocols are associated with IP over DCC: l l IETF RFC 1661: The Point-to-Point Protocol (PPP) IETF RFC 1027: Using ARP to Implement Transparent Subnet Gateways
3.5 Availability
This section describes the support required by the application of the IP over DCC solution and its dependency.

Table 3-2 Hardware and version support Feature IP over DCC Applicable Board SCC IF1A/IF1B IF0A/IF0B IFX IFH2 SL1/SD1 SLE/SDE SL4 Applicable Hardware Version All the versions All the versions All the versions All the versions All the versions All the versions All the versions All the versions Applicable Product Version V100R001 and later V100R001 and later V100R002 and later V100R002 and later V100R003 and later V100R001 and later V100R001 and later V100R002 and later
Feature Dependency
When the IP over DCC solution is used with other DCN solutions, pay attention to the relations between the IP over DCC and other DCN solutions. l l l The IP over DCC protocol stack of NEs can communicate with the HWECC protocol stack. The IP over DCC 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 third-party equipment to form a network, you can adopt the IP over DCC protocol to manage the OptiX equipment, but it is recommended that you use the HWECC protocol. If DCC bytes are used to transparently transmit NM messages through the external clock interface when the OptiX equipment is used together with third-party equipment to form a
Issue 05 (2010-10-30)
network, you can adopt the IP over DCC protocol to manage the OptiX equipment, but it is recommended that you use the HWECC protocol. l If the protocol manager is used to transparently transmit NM messages, you can adopt the IP over DCC protocol to manage the OptiX equipment, but it is recommended that you use the HWECC protocol.
3.6 Principles
This section describes the principles of the IP over DCC solution.
Principle of the Packet Transfer in Gateway Mode

Figure 3-4 shows how the IP over DCC solution transfers the messages from the NMS to a nongateway NE when the NMS applies the gateway mode to access the NE. Figure 3-4 Realization principle of message transfer (gateway mode)
Application TCP IP Application TCP IP TCP IP PPP Ethernet Ethernet DCC T2000 Gateway NE DCC Transfer NE DCC Destination NE IP PPP Application TCP IP PPP
The realization principle is as follows: 1. 2. 3. The NMS transfers application layer messages to the gateway NE through the TCP connection between them. The gateway NE extracts the messages from the TCP/IP protocol stack and reports the messages to the application layer. 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 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. The communication protocol stack of the transfer NE in Figure 3-4 is IP. Hence, the gateway NE transfers the messages to the transfer NE through the IP protocol stack. After receiving the packet that encapsulates the messages, the network layer of the transfer NE queries the destination IP address of the packet. If the destination IP address is not the IP address of the local NE, the transfer NE queries the IP routing table according to the destination IP address to obtain the corresponding route and then transfers the packet. After receiving the packet, the network layer of the destination NE reports the packet to the application layer through the transport layer because the destination IP address of the
4.
5.
3-10
packet is the IP address of the local NE. The application layer functions according to the message sent from the NMS.
Principle of the Packet Transfer in Direct Connection Mode

Figure 3-5 shows how the IP over DCC solution transfers the messages originating from the NMS to a destination NE when the NMS applies the direct connection mode to access the NE. Figure 3-5 Realization principle of message transfer (direct connection mode)
Application TCP IP IP PPP Ethernet Ethernet DCC T2000 Transfer NE DCC Transfer NE DCC Destination NE IP PPP Application TCP IP PPP
Different from the gateway mode, the original gateway NE in the direct connection mode acts as an ordinary transfer NE and the message transfer is realized at the network layer.

Follow certain planning guidelines when you plan IP over DCC.
NOTE
This section describes the planning guidelines of IP over DCC and the difference between HWECC and IP over DCC. For the shared parts, such as the planning of external DCN, NE IDs, and network division, see 3.7 Planning Guidelines in HWECC solution.

l l It is recommended that the GNE be the closest NE to the NMS, the central node of a start network, or the NE that accesses most DCCs. With the DCN bandwidth of 192 kbit/s, it is recommended that an ECC subnet (consisting of a GNE and the non-GNEs affiliated to the GNE) has not more than 120 NEs. The maximum number of NEs on an ECC subnet is 150 (only for the OptiX RTN 620 V100R005).
Planning Guidelines for DCCs

l l If a network is comprised of the OptiX equipment only, D1-D3 bytes are used for DCCs on SDH lines. If the OptiX equipment is connected to the third-party equipment through SDH lines, it is recommended that you adopt the DCC bytes used by the third-party equipment (D1-D3 or D4-D12) for DCCs.
Issue 05 (2010-10-30)
l l
In PDH microwave frames, one or three DCC bytes are used for DCCs. In Hybrid microwave frames, three DCC bytes are used for DCCs.
Planning Guidelines for IP Addresses of NEs

l l l l l l Set the IP addresses of NEs for the most simplified route settings. Set the IP addresses of GNEs, subnet masks, and default GNEs as required by the planning of external DCN. Set the IP addresses on the same network segment for the NEs connected through Ethernet NM interfaces. It is recommended that the IP addresses of a GNE and the NEs afflicted to the GNE be on different network segments. It is recommended that when an NE is connected to the third-party equipment through the Ethernet NM interface, this NE and the other NEs be on different network segments. Set the subnet masks of one network segment to the same value.
Planning Guidelines for Routes

l l l l One OSPF area has a maximum of 64 NEs. The route planning achieves communication between the NMS and GNEs, GNEs and nonGNEs, and the third-party NMS and third-party NEs. If the dynamic routing protocol fails to meet the preceding requirements, you need to plan appropriate static routes. If an NE is connected to the third-party equipment through Ethernet NM interfaces but the third-party equipment does not support GNEs or static routes, enable the ARP proxy function on the NE.
Planning of NE IPs and Routes in Typical Networking Conditions

l On a network that consists of the OptiX equipment and has only one OSPF area Figure 3-6 shows a network that consists of the OptiX equipment and has only one OSPF area. In this example, the IP addresses of GNEs and non-GNEs are on different network segments. Therefore, the NMS has a direct access to non-GNEs when GNEs have a route to the NMS or the network segment of the NMS. To achieve the direct access from a GNE to a non-GNE, you need to set a static route from the GNE to the network segment of the non-GNE (129.9.0.0). The GNE has the IP address of NE1. Figure 3-6 Planning Example of NE IPs and Routes on a Network That Consists Of the OptiX Equipment and Has Only One OSPF Area
NE 1 NMS NE 2
NE 3
130.9.0.100
130.9.0.1
129.9.0.2
129.9.0.3
Ethernet link
Radio link
3-12
Issue 05 (2010-10-30)
Analyze the routes as follows: There are routes between NE1, NE2, and NE3, because these NEs are in the same OSPF area. NE1 has a route to the network segment of 130.9.0.0 and spreads the route information in the OSPF area. Therefore, NE2 and NE3 have a route to this network segment and can access the NMS. When the NMS attempts to access NE2 and NE3, it forwards packets to NE1 through a static route. Then, NE1 forwards the packets to NE2 and NE3 along the OSPF routes.
NOTE
l If the NMS need not access non-GNEs directly, NE1, the NMS, and non-GNEs can be on the same network segment. l If NE1, the NMS, NE2, and NE3 are on the same network segment of 129.9.0.0, and the Ethernet NM interface on NE3 is connected to other equipment (that is, the interface is in "link up" state), the IP address of the GNE that manages the route from NE3 to 129.9.0.0 is changed to 129.0.3. That is, the route is changed to the local route through the Ethernet NM interface. In this case, NE3 cannot communicate with the NMS directly. To solve this problem, add a static route from NE1 to the NMS.
On a network that consists of various equipment and has only one OSPF area Figure 3-7 shows a network that consists of various equipment and has only one OSPF area. In this example, GNEs, non-GNEs, and the NEs interconnected with the third-party equipment are on different network segments. To achieve communication between the third-party NMS and a third-party GNE, a static route needs to be set between the network segments of the third-party NMS and the third-party GNE. In this example, the configuration of static routes is as follows: On the third-party NMS, configure a static route to 131.9.0.0 (the IP address of the GNE is 130.9.0.1). On NE4, configure a static route to 130.9.0.0 (the IP address of the GNE is 131.9.0.3).
Figure 3-7 Planning Example of NE IPs and Routes on a Network That Consists Of Various Equipment and Has Only One OSPF Area
NMS NE 1 130.9.0.100 NE 2 NE 3 NE 4 NE 5
Third party NMS 130.9.0.1 130.9.0.200
129.9.0.2
131.9.0.3
131.9.0.4
131.9.0.5
Third party equipment Radio link
Analyze the routes as follows:

There are routes between NE1, NE2, and NE3, because these NEs are in the same OSPF area. NE1 has a route to the network segment of 130.9.0.0 and spreads the route information in the OSPF area. Therefore, NE2 and NE3 have a route to this network segment and can access the NMS. NE3 has a route to the network segment of 131.9.0.0 and spreads the route information in the OSPF area. Therefore, NE1 and NE2 have a route to this network segment; NE1, NE2, and NE3 can access NE4. When the third-party NMS attempts to access NE4, it forwards packets to NE1 through a static route. Then, NE1 forwards the packets to NE3 through the OSPF routes, and NE3 forwards the packets to NE4. When NE4 attempts to access the third-party NMS, it forwards packets to NE3 through a static route. Then, NE3 forwards the packets to NE1 through the OSPF routes, and NE1 forwards the packets to the third-party NMS. l On a network that consists of various equipment and has multiple OSPF areas Figure 3-8 shows a network that consists of various equipment and has multiple OSPF areas. In this example, NE3 and NE4 are connected through Ethernet NM interfaces. The OSPF protocol is disabled on Ethernet NM interfaces by default. Therefore, the OptiX Equipment is divided into two OptiX areas. To avoid the configuration of too many static routes, the non-GNEs in different areas and the NEs with Ethernet NM interface connections are allocated with IP addresses on different segments. Therefore, you only need to set a static route from the third-party NMS to a third-party GNE and a static route between the two NEs connecting two OSPF areas. In this example, the configuration of static routes is as follows: On the third-party NMS, configure a static route to the network segment of 133.9.0.0 (the IP address of the GNE is 130.9.0.1). On NE7, configure a static route to 130.9.0.0 (the IP address of the GNE is 133.9.0.6). On NE3, configure a static route to 132.9.0.0 and a static route to 133.9.0.0 (the IP address of the GNE is 131.9.0.4). On NE4, configure a static route to 129.9.0.0 and a static route to 130.9.0.0 (the IP address of the GNE is 131.9.0.3).
3-14
Issue 05 (2010-10-30)
Figure 3-8 Planning Example of NE IPs and Routes on a Network That Consists Of Various Equipment and Has Multiple OSPF Areas
NE 3 NE 2 NMS NE 1
130.9.0.100 129.9.0.2 130.9.0.3 Third party NMS
131.9.0.3
130.9.0.200 NE 4 NE 5 NE 6 NE 7 NE 8
131.9.0.4
132.9.0.5
133.9.0.6
133.9.0.7
133.9.0.8
Third party equipment Radio link
Analyze the routes as follows: There are routes between NE1, NE2, and NE3, because these NEs are in the same OSPF area. Therefore, there are routes between NE4, NE5, and NE6. NE3 has routes to NE4, NE5, NE6, and N7, and spreads the information in the OSPF area. Therefore, NE1 and NE2 also have routes to NE4, NE5, and NE6. NE4 has routes to NE1, NE2, and NE3, and spreads the information in the OSPF area. Therefore, NE5 and NE6 also have routes to NE1, NE2, and NE3. The NMS has an access to each NE through GNEs because all NEs can communicate with one another. When the third-party NMS attempts to access NE7, it forwards packets to NE1 through a static route. Then, the packets are forwarded from NE1 to NE6, and finally reaches NE7. When the NE7 attempts to access the third-party NMS, it forwards packets to NE6 through a static route. Then, the packets are forwarded from NE6 to NE1, and finally reaches the third-party NMS.
NOTE
If the OSPF function is enabled on the Ethernet NM interfaces of NE3 and NE4, NE1-NE6 are in the same OSPF area. Therefore, the IP addresses and routes can be planned in a manner similar to Figure 3-7.
Issue 05 (2010-10-30)
3-15

The configuration of the IP over DCC solution consists of two parts, that is, the configuration of communications data at the near end of the NE and the creation of the NE on the NMS. Table 3-3 Configuration flow for the IP over DCC solution Step 1 Operation A.1.5 Changing NE IDs Description Required. Set the parameters as follows: l Set ID to be the NE ID specified during the DCN planning. l If the extended NE ID specified during the DCN planning is required, change Extended ID. 2 A.3.1 Setting NE Communication Parameters Required. Set the parameters as follows: l Set IP and Subnet Mask according to the planning of the external DCN. l Set Gateway IP Address if the default GNE needs to be configured for the non-GNEs. 3 A.3.2 Configuring DCCs Required. Set the parameters as follows: l Set Protocol Type of the SDH line port and microwave port on which the IP over DCC is enabled to TCP/IP. l Set Channel Type of the SDH line port to be consistent with that of the third-party equipment if the SDH line is used to connect the third-party equipment. l Adopt the default values for the other parameters. 4 A.3.7 Enabling the ARP Proxy When the third-party NMS and the third-party GNE are in the same network segment, if the third-party NMS does not support the setting of the static route and is in the same network segment as the OptiX GNE is, the proxy ARP is enabled on the OptiX GNE; if the third-party GNE does not support the setting of the static route and is connected to the OptiX NE through the Ethernet NMS interface, the proxy ARP is enabled on the OptiX NE that is connected to the third-party GNE. Required when the OSPF protocol needs to be used between the NE and the third-party equipment. The values of the parameters are consistent with those of the third-party equipment. In the other cases, all the parameters take the default values.
A.3.6 Setting Parameters of the OSPF Protocol
3-16
Issue 05 (2010-10-30)
Step 6 7
Operation A.3.5 Creating Static IP Routes A.3.3 Configuring the Extended ECC
Description Configure the static routes of NEs according to the network planning. Required for the NEs that are connected through the Ethernet NMS interface or the subtending ports. Set the parameters as follows: l Set Extended Mode to Specified Mode. l Adopt the default values for the other parameters.
NOTE This operation is performed to disable the automatic extended ECC function of the NE.
In the other cases, all the parameters take the default values. 8 A.3.11 Querying IP Routes In normal situations: l NEs have correct routes to other OptiX NEs or network segments in which the OptiX NEs are. l NEs have correct routes to the third-party GNEs or network segments in which the NEs are. l NEs have correct routes to the OptiX NMS or network segment in which the OptiX NMS is. l NEs have correct routes to the third-party NMS or network segment in which the third-party NMS is. 9 Creating NEs on the centralize d NMS A.1.2 Creating NEs by Using the Manual Method A.1.1 Creating NEs by Using the Search Method It is recommended that you perform the operations to add one or more NEs on a large existing network by using the Web LCT.
In other cases, this method is preferred.
NOTE
If the centralized NMS is U2000 instead of Web LCT, the NEs need to be created on the U2000. For the information on how to create NEs on the U2000, see Feature Description (U2000).

This section uses an example to describe how to plan and configure the IP over DCC solution according to network conditions.
3.9.1 Networking Diagram This section describes the networking information about the NEs. 3.9.2 Service Planning The service planning information contains all the parameter information required for configuring the NE data. 3.9.3 Configuration Process This section describes the procedure of data configuration.

This section describes the networking information about the NEs. The OptiX radio transmission equipment and the third-party wireless transmission equipment form the microwave transmission network, as shown in Figure 3-9. On the microwave transmission network, the third-party equipment is located at the edge and the OptiX equipment is located in the center. The OptiX equipment needs to transparently transmit the NM messages between the third-party equipment at the edge of the network and the third-party NMS in the center of the network. Figure 3-9 Networking diagram
NE8 NE7 Third-party NMS NE6 NE5 NE4
NE3
NMS
NE1 Third-party equipment
NE2
OptiX equipment
Router Radio link
LAN sw itch Ethernet link

The service planning information contains all the parameter information required for configuring the NE data. l The third-party equipment supports the connection to the NMS through the Ethernet NMS interface. Therefore, the OptiX equipment can transparently transmit the NM messages
3-18
between the third-party equipment and the third-party NMS through the IP over DCC solution. l l Select NE1 that is the closest to the NMS as the GNE. The OptiX NMS and NE1 are located at the same place and the third-party NMS is located at another place. Therefore, construct the DCN between the third-party NMS and NE1 through a router or protocol converter. Allocate IDs and IP addresses for all the NEs according to the conditions of the network. Figure 3-10 Allocation of IDs/IP addresses for all the NEs
132.9.0.7/16 11.0.0.200/16 9-6 132.9.0.6 0.0.0.0
132.9.0.8/16 9-5 131.9.0.5 0.0.0.0 9-4 130.9.0.4 0.0.0.0 9-3 130.9.0.3 0.0.0.0
11.0.0.100/16
10.0.0.200/16 9-1 10.0.0.1 0.0.0.0 10.0.0.100/16 Extended ID-Basic ID IP address Gatew ay 9-2 129.9.0.2 0.0.0.0
Plan NE routes. Configure a static route between NE1 and the third-party NMS (11.0.0.100). The gateway is the interface address of the router 10.0.0.200. Configure a static route between NE3 and the network segment 131.9.0.0. The gateway is the IP address of NE4 130.9.0.4. Configure a static route between NE3 and the network segment 132.9.0.0. The gateway is the IP address of NE4 130.9.0.4. Configure a static route between NE4 and the network segment 129.9.0.0. The gateway is the IP address of NE3 130.9.0.3. Configure a static route between NE4 and the network segment 10.0.0.0. The gateway is the IP address of NE3 130.9.0.3. Configure a static route between NE4 and the third-party NMS (11.0.0.100). The gateway is the IP address of NE3 130.9.0.3.

Issue 05 (2010-10-30)
3-19
Context
NOTE
In this configuration example, only the configuration information about the typical NEs, NE1, NE3, and NE4 is provided.
Procedure
Step 1 See A.1.5 Changing NE IDs and modify the NE ID. The values for the related parameters are provided as follows. Parameter Value Range NE1 New ID New Extended ID 1 9 (default value) NE3 3 9 (default value) NE4 4 9 (default value)
Step 2 See A.3.1 Setting NE Communication Parameters and set the NE communication parameters. The values for the related parameters are provided as follows. Parameter Value Range NE1 IP Address Gateway IP Address Subnet Mask 10.0.0.1 0.0.0.0 (default value) 255.255.0.0 (default value) NE3 130.9.0.3 0.0.0.0 (default value) 255.255.0.0 (default value) NE4 130.9.0.4 0.0.0.0 (default value) 255.255.0.0 (default value)
Step 3 See A.3.2 Configuring DCCs and configure the DCCs. The values for the related parameters are provided as follows. Parameter Value Range All Microwave/ Line Ports (NE1) Enabled/Disabled Enabled (default value) All Microwave/ Line Ports (NE3) Enabled (default value) All Microwave/ Line Ports (NE4) Enabled (default value)
3-20
Issue 05 (2010-10-30)
Parameter
Value Range All Microwave/ Line Ports (NE1) All Microwave/ Line Ports (NE3) D1 (default value of the PDH microwave port whose capacity is smaller than 16 E1s) D1-D3 (default values of other line ports) TCP/IP All Microwave/ Line Ports (NE4) D1 (default value of the PDH microwave port whose capacity is smaller than 16 E1s) D1-D3 (default values of other line ports) TCP/IP
Channel Type
D1 (default value of the PDH microwave port whose capacity is smaller than 16 E1s) D1-D3 (default values of other line ports)
Protocol Type
TCP/IP
Step 4 See A.3.5 Creating Static IP Routes and create the static IP routes. The values for the related parameters are provided as follows. Paramete r Destinatio n Address Subnet Mask Gateway IP Address Value Range NE1 11.0.0.100 255.255.0. 0 10.0.0.200 NE3 131.9.0.0 255.255.0. 0 130.9.0.4 132.9.0.0 255.255.0. 0 130.9.0.4 NE4 129.9.0.0 255.255.0. 0 130.9.0.3 10.0.0.0 255.255.0. 0 130.9.0.3 11.0.0.100 255.255.0. 0 130.9.0.3
Step 5 See A.3.3 Configuring the Extended ECC and configure the extended ECC. The values for the related parameters are provided as follows. Parameter Value Range NE1 ECC Extended Mode Port (on the server side) Opposite IP (on the client side) Port (on the client side) Specified mode 1601 (default value) 0.0.0.0 (default value) 1601 (default value) NE3 Specified mode 1601 (default value) 0.0.0.0 (default value) 1601 (default value) NE4 Specified mode 1601 (default value) 0.0.0.0 (default value) 1601 (default value)
Issue 05 (2010-10-30)
3-21
Step 6 See A.3.11 Querying IP Routes and query the ECC routes. The expected result is as follows: l On NE1, The route and gateway between NE1 and 129.9.0.2, 130.9.0.3, 130.9.0.0, 131.9.0.0, and 132.9.0.0 are 129.9.0.2. The route and gateway between NE1 and 10.0.0.0 are 10.0.0.1. The route and gateway between NE1 and 11.0.0.100 are 10.0.0.200. l On NE3, The route and gateway between NE3 and 131.9.0.0 and 132.9.0.0 are 130.9.0.4. The route and gateway between NE3 and 130.9.0.0 are 130.9.0.3. The route and gateway between NE3 and 129.9.0.2, 10.0.0.1, 10.0.0.0, and 11.0.0.100 are 129.9.0.2. l On NE4, The route and gateway between NE4 and 131.9.0.0 and 132.9.0.0 are 131.9.0.5. The route and gateway between NE4 and 130.9.0.0 are 130.9.0.4. The route and gateway between NE4 and 129.9.0.0, 10.0.0.0, 10.0.0.1, and 11.0.0.100 are 130.9.0.3. Step 7 See A.1.1 Creating NEs by Using the Search Method and create the NEs on the centralized NMS. 10.0.0.1 is the search network segment of the IP address of the GNE. In normal cases, all the NEs can be created on the centralized NMS. ----End
Follow-up Procedure
To ensure the interconnection between the third-party NMS and the third-party GNE, the following routes need to be added. l l Route between the third-party NMS and the network segment 132.9.0.0. The gateway is 11.0.0.200. Route between NE7 and the network segment 11.0.0.100. The gateway is 132.9.0.6.

This section provides the hyperlinks of the operation tasks associated with the IP over DCC feature.
Related Tasks
A.1.1 Creating NEs by Using the Search Method A.1.2 Creating NEs by Using the Manual Method A.1.5 Changing NE IDs A.3.1 Setting NE Communication Parameters A.3.2 Configuring DCCs
A.3.5 Creating Static IP Routes A.3.6 Setting Parameters of the OSPF Protocol A.3.7 Enabling the ARP Proxy A.3.11 Querying IP Routes A.3.3 Configuring the Extended ECC

The IP over DCC solution does not involve any alarm or event.
3.12 FAQs
This section provides the answers to the questions that are frequently raised when the IP over DCC solution is used. Q: Compared with other solutions for communicating NM information, what advantages does the IP over DCC solution have? A: Main advantages are as follows: l The IP over DCC solution applies the standard TCP/IP protocol stack. With the IP over DCC solution, the OptiX equipment easily interworks with third-party equipment and hence the network management is simplified. The OSI over DCC solution applies the transfer function of the network layer of the protocol stack. Hence, no extra overhead and service channel are needed. The IP over DCC solution allows different vendors to multiplex the same DCC channel. The NMS of a vendor need not be directly connected to the equipment of the vendor. The IP over DCC function supports the automatic rerouting function and hence can protect the channel that transmits the management information. The IP over DCC solution enables the development of management tools that are based on the mature IP protocol stack, for example, FTP and Telnet.
l l l l l
Q: Why does the NMS always fail to log in to an NE? A: Common causes are as follows: l l The communication connection between the NMS and the GNE is faulty. To locate the fault, run the ping or tracert command on the NMS server. The IP route between the gateway NE and a non-gateway NE is faulty. To locate the fault, check the IP route between the gateway NE and the non-gateway NE. Q: How does one use the IP over DCC solution to interconnect the OptiX equipment with third-party equipment through the SDH line? A: The steps are as follows: 1. 2.
Issue 05 (2010-10-30)
Check the DCC bytes used by DCCs with the maintenance staff of third-party equipment. Check the PPP protocol parameters with the maintenance staff of third-party equipment.
3. 4. 5.
Check the OSPF protocol parameters with the maintenance staff of third-party equipment. Configure data according to the negotiated protocol parameters and the network planning. Query IP routes at the NE that is interconnected to third-party equipment to check if there is a route to the interconnected NE. If no route is obtained, the PPP interconnection fails. Query IP routes at the gateway NE to check if there is a route to the interconnected NE and a route to other third-party equipment. If no route is obtained, the OSPF protocol interconnection fails.
6.
3-24
Issue 05 (2010-10-30)
4 OSI over DCC Solution
4
About This Chapter
OSI over DCC Solution
This chapter describes the OSI over DCC solution. 4.1 Introduction This section provides the definition of OSI over DCC and describes its purpose. 4.2 Basic Concepts This section describes the basic concepts that you should be familiar with before using OSI over DCC. 4.3 Specifications This section describes the specifications of OSI over DCC. 4.4 Reference Standards and Protocols This section describes the standards and protocols associated with OSI over DCC. 4.5 Availability This section describes the support required by the application of the OSI over DCC solution and its dependency. 4.6 Principles This section describes the principles of the OSI over DCC solution. 4.7 Planning Guidelines Follow certain planning guidelines when you plan OSI over DCC. 4.8 Configuration Flow The configuration of the OSI over DCC solution consists of two parts, that is, the configuration communications data at the peer end of the NE and the creation of the NE on the NMS. 4.9 Configuration Example This section uses an example to describe how to plan and configure the OSI over DCC solution according to network conditions. 4.10 Task Collection This section provides the hyperlinks of the operation tasks associated with the OSI over DCC feature. 4.11 Relevant Alarms and Events
The OSI over DCC solution does not involve any alarm or event. 4.12 FAQs This section provides the answers to the questions that are frequently raised when the OSI over DCC solution is used.
4-2
Issue 05 (2010-10-30)
4.1 Introduction
This section provides the definition of OSI over DCC and describes its purpose.
Definition
OSI over DCC is a DCN solution provided by Huawei. In this solution, the NMS manages NEs by using network management messages that are encapsulated in the standard OSI protocol stack. Figure 4-1 shows how network management messages are transmitted by using OSI over DCC. Different manufacturers' network management messages encapsulated in the OSI protocol stack can be transmitted through DCCs carried by optical fibers or microwave, or can be transmitted over the Ethernet between Ethernet NM interfaces or between NE cascading interfaces Figure 4-1 Networking diagram of OSI over DCC
sg yM art ack -p t 3rd SI s C O DC
3rd-party Msg OSI stack ETH Third-party NMS
sg XM pti stack O I OS CC D
3rd-party Msg OSI stack DCC
OptiX NMS
OptiX Msg OSI stack ETH
OptiX M sg OSI sta ck DCC
3rd-party Msg OSI stack ETH
3rd-part y Msg OSI sta ck DCC
OptiX equipment Ethernet link Fiber
Purpose
OSI over DCC is preferred as the DCN solution when the network is comprised of the OptiX equipment and the third-party equipment that supports OSI over DCC but does not support IP over DCC. In addition, this solution can be used when the equipment in the center of the network needs to provide a network management message transmission path over OSI for NEs at the edge of the network.
4.2 Basic Concepts

This section describes the basic concepts that you should be familiar with before using OSI over DCC.
4.2.1 OSI over DCC Protocol Stack The OSI over DCC adopts the architecture of the standard OSI protocol stack. 4.2.2 NMS Access Modes In the OSI over DCC solution, there are two modes for the NMS to access an NE: gateway access mode and direct access mode.
4.2.1 OSI over DCC Protocol Stack

The OSI over DCC adopts the architecture of the standard OSI protocol stack.
Protocol Stack Architecture

Figure 4-2 OSI over DCC protocol stack architecture
Transport layer Network layer Data link layer Ethernet Physical layer DCC TP4 IS-IS/ES-IS/CLNP LAPD
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 categories: l DCC DCCs use the DCC bytes in SDH frames, PDH or Hybrid microwave frames as the channels for communication between NEs. In the OSI over DCC solution: If the network is only comprised of the OptiX equipment, bytes D1 to D3 in SDH frames are used as DCCs. If the OptiX equipment is connected to the third-party equipment by using the SDH line, it is recommended that you use the DCC bytes that the third-party equipment uses (for example, bytes D1 to D3 or D4 to D12) as DCCs. In the PDH microwave frame, one or three DCC bytes in the frame can always be used as DCCs. In the Hybrid microwave frame, three DCC bytes in the frame can always be used as DCCs. l Ethernet physical channel The NE provides the Ethernet physical channel through the Ethernet NM port or the NE cascade port.
Data Link Layer

The main function of the data link layer is to provide reliable data transmission on physical links. For DCCs, the NE applies 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 are required to set the LAPD role. For the two ends of a DCC, set the LAPD role to network at one end and to user at the other end.
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 applies 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. Its address format is as shown in Figure 4-3. Figure 4-3 Format of the NSAP address
IDP Higher order DSP AFI IDI+pad DFI ORG RES RD Area System ID 9 10 11 12 13 14 15 16 17 18 19
NSEL
DSP
Area address 1 2 3 4 5 6 7 8
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 4-3 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. SYS ID The SYS ID refers to the system ID shown in Figure 4-3 and has six bytes. The SYS ID is used to address the routes within an area. The value of the first three bytes of the SYS 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 one IS and another. It complies with ISO 10589 and functions as the OSPF protocol in the TCP/IP protocol stack. The ISIS protocol supports the L1 and L2 layered routes. The NE whose role is L1 cannot be a neighbor of the NE in a different area and participates 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 also can participate 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). In the network as shown in Figure 4-4, 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 4-4 Layered routes of IS-IS protocol routes (L2 not consecutive)
OSI DCN T2000
L1 L2
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. In general, 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.
4-6
Issue 05 (2010-10-30)
Transport Layer
The main function of the transport layer is to provide the end-to-end communication service for the upper layer. The NE applies 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.
OSI Tunnel
This solution is used when the transmission network that adopts the OSI over DCC solution needs to use the transmission network that adopts the IP over DCC solution to transparently transmit the NM message. The OSI tunnel function involves that a virtual LAPD channel is established between the NEs on the IP network. In this manner, the NM message encapsulated in compliance with the OSI protocol is transparently transmitted. Figure 4-5 shows an application example of the OSI tunnel. In this example, the third-party equipment adopts the OSI over DCC solution and needs to pass the service through the OptiX transmission network that adopts the IP over DCC solution Hence, an OSI tunnel needs to be established between NE1 and NE3. Perform the following steps to delete the VLAN service: l Note that the SDH line connecting the OptiX equipment to the third-party equipment adopts the DCC over OSI protocol, whereas the SDH line and radio link inside the network adopt the IP over DCC protocol. Enable the OSI tunnel function on NE1. The IP address of the opposite NE is the IP address of NE3 (that is, 129.9.0.3). The LAPD role is "network". Enable the OSI tunnel function on NE3. The IP address of the opposite NE is the IP address of NE1 (that is, 129.9.0.1). The LAPD role is "user".
l l
Figure 4-5 Application example of the OSI tunnel

OSI tunnel enabled NE 1 NE 2 OSI tunnel enabled NE 3
129.9.0.1 129.9.0.2
129.9.0.3
Third-party NMS
Third-party equipment Radio link Fiber
Issue 05 (2010-10-30)
4-7

NOTE
The LAPD roles of NE1 and NE3 can be exchanged but cannot be the same.
4.2.2 NMS Access Modes

In the OSI over DCC solution, there are two modes for the NMS to access an NE: gateway access mode and direct access mode.
Gateway Access Mode

In the gateway access mode, 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. The core routing table synthesizes the transport layer routing tables of all communication protocol stacks. Each route item includes the following: l l l l ID of the destination NE Address of the transfer NE Communication protocol stack of the transfer NE Transfer distance
Direct Access Mode

In the direct access mode, the NMS 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: l l l Destination System ID Cost Adjacency No.
Each route item in the L2 routing table includes the following: l l l 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, theoretically, the NMS can access any NE using the direct access mode, that is, the NMS can consider any NE as the gateway NE. To improve the communication efficiency, there should not be too many NEs that are accessed in the direct access mode in a network.
4.3 Specifications
This section describes the specifications of OSI over DCC.
The OptiX RTN 620 supports the following specifications of OSI over DCC. Table 4-1 Specifications of OSI over DCC Item Number of DCCs Specifications The number of DCCs is determined by the microwave/line type. l STM-1/STM-4 or SDH radio supports 12 DCC bytes, that is, D1-D12. The equipment supports three modes: D1-D3, D4-D12, and D1-D12. l When transmitting 16xE1 signals or higher-capacity PDH microwave signals, the IF1A/B board always uses Huaweidefined bytes D1-D3 as DCCs. l When transmitting PDH microwave signals less than 16xE1 signals, the IF1A/ B board always uses Huawei-defined byte D1 as the DCC channel. l The IF0A/B board always uses Huaweidefined bytes D1-D3 as DCCs. l When transmitting Hybrid microwave signals, the IFH2 board uses Huaweidefined bytes D1-D3 as DCCs. CLNP protocol Supported The NE uses the simplified NSAP address. IS-IS routing protocol Supported The CLNS role of the NE can be set to L1 or L2. The default mode is L1. ES-IS routing protocol OSI tunnel Number of NEs on the DCN Supported Supported l It is recommended that the number of areas does not exceed 20. The maximum number of areas can be 32. l It is recommended that the number of NEs in an area does not exceed 32. The maximum number of NEs in an area is 50. l With the DCN bandwidth of 192 kbit/s, it is recommended that an ECC subnet has not more than 120 NEs. The maximum number of NEs on an ECC subnet is 150 (only for the OptiX RTN 620 V100R005).
Issue 05 (2010-10-30)
4-9

This section describes the standards and protocols associated with OSI over DCC. The following standards and protocols are associated with OSI over DCC: l ISO 8473: Information technology-Protocol for providing the connectionless-mode network service: Protocol specification
4.5 Availability
This section describes the support required by the application of the OSI over DCC solution and its dependency.

Table 4-2 Hardware and version support Feature OSI over DCC Applicable Board SCC IF1A/IF1B IF0A/IF0B IFX IFH2 SL1/SD1 SLE/SDE SL4 Applicable Hardware Version All the versions All the versions All the versions All the versions All the versions All the versions All the versions All the versions Applicable Product Version V100R001 and later V100R001 and later V100R002 and later V100R002 and later V100R003 and later V100R001 and later V100R001 and later V100R002 and later
Feature Dependency
When the OSI over DCC solution is used with other DCN solutions, pay attention to the relations between the OSI over DCC and other DCN solutions. l l l The OSI protocol stack of NEs can communicate with the HWECC protocol stack only in the same area at the L1 layer. The OSI protocol stack of NEs cannot communicate with the IP over DCC protocol stack. If DCC bytes are used to transparently transmit NM messages when the OptiX equipment is used together with third-party equipment to form a network, you can adopt the OSI protocol to manage the OptiX equipment, but it is recommended that you use the HWECC protocol. If DCC bytes are used to transparently transmit NM messages through the external clock interface when the OptiX equipment is used together with third-party equipment to form a
4-10
network, you can adopt the OSI protocol to manage the OptiX equipment, but it is recommended that you use the HWECC protocol. l If the protocol manager is used to transparently transmit NM messages, you can adopt the OSI protocol to manage the OptiX equipment, but it is recommended that you use the HWECC protocol.
4.6 Principles
This section describes the principles of the OSI over DCC solution.
Gateway Mode
Figure 4-6illustrates how the OSI over DCC solution transfers NMS messages to a non-gateway NE when the NMS adopts the gateway mode to access the NE. Figure 4-6 Realization principle of message transferring (gateway mode)
Application TP4 ES-IS/CLNP Application TP4 TP4 IS-IS/CLNP LAPD DCC Transfer NE Application TP4 IS-IS/CLNP LAPD DCC Destination NE
ES-IS/CLNP IS-IS/CLNP LAPD
Ethernet
Ethernet DCC
T2000
Gateway NE
The realization principle is as follows: 1. As an ES, the NMS 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. The gateway NE extracts the messages from the OSI protocol stack and reports the messages to the application layer. 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 application 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 4-6 is OSI, the gateway NE transfers the messages to the transfer NE through the OSI protocol stack. After receiving the packet that encapsulates the messages, the network layer of the transfer 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. After receiving the packet, the network layer of the destination NE reports the packet to the application layer through the transport layer because the destination NSAP address of
2. 3.
4.
5.
Issue 05 (2010-10-30)
the packet is the same as the address of the local station. The application layer acts according to the message sent from the NMS.
Direct Connection Mode

Figure 4-7 illustrates how the OSI over DCC solution transfers NMS messages to a destination NE when the NMS adopts the direct connection mode to access the NE. Figure 4-7 Realization principle of message transferring (direct connection mode)
Application TP4 ES-IS/CLNP IS-IS/ES-IS/CLNP LAPD Ethernet Ethernet DCC T2000 Transfer NE DCC Transfer NE DCC Destination NE IS-IS/CLNP LAPD Application TP4 IS-IS/CLNP LAPD
The original gateway NE in the direct connection mode acts as an ordinary transfer NE and the message transferring is realized at the network layer. This is different from the gateway mode.

Follow certain planning guidelines when you plan OSI over DCC.
NOTE
This section describes the planning guidelines of OSI over DCC and the difference between HWECC and OSI over DCC. For the shared parts, such as the planning of NE IDs and network division, see 2.7 Planning Guidelines in HWECC solution.
Planning Guidelines for Areas

l l l l It is recommended that the number of areas does not exceed 20. The maximum number of areas is 32. It is recommended that the number of NEs in an area does not exceed 32. The maximum number of NEs in an area is 50. Each area should have L2 NEs and all the L2 NEs must be interconnected. The area ID of each area must be unique.

l l If there are multiple areas, set a gateway NE for each area, and an L2 NE is preferred to be a gateway NE. With the DCN bandwidth of 192 kbit/s, it is recommended that an ECC subnet (consisting of a GNE and the non-GNEs affiliated to the GNE) has not more than 120 NEs. The
4-12
maximum number of NEs on an ECC subnet is 150 (only for the OptiX RTN 620 V100R005). l It is recommended that the selected GNE be the closest NE to the NMS, the central node of a start network, or the NE that accesses most DCCs.
Planning Guidelines for External DCN

l l l l For stability and security of external DCN, it is recommended that you do not use the office LAN or Internet as the transmission channels of external DCN. It is recommended that the bandwidth of external DCN should not be lower than the DCC bandwidth on the network. The links at a rate of 256 kbit/s already meets the requirements. Routers on external DCN must support the OSI protocol stack. It is recommended that the channels of external DCN be provided by other networks (not a monitored network). If external DCN uses the channels provided by the data processing board, consider the risk when external DCN uses the service channels provided by a monitored network. Active and standby DCN routes or GNEs should be provided for external DCN.

l If the OptiX equipment is connected to the third-party equipment through SDH lines, it is recommended that you adopt the DCC bytes used by the third-party equipment (for example, D1-D3 or D4-D12) for DCCs. In PDH microwave frames, one or three DCC bytes are used for DCCs. In Hybrid microwave frames, three DCC bytes are used for DCCs. In the case of one LAPD link, it is recommended that you set the LAPD role to "network" for the NE closer to the NMS, and set the LAPD role to "user" for the NE further from the NMS.
l l l

The configuration of the OSI over DCC solution consists of two parts, that is, the configuration communications data at the peer end of the NE and the creation of the NE on the NMS. Table 4-3 Configuration flow for the OSI over DCC solution Step 1 Operation A.1.5 Changing NE IDs Description Required. Set the parameters as follows: l Set ID to be the NE ID specified during the DCN planning. l If the extended NE ID specified during the DCN planning is required, change Extended ID.
Issue 05 (2010-10-30)
4-13
Step 2
Operation A.3.1 Setting NE Communication Parameters
Description Required. Set the parameters as follows: l Set NSAP Address according to the external DCN planning. l Adopt the default values for the other parameters.
NOTE When setting NSAP Address, you need to set only the area ID, and the other parts are automatically generated by the NE.
A.3.2 Configuring DCCs
Required. Set the parameters as follows: l Set Protocol Type of the SDH line port and microwave port on which the OSI over DCC is enabled to OSI. l Set LAPD Role at the ends of an LAPD link to Network and User. l Set Channel Type of the SDH line port to be consistent with that of the third-party equipment if the SDH line is used to connect the third-party equipment. l Adopt the default values for the other parameters.
A.3.8 Configuring the CLNS Role
Required when the CLNS role of the NE is set to L2. Set the parameters as follows: l Set Configuration Role to L2. In the other cases, all the parameters take the default values.
NOTE By default, the CLNS role of the NE is set to L1.
A.3.9 Querying OSI Tunnel
When the third-party transmission network that adopts the OSI over DCC solution needs to use the OptiX transmission network that adopts the IP over DCC solution to transparently transmit the NM message, the OSI tunnel needs to be set on the passthrough node. Set the parameters as follows: l Set Opposite IP to the IP address of another pass-through node. l Set LAPD Actor of the two pass-through nodes to Network and User.
A.3.3 Configuring the Extended ECC
Required for the NEs that are connected through the Ethernet NMS interface or the subtending ports. Set the parameters as follows: l Set Extended Mode to Specified Mode. l Adopt the default values for the other parameters.
NOTE This operation is performed to disable the automatic extended ECC function of the NE.
4-14
Issue 05 (2010-10-30)
Step
Operation
Description In the other cases, all the parameters take the default values.
A.3.12 Querying OSI Routes
In normal situations: 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.
NOTE
The Web LCT does not support the management of NEs through the OSI protocol. Therefore, only the U2000 can be used as the centralized NMS. For the information on how to create NEs on the U2000, see Feature Description (U2000).

This section uses an example to describe how to plan and configure the OSI over DCC solution according to network conditions. 4.9.1 Networking Diagram This section describes the networking information about the NEs. 4.9.2 Service Planning The service planning information contains all the parameter information required for configuring the NE data. 4.9.3 Configuration Process This topic describes the procedure for the data configuration.

This section describes the networking information about the NEs. The OptiX wireless transmission equipment and the third-party wireless transmission equipment form the microwave transmission network, as shown in Figure 4-8. The total number of equipments on the network is more than 50. The third-party equipment supports only the OSI over DCC solution.
Issue 05 (2010-10-30)
4-15
Figure 4-8 Networking diagram
NE203 Third-party NMS OSI DCN Network cable NE201
NE204
NE103
NE101 NE102 NE202
OptiX equipment Network cable

The service planning information contains all the parameter information required for configuring the NE data. l The number of OptiX equipments and third-party equipments is more than 50. It is, however, recommended that the number of NEs in each area is equal to or smaller than 32. Therefore, the equipments are divided into two areas and four NEs on the bone network are selected as L2 NEs.
4-16
Issue 05 (2010-10-30)
Figure 4-9 Allocation of NE areas

AREA ID: 0x394F1200 Area 1
Third-party NMS L2 L2 L2 L2
OSI DCN NMS
AREA ID: 0x394F1190 Area 2
OptriX equipment Netw ork cable
l l l
Set the IDs of the NE101, NE102, and NE103 to 101, 102, and 103. Select NE101 that is the closest to the NMS as the GNE. DCC planning The third-party equipment uses D1-D3 bytes as the DCC channel. Therefore, the SDH line of the third-party equipment also uses D1-D3 bytes as the DCC channel. For an LAPD link, set the LAPD role of the NE that is the closest to the NMS to network and set the LAPD role at the other end to user.

This topic describes the procedure for the data configuration.
Context
NOTE
In this configuration example, only the configuration information about the typical NEs, NE101, NE102, and NE103 is provided.
Procedure
Step 1 See A.1.5 Changing NE IDs and modify the NE ID. The values for the related parameters are provided as follows.
Parameter
Value Range NE101 NE102 102 9 (default value) NE103 103 9 (default value)
101 9 (default value)
Step 2 See A.3.1 Setting NE Communication Parameters and set the NE communication parameters. The values for the related parameters are provided as follows. Parameter Value Range NE101 NSAP Address 394F1200 NE102 394F1200 NE103 394F1200
Step 3 See A.3.2 Configuring DCCs and configure the DCCs. The values for the related parameters are provided as follows. Parameter Value Range NE101 Enabled/Disabled Channel Type Enabled (default value) D1 (default value of the PDH microwave port whose capacity is smaller than 16 E1s) D1-D3 (default values of other line ports) Protocol Type LAPD Role OSI Network NE102 Enabled (default value) D1 (default value of the PDH microwave port whose capacity is smaller than 16 E1s) D1-D3 (default values of other line ports) OSI User (port that is connected to NE101) Network (port that is connected to other NEs) NE103 Enabled (default value) D1 (default value of the PDH microwave port whose capacity is smaller than 16 E1s) D1-D3 (default values of other line ports) OSI User (port that is connected to NE101)
Step 4 See A.3.8 Configuring the CLNS Role and configure the CLNS role. The values for the related parameters are provided as follows. Parameter Value Range NE101 Configuration Role
4-18
NE102 L2
NE103 L1 (default value)

Issue 05 (2010-10-30)
L2
Step 5 See A.3.3 Configuring the Extended ECC and configure the extended ECC. The values for the related parameters are provided as follows. Parameter Value Range NE103 ECC Extended Mode Port (on the server side) Opposite IP (on the client side) Port (on the client side) Specified mode 1601 (default value) 0.0.0.0 (default value) 1601 (default value)
Step 6 See A.3.12 Querying OSI Routes and query the OSI routes. The expected result is as follows: l On NE101, the routes of NE102 and NE103 can be viewed in the L1 routing table and the routes of NE102, NE201, and NE202 can be viewed in the L2 routing table. l On NE102, the routes of NE101 and NE103 can be viewed in the L1 routing table and the routes of NE101, NE201, and NE202 can be viewed in the L2 routing table. l On NE103, the routes of NE101 and NE103 can be viewed in the L1 routing table. ----End

This section provides the hyperlinks of the operation tasks associated with the OSI over DCC feature.
Related Tasks
A.1.1 Creating NEs by Using the Search Method A.1.2 Creating NEs by Using the Manual Method A.1.5 Changing NE IDs A.3.1 Setting NE Communication Parameters A.3.2 Configuring DCCs A.3.8 Configuring the CLNS Role A.3.9 Querying OSI Tunnel A.3.12 Querying OSI Routes A.3.3 Configuring the Extended ECC

The OSI over DCC solution does not involve any alarm or event.
Issue 05 (2010-10-30)
4-19
4.12 FAQs
This section provides the answers to the questions that are frequently raised when the OSI over DCC solution is used. Q: Compared with other solutions for communicating NM information, what advantages and disadvantages does the OSI over DCC solution have? A: The advantages are as follows: l The OSI over DCC solution applies the standard OSI protocol stack. With the OSI over DCC solution, the OptiX equipment easily interworks with third-party equipment and hence the network management is simplified. The OSI over DCC solution applies the transfer function of the network layer of the protocol stack. Hence, no extra overhead and service channel are needed. The OSI over DCC solution allows different vendors to multiplex the same physical channels. The NMS of a vendor need not be directly connected to the equipment of the vendor. The OSI over DCC function supports the automatic rerouting function and hence can protect the channel that transmits the management information.
l l l l
The disadvantages are as follows: l l The external DCN must use the router that supports the OSI protocol stack. In addition, the NM server need be installed with the OSI protocol stack software. The OSI network is not applied as wide as the TCP/IP network and there are not many OSIbased management tools.
Q: How does one use the OSI over DCC solution to interconnect the OptiX equipment with third-party equipment? A: The steps are as follows: 1. 2. 3. 4. 5. Check the DCC bytes used by DCCs with the maintenance staff of third-party equipment. Check the LAPD role and other LAPD parameters with the maintenance staff of third-party equipment. Check the protocol parameters of the network layer like the area ID in the NSAP address and the CLNS role with the maintenance staff of third-party equipment. Configure data according to the negotiated protocol parameters and the network planning. Query the link adjacency table at the NE that is interconnected to third-party equipment to check if there is an LAPD link to the interconnected NE. If no route is obtained, the LAPD protocol interconnection fails. 6. Query the OSI routes of the OptiX NE that is in the same area as third-party equipment to check if there are L1 routes to the interconnected NE and other third-party equipment. If third-party equipment is an L2 NE, it is necessary to query the OSI routes of the OptiX NE that is also an L2 NE to check if there is an L2 route to the third-party equipment. If no route is obtained, the interconnection of the network layer protocol fails.
5 DCC Transparent Transmission Solution
DCC Transparent Transmission Solution
About This Chapter

This chapter describes the DCC transparent transmission solution. 5.1 Introduction This section provides the definition of DCC transparent transmission and describes its purpose. 5.2 Specifications This section describes the specifications of DCC transparent transmission. 5.3 Availability This section describes the support required by the application of the DCC transparent transmission solution and its dependency. 5.4 Principles This section describes the principles of the DCC transparent transmission solution. 5.5 Planning Guidelines Follow certain planning guidelines when you plan DCC transparent transmission. 5.6 Configuration Procedure The configuration of the DCC transparent transmission solution consists of two parts, namely, the configuration of communications data at the near end and the creation of NEs on the NMS. 5.7 Configuration Example This section uses an example to describe how to plan and configure the DCC transparent transmission solution according to network conditions. 5.8 Task Collection This section provides the hyperlinks of the operation tasks associated with the DCC transparent transmission feature. 5.9 Relevant Alarms and Events The DCC transparent transmission solution does not involve any alarm or event. 5.10 FAQs This section provides the answers to the questions that are frequently raised when the DCC transparent transmission solution is used.
Issue 05 (2010-10-30)
5-1
5.1 Introduction
This section provides the definition of DCC transparent transmission and describes its purpose.
Definition
DCC transparent transmission is a DCN solution provided by Huawei. In this solution, different manufacturers' network management messages are translated by using different DCC bytes. In this manner, network management messages pass through a network that is composed of the OptiX equipment and the third-party SDH equipment. 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. In this networking scenario, there are two possibilities: 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 5-1 DCC transparent transmission solution when the OptiX equipment is at the edge of a network (1)
D4-D12
D4-D12 D4-D12
D4-D12
OptiX equipment
Third-party equipment
The third-party equipment uses bytes D4 to D12 as DCCs. 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.
5-2
Issue 05 (2010-10-30)
Figure 5-2 DCC transparent transmission solution when the OptiX equipment is at the edge of a network (2)
D1-D3
D1-D3 D1-D3
D1-D3
OptiX equipment
The OptiX equipment is in the center of a network. In this networking scenario, there are two possibilities: 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 D1 to D3.
Figure 5-3 DCC transparent transmission solution when the OptiX equipment is in the center of a network (1)
D1-D3 D1-D3
D1-D3 D1-D3
OptiX equipment
The third-party equipment uses bytes D4 to D12 as DCCs. 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.
Issue 05 (2010-10-30)
5-3
Figure 5-4 DCC transparent transmission solution when the OptiX equipment is in the center of a network (2)
D4-D12
D4-D12
D4-D12
D4-D12
OptiX equipment
Purpose
DCC transparent transmission is preferred as the DCN solution when the network is comprised of the OptiX equipment and the third-party SDH equipment that does not support IP over DCC or OSI over DCC.
5.2 Specifications
This section describes the specifications of DCC transparent transmission. The OptiX RTN 620 supports the following specifications of DCC transparent transmission. Table 5-1 Specifications of DCC transparent transmission Item Number of DCCs Specifications SDH radio supports 12 DCC bytes, that is, D1-D12. The equipment supports three modes: D1-D3, D4-D12, and D1-D12. An SDH path can transmit a channel of network management messages of the OptiX equipment and a channel of network management messages of the third-party equipment at the same time. l If the OptiX RTN 620 uses bytes D1-D3, the third-party equipment uses bytes D4D12 as DCCs. l If the OptiX RTN 620 uses bytes D4-D12, the third-party equipment uses bytes D1D3 as DCCs.
Capacity of DCC transparent transmission
5-4
Issue 05 (2010-10-30)
5.3 Availability
This section describes the support required by the application of the DCC transparent transmission solution and its dependency.

Table 5-2 Hardware and version support Feature DCC transparent transmission Applicable Board SCC IF1A/IF1B IFX SL1/SD1 SLE/SDE SL4 Applicable Hardware Version All the versions All the versions All the versions All the versions All the versions All the versions Applicable Product Version V100R001 and later V100R001 and later V100R002 and later V100R001 and later V100R001 and later V100R002 and later
Feature Dependency
If you apply the DCC transparent transmission solution to communicate NM messages when the OptiX equipment is used together with 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.
5.4 Principles
This section describes the principles of the DCC transparent transmission solution. In the receive direction: 1. 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. 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. The CPU processes the NM messages carried by the DCC bytes according to the protocol stack of the DCCs.
2.
3.
In the transmit direction:
Issue 05 (2010-10-30)
5-5
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. 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. 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.
2.
3.
Figure 5-5 illustrates how an NE uses bytes D1 to D3 as DCCs to transparently transmit bytes D4 to D12. Figure 5-5 Realization principle of the DCC transparent transmission
D4-D12 Overhead crossconnect matrix D1-D3 CPU Line board SCC board Line board
SDH signal
Overhead bus
Overhead bus
SDH signal

Follow certain planning guidelines when you plan DCC transparent transmission.
NOTE
This section describes the planning guidelines of DCC transparent transmission and the difference between HWECC and DCC transparent transmission. For the shared parts, such as the planning of GNEs and external DCN, see 2.7 Planning Guidelines in HWECC solution.

l l l l If the third-party equipment uses D1-D3 for DCCs, OptiX NEs use D4-D12 for DCCs. If the third-party equipment uses D4-D12 for DCCs, OptiX NEs use D1-D3 for DCCs. In PDH microwave frames, one or three DCC bytes are used for DCCs. In Hybrid microwave frames, three DCC bytes are used for DCCs.
Planning Guidelines for DCC Transparent Transmission Routes

l l Set a DCC transparent transmission route between pass-through nodes. Each node on the route transparently transmits the DCC bytes used by the third-party equipment. The Hybrid radio and PDH radio systems cannot transparently transmit the DCC bytes used by the third-party equipment.
5-6

The configuration of the DCC transparent transmission solution consists of two parts, namely, the configuration of communications data at the near end and the creation of NEs on the NMS. Table 5-3 Configuration flow for the DCC transparent transmission solution Step 1 Operation A.1.5 Changing NE IDs Remarks Required. Set the parameters as follows: l Set ID to be the NE ID according to the planning of the DCN. l If the special extended ID is required for the NE according to the planning of the DCN, change Extended ID. 2 A.3.1 Setting NE Communication Parameters Required. Set the parameters as follows: l For the GNE, set IP Address and Subnet Mask according to the planning of the external DCN. l For the GNE, set Gateway IP Address if the external DCN requires that the default gateway is configured for the NE. l For the non-GNE, it is recommended that you set IP Address to 0x81000000 + NE ID. That is, if the NE ID is 0x090001, set IP Address to 129.9.0.1. Set Subnet Mask to 255.255.0.0. 3 A.3.2 Configuring DCCs Required when the third-party equipment uses bytes D1 to D3 as DCCs. Set the parameters as follows: l Set Channel Type of the SDH port to D4-D12. l Adopt the default values for the other parameters. In the other cases, all the parameters take the default values. 4 A.3.4 Configuring DCC Transparent Transmission When the OptiX NE needs to transparently transmit the DCC byte of the third-party equipment, configure the DCC byte of the third-party equipment to be transparently transmitted in the planned route through this operation. Perform this operation only on the GNE. In normal cases: l There is an ECC route between the GNE and each of its managed non-GNEs.
Issue 05 (2010-10-30)
5-7
Step 6
Operation Creating NEs on the centralize d NMS A.1.2 Creating NEs by Using the Manual Method A.1.1 Creating NEs by Using the Search Method
Remarks It is recommended that you create NEs on the centralized NMS by using this method when you need to add one or more NEs on a large-scale network.
In the other cases, this method is preferred.
NOTE
If the centralized NMS is U2000 instead of Web LCT, the NEs need to be created on the U2000. For the information on how to create NEs on the U2000, see the Feature Description (U2000).

This section uses an example to describe how to plan and configure the DCC transparent transmission solution according to network conditions. 5.7.1 Networking Diagram This section describes the networking information about the NEs. 5.7.2 Service Planning The service planning information contains the information about all the parameters required for configuring the NE data. 5.7.3 Configuration Process This section describes the procedure of data configuration.

This section describes the networking information about the NEs. In the networking diagram shown in Figure 5-6, the OptiX radio transmission equipment and the third-party SDH optical transmission equipment form an STM-1 ring network. The thirdparty equipment does not support the IP over DCC or OSI over DCC solution.
5-8
Issue 05 (2010-10-30)
Figure 5-6 Networking diagram of the DCC transparent transmission solution
NMS
NE1
Third-party NMS
NE2
NE4
OptiX equipment
NE3
Third-party transmission equipment
Ethernet link
Radio link
Fiber

The service planning information contains the information about all the parameters required for configuring the NE data. l The networking is formed by the OptiX radio transmission equipment and the third-party SDH optical transmission equipment and the third-party equipment does not support the IP over DCC or OSI over DCC solution. Therefore, the DCC transparent transmission solution is used. Select NE1 that is closest to the NMS as GNE. Allocate IDs and IP addresses for all the NEs according to the situation of the network.
l l
Issue 05 (2010-10-30)
5-9
Figure 5-7 Allocation of IDs/IP addresses for all the NEs

NMS
10.0.0.100 9-1 10.0.0.1 0.0.0.0 9-2 129.9.0.2 0.0.0.0
NE1
Third-party NMS
NE2
9-4 129.9.0.4 0.0.0.0
9-3 129.9.0.3 0.0.0.0
NE4
NE3
Extended ID-Basic ID IP address Gatew ay
l l l
The third-party equipment uses bytes D1 to D3 as DCCs. Hence, the SDH line port and the SDH microwave port use bytes D4 to D12 as DCCs. The transparent transmission of the D1 to D3 bytes needs to be configured on NE1 to NE4. The transparent transmission of the D4 to D12 bytes needs to be configured on the thirdparty equipment.

Context
NOTE
In this configuration example, only the configuration information about NE1 is provided.
Procedure
Step 1 See A.1.5 Changing NE IDs and change the NE ID. The values for the related parameters are provided as follows.
5-10
Issue 05 (2010-10-30)
Parameter
Value Range NE1
1 9 (default value)
Step 2 See A.3.1 Setting NE Communication Parameters and set the communication parameters of the NE. The values for the related parameters are provided as follows. Parameter Value Range NE1 IP Address Gateway IP Address Subnet Mask 10.0.0.1 0.0.0.0 (default value) 255.255.0.0 (default value)
Step 3 See A.3.2 Configuring DCCs and configure the DCC. The values for the related parameters are provided as follows. Parameter Value Range SDH Line Port on the Ring Enabled/Disabled Channel Type Protocol Type Enabled (default value) D4-D12 HWECC (default value) SDH Microwave Port on the Ring Enabled (default value) D4-D12 HWECC (default value)
Step 4 See A.3.4 Configuring DCC Transparent Transmission and configure the transparent transmission of the DCC byte. Parameter Source Timeslot/ Port Transparent Transmission of Overhead Bytes at Source Port Value Range Related parameter value of the SDH line port on the ring D1 Related parameter value of the SDH line port on the ring D2 Related parameter value of the SDH line port on the ring D3
Issue 05 (2010-10-30)
5-11
Parameter Sink Timeslot/Port
Value Range Related parameter value of the SDH microwave port on the ring D1 Related parameter value of the SDH microwave port on the ring D2 Related parameter value of the SDH microwave port on the ring D3
Transparent Transmission of Overhead Bytes at Sink Port
Step 5 See A.3.10 Querying ECC Routes and query the ECC route. The expected result is as follows: l The ECC routes to NE2, NE3, and NE4 can be queried on NE1. Step 6 See A.1.1 Creating NEs by Using the Search Method and create NEs in the search mode on the centralized NMS. The search domains include the following: The search network segment when the IP address of the GNE is 10.0.0.1. In normal cases, all the NEs can be created on the centralized NMS. ----End
5.8 Task Collection

This section provides the hyperlinks of the operation tasks associated with the DCC transparent transmission feature.
Related Tasks
A.1.1 Creating NEs by Using the Search Method A.1.2 Creating NEs by Using the Manual Method A.3.2 Configuring DCCs A.3.4 Configuring DCC Transparent Transmission A.3.10 Querying ECC Routes

The DCC transparent transmission solution does not involve any alarm or event.
5.10 FAQs
This section provides the answers to the questions that are frequently raised when the DCC transparent transmission solution is used.
Q: Compared with other solutions for communicating NM information, what advantages and disadvantages does the DCC transparent transmission solution have? A: The advantages are as follows: l l The IP protocol stack or the OSI protocol stack need not be used. Therefore, a small amount of system resources are occupied. The configuration is simple.
The disadvantages are as follows: l l l The NMS of each vendor can be accessed to the DCN only through its own NE. Only DCC bytes can be transparently transmitted. The automatic rerouting function is weak.
Q: How can I use the DCC transparent transmission solution to interconnect the OptiX equipment with the third-party equipment? A: The steps are as follows: 1. 2. 3. 4. Check the DCC bytes used by DCCs with the maintenance staff of third-party equipment to ensure that different vendors use different DCC bytes. Analyze the routes for DCC transparent transmission with the maintenance staff of thirdparty equipment. Configure data according to the negotiated results and the network planning. Query ECC routes at the GNE. If there are no routes to non-GNEs, the interconnection fails.
Issue 05 (2010-10-30)
5-13
6 DCC Transparent Transmission Through the External Clock Interface Solution
DCC Transparent Transmission Through the External Clock Interface Solution
About This Chapter

This chapter describes DCC transparent transmission through the external clock interface. 6.1 Introduction This section provides the definition of DCC transparent transmission through the external clock interface and describes its purpose. 6.2 Specifications This section describes the specifications of DCC transparent transmission through the external clock interface. 6.3 Availability This section describes the support required by the application of DCC transparent transmission through the external clock interface and its dependency. 6.4 Principles This section describes the principles of DCC transparent transmission through the external clock interface. 6.5 Planning Guidelines Follow certain planning guidelines when you plan DCC transparent transmission through external clock interfaces. 6.6 Configuration Procedure To configure the solution of transparently transmitting DCCs through the external clock interface, you need to perform other configuration operations in addition to configuring the HWECC solution. 6.7 Configuration Example This section uses an example to describe how to plan and configure the DCC transparent transmission solution according to network conditions. 6.8 Task Collection This section provides the hyperlinks of the operation tasks associated with the DCC transparent transmission through the external clock interface feature.
6.9 Relevant Alarms and Events There is no related alarm or event for the DCC transparent transmission through the external clock interface solution. 6.10 FAQs This section provides the answers to the questions that are frequently raised when the DCC transparent transmission through the external clock interface solution is used.
6-2
Issue 05 (2010-10-30)
6.1 Introduction
This section provides the definition of DCC transparent transmission through the external clock interface and describes its purpose.
Definition
DCC transparent transmission through the external clock interface is a DCN solution provided by Huawei. In this solution, DCC bytes are transmitted through the external clock interface that is connected to a specified E1 interface, and the third-party equipment considers the signals as common E1 services. There are two networking scenarios for the DCC transparent transmission through the external clock interface solution: l Direct access mode An NE is directly connected to the third-party network through the external clock interface. Figure 6-1 provides a networking example of the direct access mode. In this example, the third-party network is a PDH network that provides E1 interfaces for the OptiX NEs at both ends. In this case, you can directly connect an E1 cable that connects to an external clock interface to the third-party network. The third-party network then transmits the E1 as an ordinary service. Thus, DCC bytes are transparently transmitted between the two NEs. A special application of the direct access mode is to use an E1 cable to directly connect the external clock interfaces of two OptiX NEs. Figure 6-1 Networking example for the DCC transparent transmission through the external clock interface solution (direct access mode)
External clock interface DCC bytes E1 cable PDH network External clock interface DCC bytes E1 cable
Indirect access mode An NE is connected to the third-party network through a service interface. Figure 6-2 provides a networking example of the indirect access mode. In this example, the third-party network is an SDH/PDH hybrid network. PDH signals are transmitted on the transmission path although the network provides SDH optical interfaces for the OptiX NEs at both ends. In this case, first use an E1 cable to connect the external clock interface to an E1 port of an E1 tributary board, and then configure cross-connections between the E1 service and the line board. Thus, the E1 service is accessed to the third-party network through the SDH interface. The third-party network then transmits the E1 as an ordinary service. Thus, DCC bytes are transparently transmitted between the two NEs.
Issue 05 (2010-10-30)
6-3
Figure 6-2 Networking example for the DCC transparent transmission through the external clock interface solution (indirect access mode)
External clock interface E1 port of a tributary unit DCC bytes SDH/PDH netw ork Fiber DCC bytes Fiber External clock interface E1 port of a tributary unit
Purpose
DCC transparent transmission through the external clock interface is preferred as the DCN solution when the third-party network does not support the transmission of DCC bytes but supports the transmission of E1 services.
6.2 Specifications
This section describes the specifications of DCC transparent transmission through the external clock interface. The OptiX RTN 620 supports the following specifications of DCC transparent transmission through the external clock interface. Table 6-1 Specifications of DCC transparent transmission through the external clock interface Item Number of external clock interfaces Specifications Each PXC board can support one external clock interface. The OptiX RTN 620 can house up to two PXC boards. The external clock interface can be used to one of the following three functions: l Transmit external clock signals l Transmit wayside E1 services l Transparently transmit overhead bytes, including DCC bytes, synchronous/ asynchronous data overhead bytes, and orderwire overhead bytes. Only the external clock interface of the active PXC board cab be used to transmit the DCC bytes. Specifications of external clock interfaces Compliant with ITU-T G.703. the impedance is 75 ohms.
6-4
Issue 05 (2010-10-30)
6.3 Availability
This section describes the support required by the application of DCC transparent transmission through the external clock interface and its dependency.

Table 6-2 Hardware and version support Feature DCC transparent transmission through the external clock interface Applicable Board SCC PXC Applicable Hardware Version All the versions All the versions Applicable Product Version V100R002 and later V100R002 and later
Feature Dependency
If you apply the DCC transparent transmission through the external clock interface solution to communicate NM messages when the OptiX equipment is used together with 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.
6.4 Principles
This section describes the principles of DCC transparent transmission through the external clock interface. In the receive direction: 1. The PXC board transmits the E1 service received on the external clock interface as 2.048 Mbit/s overhead signals to the overhead cross-connect matrix of the SCC board through the overhead bus. The overhead cross-connect matrix transports the DCC bytes that the NE uses to the CPU. The CPU processes the NM messages carried by the DCC bytes according to the protocol stack of the DCCs.
2. 3.
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. The overhead cross-connect matrix combines the DCC bytes sent from the CPU and other overhead bytes (such as the overhead bytes used by orderwire services and synchronous/ asynchronous data services) to form a 2.048 Mbit/s overhead signal stream, and then transmits the overhead signal stream to the external clock interface.
2.
Issue 05 (2010-10-30)
3.
The external clock interface transmits the 2.048 Mbit/s overhead signals as an E1 service to the third-party network.
Figure 6-3 illustrates how an NE transparently transmits DCC bytes through the external clock interface. In this example, DCC bytes D1 to D3 carry the NM messages. Figure 6-3 Realization principle of the DCC transparent transmission through the external clock interface
External clock interface Overhead bus PXC board
Overhead crossconnect matrix D1-D3 CPU
SCC board

Follow certain planning guidelines when you plan DCC transparent transmission through external clock interfaces. l l l l When the OptiX equipment is interconnected with a third-party network through E1 interfaces, adopt the direct access mode. When the OptiX equipment is interconnected with a network through other service interfaces, adopt the indirect access mode. Any two NEs that use a third-party network to transparently transmit DCC bytes must use the same DCC bytes. It is recommended that the NEs use D1-D3. In indirect access mode, plan the SDH timeslots for E1 services according to the negotiation result between OptiX NEs and a third-party network.

To configure the solution of transparently transmitting DCCs through the external clock interface, you need to perform other configuration operations in addition to configuring the HWECC solution.
6-6
Issue 05 (2010-10-30)
Table 6-3 Procedure for configuring the solution of transparently transmitting DCCs through the external clock interface Step 1 Operation A.3.2 Configuring DCCs Remarks Required. Set the parameters as follows: l Set Enabled/Disabled of the used external clock interface to Enabled. l Adopt the default values for the other parameters. 2 A.7.1 Creating CrossConnections of Pointto-Point Services In the case of indirect access, perform this operation to set up the point-to-point cross-connection between the E1 port to which the external interface is connected and the specific timeslot of the port on the SDH line board. This port on the SDH line board is used to interconnect with the third-party equipment. The specific timeslot is used to transparently transmit the NM messages.

This section uses an example to describe how to plan and configure the DCC transparent transmission solution according to network conditions. 6.7.1 Networking Diagram The section describes the networking information about the NEs. 6.7.2 Service Planning The service planning information contains all the parameter information required for configuring the NE data. 6.7.3 Configuration Process This section describes the procedure of data configuration.

The section describes the networking information about the NEs. Figure 6-4 shows a transmission network that is comprised of the OptiX equipment and thirdparty equipment. The third-party network provides NE1 with SDH optical interfaces and provides NE2 with E1 interfaces.
Issue 05 (2010-10-30)
6-7
Figure 6-4 Networking example for the DCC transparent transmission through the external clock interface solution
NE1 NMS
NE2
NE3
NE4
OptiX equipment
Network cable Radio link
E1 cable Fiber

The service planning information contains all the parameter information required for configuring the NE data. l l l l l Because NE1 is connected to the third-party equipment through the SDH line, the indirect connection mode is adopted. Because NE2 is connected to the third-party equipment through E1 interfaces, the direct connection mode is adopted. NE1 and NE2 use bytes D1 to D3 to transmit NM messages. In NE1, connect the external clock interface to E1 port 1 (4-PH1-1 port) on the PH1 board in slot 4. According to the negotiation result with the third-party equipment, use the first VC-12 timeslot of SL1 in slot 6 (6-SL1-1 port) of the control, switch, and clock board on NE1 to transparently transmit the network management messages of the OptiX equipment.

Context
NOTE
l In this configuration example, only the configuration information about typical NEs (NE1 and NE2) is provided. l In this configuration example, only the configurations different from the HWECC solution are provided.
6-8
Issue 05 (2010-10-30)
Procedure
Step 1 See A.3.2 Configuring DCCs and configure the DCC channel. The values for the related parameters are provided as follows. Parameter Value Range External Clock Interface (NE1) Enabled/Disabled Channel Type Protocol Type Enabled D1-D3 (default value) HWECC (default value) External Clock Interface (NE2) Enabled D1-D3 (default value) HWECC (default value)
Step 2 See A.7.1 Creating Cross-Connections of Point-to-Point Services and create the crossconnection of the point-to-point service for NE1. The values for the related parameters are provided as follows. Parameter Value Range NE1 Level Direction Source Slot Source VC4 Source Timeslot Range(e.g.1,3-6) Sink Slot Sink VC4 Sink Timeslot Range(e.g.1,3-6) VC-12 (default value) Bidirectional (default value) 4-PH1 1 6-SL1 1 1
----End
6.8 Task Collection

This section provides the hyperlinks of the operation tasks associated with the DCC transparent transmission through the external clock interface feature.
Related Tasks
A.3.2 Configuring DCCs A.7.1 Creating Cross-Connections of Point-to-Point Services
Issue 05 (2010-10-30)
6-9

There is no related alarm or event for the DCC transparent transmission through the external clock interface solution.
6.10 FAQs
This section provides the answers to the questions that are frequently raised when the DCC transparent transmission through the external clock interface solution is used. Q: Which of the DCC transparent transmission through the external clock interface solution and the extended ECC solution is used to transfer NM messages between two NEs when the two NEs are installed back-to-back? A: When the distance between the two NEs is within the transmission range of a network cable (the maximum transmission distance of a network cable is within the range from 50 meters to 100 meters), use the extended ECC solution, that is, use a network cable to connect the Ethernet NM ports or NE cascading ports of the two NEs. When the distance between the two NEs exceeds the maximum transmission distance of a network cable but is less than the transmission distance of an E1 cable (the maximum transmission distance of an E1 cable is 300 meters), use the DCC transparent transmission through the external clock interface solution. This is because the extended ECC consumes much less system resources than the DCC transparent transmission through the external clock interface. Q: Can the external clock interface be used to transparently transmit orderwire overhead bytes when the DCC transparent transmission through the external clock interface solution is already applied? A: Yes, the external clock interface can be used to transparently transmit orderwire bytes when the DCC transparent transmission through the external clock interface solution is already applied. This is because the DCC bytes occupy only certain timeslots of the E1 service that is transmitted by the external clock interface. Hence, the other timeslots of the E1 service can be used to transparently transmit the overhead bytes used by orderwire calls, asynchronous data interface services, and synchronous data interface services. Q: Why does the configuration of the DCC transparent transmission through the external clock interface solution fail? A: Common causes are as follows: l l The external clock source or the working mode for outputting the external clock is modified to 2 MHz. The wayside E1 service is configured.
6-10
Issue 05 (2010-10-30)
7 1+1 HSB
7
About This Chapter
This chapter describes the 1+1 hot standby (HSB) feature. 7.2 Basic Concepts This section describes the basic concepts associated with 1+1 HSB. 7.3 Specifications This section provides the specifications of 1+1 HSB.
1+1 HSB
7.1 Introduction This section provides the definition of 1+1 HSB and describes its purpose.
7.4 Availability This section describes the support required by the application of the 1+1 HSB feature and its dependency. 7.5 Principles The switching principle of SDH/PDH radio 1+1 HSB is different from the switching principle of Hybrid radio 1+1 HSB. 7.6 Planning Guidelines Follow certain principles when you plan 1+1 HSB. 7.7 Configuration Procedure When configuring a radio link with 1+1 HSB, you need to configure a 1+1 IF protection group and then configure IF/ODU information. 7.8 Configuration Example This section uses an example to describe how to plan and configure 1+1 HSB according to network conditions. 7.9 Task Collection This section provides the hyperlinks of the operation tasks associated with 1+1 HSB. 7.10 Relevant Alarms and Events When a 1+1 HSB switching occurs on IF boards, the system reports corresponding alarms and abnormal events. 7.11 FAQs
7 1+1 HSB
This section provides the answers to the questions that are frequently raised when 1+1 HSB is used.
7-2
Issue 05 (2010-10-30)
7 1+1 HSB
7.1 Introduction
This section provides the definition of 1+1 HSB and describes its purpose.
Definition
1+1 HSB is a configuration mode of 1+1 protection. In 1+1 HSB mode, the equipment provides 1+1 hot standby configuration for the IF boards and ODUs at both ends of each hop of radio link. Figure 7-1 shows the application of 1+1 HSB. If NE2 detects that a certain device on the main channel is faulty (the fault point can be an ODU or an IF board), NE2 switches to the standby channel to receive services. Figure 7-1 1+1 HSB protection
Before the Switching Main channel MODEM MODEM Service Service MODEM MODEM Standby channel Tx Rx Tx Rx MODEM MODEM Rx Tx Main channel Rx Tx MODEM MODEM Service Service
Standby channel
NE1
After the Switching Main channel MODEM MODEM Service Service MODEM MODEM Standby channel Tx Rx Tx Rx Rx Tx
NE2
Main channel Rx Tx MODEM MODEM Service Service MODEM MODEM
Standby channel
NE1
Change spot
NE2
fault equipment
Purpose
A radio link configured with 1+1 HSB has a higher reliability than a radio link configured with 1+0 non-protection.
7.2 Basic Concepts

This section describes the basic concepts associated with 1+1 HSB.
7 1+1 HSB
7.2.1 System Configuration 1+1 HSB requires specific system configuration. 7.2.2 Protection Type The 1+1 HSB protection is classified into the revertive mode and the non-revertive mode. 7.2.3 Switching Condition The switching priority varies with the switching condition. 7.2.4 Switching Impact Within the 1+1 HSB switching time (less than 500 ms), the service is interrupted.
7.2.1 System Configuration

1+1 HSB requires specific system configuration.
Typical Configuration of SDH/PDH Radio 1+1 HSB

One 1+1 HSB protection group uses one channel and consists of the following items: l l l Two IF boards that are of the same type Two ODUs that are of the same type One antenna (equipped with one hybrid coupler)
NOTE
l The IF board can be the IF0A board, IF0B board, IF1A board, IF1B board, IFH2 board or IFX board. l The hybrid coupler can be balanced or unbalanced. Generally, the unbalanced hybrid coupler is used.
Figure 7-2 shows a typical configuration of one SDH/PDH radio 1+1 HSB protection group on the OptiX RTN 620.
Figure 7-2 Typical configuration of 1+1 HSB (OptiX RTN 620)
ODU
Hybrid coupler
Antenna
ODU
EXT IF FAN
Slot 20
Slot 7 Slot 5 Slot 3 Slot 1
EXT EXT EXT PH1 SCC
EXT IF PXC PXC

IDU 620
7-4
Issue 05 (2010-10-30)
7 1+1 HSB
Typical Configuration of Hybrid Radio 1+1 HSB

One 1+1 HSB protection group uses one channel and consists of the following items: l l l l Two IF boards that are of the same type One EMS6 board or EFP6 board Two ODUs that are of the same type One antenna (equipped with one hybrid coupler)
NOTE
l The type of the IF board is IFH2. l The hybrid coupler can be balanced or unbalanced. Generally, the unbalanced hybrid coupler is used.
Figure 7-3 shows a typical configuration of one Hybrid radio 1+1 HSB protection group on the OptiX RTN 620. Figure 7-3 Typical configuration of 1+1 HSB (OptiX RTN 620)
ODU
Hybrid coupler
Antenna To the external equipment
ODU
Network cable
EXT IF FAN
Slot 20
EMS6 EXT EXT PH1 EXT SCC
EXT IF PXC PXC

IDU 620
ODU
To the external PDH networking Hybrid coupler Antenna Network cable
ODU
EXT IF FAN
Slot 20
EFP6 EXT EXT PH1 EXT SCC
EXT IF PXC PXC

IDU 620
Issue 05 (2010-10-30)
7-5
7 1+1 HSB
7.2.2 Protection Type

The 1+1 HSB protection is classified into the revertive mode and the 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 former working channel is restored to normal for a certain period. The period from the time when the former working channel is restored to normal to the time when the NE releases the switching is called the wait-to-restore (WTR) time. To prevent frequent switching events because the former working channel is not stable, it is recommended that you set the WTR time to 5 to 12 minutes. l Non-revertive mode When an NE is in the switching state, the NE remains the current state unchanged unless another switching event occurs even though the former working channel is restored to normal.
NOTE
The reverse switching always uses the non-revertive mode. That is, although both the main and standby equipment are normal, the system does not switch back to the main equipment after the reverse switching occurs.
7.2.3 Switching Condition

The switching priority varies with the switching condition. Table 7-1 Trigger conditions of the 1+1 HSB switching Switching Condition Clear switching (external switching) Priority From top downwards, the priority is from the highest to the lowest. Description All external switching states are cleared.
NOTE In revertive mode, the service is switched to the main IF board after the clear switching operation is performed.
Lockout of protection (external switching)
In any state, the switching changes to the lockout state. In the lockout state, no switching occurs until the lockout of protection is cleared.
7-6
Issue 05 (2010-10-30)
7 1+1 HSB
Switching Condition Forced switching (external switching)
Priority
Description If the switching is in the lockout state, no forced switching occurs. Otherwise, the system switches services from the main board to the standby board or from the standby board to the main board according to the command. The switching then changes to the forced switching state. If the switching is in the lockout or forced switching state, or if the current standby equipment is faulty, no HSB switching occurs. Otherwise, the system switches services from the current main board to the standby board. The switching then changes to the automatic switching state. For the trigger conditions of the automatic switching, refer to Table 7-2.
Fault on the main equipment
Issue 05 (2010-10-30)
7-7
7 1+1 HSB
Switching Condition Reverse switching (valid only when the reverse switching is enabled)
Priority
Description When both the main IF board and the standby IF board at the sink end report service alarms, they send the alarms to the source end by using the MWRDI overhead in the microwave frame. If the source end is in the lockout or forced switching state, or if the current standby equipment is faulty, no reverse switching occurs. Otherwise, the HSB switching occurs at the source end after the reverse switching timer expires. The reverse switching timer restarts after you successfully add a protection group or if an HSB switching event occurs. The timer duration is the WTR time (in revertive mode) or 5 minutes (in nonrevertive mode). After the reverse switching, the switching changes to the RDI state. If the switching is in the lockout, forced switching, or RDI state, or if the standby equipment is faulty, no switching occurs. Otherwise, the system switches services from the main board to the standby board or from the standby board to the main board according to the command. The switching then changes to the manual switching state.
Manual switching (external switching)
7-8
Issue 05 (2010-10-30)
7 1+1 HSB
Switching Condition Revertive switching (valid only in revertive mode)
Priority
Description When the switching is in the automatic switching state and the main equipment is already restored to normal for the WTR time, the revertive switching occurs. From the time when the main equipment is restored to normal to the time when the revertive switching occurs, the switching is in the WTR state. After the revertive switching, the switching changes to the normal state.
Table 7-2 Trigger conditions of the automatic 1+1 HSB switching Switching Condition Hardware fault on the IF board Hardware fault on the ODU POWER_ALM VOLT_LOS (IF board) RADIO_TSL_HIGH RADIO_TSL_LOW RADIO_RSL_HIGH IF_INPWR_ABN CONFIG_NOSUPPORT R_LOC R_LOF R_LOS (IF0A, IF0B, IF1A, IF1B, IFX) MW_LOF XPIC_LOS (IFX) Fault on the IF connection cable Priority At the same priority
7.2.4 Switching Impact

Within the 1+1 HSB switching time (less than 500 ms), the service is interrupted.
7 1+1 HSB
7.3 Specifications
This section provides the specifications of 1+1 HSB. Table 7-3 lists the specifications of 1+1 HSB. Table 7-3 Specifications of 1+1 HSB Item Radio type Specification SDH/PDH radio Hybrid radio Number of protection groups Switching time Protection type 1 to 2 < 500 ms Revertive mode Non-revertive mode WTR time Reverse switching Restriction on the available slot of the IF board 5 to 12 minutes Supported No restriction
7.4 Availability
This section describes the support required by the application of the 1+1 HSB feature and its dependency.
Hardware and Version

Table 7-4 Hardware and version support Feature 1+1 HSB Applicable Board IF0A IF0B IF1A IF1B IFH2 IFX Applicable Hardware Version All the versions All the versions All the versions All the versions All the versions All the versions Applicable Product Version V100R002 and later V100R002 and later V100R001 and later V100R001 and later V100R003 and later V100R002 and later
7-10
Issue 05 (2010-10-30)
7 1+1 HSB
Feature Dependency
l The configuration mode of 1+1 protection in one direction can only be 1+1 HSB, 1+1 FD, or 1+1 SD. The configuration mode in one direction can be different from that in another direction. The two IP boards in an XPIC group cannot be configured into one 1+1 HSB protection group. However, these boards can be configured into two 1+1 HSB protection groups with the two IF boards in another XPIC group in the same polarization direction. The members of the 1+1 HSB protection group cannot participate in the N+1 protection. The radio link with 1+1 HSB configuration can function as the working source, protection source, or service sink of SNCP. The AM function can be enabled in the case of 1+1 HSB Hybrid radio links.
l l l
7.5 Principles
The switching principle of SDH/PDH radio 1+1 HSB is different from the switching principle of Hybrid radio 1+1 HSB. 7.5.1 SDH/PDH Radio The cross-connect unit implements HSB switching by dually transmitting and selectively receiving TDM services. 7.5.2 Hybrid Radio The cross-connect unit implements HSB switching on the TDM plane by dually transmitting and selectively receiving TDM services; the packet switching unit implements HSB switching on the packet plane through LAG switching.
7.5.1 SDH/PDH Radio

The cross-connect unit implements HSB switching by dually transmitting and selectively receiving TDM services.
Before the Switching

Figure 7-4 1+1 HSB realization principle (before the switching, in the transmit direction)
Main ODU Main Cross-connect IF board board Service board
Antenna
Hybrid coupler
Standby ODU
Standby IF board
In the transmit direction:

7 1+1 HSB
1. 2. 3. 4.
The service interface unit transmits the received service signal to the cross-connect unit. The cross-connect unit transmits the service signal to both the main IF board and the standby IF board. The main IF board and the standby IF board send the processed IF analog signal to the main ODU and the standby ODU respectively. The main ODU transmits the RF signal to the hybrid coupler, which sends the RF signal to the antenna. The standby ODU is muted (that is, the standby ODU does not transmit the RF signal).
Figure 7-5 1+1 HSB realization principle (before the switching, in the receive direction)
Antenna
Hybrid coupler
Standby ODU
Standby IF board
In the receive direction: 1. 2. 3. 4. 5. The hybrid coupler splits the RF signal received from the antenna into two signals and sends them to the main ODU and the standby ODU. The main ODU and the standby ODU send the processed IF analog signal to the main IF board and the standby IF board respectively. The main IF board and the standby IF board send the service signal to the cross-connect unit. The cross-connect unit selects the service signal from the main IF board and transmits the service signal to the service interface unit. The service interface unit sends the service signal to other equipment.
After the Switching

Figure 7-6 1+1 HSB realization principle (after the switching, in the receive direction)
Antenna
Hybrid coupler
Standby ODU
Standby IF board
7-12
Issue 05 (2010-10-30)
7 1+1 HSB
Figure 7-7 1+1 HSB realization principle (after the switching, in the transmit direction)
Antenna
Hybrid coupler
Standby ODU
Standby IF board
After the 1+1 HSB switching: l l In the receive direction, the cross-connect unit selects the service signal from the standby IF board. In the transmit direction, the standby ODU outputs the RF signal to the hybrid coupler, which sends the RF signal to the antenna; the main ODU is muted (that is, the main ODU does not transmit the RF signal).
NOTE
The actions involved in the 1+1 HSB protection switching occur on the faulty NE. These actions do not occur on the normal NE.
7.5.2 Hybrid Radio

The cross-connect unit implements HSB switching on the TDM plane by dually transmitting and selectively receiving TDM services; the packet switching unit implements HSB switching on the packet plane through LAG switching.

Figure 7-8 1+1 HSB realization principle (before the switching, in the transmit direction)
Main ODU Main IF board Cross-connect board Service board
Hybrid coupler Antenna
Standby ODU
Standby IF board
EMS6 board
Issue 05 (2010-10-30)
7-13
7 1+1 HSB
In the transmit direction: 1. 2. 3. The service interface unit multiplexes the received E1 service signal into the VC-4 and then sends the VC-4 to the cross-connect unit. The cross-connect unit transmits the E1 service signal contained in the VC-4 to the main IF board and the standby IF board. The Ethernet service port of the main IF board is in LinkUp state, whereas the Ethernet service port of the standby IF board is in LinkDown state. The Ethernet board EMS6 transmits the Ethernet service to the Ethernet service port of the main IF board through the LAG function. The MUX unit of the main IF board multiplexes the E1 service signal and Ethernet service signal into the Hybrid microwave frame. The Hybrid microwave frame multiplexed by the MUX unit of the standby IF board does not contain the Ethernet service signal. The IF processing units of the main IF board and the standby IF board receive the Hybrid microwave frame that is multiplexed by their corresponding IF board and modulate the Hybrid microwave frame into the IF analog signal. Then, the IF processing units of the main IF board and the standby IF board send the IF analog signal to the main ODU and the standby ODU respectively. The main ODU transmits the RF signal to the hybrid coupler, which sends the RF signal to the antenna. The standby ODU is muted (that is, the standby ODU does not transmit the RF signal).
NOTE
4.
5.
6.
The switching method of Hybrid radio services on the EFP6 board is the same as the switching mode of Hybrid radio services on the EMS6 board.
Figure 7-9 1+1 HSB realization principle (before the switching, in the receive direction)
Main ODU Hybrid coupler Antenna Main IF board Cross-connect board Service board
Standby ODU
Standby IF board
EMS6 board
In the receive direction: 1. 2. 3. The hybrid coupler splits the RF signal received from the antenna into two signals and sends them to the main ODU and the standby ODU. The main ODU and the standby ODU send the processed IF analog signal to the main IF board and the standby IF board respectively. The main IF board and the standby IF board demodulate the Hybrid frame from the IF signal.
7-14
7 1+1 HSB
4.
The MUX units of the main IF board and the standby IF board receive the Hybrid microwave frame that is demodulated by their corresponding IF board and then separate the Hybrid microwave frame into the E1 service signal and Ethernet service signal. After being multiplexed into the VC-4, the E1 service signal is transmitted to the crossconnect unit. The Ethernet service signal is transmitted to the GE link on the IF board. The cross-connect unit selects the E1 service signal that is separated by the main IF board and then cross-connects the E1 service signal to the corresponding service interface unit. The EMS6 board receives the Ethernet service signal from the main IF board because the Ethernet service port of the main IF board is in LinkUp state whereas the Ethernet service port of the standby IF board is in LinkDown state.
5. 6. 7.
After the Switching

Figure 7-10 1+1 HSB realization principle (after the switching, in the receive direction)
Main ODU Hybrid coupler Antenna Main IF board Cross-connect board Service board
Standby ODU
Standby IF board
EMS6 board
Main ODU Main IF board Cross-connect board Service board
Hybrid coupler Antenna
Standby ODU
Standby IF board
EMS6 board
After the 1+1 HSB switching:

7 1+1 HSB
In the receive direction: The analog IF signal received at the standby IF board is separated into the E1 service signal and Ethernet service signal by the MUX unit. The Ethernet service port of the main IF board is in LinkDown state and the Ethernet service port of the standby IF board is in LinkUp state. The cross-connect board and the EMS6 board receive the service signal from the standby IF board. In the transmit direction: The Ethernet service port of the main IF board is in LinkDown state and the Ethernet service port of the standby IF board is in LinkUp state. The IF processing units of the main IF board and the standby IF board modulate the Hybrid microwave frame that is multiplexed by the MUX unit of their corresponding IF board into the analog IF signal. The main IF board and the standby IF board send the analog IF signal to the main ODU and the standby ODU. The standby ODU transmits the RF signal to the hybrid coupler, which sends the RF signal to the antenna. The main ODU is muted (that is, the main ODU does not transmit the RF signal).
NOTE
The actions involved in the 1+1 HSB protection switching occur on the faulty NE. These actions do not occur on the normal NE.

Follow certain principles when you plan 1+1 HSB. Plan the parameters relevant to the protection configuration. l If the protection is in the revertive mode, set the WTR time to a value, which ranges from five minutes to twelve minutes. It is recommended that you set the default value to ten minutes. It is recommended that you disable reverse switching to avoid incorrect switching actions. In the case of the OptiX RTN 620, although the 1+1 HSB protection has no restriction on the slot of the IF board, it is recommended that you install a pair of main and standby IF boards in slots 5 and 7 (the IF board in slot 5 is the main board) or in slots 6 and 8 (the IF board in slot 6 is the main board).
l l

When configuring a radio link with 1+1 HSB, you need to configure a 1+1 IF protection group and then configure IF/ODU information. Table 7-5 Configuration procedure of 1+1 HSB Step 1 Operation A.5.3 Configuring the IF/ODU Information of a Radio Link Description When configuring a radio link with 1+1 HSB, you need to configure IF and ODU information for the working radio link only. The parameters need to be set according to the network planning.
7-16
Issue 05 (2010-10-30)
7 1+1 HSB
Step 2
Operation A.5.9 Setting Parameters of ODU Interfaces
Description The parameters need to be set according to the network planning.
NOTE
You need to configure a load non-sharing and revertive LAG. For details on the configuration procedure, see Configuration Procedure of the LAG feature.

This section uses an example to describe how to plan and configure 1+1 HSB according to network conditions.
NOTE
This section considers creating 1+1 HSB radio links by using the IFU2 boards as an example. If you use the IF0A, IF0B, IF1A, IF1B, or IFX2 boards, the method of configuring 1+1 HSB is the same. The only difference is with regard to the IF parameter settings. For details, see the corresponding parameter description.
7.8.1 Networking Diagram The section describes the networking information about the NEs. 7.8.2 Service Planning The service planning information contains all the parameters required for configuring the NE data. 7.8.3 Configuration Process This section describes the procedure of data configuration.

The section describes the networking information about the NEs. To ensure the reliable transmission of services on a hop of radio link constructed by OptiX RTN 620s, you need to configure 1+1 HSB for the radio link between NE1 and NE2, as shown in Figure 7-12. Figure 7-12 1+1 HSB protection networking diagram
NE2
NE1
Issue 05 (2010-10-30)
7-17
7 1+1 HSB

The service planning information contains all the parameters required for configuring the NE data. l Plan the slots of the working board and the protection board. Plan the slots for the working board and the protection board based on the board configurations. To be specific, the IF board in slot 5 functions as the working board, and the IF board in slot 7 functions as the protection board. l Plan the protection group parameters. The 1+1 protection mode is HSB protection mode, which provides protection for the equipment. All parameters take default values unless otherwise specified. It is recommended that the reverse switching function be disabled to prevent inappropriate switchings. l Plan the radio link information. The radio link information is determined according to the network planning. The parameters are listed in the following table.
NOTE
In the case of radio links configured with HSB, one protection group maps one link. You only need to configure the IF/ODU information on the active equipment.
Table 7-6 IF planning information Parameter NE1 5-IFH2 Link ID Channel spacing (MHz) AM enabling AM guaranteed capacity mode AM full capacity mode E1 capacity ATPC status 101 28 Enabled QPSK 128QAM 16 Disabled NE2 5-IFH2 101 28 Enabled QPSK 128QAM 16 Disabled
Table 7-7 RF planning information Parameter NE1 15-ODU Transmit frequency (MHz) T/R spacing (MHz)
7-18
NE2 15-ODU 14510 420

Issue 05 (2010-10-30)
14930 420
7 1+1 HSB
Parameter
NE1 15-ODU
NE2 15-ODU 10 -45 unmute
Transmit power (dBm) Receive power (dBm) Transmission status
10 -45 unmute

Procedure
Step 1 A.5.1 Creating an IF 1+1 Protection Group. The values for the related parameters are provided as follows. Parameter Value Range NE1 Working Mode Revertive Mode WTR Time (s) Enable Reverse Switching Working Board Protection Board HSB Revertive mode (default value) 600 seconds (default value) Enabled (default value) 5-IFH2 7-IFH2 NE2 HSB Revertive mode (default value) 600 seconds (default value) Enabled (default value) 5-IFH2 7-IFH2
Step 2 A.5.3 Configuring the IF/ODU Information of a Radio Link. The values of the IF board parameters are provided as follows. Parameter Value Range NE1 5-IFH2 AM Enable Status IF Channel Bandwidth Modulation Mode of the Assured AM Capacity Enabled 28M QPSK NE2 5-IFH2 Enabled 28M QPSK
Issue 05 (2010-10-30)
7-19
7 1+1 HSB
Parameter
Value Range NE1 5-IFH2 NE2 5-IFH2 128QAM 16 101 Disabled
Modulation Mode of the Full AM Capacity E1 Capacity Link ID ATPC Enable Status
128QAM 16 101 Disabled
Step 3 A.5.9 Setting Parameters of ODU Interfaces. The values of the ODU parameters are provided as follows. Parameter Value Range NE1 15-ODU TX Frequency (MHz) T/R Spacing(MHZ) TX Power(dBm) Power to Be Received(dBm) TX Status 14930 420 10 -45 Unmute NE2 15-ODU 14510 420 10 -45 Unmute
----End
7.9 Task Collection

This section provides the hyperlinks of the operation tasks associated with 1+1 HSB.
Related Tasks
A.5.1 Creating an IF 1+1 Protection Group A.5.3 Configuring the IF/ODU Information of a Radio Link A.5.13 Querying the IF 1+1 Protection Status A.5.15 Performing IF 1+1 Protection Switching

When a 1+1 HSB switching occurs on IF boards, the system reports corresponding alarms and abnormal events.
7 1+1 HSB
Relevant Alarms
RPS_INDI The RPS_INDI alarm indicates the microwave protection switching.
Relevant Abnormal Events

IF 1+1 protection switching IF 1+1 protection switching: This abnormal event indicates that the IF 1+1 protection switching occurs.
7.11 FAQs
This section provides the answers to the questions that are frequently raised when 1+1 HSB is used. Q: During the configuration of the 1+1 HSB protection, is it necessary to configure the IF interface of the standby IF board and the ODU interface of the standby ODU? A: It is unnecessary. The system automatically copies the data of the main IF board and the main ODU. Therefore, you need to ensure that Configure Transmission Status is set to Unmute for both the main ODU and the standby ODU on the NMS. Q: Why does the configuration of the 1+1 HSB protection fail? A: Common causes are as follows: l l The IF board and the corresponding ODU that form the 1+1 HSB protection are not included in the slot layout. The standby IF board is configured with services.
Q: In the revertive mode, why does the switching fail to restore after the switching enters the RDI state? A: The revertive mode is invalid for the reverse switching. That is, although both the active and standby equipment are normal, the system does not switch the new standby equipment to active after a reverse switching. Q: When radio links work as ECC links, why is the NMS unable to receive the abnormal HSB switching event of the non-gateway NE? A: When an HSB switching occurs, the ECC needs to reroute. As a result, the ECC between the gateway NE and the non-gateway NE is transiently interrupted and the switching event cannot be reported. Q: When the main ODU is configured with the 1+1 HSB protection, why is the equipment not switched when a switching event is reported after the main ODU reports a configuration alarm? A: In the case of the 1+1 HSB protection group, the system automatically copies the data of the main ODU to the standby ODU. Hence, when the main ODU reports a configuration alarm, the standby ODU also reports the same configuration alarm. As both the main and the standby ODUs
7 1+1 HSB
report a configuration alarm, no switching occurs in the equipment. To notify the user that the ODU configuration is abnormal, however, the system reports a switching event. Q: What points should be noted before the deletion of a 1+1 HSB protection group? A: Before the deletion of a 1+1 HSB protection group, first ensure that the standby ODU is muted. Otherwise, the signal emitted by the standby ODU interferes with the signal of the main ODU. Q: What methods should be used to handle a 1+1 HSB protection switching failure? A: If the 1+1 HSB switching fails, check whether the protection groups are correctly configured, and then check whether the standby devices (including ODUs and IF boards) and standby radio link are normal. Exclude the fault that the RSL is low because of signal interference and antenna unalignment.
7-22
Issue 05 (2010-10-30)
8 1+1 FD
8
About This Chapter
This chapter describes the 1+1 frequency diversity (FD) feature. 8.1 Introduction This section provides the definition of 1+1 FD and describes its purpose. 8.2 Basic Concepts This section describes the basic concepts associated with 1+1 FD. 8.3 Specifications This section describes the specifications of 1+1 FD.
1+1 FD
8.4 Availability This section describes the support required by the application of the 1+1 FD feature and its dependency. 8.5 Principles The switching principle of SDH/PDH radio 1+1 FD is different from the switching principle of Hybrid radio 1+1 FD. 8.6 Planning Guidelines Follow certain principles when you plan 1+1 FD. 8.7 Configuration Procedure When configuring a radio link under 1+1 FD protection, you need to configure a 1+1 IF protection group and then configure IF/ODU information. 8.8 Configuration Example This section uses an example to describe how to plan and configure 1+1 FD according to network conditions. 8.9 Task Collection This section provides the hyperlinks of the operation tasks associated with 1+1 FD. 8.10 Relevant Alarms and Events When a 1+1 FD switching occurs on IF boards, the system reports corresponding alarms and abnormal events. 8.11 FAQs
8 1+1 FD
This section provides the answers to the questions that are frequently raised when 1+1 FD is used.
8-2
Issue 05 (2010-10-30)
8 1+1 FD
8.1 Introduction
This section provides the definition of 1+1 FD and describes its purpose.
Definition
1+1 FD is a configuration mode of 1+1 protection. In 1+1 FD protection mode, the system uses two channels that have a frequency spacing between them, to transmit and receive the same service signals. The opposite end selects a signal from the two received signals. With 1+1 FD protection, the impact of fading on signal transmission is reduced. Figure 8-1 shows the application of 1+1 FD. When NE2 detects that the quality of the signal at frequency F1 on the main channel is degraded, NE2 switches to the standby channel to receive the signal at frequency F2. Figure 8-1 1+1 FD protection
Before the Switching Main channel MODEM MODEM Service Service MODEM MODEM Standby channel Tx Rx Rx Tx Main channel Rx MODEM MODEM Service Service
F1
F1
Tx
F2
F2
Tx Rx
MODEM MODEM
Standby channel
NE1
After the Switching Main channel MODEM MODEM Service Service MODEM MODEM Standby channel Tx Rx Rx Tx
NE2
Main channel Rx MODEM MODEM Service Service
F1
F1
Tx
F2
F2
Tx Rx
MODEM MODEM
Standby channel
NE1
Change spot
NE2
In the case of the 1+1 FD protection, the main channel and the standby channel of the receive end receive RF signals at different frequencies from the transmit end respectively. Microwave signals at different frequencies are affected by spatial fading. Hence, when the quality of the microwave signal received on the main channel is degraded, bit errors occur in the service on the main channel. The service unit then selects the service signal on the standby channel to protect the service. In addition, the 1+1 FD protection supports 1+1 HSB protection switching.
Issue 05 (2010-10-30)
8-3
8 1+1 FD
Purpose
A radio link configured with 1+1 FD has a higher anti-fading capability and reliability than a radio link configured with 1+0 non-protection.
8.2 Basic Concepts

This section describes the basic concepts associated with 1+1 FD. 8.2.1 System Configuration 1+1 FD requires specific system configuration. 8.2.2 Protection Type The 1+1 FD protection is classified into the revertive mode and the non-revertive mode. 8.2.3 Switching Conditions The 1+1 FD protection supports two types of switching, namely, HSB switching and HSM switching. The two types of switching are triggered by different conditions. 8.2.4 Switching Impact In the case of the HSB switching, the services are interrupted within the HSB switching time (shorter than 500 ms). In the case of the HSM switching, the service is not affected because it is the hitless switching, when the AM function is enabled, the standby channel works in the modulation mode for ensuring capacity after the HSM switching. Hence, the service of a low priority may be damaged.

1+1 FD requires specific system configuration.
Typical Configuration of SDH/PDH Radio 1+1 FD

One 1+1 FD protection group uses two channels and consists of the following items: l l l Two IF boards that are of the same type Two ODUs One antenna (equipped with one balanced hybrid coupler) or two antennas
NOTE
l The IF board can be the IF0A board, IF0B board, IF1A board, IF1B board, IFX board, or IFH2 board. l If the two transmit frequencies used by the FD configuration are within the frequency combining range of one hybrid coupler, use one antenna that is equipped with one balanced hybrid coupler. Otherwise, use two antennas.
Figure 8-2 and Figure 8-3 show two typical configurations of one SDH/PDH radio 1+1 FD protection group on the OptiX RTN 620.
8-4
Issue 05 (2010-10-30)
8 1+1 FD
Figure 8-2 Typical configuration 1 of 1+1 FD (OptiX RTN 620)
ODU
Hybrid coupler
Antenna
ODU
EXT IF FAN
Slot 20
EXT EXT EXT PH1 SCC
EXT IF PXC PXC

IDU 620
ODU
Antenna
ODU
Antenna
EXT IF FAN
Slot 20
EXT EXT EXT PH1 SCC
EXT IF PXC PXC

IDU 620
Typical Configuration of Hybrid Radio 1+1 FD

One 1+1 FD protection group uses two channels and consists of the following items: l l l
Issue 05 (2010-10-30)
Two IF boards that are of the same type One EMS6 board or EFP6 board Two ODUs
8 1+1 FD
One antenna (equipped with one balanced hybrid coupler) or two antennas
NOTE
l The type of the IF board is IFH2. l If the two transmit frequencies used by the FD configuration are within the frequency combining range of one hybrid coupler, use one antenna that is equipped with one balanced hybrid coupler. Otherwise, use two antennas.
Figure 8-4 and Figure 8-5 show two typical configurations of a Hybrid radio 1+1 FD protection group constructed by EMS6 boards and EFP6 boards on the OptiX RTN 620. Figure 8-4 Typical configuration 1 of one 1+1 FD (OptiX RTN 620)
ODU
Hybrid coupler
Antenna To the external equipment
ODU
Network cable
EXT IF FAN
Slot 20
EXT IF PXC PXC

IDU 620
ODU
To the external PDH networking Hybrid coupler Antenna Network cable
ODU
EXT IF FAN
Slot 20
EXT IF PXC PXC

IDU 620
8-6
Issue 05 (2010-10-30)
8 1+1 FD
ODU
Antenna
ODU
Antenna
Network cable
To the external equipment

EXT IF FAN
Slot 20
EXT IF PXC PXC

IDU 620
ODU
Antenna To the external PDH networking
ODU
Antenna
Network cable
EXT IF FAN
Slot 20
EXT IF PXC PXC

IDU 620

The 1+1 FD protection is classified into the revertive mode and the 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 former working channel is restored to normal for a certain period. The period from the time when the former working channel is restored to normal to the time when the NE releases the switching is called the WTR time. To prevent frequent switching
8 1+1 FD
events because the former working channel is not stable, it is recommended that you set the WTR time to 5 to 12 minutes. l Non-revertive mode When an NE is in the switching state, the NE remains the current state unchanged unless another switching event occurs even though the former working channel is restored to normal.
NOTE
The revertive mode and non-revertive mode are only associated with HSB switchings (switchings on the equipment side). After an HSM switching on the channel side, a revertive switching is performed regularly on the IF board, regardless of the revertive mode.
8.2.3 Switching Conditions

The 1+1 FD protection supports two types of switching, namely, HSB switching and HSM switching. The two types of switching are triggered by different conditions.
Trigger Conditions of the HSB Switching

The HSB switching occurs on the equipment side. The equipment-side switching has the same switching action and switching impact as the 1+1 HSB switching but is triggered by different conditions. Table 8-1 Trigger conditions of the 1+1 FD HSB switching Switching Condition Clear switching (external switching) Priority From top downwards, the priority is from the highest to the lowest. Description All external switching states are cleared.
In any state, the switching changes to the lockout state. In the lockout state, no switching occurs until the lockout of protection is cleared. If the switching is in the lockout state, no forced switching occurs. Otherwise, the system switches services from the main board to the standby board or from the standby board to the main board according to the command. The switching then changes to the forced switching state.
Issue 05 (2010-10-30)
Forced switching (external switching)
8-8
8 1+1 FD
Switching Condition Fault on the main equipment
Priority
Description If the switching is in the lockout or forced switching state, or if the current standby equipment is faulty, no HSB switching occurs. Otherwise, the system switches services from the current main board to the standby board. The switching then changes to the automatic switching state. For the trigger conditions of the automatic switching, refer to Table 8-2. If the switching is in the lockout or forced switching state, or if the standby equipment is faulty, no switching occurs. Otherwise, the system switches services from the main board to the standby board or from the standby board to the main board according to the command. The switching then changes to the manual switching state. When the switching is in the automatic switching state and the main equipment is already restored to normal for the WTR time, the revertive switching occurs. From the time when the main equipment is restored to normal to the time when the revertive switching occurs, the switching is in the WTR state. After the revertive switching, the switching changes to the normal state.
Revertive switching (valid only in revertive mode)
Table 8-2 Trigger conditions of the automatic HSB switching Switching Condition Hardware fault on the IF board Hardware fault on the ODU
Issue 05 (2010-10-30)
Description At the same priority
8-9
8 1+1 FD
Switching Condition POWER_ALM VOLT_LOS (IF board) RADIO_TSL_HIGH RADIO_TSL_LOW RADIO_RSL_HIGH IF_INPWR_ABN CONFIG_NOSUPPORT XPIC_LOS (IFX) Fault on the IF connection cable
Description
Trigger Conditions of the HSM Switching

HSM switching occurs at the channel side. Channel-side switching is available in the following types: l Forced switching The forced switching refers to the HSM switching that occurs at the same time the HSB switching occurs, in the case of the SDH/PDH microwave. After the forced switching, the IF board receives its own baseband signal. l Automatic switching The automatic switching refers to the HSM switching that is automatically triggered. After automatic switching, the IF board receives baseband signals from the IF board in the paired slot. In the case of the Hybrid microwave, the automatic HSM switching is triggered by the quality degradation of the signal on the main channel. In the case of the SDH/PDH microwave, the automatic HSM switching is triggered by the conditions listed in Table 8-3. Table 8-3 Trigger conditions of the automatic HSM switching Switching Condition R_LOC R_LOF R_LOS MW_LOF MW_FEC_UNCOR Medium Priority High
8-10
Issue 05 (2010-10-30)
8 1+1 FD
Switching Condition B1_SD (When the IF board works in PDH mode.) B2_SD (When the IF board works in SDH mode.)
Priority Low
NOTE
The trigger conditions of automatic HSM switching are classified into three levels: high, medium, and low. If service alarms are reported on the main and standby IF boards, switching occurs only when the alarm on the main IF board has a higher priority than the alarm on the standby IF board. For example, if the MW_FEC_UNCOR alarm is reported on the main IF board and the B2_SD alarm is reported on the standby IF board, switching occurs; if the MW_FEC_UNCOR alarm is reported on the main and standby IF board, no switching occurs.
Revertive switching After the automatic HSM switching occurs, the IF board attempts to perform a revertive switching action periodically. If no service alarm occurs on the main channel at this time, the IF board releases the switching.
NOTE
When the AM function is enabled, the standby channel works in modulation mode for ensuring capacity after the HSM switching occurs. Hence, services of a lower priority are damaged.

In the case of the HSB switching, the services are interrupted within the HSB switching time (shorter than 500 ms). In the case of the HSM switching, the service is not affected because it is the hitless switching, when the AM function is enabled, the standby channel works in the modulation mode for ensuring capacity after the HSM switching. Hence, the service of a low priority may be damaged.
8.3 Specifications
This section describes the specifications of 1+1 FD. Table 8-4 provides the specifications of 1+1 FD. Table 8-4 Specifications of 1+1 FD Item Microwave type Specifications SDH/PDH microwave Hybrid microwave Number of protection groups HSB Switching time 1 to 2 < 500 ms
Issue 05 (2010-10-30)
8-11
8 1+1 FD
Item Switching mode
Specifications HSB HSM
Protection type
Revertive mode Non-revertive mode
WTR time Reverse switching Restriction on the available slot of the IF board
5 to 12 minutes Not supported Installed in paired slots 5 and 7 or paired slots 6 and 8
8.4 Availability
This section describes the support required by the application of the 1+1 FD feature and its dependency.

Table 8-5 Hardware and version support Feature 1+1 FD Applicable Board IF0A IF0B IF1A IF1B IFH2 IFX Applicable Hardware Version All the versions All the versions All the versions All the versions All the versions All the versions Applicable Product Version V100R002 and later V100R002 and later V100R001 and later V100R001 and later V100R003 and later V100R002 and later
Feature Dependency
l The configuration mode of 1+1 protection in one direction can only be 1+1 HSB, 1+1 FD, or 1+1 SD. The configuration mode in one direction can be different from that in another direction. The two IP boards in an XPIC group cannot be configured into one 1+1 FD protection group. However, these boards can be configured into two 1+1 FD protection groups with the two IF boards in another XPIC group in the same polarization direction. The members of the 1+1 FD protection group cannot participate in the N+1 protection.
8-12
Issue 05 (2010-10-30)
8 1+1 FD
l l l
The radio link with 1+1 FD configuration can function as the working source, protection source, or service sink of SNCP. The AM function can be enabled in the case of 1+1 FD Hybrid radio links. On the AM-enabled 1+1 FD Hybrid radio link, after an HSB switching, the standby link works in the modulation mode of the original active link; after an HSM switching, the standby link works in the guaranteed capacity modulation mode.
8.5 Principles
The switching principle of SDH/PDH radio 1+1 FD is different from the switching principle of Hybrid radio 1+1 FD. 8.5.1 SDH/PDH Radio The cross-connect unit implements HSB switching by receiving TDM services from the standby IF board; the IF board implements HSM switching by receiving baseband signals from the standby channel. 8.5.2 Hybrid Radio The cross-connect unit implements HSB switching on the TDM plane by selecting TDM services from the standby IF board; the packet switching unit implements HSB switching on the packet plane through LAG switching; the IF board implements HSM switching by receiving baseband signals from the standby channel.
8.5.1 SDH/PDH Radio

The cross-connect unit implements HSB switching by receiving TDM services from the standby IF board; the IF board implements HSM switching by receiving baseband signals from the standby channel.

Figure 8-6 1+1 FD realization principle (before the switching, in the transmit direction)
Antenna f1 Main ODU Main Cross-connect board IF board Service board
f2
Antenna
Standby ODU
Standby IF board
In the transmit direction: 1. 2. The service interface unit transmits the received service signal to the cross-connect unit. The cross-connect unit transmits the service signal to both the main IF board and the standby IF board.
Issue 05 (2010-10-30)
8 1+1 FD
3. 4.
The main IF board and the standby IF board send the processed IF analog signal to the main ODU and the standby ODU respectively. The main ODU and the standby ODU output RF signals at different frequencies and send the signals to their corresponding antennas.
Figure 8-7 1+1 FD realization principle (before the switching, in the receive direction)
Antenna Main ODU Main IF board Cross-connect board Service board
Antenna
Standby ODU
Standby IF board
In the receive direction: 1. 2. 3. 4. 5. 6. The antennas receive RF signals and send the signals to their corresponding (main and standby) ODUs. The main ODU and the standby ODU send the processed IF analog signal to the main IF board and the standby IF board respectively. The main IF board sends the processed baseband signal to its MUX unit. The standby IF board sends the processed baseband signal to the MUX units of itself and its paired board. The main IF board and the standby IF board select their own baseband signals. The cross-connect unit selects the service signal from the main IF board and transmits the service signal to the service interface unit. The service interface unit sends the service signal to other equipment.
After the Switching

Figure 8-8 1+1 FD HSB realization principle (after the switching, in the receive direction)
Antenna
Standby ODU
Standby IF board
After the 1+1 FD HSB switching:

8 1+1 FD
l l
In the receive direction, the IF boards receive their own service signals and the crossconnect unit selects the signal from the standby IF board. In the transmit direction, signals need not be processed.
Figure 8-9 1+1 FD HSM realization principle (after the switching, in the receive direction)
Antenna
Standby ODU
Standby IF board
After the 1+1 FD HSM switching: l l In the receive direction, the IF board selects the baseband signal from its paired IF board. In the transmit direction, signals need not be processed.
NOTE
The actions involved in the 1+1 FD protection switching occur on the faulty NE. These actions do not occur on the normal NE.
8.5.2 Hybrid Radio

The cross-connect unit implements HSB switching on the TDM plane by selecting TDM services from the standby IF board; the packet switching unit implements HSB switching on the packet plane through LAG switching; the IF board implements HSM switching by receiving baseband signals from the standby channel.

Figure 8-10 1+1 FD realization principle (before the switching, in the transmit direction)
Antenna f1 Main ODU Main IF board Cross-connect board Service board
f2 Antenna Standby ODU Standby IF board EMS6 board
Issue 05 (2010-10-30)
8-15
8 1+1 FD
In the transmit direction: 1. 2. 3. The service board multiplexes the received E1 service signal into the VC-4 and then sends the VC-4 to the cross-connect board. The cross-connect board transmits the E1 service signal in the VC-4 to the main IF board and the standby IF board. The Ethernet service port of the main IF board is in LinkUp state, whereas the Ethernet service port of the standby IF board is in LinkDown state. The Ethernet board EMS6 transmits the Ethernet service to the Ethernet service port of the main IF board through the LAG function. The MUX unit of the main IF board multiplexes the E1 service signal and Ethernet service signal into the Hybrid microwave frame. The MUX unit of the standby IF board multiplexes the E1 service signal and Ethernet service signal into the non-standard Hybrid microwave frame. The IF processing units of the main IF board and the standby IF board receive the Hybrid microwave frame that is multiplexed by the main IF board and modulate the Hybrid microwave frame into the analog IF signal. Then, the IF processing units of the main IF board and the standby IF board send the analog IF signal to the main ODU and the standby ODU respectively. The main ODU transmits the RF signal at frequency f1 to the main antenna. The standby ODU transmits the RF signal at frequency f2 to the standby antenna.
NOTE
4.
5.
6.
Figure 8-11 1+1 FD realization principle (before the switching, in the receive direction)
Antenna
f2
Standby ODU
Standby IF board
EMS6 board
In the receive direction: 1. The antennas receive RF signals at different frequencies and send the signals to their corresponding main ODU and standby ODU.
8-16
8 1+1 FD
2. 3.
The main ODU and the standby ODU send the processed analog IF signal to the main IF board and the standby IF board respectively. The main IF board and the standby IF board demodulate the Hybrid frame from the IF signal. The Hybrid microwave frame of the standby IF board is transmitted to the main IF board through the protection bus. The MUX units of the main IF board and the standby IF board receive the Hybrid frame that is demultiplexed from their corresponding IF board and then separate the Hybrid frame into the E1 service signal and Ethernet service signal. The E1 service signal is transmitted to the cross-connect board after being multiplexed into the VC-4. The Ethernet service signal is transmitted to the Ethernet service port of the IF board. The cross-connect board receives the E1 service signal from the main IF board and crossconnects the service signal to the corresponding service board. The EMS6 board receives the Ethernet service signal from the main IF board because the Ethernet service port of the main IF board is in LinkUp state whereas the Ethernet service port of the standby IF board is in LinkDown state.
4.
5.
6. 7.
After the Switching

f2 Antenna Standby ODU Standby IF board EMS6 board
Issue 05 (2010-10-30)
8-17
8 1+1 FD
Figure 8-13 1+1 FD HSB realization principle (after the switching, in the receive direction)
Antenna
f2
Standby ODU
Standby IF board
EMS6 board
After a 1+1 FD HSB switching: l In the transmit direction: The Ethernet service port of the main IF board is in LinkDown state and the Ethernet service port of the standby IF board is in LinkUp state. The IF processing units of the main IF board and the standby IF board modulate the Hybrid microwave frame that is multiplexed by the MUX unit of their corresponding IF board into the analog IF signal. The main IF board and the standby IF board send the analog IF signal to the main ODU and the standby ODU respectively. The main ODU transmits the RF signal at frequency f1 to the main antenna and the standby ODU transmits the RF signal at frequency f2 to the standby antenna. l In the receive direction: The Hybrid microwave frame demultiplexed by the main IF board is transmitted to the standby IF board through the protection bus. The MUX unit of the main IF board receives the Hybrid microwave frame that is multiplexed by the main IF board and then separates the Hybrid microwave frame into the E1 service signal and Ethernet service signal. The MUX unit of the standby IF board receives the Hybrid microwave frame that is multiplexed by the standby board and then separates the Hybrid microwave frame into the E1 service signal and Ethernet service signal. The Ethernet service port of the main IF board is in LinkDown state and the Ethernet service port of the standby IF board is in LinkUp state. The cross-connect board and the EMS6 board receive the service signal from the standby IF board.
8-18
Issue 05 (2010-10-30)
8 1+1 FD
Figure 8-14 1+1 FD HSM realization principle (after the switching, in the receive direction)
Antenna
f2
Standby ODU
Standby IF board
EMS6 board
After a 1+1 FD HSM switching: l l In the transmit direction, no processing is required. In the receive direction: The MUX unit of the main IF board receives the demodulated Hybrid signal frame that is transmitted from the standby IF board through the protection bus and then separates the Hybrid microwave frame into the E1 service signal and Ethernet service signal. The crossconnect board and the EMS6 board receive the service signal from the main IF board.
NOTE
The actions involved in the 1+1 FD protection switching occur on the faulty NE. These actions do not occur on the normal NE.

Follow certain principles when you plan 1+1 FD. Plan the parameters relevant to the protection configuration. l If the protection is in the revertive mode, set the WTR time to a value, which ranges from five minutes to twelve minutes. It is recommended that you set the default value to ten minutes. The spacing between the emission frequency of the main ODU and that of the standby ODU should be greater than 56 MHz to prevent adjacent-channel interference. In the case of the OptiX RTN 620, a pair of main and standby IF boards must be installed in slots 5 and 7 (the IF board in slot 5 is the main board) or in slots 6 and 8 (the IF board in slot 6 is the main board).
l l

When configuring a radio link under 1+1 FD protection, you need to configure a 1+1 IF protection group and then configure IF/ODU information.
8 1+1 FD
Table 8-6 Configuration procedure of 1+1 FD Step 1 Operation A.5.1 Creating an IF 1+1 Protection Group A.5.3 Configuring the IF/ODU Information of a Radio Link A.5.9 Setting Parameters of ODU Interfaces Description The parameters need to be set according to the network planning.
In the case of radio links configured with 1+1 FD, you need to configure the IF and ODU information on the working radio link and the ODU information on the protection radio link. The parameters need to be set according to the network planning. The parameters need to be set according to the network planning.
NOTE

This section uses an example to describe how to plan and configure 1+1 FD according to network conditions. 8.8.1 Networking Diagram The section describes the networking information about the NEs. 8.8.2 Service Planning The service planning information contains all the parameters required for configuring the NE data. 8.8.3 Configuration Process This section describes the procedure of data configuration.

The section describes the networking information about the NEs. To ensure the reliable transmission of services on a hop of radio link constructed by OptiX RTN 620s, you need to configure 1+1 FD for the radio link between NE1 and NE2, as shown in Figure 8-15.
8-20
Issue 05 (2010-10-30)
8 1+1 FD
Figure 8-15 1+1 FD protection networking diagram
NE2
NE1

The service planning information contains all the parameters required for configuring the NE data. l Plan the slots of the working board and the protection board. Plan the slots for the working board and the protection board based on the board configurations. To be specific, the IF board in slot 5 functions as the working board, and the IF board in slot 7 functions as the protection board. l Plan the protection group parameters. The 1+1 protection mode is FD, providing the channel and equipment protection function. Unless otherwise specified, all the parameters take the default values. Note that reverse switching is not available in 1+1 FD mode. l Plan the radio link information. The radio link information is determined according to the network planning. The parameters are listed in the following table.
NOTE
In the case of 1+1 FD radio links, one protection group corresponds to one link. Thus, you need to configure the IF/ODU information for the main equipment and the ODU information for the standby equipment.
Table 8-7 IF planning information Parameter NE1 5-IFH2 Link ID Channel spacing (MHz) AM enabling AM guaranteed capacity mode AM full capacity mode E1 capacity ATPC status 101 28M Enabled QPSK 128QAM 16 Disabled NE2 5-IFH2 101 28M Enabled QPSK 128QAM 16 Disabled
Issue 05 (2010-10-30)
8-21
8 1+1 FD
Table 8-8 RF planning information Parameter NE1 15-ODU Transmit frequency (MHz) T/R spacing (MHz) Transmit power (dBm) Receive power (dBm) Transmission status 14930 17-ODU 15000 NE2 15-ODU 14510 17-ODU 14580
420 10 -45 unmute
420 10 -45 unmute
420 10 -45 unmute
420 10 -45 unmute

Procedure
Step 1 A.5.1 Creating an IF 1+1 Protection Group. The following table provides the values of parameters. Parameter Value Range NE1 Working Mode Revertive Mode WTR Time (s) Working Board Protection Board FD Revertive mode (default value) 600 seconds (default value) 5-IFH2 7-IFH2 NE2 FD Revertive mode (default value) 600 seconds (default value) 5-IFH2 7-IFH2
Step 2 A.5.3 Configuring the IF/ODU Information of a Radio Link. The following table provides the values of IF board parameters.
8-22
Issue 05 (2010-10-30)
8 1+1 FD
Parameter
Value Range NE1 5-IFH2 NE2 5-IFH2 Enabled 28M QPSK 128QAM 16 101 Disabled
AM Enable Status IF Channel Bandwidth Modulation Mode of the Assured AM Capacity Modulation Mode of the Full AM Capacity E1 Capacity Link ID ATPC Enable Status
Enabled 28M QPSK 128QAM 16 101 Disabled
Step 3 A.5.9 Setting Parameters of ODU Interfaces. The following table provides the values of ODU parameters. Parameter Value Range NE1 15-ODU TX Frequency (MHz) T/R Spacing (MHZ) TX Power (dBm) Power to Be Received (dBm) TX Status 14930 420 10 -45 17-ODU 15000 420 10 -45 NE2 15-ODU 14510 420 10 -45 17-ODU 14580 420 10 -45
Unmute
Unmute
Unmute
Unmute
----End
8.9 Task Collection

This section provides the hyperlinks of the operation tasks associated with 1+1 FD.
Issue 05 (2010-10-30)
8-23
8 1+1 FD
Related Tasks
A.5.1 Creating an IF 1+1 Protection Group A.5.3 Configuring the IF/ODU Information of a Radio Link A.5.13 Querying the IF 1+1 Protection Status A.5.15 Performing IF 1+1 Protection Switching

When a 1+1 FD switching occurs on IF boards, the system reports corresponding alarms and abnormal events.
Relevant Alarms

8.11 FAQs
This section provides the answers to the questions that are frequently raised when 1+1 FD is used. Q: During the configuration of the 1+1 FD protection, is it necessary to configure the IF interface of the standby IF board? A: It is unnecessary. The system automatically copies the data of the main IF board to the standby IF board. But, it is necessary to configure the ODU interface data of both the main ODU and the standby ODU on the NMS. Q: Why does the configuration of the 1+1 FD protection fail? A: Common causes are as follows: l l l The IF board and the corresponding ODU that form the 1+1 FD protection are not included in the slot layout. The main IF board and the standby IF board are not configured in paired slots. The standby IF board is configured with services.
Q: Why the reverse switching cannot be set in the 1+1 FD mode? A: In the 1+1 FD mode, both the main ODU and the standby ODU are not muted. Hence, the source end cannot clear the service alarm at the sink end by switching the working ODU. The reverse switching is invalid for the 1+1 FD mode.
8-24
Issue 05 (2010-10-30)
8 1+1 FD
Q: When radio links work as ECC links, why is the NMS unable to receive the abnormal HSB switching event of the non-gateway NE? A: When an HSB switching occurs, the ECC needs to reroute. As a result, the ECC between the gateway NE and the non-gateway NE is transiently interrupted and the switching event cannot be reported. Q: How to deal with the 1+1 FD switching failure? A: If the 1+1 FD switching fails, check whether the protection groups are correctly configured, and then check whether the standby devices (including ODUs and IF boards) and standby radio link are normal. Exclude the fault that the RSL is low because of signal interference and antenna unalignment.
Issue 05 (2010-10-30)
8-25
9 1+1 SD
9
About This Chapter
This chapter describes the 1+1 space diversity (SD) feature. 9.1 Introduction This section provides the definition of 1+1 SD and describes its purpose. 9.2 Basic Concepts This section describes the basic concepts associated with 1+1 SD. 9.3 Specifications This section describes the specifications of 1+1 SD.
1+1 SD
9.4 Availability This section describes the support required by the application of the 1+1 SD feature and its dependency. 9.5 Principles The switching principle of SDH/PDH radio 1+1 FD is different from the switching principle of Hybrid radio 1+1 FD. 9.6 Planning Guidelines Follow certain guidelines when you plan 1+1 SD. 9.7 Configuration Procedure When configuring a radio link with 1+1 SD, you need to configure a 1+1 IF protection group and then configure IF/ODU information. 9.8 Configuration Example This section uses an example to describe how to plan and configure 1+1 SD according to network conditions. 9.9 Task Collection This section provides the hyperlinks of the operation tasks associated with 1+1 SD. 9.10 Relevant Alarms and Events When a 1+1 SD switching occurs on IF boards, the system reports corresponding alarms and abnormal events. 9.11 FAQs
9 1+1 SD
This section provides the answers to the questions that are frequently raised when 1+1 SD is used.
9-2
Issue 05 (2010-10-30)
9 1+1 SD
9.1 Introduction
This section provides the definition of 1+1 SD and describes its purpose.
Definition
1+1 SD is a configuration mode of 1+1 protection. In 1+1 SD protection mode, the system uses two antennas that have a space distance between them, to receive the same RF signals. The equipment then selects a signal from the two received RF signals. With 1+1 SD, the impact of fading on signal transmission is reduced. Figure 9-1 shows the application of 1+1 SD. If NE2 detects that bit errors occur in the service on the main channel when the quality of the signal received on the main channel is degraded, NE2 switches to the standby channel to receive the service. Figure 9-1 1+1 SD protection
Before the Switching Main channel
T2 T2 T1
Main channel Rx Tx
T1
MODEM MODEM Service Service MODEM MODEM Standby channel
Rx Tx
MODEM MODEM Service Service
Tx Rx
T2 T1
Tx Rx
MODEM MODEM
Standby channel
NE1
After the Switching Main channel
T2
NE2
T2 T1
Main channel Rx Tx MODEM MODEM Service Service
MODEM MODEM Service Service MODEM MODEM Standby channel
Rx Tx
T1
Tx Rx
T2 T1
Tx Rx
MODEM MODEM
Standby channel
NE1
Change spot
NE2
In the case of the 1+1 SD protection, the two antennas at the receive end receive the same RF signals from the transmit end. When the quality of the microwave signal that is received by the main antenna is degraded, bit errors may occur in the service on the main channel. Due to multipath fading, the quality of the signal that is received by the standby antenna may not be degraded. In this case, the service unit receives the service from the standby receive channel to protect the service. In addition, the 1+1 SD protection supports 1+1 HSB protection switching.
9 1+1 SD
Purpose
A radio link configured with 1+1 FD has a higher anti-fading capability (especially antimultipath fading) and reliability than a radio link configured with 1+0 non-protection.
9.2 Basic Concepts

This section describes the basic concepts associated with 1+1 SD. 9.2.1 System Configuration 1+1 SD requires specific system configuration. 9.2.2 Protection Type The 1+1 SD protection is classified into the revertive mode and the non-revertive mode. 9.2.3 Switching Condition The 1+1 SD protection supports two types of switching, namely, HSB switching and HSM switching. The two types of switching are triggered by different conditions. 9.2.4 Switching Impact In the case of the HSB switching, the services are interrupted within the HSB switching time (less than 500 ms). In the case of the HSM switching, the service is not affected because the HSM switching is hitless. When the AM function is enabled, the standby channel works in modulation mode for ensuring capacity after the HSM switching occurs. Hence, services of a lower priority are damaged.

1+1 SD requires specific system configuration.
Typical Configuration of SDH/PDH Radio 1+1 SD

One 1+1 SD protection group uses one channel and consists of the following items: l l l Two IF boards that are of the same type Two ODUs that are of the same type Two antennas
NOTE
The IF board can be the IF0A board, IF0B board, IF1A board, IF1B board, IFX, or IFH2 board.
Figure 9-2 shows a typical configuration of one SDH/PDH radio 1+1 SD protection group on the OptiX RTN 620.
9-4
Issue 05 (2010-10-30)
9 1+1 SD
Figure 9-2 Typical configuration of 1+1 SD (OptiX RTN 620)
ODU
Antenna
ODU
Antenna
EXT IF FAN
Slot 20
EXT EXT EXT PH1 SCC
EXT IF PXC PXC

IDU 620
Typical Configuration of Hybrid Radio 1+1 SD

One 1+1 SD protection group uses one channel and consists of the following items: l l l l Two IF boards that are of the same type One EMS6 board or EFP6 board Two ODUs that are of the same type Two antennas
NOTE
The type of the IF board is IFH2.
Figure 9-3 shows a typical configuration of one Hybrid radio 1+1 SD protection group on the OptiX RTN 620.
Issue 05 (2010-10-30)
9-5
9 1+1 SD
Figure 9-3 Typical configuration of 1+1 SD (OptiX RTN 620)
ODU
Antenna
ODU
Antenna
Network cable
To the external equipment

EXT IF FAN
Slot 20
EXT IF PXC PXC

IDU 620
ODU
Antenna To the external PDH networking
ODU
Antenna
Network cable
EXT IF FAN
Slot 20
EXT IF PXC PXC

IDU 620

The 1+1 SD protection is classified into the revertive mode and the 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 former working channel is restored to normal for a certain period. The period from the time when the former working channel is restored to normal to the time when the NE releases the switching is called the WTR time. To prevent frequent switching
9 1+1 SD
events because the former working channel is not stable, it is recommended that you set the WTR time to 5 to 12 minutes. l Non-revertive mode When an NE is in the switching state, the NE remains the current state unchanged unless another switching event occurs even though the former working channel is restored to normal.
NOTE
Both the revertive mode and non-revertive mode are only associated with HSB switching (switching on the equipment side). After HSM switching on the channel side, revertive switching periodically occurs on the IF board, regardless of the revertive mode.

The 1+1 SD protection supports two types of switching, namely, HSB switching and HSM switching. The two types of switching are triggered by different conditions.
Trigger Conditions of the HSB Switching

The HSB switching occurs on the equipment side. The equipment-side switching has the same switching action and switching impact as the 1+1 HSB switching but is triggered by different conditions. Table 9-1 Trigger conditions of the 1+1 SD HSB switching Switching Condition Clear switching (external switching) Priority From top downwards, the priority is from the highest to the lowest. Description All external switching states are cleared.
In any state, the switching changes to the lockout state. In the lockout state, no switching occurs until the lockout of protection is cleared. If the switching is in the lockout state, no forced switching occurs. Otherwise, the system switches services from the main board to the standby board or from the standby board to the main board according to the command. The switching then changes to the forced switching state.
9-7
Issue 05 (2010-10-30)
9 1+1 SD
Switching Condition Fault on the main equipment
Priority
Description If the switching is in the lockout or forced switching state, or if the current standby equipment is faulty, no HSB switching occurs. Otherwise, the system switches services from the current main board to the standby board. The switching then changes to the automatic switching state. For the trigger conditions of the automatic switching, refer to Table 9-2. When both the main IF board and the standby IF board at the sink end report service alarms, they send the alarms to the source end by using the MWRDI overhead in the microwave frame. If the source end is in the lockout or forced switching state, or if the current standby equipment is faulty, no reverse switching occurs. Otherwise, the HSB switching occurs at the source end after the reverse switching timer expires. The reverse switching timer restarts after you successfully add a protection group or if an HSB switching event occurs. The timer duration is the WTR time (in revertive mode) or 5 minutes (in nonrevertive mode). After the reverse switching, the switching changes to the RDI state.
Reverse switching (valid only when the reverse switching is enabled)
9-8
Issue 05 (2010-10-30)
9 1+1 SD
Switching Condition Manual switching (external switching)
Priority
Description If the switching is in the lockout, forced switching, or RDI state, or if the current standby equipment is faulty, no switching occurs. Otherwise, the system switches services from the main board to the standby board or from the standby board to the main board according to the command. The switching then changes to the manual switching state. When the switching is in the automatic switching state and the main equipment is already restored to normal for the WTR time, the revertive switching occurs. From the time when the main equipment is restored to normal to the time when the revertive switching occurs, the switching is in the WTR state. After the revertive switching, the switching changes to the normal state.
Table 9-2 Trigger conditions of the automatic HSB switching Switching Condition Hardware fault on the IF board Hardware fault on the ODU POWER_ALM VOLT_LOS (IF board) RADIO_TSL_HIGH RADIO_TSL_LOW RADIO_RSL_HIGH IF_INPWR_ABN CONFIG_NOSUPPORT XPIC_LOS (IFX) Priority At the same priority
Issue 05 (2010-10-30)
9-9
9 1+1 SD
Switching Condition Fault on the IF connection cable
Priority
Trigger Conditions of the HSM Switching

HSM switching is switching that occurs at the channel side. Channel-side switching is available in the following types: l Forced switching Forced switching refers to HSM switching that occurs at the same time HSB switching occurs. After forced switching, the IF board receives baseband signals from itself. l Automatic switching Automatic switching refers to HSM switching that is automatically triggered. After automatic switching, the IF board receives baseband signals from the IF board in the paired slot. In the case of the Hybrid microwave, the automatic HSM switching is triggered by the quality degradation of the signal on the main channel. In the case of the SDH/PDH microwave, the automatic HSM switching is triggered by the conditions listed in Table 9-3. Table 9-3 Trigger conditions of the automatic HSM switching Switching Condition R_LOC R_LOF R_LOS MW_LOF MW_FEC_UNCOR B1_SD (When the IF board works in PDH mode.) B2_SD (When the IF board works in SDH mode.) Medium Low Priority High
NOTE
The trigger conditions of automatic HSM switching are classified into three levels: high, medium, and low. If service alarms are reported on the main and standby IF boards, switching occurs only when the alarm on the main IF board has a higher priority than the alarm on the standby IF board. For example, if the MW_FEC_UNCOR alarm is reported on the main IF board and the B2_SD alarm is reported on the standby IF board, switching occurs; if the MW_FEC_UNCOR alarm is reported on the main and standby IF board, no switching occurs.
l
9-10
Revertive switching
9 1+1 SD
After automatic HSM switching, revertive switching periodically occurs on the IF board. If there is no service alarm on the active channel at this time, the IF board releases the switching.
NOTE
When the AM function is enabled, the standby channel works in modulation mode for ensuring capacity after the HSM switching occurs. Hence, services of a lower priority are damaged.

In the case of the HSB switching, the services are interrupted within the HSB switching time (less than 500 ms). In the case of the HSM switching, the service is not affected because the HSM switching is hitless. When the AM function is enabled, the standby channel works in modulation mode for ensuring capacity after the HSM switching occurs. Hence, services of a lower priority are damaged.
9.3 Specifications
This section describes the specifications of 1+1 SD. Table 9-4 provides the specifications of 1+1 SD. Table 9-4 Specifications of 1+1 SD Item Microwave type Specifications SDH/PDH microwave Hybrid microwave Number of protection groups HSB Switching time Switching mode 1 to 2 < 500 ms HSB HSM Protection type Revertive mode Non-revertive mode WTR time Reverse switching Restriction on the available slot of the IF board 5 to 12 minutes Supported Installed in paired slots 5 and 7 or paired slots 6 and 8
9.4 Availability
This section describes the support required by the application of the 1+1 SD feature and its dependency.
9 1+1 SD

Table 9-5 Hardware and version support Feature 1+1 SD Applicable Board IF0A IF0B IF1A IF1B IFH2 IFX Applicable Hardware Version All the versions All the versions All the versions All the versions All the versions All the versions Applicable Product Version V100R002 and later V100R002 and later V100R001 and later V100R001 and later V100R003 and later V100R002 and later
Feature Dependency
l The configuration mode of 1+1 protection in one direction can only be 1+1 HSB, 1+1 FD, or 1+1 SD. The configuration mode in one direction can be different from that in another direction. The two IP boards in an XPIC group cannot be configured into one 1+1 SD protection group. However, these boards can be configured into two 1+1 SD protection groups with the two IF boards in another XPIC group in the same polarization direction. The members of the 1+1 SD protection group cannot participate in the N+1 protection. The radio link that is configured with the 1+1 SD protection can work as the working source, protection source, or service sink of the SNCP. The AM function can be enabled in the case of 1+1 SD Hybrid radio links. If the hybrid radio links are configured with the 1+1 SD protection and if the AM function is enabled, the standby link works in existing modulation mode of the main link after the HSB switching occurs, and works in modulation mode of the guaranteed capacity after the HSM switching occurs.
l l l l
9.5 Principles
The switching principle of SDH/PDH radio 1+1 FD is different from the switching principle of Hybrid radio 1+1 FD. 9.5.1 SDH/PDH Radio The cross-connect unit implements HSB switching by receiving TDM services from the standby IF board. The IF board implements HSM switching by receiving baseband signals from the standby channel. 9.5.2 Hybrid Radio The cross-connect unit implements HSB switching on the TDM plane by selecting TDM services from the standby IF board; the packet switching unit implements HSB switching on the packet plane through LAG switching; the IF board implements HSM switching by receiving baseband signals from the standby channel.
9 1+1 SD
9.5.1 SDH/PDH Radio

The cross-connect unit implements HSB switching by receiving TDM services from the standby IF board. The IF board implements HSM switching by receiving baseband signals from the standby channel.

Figure 9-4 1+1 SD realization principle (before the switching, in the transmit direction)
Antenna Main ODU Main Cross-connect board IF board Service board
Antenna
Standby ODU
Standby IF board
In the transmit direction: 1. 2. 3. 4. The service board sends the received service signal to the cross-connect board. The cross-connect board transmits the service signal to both the main IF board and the standby IF board. The main IF board and the standby IF board send the processed IF analog signal to the main ODU and the standby ODU respectively. The main ODU transmits the RF signal to the antenna. The standby ODU mutes (that is, the standby ODU does not send the RF signal).
Figure 9-5 1+1 SD realization principle (before the switching, in the receive direction)
Antenna
Standby ODU
Standby IF board
In the receive direction: 1.

Issue 05 (2010-10-30)
The antennas receive RF signals and send the signals to their respective ODUs.
9 1+1 SD
2. 3. 4. 5. 6.
The main ODU and the standby ODU send the processed IF analog signal to the main IF board and the standby IF board respectively. The multiplex unit of the IF board sends the processed baseband signal to itself and to the multiplex unit of its paired board. The main IF board and the standby IF board select their own baseband signal. The cross-connect board selects the service signal from the main IF board and sends the signal to the service board. The service board sends the service signal to the equipment at the opposite end.
After the Switching

Figure 9-6 1+1 SD HSB realization principle (after the switching, in the receive direction)
Antenna
Standby ODU
Standby IF board
Figure 9-7 1+1 SD HSB realization principle (after the switching, in the transmit direction)
Antenna Main ODU Main Cross-connect board IF board Service board
Antenna
Standby ODU
Standby IF board
After a 1+1 SD HSB switching: l l In the receive direction, the IF boards select their own service signal. The cross-connect board selects the signal from the standby IF board. In the transmit direction, the standby ODU transmits the RF signal to the antenna. The main ODU mutes (that is, the main ODU does not send the RF signal).
9-14
Issue 05 (2010-10-30)
9 1+1 SD
Figure 9-8 1+1 SD HSM realization principle (after the switching, in the receive direction)
Antenna
Standby ODU
Standby IF board
After a 1+1 SD HSM switching: l l In the receive direction, the IF boards select the baseband signal from their own paired IF board. In the transmit direction, no processing is required.
NOTE
The actions involved in the 1+1 SD protection switching occur on the faulty NE. These actions do not occur on the normal NE.
9.5.2 Hybrid Radio

The cross-connect unit implements HSB switching on the TDM plane by selecting TDM services from the standby IF board; the packet switching unit implements HSB switching on the packet plane through LAG switching; the IF board implements HSM switching by receiving baseband signals from the standby channel.

Figure 9-9 1+1 SD realization principle (before the switching, in the transmit direction)
Antenna
Standby ODU
Standby IF board
EMS6 board
Issue 05 (2010-10-30)
9-15
9 1+1 SD
In the transmit direction: 1. 2. 3. The service board multiplexes the received E1 service signal into the VC-4 and then sends the VC-4 to the cross-connect board. The cross-connect board transmits the E1 service signal in the VC-4 to the main IF board and the standby IF board. The Ethernet service port of the main IF board is in LinkUp state, whereas the Ethernet service port of the standby IF board is in LinkDown state. The Ethernet board EMS6 transmits the Ethernet service to the Ethernet service port of the main IF board through the LAG function. The MUX unit of the main IF board multiplexes the E1 service signal and Ethernet service signal into the Hybrid microwave frame. The MUX unit of the standby IF board multiplexes the E1 service signal and Ethernet service signal into the non-standard Hybrid microwave frame. The IF processing units of the main IF board and the standby IF board receive the Hybrid microwave frame that is multiplexed by the main IF board and modulate the Hybrid microwave frame into the analog IF signal. Then, the IF processing units of the main IF board and the standby IF board send the analog IF signal to the main ODU and the standby ODU respectively. The main ODU transmits the RF signal to the antenna. The standby ODU is muted (that is, the standby ODU does not transmit the RF signal).
NOTE
4.
5.
6.
Figure 9-10 1+1 SD realization principle (before the switching, in the receive direction)
Antenna
Standby ODU
Standby IF board
EMS6 board
In the receive direction: 1. 2. The antennas receive RF signals and transmit the signals to their corresponding main ODU and standby ODU. The main ODU and the standby ODU send the processed analog IF signal to the main IF board and the standby IF board respectively.
9-16
9 1+1 SD
3.
The main IF board and the standby IF board demodulate the IF signal into the Hybrid microwave frame. The Hybrid microwave frame of the standby IF board is transmitted to the main IF board through the protection bus. The MUX units of the main IF board and the standby IF board receive the Hybrid frame that is demultiplexed from their corresponding IF boards and then separate the Hybrid frame into the E1 service signal and Ethernet service signal. The E1 service signal is transmitted to the cross-connect board after being multiplexed into the VC-4. The Ethernet service signal is transmitted to the Ethernet service port of the IF board. The cross-connect board receives the E1 service signal from the main IF board and crossconnects the service signal to the corresponding service board. The EMS6 board receives the Ethernet service signal from the main IF board because the Ethernet service port of the main IF board is in LinkUp state whereas the Ethernet service port of the standby IF board is in LinkDown state.
4.
5.
6. 7.
After the Switching

Figure 9-11 1+1 SD HSB realization principle (after the switching, in the receive direction)
Antenna
Standby ODU
Standby IF board
EMS6 board
Issue 05 (2010-10-30)
9-17
9 1+1 SD
Figure 9-12 1+1 SD HSB realization principle (after the switching, in the transmit direction)
Antenna
Standby ODU
Standby IF board
EMS6 board
After a 1+1 SD HSB switching: l In the receive direction: The MUX unit of the standby IF board receives the Hybrid microwave frame that is multiplexed by the standby IF board. The cross-connect board receives the E1 service signal that is demultiplexed from the Hybrid microwave frame received at the standby IF board and cross-connects the E1 service signal to the corresponding service board. The EMS6 board receives the Ethernet service signal from the standby IF board because the Ethernet service port of the main IF board is in LinkDown state and the Ethernet service port of the standby IF board is in LinkUp state. l In the transmit direction: The Ethernet service port of the main IF board is in LinkDown state. The Ethernet service port of the standby IF board is in LinkUp state. The main IF board and the standby IF board receive the Hybrid microwave frame that is multiplexed by the standby IF board and then transmit the modulated Hybrid microwave frame to the main ODU and the standby ODU respectively. The standby ODU transmits the RF signal to the antenna. The main ODU is muted (that is, the main ODU does not transmit the RF signal).
9-18
Issue 05 (2010-10-30)
9 1+1 SD
Figure 9-13 1+1 SD HSM realization principle (after the switching, in the receive direction)
Antenna
Standby ODU
Standby IF board
EMS6 board
After a 1+1 SD HSM switching: l l In the transmit direction, no processing is required. In the receive direction: The MUX unit of the main IF board receives the demodulated Hybrid signal frame that is transmitted from the standby IF board through the protection bus and then separates the Hybrid microwave frame into the E1 service signal and Ethernet service signal. The crossconnect board and the EMS6 board receive the service signal from the main IF board.
NOTE
The actions involved in the 1+1 SD protection switching occur on the faulty NE. These actions do not occur on the normal NE.

Follow certain guidelines when you plan 1+1 SD. Plan the parameters relevant to the protection configuration. l l There should be a height difference between the two antennas so that the dependence of the diversity-received microwave signals on the space is minimized. If the protection is in the revertive mode, set the WTR time to a value, which ranges from five minutes to twelve minutes. It is recommended that you set the default value to ten minutes. It is recommended that you enable the reverse switching. If reverse switching is enabled, and both the main IF board and the standby IF board at the sink end report a service alarm, a reverse switching occurs at the source end. In the case of the OptiX RTN 620, a pair of main and standby IF boards must be installed in slots 5 and 7 (the IF board in slot 5 is the main board) or in slots 6 and 8 (the IF board in slot 6 is the main board).
Issue 05 (2010-10-30)
9-19
9 1+1 SD

When configuring a radio link with 1+1 SD, you need to configure a 1+1 IF protection group and then configure IF/ODU information. Table 9-6 Configuration procedure of 1+1 SD Step 1 Operation A.5.1 Creating an IF 1+1 Protection Group A.5.3 Configuring the IF/ODU Information of a Radio Link A.5.9 Setting Parameters of ODU Interfaces Remarks The parameters need to be set according to network planning.
To configure 1+1 SD, you need to configure the IF/ODU information for the main equipment. The parameters need to be set according to network planning.
The parameters need to be set according to network planning.
NOTE

This section uses an example to describe how to plan and configure 1+1 SD according to network conditions. 9.8.1 Networking Diagram This section describes the networking information about NEs. 9.8.2 Service Planning The service planning information contains all the parameters required for configuring the NE data. 9.8.3 Configuration Process This section describes the procedure of data configuration.

This section describes the networking information about NEs.
9 1+1 SD
To ensure the reliable transmission of services on a hop of radio link consisting of the OptiX RTN 620, you need to configure 1+1 SD for the radio link between NE1 and NE2, as shown in Figure 9-14. Figure 9-14 1+1 SD protection networking diagram
NE2
NE1

The service planning information contains all the parameters required for configuring the NE data. l Plan the slots of the working and protection boards. Plan the slots for the working board and the protection board based on board configuration. To be specific, the IF board in slot 5 functions as the working board, and the IF board in slot 7 functions as the protection board. l Plan the parameters of protection groups. The 1+1 protection mode is SD, which provides function for the equipment. Unless otherwise specified, all the parameters take default values. The reverse switching function is enabled. In this manner, the source end can perform a reverse switching when the main IF board and the standby IF board report certain service alarms. l Plan radio link information. The radio link information is specified according to network planning. The following tables provide IF planning information and RF planning information.
NOTE
In the case of 1+1 SD radio links, one protection group corresponds to one link. Therefore, you need to configure the IF/ODU information for the main equipment only.
Table 9-7 IF planning information Parameter NE1 5-IFH2 Link ID Channel spacing (MHz) AM enabling AM guaranteed capacity mode AM full capacity mode E1 capacity
Issue 05 (2010-10-30)
NE2 5-IFH2 101 28M Enabled QPSK 128QAM 16

9-21
101 28M Enabled QPSK 128QAM 16
9 1+1 SD
Parameter
NE1 5-IFH2
NE2 5-IFH2 Disabled
ATPC status
Disabled
Table 9-8 RF planning information Parameter NE1 15-ODU Transmit frequency (MHz) T/R spacing (MHz) Transmit power (dBm) Receive power (dBm) Transmission status 14930 420 10 -45 Unmute NE2 15-ODU 14510 420 10 -45 Unmute

Procedure
Step 1 A.5.1 Creating an IF 1+1 Protection Group. The following table provides the values of parameters. Parameter Value Range NE1 Working Mode Revertive Mode WTR Time (s) Enable Reverse Switching Working Board Protection Board SD Revertive mode (default value) 600 seconds (default value) Enabled (default value) 5-IFH2 7-IFH2 NE2 SD Revertive mode (default value) 600 seconds (default value) Enabled (default value) 5-IFH2 7-IFH2
Step 2 A.5.3 Configuring the IF/ODU Information of a Radio Link. The following table provides the values of IF board parameters.
9 1+1 SD
Parameter
Value Range NE1 5-IFH2 NE2 5-IFH2 Enabled 28M QPSK 128QAM 16 101 Disabled
AM Enable Status IF Channel Bandwidth Modulation Mode of the Assured AM Capacity Modulation Mode of the Full AM Capacity E1 Capacity Link ID ATPC Enable Status
Enabled 28M QPSK 128QAM 16 101 Disabled
Step 3 A.5.9 Setting Parameters of ODU Interfaces. The following table provides the values of ODU parameters. Parameter Value Range NE1 15-ODU TX Frequency (MHz) T/R Spacing(MHZ) TX Power(dBm) Power to Be Received (dBm) TX Status 14930 420 10 -45 Unmute NE2 15-ODU 14510 420 10 -45 Unmute
----End
9.9 Task Collection

This section provides the hyperlinks of the operation tasks associated with 1+1 SD.
Related Tasks
A.5.1 Creating an IF 1+1 Protection Group A.5.3 Configuring the IF/ODU Information of a Radio Link A.5.13 Querying the IF 1+1 Protection Status
9 1+1 SD
A.5.15 Performing IF 1+1 Protection Switching

When a 1+1 SD switching occurs on IF boards, the system reports corresponding alarms and abnormal events.
Relevant Alarms

9.11 FAQs
This section provides the answers to the questions that are frequently raised when 1+1 SD is used. Q: During the configuration of the 1+1 SD protection, is it necessary to configure the IF interface of the standby IF board and the ODU interface of the standby ODU? A: It is unnecessary. The system automatically copies the relevant data of the main IF board and the main ODU. But, it is necessary to set the Configure Transmission Status of both the main ODU and the standby ODU to Unmute on the NMS. Q: Why does the configuration of the 1+1 SD protection fail? A: Common causes are as follows: l l l The IF board and the corresponding ODU that form the 1+1 SD protection are not added in the slot layout. The main IF board and the standby IF board are not configured in paired slots. The standby IF board is configured with services.
Q: In the revertive mode, why does the switching fail to restore after the switching changes to the RDI state? A: The revertive mode is invalid for the reverse switching. That is, although both the main and standby equipment are normal, the system does not switch back to the former main equipment after the reverse switching occurs. Q: When radio links work as ECC links, why is the NMS unable to receive the abnormal HSB switching event of the non-gateway NE? A: When an HSB switching occurs, the ECC needs to reroute. As a result, the ECC between the gateway NE and the non-gateway NE is transiently interrupted and the switching event cannot be reported.
9 1+1 SD
Q: When the main ODU is configured with the 1+1 SD protection, why is a switching event reported when there is no actual switching being performed if the main ODU reports a configuration alarm? A: In the case of the 1+1 SD protection group, the system automatically copies the data of the main ODU to the standby ODU. Hence, when the main ODU reports a configuration alarm, the standby ODU reports the same configuration alarm accordingly. Because both the main and the standby ODUs report a configuration alarm, a switching does not occur on the equipment. To notify the user that the ODU configuration is abnormal, however, the system reports a switching event. Q: What points should be noted before the deletion of a 1+1 SD protection group? A: Before the deletion of a 1+1 SD protection group, first mute the standby ODU. Otherwise, the signal emitted by the standby ODU interferes with the signal of the main ODU. Q: What is the method for rectifying the fault when the 1+1 SD switching fails? A: If the 1+1 SD switching fails, check whether the protection groups are correctly configured, and then check whether the standby devices (including ODUs and IF boards) and standby radio link are normal. Exclude the fault that the RSL is low because of signal interference and antenna unalignment.
Issue 05 (2010-10-30)
9-25
10 Cross-Polarization Interference Cancellation
10
About This Chapter
Cross-Polarization Interference Cancellation
This chapter describes the cross polarization interference cancellation (XPIC) feature. 10.1 Introduction This section provides the definition of XPIC and describes its purpose. 10.2 Basic Concepts This section describes basic concepts associated with XPIC. 10.3 Specifications This section provides the specifications of XPIC. 10.4 Availability This section describes the support required by the XPIC feature and its dependency. 10.5 Principles The IFX boards of the OptiX RTN 620 receive signals in the horizontal and vertical directions. The signals in the two directions are then processed and the original signals are recovered. 10.6 Planning Guidelines Follow certain guidelines when you plan XPIC. 10.7 Configuration Procedure To configure XPIC links with no protection, you only need to configure XPIC workgroups. To configure XPIC links with 1+1 protection, you need to configure 1+1 IF protection groups in addition to XPIC workgroups. 10.8 Configuration Example This section uses an example to describe how to plan and configure XPIC according to network conditions. 10.9 Task Collection This section provides the hyperlinks of the operation tasks associated with XPIC. 10.10 Relevant Alarms and Events When XPIC signals are lost, the system reports an alarm.
10.11 FAQs This section describes the answers to the questions that are frequently raised when the XPIC feature is used.
10-2
Issue 05 (2010-10-30)
10.1 Introduction
This section provides the definition of XPIC and describes its purpose.
Definition
The XPIC technology is used with the co-channel dual-polarization (CCDP) technology. When the XPIC and CCDP technologies are used together, the transmitter transmits two electromagnetic waves whose polarization directions are orthogonal to each other to the receiver over the same channel. The receiver recovers the original two channels of signals after canceling the interference between the two electromagnetic waves through the XPIC processing. The XPIC technology enables using the same channel bandwidth to transmit service signals whose capacity is two times the capacity of application without XPIC. The transmission of 2xSTM-1 signals in one direction of the radio link is considered as an example. When the XPIC technology is not used, the adjacent channel alternate polarization (ACAP) technology should be used in channel configuration. Thus, the bandwidth of two RF channels should be used to transmit these 2xSTM-1 signals. See Figure 10-1. When the XPIC technology is used, the bandwidth of one RF channel can transmit 2xSTM-1 signals by using the CCDP channel configuration mode. See Figure 10-2. Figure 10-1 Channel configuration in ACAP mode (without the application of the XPIC technology)
Site A IDU 620 STM-1 STM-1 ODU 2 ODU 1 f1 H V f2 f2 f2 ODU 2 STM-1 Site B ODU 1 IDU 620 STM-1
f1
f1
Figure 10-2 Channel configuration in CCDP mode (with the application of the XPIC technology)
Site A IDU 620 STM-1 STM-1 ODU 2 ODU 1 f1 H V f1 f1 ODU 2 Site B ODU 1 IDU 620 STM-1 STM-1
f1
f1
Issue 05 (2010-10-30)
10-3
Purpose
When the XPIC technology is used, the link transmission capacity over the same channel can be doubled.
10.2 Basic Concepts

This section describes basic concepts associated with XPIC. 10.2.1 CCDP and XPIC CCDP (Co-Channel Dual Polarization) and XPIC are two technologies that are developed based on the polarization characteristics of microwaves. CCDP doubles the link capacity by transmitting two orthogonal polarization waves over the same link, and XPIC cancels the crosspolarization interference between the two polarization waves. 10.2.2 System Configuration The application of XPIC feature requires specific system configuration.
10.2.1 CCDP and XPIC

CCDP (Co-Channel Dual Polarization) and XPIC are two technologies that are developed based on the polarization characteristics of microwaves. CCDP doubles the link capacity by transmitting two orthogonal polarization waves over the same link, and XPIC cancels the crosspolarization interference between the two polarization waves. Single-polarization transmission and CCDP transmission are two microwave transmission methods. l l Single-polarization transmission adopts the horizontally polarized wave or the vertically polarized wave on one channel to transmit one channel of signals. See Figure 10-3. CCDP transmission adopts both the horizontally polarized wave and the vertically polarized wave on one channel to transmit two channels of signals. See Figure 10-4.
Therefore, CCDP transmission doubles the link capacity in single-polarization transmission. Figure 10-3 Single-polarization transmission
Figure 10-4 CCDP transmission
10-4
Issue 05 (2010-10-30)
The ideal situation of CCDP transmission is that no interference exists between the two orthogonal signals though they are with the same frequency, and thus the receiver can easily recover the two signals. In actual engineering conditions, however, despite the orthogonality of the two signals, certain interference between the signals inevitably occurs, due to crosspolarization discrimination (XPD) of the antenna and channel degradation. To cancel the interference, the XPIC technology is adopted. In XPIC technology, the signals are received in the horizontal and vertical directions. The signals in the two directions are then processed and the original signals are recovered.

The application of XPIC feature requires specific system configuration.
NE Configuration
The OptiX RTN 620 supports one or two XPIC pairs. Each XPIC pair occupies one frequency. The XPIC pair is configured as follows: l l l Two IFX boards Two ODUs One dual-polarized antenna
Figure 10-5 shows the typical configuration of the XPIC when a single NE is configured with one XPIC pair. The two IFX boards are connected by two XPIC cables so that the XPIC cancellation signal from one IFX board is transmitted to the other IFX board. Figure 10-5 Typical configuration of XPIC
ODU
Dual-polarized antenna ODU
EXT IFX FAN

Slot 20
EXT EXT EXT SD1 SCC
EXT IFX PXC PXC

IDU 620
Issue 05 (2010-10-30)
10-5
10.3 Specifications
This section provides the specifications of XPIC. Table 10-1 lists the specifications of XPIC. Table 10-1 Specifications of XPIC Item Radio link form Radio work mode Specifications SDH radio link SDH radio link: l Service capacity: STM-1 l Channel spacing: 28 MHz l Modulation mode: 128QAM Number of XPIC workgroups Implementation mode Two groups Hardware
10.4 Availability
This section describes the support required by the XPIC feature and its dependency.

Table 10-2 Hardware and version support Feature XPIC Applicable Board IFX Applicable Hardware Version All the versions Applicable Product Version V100R002 and later
Feature Dependency
l Configuration relationship between the XPIC feature and the 1+1 HSB/FD/SD protection feature One XPIC workgroup cannot form a 1+1 HSB/FD/SD protection group. However, the radio link of an XPIC workgroup and the radio link of another XPIC workgroup in the same polarization direction can form a 1+1 HSB/FD/SD protection group. That is, the two XPIC workgroups can form two HSB/FD/SD protection groups. Figure 10-6 shows an example of how two XPIC workgroups form two 1+1 HSB protection groups respectively in the vertical and horizontal polarization direction.
10-6
Issue 05 (2010-10-30)
Figure 10-6 Typical XPIC configuration (1+1 protection configuration)

V-polarization Dual-polarized antenna H-polarization
ODU Working channel 1 Hybrid coupler ODU Protection channel 1

EXT IFX FAN

Slot 20
EXT IFX EXT IFX SD1 SCC
EXT IFX PXC PXC
The service channels on the IFX boards in slots 5 and 6 form one XPIC workgroup, whereas the service channels on the IFX boards in slots 7 and 8 form another XPIC workgroup. The service channels on the IFX boards in slots 5 and 7 form one 1+1 HSB protection group. The service channels on the IFX boards in slots 6 and 8 form another 1+1 HSB protection group. The service channels on the IFX boards in slots 5 and 6 are the working channels of the two 1+1 HSB protection groups. Generally, the two working channels (in the horizontal and vertical polarization directions) carry services. The service channels on the IFX boards in slots 7 and 8 are the protection channels of the two 1+1 HSB protection groups and provide protection for the working channels. In the receive direction, if the IFX board in slot 5 is faulty or the ODU connected to this board is faulty, HSB switching occurs on the equipment and therefore the services are switched from the IFX board in slot 5 to the IFX board in slot 7. At the same time, the fault also causes the loss of XPIC signals that are transmitted from the IFX board in slot 5 to the IFX board in slot 6. As a result, HSB switching occurs on the IFX boards in slots 6 and 8 that form a 1+1 protection group and therefore the services are switched from the IFX board in slot 6 to the IFX board in slot 8. Thus, services are switched from one XPIC workgroup to another. In the transmit direction, if the transmitter in the vertical polarization direction of the IFX board in slot 5 is faulty, the working and protection channels in the vertical polarization direction of the IFX board at the opposite end are alarmed. As a result, reverse switching occurs on the local end and services are switched from the IFX board in slot 5 to the IFX board in slot 7. In addition, the fault causes the loss of XPIC signals that are transmitted in the working and protection channels in the horizontal polarization direction of the IFX board at the opposite end. As a result, the working and protection channels in the horizontal polarization direction of the IFX board at the opposite end are alarmed. In this case, reverse switching occurs in the working and protection
Issue 05 (2010-10-30)
10-7
channels in the horizontal polarization direction of the IFX board at the local end and services are switched from the IFX board in slot 6 to the IFX board in slot 8. l Relationship between XPIC and ATPC The ATPC parameters, such as ATPC enable status and ATPC adjustment thresholds, need to be set to the same values for the links in the horizontal and vertical polarization directions in an XPIC workgroup. l Relationship between XPIC and SNCP A radio link configured with XPIC can work as the working source, protection source, or service sink of an SNCP service pair. l Relationship between XPIC and N+1 protection A member of the XPIC workgroup cannot be configured with N+1 protection.
10.5 Principles
The IFX boards of the OptiX RTN 620 receive signals in the horizontal and vertical directions. The signals in the two directions are then processed and the original signals are recovered. Figure 10-7 Working principle of XPIC
Horizontal polarization Modem horizontal
XPIC module of IFX

A/D Filter Decision Coefficient control Filter
Cross interference Cross interference
Filter
XPIC module of IFX

Coefficient control
Modem vertical
A/D
Filter
Decision
Vertical polarization
The working principle is as follows: 1. 2. The transmitter transmits two signals with the same frequency over a horizontal polarization wave and a vertical polarization wave. Due to XPD of the antenna and channel degradation, cross-polarization interference exists in the signals received by the ODU and also in the IF signals transmitted from the ODU to the IFX boards. The XPIC module on the IFX board receives the IF signal from the ODU and also the IF signal from the other IFX board, and processes the IF signals, for example, A/D conversion. The XPIC module on the IFX board controls the coefficient of the feed forward equalizer filters (FFF) of the two IF signals by using the decision feedback equalizer (DFE). As a result, after filtering and combination, the interference is cancelled in the two IF signals.
3. 4.
10-8
Issue 05 (2010-10-30)

Follow certain guidelines when you plan XPIC. When you plan XPIC, follow certain guidelines: l l When CCDP is applied to STM-1 radio links, IFX boards must be installed and the XPIC function must be enabled. The microwave work mode, transmit frequency, transmit power, T/R spacing, and ATPC parameters (including ATPC enable status and ATPC adjustment thresholds) need to be set to the same values for the links in the horizontal and vertical polarization directions in an XPIC workgroup. The slots for housing the IFX boards need to be determined based on expansion requirements. If two XPIC workgroups that form two 1+1 protection groups are not required, install the IFX boards in slots 5 and 7 (the IFX board in slot 5 processes vertically polarized signals and the IFX board in slot 7 processes horizontally polarized signals) or in slots 6 and 8 (the IFX board in slot 6 processes vertically polarized signals and the IFX board in slot 8 processes horizontally polarized signals). If two XPIC workgroups that form two 1+1 protection groups are required, install the IFX boards in slots 5 and 6 (the IFX board in slot 5 processes vertically polarized signals and the IFX board in slot 6 processes horizontally polarized signals) or in slots 7 and 8 (the IFX board in slot 7 processes vertically polarized signals and the IFX board in slot 8 processes horizontally polarized signals).

To configure XPIC links with no protection, you only need to configure XPIC workgroups. To configure XPIC links with 1+1 protection, you need to configure 1+1 IF protection groups in addition to XPIC workgroups. Table 10-3 Procedure for configuring XPIC links Step 1 Operation Complete the physical connections by using XPIC cables. A.5.1 Creating an IF 1+1 Protection Group Description Required. Use the XPIC cable to connect the X-IN and X-OUT ports on the two IFX boards of the XPIC workgroup.
Required when two XPIC workgroups need to form two 1+1 protection groups. The parameters need to be set according to the network planning.
NOTE One XPIC workgroup cannot form a 1+1 protection group. The radio links in one polarization direction from two XPIC workgroups can form one 1 +1 protection group. Therefore, two XPIC workgroups can form two 1+1 protection groups.
Issue 05 (2010-10-30)
10-9
Step 3
Operation A.5.2 Creating an XPIC Workgroup A.5.3 Configuring the IF/ODU Information of a Radio Link
Description Required. The parameters need to be set according to the network planning. Required. Set the parameters as follows: l T/R Spacing(MHZ) is set according to the network planning. l When ATPC Enable Status is set to Enabled, set ATPC Automatic Threshold Enable Status to Enabled if the equipment automatically uses the preset ATPC upper and lower thresholds based on the working mode of the IF board; set ATPC Automatic Threshold Enable Status to Disabled if you need to manually set the ATPC upper and lower thresholds for the equipment.
NOTE l You need to separately set the preceding parameters for radio links in the vertical polarization direction and the horizontal polarization direction, and ensure these parameters in the two polarization directions are set to the same values. l In the case of radio links configured with 1+1 HSB/SD, you need to configure the IF and ODU information on the working radio link only. In the case of radio links configured with 1+1 FD, you need to configure the IF and ODU information on the working radio link and the ODU information on the protection radio link.

This section uses an example to describe how to plan and configure XPIC according to network conditions. 10.8.1 Networking Diagram This section describes the networking information about the NEs. 10.8.2 Service Planning The service planning information contains all the parameters required for configuring the NE data. 10.8.3 Configuration Process This section describes the procedure of data configuration.

This section describes the networking information about the NEs. The service requirements between two sets of OptiX RTN 620 are as follows: l l l
10-10
The SDH radio links need to transmit 2xSTM-1 services. According to the spectrum planning requirement, the XPIC feature needs to be enabled. The radio links need to be protected.

101 14950M 14530M 28M 1+1 HSB V-polarization 102 14950M 14530M 28M 1+1 HSB H-polarization
NE1
Tx high Tx low Link ID Tx high station Tx Freq. Tx low station Tx Freq. Channel spacing RF Configuration Polarization
NE2
Plan the radio links that adopt XPIC as shown in Figure 10-8 to meet large-capacity transmission requirements, according to the preceding service requirements and the available spectrum resources. As shown in Figure 10-9, NE1 and NE2 adopt same board configurations. Wherein, the SD1 board is used to access 2xSTM-1 services. Figure 10-9 Board configurations
V-polarization Dual-polarized antenna H-polarization

EXT IFX FAN

Slot 20
EXT IFX EXT IFX SD1 SCC
EXT IFX PXC PXC
In this example, two XPIC workgroups form two 1+1 HSB protection groups. l The service channels on the IFX boards in slots 5 and 6 form one XPIC workgroup; the service channels on the IFX boards in slots 7 and 8 form the other XPIC workgroup.
Issue 05 (2010-10-30)
10-11
The service channels on the IFX boards in slots 5 and 7 form one 1+1 HSB protection group; the service channels on the IFX boards in slots 6 and 8 form the other 1+1 HSB protection group. The service channels on the IFX boards in slots 5 and 6 are the working channels of the two 1+1 HSB protection groups. Generally, the two working channels (in the horizontal and vertical polarization directions) carry services. The service channels on the IFX boards in slots 7 and 8 are the protection channels of the two 1+1 HSB protection groups and provide protection for the working channels.

The service planning information contains all the parameters required for configuring the NE data.
Basic Information About Radio Links

Based on the spectrum allocation on the radio network and the required radio transmission capacity, you can obtain the basic information about radio links as shown in Table 10-4. Table 10-4 Basic information about radio links Parameter Link ID Tx high site Tx low site Tx frequency at the Tx high site (MHz) Tx frequency at the Tx low site (MHz) T/R spacing (MHz) Work mode Link 1 101 NE1 NE2 14950 14530 420 Service capacity: STM-1 Channel spacing: 28 MHz Modulation mode: 128 QAM RF configuration mode Polarization direction 1+1 HSB V (vertical polarization) Link 2 102 NE1 NE2 14950 14530 420 Service capacity: STM-1 Channel spacing: 28 MHz Modulation mode: 128 QAM 1+1 HSB H (horizontal polarization)
NOTE
l The link planning information that is not associated with the configuration of IDU (except for the polarization direction) is not provided in this example. l In this example, two XPIC workgroups need to form two 1+1 HSB protection groups. Thus, the IDs of the radio links in the vertical polarization direction of the two XPIC workgroups must be set to 101 and the IDs of the radio links in the horizontal polarization direction of the two XPIC workgroups must be set to 102.
10-12
Issue 05 (2010-10-30)
Power and ATPC Information

By using the radio network planning software such as the Pathloss, you can analyze and compute the parameters of radio links and obtain the radio link power and ATPC information as shown in Table 10-5. Table 10-5 Power and ATPC information Parameter Transmit power (dBm) Link 1 6.0 (NE1) 6.0 (NE2) ATPC enabling ATPC automatic threshold enabling Disabled Link 2 6.0 (NE1) 6.0 (NE2) Disabled -
NOTE
l The transmit power is calculated in AM full-capacity mode. l The ATPC feature is not enabled in this example.
Configuration Information About 1+1 HSB Protection Groups

Figure 10-9 shows the board configurations of NE1 and NE2. Based on the rules for planning the slot priorities of IF boards and the 1+1 HSB protection, you can obtain the configuration information about the 1+1 HSB protection groups, as provided in Table 10-6. Table 10-6 Configuration information about 1+1 HSB protection groups Parameter 1+1 HSB protection group 1 V (vertical polarization) Working Board Protection Board Working Mode Revertive Mode WTR Time(s) Enable Reverse Switching 1+1 HSB protection group 2 H (horizontal polarization) Working Board Protection Board Working Mode Revertive Mode WTR Time(s) Enable Reverse Switching NE1 5-IFX 7-IFX HSB Revertive Mode 600 Enabled 6-IFX 8-IFX HSB Revertive Mode 600 Enabled NE2 5-IFX 7-IFX HSB Revertive Mode 600 Enabled 6-IFX 8-IFX HSB Revertive Mode 600 Enabled
Issue 05 (2010-10-30)
10-13
Configuration Information About XPIC Workgroups

Figure 10-9 shows the board configurations of NE1 and NE2. Based on the rules for planning the slot priorities of IF boards and the 1+1 HSB protection, you can obtain the configuration information about XPIC, as provided in Table 10-7. Table 10-7 Configuration information about XPIC Parameter XPIC Workgroup 1 V (vertical polarization) H (horizontal polarization) XPIC Workgroup 2 V (vertical polarization) H (horizontal polarization) NE1 5-IFX 6-IFX 7-IFX 8-IFX NE2 5-IFX 6-IFX 7-IFX 8-IFX
NOTE
Use the XPIC cables with angle connectors to connect the X-IN and X-OUT ports between the two IFX boards in the horizontal polarization direction, namely, the IFX boards in slots 5 and 6 or slots 7 and 8.

Procedure
Step 1 Use the XPIC cables with angle connectors to connect the X-IN and X-OUT ports between the two IFX boards in the horizontal polarization direction, namely, the IFX boards in slots 5 and 6 or slots 7 and 8. Step 2 See A.5.1 Creating an IF 1+1 Protection Group and configure 1+1 HSB protection. The parameters for configuring 1+1 HSB protection of NE1 and NE2 need to be set to the same values, as provided in the following table. Parameter Value Range 1+1 HSB Protection Group 1 V (vertical polarization) Working Mode Revertive Mode WTR Time (s) Enable Reverse Switching
10-14
1+1 HSB Protection Group 2 H (horizontal polarization) HSB Revertive Mode 600 Enabled
Issue 05 (2010-10-30)
HSB Revertive Mode 600 Enabled
Parameter
Value Range 1+1 HSB Protection Group 1 V (vertical polarization) 1+1 HSB Protection Group 2 H (horizontal polarization) 6-IFX-1 8-IFX-1
Working Board Protection Board
5-IFX-1 7-IFX-1
Step 3 See A.14.2 Creating MAs and create XPIC workgroups. Parameter Value (NE1) XPIC Workgroup 1 Work Mode Polarization direction-V Link ID-V Polarization direction-H Link ID-H TX Power (dBm) Transmission Frequency (MHz) Transmission Status ATPC Enabled 7, STM-1, 28 MHz, 128 QAM 5-IFX-1 101 6-IFX-1 102 6.0 14950 XPIC Workgroup 2 7, STM-1, 28 MHz, 128 QAM 7-IFX-1 101 8-IFX-1 102 6.0 14950 Value (NE2) XPIC Workgroup 1 7, STM-1, 28 MHz, 128 QAM 5-IFX-1 101 6-IFX-1 102 6.0 14530 XPIC Workgroup 2 7, STM-1, 28 MHz, 128 QAM 7-IFX-1 101 8-IFX-1 102 6.0 14530
unmute Disabled
unmute Disabled
unmute Disabled
unmute Disabled
Step 4 See A.14.2 Creating MAs and configure the IF/ODU information about radio links. T/R Spacing(MHZ) for the links of NE1 and NE2 are set to the same values, as provided in the following table. Parameter Value Range 5-IFX and 15-ODU T/R Spacing(MHZ) 420 6-IFX and 16-ODU 420
Issue 05 (2010-10-30)
10-15
----End

This section provides the hyperlinks of the operation tasks associated with XPIC.
Related Tasks
A.5.2 Creating an XPIC Workgroup A.5.1 Creating an IF 1+1 Protection Group A.5.3 Configuring the IF/ODU Information of a Radio Link A.5.8 Setting Parameters of IF Interfaces

When XPIC signals are lost, the system reports an alarm.
Relevant Alarms
l XPIC_LOS The XPIC_LOS alarm indicates that the XPIC compensation signal is lost.

None.
10.11 FAQs
This section describes the answers to the questions that are frequently raised when the XPIC feature is used. Q: What is the method of rectifying an XPIC fault? A: To rectify an XPIC fault, do as follows: l Check whether the data configuration is correct. The two IFX boards that form an XPIC group must be configured with the same working mode, transmission frequency, and T/R spacing. l Check whether the cables are connected correctly. Configuring the XPIC workgroup involves connecting the IF cables, connecting the XPIC cables, and installing the ODU separately from the antenna, especially when the XPIC workgroup is configured with the 1+1 protection. Divide the cables into two parts according to the polarization directions of signals and then check each part. l Check whether the dual-polarized antenna is aligned in the correct polarized direction. The XPD can meet the specifications for the antenna only when the polarization direction of the dual-polarized antenna is aligned correctly.
11 N+1 Protection
11
About This Chapter
This chapter describes the N+1 protection feature.
N+1 Protection
11.1 Introduction This section provides the definition of N+1 protection and describes its purpose. 11.2 Basic Concepts This section describes basic concepts associated with N+1 protection. 11.3 Specifications This section provides the specifications of N+1 protection. 11.4 Reference Standards and Protocols This section describes the standards and protocols associated with N+1 protection. 11.5 Availability This section describes the support required by the N+1 protection feature and its dependency. 11.6 Principles The N+1 protection uses the N+1 protection protocol to implement switching. 11.7 Planning Guidelines Follow certain guidelines when you plan N+1 protection. 11.8 Configuration Procedure To configure an N+1 protection group of radio links, you need to configure the IF/ODU information about the working and protection links and then create an N+1 protection group. 11.9 Configuration Example This section uses an example to describe how to plan and configure N+1 protection for SDH radio according to the network conditions. 11.10 Task Collection This section provides the hyperlinks of the operation tasks associated with N+1 protection. 11.11 Relevant Alarms and Performance Events When an N+1 protection switching occurs, the IF board reports corresponding alarms. 11.12 FAQs
11 N+1 Protection
This section describes the answers to the questions that are frequently raised when the N+1 protection feature is used.
11-2
Issue 05 (2010-10-30)
11 N+1 Protection
11.1 Introduction
This section provides the definition of N+1 protection and describes its purpose.
Definition
N+1 protection refers to the protection configuration that N microwave working channels in a microwave direction share one microwave protection channel. N+1 protection provides protection for microwave channels. The IF board, ODU, and radio link on the working channel can be protected through the N+1 protection. The N+1 protection provides N working channels and one protection channel. When the working channel becomes faulty, the normal services on the working channel can be switched to the protection channel for transmission. When the working channel is restored to normal, the protection channel can transmit the extra services. Figure 11-1 shows the application of N+1 protection. Figure 11-1 N+1 protection
Site A Normal service 1 Working channel 1 Site B Normal service1
...
Normal service N Extra service
Working channel N Protection channel
...
Protection switching Site A Normal service 1 Working channel 1 Site B Normal service1
...
...
Purpose
Compared with radio links configured with N+0 protection, radio links configured with N+1 protection have improved reliability.
11 N+1 Protection
11.2 Basic Concepts

This section describes basic concepts associated with N+1 protection. 11.2.1 System Configuration The N+1 protection is available in two configuration modes: 2+1 protection configuration and 3+1 protection configuration. 11.2.2 Protection Type The protection type of N+1 protection is similar to the dual-ended revertive switching mode of 1:N linear multiplex section protection. 11.2.3 Switching Condition The N+1 protection can be triggered by local SF conditions, local SD conditions, local external switching requests, and byte K sent from the NE on the opposite side. This is similar to linear multiplex section protection. 11.2.4 Switching Impact The services are interrupted within the N+1 protection switching time (shorter than 50 ms). The extra services are interrupted from the time normal services are switched to the protection channel to the time the services are restored to the working channel.

The N+1 protection is available in two configuration modes: 2+1 protection configuration and 3+1 protection configuration.
2+1 Protection Configuration

One OptiX RTN 620 system supports one 2+1 protection group. One 2+1 protection group occupies three channels and consists of the following: l l l Three IF boards Three ODUs One dual-polarized antenna (with one balanced hybrid coupler)
NOTE
l The IF board can be the IF1 board, or IFX board. As the XPIC function is not required, it is recommended that you use the IF1 board. l The three channels can use the adjacent channel alternate-polarized (ACAP) mode.
Figure 11-2 provides a typical configuration of one 2+1 protection group. The configuration is as follows: l l l The IF1 boards in slots 5 and 7 provide two working channels. The IF1 board in slot 8 provides one protection channel. The three channels are configured in the ACAP mode. See Figure 11-3. The radio receive power of the three channels should be the same if possible to reduce adjacent channel interference. That is, the ODU transmit power set for the two working channels should be higher than the ODU transmit power set for the protection channel and the increment should exactly offset the extra loss caused by the hybrid coupler.
11-4
11 N+1 Protection
One SL1 board and one SD1 board access two working services and one extra service.
Figure 11-2 Typical configuration of one 2+1 protection group
ODU Working channel 1 Hybrid coupler ODU Working channel 2 ODU Protection channel
Dual-polarized antenna
EXT IF1 FAN

Slot 20
EXT IF1 SL1 SD1 SCC
EXT IFI PXC PXC

IDU 620
Figure 11-3 Typical channel configuration of one 2+1 protection group

Working channel 1 V H Protection channel Working channel 2
3+1 Protection Configuration

Two OptiX RTN 620 systems support one 3+1 protection group. One 3+1 protection group occupies four frequencies and consists of the following: l l l l
Issue 05 (2010-10-30)
Four IF boards (two for each NE) Four ODUs (two for each NE) Two SD1 boards (one for each NE) One dual-polarized antenna (with two balanced hybrid couplers)
11 N+1 Protection
NOTE
The IF board can be the IF1 board, or IFX board. As the XPIC function is not required, it is recommended that you use the IF1 board.
Figure 11-4 provides a typical configuration of one 3+1 protection group. The configuration is as follows: l l l The two IF1 boards of the primary NE provide two working channels. The two IF1 boards of the secondary NE provide one working channel and one protection channel. The four channels are configured in the ACAP mode. See Figure 11-5. The radio receive power of the four channels should be the same if possible to reduce adjacent channel interference. That is, the ODU transmit power set for the four channels should be the same. The two SD1 boards in slots 6 and 8 of the primary NE access three working services and one extra service. One working service and the extra service are transferred to the secondary NE through the SD1 board in slot 4. The SD1 board in slot 4 of the secondary NE accesses the one working service and the extra service that are transferred from the primary NE.
NOTE
You can use one SL4 board to replace the two SD1 boards in slots 6 and 8 of the primary NE to access the services, depending on the requirements.
11-6
Issue 05 (2010-10-30)
11 N+1 Protection
Figure 11-4 Typical configuration of one 3+1 protection group
ODU Working channel 1 Hybrid coupler ODU Working channel 2
ODU Working channel 3 Hybrid coupler ODU Protection channel

EXT IF1 FAN

Slot 20
SD1 SD1 SD1 SCC
EXT IF1 PXC PXC
Primary NE (IDU 620 )
EXT IF1 FAN

Slot 20
SD1 SD1 SD1 SCC
EXT IF1 PXC PXC
Secondary NE (IDU 620 )
Figure 11-5 Typical channel configuration of one 3+1 protection group

Working channel 1 V H Protection channel Working channel 3 Working channel 2

The protection type of N+1 protection is similar to the dual-ended revertive switching mode of 1:N linear multiplex section protection. The dual-ended revertive switching mode is explained as follows:
11 N+1 Protection
l l
When a protection switching occurs, the services on the working channels in two directions are switched to the protection channels. When an NE is in the switching state, the NE releases the switching and enables the former working channel to return to the normal state some time after the former working channel is restored to normal. The period from the time the former working channel is restored to normal to the time the NE releases the switching is called the wait-to-restore (WTR) time. To prevent frequent switching events due to an unstable working channel, it is recommended that you set the WTR time to 5 to 12 minutes. By default, the WTR time is 10 minutes.

The N+1 protection can be triggered by local SF conditions, local SD conditions, local external switching requests, and byte K sent from the NE on the opposite side. This is similar to linear multiplex section protection. Table 11-1 Switching conditions of the N+1 protection Switching Condition Lockout of protection (external switching) Priority From top downwards, the priority is from the highest to the lowest. Description The lockout of protection blocks normal traffic signals from entering the protection channel but does not block traffic signals from being switched from the protection channel to the working channel. The signal fail condition in the protection channel is equivalent to the lockout of protection. Traffic signals on the working channel are forcibly switched to the protection channel. The SF on the working channel causes traffic signals to be switched to the protection channel. When there is the MW_LOF, R_LOC, R_LOF, R_LOS, MS_AIS, or B2_EXC alarm on the working channel, or when the hardware of an ODU or IF board is faulty, the SF switching is triggered.
Signal fail (SF)
11-8
Issue 05 (2010-10-30)
11 N+1 Protection
Switching Condition Signal degrade (SD)
Priority
Description The SD on the working channel causes traffic signals to be switched to the protection channel. When there is the B2_SD alarm on the working channel, the SD switching is triggered. If a switching is in the lockout or forced switching state, or if the current standby equipment is faulty, no switching occurs. Otherwise, the system switches services from the active board to the standby board or from the standby board to the active board according to the command. The switching then enters the manual switching state. After traffic signals are switched to the protection channel due to the SF/SD condition on the working channel and the working channel is already restored to normal for the WTR time, a revertive switching occurs. From the time the former active equipment is restored to normal to the time the revertive switching occurs, the switching is in the WTR state. After the revertive switching, the switching enters the normal state. Traffic signals are not actually switched. The exercise functionality is used only to check whether an NE can normally carry out the N +1 protection protocol.
Revertive switching (valid only in the revertive mode)
Exercise switching (external switching)
Issue 05 (2010-10-30)
11-9
11 N+1 Protection
NOTE
l The SD is an optional switching condition. You can specify whether to use the SD as a switching condition on the NMS. By default, the SD switching condition is used. l If two switching conditions exist on a channel at the same time, the switching of higher priority preempts the channel. l External switching commands include the following clear switching commands: clear lockout command, clear forced switching command, clear manual switching command, clear exercise switching command, clear WTR state command, and clear all command. The clear WTR state command is used to end the current WTR state of the NE and to immediately switch services to the working channel. The clear all command is used to clear all switching actions triggered by external switching commands and to clear the WTR state. l If an NE needs to perform switching according to byte K sent from the NE at the opposite end, the NE determines the switching priority according to the bridge request code contained in byte K. For details, see 15.2.2 Meanings of K Bytes.

The services are interrupted within the N+1 protection switching time (shorter than 50 ms). The extra services are interrupted from the time normal services are switched to the protection channel to the time the services are restored to the working channel.
11.3 Specifications
This section provides the specifications of N+1 protection. Table 11-2 provides the specifications of N+1 protection. Table 11-2 Specifications of N+1 protection Item Radio link form Radio work mode Specifications SDH radio link SDH radio link: l Service capacity: STM-1 l Channel spacing: 28 MHz l Modulation mode: 128QAM Number of 2+1 protection groups supported by a single NE Number of 3+1 protection groups supported by two NEs Protection switching duration WTR time One group One group Less than 50 ms 300 seconds to 720 seconds

This section describes the standards and protocols associated with N+1 protection.
11 N+1 Protection
The N+1 protection protocol, a proprietary protocol stack of Huawei, is associated with N+1 protection. Parts of this protocol are based on the 1:N linear MSP protocol specified in ITU-T G.841 "Types and characteristics of SDH network protection architectures."
11.5 Availability
This section describes the support required by the N+1 protection feature and its dependency.

Table 11-3 Hardware and version support Feature N+1 protection Applicable Board IF1 IFX Applicable Hardware Version All the versions All the versions Applicable Product Version V100R002 and later V100R002 and later
Feature Dependency
l l l l The members of a 1+1 protection group cannot be configured as members of an N+1 protection group. The ATPC parameters, such as ATPC enable status and ATPC adjustment thresholds, need to be set to the same values for the members of an N+1 protection group. A radio link configured with N+1 protection can work only as the service sink of an SNCP service pair, rather than the working source or protection source. A member of the N+1 protection group cannot join the XPIC workgroup.
11.6 Principles
The N+1 protection uses the N+1 protection protocol to implement switching. 11.6.1 2+1 Protection Configuration In the case of 2+1 protection configuration, three IF boards form a 2+1 protection group to realize protection switching. 11.6.2 3+1 Protection Configuration In the case of the 3+1 protection configuration, the primary NE forms a 3+1 protection group to implement protection switching and the secondary NE forms two STM-1 REGs to implement transparent transmission of byte K.
11.6.1 2+1 Protection Configuration

In the case of 2+1 protection configuration, three IF boards form a 2+1 protection group to realize protection switching.
NOTE
The following describes the switching principle of 2+1 protection. The 2+1 protection configuration described in 11.2.1 System Configuration is provided as an example.
Issue 05 (2010-10-30)
11-11
11 N+1 Protection
Figure 11-6 Working principle of 2+1 protection (before the switching)

PXC 4-SD1-1 5-IF1-1 15-ODU
6-SL1-1
7-IF1-1
17-ODU
4-SD1-2
8-IF1-1
18-ODU
Working channel
Protection channel
Figure 11-7 Working principle of 2+1 protection (after the switching)

PXC 4-SD1-1 5-IF1-1 15-ODU
6-SL1-1
7-IF1-1
17-ODU
4-SD1-2
8-IF1-1
18-ODU
Working channel
Protection channel
In this example, port 1 of the IF1 board in slot 5, port 1 of the IF1 board in slot 7, and port 1 of the IF1 board in slot 8 form a 2+1 protection group. When a working channel fails, the switching principle of the 2+1 protection configuration is as follows: 1. 2. Before the switching, the NE sends and receives normal traffic signals on the working channel, and sends and receives extra traffic signals on the protection channel. On detecting that the signals on a working channel fail (for example, the IF1 board in slot 5 detects that an MW_LOF alarm is generated on port 1), the IF board notifies the SCC board. The SCC board controls the PXC board to implement the transmission of the working traffic signals (port 1 of the SD1 board in slot 4) on the protection channel (port 1 of the IF1 board in slot 8). The SCC board also interacts with the NE on the opposite side through byte K to enable the NE on the opposite side to perform synchronous switching.
3.
11-12

NOTE
11 N+1 Protection
The interaction of byte K between NEs complies with the N+1 protection protocol, which is similar to the MSP protocol. For details, see Working Principle of 1:N Linear MSP.
11.6.2 3+1 Protection Configuration

In the case of the 3+1 protection configuration, the primary NE forms a 3+1 protection group to implement protection switching and the secondary NE forms two STM-1 REGs to implement transparent transmission of byte K.
NOTE
The following part describes the switching principle of the 3+1 protection. The 3+1 protection configuration described in 11.2.1 System Configuration is provided as an example.
Figure 11-8 Working principle of the 3+1 protection (before the switching)
Primary NE PXC 6-SD1-1 5-IF1-1 15-ODU
6-SD1-2
7-IF1-1
17-ODU
8-SD1-1
4-SD1-1
8-SD1-2
4-SD1-2
Secondary NE PXC 4-SD1-1 5-IF1-1 15-ODU
4-SD1-2
7-IF1-1
17-ODU
Working channel
Protection channel
Issue 05 (2010-10-30)
11-13
11 N+1 Protection
Figure 11-9 Working principle of the 3+1 protection (after the switching)
Primary NE PXC 6-SD1-1 5-IF1-1 15-ODU
6-SD1-2
7-IF1-1
17-ODU
8-SD1-1
4-SD1-1
8-SD1-2
4-SD1-2
Secondary NE PXC 4-SD1-1 5-IF1-1 15-ODU
4-SD1-2
7-IF1-1
17-ODU
Working channel
Protection channel
In this example, port 1 of the IF1 board in slot 5 of the primary NE, port 1 of the IF1 board in slot 7 of the primary NE, and ports 1 and 2 of the SD1 board in slot 4 of the primary NE form a 3+1 protection group. An REG is established between port 1 of the IF1 board in slot 5 of the secondary NE and port 1 of the SD1 board in slot 4 of the secondary NE. Another REG is established between port 1 of the IF1 board in slot 7 of the secondary NE and port 2 of the SD1 board in slot 4 of the secondary NE. When a working channel fails, the switching principle of the 3+1 protection configuration is as follows: 1. Before the switching, the primary NE sends and receives normal traffic signals on the working channel, and sends and receives extra traffic signals on the protection channel. The secondary NE works as an REG to transparently transmit VC signals and multiplex section overheads. On detecting that the signals on a working channel fail (for example, the IF1 board in slot 5 detects that an MW_LOF alarm is generated on port 1), an IF board of the secondary NE inserts the MS_AIS alarm and transparently transmits the multiplex section overheads and VC signals to port 1 of the SD1 board in slot 4 of the primary NE through port 1 of the SD1 board in slot 4 of the secondary NE.
2.
11-14
11 N+1 Protection
3. 4.
On detecting the MS_AIS alarm, the SD1 board in slot 4 of the primary NE reports the alarm to the SCC board. The SCC board controls the PXC board to implement the transmission of the working traffic signals (port 1 of the SD1 board in slot 8) on the protection channel (port 2 of the SD1 board in slot 4). The SCC board also interacts with the NE on the opposite side through byte K to enable the NE on the opposite side to perform synchronous switching. When the primary NE exchanges byte K with the NE on the opposite side, the secondary NE always transparently transmits byte K because byte K belongs to the multiplex section overheads.
NOTE
l In this example, the working channels of the secondary NE fail. If the working channels of the primary NE fail, the IF board directly reports the alarm to the SCC board to trigger the protection switching. l The REG formed by the secondary NE is slightly different from an ordinary REG. The REG formed by the secondary NE does not insert an AU_AIS alarm but inserts an MS_AIS alarm to trigger the N+1 protection switching when an MW_LOF alarm or a regenerator section alarm (for example, R_LOS, R_LOC, and R_LOF) is generated. l The interaction of byte K between NEs complies with the N+1 protection protocol, which is similar to the MSP protocol. For details, see Working Principle of 1:N Linear MSP.

Follow certain guidelines when you plan N+1 protection. When the OptiX RTN 620 transmits two or three STM-1 microwave services in a point-to-point manner, you can adopt N+1 protection. Follow these principles when planning N+1 protection: l l l Select 2+1 protection or 3+1 protection based on the transmission capacity. Plan the used channels. It is recommended that you configure the channels in the ACAP mode. Plan the parameters associated with N+1 protection. Set the WTR time to a value from five minutes to twelve minutes. It is recommended that you set the value to ten minutes. It is recommended that you set SD as a switching condition.

To configure an N+1 protection group of radio links, you need to configure the IF/ODU information about the working and protection links and then create an N+1 protection group. Table 11-4 provides the configuration procedure of 2+1 protection.
Issue 05 (2010-10-30)
11-15
11 N+1 Protection
Table 11-4 Configuration procedure of 2+1 protection Step 1 Operation A.5.3 Configuring the IF/ODU Information of a Radio Link Description Required. To configure SDH radio links with N+1 protection, you need to configure the IF and ODU information for each working link and the protection link. Set the parameters as follows: l Set Work Mode, Link ID, and ATPC Enable Status according to the network planning. l During a site commissioning, set ATPC Enable Status to Disabled. l Set TX Frequency (MHz), T/R Spacing(MHZ), and TX Power(dBm) according to the network planning. l Set TX Status to unmute.
NOTE To configure SDH radio links with N+1 protection, you need to configure the IF and ODU information for each working link and the protection link. Work Mode must be set to 7,STM-1,28MHz,128QAM for each link.
A.5.5 Creating an N+1 Protection Group
Required. The parameters of the N+1 protection groups of the equipment at both ends must be set to the same values. The parameters need to be set according to the network planning.
As shown in Figure 11-4, two OptiX RTN 620s are required for 3+1 protection. Table 11-5 provides the configuration procedure of 3+1 protection. Create REGs between two IF boards of the secondary NE and two ports of the SD1 board that is connected to the primary NE. Table 11-5 Configuration procedure of 3+1 protection Step 1 Operation A.5.3 Configuring the IF/ODU Information of a Radio Link Description Required. To configure SDH radio links with N+1 protection, you need to configure the IF and ODU information for each working link and the protection link. Set the parameters as follows: l Set Work Mode, Link ID, and ATPC Enable Status according to the network planning. l During a site commissioning, set ATPC Enable Status to Disabled. l Set TX Frequency (MHz), T/R Spacing(MHZ), and TX Power(dBm) according to the network planning. l Set TX Status to unmute.
NOTE To configure SDH radio links with N+1 protection, you need to configure the IF and ODU information for each working link and the protection link. Work Mode must be set to 7,STM-1,28MHz,128QAM for each link.
11-16
Issue 05 (2010-10-30)
11 N+1 Protection
Step 2
Operation A.5.5 Creating an N+1 Protection Group
Description Required. In the case of 3+1 protection, an N+1 protection group needs to be created only for the primary NE. The parameters of the 3+1 protection groups of the equipment at both ends must be set to the same values. The parameters need to be set according to the network planning. Required. In the case of 3+1 protection, configure crossconnections on the primary NE for working channels and protection channels that need to be carried on the secondary NE.
A.7.1 Creating CrossConnections of Point-to-Point Services A.5.6 Creating REGs
Required. Create REGs between two IF boards of the secondary NE and two ports of the SD1 board that is connected to the primary NE.

This section uses an example to describe how to plan and configure N+1 protection for SDH radio according to the network conditions. 11.9.1 Networking Diagram This section describes the networking information about the NEs. 11.9.2 Service Planning The service planning information contains all the parameters required for configuring the NE data. 11.9.3 Configuration Process This section describes the procedure of data configuration.

This section describes the networking information about the NEs. The service requirements between two SDH microwave sites are as follows: l l The SDH radio links need to transmit 3xSTM-1 services. The radio links need to be protected.
Issue 05 (2010-10-30)
11-17
11 N+1 Protection

101 14935M 14515M 28M Working Channel 1 V-polarization 102 14963M 14543M 28M Protection Channel H-polarization 103 14991M 14571M 28M Working Channel 2 V-polarization 104 15019M 14599M 28M Working Channel 3 H-polarization
NE1 NE2
Tx high Tx low
NE3 NE4
Site A
Link ID Tx high station Tx Freq. Tx low station Tx Freq. Channel spacing Channel Type Polarization
Site B
Plan the radio links that adopt N+1 (N = 3) as shown in Figure 11-10. In this example, NE1 and NE3 are primary NEs respectively for Site A and Site B; NE2 and NE4 are secondary NEs respectively for Site A and Site B. As shown in Figure 11-11, the NE and board configurations on Site A and Site B are the same.
11-18
Issue 05 (2010-10-30)
11 N+1 Protection
Figure 11-11 Board configuration diagram
ODU Working channel 1 Hybrid coupler ODU Working channel 2
ODU Working channel 3 Hybrid coupler ODU Protection channel

EXT IF1 FAN

Slot 20
SD1 SD1 SD1 SCC
EXT IF1 PXC PXC
Primary NE (IDU 620 )
EXT IF1 FAN

Slot 20
SD1 SD1 SD1 SCC
EXT IF1 PXC PXC
Secondary NE (IDU 620 )
l l
The two IF1 boards of the primary NE provide two working channels; the two IF1 boards of the secondary NE provide one working channel and one protection channel. The SD1 board in slot 6 on the primary NE accesses 2xSTM-1 services. Then, the primary NE transmits the two services respectively through Working channel 1 and Working channel 2. The primary NE accesses 1xSTM-1 service through port 1 on the SD1 board in slot 8 and transmits the service to the secondary NE through port 1 on the SD1 board in slot 4. Generally, the protection channel does not carry extra traffic.
l l

Basic Information About Radio Links

Based on the spectrum allocation on the radio network and the required radio transmission capacity, you can obtain the basic information about the radio links as shown in Table 11-6.
11 N+1 Protection
Table 11-6 Basic information about radio links Parameter Link ID Tx high site Tx low site Tx frequency at the Tx high site (MHz) Tx frequency at the Tx low site (MHz) T/R spacing (MHz) Work mode Link 1 (Working Link 1) 101 NE1 (primary NE on Site A) NE3 (primary NE on Site B) 14935 14515 420 Service capacity: STM-1 Channel spacing: 28 MHz Modulation mode: 128 QAM RF configuration mode Polarization direction N+1 (N = 3) V (vertical polarization) H (horizontal polarization) V (vertical polarization) H (horizontal polarization) Link 2 (Protection Link) 102 NE2 (secondary NE on Site A) NE4 (secondary NE on Site B) 14963 14543 420 Service capacity: STM-1 Channel spacing: 28 MHz Modulation mode: 128 QAM Link 3 (Working Link 2) 103 NE1 (primary NE on Site A) NE3 (primary NE on Site B) 14991 14571 420 Service capacity: STM-1 Channel spacing: 28 MHz Modulation mode: 128 QAM Link 4 (Working Link 3) 104 NE2 (secondary NE on Site A) NE4 (secondary NE on Site B) 15019 14599 420 Service capacity: STM-1 Channel spacing: 28 MHz Modulation mode: 128 QAM
NOTE
The planning information that is not associated with the configuration of the IDU (except for the polarization direction) is not provided in this example.
Power and ATPC information

By using the radio network planning software such as the Pathloss, you can analyze and compute the parameters of radio links and obtain the radio link power and ATPC information as shown in Table 11-7. Table 11-7 Power and ATPC information Parameter Transmit power (dBm) Link 1 (Working Link 1) 16.5 (NE1) 16.5 (NE3) Link 2 (Protection Link) 16.5 (NE2) 16.5 (NE4) Link 3 (Working Link 2) 16.5 (NE1) 16.5 (NE3) Link 4 (Working Link 3) 16.5 (NE2) 16.5 (NE4)
11-20
Issue 05 (2010-10-30)
11 N+1 Protection
Parameter ATPC enabling ATPC automatic threshold enabling
Link 1 (Working Link 1) Disabled -
Link 2 (Protection Link) Disabled -
NOTE
l The transmit power is calculated in 128 QAM modulation mode. l The ATPC feature is not enabled in this example.
N+1 Protection Configuration Information About the Primary NE

Two OptiX RTN 620s are required for configuring 3+1 protection, but you only need to configure an N+1 (N = 3) protection group on the primary NE. Based on the microwave type, slot priorities of IF boards, and configuration rules of N+1 protection, you can obtain the information about N+1 protection, as provided in Table 11-8. Table 11-8 Information about N+1 (N = 3) protection Parameter Work Unit NE1 (Primary NE on Site A) 5-IF1 7-IF1 4-SD1-1 Protection Unit WTR time(s) SD enable 4-SD1-2 600 seconds (default value) Enabled NE3 (Primary NE on Site B) 5-IF1 7-IF1 4-SD1-1 4-SD1-2 600 seconds (default value) Enabled
Cross-Connect Configuration Information About the Primary NE

In the case of 3+1 protection, configure cross-connections on the primary NE for working channels and protection channels that need to be carried on the secondary NE. As shown in Figure 11-11, respectively configure cross-connections from the receive ports (ports 1 and 2 on the SD1 board in slot 8 on the primary NE) to the transmit ports (ports 1 and 2 on the SD1 board in slot 4 on the primary NE) on NE1 and NE3. Table 11-9 Cross-connect configuration information about the primary NE Parameter Level Direction
Issue 05 (2010-10-30)
Working Link 3 VC-4 Bidirectional
Protection Link VC-4 Bidirectional

11-21
11 N+1 Protection
Parameter Source Source Port Source VC4 Source Timeslot Range (e.g.1,3-6) Sink Sink Port Sink VC4 Sink Timeslot Range (e.g.1,3-6)
Working Link 3 8-SD1 1 VC4-1 4-SD1 1 VC4-1 -
Protection Link 8-SD1 2 VC4-1 4-SD1 2 VC4-1 -
REG Configuration Information About the Secondary NE

Figure 11-11 shows the board configurations for Site A and Site B. In the case of 3+1 protection, create REGs between two IF boards of the secondary NE and two ports of the SD1 board that is connected to the primary NE. Table 11-10 REG configuration information about the secondary NE Parameter REG (Working Link 3) West Line East Line SD Enabled REG (Protection Link) West Line East Line SD Enabled NE2 (Secondary NE on Site A) 5-IF1 4-SD1-1 Enabled 7-IF1 4-SD1-2 Enabled NE4 (Secondary NE on Site B) 5-IF1 4-SD1-1 Enabled 7-IF1 4-SD1-2 Enabled

Procedure
Step 1 See A.5.3 Configuring the IF/ODU Information of a Radio Link and configure the IF/ODU parameters for each link. The following table provides the values of the IF/ODU parameters for each working link and protection link on Site A.
11 N+1 Protection
Parameter
Value (Primary NE on Site A) 5-IF1 and 15ODU 7-IF1 and 17ODU 103 7, STM-1, 28 MHz, 128 QAM Disabled 14991 420 16.5 unmute
Value (Secondary NE on Site A) 5-IF1 and 15ODU 104 7, STM-1, 28 MHz, 128 QAM Disabled 15019 420 16.5 unmute 7-IF1 and 17ODU 102 7, STM-1, 28 MHz, 128 QAM Disabled 14963 420 16.5 unmute
Link ID Work Mode ATPC Enable Status TX Frequency (MHz) T/R Spacing (MHZ) TX Power (dBm) TX Status
101 7, STM-1, 28 MHz, 128 QAM Disabled 14935 420 16.5 unmute
The following table provides the values of the IF/ODU parameters for each working link and protection link on Site B. Parameter Value (Primary NE on Site B) 5-IF1 and 15ODU Link ID Work Mode ATPC Enable Status TX Frequency (MHz) T/R Spacing (MHZ) TX Power (dBm) TX Status 101 7, STM-1, 28 MHz, 128 QAM Disabled 14515 420 16.5 unmute 7-IF1 and 17ODU 103 7, STM-1, 28 MHz, 128 QAM Disabled 14571 420 16.5 unmute Value (Secondary NE on Site B) 5-IF1 and 15ODU 104 7, STM-1, 28 MHz, 128 QAM Disabled 14599 420 16.5 unmute 7-IF1 and 17ODU 102 7, STM-1, 28 MHz, 128 QAM Disabled 14543 420 16.5 unmute
Step 2 See A.14.2 Creating MAs and create an N+1 protection group.
Issue 05 (2010-10-30)
11-23
11 N+1 Protection
In the case of 3+1 protection, an N+1 protection group needs to be created only for the primary NE. The N+1 protection parameters for NE1 (primary NE on Site A) and NE3 (primary NE on Site B) are set to the same values, as provided in the following table. Parameter WTR Time(s) SD enable Slot Mapping Relation Value Range 600 Enabled Work Unit: 5-IF1-1(SDH-1) 7-IF1-1(SDH-1) 4-SD1-1(SDH-1) Slot Mapping Relation Protection Unit: 4-SD1-2(SDH-2)
Step 3 See A.14.2 Creating MAs and configure point-to-point service cross-connections. In the case of 3+1 protection, configure cross-connections on the primary NE for working channels and protection channels that need to be carried on the secondary NE. The cross-connection parameters for NE1 (primary NE on Site A) and NE3 (primary NE on Site B) are set to the same values, as provided in the following table. Table 11-11 Cross-connect configuration information about the primary NE Parameter Level Direction Source Source Port Source VC4 Source Timeslot Range(e.g. 1,3-6) Sink Sink Port Sink VC4 Sink Timeslot Range(e.g. 1,3-6) Value (Working Link 3) VC-4 Bidirectional 8-SD1 1 VC4-1 4-SD1 1 VC4-1 Value (Protection Link) VC-4 Bidirectional 8-SD1 2 VC4-1 4-SD1 2 VC4-1 -
11-24
Issue 05 (2010-10-30)
11 N+1 Protection
Step 4 See A.14.2 Creating MAs and create REGs. In the case of 3+1 protection, you need to create REGs on the secondary NE. The REG configuration parameters for NE2 (secondary NE on Site A) and NE4 (secondary NE on Site B) are set to the same values, as provided in the following table. Parameter SD Enabled Slot Mapping Relation Value (Working Link 3) Enabled West Line: 5-IF1-1(SDH-1) East Line: 4-SD1-1(SDH-1) Value (Protection Link) Enabled West Line: 7-IF1-1(SDH-1) East Line: 4-SD1-2(SDH-2)
----End

This section provides the hyperlinks of the operation tasks associated with N+1 protection.
Related Tasks
A.5.3 Configuring the IF/ODU Information of a Radio Link A.5.5 Creating an N+1 Protection Group A.5.6 Creating REGs A.5.14 Querying the IF N+1 Protection Status A.5.16 Performing IF N+1 Protection Switching A.5.17 Starting/Stopping the N+1 Protection Protocol
11.11 Relevant Alarms and Performance Events

When an N+1 protection switching occurs, the IF board reports corresponding alarms.
Relevant Alarms
l l l NP1_SW_INDI The NP1_SW_INDI alarm indicates the N+1 protection switching. NP1_SW_FAIL The NP1_SW_FAIL alarm indicates that the N+1 protection switching fails. NP1_MANUAL_STOP The NP1_MANUAL_STOP alarm indicates that the protection protocol is manually stopped.
Relevant Performance Events

N+1 protection switching
11 N+1 Protection
This performance event indicates that the N+1 protection switching occurs.
11.12 FAQs
This section describes the answers to the questions that are frequently raised when the N+1 protection feature is used. Q: What switching states does the N+1 protection have? A: The N+1 protection has the following switching states: l l l l l l l l l l Protocol not started The state when the N+1 protection protocol is not started Protocol starting The state when the N+1 protection protocol is being started Protocol normal The normal state after the N+1 protection protocol is started Lockout The state after the protection channel is locked out Forced The state after a forced switching Manual The state after a manual switching Exercise The state after an exercise switching Signal failure The state after an SF switching Signal degrade The state after an SD switching WTR The state that lasts from the time the working equipment is restored to normal after an automatic switching to the time the revertive switching occurs in the revertive mode Q: Why cannot the forced switching be performed when the signal on the protection channel fails? A: After the signal on the protection channel fails, the protection channel is locked out. The lockout of the protection channel has a higher priority than the forced switching. Hence, the forced switching cannot be performed. Q: Why does the creation of an N+1 protection group fail? A: Common causes are as follows: l l The radio work mode of the IF board is not configured. The radio work mode of the IF board is not the STM-1 mode.
11-26
Issue 05 (2010-10-30)
11 N+1 Protection
Q: What is the method of handling an N+1 protection switching failure? A: Check whether the protection channel is normal or whether the protection channel is already used to protect other services. l l If alarms are generated on the protection channel, analyze the fault causes according to the alarms and rectify the faults. If the protection channel is already used to protect other services, rectify the faults in the other services so that the protection channel can be released to idle state or change the protection mode for this service.
Issue 05 (2010-10-30)
11-27
12 Automatic Transmit Power Control
12
Automatic Transmit Power Control
About This Chapter

This chapter describes the automatic transmit power control (ATPC) feature. 12.1 Introduction This section provides the definition of ATPC and describes its purpose. 12.2 Specifications This section describes the specifications of ATPC. 12.3 Availability This section describes the support required by the application of the ATPC feature and its dependency. 12.4 Principles The ATPC function is implemented through the ATPC overhead in the microwave frame. 12.5 Planning Guidelines Follow certain guidelines when you plan ATPC. 12.6 Configuration Procedure When configuring ATPC, you need to set the parameters of ATPC and the maximum transmit power of ODUs. 12.7 Configuration Example This section uses an example to describe how to plan and configure ATPC according to network conditions. 12.8 Task Collection This section provides the hyperlinks of the operation tasks associated with the feature. 12.9 Relevant Alarms and Events When the ATPC adjustment occurs, the IF board reports the relevant performance events. 12.10 FAQs This section provides answers to the questions that are frequently asked when ATPC is used.
Issue 05 (2010-10-30)
12-1
12.1 Introduction
This section provides the definition of ATPC and describes its purpose.
Definition
ATPC is a method of adjusting transmit power based on the fading of transmit signal detected at the receiver. When the ATPC function is enabled, the following conditions are possible: l If the RSL at the receiver is 2 dB lower than the central value of the ATPC upper threshold and the ATPC lower threshold, the receiver notifies the transmitter of an increase in the transmit power. Therefore, the RSL can be within the value range that has a bias of 2 dB from the central value of the ATPC upper threshold and the ATPC lower threshold. See Figure 12-1.
NOTE
l The preset maximum transmit power of the ODU should not be more than the rated maximum transmit power of the ODU. l If the actual transmit power of the ODU reaches the preset maximum transmit power whereas the RSL at the receiver fails to be within the value range that has a bias of 2 dB from the central value of the ATPC upper threshold and the ATPC lower threshold, adjustments are no longer made.
If the RSL at the receiver is 2 dB higher than the central value of the ATPC upper threshold and the ATPC lower threshold, the receiver notifies the transmitter of a decrease in the transmit power. Therefore, the RSL can be within the value range that has a bias of 2 dB from the central value of the ATPC upper threshold and the ATPC lower threshold. See Figure 12-1.
Figure 12-1 Relationship between the RSL and TSL

TSL/RSL
TSL
Up-fading Central value of the ATPC upper threshold and the ATPC lower threshold 2dB RSL 2dB Down-fading
12-2
Issue 05 (2010-10-30)
Purpose
The ATPC technology enables the equipment to automatically change the output power of the transmitter within the ATPC control range based on the received signal level at the receive end. In this manner, the received signal level at the receive end can be controlled within a fixed range and therefore the interference to the neighboring system and the residual error rate are reduced.
12.2 Specifications
This section describes the specifications of ATPC. Table 12-1 lists the specifications of ATPC. Table 12-1 Specifications of ATPC Item ATPC control range Specifications The upper threshold is the maximum transmit power of ODUs The lower threshold is the minimum transmit power of ODUs ATPC adjustment step Automatic adjustment based on the difference between the RSL and the central value of the ATPC upper threshold and the ATPC lower threshold. The maximum adjustment step at one time is 10 dB. > 30 dB/s Supported
ATPC adjustment speed Maximum transmit power of ODUs
12.3 Availability
This section describes the support required by the application of the ATPC feature and its dependency.

Table 12-2 Hardware and version support Feature ATPC Applicable Board IF0A IF0B IF1A IF1B
Issue 05 (2010-10-30)
Applicable Hardware Version All the versions All the versions All the versions All the versions
Applicable Product Version V100R002 and later V100R002 and later V100R001 and later V100R001 and later
12-3
Feature
Applicable Board IFH2 IFX
Applicable Hardware Version All the versions All the versions
Applicable Product Version V100R003 and later V100R002 and later
NOTE
The working principle of the ATPC function on the OptiX RTN 600 of version V100R003 or later is different from the working principle of the ATPC function on the OptiX RTN 600 of version V100R002 or earlier. In the case of the OptiX RTN 600 of version V100R002 or earlier, the receive end tests the received signal level (RSL). Then, the transmit end increases the transmit power if the RSL is lower than the preset ATPC lower threshold; the transmit end decreases the transmit power if the RSL is higher than the preset ATPC upper threshold.
Feature Dependency
l l The ATPC parameters, such as ATPC enable status and ATPC adjustment thresholds, need to be set to the same values for the members of an XPIC workgroups. The ATPC parameters, such as ATPC enable status and ATPC adjustment thresholds, need to be set to the same values for the members of an N+1 protection group.
12.4 Principles
The ATPC function is implemented through the ATPC overhead in the microwave frame. Figure 12-2 Realization principle of the ATPC
Transmitter Receiver RSL not within the value range that has a bias of 2 dB from the central valu e of the ATPC upper threshold and ATPC lower threshold RSL not within the value range that has a bias of 2 dB from the central valu e of the ATPC upper threshold and ATPC lower threshold
Microwave frame (ATPC overhead indicates power adjustment and adjustment step)
Adjust the ODU power once according to the ATPC adjustment step
...........
Microwave frame (ATPC overhead indicates power adjustment and adjustment step)
Adjust the ODU power once according to the ATPC adjustment step
...........
RSL within the value range that has a bias of 2 dB from the central valu e of the ATPC upper threshold and ATPC lower threshold
Microwave frame (ATPC overhead indicates no adjustments to the transmit power) ...........
12-4
Issue 05 (2010-10-30)
The realization principle is as follows: 1. 2. The receiver detects the RSL. When the ATPC function is enabled, if the RSL is not within the value range that has a bias of 2 dB from the central value of the ATPC upper threshold and the ATPC lower threshold, the receiver determines the power adjustment type and adjustment step according to the difference between the RSL and the central value of the ATPC upper threshold and the ATPC lower threshold. In addition, the receiver sets the ATPC overhead to inform the transmitter of the power adjustment type and adjustment step. The transmitter adjusts the transmit power of the ODU.
NOTE
3.
When the transmit power of the ODU reaches the preset value of the maximum transmit power of the ODU, the transmitter does not increase the transmit power of the ODU any longer.
4. 5.
After sending the ATPC overhead that indicates an adjustment to the transmit power, after a certain period. Hence, the transmitter is notified that the adjustment stops. If the receiver detects that the RSL is still not within the value range that has a bias of 2 dB from the central value of the ATPC upper threshold and the ATPC lower threshold, the system repeats steps 2 and 4 until the RSL is within the value range that has a bias of 2 dB from the central value.
NOTE
l When the difference between the RSL and the central value of the ATPC upper threshold and the ATPC lower threshold is less than 12 dB, one ATPC adjustment can meet the requirement for the transmit power if the interference due to fast fading does not exist. Otherwise, several ATPC adjustments are required. l If the number of ATPC adjustments reaches the maximum number but the difference between the RSL and the central value of the ATPC upper threshold and the ATPC lower threshold is more than 2 dB, the system starts new ATPC adjustments after a certain period.

Follow certain guidelines when you plan ATPC.
OptiX RTN 600 of V100R002 and Earlier

Follow certain guidelines when you plan ATPC parameters: l l l l Set the ATPC parameters consistent for both sides of a hop of radio link. It is recommended that you disable the ATPC function in areas where fast fading is severe. To prevent sudden fast fading from causing the RSL lower than receiver sensitivity, set the lower ATPC threshold to a value 10 dB or more higher than receiver sensitivity. Generally, the upper ATPC threshold should be 20 dB to 30 dB higher than the lower ATPC threshold, and must be equal to or higher than 15 dB. If the difference between the upper threshold and the lower threshold is great, the number of ATPC adjustments decreases and the system load is reduced. If the difference between the upper threshold and the lower threshold is small, the transmit power is adjusted in a timely manner and the interference to adjacent systems is reduced. It is recommended that you set the ATPC adjustment step to 5 dB.
l
Issue 05 (2010-10-30)
OptiX RTN 600 of V100R003 and Later

Follow certain guidelines when you plan ATPC parameters: l l l l l Set ATPC parameters consistent at the two sides of a hop of microwave link. It is recommended that you disable the ATPC function for areas where fast fading is severe. Set the central value of the ATPC upper threshold and the ATPC lower threshold so that the central value is equal to the required value of the receive power. Ensure that the difference between values of the automatic ATPC upper threshold and the automatic ATPC lower threshold is not less than 5 dB. Set the maximum transmit power of the ODU when the transmit power of the ODU needs to be restricted to a certain range.

When configuring ATPC, you need to set the parameters of ATPC and the maximum transmit power of ODUs. Table 12-3 Configuration procedure of ATPC Step 1 Operation A.5.3 Configuring the IF/ODU Information of a Radio Link Remarks You can set certain parameters of ATPC. Set the major parameters as follows: l When commissioning a site, set ATPC Enable Status to Disabled. l It is recommended that you set ATPC Upper Threshold (dBm) to Power to Be Received(dBm) plus 10 dB. l It is recommended that you set the lower ATPC threshold (dBm) to Power to Be Received(dBm) minus 10 dB. l It is recommended that you set ATPC Automatic Threshold Enable Status to Disabled. l If the maximum transmit power allowed by ATPC adjustment needs to be set, set Maximum Transmit Power(dBm) accordingly. l TX High Threshold(dBm), TX Low Threshold(dBm), RX High Threshold(dBm), and RX Low Threshold(dBm) affect only the performance events associated with ATPC. Set these parameters if necessary. 2 A.5.9 Setting Parameters of ODU Interfaces Set Maximum Transmit Power(dBm) of ODUs based on network planning.

This section uses an example to describe how to plan and configure ATPC according to network conditions.
12.7.1 Networking Diagram This section describes the networking information about NEs. 12.7.2 Service Planning The service planning information contains all the parameters required for configuring the NE data. 12.7.3 Configuration Process This section describes the procedure of data configuration.

This section describes the networking information about NEs. As shown in Figure 12-3, the ATPC function needs to be enabled on the radio link between two NEs of the OptiX RTN 620. Figure 12-3 Networking diagram
Enable Disabled -36.0dBm -56.0dBm -46.0dBm
NE1
NE2
ATPC Enable Status ATPC Automatic Threshold Enable ATPC Upper Threshold (dBm) ATPC Lower Threshold (dBm) Power to Be Received(dBm)

ATPC Information
Table 12-4 provides the ATPC information of NE1 and NE2.
Issue 05 (2010-10-30)
12-7
Table 12-4 ATPC information Parameter ATPC Enable Status Automatic ATPC Threshold Setting ATPC Upper Threshold (dBm)a ATPC Lower Threshold (dBm) Maximum Transmit Power of an ODU Value Range Enabled Disabled -36.0 -56.0 -
NOTE
l A planning principle defines that the upper and lower ATPC thresholds should be the value of Power to Be Received(dBm) 10 dBm. If the value of Power to Be Received(dBm) of an NE is -46.0 dBm, the upper and lower ATPC thresholds should be set to -36.0 dBm and -56.0 dBm. l The maximum transmit power of an ODU refers to the actual maximum transmit power of the ODU after the ATPC function is enabled. By default, this parameter takes the rated maximum transmit power of an ODU. When an ODU works at the rated maximum transmit power, the electromagnetic wave matches the spectrum profile Therefore, you need not set this parameter in general cases.

Procedure
Step 1 A.5.7 Configuring the ATPC function. The following table provides the parameter values of NE1 and NE2. Parameter Value Range 5-IFH2 and 15-ODU ATPC Enable Status ATPC Upper Threshold (dBm) ATPC Lower Threshold (dBm) ATPC Automatic Threshold Enable Status Enabled -36.0 -56.0 Disabled
----End

This section provides the hyperlinks of the operation tasks associated with the feature.
12-8
Issue 05 (2010-10-30)
Related Tasks
A.5.7 Configuring the ATPC function A.5.9 Setting Parameters of ODU Interfaces A.5.10 Querying ATPC Adjustment Records

When the ATPC adjustment occurs, the IF board reports the relevant performance events.
Relevant Alarms
None.

l l ATPC_P_ADJUST The ATPC_P_ADJUST indicates the positive ATPC adjustment event. ATPC_N_ADJUST The ATPC_N_ADJUST indicates the negative ATPC adjustment event.
12.10 FAQs
This section provides answers to the questions that are frequently asked when ATPC is used. Q: Why is the RSL sometimes more than 2 dB higher or lower than the central value of the ATPC threshold range, when the ATPC function is enabled? A: Major causes may be as follows: l The ATPC adjustment speed is lower than the instantaneous fading speed. This ATPC adjustment speed may be lower than the instantaneous speed of certain fadings. In this case, the transmit power adjusted by the ATPC function fails to offset the fading in a timely manner, and hence, the RSL is more than 2 dB higher or lower than the central value of the ATPC threshold range. l The transmit power reaches the threshold of the ATPC control range, and cannot be increased or decreased.
Q: What are the differences and similarities between APTC and remote transmit power control (RTPC)? Answer: The differences and similarities between ATPC and RTPC are as follows: l l Adjustment objects The adjustment objects of ATPC and RTPC are transmit power at the transmit end. Adjustment schemes The adjustment scheme of ATPC is to automatically adjust transmit power by detecting transmit signal attenuation at the receive end. The adjustment scheme of RTPC is to remotely control transmit power by issuing commands on the NMS.
Adjustment ranges The upper threshold for the ATPC adjustment range is the rated maximum transmit power of the ODU, and the lower threshold is the rated minimum transmit power of the ODU. The upper threshold for the RTPC adjustment range is the maximum transmit power that meets the spectrum mask requirements, and the lower threshold is the minimum transmit power that meets the spectrum mask requirements.
NOTE
For details on the specific RTPC adjustment range, see the RTN 600 System Parameters.
Adjustment steps ATPC automatically changes the adjustment step according to receive level and the central value of the upper and lower thresholds. The minimum adjustment step of ATPC is 1 dB. The maximum adjustment step of RTPC is limited to the adjustment range. The minimum adjustment step of RTPC is 0.5 dB.
12-10
Issue 05 (2010-10-30)
13 Adaptive Modulation
13
About This Chapter
Adaptive Modulation
This chapter describes the adaptive modulation (AM) feature. 13.1 Introduction This section provides the definition of AM and describes its purpose. 13.2 Specifications This section describes the specifications of AM. 13.3 Availability This section describes the support and dependency that AM requires. 13.4 Principles The AM function is implemented through the AM engine in the Modem unit. 13.5 Planning Guidelines Follow certain guidelines when you plan AM. 13.6 Configuration Procedure When configuring AM, you need to set the modulation mode of the guaranteed AM capacity and the modulation mode of the maximum AM capacity. 13.7 Configuration Example This section uses an example to describe how to plan and configure AM according to network conditions. 13.8 Task Collection This section provides the hyperlinks of the operation tasks associated with the feature. 13.9 Relevant Alarms and Events When the AM shift occurs, the IF board reports the relevant alarms and performance events. 13.10 FAQs This section provides answers to the questions that are frequently asked when AM is used.
Issue 05 (2010-10-30)
13-1
13.1 Introduction
This section provides the definition of AM and describes its purpose.
Definition
The AM function adjusts the modulation mode according to the quality of channels. In the case of the same channel spacing, the microwave service bandwidth varies with the modulation mode. The higher the modulation efficiency, the higher the bandwidth of the transmitted services is. When the quality of channels is good, the equipment adopts a high-efficiency modulation mode to improve transmission efficiency and frequency spectrum utilization. When the quality of channel degrades, the equipment adopts a low-efficiency modulation mode to transmit only the services with a higher priority within the available bandwidth and to discard the services with a lower priority. In this manner, the anti-interference capability is improved and the link availability for services with a high priority is ensured. When the Hybrid microwave equipment adopts the AM technology, it controls service transmission based on the service bandwidth and QoS policy corresponding to the current modulation mode. The E1 services have the highest priority. By adopting the CoS technology, the equipment schedules the Ethernet services of different types to the queues with different priorities. The services in the queues with different priorities are transmitted to the microwave port through the SP or WRR algorithm. When the queues with certain priorities are congested because of insufficient microwave bandwidth, certain or all services in the queues with these priorities are discarded. When the Hybrid microwave works in the lowest modulation mode, the equipment transmits only the E1 services. If there are extra bandwidths, the equipment can also transmit the services with a high priority. When the Hybrid microwave works in any other modulation mode, all the additional bandwidths are used to transmit the Ethernet services. In this manner, the availability of the links that carry the E1 services and the Ethernet services with a high priority is ensured, and the Ethernet service capacity is increased. Figure 13-1 shows the service change caused by the AM. The orange part indicates the E1 services. The blue part indicates the Ethernet services. The closer to the edge of the blue part, the lower is the priority of the Ethernet service. Under all channel conditions, the E1 services occupy the specific bandwidth that is permanently available. Thus, the availability of the E1 services is ensured. The bandwidth for the Ethernet services varies with the channel conditions. When the channel is in bad conditions, the Ethernet services with a low priority are discarded.
13-2
Issue 05 (2010-10-30)
Figure 13-1 Adaptive modulation
256QAM 128QAM 32QAM QPSK 256QAM Channel Capability 64QAM E1 Services Ethernet Services 128QAM 32QAM 16QAM 16QAM 64QAM
Purpose
On a radio link consisting of the Hybrid microwave systems, the AM function can ensure the link availability for services with a high priority and greatly improve the bandwidth utilization.
13.2 Specifications
This section describes the specifications of AM. Table 13-1 lists the specifications of AM. Table 13-1 Specifications of AM Item Lowest-efficiency AM mode Highest-efficiency AM mode Impact of mode shifting Specifications QPSK/16QAM/32QAM/64QAM/128QAM/ 256QAM QPSK/16QAM/32QAM/64QAM/128QAM/ 256QAM When mode shifting occurs, the transmit frequency, receive frequency, and channel spacing are not changed. In the case of down-shift, the services with a lower priority are discarded and the services with a higher priority have no errors or slips. Shifting mode AM modes are shifted step by step.
Issue 05 (2010-10-30)
13-3
Item Shifting speed
Specifications No bit error in the higher priority services in the case of 100 dB/s fast fading
13.3 Availability
This section describes the support and dependency that AM requires.

Table 13-2 Hardware and version support Feature AM Applicable Board IFH2 Applicable Hardware Version All the versions Applicable Product Version V100R003 and later
Feature Dependency
l l The AM function can work with the 1+1 HSB/FD/SD protection. When the AM function is enabled, the QoS policies need to be set to control the transmission of Ethernet services.
13.4 Principles
The AM function is implemented through the AM engine in the Modem unit.
AM Working Principle (Before the Switching)

1. 2. 3. The service is scheduled to the IF interface of the IF board and then multiplexed into the microwave frame at the MUX unit. The microwave frame is transmitted to the opposite end over the Tx path after being modulated by the IF unit. The Rx path of the opposite end receives the IF signal and then checks the quality of the received signal based on the received signal to noise ratio (SNR). In the case of the current modulation mode, the quality of the received signal is considered to be degraded if the value of the received SNR is lower than the preset threshold. In this case, the opposite end sends a signal that indicates the quality of the received signal to the AM engine. The AM engine at the opposite end sends the microwave frame to the local end after the switching indication signal is inserted into the overhead of this microwave frame. The IF unit at the local end processes the received IF signal and sends the AM switching indication signal to AM engine at the local end. The AM engine sends the switching indication signal to the MUX unit to enable the MUX unit and the air interface to change the modulation mode, as shown in Figure 13-2.
4. 5. 6.
13-4
Figure 13-2 AM switching (before the switching)
MUX unit
Microwave frame
IF Module
Tx Path
IF Module
Rx Path INDI AM Engine INDI Tx Path
Microwave frame
MUX unit
INDI AM Engine SNR MUX unit INDI Rx Path
SNR
AM Messages
Microwave frame
Microwave frame
MUX unit
Low priority service High priority service
INDI:Modulation scheme indication signal SNR:signal to noise ratio
AM Working Principle (After the Switching)

1. When the IF unit detects the SNR threshold-crossing that triggers the switching of a lowefficiency modulation mode, the unit instructs the opposite end to perform a modulation mode switching. The opposite IF unit performs QoS processing of the service according to the service bandwidth change and then schedules the corresponding service to the IF interface. Based on the result of the QoS processing, the service of a lower priority is discarded and the service of a higher priority is scheduled to the IF interface. In this case, the bandwidth of the microwave frame is decreased, as shown in Figure 13-3. When the IF unit detects the SNR threshold-crossing that triggers the switching of a high-efficiency modulation mode, it performs the operations that are similar to those performed for switching a low-efficiency modulation mode.
NOTE
In the case of the Hybrid microwave, E1 services are of the highest priority.
Issue 05 (2010-10-30)
13-5
Figure 13-3 AM switching (after the switching)
MUX unit
Microwave frame
IF Module
Tx Path
IF Module
Rx Path INDI AM Engine INDI Tx Path
Microwave frame
MUX unit
INDI AM Engine SNR MUX unit INDI Rx Path
SNR
AM Messages
Microwave frame
Microwave frame
MUX unit
Low priority service High priority service
INDI:Modulation scheme indication signal SNR:signal to noise ratio
2.
The AM function changes the modulation mode based on the frame boundary of the signal. The Rx path of the receive end sends the signal that indicates the receive mode change of the current frame to the MUX unit when detecting the change of the modulation mode. Hence, the MUX unit can receive and process service signals according to the new modulation mode.

Follow certain guidelines when you plan AM.
Planning Guidelines on the AM Enabling Status

l If Ethernet services need to meet the availability requirement for E1 services, it is recommended that you do not enable the AM function. In addition, you need to determine a fixed modulation mode according to the availability requirement and the maximum service capacity. If Ethernet services need not meet the availability requirement for E1 services (that is, a part of bandwidth can be lost when Ethernet signals degrade), it is recommended that you enable the AM function.
Planning Guidelines on AM Attributes

l Determine the highest-efficiency and lowest-efficiency AM modes based on service types, service priorities, service capacities, service bandwidth, microwave frequencies, and channel bandwidth. Calculate the availability in each AM mode by using the network planning documents. Ensure that the availability in each AM mode meets the requirements of users. Calculate the working time ratio of each AM mode.
l l
13-6

When configuring AM, you need to set the modulation mode of the guaranteed AM capacity and the modulation mode of the maximum AM capacity. Table 13-3 Configuration procedure of AM Step 1 Operation A.5.4 Setting the Hybrid/AM Attribute Remarks Configure the AM function. The parameters need to be set according to the network planning.

This section uses an example to describe how to plan and configure AM according to network conditions. 13.7.1 Networking Diagram This section describes the networking information about NEs. 13.7.2 Service Planning The service planning information contains all the parameters required for data configuration. 13.7.3 Configuration Process This section describes the procedure of data configuration.

This section describes the networking information about NEs. As shown in Figure 13-4, the AM function needs to be enabled on the radio link consisting of two NEs of the OptiX RTN 620. Figure 13-4 Networking diagram of the AM function
NE2
NE1

The service planning information contains all the parameters required for data configuration.
AM Information
Table 13-4 lists AM information. Table 13-4 AM information Parameter NE1 5-IFH2 Channel spacing (MHz) AM enabling AM guaranteed capacity mode AM full capacity mode E1 Capacity 28 Enable QPSK 128QAM 10 NE2 5-IFH2 28 Enable QPSK 128QAM 10

Procedure
Step 1 A.5.4 Setting the Hybrid/AM Attribute. The following table provides the parameter values of the IF boards on NE1 and NE2. Parameter Value Range NE1 5-IFH2 AM Enable Status IF Channel Bandwidth Modulation Mode of the Assured AM Capacity Modulation Mode of the Full AM Capacity E1 Capacity Enable 28M QPSK 128QAM 10 NE2 5-IFH2 Enable 28M QPSK 128QAM 10
----End
13-8
Issue 05 (2010-10-30)

This section provides the hyperlinks of the operation tasks associated with the feature.
Related Tasks
A.5.4 Setting the Hybrid/AM Attribute A.5.12 Querying the AM Status

When the AM shift occurs, the IF board reports the relevant alarms and performance events.
Relevant Alarms
AM_DOWNSHIFT The AM_DOWNSHIFT alarm indicates that the AM downshifts the modulation mode.

l QAMWS16 The QAMWS16 indicates the working second in the case of the QAMWS16 modulation mode. l QAMWS32 The QAMWS32 indicates the working second in the case of the QAMWS32 modulation mode. l QAMWS64 The QAMWS64 indicates the working second in the case of the QAMWS64 modulation mode. l QAMWS128 The QAMWS128 indicates the working second in the case of the QAMWS128 modulation mode. l QAMWS256 The QAMWS256 indicates the working second in the case of the QAMWS256 modulation mode. l FB_AMDCNT FB_AMDCNT indicates the count of the AM downshifts on a board in the current performance statistics period. l FB_AMUCNT FB_AMUCNT indicates the count of the AM upshifts on a board in the current performance statistics period.
13.10 FAQs
This section provides answers to the questions that are frequently asked when AM is used.
Q: What is the method of handling the failure of the AM switching? A: The possible symptoms of a modulation mode failure are as follows: l l Bit errors occur after a switching. The switching is not triggered when the switching conditions are met or the switching is triggered when the switching conditions are not met.
The possible causes of the switching failure are as follows: l The AM function is disabled. When the AM function is disabled, the radio link uses a fixed modulation mode. Hence, the flexible transmission of Ethernet services cannot be realized. l The transmit power of the ODU is manually adjusted by more than 3 dB. If the transmit power of the ODU is manually adjusted by more than 3 dB at one time, it is equivalent to the result when the rate of fast fading is more than 100 dB/s. In this case, hitless AM switching may fail. l The user incorrectly considers that the receiver sensitivity is associated with the AM switching. AM switching is realized through the detection of the SNR other than the detection of the RSL. If the SNR exceeds the specified threshold, the AM switching occurs though the RSL is higher than the receiver sensitivity. l The ATPC function and the AM function cannot work properly together. When the ATPC function is enabled, the transmit power cannot be the maximum transmit power if the upper ATPC adjustment threshold is set incorrectly. As a result, the improvement to the SNR of the radio link is affected and the AM upshift fails. An ATPC adjustment with a higher rate and a larger step results in less stability of the AM switching. The ATPC function and the AM function may affect each other when working together. Hence, it is recommended that you disable the ATPC function when the AM function is enabled.
13-10
Issue 05 (2010-10-30)
14 Subnetwork Connection Protection
14
Subnetwork Connection Protection
About This Chapter

This chapter describes the sub-network connection protection (SNCP) feature. 14.1 Introduction This section provides the definition of sub-network connection protection (SNCP) and describes its purpose. 14.2 Basic Concepts This section describes the basic concepts associated with SNCP. 14.3 Specifications This section provides the specifications of SNCP. 14.4 Reference Standards and Protocols This section describes the standards and protocols associated with SNCP. 14.5 Availability This section describes the support required by SNCP and dependency of the feature. 14.6 Principles SNCP functions based on the dual fed and selective receiving mechanism. 14.7 Planning Guidelines Follow certain guidelines when you plan SNCP. 14.8 Configuration Procedure When configuring SNCP services, you need to create cross-connections of SNCP services and set SNCP automatic switching conditions as required. 14.9 Configuration Example This section uses an example to describe how to plan and configure SNCP according to network conditions. 14.10 Task Collection This section provides the hyperlinks of the operation tasks associated with SNCP. 14.11 Relevant Alarms and Events When an SNCP switching occurs, the system reports the relevant alarms and abnormal events.
14.12 FAQs This section provides the answers to the questions that are frequently asked when SNCP is adopted.
14-2
Issue 05 (2010-10-30)
14.1 Introduction
This section provides the definition of sub-network connection protection (SNCP) and describes its purpose.
Definition
SNCP is a service protection scheme that switches services to the protection SNC when the working SNC fails or degrades. The subnet can be a chain, a ring, or a more complex network. SNCP functions based on the dual fed and selective receiving mechanism. Figure 14-1 shows the application of SNCP. Figure 14-1 Subnetwork connection protection
Working SNC Trail source Trail sink
NE A Protection SNC
NE B
Protection switching
NE A Protection SNC
NE B
Purpose
SNCP improves the reliability of service transmission, especially on ring topologies where traffic load is heavy, including ring with chain, tangent rings, and intersecting rings.
14.2 Basic Concepts

This section describes the basic concepts associated with SNCP.
14.2.1 Protection Type SNCP is classified into the revertive mode and the non-revertive mode. 14.2.2 SNCP Service Pair An SNCP service pair is a basic unit of SNCP. It consists of a working source, a protection source, and a service sink. 14.2.3 Hold-Off Time SNCP works based on services, and 1+1 protection works based on links. When services configured with SNCP are transmitted on the links configured with 1+1 protection, you need to set the hold-off time to ensure that a 1+1 protection switching occurs before an SNCP switching. In this manner, you can avoid repeated SNCP switching events caused by a 1+1 protection switching. 14.2.4 Switching Conditions SNCP configured for different services has different switching conditions. 14.2.5 Switching Impact Within the SNCP switching time (< 50 ms), services are interrupted.

SNCP is classified into the revertive mode and the non-revertive mode. l Revertive mode When an NE is in the switching state, the NE releases the switching some time after the former working channel is restored to normal. The period after the former working channel is restored to normal and before the NE releases the switching is called the wait-to-restore (WTR) time. To prevent frequent switching events due to an unstable working channel, it is recommended that you set the WTR time to a value from 5 to 12 minutes. l Non-revertive mode When an NE is in the switching state, the NE maintains the switching unless another switching occurs, even though the former working channel is restored to normal .
14.2.2 SNCP Service Pair

An SNCP service pair is a basic unit of SNCP. It consists of a working source, a protection source, and a service sink. Figure 14-2 SNCP service pair
Working source Protection source
Service sink
The working source and the protection source can be fiber lines, STM-1e electrical cables, or radio links. In addition, they need not be of the same type. The service sink can be any line or tributary.
14.2.3 Hold-Off Time

SNCP works based on services, and 1+1 protection works based on links. When services configured with SNCP are transmitted on the links configured with 1+1 protection, you need to set the hold-off time to ensure that a 1+1 protection switching occurs before an SNCP switching. In this manner, you can avoid repeated SNCP switching events caused by a 1+1 protection switching. The following part describes the function of the hold-off time on a network configured with 1 +1 SD and SNCP.
An Example Wherein 1+1 SD and SNCP Coexist

As shown in Figure 14-3, the services between NE A and NE C are configured with revertive SNCP. The radio links between NE B and NE C are configured with 1+1 SD. In normal cases, the working SNC traverses NE B. Figure 14-3 An application scenario wherein 1+1 SD and SNCP coexist
NE A
Working SNC
NE B
NE D
The service between NE B and NE C is transmitted on the main link NE C
Description of the Switching When the Hold-Off Time Is Not Set

If the hold-off time of SNCP is not set (that is, the hold-off time is 0), the fading on the active radio link between NE B and NE C triggers an SNCP switching and a 1+1 HSB switching at the same time. When a 1+1 HSB switching occurs, the services between NE B and NE C are switched to the standby radio link. When an SNCP switching occurs, the services between NE B and NE C are switched to the protection SNC trail. Figure 14-4 shows the traffic flow.
Issue 05 (2010-10-30)
14-5
Figure 14-4 Traffic flow after an SNCP switching and a 1+1 HSB switching
NE A Protection SNC
NE B
NE D
The service between NE B and NE C is transmitted on the standby link
NE C
After the fault on the link is rectified, a revertive SNCP switching occurs. Figure 14-5 shows the traffic flow after the switching. Figure 14-5 Traffic flow after a revertive SNCP switching
NE A Working SNC
NE B
NE D
NE C
14-6
Issue 05 (2010-10-30)
Description of the Switching When the Hold-Off Time Is Set

If the hold-off time is set, an SNCP switching does not occur immediately after the system detects a switching condition. Instead, the system checks whether the switching condition persists after a certain period. If the switching condition persists, an SNCP switching occurs. If the switching condition disappears, no SNCP switchings are triggered. In this example, if the hold-off time is set, the fault on the active radio link between NE B and NE C first triggers a 1+1 HSB switching. If the 1+1 HSB switching is completed within the hold-off time, the SNCP switching condition no longer exists when the hold-off time expires. Therefore, no SNCP switchings are triggered. Figure 14-6 shows the final traffic flow after the 1+1 HSB switching. Compared with the switching situation where the hold-off time is not set, two SNCP switchings are avoided. Figure 14-6 Traffic flow after a 1+1 HSB switching when the hold-off time is set
NE A Working SNC
NE B
NE D
NE C

SNCP configured for different services has different switching conditions. Table 14-1 SNCP switching conditions Switching Condition Clear switching (external switching) Priority From top to bottom, the priority is from the Description All external switching states are cleared.
Issue 05 (2010-10-30)
14-7
Switching Condition Lockout of protection channel (external switching)
Priority highest to the lowest.
Description The lockout of protection channel blocks normal service signals from entering the protection channel but does not block service signals from being switched from the protection channel to the working channel. The signal failure condition on the protection channel is equivalent to the lockout of the protection channel. If the switching is in the lockout or forced state, no switching occurs. Otherwise, the system switches services from the working SNC to the protection SNC or from the protection SNC to the working SNC according to the command. Then, the switching changes to the forced switching state. If the switching is in the lockout or forced switching state, or if the signal of the protection SNC fails, no switching occurs. Otherwise, the system switches services from the working SNC to the protection SNC. The switching then changes to the automatic switching state. For the trigger conditions of an automatic switching, refer to Table 14-2 and Table 14-3.
Signal failure
14-8
Issue 05 (2010-10-30)
Switching Condition Manual switching (external switching)
Priority
Description If the switching is in the lockout, forced, or manual switching state, or if the signal of the protection SNC fails, no switching occurs. Otherwise, the system switches services from the working SNC to the protection SNC or from the protection SNC to the working SNC according to the command. The switching then enters the manual switching state. When the switching is in the automatic state and the former working SNC is already restored to normal for the WTR time, a revertive switching occurs. After the former working SNC is restored to normal and before the revertive switching occurs, the switching is in the WTR state. After the revertive switching, the switching changes to the normal state.
NOTE
In the case of revertive SNCP, if services are currently on the protection channel, the services cannot be switched to the working channel when you perform a forced switching or a manual switching.
SNCP Switching Conditions (VC-4 Services)

Table 14-2 Trigger conditions of an automatic SNCP switching (VC-4 services) Switching Condition Hardware fault on an IF board and a line board R_LOS R_LOF R_LOC Description Default condition Default condition Default condition Default condition
Issue 05 (2010-10-30)
14-9
Switching Condition MS_AIS B2_EXC AU_LOP AU_AIS HP_LOM MW_LOF MW_LIM B3_EXC B3_SD HP_TIM HP_UNEQ
Description Default condition Default condition Default condition Default condition Default condition Default condition (applicable only when an IF board works as a line board) Default condition (applicable only when an IF board works as a line board) Optional condition Optional condition Optional condition Optional condition
NOTE
Only after you set the optical conditions as trigger conditions on the NMS, the optional conditions in the preceding table can be trigger conditions of an automatic SNCP switching at the VC-4 level. By default, the optional conditions do not trigger an automatic SNCP switching.
SNCP Switching Conditions (Lower Order Services)

Lower order services include VC-3/VC-12 services and E1 services transmitted over the Hybrid microwave.
NOTE
The VC-3/VC-12 service in the following table refers to the VC-3/VC-12 service that is transmitted over optical lines or SDH radio links and the E1 service transmitted by the IF1A/IF1B board.
Table 14-3 Trigger conditions of an automatic SNCP switching (VC-3/VC-12 services) Switching Condition Hardware fault on the line board R_LOS R_LOF R_LOC MS_AIS B2_EXC
14-10
Description Default condition Default condition Default condition Default condition Default condition Default condition
Issue 05 (2010-10-30)
Switching Condition AU_LOP AU_AIS HP_LOM MW_LOF MW_LIM TU_AIS TU_LOP
Description Default condition Default condition Default condition Default condition (applicable only when an IF board works as a line board) Default condition (applicable only when an IF board works as a line board) Default condition Default condition
Table 14-4 Trigger conditions of an automatic SNCP switching (E1 services transmitted over the Hybrid microwave) Switching Condition E1_AIS (indicating that E1 signals are all 1s) R_LOF R_LOC MW_LOF MW_LIM MW_BER_EXC MW_BER_SDa Description Default condition Default condition Default condition Default condition Default condition Default condition Default condition
NOTE
a: The MW_BER_SD alarm serves as a default condition only when AIS insertion in the case of MW_BER_SD is enabled.

Within the SNCP switching time (< 50 ms), services are interrupted.
14.3 Specifications
This section provides the specifications of SNCP. Table 14-5 lists the specifications of SNCP.
Issue 05 (2010-10-30)
14-11
Table 14-5 Specifications of SNCP Item Maximum number of SNCP protection groups Types of services protected with SNCP Specification 210 SDH/PDH services on optical transmission links SDH/PDH services transmitted on the IF1A/ IF1B/IFX boards E1 services transmitted over the Hybrid microwave Protection type Revertive mode Non-revertive mode WTR time Optional SNCP switching conditions (VC-4 services)a 5-12 minutes B3_EXC B3_SD HP_TIM HP_UNEQ Switching time Coexistence with 1+1 protection < 50 ms Supported
NOTE
a: For details about SNCP switching conditions, see 14.2.4 Switching Conditions.

This section describes the standards and protocols associated with SNCP. The following protocol is associated with SNCP: l ITU-T G.841: Types and characteristics of SDH network protection architectures
14.5 Availability
This section describes the support required by SNCP and dependency of the feature.
14-12
Issue 05 (2010-10-30)

Table 14-6 Hardware and version support Feature SNCP Applicable Board IF1A/IF1B SL1/SD1 SLE/SDE SL4 IFX IFH2 Applicable Hardware Version All the versions All the versions All the versions All the versions All the versions All the versions Applicable Product Version V100R001 and later V100R001 and later V100R001 and later V100R002 and later V100R002 and later V100R005C00 and later
Feature Dependency
l l l l l A line configured with linear MSP can work only as the service sink of an SNCP service pair, rather than the working source or protection source. A radio link configured with 1+1 protection can work as the working source, protection source, or service sink of an SNCP service pair. A radio link configured with N+1 protection can work only as the service sink of an SNCP service pair, rather than the working source or protection source. A radio link configured with XPIC can work as the working source, protection source, or service sink of an SNCP service pair. On a Hybrid microwave ring network, you can configure SNCP for E1 services and ERPS for Ethernet services.
14.6 Principles
SNCP functions based on the dual fed and selective receiving mechanism.
NOTE
The following part uses the switching triggered by the signal failure of the working SNC as an example to describe the switching principle of SNCP.
Issue 05 (2010-10-30)
14-13
Figure 14-7 SNCP working principle (before a switching)

NE A Protection SNC
NE B
Figure 14-8 SNCP working principle (after a switching)

NE A Protection SNC
NE B
When the working SNC fails, SNCP works as follows: 1. 2. 3. Before a switching, the trail source (NE A) sends normal service signals to the trail sink (NE B) through the working SNC and the protection SNC. When the IF board or line board of NE B detects that the signal of the working SNC fails, it reports this event to the SCC board. After the SCC board of NE B determines that the signal of the working SNC fails and the signal of the protection SNC is normal, the SCC board enables the cross-connect board to complete the cross-connections between the protection SNC and the service sink.

Follow certain guidelines when you plan SNCP.
Planning guidelines of the working SNC and the protection SNC

l
14-14
Do not overlap the working SNC and the protection SNC if possible.
The OptiX RTN 620 does not support the line configured with MSP or N+1 protection as the working source or protection source of SNCP.
Planning guidelines of the protection configuration parameters

l l If SNCP works in revertive mode, set the WTR time to a value from 5 to 12 minutes. It is recommended that you set the WTR time to the default value, namely, ten minutes. To prevent repeated SNCP switchings, set the hold-off time for SNCP when SNCP works with any link-level protection scheme, including 1+1 protection and FD/SD protection. The hold-off time must be longer than the switching time of the link-level protection scheme. Generally, set the hold-off time to 200 ms. The switching time of 1+1 HSB is much longer than that of SNCP. Therefore, to decrease the duration of service interruptions, it is recommended that you do not set the hold-off time when SNCP works with 1+1 HSB. It is recommended that you set the hold-off time to 0 when only SNCP is configured.

When configuring SNCP services, you need to create cross-connections of SNCP services and set SNCP automatic switching conditions as required. Table 14-7 Procedure for configuring SNCP services Step 1 Operation Configur ing the crossconnecti ons of TDM services A.7.1 Creating CrossConnections of Point-to-Point Services Description Required when the TDM service is a point-to-point service. The parameters need to be set according to the service planning. Required when the TDM service is an SNCP service. The parameters need to be set according to the service planning. 2 3 A.7.4 Setting the Automatic Switching Conditions of SNCP Services A.7.3 Inserting TU_AIS Optional when the TDM service is an SNCP service. Required when the IFH2 board and IF1 board function as the east interface board and west interface board, respectively, of an SNCP ring and pass-through services are configured between the interface boards. Perform this operation for the E1 channels on the IFH2 board.
A.7.2 Creating CrossConnections for SNCP Services
Issue 05 (2010-10-30)
14-15

NOTE
In the case of TDM services configured with SNCP, you need to configure the cross-connections of SNCP services on the add-drop NEs and configure the cross-connections of point-to-point services on the pass-through NEs.

This section uses an example to describe how to plan and configure SNCP according to network conditions. 14.9.1 Networking Diagram This section describes the networking information about NEs. 14.9.2 Service Planning The service planning information contains all the parameters required for configuring the NE data. 14.9.3 Configuration Process This section describes the process for the data configuration.

This section describes the networking information about NEs. As shown in Figure 14-9, four sets of the OptiX RTN 620 compose a Hybrid microwave ring configured with SNCP. On the ring: l l The links between NE1 and NE2 and those between NE1 and NE4 adopt 1+1 HSB protection. The links between NE2 and NE3 and those between NE3 and NE4 adopt 1+0 nonprotection.
14-16
Issue 05 (2010-10-30)
Figure 14-9 Networking diagram of an SNCP ring

Tributary board4-PH1 East IF board 8-IFH2(M)6-IFH2(S) West IF board 5-IFH2(M)7-IFH2(S) 16E1 BSC 4E1 BTS1 W SNCP W NE4 BTS4 E 4E1 E W NE1
4E1 NE2 E BTS2 Tributary board4-P01 East IF board 5-IFH2(M)6-IFH2(S) West IF board 7-IFH2(M)8-IFH2(S)
Tributary board4-PO1 4E1 W NE3 E BTS3 Tributary board4-PO1 East IF board 5-IFH2(M)6-IFH2(S) West IF board 7-IFH2(M)8-IFH2(S) East IF board 5-IFH2(M)7-IFH2(S) West IF board 8-IFH2(M)6-IFH2(S)

Timeslot Allocation Diagram

Figure 14-10 shows the timeslots that are allocated for the TDM services according to the service planning information. Figure 14-10 Timeslot allocation diagram (TDM services on a TDM radio ring network)
Station Timeslot NE1 8-IFH2 VC12: 1-8 4-PH1:1-8 4-PO1:1-8 VC12: 9-12 VC4-1 4-PH1:9-12 4-PH1:13-16 Pass through (SNCP working path) Pass through (SNCP protection path) Add/Drop (SNCP working path) Add/Drop (SNCP protection path) 4-PO1:1-8 VC12: 9-12 4-PO1:1-4 VC12: 13-16 4-PO1:1-4 4-PO1:1-4 4-PH1:9-12 VC12: 13-16 4-PO1:1-4 4-PH1:13-16 NE2 7-IFH2 5-IFH2 NE3 7-IFH2 5-IFH2 VC12: 1-8 4-PH1:1-8 NE4 8-IFH2 5-IFH2 NE1 5-IFH2
Issue 05 (2010-10-30)
14-17
As shown in Figure 14-10, the information about the timeslots that the TDM services occupy on each NE is as follows: l E1 services on NE2: The E1 services are added to or dropped from the first to eighth ports on the PO1 board in slot 4 of NE2. The E1 services are added to or dropped from the first to eighth ports on the PH1 board in slot 4 of NE1. The E1 services occupy the first to eighth VC-12 timeslots on the ring. l E1 services of NE3: The E1 services are added to or dropped from the first to fourth ports on the PO1 board in slot 4 of NE3. The E1 services are added to or dropped from the ninth to twelfth ports on the PH1 board in slot 4 of NE1. The E1 services occupy the ninth to twelfth VC-12 timeslots on the ring. l E1 services on NE4: The E1 services are added to or dropped from the first to fourth ports on the PO1 board in slot 4 of NE4. The E1 services are added to or dropped from the thirteenth to sixteenth ports on the PH1 board in slot 4 of NE1. The E1 services occupy the thirteenth to sixteenth VC-12 timeslots on the ring.
TIP
On a backhaul network for a mobile base station, services are accessed from different nodes and then aggregated to the same node for transmission. In this case, allocate the timeslots on the SNCP radio ring network as follows: 1. Allocate the timeslots to add/drop services on the NEs in anti-clockwise order. Allocate the minimum VC-12 timeslot number to the service on the nearest NE. The number of the timeslot each service occupies does not change on the ring network. 2. Repeat the previous step to configure the timeslots for the services on all the sub-chains. This timeslot allocation method ensures that only the numbers of the timeslots that the services on the nodes of the aggregation sub-chain occupy may change.
TIP
The principles for obtaining the timeslot cross-connection configurations from the SNCP service timeslot allocation diagram are as follows: l A straight line without any dot at either side represents a pass-through service. A straight line with one dot represents an add/drop service. A straight line with an arrow represents a transferred service. The vertical line under the NE name is considered as the reference. l If a straight line representing a pass-through service crosses the vertical line, it indicates that crossconnections are configured between the boards on both sides of the vertical line. The corresponding cross-connected timeslots are marked over the straight line. l If there is a straight line with one dot on one side of the vertical line, it indicates that SNCP crossconnections are configured between the board on this side of the vertical line and the board under the straight line with one dot. The corresponding cross-connected timeslots are marked over the straight line with one dot.
SNCP
Table 14-8 provides the information about SNCP.
Table 14-8 SNCP Parameter Working source Protection source Revertive mode WTR time Hold-off time Switching condition NE1 See the timeslot allocation diagram. See the timeslot allocation diagram. Revertive 600s (default value) 0 (default value) Necessary conditions for an SNCP switching (default values)
NOTE
Unless otherwise specified, WTR Time, Hold-Off Time, and Switching Condition take the default values.

This section describes the process for the data configuration.
Procedure
Step 1 See A.7.2 Creating Cross-Connections for SNCP Services and configure SNCP service crossconnections. l The values for the relevant parameters of NE1 are provided as follows. Parameter Value NE1 Service Type Level Revertive Mode Direction Hold-off Time(100ms) WTR Time(s) Source SNCP VC12 Revertive Bidirectional 0 600 8-IFH2 (working service) 5-IFH2 (protection service) Source Port Source VC4 Source Timeslot Range (e.g.1,3-6)
Issue 05 (2010-10-30)
SNCP VC12 Revertive Bidirectional 0 600 5-IFH2 (working service) 8-IFH2 (protection service) 1 VC4-1 13-16
1 VC4-1 1-12
14-19
Parameter
Value NE1
Sink Sink Port Sink VC4 Sink Timeslot Range(e.g. 1,3-6)
4-PH1 1-12
4-PH1 13-16
l The values for the relevant parameters of NE2 are provided as follows. Parameter Value NE2 Service Type Level Revertive Mode Direction Hold-off Time(100ms) WTR Time(s) Source SNCP VC12 Revertive Bidirectional 0 600 7-IFH2 (working service) 5-IFH2 (protection service) Source Port Source VC4 Source Timeslot Range(e.g.1,3-6) Sink Sink Port Sink VC4 Sink Timeslot Range(e.g.1,3-6) 1 VC4-1 1-8 4-PO1 1-8
l The values for the relevant parameters of NE3 are provided as follows. Parameter Value NE3 Service Type Level SNCP VC12
14-20
Issue 05 (2010-10-30)
Parameter
Value NE3
Revertive Mode Direction Hold-off Time(100ms) WTR Time(s) Source
Revertive Bidirectional 0 600 7-IFH2 (working service) 5-IFH2 (protection service)
Source Port Source VC4 Source Timeslot Range(e.g.1,3-6) Sink Sink Port Sink VC4 Sink Timeslot Range(e.g.1,3-6)
1 VC4-1 9-12 4-PO1 1-4
l The values for the relevant parameters of NE4 are provided as follows. Parameter Value NE4 Service Type Level Revertive Mode Direction Hold-off Time(100ms) WTR Time(s) Source SNCP VC12 Revertive Bidirectional 0 600 5-IFH2 (working service) 8-IFH2 (protection service) Source Port Source VC4 Source Timeslot Range(e.g.1,3-6) Sink Sink Port
Issue 05 (2010-10-30)
1 VC4-1 13-16 4-PO1 -
14-21
Parameter
Value NE4
Sink VC4 Sink Timeslot Range(e.g.1,3-6)
1-4
Step 2 See A.7.1 Creating Cross-Connections of Point-to-Point Services and configure the crossconnections of point-to-point services on NE2, NE3, and NE4. l The values for the relevant parameters of NE2 are provided as follows. Parameter Value NE2 Level Direction Source Source Port Source VC4 Source Timeslot Range(e.g.1,3-6) Sink Sink Port Sink VC4 Sink Timeslot Range(e.g.1,3-6) VC12 Bidirectional 7-IFH2 1 VC4-1 9-16 5-IFH2 1 VC4-1 9-16
l The values for the relevant parameters of NE3 are provided as follows. Parameter Value NE3 Level Direction Source Source Port Source VC4 Source Timeslot Range(e.g.1,3-6) Sink Sink Port
14-22
VC12 Bidirectional 7-IFH2 1 VC4-1 1-8, 13-16 5-IFH2 1

Parameter
Value NE3
Sink VC4 Sink Timeslot Range(e.g.1,3-6)
VC4-1 1-8, 13-16
l The values for the relevant parameters of NE4 are provided as follows. Parameter Value NE4 Level Direction Source Source Port Source VC4 Source Timeslot Range(e.g.1,3-6) Sink Sink Port Sink VC4 Sink Timeslot Range(e.g.1,3-6) VC12 Bidirectional 8-IFH2 1 VC4-1 1-12 5-IFH2 1 VC4-1 1-12
Step 3 See Testing E1 Services Through PRBS and test the E1 services. Test two E1 services on each base station. The test results should show that the E1 services contain no bit errors. ----End

This section provides the hyperlinks of the operation tasks associated with SNCP.
Related Tasks
A.7.1 Creating Cross-Connections of Point-to-Point Services A.7.2 Creating Cross-Connections for SNCP Services A.7.4 Setting the Automatic Switching Conditions of SNCP Services A.7.6 Converting Normal Services into SNCP Services A.7.7 Converting SNCP Services to Normal Services A.7.9 Performing SNCP Protection A.7.10 Querying the Protection Status of SNCP Services
A.7.3 Inserting TU_AIS

When an SNCP switching occurs, the system reports the relevant alarms and abnormal events.
Relevant Alarms
None.
Relevant Events
l SNCP protection switching The abnormal event of SNCP protection switching refers to the performance event that an SNCP protection switching is performed for the services configured with SNCP.
14.12 FAQs
This section provides the answers to the questions that are frequently asked when SNCP is adopted. Q: What switching states does SNCP have? A: SNCP has the following switching states: l l Normal The state when the working SNC and the protection SNC are normal SF The state after the working SNC is automatically switched in the case of a mandatory trigger condition l SD The state after the working SNC is automatically switched in the case of an optional trigger condition l l l l Lockout The state after a lockout switching Forced The state after a forced switching Manual The state after a manual switching WTR The state that exists after the working SNC is restored to normal and before the revertive switching occurs in the revertive mode
14-24
Issue 05 (2010-10-30)
15 Linear MSP
15
About This Chapter
This chapter describes the linear MSP feature. 15.3 Specifications This section describes the specifications of linear MSP.
Linear MSP
15.1 Introduction This section provides the definition of linear MSP and describes its purpose. 15.2 Basic Concepts This section describes the basic concepts associated with linear MSP.
15.4 Reference Standards and Protocols This section describes the standards and protocols associated with the linear MSP feature. 15.5 Availability This section describes the support required by linear MSP and the dependency of the feature. 15.6 Principles 1+1 linear MSP and 1:N linear MSP have different switching principles. 15.7 Planning Guidelines Follow certain guidelines when you plan linear MSP. 15.8 Configuration Procedure To configure a linear MSP service, you need to create a linear MSP group and then create service cross-connections. 15.9 Configuration Example This section uses an example to describe how to plan and configure linear MSP. 15.10 Task Collection This section provides the hyperlinks of the operation tasks associated with linear MSP. 15.11 Relevant Alarms and Events When a linear MSP switching occurs, the SCC board reports associated alarms and abnormal events. 15.12 FAQs
15 Linear MSP
This section provides answers to the questions that are frequently asked when linear MSP is used.
15-2
Issue 05 (2010-10-30)
15 Linear MSP
15.1 Introduction
This section provides the definition of linear MSP and describes its purpose.
Definition
Linear MSP refers to the MS protection function provided in the point-to-point networking. With the MS protection function, signals can be switched from the working span to the protection span between two multiplex section terminations (MSTs). Generally, linear MSP is classified into 1+1 linear MSP and 1:N linear MSP. l 1+1 linear MSP 1+1 linear MSP requires one working channel and one protection channel. Services are transmitted on the working channel and the protection channel is idle. When the working channel becomes unavailable, services are switched to the protection channel for transmission. Figure 15-1 shows the application of 1+1 linear MSP. l Figure 15-1 1+1 linear MSP
NE A Working channel NE B
Protection channel
Protection switching NE A Working channel NE B
Protection channel
1:N linear MSP 1:N linear MSP requires N working channels and one protection channel. Normal services are transmitted on the working channel, and extra services are transmitted on the protection channel. When a working channel becomes unavailable, the services on this channel are switched to the protection channel for transmission. As a result, extra services are interrupted. Figure 15-2 shows the application of 1:N linear MSP.
Issue 05 (2010-10-30)
15-3
15 Linear MSP
Figure 15-2 1:N linear MSP

NE A Normal service 1 Working channel 1 NE B Normal service1
...
...
Protection switching NE A Normal service 1 Working channel 1 NE B Normal service1
...
...
Purpose
Linear MSP improves the reliability of optical transmission lines in chain networking.
15.2 Basic Concepts

This section describes the basic concepts associated with linear MSP. 15.2.1 Protection Type Linear MSP can be classified by protection mechanism, switching mode, and revertive mode. 15.2.2 Meanings of K Bytes The linear MSP protocol uses the K1 and K2 bytes in multiplex section overheads to transfer switching requests. 15.2.3 Switching Conditions The linear MSP can be triggered by local SF conditions, local SD conditions, and local external switching requests. In dual-ended mode, the local NE can perform switching according to the K bytes from the opposite NE. 15.2.4 Switching Impact Services are interrupted within the linear MSP switching time (< 50 ms). After a 1:N linear MSP switching occurs, extra services are interrupted. After a revertive switching occurs, extra services are restored.
15 Linear MSP

Linear MSP can be classified by protection mechanism, switching mode, and revertive mode. With regard to the protection mechanism, linear MSP is classified into dedicated protection and shared protection. l Dedicated protection In the case of dedicated protection, one working channel exclusively uses one protection channel. The dedicated protection channel cannot carry extra services. 1+1 protection is dedicated protection. l Shared protection In the case of shared protection, one or more working channels share one protection channel. The shared protection channel can carry extra services. 1:N (including 1:1) protection is shared protection. With regard to the switching mode, the linear MSP is classified into single-ended switching and dual-ended switching. l Single-ended switching In single-ended switching mode, a switching occurs only at one end and the state of the other end remains unchanged. l Dual-ended switching In dual-ended switching mode, a switching occurs at both ends at the same time. With regard to the revertive mode, linear MSP is classified into the revertive mode and the nonrevertive 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 former working channel is restored to normal for a certain period. The period after the former working channel is restored to normal and before the NE releases the switching is called the WTR time. To prevent frequent switching events due to an unstable working channel, it is recommended that you set WTR time to 5 to 12 minutes. l Non-revertive mode When an NE is in the switching state, the NE maintains the current state unless another switching event occurs, even though the former working channel is restored to normal. Therefore, linear MSP is classified into the following eight modes: l l l l l l l l
Issue 05 (2010-10-30)
1+1 dual-ended revertive mode 1+1 dual-ended non-revertive mode 1+1 single-ended revertive mode 1+1 single-ended non-revertive mode 1:N dual-ended revertive mode 1:N dual-ended non-revertive mode 1:N single-ended revertive mode 1:N single-ended non-revertive mode
15 Linear MSP
15.2.2 Meanings of K Bytes

The linear MSP protocol uses the K1 and K2 bytes in multiplex section overheads to transfer switching requests. Table 15-1 Meanings of K bytes (linear MSP) K Byte K1 (bit 1 to bit 4) Meaning The four bits carry the bridge request code. Table 15-2 provides the meanings of the four bits. The four bits indicate the number of the service signal to which the bridge request corresponds. 0 represents the null signal, 1-14 represent normal service signals, and 15 represents the extra service signal (applicable only to 1:N linear MSP). The four bits carry the number of the service signal that bridges the local end and the channel. The value range of the four bits is the same as the four bits (bit 5 to bit 8) of K1. This bit indicates the protection mode. 1 represents the 1:N mode. 0 represents the 1+1 mode. The three bits carry the status signal. 000 represents the idle state, 111 represents the MS_AIS state, and 110 represents the MS_RDI state.a
K1 (bit 5 to bit 8)
K2 (bit 1 to 4)
K2 (bit 5)
K2 (bit 6 to bit 8)
NOTE
a: In certain applications, when the MS_RDI or MS_AIS alarm is not reported, K2 (bit 6 to bit 8) indicates switching modes. That is, 100 indicates the single-ended mode, and 101 indicates the dual-ended mode.
Table 15-2 Bridge request code Bit 1 1 Bit 2 1 Bit 3 1 Bit 4 1 Meaning Lockout of protection channel Forced switching Failure of highpriority signals
1 1
1 1
1 0
0 1
15-6
Issue 05 (2010-10-30)
15 Linear MSP
Bit 1 1 1
Bit 2 1 0
Bit 3 0 1
Bit 4 0 1
Meaning Failure of low priority signals Degradation of high priority signals Degradation of low priority signals Unused Manual switching Unused WTR Unused Exercise switching Unused Reverse request Non-revertive No request
1 1 0 0 0 0 0 0 0 0
0 0 1 1 1 1 0 0 0 0
0 0 1 1 0 0 1 1 0 0
1 0 1 0 1 0 1 0 1 0
NOTE
l A reverse request assumes the priority of the bridge request to which it is responding. l By default, the OptiX RTN 620 uses 1101 (failure of high priority signals) and 1011 (degradation of high priority signals) as an SF/SD switching request.

The linear MSP can be triggered by local SF conditions, local SD conditions, and local external switching requests. In dual-ended mode, the local NE can perform switching according to the K bytes from the opposite NE.
Issue 05 (2010-10-30)
15-7
15 Linear MSP
Table 15-3 Trigger conditions of a linear MSP switching Switching Condition Lockout of protection channel (external switching) Priority From top to bottom, the priority is from the highest to the lowest. Description The lockout of protection channel blocks normal service signals from entering the protection channel but does not block service signals from being switched from the protection channel to the working channel. The signal failure condition on the protection channel is equivalent to the lockout of protection channel. Service signals on the working channel are forcibly switched to the protection channel or service signals on the protection channel are switched to the working channel. If the switching is in the lockout or forced switching state, or if the SF condition exists on the protection channel, no switching occurs. The SF condition on the working channel enables service signals to be switched to the protection channel. If the switching is in the lockout or forced switching state, or if the SF condition exists on the protection channel, no switching occurs. When there is the R_LOC, R_LOF, R_LOS, MS_AIS, or B2_EXC alarm on the working channel, an SF switching is triggered.
Signal failure (SF)
15-8
Issue 05 (2010-10-30)
15 Linear MSP
Switching Condition Signal degradation (SD)
Priority
Description The SD condition on the working channel enables service signals to be switched to the protection channel. If the switching is in the lockout or forced switching state, or if the SF condition exists on the protection channel, no switching occurs. When there is the B2_SD alarm on the working channel, an SD switching is triggered. If the switching is in the lockout or forced switching state, or if the SF condition exists on the protection channel, no switching occurs. Otherwise, services are switched from the working channel to the protection channel or from the protection channel to the working channel according to the command. The switching then enters the manual switching state. After service signals are switched to the protection channel due to the SF/SD condition on the working channel and the working channel is already restored to normal for the WTR time, a revertive switching occurs. After the former active equipment is restored to normal and before a revertive switching occurs, the switching is in the WTR state. After the revertive switching, the switching changes to the normal state. Service signals are not actually switched. An exercise switching is used only to check whether an NE can normally run the MSP protocol.
Exercise switching (external switching)
Issue 05 (2010-10-30)
15-9
15 Linear MSP
NOTE
l SD is an optional switching condition. You can specify on the NMS whether SD is used as a switching condition. By default, SD is used as a switching condition. l If two switching conditions exist on a channel at the same time, the switching condition of a higher priority preempts the channel. l In addition to the external switching commands provided in the preceding table, external switching commands include the clear switching command. The clear switching command is issued to clear a lockout, forced switching, manual switching, or exercise switching. l If an NE needs to perform a switching according to the K bytes from the opposite NE, the NE determines switching priorities according to the bridge request code contained in the K bytes. For the meanings of the K bytes, see 15.2.2 Meanings of K Bytes. l If the working channels with the same switching priority request a switching at the same time, the working channel with a smaller number has a higher priority and thus preempts the protection channel. l If the protection channel is occupied already, the protection channel is preempted by a working channel with the same switching priority but a smaller number.

Services are interrupted within the linear MSP switching time (< 50 ms). After a 1:N linear MSP switching occurs, extra services are interrupted. After a revertive switching occurs, extra services are restored.
15.3 Specifications
This section describes the specifications of linear MSP. Table 15-4 lists the specifications of linear MSP. Table 15-4 Specifications of linear MSP Item Maximum number of linear MSP groups Specification One group of STM-4 linear MSP Five groups of STM-1 optical/electrical linear MSP Service type of linear MSP Protection type of linear MSP STM-4/STM-1 optical transmission link 1+1 dual-ended revertive mode 1+1 dual-ended non-revertive mode 1+1 single-ended revertive mode 1+1 single-ended non-revertive mode 1:N (N3) dual-ended revertive mode WTR time 5-12 minutes
15-10
Issue 05 (2010-10-30)
15 Linear MSP
Item MSP protocol
Specification New protocol Restructure protocol

NOTE Huawei adopts two MSP protocols, the new protocol and the restructure protocol. The new protocol is more reliable and the restructure protocol has a better compliance with standards.
SD/SF priority protection flag Switching mode indication Switching time
Supported Supported < 50 ms

This section describes the standards and protocols associated with the linear MSP feature. The following protocol is associated with linear MSP: l ITU-T G.841 Types and characteristics of SDH network protection architectures
15.5 Availability
This section describes the support required by linear MSP and the dependency of the feature.

Feature LMSP Applicable Board SL1/SD1 SLE/SDE SL4 Applicable Hardware Version All the versions All the versions All the versions Applicable Product Version V100R001 and later V100R001 and later V100R002 and later
Feature Dependency
l l A line configured with linear MSP can work only as the service sink of an SNCP service pair, rather than the working source or protection source. A line configured with linear MSP cannot be a part of an MSP ring.
15.6 Principles
1+1 linear MSP and 1:N linear MSP have different switching principles. 15.6.1 1+1 Linear MSP
15 Linear MSP
1+1 linear MSP adopts the dual fed and selective receiving mechanism to perform a switching. 15.6.2 1:N Linear MSP 1:N linear MSP adopts the automatic bridge mechanism to perform a switching.
15.6.1 1+1 Linear MSP

1+1 linear MSP adopts the dual fed and selective receiving mechanism to perform a switching.
NOTE
The following part uses a switching triggered by the signal failure on the working channel as an example to describe the switching principle of 1+1 linear MSP.
Figure 15-3 Working principle of 1+1 linear MSP (before a switching)

NE B Working NE A
Protection Working
Protection Normal service
Figure 15-4 Working principle of 1+1 linear MSP (after a switching, in single-ended mode)
NE B Working NE A
Protection Working
15-12
Issue 05 (2010-10-30)
15 Linear MSP
Figure 15-5 Working principle of 1+1 linear MSP (after a switching, in dual-ended mode)
NE B Working NE A
Protection Working
When the signal on the working channel fails, the switching principle in single-ended mode is described as follows: 1. 2. 3. Before a switching, the source sends service signals to the working channel and the protection channel. The sink receives the service signal from the working channel. When the line board at the sink in a certain direction (NE A) detects that the signal on the working channel fails, the line board reports the event to the SCC board. After the SCC board confirms that the signal on the working channel fails and the protection channel is normal, the SCC board enables the cross-connect board to complete the crossconnection between the protection channel and the service sink.
When the signal on the working channel fails, the switching principle in dual-ended mode is described as follows: 1. 2. Before a switching, the source sends service signals to the working channel and the protection channel. The sink receives the service signal from the working channel. When the sink in a certain direction (NE A) detects that the signal on the working channel fails, NE A sends the K bytes to the source (NE B) on the protection channel (the request type is "signal failure"). NE B sends the K bytes to NE A on the protection channel (the request type is "reverse request"). NE A receives the service signal from the protection channel. NE B receives the service signal from the protection channel.
3. 4. 5.
15.6.2 1:N Linear MSP

1:N linear MSP adopts the automatic bridge mechanism to perform a switching.
NOTE
The following part uses a 1:1 linear MSP switching triggered by the signal failure on the working channel as an example to describe the switching principle of 1:N linear MSP.
Issue 05 (2010-10-30)
15-13
15 Linear MSP
Figure 15-6 Working principle of 1:1 linear MSP (before a switching)

NE B Working NE A
Protection Working
Protection Normal service Extra service
Figure 15-7 Working principle of 1:1 linear MSP (after a switching)

NE B Working NE A
Protection Working
Protection Normal service Extra service
When the signal on the working channel fails, the switching principle in 1:1 mode is described as follows: 1. 2. Before a switching, the source and the sink send and receive normal service signals on the working channel, and send and receive extra service signals on the protection channel. When the sink in a certain direction (NE A) detects that the signal on the working channel fails, NE A sends the K bytes to the source (NE B) on the protection channel (the request type is "signal failure"). NE B performs a bridge of the normal service signals onto the protection channel and sends the K bytes to NE A on the protection channel (the request type is "reverse request"). NE A receives the normal service signals from the protection channel and performs a bridge of the normal service signals onto the protection channel. NE B receives the normal service signals from the protection channel.
3. 4. 5.

Follow certain guidelines when you plan linear MSP.
15 Linear MSP
Planning Guidelines of Protection Types

It is recommended that you select the 1+1 single-ended non-revertive mode or the 1:N dualended revertive mode as required. l In 1+1 single-ended non-revertive mode, a switching is performed in a simple manner and the switching time is very brief. In addition, the NEs at both sides need not be interconnected. In 1:N dual-ended revertive mode, extra services can be transmitted.
Planning Guidelines on Protection Configuration Parameters

l l The MS protocols used at both ends must be consistent. It is recommended that you apply the new protocol when both ends use the OptiX equipment. It is recommended that you use the line ports on one line board for the working channel and those on another line board for the protection channel. In this manner, you can prevent the protection failure when one line board becomes faulty. If the protection is in the revertive mode, set the WTR time to a value from 5 to 12 minutes. It is recommended that you set the WTR time to a default value, namely, ten minutes. It is recommended that you set SD as a switching condition.
l l

To configure a linear MSP service, you need to create a linear MSP group and then create service cross-connections. Table 15-5 Configuration procedure for a linear MSP service Step 1 Operation A.6.1 Configuring Ring MSP Description Required when linear MSP is configured for optical transmission lines. The parameters need to be set according to the service planning. 2 A.7.1 Creating Cross-Connections of Point-to-Point Services Required when the service is a pointto-point service. The parameters need to be set according to the service planning.

This section uses an example to describe how to plan and configure linear MSP. 15.9.1 Networking Diagram The section describes the networking information about NEs. 15.9.2 Service Planning
15 Linear MSP
Service planning information contains all the parameter information required for configuring NE data. 15.9.3 Configuration Process This section describes the procedure of data configuration.

The section describes the networking information about NEs. As shown in Figure 15-8, the relative networking information is as follows: l l To ensure the transmission of the services between NE1 and NE3, linear MSP is configured for the optical transmission lines between NE1 and NE3. NE1 transmits the first 16 E1s of an STM-1 signal to NE2.
Figure 15-8 Networking diagram of linear MSP

16E1 STM-1
NE2
NE1 4-SD1-1 4-SD1-2 5-IFH2
NE3

Service planning information contains all the parameter information required for configuring NE data.
Timeslot Allocation Diagram

Cross-connections are set up for the 16 E1 services from 4-SD1-1 on NE1 to 5-IFH2 on NE2.
NOTE
In this example, only the configuration information about NE1 is provided.
Linear MSP
In this configuration example, no extra services need to be transmitted. Therefore, the singleended non-revertive 1+1 linear MSP is configured to protect the optical transmission lines between NE1 and BSC. Table 15-6 provides the related planning information. Table 15-6 Linear MSP Parameter Protection Type Switching Mode
15-16
NE1 1+1 Linear MSP Single-Ended Switching

Issue 05 (2010-10-30)
15 Linear MSP
Parameter Revertive Mode SD Enable Protocol Type West Working Unit West Protection Unit
NE1 Non-Revertive Enabled (default value) New Protocol (default value) 4-SD1-1 4-SD1-2
NOTE
Unless otherwise specified, SD Enable and Protocol Type take default values.

Procedure
Step 1 See A.6.2 Configuring Linear MSP and create linear MSP. The values for the related parameters are provided as follows. Parameter Value Range NE1 Protection Type Switching Mode Revertive Mode WTR Time(s) SD enable Slot Mapping Relation 1+1 Linear MSP Single-Ended Switching Non-Revertive 600 Enabled l West Working Unit: 4-SD1-1 l West Working Unit: 4-SD1-2
Step 2 See A.7.1 Creating Cross-Connections of Point-to-Point Services and create the crossconnections of point-to-point services. The values for the relevant parameters of NE1 are provided as follows. Parameter Value NE1 Level
Issue 05 (2010-10-30)
VC-12
15 Linear MSP
Parameter
Value NE1
Direction Source Source VC4 Source Timeslot Range(e.g.1,3-6) Sink Sink VC4 Sink Timeslot Range(e.g.1,3-6)
Bidirectional 4-SD1-1 VC4-1 1-16 5-IFH2-1 VC4-1 1-16
Step 3 See Testing E1 Services Through PRBS and perform a PRBS test. Test two E1 services on each base station. The test results should show that the E1 services contain no bit errors. ----End

This section provides the hyperlinks of the operation tasks associated with linear MSP.
Related Tasks
A.6.2 Configuring Linear MSP A.7.1 Creating Cross-Connections of Point-to-Point Services A.6.4 Querying the Status of Linear MSP A.6.6 Performing Linear MSP Switching A.6.8 Starting/Stopping the Linear MSP Protocol

When a linear MSP switching occurs, the SCC board reports associated alarms and abnormal events.
Relevant Alarms
l l l APS_INDI The APS_INDI alarm indicates that a protection switching occurs. APS_FAIL The APS_FAIL alarm indicates that the protection switching fails. APS_MANUAL_STOP The APS_MANU_STOP alarm indicates that the MSP protocol is manually stopped.
15 Linear MSP
K1_K2_M The K1_K2_M alarm indicates that there is a mismatch between byte K1 and byte K2. If the signal channel indicated by the transmitted K1 (bit 5 to bit 8) is different from the signal channel indicated by the received K2 (bit 1 to bit 4), the SCC board reports the K1_K2_M alarm.
K2_M The K2_M alarm indicates a mismatch of byte K2. When the protection type indicated by the received K2 (bit 5) is different from the protection type used by the NE, the SCC board reports the K2_M alarm.
LPS_UNI_BI_M The LPS_UNI_BI_M alarm indicates a mismatch of the single-ended/dual-ended mode of linear MSP. When the K2 (bit 6 to bit 8) is enabled to indicate the single-ended/dual-ended mode, if the received K2 byte indicates a mode different from the mode used by the NE, the SCC board reports the LPS_UNI_BI_M alarm. This alarm applies only to the restructure protocol.

l l Linear MSP protection switching This abnormal event indicates that a linear MSP switching occurs. No response from the linear MSP remote end This abnormal event indicates that the remote end does not respond to the linear MSP switching request by the local end.
15.12 FAQs
This section provides answers to the questions that are frequently asked when linear MSP is used. Q: What switching states does linear MSP have? A: The linear MSP has the following switching states: l l l l l l l
Issue 05 (2010-10-30)
Protocol is not started The state when the linear MSP protocol is not started Protocol starting The state when the linear MSP protocol is starting Protocol normal The normal state after the linear MSP protocol is started Lockout The state after the protection channel is locked out Forced The state after a forced switching Manual The state after a manual switching Exercise
15 Linear MSP
The state after an exercise switching l l l Signal failure The state after an SF switching Signal degrade The state after an SD switching WTR The state that exists from the time the working equipment is restored to normal after an automatic switching until the time the revertive switching occurs in revertive mode Q: What should be noted in the case of linear MSP, when the OptiX equipment is interconnected with the third-party equipment? A: Note the following points: l Select the 1+1 single-ended non-revertive mode if possible. In this case, if an interconnection problem occurs, it is generally because the third-party equipment has special requirements for byte K. The 1+1 single-ended mode of certain vendors (for example, company S and company E) is actually the dual-ended mode. In this case, select the 1+1 dual-ended protection mode. ITU-T G.841 defines two priority levels for the SF and SD indications on byte K. By default, the OptiX equipment uses the SF and SD indications with the higher priority. If the thirdparty equipment uses the SF and SD indications of the lower priority, modify the configuration accordingly on the OptiX equipment. Check whether the third-party equipment uses the last three bits of byte K2 to indicate the single-ended/dual-ended mode. If yes, modify the configuration accordingly on the OptiX equipment.
l l
Q: Why cannot a forced switching be performed when the signal on the protection channel fails? A: After the signal on the protection channel fails, the protection channel is locked out. The lockout of the protection channel has a higher priority than a forced switching. Therefore, no forced switching can be performed. Q: Why are services interrupted after a 1+1 unidirectional linear MSP switching? A: During the configuration of 1+1 linear MSP on the NMS, the unidirectional cross-connection between the service source and the protection channel is not configured. Q: How to handle the failure of a linear MSP switching? A: Do as follows: 1. Check the configuration of linear MSP, especially the node ID of each NE. The configured node IDs of NEs must meet the requirements of the network topology. The node ID of each NE must be unique. 2. Check the protection channels. If an alarm is generated on the protection channel, rectify the fault according to the alarm.
16 Two-Fiber Bidirectional Ring MSP
16
Two-Fiber Bidirectional Ring MSP
About This Chapter

This chapter describes the two-fiber bidirectional ring MSP feature. 16.1 Introduction This section provides the definition of two-fiber bidirectional ring MSP and describes its purpose. 16.2 Basic Concepts This section describes the basic concepts that you should be familiar with before using two-fiber bidirectional ring MSP. 16.3 Specifications This section describes the specifications of two-fiber bidirectional ring MSP. 16.4 Reference Standards and Protocols This section describes the standards and protocols associated with two-fiber bidirectional ring MSP. 16.5 Availability This section describes the support required by the application of the two-fiber bidirectional ring MSP feature and its dependency. 16.6 Principles Two-fiber bidirectional ring MSP uses the automatic bridging mechanism between working channels and protection channels to implement switching. 16.7 Planning Guidelines Follow certain rules when you plan two-fiber directional ring MSP. 16.8 Configuration Procedure To configure a ring MSP service, you need to create a ring MSP protection group and then create service cross-connections. 16.9 Configuration Example This section uses an example to describe how to plan and configure ring MSP according to network conditions. 16.10 Task Collection
This section provides the hyperlinks of the operation tasks associated with two-fiber bidirectional ring MSP. 16.11 Relevant Alarms and Events When a two-fiber bidirectional ring MSP switching occurs, the NE reports relevant alarms and abnormal events. 16.12 FAQs This section provides the answers to the questions that are frequently raised when two-fiber bidirectional ring MSP is used.
16-2
Issue 05 (2010-10-30)
16.1 Introduction
This section provides the definition of two-fiber bidirectional ring MSP and describes its purpose.
Definition
Two-fiber bidirectional ring MSP provides protection for multiplex sections on a two-fiber bidirectional ring. With the multiplex section protection function, signals can be switched from the working section to the protection section between two multiplex section terminations (MSTs). On a two-fiber bidirectional MSP ring, the first half of VC-4s on each STM-N line is the working channel, and the other half of VC-4s is the protection channel. In normal cases, services are transmitted in the working channel. The services transmitted on two fibers flow in inverse directions. When a fiber cut occurs and the working channel becomes unavailable, the services at both ends of the fault are both switched from the working channel of the faulty fiber to the protection channel of the reverse directional fiber. Figure 16-1 shows application of a two-fiber bidirectional MSP ring.
Issue 05 (2010-10-30)
16-3
Figure 16-1 Two-fiber bidirectional MSP ring

NE A East West
West NE B East
STMtwo-fiber 4 bidirectional MSP ring
East NE D West
West NE C
East
Protection swicthing
NE A East West
West NE B East STM-4 two-fiber bidirectional MSP ring
East NE D West
West NE C
East
Service between NE A and NE C
Objective
A two-fiber bidirectional MSP ring has higher transmission reliability. It is applicable to transmission of distributed services. In the case of aggregated services, the highest service capacity of a ring network is STM-N/2; in the case of distributed services, the highest service capacity of a ring network is M x STM-N/2 (M represents the number of nodes on the ring network).
16.2 Basic Concepts

This section describes the basic concepts that you should be familiar with before using two-fiber bidirectional ring MSP. 16.2.1 Protection Type Two-fiber bidirectional ring MSP is the most widely used MSP type.
16.2.2 Meanings of Byte K The two-fiber bidirectional ring MSP protocol uses the K1 and K2 bytes in the multiplex section overhead to transmit switching requests. 16.2.3 Switching Conditions Two-fiber bidirectional ring MSP can be triggered by local SF conditions, local SD conditions, local external switching requests, and byte K sent from the node on another ring network. 16.2.4 Switching Impact Within the MSP switching time (shorter than 50 ms), services are interrupted. Extra traffic is interrupted within the period from the time normal services are switched to the protection channel to the time the services are restored to the working channel.

Two-fiber bidirectional ring MSP is the most widely used MSP type. Two-fiber bidirectional ring MSP has the following characteristics in terms of protection type: l l l A ring network uses two fibers. One fiber is used to receive signals and the other fiber is used to transmit signals. Services are received and transmitted on the same route. Normal traffic between different nodes share the protection path, and the protection path can be used to transmit extra traffic. On a two-fiber bidirectional MSP ring, the first half of the VC-4s is the working channel and the second half of the VC-4s is the protection channel. Two-fiber bidirectional ring MSP adopts the revertive mode. That is, after the working channel is restored to normal and this state lasts for a certain period, the NE releases the switching state and is switched back to the normal state. The period from the time the former working channel is restored to normal to the time the NE releases the switching state is called the WTR time. To prevent frequent switching events due to an unstable working channel, it is recommended that you set the WTR time to five to twelve minutes.
16.2.2 Meanings of Byte K

The two-fiber bidirectional ring MSP protocol uses the K1 and K2 bytes in the multiplex section overhead to transmit switching requests. Table 16-1 Meanings of byte K (two-fiber bidirectional ring MSP) Byte K K1 (bits 1 to 4) Meaning The four bits carry the bridging request code. Table 16-2 provides the meanings of the four bits. The four bits carry the ID of the destination node. The four bits carry the ID of the source node. 1 represents the long way and 0 represents the short way.
K1 (bits 5 to 8) K2 (bits 1 to 4) K2 (bit 5)
Issue 05 (2010-10-30)
16-5
Byte K K2 (bits 6 to 8)
Meaning The three bits carry the status. 000 represents the idle state, 111 represents the MS_AIS state, 110 represents the MS_RDI state, 011 represents that extra traffic exists, 010 represents bridging and switching, and 001 represents bridging.a
NOTE
a: "Bridging" means that the equipment transmits the services on the east (or west) protection channels. "Switching" means that the equipment receives the services on the east (or west) protection channels.
Table 16-2 Bridging request code Bit 1 1 Bit 2 1 Bit 3 0 Bit 4 1 Meaning Forced switching_ring (FS_R) Signal fail_ring (SF_R) Signal degrade_ring (SD_R) Manual switching_ring (MS_R) WTR Exercise switching_ring (EXER_R) Reverse request_ring (RR_R) No request
1 1
0 0
1 0
1 0
0 0
1 0
0 1
1 1
NOTE
l A reverse request assumes the priority of bridging request to which it responds. l The other values of bridging request code are used in the case of four-fiber MSP ring, and therefore, are not described here.
16-6
Issue 05 (2010-10-30)

Two-fiber bidirectional ring MSP can be triggered by local SF conditions, local SD conditions, local external switching requests, and byte K sent from the node on another ring network. Table 16-3 Switching conditions of two-fiber bidirectional ring MSP Switching Condition Lockout of protection channel (external switching) Priority From top to bottom. The priority is from the high to low. Description The lockout of protection channel blocks normal service signals from entering the protection channel but does not block service signals from being switched from the protection channel to the working channel. The signal failure condition on the protection channel is equivalent to the lockout of protection channel. Service signals on the working channel are forcibly switched to the protection channel or service signals on the protection channel are switched to the working channel. If the switching is in the lockout or forced switching state, or if the SF condition exists on the protection channel, no switching occurs. The SF condition on the working channel enables service signals to be switched to the protection channel. If the switching is in the lockout or forced switching state, or if the SF condition exists on the protection channel, no switching occurs. When there is an R_LOC, R_LOF, R_LOS, MS_AIS, or B2_EXC alarm on the working channel, SF switching is triggered.
Signal failure (SF)
Issue 05 (2010-10-30)
16-7
Switching Condition Signal degradation (SD)
Priority
Description The SD condition on the working channel enables service signals to be switched to the protection channel. If the switching is in the lockout or forced switching state, or if the SF condition exists on the protection channel, no switching occurs. When there is a B2_SD alarm on the working channel, SD switching is triggered. If the switching is in the lockout or forced switching state, or if the SF condition exists on the protection channel, no switching occurs. Otherwise, services are switched from the working channel to the protection channel or from the protection channel to the working channel according to the command. Then, the switching enters manual switching state. After service signals are switched to the protection channel due to the SF/SD condition on the working channel and the working channel is already restored to normal, the revertive switching occurs when the WTR time expires. Within the period from the time the former active equipment is restored to normal to the time the revertive switching occurs, the switching is in the WTR state. After the revertive switching, the switching enters the normal state.
16-8
Issue 05 (2010-10-30)
Switching Condition Exercise switching (external switching)
Priority
Description Service signals are not actually switched. The exercise functionality is used only to check whether an NE can normally run the MSP protocol.
NOTE
l The SD condition is an optional switching condition. You can specify on the NMS whether the SD condition is used as a switching condition. By default, the SD condition is used as a switching condition. l If two switching conditions exist on a channel at the same time, the switching condition with a higher priority preempts the channel. l External switching commands include the switching clear commands, such as the clear lockout command, clear forced switching command, clear manual switching command, clear exercise switching command, clear WTR state command, and clear all command. The clear WTR state command is used to end the current WTR state of an NE and to immediately switch services to the working channel. The clear all command is used to clear all switching actions triggered by external switching commands and to clear the WTR state. l If an NE needs to perform switching according to byte K sent from another node, the NE determines the switching priority based on the bridge request code contained in byte K. For the meanings of byte K, see 16.2.2 Meanings of Byte K.

Within the MSP switching time (shorter than 50 ms), services are interrupted. Extra traffic is interrupted within the period from the time normal services are switched to the protection channel to the time the services are restored to the working channel.
16.3 Specifications
This section describes the specifications of two-fiber bidirectional ring MSP. Table 16-4 lists the specifications of two-fiber bidirectional ring MSP. Table 16-4 Specifications of two-fiber bidirectional ring MSP Item Maximum group number of two-fiber bidirectional ring MSP Link type of two-fiber bidirectional ring MSP WTR time Switching time Specifications One group STM-4 optical transmission link 5-12 minutes < 50 ms
Issue 05 (2010-10-30)
16-9

This section describes the standards and protocols associated with two-fiber bidirectional ring MSP. The following protocol is associated with two-fiber bidirectional ring MSP: l ITU-T G.841: Types and characteristics of SDH network protection architectures
16.5 Availability
This section describes the support required by the application of the two-fiber bidirectional ring MSP feature and its dependency.

Table 16-5 Hardware and version support Feature Two-fiber bidirectional MSP ring Applicable Board SL4 Applicable Hardware Version All the versions Applicable Product Version V100R002 and later
Feature Dependency
l l The line of a two-fiber bidirectional MSP ring cannot be configured with linear MSP. The line of a two-fiber bidirectional MSP ring can work only as the sink of an SNCP service pair, and cannot work as the working source or protection source.
16.6 Principles
Two-fiber bidirectional ring MSP uses the automatic bridging mechanism between working channels and protection channels to implement switching.
NOTE
The following section describes the switching principle of two-fiber bidirectional ring MSP. The protection switching triggered by a unidirectional signal failure on a two-fiber bidirectional MSP ring formed by four NEs is provided as an example.
16-10
Issue 05 (2010-10-30)
Figure 16-2 Principle of a two-fiber bidirectional MSP ring (before switching)

NE A #1 VC-4 East West
West NE B East STM-4 two-fiber bidirectional MSP ring
East NE D West
West NE C
East Service between NE A and NE C
Figure 16-3 Principle of a two-fiber bidirectional MSP ring (after switching)

NE A East West
West NE B East
#3VC-4 STM-4 two-fiber bidirectional MSP ring #3 VC-4
East NE D West
#1 VC-4
West NE C
East
Service from NE A to NE C
When signals on the working channel fail, switching on the two-fiber bidirectional MSP ring is implemented as follows: 1. When the network is in the normal state, the services between NE A and NE C are transmitted in certain timeslots of the first VC-4 on the line. Figure 16-2 shows the signal flow of the services. When the west line board of NE B detects that the signals on the working channel in the receive direction fail, NE B sends byte K (the request type is SF_R and the state is MSRDI) in the short way (NE B->NE A) and also sends byte K (the request type is SF_R and the state is idle) in the long way (NE B->NE C->NE D->NE A). When receiving byte K that is sent from NE B to NE A, NE C and NE D transparently transmit the received byte K. When the east line board of NE A receives byte K in the short way, NE A sends byte K (the request type is RR_R and the state is idle) in the short way (NE A->NE B) and also
2.
3. 4.
Issue 05 (2010-10-30)
sends byte K (the request type is SF_R and the state is idle) in the long way (NE A->NE D->NE C->NE B). 5. When the west line board of NE A receives byte K in the long way, NE A sends byte K (the request type is RR_R and the state is bridging and switching) in the short way (NE A>NE B) and also sends byte K (the request type is SF_R and the state is bridging and switching) in the long way (NE A->NE D->NE C->NE B). NE A enters the east switching state. That is, NE A receives a service that is received from the east working channel from the west protection channel, and transmits a service that is transmitted to the east working channel to the west protection channel. In the case of a service between NE A and NE C, NE A in the normal state transmits the service to the first VC-4 channel in the east direction, but in the east switching state transmits the service to the third VC-4 channel in the west direction. 6. When receiving byte K (the request type is SF_R and the state is bridging and switching) that is sent from NE A to NE B, NE C and NE D enter the pass-through state. When NE C and NE D pass through byte K, NE C and NE D also pass through the information carried in the protection channel. When receiving byte K (the request type is SF_R and the state is bridging and switching) that are sent from NE A, NE B sends byte K (the request type is SF_R and the state is bridging and switching) in the long way (NE B->NE C->NE D->NE A). NE B enters the west switching state. That is, NE B receives a service that is received from the west working channel from the east protection channel, and transmits a service that is transmitted to the west working channel to the east protection channel. In the case of a service between NE A and NE C, NE B in the normal state receives the service from the first VC-4 channel in the west direction and transmits a service to the first VC-4 channel in the east direction, but in the west switching state receives a service from the third VC-4 channel in the east direction and transmits a service to the first VC-4 channel in the east direction.
7.

Follow certain rules when you plan two-fiber directional ring MSP.
Planning Guidelines on Node IDs

l l The number of NE nodes must not exceed 16. The value range of a node ID is from 0 to 15. In the case of a new ring network, it is recommended that you set the node ID of the central station to 0 and allocate node IDs to the other NEs counterclockwise. Ensure that the node ID of an NE is one more than the node ID of its previous NE. If you add an NE to an existing ring network, it is recommended that you set the node ID of the new NE to the number that is one less than the maximum number of the nodes (including the new NE) on the ring network.
Planning Guidelines on the Protection Configuration Parameters

l The MSP protocols used on a ring network must be consistent. It is recommended that you adopt the new protocol.
16-12
l l
Set the WTR time to a range from five minutes to twelve minutes. It is recommended that you set the value to ten minutes. It is recommended that you set SD as a switching condition.

To configure a ring MSP service, you need to create a ring MSP protection group and then create service cross-connections. Table 16-6 Configuration procedure for a ring MSP service Step 1 Operation A.6.1 Configuring Ring MSP Remarks Required when the optical transmission line is configured with ring MSP. You need to set the parameters according to the service planning. 2 A.7.1 Creating Cross-Connections of Point-to-Point Services Required when the service is a pointto-point service. You need to set the parameters according to the service planning.

This section uses an example to describe how to plan and configure ring MSP according to network conditions. 16.9.1 Networking Diagram The section describes the networking information about NEs. 16.9.2 Service Planning The service planning information contains all the parameters required for configuring the NE data. 16.9.3 Configuration Process This section describes the process of configuring service data.

The section describes the networking information about NEs. As shown in Figure 16-4, one OptiX RTN 620 (NE4) and three OptiX transmission devices form a two-fiber bidirectional MSP ring. NE4 transmits 16xE1 services between NE1 and NE5.
Issue 05 (2010-10-30)
16-13
Figure 16-4 Two-fiber bidirectional MSP ring
IF board: 7-IFH2 West line: 6-SL4 East line: 8-SL4 NE 1 NE 2 16E1 MSP ring NE 4 NE 5 NE 3

Planning Service Timeslots

On the ring network, the services from NE1 to NE5 occupy the first to sixteenth VC-12 timeslots of the first VC-4 on the east line board on NE4. On the radio link, the services from NE1 to NE5 occupy the first to sixteenth VC-12 timeslots on the IF board on NE4.
Information About Ring MSP

Table 16-7 provides the information about ring MSP. Table 16-7 Information about ring MSP Parameter WTR time (s) SD enable Protocol type West line 1 East line 1 NE4 600 Enabled New protocol 6-SL4-1 8-SL4-1

This section describes the process of configuring service data.
Procedure
Step 1 A.6.1 Configuring Ring MSP. The following table provides the values of parameters. Parameter Value NE4 Local Node West Node East Node WTR Time(s) SD enable Slot Mapping Relation 4 3 5 600 Enabled l West line 1: 6-SL4-1 l East line 1: 8-SL4-1
Step 2 A.7.1 Creating Cross-Connections of Point-to-Point Services . The following table provides values of parameters. Parameter Value NE4 Level Direction Source Source VC4 Source Timeslot Range(e.g.1,3-6) Sink Sink VC4 Sink Timeslot Range(e.g.1,3-6) VC-12 Bidirectional 8-SL4-1 VC4-1 1-16 5-IFH2-1 VC4-1 1-16
Step 3 Testing E1 Services Through PRBS. Test any two E1 services on each base station. The test results show that the E1 services contain no bit errors. ----End
Issue 05 (2010-10-30)
16-15

This section provides the hyperlinks of the operation tasks associated with two-fiber bidirectional ring MSP.
Related Tasks
A.6.1 Configuring Ring MSP A.7.1 Creating Cross-Connections of Point-to-Point Services A.6.3 Querying the Status of Ring MSP A.6.5 Performing Ring MSP Switching A.6.7 Starting/Stopping the Ring MSP Protocol

When a two-fiber bidirectional ring MSP switching occurs, the NE reports relevant alarms and abnormal events.
Relevant Alarms
l l l APS_INDI The APS_INDI alarm indicates that a protection switching occurs. APS_FAIL The APS_FAIL alarm indicates that a protection switching fails. APS_MANUAL_STOP The APS_MANU_STOP alarm indicates that the MSP protocol is manually stopped.

l l MSP switching This abnormal event indicates that a ring MSP protection switching occurs. No response from the ring MSP remote end This abnormal event indicates that the remote end does not respond to the ring MSP switching request from the local end.
16.12 FAQs
This section provides the answers to the questions that are frequently raised when two-fiber bidirectional ring MSP is used. Q: How are the east and west of a ring network defined? A: In the case of a ring network, two paths exist from one node to another. To ensure the consistency of service routes, most services are configured to travel in one direction. This
direction is called the primary direction of services on the ring network. Generally, the primary direction is counterclockwise. If the line direction in which an NE sends services is the primary direction, the line direction is called the east. If the line direction in which the NE receives services is the primary direction, the line direction is called the west. That is, the services are sent in the east and received in the west. Q: What switching states does two-fiber bidirectional ring MSP have? A: Two-fiber bidirectional ring MSP has the following switching states: l l l l Protocol is not started The state when the ring MSP protocol is not started Protocol starting The state when the ring MSP protocol starts Idle The normal state after the ring MSP protocol is started switching operation The state after a switching event In the case of an east switching, the equipment receives services from the east protection channels rather than the west working channels, and transmits services to the east working channels rather than the west working channels. In the case of a west switching, the equipment receives services from the west protection channels rather than the east working channels, and transmits services to the west protection channels rather than the east working channels. l Pass-through In the pass-through state, the cross-connections on the working channels remain unchanged, and the services on the protection channels in the east and west are passed-through. Q: What are the differences between a two-fiber bidirectional MSP ring and an SNCP ring? A: Item Protected object Protection level Protection mechanism Line rate Two-Fiber Bidirectional MSP Ring A certain section of line Multiplex section level Shared protection STM-4 or an STM mode with a higher rate Ring switching SNCP Ring Services between subnets VC-4 level, VC-3 level, or VC-12 level Dedicated protection PDH microwave, STM-1, or an STM mode with a higher rate Single-ended switching
Switching mode
Issue 05 (2010-10-30)
16-17
Item Bridging/Switching point
Two-Fiber Bidirectional MSP Ring The head end/tail end automatically performs bridging and switching according to the APS protocol. Generally, the head end/tail end is a bridging and switching node. Relatively low STM-N x n/2 (n represents the number of nodes on a ring) 16 (at most) A ring network where services are distributed among NEs
SNCP Ring The transmit end is permanently bridged and the receive end is automatically switched.
Reliability Maximum capacity
Relatively high STM-N
Number of nodes on a ring network Application scenario
No restriction A ring network where services are centralized on a central NE
Q: How to handle a two-fiber bidirectional ring MSP switching failure? A: The steps are as follows: 1. Check the data configuration of the MSP ring, especially the node ID of each NE. The configuration of the node IDs must meet the requirements of the network topology. The node ID of each NE must be unique. 2. 3. Check the protection channels. If an alarm is generated on a protection channel, rectify the fault on the protection channel. Check the MSP state of each NE. In the case of normal switching, the head-end/tail-end node is in the switching state and the intermediate nodes are in the pass-through state. l If an NE is in an exceptional state, restart the MSP protocol of the NE. l If several NEs are in an exceptional state, restart the MSP protocol of all the NEs.
16-18
Issue 05 (2010-10-30)
17 Ethernet over SDH/PDH
17
About This Chapter
Ethernet over SDH/PDH
This chapter describes the Ethernet over SDH/Ethernet over PDH (EoS/EoPDH) feature. 17.1 Introduction This section provides the definition of EoS/EoPDH and describes its purpose. 17.2 Basic Concepts This topic describes the basic concepts that you need to be familiar with before you use the Ethernet service encapsulation and mapping feature. 17.3 Specifications This section describes the specifications of EoS/EoPDH. 17.4 Reference Standards and Protocols This section describes the standards and protocols associated with EoS/EoPDH. 17.5 Availability This section describes the support required by the application of the EoS/EoPDH feature and its dependency. 17.6 Working Principle The EoS/EoPDH is implemented through the encapsulation and mapping protocols, virtual concatenation, and LCAS in a comprehensive manner. 17.7 Planning Guidelines Follow certain guidelines when you plan EoS/EoPDH. 17.8 Configuration Procedure The difference between configuring the Ethernet service based on EoS/EoPDH and configuring the common Ethernet service lies in the configuration of the internal Ethernet port. 17.9 Configuration Example This section uses an example to describe how to plan and configure EoS/EoPDH according to the network conditions. 17.10 Task Collection This section provides the hyperlinks of the operation tasks associated with the EoS/EoPDH feature.
17.11 Relevant Alarms and Events When EoS/EoPDH becomes abnormal, the NE reports corresponding alarms and performance events. 17.12 FAQs This section provides answers to the questions that are frequently asked when EoS/EoPDH is adopted.
17-2
Issue 05 (2010-10-30)
17.1 Introduction
This section provides the definition of EoS/EoPDH and describes its purpose.
Definition
Through the encapsulation and mapping protocols, EoS helps to encapsulate and map Ethernet services into one or several VC containers so that the Ethernet services can be transmitted over SDH networks. Through the encapsulation and mapping protocols, EoPDH helps to encapsulate and map Ethernet services into one or several PDH payloads so that the Ethernet services can be transmitted over SDH/PDH networks.
Purpose
EoS provides a solution to Ethernet service transmission over SDH radio or over PDH radio based on TUs. By adopting the EoS technology, carriers are able to transmit Ethernet services over existing SDH networks. As shown in Figure 17-1, application scenario 1 of EoS has the following features: l The EoS board at the network tail node is used to access Ethernet services. After the accessed Ethernet services are encapsulated and mapped into VC containers, they are transmitted over SDH radio links. Services of multiple base stations are converged through SDH radio links.
Figure 17-1 Application scenario 1 of EoS

IDU FE EoS board Crossconnect unit SDH IF unit SDH IF unit IDU Crossconnect unit SDH optical interface board STM-1/4
E1 FE
SDH radio link SDH radio link E1 FE
SDH optical interface board
Crossconnect unit
EoS board
GE
E1 FE
SDH radio link SDH radio link E1 FE
GE
BTS
NodeB
RTN
MSTP
RNC
As shown in Figure 17-2, application scenario 2 of EoS has the following features:
l l l
The FE/GE port on the Hybrid radio IF unit at the network tail node is used to access Ethernet services of NodeBs. The Ethernet services of multiple base stations are converged through Hybrid radio links. The EoS board at the convergence node encapsulates and maps all the converged and locally accessed Ethernet services into VC containers, which are then transmitted over SDH networks.
Figure 17-2 Application scenario 2 of EoS

IDU FE Hybrid IF unit Hybrid IF unit EoS board IDU Crossconnect unit SDH STM-1/4 optical interface board
E1 FE
Hybrid radio link Hybrid radio link E1 FE
SDH optical interface board
Crossconnect unit
EoS board
GE
GE E1 FE E1 FE Hybrid radio link Hybrid radio link
BTS
NodeB
RTN
MSTP
RNC
EoPDH provides a solution to Ethernet service transmission over PDH radio based on E1s. By adopting the EoPDH technology, carriers are able to transmit Ethernet services over existing PDH networks. As shown in Figure 17-3, application scenario 1 of EoPDH has the following features: l l The EoPDH board at the network tail node is used to access Ethernet services, and encapsulate and map these accessed Ethernet services into E1s for transmission. Services of two to four base stations are converged through PDH radio links.
17-4
Issue 05 (2010-10-30)
Figure 17-3 Application scenario 1 of EoPDH

IDU FE EoPDH board Crossconnect unit PDH IF unit PDH IF unit IDU Crossconnect unit E1 tributary board E1
E1 FE
PDH radio link E1 E1
E1
E1 tributary board
Crossconnect unit
EoPDH board
FE
FE
PDH transmission network
E1
FE
E1 FE
PDH radio link
E1
E1
FE
BTS
NodeB
RTN
MSTP
RNC
As shown in Figure 17-4, application scenario 2 of EoPDH has the following features: l l l The FE/GE port on the Hybrid radio IF unit at the network tail node is used to access Ethernet services of NodeBs. The Ethernet services of the two to four base stations are converged through Hybrid radio links. The EoPDH board at the convergence node encapsulates and maps all the converged and locally accessed Ethernet services into E1s for transmission.
Issue 05 (2010-10-30)
17-5
Figure 17-4 Application scenario 2 of EoPDH

IDU FE Hybrid IF unit Hybrid IF unit IDU EoPDH board Crossconnect unit E1 tributary board E1
E1 E1 FE E1 FE Hybrid radio link E1
E1 tributary board
Crossconnect unit
EoPDH board
FE
PDH transmission network
E1
FE
E1 FE
Hybrid radio link
E1
E1
FE
BTS
NodeB
RTN
MSTP
RNC
17.2 Basic Concepts

This topic describes the basic concepts that you need to be familiar with before you use the Ethernet service encapsulation and mapping feature. 17.2.1 Encapsulation and Mapping Protocols Ethernet service is a type of packet switching service but SDH optical transmission and SDH/ PDH microwave transmission are both based on the TDMA. Therefore, tunnels must be set up for the transmission of the Ethernet service on the transmission network. Generally, the EoS/ EoPDH uses the HDLC, LAPS, and GFP encapsulation and mapping protocols, where the GFP protocol is commonly used. 17.2.2 Virtual Concatenation During the application of EoS, the rate of the Ethernet service does not adapt to the rate of the standard VC container of the SDH. Hence, if you directly map the Ethernet service data into a standard VC container, the transmission bandwidth is lavishly wasted. To solve this problem, use the virtual concatenation technology to concatenate many standard VC containers into a virtual container group (VCG) that adapts to the rate of the Ethernet service. Similarly, EoPDH also requires using the virtual concatenation technology to concatenate PDHs to a VCG that adapts to the rate of the Ethernet service. 17.2.3 LCAS The link capacity adjustment scheme (LCAS) is applied on the basis of virtual concatenation and can improve the performance of virtual concatenation. The LCAS can dynamically adjust the number of virtual containers for mapping the required services, to manage the bandwidth in real time.
17.2.1 Encapsulation and Mapping Protocols

Ethernet service is a type of packet switching service but SDH optical transmission and SDH/ PDH microwave transmission are both based on the TDMA. Therefore, tunnels must be set up
for the transmission of the Ethernet service on the transmission network. Generally, the EoS/ EoPDH uses the HDLC, LAPS, and GFP encapsulation and mapping protocols, where the GFP protocol is commonly used.
HDLC
The HDLC is a general data link control procedure. When using the HDLC protocol, the system encapsulates data services into HDLC-like frames as information bits and maps the frames to SDH VC containers.
LAPS
The LAPS is also a data link control procedure. It is developed based the HDLC.
GFP
The GFP is the most widely applied general encapsulation and mapping protocol currently. It provides a general mechanism to adapt higher-layer client signal flows into the transport network and can map the variable-length payload into the byte-synchronized transport path. Client signals can be protocol data units (PDU-oriented, such as IP/PPP and Ethernet), block-code data (blockcode-oriented, such as FC and ESCON), or common bit streams. The GFP defines the following two modes to adapt to client signals: l Frame-mapping GFP (GFP-F) The GFP-F is a PDU-oriented processing mode. It encapsulates the entire PDU into the GFP payload area and does not modify the encapsulated data. According to requirements, it determines whether to add a detection area for the payload area. l Transparent GFP (GFP-T) The GFP-T is a block-code (8B/10B code block) oriented processing mode. It extracts a single character from the received data block and maps the character into the fixed-length GFP frame.
17.2.2 Virtual Concatenation

During the application of EoS, the rate of the Ethernet service does not adapt to the rate of the standard VC container of the SDH. Hence, if you directly map the Ethernet service data into a standard VC container, the transmission bandwidth is lavishly wasted. To solve this problem, use the virtual concatenation technology to concatenate many standard VC containers into a virtual container group (VCG) that adapts to the rate of the Ethernet service. Similarly, EoPDH also requires using the virtual concatenation technology to concatenate PDHs to a VCG that adapts to the rate of the Ethernet service.
SDH Virtual Concatenation

The concatenation is defined in ITU-T G.707. There are two concatenation methods: contiguous concatenation and virtual concatenation. Both methods provide concatenated bandwidth of X times Container-N at the path termination. Contiguous concatenation concatenates the contiguous C-4s in the same STM-N into an entire structure to be transmitted. It maintains the contiguous bandwidth throughout the whole transmission. Virtual concatenation concatenates many individual VC containers (VC-12 containers, VC-3 containers, or VC-4 containers) into a big virtual structure to be transmitted.
The virtual concatenation breaks the contiguous bandwidth into individual VCs, transmits the individual VCs, and recombines these VCs to a contiguous bandwidth at the end point of the transmission. In the case of the virtual concatenation, each VC container may be transmitted in different paths and there may be a transmission delay difference between VC containers. Hence, there are difficulties in restoring the client signal. Virtual concatenation only requires that the path termination equipment provides the concatenation function and it can allocate bandwidth flexibly. Hence, virtual concatenation is a widely applied concatenation technology. Virtual concatenation is available in two types, virtual concatenation in a higher order path and virtual concatenation in a lower order path. A virtual concatenation VC-4-Xv in a higher order path provides a payload area of X Container-4 (VC-4). The payload is mapped individually into X independent VC-4s. Each VC-4 has its own POH. Similarly, a virtual concatenation VC-12Xv in a lower order path provides a payload area of X Container-12 (VC-12). The payload is mapped individually into X independent VC-12s. Each VC-12 has its own POH, as does the virtual concatenation of VC-3s.
PDH Virtual Concatenation

The PDH supports only the virtual concatenation mode. The 1544 kbit/s, 2048 kbit/s, 34368 kbit/s, and 44736 kbit/s PDH signals can be concatenated to a VCG through the virtual concatenation. Take the virtual concatenation of E1 signals for example. One E1-Xv provides a payload area of X E1. The payload is mapped individually into X independent E1s. This is true in the case of the virtual concatenation of other PDH signals.
NOTE
As shown in Figure 17-8, to implement the virtual concatenation, certain payload in the PDH signals functions as the related overhead. For example, the actual payload provided by the E1-Xv (except the overhead) is Nx1980 kbit/s.
17.2.3 LCAS
The link capacity adjustment scheme (LCAS) is applied on the basis of virtual concatenation and can improve the performance of virtual concatenation. The LCAS can dynamically adjust the number of virtual containers for mapping the required services, to manage the bandwidth in real time. The LCAS technology has the following advantages: l l The LCAS can dynamically adjust (add, delete, or modify) the service bandwidth without affecting the availability of the existing service. If there are failed physical channels in virtual concatenation, the LCAS shields these physical channels. Other physical channels in virtual concatenation can transfer services. Hence, this prevents a situation where the failure of a single physical channel causes interruption of services. After the failed physical channels are restored, they can transfer services.
17.3 Specifications
This section describes the specifications of EoS/EoPDH. Table 17-1 lists the specifications of EoS/EoPDH.
Table 17-1 Specifications of EoS/EoPDH Item EMS6 Maximum bandwidth on the SDH/PDH sidea Maximum number of VCTRUNKs on the SDH/PDH side Maximum bandwidth of a VCTRUNKb Maximum number of VC-3s bound to VCTRUNKs of a board Maximum number of VC-3s bound to a VCTRUNK Maximum number of VC-12s bound to VCTRUNKs of a board Maximum number of VC-12s bound to a VCTRUNK Maximum number of E1s bound to VCTRUNKs of a boardd Maximum number of E1s bound to a VCTRUNK Maximum delay of the VC-3 virtual concatenation Maximum delay of the VC-12 virtual concatenation 2xVC-4 Specification of EoS EFT4 2xVC-4 Specification of EoPDH EFP6 1xVC-4
16
100 Mbit/s
100 Mbit/s
16x1980 kbit/s
63c
63c
63
63
63
16
16 ms
8 ms
32 ms
16 ms
Issue 05 (2010-10-30)
17-9
Item EMS6 Maximum delay of the E1 virtual concatenation Encapsulation protocol -
Specification of EoS EFT4 -
Specification of EoPDH EFP6 30 ms
HDLC LAPS GFPe
HDLC LAPS GFPe ITU-T G.7042 Huawei Mode Standard Mode Supported Supported Supported
GFPe
LCAS standard LCAS mode
ITU-T G.7042 Huawei Mode Standard Mode
ITU-T G.7042 Huawei Mode Standard Mode Supported Supported Supported
LCAS hold-off time (ms) LCAS WTR time (s) LCAS TSD detection
Supported Supported Supported
NOTE
a:
The total bandwidth is equal to the number of planned VCTRUNKs multiplied by actual bandwidth allocated to each VCTRUNK. The total bandwidth cannot be higher than the maximum SDH/PDH bandwidth.
b:
In the case of the EMS6, EFT4, and EFP6 boards, a VCTRUNK carries a limited bandwidth. If the Ethernet service capacity carried by a VCTRUNK is higher than the maximum bandwidth of this VCTRUNK, you need to bind several VC paths to this VCTRUNK. (The total bandwidth of these VC paths is greater than the maximum bandwidth of this VCTRUNK.) In addition, you need to bind several VCTRUNKs by creating a load sharing LAG, so that Ethernet service traffic can be balanced on several VCTRUNKs. In this manner, Ethernet services of a large capacity can be transmitted.
c:
For the EMS6 board and the EFT4 board, only the second VC-4 supports the VC-12 granularity and the first VC-4 supports only the VC-3 granularity.
d: e:
The EFP6 is a type of EoPDH board, and its VCTRUNK can bind E1s, which are displayed as VC-12 paths when you configure services on the Web LCT. GFP includes the GFP-F and GFP-T 2 modes. The EMS6, EFT4, and EFP6 boards support GFP-F.

This section describes the standards and protocols associated with EoS/EoPDH. l Encapsulation complies with the following protocols: RFC 1662, HDLC encapsulation protocol ITU-T Recommendation X.86, LAPS encapsulation protocol ITU-T Recommendation G.7041/Y.1303 (2003), GFP encapsulation protocol
Mapping complies with the following protocols: ITU-T Recommendation G.707, GFP-encapsulated Ethernet frame mapping the SDH ITU-T Recommendation G.8040 (2004), GFP-encapsulated Ethernet frame mapping the PDH
ITU-T Recommendation G.7042/Y.1305 (2003), Link capacity adjustment scheme (LCAS) for virtual concatenated signals
17.5 Availability
This section describes the support required by the application of the EoS/EoPDH feature and its dependency.

Table 17-2 Hardware and version support (EoS) Feature Encapsulation and mapping protocol (GFP, HDLC, and LAPS) Virtual concatenation LCAS Applicable Board EMS6 EFT4 EMS6 EFT4 EMS6 EFT4 Applicable Hardware Version All the versions All the versions All the versions All the versions All the versions All the versions Applicable Product Version V100R002 and later V100R002 and later V100R002 and later V100R002 and later V100R002 and later V100R002 and later
Table 17-3 Hardware and version support (EoPDH) Feature Encapsulation and mapping protocol (GFP) Virtual concatenation LCAS Applicable Board EFP6 Applicable Hardware Version All the versions Applicable Product Version V100R005C00 and later V100R005C00 and later V100R005C00 and later
EFP6 EFP6
All the versions All the versions
Issue 05 (2010-10-30)
17-11
Feature Dependency
The Ethernet service encapsulation, virtual concatenation, and LCAS technology do not have any impact on other features.
17.6 Working Principle

The EoS/EoPDH is implemented through the encapsulation and mapping protocols, virtual concatenation, and LCAS in a comprehensive manner. 17.6.1 Encapsulation and Mapping The HDLC/LAPS/GFP protocol encapsulates and maps Ethernet frames as PDUs. 17.6.2 Virtual Concatenation The virtual concatenation is implemented through the serial numbers of multiframes in the virtual concatenation and the overhead of multiframe indicators. 17.6.3 LCAS The LCAS implements the capacity adjustment of the virtual container by exchanging the control information between both the source and the sink side.
17.6.1 Encapsulation and Mapping

The HDLC/LAPS/GFP protocol encapsulates and maps Ethernet frames as PDUs. Among the HDLC, LAPS, and GFP protocols, the GFP protocol is most widely applied. Hence, this topic takes the GFP protocol as an example to describe how Ethernet frames are encapsulated and mapped.
17-12
Issue 05 (2010-10-30)
Structure of the GFP Frame

Figure 17-5 Structure of the GFP frame
Octet transmission order 1 2 3 4 5
Core header
Payload area
4-65535
n 1 2 3 4 5 6 7 8 Octet transmission order
a) Frame size and transmission order
16-bit payload length indicator c-HEC (CRC-16) Core header Payload headers (4-64 bytes) Payload area Client payload information field
Optional payload FCS (CRC-32)
b) Field constituting a GFP client frame
A GFP frame consists of a core header and a payload area. The Idle frame does not have the payload area. The GFP core header includes the following fields:
Payload length indicator (PLI) The PLI field represents the number of octets in the GFP payload area. The minimum value of the PLI field in a GFP client frame is 4 octets. PLI values 0 to 3 are reserved for GFP control frame usage.
Core HEC (cHEC) The cHEC field protects the integrity of the contents of the core header by enabling both single-bit error correction and multi-bit error detection.
The GFP payload area includes the payload header, client payload information field, and payload frame check sequence. The payload header consists of the type, type HEC (tHEC), extension header field, and extension HEC (eHEC). The type field includes the following: l Payload type identifier (PTI) The PTI identifies the type of GFP client frame. Two kinds of client frames are currently defined, user data frames (PTI = 000) and client management frames (PTI = 100). l l Payload FCS indicator (PFI) The PFI indicates the presence (PFI = 1) or absence (PFI = 0) of the payload FCS field. Extension header identifier (EXI) The EXI indicates the presence or absence of the extension header. When EXI = 0, there is no extension header. This frame format applies to a logical point-to-point configuration. l User payload identifier (UPI) The UPI identifies the type of the client frame. Figure 17-6 GFP type field format
Octet transmission order 15 14 13 12 11 10 9 8 Bit number 5 6 7 1 6 2 5 3 PTI PFI UPI 4 4 3 5 2 6 1 7 0 Bit number 8 Octet transmission order EXI
The tHEC field protects the integrity of the type field by enabling both single-bit error correction and multi-bit error detection. The extension header field and eHEC field are used to support special data link header technologies and are seldom used in actual situations.
Type of the GFP Frame

There are two types of GFP frame: GFP control frame and GFP client frame. Currently, the GFP control frame is available only in one type: the Idle frame. The Idle frame is a four-octet GFP control frame consisting of only a GFP core header. The Idle frame is intended for the GFP source adaptation process to facilitate the adaptation of the GFP octet stream to any given transport medium where the transport medium channel has a high capacity. Two types of GFP client frames are currently defined: client data frame and client management frame. GFP client data frames are used to transport data from the client signal. GFP client
management frames are used to transport information associated with the management of the client signal or GFP connection. The type field of the client data frames uses the following values: l l l l PTI = 100 PFI = Payload specific EXI = Payload specific UPI = See Table 17-4.
Table 17-4 UPI values of the client management frame UPI Value 0000 0000 1111 1111 0000 0001 0000 0010 0000 0011 through 1111 11110 Client signal fail (loss of client signal) Client signal fail (loss of character synchronization) Reserved for future use Usage Reserved
Ethernet Frame Encapsulation

The Ethernet board adopts the GFP-F adaptation mode to encapsulate Ethernet frames into the corresponding virtual container group. The encapsulation process is as follows: 1. The Ethernet MAC octets from the destination address through the frame check sequence, inclusive, are placed in the GFP payload information field. Octet-alignment is maintained and bit identification within octets is maintained.
Ethernet MAC frame Octets 2 2 2 2 0-60 GFP frame PLI cHEC Type tHEC GFP extension header
Octets 7 1 6 6 2
4 1
Preamble Start of frame delimiter Destination Address (DA) Source Address (SA) Length/Type MAC client data Pad Frame Check Sequence (FCS) 2 3 4 5 6 7 8
GFP payload
Bits
Bits
2. 3.
Calculate other fields of the GFP client data frame over the content of the payload. Scramble the core header and the payload area to maintain DC balance of the transported data.
Issue 05 (2010-10-30)
4.
Map GFP client data frames into virtual container groups and insert the Idle frame to realize the rate adaptation between the variable-length PDUs and the defined virtual container groups.
The decapsulation process is as follows: 1. 2. 3. Check for a correct cHEC, byte by byte in the payload of the virtual container group. Once a correct cHEC is detected, a GFP frame is found. Check for subsequent GFP frames frame by frame according to the PLI in the GFP frame and discard Idle frames. Descramble the payload area in the found GFP frame and extract the Ethernet MAC octets from the destination address through the frame check sequence, inclusive.
17.6.2 Virtual Concatenation

The virtual concatenation is implemented through the serial numbers of multiframes in the virtual concatenation and the overhead of multiframe indicators.
VC-4-Xv and VC-3-Xv

The virtual container that is formed by a VC-4-Xv/VC-3-Xv can be mapped into X individual VC-4/VC-3s which form the VC-4-Xv/VC-3-Xv. Each VC-4/VC-3 has its own POH. The POH has the same specifications as the ordinary VC-4 POH. The H4 byte in the POH is used for the virtual concatenation-specific multiframe indicator (MFI) and sequence indicator (SQ). The MFI indicates the position of a frame in the multiframe. Each frame sent by the source carries the MFI information. The sink combines the frames with the same MFI information into the C-n-Xv. The MFI consists of the MFI-1 and MFI-2. The MFI-1 is transmitted in bit 5 to bit 8 of the H4 byte and ranges from 0 to 15. The MFI-2 is transmitted in the frame whose MFI-1 is 0 and the frame whose MFI-1 is 1 in the multiframe. Bit 1 to bit 4 in the H4 bytes of the two frames indicate the higher four bits and the lower four bits of the MFI-2. Thus, MFI-2 ranges from 0 to 255. A multiframe contains 4096 frames and has a period of 512 ms. The SQ indicates the position of a frame in the C-n-Xv. The source inserts the SQ information into the frame according to the payload allocation sequence. The sink determines the sequence to extract the payload from the frames that form C-n-Xv according to the SQ. The SQ is transmitted in the frame whose MFI-1 is 14 and the frame whose MFI-1 is 15 in the multiframe. Bit 1 to bit 4 in the H4 bytes of the two frames indicate the higher four bits and the lower four bits of the SQ.
17-16
Issue 05 (2010-10-30)
Figure 17-7 VC-3-Xv/VC-4-Xv multiframe and sequence indicator

C-3-X/C-4-X 1 X C-3-Xv/C-4-Xv SQ = X-1 =0 SQ = 0 =0 MFI-1 = 0 X-1 MFI-2 = 0 =1 SQ = 0 =0 MFI-1 = 1 MFI-2 = 0
H
POH
POH
SQ = X-1 = 15 SQ = 0 MFI-1 = 15 = 0 MFI-2 = 0 X-1 SQ = 0 =0 MFI-1 = 0 = 15 MFI-2 = 1 SQ = X-1 = 15 SQ = 0 = 255 MFI-1 = 15 MFI-2 = 255 X-1 =0 SQ = 0 =0 MFI-1 = 0 MFI-2 = 0
H H
With the MFI and SQ, the sink can correctly restore the position of each frame in the C-n-Xv to avoid the frame alignment problem due to the different transmission delays of the frames.
VC-12-Xv
The virtual container that is formed by a VC-12-Xv can be mapped into X individual VC-12s which form the VC-12-Xv. Each VC-12 has its own POH. The POH has the same specifications as the ordinary VC-12 POH. Bit 2 of the K4 byte in the POH is used for the virtual concatenationspecific frame count and sequence indicator. Bit 2s of the K4 bytes in every 32 multiframes (one multiframe comprising four VC-12s) are extracted to form a 32-bit character string to express the frame count and sequence indicator. Bits 1-5 of the string express the frame count, whose value range is between 0 and 31. The structure formed by 32 multiframes has 128 frames. Hence, the resulting overall multiframe is 1096 frames (= 512 ms) long. Bits 6-11 of the string express the sequence indicator. The frame count/sequence indicator in the VC-12-Xv has the same usage as the multiframe indicator/ sequence indicator in the VC-4-Xv/VC-3-Xv.
E1-Xv
The virtual container that is formed by an E1-Xv can be mapped into X individual E1-Xvs which form the E1-Xv. As shown in Figure 17-8, ITU-T G.704 defines the E1 frame and the structure of the E1 multiframe consisting of N (N ranges from 1 to 16) E1 frames. The byte of timeslot 1 of each E1 frame is used for concatenation overhead. This provides the alignment information for the receive node. Based on the framing information provided by the overheads, the receive node can convert the receive bit into a single timeslot or channel.
POH
POH
POH
Multiframe (MF)
POH
Figure 17-8 Position of the N x 2048 kbit/s signals in the concatenation overhead
125 ms
Concatenation overhead octet
Frame number
1 2 3 4 5 T.S.0 T.S.0 T.S.0 T.S.0 T.S.0
15 T.S.0 16 T.S.0
The concatenation overhead byte includes the virtual concatenation-specific MFI and the SQ. The MFI indicates the position of a frame in the multiframe. Each frame sent from the source contains the MFI information. The sink combines the frames with the same MFI into the E1Xv. The MFI consists of the MFI-1 and MFI-2. The MFI-1 is transmitted in bit 5 to bit 8 in the concatenation overhead byte, and ranges from 0 to 15. The MFI-2 is transmitted in the frame whose MFI-1 value is 0 and the frame whose MFI-1 value is 1 in the multiframe. In the concatenation overhead byte of the two frames, bit 1 to bit 4 indicate the higher four bits and the lower four bits of the MFI-2. The SQ indicates the position of a frame in the E1-Xv. The source inserts the SQ information into the frame according to the payload allocation sequence. The sink determines the sequence to extract the payload from the frames that form the E1-Xv according to the SQ. The SQ is transmitted in bit 1 to bit 4 of the concatenation overhead byte of the frame whose MFI-1 is 15 in the multiframe. With the MFI and SQ, the sink can correctly restore the position of each frame in the E1-Xv to avoid the frame alignment problem due to different transmission delays of the frames.
17.6.3 LCAS
The LCAS implements the capacity adjustment of the virtual container by exchanging the control information between both the source and the sink side.
Control Information
Synchronization of changes in the capacity of the transmitter (So) and the receiver (Sk) is achieved by a control packet. Each control packet describes the state of the link during the next control packet. Changes are sent in advance so that the receiver can switch to the new configuration as soon as it arrives. The control packet is transported in byte H4 (higher order path) or bit 2 of byte K4 (lower order path). The control packet includes the following: l MFI or frame count MFI is used for the VC-4-Xv/VC-3-Xv and the PDH virtual concatenation, and the frame count is used for the VC-12-Xv. Both are used to indicate the position of a multiframe. For the usage, see 17.6.2 Virtual Concatenation.
SQ SQ is used to indicate the position of a standard frame in the virtual concatenation. For the usage, see 17.6.2 Virtual Concatenation.
GID The GID is used for identification of the VCG. The GID bit of all members of the same VCG has the same value. The VCG refers to a group of co-located member trail termination functions that are connected to the same virtual concatenation link. The members of a VCG are the virtual containers that form the VCG. The VCG is equivalent to the generally spoken VCTRUNK.
Control field (CTRL) The control field is used to transfer the link information from the source to the sink. It must provide the status of the individual member of the link. Table 17-5 LCAS CTRL words Command FIXED ADD NORM EOS IDLE DNU Remarks This is an indication that this end uses fixed bandwidth (non-LCAS mode). This member is about to be added to the group. Normal transmission End of sequence indication and normal transmission This member is not part of the group or about to be removed. Do not use (the payload). The sink side reported FAIL status.
CRC The CRC check is performed on every control packet after it has been received, and the contents rejected if the test fails.
l l
Member status field (MST) It reports the member status from the sink to the source. There are two states, OK and FAIL. Re-sequence acknowledge (RS-Ack) bit When a change of the status of the members in a VCG is detected at the sink side, a notification to the source has to be performed by toggling (that is, change from '0' to '1' or from '1' to '0') the RS-Ack bit.
The forward control packets from the source to the sink include the MFI, SQ, GID, CTRL, and CRC. The backward control packets from the sink to the source include the MST, RS-Ack, and CRC.
Issue 05 (2010-10-30)
17-19
Capacity Adjustment Process

Figure 17-9 Capacity adjustment process (addition of a member)
Source (EOS) Source (new) Ctrl=ADD MST=OK Ctrl=EOS RS-Ack Ctrl=NORM Sink (new) Source (EOS)
When a member is added to a VCTRUNK on the NMS, the LCAS capacity adjustment process is as follows: 1. The LCAS source assigns a sequence number (one larger than the currently highest sequence number) to the new member and sends a forward control packet with its CTRL word being ADD to the sink. The LCAS sink performs continuity check for the new member. If the link of the new member is normal, the sink sends a backward control packet in which MST = OK to the source. The LCAS source sends a forward control packet with its CTRL code being EOS to the sink for the new member, indicating that the SQ of the new member is the currently highest number in the VCG. The LCAS sink sends the RS-Ack to the source to acknowledge the change of the SQ. The LCAS source sends a forward control packet with its CTRL code being NORM to the sink for the member whose original state is EOS, indicating that the member is normally transmitted but is not the one with the highest SQ. Both the source and the sink use the new member to transport the payload.
2.
3.
4. 5.
6.
Figure 17-10 Capacity adjustment process (deletion of a member)

Source(SQ>removed member's SQ) Source(removed) Ctrl=IDLE MST=FAIL RS-Ack Ctrl=EOS/NORM RS-Ack Sink(removed) Sink(SQ>removed member's SQ)
When a member is deleted from a VCTRUNK on the NMS, the LCAS capacity adjustment process is as follows:
1. 2.
The LCAS source sends a forward control packet with its CTRL code being IDLE to the sink for the deleted member. The LCAS sink sets the status of the member to FAIL and sends a backward control packet in which MST = FAIL to the source and also sends the RS-Ack to acknowledge the change of the SQ. The LCAS source reallocates SQs for all the members whose SQ is higher than that of the deleted member (SQ decremented successively by 1). It also sends a forward control packet with its CTRL code being EOS or NORM to the sink to indicate the change of the SQ. The LCAS sink sends the RS-Ack to the source to acknowledge the change of the SQ. Both the source and the sink do not use the deleted member to transport the payload.
3.
4. 5.
Figure 17-11 Capacity adjustment process (one member link restored after a failure)
Source (link error) MST=FAIL Ctrl=DNU Sink
...
MST=OK Ctrl=NORM
When a member link of a VCTRUNK is restored after a failure, the process of adjusting the LCAS capacity is as follows: 1. 2. 3. On detecting that a member link is faulty, the LCAS sink sends a backward control packet in which MST = FAIL to the source. The LCAS source sends a forward control packet with its CTRL code being DNU to the sink for the member, indicating that the member is temporarily unavailable. If the original status of the member is EOS, the LCAS source sends a forward control packet with its CTRL word being EOS to the sink for the member whose SQ is one lower than EOS. Both the source and the sink do not use the faulty link member to transport the payload. On detecting that the member link is restored, the LCAS sink sends a backward control packet in which MST = OK to the source. The LCAS source sends a forward control packet with its CTRL code being NORM or EOS to the sink for the member, indicating that the member is restored and available. If the original status of the member is EOS, the LCAS source sends a forward control packet with its CTRL word being NORM to the sink for the member whose status is set to EOS. Both the source and the sink use the restored member to transport the payload.
4. 5. 6. 7. 8.
Issue 05 (2010-10-30)
17-21

NOTE
l The LCAS source can adopt the Huawei mode or the standard mode to send the two control packets MST and Rs-Ack. In the Huawei mode, the Rs-Ack is sent before the MST. In the standard mode, the MST is sent before the Rs-Ack. l The LCAS sink uses the trail signal fail (TSF) or the loss of multiframe (LOM) as a required condition to determine whether a link is faulty. It uses the trail signal degraded (TSD) as an optional condition. In the case of the VC-12, the TSD is the BIP_SD. In the case of the VC-3, the TSD is the B3_SD_VC12. l When a member link is faulty, the LCAS performs a protection switching after a delay of time to prevent the situation where an NE simultaneously performs a protection switching such as SNCP and deletes the member. l A VCG uses a member to transport payload some time after the member link is restored.

Follow certain guidelines when you plan EoS/EoPDH. Adhere to the following guidelines when planning the encapsulation and mapping of the Ethernet port: l l Plan the same encapsulation and mapping protocol for both sides. It is recommended that you adopt the GFP protocol. The parameters of the encapsulation and mapping protocol at both sides need to be consistent. It is recommended that you adopt the default parameters of the protocol.
Adhere to the following guidelines when planning VCTRUNKs: l As shown in Table 17-1, the capacity of VCTRUNKs needs to be determined by the actual bandwidth of the service needs. The total bandwidth is equal to the number of planned VCTRUNKs multiplied by actual bandwidth allocated to each VCTRUNK. The total bandwidth cannot be greater than the maximum SDH/PDH bandwidth. If the bandwidth required for transmitting the Ethernet service is greater than the maximum bandwidth of a single VCTRUNK, you can create a link aggregation (LAG) in load sharing mode to bind several VCTRUNKs into an LAG. In this manner, the requirement of transmitting the Ethernet service with a large capacity can be met. l l Bind only the paths in a VC-4 if possible. If the paths of several VC-4s need to be bound, the VC-4s that have the same transmission path take priority. Each VC-4 of an Ethernet board can have only VC-3 paths or only VC-12 paths. Hence, when a VCTRUNK needs to be bound with VC-3 paths, give priority to the VC-4s whose paths are already bound with the VC-3; when a VCTRUNK needs to be bound with VC-12 paths, give priority to the VC-4s whose paths are already bound with the VC-12. As the VC-4-1 of the EFT4 board and EMS6 board can bind only VC-3 paths whereas the VC-4-2 can bind both VC-12 and VC-3 paths, give priority to the paths in the VC-4-1 when a VCTRUNK needs to be bound with VC-3 paths. Generally, bidirectional paths are bound.
Adhere to the following guidelines when planning the LCAS: l l The LCAS at both sides must be enabled or disabled. If the LCAS is enabled at both sides, the used LCAS parameters at both sides must be consistent.
17-22
If the opposite equipment is the third-party equipment and does not support the Huawei mode, set the LCAS mode to the standard mode. Otherwise, set the mode to the Huawei mode at both sides. It is recommended that you set the hold-off time to 2000 ms. It is recommended that you set the WTR time to 300s. It is recommended that you disable the trail signal degrade (TSD) function.
l l l

The difference between configuring the Ethernet service based on EoS/EoPDH and configuring the common Ethernet service lies in the configuration of the internal Ethernet port. Table 17-6 lists the configuration procedure of EoS.
Issue 05 (2010-10-30)
17-23
Table 17-6 Configuration procedure of EoS Step 1 Operation A.18.2 Configuring the Internal Port of the Ethernet Board Description Required. l Encapsulation/Mapping: It is recommended that you set Mapping Protocol to GFP. The Mapping Protocol and protocol parameters set for VCTRUNKs at one end of a transmission line must be the same as the Mapping Protocol and protocol parameters set for VCTRUNKs at the other end of the transmission line respectively. l Bound path: A VCTRUNK on the EMS6 or EFT4 board supports the maximum bandwidth of 100 Mbit/s. Therefore, the total bandwidth of VC paths bound to a VCTRUNK on the EMS6 or EFT4 board cannot be more than 100 Mbit/s As the VC-4-1 of the EFT4 board and EMS6 board can bind only VC-3 paths whereas the VC-4-2 can bind both VC-12 and VC-3 paths, give priority to the paths in the VC-4-1 when a VCTRUNK needs to be bound with VC-3 paths. When a VCTRUNK needs to be bound with VC-12 paths, only the paths in the VC-4-2 can be bound. The timeslots to which the paths bound with a VCTRUNK correspond must be the same at both ends of a transmission line. l LCAS: Set Enabling LCAS according to the network planning. To enable Enabling LCAS, ensure that the LCAS protocol and protocol parameters set for VCTRUNKs at one end of a transmission line is the same as the LCAS protocol and protocol parameters set for VCTRUNKs at the other end of the transmission line. 2 A.7.1 Creating Cross-Connections of Point-to-Point Services A.7.2 Creating Cross-Connections for SNCP Services Required when the non-SNCP service is configured.
Required when the SNCP service is configured.
17-24
Issue 05 (2010-10-30)
Table 17-7 lists the configuration procedure of EoPDH. Table 17-7 Configuration procedure of EoPDH Step 1 Operation A.18.2 Configuring the Internal Port of the Ethernet Board Description Required. l Encapsulation/Mapping: The Mapping Protocol and protocol parameters set for VCTRUNKs at one end of a transmission line must be the same as the Mapping Protocol and protocol parameters set for VCTRUNKs at the other end of the transmission line respectively. The EFP6 board supports only the GFP mapping protocol. l Bound path: The EFP6 board supports the E1-level VCTRUNK. During the service configuration, however, the NMS displays that the VC-12 paths are bound. The maximum number of VC-12 paths bound to a VCTRUNK on the EFP6 board is 16. The timeslots to which the paths bound with a VCTRUNK correspond must be the same at both ends of a transmission line. l LCAS: Set Enabling LCAS according to the network planning. To enable Enabling LCAS, ensure that the LCAS protocol and protocol parameters set for VCTRUNKs at one end of a transmission line is the same as the LCAS protocol and protocol parameters set for VCTRUNKs at the other end of the transmission line. 2 A.7.1 Creating Cross-Connections of Point-to-Point Services A.7.2 Creating Cross-Connections for SNCP Services Required when the non-SNCP service is configured.
Required when the SNCP service is configured.
Issue 05 (2010-10-30)
17-25

This section uses an example to describe how to plan and configure EoS/EoPDH according to the network conditions. For details on the configuration example of an Ethernet service over the SDH/PDH network, see Configuration Example (Ethernet Services Traversing a TDM Network) in the Configuration Guide.

This section provides the hyperlinks of the operation tasks associated with the EoS/EoPDH feature.
Related Tasks
A.18.2 Configuring the Internal Port of the Ethernet Board A.7.1 Creating Cross-Connections of Point-to-Point Services A.7.2 Creating Cross-Connections for SNCP Services A.18.6 Dynamically Increasing/Decreasing the VCTRUNK Bandwidth

When EoS/EoPDH becomes abnormal, the NE reports corresponding alarms and performance events.
Relevant Alarms
l ALM_GFP_dCSF The ALM_GFP_dCSF alarm indicates that the GFP client signal is lost. On detecting the GFP client management frame that indicates the loss of the client signal from the opposite station, the board reports this alarm. l ALM_GFP_dLFD The ALM_GFP_dLFD alarm indicates that the GFP frame is out of synchronization. On detecting that the GFP frame is in the out-of-synchronization state, the board reports this alarm. l FCS_ERR The FCS_ERR alarm indicates a check error of the frame check sequence (FCS). If the FCS check on the received HDLC/LAPS/GFP frame encounters an error, the board reports this alarm. l l VCAT_LOA The VCAT_LOA alarm indicates a loss of alignment of the virtual concatenation. VCAT_LOM_VC3
17-26
Issue 05 (2010-10-30)
The VCAT_LOM_VC3 alarm indicates a loss of multiframe of the virtual concatenation at the VC-3 level. On detecting a mismatch between byte H4 and the expected multiframe sequence, the board reports this alarm. l VCAT_LOM_VC12 The VCAT_LOM_VC12 alarm indicates a loss of multiframe of the virtual concatenation at the VC-12 level. On detecting a mismatch between byte K4 and the expected multiframe sequence, the board reports this alarm. l VCAT_SQM_VC3 The VCAT_SQM_VC3 alarm indicates a mismatch of SQ of the virtual concatenation at the VC-3 level. On detecting a mismatch between the SQ of the member and the expected SQ, the board reports this alarm. l VCAT_SQM_VC12 The VCAT_SQM_VC12 alarm indicates a mismatch of SQ of the virtual concatenation at the VC-12 level. On detecting a mismatch between the SQ of the member and the expected SQ, the board reports this alarm. l LCAS_FOPR The LCAS_FOPR alarm indicates that the protocol in the LCAS receive direction fails. If the receive unit of the LCAS module of the board detects an abnormality that may cause the LCAS protocol to fail to negotiate or negotiate a wrong result, the board reports this alarm. l LCAS_FOPT The LCAS_FOPT alarm indicates that the protocol in the LCAS transmit direction fails. If the transmit unit of the LCAS module of the board detects an abnormality that may cause the LCAS protocol to fail to negotiate or negotiate a wrong result, the board reports this alarm. l LCAS_PLCR The LCAS_PLCR alarm indicates that the bandwidth is partially lost in the LCAS receive direction. the receive direction of the VCTRUNK with the LCAS enabled, if the number of paths that actually carry the payload is smaller than that of the configured paths but is not 0, the board reports this alarm. l LCAS_PLCT The LCAS_PLCT alarm indicates that the bandwidth is partially lost in the LCAS transmit direction. In the transmit direction of the VCTRUNK with the LCAS enabled, if the number of paths that actually carry the payload is smaller than that of the configured paths but is not 0, the board reports this alarm. l LCAS_TLCR The LCAS_TLCR alarm indicates that the bandwidth is totally lost in the LCAS receive direction. In the receive direction of the VCTRUNK with the LCAS enabled, if the number of paths that actually carry the payload is 0 but that of the configured paths is not 0, the board reports this alarm. l LCAS_TLCT The LCAS_TLCT alarm indicates that the bandwidth is totally lost in the LCAS transmit direction. In the transmit direction of the VCTRUNK with the LCAS enabled, if the number of paths that actually carry the payload is 0 but that of the configured paths is not 0, the board reports this alarm.
Issue 05 (2010-10-30)
17-27

l LCAS event: Adding a member is successful. This abnormal event indicates that within the specified time (10s), the member added into the VCTRUNK already carries traffic. l LCAS event: Adding a member times out. This abnormal event indicates that within the specified time (10s), the member added into the VCTRUNK cannot carry traffic. l LCAS event: Deleting a member is successful. This abnormal event indicates that within the specified time (10s), the member deleted from the VCTRUNK does not carry traffic any longer. l LCAS event: Deleting a member times out and the member is forcibly deleted. This abnormal event indicates that within the specified time (10s), the LCAS fails to enable the VCTRUNK to delete the member and as a result the local end forcibly deletes the member. l LCAS event: The bandwidth is restored. This abnormal event indicates that the member whose link is faulty starts to carry traffic again.
17.12 FAQs
This section provides answers to the questions that are frequently asked when EoS/EoPDH is adopted. Q: How does one calculate the theoretical bandwidth of a VCTRUNK for Ethernet services? A: The calculation formula is as follows: Bandwidth = Number of bound paths of the VCTRUNK x Payload rate of the binding granularity x Encapsulation efficiency of the encapsulation protocol x (Length of the Ethernet frame + Interframe gap + Preamble)/Length of the Ethernet frame. The payload rate of the VC-12 is 2.176 Mbit/s, and the payload rate of the VC-3 is 48.384 Mbit/ s. The length of the interframe gap is always 8 bytes, and the length of the preamble is always 12 bytes. In the case of the encapsulation efficiency of the GFP protocol, two cases are possible: l When the GFP protocol uses FCS32 as the check field, the encapsulation efficiency of the GFP protocol is calculated as follows: Length of the Ethernet frame/(Length of the Ethernet frame + 12-byte overload). When the GFP protocol does not have the check field, the encapsulation efficiency of the GFP protocol is calculated as follows: Length of the Ethernet frame/(Length of the Ethernet frame + 8-byte overload).
NOTE
If the Ethernet board uses the GFP protocol for Ethernet service encapsulation, set the Check Field Length parameter to control the using of the check field. By default, FCS32 is used as the check field.
Based on the preceding data, if the Ethernet board uses the default parameter values of the GFP protocol, the theoretical bandwidth of five VCTRUNKs at the VC-12 level is 10.938 Mbit/s when the length of the Ethernet frame is 1500 bytes; the theoretical bandwidth of five
VCTRUNKs at the VC-12 level is 12.025 Mbit/s when the length of the Ethernet frame is 64 bytes. Q: Why is the bandwidth of Ethernet payloads transmitted in VC-12 paths higher than the bandwidth of Ethernet payloads transmitted in E1 paths? A: Certain overheads in VC-12 paths can transmit payloads. Therefore, the actual bandwidth of Ethernet payloads transmitted in a VC-12 path, which can reach 2.17 Mbit/s, is higher than the bandwidth of an E1. When an E1 path transmits services, certain payloads are used to transmit overheads. Therefore, the bandwidth of Ethernet payloads transmitted in an E1 path is 1980 kbit/ s, which is smaller than the bandwidth of Ethernet payloads that are transmitted in a VC-12 path. In conclusion, the service capacity of a VC-12 path is greater than that of an E1 path.
Issue 05 (2010-10-30)
17-29
18 VLAN
18
About This Chapter
This chapter describes the virtual local area network (VLAN) feature. 18.1 Introduction This section provides the definition of VLAN and describes its purpose. 18.2 Basic Concepts This section describes the basic concepts associated with VLANs. 18.3 Specifications This section provides the specifications of VLANs. 18.4 Reference Standards and Protocols This section describes the standards and protocols associated with VLANs.
VLAN
18.5 Availability This section describes the support required by the application of the VLAN feature and its dependency. 18.6 Principles Implementation of the VLAN feature is relevant to the port attribute and service type. 18.7 Planning Guidelines Follow certain guidelines when you plan VLANs. 18.8 Configuration Procedure Based on the VLAN planning information, configure an Ethernet service and set the TAG attribute of an Ethernet port. 18.9 Configuration Example This section uses an example to describe how to plan and configure an Ethernet service based on the VLAN according to the network conditions. 18.10 Task Collection This section provides the hyperlinks of the operation tasks associated with VLANs. 18.11 Relevant Alarms and Events There are no alarms or performance events relevant to VLANs.
18 VLAN
18.12 FAQs This section provides the answers to the questions that are frequently raised when the VLAN feature is used.
18-2
Issue 05 (2010-10-30)
18 VLAN
18.1 Introduction
This section provides the definition of VLAN and describes its purpose.
Definition
According to specific rules, a real network topology can be divided into several logical subnetworks, which are VLANs. The broadcast packet of a VLAN can transmit only within the range of this VLAN. That is, one VLAN corresponds to a specific broadcast domain. Figure 18-1 shows the VLAN application. All Ethernet devices of a company belong to one LAN, and the Ethernet devices of different departments form their respective VLANs. The broadcast packets of a VLAN are limited to its range. In this manner, Ethernet packets of different departments are isolated, and the broadcast flooding problem on a LAN is successfully solved. Figure 18-1 Networking diagram of the VLAN application
VLAN100 Branch A VLAN101 Branch B VLAN102 Branch C
Ethernet link Radio link
VLAN100 Branch A' VLAN101 Branch B'
NE1
NE2 VLAN102
Branch C'
Purpose
The VLAN technology helps users solve the broadcast flooding problem with a low cost. In addition, the VLAN technology offers several revolutionary benefits. l Improving bandwidth utilization Broadcast packets are forwarded within the range of a specific VLAN other than on the entire LAN, so a large number of unnecessary broadcast packets are not generated. This effectively improves bandwidth utilization. In addition, a VLAN is actually a small broadcast domain; if the routing of a packet is not discovered, a switch transmits this packet only to the other ports that belong to this VLAN other than to all ports of the switch. Therefore, the packet forwarding is restricted to a specific VLAN, which also improves network utilization to a certain degree. l
Issue 05 (2010-10-30)
Isolating users and improving network security

18 VLAN
The packets of a VLAN are forwarded only within the range of this VLAN, and are not forwarded to the network devices of the other VLAN users. Therefore, using VLANs can isolate different users and can protect the privacy of user information. l Achieving virtual workgroups The final goal of using VLANs is to establish a virtual workgroup model, that is, to establish a dynamic organization environment. This enables the members of the same VLAN to communicate with each other as if they were on the same VLAN, even when they move to other positions of the network. In addition, the broadcast packets are restricted to this VLAN without affecting the members of other VLANs. If the network location of one member changes but the VLAN that the member belongs to does not change, the configuration of this member need not be changed. If the physical location of one member does not change but the VLAN that the member belongs to changes, a network administrator only needs to modify the configuration of this member. Achieving virtual workgroups is a long-term goal, which requires support in other aspects.
18.2 Basic Concepts

This section describes the basic concepts associated with VLANs. 18.2.1 Frame Format To implement the VLAN function, IEEE 802.1q defines a type of Ethernet frame that contains VLAN information, namely, the tagged frame. The tagged frame is also called the 802.1q frame. Compared with a common Ethernet frame, this type of frame has a 4-byte 802.1q header. 18.2.2 TAG Attribute Based on different methods for processing tagged frames and untagged frames, TAG attributes are classified into Tag Aware, Access, and Hybrid.
18.2.1 Frame Format

To implement the VLAN function, IEEE 802.1q defines a type of Ethernet frame that contains VLAN information, namely, the tagged frame. The tagged frame is also called the 802.1q frame. Compared with a common Ethernet frame, this type of frame has a 4-byte 802.1q header. Figure 18-2 shows the format of the tagged frame. Figure 18-2 Format of a tagged frame
Destination address Source address 4 bytes 802.1q header FCS (CRC-32)
Length/Type
Data
TCI TPID 16 bits PCP 3 bits CFI 1 bit VID 12 bits
18-4
Issue 05 (2010-10-30)
18 VLAN
The 4-byte 802.1q header is divided into two parts: tag protocol identifier (TPID) and tag control information (TCI). The TCI is divided into three parts: user_priority, canonical format indicator (CFI), and VLAN identifier (VID). l TPID A TPID is a 2-byte field, and it identifies an Ethernet frame as a tagged frame. The value is always 0x8100. When a tagged frame arrives at a network device that cannot identify the tagged frame, it is directly discarded. l PCP A priority code point (PCP) identifies the priority of an Ethernet frame. This field can be used to raise requirements for service quality. l CFI A CFI is a 1-bit field, and it is used in certain physical networks that adopt ring topologies. This field is not processed in the case of Ethernet networks. l VID A VLAN ID is a 12-bit field, and it indicates the VLAN that the frame belongs to. Restricted to the field length, the value of a VID ranges from 0 to 4095.
18.2.2 TAG Attribute

Based on different methods for processing tagged frames and untagged frames, TAG attributes are classified into Tag Aware, Access, and Hybrid. Table 18-1 provides the methods for an ingress port and an egress port to process Ethernet frames based on different TAG attributes. Table 18-1 Processing of data frames based on different TAG attributes Direction Type of Data Frame Tagged frame Untagged frame Processing Method Tag Aware Receives the frame. Discards the frame. Access Discards the frame. Receives the frame after it is added with a port VID (PVID). Transmits the frame after the VID is stripped. Hybrid Receives the frame. Receives the frame after it is added with a PVID. Transmits the frame after its PVID is stripped, if the VID is equal to the PVID. Directly transmits the frame, if the VID is not equal to the PVID.
Ingress port
Egress port
Tagged frame
Transmits the frame.
18 VLAN
NOTE
After being into a port, an untagged frame may be discarded or added with a PVID to form a tagged frame. Thus, the case that an untagged frame is transmitted out of port does not exist.
18.3 Specifications
This section provides the specifications of VLANs. Table 18-2 lists the specifications of VLANs. Table 18-2 Specifications of VLANs Item Specification EMS6 Range of VLAN IDs Number of EVPL services based on the VLAN Number of 802.1q bridges TAG attributea 1-4095 1024 1 Tag aware Access Hybrid Enabling of the ingress check VLAN transparent transmissionb VLAN switchingc Supported Supported Supported EFP6
NOTE
l a: On the OptiX RTN 620, the TAG attribute is valid only when Network Attributes of a port is set to UNI. l b: In VLAN transparent transmission, the VLAN ID of an Ethernet frame does not change when this frame is forwarded. l c: VLAN switching involves a process in which the VLAN ID of an Ethernet frame changes when this frame is forwarded. On the OptiX RTN 620, VLAN switching is implemented by performing QinQ operations.

This section describes the standards and protocols associated with VLANs. The following protocol is associated with VLANs: IEEE 802.1q: Virtual Bridged Local Area Networks
18 VLAN
18.5 Availability
This section describes the support required by the application of the VLAN feature and its dependency.

Table 18-3 Hardware and version support Feature VLAN Applicable Board EMS6 EFP6 Applicable Hardware Version All the versions All the versions Applicable Product Version V100R002 and later V100R005C00 and later
Feature Dependency
The dependency between the VLAN feature and other features is as follows: l l When the VLAN technology is used in the Layer 2 switching application, the 802.1q bridge is generated. QinQ is a Layer 2 tunnel protocol based on 802.1q encapsulation. In the QinQ application, the packet carries two-layer VLAN tags.
18.6 Principles
Implementation of the VLAN feature is relevant to the port attribute and service type. When the VLAN feature is enabled, the Ethernet switching unit processes a data frame as follows: 1. 2. Processes the data frame that is transmitted into the switch through a certain port, based on the attribute of this port. For details, see Table 18-1. Forwards the data frame based on the service type. l In the case of the private line service, the Ethernet switching unit forwards the frame to the corresponding ports based on the service configuration. l In the case of the LAN service, the Ethernet switching unit forwards the data frame to the corresponding ports based on the MAC address table. For details, see 20.6 Principles in the Layer 2 switching feature. 3. Processes the data frame that is transmitted out of the switch through a certain port, based on the attribute of this port. For details, see Table 18-1.

Follow certain guidelines when you plan VLANs.
18 VLAN
Planning Guidelines on VLAN IDs

l l Allocate a unique VLAN ID for each user. If a user needs to transmit various services to different locations, allocate different VLAN IDs for each type of service.
Planning Guidelines on TAG Attributes

l l If all of the accessed services are tagged frames, set the TAG attributes of the ingress ports for these services to Tag Aware. If all of the accessed services are untagged frames, set the TAG attributes of the ingress ports for these services to Access and set the default VLAN IDs and VLAN priorities based on the network planning information. If the accessed services are a combination of tagged frames and untagged frames, set the TAG attributes of the ingress ports for these services to Hybrid and set the default VLAN IDs and VLAN priorities based on the network planning information.

Based on the VLAN planning information, configure an Ethernet service and set the TAG attribute of an Ethernet port.
18-8
Issue 05 (2010-10-30)
18 VLAN
Table 18-4 Procedures for configuring VLAN-based EVPL services Step 1 Operation Configuri ng Ethernet interfaces on Ethernet boards A.18.1 Configuri ng External Ethernet Ports Description l You need to set Basic Attributes. Set the parameters as follows: In the case of used interfaces, set Enabled/ Disabled to Enabled. In the case of unused interfaces, set Enabled/Disabled to Disabled. In the case of Ethernet interfaces that connect to external equipment, set Working Mode to be the same value as the external equipment (the working mode of the external equipment is generally auto-negotiation). In the case of Ethernet interfaces for connection within the network, it is recommended that you set Working Mode to Auto-Negotiation. When JUMBO frames are transmitted, set Maximum Frame Length according to the actual length of a JUMBO frame. Otherwise, it is recommended that Maximum Frame Length takes the default value. l Click the Flow Control tab if the flow control function is enabled on the external equipment to which the Ethernet interface is connected. Set the parameters as follows: When the external equipment uses the nonauto-negotiation flow control function, set Non-Autonegotiation Flow Control Mode to Enable Symmetric Flow Control. When the external equipment uses the autonegotiation flow control function, set Autonegotiation Flow Control Mode to Enable Symmetric Flow Control. l You need to set TAG Attributes. In the case of a VLAN-based EVPL service, set Entry Detection to Enabled. Set the other parameters according to the network planning information. l You need to set Network Attributes. In the case of a VLAN-based EVPL service, set Port Attributes in the Network Attributes tab page to UNI. l Determine whether to set Advanced Attributes according to actual requirements.
Issue 05 (2010-10-30)
18-9
18 VLAN
Step
Operation A.18.2 Configuri ng the Internal Port of the Ethernet Board
Description Required when internal interfaces need to be used. l You need to set TAG Attributes. In the case of a VLAN-based EVPL service, set Entry Detection to Enabled. l Determine whether to set Encapsulation/ Mapping according to actual requirements. It is recommended that all the relevant parameters take the default value. Ensure that the parameters are set to the same values at both ends of a link. l In the case of a VLAN-based EVPL service, it is recommended that you set Port Attributes in the Network Attributes tab page to UNI. l Determine whether to configure the LCAS function according to actual requirements. If the LCAS function is required, set Enabling LCAS to Enabled and set LCAS Modde according to the type of third-party equipment. In addition, it is recommended that the other parameters take the default values. Ensure that the parameters are set to the same values at both ends of a link. l You need to set Bound Path. Configure bound channels according to the service planning information.
NOTE On the OptiX RTN 620, the EMS6 and EFT4 are EoS Ethernet boards, which support VCTRUNKs that bind VC-12 or VC-3 channels. The EFP6 is an EoPDH Ethernet board, which supports VCTRUNKs that bind E1 channels. On the NMS, VCTRUNKs that bind E1 channels are displayed as VCTRUNKS that bind VC-12 channels.
l Determine whether to set Advanced Attributes according to actual requirements.
18-10
Issue 05 (2010-10-30)
18 VLAN
Step 2
Operation Configuri ng a LAG A.12.1 Creating a LAG
Description Required. Set the parameters as follows: l Set LAG Type to the same value as the opposite equipment. LAG Type is generally set to Static for the equipment at both ends. l Set Load Sharing to the same value as the opposite equipment. If the LAG is configured only to implement protection, it is recommended that you set Load Sharing to Non-Sharing for the equipment at both ends. If the LAG is configured to increase the bandwidth, it is recommended that you set Load Sharing to Sharing for the equipment at both ends. l When the IFH2 board is configured with 1+1 protection, set Load Sharing to Non-Sharing for the LAGs involved in 1+1 protection on the equipment at both ends. l Set Revertive Mode to the same value as the opposite equipment. Revertive Mode is generally set to the same value for the equipment at both ends. If LAGs are involved in 1+1 protection for the IFH2 board, set Revertive Mode to Non-Revertive. This parameter is valid to only LAGs whose Load Sharing is set to NonSharing. l Set Sharing Mode to the same value as the opposite equipment. Unless otherwise specified, this parameter takes the default value. This parameter is valid to only LAGs whose Load Sharing is set to Sharing. l It is recommended that you set LAG parameters to the same values for the main and slave interfaces of the LAGs at both ends. In this case, you can set System Priority according to actual requirements. It is recommended that this parameter takes the default value. This parameter is valid to only static LAGs. l Set Main Port and Selected Slave Ports according to the network planning information. It is recommended that you set this parameter to the same value for the main and slave interfaces of the LAGs at both ends. A.12.2 Setting the Port Priority Optional.
Issue 05 (2010-10-30)
18-11
18 VLAN
Step 3
Operation Creating VLANbased EVPL services A.19.1 Creating Ethernet Private Line Services
Description Required. Set the parameters as follows: l Set Service Type to EPL. l Set Direction to Bidirectional. l Set Source Port and Sink Port according to the network planning information. l Set Source C-VLAN(e.g.1,3-6) and Sink CVLAN(e.g.1,3-6) according to the network planning information. l If any VCTRUNK to which no paths are bound is used as Source Port or Sink Port, configure corresponding bound channels according to the service planning information.
Configuri ng the QoS
A.13.1 Creating a Flow
Required when you need to perform CAR or CoS operations. Before perform any CAR or CoS operations, you need to create flows. Set the relevant parameters according to the network planning information.
A.13.2 Creating the CAR A.13.3 Creating the CoS A.13.4 Binding the CAR/ CoS A.13.5 Configuri ng the Traffic Shaping for Egress Port Queues
Required when you need to perform CAR or CoS operations for a specific flow over a port. Set CAR or CoS parameters and bind the configured CAR or CoS to the corresponding flow according to the network planning information.
Required when you need to perform traffic shaping for the queues at a specific egress port. Set the relevant parameters according to the network planning information.
18-12
Issue 05 (2010-10-30)
18 VLAN
Step
Operation A.13.6 Configuri ng Port Shaping A.13.8 Configuri ng the Queue Schedulin g Mode
Description Required when you need to limit the egress bandwidth that an Ethernet service occupies. Set the relevant parameters according to the network planning information. Required if you need to perform queue scheduling over an egress port or limit the bandwidth of queues over an egress port. Set the relevant parameters according to the network planning information. Required in the case of the two NEs where the two Ethernet interfaces involved in the service test are located. Set the parameters as follows: l Set Maintenance Domain Name and Maintenance Level to the same values for the two NEs. l In the test of an Ethernet service between two edge nodes on the transport network, it is recommended that Maintenance Level takes the default value 4. In the test of an Ethernet service between two internal NEs on the transport network, set Maintenance Level to a value smaller than 4. In the test of an Ethernet service between two Ethernet interfaces on the same NE, set Maintenance Level to a value smaller than the value that is set in the test of an Ethernet service between two internal NEs on the transport network. A.14.2 Creating MAs Required in the case of the NEs where the two Ethernet interfaces involved in the service test are located. Set the parameters as follows: l Set Maintenance Domain Name to the value of Maintenance Domain Name that is set in the preceding step. l Set Maintenance Association Name to the same value for the two NEs.
Perform a LB test.
A.14.1 Creating MDs
Issue 05 (2010-10-30)
18-13
18 VLAN
Step
Operation A.14.3 Creating MPs
Description Required in the case of the NEs where the two Ethernet interfaces involved in the service test are located. Set the parameters as follows: l Set Maintenance Association Name to the value of Maintenance Association Name that is set in the preceding step. l Set Node to the Ethernet interfaces that are involved in the service test. l Set MP ID to different values for MEPs in the same maintenance domain. l If the OAM information initiated by the MEP travels through the packet switching unit on the local NE, set Direction of the MEP to Ingress. Otherwise, set Direction to Egress. l If the MP ID is used to identify an MEP, set CC Status to Active. l It is recommended that you set CCM Sending Period(ms) to 1000 ms. A.21.1 Testing Ethernet Services by Using the LB Function Required. The LB test result should show that no packet loss occurs.
18-14
Issue 05 (2010-10-30)
18 VLAN
Table 18-5 Procedure for configuring IEEE 802.1q bridge-based EVPLAN services Step 1 Operation Configuri ng Ethernet interfaces on Ethernet boards A.18.1 Configuri ng External Ethernet Ports Description l You need to set Basic Attributes. Set the parameters as follows: In the case of used interfaces, set Enabled/ Disabled to Enabled. In the case of unused interfaces, set Enabled/Disabled to Disabled. In the case of Ethernet interfaces that connect to external equipment, set Working Mode to be the same value as the external equipment (the working mode of the external equipment is generally auto-negotiation). In the case of Ethernet interfaces for connection within the network, it is recommended that you set Working Mode to Auto-Negotiation. When JUMBO frames are transmitted, set Maximum Frame Length according to the actual length of a JUMBO frame. Otherwise, it is recommended that Maximum Frame Length takes the default value. l Click the Flow Control tab if the flow control function is enabled on the external equipment to which the Ethernet interface is connected. Set the parameters as follows: When the external equipment uses the nonauto-negotiation flow control function, set Non-Autonegotiation Flow Control Mode to Enable Symmetric Flow Control. When the external equipment uses the autonegotiation flow control function, set Autonegotiation Flow Control Mode to Enable Symmetric Flow Control. l You need to set TAG Attributes. In the case of an IEEE 802.1q bridge-based EVPLAN service, set Port Attributes in the Network Attributes tab page to UNI. l To enable the port loop detection function or broadcast packet suppression function, you need to set Advanced Attributes. Set the relevant parameters according to the network planning information.
Issue 05 (2010-10-30)
18-15
18 VLAN
Step
Description Required when internal interfaces need to be used. l Determine whether to set Encapsulation/ Mapping according to actual requirements. It is recommended that all the relevant parameters take the default value. Ensure that the parameters are set to the same values at both ends of a link. l In the case of an IEEE 802.1q bridge-based EVPLAN service, set Port Attributes in the Network Attributes tab page to UNI. l Determine whether to configure the LCAS function according to actual requirements. If the LCAS function is required, set Enabling LCAS to Enabled and set LCAS Modde according to the type of third-party equipment. In addition, it is recommended that the other parameters take the default values. Ensure that the parameters are set to the same values at both ends of a link. l You need to set Bound Path. Configure bound channels according to the service planning information.
18-16
Issue 05 (2010-10-30)
18 VLAN
Step 2
Description Required if FE/GE interfaces are configured in a LAG for protection or if the IFH2 board is configured with 1+1 protection. Set the parameters as follows: l Set LAG Type to the same value as the opposite equipment. LAG Type is generally set to Static for the equipment at both ends. l In the case of FE/GE interfaces, set Load Sharing to the same value as the opposite equipment. If the LAG is configured only to implement protection, it is recommended that you set Load Sharing to Non-Sharing for the equipment at both ends. If the LAG is configured to increase the bandwidth, it is recommended that you set Load Sharing to Sharing for the equipment at both ends. l When the IFH2 board is configured with 1+1 protection, set Load Sharing to Non-Sharing for the LAGs involved in 1+1 protection on the equipment at both ends. l Set Revertive Mode to the same value as the opposite equipment. Revertive Mode is generally set to the same value for the equipment at both ends. If LAGs are involved in 1+1 protection for the IFH2 board, set Revertive Mode to Non-Revertive. This parameter is valid to only LAGs whose Load Sharing is set to NonSharing. l Set Sharing Mode to the same value as the opposite equipment. Unless otherwise specified, this parameter takes the default value. This parameter is valid to only LAGs whose Load Sharing is set to Sharing. l It is recommended that you set LAG parameters to the same values for the main and slave interfaces of the LAGs at both ends. In this case, you can set System Priority according to actual requirements. It is recommended that this parameter takes the default value. This parameter is valid to only static LAGs. l Set Main Port and Selected Slave Ports according to the network planning information. It is recommended that you set this parameter to the same value for the main and slave interfaces of the LAGs at both ends.
Issue 05 (2010-10-30)
18-17
18 VLAN
Step
Operation A.12.2 Setting the Port Priority
Description Optional.
Configuri ng ERPS protection
A.9.1 Creating ERPS Instances
Required if ERPS is configured. The main parameters are provided as follows: l Set ERPS ID, East Port, and West Port according to the network planning information. l When setting RPLOwner Ring Node Flag, note that an Ethernet ring has only one RPL owner. l When you set Control VLAN, pay attention to the following points: The value of Control VLAN must different from the VLAN ID carried by Ethernet service packets or the VLAN ID carried by inband DCN packets. Add Control VLAN to the VLAN filter table of an IEEE 802.1q bridge when you create EVPLAN services based on this bridge.
A.9.2 Setting Paramete rs of the Ethernet Ring Protocol 4 Creating IEEE 802.1q bridgebased EVPLAN services A.19.2 Creating Ethernet LAN Services
Required if the values of the default parameters of the ERPS timers need to be changed. Set Hold-Off Time(ms), Guard Time(ms), and WTR Time(min) according to actual requirements. Set these parameters to the same values for all the NEs on the network. Required. Set the parameters as follows: l Set VB Name according to the network planning information. l Set Bridge Type to 802.1q. l Set Mount Port according to the network planning information. l If any VCTRUNK to which no channels are bound is used as Mount Port, configure corresponding bound channels according to the service planning information.
NOTE On the OptiX RTN 620, the EMS6 and EFT4 are EoS Ethernet boards, which support VCTRUNKs that bind VC-12 or VC-3 channels. The EFP6 is an EoPDH Ethernet board, which supports VCTRUNKs that bind E1 channels. On the NMS, VCTRUNKs that bind E1 channels are displayed as VCTRUNKs that bind VC-12 channels.
18-18
Issue 05 (2010-10-30)
18 VLAN
Step 5
Operation A.19.4 Creating the VLAN Filtering Table
Description Required. Set VLAN ID(e.g;1,3-6) and Selected forwarding ports according to the network planning information. Required if you need to set certain MAC address entries not to age. Set the relevant parameters according to the network planning information.
Managing the MAC address table
A.20.1 Creating a Static MAC Address Entry A.20.2 Creating a Blacklist Entry of a MAC Address A.20.3 Setting the Aging Time of a MAC Address Table Entry
Required if you need to disable usage of EPLAN services on the host of certain MAC addresses. Set the relevant parameters according to the network planning information.
Required if you need to disable the aging function or change the aging time (five minutes by default). Set the relevant parameters according to the network planning information.
A.19.3 Modifying the Mounted Port of a Bridge Configuri ng the QoS A.13.1 Creating a Flow
Required if you need to change a port connected to a VB, enabled status of a port connected to a VB, or Hub/Spoke attribute of a port connected to a VB. Required when you need to perform CAR or CoS operations. Before performing any CAR or CoS operations, you need to create flows. Set the relevant parameters according to the network planning information.
A.13.2 Creating the CAR A.13.3 Creating the CoS A.13.4 Binding the CAR/ CoS
Issue 05 (2010-10-30)
18-19
18 VLAN
Step
Operation A.13.5 Configuri ng the Traffic Shaping for Egress Port Queues A.13.6 Configuri ng Port Shaping A.13.8 Configuri ng the Queue Schedulin g Mode
Description Required when you need to perform traffic shaping for the queues at a specific egress port. Set the relevant parameters according to the network planning information.
Required when you need to limit the egress bandwidth that an Ethernet service occupies. Set the relevant parameters according to the network planning information. Required if you need to perform queue scheduling over an egress port or limit the bandwidth of queues over an egress port. Set the relevant parameters according to the network planning information. Required in the case of the NEs where the two Ethernet interfaces involved in the service test are located. Set the parameters as follows: l Set Maintenance Domain Name and Maintenance Level to the same values for the two NEs. l In the test of an Ethernet service between two edge nodes on the transport network, it is recommended that Maintenance Level takes the default value 4. In the test of an Ethernet service between two internal NEs on the transport network, set Maintenance Level to a value smaller than 4. In the test of an Ethernet service between two Ethernet interfaces on the same NE, set Maintenance Level to a value smaller than the value that is set in the test of an Ethernet service between two internal NEs on the transport network.
Perform a LB test
A.14.1 Creating MDs
A.14.2 Creating MAs
Required in the case of the NEs where the two Ethernet interfaces involved in the service test are located. Set the parameters as follows: l Set Maintenance Domain Name to the value of Maintenance Domain Name that is set in the preceding step. l Set Maintenance Association Name to the same value the two NEs. l Set Relevant Service to the same service for the two NEs.
18-20
Issue 05 (2010-10-30)
18 VLAN
Step

This section uses an example to describe how to plan and configure an Ethernet service based on the VLAN according to the network conditions. l For details on the configuration example of an Ethernet private line service based on the VLAN, see Configuration Example (VLAN-Based EVPL Services) in the Configuration Guide. For details on the configuration example of an Ethernet switching service based on the VLAN, see Configuration Example (IEEE 802.1q Bridge-Based EVPLAN Services) in the Configuration Guide.

This section provides the hyperlinks of the operation tasks associated with VLANs.
Related Tasks
A.18.1 Configuring External Ethernet Ports
18 VLAN
A.18.2 Configuring the Internal Port of the Ethernet Board A.19.1 Creating Ethernet Private Line Services A.19.2 Creating Ethernet LAN Services A.19.3 Modifying the Mounted Port of a Bridge A.19.4 Creating the VLAN Filtering Table A.19.5 Creating QinQ Private Line Services A.19.6 Creating IEEE 802.1ad Bridge-Based EVPLAN Services

There are no alarms or performance events relevant to VLANs.
Relevant Alarms
None.
Relevant Events
None.
18.12 FAQs
This section provides the answers to the questions that are frequently raised when the VLAN feature is used. Q: Why should Encapsulation Type be set to 802.1Q or QINQbefore the VLAN feature is enabled? A: When Encapsulation Type is set to 802.1Q or QINQ, the Ethernet switching board can check the VLAN tag based on the TAG attribute. Q: What is the relationship between the VLAN, C-VLAN, and S-VLAN? A: The C-VLAN and S-VLAN are concepts that are used in the QinQ service. A C-VLAN refers to a client-side VLAN, and an S-VLAN refers to a service layer VLAN of carriers. The VLAN that is commonly referred to is equivalent to the C-VLAN in the case of the QinQ service.
18-22
Issue 05 (2010-10-30)
19 QinQ
19
About This Chapter
This chapter describes the QinQ (802.Q in 802.Q) feature. 19.1 Introduction This section provides the definition of QinQ and its purpose. 19.2 Basic Concepts This section describes the basic concepts associated with QinQ. 19.3 Specifications This section describes the specifications of QinQ. 19.4 Reference Standards and Protocols This section describes the standards and protocols associated with QinQ.
QinQ
19.5 Availability This section describes the support required by QinQ and dependency of the feature. 19.6 Principles The working principle of QinQ is closely related to service types. 19.7 Planning Guidelines Follow certain principles when you plan QinQ. 19.8 Configuration Procedure The configuration procedure of QinQ-based Ethernet services is closely associated with the types of Ethernet services. 19.9 Configuration Example This section uses examples to describe how to plan and configure QinQ-based Ethernet services according to the network conditions. 19.10 Task Collection This section provides the hyperlinks of the operation tasks associated with QinQ. 19.11 Relevant Alarms and Events No alarms or performance events are associated with QinQ. 19.12 FAQs
19 QinQ
This section provides answers to the questions that are frequently asked when the QinQ feature is used.
19-2
Issue 05 (2010-10-30)
19 QinQ
19.1 Introduction
This section provides the definition of QinQ and its purpose.
Definition
QinQ is a Layer 2 tunnel protocol based on IEEE 802.1q encapsulation. The QinQ technology encapsulates a private virtual local area network (VLAN) tag into a public VLAN tag. Therefore, the packets with two layers of VLAN tags can be transmitted on the backbone network of a carrier. In this manner, QinQ provides Layer 2 virtual private network (VPN) tunnels. Figure 19-1 shows the application of QinQ. Figure 19-1 Application of QinQ in EVPL services
C-VLAN1 NE1
Service network A NE2 NE3 S-VLAN3 C-VLAN1 S-VLAN4 C-VLAN1 S-VLAN1 C-VLAN1 S-VLAN2 C-VLAN1 Service network B NE4 C-VLAN1
C-VLAN1 S-VLAN1 C-VLAN1 S-VLAN2 C-VLAN1
Frame of customer a Frame of customer b C-VLAN1
Purpose
QinQ provides a Layer 2 VPN solution that is much cheaper and easier than multi-protocol label switch (MPLS). By using the VLAN QinQ technology, data packets carry two layers of VLAN tags to distinguish different services. This changes the limitation that only one VLAN tag is used to mark the data packets, and increases the number of VLAN IDs. The inner VLAN tag is called C-VLAN and used as the customer VLAN. The outer VLAN is called S-VLAN and used as the service provider VLAN. The major functions of the QinQ technology are as follows: l l l l With the application of the QinQ technology, the number of VLAN IDs can reach 4096 x 4096. This meets the increasing requirements for VLAN IDs. Customers and operators can plan VLAN resources independently and flexibly. Therefore, network configuration and maintenance is simplified. The QinQ technology replaces the MPLS technology to provide a cheaper and simpler Layer 2 VPN solution. The QinQ technology achieves the expansion of Ethernet services from local area networks (LANs) to wide area networks (WANs).
Issue 05 (2010-10-30)
19 QinQ
19.2 Basic Concepts

This section describes the basic concepts associated with QinQ. 19.2.1 Frame Format The QinQ technology defines three types of Ethernet frames: Ethernet frame with only a CTAG, Ethernet frame with a C-TAG and an S-TAG, and Ethernet frame with only an S-TAG. 19.2.2 Network Attributes The network attribute of each Ethernet port can be set to UNI, C-Aware, or S-Aware, depending on how the port processes C-TAGs and S-TAGs. 19.2.3 Application of the QinQ Technology in Private Line Services When used for private line services, QinQ can process VLAN tags in different manners as required. 19.2.4 Application of the QinQ Technology in 802.1ad Bridge Services When used for 802.1ad bridge services, QinQ can process VLAN tags in different manners as required.
19.2.1 Frame Format

The QinQ technology defines three types of Ethernet frames: Ethernet frame with only a CTAG, Ethernet frame with a C-TAG and an S-TAG, and Ethernet frame with only an S-TAG.
Ethernet Frame with Only a C-TAG

The Ethernet frame with only a C-TAG has the same format as the tagged frame defined in IEEE 802.1q. Therefore, the tagged frame defined in IEEE 802.1Q is an Ethernet frame that contains a C-VLAN tag. For details on the format of a tagged frame, see Format of the tagged frame. Figure 19-2 Format of the Ethernet frame with only a C-TAG
4 bytes Destination address Source address C-TAG Length/Type Data FCS (CRC-32)
TCI TPID 16 bits PCP 3 bits CFI 1 bit VID 12 bits
Ethernet Frame with a C-TAG and an S-TAG

In the case of an Ethernet frame that contains a C-TAG and an S-TAG, the S-TAG is added before the C-TAG. The differences between the S-TAG and the C-TAG are as follows: l
19-4
The TPID is different.

19 QinQ
As defined in IEEE 802.1ad, the TPID in the S-TAG is 0x88a8, whereas the TPID in the C-TAG is 0x8100. l The drop eligible indicator (DEI) replaces the CFI. The DEI works with the PCP to indicate the priority of the S-TAG. Figure 19-3 Format of the Ethernet frame with a C-TAG and an S-TAG
4 bytes Destination address Source address S-TAG C-TAG Length/Type Data FCS (CRC-32)
TCI TPID 16 bits PCP 3 bits DEI 1 bit VID 12 bits
Ethernet Frame with Only an S-TAG

The Ethernet frame with only an S-TAG contains only an S-TAG and does not contain any CTAG. Figure 19-4 Format of the Ethernet frame with only an S-TAG
4 bytes Destination address Source address S-TAG Length/Type Data FCS (CRC-32)
TCI TPID 16 bits PCP 3 bits DEI 1 bit VID 12 bits
19.2.2 Network Attributes

The network attribute of each Ethernet port can be set to UNI, C-Aware, or S-Aware, depending on how the port processes C-TAGs and S-TAGs.
UNI Port
A UNI port verifies and processes the outer tag of an Ethernet frame according to the TAG attribute of the port. UNI ports cannot be used in the case of QinQ services.
19 QinQ
C-Aware Port
A C-Aware port considers that an accessed packet does not contain an S-TAG. C-Aware ports can be used in the case of QinQ services.
NOTE
l C-TAG frames and untagged frames can normally enter and exit C-aware ports. l When an S-TAG frame enters and exits a C-Aware port, the port processes the S-TAG as a C-TAG. l When a frame that contains an S-TAG and a C-TAG enters and exits a C-Aware port, the port processes the S-TAG as a C-TAG and does not process the inner C-TAG.
S-Aware Port
An S-Aware port considers that an accessed packet contains an S-TAG. S-Aware ports can be used in the case of QinQ services.
NOTE
l S-TAG frames or the frames that contain an S-TAG and a C-TAG can normally enter and exit S-Aware ports. l When a C-TAG frame enters and exits an S-Aware port, the port processes the C-TAG frame as an S-TAG frame. l When an untagged frame enters an S-aware port, the port discards the frame.
19.2.3 Application of the QinQ Technology in Private Line Services

When used for private line services, QinQ can process VLAN tags in different manners as required. In the case of the OptiX RTN 620, QinQ can perform the following VLAN tag operations for private line services: l l l l l l l Transparently transmitting C-VLAN tags Adding S-VLAN tags Stripping S-VLAN tags Transparently transmitting S-VLAN tags Switching S-VLAN tags Transparently transmit S-VLAN and C-VLAN Translate S-VLAN and transparently transmit C-VLAN
The following part explains the operations in an application scenario wherein QinQ is used for private line services.
Private Line Services Between C-Aware Ports

Two VLAN tag operations can be performed for the private line services between C-Aware ports.
19-6
Issue 05 (2010-10-30)
19 QinQ
Table 19-1 Private line services between C-Aware ports Type of Packet (Type of Source Port) PORT+C-VLAN (CAware port) Operation Type Direction Description
Transparently transmitting CVLAN tags
Unidirectional/ Bidirectional
Packets are transparently transmitted according to CVLANs Packets are transparently transmitted.
PORT (C-Aware port)
Transparently transmitting CVLAN tags
Private Line Services Between a C-Aware Port and an S-Aware Port

Three VLAN tag operations can be performed for the private line services between a C-Aware port and an S-Aware port. Table 19-2 Private line services between a C-aware port and an S-aware port Type of Packet (Type of Source Port) PORT+CVLAN (CAware port) Operation Type Direction Description
Adding SVLAN tags
Unidirectional
Packets are transmitted according to C-VLAN tags and one S-VLAN tag is added to each packet. In the case of the services from a CAware port to an S-Aware port, the port transmits the packets according to C-VLAN tags and adds an SVLAN tag to each packet. In the case of the services from an S-aware port to a C-Aware port, the port transmits the packets according to C-VLAN tags and strips the SVLAN tag from each packet.
Bidirectional
PORT (CAware port)
Adding SVLAN tags
Unidirectional
Packets are transmitted and an SVLAN tag is added to each packet.
Issue 05 (2010-10-30)
19-7
19 QinQ
Type of Packet (Type of Source Port)
Operation Type
Direction
Description
Bidirectional
In the case of the services from a CAware port to an S-Aware port, the port adds an S-VLAN tag to each packet. In the case of the services from an S-aware port to a C-aware port, the port strips the S-VLAN tag from each packet.
PORT+SVLAN (SAware port) PORT+CVLAN+SVLAN (SAware port)
Stripping SVLAN tags Stripping SVLAN tags
Unidirectional
Packets are transmitted according to S-VLAN tags and the S-VLAN tag is stripped from each packet. Packets are transmitted according to S-VLAN tags and C-VLAN tags. S-VLAN tag is stripped from each packet.
Unidirectional
NOTE
When QinQ adds S-VLAN tags, the priorities of S-VLAN tags can be inherited from C-VLAN tags or be manually specified.
Private Line Services Between S-Aware Ports

Two VLAN tag operations can be performed for the private line services between S-Aware ports. Table 19-3 Private line services between S-Aware ports Type of Packet (Type of Source Port) PORT+S-VLAN (SAware port) Operation Type Direction Description
Transparently transmitting SVLAN tags
Packets are transparently transmitted according to SVLAN tags. Packets are transmitted according to SVLAN tags. SVLAN IDs are changed.
PORT+S-VLAN (SAware port)
Switching S-VLAN tags
19-8
Issue 05 (2010-10-30)
19 QinQ
Type of Packet (Type of Source Port) PORT
Operation Type
Direction
Description
Transparently transmit S-VLAN and C-VLAN Transparently transmit S-VLAN and C-VLAN
Unidirectional/ Bidirectional Unidirectional/ Bidirectional
Packets are transparently transmitted. Packets are transparently transmitted according to SVLAN tags and CVLAN tags. Packets are transmitted according to SVLAN tags and CVLAN tags. SVLAN IDs are changed.
PORT+C-VLAN+SVLAN (S-Aware port)
PORT+C-VLAN+SVLAN (S-Aware port)
Translate S-VLAN and transparently transmit C-VLAN
19.2.4 Application of the QinQ Technology in 802.1ad Bridge Services

When used for 802.1ad bridge services, QinQ can process VLAN tags in different manners as required. The ports that are mounted to the 802.1ad bridge support the following four VLAN tag operations: l l l l Add S-VLAN based for Port Add S-VLAN based for Port and C-VLAN Mount Port Mount Port and base for Port and S-VLAN
VLAN Tag Operations of C-Aware Ports

Table 19-4 lists the VLAN tag operations of the C-Aware ports that are mounted to the 802.1ad bridge.
Issue 05 (2010-10-30)
19-9
19 QinQ
Table 19-4 VLAN tag operations of C-Aware ports Type of Services PORT Operation Type Add S-VLAN based for Port Direction Ingress Description 1. When data frames enter the bridge through a C-Aware port, the port adds the planned SVLAN tags to the data frames. 2. After the data frames enter the bridge, they are forwarded according to the MAC address table. Egress When the data frames leave the bridge through a C-Aware port, the port strips S-VLAN tags. 1. Entry detection is performed for data frames according to CVLAN tags. 2. S-VLAN tags are added to the data frames according to the mapping relationship between the C-VLAN tags of the data frames and S-VLAN tags(a). If the mapping relation does not exist, the data frames are discarded. 3. After the data frames enter the bridge, they are forwarded according to the S-VLAN filter table. Egress When the data frames leave the bridge through a C-aware port, the port strips S-VLAN tags.
PORT+CVLAN
Add S-VLAN based for Port and C-VLAN
Ingress
NOTE
a: l When QinQ adds S-VLAN tags, the priorities of S-VLAN tags can be inherited from C-VLAN tags or be manually specified. l One C-Aware port can add different S-VLAN tags to the packets with different C-VLAN tags.
VLAN Tag Operations of S-Aware Ports

Table 19-5 lists the VLAN tag operations of the S-Aware ports that are mounted to the 802.1ad bridge.
19-10
Issue 05 (2010-10-30)
19 QinQ
Table 19-5 VLAN tag operations of S-Aware ports Type of Services PORT Operation Type Mount Port Direction Ingress Description 1. The data frames that enter the bridge through an S-Aware port are not filtered. 2. After the data frames enter the bridge, they are forwarded according to the MAC address table. Egress When the data frames leave the bridge through an S-Aware port, they are transparently transmitted. 1. An S-Aware port filters the incoming data frames according to the customized filtering condition. That is, the frame that carries an S-VLAN tag different from the specified S-VLAN tag is discarded. 2. After the data frames enter the bridge, they are forwarded according to the S-VLAN filter table. Egress When the data frames leave the bridge through an S-Aware port, they are transparently transmitted.
PORT+SVLAN
Mount Port and base for Port and S-VLAN
Ingress
19.3 Specifications
This section describes the specifications of QinQ. Table 19-6 lists the specifications of QinQ. Table 19-6 Specifications of QinQ Item Specification EMS6 Setting of the QinQ type fielda EFP6
Supported, with a default value of 0x8100

NOTE The equipment supports the setting of the QinQ type field only based on the board. The equipment does not support the setting of the QinQ type field based on the port.
Range of S-VLAN IDs

Issue 05 (2010-10-30)
1-4095
19-11
19 QinQ
Item
Specification EMS6 EFP6
Number of QinQ-based EVPL services Number of QinQ-based EVPLAN services Network attribute
1024 1 UNI C-Aware S-Aware
QinQ operation type (QinQbased EVPL services)
Transparently transmitting C-VLAN tags Adding S-VLAN tags Stripping S-VLAN tags Transparently transmitting S-VLAN tags Switching S-VLAN tags
Transparently transmitting C-VLAN tags Adding S-VLAN tags Stripping S-VLAN tags Transparently transmitting S-VLAN tags Switching S-VLAN tags Transparently transmit SVLAN and C-VLAN Translate S-VLAN and transparently transmit CVLAN
QinQ operation type (QinQbased EVPLAN services)
Add S-VLAN base for Port Add S-VLAN base for Port and C-VLAN Mount Port Mount Port and base for Port and S-VLAN

This section describes the standards and protocols associated with QinQ. The following protocols are associated with QinQ: l l IEEE 802.1q: Virtual Bridged Local Area Networks IEEE 802.1ad: Virtual Bridged Local Area Networks Amendment 4: Provider Bridges
19.5 Availability
This section describes the support required by QinQ and dependency of the feature.
19-12
Issue 05 (2010-10-30)
19 QinQ

Table 19-7 Hardware and version support Feature EVPL (QinQ) Applicable Board EMS6 EFP6 EVPLAN (802.1ad bridge) EMS6 EFP6 Applicable Hardware Version All the versions All the versions All the versions All the versions Applicable Product Version V100R002 and latera V100R005C00 and later V100R003 and later V100R004C00 and later
NOTE
a: The V100R003 and an earlier version only support the priorities of S-VLAN tags that are manually specified. The V100R005 and a later version support the priorities of S-VLAN tags that are inherited from C-VLAN tags or manually specified.
Feature Dependency
The dependency between the QinQ feature and other features is as follows: The QinQ-based Ethernet LAN services depends on the 802.1ad bridge.
19.6 Principles
The working principle of QinQ is closely related to service types.
Working Principle of QinQ in Ethernet Private Line Services

This section uses EVPL (QinQ) services illustrated in Figure 19-5 to describe how data frames are processed on a QinQ network. Figure 19-5 EVPL (QinQ) services
C-VLAN1 NE1
Service network A NE2 NE3 S-VLAN3 C-VLAN1 S-VLAN4 C-VLAN1 S-VLAN1 C-VLAN1 S-VLAN2 C-VLAN1 Service network B NE4 C-VLAN1
C-VLAN1 S-VLAN1 C-VLAN1 S-VLAN2 C-VLAN1
Frame of customer a Frame of customer b C-VLAN1
Issue 05 (2010-10-30)
19-13
19 QinQ
On the network, the data frames from NE1 to NE4 are processed as follows: 1. NE1 adds an S-TAG to each data frame from customer a and customer b that are connected to NE1, and forwards the frames to NE2. NE1 adds an S-VLAN1 tag to each data frame from customer a and an S-VLAN2 tag to each frame from customer b. Based on S-VLAN tags, NE2 transparently transmits the data frames of customer a and customer b to NE3 on service network B. Because service provider B plans different S-VLAN tags for customer a and customer b, NE3 translates the data frame that contains an S-VLAN1 tag into a data frame that contains an S-VLAN3 tag, translates the data frame that contains an S-VLAN2 tag into a data frame that contains an S-VLAN4 tag, and forwards the data frames to NE4. NE4 removes the S-VLAN3 tag and S-VLAN4 tag, and forwards the data frames to the Ethernet ports of customer a and customer b.
2. 3.
4.
The data frame process from NE4 to NE1 is reverse to the preceding process.
Working Principle of QinQ in Ethernet LAN Services

This section uses EVPLAN (802.1ad bridge) services illustrated in Figure 19-6 to describe how data frames are processed on the 802.1ad bridge. Figure 19-6 EVPLAN (802.1ad Bridge) Service Example
NodeB 1 VoIP
VCTRUNK1 PORT1 PORT1
Service C-VLAN 10 VoIP 20 HSI
NE1 NodeB 2
HSI
PORT2
NE3
VCTRUNK2
PORT1
NE2
NE3:EMS6 S-VLAN 100 PORT1 VoIP S-VLAN 200 PORT2 HSI VCTRUNK1 NE1
Service C-VLAN VoIP 30 HSI 40
PORT1
NodeB 1
VCTRUNK2
NE2 PORT1
NodeB 2
802.1ad bridge PORT Strip S-VLAN Label C-VLAN(10/30) Data(VoIP) C-VLAN(20/40) Data(HSI) Add S-VLAN Label S-VLAN(100) S-VLAN(200) C-VLAN(10/30) C-VLAN(20/40) Data(VoIP) Data(HSI) VCTRUNK Strip S-VLAN Label C-VLAN(10/30) Data(VoIP) C-VLAN(20/40) Data(HSI)
19-14
Issue 05 (2010-10-30)
19 QinQ
As shown in Figure 19-6, the transmission network needs to carry voice over IP (VoIP) services and high speed Internet (HSI) services. VoIP services and HSI services are accessed by NodeB 1 and NodeB 2. The two types of services use different C-VLAN tags as planned. On the network side, the convergence node NE3 adds S-VLAN tags to the services as planned so that NE3 can mark and schedule the two types of services in a unified manner. On the network, NE3 processes data frames as follows: 1. 2. 3. 4. VoIP services and HSI services are accessed by NodeB 1 and NodeB, and then transparently transmitted to NE3 through NE1 and NE2. NE3 adds S-VLAN tag 100 to the VoIP services of NodeB 1, NodeB 2, and VoIP server (with C-VLAN tags 10 and 30). NE3 adds S-VLAN tag 200 to the HSI services of NodeB 1, NodeB 2, and HSI server (with C-VLAN tags 20 and 40). On the 802.1ad bridge, the data frames with S-VLAN tags are switched to corresponding Ethernet ports as specified in the S-VLAN filter table. The Ethernet ports strip S-VLAN tags and transmit the data frames.

Follow certain principles when you plan QinQ.
Planning Guidelines of S-VLAN Tags

Follow these two principles when planning S-VLAN IDs: l l The S-VLAN ID allocated to each customer must be unique. If a customer has different types of services that need to be transmitted to different destinations, a unique S-VLAN ID must be allocated to each type of services.
Planning Guidelines of QinQ-based Ethernet Private Line Services

Follow these two principles when planning QinQ-based Ethernet private line services: l l l l l If packets need to be forwarded according to C-VLAN tags or C-VLAN tags need to be translated, select the private line services between C-Aware ports. If S-VLAN tags need to be added or stripped, select the private line services between a CAware port and an S-Aware port. If packets need to be forwarded according to S-VLAN tags or S-VLAN tags need to be translated, select the private line services between S-Aware ports. Check whether operations need to be performed based on PORT, PORT+C-VLAN, or PORT+S-VLAN. Check whether unidirectional operations or bidirectional operations are required.
Planning Guidelines of QinQ-based Ethernet LAN Services

Follow these two principles when planning QinQ-based Ethernet LAN services: l If the packets that enter the port do not contain a VLAN tag or contain a C-VLAN tag, plan the network attribute of the port as "C-Aware".
Issue 05 (2010-10-30)
19 QinQ
l l l
If the packets that enter the port contain an S-VLAN tag, plan the network attribute of the port as "S-Aware". In the case of a C-Aware port, select "Add S-VLAN Base for Port" or "Add S-VLAN Base for Port and C-VLAN" as required. In the case of an S-Aware port, select "Mount Port" or "Mount Port and Base for Port and S-VLAN" as required.
In the case of the OptiX RTN 620, follow these three principles when planning QinQ: l l QinQ private line services are mainly used as point-to-point Ethernet services that are transparently transmitted over one hop of radio link. When multiple point-to-point Ethernet services are transparently transmitted over one hop of radio link, the S-VLAN ID of each Ethernet service must be unique.

The configuration procedure of QinQ-based Ethernet services is closely associated with the types of Ethernet services. The following table describes the configuration procedure of QinQ-based Ethernet private line services.
19-16
Issue 05 (2010-10-30)
19 QinQ
Table 19-8 Procedures for configuring QinQ-based EVPL services Step 1 Operation Configuri ng Ethernet interfaces on Ethernet boards A.18.1 Configuri ng External Ethernet Ports Description l You need to set Basic Attributes. Set the parameters as follows: In the case of used interfaces, set Enabled/ Disabled to Enabled. In the case of unused interfaces, set Enabled/Disabled to Disabled. In the case of Ethernet interfaces that connect to external equipment, set Working Mode to be the same value as the external equipment (the working mode of the external equipment is generally auto-negotiation). In the case of Ethernet interfaces for connection within the network, it is recommended that you set Working Mode to Auto-Negotiation. When JUMBO frames are transmitted, set Maximum Frame Length according to the actual length of a JUMBO frame. Otherwise, it is recommended that Maximum Frame Length takes the default value. l Click the Flow Control tab if the flow control function is enabled on the external equipment to which the Ethernet interface is connected. Set the parameters as follows: When the external equipment uses the nonauto-negotiation flow control function, set Non-Autonegotiation Flow Control Mode to Enable Symmetric Flow Control. When the external equipment uses the autonegotiation flow control function, set Autonegotiation Flow Control Mode to Enable Symmetric Flow Control. l You need to set Network Attributes. In the case of a QinQ-based EVPL service, set Port Attributes in the Network Attributes tab page to C-Aware or S-Aware. l Determine whether to set Advanced Attributes according to actual requirements.
Issue 05 (2010-10-30)
19-17
19 QinQ
Step
Description Required when internal interfaces need to be used. l Determine whether to set Encapsulation/ Mapping according to actual requirements. It is recommended that all the relevant parameters take the default value. Ensure that the parameters are set to the same values at both ends of a link. l In the case of a QinQ-based EVPL service, set Port Attributes in the Network Attributes tab page to C-Aware or S-Aware. l Determine whether to configure the LCAS function according to actual requirements. If the LCAS function is required, set Enabling LCAS to Enabled and set LCAS Modde according to the type of third-party equipment. In addition, it is recommended that the other parameters take the default values. Ensure that the parameters are set to the same values at both ends of a link. l You need to set Bound Path. Configure bound channels according to the service planning information.
19-18
Issue 05 (2010-10-30)
19 QinQ
Step 2
Description Required. Set the parameters as follows: l Set LAG Type to the same value as the opposite equipment. LAG Type is generally set to Static for the equipment at both ends. l Set Load Sharing to the same value as the opposite equipment. If the LAG is configured only to implement protection, it is recommended that you set Load Sharing to Non-Sharing for the equipment at both ends. If the LAG is configured to increase the bandwidth, it is recommended that you set Load Sharing to Sharing for the equipment at both ends. l When the IFH2 board is configured with 1+1 protection, set Load Sharing to Non-Sharing for the LAGs involved in 1+1 protection on the equipment at both ends. l Set Revertive Mode to the same value as the opposite equipment. Revertive Mode is generally set to the same value for the equipment at both ends. If LAGs are involved in 1+1 protection for the IFH2 board, set Revertive Mode to Non-Revertive. This parameter is valid to only LAGs whose Load Sharing is set to NonSharing. l Set Sharing Mode to the same value as the opposite equipment. Unless otherwise specified, this parameter takes the default value. This parameter is valid to only LAGs whose Load Sharing is set to Sharing. l It is recommended that you set LAG parameters to the same values for the main and slave interfaces of the LAGs at both ends. In this case, you can set System Priority according to actual requirements. It is recommended that this parameter takes the default value. This parameter is valid to only static LAGs. l Set Main Port and Selected Slave Ports according to the network planning information. It is recommended that you set this parameter to the same value for the main and slave interfaces of the LAGs at both ends. A.12.2 Setting the Port Priority Optional.
Issue 05 (2010-10-30)
19-19
19 QinQ
Step 3
Operation Creating QinQbased EVPL services A.19.1 Creating Ethernet Private Line Services
Description Required. Set the parameters as follows: l Set Service Type to EVPL (QinQ). l Set Direction to Bidirectional. l Set Operation Type, Source Port, Source CVLAN(e.g.1,3-6), Source S-VLAN, Sink Port, Sink C-VLAN(e.g.1,3-6), Sink S-VLAN, CVLAN Priority and S-VLAN Priority according to the network planning information. l If any VCTRUNK to which no paths are bound is used as Source Port or Sink Port, configure corresponding bound channels according to the service planning information.
Configuri ng the QoS
Required when you need to perform CAR or CoS operations. Before perform any CAR or CoS operations, you need to create flows. Set the relevant parameters according to the network planning information.
A.13.2 Creating the CAR A.13.3 Creating the CoS A.13.4 Binding the CAR/ CoS A.13.5 Configuri ng the Traffic Shaping for Egress Port Queues
Required when you need to perform traffic shaping for the queues at a specific egress port. Set the relevant parameters according to the network planning information.
19-20
Issue 05 (2010-10-30)
19 QinQ
Step
Operation A.13.6 Configuri ng Port Shaping A.13.8 Configuri ng the Queue Schedulin g Mode
Description Required when you need to limit the egress bandwidth that an Ethernet service occupies. Set the relevant parameters according to the network planning information. Required if you need to perform queue scheduling over an egress port or limit the bandwidth of queues over an egress port. Set the relevant parameters according to the network planning information. Required in the case of the two NEs where the two Ethernet interfaces involved in the service test are located. Set the parameters as follows: l Set Maintenance Domain Name and Maintenance Level to the same values for the two NEs. l In the test of an Ethernet service between two edge nodes on the transport network, it is recommended that Maintenance Level takes the default value 4. In the test of an Ethernet service between two internal NEs on the transport network, set Maintenance Level to a value smaller than 4. In the test of an Ethernet service between two Ethernet interfaces on the same NE, set Maintenance Level to a value smaller than the value that is set in the test of an Ethernet service between two internal NEs on the transport network. A.14.2 Creating MAs Required in the case of the NEs where the two Ethernet interfaces involved in the service test are located. Set the parameters as follows: l Set Maintenance Domain Name to the value of Maintenance Domain Name that is set in the preceding step. l Set Maintenance Association Name to the same value for the two NEs.
Perform a LB test.
A.14.1 Creating MDs
Issue 05 (2010-10-30)
19-21
19 QinQ
Step
The following table describes the configuration procedure of QinQ-based Ethernet LAN services.
19-22
Issue 05 (2010-10-30)
19 QinQ
Table 19-9 Procedure for configuring IEEE 802.1ad bridge-based EVPLAN services Step 1 Operation Configuri ng Ethernet interfaces on Ethernet boards A.18.1 Configuri ng External Ethernet Ports Description l You need to set Basic Attributes. Set the parameters as follows: In the case of used interfaces, set Enabled/ Disabled to Enabled. In the case of unused interfaces, set Enabled/Disabled to Disabled. In the case of Ethernet interfaces that connect to external equipment, set Working Mode to be the same value as the external equipment (the working mode of the external equipment is generally auto-negotiation). In the case of Ethernet interfaces for connection within the network, it is recommended that you set Working Mode to Auto-Negotiation. When JUMBO frames are transmitted, set Maximum Frame Length according to the actual length of a JUMBO frame. Otherwise, it is recommended that Maximum Frame Length takes the default value. l Click the Flow Control tab if the flow control function is enabled on the external equipment to which the Ethernet interface is connected. Set the parameters as follows: When the external equipment uses the nonauto-negotiation flow control function, set Non-Autonegotiation Flow Control Mode to Enable Symmetric Flow Control. When the external equipment uses the autonegotiation flow control function, set Autonegotiation Flow Control Mode to Enable Symmetric Flow Control. l You need to set TAG Attributes. In the case of an IEEE 802.1ad bridge-based EVPLAN service, set Port Attributes in the Network Attributes tab page to C-Aware or S-Aware.
NOTE When an Ethernet frame enters the IEEE 802.1ad bridge through a port whose network attribute is CAware, a specific S-TAG is added to the Ethernet frame. When an Ethernet frame exits the IEEE 802.1ad bridge through a port whose network attribute is CAware, a specific S-TAG is stripped from the Ethernet frame.
l You need to set Bound Path. Configure bound channels according to the service planning information.
Issue 05 (2010-10-30)
19-23
19 QinQ
Step
Operation
Description
l To enable the port loop detection function or broadcast packet suppression function, you need to set Advanced Attributes. Set the relevant parameters according to the network planning information. A.18.2 Configuri ng the Internal Port of the Ethernet Board Required when internal interfaces need to be used. l Determine whether to set Encapsulation/ Mapping according to actual requirements. It is recommended that all the relevant parameters take the default value. Ensure that the parameters are set to the same values at both ends of a link. l In the case of an IEEE 802.1ad bridge-based EVPLAN service, set Port Attributes in the Network Attributes tab page to C-Aware or SAware.
l Determine whether to configure the LCAS function according to actual requirements. If the LCAS function is required, set Enabling LCAS to Enabled and set LCAS Modde according to the type of third-party equipment. In addition, it is recommended that the other parameters take the default values. Ensure that the parameters are set to the same values at both ends of a link. l Determine whether to set Advanced Attributes according to actual requirements.
19-24
Issue 05 (2010-10-30)
19 QinQ
Step 2
Issue 05 (2010-10-30)
19-25
19 QinQ
Step
Required if ERPS is configured. The main parameters are provided as follows: l Set ERPS ID, East Port, and West Port according to the network planning information. l When setting RPLOwner Ring Node Flag, note that an Ethernet ring has only one RPL owner. l When you set Control VLAN, pay attention to the following points: The value of Control VLAN must be different from the VLAN ID carried by Ethernet service packets or the VLAN ID carried by inband DCN packets.
A.9.2 Setting Paramete rs of the Ethernet Ring Protocol 4 Creating IEEE 802.1ad bridgebased EVPLAN services A.19.6 Creating IEEE 802.1ad BridgeBased EVPLAN Services
Required if the values of the default parameters of the ERPS timers need to be changed. Set Hold-Off Time(ms), Guard Time(ms), and WTR Time(min) according to actual requirements. Set these parameters to the same values for all the NEs on the network. Required. Set the parameters as follows: l Set VB Name according to the network planning information. l Set Bridge Type to 802.1ad. l Set Mount Port according to the network planning information. l If any VCTRUNK to which no channels are bound is used as Mount Port, configure corresponding bound channels according to the service planning information.
A.19.4 Creating the VLAN Filtering Table
Required if Bridge Switching Mode is set to IVL/ Ingress Filter Enable. Set VLAN ID(e.g;1,3-6) and Selected forwarding ports according to the network planning information.
19-26
Issue 05 (2010-10-30)
19 QinQ
Step 6
Operation Managing the MAC address table A.20.1 Creating a Static MAC Address Entry A.20.2 Creating a Blacklist Entry of a MAC Address A.20.3 Setting the Aging Time of a MAC Address Table Entry
Description Required if you need to set certain MAC address entries not to age. Set the relevant parameters according to the network planning information.
Required if you need to perform CAR or CoS operations for a specific flow over a port. Set CAR or CoS parameters and bind the configured CARs or CoSes to the corresponding flows according to the network planning information.
Issue 05 (2010-10-30)
19-27
19 QinQ
Step
Description Required if you need to perform traffic shaping for the queues at a specific egress port. Set the relevant parameters according to the network planning information.
Required if you need to limit the egress bandwidth that an Ethernet service occupies. Set the relevant parameters according to the network planning information. Required if you need to perform queue scheduling over an egress port or limit the bandwidth of queues over an egress port. Set the relevant parameters according to the network planning information. Required in the case of the NEs where the two Ethernet interfaces involved in the service test are located. Set the parameters as follows: l Set Maintenance Domain Name and Maintenance Level to the same values for the two NEs. l In the test of an Ethernet service between two edge nodes on the transport network, it is recommended that Maintenance Level takes the default value 4. In the test of an Ethernet service between two internal NEs on the transport network, set Maintenance Level to a value smaller than 4. In the test of an Ethernet service between two Ethernet interfaces on the same NE, set Maintenance Level to a value smaller than the value that is set in the test of an Ethernet service between two internal NEs on the transport network.
Perform a LB test
A.14.1 Creating MDs
A.14.2 Creating MAs
19-28
Issue 05 (2010-10-30)
19 QinQ
Step

This section uses examples to describe how to plan and configure QinQ-based Ethernet services according to the network conditions. l l For details on the configuration example of a QinQ-based Ethernet private line service, see Configuration Example (QinQ-Based EVPL Services) in the Configuration Guide. For details on the configuration example of a QinQ-based Ethernet LAN service, see Configuration Example (IEEE 802.1ad Bridge-Based EVPLAN Services) in the Configuration Guide.

This section provides the hyperlinks of the operation tasks associated with QinQ.
Related Tasks
19 QinQ
A.18.2 Configuring the Internal Port of the Ethernet Board A.18.5 Modifying the Type Field of QinQ Frames A.19.5 Creating QinQ Private Line Services A.19.6 Creating IEEE 802.1ad Bridge-Based EVPLAN Services

No alarms or performance events are associated with QinQ.
Relevant Alarms
None.
Relevant Events
None.
19.12 FAQs
This section provides answers to the questions that are frequently asked when the QinQ feature is used. Q: Why does the interconnection of QinQ private line services with other types of equipment fail? A: Common causes are as follows: l The QinQ type field varies with the type of equipment. In the case of the OptiX RTN 620, the TPID in an S-TAG is 0x8100. In the case of other types of equipment, the TPID may adopt a different value, for example, 0x88a8. The standards for the QinQ feature are being developed. The principles for adding tags are different between various types of equipment.
Q: What is the relationship between the VLAN, C-VLAN, and S-VLAN? A: C-VLAN and S-VLAN are concepts that are used in QinQ services. C-VLAN refers to the VLAN on the client side, and S-VLAN refers to the VLAN at the service layer of carriers. Generally, a VLAN refers to the C-VLAN of QinQ services.
19-30
Issue 05 (2010-10-30)
20 Layer 2 Switching
20
About This Chapter
Layer 2 Switching
This chapter describes the Layer 2 switching feature. 20.1 Introduction This section provides the definition of Layer 2 switching and describes its purpose. 20.2 Basic Concepts This section describes the basic concepts related to Layer 2 switching. 20.3 Specifications This section describes the specifications of Layer 2 switching. 20.4 Reference Standards and Protocols This section describes the standards and protocols associated with Layer 2 switching. 20.5 Availability This section describes the support required by the application of the Layer 2 switching feature and its dependency. 20.6 Principles The key of Layer 2 switching is to forward Ethernet packets based on a MAC address table. 20.7 Planning Guidelines Follow certain guidelines when you plan Layer 2 switching. 20.8 Configuration Procedure Configuring Ethernet services based on Layer 2 switching involves configuring EPLAN and EVPLAN services. 20.9 Configuration Example This section uses an example to describe how to plan and configure Ethernet services based on Layer 2 switching according to the network conditions. 20.10 Task Collection This section provides the hyperlinks of the operation tasks associated with Layer 2 switching. 20.11 Relevant Alarms and Events There are no alarms or performance events relevant to Layer 2 switching.
20.12 FAQs This section provides the answers to the questions that are frequently raised when Layer 2 switching is used.
20-2
Issue 05 (2010-10-30)
20.1 Introduction
This section provides the definition of Layer 2 switching and describes its purpose.
Definition
On a LAN, a bridge or Layer 2 switch forwards Ethernet data based on a MAC address. The MAC address is a Layer 2 address in the OSI model. Thus, this data forwarding mode is called Layer 2 switching.
Purpose
In the case of Ethernet boards that have the Layer 2 switching capability, the switching domain can be divided into multiple independent sub-switching domains. In this manner, LAN services at multiple nodes can be isolated and dynamically shared. Figure 20-1 shows a typical application of Layer 2 switching. Company A has three departments located in different places, and Ethernet services of the three departments are transmitted to the transmission network through NE1, NE2, and NE3. The convergence node NE2 needs to perform Layer 2 switching for Ethernet services from the two access nodes NE1 and NE3, and NE1 and NE3 need not communicate with each other. Figure 20-1 Application of Layer 2 switching
PORT1 PORT2
Department 3
PORT1
PORT2
NE3
PORT1 PORT1 PORT2
PORT1 PORT1
PORT3
NE 1
Department 1 Access Point Bridge
NE 2
Department 2 Department of Company A
Issue 05 (2010-10-30)
20-3
20.2 Basic Concepts

This section describes the basic concepts related to Layer 2 switching. 20.2.1 Bridge A bridge refers to a functional unit that is used to connect two LANs or multiple LANs. 20.2.2 Hub/Spoke In the case of a convergence service, the mutual access between the non-central stations and central stations is required but the access between non-central stations is not required. In this case, specify a mounted port as a Hub port or a Spoke port. 20.2.3 Managing a MAC Address Table The entries in a MAC address table indicate the corresponding relationship between MAC addresses and ports. A MAC address table contains the following entries: dynamic entry, static entry, and blacklist entry.
20.2.1 Bridge
A bridge refers to a functional unit that is used to connect two LANs or multiple LANs.
Bridge Type
A bridge supported by equipment is available in three types: 802.1d bridge, 802.1q bridge, and 802.1ad bridge. As shown in Figure 20-2, the services on different 802.1d bridges are isolated, but the services of different VLANs on one bridge are not isolated. The services on different 802.1q bridges are isolated and the services of different VLANs on one bridge are also isolated. Figure 20-2 802.1d bridge and 802.1q bridge
LP3 VLAN1 VLAN2 VLAN3 ... 802.1d bridge LP: Logic Port LP4 LP5 LP6 LP7 LP8 LP3 LP4 LP5 LP6 LP7 LP8
LP1 LP2 LP3
LP1 LP2 LP3
VLAN1 VLAN2
VLAN3 802.1q bridge
As shown in Figure 20-3, the following conditions may occur in the case of a 802.1ad bridge: l l When Bridge Switch Mode is set to SVL/Ingress Filter Disable, the services on different bridges are isolated but the services of different S-VLANs on one bridge are not isolated. When Bridge Switch Mode is set to IVL/Ingress Filter Enable, the services on different bridges are isolated and the services of different S-VLANs on one bridge are also isolated.
20-4
Figure 20-3 802.1ad bridge

LP3 LP4 S-VLAN1 S-VLAN2 S-VLAN3 ... 802.1ad bridge SVL/Ingress Filter Disable LP: Logic Port LP5 LP6 LP7 LP8 LP3 LP4 LP5 LP6 LP7 LP8
LP1 LP2 LP3
LP1 LP2 LP3
S-VLAN1 S-VLAN2
S-VLAN3 802.1ad bridge IVL/Ingress Filter Enable
LP: logical port
Table 20-1 List of bridges Item Bridge switch mode VLAN filter table Ingress filter 802.1d Bridge SVL/Ingress filter disable Not configured Disabled: Does not check the VLAN tag. 802.1q Bridge IVL/Ingress filter enable Required Enabled: Checks the VLAN tag. If the VLAN ID is not the VLAN ID of the port specified in the VLAN filter table, the packet is discarded. IVLb Obtains the packet forwarding port by querying the MAC address table, based on the destination MAC address and VLAN ID of a packet. 802.1ad Bridge SVL/Ingress filter disable Not configured Disabled: Does not check the VLAN tag. IVL/Ingress filter enable Required Enabled: Checks the SVLAN tag. If the VLAN ID is not the VLAN ID of the port specified in the VLAN filter table, the packet is discarded. IVLb Obtains the packet forwarding port by querying the MAC address table, based on the destination MAC address and S-VLAN ID of a packet.
Bridge learning mode Packet forwarding mode
SVLa Obtains the packet forwarding port by querying the MAC address table, based on the destination MAC address of a packet.
SVLa Obtains the packet forwarding port by querying the MAC address table, based on the destination MAC address of a packet.
Issue 05 (2010-10-30)
20-5
Item Range of broadcasting
802.1d Bridge Forwards the broadcast packet to all the ports on a bridge.
802.1q Bridge Forwards the broadcast packet to the ports that are specified in the VLAN filter table. UNI
802.1ad Bridge Forwards the broadcast packet to all the ports on a bridge. Forwards the broadcast packet to the ports that are specified in the S-VLAN filter table. C-Aware S-Aware
Mount port attribute
UNI
C-Aware S-Aware
NOTE
l a: When using the shared VLAN learning (SVL) mode, a bridge creates an entry based on the source MAC address and the source port of a packet. This entry is valid to all VLANs. l b: When using the independent VLAN learning (IVL) mode, a bridge creates an entry based on the source MAC address, VLAN ID, and source port of a packet. This entry is only valid to this VLAN. l For details on an 802.1ad bridge, see 19.2.4 Application of the QinQ Technology in 802.1ad Bridge Services.
Logical Port
The OptiX RTN 620 considers all the ports mounted to a bridge are logical ports, each of which can exist in one or more sub-switching domains. A logical port can be a PORT or a VCTRUNK.
20.2.2 Hub/Spoke
In the case of a convergence service, the mutual access between the non-central stations and central stations is required but the access between non-central stations is not required. In this case, specify a mounted port as a Hub port or a Spoke port. l Hub Port Hub ports can mutually access each other. Hub ports and Spoke ports can mutually access each other. l Spoke Port Spoke ports cannot mutually access each other. Spoke ports and Hub ports can mutually access each other.
NOTE
A mounted port is a Hub port by default. During configuration, you can configure the mounted port of a central station to a Hub port, and configure the mounted port of a non-central station to a Spoke port. In this manner, a central station can communicate with a non-central station, but non-central stations cannot communicate with each other.
20-6
Issue 05 (2010-10-30)
20.2.3 Managing a MAC Address Table

The entries in a MAC address table indicate the corresponding relationship between MAC addresses and ports. A MAC address table contains the following entries: dynamic entry, static entry, and blacklist entry. l Dynamic entry A dynamic entry is obtained by learning of a bridge through the SVL/IVL mode. The dynamic entry ages, and is lost after the Ethernet switching board is reset. l Static entry A static entry is manually added by a network administrator to the MAC address table by using the NMS. The static entry does not age, and is not lost after the Ethernet switching board is reset. Generally, the static entry is configured when a port corresponds to a device with its MAC address known and this device transmits large traffic for a long time. l Blacklist entry A blacklist entry, that is, the MAC disabled entry, is used to discard the data frame that contains the specified MAC address (source MAC address or destination MAC address). A blacklist entry is also called a blackhole entry. The blacklist entry is configured by the network administrator. The blacklist entry does not age, and is not lost after the Ethernet processing board is reset.
NOTE
If one routing entry is not updated in a certain period, that is, if no new packet from this MAC address is received to enable the re-learning of this MAC address, this routing entry is automatically deleted. This mechanism is called aging, and this period is called aging time.
20.3 Specifications
This section describes the specifications of Layer 2 switching. Table 20-2 provides specifications of Layer 2 switching. Table 20-2 Specifications of Layer 2 switching Item Specifications EMS6 Switching capacity of a board Bridge type 2.7 Gbit/s 802.1d bridge 802.1q bridge 802.1d bridge Bridge switch mode IVL/Ingress filter enabled (802.1q bridge and 802.1ad bridge) SVL/Ingress filter disabled (802.1d bridge and 802.1ad bridge) EPLAN/EVPLAN services Number of supported bridges Supported 1 EFP6 755 Mbit/s
Issue 05 (2010-10-30)
20-7
Item
Specifications EMS6 EFP6 22
Number of logical ports mounted with a bridge Hub/Spoke attribute Number of static MAC address entries Number of MAC address entries MAC address aging time Enabling broadcast packet suppression Broadcast packet suppression threshold
14 Supported 512 16K 1 minute to 120 days Supported 10%-100%

This section describes the standards and protocols associated with Layer 2 switching. The following standards and protocols are associated with Layer 2 switching: l l l IEEE 802.1d: Media Access Control (MAC) Bridges IEEE 802.1q: Virtual Bridged Local Area Networks IEEE 802.1ad: Virtual Bridged Local Area Networks Amendment 4: Provider Bridges
20.5 Availability
This section describes the support required by the application of the Layer 2 switching feature and its dependency.

Table 20-3 Hardware and version support Feature 802.1q bridge Applicable Board EMS6 EFP6 802.1d bridge
20-8
Applicable Hardware Version All the versions All the versions All the versions
Applicable Product Version V100R003 and later V100R005C00 and later V100R003 and later
Issue 05 (2010-10-30)
EMS6
Feature
Applicable Board EFP6
Applicable Hardware Version All the versions All the versions All the versions
Applicable Product Version V100R005C00 and later V100R003 and later V100R005C00 and later
802.1ad bridge
EMS6 EFP6
Feature Dependency
The dependency between the Layer 2 switching feature and other features is as follows: l l l l l l The port that is used by a bridge cannot be used for a private line service. The STP/RSTP protocol is only applicable to a bridge. IGMP Snooping is only applicable to a bridge. The port on a bridge supports the QoS function. ERPS is only applicable to a bridge. A LAG group is only used as a logical port of a bridge.
20.6 Principles
The key of Layer 2 switching is to forward Ethernet packets based on a MAC address table.
Packet Forwarding Procedure of 802.1d and 802.1q Bridges

1. In the case of an 802.1q bridge, it checks the VLAN ID of a data frame that is received at the port. If the VLAN ID of this frame does not equal the VLAN ID of the port that is defined in the VLAN filter table, the bridge discards this frame. If the broadcast packet suppression function of the bridge port is enabled and the traffic of the broadcast packet exceeds the preset threshold value, the port discards the broadcast frame whose traffic exceeds the threshold. If the IGMP Snooping protocol of the bridge is enabled, the bridge processes the IGMP packet and multicast packet that are received at the port, according to the principle described in 23.6 Principles. If the bridge receives the multicast packet but the IGMP Snooping protocol is disabled, it forwards the multicast packet among all the ports of the bridge or among all the mounted ports of the VLAN (excluding the source port). According to the learning mode (SVL or IVL), the bridge adds or updates the entry corresponding to the source MAC address of the data frame in the MAC address table, and thus establishes the mapping relationship between the MAC address and the destination port. The bridge checks the destination MAC address of the data frame in the MAC address table. l If the blacklist entry corresponding to the destination MAC address exists, the bridge discards this data frame.
2.
3.
4.
5.
6.
l If the dynamic entry or the static entry corresponding to the destination MAC address exists, the bridge forwards this data frame to the destination port indicated by the entry. l If no corresponding entry exists, the bridge forwards the packet among all the ports of the bridge or among all the mounted ports of the VLAN (excluding the source port), according to the bridge type (802.1d bridge or 802.1q bridge). 7. The bridge needs to determine whether the source port and the destination port are Hub or Spoke when forwarding the data frame. If the source port is a Hub port, the bridge forwards the packet to the Hub port and the Spoke port. If the source port is the Spoke port, the bridge forwards the packet only to the Hub port.
NOTE
If the STP or the RSTP of the bridge is enabled, only the port in the forwarding state can forward the data frame.
Packet Forwarding Procedure of an 802.1ad Bridge

For the packet forwarding procedure of an 802.1ad bridge, see 19.6 Principles.

Follow certain guidelines when you plan Layer 2 switching.
Planning Guidelines on a Bridge

l Using the 802.1q bridge is a priority. If the conditions of the VLAN used by the user are unknown and if the isolation of the data among VLANs is not required, you can also use the 802.1d bridge. If the Layer 2 switching services from several branch nodes are converged at a convergence node, set this convergence node to Hub and set these branch nodes to Spoke. In the case of the multipoint-to-multipoint Layer 2 switching service, set each node to Hub.
Planning Guidelines on a MAC Address Table

l l l In normal cases, if a port corresponds to a set of equipment with a known MAC address and the equipment has constant and large traffic, configure static entries. If certain nodes are not allowed to transmit data frames, configure the corresponding MAC disabled entries for the bridge that accesses these nodes. Set the aging time of the MAC address table to the same value as the aging time of the interconnected Ethernet equipment. It is recommended that you set the aging time of the MAC address table to 5 minutes (default value).

Configuring Ethernet services based on Layer 2 switching involves configuring EPLAN and EVPLAN services. The procedures for configuring an Ethernet service vary according to the type of the bridge. The following tables provide the configuration procedures.
20-10
Issue 05 (2010-10-30)
Table 20-4 Procedure for configuring IEEE 802.1d bridge-based EPLAN services Step 1 Operation Configuri ng Ethernet interfaces on Ethernet boards A.18.1 Configuri ng External Ethernet Ports Description l You need to set Basic Attributes. Set the parameters as follows: In the case of used interfaces, set Enabled/ Disabled to Enabled. In the case of unused interfaces, set Enabled/Disabled to Disabled. In the case of Ethernet interfaces that connect to external equipment, set Working Mode to be the same value as the external equipment (the working mode of the external equipment is generally auto-negotiation). In the case of Ethernet interfaces for connection within the network, it is recommended that you set Working Mode to Auto-Negotiation. When JUMBO frames are transmitted, set Maximum Frame Length according to the actual length of a JUMBO frame. Otherwise, it is recommended that Maximum Frame Length takes the default value. l Click the Flow Control tab if the flow control function is enabled on the external equipment to which the Ethernet interface is connected. Set the parameters as follows: When the external equipment uses the nonauto-negotiation flow control function, set Non-Autonegotiation Flow Control Mode to Enable Symmetric Flow Control. When the external equipment uses the autonegotiation flow control function, set Autonegotiation Flow Control Mode to Enable Symmetric Flow Control. l In the case of an IEEE 802.1d bridge-based EPLAN service, set Port Attributes in the Network Attributes tab page to UNI. l You need to set Bound Path. Configure bound channels according to the service planning information.
Issue 05 (2010-10-30)
20-11
Step
Operation
Description l To enable the port loop detection function or broadcast packet suppression function, you need to set Advanced Attributes. Set the relevant parameters according to the network planning information. A.18.2 Configuri ng the Internal Port of the Ethernet Board Required when internal interfaces need to be used. l Determine whether to set Encapsulation/ Mapping according to actual requirements. It is recommended that all the relevant parameters take the default value. Ensure that the parameters are set to the same values at both ends of a link. l In the case of an IEEE 802.1d bridge-based EPLAN service, set Port Attributes in the Network Attributes tab page to UNI. l Determine whether to configure the LCAS function according to actual requirements. If the LCAS function is required, set Enabling LCAS to Enabled and set LCAS Modde according to the type of third-party equipment. In addition, it is recommended that the other parameters take the default values. Ensure that the parameters are set to the same values at both ends of a link. l Determine whether to set Advanced Attributes according to actual requirements.
20-12
Issue 05 (2010-10-30)
Step 2
Issue 05 (2010-10-30)
20-13
Step
Required when you need to configure the ERPS. Set the parameters as follows: l Set ERPS ID, East Port, and West Port according to the service planning information. l When setting RPLOwner Ring Node Flag, note that an Ethernet ring has only one RPL owner. l When setting Control VLAN, note that Control VLAN must be different from the VLAN ID carried by the Ethernet service packets or the VLAN ID carried by the inband DCN packets.
A.9.2 Setting Paramete rs of the Ethernet Ring Protocol
Required when you need to configure the ERPS. Set the relevant parameters according to the service planning information. l Set Hold-Off Time(ms), Guard Time(ms), and WTR Time(min) according to actual requirements. Set these parameters to the same values for all the NEs on the network. l Entity Level must be different from the entity level of IEEE 802.1ag OAM packets.
Creating IEEE 802.1d bridgebased EPLAN services
A.19.2 Creating Ethernet LAN Services
Required. Set the parameters as follows: l Set VB Name according to the network planning information. l Set Bridge Type to 802.1d. l Set Mount Port according to the network planning information. l If any VCTRUNK to which no channels are bound is used as Mount Port, configure corresponding bound channels according to the service planning information.
20-14
Issue 05 (2010-10-30)
Step 5
Issue 05 (2010-10-30)
20-15
Step
Perform a LB test
A.14.1 Creating MDs
A.14.2 Creating MAs
20-16
Issue 05 (2010-10-30)
Step
Issue 05 (2010-10-30)
20-17
Table 20-5 Procedure for configuring IEEE 802.1q bridge-based EVPLAN services Step 1 Operation Configuri ng Ethernet interfaces on Ethernet boards A.18.1 Configuri ng External Ethernet Ports Description l You need to set Basic Attributes. Set the parameters as follows: In the case of used interfaces, set Enabled/ Disabled to Enabled. In the case of unused interfaces, set Enabled/Disabled to Disabled. In the case of Ethernet interfaces that connect to external equipment, set Working Mode to be the same value as the external equipment (the working mode of the external equipment is generally auto-negotiation). In the case of Ethernet interfaces for connection within the network, it is recommended that you set Working Mode to Auto-Negotiation. When JUMBO frames are transmitted, set Maximum Frame Length according to the actual length of a JUMBO frame. Otherwise, it is recommended that Maximum Frame Length takes the default value. l Click the Flow Control tab if the flow control function is enabled on the external equipment to which the Ethernet interface is connected. Set the parameters as follows: When the external equipment uses the nonauto-negotiation flow control function, set Non-Autonegotiation Flow Control Mode to Enable Symmetric Flow Control. When the external equipment uses the autonegotiation flow control function, set Autonegotiation Flow Control Mode to Enable Symmetric Flow Control. l You need to set TAG Attributes. In the case of an IEEE 802.1q bridge-based EVPLAN service, set Port Attributes in the Network Attributes tab page to UNI. l To enable the port loop detection function or broadcast packet suppression function, you need to set Advanced Attributes. Set the relevant parameters according to the network planning information.
20-18
Issue 05 (2010-10-30)
Step
Description Required when internal interfaces need to be used. l Determine whether to set Encapsulation/ Mapping according to actual requirements. It is recommended that all the relevant parameters take the default value. Ensure that the parameters are set to the same values at both ends of a link. l In the case of an IEEE 802.1q bridge-based EVPLAN service, set Port Attributes in the Network Attributes tab page to UNI. l Determine whether to configure the LCAS function according to actual requirements. If the LCAS function is required, set Enabling LCAS to Enabled and set LCAS Modde according to the type of third-party equipment. In addition, it is recommended that the other parameters take the default values. Ensure that the parameters are set to the same values at both ends of a link. l You need to set Bound Path. Configure bound channels according to the service planning information.
Issue 05 (2010-10-30)
20-19
Step 2
20-20
Issue 05 (2010-10-30)
Step
Required if ERPS is configured. The main parameters are provided as follows: l Set ERPS ID, East Port, and West Port according to the network planning information. l When setting RPLOwner Ring Node Flag, note that an Ethernet ring has only one RPL owner. l When you set Control VLAN, pay attention to the following points: The value of Control VLAN must different from the VLAN ID carried by Ethernet service packets or the VLAN ID carried by inband DCN packets. Add Control VLAN to the VLAN filter table of an IEEE 802.1q bridge when you create EVPLAN services based on this bridge.
A.9.2 Setting Paramete rs of the Ethernet Ring Protocol 4 Creating IEEE 802.1q bridgebased EVPLAN services A.19.2 Creating Ethernet LAN Services
Required if the values of the default parameters of the ERPS timers need to be changed. Set Hold-Off Time(ms), Guard Time(ms), and WTR Time(min) according to actual requirements. Set these parameters to the same values for all the NEs on the network. Required. Set the parameters as follows: l Set VB Name according to the network planning information. l Set Bridge Type to 802.1q. l Set Mount Port according to the network planning information. l If any VCTRUNK to which no channels are bound is used as Mount Port, configure corresponding bound channels according to the service planning information.
Issue 05 (2010-10-30)
20-21
Step 5
Operation A.19.4 Creating the VLAN Filtering Table
Description Required. Set VLAN ID(e.g;1,3-6) and Selected forwarding ports according to the network planning information. Required if you need to set certain MAC address entries not to age. Set the relevant parameters according to the network planning information.
Managing the MAC address table
A.20.1 Creating a Static MAC Address Entry A.20.2 Creating a Blacklist Entry of a MAC Address A.20.3 Setting the Aging Time of a MAC Address Table Entry
20-22
Issue 05 (2010-10-30)
Step
Perform a LB test
A.14.1 Creating MDs
A.14.2 Creating MAs
Issue 05 (2010-10-30)
20-23
Step
20-24
Issue 05 (2010-10-30)
Table 20-6 Procedure for configuring IEEE 802.1ad bridge-based EVPLAN services Step 1 Operation Configuri ng Ethernet interfaces on Ethernet boards A.18.1 Configuri ng External Ethernet Ports Description l You need to set Basic Attributes. Set the parameters as follows: In the case of used interfaces, set Enabled/ Disabled to Enabled. In the case of unused interfaces, set Enabled/Disabled to Disabled. In the case of Ethernet interfaces that connect to external equipment, set Working Mode to be the same value as the external equipment (the working mode of the external equipment is generally auto-negotiation). In the case of Ethernet interfaces for connection within the network, it is recommended that you set Working Mode to Auto-Negotiation. When JUMBO frames are transmitted, set Maximum Frame Length according to the actual length of a JUMBO frame. Otherwise, it is recommended that Maximum Frame Length takes the default value. l Click the Flow Control tab if the flow control function is enabled on the external equipment to which the Ethernet interface is connected. Set the parameters as follows: When the external equipment uses the nonauto-negotiation flow control function, set Non-Autonegotiation Flow Control Mode to Enable Symmetric Flow Control. When the external equipment uses the autonegotiation flow control function, set Autonegotiation Flow Control Mode to Enable Symmetric Flow Control. l You need to set TAG Attributes. In the case of an IEEE 802.1ad bridge-based EVPLAN service, set Port Attributes in the Network Attributes tab page to C-Aware or S-Aware.
l You need to set Bound Path. Configure bound channels according to the service planning information.
Issue 05 (2010-10-30)
20-25
Step
Operation
Description
l To enable the port loop detection function or broadcast packet suppression function, you need to set Advanced Attributes. Set the relevant parameters according to the network planning information. A.18.2 Configuri ng the Internal Port of the Ethernet Board Required when internal interfaces need to be used. l Determine whether to set Encapsulation/ Mapping according to actual requirements. It is recommended that all the relevant parameters take the default value. Ensure that the parameters are set to the same values at both ends of a link. l In the case of an IEEE 802.1ad bridge-based EVPLAN service, set Port Attributes in the Network Attributes tab page to C-Aware or SAware.
l Determine whether to configure the LCAS function according to actual requirements. If the LCAS function is required, set Enabling LCAS to Enabled and set LCAS Modde according to the type of third-party equipment. In addition, it is recommended that the other parameters take the default values. Ensure that the parameters are set to the same values at both ends of a link. l Determine whether to set Advanced Attributes according to actual requirements.
20-26
Issue 05 (2010-10-30)
Step 2
Issue 05 (2010-10-30)
20-27
Step
Required if ERPS is configured. The main parameters are provided as follows: l Set ERPS ID, East Port, and West Port according to the network planning information. l When setting RPLOwner Ring Node Flag, note that an Ethernet ring has only one RPL owner. l When you set Control VLAN, pay attention to the following points: The value of Control VLAN must be different from the VLAN ID carried by Ethernet service packets or the VLAN ID carried by inband DCN packets.
A.9.2 Setting Paramete rs of the Ethernet Ring Protocol 4 Creating IEEE 802.1ad bridgebased EVPLAN services A.19.6 Creating IEEE 802.1ad BridgeBased EVPLAN Services
Required if the values of the default parameters of the ERPS timers need to be changed. Set Hold-Off Time(ms), Guard Time(ms), and WTR Time(min) according to actual requirements. Set these parameters to the same values for all the NEs on the network. Required. Set the parameters as follows: l Set VB Name according to the network planning information. l Set Bridge Type to 802.1ad. l Set Mount Port according to the network planning information. l If any VCTRUNK to which no channels are bound is used as Mount Port, configure corresponding bound channels according to the service planning information.
Required if Bridge Switching Mode is set to IVL/ Ingress Filter Enable. Set VLAN ID(e.g;1,3-6) and Selected forwarding ports according to the network planning information.
20-28
Issue 05 (2010-10-30)
Step 6
Required if you need to perform CAR or CoS operations for a specific flow over a port. Set CAR or CoS parameters and bind the configured CARs or CoSes to the corresponding flows according to the network planning information.
Issue 05 (2010-10-30)
20-29
Step
Description Required if you need to perform traffic shaping for the queues at a specific egress port. Set the relevant parameters according to the network planning information.
Required if you need to limit the egress bandwidth that an Ethernet service occupies. Set the relevant parameters according to the network planning information. Required if you need to perform queue scheduling over an egress port or limit the bandwidth of queues over an egress port. Set the relevant parameters according to the network planning information. Required in the case of the NEs where the two Ethernet interfaces involved in the service test are located. Set the parameters as follows: l Set Maintenance Domain Name and Maintenance Level to the same values for the two NEs. l In the test of an Ethernet service between two edge nodes on the transport network, it is recommended that Maintenance Level takes the default value 4. In the test of an Ethernet service between two internal NEs on the transport network, set Maintenance Level to a value smaller than 4. In the test of an Ethernet service between two Ethernet interfaces on the same NE, set Maintenance Level to a value smaller than the value that is set in the test of an Ethernet service between two internal NEs on the transport network.
Perform a LB test
A.14.1 Creating MDs
A.14.2 Creating MAs
20-30
Issue 05 (2010-10-30)
Step

This section uses an example to describe how to plan and configure Ethernet services based on Layer 2 switching according to the network conditions. l For a configuration example of Ethernet services based on an 802.1d bridge, see Configuration Example (IEEE 802.1d Bridge-Based EPLAN Services) in the Configuration Guide. For a configuration example of Ethernet services based on an 802.1q bridge, see Configuration Example (IEEE 802.1q Bridge-Based EVPLAN Services) in the Configuration Guide. For a configuration example of Ethernet services based on an 802.1ad bridge, see Configuration Example (IEEE 802.1ad Bridge-Based EVPLAN Services) in the Configuration Guide.

This section provides the hyperlinks of the operation tasks associated with Layer 2 switching.
Related Tasks
A.18.1 Configuring External Ethernet Ports A.18.2 Configuring the Internal Port of the Ethernet Board A.19.2 Creating Ethernet LAN Services A.19.3 Modifying the Mounted Port of a Bridge A.19.4 Creating the VLAN Filtering Table A.19.6 Creating IEEE 802.1ad Bridge-Based EVPLAN Services

There are no alarms or performance events relevant to Layer 2 switching.
Relevant Alarms
None.
Relevant Events
None.
20.12 FAQs
This section provides the answers to the questions that are frequently raised when Layer 2 switching is used. Q: When do I need to configure Layer 2 switching services? A: In the case of the OptiX RTN 620, multipoint-to-multipoint services must be configured as Layer 2 switching services; point-to-multipoint services are configured as private line services if they can be isolated based on VLAN tags, and are configured as Layer 2 switching services if they cannot be isolated.
20-32
Issue 05 (2010-10-30)
21 Ethernet Ring Protection Switching
21
Ethernet Ring Protection Switching
About This Chapter

This chapter describes the Ethernet ring protection switching (ERPS) feature. 21.1 Introduction This section provides the definition of ERPS and describes its purpose. 21.2 Basic Concepts This section describes the basic concepts associated with ERPS. 21.3 Specifications This section describes the specifications of ERPS. 21.4 Reference Standards and Protocols This section describes the standards and protocols associated with ERPS. 21.5 Availability This section describes the support required by the application of the ERPS feature and its dependency. 21.6 Principles ERPS uses the R-APS protocol to implement protection switching. 21.7 Planning Guidelines Follow certain principles when you plan ERPS. 21.8 Configuration Procedure The key to configuring ERPS is creating an ERPS protection instance. 21.9 Configuration Example This topic uses an example to describe how to plan and configure ERPS according to network conditions. 21.10 Task Collection This section provides the hyperlinks of the operation tasks associated with the ERPS feature. 21.11 Relevant Alarms and Events When an exception occurs in ERPS, the NE reports the relevant alarms and abnormal events. 21.12 FAQs
This section provides answers to the questions that are frequently raised when the ERPS feature is used.
21-2
Issue 05 (2010-10-30)
21.1 Introduction
This section provides the definition of ERPS and describes its purpose.
Definition
Based on the automatic protection switching (APS) protocol and protection switching mechanism, ERPS defines a protocol for Ethernet ring protection. ERPS is applicable to the Ethernet ring topology at the Ethernet Layer 2, and provides protection for LAN services on an Ethernet ring.
Purpose
When a ring network is configured with ERPS, in normal cases, the RPL owner blocks the port on a certain side so that all the services are transmitted through the port on the other side. In this manner, service loops can be prevented. If a segment of links fails or an NE becomes faulty, the RPL owner unblocks the preceding port and thus the services that cannot be transmitted over the faulty point can be transmitted through this port. In this manner, ring protection is achieved. The Ethernet ring network as shown in Figure 21-1 is configured with ERPS. Generally, the RPL owner (NE D) blocks the port that is connected to NE A, and all the services are transmitted over the link NE A<->NE B<->NE C<->NE D. When the link between NE A<->NE B becomes faulty, NE D unblocks the port that is blocked so that the services can be transmitted over the link NE A<->NE D<->NE C<->NE B.
Issue 05 (2010-10-30)
21-3
Figure 21-1 Implementation of ERPS
NE A
NE B
NE D
NE C
Protection switching
Failure
NE A
NE B
NE D
NE C Link Ethernet service direction Blocked port
21.2 Basic Concepts

This section describes the basic concepts associated with ERPS. 21.2.1 Protection Instance A protection instance is the basic unit of ERPS. 21.2.2 Protection Type
ERPS is revertive. 21.2.3 R-APS Message When the ERPS scheme is used, a switching request is transmitted through the ring-APS (RAPS) message. 21.2.4 R-APS Timer In the ERPS process, three timers including the guard timer, WTR timer, and holdoff timer are used. 21.2.5 Switching Condition The switching actions of an Ethernet ring consisting of Ethernet ports and an Ethernet ring consisting of microwave ports are triggered by different conditions. 21.2.6 Switching Impact The services are interrupted within the ERPS time.
21.2.1 Protection Instance

A protection instance is the basic unit of ERPS. Figure 21-2 shows a protection instance of ERPS. The protection instance of ERPS refers to an Ethernet ring that runs the ERPS protocol. On this Ethernet ring, the Ethernet ring node, ring link, ring protection link (RPL), RPL owner, and east (E) ports and west (W) ports at each Ethernet ring node are defined. Figure 21-2 Protection instance of ERPS
Ring link W
RPL E
Ethernet Ring Node A W E
RPL connection point
E Ethernet Ring Node B Ring link Ring link
W RPL Owner
Ethernet Ring Node C Blocked port Ring link Ring Protection Link (Blocked) Ethernet service direction
An RPL refers to a link on an Ethernet ring whose service channels are blocked when this Ethernet ring is in normal status. Only one RPL is available on one Ethernet ring.
An RPL owner refers to an Ethernet ring node located at one end of an RPL. The RPL owner is marked with the RPL owner label. When an Ethernet ring is in normal status, the RPL connection point on the RPL owner is blocked to prevent the service channels from forming loops. A ring port is an ring link connection point on an Ethernet ring node. The OptiX RTN 620 does not support Ethernet tangent rings or Ethernet intersecting rings. That is, different protection instances of ERPS cannot contain one or more same ring ports. Consider Figure 21-2 as an example. Generally, the port on an Ethernet ring node for transmitting counter-clockwise services is an east ring port, and the port on the same Ethernet ring node for receiving counterclockwise services is a west ring port.

ERPS is revertive. In revertive mode, when an NE is in the switching state, the NE releases the switching and returns to the normal state if the working channel is restored to normal and this state lasts for a certain period. The period after the working channel is restored to normal and before the NE releases the switching state is called the WTR time. To prevent frequent switching events because the working channel is not stable, it is recommended that you set the WTR time to 5 to 12 minutes.
21.2.3 R-APS Message

When the ERPS scheme is used, a switching request is transmitted through the ring-APS (RAPS) message. The ring nodes transmit R-APS messages on the specific R-APS channel to ensure that all the ring nodes perform consistent operations to implement ERPS. The frame format of the R-APS message is a type of ETH-OAM frame formats, as shown in Figure 21-3. An R-APS message uses a fixed default MAC destination address, namely, 01-19-A7-00-00-01. An R-APS message also carries a VLAN ID, which identifies an R-APS message from the Ethernet service message. Therefore, the VLAN ID contained in the R-APS message cannot be the same as the VLAN ID contained in the Ethernet service message. Through different VLAN IDs, R-APS messages and Ethernet service messages can be separately transmitted over isolated VLAN channels. To prevent messages from forming loops, the blocked ports on the R-APS channel and on the Ethernet service channel must be the same. That is, the same ring port is blocked for the R-APS channel and the Ethernet service channel.
21-6
Issue 05 (2010-10-30)
Figure 21-3 Frame format of an R-APS message

1 byte 1 byte 1 byte 1 byte
Mac Destination Address
Mac Source Address 802.1Q Header Type Flags TLV Offset MEL Version OpCode
R-APS Specific Information (32 bytes)
... Frame Check Sequence
Each R-APS message contains the R-APS specific information. Figure 21-4 shows the frame format of the R-APS specific information. Figure 21-4 Frame format of the R-APS specific information
1 byte 0 1 2 Request /State 3 4 5 6 7 0 1 2 1 byte 3 4 5 Status Reserved 1 D R N B F Status Reserved Node ID (6 bytes) 6 7 1 byte 1 byte
Reserved 2 (24 bytes)
Table 21-1 details each field in the R-APS specific information. Table 21-1 Description of each field in the R-APS specific information Field Request/State Value 1011 0000 Others Reserved 1
Issue 05 (2010-10-30)
Description Indicates signal fail (SF). Indicates no request (NR). Reserved. Reserved.
21-7
0000
Field Status RPL blocked (RB) Do not flush (DNF)
Value 1 0 1 0 Status Reserved All 0s
Description Indicates that an RPL is blocked. Indicates that an RPL is not blocked. Indicates that the ring node does not empty the MAC address table. Indicates that the ring node empties the MAC address table. Reserved. Indicates the MAC address of a ring node. The MAC address is unique. Reserved.
Node ID Reserved 2
According to the values of the fields provided in Table 21-1, the following R-APS messages are defined: l R-APS (SF) message: A node detecting an SF condition transmits the R-APS (SF) message. The other ring nodes that receive the R-APS (SF) message are notified that a remote node is faulty. R-APS (NR, RB) message: The RPL owner transmits the R-APS (NR, RB) message. The other ring nodes that receive the R-APS (NR, RB) message are notified that the Ethernet ring is in normal status and the RPL connection point on the remote RPL owner is blocked. R-APS (NR) message: A node that detects fault recovery transmits the R-APS (NR) message. Nodes that receive the R_APS (NR) message are notified that the switching trigger condition at the remote end is cleared.
If an R-APS message contains the DNF flag (that is, the value of the DNF field is equal to 1), a node that detects the fault on the RPL transmits this message. The node that receives this message is notified that it should not empty the MAC address table.
21.2.4 R-APS Timer

In the ERPS process, three timers including the guard timer, WTR timer, and holdoff timer are used.
Guard Timer
A ring node continuously transmits R-APS messages over an Ethernet ring. As a result, outdated R-APS messages may exist on the ring. Receipt of these outdated R-APS messages may result in incorrect ERPS actions. As a type of R-APS timers, a guard timer can prevent ring nodes from receiving outdated R-APS messages. When a faulty ring node detects that the switching condition is cleared, it starts the guard timer and starts to forward R-APS (NR) messages. When the guard timer is running, the ring node discards the R-APS messages that arrive. After the guard timer expires, the received R-APS messages are forwarded. The period of a guard timer may be set in 10 ms steps between 10 ms and 2000 ms, with a default value of 500 ms.
WTR Timer
A WTR timer prevents frequent switching actions due to an unstable working channel. The period of a WTR timer may be set in 1 minute steps between 5 minutes and 12 minutes, with a default value of 5 minutes. The period after the faulty channel is restored to normal and before the NE releases the switching is called the WTR time. When the faulty channel is restored to normal, the WTR timer on the RPL owner is started. When the WTR timer is running, a WTR timer running signal is continuously generated. When the WTR timer expires and no switching request with a higher priority is received, the WTR timer running signal is no longer generated but a WTR expire signal is continuously generated.
Holdoff Timer
A holdoff timer can adjust the switching sequence between the ERPS scheme and other coexisting protection schemes. The holdoff timer allows another protection switching (for example, the LAG protection) to be triggered, before ERPS switching, to rectify a fault. When a ring node detects one or more new faults, the holdoff timer is started if the preset holdoff time is non-zero. When the holdoff timer is running, the fault is not reported to the ERPS scheme for processing. When the holdoff timer expires, the link status is checked regardless of whether the fault that starts the timer persists. If there is still a fault, it is reported to the ERPS scheme for protection switching. The reported fault may not be the same as the fault that starts the holdoff timer. The period of the holdoff timer may be set in 100 ms steps between 0s and 10s. The default value is 0s.

The switching actions of an Ethernet ring consisting of Ethernet ports and an Ethernet ring consisting of microwave ports are triggered by different conditions. Table 21-2 Trigger conditions of ERPS Switching Condition Local SF Priority From top downward s, the priority is from the highest to the lowest. Description l When a ring node detects the local SF condition on one of its ring ports, the ring node blocks the service channel and R-ASP channel of this ring port. l In this case, the two ring ports on this ring node transmit RAPS (SF) messages. l The local SF condition enables the ring node to empty the MAC address table. l The SF switching is triggered when the ETH_LOS alarm is reported.
NOTE In the case of a ring port that is configured into a LAG, the existence of the local SF conditions is considered only when the entire LAG fails.
Issue 05 (2010-10-30)
21-9
Switching Condition Receipt of an R-APS (SF) message at the local node
Priority
Description l When the RPL owner receives an R-APS (SF) message and does not receive a local switching request with a higher priority, the RPL owner unblocks the RPL connection point that is already blocked and then connects the service channel on the RPL. l When the RPL owner receives an R-APS (SF) message and the local SF condition persists, the RPL owner ignores the R-APS (SF) message. l When the other ring nodes receive an R-APS (SF) message that does not contain the DNF flag, these ring nodes empty their MAC address tables. l When the other ring nodes receive an R-APS (SF) message that contains the DNF flag, these ring nodes do not empty their MAC address tables.
Expiry of the WTR timer
l When a ring node detects that the local SF condition on another ring node is cleared, this ring node continuously transmits R-APS (NR) messages, through its two ring ports, to the Ethernet ring to notify that no switching request exists at the local end. In addition, this ring node starts the guard timer. l When the RPL owner receives an R-APS (NR) message, it starts the WTR timer. During the duration period of the WTR timer, the receipt of the R-APS (SF) message or the generation of the local SF condition at the RPL owner stops the WTR timer. l When the WTR timer expires and a switching trigger condition with a higher priority does not exist, the RPL owner blocks the service channel on the RPL and then transmits R-APS (NR, RB) messages, through its two ring ports, to the Ethernet ring to notify that the RPL is blocked. In addition, the RPL owner empties the MAC address table.
Receipt of an R-APS (NR, RB) message at the local node
l When the other ring nodes receive an R-APS (NR, RB) message that does not contain the DNF flag, all the ring nodes on which the local SF condition does not exist unblock all the non-RPLs that are blocked and empty their MAC address tables. l If the R-APS (NR, RB) message is received after all the preceding actions are performed, the ring nodes no longer empty their MAC address tables.

The services are interrupted within the ERPS time.
21-10
Issue 05 (2010-10-30)
21.3 Specifications
This section describes the specifications of ERPS. Table 21-3 lists the specifications of ERPS. Table 21-3 Specifications of ERPS Item EMS6 Protection instance of ERPS Number of supported ERPS instances Type of supported ERPS east/west port 1-7 FE/GE port
NOTE The OptiX RTN 620 does not support Ethernet tangent rings or Ethernet intersecting rings. That is, the west and east ports must belong to the same Ethernet ring.
Specification
RPL owner Control VLAN IDs on the R-APS channel Timer Holdoff timer
Only one RPL owner exists on an Ethernet ring. 1-4094

NOTE A control VLAN ID cannot be the same as the VLAN ID contained in services.
The period of the holdoff timer is set in 100 ms steps between 0s and 10s. The default value is 0s. The period of the WTR timer is set in 1 minute steps between 5 minutes and 12 minutes. The default value is 5 minutes. The period of the guard timer is set in 10 ms steps between 10 ms and 2000 ms. The default value is 500 ms. 1s to 10s 0 to 7 (4 by default)
NOTE An entity level cannot the same as the entity level of an ETH-OAM packet.
WTR timer
Guard timer
R-APS message
Interval of packet transmission Entity level

This section describes the standards and protocols associated with ERPS.
The following protocol is associated with ERPS: ITU-T G.8032/Y.1344: Ethernet Ring Protection Switching
21.5 Availability
This section describes the support required by the application of the ERPS feature and its dependency.

Table 21-4 Hardware and version support Feature ERPS Applicable Board EMS6 Applicable Hardware Version All the versions Applicable Product Version V100R005C00 and later
Feature Dependency
ERPS is associated with 1+1 protection, SNCP, and LAG. l Relationship between ERPS and LAG The FE/GE port that is configured with LAG protection can function as the ring port in ERPS. l Relationship between ERPS and SNCP On a Hybrid radio ring network, SNCP can be configured for E1 services and ERPS can be configured for Ethernet services. l Relationship between ERPS and EVPLAN services based on the IEEE 802.1q bridge If ERPS is used, you need to add the control VLAN ID of the ERPS to the VLAN filter table of an IEEE 802.1q bridge when creating EVPLAN services based on this bridge.
21.6 Principles
ERPS uses the R-APS protocol to implement protection switching. Figure 21-5 shows the working principle of ERPS on the OptiX RTN 620.
21-12
Issue 05 (2010-10-30)
Figure 21-5 Working principle of ERPS (in the case of a fault on a non-RPL link)
NE A NE B RPL NE C NE D RPL Owner
W Normal State
1 2 3 4 5 6
SF Recovery Guard timer NR NR Guard timer NR NR NR WTR timer SF SF Flush SF Flush SF Flush SF SF Flush SF SF Failure
Protection State
7 8
NR, RB Normal State
NR, RB
NR, RB
Flush
NR, RB
10
Flush
NR, RB
Flush
NR, RB
Flush
NR, RB
NR, RB
As shown in Figure 21-5, the process of ERPS is described as follows: 1. 2. 3. When the Ethernet ring is in normal status, the east (E) ring port on the RPL owner (NE D) is blocked. The ring link between NE A and NE B becomes faulty. NE A and NE B detect the local SF condition. After the holdoff timer expires, NE A and NE B block the ring ports that are connected to the faulty link and empty their MAC address tables. NE A and NE B rapidly transmit three R-APS (SF) messages to the Ethernet ring, to prevent switching delay caused by accidental loss of R-APS messages. When the SF condition persists, NE A and NE B keep transmitting R-APS (SF) messages to the Ethernet ring periodically. The ring nodes that receive an R-APS (SF) message empty their MAC address tables. When the RPL owner receives an R-APS (SF) message, it unblocks the blocked RPL connection point. The ERPS is complete and the ring becomes stable. The fault on the link between NE A and NE B is rectified.
4.
5.
6. 7.
Issue 05 (2010-10-30)
8.
NE A and NE B detect that the SF condition is cleared. In this case, NE A and NE B start their guard timers and start to periodically transmit R-APS (NR) messages to the other ring nodes. (The first three messages are transmitted in a rapid manner.) A guard timer can prevent frequent switching events on NE A and NE B because of the receipt of an R-APS message. After the guard timer expires, NE A and NE B are allowed to receive new R-APS messages. When the RPL owner receives an R-APS (NR) message, it starts the WTR timer. After the WTR timer expires, the RPL owner blocks the RPL connection point and periodically transmits R-APS (NR, RB) messages and empties the MAC address table. The first three R-APS (NR, RB) messages are transmitted in a rapid manner.
9.
10. When NE A and NE B receive R-APS (NR, RB) messages, they unblock the blocked ring ports and stop transmitting R-APS (NR) messages. In addition, NE A, NE B, and NE C empty their MAC address tables when receiving R-APS (NR, RB) messages. In this case, the Ethernet ring returns to normal. Figure 21-6 Working principle of ERPS (in the case of a fault on an RPL)
NE A NE B RPL NE C NE D RPL Owner
W Normal State
1 2 3 4 5
Guard timer SF (DNF) SF (DNF) SF (DNF) SF (DNF) Recovery Guard timer NR NR NR WTR timer Failure
Protection State
NR
NR
NR, RB (DNF) Normal State
NR, RB (DNF)
NR, RB (DNF)
NR, RB (DNF)
8
NR, RB (DNF) NR, RB (DNF) NR, RB (DNF) NR, RB (DNF)
As shown in Figure 21-6, the process of ERPS is described as follows: 1. 2. 3. When the Ethernet ring is in normal status, the east (E) port on the RPL owner (NE D) is blocked. The RPL between NE A and NE D becomes faulty. NE A and NE D detect the local SF condition. After the holdoff timer expires, the west (W) ring port on NE A that is connected to the faulty RPL is blocked.
21-14
4.
NE A and NE D rapidly transmit three R-APS (SF) messages to the Ethernet ring, to prevent switching delay caused by accidental loss of R-APS messages. When the SF condition persists, NE A and NE D keep transmitting R-APS (SF) messages to the Ethernet ring periodically. An R-APS (SF) message contains the DNF flag, which prevents every node on the Ethernet ring from emptying the MAC address table under any condition. On the receipt of an R-APS (SF) message that contains the DNF flag, the RPL owner ignores the R-APS (SF) message because the local SF condition has a higher priority. When an R-APS (SF) message that contains the DNF flag is received, the other ring nodes are notified that the RPL is faulty and that they do not empty their MAC address tables under any conditions. In this case, the Ethernet ring is stable. The SF message that contains the DNF flag exists on the ring. The fault on the RPL between NE A and NE D is rectified. NE A and NE D detect that the switching condition is cleared. In this case, NE A and NE D start their guard timers and start to periodically transmit R-APS (NR) messages to the other ring nodes. (The first three messages are transmitted in a rapid manner.) A guard timer prevents NE A and NE D from receiving R-APS messages. After the guard timer expires, NE A and NE D are allowed to receive new R-APS messages. After the WTR timer expires, the RPL owner blocks the RPL connection point. In addition, the RPL owner starts to periodically transmit R-APS (NR, RB) messages that contain DNF flags. (The first three messages are transmitted in a rapid manner.) In this manner, all the ring nodes are notified that they do not empty their MAC address tables under any conditions. When NE A receives an R-APS (NR, RB) message, it unblocks the blocked west (W) ring port and stops transmitting R-APS (NR) messages. When NE A, NE B, and NE C receive R-APS (NR, RB) messages, they are notified that the RPL is restored to normal and that they do not empty their MAC address tables under any conditions. In this case, the Ethernet ring returns to normal.
5. 6.
7.
8.

Follow certain principles when you plan ERPS.
Planning Guidelines on an ERPS ID

It is recommended that the ERPS ID of the RPL owner take the smallest value and the ERPS IDs of the other ring nodes are increased by one along the counter-clockwise direction of the Ethernet ring. For example, the ERPS ID of the RPL owner can be 1, and the other ring nodes in the counter-clockwise direction of the Ethernet ring can be 2, 3, and 4.
NOTE
An ERPS ID ranges from 1 to 7.
Planning Guidelines on East and West Ports

In the case of one Ethernet ring node, it is recommended that you set the service transmit port as the east ring port and the service receive port as the west ring port along the counter-clockwise direction of the Ethernet ring.
Planning Guidelines on an RPL Owner

l
Issue 05 (2010-10-30)
Only one ring node on an Ethernet ring can be the RPL owner.
l l
It is recommended that you set the Ethernet ring node that has small traffic as an RPL owner. The RPL on one side of an RPL owner is blocked when the Ethernet ring network is in normal status. Therefore, do not set the service convergence node or central site as an RPL owner so that traffic can be balanced on the Ethernet ring links. After planning an RPL owner, ensure that the traffic on the entire Ethernet ring is balanced.
Planning Guidelines on an RPL Connection Point

It is recommended that you set the east ring port on the RPL owner as an RPL connection point.
NOTE
When an Ethernet ring is normal, the RPL connection point on the RPL owner is blocked to prevent the service channels from forming loops.
Planning Guidelines on a Control VLAN ID

l l A control VLAN ID cannot be the same as the VLAN ID carried in services. Add the control VLAN ID to the VLAN filter table of an IEEE 802.1q bridge when you create EVPLAN services based on this bridge.
Planning Guidelines on an ERPS Timer

l l Set the parameters of the three ERPS timers the same for all the ring nodes. It is recommended that you set the period of the holdoff timer to 0s and that the other parameters associated with the timers take the default values.
Planning Guidelines on an Entity Level

An entity level cannot be the same as the entity level of ETH-OAM packets.

The key to configuring ERPS is creating an ERPS protection instance.
21-16
Issue 05 (2010-10-30)
Table 21-5 Procedure for configuring ERPS Step 1 Operation A.9.1 Creating ERPS Instances Description Required when you need to configure ERPS. Set the parameters as follows: l Set ERPS ID, East Port, and West Port according to the network planning information. l Only one RPL owner can exist on one Ethernet ring. l Different ERPS protection instances cannot contain any same ring ports. l When you set Control VLAN, pay attention to the following points: The value of Control VLAN must be different from the VLAN ID carried by Ethernet service packets or the VLAN ID carried by inband DCN packets. Add Control VLAN to the VLAN filter table of an IEEE 802.1q bridge when you create EVPLAN services based on this bridge. 2 A.9.2 Setting Parameters of the Ethernet Ring Protocol Required when you need to configure ERPS. Set the parameters according to the network planning information. l Set Hold-Off Time(ms), Guard Time(ms), and WTR Time (min) to the same values for all the NEs on the ring. l Entity Level must be different from the entity level of an ETH-OAM packet.

This topic uses an example to describe how to plan and configure ERPS according to network conditions. 21.9.1 Networking Diagram This section describes the networking information about NEs. 21.9.2 Service Planning The service planning information contains all the parameters required for configuring the NE data. 21.9.3 Configuration Process This section describes the procedure of data configuration.

This section describes the networking information about NEs. As shown in Figure 21-7, NE1, NE2, NE3, and NE4 form a Hybrid radio ring network, and ERPS is configured to protect the Ethernet services on the ring network. The Hybrid radio ring network is configured with ERPS. In normal cases, the RPL owner NE1 blocks the east RPL port and all the services are transmitted through the west RPL port. If a
segment of links fails or an NE becomes faulty, NE1 enables the blocked east RPL port and the services can be transmitted through the east RPL port. Figure 21-7 Networking diagram
Hybrid IF board (E): 5-IFH2 Hybrid IF board (W): 6-IFH2 7-EMS6 E W NE3
ETH BSC ETH W
E ERPS
ETH NE4
BTS1
NE2 E
RPL Port RPL ETH W NE1 E BTS3 Hybrid IF board (E): 5-IFH2 Hybrid IF board (W): 6-IFH2 7-EMS6 RPL Owner
BTS4
Hybrid IF board (E): 5-IFH2 Hybrid IF board (W) 6-IFH2 7-EMS6
Hybrid IF board (E): 5-IFH2 Hybrid IF board (W): 6-IFH2 7-EMS6
Bloked port

The service planning information contains all the parameters required for configuring the NE data. Table 21-6 Configuration information about the ERPS protection instance Parameter ERPS ID East Port West Port NE1 1 7-EMS6-5 7-EMS6-6 NE2 1 7-EMS6-5 7-EMS6-6 NE3 1 7-EMS6-5 7-EMS6-6 NE4 1 7-EMS6-5 7-EMS6-6
21-18
Issue 05 (2010-10-30)
Parameter RPL Owner Ring Node Flag RPL Port Control VLAN
NE1 Yes 7-EMS6-5 4093
NE2 No 4093
NE3 No 4093
NE4 No 4093
NOTE
Add the control VLAN ID to the VLAN filter table of an IEEE 802.1q bridge when you create EVPLAN services based on this bridge.
Table 21-7 Configuration information about the ERPS protocol parameters Parameter Hold-Off Time (ms) Guard Time (ms) WTR Time (min) Packet Transmit Interval(s) Entity Level NE1 0 500 5 5 4 NE2 0 500 5 5 4 NE3 0 500 5 5 4 NE4 0 500 5 5 4

Procedure
Step 1 See A.9.1 Creating ERPS Instances and create the ERPS protection instance. The values for the required parameters are provided as follows. Parameter Value Range NE1 ERPS ID East Port West Port
Issue 05 (2010-10-30)
NE2 1 PORT5 PORT6
NE3 1 PORT5 PORT6
NE4 1 PORT5 PORT6

21-19
1 PORT5 PORT6
Parameter
Value Range NE1 NE2 No 4093 NE3 No 4093 NE4 No 4093
RPLOwner Ring Node Flag RPL Port Control VLAN
Yes PORT5 4093
NOTE
Add the control VLAN ID to the VLAN filter table of an IEEE 802.1q bridge when you create EVPLAN services based on this bridge.
Step 2 See A.9.2 Setting Parameters of the Ethernet Ring Protocol and set the ERPS protocol parameters. The values for the required parameters are provided as follows. Parameter Value Range NE1 Hold-Off Time(ms) Guard Time(ms) WTR Time(min) Packet Transmit Interval(s) Entity Level 0 500 5 5 4 NE2 0 500 5 5 4 NE3 0 500 5 5 4 NE4 0 500 5 5 4
----End

This section provides the hyperlinks of the operation tasks associated with the ERPS feature.
Related Tasks
A.9.1 Creating ERPS Instances A.9.2 Setting Parameters of the Ethernet Ring Protocol A.9.3 Querying the Status of the Ethernet Ring Protection Switching Protocol

When an exception occurs in ERPS, the NE reports the relevant alarms and abnormal events.
Relevant Alarms
MULTI_RPL_OWNER The MULTI_RPL_OWNER indicates that more than one RPL owner exists on the Ethernet ring network.

None.
21.12 FAQs
This section provides answers to the questions that are frequently raised when the ERPS feature is used. Q: Why does ERPS fail when a fault occurs on the Ethernet ring link? A: The possible causes are as follows: l l The preset value of Hold-Off Time(ms) in the ERPS protocol parameters is long. It is recommended that you set this parameter to 0. Two or more Ethernet links are faulty on the Etherent ring network. ERPS functions for Ethernet services only when one Ethernet link becomes faulty. If more than one Ethernet link is faulty, ERPS fails. l The preset value of Control VLAN in the parameters of an ERPS protection instance is the same as the VLAN ID carried in Ethernet service packets or in inband DCN packets. If the VLAN ID is repeated, modify the value of Control VLAN on the NMS. l The ERPS protocol parameters are set different for the ring nodes on the Ethernet ring. On the NMS, set the ERPS protocol parameters to the same values for all the rings nodes on the Ethernet ring. l Different protection instances of ERPS contain one or more same ring ports. The OptiX RTN 620 does not support Ethernet tangent rings or Ethernet intersecting rings. That is, different protection instances of ERPS cannot contain one or more same ring ports. l More than one RPL owner exists on the Ethernet ring. Only one RPL owner can exist on an Ethernet ring.
Issue 05 (2010-10-30)
21-21
22 STP
22
About This Chapter
This chapter describes the Spanning Tree Protocol (STP). 22.1 Introduction This section provides the definition of STP/RSTP and describes its purpose. 22.2 Basic Concepts This section describes the basic concepts associated with STP/RSTP. 22.3 Specifications This section describes the specifications of STP/RSTP. 22.4 Reference Standards and Protocols This section describes the standards and protocols associated with STP/RSTP.
STP
22.5 Availability This section describes the support required by the application of the STP/RSTP feature and its dependency. 22.6 Principles The implementation of the STP complies with IEEE 802.1d, and the implementation of the RSTP complies with IEEE 802.1w. 22.7 Planning Guidelines Follow certain principles when you plan STP/RSTP. 22.8 Configuration Procedure To use the STP/RSTP, you need to configure the STP type and protocol parameters, and then enable the STP. 22.9 Configuration Example This section uses an example to describe how to plan and configure STP/RSTP according to network conditions. 22.10 Task Collection This section provides the hyperlinks of the operation tasks associated with STP/RSTP. 22.11 Relevant Alarms and Events When the status of a port on the bridge changes, the NE reports the relevant alarms.
22 STP
22.12 FAQs This section describes the answers to the frequently asked questions that are raised when the STP/RSTP is used.
22-2
Issue 05 (2010-10-30)
22 STP
22.1 Introduction
This section provides the definition of STP/RSTP and describes its purpose.
Definition
Spanning Tree Protocol (STP) is an algorithm described in IEEE 802.1d. This protocol configures any activated topology of any bridge connected to a LAN to a single spanning tree. Rapid Spanning Tree Protocol (RSTP) is an optimized STP, which features fast convergence after a topology change. The RSTP is compatible with the STP. They can be identified by the bridge that uses the RSTP for calculating the spanning tree.
Purpose
The STP/RSTP meets the following requirements: l l Configures any activated topology of any bridge to a single spanning tree. Releases the redundant data loop if there is any between two stations in the network topology. Reconfigures the spanning tree topology in the case of a bridge fault or an interrupted route, thus providing a certain protection, and prevents temporary data loops by automatically containing the bridges and ports of the bridges that are newly added into the LAN. Stabilizes the activated topology in a rapid manner. The finally activated topology can be predicted and repeated. In addition, the topology can be selected by managing the parameters of certain algorithms. Operations to the end stations are transparent. For example, the end stations are unaware of their attachment to a single LAN or a bridged LAN. A small part of the available bandwidth of the link is used to create or maintain the spanning tree, and the bandwidth does not increase with the expanding network size.
l l l l
STP/RSTP on the OptiX RTN 620 provides protection for a user network that has multiple access points. As shown in Figure 22-1, when user equipment accesses the OptiX RTN 620 through two different trails, you can start STP/RSTP for the ports on the OptiX RTN 620 that are connected to the user network. In this manner, the NEs can run the spanning tree algorithm together with the switches that run STP/RSTP, and generate a spanning tree trail. In this case, when an access link becomes faulty and the original spanning tree trail is interrupted, the spanning tree algorithm is run again to generate a new spanning tree trail. In this manner, the user network with multiple access points is protected.
Issue 05 (2010-10-30)
22-3
22 STP
Figure 22-1 Networking diagram of the STP/RSTP application
OptiX RTN
OptiX RTN
LAN Switch A STP/RSTP Pass Blocked Port
LAN Switch B
LAN Switch A
LAN Switch B
22.2 Basic Concepts

This section describes the basic concepts associated with STP/RSTP. l Bridge protocol data unit (BPDU) The STP transmits the BPDU among pieces of equipment to determine the network topology. The BPDU contains adequate information that is required to implement the calculation of the spanning tree. The BPDU is classified into the following categories: Configuration BPDU (CBPDU) The CBPDU refers to a packet that is used to calculate the spanning tree and maintain the spanning tree topology. The CBPDU contains the root bridge ID, root path cost, designated bridge ID, designated port ID, and related timing information. Topology change notification BPDU (TCN BPDU) The TCN BPDU refers to a packet that is used to notify the relevant equipment of the network topology change in the case of topology change. l Bridge ID The bridge ID is used to indicate a bridge. The bridge ID is 64-bit long. The most significant 16 bits indicate the priority of the bridge, and the least significant 48 bits indicate the MAC address of a certain bridge port. In the STP, the bridge ID also indicates the priority of the bridge. The smaller the value of the bridge ID, the higher the priority. l Port ID The port ID is used to identify a port on the bridge. The port ID is 16-bit long. The most significant eight bits indicate the priority of the port, and the least significant eight bits indicate the port number. In the STP, the port ID also indicates the priority of the port. The smaller the value of the port ID, the higher the priority. l Root bridge In a network that enables the STP, only one root bridge exists. The root bridge is selected based on the running of the STP. The bridge with the smallest bridge ID is selected as the root bridge. When a network that enables the STP is stabilized, only the root bridge generates and transmits the CBPDU periodically. Other bridges only relay the CBPDU. This can ensure a stable network topology. If the network topology is changed, the root bridge may also change.
22 STP
Root port The root port refers to a port on the bridge that transmits/receives frames to/from the root bridge. Each non-root bridge has only one root port. The root port is selected based on the running of the STP. The port of a bridge whose root path cost is the smallest is selected as the root port. If more than one port whose root path cost is the smallest exist, the port with the smallest port ID is selected as the root port.
Designated port The designated port refers to a port of a LAN that transmits/receives frames to/from the root bridge. Each LAN has only one designated port. The designated port is selected based on the running of the STP. The port that is connected to the LAN and whose root path cost is the smallest is selected as the designated port. If more than one port whose root path cost is the smallest exist and if these ports are on different bridges, the port whose bridge ID is the smallest is selected as the designated port. If more than one port whose root path cost is the smallest exist and if these ports are on the same bridge, the port with the smallest port ID is selected as the designated port.
Alternate port The alternate port refers to a port that is in the blocking state due to the learning of the BPDU transmitted by other bridges. The alternate port is only for the RSTP. The STP does not involve the alternate port.
Backup port The backup port refers to a port that is in the blocking state due to the learning of the BPDU transmitted by the bridge where the port resides. The backup port is only for the RSTP. The STP does not involve the backup port.
Path cost The path cost is used to indicate the status of the network that is connected to the port. The higher the rate of the port, the smaller the path cost.
Root path cost The root path cost refers to the cost of the path from a certain port to the root bridge, namely, the sum of path cost of all the passed ports from this port to the root bridge.
Port state In a network that enables the STP, the port can be any of the following states: Blocking A port in the blocking state only receives and processes the BPDU and does not transmit the BPDU. When a port is in the blocking state, it does not learn the MAC address and does not forward the user packet. Listening It is a transitional state. A port in the listening state transmits, receives, and processes the BPDU. When a port is in the listening state, it neither learns the MAC address nor forwards the user packet. Learning It is a transitional state. A port in the learning state transmits, receives, and processes the BPDU. When a port is in the learning state, it learns the MAC address but does not forward the user packet. Forwarding A port in the forwarding state transmits, receives, and processes the BPDU. When a port is in the learning state, it learns the MAC address and forwards the user packet.
Issue 05 (2010-10-30)
22-5
22 STP
Disabled A port in the disabled state does not forward frames, and does not implement the spanning tree algorithm or STP.
NOTE
The blocking, listening, and disabled states are combined into the discarding state in the RSTP.
Point-to-Point attribute The point-to-point attribute of a port can be set to adaptive connection, shared media, or link connection. If the attribute of a port is set to adaptive connection, the bridge determines the actual point-to-point attribute of the port according to the actual working mode of the port. If the port works in full-duplex mode, the actual point-to-point attribute of the port is "True". If the port works in half-duplex mode, the actual point-to-point attribute of the port is "False". If the point-to-point attribute of a port is set to shared media, the actual pointto-point attribute of the port is "False". If the point-to-point attribute of a port is set to link connection, the actual point-to-point attribute is "True". Only the port whose point-to-point attribute is "True" can transmit the rapid migration request and response. The point-to-point attribute is only for the RSTP. The STP does not involve the point-topoint attribute.
Edge port The edge port refers to the bridge port that is connected only to the LAN. If a port is set as an edge port and this port can receive the BPDU, the port is an actual edge port. If the role of this edge port is a designated port, the actual port state can be quickly migrated. The edge port is only for the RSTP. The STP does not involve the edge port.
Timer Port timers are classified into the following categories: Hold timer The hold timer is used to measure the interval between two CBPDU transmissions. The timeout value is the Hold Time of the bridge. Message age timer The message age timer is used to measure the age of the CBPDU packet recorded by a port. When the age of the CBPDU packet stored by the bridge exceeds the Message Age parameter, the bridge discards the packet. The Message Age parameter determines the initialization age when the CBPDU packet is stored in the bridge. The Message Age parameter is 0 when the root bridge generates the packet. Each time the packet is forwarded to a port, a fixed increment value is added to the Message Age parameter. Forward delay timer The forward delay timer is used to measure the holding time of a port in the listening state and in the learning state. When the listening state remains for a period that is the same as the value of the Forward Delay parameter, the port changes to the learning state. When the learning state remains for a period that is the same as the value of the Forward Delay parameter, the port changes to the forwarding state. Bridge timers are classified into the following categories: Hello timer The hello timer is used to measure the interval when the bridge transmits the CBPDU packet. The timeout value is the Bridge Hello Time of the bridge. Topology change notification timer The topology change notification timer indicates the duration when the bridge periodically transmits the TCN. The timer is used to notify the designated bridge in the
22-6
Issue 05 (2010-10-30)
22 STP
LAN that is attached to the root port of the bridge of any detected topology change. The timeout value is the Bridge Hello Time of the bridge. Topology change timer In the case of the root bridge, when receiving the TCN, the bridge transmits the TCN after the topology change is complete and the time period indicated by the topology change timer times out. The timeout value is the Topology Change Time of the bridge.
NOTE
The Max Age, Hello Time, and Forward Delay parameters that are used by different bridges are unified to the values of these three parameters that are used by the root bridge, by mutually transmitting the CBPDU.
22.3 Specifications
This section describes the specifications of STP/RSTP. Table 22-1 lists the specifications of STP/RSTP. Table 22-1 Specifications of STP/RSTP Item Specification EMS6 Type of the STP STP RSTP Application scope of the STP Bridge parameters Port parameters All the ports on the bridge on which the STP is enabled Bridge priority and bridge timer Port priority, port path cost, parameter for enabling the edge port, and settings of automatic detection and point-to-point attribute of the edge port Supported Supported The working mode of the STP used by the port can be automatically migrated according to the type of the STP used by the opposite equipment if the system is enabled with the RSTP. For the rapid migration, the maximum stabilization duration is less than one second; for the non-rapid migration, the maximum stabilization duration is less than one minute. EFP6
Querying the running information of the STP Resetting the STP Migrating the port protocol
Topology stabilization duration

This section describes the standards and protocols associated with STP/RSTP.
22 STP
The following protocols are associated with STP/RSTP: l l IEEE 802.1d: Media Access Control (MAC) Bridges IEEE 802.1w: Rapid Reconfiguration of Spanning Tree
22.5 Availability
This section describes the support required by the application of the STP/RSTP feature and its dependency.

Table 22-2 Hardware and version support Feature STP Applicable Board EMS6 EFP6 RSTP EMS6 EFP6 Applicable Hardware Version All the versions All the versions All the versions All the versions Applicable Product Version V100R002 and later V100R005C00 and later V100R002 and later V100R005C00 and later
Feature Dependency
The dependency between the STP/RSTP feature and other features is as follows: The STP/RSTP protocol is only applicable to a bridge. The port on which the STP/RSTP is enabled cannot function as an ERPS port.
22.6 Principles
The implementation of the STP complies with IEEE 802.1d, and the implementation of the RSTP complies with IEEE 802.1w. The STP algorithm is run as follows: 1. In the initialization state, all the ports on all the bridges are in the listening state. In this case, each port generates the CBPDU, and the CBPDU considers the bridge where the port resides as the root bridge and the root path cost value is 0. Each port transmits the CBPDU periodically, and the period is equal to the value of the Hello Time of the bridge. Each bridge compares the information of the CBPDU that is received on the port with the CBPDU information that is stored by that port. The bridge compares CBPDU information as follows:
2.
22 STP
(1) The bridge compares the root bridge IDs. When the root bridge ID is smaller, the quality is better. (2) If the root bridge IDs are the same, the bridge compares the root path cost values. When the root path cost value is smaller, the quality is better. (3) If the root path cost values are the same, the bridge compares the designated bridge IDs. When the designated bridge ID is smaller, the quality is better. (4) If the designated bridge IDs are the same, the bridge compares the designated port IDs. When the designated port ID is smaller, the quality is better. 3. If the information of the CBPDU that is received on the port is better, the bridge replaces the information of the CBPDU that is originally stored by the port. If the root bridge ID or the root path cost value in the information of the CBPDU that replaces the information of the CBPDU originally stored by the port is smaller than the root bridge ID or the root path cost value recorded by the bridge, the bridge needs to process it as follows: l The bridge stores the information of the CBPDU (including the root bridge ID, root path cost, Message Age, and corresponding timers). l The bridge updates the root bridge ID and root path cost at the same time (the root path cost of the bridge is equal to the sum of the root path cost of the port that stores the CBPDU and the root path cost of the port that receives the CBPDU). l The designated port updates the designated root bridge and the root path cost at the same time (the root path cost of the designated port is equal to the sum of the root path cost of the bridge and the path cost of the designated port). l The designated port relays the CBPDU. If the information of the CBPDU that is received at the port is worse than the CBPDU information that is originally stored by the port, the port transmits the stored CBPDU as a response. 4. 5. 6. If a bridge maintains a root bridge ID that is the same as its bridge ID and the root path cost is 0, this bridge is the root bridge. The root bridge sets the path cost of each port on it to 0. If a bridge is a non-root bridge, it considers the port that receives the best CBPDU information as the root port. If a bridge is a non-root bridge, it considers any of the following ports as the designated port: l The bridge ID and port ID of a port are the same as the designated bridge ID and port ID that are recorded by the port respectively. l The root bridge ID of the bridge is different from the root bridge ID that is recorded by the port. l The root path cost value of a port (namely, the sum of the root path cost value of the bridge and the path cost value of the port) is smaller than the root path cost value that is recorded by the port. l The root path cost value of a port is the same as the root path cost value that is recorded by the port, but the bridge ID is smaller than the designated bridge ID of the port. l The root path cost value of a port is the same as the root path cost value recorded by the port, and the bridge ID is the same as the designated bridge ID of the port. The port ID, however, is smaller than the designated ID of the port. 7. When the time period indicated by the Forward Delay parameter set for the listening state timer of the port times out, the root port and the designated port change to the learning state. When the learning state remains for a period that is the same as the value of the Forward
Issue 05 (2010-10-30)
22 STP
Delay parameter, the root port and the designated port change to the forwarding state. The other ports change to the blocking state. 8. If a trail becomes faulty, the root port on this trail no longer receives new CBPDUs. Therefore, the original CBPDU is discarded due to timeout. In this case, the spanning tree is calculated again, and a new trail will be generated to replace the faulty trail, thus restoring the connectivity of the network.
Improvement in the RSTP

Compared with the STP, the RSTP is improved as follows: l Classification of port roles The port roles in the RSTP are further classified into the following types: root port, designated port, alternate port, and backup port. l Classification of port states The blocking, listening, and disabled states are combined into the discarding state in the RSTP. l Quick migration between port states The quick migration between port states can be classified into the quick migration between root port states, quick migration between designated port states, quick migration between alternate port states, and quick migration between backup port states. Quick migration between root port states If a backup port is the optimal (in a period less than twice of the Hello Time), it changes to the forwarding state without any delay. In addition, the designated port of the original root port (that functions in a period less than the Forward Delay) changes to the discarding state. Quick migration between designated port states If an edge port functions as a designated port, the port changes to the forwarding state without any delay. The designated port the actual point-to-point attribute of which is "True" can implement quick migration between port states through rapid migration between the request process and the response process. Quick migration between alternate port states and backup port states The alternate port and the backup port change to the discarding state without any delay.

Follow certain principles when you plan STP/RSTP. l l The STP/RSTP must be enabled only when the loop occurs on the link that is connected to the customer equipment. It is recommended that you enable the STP/RSTP on only the port on the bridge that is connected to the customer equipment. The STP/RSTP cannot be enabled on the port that is connected to the network equipment. It is recommended that you enable the RSTP if the STP type is not specified on the connected customer equipment.
22-10
22 STP
You can set bridge parameters, port parameters, and point-to-point attribute of the STP/ RSTP according to the requirements of the customer equipment. Unless otherwise specified, these parameters take default values.

To use the STP/RSTP, you need to configure the STP type and protocol parameters, and then enable the STP. Table 22-3 Procedure for configuring the STP/RSTP Step 1 Operation A.10.1 Configuring the Spanning Tree Protocol A.10.2 Setting the Parameters of Spanning Tree Protocol Description Required. Set the parameters as follows: l Set Protocol Enabled to Disabled to disable the STP/RSTP. l Set Protocol Type to the planned STP type. Required. Set the parameters as follows: l Set the following bridge parameters according to the network plan: Priority (Bridge Parameter), Max Age(s), Hello Time (s), Forward Delay(s), and TxHoldCount (per second). l Set the following port parameters according to the network plan: Priority (Port Parameters), Port Path Cost, Admin Edge Attribute, Protocol Enabled, and Auto Edge Detection.
NOTE Set Protocol Enabled of the port that is connected to the access equipment to Enabled and set Protocol Enabled of the port that is connected to the transmission equipment to Disabled.
A.10.1 Configuring the Spanning Tree Protocol
Required. Set the parameter as follows: Set Protocol Enabled to Enabled.

This section uses an example to describe how to plan and configure STP/RSTP according to network conditions. 22.9.1 Networking Diagram This section describes the networking information about the NEs. 22.9.2 Service Planning The service planning information contains all the parameters required for configuring the NE data. 22.9.3 Configuration Process This section describes the procedure of data configuration.
22 STP

This section describes the networking information about the NEs. As shown in Figure 22-2, NE1 is the OptiX RTN 620. Through the configuration of the EPLAN service, NE1 transmits the Ethernet access service to NE2. l l l l l The VB ID of the configured EPLAN service is 1 and the VB Name is VB1. The Ethernet port of LAN switch 1 is connected to port 1 on the EMS6 board in slot 4 on NE1 and is mounted to logical port 1 on VB1. The Ethernet port of LAN switch 2 is connected to port 2 on the EMS6 board in slot 4 on NE1 and is mounted to logical port 2 on VB1. Port 5 on the EMS6 board in slot 4 on NE1 is connected to the GE port on the IFH2 board in slot 5 and is mounted to logical port 3 on VB1. The IFH2 board in slot 5 carries the radio link to NE2.
NE1 and the Layer 2 switches LAN switch 1 and LAN switch 2 on the access side need to work with the RSTP that uses LAN switch 1 as the root switch enabled. This prevents the network loop on the access side, thus protecting the network. Figure 22-2 Networking diagram
LAN Swich 1 Root ETH RNC LAN Swich 2 NE1 NE2 NodeB
Port group

Protocol Information
Table 22-4 provides the information about the STP/RSTP configuration on NE1. Table 22-4 Protocol information Parameter VB Protocol type Protocol enabled
22-12
NE1 VB1 RSTP Enableda

Issue 05 (2010-10-30)
22 STP
NOTE
a: It is recommended that you set this parameter to Disabled when creating an RSTP port group. After configuring all the RSTP parameters, set this parameter to Enabled. In this manner, the RSTP is not affected due to RSTP parameter change.
Information About Bridge Parameters

Configure parameters of bridge VB1 of NE1 according to the planned values of the LAN switch on the access side, as shown in Table 22-5. Table 22-5 Information about bridge parameters Parameter Priority (bridge parameter) Max Age (s) Hello Time (s) Forward Delay (s) TxHoldCout (times/second) NE1 32768 20 2 15 6
Information About Port Parameters

Configure parameters of the Ethernet port on NE1 according to the planned values of the LAN switch on the access side, as shown in Table 22-6. Table 22-6 Information about port parameters Parameter NE1 PORT1 Priority (port parameter) Port path cost Edge port enabled Protocol enabled Auto edge port detection disabled 128 2 Disabled Enabled Disabled PORT2 128 2 Disabled Enabled Disabled PORT5 Disabled Disabled Disabled
NOTE
In this example, PORT1, PORT2, and PORT5 are mounted to port 1, port 2, and port 3.
Issue 05 (2010-10-30)
22-13
22 STP

Procedure
Step 1 See A.10.1 Configuring the Spanning Tree Protocol and configure the STP/RSTP. The values for enabling the STP/RSTP on NE1 are provided as follows. Parameter Protocol Enabled Protocol Type Value Range Disabled RSTP
Step 2 See A.10.2 Setting the Parameters of Spanning Tree Protocol and configure STP/RSTP parameters. The values for the relevant parameters of bridge VB1 of NE1 are provided as follows. Parameter Priority (Bridge Parameter) Max Age(s) Hello Time(s) Forward Delay(s) TxHoldCount (per second) Value Range 32768 20 2 15 6
The values for the parameters of the Ethernet port on NE1 are as follows. Parameter Value Range PORT1 Priority (Port Parameters) Port Path Cost Admin Edge Attribute Protocol Enabled Auto Edge Detection 128 2 Disabled Enabled Disabled PORT2 128 2 Disabled Enabled Disabled PORT5 Disabled Disabled Disabled
Step 3 See A.10.1 Configuring the Spanning Tree Protocol and configure the STP/RSTP. The values for enabling the STP/RSTP on NE1 are provided as follows.
22 STP
Parameter Protocol Enabled
Value Range Enabled
----End

This section provides the hyperlinks of the operation tasks associated with STP/RSTP.
Related Tasks
A.10.1 Configuring the Spanning Tree Protocol A.10.2 Setting the Parameters of Spanning Tree Protocol A.10.3 Querying the Running Information About the Spanning Tree Protocol

When the status of a port on the bridge changes, the NE reports the relevant alarms.
Relevant Alarms
None.
Relevant Events
None.
22.12 FAQs
This section describes the answers to the frequently asked questions that are raised when the STP/RSTP is used. Q: What are the similarities and differences between RSTP and ERPS for the OptiX RTN 620? A: Both the RSTP and ERPS support the Ethernet ring protection and prevent the network loop. The differences lie in the working principle. Both have advantages. l The RSTP supports the Ethernet ring and mesh network. The working principle of the RSTP is complicated, and thus obtaining the specific service flow is difficult. In addition, the RSTP occupies a large number of network resources. When the network is faulty, the time required for re-stabilizing the network topology is long. The ERPS supports only the Ethernet ring and does not support the tangent ring or intersecting ring. The working principle of the ERPS is simple. The network resources occupied by the ERPS are smaller than the network resources occupied by the RSTP. When the network is faulty, the time required for protection switching is short.
Q: Can STP and RSTP coexist on the same network? If they can, can protection switching function normally?
22 STP
A: RSTP is compatible with STP. Therefore, they can coexist on the same network. When STP is started for several devices, and RSTP is started for other devices, STP is used for protecting the network. Q: What if packet loss occurs when the STP protocol is configured on the local and opposite equipment? A: Check whether the STP protocol is the same on both ends. Then, check whether the parameters of the STP protocol are configured consistently on both ends. Finally, check whether the parameters of the ports are configured consistently on both ends.
22-16
Issue 05 (2010-10-30)
23 IGMP Snooping
23
About This Chapter
This chapter describes the IGMP Snooping protocol.
IGMP Snooping
23.1 Introduction This section provides the definition of IGMP Snooping and describes its purpose. 23.2 Basic Concepts This section describes the basic concepts associated with IGMP Snooping. 23.3 Specifications This section describes the specifications of IGMP Snooping. 23.4 Reference Standards and Protocols This section describes the standards and protocols associated with IGMP Snooping. 23.5 Availability This section describes the support required by the application of the IGMP Snooping feature and its dependency. 23.6 Principles IGMP Snooping creates and maintains the mapping relationships between group members and switch ports by sensing IGMP packets. This ensures that multicast packets can be transmitted only to the ports that are connected to multicast users. 23.7 Planning Guidelines Follow certain guidelines when you plan IGMP Snooping. 23.8 Configuration Procedure To use the IGMP Snooping protocol, you need to set the IGMP Snooping parameters. In addition, you can set the static routing member as required. 23.9 Configuration Example This section uses an example to describe how to plan and configure IGMP Snooping according to network conditions. 23.10 Task Collection This section provides the hyperlinks of the operation tasks associated with IGMP Snooping. 23.11 Relevant Alarms and Events
23 IGMP Snooping
If the multicast table entries or multicast members reach the maximum number, the NE reports the corresponding abnormal event. 23.12 FAQs This section provides the answers to the questions that are frequently raised when the IGMP Snooping feature is used.
23-2
Issue 05 (2010-10-30)
23 IGMP Snooping
23.1 Introduction
This section provides the definition of IGMP Snooping and describes its purpose.
Definition
As a Layer 2 multicast protocol, the IGMP Snooping protocol creates and maintains the mapping relationships between group members and switch ports by sensing IGMP packets. This ensures that multicast packets can be transmitted only to the ports that are connected to multicast users. When the multicast router is connected to the host by using a bridge, the bridge broadcasts multicast packets to all the ports if the IGMP Snooping protocol is disabled on the bridge, as shown in Figure 23-1; the bridge forwards multicast packets only to the ports that are connected to multicast users if the IGMP Snooping protocol is enabled on the bridge. Figure 23-1 Transmission of multicast packets (with the IGMP Snooping protocol disabled)
Internet/ Intranet Video stream
VOD server Multicast router Video stream Layer 2 Ethernet switch Video stream Video stream Video stream
Multicast group member
Non-multicast Non-multicast group member group member
Issue 05 (2010-10-30)
23-3
23 IGMP Snooping
Figure 23-2 Transmission of multicast packets (with the IGMP Snooping protocol enabled)
Internet/ Intranet Video stream
VOD server Multicast router Layer 2 Ethernet switch Video stream Video stream
Multicast group member
Non-multicast Non-multicast group member group member
Purpose
The IGMP Snooping function improves bandwidth utilization and enhances information security.
23.2 Basic Concepts

This section describes the basic concepts associated with IGMP Snooping. l Multicast Multicast transmission provides one-to-many network connections between a transmitter and multiple receivers. Multicast allows a transmitter to send several copies of data packets to multiple receivers. It increases data transmission efficiency and reduces the possibility of congestion on backbone networks. l IP multicast protocol Based on the IP protocol stack, the IP multicast protocol uses a class D IP address that is similar to the unicast address to indicate a group. When a packet is transmitted to all the IP hosts in a multicast group, the calling and access mode is similar to the calling and access mode of the unicast. The hosts in an IP multicast group can join or quit this multicast group at any time and at any location, without restrictions on the number of members. The multicast router does not store the member relationships of all the hosts. The router stores the information only about whether any host on the physical subnetwork belongs to a specific multicast group. The host stores the information only about the multicast groups that it joins. l IGMP protocol The IGMP protocol helps to create a multicast group between the host and the multicast router, and maintains member relationships of the multicast group. l
23-4
Router port
23 IGMP Snooping
A port that is connected to the multicast router is a router port. In the IGMP Snooping protocol, a port that receives the IGMP general query packet functions as a router port. l Multicast member port A port that is connected to the multicast group member is a multicast member port. A multicast group member refers to a host that joins a multicast group. l Multicast group A multicast group records the mapping relationships between router ports, MAC multicast addresses, and multicast group members. A multicast group is also called a multicast table entry. Multicast table entries are classified into static multicast table entries and dynamic multicast table entries. A static multicast table entry is manually configured by users and will not be aged. A dynamic multicast table entry is acquired through the SVL/IVL method, and will be aged.
NOTE
If a multicast group is not updated in a certain period (that is, no IGMP request from its connected router port is received), all the multicast groups that are associated with the router port are deleted. This mechanism is called aging, and this period is called aging time.
Maximum query response time When the bridge transmits the IGMP query packet to a multicast member port, the router port starts the maximum query response timer. If the bridge does not receive the IGMP report packet within the maximum query response time, the bridge adds one to the noresponse times of the multicast member port. When the no-response times of the port exceed the preset threshold, the bridge deletes the multicast member from the multicast group.
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 host to the multicast router. The IGMP report packet is used to applying for the joining of a multicast group or to respond to the IGMP query packet.
23.3 Specifications
This section describes the specifications of IGMP Snooping. Table 23-1 lists the specifications of IGMP Snooping. Table 23-1 Specifications of IGMP Snooping Item Number of supported static multicast groups Specification 512
Issue 05 (2010-10-30)
23-5
23 IGMP Snooping
Item Number of supported dynamic multicast groups No-response times Version of supported IGMP packets
Specification 512 1-4 V1 V2
Multicast aging time Processing of unknown multicast packets
1 to 120 minutes Discarding Broadcasting

This section describes the standards and protocols associated with IGMP Snooping. The following protocol is associated with IGMP Snooping: l IETF RFC 4541: Considerations for Internet Group Management Protocol (IGMP) and Multicast Listener Discovery (MLD) Snooping Switches
23.5 Availability
This section describes the support required by the application of the IGMP Snooping feature and its dependency.

Table 23-2 Hardware and version support Feature IGMP Snooping Applicable Board EMS6 EFP6 Applicable Hardware Version All the versions All the versions Applicable Product Version V100R003 and later V100R005C00 and later
Feature Dependency
l l l The IGMP Snooping feature can be enabled only for the EPLAN and EVPLAN services. One LAG can be a member of an IGMP Snooping multicast group. ERPS does not affect the IGMP Snooping feature.
23-6
Issue 05 (2010-10-30)
23 IGMP Snooping
23.6 Principles
IGMP Snooping creates and maintains the mapping relationships between group members and switch ports by sensing IGMP packets. This ensures that multicast packets can be transmitted only to the ports that are connected to multicast users.
Processing Flow
An 802.1q bridge processes the IGMP Snooping protocol as follows: 1. If 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 a router port. (2) If this port is not learnt, the bridge records this port as a router port. (3) If the port that receives the packet is already recorded as a router port, the bridge broadcasts the packet in a specific multicast group if there is any and starts the timer for counting the maximum query response time. Otherwise, the bridge broadcasts the packet in the VLAN domain of the 802.1q bridge. After receiving the query packet, the router port updates the MAC address aging time of the port. 2. If 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 VLAN domain of the 802.1q bridge. (2) If this multicast record is not learnt and if no multicast group exists, the bridge creates a multicast group and creates the mapping relationships between the router ports, MAC multicast addresses, and multicast group members by considering this port as the multicast member port. (3) If this multicast record is not learnt, but this port is not included in the multicast member ports of a specific multicast group, the multicast group adds this port as a multicast member port. (4) If this multicast record is learnt, the bridge resets the count of no-response times for this multicast member. 3. If the bridge receives the multicast packet, it processes this packet as follows: l Queries all the multicast groups of the bridge. l If a multicast group that matches the multicast address and the VLAN ID exists in the multicast table, the bridge forwards the packet to this multicast group. l If such a multicast group does not exist, the bridge discards the multicast packet or broadcasts the packet in the VLAN range based on the NMS setting. 4. The bridge processes the aging of dynamic multicast members as follows: l If the maximum query response time times out, the bridge adds one to the no-response times of the multicast member. l If the no-response times of a multicast member exceeds the threshold, the bridge deletes this multicast member port. l When a multicast group member quits its group, the multicast management router sends the specific query packet to all the connected switches (applicable only to IGMP V2).
23 IGMP Snooping
In this manner, the router determines whether any member exists in the group. If there are no members, the router deletes this multicast group. 5. The bridge ages a dynamic router port as follows: After the VLAN learns a router port, a timer for counting the aging time is enabled at this port. If the timer expires, the bridge deletes the router port. If the port is the only router port in the VLAN domain, the bridge deletes all the multicast groups that are learnt in the VLAN domain. 6. The bridge processes the leave packet as follows: If the bridge receives a leave packet, the bridge deletes the corresponding multicast member from the multicast group. If the port is the only multicast member port in the VLAN domain, the bridge deletes this multicast group.
NOTE
An 802.1d bridge processes the IGMP Snooping protocol in a similar way. Unlike the 802.1q bridge, the 802.1d bridge learns the packet by using the SVL method rather than the IVL method, and the 802.1d bridge broadcasts the packet without the restriction of the VLAN domain.
Version
The IGMP query packet is available in the following versions: V1, V2, and V3. The Ethernet switching board can process versions V1 and V2. V2 is compatible with V1. Compared with V1, V2 is improved as follows: l Supports the multicast group leave packet. This packet can efficiently decrease the delay generated in the process of deleting a multicast group. l Supports the specific query packet. This packet allows broadcasting the IGMP query packet only in a specific multicast group.

Follow certain guidelines when you plan IGMP Snooping. l 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. 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.

To use the IGMP Snooping protocol, you need to set the IGMP Snooping parameters. In addition, you can set the static routing member as required.
23-8
Issue 05 (2010-10-30)
23 IGMP Snooping
Table 23-3 Procedure for configuring IGMP Snooping Step 1 Operation A.11.1 Configuring the IGMP Snooping Protocol Description Required. The parameters need to be set according to the service planning. It is recommended that you use the default values. Optional. The parameters need to be set according to the service planning. It is recommended that you use the default values.
A.11.2 Modifying the Aging Time of a Multicast Table Item

This section uses an example to describe how to plan and configure IGMP Snooping according to network conditions. 23.9.1 Networking Diagram This section describes the networking information about the NEs. 23.9.2 Service Planning The service planning information contains all the parameters required for configuring the NE data. 23.9.3 Configuration Process This section describes the procedure of data configuration.

This section describes the networking information about the NEs. As shown in Figure 23-3, NE1 functions as the end node and accesses the network through the 3-IFU2 board. The EVPLAN service based on the 802.1q bridge is configured on NE1 to provide multicast services. To improve multicast efficiency, enable the IGMP Snooping feature.
Issue 05 (2010-10-30)
23-9
23 IGMP Snooping
NE1 Internet/Intranet FE FE FE Ethernet switch Host Ethernet switch VOD server
Host
Host
Host
Host

The service planning information contains all the parameters required for configuring the NE data. In this example, the IGMP Snooping information is as follows: The multicast aging time is set to 10 minutes according to the requirements of the multicast router.

Procedure
Step 1 See A.11.1 Configuring the IGMP Snooping Protocol and configure the IGMP Snooping protocol. The values for the parameters of Enable IGMP Snooping Protocol are provided as follows. Parameter Value Range NE1 Protocol Enable Enabled
Step 2 See A.11.2 Modifying the Aging Time of a Multicast Table Item and modify the aging time of a multicast table entry. The values of Multicast Aging Time are provided as follows.
23 IGMP Snooping
Parameter
Value Range NE1
Multicast Aging Time (Min)
10
----End

This section provides the hyperlinks of the operation tasks associated with IGMP Snooping.
Related Tasks
A.11.1 Configuring the IGMP Snooping Protocol A.11.2 Modifying the Aging Time of a Multicast Table Item A.11.3 Querying the Running Information of the IGMP Snooping Protocol

If the multicast table entries or multicast members reach the maximum number, the NE reports the corresponding abnormal event.
Relevant Alarms
None.

Multi Cast Group Address Used Up This event indicates that on the NE that is enabled with the IGMP Snooping function, the multicast table entries or multicast members reach the maximum number.
Relevant RMON Performance Events

For details, see RMON Event Reference.
23.12 FAQs
This section provides the answers to the questions that are frequently raised when the IGMP Snooping feature is used. Q: Does IGMP Snooping change the packets that are transmitted between the multicast server and the host?
23 IGMP Snooping
A: IGMP Snooping is a multicast constraint mechanism that is adopted by the Layer 2 equipment to manage and control multicast groups. IGMP Snooping limits the packet transmitted by the multicast server within the multicast groups. This process, however, does not change the packet.
23-12
Issue 05 (2010-10-30)
24 Link Aggregation Group
24
About This Chapter
Link Aggregation Group
This chapter describes the link aggregation group (LAG) feature. 24.1 Introduction This section provides the definition of LAG and describes its purpose. 24.2 Basic Concepts This section describes the basic concepts associated with LAGs. 24.3 Specifications This section describes the specifications of LAGs. 24.4 Reference Standards and Protocols This section describes the standards and protocols associated with LAGs. 24.5 Availability This section describes the support required by the application of the LAG feature and its dependency. 24.6 Principles The LACP protocol is used to implement dynamic aggregation and de-aggregation of Ethernet links. Implementation of LAGs complies with IEEE 802.3ad. 24.7 Planning Guidelines Follow certain principles when you plan LAGs. 24.8 Configuration Procedure To use the LAG protocol, you need to configure a LAG. In addition, you can configure the priorities of the ports in the LAG as required. 24.9 Configuration Example This section uses an example to describe how to plan and configure a LAG according to network conditions. 24.10 Task Collection This section provides the hyperlinks of the operation tasks associated with LAGs. 24.11 Relevant Alarms and Events
When the LAG is unavailable or a certain member in the LAG is unavailable, the system control board reports the relevant alarms. 24.12 FAQs This section describes the answers to the frequently asked questions that are raised when the LAG feature is used.
24-2
Issue 05 (2010-10-30)
24.1 Introduction
This section provides the definition of LAG and describes its purpose.
Definition
Link aggregation allows one or more links that are attached to the same equipment to be aggregated together to form a LAG. In this manner, a MAC client can consider a LAG as a link.
Purpose
As shown in Figure 24-1, a LAG provides the following functions: l Increased bandwidth A LAG provides users with a cost-effective method for increasing the link bandwidth. Users obtain data links with higher bandwidths by combining multiple physical links into one logical link without upgrading the existing equipment. The bandwidth of the logical link is equal to the sum of the bandwidths of the physical links. The aggregation module distributes the traffic to different links by using the load sharing algorithm, thus providing the load sharing function for links. l Increased availability The links in a LAG dynamically back up each other. When a link fails, the other links in the LAG quickly take over. The process in which link aggregation starts the backup link is associated only with the links in the same LAG, and the links not in the LAG are not involved. Figure 24-1 Link aggregation group
Link 1 Link 2 Ethernet packet Link 3 LAG Ethernet packet
24.2 Basic Concepts

This section describes the basic concepts associated with LAGs. 24.2.1 LAG Types A LAG can be classified into manual aggregation or static aggregation based on the aggregation type. A LAG can also be classified into load sharing and load non-sharing based on the load type. 24.2.2 Port Types
In a LAG, ports are classified into main ports and slave ports. 24.2.3 Switching Conditions A service is switched between ports when a port fails or the key chip of a port is faulty. 24.2.4 Switching Impact During LAG switching (less than 500 ms), all the services on the link are interrupted.
24.2.1 LAG Types

A LAG can be classified into manual aggregation or static aggregation based on the aggregation type. A LAG can also be classified into load sharing and load non-sharing based on the load type.
Aggregation Types
A LAG supports the following aggregation types: l Manual aggregation A user manually creates a LAG. When a member port is added or deleted, the link aggregation control protocol (LACP) is not started. A port is in the up or down state. The system determines whether to aggregate a port according to its physical state (UP or DOWN), working mode, and rate.. l Static aggregation When a user adds or deletes a member port in the created LAG, the Link Aggregation Control Protocol (LACP) needs to be enabled. The LAG determines the status of each member port by using the LACP protocol. A member port can be in selected, standby, or unselected state. Static aggregation is more accurate and more effective than manual aggregation in controlling link aggregation.
NOTE
In a LAG: l When the port status is selected, the port can bear services. l When the port status is standby, the port cannot bear services. l When the port status is unselected, the port does not meet the aggregation requirement. For example, the port fails to receive the LACP packets from the opposite end in a timeout duration.
Load Sharing
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 a LAG share the load. In load sharing mode, the bandwidth of a link increases. When a member is added to or deleted from a LAG, or when a certain link fails, the traffic is re-allocated automatically. The load sharing algorithms are described as follows: AUTO Based on MAC addresses, including based on the source MAC address, destination MAC address, and source MAC address xor destination MAC address
Based on IP addresses, including based on the source IP address, destination IP address, and source IP address xor destination IP address l 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 a selected link in a LAG fails, the system selects a link from the standby links in the LAG to replace the failed link. When a LAG is set to a load non-sharing mode, it can be set to revertive or non-revertive. When a LAG is set to revertive, services are switched back to the working link after this link is restored to normal. When a LAG is set to non-revertive, the status of the LAG does not change even after the working link is normal. That is, services are still transmitted on the standby link.
24.2.2 Port Types

In a LAG, ports are classified into main ports and slave ports.
Main Port
Representing a logical port aggregated by ports of a LAG, a main port has the following features: l l l l l A main port represents a LAG to participate in service configuration. A LAG has and can only have one main port. The main port can be in selected, standby, or unselected state. A main port must be in the affiliated aggregation group until the aggregation group is deleted. When the aggregation group is deleted, all the services in the aggregation group continue to exist on the main port and no services are lost.
Slave Port
In a LAG, the ports other than the main port are slave ports. A slave port has the following features: l l l l A slave port cannot participate in service configuration. A LAG can have several slave ports. A slave port can be in selected, standby, or unselected state. A slave port can be added to or deleted from a LAG by using the NMS.

A service is switched between ports when a port fails or the key chip of a port is faulty. Table 24-1 Switching conditions Switching Condition A certain Ethernet port is in the link down state. Description If the member port of a LAG is an Ethernet port and this port is in the link down state, the ETH_LOS alarm is reported.
24-5
Issue 05 (2010-10-30)
Switching Condition The port on a certain Ethernet board is faulty. A failure on the link is detected by running of the LACP protocol.
Description If the port on a certain Ethernet board becomes faulty, LAG switching is triggered. If the LACP protocol packets are not received for three consecutive periods (3s), the link is considered unavailable and then LAG switching is triggered.

During LAG switching (less than 500 ms), all the services on the link are interrupted.
24.3 Specifications
This section describes the specifications of LAGs. Table 24-2 lists the specifications of LAGs. Table 24-2 Specifications of LAGs Item Specification EFP6 Maximum number of supported LAGs Type of supported ports in a LAG Number of available ports in a LAG 11 FE port VCTRUNK port 6 (FE port) 16 (VCTRUNK port) EMS6 7 FE/GE port VCTRUNK port 4 (FE port) 2 (GE port) 8 (VCTRUNK port) LAG type Manual aggregation Static aggregation Load sharing Load sharing Load non-sharing (with only one slave port supported) Load sharing type (in load sharing mode only) Based on the source MAC address xor the destination MAC address Based on the source IP address xor the destination IP address Revertive mode (in load nonsharing mode only)a Switching time
24-6
Revertive Non-revertive Less than 500 ms

Issue 05 (2010-10-30)
Item
Specification EFP6 EMS6
Distributed LAG
Not supported
NOTE
a: All the LAGs of a board use the same load sharing algorithm.

This section describes the standards and protocols associated with LAGs. The following protocol is associated with LAGs: l IEEE 802.3ad: Carrier sense multiple access with collision detection (CSMA/CD) access method and physical layer specifications
24.5 Availability
This section describes the support required by the application of the LAG feature and its dependency.

Table 24-3 Hardware and version support Feature LAG Applicable Board EMS6 EFP6 Applicable Hardware Version All the versions All the versions Applicable Product Version V100R003 and later V100R005C00 and later
Feature Dependency
l l The Ethernet ports in a LAG must be of the same type. FE ports and GE ports cannot be aggregated. In the case of the Hybrid radio configured with 1+1 IF protection, the IFH2 board must be interconnected with the EMS6 board; the interconnected port of the EMS6 board must adopt manual aggregation and must be set to load non-sharing and non-revertive.
24.6 Principles
The LACP protocol is used to implement dynamic aggregation and de-aggregation of Ethernet links. Implementation of LAGs complies with IEEE 802.3ad.
Procedure for Creating a Static LAG

The LACP protocol is developed based on IEEE 802.3ad and performs the following functions: l The LACP protocol provides the data switching equipment with a standard negotiation mode. In this manner, the system can automatically aggregate links according to its configuration and enable the aggregated links to transmit and receive data. The LACP protocol maintains the status of the aggregated links. When the aggregation conditions change, the LACP protocol automatically adjusts or releases the LAG.
As shown in Figure 24-2, the LACP protocol aggregates links as follows: 1. Equipment A and equipment B exchange LACP packets through PORT1, PORT2, PORT3, and PORT4. An LACP packet contains the information such as the system priority, system MAC address, port priority, port ID, and operation key. 2. After receiving an LACP packet from equipment A, equipment B compares the information in the LACP packet with the information saved by the other ports and selects the ports that can be aggregated. After receiving an LACP packet from equipment B, equipment A compares the information in the LACP packet with the information saved by the other ports and selects the ports that can be aggregated. Equipment A and equipment B reach agreement on the ports that can be added into a LAG and then form a LAG. Equipment A negotiates with equipment B on the parameters of the LAG, including the main port and revertive mode. The rule for negotiation is as follows: A LAG adopts the main port and revertive mode parameters set on the equipment whose system priority value is smaller. As shown in Figure 24-2, the following assumptions are made: The system priority of the LAG on equipment A is 100, the main port is PORT1, and the LAG is set to revertive. The system priority of the LAG on equipment B is 10, the main port is PORT2, and the LAG is set to non-revertive. In this case, the negotiation result is as follows: The link corresponding to the main port PORT2 on equipment B functions as the main link, and the LAG is a revertive one.
NOTE
3.
4. 5.
If the system priorities and port priorities of the interconnected LAGs are the same, use the parameters of the LAG in which the MAC address of the main port is smaller.
Figure 24-2 Application of the LACP protocol

Equipment A LACP packet PORT1 PORT2 PORT3 PORT4 PORT1 PORT2 PORT3 PORT4 Equipment B
24-8
Issue 05 (2010-10-30)
Procedure of LAG Switching

In the case of a load non-sharing LAG, when the NE detects that a certain port in the LAG is in the link down state or that the other conditions for triggering LAG switching are met, the following operations are performed: 1. 2. 3. 4. The faulty port at the local end is shut down. The link with the highest priority among the standby links is selected to replace the faulty link. The LACP packet is sent to the NE at the opposite end. According to the LACP packet, the NE at the opposite end shuts down the corresponding port and implements switching between the ports.
NOTE
If the LAG is in load sharing mode, the faulty link is shut down and then the traffic is re-allocated to each link according to the load sharing algorithm.

Follow certain principles when you plan LAGs.
Planning Guidelines of LAGs Connected to the Customer Equipment

l The type of the LAG configured on the local equipment must be the same as that configured on the opposite equipment. It is recommended that the equipment at both ends adopt static aggregation. The load sharing type of the LAG configured on the local equipment must be the same as that configured on the opposite equipment. It is recommended that the LAG used for protection adopt load non-sharing on the equipment at both ends. In addition, it is recommended that the LAG for increasing bandwidths adopt load sharing on the equipment at both ends. You can set a specific type only for a LAG in load sharing mode. It is recommended that you use the default load sharing type. It is recommended that the main and slave ports on the equipment at both ends adopt the same settings. It is recommended that the system priority of a LAG take the default value. The system priority can be set only in manual aggregation.
l l l
Planning Guidelines of LAGs in the Case of 1+1 Protection

l l l l l Set the aggregation type to manual aggregation. Set the load sharing mode to load non-sharing. Set the LAG to non-revertive. The port that is connected to the main IFH2 board functions as the main port, and the port that is connected to the standby IFH2 board functions as the slave port. If the IFH2 board provides more than 100 Mbit/s Ethernet services, it must be connected to the GE port.
Issue 05 (2010-10-30)

To use the LAG protocol, you need to configure a LAG. In addition, you can configure the priorities of the ports in the LAG as required. Table 24-4 Procedure for configuring a LAG connected to the customer equipment St ep 1 Operation A.12.1 Creating a LAG Description Required, Set the parameters as follows: l Set LAG Type to the same value as the opposite equipment. Generally, set LAG Type to Static for the equipment at both ends. l Set Load Sharing to the same value as the opposite equipment. If the LAG is configured to provide protection, it is recommended that you set Load Sharing to NonSharing for the equipment at both ends. If the LAG is configured to increase bandwidths, it is recommended that you set Load Sharing to Sharing for the equipment at both ends. l Set Revertive Mode to the same value as the opposite equipment. Generally, set Revertive Mode to Revertive for the equipment at both ends. l Set Main Port, Selected Slave Ports, and Available Slave Ports according to the planing information. It is recommended that the main and slave ports on the equipment at both ends adopt the same settings. 2 A.12.2 Setting the Port Priority Optional.
24-10
Issue 05 (2010-10-30)
Table 24-5 Procedure for configuring a LAG connected to the IF board in 1+1 protection configuration St ep 1 Operation A.12.1 Creating a LAG Description Required . Set the parameters as follows: l Set LAG Type to Manual. l Set Load Sharing to Non-Sharing. l Set Revertive Mode to Non-Revertive. l Set Main Port to the working board in the 1+1 protection configuration, and set Selected Slave Ports to the protection board in the 1+1 protection configuration. 2 A.12.2 Setting the Port Priority Optional.

This section uses an example to describe how to plan and configure a LAG according to network conditions. 24.9.1 Networking Diagram The section describes the networking information about the NEs. 24.9.2 Service Planning The service planning information contains all the parameters required for configuring the NE data. 24.9.3 Configuration Process This section describes the procedure of data configuration.

The section describes the networking information about the NEs. As shown in Figure 24-3, the networking information is as follows: l Port 5-EMS6-5 of NE1 is connected to the main IF board of the 1+1 protection group and functions as the main port; port 5-EMS6-6 of NE1 is connected to the standby IF board of the 1+1 protection group and functions as the slave port. NE1 is configured with 1+1 HSB protection.
Issue 05 (2010-10-30)
24-11
Figure 24-3 LAG networking diagram
NE 1 Main port: 5-EMS6-5 Slave port: 5-EMS6-6
NE 2 Main port: 5-EMS6-5 Slave port: 5-EMS6-6

The service planning information contains all the parameters required for configuring the NE data. Table 24-6 provides the information about the LAG configuration on the NE. Table 24-6 LAG information Parameter LAG Type Load Sharing Revertive mode Main Port Slave Port NE1 Manual Non-Sharing Non-Revertive 5-EMS6-5 5-EMS6-6

Procedure
Step 1 See A.12.1 Creating a LAG and configure a LAG. The values for the required parameters that are set in the main interface are as follows. Parameter LAG Name LAG Type Load Sharing Revertive Mode Value Range LAG_1 Manual Non-Sharing Non-Revertive
24-12
Issue 05 (2010-10-30)
The values for the required parameters on the Port Setting tab are as follows. Parameter Main Port Selected Slave Ports Value Range PORT5 PORT6
----End

This section provides the hyperlinks of the operation tasks associated with LAGs.
Related Tasks
A.12.1 Creating a LAG A.12.2 Setting the Port Priority A.12.3 Querying the Protocol Information of the LAG

When the LAG is unavailable or a certain member in the LAG is unavailable, the system control board reports the relevant alarms.
Relevant Alarms
l LAG_PORT_FAIL The LAG_PORT_FAIL alarm indicates that a port in an Ethernet LAG fails. When a PORT in the LAG becomes unavailable, the system reports this alarm. l LAG_VC_PORT_FAIL The LAG_VC_PORT_FAIL alarm indicates that a VCG port in a LAG fails. When a VCTRUNK port in a LAG becomes unavailable, the system reports this alarm.

None.
24.12 FAQs
This section describes the answers to the frequently asked questions that are raised when the LAG feature is used. Q: Does the OptiX RTN 620 support dynamic aggregation? A: The OptiX RTN 620 does not support dynamic aggregation.
Issue 05 (2010-10-30)
24-13
Q: Can the LAG load sharing function be enabled on the EMS6 board that is interconnected with the equipment that is enabled with MPLS? A: No. The MAC address and IP address of the equipment enabled with MPLS are fixed, the LAG load sharing algorithm is based on the MAC address or IP address. Therefore, the LAG load sharing function cannot be enabled.
24-14
Issue 05 (2010-10-30)
25 Link State Pass Through
25
About This Chapter
Link State Pass Through
This chapter describes the link state pass through (LPT) feature. 25.1 Introduction This section provides the definition of LPT and describes its purpose. 25.2 Basic Concepts This section describes the basic concepts associated with LPT. 25.3 Specifications This section provides the specifications of LPT. 25.4 Reference Standards and Protocols This section describes the standards and protocols associated with LPT. 25.5 Availability This section describes the support required by the application of the LPT feature and its dependency. 25.6 Principles LPT is implemented by transmitting specific packets, but the approaches of implementation in the case of various faults are different. 25.7 Planning Guidelines Follow certain guidelines when you plan LPT. 25.8 Configuration Procedure The configuration procedure for LPT contains only one configuration task. 25.9 Configuration Example This section uses an example to describe how to plan and configure LPT according to network conditions. 25.10 Task Collection This section provides the hyperlinks of the operation tasks associated with LPT. 25.11 Relevant Alarms and Events When a service network fault is detected through LPT or a notification of the fault detected by LPT is received, the NE reports the corresponding alarm.
25.12 FAQs This section provides answers to the questions that are frequently asked when the LPT feature is used.
25-2
Issue 05 (2010-10-30)
25.1 Introduction
This section provides the definition of LPT and describes its purpose.
Definition
LPT can detect the faults that occur at the service access node or on the intermediate transmission network, and then can instruct the equipment at both ends of the transmission network to start the backup network immediately for communication. In this manner, LPT ensures normal transmission of the important data. As a protection scheme based on links, LPT is available in point-to-point and point-to-multipoint modes so as to provide network level protection for the transmission of point-to-point private line services and point-to-multipoint convergence services. l Figure 25-1 shows the LPT application in point-to-point private line services.
Figure 25-1 Networking diagram of point-to-point LPT
Backup network
Service network Router A Access link 1 Working link Protection link

NE1 NE2
Access link 2
Router B
In general cases, router A and router B communicate data through the network service devices, which are NE1 and NE2 (two sets of the Figure 25-1) as shown in OptiX RTN 620. When the link between router A and router B is faulty, the communication between router A and router B is interrupted. For important users, however, even when such a fault occurs, the important data must be transmitted normally. Therefore, the system must be able to detect and report faults in a timely manner and then can start the backup network to ensure the communication. l Figure 25-2 shows the LPT application in point-to-multipoint convergence services.
Issue 05 (2010-10-30)
25-3
Figure 25-2 Networking diagram of point-to-multipoint LPT
Backup network
Port 2 Port 1 Port 3 Service network Port 1 Router A NE1 Port 2 Port 1 NE3 Backup network Router D Port 3 Router C Port 2 NE2 Router B
Protection link Working link
In normal cases, router A, router B, router C, and router D communicate data through the service network. When the link between router A and NE1 is faulty, router A fails to communicate with router B, router C, and router D. For important users, however, even when such a fault occurs, the important data must be transmitted normally. Therefore, the system must be able to detect and report faults in a timely manner and then can start the backup network to ensure the communication.
Purpose
LPT helps to detect and report the faults that occur at the service access node or on the intermediate transmission network so that the data communications equipment (such as routers) can start the backup network immediately for communication. In this manner, LPT ensures the normal transmission of important data.
25.2 Basic Concepts

This section describes the basic concepts associated with LPT. 25.2.1 LPT Bearer Mode To enable LPT frames to pass through different Layer 2 networks, LPT is defined at Layer 2.5. In this case, LPT packets can be carried in various bearer modes. 25.2.2 Hold-Off Time When the link on which Ethernet services are transmitted is configured with other protection schemes, set the hold-off time of LPT. In this manner, the NE notifies the equipment at both
ends of a transmission network the fault on the transmission link only when the other protection schemes fail.
25.2.1 LPT Bearer Mode

To enable LPT frames to pass through different Layer 2 networks, LPT is defined at Layer 2.5. In this case, LPT packets can be carried in various bearer modes. LPT packets can be carried by Ethernet MAC frames, generic framing procedure (GFP) frames, and client signal fail (CSF) frames. The LPT bearer mode varies according to the type of LPT packet. When the bearer mode of a received LPT packet is different from that of the equipment at the receive end, the LPT packet is discarded.
25.2.2 Hold-Off Time

When the link on which Ethernet services are transmitted is configured with other protection schemes, set the hold-off time of LPT. In this manner, the NE notifies the equipment at both ends of a transmission network the fault on the transmission link only when the other protection schemes fail. The following part uses an application scenario wherein 1+1 HSB and LPT work together to describe the functions of the hold-off time.
Example of Coexisting LPT and 1+1 HSB

As shown in Figure 25-3, the radio link between NE1 and NE2 is configured with 1+1 HSB and the LPT is enabled for the Ethernet private line service. In general cases, router A and router B communicate data through the network service devices, which are NE1 and NE2 (two sets of the OptiX RTN 620) as shown in Figure 25-3. Figure 25-3 Coexisting LPT and 1+1 HSB
Backup network
VCTRUNK 1 Router A
NE1
Traffic flow
NE2
Router B
Switching When the Hold-Off Time Is Not Set

If the hold-off time of LPT is not set (that is, the hold-off time is set to 0), the fading on the main radio link between NE1 and NE2 causes a service fault, which triggers LPT switching and 1+1
HSB switching at the same time. The 1+1 HSB switching enables the service between NE1 and NE2 to be transmitted on the standby radio link. The LPT switching enables the service between router A and router B to be transmitted in the backup path. Figure 25-4 shows the traffic flow. Figure 25-4 Traffic flow after LPT switching and 1+1 HSB switching
Backup network
Router A
VCTRUNK 1
NE1
Traffic Flow
NE2
Router B
After the fault on the link is rectified, the revertive LPT switching occurs. Figure 25-5 shows the traffic flow after the switching. Figure 25-5 Traffic flow after the revertive LPT switching
Backup network
VCTRUNK 1 Router A
NE1
Traffic flow
NE2
Router B
Switching When the Hold-Off Time Is Set

If the hold-off time is set, LPT switching does not occur immediately after the switching condition is detected. Instead, the system checks whether the switching condition persists after a certain period. If the switching condition persists, the LPT switching occurs. If the switching condition disappears, the LPT switching is not triggered. In this example, the fault on the main radio link between NE1 and NE2 first triggers the 1+1 HSB switching if the hold-off time is set. If the 1+1 HSB switching is complete within the hold25-6 Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 05 (2010-10-30)
off time, the LPT switching condition no longer exists when the hold-off time expires. Therefore, the LPT switching does not occur. Figure 25-6 shows the final traffic flow after the 1+1 HSB switching. Compared with the switching condition when the hold-off time is not set, occurrence of two LPT switching events is prevented. Figure 25-6 Traffic flow after the 1+1 HSB switching when the hold-off time is set
Backup network
VCTRUNK 1 Router A
NE1
Traffic flow
NE2
Router B
25.3 Specifications
This section provides the specifications of LPT. Table 25-1 lists the specifications of LPT. Table 25-1 Specifications of LPT Item Service transmission modes supported by LPT Service types supported by LPT Specification Ethernet over SDH Ethernet over PDH Point-to-point Ethernet private line service Point-to-multipoint Ethernet private line service Bearer modes of LPT packets Ethernet MAC frame GFP management frame (defined by Huawei) GFP CSF frame Hold-off time 0-10000 ms, in steps of 100 ms

This section describes the standards and protocols associated with LPT.
LPT complies with Huawei proprietary protocols.
25.5 Availability
This section describes the support required by the application of the LPT feature and its dependency.

Table 25-2 Hardware and version support Feature Point-to-point LPT Applicable Board EFT4 EMS6 EFP6 Point-to-multipoint LPT EMS6 EFP6 Applicable Hardware Version SL61EFT4 VER.B SL61EMS6 VER.B All the versions SL61EMS6 VER.B All the versions Applicable Product Version V100R003 and later V100R003 and later V100R005C00 and later V100R003 and later V100R005C00 and later
Feature Dependency
l l l l LPT is applicable only to point-to-point and point-to-multipoint Ethernet private line services. An Ethernet port on which LPT is enabled must be in auto-negotiation mode. Only Ethernet services that are transmitted over SDH or over PDH links can adopt LPT. LPT can work together with other protection schemes.
25.6 Principles
LPT is implemented by transmitting specific packets, but the approaches of implementation in the case of various faults are different. 25.6.1 Point-to-Point Service LPT protects a point-to-point service against a fault that occurs at a service access node or on an intermediate transmission network, but the approaches of implementing the LPT function in the two scenarios are different. 25.6.2 Point-to-Multipoint Service In the case of point-to-multipoint services, Ethernet port-shared Ethernet services and VCTRUNK-shared Ethernet services have different approaches to LPT implementation.
25-8
Issue 05 (2010-10-30)
25.6.1 Point-to-Point Service

LPT protects a point-to-point service against a fault that occurs at a service access node or on an intermediate transmission network, but the approaches of implementing the LPT function in the two scenarios are different.
Fault on a Service Network in Point-to-Point LPT

l Fault detection
Access node 1
Service Broken equipment A
Service network
Broken
Service equipment B
Access node 2
A fault occurs on a link on the service network (from A to B). In this case, service equipment A cuts off its connection to access node 2. In addition, service equipment B sends Broken packets to service equipment A. After receiving the Broken packets, service equipment A cuts off its connection to access node 1. The process of network fault detection is complete.
NOTE
If a fault occurs on the service network bidirectionally, the detection mechanism is the same as that when a unidirectional fault occurs.
Fault recovery
Non_Broken Non_Broken Service network Service equipment B Access node 2
Access node 1
Service equipment A
After service equipment A and service equipment B detect that the service network is restored, they send Non_Broken packets to each other to notify the opposite end that the link is restored. In addition, they restore their local connections to access nodes.
Access node 1
Service equipment A
Service network
Service equipment B
Access node 2
When service equipment A and service equipment B receive the Non_Broken packets from the opposite end, or if the waiting time for receipt of the Broken packets times out, service equipment A and service equipment B determine that the entire link is normal and then restore the local link.
Fault on the Access Node Link in Point-to-Point LPT

l Fault detection
Issue 05 (2010-10-30)
25-9

Shut down the Ethernet port and report the LPT_RFI alarm Service equipment B Access node 2
Report an alarm indicating a link fault Access node 1 Service equipment A
Service network Broken
1. 2. l
After service equipment A detects a fault on the access node link, it reports the alarm indicating the fault and sends Broken control frames to service equipment B. On the receipt of Broken control frames, service equipment B shuts down the Ethernet port and reports the LPT_RFI alarm. Fault recovery
Clear the alarm indicating the link fault Service network Non_Broke n Recover the local connection Service equipment B Access node 2
Access node 1
Service equipment A
1. 2.
After service equipment A detects that the fault on the access node link disappears, it sends Non_Broken control frames to service equipment B. On the receipt of Non-Broken control frames, service equipment B starts up the Ethernet port at the local end.
25.6.2 Point-to-Multipoint Service

In the case of point-to-multipoint services, Ethernet port-shared Ethernet services and VCTRUNK-shared Ethernet services have different approaches to LPT implementation.
LPT for Ethernet Port-Shared Ethernet Services

l Fault detection
Shut down the port and report the LPT_RFI alarm Shut down the port and report the link fault Convergen ce node Service equipment A Broken Broken Service equipment B Access node 1
Shut down the port and report the LPT_RFI alarm Service equipment C Access node 2
Service equipment A that is connected to the convergence node detects its access point is faulty, and reports the alarm indicating the fault. In addition, service equipment A transmits Broken packets to service equipment B and service equipment C. On the receipt of the Broken packets, service equipment B and service equipment C cut off the connections at the local end and report the LPT_RFI alarm.
Fault recovery
Start up the port Clear the alarm indicating the link fault Non_Broken Service equipment B Access node 1
Convergen ce node
Service equipment A Service equipment C Start up the port Access node 2
Non_Broken
Service equipment A that is connected to the convergence node detects that the preceding fault is rectified, and clears the alarm indicating the fault. In addition, service equipment A transmits Non-Broken packets to service equipment B and service equipment C. On the receipt of the NonBroken packets, service equipment B and service equipment C recover the connections at the local end and clear the LPT_RFI alarm.
LPT for VCTRUNK-Shared Ethernet Services

l Fault detection
Access node A Cut off the local connection and report the LPT_RFI alarm Service equipment A Access node B Service equipment B Broken Access node B' Access node A'
Service equipment A detects that a VCTRUNK in the direction from B to A becomes faulty and cuts off its connection to the access node. In addition, service equipment A sends Broken packets to service equipment B. On the receipt of the Broken packets, service equipment B cuts off its connections to the access nodes. The process of VCTRUNK fault detection is complete.
NOTE
If a fault occurs on the service network bidirectionally, the detection mechanism is the same as that when a unidirectional fault occurs.
Fault recovery
Access node A Service equipment A Access node B Start up the VCTRUNK and clear the LPT_RFI alarm Access node A' Service equipment B Access node B'
Non_Broken
After service equipment A and service equipment B detect that the VCTRUNK is restored, they send Non_Broken packets to each other to notify the opposite end and restore their local connections to the access nodes.
Issue 05 (2010-10-30)
25-11

Start up the port and clear the alarm Service equipment A Access node B Start up the port and clear the alarm

Start up the port and clear the alarm Service equipment B Start up the port and clear the alarm Access node B'
Access node A
Start up the VCTRUNK and clear the LPT_RFI alarm
Access node A'
Non_Broken
On the receipt of the Non_Broken packets from their opposite end, service equipment A and service equipment B recover the connections to the access nodes and clear the LPT_RFI alarm.

Follow certain guidelines when you plan LPT.
NOTE
Point-to-point LPT and point-to-multipoint LPT are mutually exclusive. Therefore, you can select only one configuration mode to implement LPT.
Planning Guidelines of the Private Line Service Type

l l l The configured data service must be pure transparent transmission service. In the case of the point-to-point service, use the Ethernet transparent transmission service. In the case of the point-to-multipoint service, the data service must adopt the tree topology, which is consistent with the LPT topology.
Planning Guidelines of the Service Direction

l l The direction needs to be set only when you configure point-to-point LPT, and it indicates the direction of the EPL service that is transparently transmitted on a port. In the case of a pair of PORT and VCTRUNK, you can set the direction to positive or reverse. When the source port is a PORT and the sink port is a VCTRUNK, the direction is set to positive. When the source port is a VCTRUNK and the sink port is a PORT, the direction is set to reverse.
Planning Guidelines of the Hold-Off Time

l l You can set Port-Type Port Hold-Off Time(ms) and VCTRUNK Port Hold-Off Time (ms) only when LPT pass-through is enabled. When LPT switching is enabled, a port informs the opposite end after the hold-off time.
Planning Guidelines of the Port at a Convergence Point

l l l l The port at a convergence point needs to be set in the case of point-to-multipoint LPT. The port at a convergence point can be set to a PORT or a VCTRUNK port. The port at an access point is set to a VCTRUNK port if the port at a convergence point is set to a PORT. The port at an access point is set to a PORT if the port at a convergence point is set to a VCTRUNK port.
25-12
Planning Guidelines of the Bearer Mode

l l l The bearer mode can be set to GFP, GFP CSF, or MAC. You can select an appropriate one as required. When the port at the convergence point is set to a PORT, Bearer Mode need not be set. When the port at the convergence point is set to a VCTRUNK port, Bearer Mode needs to be set.
Planning Guidelines of the Port at an Access Point

l l l l The port at an access point needs to be set in the case of point-to-multipoint LPT. The port at an access point can be set to a PORT or a VCTRUNK port. The port at an access point is set to a VCTRUNK port if the port at a convergence point is set to a PORT. The port at an access point is set to a PORT if the port at a convergence point is set to a VCTRUNK port.

The configuration procedure for LPT contains only one configuration task. Table 25-3 Procedure for configuring LPT for Point-to-Point Services Step 1 Operation Configur ing LPT for Point-toPoint Services A.17.1 Configuring LPT for Point-to-Point Services Description Required when the service is a point-to-point service. The parameters need to be set according to the service planning.
Table 25-4 Procedure for configuring LPT for Point-to-Multipoint Services Step 1 Operation Configur ing LPT for Point-toMultipoi nt Services A.17.2 Configuring LPT for Point-to-Multipoint Services Description Required when the service is a point-to-multipoint service. The parameters need to be set according to the service planning.

This section uses an example to describe how to plan and configure LPT according to network conditions.
25.9.1 Networking Diagram This section describes the networking information about the NEs. 25.9.2 Service Planning The service planning information contains all the parameters required for configuring the NE data. 25.9.3 Configuration Process This section describes the procedure of data configuration.

This section describes the networking information about the NEs. As shown in Figure 25-7, NE1 is configured with point-to-multipoint LPT, NE2 and NE3 are configured with point-to-point LPT. When the link between router A and NE1 is faulty, the Ethernet port associated with the IF port on NE1 is shut down; the access routers (router B and router C) start the backup network. In this manner, the normal communication of important data is ensured. Figure 25-7 Networking diagram of LPT
4-EMS6-PORT1 (to NE1)
NE2 NE1 4-EMS6-PORT1 (to Router A) 4-EMS6-VCTRUNK1 (to NE2) 4-EMS6-VCTRUNK2 (to NE3) NE3
Router B
Router A
Router C
4-EMS6-PORT1 (to NE1)
NOTE
Point-to-multipoint LPT needs to be configured only on the convergence node. Point-to-multipoint LPT adopts unidirectional communication. Therefore, if the link from NE1 to NE2 or from NE1 to NE3 becomes faulty, services are not switched to the backup network.

LPT Configuration Information

Table 25-5 provides the LPT configuration information.
Table 25-5 LPT configuration information of NE1 Parameter Convergence Point Access Point NE1 PORT1 VCTRUNK1 VCTRUNK2 Bearer Mode Hold-Off Time(ms) GFP (HUAWEI) 0
Table 25-6 LPT configuration information of NE2 Parameter LPT Bearer Mode PORT-Type Port Hold-off Time(ms) VCTRUNK Port Hold-off Time NE2 Yes GFP (HUAWEI) 0 0
Table 25-7 LPT configuration information of NE3 Parameter LPT Bearer Mode PORT-Type Port Hold-off Time(ms) VCTRUNK Port Hold-off Time NE3 Yes GFP (HUAWEI) 0 0

Procedure
Step 1 See A.17.2 Configuring LPT for Point-to-Multipoint Services and configure point-tomultipoint LPT. The values for the relevant parameters of NE1 are provided as follows. The values for the parameters of the convergence point are as follows. Parameter Value Range NE1 Port Hold-Off Time(ms)
Issue 05 (2010-10-30)
Port 0
25-15
The values for the parameters of the access point are as follows. Parameter Value Range NE1 Port VCTRUNK1 VCTRUNK2 Bearer Mode GFP(HUAWEI)
Step 2 See A.17.1 Configuring LPT for Point-to-Point Services and configuring for point-to-point LPT. l The values for the relevant parameters of NE2 are provided as follows. Parameter Value Range NE2 LPT Bearer Mode PORT-Type Port Hold-off Time (ms) VCTRUNK Port Hold-off Time(ms) Yes GFP (HUAWEI) 0 0
l The values for the relevant parameters of NE3 are provided as follows. Parameter Value Range NE3 LPT Bearer Mode PORT-Type Port Hold-off Time (ms) VCTRUNK Port Hold-off Time(ms) Yes GFP (HUAWEI) 0 0
----End

This section provides the hyperlinks of the operation tasks associated with LPT.
Related Tasks
A.17.1 Configuring LPT for Point-to-Point Services
A.17.2 Configuring LPT for Point-to-Multipoint Services

When a service network fault is detected through LPT or a notification of the fault detected by LPT is received, the NE reports the corresponding alarm.
Relevant Alarms
l LPT_INEFFECT The LPT_INEFFECT alarm indicates that the LPT function fails. When LPT is configured on an inapplicable board, the system reports this alarm. l LPT_RFI The LPT_RFI alarm indicates a remote LPT failure. When LPT detects that the remote port fails or the LPT service network where the remote port resides fails, the system reports this alarm.

None.
25.12 FAQs
This section provides answers to the questions that are frequently asked when the LPT feature is used. Q: Does Hybrid radio support LPT? A: In Ethernet over SDH and Ethernet over SDH scenarios, LPT is supported. In the Native Ethernet scenario, LPT is not supported. Hybrid radio involves combined transmission of Native E1 services and Native Ethernet services. Therefore, Hybrid radio does not support LPT.
Issue 05 (2010-10-30)
25-17
26 QoS
26
About This Chapter
This chapter describes the quality of service (QoS) feature. 26.1 Introduction This section provides the definition of QoS and describes its purpose. 26.2 Basic Concepts This section describes the basic concepts that are associated with QoS. 26.3 Specifications This section describes the specifications of QoS. 26.4 Reference Standards and Protocols This section describes the standards and protocols associated with QoS. 26.5 Availability QoS requires support of the applicable equipment and boards.
QoS
26.6 Principles The CAR and traffic shaping functions are implemented based on the token bucket algorithm. 26.7 Planning Guidelines Follow certain guidelines when you plan QoS. 26.8 Configuration Procedure When you plan QoS, define a flow and set required QoS parameters. 26.9 Configuration Example This section uses an example to describe how to plan and configure QoS according to network conditions. 26.10 Task Collection This section provides the hyperlinks of the operation tasks associated with the QoS feature. 26.11 Relevant Alarms and Events There is no alarm or abnormal event relevant to the QoS feature. 26.12 FAQs
26 QoS
This section provides answers to the questions that are frequently raised when the QoS feature is used.
26-2
Issue 05 (2010-10-30)
26 QoS
26.1 Introduction
This section provides the definition of QoS and describes its purpose.
Definition
QoS refers to the ability of a communication network to ensure the expected service quality under any conditions, in the aspects of bandwidth, delay, delay jitter, and packet loss ratio. QoS helps to ensure that the request and response from the user or the request and response from the application meet the requirements of an expected service class. On legacy IP networks, all packets are processed in first in first out (FIFO) queues by adopting the best effort strategy. This method cannot meet the stringent requirements of emerging services for the bandwidth, delay, and delay jitter. Therefore, the QoS technology is developed. Figure 26-1 shows how packets are transmitted through an interface that does not support QoS when the network is congested. Figure 26-1 FIFO queue
Packets to be transmitted through the interface Queue FIFO Out-of-queue grooming Packets transmitted out of the interface
The urgency of packets decreases from left to right.
All packets to be transmitted through this interface enter the tail of the FIFO queue according to the sequence of their arrival at the interface. The interface transmits these packets from the head of the queue. The packets are not differentiated during the transmission, and the quality of packet transmission is not ensured. Figure 26-1 shows how packets of different QoS levels are transmitted through queues with different priorities. Figure 26-2 Queues with different priorities
Packets to be transmitted through the interface Queue Classification Queue 8 Queue 7 Queue 6 Priority Highest High Low Out-of-queue grooming Packets transmitted out of the interface
Queue 1 Lowest
...
Issue 05 (2010-10-30)
26-3
26 QoS
After packets arrive at the interface, the packets are classified first. Then, these packets enter the tail of their corresponding queues according to their types. The interface transmits the higherpriority packets in the queue first and then transmits the lower-priority packets in the queue. In this manner, the higher-priority packets are always transmitted first and these packets have low delay jitter. In addition, the performance indexes of these packets, including the packet loss ratio and delay jitter, can be ensured even in the case of network congestion.
Purpose
The QoS technology helps a transmission network to provide service policies with different priorities, to meet various requirements of voice, video, and data services. Therefore, a transmission network is able to ensure the expected service quality any conditions, in the aspects of bandwidth, delay, delay jitter, and packet loss ratio. QoS helps to ensure that the request and response from the user or the request and response from the application meet the requirements of an expected service class.
26.2 Basic Concepts

This section describes the basic concepts that are associated with QoS. 26.2.1 Traffic Classification A flow refers to a collection of packets with the same characteristics. In the case of the Ethernet switching unit, a flow refers to a collection of packets that requires the same QoS operations. Traffic classification means, according to certain rules, classifying packets into several types of flows, on which different QoS operations are performed. Traffic classification is a prerequisite and basis for QoS operations. 26.2.2 CoS A class of service (CoS) helps to schedule packets into egress queues with different priorities, so that these packets can be processed according to the priority of each queue. In this manner, packets with different priorities can be processed according to different QoS requirements. 26.2.3 CAR The committed access rate (CAR) is a type of traffic policing technology. When the CAR is used, the rate of the traffic after 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. In this manner, the CAR restricts the traffic into the transmission network. 26.2.4 Traffic Shaping Traffic shaping can restrict the traffic and burst of a connection on a network, and thus enables the packet to be transmitted at an even rate. The Ethernet switching unit shapes the irregular traffic or the traffic that does not conform to the specified traffic characteristics based on the generic traffic shaping (GTS) technology. 26.2.5 Queue Scheduling The commonly used queue scheduling methods in QoS include strict-priority (SP), weighted round robin (WRR), and SP+WRR. 26.2.6 QoS Model The Ethernet switching unit performs traffic classification, CAR, and CoS operations in the ingress direction, and performs traffic shaping and egress queue scheduling in the egress direction.
26 QoS
26.2.1 Traffic Classification

A flow refers to a collection of packets with the same characteristics. In the case of the Ethernet switching unit, a flow refers to a collection of packets that requires the same QoS operations. Traffic classification means, according to certain rules, classifying packets into several types of flows, on which different QoS operations are performed. Traffic classification is a prerequisite and basis for QoS operations. The flow type is based on the associated Ethernet service type of the flow. This section describes various flow types. For details on the support of the board for the flow types, see 26.3 Specifications. l Port flow The packets from a certain port are classified as a type of flow. The associated Ethernet service of this flow type is the line service that uses this port as the service source. The Layer 2 switching service can also be classified as a port flow. l Port+VLAN flow The packets that are from a certain port with a specified VLAN ID are classified as a type of flow. The associated Ethernet service of this flow type is the EVPL service (based on VLAN) or EVPLAN service (based on the 802.1q bridge) that uses this port+VLAN as the service source. l Port+S-VLAN flow The packets that are from a certain port and have a specified S-VLAN are classified as a type of flow. The associated Ethernet service of this flow type is the EVPL service (based on QinQ) or EVPLAN service (based on the 802.1ad bridge) that uses this port+S-VLAN as the service source. l Port+C-VLAN+S-VLAN flow The packets that are from a certain port and have a specified C-VLAN+S-VLAN are classified as a type of flow. The associated Ethernet service of this flow type is the EVPL service (based on QinQ) or EVPLAN service (based on the 802.1ad bridge) that uses this port+C-VLAN+S-VLAN as the service source. l Port+VLAN+Pri flow The packets that are from a certain port and have the specified VLAN and VLAN priority are classified as a type of flow. The associated Ethernet service of this flow type is the private line service that uses this port+VLAN+Pri as the service source.
26.2.2 CoS
A class of service (CoS) helps to schedule packets into egress queues with different priorities, so that these packets can be processed according to the priority of each queue. In this manner, packets with different priorities can be processed according to different QoS requirements. This section describes various priority classification methods. For details on the support of the board for priority classification methods, see 26.3 Specifications. l Simple If the CoS type of a flow is set to simple, all the packets in this flow are directly scheduled to a specified egress queue. l
Issue 05 (2010-10-30)
VLAN priority
26 QoS
If the CoS type of a flow is set to VLAN priority, the packets in this flow are scheduled to specified egress queues according to the user priorities specified in the VLAN tags of these packets. l DSCP If the CoS type of a flow is set to differentiated services code point (DSCP), the packets in this flow are scheduled to specified egress queues according to the DSCPs carried in the IPv6 packets. This CoS type is applicable to IPv6 packets. l IP TOS If the CoS type of a flow is set to IP TOS, the packets in this flow are scheduled to specified egress queues according to the TOS values carried in the IPv4 packets. This CoS type is applicable to IPv4 packets.
26.2.3 CAR
The committed access rate (CAR) is a type of traffic policing technology. When the CAR is used, the rate of the traffic after 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. In this manner, the CAR restricts the traffic into the transmission network. The OptiX RTN 620 supports the CAR processing for traffic in the ingress direction after it is classified. The CAR processing operations 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 policing of the CAR. These packets are always forwarded first in the case of 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 are directly discarded. When the rate of packets is higher than the CIR but is equal to or lower than the PIR, these packets whose rate exceeds the CIR can pass the restriction of the CAR and is marked yellow, and these packets are discarded first in the case of network congestion. When the rate of packets is equal to or lower than the CIR in a certain period, certain packets can burst and these packets are always forwarded first in the case of network congestion. The maximum traffic of burst packets is determined by the committed burst size (CBS). When the rate of packets 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 traffic of burst packets is determined by the maximum burst size (MBS).
l l
Figure 26-3 shows the traffic change after the CAR processing. The packets that are marked red are directly discarded, and the packets that are marked yellow and green pass the policing of the CAR. In addition, the packets that are marked yellow are processed according to the preset value.
26-6
Issue 05 (2010-10-30)
26 QoS
Figure 26-3 CAR processing
MBS PIR CBS CIR PIR CIR PIR MBS CBS CIR
CAR
26.2.4 Traffic Shaping

Traffic shaping can restrict the traffic and burst of a connection on a network, and thus enables the packet to be transmitted at an even rate. The Ethernet switching unit shapes the irregular traffic or the traffic that does not conform to the specified traffic characteristics based on the generic traffic shaping (GTS) technology. In the case of the port queue whose traffic shaping feature is enabled, the Ethernet switching unit processes the packets as follows before they enter the queue: l l l When the rate of the packets is equal to or lower than the set CIR, these packets directly enter the egress queue. When the rate of the packets is higher than the set PIR, these packets enter the buffer. When the buffer overflows, the packets are discarded. When the rate of the packets is higher than the CIR but is equal to or lower than the PIR, the packets whose rate is higher than the CIR enter the buffer of the CIR. When the buffer overflows, these packets are marked yellow and enter the egress queue. In this case, these packets are discarded in the case of queue congestion. When the rate of the packets that pass the restriction of the traffic shaping in a certain period is equal to or lower than the CIR, certain burst packets enter the egress queue. The maximum traffic of the burst packets is determined by the CBS. When the rate of the packets that pass the restriction of the traffic shaping in a certain period is higher than the CIR but is equal to or lower than the PIR, certain burst packets enter the buffer of the CIR. The maximum traffic of the burst packets is determined by the MBS.
As is evident from the preceding processing mechanism, the difference of the traffic shaping from the CAR is as follows: l l In the processing of the CAR, the packet that does not conform to the traffic characteristics is downgraded in priority or directly discarded. In the processing of the traffic shaping, the packet that does not conform to the traffic characteristics is stored in the buffer. The packet is downgraded in priority or directly discarded only when the buffer overflows. Traffic shaping increases the delay of services, but CAR does not.
Figure 26-4 shows the traffic change after traffic shaping. During the traffic shaping process, the yellow part indicates the traffic that is directly transmitted without traveling through the
26 QoS
buffer queue, the yellow part indicates the traffic that is transmitted after traveling through the buffer queue, and the red part indicates the traffic that is discarded. Figure 26-4 Traffic shaping
MBS PIR CBS CIR
PIR CIR
PIR
Shaping
CIR
26.2.5 Queue Scheduling

The commonly used queue scheduling methods in QoS include strict-priority (SP), weighted round robin (WRR), and SP+WRR. This section describes various queue scheduling algorithms. For details on the support of the board for queue scheduling algorithms, see 26.3 Specifications.
Basic Concepts
Available bandwidth at a port: refers to the bandwidth that the system allocates to a port. l In the case of an external Ethernet port, the available bandwidth at a port is determined by the working mode of this port. For example, if the working mode of a port is 1000M fullduplex, the available bandwidth of the port is 1000 Mbit/s. In the case of a VCTRUNK port, the available bandwidth is determined by the total bandwidth of the virtual concatenation (VC) paths that are bound to the port virtual concatenation group (VCG).
SP Scheduling Algorithm
Figure 26-5 illustrates the SP scheduling algorithm. Figure 26-5 Queues with different priorities
Packets to be transmitted through the interface Queue Classification Queue 8 Queue 7 Queue 6 Priority Highest High Low Out-of-queue grooming Packets transmitted out of the interface
Queue 1 Lowest
...
26-8
Issue 05 (2010-10-30)
26 QoS
The SP scheduling algorithm is designed for key service applications. A key service must be processed with the highest priority when congestion occurs so that the response delay can be shortened. For example, a port provides eight egress queues, which are allocated with priorities from 7 to 0 in a descending order. During the SP queue scheduling, packets are transmitted in a descending order of priorities. When a queue with a higher priority is empty, the packets in the queue with a lower priority can be transmitted. In this manner, packets of key services are placed into the queues with higher priorities and packets of non-key services (such as email services) are placed into queues with lower priorities. Therefore, 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. The disadvantage of the SP scheduling algorithm is as follows: If there are packets in the queues with higher priorities when congestion occurs, the packets in the queues with lower priorities cannot be transmitted all the time.
WRR Scheduling Algorithm

Figure 26-6 illustrates the WRR scheduling algorithm. Figure 26-6 WRR scheduling algorithm
Packets to be transmitted through the interface Queue Classification Queue 4 Queue 3 Queue 2 Queue 1 Weight 50 30 10 10 Out-of-queue grooming Packets transmitted out of the interface
The WRR scheduling algorithm divides each port into several egress queues and schedules the packets in these queues in turn. This ensures that each queue obtains a certain service period. For example, a port provides four queues. In a descending order of priorities, the WRR configures the w4, w3, w2, and w1 weights for the four queues. Each weight stands for the proportion of resources that the relevant queue can obtain from the total resources. If this port is a 100 Mbit/ s port and the weights of its four queues are set to 50, 30, 10, and 10 (corresponding to w4, w3, w2, and w1) by the WRR scheduling algorithm, a minimum of 10 Mbit/s bandwidth is guaranteed for the queue with the lowest priority. This prevents the disadvantage that packets in the queues with lower priorities may fail to obtain services for a long time in the case of the SP queue scheduling. Another advantage of the WRR scheduling is as follows: Although scheduling of multiple queues is performed in the polling manner, time segment allocated to each queue is not fixed. That is, when a queue is empty, the packets in the next queue are scheduled immediately. In this manner, the bandwidth resources can be fully utilized.
26 QoS
SP+WRR Scheduling Algorithm

As shown in Figure 26-7, the SP+WRR scheduling algorithm combines the advantages of the SP and WRR scheduling algorithms. That is, when the SP+WRR scheduling algorithm is used, one of the egress queues is configured as an SP queue so that these packets can be always scheduled first and therefore the key services can be processed first; the other egress queues adopt the WRR scheduling algorithm so that each queue can obtain a certain service time segment. Figure 26-7 SP+WRR scheduling algorithm
SP queues Priority Packets to be transmitted through the port Queue 8 Weights WRR queues 64 Classification 32 16 Queue 7 Queue 6 Queue 5 WRR queue Egress queue scheduling Low High Packets transmitted out of the port
...
Queue 1 Queues whose priorities are in a descending order from left to right
The scheduling rules are as follows: l l l The packets in an SP queue are always transmitted first. The packets in the WRR queues can be transmitted only when the SP queue is empty. When several SP queues exist, the priorities of these SP queues are compared according to the priority arrangement in a descending order from 8 to 0. Each WRR queue is allocated with a certain service time segment based on the weight. During the specified service time segment, the packets in the corresponding WRR queue are transmitted. If a WRR queue that corresponds to a service time segment does not have packets, this service time segment is removed and the packets in the queue that corresponds to the following service time segment are transmitted.
The following part considers the port that has eight egress queues (one SP queue and seven WRR queues) as an example. l Queue 8 (whose CoS priority is 7) uses the SP algorithm. If this queue has packets, these packets are transmitted first. When this queue does not have packets, packets in the other queues are allowed transmitting. Service time segments are allocated to queues 1-7 (whose CoS priorities are 0-6) according to the weights 1:2:4:8:16:32:64, and at each time segment the packets in the corresponding queue are transmitted. If the queue that corresponds to a time segment does not have packets, this time segment is removed and the packets in the queue that corresponds to the following time segment are transmitted. For example, if four queues (queue A, queue B, queue C, and queue D) are weighted as follows: 1:2:4:8, the WRR allocates the service time segments in the form of cyclic sequence with a period of DCDBDCDADCDBDCD.
26-10
Issue 05 (2010-10-30)

NOTE
26 QoS
If the traffic shaping function of some queues is enabled, the bandwidth is first allocated to these queues according to the preset CIR. The remaining bandwidth is allocated to the queues by using the SP+WRR algorithm. For example, if the total bandwidth at a port is 100 Mbit/s, the traffic shaping function is enabled for queues 5 and 7, and the preset CIR is 10 Mbit/s, the remaining bandwidth is 80 Mbit/s. The 80 Mbit/s bandwidth is allocated to the eight queues by using the SP+WRR algorithm.
26.2.6 QoS Model

The Ethernet switching unit performs traffic classification, CAR, and CoS operations in the ingress direction, and performs traffic shaping and egress queue scheduling in the egress direction. Figure 26-8 shows the entire QoS process on the Ethernet switching unit. For details on the support of the board for various QoS functions, see 26.5 Availability. The Ethernet switching unit performs QoS operations as follows: 1. 2. Classifies the traffic according to the associated service type. Performs CAR operations for the flow that requires traffic policing: Packets whose rate is lower than the CIR are marked green, and packets whose rate is lower than the PIR are marked yellow. Performs CoS operations for the flows that require differentiated service classes: The traffic of different CoSs is labeled and then can be scheduled to egress queues with different CoS priorities. Forwards packets to the egress port by using a certain algorithm. Schedules packets to corresponding egress queues according to the CoS priorities labeled at the ingress, and schedules packets whose CoS priorities are not labeled to default egress queues. In the case of egress queues that require traffic shaping, performs traffic shaping for the packets and schedules these queues by using a certain scheduling algorithm; in the case of egress queues that do not require traffic shaping, schedules them by using a certain scheduling algorithm. Transmits packets in the egress queues by using a certain queue scheduling algorithm. If congestion occurs in the egress queues, the packets that are marked yellow are always discarded first based on the congestion avoidance algorithm.
3.
4. 5.
6.
7.
Figure 26-8 QoS processing
Flow classification
CAR
CoS Forwarding
Queue scheduling without shaping Queue scheduling with shaping
Packet scheduling
Issue 05 (2010-10-30)
26-11
26 QoS
26.3 Specifications
This section describes the specifications of QoS. Table 26-1 lists the specifications of QoS. Table 26-1 Specifications of QoS Item Specification EMS6 Traffic classification Maximum number of flows Flow Type 1024 Port flowa Port+VLAN flow Port+S-VLAN flow Port+C-VLAN +S-VLAN flow EFP6 512 Port flow Port+VLAN flow Port+S-VLAN flow Port+C-VLAN +S-VLAN flow Port+VLAN +Pri flow CAR Maximum number of CAR strategies CIR step PIR step CoS Priority classification method 1024 512 IFH2 -
64 kbit/s 64 kbit/s Simple VLAN priorityb DSCPb IP ToS
64 kbit/s 64 kbit/s Simple VLAN priority DSCP IP ToS Simple: 8 VLAN priority: 22 DSCP: 22 IP ToS: 22 -
VLAN priority
Number of mapping relationship table
Simple: 8 VLAN priority: 6 DSCP: 6 IP ToS: 8
VLAN priority: 1
Traffic shaping (port)
CIR PIR step
Fixed value 64 kbit/sc
26-12
Issue 05 (2010-10-30)
26 QoS
Item
Specification EMS6 EFP6 64 kbit/s 64 kbit/s 8-level queue scheduling IFH2 4-level queue scheduling
Traffic shaping (queues at a port) Scheduling of queues at a port
CIR step PIR step Number of queue scheduling levelsd Queue scheduling methode
64 kbit/s 64 kbit/s 8-level queue scheduling
SP WRR SP+WRR (default, and can be modified) l Queue 8: SP l Queues 1 to 7: WRR
SP+WRR, whose allocation is fixed and cannot be modified l Queue 8: SP l Queues 1 to 7: WRR Fixed weight allocation (which cannot be modified)
SP
Weight allocation of WRR
Default weight allocation (which can be modified)
NOTE
a:
In the case of the EMS6 board, the 802.1q and 802.1d bridges support only traffic classification based on the port.
b:
In the case of the EMS6 board, comply with the following requirements for a CoS application:
l If a flow at a certain port is bound with a CoS with a certain VLAN priority, the other flows at the port cannot be bound with a CoS with another VLAN priority or any DSCP CoS. l If a flow at a certain port is bound with a DSCP CoS, the other flows at the port cannot be bound with any other DSCP CoS or a CoS with any VLAN priority.
c:
In the case of the EMS6 board, the PIR of a port meets the following constraints:
l The PIR is equal to or higher than the PIR of any queue at this port. l The PIR is equal to or higher than the sum of the CIRs of all the queues at this port.
d:
l Eight queues are available at the egress port of the EMS6 and EFP6 boards. The mapping relationships between CoS priorities and egress queues are as follows. Under the same condition, if the CoS priority is higher, the priority of the corresponding queue is higher. CoS Priority 0 1 2 Egress Queue Queue 1 Queue 2 Queue 3
Issue 05 (2010-10-30)
26-13
26 QoS
CoS Priority 3 4 5 6 7

Egress Queue Queue 4 Queue 5 Queue 6 Queue 7 Queue 8
l Four queues are available at the egress port of the IFH2 board. The mapping relationships between CoS priorities and egress queues are as follows. Under the same condition, if the CoS priority is higher, the priority of the corresponding queue is higher. The IFH2 board supports only the CoS based on the VLAN priority. By default, the data frames that do not carry VLAN tags are scheduled to queue 1 with the lowest priority. CoS Priority 0 1 2 3 Egress Queue Queue 1 Queue 2 Queue 3 Queue 4
e:
l In the case of the EMS6 and EFP6 boards, the SP+WRR algorithm is relevant to the traffic shaping of queues. If the traffic shaping function of some queues is enabled, the bandwidth is first allocated to these queues according to the preset CIR. The remaining bandwidth is allocated to the queues by using the SP+WRR algorithm. For example, if the total bandwidth at a port is 100 Mbit/s, the traffic shaping function is enabled for queues 5 and 7, and the preset CIR is 10 Mbit/s, the remaining bandwidth is 80 Mbit/s. The 80 Mbit/s bandwidth is allocated to the eight queues by using the SP+WRR algorithm. l In the case of the EMS6 board, the scheduling method of queues at a port can be modified but SP queues must be in front of WRR queues. For example, if three SP queues and five WRR queues are required, queues 6 to 8 need to be set as SP queues and queues 1 to 5 need to be set as WRR queues.

This section describes the standards and protocols associated with QoS. QoS complies with IETF RFC 2697, RFC 2698, RFC 2309, RFC 2597, RFC 2598, and IEEE 802.1p.
26.5 Availability
QoS requires support of the applicable equipment and boards.
26-14
Issue 05 (2010-10-30)
26 QoS

Table 26-2 Hardware and version support (QoS) Feature Traffic classification Applicable Board EMS6 EFP6 CAR EMS6 EFP6 CoS EMS6 IFH2 EFP6 Traffic shaping (port) Traffic shaping (queues at a port) EMS6 EMS6 EFP6 EMS6 IFH2 EFP6 Applicable Hardware Version All the versions All the versions All the versions All the versions All the versions All the versions All the versions All the versions All the versions All the versions All the versions All the versions All the versions Applicable Product Version V100R002 and later V100R005C00 and later V100R002 and later V100R005C00 and later V100R002 and later V100R003 and later V100R005C00 and later V100R005C00 and later V100R002 and later V100R005C00 and later V100R002 and later V100R003 and later V100R005C00 and later
Queue scheduling
Feature Dependency
QoS is independent of other features.
26.6 Principles
The CAR and traffic shaping functions are implemented based on the token bucket algorithm. 26.6.1 CAR The CAR uses the dual token bucket three color marker algorithm. 26.6.2 Traffic Shaping Traffic shaping uses the dual token bucket three color marker algorithm that is similar to the algorithm used by the CAR. The buffer queue, however, is added before the Tc token bucket in the algorithm used by traffic shaping.
26 QoS
26.6.1 CAR
The CAR uses the dual token bucket three color marker algorithm.
Token Bucket Algorithm

Figure 26-9 shows the basic principle of the token bucket algorithm. Figure 26-9 Basic principle of the token bucket algorithm
Tokens are placed into the token bucket at a specified rate
...
Tokens
Packets that need to be sent from this port
Packets that leave this port
Classification
Token bucket
Packets are discarded or processed in another way
In this algorithm, the token bucket is a container that has a certain capacity for storing tokens. The tokens are placed into the bucket at a specified rate. When the number of tokens in the bucket exceeds the capacity of the bucket, the number of tokens no longer increases. A token indicates certain packet traffic. When the packets are transmitted, certain tokens are removed from the buckets according to the length of the packet. When the number of tokens that are stored in the token bucket cannot support the transmitting of the packets, these packets are discarded or processed in another way. When the token bucket is filled with tokens, the packet traffic that is represented by these tokens can be transmitted, which allows the transmission of the burst data. Hence, the traffic of the burst packets is determined by the capacity of the bucket.
Dual Token Bucket Three Color Marker Algorithm

Figure 26-10 shows the basic principle of the dual token bucket three color marker algorithm that is used by the CAR.
26-16
Issue 05 (2010-10-30)
26 QoS
Figure 26-10 Basic principle of the algorithm that is used by the CAR
...
PIR
...
CIR
Classification
Tp
Tc
This algorithm uses two token buckets Tc and Tp, and marks colors for packets according to the situations when these packets pass the token bucket. The parameters of these two token buckets are as follows: l l The packet is placed into the Tc token bucket at the rate of CIR, and the capacity of the Tc token bucket is equal to the CBS. The packet is placed into the Tp token bucket at the rate of PIR, and the capacity of the Tp token bucket is equal to the MBS.
A packet is marked as follows: l If a packet obtains the Tc token, this packet is marked green. This type of packet can pass the restriction of the CAR and is forwarded first even in the case of network congestion. l If a packet obtains the Tp token but does not obtain the Tc token, this packet is marked yellow. This type of packet can pass the restriction of the CAR but is discarded first in the case of network congestion. l If a packet does not obtain the Tp token, this packet is marked red. This type of packet is directly discarded.
26.6.2 Traffic Shaping

Traffic shaping uses the dual token bucket three color marker algorithm that is similar to the algorithm used by the CAR. The buffer queue, however, is added before the Tc token bucket in the algorithm used by traffic shaping. Figure 26-11 shows the basic principle of the dual token bucket three color marker algorithm that is used by traffic shaping.
Issue 05 (2010-10-30)
26-17
26 QoS
Figure 26-11 Basic principle of the algorithm that is used by the traffic shaping
Tp buffer queue
Tp token bucket
This algorithm uses two token buckets Tc and Tp, and places packets into different queues according to the situations when these packets pass the token bucket. The parameters of these two token buckets are as follows: l l The packet is placed into the Tc token bucket at the rate of CIR, and the capacity of the Tc token bucket is equal to the CBS. The packet is placed into the Tp token bucket at the rate of PIR, and the capacity of the Tp token bucket is equal to the MBS.
...
PIR
Tc buffer queue
Tc token bucket
...
CIR
A packet is placed into a queue as follows: l l If a packet obtains the Tc token, this packet is directly placed into the egress queue. If a packet obtains the Tp token but does not obtain the Tc token, this packet is placed into the Tc buffer queue. When the Tc buffer queue overflows, the overflow packet is marked yellow and then enters the egress queue, which indicates that the packet is discarded first in the case of network congestion. l If a packet does not obtain the Tp token, this packet is placed into the Tp buffer queue. When the Tp buffer queue overflows, the overflow packet is directly discarded.

Follow certain guidelines when you plan QoS. Select appropriate QoS functions as required. Adhere to the following principles: l l l Selecting the CAR is a priority, which can control the service traffic on the ingress side. In the case of the key service that needs to improve traffic fluctuation, select the traffic shaping function. If differentiated services are required for differentiated service types or different user classes, select the CoS function.
Adhere to the following principles when planning the CAR: l

26-18
Bind a CAR to a flow. Do not bind a CAR to multiple flows.

26 QoS
The sum of CIRs of all the CARs that are associated with a PORT or a VCTRUNK should not exceed the physical bandwidth of this PORT or this VCTRUNK.
Adhere to the following principles when planning the traffic shaping and CoS: l l l l Allocate the service of low delay or the service of low delay commitment (such as the signaling data, VoIP data, and network management protocol packet) to the SP queue. Allocate the service that does not require low delay or that does not provide low delay commitment (such as the Internet service) to the WRR queue. The sum of CIRs of all the queues that are associated with a PORT or a VCTRUNK should not exceed the physical bandwidth of this PORT or this VCTRUNK. Plan the parameters of the traffic shaping according to the traffic features, thus preventing frequent buffer overflows.

When you plan QoS, define a flow and set required QoS parameters. Table 26-3 provides the procedure for configuring QoS for the EMS6 and EFP6 boards. Table 26-3 Procedure for configuring QoS for the EMS6 and EFP6 boards Step 1 2 3 4 5 Operation Description
A.13.1 Creating Required when the CAR or CoS operations are required for a a Flow certain flow at the port. A.13.2 Creating Required when the ingress bandwidth and burst size in the ingress the CAR direction need to be limited. A.13.3 Creating Required when the packets in a flow need to be scheduled to the CoS egress queues with different priorities. A.13.4 Binding the CAR/CoS Required when the preset CAR or CoS policy needs to be applied to a flow.
A.13.5 Required when the traffic shaping policy needs to be set for egress Configuring the queues. Traffic Shaping for Egress Port Queues A.13.6 Configuring Port Shaping A.13.8 Configuring the Queue Scheduling Mode Required when the traffic shaping policy needs to be set for queues at the port on the EMS6 board. Required when the default egress queue scheduling method of the EMS6 board needs to be adjusted.
Issue 05 (2010-10-30)
26-19
26 QoS
The IFH2 board supports only the CoS based on the board. For details on the configuration procedure, see Table 26-4. Table 26-4 Procedure for configuring QoS for the IFH2 board Step 1 Operation A.13.7 Configuring the CoS of the IFH2 Board Description Required when packets need to be scheduled to egress queues with different priorities based on the VLAN priorities of these packets.

This section uses an example to describe how to plan and configure QoS according to network conditions. 26.9.1 Networking Diagram This section describes the networking information about the NEs. 26.9.2 Service Planning The service planning information contains all the parameters required for configuring the NE data. 26.9.3 Configuration Process This section describes the procedure of data configuration.

This section describes the networking information about the NEs. As shown in Figure 26-12, the service transmitted from each BTS carries a VLAN ID, and the VLAN IDs of the entire network are planned in a uniform manner. Therefore, the EVPL service based on the VLAN can be used to transmit the service. In this case, the radio network needs to perform QoS planning and processing for the services based on their VLAN priorities. Figure 26-12 Networking diagram (EPVL service based on the VLAN)
BTS2 VLAN 110 10Mbit/s FE
FE BTS3 VLAN 120 25Mbit/s
FE NE4 FE NE3 FE NE5 BTS4 VLAN 130 25Mbit/s NE2 BTS1 VLAN 100 45Mbit/s NE1
FE
BSC
FE NE6 BTS5 VLAN 140 15Mbit/s
26-20
Issue 05 (2010-10-30)
26 QoS
Table 26-5 provides the relationship between the type of service transmitted by the BTS, VLAN priority, and expected priority of processing. Table 26-5 QoS requirement Type of Service Transmitted by the BTS Real-time voice service and signaling Real-time OM and HSDPA services Non-real-time R99 service HSDPA data service User Priority Defined in the VLAN Tag 5 3 2 0 Expected Priority of Processing Highest High Common Lowest
Figure 26-12 shows the connections of Ethernet links. Table 26-6 Connections of Ethernet links (NE1) Link Between NE1 and the BSC Port 6-EMS6-PORT1 6-EMS6-PORT2 Between NE1 and NE2 6-EMS6-PORT5 (connecting the main IF board 5-IFH2 in the 1+1 HSB protection group) 6-EMS6-PORT6 (connecting the standby IF board 7-IFH2 in the 1+1 HSB protection group) Description Configure these ports into a load-sharing LAG group, therefore increasing the link bandwidth. Configure these ports into a non-load-sharing LAG, which needs to participate in 1+1 HSB protection.
Table 26-7 Connections of Ethernet links (NE2) Link Between NE2 and NE3 Port 6-EMS6-PORT1 Description Configure this port to transmit backhaul services from a base station. Configure this port to access services from BTS1.
26-21
Between NE2 and BTS1
6-EMS6-PORT2
Issue 05 (2010-10-30)
26 QoS
Link Between NE2 and NE1
Port 6-EMS6-PORT5 (connecting the main IF board 5-IFH2 in the 1+1 HSB protection group) 6-EMS6-PORT6 (connecting the standby IF board 7-IFH2 in the 1+1 HSB protection group)
Description Configure these ports into a non-load-sharing LAG, which needs to participate in 1+1 HSB protection.
Table 26-8 Connections of Ethernet links (NE3) Link Between NE3 and NE4 Port 8-EMS6-PORT1 (connecting the main IF board 5-IFH2 in the 1+1 HSB protection group) 8-EMS6-PORT2 (connecting the standby IF board 7-IFH2 in the 1+1 HSB protection group) Between NE3 and NE5 8-EMS6-PORT3 Configure this port to transmit Ethernet services on Hybrid radio. Configure this port to transmit backhaul services from a base station. Description Configure these ports into a non-load-sharing LAG, which needs to participate in 1+1 HSB protection.
Between NE3 and NE2
8-EMS6-PORT4
Table 26-9 Connections of Ethernet links (NE4) Link Between NE4 and NE3 Port 6-EMS6-PORT1 (connecting the main IF board 5-IFH2 in the 1+1 HSB protection group) 6-EMS6-PORT2 (connecting the standby IF board 7-IFH2 in the 1+1 HSB protection group) Between NE4 and BTS2 6-EMS6-PORT3 Configure this port to access services from BTS2. Description Configure these ports into a non-load-sharing LAG, which needs to participate in 1+1 HSB protection.
26-22
Issue 05 (2010-10-30)
26 QoS
Link Between NE4 and BTS3
Port 6-EMS6-PORT4
Description Configure this port to access services from BTS3.
Table 26-10 Connections of Ethernet links (NE5) Link Between NE5 and NE6 Port 6-EMS6-PORT1 Description Configure this port to transmit Ethernet services on Hybrid radio. Configure this port to transmit Ethernet services on Hybrid radio. Configure this port to access services from BTS4.
Between NE5 and NE3
6-EMS6-PORT2
Between NE5 and BTS4
6-EMS6-PORT3
Table 26-11 Connections of Ethernet links (NE6) Link Between NE6 and NE5 Port 5-IFH2-PORT1 Description Configure this port to directly access services from BTS5.

VLAN-Based EVPL Services

Table 26-12 to Table 26-16 provide the planning information of the VLAN-based EVPL services. Table 26-12 Information about the VLAN-based EVPL service (NE1) Parameter NE1 Between NE2 and BSC Board Service type Service direction
Issue 05 (2010-10-30)
6-EMS6 EPL Bidirectional

26-23
26 QoS
Parameter
NE1 Between NE2 and BSC
Source port Source C-VLAN Sink port Sink C-VLAN
PORT5 100, 110, 120, 130, 140 PORT1 100, 110, 120, 130, 140
Table 26-13 Information about the VLAN-based EVPL service (NE2) Parameter NE2 Between NE3 and NE1 Board Service type Service direction Source port Source C-VLAN Sink port Sink C-VLAN 6-EMS6 EPL Bidirectional PORT1 110, 120, 130, 140 PORT5 110, 120, 130, 140 Between BTS1 and NE1 6-EMS6 EPL Bidirectional PORT2 100 PORT5 100
Table 26-14 Information about the VLAN-based EVPL service (NE3) Parameter NE3 Between NE2 and NE5 Board Service type Service direction Source port Source C-VLAN Sink port Sink C-VLAN 8-EMS6 EPL Bidirectional PORT4 130, 140 PORT3 130, 140 Between NE2 and NE4 8-EMS6 EPL Bidirectional PORT4 110, 120 PORT1 110, 120
26-24
Issue 05 (2010-10-30)
26 QoS
Table 26-15 Information about the VLAN-based EVPL service (NE4) Parameter NE4 Between BTS2 and NE3 Board Service type Service direction Source port Source C-VLAN Sink port Sink C-VLAN 6-EMS6 EPL Bidirectional PORT3 110 PORT1 110 Between BTS3 and NE3 6-EMS6 EPL Bidirectional PORT4 120 PORT1 120
Table 26-16 Information about VLAN-based EVPL service (NE5) Parameter NE5 Between BTS4 and NE3 Board Service type Service direction Source port Source C-VLAN Sink port Sink C-VLAN 6-EMS6 EPL Bidirectional PORT3 130 PORT2 130 Between NE6 and NE3 6-EMS6 EPL Bidirectional PORT1 140 PORT2 140
NOTE
On NE6, EPL services are accessed directly through the IFH2 board. Therefore, you need not configure Ethernet private line services on NE6 manually.
QoS (Flow)
Before configuring QoS, you need to create the corresponding flows.
Issue 05 (2010-10-30)
26-25
26 QoS
Table 26-17 Flow (NE1) Parameter Flow type Value PORT +VLANbased flow 6-EMS6PORT1 100 1 PORT +VLANbased flow 6-EMS6PORT1 110 1 PORT +VLANbased flow 6-EMS6PORT1 120 1 PORT +VLANbased flow 6-EMS6PORT1 130 1 PORT +VLANbased flow 6-EMS6PORT1 140 1
Port VLAN ID Bound CAR Bound CoS
Table 26-18 Flow (NE2) Parameter Flow type Value PORT +VLANbased flow 6-EMS6PORT1 110 1 PORT +VLANbased flow 6-EMS6PORT1 120 1 PORT +VLANbased flow 6-EMS6PORT1 130 1 PORT +VLANbased flow 6-EMS6PORT1 140 1 PORT +VLANbased flow 6-EMS6PORT2 100 1 1
Port VLAN ID Bound CAR Bound CoS
Table 26-19 Flow (NE3) Parameter Flow type Port VLAN ID Bound CAR Bound CoS Value PORT+VLANbased flow 8-EMS6PORT4 110 1 PORT+VLANbased flow 8-EMS6PORT4 120 1 PORT+VLANbased flow 8-EMS6PORT4 130 1 PORT+VLANbased flow 8-EMS6PORT4 140 1
26-26
Issue 05 (2010-10-30)
26 QoS
Table 26-20 Flow (NE4) Parameter Flow type Port VLAN ID Bound CAR Bound CoS Value PORT+VLAN-based flow 6-EMS6-PORT3 110 1 1 PORT+VLAN-based flow 6-EMS6-PORT4 120 2 1
Table 26-21 Flow (NE5) Parameter Flow type Port VLAN ID Bound CAR Bound CoS Value PORT+VLAN-based flow 6-EMS6-PORT3 130 1 1
NOTE
On NE6, the point-to-point EPL service is accessed directly through the IFH2 board. Therefore, you need not configure flows.
QoS (CAR)
Table 26-22 CAR (services accessed from BTS1 to NE2) Parameter CAR ID Enabled/Disabled Committed information rate(kbit/s) Committed burst size (kbyte) PIR (kbit/s) Maximum burst size (kbyte) Value 1 Enabled 46080 0 92160 0
Issue 05 (2010-10-30)
26-27
26 QoS
Table 26-23 CAR (services accessed from BTS2 and BTS3 to NE4) Parameter CAR ID Enabled/Disabled Committed information rate (kbit/s) Committed burst size (kbyte) PIR (kbit/s) Maximum burst size (kbyte) Value 1 Enabled 10240 0 20480 0 2 Enabled 25600 0 51200 0
Table 26-24 CAR (services accessed from BTS4 to NE5) Parameter CAR ID Enabled/Disabled Committed information rate (kbit/s) Committed burst size (kbyte) PIR (kbit/s) Maximum burst size (kbyte) Value 1 Enabled 25600 0 51200 0
NOTE
On NE6, the point-to-point EPL service is accessed directly through the IFH2 board. Therefore, you need not configure the CAR.
QoS (CoS)
During service planning, it is recommended that you allocate corresponding VLAN priorities to the BTS services according to service types. Then, the transmission network performs CoS operations according to the allocated VLAN priorities. In this example, all the base stations are of the same type. Therefore, configure the same CoS operations for Ethernet interfaces on the EMS6 boards on NE1 to NE5 that access or backhaul services from the base stations. Refer to Table 26-25 and Table 26-26. In the case of NE6, configure the CoS operation for the IFH2 board. Table 26-25 CoS attributes of the EMS6 boards Parameter CoS ID
26-28
Value 1
26 QoS
Parameter CoS type
Value VLAN priority
Table 26-26 CoS parameters of the EMS6 boards CoS Parameter User priority 0 in the VLAN tag User priority 1 in the VLAN tag User priority 2 in the VLAN tag User priority 3 in the VLAN tag User priority 4 in the VLAN tag User priority 5 in the VLAN tag CoS Priority 0 Service Type HSDPA data services (HSPA interactive and HSPA background services) R99 non-real-time services (R99 interactive and R99 background services) OM and HSDPA real-time services (OM streaming and HSPA streaming services) Real-time voice service and signaling service (R99 conversational and R99 streaming services) -
0 1
0 3
User priority 6 in the VLAN tag User priority 7 in the VLAN tag
0 0
Table 26-27 CoS operations on the IFH2 board CoS Parameter User priority 0 in the VLAN tag User priority 1 in the VLAN tag User priority 2 in the VLAN tag CoS Priority 0 Service Type HSDPA data services (HSPA interactive and HSPA background services) R99 non-real-time services (R99 interactive and R99 background services)
0 1
Issue 05 (2010-10-30)
26-29
26 QoS
CoS Parameter User priority 3 in the VLAN tag User priority 4 in the VLAN tag User priority 5 in the VLAN tag
CoS Priority 2
Service Type OM and HSDPA real-time services (OM streaming and HSPA streaming services) Real-time voice service and signaling service (R99 conversational and R99 streaming services) -
0 3
User priority 6 in the VLAN tag User priority 7 in the VLAN tag
0 0
QoS (Queue Scheduling)

To schedule queues over an interface so that the Ethernet packets in the queues are forwarded in a specific sequence computed by a scheduling algorithm, you need to configure queue scheduling. In this example, services from base stations are scheduled in descending order of queue priority. That is, services in queues with higher priority are forwarded from the EMS6 board to the Ethernet interface on the IFH2 board first; after all the services in queues with higher priority are transmitted, services in queues of lower priority are transmitted.
NOTE
When LAGs comprised of interfaces on the EMS6 board are configured for 1+1 HSB protection, you need to configure queue scheduling only on the main interfaces in the LAGs involved in 1+1 HSB protection.
Table 26-28 Queue scheduling on the EMS6 board Port Queue 1 Scheduling Scheme SP Service Type HSDPA data services (HSPA interactive and HSPA background services) R99 non-real-time services (R99 interactive and R99 background services) OM and HSDPA real-time services (OM streaming and HSPA streaming services) Issue 05 (2010-10-30)
2 3
SP SP
SP
5
26-30
SP
26 QoS
Port Queue 6
Scheduling Scheme SP
Service Type Real-time voice service and signaling service (R99 conversational and R99 streaming services) -
7 8
SP SP
QoS (Port Shaping)

If the Ethernet bandwidth planned for the aggregation link is lower than the total bandwidth of the aggregation services, perform port shaping at the edge node to limit the Ethernet service traffic that travels to the aggregation node, thus preventing congestion at the aggregation node. In this example, you need not configure port shaping.

Procedure
Step 1 See A.19.1 Creating Ethernet Private Line Services and configure Ethernet private line services. The values for the relevant parameters of NE1 are provided as follows. Parameter Value Between NE2 and BSC Board Service Type Direction Source Port Source C-VLAN(e.g.1,3-6) Sink Port Sink C-VLAN(e.g.1,3-6) 6-EMS EPL Bidirectional PORT5 100,110,120,130,140 PORT1 100,110,120,130,140
The values for the relevant parameters of NE2 are provided as follows.
Issue 05 (2010-10-30)
26-31
26 QoS
Parameter
Value Between NE3 and NE1 Between BTS1 and NE1 6-EMS EPL Bidirectional PORT2 100 PORT5 100
Board Service Type Direction Source Port Source C-VLAN(e.g.1,3-6) Sink Port Sink C-VLAN(e.g.1,3-6)
6-EMS EPL Bidirectional PORT1 110,120,130,140 PORT5 110,120,130,140
The values for the relevant parameters of NE3 are provided as follows. Parameter Value Between NE2 and NE5 Board Service Type Direction Source Port Source C-VLAN(e.g.1,3-6) Sink Port Sink C-VLAN(e.g.1,3-6) 8-EMS EPL Bidirectional PORT4 130,140 PORT3 130,140 Between NE2 and NE4 8-EMS EPL Bidirectional PORT4 110,120 PORT1 110,120
The values for the relevant parameters of NE4 are provided as follows. Parameter Value Between BTS2 and NE3 Board Service Type Direction Source Port Source C-VLAN(e.g.1,3-6) Sink Port
26-32
Between BTS3 and NE3 6-EMS EPL Bidirectional PORT4 120 PORT1
Issue 05 (2010-10-30)
6-EMS EPL Bidirectional PORT3 110 PORT1

26 QoS
Parameter
Value Between BTS2 and NE3 Between BTS3 and NE3 120
Sink C-VLAN(e.g.1,3-6)
110
The values for the relevant parameters of NE5 are provided as follows. Parameter Value Between BTS4 and NE3 Board Service Type Direction Source Port Source C-VLAN(e.g.1,3-6) Sink Port Sink C-VLAN(e.g.1,3-6) 6-EMS EPL Bidirectional PORT3 130 PORT2 130 Between NE6 and NE3 6-EMS EPL Bidirectional PORT1 140 PORT2 140
Step 2 See A.13.1 Creating a Flow and create flows. The values for the relevant parameters of NE1 are provided as follows. Parameter Value 6-EMS6 Flow Type Port VLAN ID Port+VLAN Flow PORT1 100 Port+VLAN Flow PORT1 110 Port+VLAN Flow PORT1 120 Port+VLAN Flow PORT1 130 Port+VLAN Flow PORT1 140
The values for the relevant parameters of NE2 are provided as follows. Parameter Value 6-EMS6 Flow Type Port Port+VLAN Flow PORT2 Port+VLAN Flow PORT1 Port+VLAN Flow PORT1 Port+VLAN Flow PORT1 Port+VLAN Flow PORT1
Issue 05 (2010-10-30)
26-33
26 QoS
Parameter
Value 6-EMS6
VLAN ID
100
110
120
130
140
The values for the relevant parameters of NE3 are provided as follows. Parameter Value 8-EMS6 Flow Type Port VLAN ID Port+VLAN Flow PORT4 110 Port+VLAN Flow PORT4 120 Port+VLAN Flow PORT4 130 Port+VLAN Flow PORT4 140
The values for the relevant parameters of NE4 are provided as follows. Parameter Value 6-EMS6 Flow Type Port VLAN ID Port+VLAN Flow PORT3 110 Port+VLAN Flow PORT4 120
The values for the relevant parameters of NE5 are provided as follows. Parameter Value 6-EMS6 Flow Type Port VLAN ID Port+VLAN Flow PORT3 130
Step 3 See A.13.2 Creating the CAR and configure the CAR. The values for the relevant parameters of NE2 are provided as follows.
26-34
Issue 05 (2010-10-30)
26 QoS
Parameter
Value 6-EMS6
CAR ID Enabled/Disabled Committed Information Rate (kbit/s) Committed Burst Size (kbyte) Peak Information Rate (kbit/s) Maximum Burst Size (kbyte)
1 Enabled 46080 0 92160 0
The values for the relevant parameters of NE4 are provided as follows. Parameter Value 6-EMS6 CAR ID Enabled/Disabled Committed Information Rate (kbit/s) Committed Burst Size (kbyte) Peak Information Rate (kbit/s) Maximum Burst Size (kbyte) 1 Enabled 10240 0 20480 0 2 Enabled 25600 0 51200 0
The values for the relevant parameters of NE5 are provided as follows. Parameter Value 6-EMS6 CAR ID Enabled/Disabled Committed Information Rate (kbit/s) Committed Burst Size (kbyte) Peak Information Rate (kbit/s) 1 Enabled 25600 0 51200
Issue 05 (2010-10-30)
26-35
26 QoS
Parameter
Value 6-EMS6
Maximum Burst Size (kbyte)
Step 4 See A.13.3 Creating the CoS and configure the CoS. The values for the relevant parameters of NE1 to NE5 are provided as follows. Parameter Value 6-EMS6a CoS ID CoS Type 1 VLAN Priority
CoS Parameter User Priority 0 in the VLAN Tag User Priority 1 in the VLAN Tag User Priority 2 in the VLAN Tag User Priority 3 in the VLAN Tag User Priority 4 in the VLAN Tag User Priority 5 in the VLAN Tag User Priority 6 in the VLAN Tag User Priority 7 in the VLAN Tag
CoS Priority 0 0 1 2 0 3 0 0
NOTE
a: On NE3, the EMS6 in slot 8 is used.
Step 5 See A.13.7 Configuring the CoS of the IFH2 Board and configure the CoS on the IFH2 board. The values for the relevant parameters of NE6 are provided as follows. Parameter Value 5-IFH2-1 CoS Parameter User Priority 0 in the VLAN Tag User Priority 1 in the VLAN Tag
26-36
CoS Priority 0 0
Issue 05 (2010-10-30)
26 QoS
Parameter
Value 5-IFH2-1
CoS Parameter User Priority 2 in the VLAN Tag User Priority 3 in the VLAN Tag User Priority 4 in the VLAN Tag User Priority 5 in the VLAN Tag User Priority 6 in the VLAN Tag User Priority 7 in the VLAN Tag
CoS Priority 1 2 0 3 0 0
Step 6 See A.13.8 Configuring the Queue Scheduling Mode and configure the queue scheduling mode. The values for the relevant parameters of NE1 to NE5 are provided as follows. Paramete r Value NE1 6-EMS6 Port PORT1 NE2 6-EMS6 PORT5 NE3 8-EMS6 PORT1 NE4 6-EMS6 PORT1 NE5 6-EMS6 PORT1 6-EMS6 PORT2
Port Queue 1 2 3 4 5 6 7 8
Scheduling Mode SP SP SP SP SP SP SP SP
----End
Issue 05 (2010-10-30)
26-37
26 QoS

This section provides the hyperlinks of the operation tasks associated with the QoS feature.
Related Tasks
A.13.1 Creating a Flow A.13.2 Creating the CAR A.13.3 Creating the CoS A.13.4 Binding the CAR/CoS A.13.5 Configuring the Traffic Shaping for Egress Port Queues A.13.6 Configuring Port Shaping A.13.7 Configuring the CoS of the IFH2 Board

There is no alarm or abnormal event relevant to the QoS feature.
Relevant Alarms
None.

None.
26.12 FAQs
This section provides answers to the questions that are frequently raised when the QoS feature is used. Q: Why is the Ethernet service interrupted after traffic shaping is enabled? A: Generally, this problem occurs because the CIR and PIR are not configured. The default values of the CIR and PIR are 0. Q: Why is the rate limitation result calculated according to the preset CIR different from the rate limitation result that is actually measured by the meter? A: It is normal that a slight difference exists between the rate limitation result calculated according to the preset CIR and the rate limitation result actually measured by the meter. The difference is caused by the leaky bucket algorithm and chip processing precision.
26-38
Issue 05 (2010-10-30)
27 ETH-OAM
27
About This Chapter
This chapter describes the ETH-OAM feature.
ETH-OAM
27.1 Introduction This section provides the definition of ETH-OAM and describes its purpose. 27.2 Basic Concepts This section describes the basic concepts that you should be familiar with before using ETHOAM. 27.3 Specifications This section describes the specifications of ETH-OAM. 27.4 Reference Standards and Protocols This section describes the standards and protocols associated with ETH-OAM. 27.5 Availability This section describes the support required by the application of the ETH-OAM feature and its dependency. 27.6 Principles Various OAM operations in ETH-OAM are performed through specific OAM packets. 27.7 Planning Guidelines Follow certain guidelines when you plan ETH-OAM. 27.8 Configuration Procedure The configuration procedure of IEEE 802.1ag OAM is irrelevant to the configuration procedure of IEEE 802.3ah OAM 27.9 Configuration Example (IEEE 802.1ag OAM) This section uses an example to describe how to plan and configure IEEE 802.1ag OAM according to network conditions. 27.10 Configuration Example (IEEE 802.3ah OAM) This section uses an example to describe how to plan and configure IEEE 802.3ah OAM according to the network conditions. 27.11 Task Collection
27 ETH-OAM
The operation tasks associated with 802.1ag OAM are irrelevant to the operation tasks associated with 802.3ah OAM. 27.12 Relevant Alarms and Events When detecting an exception by performing ETH-OAM operations, an NE reports the corresponding alarm. 27.13 FAQs This section provides the answers to the questions that are frequently raised when ETH-OAM is used.
27-2
Issue 05 (2010-10-30)
27 ETH-OAM
27.1 Introduction
This section provides the definition of ETH-OAM and describes its purpose.
Definition
Based on the MAC layer, the ETH-OAM protocol performs OAM operations for the Ethernet by transmitting OAM packets. This protocol is irrelevant to the transmission medium. The OAM packets are processed only at the MAC layer, having no impact on the other layers of the Ethernet. In addition, as a low-rate protocol, the ETH-OAM protocol occupies low bandwidths. Thus, this protocol does not affect services carried on links. The OptiX RTN equipment provides a complete Ethernet OAM solution according to the ETHOAM standard specified in IEEE 802.1ag and IEEE 802.3ah. See Figure 27-1. Figure 27-1 ETH-OAM solution
IEEE 802.3ah IEEE 802.1ag IEEE 802.3ah
Transmission network
Customer Ethernet equipment Microwave equipment
IEEE 802.1ag OAM focuses on the maintenance of end-to-end Ethernet links. Based on services, IEEE 802.1ag OAM implements end-to-end detection in the unit of "maintenance domain" and performs segmental management on each network segment that is involved in the same service on a network. IEEE 802.3ah OAM focuses on the maintenance of point-to-point Ethernet links between two directly-connected devices in the first mile. IEEE 802.3ah OAM does not focus on a specific service. It maintains the point-to-point Ethernet link by performing the OAM autodiscovery, link performance monitoring, fault detection, remote loopback, and self-loop check.
Purpose
ETH-OAM enhances Ethernet Layer 2 maintenance functions and it strongly supports service continuity verification, service deployment commissioning, and network fault locating.
27 ETH-OAM
27.2 Basic Concepts

This section describes the basic concepts that you should be familiar with before using ETHOAM. 27.2.1 IEEE 802.1ag OAM Management IEEE 802.1ag OAM focuses on the maintenance of end-to-end Ethernet links. It provides segmental and layered management over the service flow by specifying the maintenance domain (MD), maintenance association (MA), and maintenance point (MP). 27.2.2 IEEE 802.1ag OAM Operation The Ethernet unit supports IEEE 802.1ag ETH-OAM operations, including the continuity check (CC), loopback (LB), link trace (LT) test, ping, alarm indication signal (AIS) activation, and performance check. 27.2.3 IEEE 802.3ah OAM Operation The Ethernet unit supports IEEE 802.3ah ETH-OAM operations, including the OAM autodiscovery, link performance monitoring, remote loopback, and self-loop test.
27.2.1 IEEE 802.1ag OAM Management

IEEE 802.1ag OAM focuses on the maintenance of end-to-end Ethernet links. It provides segmental and layered management over the service flow by specifying the maintenance domain (MD), maintenance association (MA), and maintenance point (MP).
MP
An MP is the functional entity of IEEE 802.1ag OAM. Each MP has a maintenance point identification (MPID). This ID is unique in the entire MA. The information about the MP is recorded in the MAC address table, MP table, and routing table. The service type, service ID, and VLAN tag are key contents in the MP configuration information. Once the MP is created successfully, the protocol packet carrying the information about this MP is broadcast to other MPs that are associated with services. Then, these MPs receive the protocol packet and record the information for future use. MPs are classified into MEPs and MIPs. l MEP A maintenance association end point (MEP) specifies the starting position of an MA. It initiates and terminates an OAM packet, and is associated with services. l MIP A maintenance association intermediate point (MIP) cannot initiate OAM packets. An MIP can respond to and forward an LB or LT packet, and cannot respond to but can forward a CC packet.
27-4
Issue 05 (2010-10-30)

NOTE
27 ETH-OAM
l All OAM operations must be initiated by an MEP. An MIP cannot initiate any OAM operation or send any OAM packet, but can respond to or forward an OAM packet. l An MP is available in two types: standard MP and common MP. A standard MP complies with IEEE 802.1ag Draft 8.0, and a common MP complies with IEEE 802.1ag Draft 3.0. An MP can respond to the OAM operation initiated by another MP of the same type. l A common MP does not involve the concepts of MD and MA.
MD
An MD refers to a network that requires OAM. On a network, users, service providers, and carriers focus on different network segments. Thus, management over different network segments that a service travels through is required. In addition, different service flows need to be managed separately. l IEEE 802.1ag OAM maintains the Ethernet by performing end-to-end check based on the MD. With regard to OAM, an MD is a collection of all the MPs in a service application. These MPs consist of MEPs and MIPs. For the management segment to be maintained, MEPs can be established at both ends so that the range of the MD is specified. In addition, MIPs at other positions in this management segment can be established as required. When operations are performed on these MPs, based on the relationships and responses between the MPs, the state of the whole management segment is under control. In this manner, fault detection and locating is achieved.
MA
An MA is a domain associated with services, and an MA consists of several MEPs and MIPs. On the network of a carrier, a VLAN corresponds to a service instance. On the equipment, a VLAN corresponds to an MA or multiple MAs. By classifying MAs, you can detect the connectivity faults of a network that transmits a certain service instance. l l An MA is a part of an MD. An MD can be divided into one MA or multiple MAs. The level of an MA is the same as the level of the MD to which it belongs.
Layered Management
IEEE 802.1ag OAM adds the management level fields to OAM protocol packets to provide layered management. The higher level management domain can cross the lower level management domain, but the lower level management domain cannot cross the higher level management domain. Based on such layered management, a service can be maintained segmentally and different service flows can be managed. Figure 27-2 shows the logical diagram of MD layers.
Issue 05 (2010-10-30)
27-5
27 ETH-OAM
Figure 27-2 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 Ports Maintenance Intermediate Points AIS Convergence Function Logical path of CFM Messages Maintenance Entities
Currently, IEEE 802.1ag Draft 8.0 supports the eight-level layer division, from level 0 to level 7. "0" indicates the lowest level and "7" indicates the highest level. Eight maintenance entity (ME) levels correspond to the user, supplier, and carrier accordingly. l l l ME levels for the user: 7, 6, 5 ME levels for the supplier: 4, 3 ME levels for the carrier: 2, 1, 0
Layer levels from the highest to the lowest are as follows: user ME level > supplier ME level > carrier ME level.
NOTE
IEEE 802.1ag Draft 3.0 supports the eight-level layer division, from level 0 to level 7. "0" indicates the highest level and "7" indicates the lowest level. l ME levels for the user: 0, 1, 2 l ME levels for the supplier: 3, 4 l ME levels for the carrier: 5, 6, 7 Layer levels from the highest to the lowest are as follows: user ME level > supplier ME level > carrier ME level.
The dashed lines in the diagram show the logical channels that IEEE 802.1ag OAM packets travel through. Methods for MPs at different layers to process OAM protocol packets are as follows: l l In the case of the OAM protocol packets whose layer level is higher, the MPs transparently transmit them. In the case of the OAM protocol packets whose layer level is lower, the MPs discard them directly.
27-6
27 ETH-OAM
In the case of the OAM protocol packets whose layer level is the same, the MPs respond to or terminate the packets according to the messages types of these OAM protocol packets.
27.2.2 IEEE 802.1ag OAM Operation

The Ethernet unit supports IEEE 802.1ag ETH-OAM operations, including the continuity check (CC), loopback (LB), link trace (LT) test, ping, alarm indication signal (AIS) activation, and performance check. Table 27-1 details IEEE 802.1ag ETH-OAM operations and application scenarios. Table 27-1 IEEE 802.1ag ETH-OAM operations and application scenarios Operation Name CC Description The connectivity between MEPs is detected through periodical exchange of continuity check messages (CCMs). This detection method is called CC.
NOTE Only an MEP can initiate and respond to a CC test.
Application Scenario l The CC method is used to test unidirectional connectivity of links in real time. l The CC method fails to locate the specific fault on the link. To achieve this purpose, use the CC method and LT method. l The LB method is used to test bidirectional connectivity of links.
LB
The LB method can be used to test the status of any link from the source MEP to any MEP in the MD.
NOTE l Only an MEP can initiate an LB test.
l Unlike a CC, the LB method provides one-time detection. You need to issue a command to l In the case of a standard MP, if an initiate an LB test. MIP functions as the sink end of an LB test, the LB test must be l The LB method fails to locate the performed based on the MAC specific faulty link on a network address. in one attempt.
l In the case of a standard MP, an LB test can be performed only after the CC function is enabled.
LT
Compared with the LB method, the LT method is more powerful on fault locating. That is, the LT method can locate the faulty network segment in one attempt.
NOTE l Only an MEP can initiate an LT test and functions as the termination point of an LT test. l In the case of a standard MP, an LT test can be performed only after the CC function is enabled.
l The LT method is used to locate a problem on site. l The LT method is also used to locate a fault. l Compared with an LB test, all the MPs on the link under an LT test respond to LTM frames. According to their responses, all the MIPs from the source MEP to the destination MEP can be determined.
Issue 05 (2010-10-30)
27-7
27 ETH-OAM
Operation Name Ping
Description The OAM_ping method is a type of in-service test. The OAM_ping method helps to simulate the packet loss ratio and delay of services that result from bit errors. In addition to the continuity test, the OAM_ping method provides refined management over the performance of Ethernet links at the MAC layer.
Application Scenario The OAM_ping method is used to check the performance of services between the local equipment and the data communications equipment that supports the ICMP protocol. The OAM_ping method provides an in-service test of the packet loss ratio and delay that result from bit errors. Compared with the CC method, the OAM_ping method provides more detailed and accurate OAM information. The AIS activation method is used when the fault information needs to be reported to a higher level MP. To locate a fault accurately if several MDs exist on links, activate the AIS and set the level of the customer layer that functions to suppress the AIS information.
AIS activation
The AIS is used to report errors to a higher level node in the case of ETHOAM. After a fault is detected by an MP, if this MP activates the AIS, it sends the AIS packet to a higher level MP so that the higher level MP is informed of the fault information; if this MP does not activate the AIS, it does not report the fault.
NOTE In normal cases, if an MP is set to level n, the level of the customer layer that functions to suppress the AIS information is set to n+1.
Performance check
The performance check method provides an in-service test of packet loss ratio and delay based on the check of the connectivity between the MPs on the Ethernet service processing unit.
The performance check method is used to check the performance of services between the local equipment and the OptiX equipment that supports a performance check.
27.2.3 IEEE 802.3ah OAM Operation

The Ethernet unit supports IEEE 802.3ah ETH-OAM operations, including the OAM autodiscovery, link performance monitoring, remote loopback, and self-loop test. Table 27-2 details IEEE 802.3ah ETH-OAM operations and application scenarios.
27-8
Issue 05 (2010-10-30)
27 ETH-OAM
Table 27-2 IEEE 802.3ah ETH-OAM operations and application scenarios Operation Name Autodiscovery Description By exchanging the information OAM protocol data unit (OAMPDU) periodically, the local equipment is informed whether the opposite end supports the IEEE 802.3ah OAM protocol. Application Scenario l The auto-discovery method is used to find the equipment on a network and identify the OAM capability. l If an auto-discovery fails, the corresponding alarm is reported. l A successful OAM autodiscovery is a prerequisite for implementing link performance monitoring and remote loopbacks. That is, the link performance monitoring and loopback functions are available at the port only when an OAM auto-discovery is successful. Link performance monitoring The link performance monitoring method monitors the bit error performance (error frames or error signals) of a link. On detecting that bit errors exceed the threshold, the local end sends the specific bit error event to the opposite end through the event notification OAMPDU. In this case, the opposite end reports the alarm accordingly. The OAM entity at the local end transmits the loopback control OAMPDU to the remote OAM entity to request a loopback. Based on the analysis of the loopback data, the fault locating and link performance test are performed.
NOTE The OptiX RTN 620 does not support response to a remote loopback.
l The link performance monitoring method is used to monitor the performance of services on a link in real time. l The link performance monitoring method can precisely analyze and monitor the link performance within a specific range. l The remote loopback method is used to locate a problem on site. l By comparing the number of transmitted packets with the number of received packets in the loopback, the remote loopback method helps to detect bidirectional performance and faults of the link from the loopback initiation end to the loopback response end. l The self-loop test method is used to check the port loopback status and intra-board loopback status, so as to prevent broadcast storm resulting from loopbacks. l This method also helps to detect a loop during networking and report the specific alarm to a user.
27-9
Remote loopback
Self-loop test
After the self-loop test method is enabled on an Ethernet service processing unit, the self-loop that occurs when the fiber in the transmit direction of a port is connected to the same port in the receive direction, and the loopback between two connected ports on the same board can be checked.
Issue 05 (2010-10-30)
27 ETH-OAM
27.3 Specifications
This section describes the specifications of ETH-OAM. Table 27-3 and Table 27-4 list the specifications of ETH-OAM. Table 27-3 Specifications of ETH-OAM (IEEE 802.1ag) Item Specification EMS6 OAM operation CC LB LT Ping AIS activation Performance monitoring Number of supported MDs Number of supported MAs Number of supported MPs Supported MP type 32 32 32 Standard MP (in compliance with IEEE 802.1ag Draft 8.0) Common MP (in compliance with IEEE 802.1ag Draft 3.0) CCM transmission interval (in the case of a common MP) CCM transmission interval (in the case of a standard MP) 1000 ms to 60000 ms, in steps of 100 ms 1000 ms 10000 ms 60000 ms 600000 ms EFP6
Table 27-4 Specifications of ETH-OAM (IEEE 802.3ah) Item Specification EMS6 OAM operation Auto-discovery Link performance monitoring Fault locating Remote loopback Self-loop test
EFP6
27 ETH-OAM
Item
Specification EMS6 EFP6
Monitoring on error frame events Monitoring on error frame second events Monitoring on error frame period events OAM mode
Supported Supported Supported Active Passive

This section describes the standards and protocols associated with ETH-OAM. The following protocols are associated with ETH-OAM: l l IEEE 802.1ag: Virtual Bridged Local Area Networks Amendment 5: Connectivity Fault Management IEEE 802.3ah: Media Access Control Parameters, Physical Layers, and Management Parameters for Subscriber Access Networks
27.5 Availability
This section describes the support required by the application of the ETH-OAM feature and its dependency.

Table 27-5 Hardware and version support Feature IEEE 802.1ag ETHOAM Applicable Board EMS6 EFP6 EMS6 EFP6 Applicable Hardware Version All the versions All the versions All the versions All the versions Applicable Product Version V100R003 and later V100R005C00 and later V100R003 and later V100R005C00 and later
IEEE 802.3ah ETHOAM
Issue 05 (2010-10-30)
27-11
27 ETH-OAM
Feature Dependency
The ETH-OAM feature does not affect other feature.
27.6 Principles
Various OAM operations in ETH-OAM are performed through specific OAM packets. 27.6.1 IEEE 802.1ag OAM In the case of IEEE 802.1ag OAM, OAM operations are performed by communicating OAMPDUs between MPs. 27.6.2 IEEE 802.3ah OAM In the case of IEEE 802.3ah OAM, OAM operations are performed by communicating OAMPDUs.
27.6.1 IEEE 802.1ag OAM

In the case of IEEE 802.1ag OAM, OAM operations are performed by communicating OAMPDUs between MPs.
IEEE 802.1ag OAMPDU

The maintenance functions of IEEE 802.1ag OAM are implemented by communicating OAMPDUs between MPs. Being familiar with the IEEE 802.1ag OAM protocol packets helps you understand how the maintenance functions of the IEEE 802.1ag OAM are implemented. Figure 27-3 shows the IEEE 802.1ag OAMPDU. Figure 27-3 IEEE 802.1ag OAMPDU
OAM Mac Destination Address
OAM Mac Source Address Ether Type(VLAN) Ether Type(OAM) Type Length Service-ID VLAN Tag VER OAM Type
OAM Date
Frame Check Sequence
OAM Mac Destination Address: indicates the broadcast address (in the case of a CC) or MAC address of the sink MP (in the case of an LB or LT test).
27-12
27 ETH-OAM
l l l l l
OAM Mac Source Address: indicates the MAC address of the source MP. Ether Type(VLAN): indicates the type of Ethernet data, such as 0x8100. VLAN tag: indicates the VLAN value of the service traffic. Ether Type (OAM): indicates the type of the ETH-OAM protocol packet. OAM Type: specifies how an MP differs and responds to various OAM operations according to the types of OAM packets. For details on the mapping relationships between OAM Type values and types of OAM packets, see Table 27-6. Table 27-6 Mapping relationships between OAM Type values and types of OAM packets (in the case of a standard MP) OAM Type 1 2 3 4 5 OAMPDU Continuity check message (CCM) Loopback return (LBR) Loopback message (LBM) Link trace reply (LTR) Link trace message (LTM) Usage CC LB test LB test LT test LT test
CC
Used to test link status unidirectionally, an LB test is implemented as follows: 1. The source MEP constructs a CCM packet and transmits it periodically. After receiving the CCM packet from the source MEP, the sink MEP directly enables the CC function for this source MEP. If the sink MEP fails to receive the CCM packet from the source MEP within the check period (that is, 3.5 times of the transmission interval), it reports the corresponding alarm automatically. The alarm clears after the link is restored and the sink MEP receives the CCM packet from the sink MEP.
2.
As shown in Figure 27-4, a CC is implemented as follows: 1. 2. MEP1 transmits CCM packets. On the receipt of the first CCM packet, MEP2, MEP3, and MEP4 in the same MD start their timers so that they can receive the CCM packet from MEP1 periodically. (1) Once the link is faulty, MEP2, MEP3, and MEP4 may fail to receive the CCM packet within the check period. In this case, MEP2, MEP3, and MEP4 report the corresponding alarms. (2) The alarm clears after the link is restored.
Issue 05 (2010-10-30)
27-13
27 ETH-OAM
Figure 27-4 CC diagram

MEP1
VB
MEP2 MEP4 VB VB MEP3
LB Test
Based on bidirectional services, an LB test is performed manually at one time. An LB test is implemented as follows: 1. 2. The source MEP constructs an LBM packet and starts the timer at the same time. After receiving the LBM packet, the sink MP constructs an LBR packet and transmits it back to the source MEP. On the receipt of the LBR packet at the source MEP, the LB test is successful. If the source MEP fails to receive the LBR packet from the sink MEP when its timer expires, the LB test fails. MEP1 transmits an LBM packet to MEP4. After receiving the LBM packet, MIP2 and MIP3 in the same MD transparently transmit the packet after finding that the sink MAC address contained in the packet is different from their own MAC addresses. After receiving the LBM packet, the sink MEP4 transmits an LBR packet to the source MEP1. On the receipt of the LBR packet at MEP1, the LB test is complete.
As shown in Figure 27-5, an LB test is implemented is as follows: 1. 2.
3.
Figure 27-5 LB test diagram
MEP1
MIP2 LBM LBR
MIP3
MEP4
27-14
Issue 05 (2010-10-30)
27 ETH-OAM
LT Test
An LT test is implemented as follows: 1. 2. 3. The source MEP constructs an LTM packet and starts the timer at the same time. All MIPs on the link in the same MD continue to transmit the received LTM packet to the sink MEP and return an LTR packet to the source MEP. After receiving the LTM packet, the sink MEP terminates the LTM packet and transmits an LTR packet back to the source. On the receipt of the LTR packet at the source MEP, the LT test is successful. If the source MEP fails to receive the LTR packet from the sink MEP when its timer expires, the LT test fails.
NOTE
l Additionally, the parameter hop is added to the packet that is transmitted back. The parameter hop is used to indicate the number of the MP that returns the LTR packet on the link. Every time an LTR packet is returned, the number of hops is increased by one. l The function of an LT test is similar to the function of an LB test. The difference is described as follows: In an LB test, only a sink MP responds to LBM frames. In an LT test, all the MPs on the link respond to LTM frames and therefore all the MIPs that are involved from the source MEP to the destination MEP can be identified based on the response messages.
As shown in Figure 27-6, an LT test is implemented as follows: 1. 2. 3. The source MEP1 transmits an LTM packet to the sink MEP3. After receiving the LTM packet, MIP2 transmits an LTR packet to the source MEP1 and forwards the LTM packet. After receiving the LTM packet, the sink MEP3 terminates the LTM packet and transmits an LTR packet to the source MEP1. On the receipt of the LTR packet at MEP1, the LT test is complete.
Figure 27-6 LT test diagram
MEP1
1
MIP2 LTM LTR LTM LTR
MEP3
3
Ping Test
When the equipment at both ends supports the ARP and ICMP protocols, only Huawei equipment can initiate a ping test and Huawei equipment does not respond to a request for a ping test from the opposite equipment. A ping test is implemented as follows: The test initiation end acquires the IP address of the MP and then constructs the ARP packet and ICMP packet for transmission. The MP resolves the
27 ETH-OAM
received ARP packet or ICMP packet and then transmits a response packet back to the test initiation end. Based on the information carried in the received response packet, the initiation end reports the ping test result to the NE software, including the packet loss ratio and delay.
AIS Activation
To locate a fault accurately when several MDs exist on links, activate the AIS and set the level of the customer layer that functions to suppress the AIS information. The AIS activation is implemented as follows: If several maintenance levels exist on links and the level of MP A is n, set the level of the customer layer to n+1 and activate the AIS for MP A. When detecting a fault, MP A reports the AIS alarm to the higher level MPs excluding the MP at the customer layer; the alarm on the MP at the customer layer is suppressed. In this case, if multiple MPs report alarms, you can locate the MP where the fault occurs by checking the alarms reported on MPs of each layer and alarm suppression.
NOTE
In normal cases, if an MP is set to level n, the level of the customer layer that functions to suppress the AIS information is set to n+1.
Performance Check
The performance check method provides an in-service test of packet loss ratio and delay based on the connectivity check between the MPs on the Ethernet service processing unit. A performance check is implemented as follows: The source MP initiates several LB tests and counts different packet loss ratio and delay values.
27.6.2 IEEE 802.3ah OAM

In the case of IEEE 802.3ah OAM, OAM operations are performed by communicating OAMPDUs. Figure 27-7 shows the IEEE 802.3ah OAMPDU.
27-16
Issue 05 (2010-10-30)
27 ETH-OAM
Figure 27-7 IEEE 802.3ah OAMPDU
Octets 6 6 2 1 2 1 42-1496 4
MAC Destination Address MAC Source Address Type Subtype Flags Field Code Data/Pad Field Frame Check Sequence
l l l l l l
Mac Destination Address: indicates the multicast address of the slow protocol, whose value is fixed to 0x01-80-C2-00-00-02. Mac Source Address: indicates the MAC address of the port. Type: indicates the type of the slow protocol, whose value is fixed to 0x8809. Subtype: specifies that the slow protocol is IEEE 802.3ah OAM, whose value is fixed to 0x03. Flags Field: specifies some important state information such as link fault, dying gasp, and critical event. The state information helps to locate faults. Code: identifies IEEE 802.3ah OAM protocol packets of different types. The main packet types are information OAMPDU, event notification OAMPDU, and loopback control OAMPDU. They are associated with auto-discovery, link performance monitoring, and remote loopback respectively. For details on the mapping relationships between Code values and OAM packet types, see Table 27-7. Table 27-7 Mapping relationships between Code values and OAM packet types Code 0x00 0x01 OAMPDU Information Event notification Usage Exchanges the OAM information between the local end and opposite end. Notifies the opposite equipment that bit error performance events occur on the link. Requests one or multiple specific MIB messages.
27-17
0x02
Variable request
Issue 05 (2010-10-30)
27 ETH-OAM
Code 0x03 0x04 0x05-0x FD 0xFE
OAMPDU Variable response Loopback control Reserved Organization specific
Usage Responds to one or multiple specific MIB messages. Enables or disables the remote OAM loopback. Reserved Indicates the extended OAMPDU function that can be selected by different equipment manufacturers. Reserved
0xFF l
Reserved
Data/Pad Field: contains the OAMPDU data, and has a variable length from 42 bytes to 1496 types. When the OAMPDU length is less than 64 bytes (that is, the minimum length), the extended bytes are padded into the field. Frame Check Sequence: indicates the frame check.
Auto-Discovery
As shown in Figure 27-8, when the Code field of the OAMPDU is 0x00, it indicates that the OAMPDU is the information OAMPDU and is used for an OAM auto-discovery.
27-18
Issue 05 (2010-10-30)
27 ETH-OAM
Figure 27-8 Packet format of the information OAMPDU

Octets 1 1 1 2 1 1 2 3 4 Fields Information Type Information Length OAM Version Revision State OAM Configuration OAMPDU Configuration OUI Vendor Specific Information Fixed Values 0x01 0x10 0x01
Octets 6 6 2 1 2 1
Fields Destination Address Source Address Length/Type Subtype Flags Code
Fixed Values 01-80-c2-00-00-02
88-09 0x03
LOCAL INFORMATION TLV
0x00
42-1496 Data/Pad 4 FCS
INFORMATION OAMPDU
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
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 the local information type-length-value (TLV) domain and remote information TLV domain. An OAM configuration byte is contained in a TLV domain. When the link is normal, the information about bit digits in the OAM configuration byte determines whether an OAM auto-discovery is successful. In addition, the information about bit digits determines what functions can be performed after the OAM autodiscovery is successful. Table 27-8 details an OAM configuration byte.
Issue 05 (2010-10-30)
27-19
27 ETH-OAM
Table 27-8 Details of an OAM configuration byte Bit Digit 7-5 Name Reserved Description These bits are set to 0s when the OAMPDU is transmitted and are ignored when the OAMPDU is received. l When this bit is set to 1, it indicates that the data terminal equipment (DTE) supports the transmission of variable response OAMPDUs. l When this bit is set to 0, it indicates that the DTE does not support the transmission of variable response OAMPDUs. 3 Link events l When this bit is set to 1, it indicates that the DTE supports the monitoring on bit error performance (error frames or error signals) of links. When bit errors exceed the threshold, the specific bit error event is transmitted to the opposite end over the specified OAMPDU. l When this bit is set to 0, it indicates that the DTE does not support the monitoring on bit error performance of links. 2 OAM remote loopback support l When this bit is set to 1, it indicates that the DTE supports a loopback request of the remote end. When the loopback command is issued at the remote end, the local end transmits all packets, except OAMPDU packets, back to the remote end for loopback. l When this bit is set to 0, it indicates that the DTE does not support a remote loopback.
Variable retrieval
27-20
Issue 05 (2010-10-30)
27 ETH-OAM
Bit Digit 1
Name Unidirectional support
Description l When this bit is set to 1, it indicates that the local end can continue to transmit OAMPDU packets to the remote end when a fault occurs in the receive direction. l When this bit is set to 0, it indicates that the local end cannot transmit OAMPDU packets to the remote end when the path in the receive direction fails.
OAM mode
l When this bit is set to 1, it indicates that the OAM mode of the DTE is set to Active. l When this bit is set to 0, it indicates that the OAM mode of the DTE is set to Passive. When the local end works in Passive mode, certain OAM functions are not supported. For details, see Table 27-9.
Table 27-9 Mapping relationships between OAM working modes and OAM capabilities OAM Capability OAM Mode Active Mode Initiating an OAM autodiscovery Responding to an OAM autodiscovery Sending the information OAMPDU Sending the event notification OAMPDU Sending the variable request OAMPDU Yes Yes Yes Yes Yes Passive Mode No Yes Yes Yes No
Issue 05 (2010-10-30)
27-21
27 ETH-OAM
OAM Capability
OAM Mode Active Mode Passive Mode Yes No Yes Yes
Sending the variable response OAMPDU Sending the loopback control OAMPDU Responding to the loopback control OAMPDU Sending the organization specific OAMPDU
Yes Yes Yes Yes
When the IEEE 802.3ah OAM protocol is enabled at the port on the Ethernet service processing board, the port broadcasts the information OAMPDU periodically, and receives and processes the information OAMPDU from the opposite port. By exchanging the OAM information (including the OAM configuration information and OAM status information), the OAM connection is established between the two ends.
Link Performance Monitoring

As shown in Figure 27-9, when the Code field of the OAMPDU is 0x01, it indicates that the OAMPDU is the event notification OAMPDU, which is used for notifying bit error performance events mutually.
27-22
Issue 05 (2010-10-30)
27 ETH-OAM
Figure 27-9 Packet format of the event notification OAMPDU

Octets 2 1 1 2 8 8 8 8 4 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 Fixed Values
0x01 0x28
Octets 6 6 2 1 2 1
Fields Destination Address Source Address Length/Type Subtype Flags Code
Fixed Values 01-80-c2-00-00-02
88-09 0x03
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
0x01
42-1496 Data/Pad 4 FCS
ENENT NOTIFICATION OAMPDU
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 count performance from different aspects, link performance monitoring is classified into monitoring on error frame events, monitoring on error frame second events, and monitoring on error frame period events. l Condition for triggering error frame events: Within a window period for error frame monitoring, the number of actually received error frames is more than the preset threshold value.
Issue 05 (2010-10-30)
27-23
27 ETH-OAM
l l
Condition for triggering error frame second events: Within the specific seconds, the number of detected error frame seconds is more than the preset threshold value. Condition for triggering error frame second events: Among a specific number of received frames, the number of detected error frames is more than the preset threshold value.
When the IEEE 802.3ah OAM protocol is enabled at a port, the protocol queries the RMON statistic count on the hardware chip periodically to obtain the information such as the number of correct packets and the number of error packets. After the information is processed, you can determine whether the preceding three performance events occur or not. If a performance event occurs, the opposite end is informed of this event over the event notification OAMPDU. After receiving the notification, the opposite end reports the ETHOAM_RMT_SD alarm so that maintenance engineers can handle the alarm in a timely manner.
Remote Loopback
As shown in Figure 27-10, when the Code field of the OAMPDU is 0x04, it indicates that the OAMPDU is the loopback control OAMPDU, which is used for loopback tests. Figure 27-10 Packet format of the loopback control OAMPDU
Octets 6 6 2 1 2 1 1+41 4 Fields Destination Address Source Address Length/Type Subtype Flags Code Data/Pad FCS 0x04 88-09 0x03 Octets 1 Fields Remote Loopback Command Fixed Values 0x01 Fixed Values 01-80-c2-00-00-02
ENABLE REMOTE LOOPBACK COMMAND

1 Remote Loopback Command 0x02
LOOPBACK CONTROL OAMPDU
DISABLE REMOTE LOOPBACK COMMAND
The loopback initiation end transmits the loopback control OAMPDU packet to the opposite end first. After receiving the packet, the opposite end checks whether it can respond to the remote loopback. If so, the opposite end responds to the remote loopback and transmits a response packet to the initiation end. After receiving the response packet from the opposite response end, the local initiation end analyzes the packet to confirm that the opposite end is in the response loopback state. Then, the local end changes to the loopback initiation state. In this manner, the entire process of loopback initiation is complete.
Self-Loop Test
The self-loop test is developed by Huawei on the basis of the IEEE 802.3ah protocol. The self-loop test packet is constructed as the IEEE 802.3ah OAM protocol packet, with a packet type set to the reserved type 6. The first eight significant reserved bits in the Flags Field are used to carry the ID of the transmit port.
27 ETH-OAM
l l
When the self-loop test is enabled at a port, the self-loop check packets are transmitted from the port. One packet is transmitted every second. When another port receives self-loop check packets, it compares the source MAC address carried in the packets with its own MAC address. If the MAC addresses are the same, it indicates that the local port and the opposite port are located on the same Ethernet service processing board. Then, the port compares its ID with the ID of the opposite port. If the IDs are the same, it indicates that the two ports are the same port. That is, this loopback is a self-loop. If the IDs are different, it indicates that this loopback is an intra-board loopback.

Follow certain guidelines when you plan ETH-OAM.
IEEE 802.1ag OAM

When you create an MP, follow certain guidelines: l l If the interconnected equipment supports IEEE 802.1ag Draft 8.0, create a standard MP. If the interconnected equipment supports only IEEE 802.1ag Draft 3.0, create a common MP.
When you create an MD, follow certain guidelines: l l l An MD name identifies a unique MD on a network. Multiple MDs can be embedded or tangent. A higher level MD can embed a lower level MD. Multiple MDs, however, cannot intersect. An MD is not created for common MPs.
When you create an MA, follow certain guidelines: l l l An MA name must be unique in one MD. MA names in different MDs can be the same. An MA needs to be associated with a VLAN and can be associated with only one VLAN. Several MAs can be associated with the same VLAN. An MA is not created for common MPs.
When you create an MP, follow certain guidelines: l l l l l The service ID needs to be specified. Several MPs can be created on one service. A maximum of 32 MPs can be created on one NE. The MP ID is unique on a network. The levels of the MPs in the same MD must be the same. In an OAM test, all the MPs that perform operations on the same service flow must be in the same MD. In an existing MD for a certain service flow, if an MP of the same level or a higher level is created, the existing MD is impaired, thereby resulting in an OAM test failure. MEPs and MIPs can be created on one service at the same port. The MIP, however, must be of the highest level in all the MPs. In addition, only one MIP can be created. It is recommended that you adopt an MEP as the source and sink of an OAM test. Before performing an LB or LT test, you must activate the CC function if you use an MP ID to identify the sink.
l l l
Issue 05 (2010-10-30)
27 ETH-OAM
The MAC addresses of the MEP and MIP involved in an OAM test cannot be the same.
Select various detection functions as required. Table 27-1 provides details on IEEE 802.1ag ETH-OAM operations and application scenarios.
IEEE 802.3ah OAM

l Only the end in the Active mode can initiate an auto-discovery or remote loopback. The OAM modes can be set to Active at both ends, or Active at one end and Passive at the other end. Note that the OAM modes cannot be set to Passive at both ends. Select appropriate OAM functions as required. Table 27-2 details IEEE 802.3ah ETHOAM operations and application scenarios.

The configuration procedure of IEEE 802.1ag OAM is irrelevant to the configuration procedure of IEEE 802.3ah OAM 27.8.1 IEEE 802.1ag OAM When you use the IEEE 802.1ag OAM feature, define appropriate OAM MPs according to the actual situation and then perform OAM operations as required. 27.8.2 IEEE 802.3ah OAM When you use the IEEE 802.3ah OAM feature, perform appropriate OAM operations as required.
27.8.1 IEEE 802.1ag OAM

When you use the IEEE 802.1ag OAM feature, define appropriate OAM MPs according to the actual situation and then perform OAM operations as required.
27-26
Issue 05 (2010-10-30)
27 ETH-OAM
Table 27-10 Procedure for configuring IEEE 802.1ag OAM Step 1 Operation A.14.1 Creating MDs Description Required when you need to create a standard MP. Set the parameters as follows: l Set Maintenance Domain Name and Maintenance Level to the same values for the NEs on which OAM operations are performed. l In the test of Ethernet services between edge nodes on a transmission network, it is recommended that Maintenance Level take the value of 4. In the test of Ethernet services between NEs within a transmission network, set Maintenance Level to a value less than 4. 2 A.14.2 Creating MAs Required when you need to create a standard MP. Set the parameters as follows: l Set Maintenance Domain Name to the value of Maintenance Domain Name that is set in Step 1. l Set Maintenance Association Name to the same values for the NEs on which OAM operations are performed.
Issue 05 (2010-10-30)
27-27
27 ETH-OAM
Step 3
Description Required. Set the parameters as follows: l In the case of a standard MP, set Maintenance Domain Name and Maintenance Association Name to the values of Maintenance Domain Name and Maintenance Association Name that are set in Step 2. l In the case of a common MP, set Maintenance Domain Name and Maintenance Association Name to NULL. l In the case of an MEP, set Node to the board and port that initiate and terminate OAM operations. In the case of an MIP, set Node to the board and port that Ethernet services travel through. l Set VLAN ID to any VLAN. The settings of the source MEP and sink MEP must be the same. l In the same MA, the value of MP ID must be unique. l If the services between MEPs travel through the Ethernet processing unit, set the Direction to Ingress; otherwise, set the direction to Egress. Generally, ETH-OAM is applicable to end-to-end maintenance of a certain service. Therefore, Direction is set to Ingress for MPs. In the case of MIPs, set Direction to Bidirectional. l In the case of a standard MP, if the sink MP is identified based on the MP ID during the LB or LT test, set CC Status to Active.
NOTE If an LT test is performed and the specified faulty segment needs to be identified, the MIP must be set.
A.14.4 Performing a CC Test
Required when you need to perform a CC.

Issue 05 (2010-10-30)
27-28
27 ETH-OAM
Step
Operation A.14.5 Performing an LB Check A.14.6 Performing a Link Trace Check
Description Required when you need to perform an LB test. Required when you need to perform an LT test. Required when you need to inform the MP at the higher level layer of a fault. Required when you need to check the performance of services between the local equipment and the data communications equipment that supports the ICMP protocol. Required when you need to check the performance of services between the local equipment and the OptiX equipment that supports performance check.
A.14.7 Activating the AIS
A.14.8 Performing a Ping Test
A.14.9 Performing Performance Detection
27.8.2 IEEE 802.3ah OAM

When you use the IEEE 802.3ah OAM feature, perform appropriate OAM operations as required. Table 27-11 Procedure for configuring IEEE 802.3ah OAM Step 1 Operation A.15.1 Enabling the OAM Auto-Discovery Function Description Required. Set the parameters as follows: l Set Enable OAM Protocol to Enabled. l It is recommended that you set OAM Working Mode to Active.
Issue 05 (2010-10-30)
27-29
27 ETH-OAM
Step 2
Operation Link Performance Monitoring A.15.2 Enabling the Link Event Notification
Description Optional. Set Remote Alarm Support for Link Event to Enabled if the opposite NE needs to be informed of the faults or performance threshold events that are detected. Optional. Perform this operation when you need to adjust the thresholds of performance events. Optional. Ensure that Remote Side Loopback Response is set to Enabled for the remote equipment when you need to perform a remote loopback. Optional. Set Loop Detection to Enabled when you need to perform a self-loop test at the port.
A.15.3 Modifying the Parameters of the OAM Error Frame Monitoring Threshold
Remote Loopback
A.15.4 Performing the Remote Loopback
Self-Loop Test
A.15.5 Enabling the Self-Loop Detection
27.9 Configuration Example (IEEE 802.1ag OAM)

This section uses an example to describe how to plan and configure IEEE 802.1ag OAM according to network conditions. 27.9.1 Networking Diagram This section describes the networking information about NEs. 27.9.2 Service Planning The service planning information contains all the parameters required for configuring the NE data. 27.9.3 Configuration Process This section describes the procedure of data configuration.
27 ETH-OAM

This section describes the networking information about NEs. Figure 27-11 shows a radio network that transmits Ethernet services for base station backhauls. The network is divided into several VLANs. VLAN 100 to VLAN 109 are used by services of NodeB A, and VLAN 110 to VLAN 119 are used by services of NodeB B. After a fault on the radio network, faults occur in services of NodeB A in VLAN 100 and services of NodeB B in VLAN 110. In this case, LT tests are required to locate the fault. Figure 27-11 Networking diagram of IEEE 802.1ag OAM
NodeB A VLAN 100-109
5-IFH2-1(to NE2) 4-EMS6-5(to 5-IFH2-2) 4-EMS6-1(to NodeB A) 4-EMS6-2(to NodeB B) 4-EMS6-1(to RNC) 7-IFH2-2(to 4-EMS6-5) 7-IFH2-1(to NE1)
NE 1 NodeB B VLAN 110-119
NE 2
RNC
Ethernet link
Radio link

Planning Information About the MP

NOTE
NE1 and NE2 support IEEE 802.1ag Draft 8.0, and therefore you can create standard MPs to provide ETHOAM.
Figure 27-12 shows the planning information about the MP.
Issue 05 (2010-10-30)
27-31
27 ETH-OAM
Figure 27-12 Information about the MPs that belong to different VLANs
MA1 NE1 4-EMS6-1 4-EMS6-5 4-EMS6-5 NE2 4-EMS6-1
VLAN100 MEP 1 MIP 5 MA2 NE1 4-EMS6-2 4-EMS6-5 4-EMS6-5 NE2 4-EMS6-1 MIP 6 MEP 2
VLAN110 MEP 3 MIP 7 MIP 8 MEP 4
OAM Configuration Information

Table 27-12, Table 27-13, Table 27-14, Table 27-15, and Table 27-16 provide the information about the MD, MA, MEP, MIP, and LT test. Table 27-12 Information about the MD Parameter Maintenance Domain Name Maintenance Domain Level NE1 MD1 4 NE2 MD1 4
Table 27-13 Information about the MA Parameter Maintenance Domain Name Maintenance Association Name NE1 MD1 MA1 MD1 MA2 NE2 MD1 MA1 MD1 MA2
27-32
Issue 05 (2010-10-30)
27 ETH-OAM
Table 27-14 Information about the MEP Parameter Maintenance Domain Name Maintenance Association Name Node VLAN ID MP ID Type Direction CC Status NE1 MD1 MA1 MD1 MA2 NE2 MD1 MA1 MD1 MA2
4-EMS6-1 100 1 MEP Ingress Active
NOTE
If the sink MP is identified based on the MP ID, CC Status must be set to Active.
Table 27-15 Information about the MIP Parameter Maintenance Domain Name Maintenance Association Name Node VLAN ID MP ID Type Direction NE1 MD1 MA1 MD1 MA2 NE2 MD1 MA1 MD1 MA2
4-EMS6-5 100 5 MIP Bidirectional
Table 27-16 Information about the LT test Parameter Maintenance Domain Name NodeB A to RNC MD1 NodeB B to RNC MD1
Issue 05 (2010-10-30)
27-33
27 ETH-OAM
Parameter Maintenance Association Name LT Source MP ID LT Sink MP ID
NodeB A to RNC MA1 1 2
NodeB B to RNC MA2 3 4

Procedure
Step 1 A.14.1 Creating MDs. The values for the involved parameters are provided as follows. Parameter Value Range NE1 Maintenance Domain Name Maintenance Level MD1 4 NE2 MD1 4
Step 2 A.14.2 Creating MAs. The values for the involved parameters are provided as follows. Parameter Value Range NE1 Maintenance Domain Name Maintenance Association Name MD1 MA1 MD1 MA2 NE2 MD1 MA1 MD1 MA2
Step 3 A.14.3 Creating MPs. The values for the involved parameters of NE1 are provided as follows.
27-34
Issue 05 (2010-10-30)
27 ETH-OAM
Parameter
Value Range MEP MIP MD1 MA2 MD1 MA1 MD1 MA2
Maintenance Domain Name Maintenance Association Name Node VLAN ID MP ID Type Direction CC Status
MD1 MA1
4-EMS6PORT1 100 1 MEP Ingress Active
4-EMS6PORT5 100 5 MIP Bidirectional -
The values for the involved parameters of NE2 are provided as follows. Parameter Value Range MEP Maintenance Domain Name Maintenance Association Name Node VLAN ID MP ID Type Direction CC Status MD1 MA1 MD1 MA2 MIP MD1 MA1 MD1 MA2
Step 4 A.14.6 Performing a Link Trace Check. l The values for the parameters that are associated with the LT test for Ethernet services from NodeB A to the RNC are provided as follows.
Issue 05 (2010-10-30)
27-35
27 ETH-OAM
Parameter LT Source MP ID LT Sink MP ID
Value Range 1 2
l The values for the parameters that are associated with the LT test for Ethernet services from NodeB B to the RNC are provided as follows. Parameter LT Source MP ID LT Sink MP ID Value Range 3 4
In normal cases, no packets are lost. If any fault occurs, locate the fault based on the test result. ----End
27.10 Configuration Example (IEEE 802.3ah OAM)

This section uses an example to describe how to plan and configure IEEE 802.3ah OAM according to the network conditions. 27.10.1 Networking Diagram This section describes the networking information about NEs. 27.10.2 Service Planning The service planning information contains all the parameters required for configuring the NE data. 27.10.3 Configuration Process This section describes the procedure of data configuration. In this example, NE1 and NE2 adopt the same configuration method and use the same configuration data. Therefore, this section describes only NE1.

This section describes the networking information about NEs. The application of the IEEE 802.3ah OAM feature does not focus on specific services. Instead, the application of the IEEE 802.3ah OAM feature focuses on the maintenance of the point-topoint Ethernet link between two sets of equipment that are directly connected to each other. When all the equipment supports the IEEE 802.3ah OAM protocol, the OAM auto-discovery is performed if the IEEE 802.3ah OAM protocol is enabled on all the interconnected ports. If the OAM auto-discovery is successful, you can perform OAM operations as required. As shown in Figure 27-13, you can enable the IEEE 802.3ah OAM protocol if you need to monitor the performance of the Ethernet link between NE1 and NE2, which are connected directly to each other.
27-36
Issue 05 (2010-10-30)
27 ETH-OAM
Figure 27-13 Networking diagram of IEEE 802.3ah OAM
IEEE 802.3ah
4-EMS6-1(to NE2) 4-EMS6-1(to NE1)
NodeB A
NE3
NE1
NE2
NE4
NodeB B
Customer Ethernet equipment Microwave equipment

OAM Parameters
Table 27-17 provides the OAM parameters. Table 27-17 OAM parameters Parameter Port Enable OAM Protocol OAM Working Mode Remote Alarm Support for Link Event NE1 4-EMS6-PORT1 Enabled Active Enabled NE2 4-EMS6-PORT1 Enabled Active Enabled
Error Frame Monitoring Information in OAM

Table 27-18 provides the error frame monitoring information in OAM.
Issue 05 (2010-10-30)
27-37
27 ETH-OAM
Table 27-18 Error frame monitoring information in OAM Parameter Port Error Frame Monitor Window (ms) Error Frame Monitor Threshold (Entries) Error Frame Period Window (frame) Error Frame Period Threshold (frame) Error Frame Second Window (s) Error Frame Second Threshold (s) NE1 4-EMS6-PORT1 2000 2 1488000 2 120 2 NE2 4-EMS6-PORT1 2000 2 1488000 2 120 2
NOTE
In normal cases, it is recommended that you use the default error frame monitoring information.

This section describes the procedure of data configuration. In this example, NE1 and NE2 adopt the same configuration method and use the same configuration data. Therefore, this section describes only NE1.
Procedure
Step 1 A.15.1 Enabling the OAM Auto-Discovery Function. The values for the involved parameters are provided as follows. Parameter Enable OAM Protocol OAM Working Mode Value Range Enabled Active
Step 2 A.15.2 Enabling the Link Event Notification. The values for the involved parameters are provided as follows. Parameter Remote Alarm Support for Link Event
27-38
Value Range Enabled

Issue 05 (2010-10-30)
27 ETH-OAM
Step 3 A.15.3 Modifying the Parameters of the OAM Error Frame Monitoring Threshold . The values for the involved parameters are provided as follows. Parameter Error Frame Monitor Window (ms) Error Frame Monitor Threshold (Entries) Error Frame Period Window (frame) Error Frame Period Threshold (frame) Error Frame Second Window (s) Error Frame Second Threshold (s) Value Range 2000 2 1488000 2 120 2
----End

The operation tasks associated with 802.1ag OAM are irrelevant to the operation tasks associated with 802.3ah OAM. 27.11.1 Task Collection (IEEE 802.1ag OAM) This section provides the hyperlinks of the operation tasks associated with IEEE 802.1ag OAM. 27.11.2 Task Collection (IEEE 802.1ah OAM) This section provides the hyperlinks of the operation tasks associated with IEEE 802.3ah OAM.
27.11.1 Task Collection (IEEE 802.1ag OAM)

This section provides the hyperlinks of the operation tasks associated with IEEE 802.1ag OAM.
Related Tasks
A.14.1 Creating MDs A.14.2 Creating MAs A.14.3 Creating MPs A.14.4 Performing a CC Test A.14.5 Performing an LB Check A.14.6 Performing a Link Trace Check A.14.7 Activating the AIS A.14.8 Performing a Ping Test A.14.9 Performing Performance Detection
Issue 05 (2010-10-30)
27-39
27 ETH-OAM
27.11.2 Task Collection (IEEE 802.1ah OAM)

This section provides the hyperlinks of the operation tasks associated with IEEE 802.3ah OAM.
Related Tasks
A.15.1 Enabling the OAM Auto-Discovery Function A.15.2 Enabling the Link Event Notification A.15.3 Modifying the Parameters of the OAM Error Frame Monitoring Threshold A.15.4 Performing the Remote Loopback A.15.5 Enabling the Self-Loop Detection

When detecting an exception by performing ETH-OAM operations, an NE reports the corresponding alarm.
Relevant Alarms
Alarms relevant to a standard MP are as follows: l ETH_CFM_LOC The ETH_CFM_LOC alarm indicates the loss of continuity. When the system does not receive the CCM sent by the remote MEP within 3.5 times of the continuity check period, the ETH_CFM_LOC alarm is reported. l ETH_CFM_MISMERGE The ETH_CFM_MISMERGE alarm indicates an incorrect connection. When the system receives a message that indicates a mismatch of MA IDs or receives a low level CCM, the ETH_CFM_MISMERGE alarm is reported. l ETH_CFM_RDI The ETH_CFM_RDI alarm indicates that the remote MEP fails to receive CCMs. When the system receives a CCM that contains the RDI sent by the remote end, the ETH_CFM_RDI alarm is reported. l ETH_CFM_UNEXPERI The ETH_CFM_UNEXPERI alarm indicates error frames. When the system receives an invalid CCM, the ETH_CFM_UNEXPERI alarm is reported. l ETHOAM_SELF_LOOP The ETHOAM_SELF_LOOP alarm indicates that a MAC port is looped back when the point-to-point ETH-OAM function is enabled. When the MAC port of a board receives the OAM protocol packet sent by the MAC port or the local board after the loopback detection function is enabled, this alarm is reported. Alarms relevant to a common MP are as follows: l EX_ETHOAM_CC_LOS The EX_ETHOAM_CC_LOS alarm indicates that the periodical CC packet is lost. After receiving the first CC packet, the sink MP starts the timer to periodically check the link
27 ETH-OAM
between the source MP and the sink MP. If the sink MP does not receive the CC packet sent by the same source MP even when its timer expires, this alarm is reported. l EX_ETHOAM_MPID_CNFLCT The EX_ETHOAM_MPID_CNFLCT alarm indicates that the IDs of MPs are in conflict. When an MP receives the packet sent by the MP that has the same ID and the two MPs are in the same MD, this alarm is reported. l ETHOAM_RMT_LOOP The ETHOAM_RMT_LOOP alarm indicates that a remote loopback is initiated when the point-to-point ETH-OAM function is enabled. When the port on which the OAM protocol is enabled responds to the remote loopback command sent from the opposite end or the opposite end issues the loopback control command, this alarm is reported. l ETHOAM_RMT_SD The ETHOAM_RMT_SD alarm indicates that the performance of the remote Ethernet is degraded when the point-to-point ETH-OAM function is enabled. When the port on which the OAM protocol is enabled receives the link event notification packet sent by the opposite end, this alarm is reported. l ETHOAM_RMT_CRIT_FAULT The ETHOAM_RMT_CRIT_FAULT alarm indicates a critical fault at the remote end when the point-to-point ETH-OAM function is enabled. When the port on which the OAM protocol is enabled receives the OAM packet that contains critical fault information sent by the opposite end, this alarm is reported. l ETHOAM_DISCOVER_FAIL The ETHOAM_DISCOVER_FAIL alarm indicates a discovery failure when the point-topoint ETH-OAM function is enabled. When the discovery performed by a port on which the OAM protocol is enabled fails, this alarm is reported. l ETHOAM_VCG_SELF_LOOP The ETHOAM_VCG_SELF_LOOP alarm indicates that a VCTRUNK port is looped back when the point-to-point ETH-OAM function is enabled. When the VCTRUNK port of a board receives the OAM protocol packet sent by the VCTRUNK port or the local board after the loopback detection function is enabled, this alarm is reported.
Relevant Events
None.
27.13 FAQs
This section provides the answers to the questions that are frequently raised when ETH-OAM is used. Question: Does the ETH-OAM affect the Ethernet services? Answer: The ETH-OAM detects and monitors the connectivity and performance of the service trail by using the Ethernet OAMPDU. During the detection and monitoring, the services are not affected. Answer: Compared with conventional Ethernet maintenance and fault locating methods, what are the advantages of ETH-OAM? Answer: ETH-OAM has the following advantages:
27 ETH-OAM
l l l l l
As a low-rate protocol, the ETH-OAM protocol occupies low bandwidth. Thus, this protocol does not affect services carried on the link. ETH-OAM is not related to the encapsulation format of the Ethernet. Thus, the OAM function between different encapsulation formats can be realized. ETH-OAM allows the loopback to be performed for a specific service selectively. ETH-OAM can detect faults in the hardware. ETH-OAM can detect and locate faults automatically.
27-42
Issue 05 (2010-10-30)
28 Synchronous Ethernet
28
About This Chapter
Synchronous Ethernet
This chapter describes the synchronous Ethernet feature. 28.1 Introduction This section describes the definition of synchronous Ethernet and describes its purpose. 28.2 Specifications This section describes the specifications of synchronous Ethernet. 28.3 Reference Standards and Protocols This section describes the standards and protocols associated with synchronous Ethernet. 28.4 Availability This section describes the support required by the application of the synchronous Ethernet feature and its dependency. 28.5 Principles The realization of the synchronous Ethernet feature complies with ITU-T G.8261 and ITU-T G. 8262. 28.6 Planning Guidelines Follow certain rules when you plan synchronous Ethernet. 28.7 Configuration Procedure By default, the NEs consider that all the Ethernet links provide clock signals. Thus, you need only to configure the clock source for the NEs that require synchronous Ethernet clock signals. 28.8 Configuration Example This section uses an example to describe how to plan and configure synchronous Ethernet according to the network conditions. 28.9 Task Collection This section provides the hyperlinks of the operation tasks associated with synchronous Ethernet. 28.10 Relevant Alarms and Events When an abnormality occurs when the Ethernet link functions as the clock source, the NE reports the corresponding alarm. 28.11 FAQs
This section provides the answers to the questions that are frequently raised when synchronous Ethernet is used.
28-2
Issue 05 (2010-10-30)
28.1 Introduction
This section describes the definition of synchronous Ethernet and describes its purpose.
Definition
Synchronous Ethernet is a technology of frequency synchronization at the physical layer. It extracts clock signals from serial bit streams on an Ethernet line, and transmits the data through the extracted clock signals to implement the transfer of clock signals.
Purpose
The synchronous Ethernet technology is used to transfer clock signals through Ethernet links. As shown in Figure 28-1, the OptiX RTN 620s form a synchronous Ethernet. The synchronous Ethernet transfers the clock information between the RNC equipment and the NodeB. Figure 28-1 Application of synchronous Ethernet in a wireless access network
NE1 GE
NE2 GE
NodeB
RNC
Ethernet clock signal Ethernet link
28.2 Specifications
This section describes the specifications of synchronous Ethernet. Table 28-1 lists the specifications of synchronous Ethernet. Table 28-1 Specifications of synchronous Ethernet Item Port receiving synchronous Ethernet clock signals Port transmitting synchronous Ethernet clock signals
Issue 05 (2010-10-30)
Specification GE port of the IFH2 board GE port of the IFH2 board
28-3
Item Input/Output of SSM packets Clock frequency stability (holdover mode) Clock frequency stability (locked mode)
Specification Not supported Less than 4.6 ppm Less than 50 ppb
NOTE
When the FE/GE port works in 10BASE-T mode, it does not support the synchronous Ethernet clock.

This section describes the standards and protocols associated with synchronous Ethernet. The following protocols are associated with synchronous Ethernet: l l ITU-T G.8261: Timing and Synchronization aspects in Packet Networks ITU-T G.8262: Timing characteristics of synchronous Ethernet equipment slave clock
28.4 Availability
This section describes the support required by the application of the synchronous Ethernet feature and its dependency.

Table 28-2 Hardware and version support Feature Synchronous Ethernet Applicable Board IFH2 Applicable Hardware Version All the versions Applicable Product Version V100R003 and later
NOTE
Only the GE port on the IFH2 board of the OptiX RTN 620 supports the synchronous Ethernet function. The Ethernet boards (including EFT4, EMS6, and EFP6) do not support the synchronous Ethernet function.
Feature Dependency
Synchronous Ethernet does not affect other features.
28.5 Principles
The realization of the synchronous Ethernet feature complies with ITU-T G.8261 and ITU-T G. 8262.
As shown in Figure 28-2, the synchronous Ethernet function of the OptiX RTN 620 is implemented as follows. When the Ethernet interface is the clock source of the local NE: 1. The PHY component of the Ethernet interface recovers the clock signals from the code stream in the Ethernet link, and divides the frequency of the clock signals. Then, the clock signals are sent to the system clock module. The system clock module selects a clock with the highest priority based on the clock source priority table and synchronizes this clock to be the system clock.
2.
When the Ethernet interface is the clock source of the local NE that outputs clock signals to the downstream equipment: 1. 2. The system clock module sends a highly precise system clock to the Ethernet interface of the NE. The PHY component of the Ethernet interface sends the clock through the code stream in the Ethernet link.
Figure 28-2 Realization principle of synchronous Ethernet

Clock recovery Line clock Frequency division
System clock module
Ethernet interface module
PHY MAC
PLL
System clock
Receive direction Transmit direction

Follow certain rules when you plan synchronous Ethernet. The synchronous Ethernet feature is planned according to the networkwide synchronous policy. If the upstream NE needs to transfer clock signals to the local NE through Ethernet, the synchronous Ethernet is enabled (the port for transmitting clock signals is configured as the clock source).
Issue 05 (2010-10-30)
28-5

By default, the NEs consider that all the Ethernet links provide clock signals. Thus, you need only to configure the clock source for the NEs that require synchronous Ethernet clock signals. In the case of the OptiX RTN 620, see Table 28-3 to configure the Ethernet clock source. Table 28-3 Configuration procedure for synchronous Ethernet Step 1 Operation A.8.1 Configuring Clock Sources Remarks Required In the case of an NE that accesses the Ethernet clock source directly, set the Ethernet clock source as the clock source of the NE.

This section uses an example to describe how to plan and configure synchronous Ethernet according to the network conditions. 28.8.1 Networking Diagram This section describes the networking information about NEs. 28.8.2 Service Planning The service planning information contains all the parameters required for configuring the NE data. 28.8.3 Configuration Process This section describes the process of configuring service data.

This section describes the networking information about NEs. As shown in Figure 28-3, synchronous Ethernet clocks are configured on Hybrid radio links according to the clock synchronization requirement. On the ring: l l The microwave transmission network transfers clock signals between the BSC and the BTS. The BTS and all the NEs support synchronous Ethernet.
28-6
Issue 05 (2010-10-30)
Figure 28-3 Networking diagram of synchronous Ethernet

5-IFH2-1(to NE2) 5-IFH2-2(to BTS) 5-IFH2-1(to NE1) 5-IFH2-2(to BSC)
GE BTS NE1 NE2
GE
BSC

Clock Source Information

Based on 28.8.1 Networking Diagram, you can obtain the clock source information as shown in Figure 28-4. Figure 28-4 Networking diagram
GE BTS NE1 5-IFH2-1/ Internal NE2 5-IFH2-2/ Internal GE
BSC
NOTE
You need to separately configure an Ethernet clock source for each link in the LAG.
Clock Protection
The GE port of the OptiX RTN 620 does not support reception and transmission of SSM packets. Thus, you need not enable the SSM and extended SSM protocols.
Clock Synchronization Policy for a Base Station

In this example, the microwave network is synchronized with the BSC through the GE port and provides timing reference signals through the GE port.

This section describes the process of configuring service data.
Procedure
Step 1 A.14.2 Creating MAs. The following table provides the values of parameters. Parameter Value Range NE1 Clock Source 5-IFH2-1(IF) Internal clock source NE2 5-IFH2-2(ETH) Internal clock source
Step 2 A.14.2 Creating MAs. NE Working Mode of all the NEs is Tracing Mode. ----End

This section provides the hyperlinks of the operation tasks associated with synchronous Ethernet.

When an abnormality occurs when the Ethernet link functions as the clock source, the NE reports the corresponding alarm.
Relevant Alarms
l l SYNC_C_LOS The SYNC_C_LOS alarm indicates that the class of synchronization source is lost. LTI The LTI alarm indicates loss of synchronization source. This alarm is reported when all the synchronization sources of an NE are lost.
Relevant Events
None.
28.11 FAQs
This section provides the answers to the questions that are frequently raised when synchronous Ethernet is used. Q: Does synchronous Ethernet support the transmission of clock quality information? A: The port of the OptiX RTN 620 does not support the reception and transmission of SSM packets.
29 Remote Monitoring
29
About This Chapter
Remote Monitoring
This chapter describes the remote monitoring (RMON) feature. 29.1 Introduction This section provides the definition of RMON and describes its purpose. 29.2 Basic Concepts This section describes the basic concepts that you should be familiar with before using RMON. 29.3 Specifications This section describes the specifications of RMON. The specifications of each management group are described and the port rate can be queried by using the RMON function. 29.4 Reference Standards and Protocols This section describes the standards and protocols associated with RMON. 29.5 Availability This section describes the support required by RMON and dependency of the feature. 29.6 Principles The RMON agent is embedded in an Ethernet board. The NMS exchanges data information with the agent through basic SNMP commands. In this manner, the network statistics is collected. 29.7 Planning Guidelines Follow certain guidelines when you plan RMON. 29.8 Configuration Procedure When applying RMON, you need to perform different operations as required. 29.9 Configuration Example This section uses an example to describe how to plan and configure RMON according to network conditions. 29.10 Task Collection This section provides the hyperlinks of the operation tasks associated with RMON. 29.11 Relevant Alarms and Events
Issue 05 (2010-10-30)
29-1
When the entries in an RMON alarm group exceed the pre-set thresholds, a performance event is reported, indicating that the RMON module performance value crosses the lower threshold or upper threshold. 29.12 FAQs This section describes the answers to the questions that are frequently asked when the RMON feature is used.
29-2
Issue 05 (2010-10-30)
29.1 Introduction
This section provides the definition of RMON and describes its purpose.
Definition
The RMON feature is based on the management information base (MIB) in the architecture of the simple network management protocol (SNMP). RMON defines the method of managing Ethernet performance. Through the RMON function, you can monitor the performance of Ethernet ports in the same manner as you monitor the performance of SDH or PDH ports.
Purpose
RMON detects the performance of Ethernet services.
29.2 Basic Concepts

This section describes the basic concepts that you should be familiar with before using RMON. 29.2.1 SNMP Currently, SNMP is the most widely used network management protocol. SNMP is used to ensure transport of the management information between any two nodes on the network. This facilitates the network administrator to retrieve information, modify information, locate a fault, perform fault diagnosis, plan capacities, and generate a report on any node. 29.2.2 RMON Management Groups The Ethernet board provides the following RMON management groups specified in IETF RFC2819: statistics group, history group, alarm group, and history control group. 29.2.3 List of RMON Alarm Entries RMON alarm entries refer to the table entries in the RMON alarm group. 29.2.4 List of RMON Performance Entries RMON performance entries refer to the table entries in the RMON statistics group or history group.
29.2.1 SNMP
Currently, SNMP is the most widely used network management protocol. SNMP is used to ensure transport of the management information between any two nodes on the network. This facilitates the network administrator to retrieve information, modify information, locate a fault, perform fault diagnosis, plan capacities, and generate a report on any node.
Architecture of SNMP
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. When the RMON function is used, the Web LCT or T2000 server functions as the NMS.
Agent The agent is the server software that is running on the network equipment. When the RMON function is used, the agent is embedded in an Ethernet board.
The NMS can send GetRequest, GetNextRequest, or SetRequest packets to the agent. On receiving such request packets, the agent performs a read or write operation according to the type of the packets, generates Response packets, and sends Response packets to the NMS. When an exception occurs on the equipment or the state of the equipment changes (for example, the equipment restarts), the agent sends Trap packets to the NMS and reports the event to the NMS. The transmission of SNMP packets is based on the connectionless transport layer UDP. Therefore, SNMP helps to implement connections between a wide variety of equipment.
MIB
In SNMP packets, management variables are used to describe the managed objects on the equipment. To uniquely identify each managed object on the equipment, SNMP uses the hierarchical naming scheme. The overall hierarchy 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. MIB described the tree hierarchy and collects the definitions of standard variables of the monitored network equipment. RMON is a common MIB defined according to IETF RFC2819.
29.2.2 RMON Management Groups

The Ethernet board provides the following RMON management groups specified in IETF RFC2819: statistics group, history group, alarm group, and history control group.
Statistics Group
A statistics group counts the absolute performance values from the time the statistics group is created until the current time. The Ethernet board supports port-based statistics groups. In the case of a board, you can create one statistics group for only one port. The sampling interval of a statistics group can be set. The value range of the sampling interval is from 5 second to 150 seconds. For the performance entries that can be added to a statistics group, see 29.2.3 List of RMON Alarm Entries.
Alarm Group
An alarm group monitors the specified alarm objects (for example, the performance data of ports). When the value of the monitored data crosses a configured threshold, an alarm is generated. An Ethernet board supports port-based alarm groups. You can create only one alarm group for a board. The number of alarm entries in an alarm group cannot exceed ten. You can set the following items for an alarm object: monitored object, sampling interval, report mode (report in case of upper threshold-crossing, report in case of lower threshold-crossing, report in case of upper threshold-crossing or lower threshold-crossing), and upper/lower thresholds. For the alarm entries that can be added to an alarm group, refer to 29.2.4 List of RMON Performance Entries.
History Control Group

A history control group specifies the methods of monitoring history performance data. According to the attributes of the history control group, an Ethernet board periodically collects the required statistical network information and temporarily stores the information on the board. A history control group has the following attributes: l History table type You can set the history table type to 30-second, 30-minute, custom period 1, or custom period 2. In the case of a custom period, you need to manually set the required sampling interval. l Monitored object This specifies the port for which performance counting is performed. You can set monitored objects for each history table type. l Performance entry This specifies the performance entries to which the history performance data corresponds. The stored data is the latest history performance data, because the history performance data is stored in the wrap mode. For example, if the performance entry is set to 10, it indicates that an Ethernet board stores the latest 10 history performance data entries. You can set the number of items for each history table type. The number of items can be set to a maximum of 50.
History Group
A history group specifies the methods of querying history performance data. An Ethernet board filters the history performance data stored on the board according to the attributes of the history group and returns the history performance data that meets the filtering conditions. A history group has the following attributes: l History table type This specifies the sampling period to which the history performance data corresponds. You can set the history table type to 30-second, 30-minute, custom period 1, or custom period 2. l l Monitored object This specifies the port to which the history performance data corresponds. Performance entry This specifies the performance entries to which the history performance data corresponds. The list of performance entries is the same as the list of the performance entries that can be added into a statistics group. l Query conditions This specifies the relative time to which the history performance data corresponds. 1 represents the earliest item. You can query a maximum of ten entries at one time.
NOTE
You can query performance in a history group only after you enable the performance monitoring function in the history control group.
29.2.3 List of RMON Alarm Entries

RMON alarm entries refer to the table entries in the RMON alarm group.
Table 29-1 List of RMON alarm entries Alarm Name Dropevent UndersizePkts OversizePkts Fragments Jabbers FCSErrors Description Number of packet loss events exceeding the threshold Number of undersized packets exceeding the threshold Number of oversized packets exceeding the threshold Number of fragment packets exceeding the threshold Number of jabber packets exceeding the threshold Number of packets with FCS errors exceeding the threshold EMS6, EFT4, EFP6 Source EMS6, EFT4, IFH2, EFP6
29.2.4 List of RMON Performance Entries

RMON performance entries refer to the table entries in the RMON statistics group or history group. Table 29-2 List of RMON performance entries Category of Performa nce Entries Basic performanc e Name of a Performance Entry Source
Packets received (packets) Packets received (64 bytes in length) (packets) Packets received (65-127 bytes in length) (packets) Packets received (128-255 bytes in length) (packets) Packets received (256-511 bytes in length) (packets) Packets received (512-1023 bytes in length) (packets) Packets received (1024-1518 bytes in length) (packets)
EMS6, EFT4, IFH2, EFP6
29-6
Issue 05 (2010-10-30)
Category of Performa nce Entries
Name of a Performance Entry
Source
Bytes received (bytes) Oversized packets received (packets) Undersized packets received (packets) Multicast packets received (packets) Broadcast packets received (packets) Undersized error packets received (packets) Oversized error packets received (packets) Packet loss events Fragments received (packets) Collisions (times) FCS and alignment error packets (packets) Extended performanc e Packets transmitted (64 bytes in length) (packets) Packets transmitted (65-127 bytes in length) (packets) Packets transmitted (128-255 bytes in length) (packets) Packets transmitted (256-511 bytes in length) (packets) Packets transmitted (512-1023 bytes in length) (packets) Packets transmitted (1024-1518 bytes in length) (packets) Packets received and transmitted (64 bytes in length) (packets) Packets received and transmitted (65-127 bytes in length) (packets) Packets received and transmitted (128-255 bytes in length) (packets) IFH2, EFP6 EMS6, EFT4, EFP6 EMS6, EFT4, IFH2 EMS6, EFT4,EFP6 EMS6, EFT4 EFT4, EFP6 EMS6, EFT4, IFH2, EFP6
Issue 05 (2010-10-30)
29-7
Source
Packets received and transmitted (256-511 bytes in length) (packets) Packets received and transmitted (512-1023 bytes in length) (packets) Packets received and transmitted (1024-1518 bytes in length) (packets) Unicast packets transmitted (packets) Pause frames received (frames) Pause frames transmitted (frames) FCS error frames (frames) Oversized packets transmitted (packets) Packets transmitted (packets) Bytes transmitted (bytes) Packets received (1519 bytes to the MTU in length) (packets) Packets transmitted (1519 bytes to the MTU in length) (packets) Packets received and transmitted (1519 bytes to the MTU in length) (packets) Transmitting packet loss events (packets) Unicast packets received (packets) Multicast packets transmitted (packets) Broadcast packets transmitted (packets) Rate of good full-frame bytes received (bytes/second) Rate of good full-frame bytes transmitted (bytes/second) EMS6, EFT4, EFP6 IFH2
29-8
Issue 05 (2010-10-30)
Source
Good full-frame bytes received (bytes) Good full-frame bytes transmitted (bytes) Control frames received (frame) Control frames transmitted (frame) Alignment error frames (frame) Control packets transmitted (packets) Frames properly transmitted after only one collision (frame) Frames properly transmitted after multiple collisions (frame) Late collisions (times) Frames unsuccessfully transmitted after successive collisions (frame) Delayed frames (frame) VCG performanc e Packets received (packets) Packets transmitted (packets) Good packets received (packets) Good packets transmitted (packets) Rate of good full-frame bytes received (bytes/second) Rate of good full-frame bytes transmitted (bytes/second) Octects Received(octets) Octects Transmitted(octets) EMS6, EFP6 EMS6, EFT4 EMS6, EFT4, EFP6 EMS6, EFT4, EFP6 EFP6 EMS6, EFT4
NOTE
The ports of the EMS6, EFP6, EFT4, and IFH2 boards support the basic performance and the extended performance. The VCTRUNK of the EMS6 and EFP6 board supports the VCG performance. The VCTRUNK of the EFT4 board does not support RMON.
Issue 05 (2010-10-30)
29-9
29.3 Specifications
This section describes the specifications of RMON. The specifications of each management group are described and the port rate can be queried by using the RMON function. Table 29-3 lists the specifications of RMON. Table 29-3 Specifications of RMON Item Statistics group Querying the realtime performance statistics of Ethernet ports Sampling interval (s) Resetting statistics group counter Alarm group Querying the realtime alarm statistics of Ethernet ports Sampling interval (s) Setting the upper and lower thresholds of performance statistics Setting the alarm report mode Setting the monitoring status History control group Setting the sampling period of history performance statistics Setting the monitoring status Specification Supported
5-150 Supported Supported
5-600 Supported
Supported Supported 30-second 30-minute 300 seconds to 43200 seconds 300 seconds to 86400 seconds Supported
29-10
Issue 05 (2010-10-30)
Item History group Querying the history performance statistics of Ethernet ports Setting the sampling period of history performance statistics
Specification Supported
30-second 30-minute 300 seconds to 43200 seconds 300 seconds to 86400 seconds

This section describes the standards and protocols associated with RMON. The following protocols are associated with RMON: l l IETF RFC 1757: Remote Network Monitoring Management Information Base IETF RFC 2819: Remote Network Monitoring Management Information Base
29.5 Availability
This section describes the support required by RMON and dependency of the feature.

Table 29-4 Hardware and version support Feature RMON Applicable Board EFT4 EMS6 IFH2 EFP6 Applicable Hardware Version All the versions All the versions All the versions All the versions Applicable Product Version V100R002 and later V100R002 and later V100R003 and later V100R005C00 and later
Feature Dependency
The RMON feature does not affect other features.
Issue 05 (2010-10-30)
29-11
29.6 Principles
The RMON agent is embedded in an Ethernet board. The NMS exchanges data information with the agent through basic SNMP commands. In this manner, the network statistics is collected.
Statistics Group
The processing flow is as follows: 1. 2. 3. A maintenance engineer clicks Resetting begins. The NMS sends the corresponding request packet to the RMON agent. The RMON agent embedded in the Ethernet board resets the corresponding current performance counting register and returns the corresponding response packet to the NMS according to the information of the statistics group in the request packet. The NMS sends a request packet to the RMON agent every sampling interval. The RMON agent returns the value of the current performance counting register through the response packet. The maintenance engineer clicks Stop. The NMS stops sending the corresponding request packet to the RMON agent.
NOTE
4.
5. 6.
If the maintenance engineer selects Start, the RMON agent does not reset the performance counting register.
Alarm Group
The processing flow is as follows: 1. 2. 3. 4. 5. The maintenance engineer clicks Apply. The NMS sends the corresponding request packet to the RMON agent. The RMON agent embedded in the Ethernet board monitors the corresponding alarm object according to the information of the alarm group in the request packet. When the alarm object crosses the preset threshold in the corresponding direction, the RMON agent sends the corresponding trap packet to the NMS. The NMS generates the corresponding RMON alarm according to the information in the packet.
History Control Group

The processing flow is as follows: 1. 2. 3. The maintenance engineer clicks Apply. The NMS sends the corresponding request packet to the RMON agent. The RMON agent embedded in the Ethernet board periodically counts the performance value of the monitored object and stores the performance value in the corresponding history performance register according to the information of the history control group in the request packet.
29-12
History Group
The processing flow is as follows: 1. 2. 3. A maintenance engineer clicks Query. The NMS sends the corresponding request packet to the RMON agent. The RMON agent embedded in the Ethernet board queries the history performance registers that meet the requirements and returns the performance values in the registers to the NMS through the response packet according to the information of the history group in the request packet.

Follow certain guidelines when you plan RMON.
Planning Guidelines of Management Groups

l l l When you need to monitor the current performance of a port in real time, select the statistics group. When you need to monitor certain performance items of a port in a long term, select the alarm group. 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.
Planning Guidelines of Statistics Items

l When you need to analyze the exceptions occurred on a port, select the following statistical items: fragments, undersized packets received, FCS errors, pause frames received, pause frames transmitted. When you need to analyze the traffic on a port, select the following statistical items: bytes received and bytes transmitted. When you need to analyze the information on packet transmitting and packet receiving on a port, select the following statistical items: packets received and packets transmitted. When you need to analyze the 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, and broadcast packets transmitted.
l l l

When applying RMON, you need to perform different operations as required.
Issue 05 (2010-10-30)
29-13
Table 29-5 Configuration procedure of RMON Step 1 Operation A.16.1 Browsing the Performance Data in the Statistics Group of an Ethernet Port Description Required if the current performance events of the Ethernet port need to be browsed. l Select the Ethernet port and performance events for the browsing operation. l Set Sampling Interval as required. 2 A.16.4 Browsing the Performance Data in the History Group of an Ethernet Port Required if the history performance events of the Ethernet port need to be browsed. l Select the Ethernet port, performance events, and the start/end time of browsing period for the browsing operation. l Set History Table Type as required. 3 A.16.3 Configuring a History Control Group Optional. If you need to browse the history performance events or history alarm group in a self-defined period, set the history control group with a self-defined period. Required if you need to define certain alarms to be monitored. Set the parameters as required.
A.16.2 Configuring an Alarm Group for an Ethernet Port

This section uses an example to describe how to plan and configure RMON according to network conditions. 29.9.1 Networking Diagram This section describes the networking information about the NEs. 29.9.2 Fault Analysis This section describes the basic principle of using RMON to troubleshoot Ethernet services.
29.9.3 Troubleshooting Flow This section describes the process of troubleshooting a faulty service.

This section describes the networking information about the NEs. As shown in Figure 29-1, the point-to-point private line service between NE2 and the BSC is configured on NE1. In the service transmission process, the BSC receives less traffic than expected. If the regular alarm analysis fails to locate the problem, you need to use the RMON function to locate the fault of the data service. Figure 29-1 Networking diagram
5-IFH2-1(to NE1) 4-EMS6-1(to BTS1) 4-EMS6-2(to BTS2)
Tranparent transmission E-LINE service
5-IFH2-1(to NE2) 4-EMS6-1(to BSC)
BTS1 BTS2 NE2

Ethernet link
NE1
Radio link
BSC
29.9.2 Fault Analysis

This section describes the basic principle of using RMON to troubleshoot Ethernet services. 1. Determine the port where the fault occurs by checking the traffic on Ethernet ports and Hybrid IF boards along the trail of a faulty Ethernet service. l If the transmitted traffic of the transmit port is roughly equal to the received traffic of the receive port, it indicates the service is normal. l If the transmit traffic of the transmit port is much different from the receive traffic of the receive port, it indicates the service is abnormal. 2. Check the statistics of threshold-exceeding performance events at an abnormal port. Then, determine the causes of faults. For details, see "RMON Alarms and Performance Events" in Alarms and Performance Events Reference. See "RMON Alarms and Performance Events" in the Alarms and Performance Events Reference.
3.
29.9.3 Troubleshooting Flow

This section describes the process of troubleshooting a faulty service.
Procedure
Step 1 Obtain the statistics of the received and transmitted traffic on each Ethernet port and IF board within a period of time. For details, see A.16.4 Browsing the Performance Data in the History Group of an Ethernet Port.
In this example, the statistics is as follows: l The transmitted traffic of BTS1 is roughly equal to the received traffic on 4-EMS6-1 of NE2. The transmitted traffic of BTS2 is roughly equal to the received traffic on 4-EMS6-2 of NE2. l The sum of received traffic on 4-EMS6-1 and 4-EMS6-2 of NE2 is roughly equal to the received traffic on 5-IFH2-2 of NE2. l The transmitted traffic on 5-IFH2-2 of NE2 is roughly equal to the received traffic on 5IFH2-2 of NE1. l The transmitted traffic on 5-IFH2-2 of NE1 is roughly equal to the received traffic on 4EMS6-1 of NE1. l The received traffic of the BSC is quite different from the transmitted traffic of 4-EMS6-1. Therefore, the link between NE1 and the BSC is faulty. Step 2 Browse the performance events reported by the BSC and NE1. A large number of performance events are reported to indicate that RMON module performance value crosses the upper threshold. These performance events are caused by the RMON alarm entry indicating that the number of fragment packets crosses the threshold. According to the Alarms and Performance Events Reference, the causes of the fault are as follows: l The working modes of the ports at both ends are inconsistent. l The hardware on the local end is faulty. Step 3 See the Alarms And Performance Events Reference to rectify the fault. 1. Query the working modes of 4-EMS6-1 on NE1 and the Ethernet port on the BSC. For details, see A.18 Configuring Ethernet Ports in the Configuration Guide. The query results show that the Ethernet ports on NE1 and the BSC are working in different modes. Change the working modes to the same. For details, see A.18 Configuring Ethernet Ports in the Configuration Guide.
2.
----End

This section provides the hyperlinks of the operation tasks associated with RMON.
Related Tasks
A.8.1 Configuring Clock Sources A.8.6 Querying the Clock Synchronization Status A.16.1 Browsing the Performance Data in the Statistics Group of an Ethernet Port A.16.2 Configuring an Alarm Group for an Ethernet Port A.16.3 Configuring a History Control Group A.16.4 Browsing the Performance Data in the History Group of an Ethernet Port
29-16
Issue 05 (2010-10-30)

When the entries in an RMON alarm group exceed the pre-set thresholds, a performance event is reported, indicating that the RMON module performance value crosses the lower threshold or upper threshold.
Relevant Alarms
None.
Relevant Events
l RMON module performance value lower than the lower threshold This performance event indicates that the current RMON performance statistics is lower than the lower threshold. l RMON module performance value higher than the upper threshold This performance event indicates that the current RMON performance statistics is higher than the higher threshold.
29.12 FAQs
This section describes the answers to the questions that are frequently asked when the RMON feature is used. Q: How does one use the statistical items obtained by using the RMON function? A: The statistical items obtained by using the RMON function are primarily used in the following scenarios: l Analyzing the exceptions that occur on a port Focus on the following statistical items that indicate exceptions: Fragments Generally, a mismatch between working modes causes the occurrence of fragments. Fragments occur most commonly when the working mode at one end is set to autonegotiation but the working mode at the other end is set to full-duplex. Undersized packets received When undersized packets occur, first check whether the port modes match each other, then check the quality of network cables, and finally check whether the hardware of the Ethernet board is faulty by using another Ethernet port or replacing the Ethernet board. Oversized packets received Generally, the setting of the maximum frame length to a very small value causes the occurrence of oversized packets. FCS errored frames When the packets with FCS errors occur, first check whether the port modes match each other, then check the quality of the network cable, and finally check whether the hardware of the Ethernet board is faulty by using another Ethernet port or replacing the Ethernet board.
Pause frames received and pause frames transmitted When pause frames occur, first check whether the flow control function is correctly set, and then adjust the service traffic or perform traffic shaping to prevent the traffic on ports from being controlled. l Analyzing the information on packet transmitting and packet receiving on each port of a service For example, when two ports share one VCTRUNK to provide a private line service, you can count the packets received on both ports and compare the count with the number of transmitted packets to determine whether packet loss occurs. l Analyzing the traffic on a port For example, in the case of a transparently transmitted service from a port to a VCTRUNK, you can count the received and transmitted bytes on the port, and compare the count with the bandwidth of the VCTRUNK. In this manner, you can determine whether the VCTRUNK is bound with an appropriate number of timeslots. l Analyzing the types of packets For example, in the case of a port mounted on a bridge, you can count the received packets and the received broadcast packets. Then, calculate the proportion of the received broadcast packets to the received packets. In this manner, you can determine whether a broadcast storm occurs on the peer equipment. Q: What are the advantages of RMON, compared with the traditional performance data management method? A: RMON has the following advantages: l l All statistics data is stored in the agent and out-of-service operations on the NMS are supported. RMON can count the port statistics, set and query the control information, and analyze the performance of the connected Ethernet segments. In addition, RMON can save the history performance data and the NMS can query the statistics of a board only when required. In this manner, less data traffic is required for network management. RMON is flexible in alarms and performance events. RMON notifies the NMS of the network performance change through alarms and performance events, which facilitates network management. Multiple management stations are supported.
29-18
Issue 05 (2010-10-30)
A Task Collection
Task Collection
This chapter describes various operation tasks associated with corresponding features. A.1 Managing NEs Before you configure NEs, ensure that the NEs can be managed on the NMS. A.2 Configuring Performance Monitoring Status of NEs By default, the performance monitoring of NEs is enabled. You can disable or enable this function manually and set the period of the performance monitoring of NEs manually. A.3 Managing Communication To manage NEs on the NMS, ensure that DCN communication is normal. A.4 Configuring Service Access of NEs You can ensure the security of a network by setting service access of the NEs on the network. A.5 Managing Radio Links Before you configure the radio link between two radio sites, you need to configure the corresponding information about the radio link. A.6 Managing MSP The OptiX RTN 620 supports ring MSP and linear MSP. A.7 Managing TDM Services TDM services include SDH services and PDH services. A.8 Managing Clocks To ensure clock synchronization between transmission nodes on a transport network, you need to manage the NE clocks. A.9 Managing ERPS Protection This chapter describes how to configure ERPS to provide protection for an Ethernet ring network. A.10 Managing the STP If a loop exists in the network topology of Ethernet services, you need to enable the Spanning Tree Protocol (STP) or Rapid Spanning Tree Protocol (RSTP). A.11 Managing the IGMP Snooping If a multicast router exists on a network, the bridge can enable the IGMP Snooping protocol to implement the multicast function together with the router. A.12 Managing LAGs
Issue 05 (2010-10-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. A-1
A Task Collection
Link aggregation enables one or multiple links that are connected to the same equipment to be aggregated into a LAG. The aggregated links are considered as a single logical link at the MAC layer. In this manner, bandwidth and availability of radio links are improved. A.13 Managing the QoS By managing the QoS, you can provide differentiated services for different service types. A.14 Using the IEEE 802.1ag OAM By using the IEEE 802.1ag OAM, you can maintain the Ethernet service in an end-to-end manner. A.15 Using the IEEE 802.3ah OAM With the IEEE 802.3ah OAM, you can maintain point-to-point Ethernet links. A.16 Using RMON Remote monitoring (RMON) is mainly used to monitor the data traffic on a network segment or on the entire network. Currently, it is one of the widely used network management standards. A.17 Configuring LPT After enabling the LPT function for an Ethernet service, you need to configure the LPT port and the relevant information. A.18 Configuring Ethernet Ports OptiX RTN 620The supported Ethernet ports include the external FE/GE ports on Ethernet boards, internal VCTRUNK ports, and IFUP ports on the IFH2 board. A.19 Configuring Ethernet Services Ethernet services are classified into EPL services, EVPL services, EPLAN services, and EPVLAN services. A.20 Managing the MAC Address Table The MAC address table is the core of the EPLAN or EVPLAN service. The OptiX RTN 620 provides various functions for managing the MAC address table. A.21 Testing Ethernet Services By testing Ethernet services, you can check whether Ethernet services are available on radio links.
A-2
Issue 05 (2010-10-30)
A Task Collection
A.1 Managing NEs

Before you configure NEs, ensure that the NEs can be managed on the NMS. A.1.1 Creating NEs by Using the Search Method The Web LCT can find all NEs that communicate with a specific gateway NE according to the IP address of the gateway NE or the IP address range of the gateway NE. In addition, the Web LCT can create the NEs in batches. Compared with the method of manually creating NEs, this method is quicker and more reliable. A.1.2 Creating NEs by Using the Manual Method Using the manual method, you can only create NEs one by one. The manual method, unlike the search method, does not enable creation of NEs in batches. A.1.3 Logging In to an NE After an NE is created, you need to log in to the NE before managing the NE. A.1.4 Configuring Logical Boards If the logical board corresponding to a physical board is not added in the slot layout, add the logical board in the slot layout. If the physical board is inconsistent with the logical board in the slot layout, delete the inconsistent logical board and add the correct logical board. A.1.5 Changing NE IDs This section describes how to change NE IDs according to the engineering plan to ensure that each NE ID is unique. The modification does not affect services. A.1.6 Changing NE Names To accurately identify an NE in the Main Topology, you need to name the NE according to the geographical location or the equipment connected to the NE. A.1.7 Synchronizing NE Time By setting the NE time to be synchronous with the time on the NMS, you can record the exact time when alarms and abnormal events occur. A.1.8 Localizing NE Time When the daylight saving time (DST) is used in the area where the NE is located, you need to localize the NE time to synchronize the NE with the local time.
A.1.1 Creating NEs by Using the Search Method

The Web LCT can find all NEs that communicate with a specific gateway NE according to the IP address of the gateway NE or the IP address range of the gateway NE. In addition, the Web LCT can create the NEs in batches. Compared with the method of manually creating NEs, this method is quicker and more reliable.
Prerequisite
The NEs must gain the access to the computer where the Web LCT software is installed.
Tools, Equipment, and Materials

Web LCT
A Task Collection
Context
You can create an NE by searching for the NE and then adding the NE on the Web LCT. In addition, you can create an NE by adding the NE manually. Generally, the NE ID is not known during initial NE configuration. Therefore, the searching method is used to create an NE in most cases.
Procedure
Step 1 In NE List, click NE Search. Then, the Search NE dialog box is displayed. Step 2 Optional: Set Domain to 129.9.255.255, and click Search.
NOTE
During initial configuration, Domain is 129.9.255.255 by default. After the gateway NE IP address of the searched NE is changed, you need to change the value of Domain.
Step 3 After the Web LCT finds the NEs to be managed, click End Search.
Step 4 Select the NE that needs to be added and click Add NE. A dialog box is displayed, indicating that the NE is added successfully. Step 5 Click OK. A new NE is already added to the NE list.
Step 6 Click Cancel. ----End

A-4 Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 05 (2010-10-30)
A Task Collection
A.1.2 Creating NEs by Using the Manual Method

Using the manual method, you can only create NEs one by one. The manual method, unlike the search method, does not enable creation of NEs in batches.
Prerequisite
l l The NEs must gain the access to the computer where the Web LCT software is installed. The NE IDs must be known.

Web LCT
Context
You can create an NE by adding the NE manually. In addition, you can create an NE by searching for the NE. If the NE ID is not known during initial NE configuration, you can create the NE by searching for the NE and adding the NE on the Web LCT.
Procedure
Step 1 In NE List, click Add NE. Then, select Europe. Then, the Add NE dialog box is displayed. Step 2 In the Add NE dialog box, set the NE parameters.
Step 3 Click OK. A new NE is already added to the NE list.
----End
Issue 05 (2010-10-30)
A-5
A Task Collection
Parameters
Parameter NE ID Value Range 1 to 49135 Default Value Description l This parameter indicates the basic NE ID. When there is no extended ID, the basic NE IDs must be unique on the networks that are managed by the same NMS. l Set this parameter according to the DCN planning information. Extended ID 1 to 254 9 l Do not change the extended ID when the number of actual NEs does not exceed the range permitted by the basic NE ID. l It is recommended that this parameter takes the default value. Gateway Type IP Gateway Serial Port IP Address This parameter is set to 129.9.0.x when the NE is delivered from the factory. "x" indicates the basic NE ID that is set when the NE is delivered from the factory. l 1400 (when Gateway Type is set to IP Gateway) l COM1 (when Gateway Type is set to Serial Port) 1200bps This parameter specifies the communication rate between the NE to be created and the corresponding gateway NE. This parameter is displayed only when Gateway Type is set to Serial Port. IP Gateway This parameter specifies the type of the gateway that is used for the communication between the Web LCT and the NEs. This parameter specifies the IP address of the gateway NE to which the NE to be created belongs. This parameter is displayed only when Gateway Type is set to IP Gateway.
Port
l 1400 (when Gateway Type is set to IP Gateway) l COM1-COM32 (when Gateway Type is set to Serial Port)
This parameter specifies the port corresponding to the gateway NE to which the NE to be created belongs.
Baud Rate
1200bps 2400bps 4800bps 9600bps 19200bps 38400bps 57600bps 115200bps
A-6
Issue 05 (2010-10-30)
A Task Collection
Parameter User Name
Value Range -
Default Value lct
Description This parameter specifies the name of the user. This parameter can take the default value in the case of initial login. The default password of user lct is password.
Password
A.1.3 Logging In to an NE
After an NE is created, you need to log in to the NE before managing the NE.
Prerequisite
l l The NE user must have the authority of Operation Level or higher. The NEs to be managed must be created in the NE List.

Web LCT
Procedure
Step 1 In the NE List, select the target NE and click NE Login.
TIP
You can select more than one NE at one time.
The NE Login dialog box is displayed. Step 2 Enter User Name and Password. Then, click OK.
l The default User Name is lct.

A Task Collection
l The default Password of user lct is password. Login Status of the NE in the NE List changes to Logged In. Alarm Status of the NE is changed from Unknown to the current alarm status of the NE. Step 3 Click NE Explorer. The NE Explorer is displayed.
TIP
To quickly start the NE Explorer, double-click the NE to be managed in the NE list.
TIP
l Check the legend to learn the specific meanings of different colors and symbols in the slot layout diagram. l Click to fold/unfold the legend.
----End
Example
Table A-1 Parameters Parameter User Name Value Range Default Value lct Description This parameter specifies the name of the user. This parameter can take the default value in the case of initial login. The default password of user lct is password. When this parameter is selected, enter User Name and Password to log in to all the selected NEs.
Password Use same user name and password to login
Selected Deselected
Deselected
A-8
Issue 05 (2010-10-30)
A Task Collection
Parameter Use the user name and password that was used last time
Value Range Selected Deselected
Default Value Deselected
Description When this parameter is selected, enter User Name and Password that were used for the latest login to log in to the NE.
A.1.4 Configuring Logical Boards

If the logical board corresponding to a physical board is not added in the slot layout, add the logical board in the slot layout. If the physical board is inconsistent with the logical board in the slot layout, delete the inconsistent logical board and add the correct logical board.
Prerequisite
l l The NE user must have the authority of Operation Level or higher. All the boards must be installed correctly.

Web LCT
Context
The NE software manages a physical board by considering the physical board as one or more logical boards. In the OptiX RTN 620: l l An SCC physical board is considered as a logical SCC and a logical EOW board. The slot number of the logical SCC board is 2, and the slot number of the logical EOW is 21. Other physical boards of the IDU are considered as the logical boards with the same names. The slot numbers of the logical boards are the same as the slot numbers of the corresponding physical boards.
An ODU is considered as an ODU logical board. The ODU logical slot number is 10 plus the slot number of the IF board connected to the ODU. The STAT indicator on the physical IDU board will be lit only if the logical IDU board matches with the physical IDU board.
Procedure
Step 1 Click the Slot Layout tab and click Add Logical Boards. Based on the slot layout, the NE automatically configures the logical boards that are required but still not be configured for certain physical boards. Step 2 Optional: Right-click the slots in which boards are to be added, and select Add xxx. "xxx" refers to the boards to be added.
NOTE
Add the PXC board before you add the IF boards and service boards. Manually adding the logical boards applies to the cases when relevant data need to be configured before the physical boards are installed.
Issue 05 (2010-10-30)
A-9
A Task Collection
Step 3 Optional: Right-click the slots in which boards are to be deleted, and select Delete. Delete the services, clock, orderwire and protections on the boards before you delete the boards. ----End
A.1.5 Changing NE IDs

This section describes how to change NE IDs according to the engineering plan to ensure that each NE ID is unique. The modification does not affect services.
Prerequisite
The NE user must have the authority of Operation Level or higher.

Web LCT
Procedure
Step 1 In the NE Explorer, select the NE from the Object Tree and choose Configuration > NE Attribute from the Function Tree. Step 2 Click Modify NE ID. The Modify NE ID dialog box is displayed. Step 3 Set a new ID for the NE.
Step 4 Click OK. Then, a dialog box is displayed. Click OK. ----End
Example
Table A-2 Parameters Parameter New ID Value Range 1 to 49135 Default Value Description l The new ID refers to the basic ID. When the extended ID is not used, the basic ID of an NE within any network that is managed by an NMS must be unique. l Set this parameter according to the DCN planning information.
A Task Collection
Parameter New Extended ID
Value Range 1 to 254
Default Value 9
Description l When the number of existing NEs does not exceed the range represented by the basic ID, do not modify the extended ID. l It is recommended that this parameter takes the default value.
NOTE
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.
Follow-up Procedure
In the case of the OptiX RTN 620, you only need to close the NE Explorer and then re-log in to the NE, if the IP address does not change accordingly after the NE ID changes; You need to delete the original NE, create an NE, and then log in to the NE, if the IP address of the NE changes after the NE ID changes. Before the IP address of the NE is changed manually, the IP address changes accordingly if the NE ID changes. After the IP address of the NE is changed manually, the IP address does not change accordingly if the NE ID changes.
A.1.6 Changing NE Names

To accurately identify an NE in the Main Topology, you need to name the NE according to the geographical location or the equipment connected to the NE.
Prerequisite

Web LCT
Procedure
Step 1 In the NE Explorer, select the NE from the Object Tree and then choose Configuration > NE Attribute from the Function Tree. Step 2 Enter the name of the NE in Name. Step 3 Click Apply. ----End
A.1.7 Synchronizing NE Time

By setting the NE time to be synchronous with the time on the NMS, you can record the exact time when alarms and abnormal events occur.
A Task Collection
Prerequisite
l l The NE user must have the authority of Operation Level or higher. Ensure that the time zone and time on the NM computer are correctly set.

Web LCT
Precautions
In the commissioning phase, you only need to synchronize the NE time with the time of the Web LCT server to ensure that the time of the alarms and abnormal events reported on the NE is correct. After all the NEs are placed under the NMS, re-synchronize the NE time according to the synchronization strategy of the network time.
Procedure
Step 1 In the NE Explorer, select the NE from the Object Tree and then choose Configuration > NE Time Synchronization from the Function Tree. Step 2 Set the synchronous mode. If ... Then ...
You set Synchronous Mode to NULL or NTP Set the relevant parameters, and then click Apply. You set Synchronous Mode to NM Set the relevant parameters, and then click Apply to perform step Step 6.
You set Synchronous Mode to Standard NTP Set the related parameters, and then click Apply to perform steps Step 3 to Step 5.
NOTE
If you only need to synchronize the NE time and need not change the type of synchronization or parameters, select the synchronization option corresponding to the NE, right-click, and choose Synchronize with NM Time.
Step 3 Configure the upper-layer standard NTP server of the NE. 1. 2. Click the Standard NTP Server tab. In the Standard NTP Server tab page, click Add. After setting the parameters of the standard NTP server, click OK.
NOTE
l If the NE is a GNE, set the external NTP server as the standard NTP server. l If the NE is a non-GNE, set the GNE as the standard NTP server.
Step 4 Optional: Configure the NTP access control rights. 1. 2. Click the Access Control Rights tab. In the Access Control Rights tab page, click Add. After setting the parameters of the access control rights, click OK.
Step 5 Optional: Configure the NTP key.

A Task Collection
1. 2.
Click the Standard NTP Key Management tab. In the Standard NTP Key Management tab page, click Add. After setting the parameters of the NTP key management, click OK.
NOTE
l Configuring the NTP key is required only when NTP authentication is enabled. l To pass the NTP authentication, the NTP authentication must be enabled on both the client and the server, and Key, Password, and Encryption Type of the client must be consistent with those of the server.
Step 6 Optional: Set Synchronization Starting Time and click Apply. ----End
Example
Table A-3 Parameters Parameter Synchronous Mode Value Range NTP Standard NTP NM NULL Default Value NULL Description l When this parameter is set to NM, the NE is synchronized with the NMS server. l When this parameter is set to NTP, the NE is synchronized with the network time protocol (NTP) server. l When this parameter is set to Standard NTP, the NE is synchronized with the NTP server through the standard NTP protocol. Standard NTP Authentication Enable Disable Disable l This parameter is valid only when Synchronous Mode is set to Standard NTP. l When this parameter is set to Enable, the NTP authentication is required. Therefore, the key used for the NTP authentication should be configured.
Issue 05 (2010-10-30)
A-13
A Task Collection
Parameter Server Enabled
Value Range ECC Server Disable
Default Value ECC Server
Description l This parameter is valid only when Synchronous Mode is set to NTP. l This parameter indicates whether the NE functions as the ECC server and provides NTP service for the ECC communication between this NE and other NEs. l If this NE can communicate with the NTP server over IP but the other NEs that communicate with this NE over ECC cannot communicate with the NTP server over IP, set this parameter to ECC Server. Otherwise, set this parameter to Disable.
Client Enabled
l ECC Client, IP Client, Disable (when Server Enabled is set to ECC Server) l ECC Client, IP Client (when Server Enabled is set to Disable)
ECC Client
l This parameter is valid only when Synchronous Mode is set to NTP. l When this parameter is set to ECC Client, the NE is synchronized with the ECC server of the NTP based on ECC communication. l When this parameter is set to IP Client, the NE is synchronized with the NTP server based on IP communication. l When the NE can implement communication directly through IP or the NTP server, set this parameter to IP Client. When the NE can communicate with the ECC server of the NTP over ECC, set this parameter to ECC Client. l When the NE functions as the ECC server and is not synchronized with an NTP server, set this parameter to Disable.
Synchronous Server
l This parameter is valid only when Synchronous Mode is set to NTP. l To modify this parameter, right-click this parameter and then select the option from the shortcut menu according to actual requirements. l When Client Enabled is set to ECC Client, this parameter indicates the NE ID of the ECC server. l When Client Enabled is set to IP Client, this parameter indicates the IP address of the higher level NTP server.
A-14
Issue 05 (2010-10-30)
A Task Collection
Parameter Polling Period (min)
Default Value 120
Description l This parameter is valid only when Synchronous Mode is set to NTP. l This parameter indicates the interval between the requests sent by the NTP client. l Set this parameter according to the requirements of the NTP server.
The Number of Sampling
1 to 8
l This parameter is valid only when Synchronous Mode is set to NTP. l This parameter indicates the number of NTP packets that are sent for obtaining information required for synchronizing the time at each request. l Set this parameter according to the requirements of the NTP server.
Table A-4 Parameters of the standard NTP server Parameter Standard NTP Server Flag Value Range NE ID NE IP Default Value NE ID Description l When ECC is used to communicate with the standard NTP server, set the parameter to NE ID. l When the IP protocol is used to communicate with the standard NTP server, set the parameter to NE IP. Standard NTP Server Standard NTP Server Key Standard NTP Version Used First 0 to 1024 2 3 Yes No No 1 2 This parameter specifies the ID or IP address of the standard NTP server. This parameter specifies the NTP protocol key. 0 indicates that no key is required. Set this parameter according to the settings for the standard NTP protocol version used at the peer end. This parameter specifies whether to select a server preferentially when multiple NTP servers are available.
Issue 05 (2010-10-30)
A-15
A Task Collection
Table A-5 Parameters of the access control rights Parameter ACL No. NE Flag Value Range 1 to 250 NE ID NE IP Default Value 1 NE ID Description This parameter specifies the number of the ACL. l When ECC is used to communicate with the standard NTP server, set the parameter to NE ID. l When the IP protocol is used to communicate with the standard NTP server, set the parameter to NE IP. NE Whether to Receive Data Packet Right Level Yes No query synchronize server peer query Yes This parameter specifies the ID or IP address of an NE. This parameter specifies whether to receive packets from an NE. The equipment provides four levels of access control. When an NTP access request is received on the local equipment, the request is matched with the levels from the minimum access limit to the maximum access limit, and the first matched level prevails. The matching order is as follows: l Peer (minimum access limit): The time request and the control query can be carried out for the NTP service of the local equipment. The local clock can also be synchronized with the remote server. l Server: The time request and the control query can be carried out for the NTP service of the local equipment, but the local clock is not synchronized to the remote server. l Synchronization: The time query is allowed for only the NTP service of the local equipment. l Query (maximum access limit): The control query can be carried out only for the NTP service of the local equipment.
Table A-6 Parameters of the NTP key management Parameter Encryption Value Range MD5 Default Value MD5 Description This parameter specifies the MD5 key algorithm.
A-16
Issue 05 (2010-10-30)
A Task Collection
Parameter Key Password Trusted
Value Range 1 to 1024 Yes No
Default Value 1 No
Description This parameter specifies the number of the key. This parameter specifies the password of the key. If you set this parameter to No, the key is verified but cannot be trusted during the clock synchronization. Therefore, the clock of the NE cannot be synchronized.
A.1.8 Localizing NE Time

When the daylight saving time (DST) is used in the area where the NE is located, you need to localize the NE time to synchronize the NE with the local time.
Prerequisite

Web LCT
Procedure
Step 1 In the NE Explorer, select the NE from the Object Tree and then choose Configuration > NE Time Localization Management from the Function Tree. Step 2 Set the correct time zone and daylight saving time of the NE depending on the location of the NE.
Issue 05 (2010-10-30)
A-17
A Task Collection
Step 3 Click Apply. ----End
Example
Table A-7 Parameters Parameter Time Zone Value Range Default Value Description l Changing the time zone results in transition of the current NE time. l Set this parameter according to the location of the NE. DST Enabled Disabled Disabled l The DST-related parameters are valid only if this parameter is set to Enabled. l Set these parameters depending on whether the location of the NE adopts the DST.
A Task Collection
Parameter DST Rule
Value Range MM-WW-DD MM-DD
Default Value MM-WW-DD
Description l When the DST Rule is set to MM-WWDD, Start Time and Stop Time of the DST is set in month-week-day format. l When the DST Rule is set to MM-DD, Start Time and Stop Time of the DST is set in month-day format. l Set this parameter according to the DST rule in the location of the NE.
DST Offset Start Time Stop Time
l Start Time is automatically added with the DST Offset time according to the current NE time. l Stop Time is automatically decreased by the DST Offset time according to the current NE time. l Set the three parameters according to the DST rule in the location of the NE.
A.2 Configuring Performance Monitoring Status of NEs

By default, the performance monitoring of NEs is enabled. You can disable or enable this function manually and set the period of the performance monitoring of NEs manually.
Prerequisite

Web LCT
Procedure
Step 1 In the NE Explorer, select the NE and then choose Performance > NE Performance Monitor Time from the Function Tree. Step 2 Set the parameters of NE performance monitoring. 1. 2. 3. Select 15-Minute or 24-Hour. Select Enable or Disable in Set 15-Minute Monitoring or Set 24-Hour Monitoring. Set the start time and end time of the performance monitoring of NEs.
Issue 05 (2010-10-30)
A-19
A Task Collection
NOTE
l Set 15-Minute Monitoring and Set 24-Hour Monitoring are generally set to Enable. l You can specify the start time of the performance monitoring function, only after selecting Enable in the Set 15-Minute Monitoring or Set 24-Hour Monitoring area. l You can specify the end time of the performance monitoring function, only after selecting Enable and then selecting To in the Set 15-Minute Monitoring or Set 24-Hour Monitoring area.
A.3 Managing Communication

To manage NEs on the NMS, ensure that DCN communication is normal. A.3.1 Setting NE Communication Parameters The communication parameters of an NE include the IP address and extended ID of the NE, the gateway IP address, NSAP address, and the subnet mask. A.3.2 Configuring DCCs To meet the requirements for managing a complex network, you need to set the channel type, protocol type, or enable status of the DCCs according to the service planning information. A.3.3 Configuring the Extended ECC When there is no DCC between two or more NEs, connect the Ethernet NM ports or NE cascading ports on the system control unit of the NEs to realize communication through the extended ECC. A.3.4 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
A Task Collection
together with other equipment to form a network and can also transparently transmit the NM messages between ECC subnets. A.3.5 Creating Static IP Routes When dynamic routes fail to meet the planning requirements, you need to create the corresponding static IP routes manually. A.3.6 Setting Parameters of the OSPF Protocol When the IP over DCC solution is used to realize the interconnection between the OptiX equipment and the third-party equipment, you need to set the parameters of the OSPF protocol according to the requirements of the third-party equipment, thus implementing the route protocol interworking between the OptiX equipment and the third-party equipment. A.3.7 Enabling the ARP Proxy The proxy ARP enables the NEs in the same network segment but different domains to communicate with each other. A.3.8 Configuring the CLNS Role When the CLNS role of an NE is L1, the NE is involved in the routes in the area. When the CLNS role of an NE is L2, the NE is involved in the routes between areas. By default, the CLNS role of the OptiX equipment is L1. A.3.9 Querying OSI Tunnel The OSI tunnel function involves the creation of a virtual LAPD channel between the NEs on the IP network. In this manner, the NM message encapsulated in compliance with the OSI protocol can be transparently transmitted. A.3.10 Querying ECC Routes By querying ECC routes, you can check whether the correct HWECC solution is configured and whether the communication between NEs is normal. A.3.11 Querying IP Routes By querying IP routes, you can check whether the IP over DCC solution is configured correctly and whether the communication between NEs is normal. A.3.12 Querying OSI Routes By querying OSI routes, you can check whether the OSI over DCC solution is configured correctly and whether the communication between NEs is normal.
A.3.1 Setting NE Communication Parameters

The communication parameters of an NE include the IP address and extended ID of the NE, the gateway IP address, NSAP address, and the subnet mask.
Prerequisite

Web LCT
Procedure
Step 1 In the NE Explorer, select the NE from the Object Tree and then choose Communication > Communication Parameters from the Function Tree.
A Task Collection
Step 2 Set the communication parameters of the NE.
Example
Table A-8 Parameters Parameter IP Value Range Default Value Before delivery, the IP address of the NE is set to 129.9.0.x. The letter x indicates the basic ID. 0.0.0.0 255.255.0.0 Description In the HWECC solution, an IP address is set according to the following rules: l The IP address, subnet mask, and default gateway of the gateway NE must meet the planning requirements of the external DCN. l If an NE uses the extended ECC, the IP address must be in the same network segment. l The IP address of other NEs must be set according to the NE ID. In this example, the IP address of an NE must be set in the format of 0x81000000+ID. That is, if the ID is 0x090001, the IP address must be set to 129.9.0.1.
Gateway IP Subnet Mask
A-22
Issue 05 (2010-10-30)
A Task Collection
Parameter Extended ID
Default Value 9
Description l Do not change the extended ID when the number of actual NEs does not exceed the range permitted by the basic NE ID. l It is recommended that this parameter takes the default value.
NSAP Address
This parameter is valid only when the OSI over DCC solution is applied. This parameter is used to set only the area ID of an NSAP address. The other parts of the NSAP address are automatically generated by the NE. The communication between the client and the server is encrypted if this parameter is set to Security SSL.
Connection Mode
Common Security SSL
Common
A.3.2 Configuring DCCs

To meet the requirements for managing a complex network, you need to set the channel type, protocol type, or enable status of the DCCs according to the service planning information.
Prerequisite

Web LCT
Precautions
The OptiX RTN 620 simultaneously supports 12 channels comprising byte D1, 12 channels comprising bytes D1 to D3, 6 channels comprising bytes D4 to D12, and 2 channels comprising bytes D1 to D12. If the DCC communication configuration already exceeds the restriction, close or adjust the DCCs of certain interfaces, depending on the actual situation.
Procedure
Step 1 In the NE Explorer, select the NE and then choose Communication > DCC Management from the Function Tree. Click the DCC Rate Configuration tab. Step 2 Optional: Modify the channel type or protocol type of an existing DCC. 1. 2. 3.
Issue 05 (2010-10-30)
Select the DCC to be modified and click Delete. Click Create. Then, the Create dialog box is displayed. Set the DCCs.
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. A-23
A Task Collection
4. 1. 2.
Click OK. Double-click the cell in the Enable Status column to which the DCC corresponds. Set the required state in the drop-down box. Click Apply.
Step 3 Optional: Modify the enabled status of a DCC.
----End
Example
Table A-9 Parameters Parameter Port Value Range Line interface External clock interface Enabled/Disabled Enabled Disabled Enabled (in the case of line interfaces) Disabled (in the case of the external clock interface) Default Value Description This parameter specifies the port of the DCCs.
It is recommended that you use the default value except in the following cases: l Set Enabled/Disabled of the interface that is connected to another ECC subnet to Disabled. l Set Enabled/Disabled of the interface that is connected to a third-party network but does not transmit NM messages to Disabled. l When the DCC transparent transmission through the external clock interface solution is applied, set Enabled/ Disabled of the used external clock interface to Enabled.
A-24
Issue 05 (2010-10-30)
A Task Collection
Parameter Channel Type
Value Range D1-D1 D1-D3 D4-D12 D1-D12
Default Value -
Description 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 interfaces 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 interfaces must not conflict with the channel type of the third-party network.
Protocol Type
HWECC TCP/IP OSI
HWECC
It is recommended that you use the default value except in the following cases: l When the IP over DCC solution is applied, set Protocol Type to TCP/IP. l When the OSI over DCC solution is applied, set Protocol Type to OSI.
LAPD Role
User Network
User
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.
A.3.3 Configuring the Extended ECC

When there is no DCC between two or more NEs, connect the Ethernet NM ports or NE cascading ports on the system control unit of the NEs to realize communication through the extended ECC.
Prerequisite

Web LCT
Procedure
Step 1 In the NE Explorer, select the NE and then choose Communication > ECC Management from the Function Tree. Step 2 Set ECC Extended Mode. Step 3 Optional: Set other parameters when the ECC extended mode is set to the specified mode.
A Task Collection
Step 4 Click Apply. A dialog box is displayed indicating that this operation will reset the communication between NEs. Step 5 Click OK. ----End
Example
Table A-10 Parameters Parameter ECC Extended Mode Port (on the server side) Value Range Auto mode Specified mode 1601 to 1699 1601 Default Value Specified mode Description It is recommended that this parameter takes the default value. l This parameter is valid only when ECC Extended Mode is set to Specified mode. l This parameter can be set only when the NE functions as the server of the extended ECC. In normal cases, the NE that is close to the U2000 functions as the server. l This parameter can be set to any value from 1601 to 1699. Opposite IP (on the client side) l This parameter is valid only when ECC Extended Mode is set to Specified mode. l This parameter can be set only when the NE functions as the client of the extended ECC. Except for the NE that functions as the server, all other NEs that use the extended ECC can function as the client.
Issue 05 (2010-10-30)
A-26
A Task Collection
Parameter Port (on the client side)
Default Value 1601
Description l Opposite IP and Port are respectively set to the IP address of the server NE and the specified port number.
A.3.4 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 NM messages between ECC subnets.
Prerequisite

Web LCT
Procedure
Step 1 In the NE Explorer, select the NE and then choose Communication > DCC Management from the Function Tree. Step 2 Click the DCC Transparent Transmission Management tab. Step 3 Click Create. Then, the Create DCC Transparent Transmission Byte dialog box is displayed. Step 4 Set the parameters of the DCC transparent transmission byte.
Issue 05 (2010-10-30)
A-27
A Task Collection
Step 5 Click OK. ----End
Example
Table A-11 Parameters Parameter Source Timeslot/ Porta Transparent Transmission of Overhead Byte at Source Portb Value Range Line interfaces D1 D2 D3 D4 D5 D6 D7 D8 D9 D10 D11 D12 E1 E2 F1 X1 X2 X3 X4 Sink Timeslot/ Porta Line interfaces Default Value D1 Description l Only one overhead byte can be selected at a time. l X1, X2, X3, and X4 represent the selfdefined 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).
A-28
Issue 05 (2010-10-30)
A Task Collection
Parameter Transparent Transmission of Overhead Byte at Sink Portb
Value Range D1 D2 D3 D4 D5 D6 D7 D8 D9 D10 D11 D12 E1 E2 F1 X1 X2 X3 X4
Default Value D1
Description 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.
NOTE
l a: The system establishes a bidirectional cross-connection between the overhead byte at the source port and the overhead byte at the sink port. Hence, you can set a port to be a source port or a sink port. l b: When an IF port works in the PDH mode, the number of overhead bytes that can be used is less than the number of overhead bytes that are listed.
A.3.5 Creating Static IP Routes

When dynamic routes fail to meet the planning requirements, you need to create the corresponding static IP routes manually.
Prerequisite

Web LCT
Issue 05 (2010-10-30)
A-29
A Task Collection
Procedure
Step 1 In the NE Explorer, select the NE, and choose Communication > IP Stack Protocol Management from the Function Tree. Click the IP Route Management tab. Step 2 Click New. Then, the Create an IP Route dialog box is displayed. Step 3 Set the parameters of the static IP route.
Example
Table A-12 Parameters Parameter Destination Address Mask Gateway IP Value Range Default Value Description Set this parameter to an IP address or an IP address range. This parameter specifies the subnet mask of the set Destination Address. This parameter specifies the IP address of the gateway to which the set Destination Address corresponds, that is, the next-hop address.
NOTE
The created static route has a lower priority than a dynamic route.
A.3.6 Setting Parameters of the OSPF Protocol

When the IP over DCC solution is used to realize the interconnection between the OptiX equipment and the third-party equipment, you need to set the parameters of the OSPF protocol according to the requirements of the third-party equipment, thus implementing the route protocol interworking between the OptiX equipment and the third-party equipment.
Prerequisite
A Task Collection

Web LCT
Procedure
Step 1 In the NE Explorer, select the NE from the Object Tree, and then choose Communication > IP Stack Protocol Management from the Function Tree. Step 2 Click the OSPF Parameter Settings tab. Step 3 Set the parameters of the OSPF protocol. Step 4 Click Apply. Then, close the dialog box that is displayed. ----End
A.3.7 Enabling the ARP Proxy

The proxy ARP enables the NEs in the same network segment but different domains to communicate with each other.
Prerequisite

Web LCT
Procedure
Step 1 In the NE Explorer, select the NE, and choose Communication > IP Stack Protocol Management from the Function Tree. Click the IP Route Management tab. Step 2 Click the Proxy ARP tab. Step 3 Set the enabled status of the proxy ARP. Step 4 Click Apply. ----End
A.3.8 Configuring the CLNS Role

When the CLNS role of an NE is L1, the NE is involved in the routes in the area. When the CLNS role of an NE is L2, the NE is involved in the routes between areas. By default, the CLNS role of the OptiX equipment is L1.
Prerequisite

Web LCT
A Task Collection
Procedure
Step 1 In the NE Explorer, select the NE from the Object Tree and then choose Communication > OSI Management from the Function Tree. Step 2 Click the Network Layer Parameters tab. Step 3 Set the CLNS role of the NE.
NOTE
When Configuration Role is set to L2, the NE has the functions of the L1 role and the L2 role.
Step 4 Click Apply. A dialog box is displayed, indicating that this operation will perform a warm reset on the SCC. Step 5 Click OK. ----End
Example
Table A-13 Parameters Parameter Configuration Role Value Range L2 L1 Default Value L1 Description l An NE whose Configuration Role is set to L1 cannot function as a neighbor of an NE in the other area. It uses a route in the local area only and access the other area by distributing the default route of the nearest L2 NE. l An NE whose Configuration Role is set to L2 can function as a neighbor of an NE in the other area and can use a route in the backbone area. The backbone area is a collection that is formed by consecutive L2 NEs. That is, the L2 NE of all the roles must be consecutive (connected to each other).
A.3.9 Querying OSI Tunnel

The OSI tunnel function involves the creation of a virtual LAPD channel between the NEs on the IP network. In this manner, the NM message encapsulated in compliance with the OSI protocol can be transparently transmitted.
Prerequisite
A Task Collection

Web LCT
Procedure
Step 1 In the NE Explorer, select the NE and then choose Communication > OSI Management from the Function Tree. Click the OSI Tunnel tab. Step 2 Click New. Then, the Create OSI Tunnel dialog box is displayed. Step 3 Set Remote IP Address and LAPD Actor. Step 4 Click OK. Step 5 Set the attributes of the OSI tunnel according to the service planning information Step 6 Click Apply. ----End

By querying ECC routes, you can check whether the correct HWECC solution is configured and whether the communication between NEs is normal.
Prerequisite

Web LCT
Procedure
Step 1 In the NE Explorer, select the NE from the Object Tree and then choose Communication > NE ECC Link Management from the Function Tree. Step 2 Check whether the ECC route and related parameters are set correctly in NE ECC Link Management List. ----End
A.3.11 Querying IP Routes

By querying IP routes, you can check whether the IP over DCC solution is configured correctly and whether the communication between NEs is normal.
Prerequisite

Web LCT
A Task Collection
Procedure
Step 1 In the NE Explorer, select the NE from the Object Tree and then choose Communication > IP Stack Protocol Management from the Function Tree. Click the IP Route Management tab. Step 2 Check whether the IP routes and related parameters in the routing table are in accordance with the service planning information. ----End
A.3.12 Querying OSI Routes

By querying OSI routes, you can check whether the OSI over DCC solution is configured correctly and whether the communication between NEs is normal.
Prerequisite

Web LCT
Procedure
Step 1 In the NE Explorer, select the NE from the Object Tree and then choose Communication > OSI Management from the Function Tree. 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 about the L1 routes is correct. Step 5 Click the L2 Routing tab to check whether the information about the L2 routes is correct. ----End
A.4 Configuring Service Access of NEs

You can ensure the security of a network by setting service access of the NEs on the network. A.4.1 Configuring LCT Access to NEs When an NE is managed by the NMS, the LCT cannot access this NE by default. A.4.2 Configuring Ethernet Access to NEs By default, the NMS can access an NE by using the Ethernet port. A.4.3 Configuring Serial Interface Access to NEs By default, the NMS can access an NE through serial interfaces.
A.4.1 Configuring LCT Access to NEs

When an NE is managed by the NMS, the LCT cannot access this NE by default.
A Task Collection
Prerequisite

Web LCT
Context
l If the LCT requests to log in to an NE to which the NMS has logged in, the NE determines whether to permit the login of the LCT according to the status of LCT Access Control Switch. If the LCT requests to log in to an NE to which the NMS has not logged in, the NE permits the login of the LCT regardless of the status of LCT Access Control Switch. The NMS, however, can log in to an NE to which the LCT has logged in. That is, the login of the LCT does not affect the login of the NMS. After the NMS user logs in to the NE successfully, the logged LCT user is not affected. If LCT Access Control Switch is set to Disable Access, the logged LCT user is also not affected.
Procedure
Step 1 In the NE Explorer, select the NE from the Object Tree and then choose Security > LCT Access Control from the Function Tree.
Step 2 Click Access Allowed to enable the LCT access function.

NOTE
To disable the LCT access function, click Disable Access.
----End
A.4.2 Configuring Ethernet Access to NEs

By default, the NMS can access an NE by using the Ethernet port.
Prerequisite

Web LCT
Context
l l It is recommended that the LCT accesses an NE through Ethernet interfaces. If you need to initialize an NE or perform software loading by using the LCT, the LCT needs to access the NE through Ethernet interfaces.
Issue 05 (2010-10-30)
A Task Collection
Procedure
Step 1 In the NE Explorer, select the NE from the Object Tree and then choose Communication > Access Control from the Function Tree. Step 2 Select the Enable Ethernet Access check box and click Apply to enable the Ethernet access function.
NOTE
To disable the Ethernet access function, deselect the Enable Ethernet Access check box and click Apply.
----End
A.4.3 Configuring Serial Interface Access to NEs

By default, the NMS can access an NE through serial interfaces.
Prerequisite

Web LCT
Context
If the LCT cannot access an NE through serial interfaces when the Enable Serial Port Access check box is selected, the LCT access function may be disabled.
Procedure
Step 1 In the NE Explorer, select the NE from the Object Tree and then choose Communication > Access Control from the Function Tree. Step 2 Select the Enable Serial Port Access check box and select Access NM. Then, click Apply.
A-36
Issue 05 (2010-10-30)
A Task Collection
Step 3 Optional: Select the baud rate of the serial interface from the Baud Rate drop-down list. Click Apply to complete the setting. ----End
Example
Table A-14 Parameters Parameter Enable Serial Port Access Value Range Selected Not selected Default Value Selected Description If the Enable Serial Port Access check box is selected, the serial port access function is available. If Access Command Line is selected, the serial interface can be used to access the command line terminal. If Access NM is selected, the serial interface can be used to access the NMS. This parameter specifies the communication rate of the serial port. This parameter can be set only when the Enable Serial Port Access check box is selected.
Access Command Line
Selected Not selected
Not selected
Access NM
Selected
Baud Rate
1200 2400 4800 9600 19200 38400 57600 115200
9600
A.5 Managing Radio Links

Before you configure the radio link between two radio sites, you need to configure the corresponding information about the radio link. A.5.1 Creating an IF 1+1 Protection Group If the radio link adopts 1+1 HSB/FD/SD protection, you need to create the corresponding IF 1 +1 protection group. A.5.2 Creating an XPIC Workgroup When two IFX boards that form an XPIC workgroup are installed on an IDU, you can create an XPIC workgroup to ensure that the XPIC workgroup is configured with the same work mode, transmission frequency, TX power, and ATPC attributes. A.5.3 Configuring the IF/ODU Information of a Radio Link By configuring the IF/ODU information of a radio link, you can configure the IF/ODU information that is frequently used by the radio link.
A Task Collection
A.5.4 Setting the Hybrid/AM Attribute Hybrid radio supports hybrid transmission of E1 services and Ethernet services and supports the adaptive modulation (AM) function. Therefore, Hybrid radio ensures reliable transmission of E1 services and flexible transmission of Ethernet services whose bandwidth is large and changes dynamically. A.5.5 Creating an N+1 Protection Group When the OptiX RTN 620 transmits two or three STM-1 radio services in point-to-point mode, you can adopt the N+1 protection configuration. A.5.6 Creating REGs In the case of 3+1 protection, you need to configure REGs for the secondary NE. A.5.7 Configuring the ATPC function To configure the ATPC function, set the ATPC attributes of the IF board. A.5.8 Setting Parameters of IF Interfaces This section describes how to set parameters of IF interfaces, including the IF attributes and ATPC attributes of the IF boards. A.5.9 Setting Parameters of ODU Interfaces This section describes how to set parameters of an ODU interface, including the RF attributes, power attributes, and advanced attributes of the ODU. A.5.10 Querying ATPC Adjustment Records By querying the ATPC adjustment records, you can be familiar with the running status of the ATPC function. A.5.11 Querying History Transmit Power and Receive Power Checking the change trend of the history transmit power and receive power provides reference for radio link troubleshooting. A.5.12 Querying the AM Status By querying the AM status, you can trace the change of the modulation mode when the AM function is used. A.5.13 Querying the IF 1+1 Protection Status You can learn about the current information of the IF 1+1 protection by querying the IF 1+1 protection status. A.5.14 Querying the IF N+1 Protection Status You can learn about the current information of the IF N+1 protection by querying the IF N+1 protection status. A.5.15 Performing IF 1+1 Protection Switching You can perform an external switching on an IF 1+1 protection group by performing an IF 1+1 protection switching. A.5.16 Performing IF N+1 Protection Switching You can perform an external switching on an IF N+1 protection group by performing an IF N +1 protection switching. A.5.17 Starting/Stopping the N+1 Protection Protocol If you first stop the N+1 protection protocol and then start it, the N+1 protection protocol can be restored to the initial state.
A-38
Issue 05 (2010-10-30)
A Task Collection
A.5.1 Creating an IF 1+1 Protection Group

If the radio link adopts 1+1 HSB/FD/SD protection, you need to create the corresponding IF 1 +1 protection group.
Prerequisite
l l The NE user must have the authority of Operation Level or higher. The IF boards and the ODUs to which the IF boards are connected must be added.

Web LCT
Procedure
Step 1 In the NE Explorer, select the NE from the Object Tree and then choose Configuration > Link Configuration from the Function Tree. Step 2 Click the IF 1+1 Protection tab. Step 3 Click New. Then, the Create IF 1+1 Protection dialog box is displayed. Step 4 Set the parameters of the IF 1+1 protection.
Issue 05 (2010-10-30)
A-39
A Task Collection
Example
Table A-15 Parameters Parameter Working Mode Value Range HSB FD SD Default Value HSB Description l In 1+1 HSB protection mode, the system provides a 1+1 hot standby configuration for the IF board and ODU at both ends of each hop of a radio link to provide protection. l In 1+1 FD protection mode, the system uses two channels that have a frequency spacing between them, to transmit and receive the same signal. The remote end selects signals from the two received signals. With the 1+1 FD protection, the impact of the fading on signal transmission is reduced. l In 1+1 SD protection mode, the system uses two antennas that have a space distance between them, to receive the same signal. The equipment selects signals from the two received signals. With the 1+1 SD protection, the impact of the fading on signal transmission is reduced. l The 1+1 FD protection mode and 1+1 SD protection mode are compatible with the 1+1 HSB switching function. l Set this parameter according to the service planning information. Revertive Mode Revertive Non-Revertive Revertive l When this parameter is set to Revertive, the NE that is in the switching state releases the switching and enables the former working channel to return to the normal state some time after the former working channel is restored to normal. l When this parameter is set to NonRevertive, the NE that is in the switching state keeps the current state unchanged unless another switching occurs even though the former working channel is restored to normal. l It is recommended that this parameter takes the default value.
A-40
Issue 05 (2010-10-30)
A Task Collection
Parameter WTR Time (s)
Default Value 600
Description l This parameter is valid only when Revertive Mode is set to Revertive. l When the time after the former working channel is restored to normal reaches the set wait-to-restore (WTR) time, a revertive switching occurs. l It is recommended that this parameter takes the default value.
Enable Reverse Switching
Enable Disable
Enable
l When both the main IF board and the standby IF board at the sink end report service alarms, they send the alarms to the source end by using the MWRDI overhead in the microwave frame. When this parameter at the source end is set to Enable and the reverse switching conditions are met, the IF 1+1 protection switching occurs at the source end. l This parameter is valid only when Working Mode is set to HSB or SD. l Generally, if Working Mode is set to HSB, it is recommended that you set this parameter to Disabled; if Working Mode is set to SD, it is recommended that you set this parameter to Enabled.
Working Board Protection Board
IF ports
l In 1+1 FD/SD mode, two IF boards must be installed as a pair in slots 5 and 7 (the IF board in slot 5 is recommended to be the main board) or in slots 6 and 8 (the IF board in slot 6 is recommended to be the main board). l In 1+1 HSB mode, the IF boards can be installed in slots 5-8. It is recommended that you install two IF boards in a pair in slots 5 and 7 (the IF board in slot 5 is the main board) or in slots 6 and 8 (the IF board in slot 6 is the main board).
NOTE
The parameters Working Mode, Revertive Mode, WTR Time (s), and Enable Reverse Switching must be set to the same values at both ends of a radio link hop.
Follow-up Procedure
l In the case of 1+1 HSB protection and 1+1 SD protection, you need to configure the IF/ ODU information of the main radio link later. The standby radio link automatically copies
Issue 05 (2010-10-30)
A-41
A Task Collection
the related information of the active microwave link except the transmission status of the ODU. l In the case of 1+1 FD protection, you need to configure the IF/ODU information of the main radio link and the information of the standby ODU later. The standby radio link automatically copies the IF information of the main radio link.
NOTE
The default TX Status of an ODU is Unmute. Therefore, you need not configure the TX Status of the standby ODU after you create an IF 1+1 protection group.
A.5.2 Creating an XPIC Workgroup

When two IFX boards that form an XPIC workgroup are installed on an IDU, you can create an XPIC workgroup to ensure that the XPIC workgroup is configured with the same work mode, transmission frequency, TX power, and ATPC attributes.
Prerequisite
l l l The NE user must have the authority of Operation Level or higher. The IFX boards and the ODUs to which the IFX boards are connected must be created. The XPIC Enabled parameter must be set to Enabled (default value) for the IFX boards.

Web LCT
Procedure
Step 1 In the NE Explorer, select the NE from the Object Tree and then choose Configuration > Link Configuration from the Function Tree. Step 2 Click the XPIC tab. Step 3 Click New. Then, the Create XPIC Protection Group dialog box is displayed. Step 4 Set the parameters for the XPIC workgroup.
A-42
Issue 05 (2010-10-30)
A Task Collection
Example
Table A-16 Parameters Parameter Working Mode Value Range 7,STM-1,28MHz, 128QAM Default Value Description This parameter specifies the radio working mode. The format of a radio working mode is "service capacity, working bandwidth, modulation mode". The radio working modes must be the same at the receive and transmit ends. l Polarization direction-V and Polarization direction-H indicate the IF interfaces to which polarization direction V and polarization direction H correspond. l It is recommended that you install the two IFX boards that form an XPIC workgroup in the slots that are at the same layer or in the same column. Set the IF interface on the IFX board that has a smaller slot number to Polarization direction-V and the IF interface on the other IFX board to Polarization direction-H.
Polarization direction-V Polarization direction-H
IF interfaces IFX boards
Issue 05 (2010-10-30)
A-43
A Task Collection
Parameter Link ID-V Link ID-H
Default Value -
Description l Link ID-V and Link ID-H indicate the link IDs to which polarization direction V and polarization direction H correspond. l Link IDs are identifiers of radio links and are used to prevent radio links between sites from being wrongly connected. l When the link ID received by an NE is different from the link ID set for the NE, the NE reports an MW_LIM alarm and inserts the AIS. l Set these two parameters according to the service planning information.? These two parameters must be set to different values, but Link ID-V must be set to the same value at both ends of a radio link and Link ID-H must also be set to the same value at both ends of a radio link. l The value of this parameter must not exceed the rated power range supported by the ODU. l The transmit power of the ODU must be set to the same value at both ends of a radio link. l Set this parameter according to the service planning information.
TX Power (dBm)
-10.0 to +35.0
Transmission Frequency (MHz)
0 to 4294967.295
l The parameter specifies the channel center frequency. l The value of this parameter must not be less than the sum of the lower transmit frequency limit supported by the ODU and a half of the channel spacing, and must not be more than the difference between the upper transmit frequency limit supported by the ODU and a half of the channel spacing. l Set this parameter according to the service planning information.
A-44
Issue 05 (2010-10-30)
A Task Collection
Parameter Transmission Status
Value Range mute unmute
Default Value -
Description l When Transmission Status is set to mute, the transmitter of the ODU does not work but the ODU can normally receive radio signals. l When Transmission Status is set to unmute, the ODU normally transmits and receives radio signals. l This parameter generally takes the default value.
ATPC Enabled
Enabled Disabled
l This parameter specifies whether the ATPC function is enabled. This parameter indicates whether the ATPC function is enabled. The ATPC function ensures that the transmit power of the transmitter automatically traces the changes of the receive level at the receive end, within the ATPC controlled range. l In the case of areas where fast fading is severe, it is recommended that you set this parameter to Disabled. l During commissioning, set this parameter to Disabled to ensure that the transmit power is not changed. After commissioning, re-set the ATPC attributes.
ATPC Adjustment (dB)
1 2 3 4 5
This parameter specifies the step for an ATPC adjustment to the ODU transmit power.
ATPC Upper Threshold (dBm) ATPC Lower Threshold (dBm)
-20 to -75 -35 to -90
l Set the central value between the ATPC upper threshold and the ATPC lower threshold so that the central value is equal to the required value of the receive power. l Ensure that the difference between values of the automatic ATPC upper threshold and the automatic ATPC lower threshold is not less than 5 dB.
NOTE
Each of the ATPC parameters must be set to the same value at both ends of a radio link.
Issue 05 (2010-10-30)
A-45
A Task Collection
Follow-up Procedure
Generally, you do not need to configure the IF/ODU information after you configure an XPIC workgroup. You, however, need to set the T/R spacing used by the ODU in the IF/ODU Configuration tab page if the used ODU supports two T/R spacings.
A.5.3 Configuring the IF/ODU Information of a Radio Link

By configuring the IF/ODU information of a radio link, you can configure the IF/ODU information that is frequently used by the radio link.
Prerequisite
l l The NE user must have the authority of Operation Level or higher. The IF boards and the ODUs to which the IF boards are connected must be added.

Web LCT
Precautions
l l In 1+1 HSB/SD protection mode, one protection group corresponds to one radio link. In this case, you need configure only the IF/ODU information of the main equipment. In 1+1 FD protection mode, one protection group corresponds to one radio link. In this case, you need configure the IF/ODU information of the main equipment and the ODU information of the standby equipment. In the case of XPIC radio links, one XPIC workgroup corresponds to two radio links. The IF/ODU information of the radio links must be configured in the XPIC workgroup. In the case of N+1 protection mode, one N+1 protection group corresponds to N+1 radio links and the IF/ODU information of the N+1 radio links must be set separately.
l l
Procedure
Step 1 In the NE Explorer, select the NE from the Object Tree and then choose Configuration > Link Configuration from the Function Tree. Step 2 Click the IF/ODU Configuration tab. Step 3 Click an IF board icon or ODU icon. Then, the system displays the IF/ODU information of the radio link to which the IF board or ODU to which the IF board is connected belongs. Step 4 Configure the corresponding IF information of the radio link. Step 5 Click Apply. Step 6 Configure the corresponding ODU information of the radio link. Step 7 Click Apply.
A-46
Issue 05 (2010-10-30)

NOTE
A Task Collection
You need to click Apply after you set the IF information of the radio link and click Apply after you set the ODU information of the radio link.
----End
Example
Table A-17 Parameters Parameter Work Mode Value Range 1,4E1,7MHz,QPSK 2,4E1,3.5MHz, 16QAM 3,8E1,14MHz,QPS K 4,8E1,7MHz, 16QAM 5,16E1,28MHz,QP SK 6,16E1,14MHz, 16QAM 7,STM-1,28MHz, 128QAM 8,E3,28MHz,QPSK 9,E3,14MHz, 16QAM 10,22E1,14MHz, 32QAM 11,26E1,14MHz, 64QAM 12,32E1,14MHz, 128QAM 13,35E1,28MHz, 16QAM 14,44E1,28MHz, 32QAM 15,53E1,28MHz, 64QAM 16,5E1,7MHz,QPS K 17,10E1,14MHz,Q PSK 18,2E1,3.5MHz,QP SK Default Value Description l This parameter indicates the radio work mode in "work mode, service capacity, channel spacing, modulation mode" format. l The IF1A/IF1B board supports radio working modes 1-15 and the IF0A/IF0B board supports radio working modes 5 and 16-18. The IFX board supports radio working mode 7. l The IFH2 board on the IDU 620 does not support Work Mode. l Set this parameter according to the service planning information. The radio working modes of the IF boards at both ends of the radio link must be the same.
Issue 05 (2010-10-30)
A-47
A Task Collection
Parameter Link ID
Default Value -
Description l As the identifier of a radio link, this parameter is used to prevent misconnection of radio links between sites. l If this parameter is different from Received Link ID, the NE reports the MW_LIM alarm and inserts the AIS into the downstream. l Set this parameter according to the service planning information. Each radio link of an NE must have a unique link ID, and the link IDs at both ends of a radio link must be the same.
Received Link ID
This parameter displays the received link ID.

NOTE The link ID at the local end must the same as the link ID at the opposite end.
ATPC Enable Status
Enabled Disabled
l This parameter specifies whether the ATPC function is enabled. This parameter indicates whether the ATPC function is enabled. The ATPC function ensures that the transmit power of the transmitter automatically traces the changes of the receive level at the receive end, within the ATPC controlled range. l In the case of areas where fast fading is severe, it is recommended that you set this parameter to Disabled. l During commissioning, set this parameter to Disabled to ensure that the transmit power is not changed. After commissioning, re-set the ATPC attributes.
ATPC Threshold (dBm) ATPC Upper Threshold(dBm)
-75.0 to -20.0
-45.0
This parameter displays the permitted ATPC adjustment range. l Set the central value between the ATPC upper threshold and the ATPC lower threshold to a value for the expected receive power. l It is recommended that you set ATPC Upper Threshold(dBm) to the sum of the planned central value between the ATPC upper threshold and the ATPC lower threshold and 10 dB, and ATPC
A-48
Issue 05 (2010-10-30)
A Task Collection
Parameter ATPC Lower Threshold(dBm)
Value Range -35.0 to -90.0
Default Value -70.0
Description Lower Threshold(dBm) to the difference between the planned central value between the ATPC upper threshold and the ATPC lower threshold and 10 dB. l You can set the ATPC upper threshold only when ATPC Automatic Threshold(dBm) is set to Disabled.
ATPC Automatic Threshold Enable Status
Enabled Disabled
Disabled
l This parameter specifies whether the ATPC automatic threshold function is enabled. l If this parameter is set to Enabled, the equipment automatically uses the preset ATPC upper and lower thresholds according to the work mode of the radio link. l If this parameter is set to Disabled, you need to manually set ATPC Upper Threshold(dBm) and ATPC Lower Threshold(dBm).
TX Frequency (MHz)
0 to 4294967.295
l The parameter specifies the channel center frequency. l The value of this parameter must not be less than the sum of the lower transmit frequency limit supported by the ODU and a half of the channel spacing, and must not be more than the difference between the upper transmit frequency limit supported by the ODU and a half of the channel spacing. l The difference between the transmit frequencies of the ODUs at both ends of a radio link is a T/R spacing. l Set this parameter according to the service planning information.
Range of TX Frequency(MHz) Actual TX Frequency(MHz)
This parameter specifies the transmit frequency range of an ODU. This parameter displays the actual transmit frequency of an ODU.
Issue 05 (2010-10-30)
A-49
A Task Collection
Parameter Actual RX Frequency(MHz) T/R Spacing (MHZ)
Value Range 0 to 4294967.295
Default Value -
Description This parameter displays the actual receive frequency of an ODU. l This parameter indicates the spacing between the TX frequency and receive frequency of the ODU. If Station Type of the ODU is TX high, the transmit frequency is one T/R spacing higher than the receive power. If Station Type of the ODU is TX low, the transmit frequency is one T/R spacing lower than the receive power. l If the ODU supports only one T/R spacing, set this parameter to 0, indicating that the T/R spacing supported by the ODU is used. l The T/R spacing of the ODU should be set to the same value at both the ends of a radio link.
Actual T/R Spacing(MHZ) TX Power(dBm)
-10.0 to +35.0
This parameter displays the actual T/R spacing of a board. l The value of this parameter must not exceed the rated power range supported by the ODU. l The transmit power of the ODU must be set to the same value at both ends of a radio link. l Set this parameter according to the service planning information.
Range of TX Power (dBm) Actual TX Power (dBm) Actual RX Power (dBm) TX Status
mute unmute
This parameter specifies the transmit power range of an ODU. This parameter displays the actual transmit power of an ODU. This parameter displays the actual receive power of an ODU. l When Transmission Status is set to mute, the transmitter of the ODU does not work but the ODU can normally receive radio signals. l When Transmission Status is set to unmute, the ODU normally transmits and receives radio signals. l This parameter, generally, takes the default value.
A-50
Issue 05 (2010-10-30)
A Task Collection
Parameter Actual TX Status
Value Range mute unmute
Default Value -
Description This parameter displays the transmission status of the RF transmitter. This parameter displays the operating frequency band of an ODU. This parameter displays the type of an ODU. This parameter displays the type of a site. This parameter displays the production serial number and the manufacturer code of an ODU. This parameter displays the output power level of an ODU.
Frequency(GHz) Equip Type Station Type Produce SN
Transmission Power Type
NOTE
The ATPC attributes must be set to the same at both the ends of a radio link.
A.5.4 Setting the Hybrid/AM Attribute

Hybrid radio supports hybrid transmission of E1 services and Ethernet services and supports the adaptive modulation (AM) function. Therefore, Hybrid radio ensures reliable transmission of E1 services and flexible transmission of Ethernet services whose bandwidth is large and changes dynamically.
Prerequisite

Web LCT
Context
The OptiX RTN 620 supports the Hybrid/AM function. The IFH2 board is used as the Hybrid IF board.
Procedure
Step 1 In the NE Explorer, select the Hybrid IF board, and then choose Configuration > Hybrid/AM Configuration from the Function Tree. Step 2 Click Query. Step 3 Set the parameters associated with the Hybrid/AM function.
A Task Collection
NOTE
To set the Hybrid IF board to work in Super PDH mode of 40M/64QAM, do as follows: 1. Set AM Enable Status to Disable and set Manually Specified Modulation Mode to 64QAM. Click Apply. 2. Set IF Channel Bandwidth to 40M. Click Apply.
Example
Table A-18 Parameters Parameter IF Channel Bandwidth Value Range In the case of the IFH2 board on the OptiX RTN 620: l 7M l 14M l 28M l 40M l 56M AM Enable Status Disable Enable l When this parameter is set to Disable, the radio link uses the specific modulation mode only. In this case, you need to select Manually Specified Modulation Mode. l When this parameter is set to Enable, the radio link uses the corresponding modulation mode according to the channel conditions. Hence, the Hybrid radio ensures reliable transmission of the E1 services and provides dynamic bandwidth for the Ethernet services when the AM function is enabled. Modulation Mode of the Assured AM Capacity QPSK 16QAM 32QAM 64QAM 128QAM 256QAM QPSK This parameter specifies the lowest-efficiency modulation mode that the AM function supports. Set this parameter to the planned value. Generally, the value of this parameter is determined by the service transmission bandwidth that the Hybrid radio must ensure and the availability of the radio link that corresponds to this modulation mode. This parameter is valid only when AM Enable Status is set to Enable. Default Value 7M Description IF Channel Bandwidth indicates the channel spacing of the corresponding radio links. This parameter needs to set according to the service planning information.
NOTE Only the combination of the IF Channel Bandwidth of 40M and the modulation mode of 64QAM forms the Super PDH mode. The Super PDH mode does not support the AM function.
A-52
Issue 05 (2010-10-30)
A Task Collection
Parameter Modulation Mode of the Full AM Capacity
Value Range QPSK 16QAM 32QAM 64QAM 128QAM 256QAM
Default Value 128QAM
Description This parameter specifies the highest-efficiency modulation mode that the AM function supports. Set this parameter to the planned value. Generally, the value of this parameter is determined by the bandwidth of the services that need to be transmitted over the Hybrid radio and the availability of the radio link that corresponds to this modulation mode. This parameter is valid only when AM Enable Status is set to Enable.
Manually Specified Modulation Mode
QPSK 16QAM 32QAM 64QAM 128QAM 256QAM
This parameter specifies the modulation mode that the radio link uses for the transmission. This parameter is valid only when AM Enable Status is set to Disable.
E1 Capacity
1 to 75
This parameter specifies the maximum number of E1 services that are transmitted in Hybrid radio mode. The value of this parameter cannot exceed the Assured E1 Capacity. E1 Capacity must be set to the same value at both ends of a radio link.
A.5.5 Creating an N+1 Protection Group

When the OptiX RTN 620 transmits two or three STM-1 radio services in point-to-point mode, you can adopt the N+1 protection configuration.
Prerequisite
l l l l The NE user must have the authority of Operation Level or higher. The IF boards and the ODUs to which the IF boards are connected must be added. The STM-1 optical/electrical interface boards (only in the case of the primary NE that is to be configured with 3+1 protection) must be added. The IF boards must work in STM-1 mode.

Web LCT
Context
When an N+0 service is converted into an N+1 service by configuring the N+1 protection, the original services are not interrupted.
A Task Collection
Procedure
Step 1 In the NE Explorer, select the NE from the Object Tree and then choose Configuration > Link Configuration from the Function Tree. Click the N+1 Protection tab. Step 2 Click Create. Then, the Create an N+1 Protection Group dialog box is displayed. Step 3 Set the attributes of the N+1 protection group. Step 4 Set the slot mapping relation. 1. 2. In Select Mapping direction, select Working Unit. In Select Mapping Mode, select the line interface to which a working channel corresponds and click 3. 4. 5. .
Repeat Step 4.2 to select the line interfaces to which other working channels correspond. In Select Mapping direction, select Protection Unit. In Select Mapping Mode, select the line interface to which the protection channel corresponds and click .
A-54
Issue 05 (2010-10-30)
A Task Collection
Example
Table A-19 Parameters Parameter WTR Time(s) Value Range 300 to 720 Default Value 600 Description l When the time after the former working channel is restored to normal reaches the set wait-to-restore (WTR) time, a revertive switching occurs. l It is recommended that this parameter takes the default value. SD enable Enabled Disabled Enabled l When SD enable is set to Enabled, the B2_SD alarm is considered as a switching condition. l It is recommended that this parameter takes the default value. Slot Mapping Relation l In the case of 2+1 protection, map two IF interfaces as Working Unit and map the remaining IF interface as Protection Unit. l In the case of the 3+1 protection, it is recommended that you map the two IF interfaces and the first line interface of the STM-1 optical/electrical interface board that is connected to the secondary NE as Working Unit, and map the other line interface as Protection Unit.
NOTE
Set the attributes of the N+1 protection group to the same values for the equipment at both ends.
A.5.6 Creating REGs

In the case of 3+1 protection, you need to configure REGs for the secondary NE.
Prerequisite
l l l l The NE user must have the authority of Operation Level or higher. The IF boards and the ODUs to which the IF boards are connected must be added. The STM-1 optical/electrical interface board that is connected to the primary NE must be added. The IF boards must work in STM-1 mode.

Web LCT
A Task Collection
Context
In the case of 3+1 protection, you need to configure REGs for the secondary NE.
Procedure
Step 1 In the NE Explorer, select the NE from the Object Tree and then choose Configuration > REG Configuration from the Function Tree. Step 2 Click Create. Then, the Create REG dialog box is displayed. Step 3 Set the SD Enabled parameter. Step 4 Set the slot mapping relation. 1. 2. In Slot Mapping Direction, select West Line. In Select Mapping Mode, select the line interface to which the west line corresponds and click 3. 4. .
In Slot Mapping Direction, select East Line. In Select Mapping Mode, select the line interface to which the east line corresponds and click .
Step 5 Click OK. Step 6 Repeat steps Step 2 to Step 5 and create another REG.
A-56
Issue 05 (2010-10-30)
A Task Collection
----End
Example
Table A-20 Parameters Parameter SD Enabled Value Range Enabled Disabled Default Value Enabled Description l When this parameter is set to Enabled, the REG inserts an MS_AIS alarm if a B2_SD alarm is generated. l It is recommended that this parameter takes the default value. Slot Mapping Relation It is recommended that you map the IF interface as West Line and the interface on the STM-1 optical/electrical interface board as East Line.
A.5.7 Configuring the ATPC function

To configure the ATPC function, set the ATPC attributes of the IF board.
Prerequisite
l l
Issue 05 (2010-10-30)
The NE user must have the authority of Operation Level or higher. The corresponding IF board must be added.
A Task Collection

Web LCT
Precautions
l l In the case of two IF boards that are configured as a 1+1 protection group, set only the ATPC attributes of the main IF board. The following procedure describes how to set ATPC parameters in the IF interface configuration dialog box of the IF board. You can also set ATPC parameters during the following process: A.5.2 Creating an XPIC Workgroup A.5.3 Configuring the IF/ODU Information of a Radio Link
Procedure
Step 1 In the NE Explorer, select the IF board from the Object Tree and then choose Configuration > IF Interface from the Function Tree. Step 2 Click the ATPC Attributes tab. Step 3 Set the ATPC attributes.
Example
Table A-21 Parameters Parameter ATPC Enable Status Value Range Enabled Disabled Default Value Disabled Description l This parameter specifies whether the ATPC function is enabled. This parameter specifies whether the ATPC function is enabled. The ATPC function enables the transmit power of a transmitter to automatically trace the change of the received signal level (RSL) at the receive end within the ATPC control range. l In the case of areas where fast fading is severe, it is recommended that you set this parameter to Disabled. ATPC Upper Threshold (dBm) -20 to -75 -45 l Set the central value between the ATPC upper threshold and the ATPC lower threshold so that the central value is
Issue 05 (2010-10-30)
A-58
A Task Collection
Parameter ATPC Lower Threshold (dBm)
Value Range -35 to -90
Default Value -70
Description equal to the required value of the receive power. l Ensure that the difference between values of the automatic ATPC upper threshold and the automatic ATPC lower threshold is not less than 5 dB. This parameter specifies the step for an ATPC adjustment to the ODU transmit power.
ATPC Adjustment (dB)
1 2 3 4 5
Enabled Disabled
Enabled
l This parameter specifies whether the ATPC function is enabled. This parameter specifies whether the ATPC function is enabled. The ATPC function enables the transmit power of a transmitter to automatically trace the change of the received signal level (RSL) at the receive end within the ATPC control range. l When the function is enabled, the manually set ATPC upper and lower thresholds are invalid. The equipment automatically uses the preset ATPC upper and lower thresholds based on the working mode of the IF board. l When the function is disabled, the manually set ATPC upper and lower thresholds are used.
ATPC Automatic Threshold (dBm) ATPC Upper Automatic Threshold(dBm) ATPC Lower Automatic Threshold(dBm)
This parameter displays the ATPC automatic threshold. This parameter displays the ATPC upper automatic threshold. This parameter displays the ATPC lower automatic threshold.
NOTE
l Set ATPC attributes to the same values at both ends of a radio link. l During commissioning, set ATPC Enable Status to Disabled to ensure that the transmit power is not changed. After commissioning, re-set the ATPC attributes.
Issue 05 (2010-10-30)
A-59
A Task Collection
A.5.8 Setting Parameters of IF Interfaces

This section describes how to set parameters of IF interfaces, including the IF attributes and ATPC attributes of the IF boards.
Prerequisite
The NE user must have the authority of Operation Level or higher. The corresponding IF boards must be added.

Web LCT
Procedure
Step 1 In the NE Explorer, select the IF board from the Object Tree and then choose Configuration > IF Interface from the Function Tree. Step 2 Click the IF Attributes tab. Step 3 Set each parameter for the IF attributes.
NOTE
In the case of the IFH2 board on the OptiX RTN 620, Radio Work Mode cannot be specified manually.
Step 4 Click Apply. Step 5 Click the ATPC Attributes tab. Step 6 Set each parameter for the ATPC attributes.
A-60
Issue 05 (2010-10-30)
A Task Collection
Example
Table A-22 Parameters Parameter Radio Work Mode Value Range 1,4E1,7MHz,QPSK 2,4E1,3.5MHz, 16QAM 3,8E1,14MHz,QPS K 4,8E1,7MHz, 16QAM 5,16E1,28MHz,QP SK 6,16E1,14MHz, 16QAM 7,STM-1,28MHz, 128QAM 8,E3,28MHz,QPSK 9,E3,14MHz, 16QAM 10,22E1,14MHz, 32QAM 11,26E1,14MHz, 64QAM 12,32E1,14MHz, 128QAM 13,35E1,28MHz, 16QAM 14,44E1,28MHz, 32QAM 15,53E1,28MHz, 64QAM 16,5E1,7MHz,QPS K 17,10E1,14MHz,Q PSK 18,2E1,3.5MHz,QP SK Default Value Description l This parameter indicates the radio working mode in "working mode, service capacity, channel spacing, modulation mode" format. l The IF1A/IF1B board supports radio working modes 1-15 and the IF0A/ IF0B board supports radio working modes 5 and 16-18. The IFX board supports radio working mode 7. l In the case of the IFH2 board on the OptiX RTN 620, Radio Work Mode cannot be specified manually. l Set this parameter according to the service planning information. The radio working modes of the IF boards at both ends of the radio link must be the same.
Issue 05 (2010-10-30)
A-61
A Task Collection
Parameter Radio Link ID
Default Value -
Description l As the identifier of a radio link, this parameter is used to prevent misconnection of radio links between sites. l If this parameter is different from Received Link ID, the NE reports the MW_LIM alarm and inserts the AIS into the downstream. l Set this parameter according to the service planning information. Each radio link of an NE must have a unique link ID, and the link IDs at both ends of a radio link must be the same.
IF Port Loopbacka
Non-Loopback Inloop Outloop
Non-Loopback
l IF port inloop indicates that loopback occurs in the IF signals to be transmitted to the opposite end. l IF port outloop indicates that loopback occurs in the IF signals to be received. l This parameter generally takes the default value.
2M Wayside Enable Statusb
Enabled Disabled
Disabled
l In the case of the IFX board, this parameter is valid only when Radio Work Mode is set to 7,STM-1,28MHz,128QAM. l In the case of the IF1A/IF1B board, this parameter is valid only when Radio Work Mode is set to 7,STM-1,28MHz,128QAM, 8,E3,28MHz,QPSK, or 9,E3,14MHz, 16QAM. l This parameter indicates whether the radio link transmits the wayside E1 service. l The wayside E1 service is a 2.048 kbit/ s service that is transmitted over the overheads of the STM-1 microwave frame. The OptiX RTN 620 accesses the wayside E1 service through the external clock interface on the PXC board.
A-62
Issue 05 (2010-10-30)
A Task Collection
Parameter 2M Wayside Input Boardb
Value Range 1 3
Default Value 1
Description l This parameter is valid only when 2M Wayside Enable Status is set to Enabled. l This parameter indicates the slot in which the PXC board accesses the wayside E1 service through the external clock interface.
Consecutive Wave Status
Stop Start
This parameter displays or specifies the status of transmitting the carrier signals from the IF interface. This parameter can be set to Start in the commissioning process only. In normal cases, this parameter is set to Stop. Otherwise, services are interrupted.
XPIC Enablec
Enabled Disabled
Enabled
l This parameter indicates whether the XPIC function is enabled for the IFX board. l If the IFX board does not use the XPIC function, set this parameter to Disabled. In this case, use an XPIC cable to perform self-loop at the XPIC interfaces.
ATPC Enable Statusd
Enabled Disabled
Disabled
l This parameter specifies whether the ATPC function is enabled. This parameter indicates whether the ATPC function is enabled. The ATPC function ensures that the transmit power of the transmitter automatically traces the changes of the RSL at the receive end, within the ATPC controlled range. l In the case of areas where fast fading is severe, it is recommended that you set this parameter to Disabled. l During commissioning, set this parameter to Disabled to ensure that the transmit power is not changed. After commissioning, re-set the ATPC attributes.
ATPC Upper Threshold (dBm)d
-20 dBm to -75 dBm
l Set the central value between the ATPC upper threshold and the ATPC lower threshold so that the central value is equal to the required value of the receive power. l Ensure that the difference between values of the automatic ATPC upper
Issue 05 (2010-10-30)
A-63
A Task Collection
Parameter ATPC Lower Threshold (dBm)d
Value Range -35 dBm to -90 dBm
Default Value -
Description threshold and the automatic ATPC lower threshold is not less than 5 dB.
Enabled Disabled
Enabled
l This parameter specifies whether the ATPC function is enabled. This parameter indicates whether the ATPC function is enabled. The ATPC function ensures that the transmit power of the transmitter automatically traces the changes of the RSL at the receive end, within the ATPC controlled range. l When the function is enabled, the manually set ATPC upper and lower thresholds are invalid. The equipment automatically uses the preset ATPC upper and lower thresholds based on the working mode of the IF board. l When the function is disabled, the manually set ATPC upper and lower thresholds are used.
NOTE
l a: The IFX and IFH2 boards do not support loopback at the IF interfaces. l b: The IF0A/IF0B and IFH2 boards do not support the wayside E1 service. l c: The IF0A/IF0B, IFH2, and IF1A/IF1B boards do not support the XPIC function. l d: The ATPC attributes must be set to the same values at both ends of a radio link.
A.5.9 Setting Parameters of ODU Interfaces

This section describes how to set parameters of an ODU interface, including the RF attributes, power attributes, and advanced attributes of the ODU.
Prerequisite
l l l The NE user must have the authority of Operation Level or higher. The corresponding IF boards must be added. The corresponding ODU must be added in the slot layout diagram.

Web LCT
A Task Collection
Procedure
Step 1 In the NE Explorer, select the ODU from the Object Tree and then choose Configuration > ODU Interface from the Function Tree. Step 2 Click the Radio Frequency Attributes tab. Step 3 Set the transmit frequency and T/R spacing.
Step 4 Click Apply. Step 5 Click the Power Attributes tab. Step 6 Set the transmit power of the ODU.
Step 7 Click Apply. Step 8 Click the Advanced Attributes tab. Step 9 Set Configure Transmission Status.
Example
Table A-23 Parameters Parameter Transmit Frequency (MHz) Value Range Default Value Description l The parameter specifies the channel center frequency. l The value of this parameter must not be less than the sum of the lower transmit frequency limit supported by the ODU and a half of the channel spacing, and must not be more than the difference between the upper transmit frequency limit supported by the ODU and a half of the channel spacing. l The difference between the transmit frequencies of the ODUs at both ends of a radio link is a T/R spacing. l Set this parameter according to the service planning information.
A Task Collection
Parameter T/R Spacing (MHz)
Value Range 0 to 4294967.295
Default Value -
Description l This parameter indicates the spacing between the transmit frequency and receive frequency of the ODU. If Station Type of the ODU is TX high, the transmit frequency is one T/R spacing higher than the receive power. If Station Type of the ODU is TX low, the transmit frequency is one T/R spacing lower than the receive power. l If the ODU supports only one T/R spacing, set this parameter to 0, indicating that the T/R spacing supported by the ODU is used. l The T/R spacing of the ODU must be set to the same value at both ends of a radio link.
Maximum Transmit Power (dBm)
l The value of this parameter must not exceed the rated power range supported by the ODU. l This parameter specifies the upper threshold of the transmit power range of an ODU. After an ATPC adjustment, the transmit power cannot exceed the value of this parameter. l Set this parameter according to the service planning information.
Transmit Power (dBm)
l The value of this parameter must not exceed the rated power range supported by the ODU. l The transmit power of the ODU must be set to the same value at both ends of a radio link. l Set this parameter according to the service planning information.
A-66
Issue 05 (2010-10-30)
A Task Collection
Parameter Receive Power (dBm)
Value Range -
Default Value -
Description l This parameter specifies the expected receive power of the ODU and is mainly used in the antenna alignment stage. After this parameter is set, the NE automatically enables the antenna nonalignment indication function. l When the antenna non-alignment indication function is enabled, if the actual receive power of the ODU is 3 dB or more beyond the preset receive power, the ODU indicator on the IF board connected to the ODU blinks yellow (300 ms on and 300 ms off), indicating that the antennas are not aligned. l After the antennas are aligned for consecutive 30 minutes, the NE automatically disables the antenna nonalignment indication function. l Set this parameter according to the service planning information.
Configure Transmission Status
mute unmute
unmute
l When Transmission Status is set to mute, the transmitter of the ODU does not work but the ODU can normally receive radio signals. l When Transmission Status is set to unmute, the ODU normally transmits and receives radio signals. l This parameter generally takes the default value.
A.5.10 Querying ATPC Adjustment Records

By querying the ATPC adjustment records, you can be familiar with the running status of the ATPC function.
Prerequisite
l l l The NE user must have the authority of Operation Level or higher. The corresponding IF boards must be added. The corresponding ODU must be added in the slot layout diagram.

Web LCT
Issue 05 (2010-10-30)
A-67
A Task Collection
Procedure
Step 1 In the NE Explorer, select the ODU from the Object Tree and then choose Configuration > ATPC Adjustment Record from the Function Tree. Step 2 Click Query. Then, the running information of the ATPC function is returned. ----End
A.5.11 Querying History Transmit Power and Receive Power

Checking the change trend of the history transmit power and receive power provides reference for radio link troubleshooting.
Prerequisite

Web LCT
Procedure
Step 1 In the NE Explorer, select the ODU for which the history transmit power and receive power need be queried from the Object Tree, and choose Configuration > Performance Graph Analyse from the Function Tree. Step 2 Specify the start time and end time of a specific time span. The time span starts from the last routine maintenance time to the current time. Step 3 Set Counter Type to 15M. Step 4 Click Drawing. The history transmit and receive power curve of the ODU in the specified time span is displayed. Step 5 Analyze the power curve. If the receive power fading of two adjacent points exceeds 20 dB, but the weather does not change, contact the troubleshooting engineers. ----End
A.5.12 Querying the AM Status

By querying the AM status, you can trace the change of the modulation mode when the AM function is used.
Prerequisite

Web LCT
A Task Collection
Related Information
The AM working state can be queried only when the OptiX RTN 620 is configured with Hybrid radio services.
Procedure
Step 1 Choose Configuration > Hybrid/AM Configuration from the Function Tree. Step 2 Select the corresponding IFH2 board in the Hybrid/AM Configuration tab page. Step 3 Click Query. The current modulation modes of the transmit end and the receive end of the IFH2 board are displayed. ----End
A.5.13 Querying the IF 1+1 Protection Status

You can learn about the current information of the IF 1+1 protection by querying the IF 1+1 protection status.
Prerequisite
l l The NE user must have the authority of Operation Level or higher. The 1+1 protection group must be configured.

Web LCT
Procedure
Step 1 In the NE Explorer, select the NE from the Object Tree and then choose Configuration > Link Configuration from the Function Tree. Step 2 Click the IF 1+1 Protection tab. Step 3 Select the ID of the protection group to be queried under Protection Group. Step 4 Click Query. Check the working status of the IF 1+1 protection group in the Slot Mapping Relation area. ----End
A.5.14 Querying the IF N+1 Protection Status

You can learn about the current information of the IF N+1 protection by querying the IF N+1 protection status.
Prerequisite
l l
Issue 05 (2010-10-30)
The NE user must have the authority of Operation Level or higher. The N+1 protection group must be configured.
A Task Collection

Web LCT
Procedure
Step 1 In the NE Explorer, select the NE from the Object Tree and then choose Configuration > Link Configuration from the Function Tree. Step 2 Click the N+1 Protection tab. Step 3 Select the ID of the protection group to be queried under Protection Group. Step 4 Click Query. Check the working status of the IF N+1 protection group in the Slot Mapping Relation area. ----End
A.5.15 Performing IF 1+1 Protection Switching

You can perform an external switching on an IF 1+1 protection group by performing an IF 1+1 protection switching.
Prerequisite
l l The NE user must have the authority of Operation Level or higher. An IF 1+1 protection group must be configured.

Web LCT
Procedure
Step 1 In the NE Explorer, select the NE from the Object Tree and then choose Configuration > Link Configuration from the Function Tree. Step 2 Click the IF 1+1 Protection tab. Step 3 In Slot Mapping Relation, select the working unit or the protection unit of a protection group. Right-click the selected unit and select the required switching mode from the shortcut menu. A dialog box is displayed, prompting you whether to perform the switching. Step 4 Click Yes. A dialog box is displayed, indicating that the operation is successful. Step 5 Click OK. Step 6 Click Query. ----End
A.5.16 Performing IF N+1 Protection Switching

You can perform an external switching on an IF N+1 protection group by performing an IF N +1 protection switching.
A Task Collection
Prerequisite
l l The NE user must have the authority of Operation Level or higher. The N+1 protection group must be configured.

Web LCT
Procedure
Step 1 In the NE Explorer, select the NE from the Object Tree and then choose Configuration > Link Configuration from the Function Tree. Step 2 Click the N+1 Protection tab. Step 3 In Slot Mapping Relation, select the working unit or the protection unit of a protection group. Right-click the selected unit and select the required switching mode from the shortcut menu. A dialog box is displayed, indicating that the operation is successful. Step 4 Click Yes. Step 5 Click Query. ----End
A.5.17 Starting/Stopping the N+1 Protection Protocol

If you first stop the N+1 protection protocol and then start it, the N+1 protection protocol can be restored to the initial state.
Prerequisite
l l The NE user must have the authority of Operation Level or higher. The N+1 protection group must be configured.

Web LCT
Precautions
l l Stopping the N+1 protection protocol causes the failure of the N+1 protection. When services are switched onto the protection channel, stopping the N+1 protection protocol causes the services to switch back to the working channel. At this time, if the working channel is normal, the services are transiently interrupted. If the working channel is faulty, the services are interrupted until the working channel is restored to normal or the N+1 protection protocol is started.
Procedure
Step 1 In the NE Explorer, select the NE from the Object Tree and then choose Configuration > Link Configuration from the Function Tree.
A Task Collection
Step 2 Click the N+1 Protection tab. Step 3 Select the N+1 protection group and click Start Protocol or Stop Protocol. A dialog box is displayed, indicating that the operation is successful. Step 4 Click OK. Step 5 Click Query. ----End
A.6 Managing MSP

The OptiX RTN 620 supports ring MSP and linear MSP. A.6.1 Configuring Ring MSP If a ring network formed by STM-4 fibers is used and the services are discrete services, you can configure ring MSP to provide protection for the ring network. A.6.2 Configuring Linear MSP To protect the services carried by the optical fibers or STM-1e cables between two nodes, you can configure linear MSP. A.6.3 Querying the Status of Ring MSP You can know the current status of a ring MSP group by querying the status of ring MSP. A.6.4 Querying the Status of Linear MSP You can know the current status of a linear MSP group by querying the status of linear MSP. A.6.5 Performing Ring MSP Switching You can perform an external switching on a ring MSP protection group by performing a ring MSP switching. A.6.6 Performing Linear MSP Switching You can perform an external switching on a linear MSP protection group by performing a linear MSP switching. A.6.7 Starting/Stopping the Ring MSP Protocol If you first stop the ring MSP protocol and then start it, the ring MSP status can be restored to the initial state. A.6.8 Starting/Stopping the Linear MSP Protocol If you first stop the linear MSP protocol and then start it, the linear MSP status can be restored to the initial state.
A.6.1 Configuring Ring MSP

If a ring network formed by STM-4 fibers is used and the services are discrete services, you can configure ring MSP to provide protection for the ring network.
Prerequisite
l l
A-72
The NE user must have the authority of Operation Level or higher. The boards where the working unit and the protection unit are located must be configured.
A Task Collection

Web LCT
Context
When an unprotected service is converted into a ring MSP service by configuring the ring MSP, the original services are not interrupted.
Procedure
Step 1 In the NE Explorer, select the NE from the Object Tree and then choose Configuration > Ring MS from the Function Tree. Step 2 Click New. A dialog box is displayed, indicating that the service will change to extra service and protection switching will interrupt the service in the protection timeslot. Step 3 Click OK. Then, the Create a Ring Multiplex Section dialog box is displayed. Step 4 Set the attributes of the ring MSP protection group according to the service planning information. Step 5 Set the slot mapping relation. 1. 2. 3. Set Local Node, West Node, and East Node according to the service planning information. In Select Mapping Direction, select West Line 1. In Select Mapping Mode, select the line interface to which the working channel corresponds and click 4. 5. .
In Select Mapping Direction, select East Line 1. In Select Mapping Mode, select the line interface to which the protection channel corresponds and click .
Issue 05 (2010-10-30)
A-73
A Task Collection
Example
Table A-24 Parameters Parameter Level Protection Type Local Node Value Range STM-4 2-fiber Bidirectional Multiplex Section 0 to 15 Default Value STM-4 2-fiber Bidirectional Multiplex Section 0 Description This parameter is always set to STM-4. This parameter is always set to 2-fiber Bidirectional Multiplex Section. l This parameter specifies the node ID allocated to the local NE. l The node ID of each NE must be unique. West Node 0 to 15 0 This parameter specifies the node ID that is allocated to the NE to which the west line board of the local NE is connected. This parameter specifies the node ID that is allocated to the NE to which the east line board of the local NE is connected.
East Node
0 to 15
A-74
Issue 05 (2010-10-30)
A Task Collection
Parameter WTR Time(s)
Default Value 600
Description l When the time after the former working channel is restored to normal reaches the set value of this parameter, a revertive switching occurs. l It is recommended that this parameter takes the default value.
SD enable
Enabled Disabled
Enabled
l When SD enable is set to Enabled, the B2_SD alarm is considered as a switching condition. l It is recommended that this parameter takes the default value.
Protocol Type
New Protocol Restructure Protocol
New Protocol
l The new protocol is more mature than the restructure protocol but the restructure protocol is in better compliance with the standards than the new protocol. l It is recommended that you select the new protocol. When the OptiX equipment is interconnected with the third-party equipment, select the restructure protocol if an interconnection problem occurs when the new protocol is adopted.
Slot Mapping Relation
It is recommended that you map the line interface of the SL4 board in slot 6 as West Line 1 and map the line interface of the SL4 board in slot 8 as East Line 1. l If you select Map as VC4, the VC-4 is considered as the unit of the settings in the slot mapping relation. l It is recommended that this parameter takes the default value.
Map as VC4
Not selected
NOTE
The protection groups of the NEs that form a ring multiplex section must be set with the same attributes except Local Node, West Node, and East Node.
Follow-up Procedure
In the case of a two-fiber bidirectional MSP ring, you need to configure bidirectional crossconnections between the services and the timeslots of the working channel (the first half of the timeslots of the line port) later. If extra services need to be transmitted, you need to configure bidirectional cross-connections between the extra services and the timeslots of the protection channel (the second half of the timeslots of the line port).
A Task Collection
A.6.2 Configuring Linear MSP

To protect the services carried by the optical fibers or STM-1e cables between two nodes, you can configure linear MSP.
Prerequisite
l l The NE user must have the authority of Operation Level or higher. The boards where the working unit and the protection unit are located must be configured.

Web LCT
Context
When an unprotected service is converted into a linear MSP service by configuring the linear MSP, the original services are not interrupted.
Procedure
Step 1 In the NE Explorer, select the NE from the Object Tree and then choose Configuration > Linear MS from the Function Tree. Step 2 Click Create. Then, the Create a Linear Multiplex Section dialog box is displayed. Step 3 Set the attributes of the linear MSP group.
NOTE
When Protection Type is set to 1:N Protection, a dialog box is displayed, indicating that the service will change to extra service and protection switching will interrupt the service in the protection timeslot.
Step 4 Set the slot mapping relation. 1. 2. In Select Mapping Direction, select West Working Unit. In Select Mapping Mode, select the line interface to which the working channel corresponds and click 3. 4. .
In Select Mapping Direction, select West Protection Unit. In Select Mapping Mode, select the line interface to which the protection channel corresponds and click .
A-76
Issue 05 (2010-10-30)
A Task Collection
Example
Table A-25 Parameters Parameter Protection Type Value Range 1+1 Protection 1:N Protection Switching Mode l Single-Ended Switching, Dual-Ended Switching (1+1 protection) l Dual-Ended Switching (1:N protection) l Single-Ended Switching (1 +1 protection) l Dual-Ended Switching (1:N protection) Default Value 1+1 Protection Description l In single-ended mode, if the services on the working channels in a certain direction need to be switched, only the services on the working channels in the direction are switched to the protection channels. l In dual-ended mode, the services on the working channels in two directions are switched to the protection channels. l When Revertive Mode is set to Revertive, the NE that is in the switching state releases the switching and enables the former working channel to return to the normal state some time after the former working channel is restored to normal. l When Revertive Mode is set to NonRevertive, the NE that is in the
A-77
Issue 05 (2010-10-30)
A Task Collection
Parameter Revertive Mode
Value Range l Non-Revertive, Revertive (1+1 protection) l Revertive (1:N protection)
Default Value l Non-Revertive (1+1 protection) l Revertive (1:N protection)
Description switching state keeps the current state unchanged unless another switching occurs even though the former working channel is restored to normal. l When extra services need to be transmitted or several working channels exist, select 1:N protection. l In the case of other situations, it is recommended that you select the 1+1 single-ended and non-revertive mode.
WTR Time(s)
300 to 720
600
l This parameter is valid only when Revertive Mode is set to Revertive. l When the time after the former working channel is restored to normal reaches the set wait-to-restore (WTR) time, a revertive switching occurs. l It is recommended that this parameter takes the default value.
SD enable
Enabled Disabled
Enabled
l When SD enable is set to Enabled, the B2_SD alarm is considered as a switching condition. l It is recommended that this parameter takes the default value.
Protocol Type
New Protocol Restructure Protocol
New Protocol
l The new protocol is more mature than the restructure protocol but the restructure protocol is in better compliance with the standards than the new protocol. l It is recommended that you select the new protocol. When the OptiX equipment is interconnected with the third-party equipment, select the restructure protocol if an interconnection problem occurs when the new protocol is adopted.
A-78
Issue 05 (2010-10-30)
A Task Collection
Parameter SD/SF PRI Switching Tag
Value Range High Priority Low Priority
Default Value High Priority
Description l When this parameter is set to High priority, "1101" and "1011" are used as an SF/SD switching request. l When this parameter is set to Low priority, "1100" and "1010" are used as an SF/SD switching request. l It is recommended that this parameter takes the default value.
Switching Mode Indication
Not indicated Indicated
Not indicated
l When this parameter is set to Indicated, the MSP protocol uses K2 (bit 6 to bit 8) to indicate the switching mode (that is, uses code "100" to indicate the single-ended mode and code "101" to indicate the dual-ended mode). l When this parameter is set to Not indicated, the MSP protocol does not indicate the switching mode. l It is recommended that this parameter takes the default value.
Slot Mapping Relation
l In the case of 1+1 protection, only one line interface can be mapped as West Working Unit; in the case of 1:N protection, a maximum of three line interfaces can be mapped as West Working Unit. l Only one line interface can be mapped as West Protection Unit. l Ensure that the line interface that is mapped as West Protection Unit and the line interface that is mapped as West Working Unit are not on the same board, if possible.
NOTE
Ensure that the MSP groups of the equipment at both ends of the linear multiplex section are set with the same attributes.
Follow-up Procedure
l In the case of 1:N linear MSP, you need to configure bidirectional cross-connections between the services and the working channels later. If extra services need to be transmitted, it is necessary to configure bidirectional cross-connections between the extra services and the protection channels.
Issue 05 (2010-10-30)
A-79
A Task Collection
In the case of 1+1 linear MSP, you need to configure unidirectional cross-connections between the services and the protection channels, in addition to configuring the bidirectional cross-connections between the services and the working channels.
A.6.3 Querying the Status of Ring MSP

You can know the current status of a ring MSP group by querying the status of ring MSP.
Prerequisite
l l The NE user must have the authority of Operation Level or higher. A ring MSP group must be configured.

Web LCT
Procedure
Step 1 In the NE Explorer, select the NE from the Object Tree and then choose Configuration > Ring MS from the Function Tree. Step 2 Select the ring MSP group to be queried in the Ring MS tab page. Step 3 Choose Query > Query Protection Group. ----End
A.6.4 Querying the Status of Linear MSP

You can know the current status of a linear MSP group by querying the status of linear MSP.
Prerequisite
l l The NE user must have the authority of Operation Level or higher. A linear MSP group must be configured.

Web LCT
Procedure
Step 1 In the NE Explorer, select the NE from the Object Tree and then choose Configuration > Linear MS from the Function Tree. Step 2 Select the linear MSP group to be queried in the Linear MS tab page. Step 3 Choose Query > Query Protection Group. ----End
A Task Collection
A.6.5 Performing Ring MSP Switching

You can perform an external switching on a ring MSP protection group by performing a ring MSP switching.
Prerequisite
l l The NE user must have the authority of System Level or higher. A ring MSP group must be configured.

Web LCT
Procedure
Step 1 In the NE Explorer, select the NE from the Object Tree and then choose Configuration > Ring MS from the Function Tree. Step 2 In Slot Mapping Relation, select the working unit or the protection unit of a protection group. Right-click the selected unit and select the required switching mode from the shortcut menu. A dialog box is displayed, indicating that the operation is successful. Step 3 Click Yes. Step 4 Click Query > Query Switching Status. ----End
A.6.6 Performing Linear MSP Switching

You can perform an external switching on a linear MSP protection group by performing a linear MSP switching.
Prerequisite
l l The NE user must have the authority of System Level or higher. A linear MSP group must be configured.

Web LCT
Procedure
Step 1 In the NE Explorer, select the NE from the Object Tree and then choose Configuration > Linear MS from the Function Tree. Step 2 In Slot Mapping Relation, select the working unit or the protection unit of a protection group. Right-click the selected unit and select the required switching mode from the shortcut menu. A dialog box is displayed, indicating that the operation is successful. Step 3 Click Yes.
A Task Collection
Step 4 Click Query > Query Switching Status. ----End
A.6.7 Starting/Stopping the Ring MSP Protocol

If you first stop the ring MSP protocol and then start it, the ring MSP status can be restored to the initial state.
Prerequisite
l l The NE user must have the authority of System Level or higher. A ring MSP group must be configured.

Web LCT
Precautions
l l Stopping the ring MSP protocol causes the failure of the ring MSP. When services are switched onto the protection channel, stopping the ring MSP protocol causes the services to switch back to the working channel. At this time, if the working channel is normal, the services are transiently interrupted. If the working channel is faulty, the services are interrupted until the working channel is restored to normal or the ring MSP protocol is started.
Procedure
Step 1 In the NE Explorer, select the NE from the Object Tree and then choose Configuration > Ring MS from the Function Tree. Step 2 Select the ring MSP group and click Start Protocol or Stop Protocol. A dialog box is displayed, indicating that the operation is successful. Step 3 Click OK. Step 4 Click Query. ----End
A.6.8 Starting/Stopping the Linear MSP Protocol

If you first stop the linear MSP protocol and then start it, the linear MSP status can be restored to the initial state.
Prerequisite
l l The NE user must have the authority of System Level or higher. A linear MSP group must be configured.

Web LCT
A Task Collection
Precautions
l l Stopping the linear MSP protocol causes the failure of the linear MSP. When services are switched onto the protection channel, stopping the linear MSP protocol causes the services to switch back to the working channel. At this time, if the working channel is normal, the services are transiently interrupted. If the working channel is faulty, the services are interrupted until the working channel is restored to normal or the linear MSP protocol is started.
Procedure
Step 1 In the NE Explorer, select the NE from the Object Tree and then choose Configuration > Linear MS from the Function Tree. Step 2 Select the linear MSP group and click Start Protocol or Stop Protocol. A dialog box is displayed, indicating that the operation is successful. Step 3 Click OK. Step 4 Click Query. ----End
A.7 Managing TDM Services

TDM services include SDH services and PDH services. A.7.1 Creating Cross-Connections of Point-to-Point Services In a cross-connection of point-to-point services, one service source corresponds to one service sink. A.7.2 Creating Cross-Connections for SNCP Services The cross-connection of SNCP services is a cross-connection that a working source and a protection source correspond to a service sink. A.7.3 Inserting TU_AIS This section describes how to configure TU_AIS insertion so that the IFH2 board inserts TU_AIS back after detecting E1_AIS on an E1 channel. You need to configure TU_AIS insertion on E1 channels on the IFH2 board when the IFH2 board and IF1 board function as the east interface board and west interface board, respectively, of an SNCP ring and pass-through services are configured between the interface boards. A.7.4 Setting the Automatic Switching Conditions of SNCP Services In the case of the SNCP services at the VC-4 level, you can set certain alarms as the automatic switching conditions. A.7.5 Deleting Cross-Connections When a service is not used, you can delete the cross-connections of this service to release the corresponding resources. A.7.6 Converting Normal Services into SNCP Services After converting the normal services into the SNCP services, you can convert the unidirectional cross-connection of the normal services into the unidirectional cross-connection in the receive direction of the SNCP services. A.7.7 Converting SNCP Services to Normal Services
A Task Collection
After converting the SNCP services into the normal services, you can convert the SNCP crossconnection in the receive direction into the unidirectional cross-connection of the normal services. A.7.8 Querying TDM Services You can learn about the TDM services that are configured for an NE by querying TDM services. A.7.9 Performing SNCP Protection You can perform external switching on SNCP services by performing this operation. A.7.10 Querying the Protection Status of SNCP Services You can know the current information of an SNCP service by querying the protection status of SNCP services.
A.7.1 Creating Cross-Connections of Point-to-Point Services

In a cross-connection of point-to-point services, one service source corresponds to one service sink.
Prerequisite
l l The NE user must have the authority of Operation Level or higher. The boards where the source and the sink are located must be configured.

Web LCT
Procedure
Step 1 In the NE Explorer, select the NE from the Object Tree and then choose Configuration > CrossConnection Configuration from the Function Tree. Step 2 Optional: Click Scheme to change the VC-12 timeslot numbering policy used by the crossconnection.
Step 3 Click New. Then, the Create SDH Service dialog box is displayed. Step 4 Configure the cross-connections of the service.
A-84
Issue 05 (2010-10-30)
A Task Collection
Step 5 Click OK.

NOTE
l When you create a cross-connection whose source or sink is the timeslots of an IF board, the creation may fail due to the limited number of licenses. l The calculation of the required number of licenses is based on the total number of service timeslots of all the IF boards that are involved in cross-connections. In the case of the cross-connections of VC-3 or VC-4 services, the VC-3 or VC-4 services need to be converted into E1 services that have the same capacity. For example, the cross-connections of one E3 service from a PL3 board to an IF board require the number of licenses that are used for 21xE1. One VC-3 pass-through service between two IF boards requires the number of licenses that are used for 42xE1. The 8xE1 SNCP services from two IF boards to one PO1 board require the number of licenses that are used for 16xE1.
----End
Example
Table A-26 Parameters Parameter Level Value Range VC12 VC3 VC4 Default Value VC12 Description l This parameter specifies the level of the cross-connections. l In the case of E1 services or data services in bound VC-12 paths, set this parameter to VC12. l In the case of E3/T3 services or data services in bound VC-3 paths, set this parameter to VC3. l If all the services in a VC-4 path are passed through the NE, set this parameter to VC4.
Issue 05 (2010-10-30)
A-85
A Task Collection
Parameter Direction
Value Range Unidirectional Bidirectional
Default Value Bidirectional
Description l When this parameter is set to Unidirectional, create the crossconnections from the service source to the service sink only. l When this parameter is set to Bidirectional, create the crossconnections from the service source to the service sink and from the service sink to the service source. l It is recommended that you set this parameter to Bidirectional.
Source Source Port Source VC4
This parameter specifies the slot where the service source is located. This parameter specifies the interface where the service source is located. This parameter specifies the number of the VC-4 path where the service source is located. l This parameter indicates the timeslot range corresponding to the service source. l This parameter can be set to a value or multiple values. When this parameter is set to multiples values, use "," to separate each value and use "-" to indicate sequential numbers. For example, "1,3-6" indicates 1, 3, 4, 5, and 6. l If the IF board works in the PDH mode, E1s/E3s 1-n transmitted over radio correspond to VC-12/VC-3 timeslots 1n. Ports 1-n of E1 interface boards and E3/T3 interface boards correspond to VC-12/VC-3 timeslots 1-n. l The E1s 1-75 transmitted on the IFH2 board correspond to the 1-63 VC-12 timeslots of the first VC-4 and the 1-12 VC-12 timeslots of the second VC-4.
Source Timeslot Range(e.g.1,3-6)
Sink Sink Port Sink VC4
This parameter specifies the slot where the service ink is located. This parameter specifies the port where the service sink is located. This parameter specifies the number of the VC-4 where the service sink is located.
A-86
Issue 05 (2010-10-30)
A Task Collection
Parameter Sink Timeslot Range(e.g.1,3-6)
Value Range -
Default Value -
Description l This parameter indicates the timeslot range corresponding to the service sink. l This parameter can be set to a value or multiple values. When this parameter is set to multiples values, use "," to separate each value and use "-" to indicate sequential numbers. For example, "1,3-6" indicates 1, 3, 4, 5, and 6. l If the IF board works in the PDH mode, E1s/E3s 1-n transmitted over radio correspond to VC-12/VC-3 timeslots 1n. Ports 1-n of E1 interface boards and E3/T3 interface boards correspond to VC-12/VC3 timeslots 1-n. l The E1s 1-75 transmitted on the IFH2 board correspond to the 1-63 VC-12 timeslots of the first VC-4 and the 1-12 VC-12 timeslots of the second VC-4.
A.7.2 Creating Cross-Connections for SNCP Services

The cross-connection of SNCP services is a cross-connection that a working source and a protection source correspond to a service sink.
Prerequisite
l l The NE user must have the authority of Operation Level or higher. The boards where the source and the sink are located must be configured.

Web LCT
Procedure
Step 1 In the NE Explorer, select the NE from the Object Tree and then choose Configuration > CrossConnection Configuration from the Function Tree. Step 2 Optional: Click Scheme to change the VC-12 timeslot numbering policy used by the crossconnection.
Step 3 Click Create SNCP. The Create SNCP Service dialog box is displayed.
A Task Collection
Step 4 Set the attributes of the SNCP protection group and the slot mapping relation of the SNCP service.
Step 5 Click OK.

NOTE
l When you create a cross-connection whose source or sink is the timeslots of an IF board, the creation may fail due to the limited number of licenses. l The calculation of the required number of licenses is based on the total number of service timeslots of all the IF boards that are involved in cross-connections. In the case of the cross-connections of VC-3 or VC-4 services, the VC-3 or VC-4 services need to be converted into E1 services that have the same capacity. For example, the cross-connections of one E3 service from a PL3 board to an IF board require the number of licenses that are used for 21xE1. One VC-3 pass-through service between two IF boards requires the number of licenses that are used for 42xE1. The 8xE1 SNCP services from two IF boards to one PO1 board require the number of licenses that are used for 16xE1.
----End
Example
Table A-27 Parameters Parameter Service Type Value Range SNCP Default Value SNCP Description -
A-88
Issue 05 (2010-10-30)
A Task Collection
Parameter Level
Value Range VC12 VC3 VC4
Default Value VC12
Description l This parameter specifies the level of the cross-connections. l If the service is an E1 service or a data service that is bound with VC-12 paths, set this parameter to VC12. l If the service is an E3/T3 service or a data service that is bound with VC-3 paths, set this parameter to VC3. l If all the services in a VC-4 pass through the NE, set this parameter to VC4.
Revertive Mode
Non-revertive Revertive
l When this parameter is set to Revertive, the NE that is in the switching state releases the switching and causes the former working channel to return to the working state some time after the former working channel is restored to normal. l When this parameter is set to NonRevertive, the NE that is in the switching state keeps the state of the former working channel unchanged even though the former working channel is restored to normal unless another switching occurs. l It is recommended that you set this parameter to Revertive.
Direction
Unidirectional Bidirectional
l When this parameter is set to Unidirectional, only the crossconnections in the SNCP receive direction are created. l When this parameter is set to Bidirectional, both the crossconnections in the SNCP receive direction and the cross-connections in the SNCP transmit direction are created. l It is recommended that you set this parameter to Bidirectional.
Issue 05 (2010-10-30)
A-89
A Task Collection
Parameter Hold-off Time (100ms)
Default Value 0
Description l When a line fault occurs, an NE can perform SNCP switching after a delay of time to prevent the situation where the NE performs SNCP switching and other protection switching at the same time. This parameter specifies the duration of the delay. l When SNCP coexists with other protection configurations, it is recommended that this parameter takes the default value.
WTR Time(s)
300 to 720
600
l This parameter is valid only when Revertive Mode is set to Revertive. l When the time after the former working channel is restored to normal reaches the set wait-to-restore (WTR) time, a revertive switching occurs. l It is recommended that this parameter takes the default value.
Source Source Port Source VC4 Source Timeslot Range(e.g.1,3-6)
This parameter specifies the slot where the service source is located. This parameter specifies the port where the service source is located. This parameter specifies the number of the VC-4 where the service source is located. l This parameter specifies the timeslot range to which the service source corresponds. l You can set this parameter to a number or several numbers. When you set this parameter to several numbers, use "," to separate these discrete values and use "-" to indicate continuous numbers. For example, "1, 3-6" indicates numbers 1, 3, 4, 5, and 6. l In the case of an IF board that works in PDH mode, the first to the nth E1s/E3s transmitted by microwaves correspond to the first to the nth VC-12/VC-3 timeslots respectively. Similarly, the first to the nth ports of an E1 interface board or an E3/T3 interface board correspond to the first to the nth VC-12/ VC-3 timeslots respectively.
A-90
Issue 05 (2010-10-30)
A Task Collection
Parameter Sink Sink Port Sink VC4 Sink Timeslot Range(e.g.1,3-6)
Value Range -
Default Value -
Description This parameter specifies the slot where the service ink is located. This parameter specifies the port where the service sink is located. This parameter specifies the number of the VC-4 where the service sink is located. l This parameter specifies the timeslot range to which the service sink corresponds. l You can set this parameter to a number or several numbers. When you set this parameter to several numbers, use "," to separate these discrete values and use "-" to indicate continuous numbers. For example, "1, 3-6" indicates numbers 1, 3, 4, 5, and 6. l In the case of an IF board that works in PDH mode, the first to the nth E1s/E3s transmitted by microwaves correspond to the first to the nth VC-12/VC-3 timeslots respectively. Similarly, the first to the nth ports of an E1 interface board or an E3/T3 interface board correspond to the first to the nth VC-12/ VC-3 timeslots respectively.
Follow-up Procedure
If Direction is set to Unidirectional, the cross-connection only in the SNCP receive direction is created. Hence, you need to configure a unidirectional cross-connection between the service and the working trail, and later, a unidirectional cross-connection between the service and the protection trail.
A.7.3 Inserting TU_AIS

This section describes how to configure TU_AIS insertion so that the IFH2 board inserts TU_AIS back after detecting E1_AIS on an E1 channel. You need to configure TU_AIS insertion on E1 channels on the IFH2 board when the IFH2 board and IF1 board function as the east interface board and west interface board, respectively, of an SNCP ring and pass-through services are configured between the interface boards.
Prerequisite
l l
Issue 05 (2010-10-30)
The NE user must have the authority of Operation Level or higher. The IFH2 board must be added in the Slot Layout.
A Task Collection

Web LCT
Procedure
Step 1 In the NE Explorer, select the IFH2 board from the Object Tree and then choose Alarm > Triggered Alarm Insertion from the Function Tree. Step 2 Select the E1 channels on the IFH2 board that are involved in the SNCP and then set Insert TUAIS to E1AIS to Enable. Step 3 Click Apply. ----End
Parameters
Parameter Port E1 Channel Insert TUAIS to E1AIS Value Range 1 to 75 Enable, Disabled Default Value Disabled Description This parameter displays the slot of the IFH2 board and the number of the IF interface. This parameter displays the numbers of the E1 channels on the IFH2 board. When this parameter is set to Enable, the E1 channel inserts TU_AIS back after detecting E1_AIS.
A.7.4 Setting the Automatic Switching Conditions of SNCP Services

In the case of the SNCP services at the VC-4 level, you can set certain alarms as the automatic switching conditions.
Prerequisite
l l The NE user must have the authority of Operation Level or higher. An SNCP protection group at the VC-4 level must be configured.

Web LCT
Procedure
Step 1 In the NE Explorer, select the NE from the Object Tree and then choose Configuration > SNCP Service Control from the Function Tree. Step 2 Select the SNCP protection group. Double-click Initiation Condition to which the working service corresponds.
A Task Collection
The Initiation Condition dialog box is displayed. Step 3 Select SD switching conditions. Click OK.
Step 4 Select the SNCP protection group. Double-click Initiation Condition to which the protection service corresponds. The Initiation Condition dialog box is displayed. Step 5 Repeat step Step 3. Step 6 Click Apply. A dialog box is displayed, prompting whether to perform the switching. Step 7 Click Yes. ----End
Example
Table A-28 Parameters Parameter HPUNEQ Value Range Selected Not selected Default Value Not selected Description l When this item is selected, the SNCP service considers the HP_UNEQ alarm as an SD switching condition. l It is recommended that this parameter takes the default value. HPTIM Selected Not selected Not selected l When this item is selected, the SNCP service considers the HP_TIM alarm as an SD switching condition. l It is recommended that this parameter takes the default value. B3SD Selected Not selected Not selected l When this item is selected, the SNCP service considers the B3_SD alarm as an SD switching condition. l It is recommended that this parameter takes the default value. B3EXC Selected Not selected Not selected l When this item is selected, the SNCP service considers the B3_EXC alarm as an SD switching condition. l It is recommended that this parameter takes the default value.
Issue 05 (2010-10-30)
A-93
A Task Collection
NOTE
It is recommended that you set Initiation Condition of the working service to be the same as Initiation Condition of the protection service.
A.7.5 Deleting Cross-Connections

When a service is not used, you can delete the cross-connections of this service to release the corresponding resources.
Prerequisite
l l The NE user must have the authority of Operation Level or higher. The cross-connections of the service must be configured and the service is notused.

Web LCT
Procedure
Step 1 In the NE Explorer, select the NE from the Object Tree and then choose Configuration > CrossConnection Configuration from the Function Tree. Step 2 Click Query. Step 3 Select the cross-connection of the point-to-point service that needs to be deleted in CrossConnection. Step 4 Click Delete. Then, a dialog box is displayed. Click OK. Step 5 Click Query. At this time, the cross-connection of the point-to-point service is already deleted. ----End
A.7.6 Converting Normal Services into SNCP Services

After converting the normal services into the SNCP services, you can convert the unidirectional cross-connection of the normal services into the unidirectional cross-connection in the receive direction of the SNCP services.
Prerequisite
l l The NE user must have the authority of Operation Level or higher. The unidirectional cross-connection of normal services must be configured and the source of the cross-connection must be a line board.

Web LCT
A Task Collection
Context
When this task is performed to convert a normal service into an SNCP service, the original services are not interrupted.
Procedure
Step 1 In the NE Explorer, select the NE from the Object Tree and then choose Configuration > CrossConnection Configuration from the Function Tree. Step 2 Select the bidirectional cross-connection of the normal service in Cross-connection. Then, right-click and choose Expand from the shortcut menu. Step 3 Select the unidirectional cross-connection of the normal service in Cross-connection. Then, right-click and choose Convert to SNCP from the shortcut menu. Then, the Convert to SNCP service dialog box is displayed. Step 4 Set the attributes of the SNCP protection group and the slot mapping relation of the SNCP service.
Issue 05 (2010-10-30)
A-95
A Task Collection
Example
Table A-29 Parameters Parameter Revertive Mode Value Range Non-revertive Revertive Default Value Revertive Description l When this parameter is set to Revertive, the NE that is in the switching state releases the switching and causes the former working channel to return to the working state some time after the former working channel is restored to normal. l When this parameter is set to NonRevertive, the NE that is in the switching state keeps the state of the former working channel unchanged even though the former working channel is restored to normal unless another switching occurs. l It is recommended that you set this parameter to Revertive. Hold-off Time (100ms) 0 to 100 0 l When a line fault occurs, an NE can perform SNCP switching after a delay of time to prevent the situation where the NE performs SNCP switching and other protection switching at the same time. This parameter specifies the duration of the delay. l When SNCP coexists with other protection configurations, it is recommended that this parameter takes the default value. WTR Time(s) 300 to 720 600 l This parameter is valid only when Revertive Mode is set to Revertive. l When the time after the former working channel is restored to normal reaches the set wait-to-restore (WTR) time, a revertive switching occurs. l It is recommended that this parameter takes the default value. Source Port Source VC4 This parameter specifies the port where the service source is located. This parameter specifies the number of the VC-4 where the service source is located.
A-96
Issue 05 (2010-10-30)
A Task Collection
Parameter Source Timeslot Range(e.g.1,3-6)
Value Range -
Default Value -
Description l This parameter specifies the timeslot range to which the service source corresponds. l You can set this parameter to a number or several numbers. When you set this parameter to several numbers, use "," to separate these discrete values and use "-" to indicate continuous numbers. For example, "1, 3-6" indicates numbers 1, 3, 4, 5, and 6. l In the case of an IF board that works in PDH mode, the first to nth E1s/E3s transmitted by microwaves correspond to the first to nth VC-12/VC-3 timeslots respectively. Similarly, the first to nth ports of an E1 interface board or an E3/ T3 interface board correspond to the first to nth VC-12/VC-3 timeslots respectively.
Sink Port Sink VC4 Sink Timeslot Range(e.g.1,3-6)
This parameter specifies the port where the service sink is located. This parameter specifies the number of the VC-4 where the service sink is located. l This parameter specifies the timeslot range to which the service sink corresponds. l You can set this parameter to a number or several numbers. When you set this parameter to several numbers, use "," to separate these discrete values and use "-" to indicate continuous numbers. For example, "1, 3-6" indicates numbers 1, 3, 4, 5, and 6. l In the case of an IF board that works in the PDH mode, the first to nth E1s/E3s transmitted by microwaves correspond to the first to nth VC-12/VC-3 timeslots respectively. Similarly, the first to nth ports of an E1 interface board or an E3/ T3 interface board correspond to the first to nth VC-12/VC-3 timeslots respectively.
Follow-up Procedure
The SNCP service after the conversion is the SNCP service only in the receive direction. Later, you need to configure a unidirectional cross-connection between the service and the working
A Task Collection
trail, and a unidirectional cross-connection between the service and the protection trail. The normal service can be converted into the SNCP service both in the receive direction and the transmit direction only after the configuration.
A.7.7 Converting SNCP Services to Normal Services

After converting the SNCP services into the normal services, you can convert the SNCP crossconnection in the receive direction into the unidirectional cross-connection of the normal services.
Prerequisite
l l l The NE user must have the authority of Operation Level or higher. The current service is transmitted on the working path. The SNCP cross-connection in the receive direction must be configured.

Web LCT
Context
When this task is performed to convert an SNCP service into a normal service, the original services are not interrupted.
Procedure
Step 1 In the NE Explorer, select the NE from the Object Tree and then choose Configuration > CrossConnection Configuration from the Function Tree. Step 2 In the Auto-Created Cross-Connection pane, select the cross-connection and click To Normal. Step 3 Choose Working or Protection from the displayed menu. l l To convert the cross-connection into a cross-connection between the working source and the service sink, choose Working. To convert the cross-connection into a cross-connection between the protection source and the service sink, choose Protection.
----End
Follow-up Procedure
You need to delete the unidirectional cross-connection between the service and the working path or the unidirectional cross-connection between the service and the protection path. The SNCP service can be converted into the normal service both in the receive direction and the transmit direction only after the deletion.
A.7.8 Querying TDM Services

You can learn about the TDM services that are configured for an NE by querying TDM services.
A Task Collection
Prerequisite

Web LCT
Procedure
Step 1 In the NE Explorer, select the NE from the Object Tree and then choose Configuration > CrossConnection Configuration from the Function Tree. Step 2 Click Query. ----End
A.7.9 Performing SNCP Protection

You can perform external switching on SNCP services by performing this operation.
Prerequisite
l l The NE user must have the authority of System Level or higher. The SNCP protection group must be configured.

Web LCT
Procedure
Step 1 In the NE Explorer, select the NE from the Object Tree and then choose Configuration > SNCP Service Control from the Function Tree. Step 2 Select the SNCP protection group. Right-click on the selected group and select the required switching mode. A dialog box is displayed, indicating that the operation is successful. Step 3 Click OK. Step 4 Click Query. ----End
A.7.10 Querying the Protection Status of SNCP Services

You can know the current information of an SNCP service by querying the protection status of SNCP services.
Prerequisite
l l
Issue 05 (2010-10-30)
The NE user must have the authority of Operation Level or higher. The SNCP protection group must be configured.
A Task Collection

Web LCT
Procedure
Step 1 In the NE Explorer, select the NE from the Object Tree and then choose Configuration > SNCP Service Control from the Function Tree. Step 2 Select the SNCP group to be queried in the SNCP Service Control tab page. Step 3 Click Query. ----End
A.8 Managing Clocks

To ensure clock synchronization between transmission nodes on a transport network, you need to manage the NE clocks. A.8.1 Configuring Clock Sources This section describes how to configure clock sources according to the planned clock synchronization scheme so that all the NEs on the network trace the same clock. A.8.2 Configuring Protection for Clock Sources This section describes how to configure protection for clock sources. In the case of simple networks such as chain networks, you need not configure protection for the clock sources. The clock sources are protected according to the clock source priority table. In the case of complex clock networks such as ring networks or tangent rings and intersecting rings deriving from ring networks, protection for the clock sources need to be implemented by means of the standard SSM protocol or extended SSM protocol. A.8.3 Modifying Clock Output Parameters The NE outputs the 2 Mbit/s external clock regardless of the clock quality. A.8.4 Changing Conditions for Clock Source Switching You need to change the default conditions for clock source switching of the NE for special purposes. A.8.5 Modifying the Recovery Parameter of the Clock Source In the case of the special requirements, you can modify the recovery parameter of the clock source. A.8.6 Querying the Clock Synchronization Status You can check the current clock synchronization status of an NE by querying the clock synchronization status.
A.8.1 Configuring Clock Sources

This section describes how to configure clock sources according to the planned clock synchronization scheme so that all the NEs on the network trace the same clock.
Prerequisite
l
A-100

A Task Collection
The PXC board and the boards that input and output clock sources must be added in the Slot Layout.

Web LCT
Procedure
Step 1 In the NE Explorer, select the NE from the Object Tree and then choose Configuration > Clock > Clock Source Priority from the Function Tree. Step 2 Click Create. Then, the Add Clock Source dialog box is displayed. Step 3 Select the clock sources.
TIP
By pressing the Ctrl key on the keyboard, you can select multiple clock sources at one time.
Step 4 Click OK. Step 5 Optional: Repeat steps Step 2 to Step 4 to add other clock sources. Step 6 Optional: Select a clock source and click clock source. or to adjust the priority of a
The clock priorities levels are arranged in a descending order from the first row to the last row. The internal clock source is always of the lowest priority. Step 7 Optional: Set External Clock Source Mode and Synchronous Status Byte for the external clock sources.
Issue 05 (2010-10-30)
A-101
A Task Collection
Parameter Description
Parameter Clock Source Value Range Default Value Description l External clock source 1 indicates the external clock source from the interface on the PXC board in slot 1. External clock source 2 indicates the external clock source from the interface on the PXC board in slot 3. l IFH2-1(SDH) indicates the microwave clock source. l IFH2-2(ETH) indicates the clock source of the synchronous Ethernet. l The internal clock source is always of the lowest priority and indicates that the NE works in the free-run mode. l Determine the clock sources and the corresponding clock source priority levels according to the clock synchronization scheme. External Clock Source Mode 2 Mbit/s 2 MHz 2 Mbit/s l This parameter specifies the type of the external clock source signal. l Set this parameter depending on the external clock signal. The external clock signal is generally a 2 Mbit/s signal. Synchronous Status Byte SA4 to SA8 SA4 l This parameter is valid only when External Clock Source Mode is set to 2Mbit/s. l This parameter indicates which bit of the TS0 in odd frames of the external clock signal is used to transmit the SSM. l This parameter needs to be set only when the SSM or extended SSM is enabled. The external clock sources generally transmit the SSM over the SA4.
A.8.2 Configuring Protection for Clock Sources

This section describes how to configure protection for clock sources. In the case of simple networks such as chain networks, you need not configure protection for the clock sources. The clock sources are protected according to the clock source priority table. In the case of complex clock networks such as ring networks or tangent rings and intersecting rings deriving from ring
A Task Collection
networks, protection for the clock sources need to be implemented by means of the standard SSM protocol or extended SSM protocol.
Prerequisite
l l The NE user must have the authority of Operation Level or higher. The clock source priority table must be configured.
Procedure
Step 1 In the NE Explorer, select the NE from the Object Tree and then choose Configuration > Clock > Clock Subnet Configuration from the Function Tree. Step 2 Enable the clock protection protocol. 1. 2. Click the Clock Subnet tab. Enable the clock protection protocol and set the protocol parameters.
3. 1. 2.
Click Apply. Click the Clock Quality tab. Click the Clock Source Quality tab and set relevant parameters.
Step 3 Optional: Customize the clock quality.
3.
Click the Manual Setting of 0 Quality Level tab and set relevant parameters.
4. 1. 2.
Click Apply. Click the SSM Output Control tab. Set the SSM output interface.
Step 4 Set the SSM output interface.
Issue 05 (2010-10-30)
A-103
A Task Collection
3. 1. 2.
Click Apply. Click the Clock ID Status tab. Set the clock ID output interface.
Step 5 Optional: Set the clock ID output interface.
3.
Click Apply.
----End
A-104
Issue 05 (2010-10-30)
A Task Collection
Example
Table A-30 Parameter Description: Clock Subnet Setting_Clock Subnet Parameter Protection Status Value Range Start Extended SSM Protocol Start Standard SSM Protocol Stop SSM Protocol Default Value Stop SSM Protocol Description l The SSM protocol is a scheme used for synchronous management in an SDH network and indicates that the SSM is transmitted over the lower four bits of the S1 byte and can be exchanged between the nodes. The SSM protocol ensures that the equipment automatically select the clock source with the highest quality and highest priority, thus preventing clock mutual tracing. l The extended SSM protocol is the extension of the standard SSM protocol. It defines the unique ID for each clock source and uses the higher four bits of the S1 byte to pass the ID. The extended SSM protocol can be used to prevent the NEs from tracing their own clocks. l If third-party equipment exists on the ring network, enable the SSM protocol. If only OptiX equipment exists on the ring network and clock mutual tracing can be prevented through certain configurations of the clock sources, the SSM protocol can also be enabled. l If only OptiX equipment exists on the ring network, it is recommended that the extended SSM protocol is used. Affiliated Subnet 0 to 255 0 l This parameter is used when the clock subnet need to be created on the NMS. l The NEs that trace the same clock source should be allocated with the same clock subnet ID.
Issue 05 (2010-10-30)
A-105
A Task Collection
Parameter Clock Source ID
Value Range (None) 1 to 15
Default Value (None)
Description l This parameter is valid only when the SSM protocol is enabled. l Allocate the clock source ID for the following clock sources only: External clock source Internal clock source of the node that accesses the external clock sources Internal clock source of the joint node of a ring and a chain or the joint node of two rings Line clock source that enters the ring when the intra-ring line clock source is configured at the joint node of a ring and a chain or the joint node of two rings
Table A-31 Parameter Description: Clock Subnet Setting_Clock Quality Parameter Configuration Quality Value Range Automatic Extraction 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 Default Value Automatic Extraction Description This parameter specifies the quality level that is configured for the clock source. This function is required only in a special scenario or in a test. Generally, this parameter need not be set.
A-106
Issue 05 (2010-10-30)
A Task Collection
Parameter Manual Setting of 0 Quality Level
Value Range Do Not Use For Synchronization G.811 Reference Clock Between G.811 Reference Clock and G.812 Transit Clock G.812 Transit Clock Between G.812 Transit Clock and G. 812 Local Clock G.812 Local Clock Between G.812 Local Clock and Synchronization Equipment Source (SETS) SETS Clock Between Synchronization Equipment Timing Source(SETS) and Quality Unavailable
Default Value Do Not Use For Synchronization
Description This parameter specifies the clock quality whose level is manually set to zero. l Do Not Use For Synchronization: the notification information in the reverse direction of the selected synchronization clock source to prevent direct mutual locking of adjacent NEs l G.811 Reference Clock: the clock signal specified in ITU-T G.811 l Between G.811 Reference Clock and G.812 Transit Clock: lower than the quality level of the clock signal specified in ITU-T G.811 but higher than the quality level of the transit exchange clock signal specified in ITU-T G.812 l G.812 Transit Clock: the transit exchange clock signal specified in ITUT G.812 l Between G.812 Transit Clock and G. 812 Local Clock: lower than the quality level of the transit exchange clock signal specified in ITU-T G.812 but higher than the quality level of the local exchange clock signal specified in ITU-T G.812 l G.812 Local Clock: the local exchange clock signal specified in ITU-T G.812 l Between G.812 Local Clock and Synchronization Equipment Source (SETS): lower than the quality level of the local exchange clock signal specified in ITU-T G.812 but higher than the quality level of the clock signal of the SETS l SETS Clock: the clock signal of the SETS l Between Synchronization Equipment Timing Source(SETS) and Quality Unavailable: lower than the quality level of the clock signal of the SETS but higher than the quality level unavailable in the synchronous timing source
Issue 05 (2010-10-30)
A-107
A Task Collection
Table A-32 Parameter Description: Clock Subset Setting_SSM Output Control Parameter Control Status Value Range Enabled Disabled Default Value Enabled Description l This parameter is valid only when the SSM protocol or the extended SSM protocol is enabled. l This parameter specifies whether the SSM is output from the line interface. l When a line interface is connected to another NE on the same clock subnet, set this parameter to Enabled. In other cases, set this parameter to Disabled.
Table A-33 Parameter Description: Clock Subset Setting_Clock ID Enabling Status Parameter Enabled Status Value Range Enabled Disabled Default Value Enabled Description This parameter specifies whether the output signal from an interface contains the clock ID.
A.8.3 Modifying Clock Output Parameters

The NE outputs the 2 Mbit/s external clock regardless of the clock quality.
Prerequisite
l l The NE user must have the authority of Operation Level or higher. The PXC board must be added in the Slot Layout.

Web LCT
Precautions
In the case of OptiX RTN 620, external clock source 1 indicates the external clock from the PXC board in slot 1 and external clock source 2 indicates the external clock from the PXC board in slot 3.
Procedure
Step 1 In the NE Explorer, select the NE from the Object Tree and then choose Configuration > Clock > Phase-Locked Source Output by External Clock from the Function Tree. Step 2 Modify the clock output parameters.
A Task Collection
Parameter External Clock Output Mode Value Range 2 Mbit/s 2 MHz Default Value 2 Mbit/s Description l This parameter specifies the mode of the output clock. l This parameter needs to be set according to the requirements of the interconnected equipment. The external clock signal is generally a 2 Mbit/s signal. External Clock Output Timeslot ALL SA4 to SA8 ALL l This parameter is valid only when External Clock Output Mode is set to 2Mbit/s. l This parameter indicates which bit of the TS0 in odd frames of the output clock signal is used to transmit the SSM. l If this parameter is set to ALL, it indicates that all the bits of the TS0 are used to transmit the SSM. l It is recommended that this parameter takes the default value. External Source Output Threshold 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 2M Phase-Locked Source Fail Condition No Failure Condition AIS LOF AIS OR LOF No Failure Condition Threshold Disabled l This parameter specifies the lowest quality of the output clock. If the clock quality is lower than the value of this parameter, it indicates that the external clock source does not output any clock signal. l If this parameter is set to Threshold Disabled, it indicates that the external clock source always outputs the clock signal. l It is recommended that this parameter takes the default value. l This parameter specifies the failure condition of the 2 Mbit/s phase-locked clock source. l It is recommended that this parameter takes the default value.
Issue 05 (2010-10-30)
A-109
A Task Collection
Parameter 2M Phase-Locked Source Fail Action
Value Range Shut Down Output 2M Output S1 Byte Unavailable Send AIS
Default Value Shut Down Output
Description l This parameter is valid only when 2M Phase-Locked Source Fail Condition is not set to No Failure Condition. l This parameter specifies the operation of the 2 Mbit/s phase-locked loop (PLL) when the 2 Mbit/s phase-locked clock source meets the failure conditions. l It is recommended that this parameter takes the default value.
A.8.4 Changing Conditions for Clock Source Switching

You need to change the default conditions for clock source switching of the NE for special purposes.
Prerequisite
l l The NE user must have the authority of Operation Level or higher. The PXC board and the boards that input and output clock sources must be added in the Slot Layout.

Web LCT
Procedure
Step 1 In the NE Explorer, select the NE from the Object Tree and then choose Configuration > Clock > Clock Source Switching from the Function Tree. Step 2 Click the Clock Source Switching Condition tab. Step 3 Change the conditions for clock source switching.
Parameter AIS Alarm Generated Value Range No Yes Default Value No Description This parameter specifies the enabled status of switching conditions. If an AIS alarm is generated on an NE, the NE considers that the corresponding clock source fails.
Issue 05 (2010-10-30)
A-110
A Task Collection
Parameter B2-EXC Alarm Generated
Value Range No Yes
Default Value No
Description This parameter specifies the enabled status of switching conditions. If a B2-EXC alarm is generated on an NE, the NE considers that the corresponding clock source fails.
A.8.5 Modifying the Recovery Parameter of the Clock Source

In the case of the special requirements, you can modify the recovery parameter of the clock source.
Prerequisite
l l The NE user must have the authority of Operation Level or higher. The corresponding boards must be added in the Slot Layout.

Web LCT
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Clock > Clock Source Switching . Step 2 Click the Clock Source Reversion Parameter tab. Step 3 Set the recovery parameter of the clock source.
Issue 05 (2010-10-30)
A-111
A Task Collection
Example
Table A-34 Parameters Parameter Higher Priority Source Reversion Mode Value Range Auto-Revertive Non-Revertive Default Value Auto-Revertive Description l When the quality of a higher-priority clock source degrades, the NE automatically switches the clock source to a lower-priority clock source. If this parameter is set to Auto-Revertive, the NE automatically switches the clock source to the higher-priority clock source when this higher-priority clock source restores. If this parameter is set to Non-Revertive, the NE does not automatically switch the clock source to the higher-priority clock source when this higher-priority clock source restores. l Correct setting of Clock Source Switching Condition ensures the reliability of the clock source switching. To improve the clock quality, select Auto-Revertive. Otherwise, to prevent jitter of the clock, generally, it is recommended that you set this parameter to Non-Revertive. Clock Source WTR Time(min.) 0 to 12 5 l This parameter specifies the duration from the time when the clock source restoration is detected to the time when the clock source switching is triggered. This parameter is used to avoid frequent switching of the clock source due to instability of the clock source state within a short time. l This parameter is valid only when Higher Priority Clock Source Reversion Mode is set to AutoRevertive.
A.8.6 Querying the Clock Synchronization Status

You can check the current clock synchronization status of an NE by querying the clock synchronization status.
Prerequisite
A Task Collection
Procedure
Step 1 Choose Configuration > Clock > Clock Synchronization Status from the Function Tree. Step 2 Click Query to check the clock synchronization status. ----End
A.9 Managing ERPS Protection

This chapter describes how to configure ERPS to provide protection for an Ethernet ring network. A.9.1 Creating ERPS Instances The Ethernet ring protection switching (ERPS) protection is configured through creation of Ethernet ring protection instances. A.9.2 Setting Parameters of the Ethernet Ring Protocol The parameters to be set include the hold-off time, WTR time, and guard time. A.9.3 Querying the Status of the Ethernet Ring Protection Switching Protocol By using this operation, you can know the current status of the Ethernet ring protection switching.

The Ethernet ring protection switching (ERPS) protection is configured through creation of Ethernet ring protection instances.
Prerequisite
l l The NE user must have the authority of Operation Level or higher. The Ethernet boards must be added to the Slot Layout.

Web LCT
Precautions
If ERPS is used, you need to add the control VLAN ID to the VLAN filter table of an IEEE 802.1q bridge when creating EVPLAN services based on this bridge.
Procedure
Step 1 In the NE Explorer, select the EMS6 board from the Object Tree and then choose Configuration > Ethernet Protection > ERPS Management from the Function Tree. Step 2 Click New. The Create Ethernet Ring Protection Protocol Instance dialog box is displayed. Step 3 Set the parameters for the ERPS protection instance.
A Task Collection
Example
Table A-35 Parameters Parameter ERPS ID Value Range 1 to 7 Default Value Description l This parameter specifies the ID of an ERPS instance. l The ID of an ERPS instance must be unique. East Port West Port l This parameter specifies the east/west port of the ERPS instance. l The OptiX RTN 620 does not support tangent Ethernet rings or intersecting Ethernet rings. That is, in the case of OptiX RTN 620, the east and west ports must belong to the same Ethernet ring. l This parameter specifies whether a node on the ring is the ring protection link (RPL) owner. l Only one node on the Ethernet ring can be set as the RPL owner.
RPLOwner Ring Node Flag
Yes No
No
A Task Collection
Parameter RPL Port Control VLAN
Default Value -
Description This parameter specifies the RPL port. l This parameter specifies the VLAN ID of Control VLAN. l Each node on the Ethernet ring transmits the Ring-APS (RAPS) packets on the dedicated R-APS channel to ensure consistency between the nodes when the ERPS switching is performed. Control VLAN is used for isolating the dedicated R-APS channel. Therefore, the VLAN ID in Control VLAN must be different from the VLAN IDs that are contained in the service packets or inband DCN packets.
Destination Node
01-19-A7-00-00-01
01-19-A7-00-00-01
This parameter displays the MAC address of the destination node. The default destination MAC address in the R-APS packets is always 01-19A7-00-00-01.
A.9.2 Setting Parameters of the Ethernet Ring Protocol

The parameters to be set include the hold-off time, WTR time, and guard time.
Prerequisite
l l The NE user must have the authority of Operation Level or higher. The protection instance of the ERPS must be created.

Web LCT
Issue 05 (2010-10-30)
A-115
A Task Collection
Procedure
Step 1 Select the EMS6 board from the Object Tree in the NE Explorer. Choose Configuration > Ethernet Protection > ERPS Management. Step 2 Optional: Double-click Control VLAN, and then modify the VLAN ID.
Step 3 Set the parameters of Ethernet ring protocol.
Example
Table A-36 Parameters Parameter ERPS ID Value Range 1 to 7 Default Value Description l This parameter specifies the ID of an ERPS instance. l The ID of an ERPS instance must be unique. East Port West Port RPL Owner Ring Node Flag This parameter displays the east/west port of the ERPS instance. l This parameter displays whether a node on the ring is the ring protection link (RPL) owner. l An Ethernet ring has only an RPL owner. RPL Port This parameter displays the RPL port.
A-116
Issue 05 (2010-10-30)
A Task Collection
Parameter Control VLAN
Default Value -
Description l This parameter specifies the VLAN ID of Control VLAN. l Each node on the Ethernet ring transmits the Ring-APS (RAPS) packets on the dedicated R-APS channel to ensure consistency between the nodes when the ERPS switching is performed. Control VLAN is used for isolating the dedicated R-APS channel. Therefore, the VLAN ID in Control VLAN must be different from the VLAN IDs that are contained in the service packets or inband DCN packets.
Destination Node
01-19-A7-00-00-01
01-19-A7-00-00-01
This parameter displays the MAC address of the destination node. The default destination MAC address in the R-APS packets is always 01-19A7-00-00-01.
Issue 05 (2010-10-30)
A-117
A Task Collection
Parameter Hold-Off Time(ms)
Value Range 0 to 10000 (step: 100)
Default Value 0
Description l This parameter specifies the hold-off time of the ERPS holdoff timer. l The hold-off timer is used for negotiating the protection switching sequence when the ERPS coexists with other protection schemes, so that the fault can be rectified in the case of other protection switching (such as LAG protection) before the ERPS occurs. When a node on the ring detects one or more new faults, it starts up the hold-off timer if the preset hold-off time is set to a value that is not 0. During the hold-off time, the fault is not reported to trigger an ERPS. When the holdoff timer times out, the node checks the link status regardless whether the fault that triggers the startup of the timer exists. If the fault exists, the node reports it to trigger an ERPS. This fault can be the same as or different from the fault that triggers the initial startup of the hold-off timer.
A-118
Issue 05 (2010-10-30)
A Task Collection
Parameter Guard Time(ms)
Default Value 500
Description l This parameter specifies the guard time of the ERPS guard timer. l The nodes on the ring continuously forward the R-APS packets to the Ethernet ring. As a result, the outdated RAPS packets may exist on the ring network. After a node on the ring receives the outdated R-APS packets, an incorrect ERPS may occur. The ERPS guard timer is an R-APS timer used for preventing a node on the ring from receiving outdated R-APS packets. When a faulty node on the ring detects that the switching condition is cleared, the node starts up the guard timer and starts to forward the RAPS (NR) packets. During this period, the R-APS packets received by the node are discarded. The received R-APS packets are forwarded only after the time of the guard timer expires.
Issue 05 (2010-10-30)
A-119
A Task Collection
Parameter WTR Time(min)
Default Value 5
Description l This parameter specifies the WTR time of the WRT timer in the case of ERPS protection. l The WTR time refers to the duration from the time when the working channel is restored to the time when the switching is released. When the working channel is restored, the WTR timer of the RPL owner starts up. In addition, a signal that indicates the operation of the WTR timer is continuously output in the timing process. When the WTR timer times out and no switching request of a higher priority is received, the signal indicating the operation of the WTR timer is not transmitted. In addition, the WTR release signal is continuously output. l The WTR timer is used to prevent frequent switching caused by the unstable working channel.
Packet Transmit Interval(s)
1 to 10
This parameter specifies the interval for transmitting the R-APS packets.
A-120
Issue 05 (2010-10-30)
A Task Collection
Parameter Entity Level
Value Range 0 to 7
Default Value 4
Description l This parameter specifies the level of the maintenance entity. l This parameter must be different from the entity level set for the ETH OAM.
Last Switching Request RB Status
This parameter displays the last switching request. This parameter displays the RB status of the packets received by the working node. l noRB: The RPL is not blocked. l RB (RPL Blocked): The RPL is blocked.
DNF Status
This parameter displays the DNF status of the packets received by the working node. l noDNF: The R-APS packets do not contain the DNF flag. In this case, the packets are forwarded by the node that detects the fault on a non-RPL link, and the node that receives the packets is requested to clear the forwarding address table. l DNF: The R-APS packets contain the DNF flags. In this case, the packets are forwarded by the node that detects the fault on an RPL link, and the node that receives the packets is informed not to clear the forwarding address table.
Issue 05 (2010-10-30)
A-121
A Task Collection
Parameter Status of State Machine
Value Range -
Default Value -
Description This parameter displays the status of the state machine at the working node. l Idle: The Ethernet ring is in normal state. For example, no node on the Ethernet ring detects any faults or receives the R_APS (NR, RB) packets. l Protection: The Ethernet ring is in protected state. For example, a node on the ring is in the WTR period, because the fault on the node triggers the ERPS or the fault is rectified.
Node Carried with Current Packet
This parameter specifies the MAC address carried in the R-APS packets received by the current node. The MAC address refers to the MAC address of the source node that initiates the switching request.
A.9.3 Querying the Status of the Ethernet Ring Protection Switching Protocol
By using this operation, you can know the current status of the Ethernet ring protection switching.
Prerequisite

Web LCT
A-122
Issue 05 (2010-10-30)
A Task Collection
Procedure
Step 1 Select the EMS6 board from the Object Tree in the NE Explorer. Choose Configuration > Ethernet Protection > ERPS Management from the Function Tree. Step 2 Click Query. Step 3 Query the status of the Ethernet ring protection switching. ----End
A.10 Managing the STP

If a loop exists in the network topology of Ethernet services, you need to enable the Spanning Tree Protocol (STP) or Rapid Spanning Tree Protocol (RSTP). A.10.1 Configuring the Spanning Tree Protocol In the case of the Layer 2 switching service, if a loop is formed, you need to enable the STP or RSTP for the bridge and set bridge parameters and port parameters. A.10.2 Setting the Parameters of Spanning Tree Protocol If the STP or RSTP is enabled on a bridge, you can set the bridge parameters and port parameters of the STP or RSTP according to the requirements of the reachable data communications equipment. A.10.3 Querying the Running Information About the Spanning Tree Protocol The running information about the STP includes the bridge running information and port running information.
A.10.1 Configuring the Spanning Tree Protocol

In the case of the Layer 2 switching service, if a loop is formed, you need to enable the STP or RSTP for the bridge and set bridge parameters and port parameters.
Prerequisite
The NE user must have the authority of Operation Level or higher. Ethernet switching boards must be created on the Slot Layout. Ethernet services must be created.

Web LCT
Precautions
The OptiX RTN 620 supports the Ethernet switching boards EMS6 and EFP6.
Procedure
Step 1 In the NE Explorer, select the required Ethernet switching board, and then choose Configuration > Layer-2 Switching Management > Spanning Tree from the Function Tree.
A Task Collection
Step 2 Enable the protocol. 1. 2. Click the Protocol Enable tab. Set the parameters of the enabled protocol.
3.
Click Apply.
----End
Parameters
Parameter VB Protocol Enabled Value Range Enable Disabled Default Value Disabled Description Indicates the created bridge. l Indicates whether to enable the STP. l In the service networking process, it is recommended that you prevent a loop from forming in the case of the Layer 2 switching service and thus avoid enabling the STP or RSTP. l If a loop is already formed in the service networking process, you must enable the STP or RSTP. Protocol Type STP RSTP RSTP l This parameter is valid only when Protocol Enabled is set to Enabled. l The protocol type is set according to the requirement of the interconnected Ethernet equipment. In normal cases, it is recommended that you use the default value.
NOTE
l In the service networking process, it is recommended that you prevent a loop from forming in the case of the Layer 2 switching service and thus avoid enabling the STP or RSTP. l Because the RSTP and STP are complicated, it is recommended that you negotiate with the engineer in charge of maintaining the opposite Ethernet equipment and set the relevant parameters as instructed, before enabling the STP or RSTP.
A.10.2 Setting the Parameters of Spanning Tree Protocol

If the STP or RSTP is enabled on a bridge, you can set the bridge parameters and port parameters of the STP or RSTP according to the requirements of the reachable data communications equipment.
Prerequisite
A Task Collection
Ethernet switching boards must be created on the Slot Layout. Ethernet services must be created.

Web LCT
Precautions
Procedure
Step 1 In the NE Explorer, select the required Ethernet switching board, and then choose Configuration > Layer-2 Switching Management > Spanning Tree from the Function Tree. Step 2 Set bridge parameters. 1. 2. Click the Bridge Parameter tab. Set bridge parameters.
3. 1. 2.
Click Apply. Click the Port Parameter tab. Set port parameters.
Step 3 Set port parameters.
3. 1. 2.
Click Apply. Click the Point to Point Attribute tab. Set the point-to-point attributes of the port.
Step 4 Optional: To enable the RSTP, specify the point-to-point attribute of the Ethernet port.
3.
Click Apply.
----End
Issue 05 (2010-10-30)
A-125
A Task Collection
Parameters
Parameter Priority (Bridge Parameter) Value Range 0 to 61440 Default Value 32768 Description l The most significant 16 bits of the bridge ID indicate the priority of the bridge. l When the value is smaller, the priority is higher. As a result, the bridge is more possible to be selected as the root bridge. l If the priorities of all the bridges on the STP network use the same value, the bridge whose MAC address is the smallest is selected as the root bridge. Max Age(s) 6 to 40 20 l Indicates the maximum age of the CBPDU packet that is recorded by the port. l The greater the value, the longer the transmission distance of the CBPDU, which indicates that the network diameter is greater. When the value of this parameter is greater, it is less possible that the bridge detects the link fault immediately and thus the network adaptability is reduced. Hello Time(s) 1 to 10 2 l Indicates the interval for transmitting the CBPDU packets through the bridge. l The greater the value of this parameter, the less the network resources that are occupied by the spanning tree. The topology stability, however, decreases. Forward Delay(s) 4 to 30 15 l Indicates the holding time of a port in the listening state and in the learning state. l The greater the value, the longer the delay of the network state change. Hence, the topology changes are slower and recovery in the case of faults is slower. TxHoldCount (per second) Priority (Port Parameters) 1 to 10 0 to 240 6 128 Indicates the number of times the port transmits the CBPDU in every second. l The most significant eight bits of the port ID indicate the port priority. l When the value is smaller, the priority is higher.
A-126
Issue 05 (2010-10-30)
A Task Collection
Parameter Port Path Cost
Default Value 19
Description l Indicates the status of the network that the port is connected to. l In the case of the bridges on both ends of the path, set this parameter to the same value.
Admin Edge Attribute
Enabled Disabled
Disabled
l This parameter is valid for the RSTP only. l This parameter indicates whether to set the port as an edge port. The edge port refers to the bridge port that is connected only to the LAN. The edge port receives the BPDU but does not transmit the BPDU. l You can set this parameter to Enabled only when the Ethernet port on the Ethernet board is connected directly to a data communications terminal, such as a computer. In other cases, it is recommended that you use the default value.
Protocol Enabled
Enabled Disabled
Enabled
l Indicates whether the STP/RSTP is enabled for the port. l If you set this parameter to Disabled, the BPDU cannot be processed or transmitted. l It is recommended that you use the default value.
Auto Edge Detection
Enabled Disabled
Disabled
l This parameter is valid only when Admin Edge Attribute is set to Enabled. l When you set this parameter to Enabled, the RSTP considers this port as a non-edge port if the bridge detects that this port is connected to a port of another bridge. l If you set Admin Edge Attribute to Enabled, you need to set this parameter to Enabled. In other cases, it is recommended that you use the default value.
Issue 05 (2010-10-30)
A-127
A Task Collection
Parameter Point-to-Point Attribute
Value Range Adaptive connection Link connection Shared media
Default Value Adaptive connection
Description l This parameter is valid only when the RSTP is used. l If you set this parameter to Adaptive connection, the bridge determines the actual point-to-point attribute of the port according to the actual working mode of the port. If the actual working mode is full-duplex, the actual point-to-point attribute is "true". If the actual working mode is half-duplex, the actual point-topoint attribute is "false". l If you set this parameter to Link connection, the actual point-to-point attribute of the port is "true". l If you set this parameter to Shared media, the actual point-to-point attribute of the port is "false". l Only the port whose actual point to point attribute is "true" can transmit the fast transition request and response messages. l It is recommended that you use the default value.
NOTE
l In the service networking process, it is recommended that you prevent a loop from forming in the case of the Layer 2 switching service and thus avoid enabling the STP or RSTP. l Because the RSTP and STP are complicated, it is recommended that you negotiate with the engineer in charge of maintaining the opposite Ethernet equipment and set the relevant parameters as instructed, before enabling the STP or RSTP.
A.10.3 Querying the Running Information About the Spanning Tree Protocol
The running information about the STP includes the bridge running information and port running information.
Prerequisite
The NE user must have the authority of Operation Level or higher. Ethernet switching boards must be created on the Slot Layout. Ethernet LAN services must be created. The STP or RSTP of the bridge must be enabled.
A Task Collection

Web LCT
Precautions
Procedure
Step 1 In the NE Explorer, select the required Ethernet switching board, and then choose Configuration > Layer-2 Switching Management > Spanning Tree from the Function Tree. Step 2 Query the bridge running information. 1. 2. 3. Click the Bridge Running Info tab. Click Query. View the bridge running information.
Step 3 Query the port running information. 1. 2. 3. Click the Port Running Info tab. Click Query. View the port running information.
----End
A.11 Managing the IGMP Snooping

If a multicast router exists on a network, the bridge can enable the IGMP Snooping protocol to implement the multicast function together with the router. A.11.1 Configuring the IGMP Snooping Protocol If the bridge accesses a LAN where the IGMP multicast server exists, you can enable the IGMP Snooping protocol and configure the method for processing the unknown multicast packet. A.11.2 Modifying the Aging Time of a Multicast Table Item In the case of an Ethernet switching board, the aging time of a multicast table item is 8 minutes by default. A.11.3 Querying the Running Information of the IGMP Snooping Protocol The running information of the IGMP Snooping protocol includes the current multicast router port and multicast table items.
A.11.1 Configuring the IGMP Snooping Protocol

If the bridge accesses a LAN where the IGMP multicast server exists, you can enable the IGMP Snooping protocol and configure the method for processing the unknown multicast packet.
Prerequisite
l l
Issue 05 (2010-10-30)
The NE user must have the authority of Operation Level or higher. The corresponding Ethernet switching board must be added to the Slot Layout.
A Task Collection
l l
The Ethernet LAN service must be created. The VLAN filtering table must be created.

Web LCT
Precautions
Procedure
Step 1 In the NE Explorer, select the Ethernet switching board, and choose Configuration > Layer-2 Switching Management > IGMP Snooping Protocol from the Function Tree. Step 2 Click the Enable IGMP Snooping Protocol tab. Step 3 Configure the information about the IGMP Snooping protocol.
Parameters
Parameter Protocol Enable Value Range Enabled Disabled Default Value Disabled Description l This parameter specifies whether to enable the IGMP Snooping protocol. l If the bridge accesses a LAN where the IGMP multicast server exists, you determine whether to enable the IGMP Snooping protocol according to the requirement.
A-130
Issue 05 (2010-10-30)
A Task Collection
Parameter The Discarded Tag of the Packet Excluded in the Multicast Group
Value Range Enabled Disabled
Default Value Enabled
Description l This parameter is valid only when Protocol Enable is set to Enabled. l If the IEEE 802.1q bridge or the IEEE 802.1ad bridge receives a multicast packet whose multicast address has no matching item in the multicast table (that is, this multicast packet is an unknown multicast packet), this parameter indicates the method for processing this packet. l When this parameter is set to Enabled, The unknown multicast packet is discarded. l When this parameter is set to Disabled, the unknown multicast packet is broadcast in the VLAN. l Set this parameter according to the requirement of the IGMP multicast server.
A.11.2 Modifying the Aging Time of a Multicast Table Item

In the case of an Ethernet switching board, the aging time of a multicast table item is 8 minutes by default.
Prerequisite
l l l l The NE user must have the authority of Operation Level or higher. The corresponding Ethernet switching board must be added to the Slot Layout. The Ethernet LAN service must be created. The IGMP Snooping protocol of the bridge must be enabled.

Web LCT
Precautions
Procedure
Step 1 In the NE Explorer, select the Ethernet switching board, and choose Configuration > Layer-2 Switching Management > IGMP Snooping Protocol from the Function Tree. Step 2 Click the Multicast Aging Time tab.
A Task Collection
Step 3 Modify the aging time of the multicast table item.
Parameters
Parameter Multicast Aging Time (Min) Value Range 1 to 120 Default Value 8 Description l When a table item is not updated in a certain period (that is, no IGMP request from this multicast address is received), this table item is automatically deleted. This mechanism is called aging, and this period is called aging time. l If this parameter is set to a very large value, the bridge stores excessive multicast table items that are outdated. As a result, the resources of the multicast table are exhausted. l If this parameter is set to a very small value, the bridge may delete multicast table items that are required. As a result, service forwarding efficiency is reduced.
A.11.3 Querying the Running Information of the IGMP Snooping Protocol

The running information of the IGMP Snooping protocol includes the current multicast router port and multicast table items.
Prerequisite
l l l l The NE user must have the authority of Operation Level or higher. The corresponding Ethernet switching board must be added to the Slot Layout. The Ethernet LAN service must be created. The IGMP Snooping protocol of the bridge must be enabled.

Web LCT
Precautions
A Task Collection
Procedure
Step 1 In the NE Explorer, select the Ethernet switching board, and choose Configuration > Layer-2 Switching Management > IGMP Snooping Protocol from the Function Tree. Step 2 Query the information about the router port. 1. 2. 3. Click the Multicast Router Port Management tab. Click Query. Check the information about the router port.
Step 3 Query the information about the multicast table items. 1. 2. 3. Click the Multicast Table Item tab. Click Query. Check the information about the multicast table items.
----End
A.12 Managing LAGs

Link aggregation enables one or multiple links that are connected to the same equipment to be aggregated into a LAG. The aggregated links are considered as a single logical link at the MAC layer. In this manner, bandwidth and availability of radio links are improved. A.12.1 Creating a LAG To improve bandwidth and availability of Ethernet links between two NEs, you need to create the corresponding LAG. A.12.2 Setting the Port Priority In a LAG that uses the static aggregation mode, a port with higher priority is preferred to transmit services. A.12.3 Querying the Protocol Information of the LAG This section describes how to learn about the running information of the LACP protocol used by LAGs.
A.12.1 Creating a LAG

To improve bandwidth and availability of Ethernet links between two NEs, you need to create the corresponding LAG.
Prerequisite
l l l The NE user must have the authority of Operation Level or higher. The physical network topology must be established. The corresponding Ethernet switching board must be added to the Slot Layout.

Web LCT
A Task Collection
Precautions
Procedure
Step 1 In the NE Explorer, select the Ethernet switching board, and choose Configuration > Ethernet Interface Management > Ethernet Link Aggregation Management from the Function Tree. Step 2 Click the Link Aggregation Group Management tab. Step 3 Click New. Then, the Create Link Aggregation Group dialog box is displayed. Step 4 Set the parameters of the LAG.
Parameters
Parameter LAG No. Value Range Default Value Description This parameter specifies the LAG number.
Issue 05 (2010-10-30)
A-134
A Task Collection
Parameter LAG Name
Value Range -
Default Value -
Description This parameter specifies the LAG name.
Issue 05 (2010-10-30)
A-135
A Task Collection
Parameter LAG Type
Value Range Static Manual
Default Value Static
Description l Static: To add or delete a member port of a LAG, you need to enable the Link Aggregation Control Protocol (LACP) protocol. In a LAG, a port may be in Selected or Standby state. The aggregation information is exchanged among different equipment through the LACP protocol to ensure that the aggregation information is the same among all the nodes. l Manual: To add or delete a member port of a LAG, you need not enable the LACP protocol. The port may be in UP or DOWN state. Determine whether to perform aggregation according to the port status. l In the case of the LAG that is created for IF 1+1 protection, set this parameter to Manual. In other cases, set this parameter according to the configuration on the opposite equipment.
A-136
Issue 05 (2010-10-30)
A Task Collection
Parameter Load Sharing
Value Range Sharing Non-Sharing
Default Value Sharing
Description l Sharing: Each member link of a LAG processes traffic at the same time and shares the traffic load. The sharing mode increases bandwidth utilization of the link. When the LAG members change, or certain links fail, the system automatically reallocates the traffic. l Non-Sharing: Only one member link of a LAG carries traffic, and the other links is in standby state. In this case, a hot backup mechanism is provided. When the active link of a LAG is faulty, the system activates the standby link, thus preventing against a link failure. l In the case of a LAG that is created for IF 1+1 protection, set this parameter to Non-Sharing. In other cases, set this parameter according to the configuration on the opposite equipment.
Issue 05 (2010-10-30)
A-137
A Task Collection
Parameter Sharing Mode
Value Range IP Sharing Mode Mac Sharing Mode
Default Value IP Sharing Mode
Description You can set this parameter only when Load Sharing is Sharing. l You can set this parameter only when Load Sharing is NonSharing. l When Hybrid radio is configured with 1 +1 protection, set this parameter to Non-Revertive.
Revertive Mode
Revertive Non-Revertive
Revertive
A-138
Issue 05 (2010-10-30)
A Task Collection
Parameter Main Port
Value Range -
Default Value -
Description l This parameter specifies the main port in a LAG. l In the case of a LAG that is created for IF 1+1 protection, you need to set Main Port to the port that is interconnected with the main IF board IFH2. l In other cases, set this parameter according to the configuration on the opposite equipment. l After creating a LAG, you can add Ethernet services to the main port only and cannot add services to a slave port. l When Load Sharing is set to Non-Sharing, all services are transmitted on the link to which the main port is connected. The links to which other slave ports are connected function as protection links.
Issue 05 (2010-10-30)
A-139
A Task Collection
Parameter Available Slave Ports
Value Range -
Default Value -
Description l This parameter specifies the slave ports in a LAG. A LAG is manually created rather than being automatically created by the system. A LAG contains a main port and slave ports. The slave ports in a LAG are fixed. The system does not automatically add or remove slave port of a LAG. If required, you need to change slave ports of a LAG manually. l In the case of a LAG that is created for IF 1+1 protection, you need to set Selected Slave Ports to the port that is interconnected with the standby IF board IFH2. l In other cases, set this parameter according to the configuration on the opposite equipment.
Selected Slave Ports
This parameter displays the ports that are already selected as slave ports of a LAG.
A-140
Issue 05 (2010-10-30)
A Task Collection
A.12.2 Setting the Port Priority

In a LAG that uses the static aggregation mode, a port with higher priority is preferred to transmit services.
Prerequisite
l l The NE user must have the authority of Operation Level or higher. The corresponding Ethernet switching board must be added to the Slot Layout.

Web LCT
Precautions
Procedure
Step 1 In the NE Explorer, select the Ethernet switching board, and choose Configuration > Ethernet Interface Management > Ethernet Link Aggregation Management from the Function Tree. Step 2 Click the Link Aggregation Parameters tab. Step 3 Set the parameters about the port priority.
NOTE
l A port ID consists of Port and Port Priority. The port that has the smaller ID in a LAG is aggregated first. l A system ID consists of System Parameter Settings and System MAC Address. When the system negotiates with the remote system, the system with the smaller ID can first select the ports to be aggregated. In this example, the system refers to the board, and the system MAC address refers to the MAC address of the board. The factory-set MAC address is globally unique and cannot be modified.
----End
Issue 05 (2010-10-30)
A-141
A Task Collection
Parameters
Parameter Port Value Range Default Value Description This parameter displays the port whose priority can be set. l This parameter is valid only when LAG Type is set to Static. l This parameter indicates the priorities of the ports in a LAG as defined in the LACP protocol. The smaller the value, the higher the priority. l When ports are added into a LAG, the port of the highest priority is preferred for service transmission.
Port Priority
0 to 65535 (step: 1)
32768
A-142
Issue 05 (2010-10-30)
A Task Collection
Parameter System Priority
Default Value 32768
Description l This parameter is valid only when LAG Type is set to Static. l This parameter indicates the priority of a LAG. The smaller the value, the higher the priority. l When a local LAG negotiates with an opposite LAG through LACP packets, both LAGs can obtain the system priorities of each other. Then, the computation result based on the logic that is selected by the LAG with the higher system priority is considered as the result of both LAGs. If the priorities of both LAGs are the same, the system MAC addresses are compared. Then, the computation result based on the logic that is selected by the LAG with lower system MAC address is considered as the result of both LAGs.
System MAC Address
This parameter displays the system MAC address.
Issue 05 (2010-10-30)
A-143
A Task Collection
A.12.3 Querying the Protocol Information of the LAG

This section describes how to learn about the running information of the LACP protocol used by LAGs.
Prerequisite

Web LCT
Procedure
Step 1 In the NE Explorer, select the Ethernet switching board, and choose Configuration > Ethernet Interface Management > Ethernet Link Aggregation Management from the Function Tree. Step 2 Click the Link Aggregation Group Management tab. Step 3 Click Query. Step 4 In the main interface, select the LAG to be queried. Right-click the LAG and choose an option from the dropdown list. A dialog box is displayed, indicating the query result. ----End
A.13 Managing the QoS

By managing the QoS, you can provide differentiated services for different service types. A.13.1 Creating a Flow In the case of an Ethernet switching board, a flow refers to a collection of packets on which the same QoS operation is performed. Creating a flow is the prerequisite for performing CAR and CoS operations. A.13.2 Creating the CAR CAR is a type of traffic policing technology. After the flow classification, the CAR assesses the rate of the traffic in a certain period (including in the long term and in the short term). The CAR sets the packet whose rate does not exceed the specified rate to high priority and discards the packet whose rate exceeds the specified rate or downgrades this kind of packet, thus restricting the traffic into the transmission network. A.13.3 Creating the CoS By using the CoS, the packets in a flow can be scheduled to different queues of different priorities and can be processed according to the priority of each queue. This ensures that the packets of different priorities can be processed according to different QoS requirements. A.13.4 Binding the CAR/CoS To enable the CAR or CoS function, you need to bind the corresponding flow to the created CAR/CoS. A.13.5 Configuring the Traffic Shaping for Egress Port Queues
A Task Collection
The traffic shaping function can restrict the traffic and burst of a connection on a network, and thus enables the packets to be transmitted at an even rate. A.13.6 Configuring Port Shaping This topic describes how to configure the traffic shaping function and how to set the shaping parameters for an egress port. A.13.7 Configuring the CoS of the IFH2 Board The IFH2 board supports the ability of scheduling packets into different queues according to the corresponding user priorities specified in the VLAN tags. A.13.8 Configuring the Queue Scheduling Mode The The OptiX RTN 620 supports the setting of the queue scheduling mode for a port on the EMS6 board and the setting of the weight values of the corresponding WRR queues.

In the case of an Ethernet switching board, a flow refers to a collection of packets on which the same QoS operation is performed. Creating a flow is the prerequisite for performing CAR and CoS operations.
Prerequisite
The NE user must have the authority of Operation Level or higher. Ethernet switching boards must be created on the Slot Layout. The associated Ethernet services must be created.

Web LCT
Precautions
The Ethernet switching boards supported by the OptiX RTN 620 are the EMS6 and EFP6.
Procedure
Step 1 In the NE Explorer, select the required Ethernet switching board, and then choose Configuration > QoS Management > Flow Management from the Function Tree. Step 2 Click the Flow Configuration tab. Step 3 Click New. The New Flow dialog box is displayed. Step 4 Set the flow parameters.
Issue 05 (2010-10-30)
A-145
A Task Collection
A-146
Issue 05 (2010-10-30)
A Task Collection
Parameters
Parameter Flow Type Value Range Port Flow Port+VLAN Flow Port+SVLAN Flow Port+CVLAN +SVLAN Flow Port+VLAN +Priority Flow Default Value Port Flow Description Port flow: The packets from a certain port are classified as a type of flow. The Ethernet service associated with this flow type is the Ethernet private line service or Layer 2 switching service that uses this port as the service source. Port+VLAN flow: The packets that are from a certain port and have a specified VLAN ID are classified as a type of flow. The associated Ethernet service of this flow type is the EVPL service (based on VLAN) or EVPLAN service (based on the 802.1q bridge) that uses Port+VLAN as the service source. Port+SVLAN flow: The packets that are from a certain port and have a specified SVLAN ID are classified as a type of flow. The associated Ethernet service of this flow type is the EVPL service (based on QinQ) or EVPLAN service (based on the 802.1ad bridge) that uses Port+S-VLAN as the service source. Port+CVLAN+SVLAN flow: The packets that are from or to a certain port and have a specified CVLAN+SVLAN are classified as a type of flow. The associated Ethernet service of this flow type is the EVPL service (based on QinQ) or EVPLAN service (based on the 802.1ad bridge) that uses Port+CVLAN+S-VLAN as the service source. Port+VLAN+Priority flow: The packets that are from a certain port and have a specified VLAN ID and a specified VLAN priority are classified as a type of flow. The associated Ethernet service of this flow type is the Ethernet private line service that uses Port+VLAN+Priority as the service source. This parameter is applicable to only the EFP6 board rather than the EMS6 board.
Issue 05 (2010-10-30)
A-147
A Task Collection
Parameter Port
Value Range In the case of the EMS6 board: PORT1-PORT6, VCTRUNK1VCTRUNK8 In the case of the EFP6 board: PORT1-PORT6, VCTRUNK1VCTRUNK16
Default Value PORT1
Description l When the associated service is the private line service, set this parameter to the source port or sink port of the associated Ethernet service. l When the associated service is the Layer 2 switching service, set this parameter to a mounted port of the bridge.
VLAN ID
1-4095
l This parameter is valid only when Flow Type is set to Port+VLAN Flow or Port +VLAN+Priority Flow. l Set this parameter to the source VLAN of the associated Ethernet service.
C-VLAN
1-4095
l This parameter is valid only when Flow Type is set to Port+SVLAN+CVLAN Flow. l Set this parameter to the source CVLAN of the associated Ethernet service.
S-VLAN
1-4095
l This parameter is valid only when Flow Type is set to Port+SVLAN Flow or Port+SVLAN+CVLAN Flow. l Set this parameter to the source S-VLAN of the associated Ethernet service.
Follow-up Procedure
After creating a flow, bind it to the corresponding CAR or CoS operation as required.
A.13.2 Creating the CAR

CAR is a type of traffic policing technology. After the flow classification, the CAR assesses the rate of the traffic in a certain period (including in the long term and in the short term). The CAR sets the packet whose rate does not exceed the specified rate to high priority and discards the packet whose rate exceeds the specified rate or downgrades this kind of packet, thus restricting the traffic into the transmission network.
Prerequisite
The NE user must have the authority of Operation Level or higher. Ethernet switching boards must be created on the Slot Layout.
A-148
Issue 05 (2010-10-30)
A Task Collection

Web LCT
Precautions
Procedure
Step 1 In the NE Explorer, select the required Ethernet switching board, and then choose Configuration > QoS Management > Flow Management from the Function Tree. Step 2 Click the CAR Configuration tab. Step 3 Click New. The New CAR dialog box is displayed. Step 4 Set the CAR parameters.
Parameters
Parameter CAR ID Value Range In the case of the EMS6 board: 1-1024 In the case of the EFP6 board: 1-512 Enabled/Disabled Enable Disabled Disabled Indicates whether to enable the CAR operation performed on the flow bound to the CAR. Default Value Description Identifies a CAR operation. This parameter is used to bind a flow to an associated CAR operation.
Issue 05 (2010-10-30)
A-149
A Task Collection
Parameter Committed Information Rate (kbit/s)
Value Range FE: an integer ranging from 0 to 100032, in the increments of 64 GE: an integer ranging from 0 to 1048576, in the increments of 64
Default Value 0
Description l Indicates the CIR. When the rate of the packets is not more than the CIR, these packets pass the restriction of the CAR and are forwarded first even in the case of network congestion. l The value of this parameter cannot be more than the PIR.
Committed Burst Size (kbyte)
In the case of the EMS6 board: 0-1024 In the case of the EFP6 board: 0-1024
Indicates the CBS. When the rate of the packets that pass the restriction of the CAR is not more than the CIR in a certain period, certain packets can burst and can pass the restriction of the CAR. These packets can be forwarded first even in the case of network congestion. The maximum traffic of the burst packets is determined by the CBS. Note that the CBS has an inherent size, and this parameter indicates the increment value only. The inherent size of the CBS is determined by the CIR. The greater the CIR, the greater the CBS. l Indicates the PIR. When the rate of the packets is more than the PIR, these packets that exceed the rate restriction are directly discarded. When the rate of the packets is more than the CIR but is not more than the PIR, the packets whose rate is more than the CIR can pass the restriction of the CAR and are marked yellow, which enables these packets to be discarded first in the case of network congestion. l The value of this parameter is not more than the bandwidth at the port.
Peak Information Rate (kbit/s)
FE: an integer ranging from 0 to 100032, in the increments of 64 FE: an integer ranging from 0 to 1048576, in the increments of 64
Maximum Burst Size (kbyte)
In the case of the EMS6 board: 0-1024 In the case of the EFP6 board: 0-1024
Indicates the MBS. When the rate of the packets that pass the restriction of the CAR is more than the CIR but is not more than the PIR, certain packets can burst and are marked yellow, which enables these packets to be discarded first in the case of network congestion. The maximum traffic of the burst packets is determined by the specified MBS. Note that the MBS has an inherent size, and this parameter indicates the increment value only. The inherent size of the MBS is determined by the PIR. The greater the PIR, the greater the MBS.
A-150
Issue 05 (2010-10-30)
A Task Collection
Follow-up Procedure
After creating the CAR, bind the flow to the corresponding CAR operation as required.
A.13.3 Creating the CoS

By using the CoS, the packets in a flow can be scheduled to different queues of different priorities and can be processed according to the priority of each queue. This ensures that the packets of different priorities can be processed according to different QoS requirements.
Prerequisite

Web LCT
Precautions
Procedure
Step 1 In the NE Explorer, select the required Ethernet switching board, and then choose Configuration > QoS Management > Flow Management from the Function Tree. Step 2 Click the CoS Configuration tab. Step 3 Click New. The New CoS dialog box is displayed. Step 4 Set the CoS parameters.
Issue 05 (2010-10-30)
A-151
A Task Collection
A-152
Issue 05 (2010-10-30)
A Task Collection
Parameters
Parameter CoS ID Value Range In the case of EFP6: 1-64 In the case of EMS6: 1-65535 CoS Type l Simple l VLAN priority l DSCP l IPTOS Default Value 1 Description Identifies a CoS operation. This parameter is used to bind a flow to an associated CoS operation.
l If you set the CoS type of a flow to Simple, the packets in this flow are scheduled to specified egress queues. l If you set the CoS type of a flow to VLAN priority, the packets in this flow are scheduled to specified egress queues according to the user priorities specified in the VLAN tags of these packets. l If you set the CoS type of a flow to DSCP, the packets in this flow are scheduled to specified egress queues according to differentiated services code point (DSCP) in the IPv6 tags of these packets. l If you set the CoS type of a flow to IPTOS, the packets in this flow are scheduled to specified egress queues according to the TOS value specified in the IPv4 tags of these packets. The packets in a data flow bound with this rule are called IPv4 packets.
Issue 05 (2010-10-30)
A-153
A Task Collection
Parameter CoS Priority
Value Range 0-7
Default Value 0
Description Specifies a queue to which a packet is scheduled. l Each Ethernet port on the EMS6 or EFP6 board supports eight egress port queues. Queues 1-8 respectively correspond to the CoS priority of 0, 1, 2, 3, 4, 5, 6, and 7. l By default, queue 8 (with the CoS priority of 7) is the SP queue, and queues 1-7 (with the respective CoS priority of 0-6) are the WRR queues and their weights are in proportion of 1:2:4:8:16:32:64. In the case of the EMS6 board, the queue algorithm and the weight proportion of the WRR queues can be changed. In the case of the EFP6 board, the queue algorithm and the weight proportion of the WRR queues cannot be changed. l In the case of the EMS6 board, when the priorities of the SP queues are compared, queue 8 (with the CoS priority of 7) is of the highest priority, and queue 1 (with the CoS priority of 0) is of the lowest priority. l If the traffic shaping function is enabled for certain queues, the bandwidth is first allocated to these queues according to the specified CIR. The remaining bandwidth is allocated to the eight queues according to the SP+WRR algorithm.
Follow-up Procedure
After creating the CoS, bind the flow to the corresponding CoS operation as required.
A.13.4 Binding the CAR/CoS

To enable the CAR or CoS function, you need to bind the corresponding flow to the created CAR/CoS.
Prerequisite
The NE user must have the authority of Operation Level or higher. Ethernet switching boards must be created on the Slot Layout. The flow and CAR/CoS must be created.
A Task Collection

Web LCT
Precautions
Procedure
Step 1 In the NE Explorer, select the required Ethernet switching board, and then choose Configuration > QoS Management > Flow Management from the Function Tree. Step 2 Click the Flow Configuration tab. Step 3 Bind the CAR/CoS.
Parameters
Parameter Bound CAR Value Range Default Value Description Indicates the CAR ID that corresponds to a CAR operation. Different CAR IDs are bound to different flows, even though the parameters of the CAR operations are the same. Indicates the CoS ID that corresponds to a CoS operation.
Bound CoS
A.13.5 Configuring the Traffic Shaping for Egress Port Queues

The traffic shaping function can restrict the traffic and burst of a connection on a network, and thus enables the packets to be transmitted at an even rate.
Prerequisite
Precautions
A Task Collection
Procedure
Step 1 In the NE Explorer, select the required Ethernet switching board, and then choose Configuration > QoS Management > Port Shaping Management from the Function Tree. Step 2 Click the Port Queue Information tab. Step 3 In Port List, select a port. Step 4 Set the traffic shaping information about the egress port queue.
Parameters
Parameter Port Enabled/Disabled Value Range Enable Disabled Default Value Disabled Description Indicates the port whose traffic needs to be shaped. l Indicates whether to enable the traffic shaping function of an egress queue. l If the traffic shaping function of certain queues is enabled, the bandwidth is allocated first to these queues according to the specified CIR. The remaining bandwidth is allocated to all the queues according to the SP+WRR algorithm. CIR (kbit/s) FE: an integer ranging from 0 to 100032, in the increments of 64 FE: an integer ranging from 0 to 1048576, in the increments of 64 0 l Indicates the CIR. When the rate of the packets is not more than the CIR, these packets directly enter the egress queue. l The value of this parameter cannot be more than the PIR.
A-156
Issue 05 (2010-10-30)
A Task Collection
Parameter PIR (kbit/s)
Value Range FE: an integer ranging from 0 to 100032, in the increments of 64 FE: an integer ranging from 0 to 1048576, in the increments of 64
Default Value 0
Description l Indicates the PIR. When the rate of the packets is more than the PIR, these packets that exceed the rate restriction are directly discarded. When the rate of the packets is more than the CIR but not more than the PIR, the packets whose rate is more than the CIR enter the buffer of the CIR. When the buffer overflows, the packets are marked yellow and enter the egress queue, which enables these packets to be discarded first in the case of queue congestion. l The value of this parameter cannot be more than the bandwidth at the port.
A.13.6 Configuring Port Shaping

This topic describes how to configure the traffic shaping function and how to set the shaping parameters for an egress port.
Prerequisite

Web LCT
Context
The Ethernet switching board supported by the OptiX RTN 620 is the EMS6.
Procedure
Step 1 In the NE Explorer, select the required Ethernet switching board, and then choose Configuration > QoS Management > Port Shaping Management from the Function Tree. Step 2 Click the Port Shaping tab. Step 3 In Port Shaping, select a port. Step 4 Set the parameters for traffic shaping of the corresponding port.
Issue 05 (2010-10-30)
A-157
A Task Collection
Parameters
Parameter Status Value Range Enabled Disabled PIR (kbit/s) FE: an integer ranging from 0 to 102400, in the increments of 64 FE: an integer ranging from 0 to 1048576, in the increments of 64 0 Default Value Disabled Description Indicates whether to enable the traffic shaping function of a port. In the case of the EMS6 board, the PIR of the port must be based on the following constraints: l Not less than the PIR of any queue on the port l Not less than the sum of the CIRs of all the queues on the port
A.13.7 Configuring the CoS of the IFH2 Board

The IFH2 board supports the ability of scheduling packets into different queues according to the corresponding user priorities specified in the VLAN tags.
Prerequisite
The NE user must have the authority of Operation Level or higher. The IFH2 board must be created on the Slot Layout.

Web LCT
Procedure
Step 1 In the NE Explorer, select the required IFH2 board, and then choose Configuration > QoS Management > Flow Management from the Function Tree. Step 2 Set CoS Priority for CoS Priority for User Priority 0 to User Priority 7 in the VLAN Tag.
A-158
Issue 05 (2010-10-30)
A Task Collection
Parameters
Parameter CoS Parameter Value Range User Priority 0 in the VLAN Tag, User Priority 1 in the VLAN Tag, User Priority 2 in the VLAN Tag, User Priority 3 in the VLAN Tag, User Priority 4 in the VLAN Tag, User Priority 5 in the VLAN Tag, User Priority 6 in the VLAN Tag, User Priority 7 in the VLAN Tag 0-3 Default Value Description Indicates the data flow. The IFH2 board supports differentiation of the data flows according to the user priorities specified in the VLAN tags of the packets.
CoS Priority
l Specifies a queue to which a packet is scheduled. l The IFH2 board supports four egress port queues. Queues 1-4 respectively correspond to the CoS priority of 0, 1, 2, and 3. l The SP algorithm is used. Queue 4 (with the CoS priority of 3) is of the highest priority, and queue 1 (with the CoS priority of 0) is of the lowest priority.
A.13.8 Configuring the Queue Scheduling Mode

The The OptiX RTN 620 supports the setting of the queue scheduling mode for a port on the EMS6 board and the setting of the weight values of the corresponding WRR queues.
A Task Collection
Prerequisite

Web LCT
Precautions
The Ethernet switching boards supported by the OptiX RTN 620 are the EMS6 and EFP6. The queue scheduling mode of the EFP6 and the weight value of a WRR queue are always the same and cannot be changed.
Procedure
Step 1 In the NE Explorer, select the required Ethernet switching board, and then choose Configuration > QoS Management > from the Function Tree. Step 2 Click the Port Queue Information tab. Step 3 In Port List, select a port. Step 4 Set Scheduling Mode and Weight of the corresponding queue on the port.
A-160
Issue 05 (2010-10-30)
A Task Collection
Parameters
Parameter Scheduling Mode Value Range SP WRR Default Value Queue 1: WRR Queue 2: WRR Queue 3: WRR Queue 4: WRR Queue 5: WRR Queue 6: WRR Queue 7: WRR Queue 8: SP Description By default, queue 8 (with the CoS priority of 7) of the EMS6 board is the SP queue, and queues 1-7 (with the respective CoS priority of 0-6) are the WRR queues and their weights are in the proportion of 1:2:8:16:32:64. The scheduling principles of the SP+WRR are as follows: l A port immediately transmits the packets in the SP queue and can transmit the packets in the WRR queue only when no packets exist in the SP queue. l If multiple SP queues exist on a port, the port compares the SP queues according to their priorities (queue 8 has the highest priority and queue 1 has the lowest priority). l According to the fixed weight value, you can allocate the time slice to each WRR queue. Then, the port transmits the packets in the corresponding WRR queue in each time slice. If a WRR queue in a time slice does not contain any packets, the WRR queue removes this time slice and then transmits the packets in the corresponding WRR queue in the next time slice.
NOTE If the traffic shaping feature of certain queues is enabled, the bandwidth is allocated first to the queues whose traffic shaping feature is enabled, according to the specified CIR. The remaining bandwidth is then allocated to the other queues based on the SP+WRR algorithm. For example, the total bandwidth of a port is 100 Mbit/s, the traffic shaping function is enabled for queues 5 and 7 on the port, and the specified CIR of each queue is 10 Mbit/s. In this case, the remaining bandwidth is 80 Mbit/s. The remaining bandwidth of 80 Mbit/s is allocated to the queues whose traffic shaping function is disabled, according to the SP+WRR algorithm.
Issue 05 (2010-10-30)
A-161
A Task Collection
Parameter Weight
Value Range An integer ranging from 1 to 64
Default Value Queue 1: 1 Queue 2: 2 Queue 3: 4 Queue 4: 8 Queue 5: 16 Queue 6: 32 Queue 7: 64 Queue 8: Unconfigurable
Description By default, queue 8 (with the CoS priority of 7) of the EMS6 board is the SP queue, and queues 1-7 (with the respective CoS priority of 0-6) are the WRR queues and their weights are 1:2:4:8:16:32:64.
A.14 Using the IEEE 802.1ag OAM

By using the IEEE 802.1ag OAM, you can maintain the Ethernet service in an end-to-end manner. A.14.1 Creating MDs A maintenance domain (MD) defines the scope and level of the Ethernet OAM. The MDs of different levels and scopes can provide differentiated OAM services to users. A.14.2 Creating MAs A maintenance domain (MD) can be divided into several independent maintenance associations (MA). By creating MAs, operators can associate specific Ethernet services with the MAs for easy Ethernet OAM operation. A.14.3 Creating MPs The functions of the IEEE 802.1ag OAM can be used only after MPs are created. A.14.4 Performing a CC Test After the continuity check (CC) test, the unidirectional link status can be checked automatically and periodically. If the link is faulty after the CC test is started at the source end, the sink equipment reports the EX_ETHOAM_CC_LOS (Huawei MP) or ETH_CFM_LOS (Standard MP) alarm. A.14.5 Performing an LB Check During a loopback (LB) check, you can check the bidirectional connectivity between the source MEP and any MEP in the same traffic flow. A.14.6 Performing a Link Trace Check Based on the loopback (LB) test, the link trace (LT) test further improves the capability to locate faults. That is, the faulty network segment can be located through only one test. A.14.7 Activating the AIS After the maintenance point (MP) where the AIS is active detects a fault, the MP transmits the AIS packet to superstratum MP for the notification of the fault. A.14.8 Performing a Ping Test By using Layer 3 ARP and ICMP packets, the ping test checks the connectivity between the processing board of an Ethernet service and the data communications equipment, such as a switch and router, the packet loss ratio of a service, and the delay time.
A Task Collection
A.14.9 Performing Performance Detection After the continuity between the MPs of the processing boards of Ethernet services is checked, the performance detection implements the on-line test of the packet loss ratio and delay time of the services.
A.14.1 Creating MDs

A maintenance domain (MD) defines the scope and level of the Ethernet OAM. The MDs of different levels and scopes can provide differentiated OAM services to users.
Prerequisite
l l l The NE user must have the authority of Operation Level or higher. The board for creating the MDs has been installed. Ethernet services have been created.

Web LCT
Procedure
Step 1 In the NE Explorer, select the relevant board, and then choose Configuration > Ethernet Maintenance > Ethernet Service OAM from the Function Free. Step 2 In the right-hand pane, click OAM Configuration to display the OAM Configuration dialog box.
NOTE
In this user interface, you can maintain or delete OAM MDs.
Step 3 Click New, and then select Create MD from the drop-down list. Step 4 In the Create MD dialog box that is displayed, set the corresponding parameters.
A Task Collection
Example
Table A-37 Parameters Field Maintenance Domain Name Maintenance Association Name Maintenance Domain Level Value For example: MD1 For example: MA1 Default Description Displays or sets the MD name. Displays or sets the maintenance association name. Displays or sets the maintenance domain level. The greater the value, the higher the priority.
Consumer High(7) Consumer Middle(6) Consumer Low(5) Provider High(4) Provider Low(3) Operator High(2) Operator Middle(1) Operator Low(0)
Operator Low(0)
Maintenance Level
Consumer High(7) Consumer Middle(6) Consumer Low(5) Provider High(4) Provider Low(3) Operator High(2) Operator Middle(1) Operator Low(0)
Operator Low(0)
The priority of the MP is the priority of the MD. The greater the value, the higher the priority.
A.14.2 Creating MAs

A maintenance domain (MD) can be divided into several independent maintenance associations (MA). By creating MAs, operators can associate specific Ethernet services with the MAs for easy Ethernet OAM operation.
A Task Collection
Prerequisite
l l The NE user must have the authority of Operation Level or higher. The MD has been created.

Web LCT
Procedure
Step 1 In the NE Explorer, select the relevant board, and then choose Configuration > Ethernet Maintenance > Ethernet Service OAM from the Function Free. Step 2 In the right-hand pane, click OAM Configuration to display the OAM Configuration dialog box.
NOTE
In this user interface, you can create or delete OAM MAs.
Step 3 Click New, and then select Create MA from the drop-down list.
Step 4 In the Create MA dialog box that is displayed, set the corresponding parameters.
Example
Table A-38 Parameters Field Maintenance Domain Name Value For example: MD1 Default Description Displays the maintenance domain name.
Issue 05 (2010-10-30)
A-165
A Task Collection
Field Maintenance Association Name
Value For example: MA1
Default -
Description Sets the maintenance association name. MA is a domain related to a service. Through MA division, the connectivity check (CC) can be performed on the network that transmits a service instance.
A.14.3 Creating MPs

The functions of the IEEE 802.1ag OAM can be used only after MPs are created.
Prerequisite
l l l The NE user must have the authority of Operation Level or higher. The Ethernet service has been created and activated. The MD and MA have been created before you create the standard MP.

Web LCT
Precautions
In an OAM test, all maintenance points that are involved in the operation of the same service flow must be in the same maintenance domain. In an existing maintenance domain involved in the same service flow, creating a maintenance point of the same level or a higher level may damage the existing maintenance domain. As a result, the OAM test fails.
Procedure
Step 1 In the NE Explorer, select an Ethernet board, and then choose Configuration > Ethernet Maintenance > Ethernet Service OAM from the Function Tree. Step 2 Click New to displayed the Create MP dialog box. Set the relevant parameters in the dialog box.
A-166
Issue 05 (2010-10-30)
A Task Collection
Step 3 Optional: Click Advanced. In the dialog box that is displayed, click Advanced.
NOTE
If an MEP is created, you can choose whether to perform the following configuration. l Activate the CC and configure the sending period of the CC test. l Set the timeout time for the LB or LT test.
Example
Table A-39 Parameters Field Maintenance Domain Name Value For example: MD1 Default NULL Description Displays the MD of the MP.
NOTE An MD is not required for a non-standard MP. For the creation of a non-standard MP, select NULL.
Maintenance Association Name
For example: MA1
NULL
Displays the MA of the created MP.

NOTE An MA is not required for a non-standard MP. For the creation of a non-standard MP, select NULL.
Node
slot-board-port
Selects the port where you want to create an MP.
Issue 05 (2010-10-30)
A-167
A Task Collection
Field VLAN ID
Value 1-4095
Default -
Description Configures the ID of the VLAN to which the service of the MP belongs. The information is contained in the OAM data packet. The MPs with the same VLAN ID in an MD can communicate with each other.
NOTE Leave this field blank for PORT services. For PORT+VLAN services, set this parameter for the services to be monitored.
MP ID
Standard MP: 00-00-0000 to FFFF-1FFF Non-standard MP: 00-00-0000 to FFFF-FF00
Uniquely identifies an MP. 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 MP on the network node. The MP ID must be unique in the entire network. Specifies the MP type defined in IEEE 802.1ag. MEP stands for Maintenance association End Point, and MIP stands for Maintenance association Intermediate Point. Only MEPs have the directions. Set the direction in which the packets are transmitted to the port as the Ingress direction, and set the direction in which the packets are transmitted from the port as the Egress direction. The direction of the MIPs can be only bidirectional. Specifies whether to activate the connectivity check (CC) function at an MP. Displays the timeout duration in the LB test. Sets the timeout duration of the LT test. Sets the time interval for sending the CCM packet at the maintenance point where the CC test is performed. l If the time interval is very short, excessive service bandwidths are used. l If the time interval is very long, the CC test is less sensitive to the service interruption. Thus, the default value is recommended.
Type
MEP MIP
MEP
Direction
Ingress Egress
CC Status
Activate Inactivate
Inactivate
LB Timeout(ms) LT Timeout(ms) CCM Sending Period(ms)
3000-60000, in increments of 100 3000-60000, in increments of 100 Standard MP: 1000 10000 6000 600000 Common MP: 1000-60000
5000 5000 Standard MP: 1000 Common MP: 5000
A-168
Issue 05 (2010-10-30)
A Task Collection
A.14.4 Performing a CC Test

After the continuity check (CC) test, the unidirectional link status can be checked automatically and periodically. If the link is faulty after the CC test is started at the source end, the sink equipment reports the EX_ETHOAM_CC_LOS (Huawei MP) or ETH_CFM_LOS (Standard MP) alarm.
Prerequisite
l l l The NE user must have the authority of Operation Level or higher. The MEP must be created. Only the MEP can enable the CC test and function as the receiving and responding end in the test.

Web LCT
Procedure
Step 1 In the NE Explorer, select an Ethernet board, and then choose Configuration > Ethernet Maintenance > Ethernet Service OAM from the Function Tree. Step 2 Select the node that you want to monitor, click OAM Operation and then select Activate CC.
TIP
l Alternatively, you can select a node, right-click, and then choose Activate CC from the shortcut menu to start the CC test. l You can select a node, right-click, and then choose Inactivate CC from the shortcut menu to stop the CC test.
NOTE
Before the CC test, set an appropriate value for CCM Sending Period (ms) according to the actual requirements.
----End
A.14.5 Performing an LB Check

During a loopback (LB) check, you can check the bidirectional connectivity between the source MEP and any MEP in the same traffic flow.
Prerequisite
l l l l l
Issue 05 (2010-10-30)
The NE user must have the authority of Operation Level or higher. The source and sink MEPs, and MIPs in the same maintenance domain must be created. Only the MEP can enable the LB check. For a standard MP, the LB test must be performed based on the MAC address when the MIP functions as the receive end of the test. On a standard MP, the CC function must be enabled before the LB test can be performed.
A Task Collection

Web LCT
Context
During the LB check, the source MEP constructs and transmits the LBM frames, and starts the timer. If the destination MP receives the LBM frames, it sends the LBR frames back to the source MEP. This indicates that the loopback is successful. If the source MEP timer times out, it indicates that the loopback fails.
Procedure
Step 1 In the NE Explorer, select an Ethernet board, and then choose Configuration > Ethernet Maintenance > Ethernet Service OAM from the Function Tree. Step 2 Select the node that you want to monitor, click OAM Operation and select Start LB. The LB Test dialog box is displayed. Step 3 Enter the ID of the LB test source MP and the ID of the sink MP. Step 4 Click Start LB. The check result is displayed.
TIP
Alternatively, you can select a node, right-click, and then choose Start LB from the shortcut menu to start the LB test.
NOTE
Before you perform the check, set LB Timeout(ms) to an appropriate value.
----End
Example
Table A-40 Parameters Field LB Source MP ID LB Sink MP ID Test Result Value For example: 00-00-0001 For example: 00-00-0002 Succeeded Failed Default Description Displays the source MP of the LT test. Displays the sink MP of the LB test. Displays the test result after an LB test or LT test is performed.
A-170
Issue 05 (2010-10-30)
A Task Collection
Field Test based on the MAC Address
Value Checked Unchecked
Default Unchecked
Description Specifies whether the test is performed based on the MAC address.
NOTE You can perform the MAC address-based LB test on only standard MPs.
LB Sink MP MAC Address
For example: 00-01-00-0F-00-00
Displays the MAC address of the sink MP.
A.14.6 Performing a Link Trace Check

Based on the loopback (LB) test, the link trace (LT) test further improves the capability to locate faults. That is, the faulty network segment can be located through only one test.
Prerequisite
l l l l The NE user must have the authority of Operation Level or higher. The source and sink MEPs, and MIPs in the same maintenance domain must be created. Only MEPs can initiate the LT test and work as the termination point in the test. In the case of a standard MP, you must activate CC before LT check.

Web LCT
Context
l During the LT check, the source MEP constructs and transmits LTM frames and starts the timer. All the MPs that receive the LTM frames send the LTR frame response. According to the LTR frame response, you can verify all the MIPs that pass from the source MEP to the destination MEP.
Performing an LT check does not affect the service.
Procedure
Step 1 In the NE Explorer, select the required Ethernet board, and then choose Configuration > Ethernet Maintenance > Ethernet Service OAM from the Function Tree. Step 2 Select the node that you want to monitor, click OAM Operation and select Start LT. The LT Test dialog box is displayed.
A Task Collection
Step 3 Enter the LT test source maintenance point ID and sink maintenance point ID. Step 4 Click Start LT and the check result is displayed.
TIP
Alternatively, you can right-click a node and choose Start LT from the shortcut menu to start the LT test.
NOTE
Before you perform the check, set an appropriate LT Timeout(ms) as required.
----End
Example
Table A-41 Parameters Parameter LT Source MP ID Value Range For example: 00-00-0001 Default Value Description This parameter displays the source maintenance point in the LT test. This parameter displays the source maintenance point in the LT test. This parameter displays the maintenance point that responds to the test. This parameter displays the type of the responding maintenance point in each LT test. This parameter displays the number of hops from the maintenance source endpoint to a maintenance intermediate point, namely, That is, the number of responding intermediate points from the maintenance source point to a certain responding point. This parameter displays the test result after an LB test or LT test is performed.
LT Sink MP ID
For example: 00-00-0002
Responding MP
Responding MP Type
MEP MIP
Hop Count
For example: 1
Test Result
Succeeded Failed
A-172
Issue 05 (2010-10-30)
A Task Collection
A.14.7 Activating the AIS

After the maintenance point (MP) where the AIS is active detects a fault, the MP transmits the AIS packet to superstratum MP for the notification of the fault.
Prerequisite
l l The NE user must have the authority of Operation Level or higher. The source and sink MEPs, and MIPs in the same maintenance domain must be created.

Web LCT
Procedure
Step 1 In the NE Explorer, select the required Ethernet board, and then choose Configuration > Ethernet Maintenance > Ethernet Service OAM from the Function Tree. Step 2 Select the node to be monitored. Double-click or right-click AIS Active State and then select Active or Deactive. Step 3 Click Apply. ----End
Example
Table A-42 Parameters Field AIS Active State Value Range Active Inactive Client Layer Level 1 to 7 7 Default Value Inactive Description This parameter displays or specifies the AIS activation status. This parameter displays or specifies the level of the MP where AIS fault messages are suppressed. If Level of the MP is set to Operator High(2) and Client Layer Level to 4, this MP reports AIS packets to only the MP whose Level is Provider Low(3) or Level is higher than Consumer Low(5).
NOTE Usually, if the Level of an MP is set to n, its Client Layer Level is set to n+1.
Issue 05 (2010-10-30)
A-173
A Task Collection
Field AIS Period(ms)
Value Range 1000 60000
Default Value -
Description This parameter displays or specifies the AIS period.
A.14.8 Performing a Ping Test

By using Layer 3 ARP and ICMP packets, the ping test checks the connectivity between the processing board of an Ethernet service and the data communications equipment, such as a switch and router, the packet loss ratio of a service, and the delay time.
Prerequisite
l l l The NE user must have the authority of Operation Level or higher. The source and sink MEPs, and MIPs in the same maintenance domain must be created. You must be aware of the IP addresses of the source MP and the sink MP for the ping test.

Web LCT
Context
The source end of the ping test obtains the IP addresses of the source MP and sink MP, and constructs and sends ARP packets and ICMP packets. The MP that receives the ARP packets or ICMP packets parses the packets, and responds to the source end. After receiving the response packet, the source end reports the ping test result to the NE software (including the ratio of packet loss and time delay) based on the response packet.
Procedure
Step 1 In the NE Explorer, select the required Ethernet board, and then choose Configuration > Ethernet Maintenance > Ethernet Service OAM from the Function Tree. Step 2 Select the node that you want to monitor, click OAM Operation and select Start Ping. The Ping Test dialog box is displayed. Step 3 Select Send Mode. Then set Packet Length, Timeout, and Ping Attempts for the ping packet. Step 4 Set Destination IP Address and Local IP Address. Step 5 Click Start Ping. The check result is displayed. ----End
A-174
Issue 05 (2010-10-30)
A Task Collection
Example
Table A-43 Parameters Parameter Send Mode Value Range Burst Mode Continue Mode Default Value Burst Mode Description This parameter displays a mode in which ping test packets are sent. Burst Mode: sending the ping test packets according to the set sending times. Continue Mode: sending the ping test packets constantly. When this mode is selected, the sending times cannot be set. Packet Length 64 to 1522 bytes 64 This parameter displays the packet length of the ping test packet. This parameter displays the timeout time. If the ping test packet has been sent and the source MP does not receive the returned packet from the sink MP after timeout, it indicates that the ping test fails. This parameter displays the times of sending ping test packets when Send Mode is set to Burst Mode. This parameter displays the IP address of the sink MP. This parameter displays the IP address of the source MP.
Timeout
3 to 60 seconds
Ping Attempts
1 to 1000 attempts
Destination IP Address
0.0.0.0
Local IP Address
0.0.0.0
Issue 05 (2010-10-30)
A-175
A Task Collection
A.14.9 Performing Performance Detection

After the continuity between the MPs of the processing boards of Ethernet services is checked, the performance detection implements the on-line test of the packet loss ratio and delay time of the services.
Prerequisite
l l The NE user must have the authority of Operation Level or higher. The source and sink MEPs, and MIPs in the same maintenance domain must be created.

Web LCT
Context
After the continuity between the MPs of the processing boards of Ethernet services is checked, the performance detection implements the on-line test of the packet loss ratio and delay time of the services. The implementation principle of the performance detection is as follows: The source MP initiates multiple LB tests, and then the MP collects information about the packet loss ratio and delay time.
Procedure
Step 1 In the NE Explorer, select an Ethernet board, and then choose Configuration > Ethernet Maintenance > Ethernet Service OAM from the Function Tree. Step 2 Select the node that you want to monitor, click OAM Operation and select Performance Detect. The Performance Detect dialog box is displayed. Step 3 Select Send Mode. Then set Frame Length, Timeout, and Detect Attempts for the tested packet. Step 4 Set Source MP ID and Destination MP ID. Step 5 Click Start Detect. The check result is displayed. ----End
A-176
Issue 05 (2010-10-30)
A Task Collection
Example
Table A-44 Parameters Parameter Send Mode Value Burst Mode Continue Mode Default Burst Mode Description Specifies a mode in which performance detection packets are sent. Burst Mode: sending the detection packets according to the set sending times Continue Mode: sending the detection packets constantly. When this mode is selected, the sending times cannot be set. Packet Length 64 to 1522 bytes 64 Specifies the length of a performance detection packet. Specifies the timeout time. If the performance detection packet has been sent and the source MP does not receive the returned packet from the sink MP after timeout, it indicates that the performance detection fails. Specifies the times of sending performance detection packets when Send Mode is set to Burst Mode. Specifies the ID of the source MP that sends detection packets.
Timeout
3 to 60 seconds
Detect Attempts
1-1000(Times)
Source MP ID
Standard MP: 00-00-0000 to FF-FF-1FFF Common MP: 00-00-0000 to FF-FF-FF00
Destination MP ID
Standard MP: 00-00-0000 to FF-FF-1FFF Common MP: 00-00-0000 to FF-FF-FF00
Specifies the ID of the sink MP involved in the performance detection.
Issue 05 (2010-10-30)
A-177
A Task Collection
A.15 Using the IEEE 802.3ah OAM

With the IEEE 802.3ah OAM, you can maintain point-to-point Ethernet links. A.15.1 Enabling the OAM Auto-Discovery Function The IEEE 802.3ah OAM is realized based on the OAM auto-discovery function. After the OAM auto-discovery succeeds, the equipment automatically monitors the fault and performance of the link. A.15.2 Enabling the Link Event Notification After the link event notification is enabled on the local equipment, if the OAM detects a link fault and link performance event, the opposite equipment is informed. A.15.3 Modifying the Parameters of the OAM Error Frame Monitoring Threshold The threshold for the OAM error frame monitoring is a standard for the OAM to detect the link performance. Usually, the default value is used. You can modify the value according to the situation of the link. A.15.4 Performing the Remote Loopback After the Ethernet port on the local equipment sends data to the port on the interconnected equipment, the local end can request the opposite end to return the data. A.15.5 Enabling the 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.
A.15.1 Enabling the OAM Auto-Discovery Function

The IEEE 802.3ah OAM is realized based on the OAM auto-discovery function. After the OAM auto-discovery succeeds, the equipment automatically monitors the fault and performance of the link.
Prerequisite

Web LCT
Context
The OAM auto-discovery is realized through the auto-negotiation between the local equipment and the opposite equipment. If the negotiation fails, the local equipment reports an alarm. After the OAM auto-discovery succeeds, the link performance is monitored according to the error frame threshold. You can set the error frame threshold on the NMS. l The OAM mode includes the active mode and the passive mode. For two interconnected systems, the OAM mode of either or both systems must be the active mode. Otherwise, the OAM auto-discovery fails. If the OAM modes of the two systems are passive modes, a fault occurs on the line, or one system fails to receive the OAM protocol message, an alarm is reported, indicating that the OAM auto-discovery fails.
A-178
A Task Collection
Procedure
Step 1 In the NE Explorer, select an Ethernet board, and then choose Configuration > Ethernet Maintenance > Ethernet Port OAM from the Function Tree. Step 2 Click the OAM Parameter tab, and then set OAM Working Mode. Select Enabled from the Enable OAM Protocol drop-down list.
Step 3 Click Apply. Step 4 Click the Remote OAM Parameter tab. Click Query to obtain the OAM capability of the peer end. ----End
Example
Table A-45 Parameters Field Port Enable OAM Protocol Value For example: PORT1 Enabled Disabled Default Disabled Description Displays the port name. Specifies whether the point-to-point OAM protocol (IEEE 802.3ah protocol) is enabled. After the OAM protocol is enabled, the current Ethernet port starts to use the preset mode to set up an OAM connection with the peer end.
Issue 05 (2010-10-30)
A-179
A Task Collection
Field OAM Working Mode
Value Active Passive
Default Active
Description IEEE Specifies a negotiation mode specified in IEEE 802.3ah. It can be set to Active or Passive. 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 peer end to send the OAM connection request.
Remote Alarm Support for Link Event
Enabled Disabled
Enabled
Specifies whether the detected link event is reported to the peer end (for example, Error Frame Period Threshold, Error Frame Monitor Threshold, and Error Frame Second Threshold). Displays whether the unidirectional operation is supported. Displays the maximum length of the OAM packets. Specifies the loopback status of a port on a board.
Unidirectional Operation Max. OAM Packet Length (byte) Loopback Status
Enabled Disabled For example: 1000
Disabled
Initiate Loopback at Local Respond Loopback of Remote Non-Loopback
Non-Loopback
A.15.2 Enabling the Link Event Notification

After the link event notification is enabled on the local equipment, if the OAM detects a link fault and link performance event, the opposite equipment is informed.
Prerequisite
l l The NE user must have the authority of Operation Level or higher. Make sure that the OAM auto-discovery succeeds at both ends.
A-180
Issue 05 (2010-10-30)
A Task Collection

Web LCT
Context
When the OAM auto-discovery succeeds at both ends, the link fault detection and performance detection are automatically started. l 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. l 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 Web LCT. 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 Web LCT. Based on the alarm, you can determine the fault type.
Procedure
Step 1 In NE Explorer, select the required Ethernet board, and then choose Configuration > Ethernet Maintenance > Ethernet Port OAM from the Function Tree. Step 2 Click the OAM Parameter tab, and then set Remote Alarm Support for Link Event to Enabled.
Issue 05 (2010-10-30)
A-181
A Task Collection
Example
Table A-46 Parameters Field Port Enable OAM Protocol Value For example: PORT1 Enabled Disabled Default Disabled Description Displays the port name. Specifies whether the point-to-point OAM protocol (IEEE 802.3ah protocol) is enabled. After the OAM protocol is enabled, the current Ethernet port starts to use the preset mode to set up an OAM connection with the peer end. OAM Working Mode Active Passive Active IEEE Specifies a negotiation mode specified in IEEE 802.3ah. It can be set to Active or Passive. 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 peer end to send the OAM connection request. Remote Alarm Support for Link Event Enabled Disabled Enabled Specifies whether the detected link event is reported to the peer end (for example, Error Frame Period Threshold, Error Frame Monitor Threshold, and Error Frame Second Threshold). Displays whether the unidirectional operation is supported. Displays the maximum length of the OAM packets.
Unidirectional Operation Max. OAM Packet Length (byte)
Disabled
A-182
Issue 05 (2010-10-30)
A Task Collection
Field Loopback Status
Value Initiate Loopback at Local Respond Loopback of Remote Non-Loopback
Default Non-Loopback
Description Specifies the loopback status of a port on a board.
A.15.3 Modifying the Parameters of the OAM Error Frame Monitoring Threshold
The threshold for the OAM error frame monitoring is a standard for the OAM to detect the link performance. Usually, the default value is used. You can modify the value according to the situation of the link.
Prerequisite
l l The NE user must have the authority of Operation Level or higher. The IEEE 802.3ah OAM function must be enabled on the remote equipment. In addition, OAM auto-discovery succeeds at both ends.

Web LCT
Context
After the OAM auto-discovery succeeds, set Error Frame Period Window (Frame) and Error Frame Monitor Threshold, and set Remote Alarm Support for Link Event to Enabled 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. Therefore, the local end reports the ETHOAM_RMT_SD alarm.
Procedure
Step 1 In NE Explorer, select the required Ethernet board, and then choose Configuration > Ethernet Maintenance > Ethernet Port OAM from the Function Tree. Then, click the OAM Error Frame Monitor tab. Step 2 Select a port and set the error frame monitoring parameters.
Issue 05 (2010-10-30)
A-183
A Task Collection
Example
Table A-47 Parameters Parameter Error Frame Monitor Window (ms) Value Range 1000 to 60000, in step of 100 Default Value Description In the specified Error Frame Monitor Window (ms), if the number of error frames exceeds the specified Error Frame Monitor Threshold (Entries) due to the link degradation, the link event alarm is reported. This parameter specifies the threshold of monitoring error frames. Within the specified value of Error Frame Period Window (frame), if the number of error frames on the link exceeds the preset value of Error Frame Period Threshold (frame), an alarm is reported.
Error Frame Monitor Threshold (Entries) Error Frame Period Window (frame)
1 to 4294967295, in step of 1 For an FE interface: 14880 to 8928000, in step of 1 For a GE interface: 148800 to 89280000, in step of 1
Error Frame Period Threshold (frame) Error Frame Second Window (s)
1 to 892800000, in step of 1 10 to 900, in step of 1
This parameter specifies the threshold of monitoring the error frame period. If any error frame occurs in one second, this second is called an errored frame second. Within the specified value of Error Frame Second Window(s), if the number of error frames on the link exceeds the preset value of Error Frame Second Threshold (s), an alarm is reported.
A-184
Issue 05 (2010-10-30)
A Task Collection
Parameter Error Frame Second Threshold (s)
Value Range 1 to 900, in step of 1
Default Value -
Description This parameter specifies the threshold of monitoring error frame seconds.
A.15.4 Performing the Remote Loopback

After the Ethernet port on the local equipment sends data to the port on the interconnected equipment, the local end can request the opposite end to return the data.
Prerequisite
l l l l The NE user must have the authority of Operation Level or higher. Make sure that the OAM auto-discovery succeeds. For the equipment where the loopback is initiated, OAM Working Mode must be set to Active. The remote equipment that responds to the loopback must support the remote loopback. In addition, the function of responding to the remote loopback must be enabled on the remote equipment.

Web LCT
Context
l l The OptiX RTN 620 does not respond to a remote loopback. 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 loopback initiating state and reports the loopback initiating alarm. After the remote loopback function is enabled, service packets except the OAMPDU are looped back at the remote end. After using the remote loopback function to locate faults and test link performance, 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 clears automatically.
l l
Procedure
Step 1 In NE Explorer, select the required Ethernet board, and then choose Configuration > Ethernet Maintenance > Ethernet Port OAM from the Function Tree. Step 2 Click the OAM Parameter tab. Select the port that needs to initiate a loopback, and choose Enable Remote Loopback from the drop-down list of OAM. Step 3 Click Apply. ----End
A Task Collection
Example
Table A-48 Parameters Field Port Enable OAM Protocol Value For example: PORT1 Enabled Disabled Default Disabled Description Displays the port name. Specifies whether the point-to-point OAM protocol (IEEE 802.3ah protocol) is enabled. After the OAM protocol is enabled, the current Ethernet port starts to use the preset mode to set up an OAM connection with the peer end. OAM Working Mode Active Passive Active IEEE Specifies a negotiation mode specified in IEEE 802.3ah. It can be set to Active or Passive. 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 peer end to send the OAM connection request. Remote Alarm Support for Link Event Enabled Disabled Enabled Specifies whether the detected link event is reported to the peer end (for example, Error Frame Period Threshold, Error Frame Monitor Threshold, and Error Frame Second Threshold). Displays whether the unidirectional operation is supported. Displays the maximum length of the OAM packets.
Unidirectional Operation Max. OAM Packet Length (byte)
Disabled
A-186
Issue 05 (2010-10-30)
A Task Collection
Field Loopback Status
Value Initiate Loopback at Local Respond Loopback of Remote Non-Loopback
Default Non-Loopback
Description Specifies the loopback status of a port on a board.
A.15.5 Enabling the 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.
Prerequisite
l l The NE user must have the authority of Operation Level or higher. The physical Ethernet port to be detected must be enabled.

Web LCT
Context
When the self-loop detection is enabled for an external physical port, if the self-loop situation occurs at the port, the ETHOAM_SELF_LOOP alarm is reported.
Procedure
Step 1 In NE Explorer, select the required Ethernet board, and then choose Configuration > Ethernet Interface Management > Ethernet Interface from the Function Tree. Step 2 Configure the physical Ethernet port to be detected. 1. 2. Select External Port and then click the Advanced Attributes tab. Enable Loop Detection.
3.
Click Apply.
----End
A Task Collection
Example
Table A-49 Parameters Parameter Port Value Range PORTn Default Value Description Indicates the PORT port. The letter n indicates the number of the PORT port. Enables or disables broadcast packet suppression. When the broadcast packet suppression function is enabled, if the broadcast packet occupies a bandwidth that exceeds the overall bandwidth of the port multiplied by the suppression threshold, the broadcast packet is suppressed. Specifies whether to enable loop detection, which is used to check whether a loop exists on a port.
Enabling Broadcast Packet Suppression Broadcast Packet Suppression Threshold
Disabled Enabled 10%-100%
Disabled
Loop Detection
Disabled Enabled
Disabled
A.16 Using RMON

Remote monitoring (RMON) is mainly used to monitor the data traffic on a network segment or on the entire network. Currently, it is one of the widely used network management standards. A.16.1 Browsing the Performance Data in the Statistics Group of an Ethernet Port After you configure an RMON statistics group for an Ethernet port, you can browse the realtime statistical performance data of the port. A.16.2 Configuring an Alarm Group for an Ethernet Port After you configure an RMON alarm group for an Ethernet port, you can monitor the performance threshold-crossing events of the port in the long term. A.16.3 Configuring a History Control Group When configuring a history control group for an Ethernet port, you configure how the history performance data of the port is monitored. The Ethernet board monitors the history performance
A Task Collection
data of each port at the default sampling interval of 30 minutes. An Ethernet board stores 50 history performance data items. A.16.4 Browsing the Performance Data in the History Group of an Ethernet Port After you configure an RMON history group for an Ethernet port, you can browse the statistical history performance data of the port.
A.16.1 Browsing the Performance Data in the Statistics Group of an Ethernet Port
After you configure an RMON statistics group for an Ethernet port, you can browse the realtime statistical performance data of the port.
Prerequisite
l l The NE user must have the authority of Operation Level or higher. The associated boards must be added to the Slot Layout.

Web LCT
Procedure
Step 1 Select the corresponding board from the Object Tree in NE Explorer. Choose Performance > RMON Performance from the Function Tree. Step 2 Click the Statistics Group tab. Step 3 Set the required parameters for the statistics group. Step 4 Click Resetting begins.
NOTE
If you click Start, the register of the statistics group is not reset to clear the existing data.
----End
Example
Table A-50 Parameters Parameter Sampling Interval Display Accumulated Value Value Range 5-150 seconds Selected Deselected Default Value 5 Deselected Description This parameter specifies the period of sampling the performance data. This parameter specifies whether the displayed performance value is the increment of the register value compared with the register value at the end of the previous sampling interval or the current absolute value of the register.
Issue 05 (2010-10-30)
A-189
A Task Collection
A.16.2 Configuring an Alarm Group for an Ethernet Port

After you configure an RMON alarm group for an Ethernet port, you can monitor the performance threshold-crossing events of the port in the long term.
Prerequisite

Web LCT
Procedure
Step 1 Select the corresponding board from the Object Tree in NE Explorer. Choose Performance > RMON Performance from the Function Tree. Step 2 Click the Alarm Group tab. Step 3 Set the required parameters for the alarm group. Step 4 Click Apply. ----End
Example
Table A-51 Parameters Parameter Sampling Interval (s) Report Mode Value Range 5-600 Report All Report in Case of Upper ThresholdCrossing Report in Case of Lower ThresholdCrossing Upper Threshold Lower Threshold Monitor Status 1-4294967295 0-4294967294 Enabled Disabled 1 0 Disabled This parameter specifies the upper threshold of the performance data. This parameter specifies the lower threshold of the performance data. This parameter specifies whether to monitor the object. Default Value 10 Report All Description This parameter specifies the period of sampling the performance data. This parameter specifies how the performance threshold-crossing events are reported.
A-190
Issue 05 (2010-10-30)
A Task Collection
A.16.3 Configuring a History Control Group

When configuring a history control group for an Ethernet port, you configure how the history performance data of the port is monitored. The Ethernet board monitors the history performance data of each port at the default sampling interval of 30 minutes. An Ethernet board stores 50 history performance data items.
Prerequisite

Web LCT
Procedure
Step 1 Select the corresponding board from the Object Tree in NE Explorer. Choose Performance > RMON Performance from the Function Tree. Step 2 Click the History Control Group tab. Step 3 Set the required parameters for the history group. Step 4 Click Apply. ----End
Example
Table A-52 Parameters Parameter History Control Group Value Range 30-Second 30-Minute Custom Period1 Custom Period2 Sampling Interval (s) l 300-43200 (Custom Period1) l 300-86400 (Custom Period2) Number of Items Monitor Status 1-50 Enabled Disabled l 900 (Custom Period1) l 86400 (Custom Period2) This parameter is valid only when History Control Group is set to Custom Period1 or Custom Period2. This parameter specifies the period of sampling the performance data. Default Value 30-Second Description This parameter specifies the period of sampling the history performance data.
50 Disabled
This parameter specifies the number of performance data items. This parameter specifies whether to monitor the object.
Issue 05 (2010-10-30)
A-191
A Task Collection
A.16.4 Browsing the Performance Data in the History Group of an Ethernet Port
After you configure an RMON history group for an Ethernet port, you can browse the statistical history performance data of the port.
Prerequisite
l l l The NE user must have the authority of Operation Level or higher. The associated boards must be added to the Slot Layout. The monitored objects and the corresponding history table type must be set in the History Control Group tab.

Web LCT
Procedure
Step 1 Select the corresponding board from the Object Tree in NE Explorer. Choose Performance > RMON Performance from the Function Tree. Step 2 Click the History Group tab. Step 3 Set the required parameters for the history group. Step 4 Click Query. ----End
Example
Table A-53 Parameters Parameter History Table Type Value Range 30-Second 30-Minute Custom Period1 Custom Period2 Start Item 1-50 1 This parameter specifies the item from which the system queries the history performance data. 1 represents the earliest item. This parameter specifies the item after which the system stops querying the history performance data. The value of this parameter must not be more than the sum of Start Item plus 9. Default Value 30-Second Description This parameter specifies the period of sampling the history performance data.
End Item
1-50
A-192
Issue 05 (2010-10-30)
A Task Collection
A.17 Configuring LPT

After enabling the LPT function for an Ethernet service, you need to configure the LPT port and the relevant information. A.17.1 Configuring LPT for Point-to-Point Services After enabling the LPT function for an Ethernet service, you need to configure the corresponding LPT port and relevant information. A.17.2 Configuring LPT for Point-to-Multipoint Services To configure LPT for point-to-multipoint services, you need to specify the corresponding relationships between aggregation ports and access ports and LPT parameters.
A.17.1 Configuring LPT for Point-to-Point Services

After enabling the LPT function for an Ethernet service, you need to configure the corresponding LPT port and relevant information.
Prerequisite
l l l l l The NE user must have the authority of Operation Level or higher. The corresponding Ethernet board must be added to the Slot Layout. The Ethernet board must support the LPT function for point-to-point services. The PORT-based Ethernet private line service must be created and activated. The Ethernet services must be configured as pure pass-through services.

Web LCT
Precautions
NOTE
l Point-to-point LPT and point-to-multipoint LPT are mutually exclusive. On the same board, you can select only one configuration mode to implement the LPT function. l In the case of point-to-point LPT, services are configured as pure transparently transmitted services.
Procedure
Step 1 In the NE Explorer, select the Ethernet board, and choose Configuration > Ethernet Interface Management > LPT Management from the Function Tree. Step 2 Click Query. Step 3 Select a PORT and a VCTRUNK port, and then set the following parameters.
NOTE
If LPT is enabled, you can set PORT-Type Port Hold-off Time(ms) and VCTRUNK Port Hold-off Time(ms) according to actual requirements.
Issue 05 (2010-10-30)
A-193
A Task Collection
Parameters
Table A-54 Parameters of the point-to-point LPT Parameter Port VCTRUNK Port Value Range Default Value Description This parameter specifies the external interface. This parameter specifies the VCTRUNK port where EPL services are transparently transmitted. This parameter specifies the direction of the EPL services that are transparently transmitted. The direction is Positive if the source port is a PORT and the sink port is a VCTRUNK port. The direction is Reverse if the source port is a VCTRUNK port and the sink port is a PORT. LPT Yes No Bearer Mode GFP (HUAWEI) Ethernet PORT-Type Port Hold-off Time (ms) 0 to 10000 100 GFP (HUAWEI) No This parameter specifies whether to use LPT. l This parameter is valid only when the LPT occurs. l This parameter specifies the bearer mode of LPT frames. l This parameter is valid only when the LPT occurs. l When the LPT switching is enabled, the port informs the opposite end after the hold-off time.
Direction
Positive Reverse
A-194
Issue 05 (2010-10-30)
A Task Collection
Parameter VCTRUNK Port Hold-off Time (ms)
Default Value 100
Description l This parameter is valid only when the LPT occurs. l When the LPT switching is enabled, the port informs the opposite end after the hold-off time.
A.17.2 Configuring LPT for Point-to-Multipoint Services

To configure LPT for point-to-multipoint services, you need to specify the corresponding relationships between aggregation ports and access ports and LPT parameters.
Prerequisite
l l l l l The NE user must have the authority of Operation Level or higher. The corresponding Ethernet board must be added to the Slot Layout. The Ethernet board must support the LPT function for point-to-multipoint services. The PORT-based Ethernet private line service must be created and activated. The Ethernet services must be configured as pure pass-through services.

Web LCT
Precautions
NOTE
l Point-to-point LPT and point-to-multipoint LPT are mutually exclusive. On the same board, you can select only one configuration mode to implement the LPT function. l In the case of point-to-point LPT, services are configured as pure transparently transmitted services.
CAUTION
Before configuring the point-to-multipoint LPT function, make sure that the following two conditions are met. Otherwise, the services may be interrupted. l l The data services are displayed in the tree topology. The data service topology is consistent with the topology of the LPT.
Procedure
Step 1 In the NE Explorer, select the Ethernet board, and choose Configuration > Ethernet Interface Management > LPT Management from the Function Tree.
A Task Collection
Step 2 Click the PtoMP LPT button. Then, the LPT Management dialog box is displayed. Step 3 Click New. Then, the Create LPT dialog box is displayed. Step 4 Set the parameters of point-to-multipoint LPT.
----End
Parameters
Table A-55 Parameters of aggregation points Parameter Port Value Range Default Value Description This parameter specifies the port where the aggregation point resides. l This parameter is valid only when the LPT occurs. l You can set this parameter manually only if the selected port is a VCTRUNK port.
Bearer Mode
GFP (HUAWEI) Ethernet
GFP (HUAWEI)
A-196
Issue 05 (2010-10-30)
A Task Collection
Parameter Hold-Off Time(ms)
Default Value 0
Description When the LPT switching is enabled, the port informs the opposite end after the hold-off time.
Table A-56 Parameters of access points Parameter Port Value Range Default Value Description This parameter specifies the port where the access point resides. l This parameter is valid only when the LPT occurs. l You can set this parameter manually only if the selected port is a VCTRUNK port.
Bearer Mode
GFP(HUAWEI) Ethernet
GFP(HUAWEI)
A.18 Configuring Ethernet Ports

OptiX RTN 620The supported Ethernet ports include the external FE/GE ports on Ethernet boards, internal VCTRUNK ports, and IFUP ports on the IFH2 board. A.18.1 Configuring External Ethernet Ports When an NE uses external ports of Ethernet boards to gain access to Ethernet services, the attributes of external ports need to be configured so that external ports can work with the data communication equipment on the client side to provide normal access to Ethernet services. A.18.2 Configuring the Internal Port of the Ethernet Board When an NE transmits Ethernet services to a line through an internal port (that is, VCTRUNK) of an Ethernet board, the attributes of the internal port need to be set. Thus, the Ethernet board works with the Ethernet board at the opposite end to achieve the transmission of the Ethernet services on the network. A.18.3 Configuring Ethernet Ports of the IFH2 Board When an NE transmits Ethernet services through Hybrid radio, the attributes of the Ethernet port of the IFH2 board need to be set. A.18.4 Modifying the Type Field of Jumbo Frames By default, the type field of Jumbo frames processed by Ethernet boards is set to 0x8700. A.18.5 Modifying the Type Field of QinQ Frames
A Task Collection
By default, the type field (that is, the TPID in an S-TAG) of QinQ frames processed by Ethernet switching boards is set to 0x8100. A.18.6 Dynamically Increasing/Decreasing the VCTRUNK Bandwidth When the LCAS function is enabled on an NE, you can dynamically increase or decrease the VCTRUNK-bound paths to increase or decrease the bandwidth. The operation does not affect services.

When an NE uses external ports of Ethernet boards to gain access to Ethernet services, the attributes of external ports need to be configured so that external ports can work with the data communication equipment on the client side to provide normal access to Ethernet services.
Prerequisite
l l The NE user must have the authority of Operation Level or higher. Ethernet switching boards must be added on the Slot Layout.

Web LCT
Precautions
l The Ethernet boards supported by the OptiX RTN 620 are the EFT4, EMS6, and EFP6. Ethernet ports FE1-FE4 of an EFT4 board correspond to PORT1-PORT4 respectively. The EFT4 board does not support the setting of TAG attributes, network attributes, and advanced attributes. Ethernet ports FE1-FE4 of an EMS6 board correspond to PORT1-PORT4 respectively. Ports GE1 and GE2 of an EMS6 board correspond to PORT5 and PORT6 respectively. Ethernet ports FE1-FE6 of an EFP6 board correspond to PORT1-PORT6 respectively. l The following procedures describe how to configure the external port of an EMS6 board.
Procedure
Step 1 In the NE Explorer, select the required Ethernet board, and then choose Configuration > Ethernet Interface Management > Ethernet Interface from the Function Tree. Step 2 Select External Port. Step 3 Set the basic attributes of the port. 1. 2. Click the Basic Attributes tab. Set the basic attributes of the port.
3.
Click Apply.
Step 4 Set the flow control mode of the port. 1. 2.

A-198
Click the Flow Control tab. Set the flow control mode of the port.
A Task Collection
3. 1. 2.
Click Apply. Click the TAG Attributes tab. Set the TAG attributes of the port.
Step 5 Optional: Set the TAG attributes of the port.
3. 1. 2.
Click Apply. Click the Network Attributes tab. Set the network attributes of the port.
Step 6 Optional: Set the network attributes of the port.
3. 1. 2.
Click Apply. Click the Advanced Attributes tab. Set the advanced attributes of the port.
Step 7 Optional: Specifies the network attribute of a port.
3.
Click Apply.
----End
Example
Table A-57 Parameters for the basic attributes Parameter Enabled/Disabled Value Range Enabled Disabled Default Value Disabled Description l If the port gains access to services, set this parameter to Enabled. In the case of other ports, set this parameter to Disabled. l If you set this parameter to Enabled for the port that does not gain access to services, an ETH_LOS alarm may be generated.
Issue 05 (2010-10-30)
A-199
A Task Collection
Parameter Working Mode
Value Range
Default Value
Description l The Ethernet ports of different types support different working modes. l When the equipment at the opposite end works in the auto-negotiation mode, set the working mode of the equipment at the local end to Auto-Negotiation. l When the equipment at the opposite end works in full-duplex mode, set the working mode of the equipment at the local end to 10M Full-Duplex, 1000 Full-Duplex or 1000M Full-Duplex, depending on the port rate of the equipment at the opposite end. l When the equipment at the opposite end works in half-duplex mode, set the working mode of the equipment at the local end to 10M Full-Duplex, 100M Full-Duplex or set to AutoNegotiation, depending on the port rate of the equipment at the opposite end. l The GE optical interfaces on the EMS6 support only auto-negotiation and 1000M full duplex working modes.
l In the case of the Auto-Negotiation EFT4 board: AutoNegotiation 10M FullDuplex 100M FullDuplex l In the case of the EMS6 board: AutoNegotiation 10M HalfDuplex 10M FullDuplex 100M HalfDuplex 100M FullDuplex 1000M FullDuplex l In the case of the EFP6 board: AutoNegotiation 10M HalfDuplex 10M FullDuplex 100M HalfDuplex 100M FullDuplex
A-200
Issue 05 (2010-10-30)
A Task Collection
Parameter Maximum Frame Length
Value Range In the case of the EFT4 board: 1518-1535 In the case of the EMS6 board: 1518-9600 In the case of the EFP6 board: 1518-2000
Default Value 1522
Description l The value of this parameter is greater than the maximum length of a frame among all the data frames to be transmitted. l If Jumbo frames are not considered and the accessed services are ordinary Ethernet frames that use VLAN tags or do not have VLAN tags, it is recommended that you use the default value. If the access services include services (such as QinQ services) that use two-layer tags, it is recommended that you set this parameter to 1526 or a greater value.
MAC LoopBack
Non-Loopback Inloop
Non-Loopback
l When you set this parameter to Inloop, the Ethernet frame signals to be sent to the opposite end are looped back. l In normal cases, it is recommended that you use the default value.
PHY LoopBack
Non-Loopback Inloop
Non-Loopback
l When you set this parameter to Inloop, the Ethernet physical signals to be sent to the opposite end are looped back. l In normal cases, it is recommended that you use the default value.
Issue 05 (2010-10-30)
A-201
A Task Collection
Table A-58 Parameters for flow control Parameter NonAutonegotiation Flow Control Mode Value Range Disabled Enable Symmetric Flow Control Send Only Receive Only Default Value Disabled Description l This parameter is valid only when you set Working Mode to AutoNegotiation. l When you set this parameter to Enable Symmetric Flow Control, the port can send the PAUSE frames and process the received PAUSE frames. l When you set this parameter Send Only, the port can send the PAUSE frames in the case of congestion but cannot process the received PAUSE frames. l When you set this parameter to Send Only, the port can process the received PAUSE frames but cannot send the PAUSE frames in the case of congestion. l The non-autonegotiation flow control mode of the equipment at the local end must be the same as the nonautonegotiation flow control mode of the equipment at the opposite end.
A-202
Issue 05 (2010-10-30)
A Task Collection
Parameter Autonegotiation Flow Control Mode
Value Range Disabled Enable Symmetric Flow Control Enable Symmetric/ Dissymmetric Flow Control Enable Symmetric Flow Control
Default Value Disabled
Description l This parameter is valid only when you set Working Mode to AutoNegotiation. l When you set this parameter to Enable Symmetric Flow Control, the port can send the PAUSE frames and process the received PAUSE frames. l When you set this parameter to Enable Symmetric Flow Control, the port can send the PAUSE frames in the case of congestion but cannot process the received PAUSE frames. l When you set this parameter to Enable Symmetric/Dissymmetric Flow Control, the port can perform as follows: Sends and processes the PAUSE frames. Sends but does not process the PAUSE frames. Processes but does not send PAUSE frames. l The auto-negotiation flow control mode of the equipment at the local end must be the same as the auto-negotiation flow control mode of the equipment at the opposite end.
Table A-59 Parameters for the TAG attributes Parameter TAG Value Range Tag Aware Access Hybrid Default Value Tag Aware Description l When ports are configured with TAG flags, the ports process frames by using the methods provided in Table A-62. l If all the accessed services are frames with the VLAN tag (tagged frames), set this parameter to Tag Aware. l If all the accessed services are frames without the VLAN tag (untagged frames), set this parameter to Access. l If the accessed services contain tagged frames and untagged frames, set this parameter to Hybrid.
Issue 05 (2010-10-30)
A-203
A Task Collection
Parameter Default VLAN ID
Default Value 1
Description l This parameter is valid only when you set TAG to Access or Hybrid. l For details about the functions of this parameter, see Table A-62. l You need to set this parameter according to the actual situation.
VLAN Priority
0 to 7
l This parameter is valid only when you set TAG to Access or Hybrid. l For details about the functions of this parameter, see Table A-62. l When the VLAN priority is required to divide streams or to be used for other purposes, set this parameter according to the actual situation. Generally, it is recommended that you use the default value.
Entry Detection
Enabled Disabled
Enable
l Indicates whether to check the incoming packets from the port according to the TAG attributes. l You need to set this parameter according to the actual situation.
Table A-60 Parameters for the network attributes Parameter Port Attributes Value Range UNI C-Aware S-Aware Default Value UNI Description l When you set this parameter to UNI, the port processes data frames according to the tag attributes. l When you set this parameter to CAwareor S-Aware, the port does not process the data frames according to the tag attributes but processes the data frames according to the method of processing QinQ services. l If a port needs to transmit a QinQ-based service, set this parameter to C-Aware or S-Aware. Otherwise, this parameter takes the default value.
A-204
Issue 05 (2010-10-30)
A Task Collection
Table A-61 Parameters for the advanced attributes Parameter Enabling Broadcast Packet Suppression Value Range Disabled Enabled Default Value Disabled Description Specifies whether to restrict the traffic of broadcast packets according to the ratio of the broadcast packets to the total packets. When a broadcast storm may occur in the equipment at the opposite end, set this parameter to Enabled. The port discards the received broadcast packets when the ratio of the received broadcast packets to the total packets exceeds the value of this parameter. The value of this parameter is greater than the ratio of the broadcast packets to the total packets when the broadcast storm does not occur. Generally, set this parameter to 30% or a greater value. l Specifies the threshold when the flow is zero. This parameter is valid only when you set Zero-Flow Monitor to Enabled. l This parameter is not applicable to the EFP6 board. l Specifies whether to enable the zeroflow monitoring function. l When this parameter is set to Enabled for a port, the traffic threshold-crossing alarm is reported if the traffic over the port is lower than the traffic threshold. l This parameter is not applicable to the EFP6 board. Zero-Flow Monitor Interval (min) 0 to 30 0 l Specifies the zero-flow monitoring cycle. This parameter is valid only when you set Zero-Flow Monitor to Enabled. l This parameter is not applicable to the EFP6 board. Loop Detection Disabled Enabled Disabled Specifies whether to enable loop detection, which is used to check whether a loop exists on the port.
Broadcast Packet Suppression Threshold
10% to 100%
30%
Flow Threshold (Mbps)
In the case of PORT1-PORT4: 0 to 100 In the case of PORT5-PORT6: 0 to 1000
In the case of PORT1-PORT4: 100 In the case of PORT5-PORT6: 1000 Disabled
Zero-Flow Monitor
Disabled Enabled
Issue 05 (2010-10-30)
A-205
A Task Collection
Table A-62 Methods used by ports to process data frames Direction Type of Data Frame Tagged frame Untagged frame Processing Method Tag aware The port receives the frame. The port discards the frame. Access The port discards the frame. The port adds the VLAN tag to which Default VLAN ID and VLAN Priority correspond, to the frame, and receives the frame. The port strips the VLAN tag from the frame and then transmits the frame. Hybrid The port receives the frame. The port adds the VLAN tag to which Default VLAN ID and VLAN Priority correspond, to the frame, and receives the frame. l If the VLAN ID in the frame is Default VLAN ID, the port strips the VLAN tag from the frame and then transmits the frame. l If the VLAN ID in the frame is not Default VLAN ID, the port directly transmits the frame.
Ingress
Egress
Tagged frame
The port transmits the frame.
A.18.2 Configuring the Internal Port of the Ethernet Board

When an NE transmits Ethernet services to a line through an internal port (that is, VCTRUNK) of an Ethernet board, the attributes of the internal port need to be set. Thus, the Ethernet board works with the Ethernet board at the opposite end to achieve the transmission of the Ethernet services on the network.
Prerequisite
l l The NE user must have the authority of Operation Level or higher. The Ethernet board must be added on the Slot Layout.

Web LCT
A-206
Issue 05 (2010-10-30)
A Task Collection
Precautions
The Ethernet boards supported by the OptiX RTN 620 are the EFT4, EMS6, and EFP6. l l l The EFT4 board supports VCTRUNKs 1-4, which are bound with PORTs 1-4 respectively. The EFT4 board does not support the setting of TAG attributes and network attributes. The EMS6 board supports VCTRUNKs 1-8. VCTRUNKs 1-8 determine the services to be transmitted, depending on information of the created Ethernet services. The EMS6 board supports VCTRUNKs 1-16. VCTRUNKs 1-16 determine the services to be transmitted, depending on information of the created Ethernet services.
The following procedures describe how to configure the internal port of an EMS6 board.
Procedure
Step 1 In the NE Explorer, select the required Ethernet service board, and then choose Configuration > Ethernet Interface Management > Ethernet Interface from the Function Tree. Select Internal Port. Step 2 Optional: Set the TAG attributes of the port. 1. 2. Click the TAG Attributes tab. Set the TAG attributes of the port.
3.
Click Apply.
Step 3 Set the encapsulation and mapping protocol used by the port. 1. 2. Click the Encapsulation/Mapping tab. Set Mapping Protocol and the protocol parameters.
3.
Click Apply.
Step 4 Optional: Set the network attributes of the port. 1. 2. Click the Network Attributes tab. Set the network attributes of the port.
3.
Click Apply.
Step 5 Enable the LCAS function for the port. 1. 2.

Issue 05 (2010-10-30)
Click the LCAS tab. Set the Enabling LCAS parameter and other LCAS parameters.
A Task Collection
3. 1.
Click Apply. Click Configuration. The Bound Path Configuration dialog box is displayed. Set the attributes of the bound path.
Step 6 Optional: Set the bound path.
2. 3. 4.
In Configurable Ports, select a VCTRUNK as the configurable port. In Available Bound Paths, set Level and Direction of the bound paths. Select required items in Available Resources and Available Timeslots and click .
5.
Optional: Repeat step Step 6.4 to bind other VC paths.
6.
Click OK.
NOTE
The result of configuring the attributes of bound paths during service configuration is consistent with the result of directly setting the attributes of VCTRUNK ports.
Step 7 Set the advanced attributes of the port. 1. 2. Click the Advanced Attributes tab. Set the relevant parameters of the advanced attributes of the internal port.
A-208
Issue 05 (2010-10-30)
A Task Collection
3.
Click Apply.
NOTE
l The Mapping Protocol and protocol parameters set for VCTRUNKs at one end of a transmission line must be the same as the Mapping Protocol and protocol parameters set for VCTRUNKs at the other end of the transmission line. l The Enabling LCAS and LCAS protocol parameters set for VCTRUNKs at one end of a transmission line must be the same as the Enabling LCAS and LCAS protocol parameters set for VCTRUNKs at the other end of the transmission line. l The timeslots to which the paths bound with a VCTRUNK correspond must be the same at both ends of a transmission line.
----End
Example
Table A-63 Parameters for the TAG attributes Parameter TAG Value Range Tag Aware Access Hybrid Default Value Tag Aware Description l When ports are configured with TAG flags, the ports process frames by using the methods provided in Table A-69. l If all the accessed services are frames with the VLAN tag (tagged frames), set this parameter to Tag Aware. l If all the accessed services are frames without the VLAN tag (untagged frames), set this parameter to Access. l If the accessed services contain tagged frames and untagged frames, set this parameter to Hybrid. Default VLAN ID 1 to 4095 1 l This parameter is valid only when you set TAG to Access or Hybrid. l For details about the functions of this parameter, see Table A-69. l You need to set this parameter according to the actual situation. VLAN Priority 0 to 7 0 l This parameter is valid only when you set TAG to Access or Hybrid. l For details about the functions of this parameter, see Table A-69. l When the VLAN priority is required to divide streams or to be used for other purposes, set this parameter according to actual situations. Generally, it is recommended that you use the default value.
Issue 05 (2010-10-30)
A-209
A Task Collection
Parameter Entry Detection
Default Value Enable
Description l Indicates whether to check the incoming packets from the port according to the TAG attributes. l You need to set this parameter according to the actual situation.
Table A-64 Parameters for encapsulation or mapping Parameter Mapping Protocol Value Range GFP LAPS HDLC Scramble Scrambling Mode [X43+1] Unscrambled Scrambling Mode [X48+1] Set Inverse Value For CRC Yes No Yes Scrambling Mode [X43+1] Default Value GFP Description It is recommended that you use the default value. The EFP6 board supports only GFP. l Indicates the scrambling polynomial used by the mapping protocol. l It is recommended that you use the default value. l This parameter is valid only when you set Mapping Protocol to LAPS or HDLC. l If you set this parameter to Yes, the FCS is the result after you perform a negation operation for the CRC. l If you set this parameter to No, the FCS is the CRC. Check Field Length FCS32 FCS16 No FCS32 l When you set this parameter to FCS32, a 32-bit FCS is used. l When you set this parameter to FCS16, a 16-bit FCS is used. l When the Ethernet board uses the GFP mapping protocol, set this parameter to FCS32 or No. l When the Ethernet board uses the HDLC mapping protocol, set this parameter to FCS32 and FCS16. l When the Ethernet board uses the LAPS mapping protocol, set this parameter to FCS32. l It is recommended that you use the default value.
A-210
Issue 05 (2010-10-30)
A Task Collection
Parameter FCS Calculated Bit Sequence
Value Range Big endian Little endian
Default Value l Big endian (GFP) l Little endian (LAPS or HDLC)
Description l When you set this parameter to Big endian, the least significant byte of the FCS is placed first and the most significant byte is placed last. l When you set this parameter to Little endian, the most significant byte of the FCS is placed first and the least significant byte is placed last. l It is recommended that you use the default value.
Extension Header Option
No Yes
No
l Indicates whether the GFP payload header contains the extension header and eHEC. l You can set this parameter only when Mapping Protocol is set to GFP. l It is recommended that you set this parameter to No.
Table A-65 Parameters for the network attributes Parameter Port Attributes Value Range UNI C-Aware S-Aware Default Value UNI Description l When you set this parameter to UNI, the port processes data frames according to the tag attributes. l If you set this parameter to C-Aware or S-Aware, the port does not process the data frames according to the tag attributes but processes the data frames according to the method of processing QinQ services. l If a port needs to transmit a QinQ-based service, set this parameter to C-Aware or S-Aware. Otherwise, this parameter takes the default value.
Issue 05 (2010-10-30)
A-211
A Task Collection
Table A-66 Parameters for the LCAS Parameter Enabling LCAS Value Range Enabled Disabled Default Value Disabled Description l Indicates whether the LCAS function is enabled. l The LCAS can dynamically adjust the number of virtual containers for mapping required services to meet the bandwidth requirements of the application. As a result, the bandwidth utilization ratio is improved. LCAS Modde Huawei Mode Standard Mode Huawei Mode l Indicates the sequence in which the LCAS sink sends the MST control packet and Rs-Ack control packet. l When you set this parameter to Huawei Mode, the LCAS sink first sends the RsAck and then sends the MST. l When you set this parameter to Standard Mode, the LCAS sink first sends the MST and then sends the RsAck. l If the equipment at the opposite end is the third-party equipment and does not support the Huawei mode, set this parameter to Standard Mode. Otherwise, set this parameter to Huawei Mode. Hold Off(ms) FE: an integer ranging from 2000 to 10000, in the increments of 100 2000 l When a member link is faulty, the LCAS performs switching after a delay of time to prevent the situation where an NE simultaneously performs a protection switching such as SNCP and performs an LCAS switching. This parameter specifies the duration of the delay. l It is recommended that you use the default value. WTR(s) 0 to 720 300 l When the time after a member link is restored to normal reaches the specified value of this parameter, the VCG uses the restored member link. l It is recommended that you use the default value.
A-212
Issue 05 (2010-10-30)
A Task Collection
Parameter TSD
Description l Indicates whether the TSD is used as a condition for determining whether a member link is faulty. In the case of the VC-12, the TSD refers to the BIP_SD. In the case of the VC-3, the TSD refers to the B3_SD_VC3. l It is recommended that you use the default value.
Table A-67 Parameters for bound paths Parameter Configuration Selected Bound Paths Value Range All the VCTRUNK ports Default Value VCTRUNK1 Description Indicates the VCTRUNK of the VC path to be configured. You need to plan and set this parameter according to the following principles: l The capacity of the VCTRUNK is determined by the actual bandwidth required by the services. l A VCTRUNK is bound with the paths in a VC-4 only, if possible. To bound a VCTRUNK with the paths in several VC-4s, first select the VC-4s whose transmission paths are the same. l Each VC-4 of the Ethernet board can contain only the VC-3 or VC-12 paths. Therefore, if a VCTRUNK needs to be bound with the VC-3 paths, first select the paths in the VC-4 that is already bound with certain VC-3 paths. If a VCTRUNK needs to be bound with the VC-12 paths, first select the paths in the VC-4 that is already bound with certain VC-12 paths. l VC4-1 of the EFT4 and EMS6 boards supports only VC-3 paths, but VC4-2 of the EFT4 and EMS6 boards supports the VC-12 and VC-3 paths. Therefore, if a VCTRUNK needs to be bound with the VC-3 paths, first select the paths in VC4-1. l Generally, bind bidirectional paths.
Issue 05 (2010-10-30)
A-213
A Task Collection
Table A-68 Parameters for the advanced attributes Parameter Zero-Flow Monitor Value Range An integer ranging from 0, 2000 to 10000, in the increments of 100 Default Value 2000 Description l When a member link is faulty, the LCAS performs switching after a delay of time to prevent the situation where an NE simultaneously performs a protection switching such as SNCP and performs an LCAS switching. This parameter specifies the duration of the delay. l It is recommended that you use the default value.
Table A-69 Methods used by ports to process data frames Direction Type of Data Frame Tagged frame Untagged frame Processing Method Tag aware The port receives the frame. The port discards the frame. Access The port discards the frame. The port adds the VLAN tag to which Default VLAN ID and VLAN Priority correspond, to the frame, and receives the frame. The port strips the VLAN tag from the frame and then transmits the frame. Hybrid The port receives the frame. The port adds the VLAN tag to which Default VLAN ID and VLAN Priority correspond, to the frame, and receives the frame. l If the VLAN ID in the frame is Default VLAN ID, the port strips the VLAN tag from the frame and then transmits the frame. l If the VLAN ID in the frame is not Default VLAN ID, the port directly transmits the frame.
Ingress
Egress
Tagged frame
The port transmits the frame.
A-214
Issue 05 (2010-10-30)
A Task Collection
A.18.3 Configuring Ethernet Ports of the IFH2 Board

When an NE transmits Ethernet services through Hybrid radio, the attributes of the Ethernet port of the IFH2 board need to be set.
Prerequisite
l l The NE user must have the authority of Operation Level or higher. The IFH2 board must be created on the Slot Layout.

Web LCT
Procedure
Step 1 In the NE Explorer, select the IFH2 board, and then choose Configuration > Ethernet Interface Management > Ethernet Interface from the Function Tree. Step 2 Set the basic attributes of the port. 1. 2. Click the Basic Attributes tab. Set the basic attributes of the port.
3. 1. 2.
Click Apply. Click the Flow Control tab. Set the flow control mode of the port.
Step 3 Set the flow control mode of the port.
3.
Click Apply.
----End
Issue 05 (2010-10-30)
A-215
A Task Collection
Example
Table A-70 Parameters for the basic attributes Parameter Enabled/Disabled Value Range Disabled Enabled Default Value Disabled Description l If the port gains access to services, set this parameter to Enabled. In the case of other ports, set this parameter to Disabled. l When you set this parameter to Enabled for the port that does not gain access to services, an ETH_LOS alarm may be generated. Working Mode Auto-Negotiation 10M Full-Duplex 100M Full-Duplex 1000M Half-Duplex Auto-Negotiation l The Ethernet ports of different types support different working modes. l When the equipment at the opposite end works in the auto-negotiation mode, set this parameter to Auto-Negotiation. l When the equipment at the opposite end works in full-duplex mode, set the working mode of the equipment at the local end to 10M Full-Duplex, 100 FullDuplex or 1000M Full-Duplex, depending on the port rate of the equipment at the opposite end.
Table A-71 Parameters for flow control Parameter NonAutonegotiation Flow Control Mode Value Range Disabled Enable Symmetric Flow Control Default Value Disabled Description l This parameter is valid only when you set Working Mode to AutoNegotiation. l If you set this parameter to Enable Symmetric Flow Control, the port can send the PAUSE frames and process the received PAUSE frames. l The non-autonegotiation flow control mode of the equipment at the local end must be the same as the nonautonegotiation flow control mode of the equipment at the opposite end.
A-216
Issue 05 (2010-10-30)
A Task Collection
Parameter Auto-Negotiation Flow Control
Value Range Disabled Enable Symmetric Flow Control
Description l This parameter is valid only when you set Working Mode to AutoNegotiation. l When you set this parameter to Enable Symmetric Flow Control, the port can send and process the PAUSE frames. l The auto-negotiation flow control mode of the equipment at the local end must be the same as the auto-negotiation flow control mode of the equipment at the opposite end.
A.18.4 Modifying the Type Field of Jumbo Frames

By default, the type field of Jumbo frames processed by Ethernet boards is set to 0x8700.
Prerequisite

Web LCT
Precautions
The EMS6 board supports the modification of the type field of Jumbo frames.
Procedure
Step 1 In the NE Explorer, select the EMS6 board, and then choose Configuration > Ethernet Interface Management > Jumbo Frame from the Function Tree. Step 2 Modify the type field of Jumbo frames.
Issue 05 (2010-10-30)
A-217
A Task Collection
Parameters
Parameter Jumbo Frame Value Range 00 00 to FF FF Default Value 88 70 Description Indicates the type field of Jumbo frames. Set this parameter according to the type field of the accessed Jumbo frames.
A.18.5 Modifying the Type Field of QinQ Frames

By default, the type field (that is, the TPID in an S-TAG) of QinQ frames processed by Ethernet switching boards is set to 0x8100.
Prerequisite

Web LCT
Precautions
In the case of the OptiX RTN 620, the Ethernet board that supports modification of the QinQ type area are the EMS6 and EFP6.
Procedure
Step 1 In the NE Explorer, select the required Ethernet board, and then choose Configuration > Advanced Attribute > QinQ Type Type Area Settings from the Function Tree. Step 2 Modify the type field of QinQ frames.
Parameters
Parameter QinQ Type Area (Hexadecimal) Value Range 81 00 88 A8 91 00 Default Value 81 00 Description Indicates the type field of QinQ frames. You need to set this parameter according to the type field of the accessed QinQ frames.
A-218
Issue 05 (2010-10-30)
A Task Collection
A.18.6 Dynamically Increasing/Decreasing the VCTRUNK Bandwidth

When the LCAS function is enabled on an NE, you can dynamically increase or decrease the VCTRUNK-bound paths to increase or decrease the bandwidth. The operation does not affect services.
Prerequisite

Web LCT
Procedure
Step 1 In the NE Explorer, select the required Ethernet service board, and then choose Configuration > Ethernet Interface Management > Ethernet Interface from the Function Tree. Step 2 Select Internal Port. Step 3 Click the Bound Path tab. Step 4 Click Configuration. The Bound Path Configuration dialog box is displayed. Step 5 Optional: Dynamically increase the VCTRUNK bandwidth. 1. 2. 3. In Configurable Ports, select a VCTRUNK as the configurable port. In Available Bound Paths, set Level and Direction of the bound paths. Select the desired items in Available Resources and Available Timeslots, and click .
Issue 05 (2010-10-30)
A-219
A Task Collection
4. 1. 2.
Optional: Repeat Step 5.3 and bind other VC paths. Deselect the Display in Combination checkbox. Select the VC paths to be deleted in Selected Bound Paths, and then click .
Step 6 Optional: Dynamically decrease the VCTRUNK bandwidth.
3.
Optional: Repeat Step 6.2 to delete other VC paths.
A-220
Issue 05 (2010-10-30)
A Task Collection
Parameters
Parameter Configurable Ports Selected Bound Paths Value Range Default Value Description Indicates the VCTRUNK of the VC path to be configured. You need to plan and set this parameter according to the following principles: l The capacity of the VCTRUNK is determined by the actual bandwidth required by the services. l A VCTRUNK is bound with the paths in a VC-4 only, if possible. To bound a VCTRUNK with the paths in several VC-4s, first select the VC-4s whose transmission paths are the same. l Each VC-4 of the Ethernet board can contain only the VC-3 or VC-12 paths. Therefore, if a VCTRUNK needs to be bound with the VC-3 paths, first select the paths in the VC-4 that is already bound with certain VC-3 paths. If a VCTRUNK needs to be bound with the VC-12 paths, first select the paths in the VC-4 that is already bound with certain VC-12 paths. l VC4-1 of the EFT4 and EMS6 boards supports only VC-3 paths, but VC4-2 of the EFT4 and EMS6 boards supports the VC-12 and VC-3 paths. Therefore, if a VCTRUNK needs to be bound with the VC-3 paths, first select the paths in VC4-1. l Generally, bind bidirectional paths.
A.19 Configuring Ethernet Services

Ethernet services are classified into EPL services, EVPL services, EPLAN services, and EPVLAN services. A.19.1 Creating Ethernet Private Line Services This section describes how to create EPL services and VLAN-based EVPL services. A.19.2 Creating Ethernet LAN Services
A Task Collection
This section describes how to create IEEE 802.1d bridge-based EPLAN services and IEEE 802.1q bridge-based EVPLAN services. A.19.3 Modifying the Mounted Port of a Bridge This section describes how to modify the mounted port of a bridge, the enabled state of the mounted port, and Hub/Spoke attribute of the port. A.19.4 Creating the VLAN Filtering Table To create an IEEE 802.1q bridge-based EPLAN service, you need to create the VLAN filtering table. A.19.5 Creating QinQ Private Line Services To enable the Ethernet switching board to transmit QinQ private line services, perform this task to configure the related information such as the service source and service sink. A.19.6 Creating IEEE 802.1ad Bridge-Based EVPLAN Services To create EVPLAN services that are based on the IEEE 802.1ad bridge, you need to set relevant service information, including the attributes of the bridge and the ports that are mounted to the bridge. A.19.7 Deleting an Ethernet Private Line Service When an Ethernet private line service is not used, you need to delete the Ethernet private line service to release the corresponding resources. A.19.8 Creating an Ethernet LAN Service When an Ethernet LAN service is not used, you need to delete the Ethernet LAN service to release the corresponding resources.
A.19.1 Creating Ethernet Private Line Services

This section describes how to create EPL services and VLAN-based EVPL services.
Prerequisite

Web LCT
Precautions
l l This section does not describe the method for creating QinQ-based private line services. The OptiX RTN 620 supports the Ethernet switching boards EMS6 and EFP6. The EFT4 board is an Ethernet transparent transmission board. Each PORT on the EFT4 board corresponds to a VCTRUNK. Therefore, you need not create the Ethernet private line service.
Procedure
Step 1 In the NE Explorer, select the Ethernet switching board, and choose Configuration > Ethernet Service > Ethernet Line Service from the Function Tree. Step 2 Click New.
A Task Collection
The Create Ethernet Line Service dialog box is displayed. Step 3 Set the attributes of the private line service.
Step 4 Optional: Set the port attributes of the source port and sink port.
NOTE
The result of setting the port attributes during the Ethernet line service configuration process is the same as the result of directly setting the Ethernet service port attributes.
Step 5 Optional: Set the bound path. 1. Click Configuration. The Bound Path Configuration dialog box is displayed. Set the attributes of the bound path. In Configurable Ports, select a VCTRUNK as the configurable port. In Available Bound Paths, set Level and Direction of the bound paths. Select required items in Available Resources and Available Timeslots and click . 5. Optional: Repeat step Step 5.4 to bind other VC paths.
2. 3. 4.
Issue 05 (2010-10-30)
A-223
A Task Collection
6.
Click OK.
NOTE
Parameters
Table A-72 Parameters on the main interface Parameter Service Type Value Range EPL EVPL (QinQ) Default Value EPL Description When creating a non-QinQ private line service, set this parameter to EPL.
A-224
Issue 05 (2010-10-30)
A Task Collection
Parameter Direction
Value Range Bidirectional Unidirectional
Description l After setting this parameter to Unidirectional, create the service only from the service source to the service sink. That is, the service source is forwarded only to the sink port. l After setting this parameter to Bidirectional, create the service from the service source to the service sink and the service from the service sink to the service source. That is, when the service source is forwarded to the sink port, the service sink is forwarded to the source port. l It is recommended that you set this parameter to Bidirectional.
Source Port
l This parameter specifies the port where the service source resides. l When creating the bidirectional Ethernet service from a PORT to a VCTRUNK, use a specific PORT as the source port.
Source C-VLAN (e.g.1,3-6)
1 to 4095
l You may set this parameter to null, a number, or several numbers. When setting this parameter to several numbers, use "," to separate these discrete values and use "-" to indicate continuous numbers. For example, "1, 3-6" indicates numbers 1, 3, 4, 5, and 6. l The number of VLANs set in this parameter should be the same as the number of VLANs set in Sink C-VLAN (e.g.1,3-6). l When you set this parameter to null, all the services of the source port work as the service source. l When you set this parameter to a nonnull value, only the services of the source port whose VLAN IDs are included in the set value of this parameter work as the service source.
Issue 05 (2010-10-30)
A-225
A Task Collection
Parameter Sink Port
Value Range -
Default Value -
Description l This parameter specifies the port where the service sink is located. l Set the value of this parameter to be different from the value of Source Port. l When creating the bidirectional Ethernet service from a PORT to a VCTRUNK, it is recommended that you use a VCTRUNK as the sink port.
Sink C-VLAN(e.g. 1,3-6)
1 to 4095
l You may set this parameter to null, a number, or several numbers. When setting this parameter to several numbers, use "," to separate these discrete values and use "-" to indicate continuous numbers. For example, "1, 3-6" indicates numbers 1, 3, 4, 5, and 6. l The number of VLANs set in this parameter should be the same as the number of VLANs set in Source CVLAN(e.g.1,3-6). l When you set this parameter to null, all the services of the sink port work as the service sink. l When you set this parameter to a nonnull value, only the services of the sink port whose VLAN IDs are included in the set value of this parameter work as the service sink.
Table A-73 Parameters of port attributes Parameter Port Enabled Value Range Enabled Disabled TAG Tag Aware Access Hybrid Tag Aware Default Value Description When the source port or the sink port is set to a PORT, set Port Enabled to Enabled. l When all the accessed services are frames with the VLAN tag (tagged frames), set this parameter to Tag Aware. l When all of the accessed services are not frames with the VLAN tag (untagged frames), set this parameter to Access. l When the accessed services contain tagged frames and untagged frames, set this parameter to Hybrid.
A-226
Issue 05 (2010-10-30)
A Task Collection
Table A-74 Parameters of bound paths Parameter Configurable Ports Selected Bound Paths Value Range Default Value Description This parameter specifies the VCTRUNK whose VC paths are to be configured. Adhere to the following principles to plan and set this parameter: l The capacity of VCTRUNKs should be determined by the actual bandwidth required by services. l Bind only the paths in a VC-4 for a VCTRUNK if possible. If the paths in several VC-4s need to be bound, the VC-4s that have the same transmission path take priority. l Each VC-4 of an Ethernet board can have only VC-3 paths or only VC-12 paths. Therefore, when a VCTRUNK needs to be bound with VC-3 paths, select VC-3 paths first from the VC-4 certain of whose VC-3 paths are already bound. When a VCTRUNK needs to be bound with VC-12 paths, select VC-12 paths first from the VC-4 certain of whose VC-12 paths are already bound. l Give priority to the paths in the VC-4-1 if a VCTRUNK needs to be bound with VC-3 paths because the VC-4-1s of the EMS6 board support only VC-3 paths whereas the VC-4-2s support both VC-12 paths and VC-3 paths. l Generally, bidirectional paths are bound.
A.19.2 Creating Ethernet LAN Services

This section describes how to create IEEE 802.1d bridge-based EPLAN services and IEEE 802.1q bridge-based EVPLAN services.
Prerequisite

Web LCT
Issue 05 (2010-10-30)
A-227
A Task Collection
Precautions
l l This section describes only how to create the IEEE 802.1d bridge and how to create the IEEE 802.1q bridge. The OptiX RTN 620 supports the Ethernet switching boards EMS6 and EFP6.
Procedure
Step 1 In the NE Explorer, select the Ethernet switching board, and choose Configuration > Ethernet Service > Ethernet LAN Service from the Function Tree. Step 2 Click New. The Create Ethernet LAN Service dialog box is displayed. Step 3 Set the attributes of the bridge according to the bridge type. l Set the attributes of the IEEE 802.1q bridge.
l Set the attributes of the IEEE 802.1d bridge.
A-228
Issue 05 (2010-10-30)
A Task Collection
Step 4 Configure the mounted ports of the bridge. 1. 2. Click Configure Mount. The Service Mount Configuration dialog box is displayed. Select a port from the ports listed in Available Mounted Ports, and then click . 3. Optional: Repeat step Step 4.2 to mount other ports.
4.
Click OK.

A Task Collection
1.
Click Configuration. The Bound Path Configuration dialog box is displayed. Set the attributes of the bound path.
2. 3. 4.
In Configurable Ports, select a VCTRUNK as the configurable port. In Available Bound Paths, set Level and Direction of the bound paths. Select required items in Available Resources and Available Timeslots and click .
5.
6.
Click OK.
NOTE
Parameters
Table A-75 Parameters on the main interface Parameter VB Name Value Range Default Value Description This parameter is a string that describes the bridge. It is recommended that you set this string to a value that contains the specific purpose of the bridge.
Issue 05 (2010-10-30)
A-230
A Task Collection
Parameter Bridge Type
Value Range 802.1q 802.1d 802.1ad
Default Value 802.1q
Description l After setting this parameter to 802.1q, create the IEEE 802.1q bridge. l After setting this parameter to 802.1d, create the IEEE 802.1d bridge. l After setting this parameter to 802.1ad, create the IEEE 802.1ad bridge. l The IEEE 802.1q bridge is preferred. If the conditions of the VLAN that is used by the user are not known and if the user does not require the isolation of the data among VLANs, you can also use the IEEE 802.1d bridge. l This section describes only how to create the IEEE 802.1d bridge and how to create the IEEE 802.1q bridge.
Bridge Switching Mode
IVL/Ingress Filter Enable(802.1q) SVL/Ingress Filter Disable(802.1d)
IVL/Ingress Filter Enable(802.1q) SVL/Ingress Filter Disable(802.1d)
l When the bridge uses the SVL mode, all the VLANs share one MAC address table. When the bridge uses the IVL mode, all the VLANs correspond to their respective MAC address tables. l If the ingress filter is enabled, the VLAN tag is checked at the ingress port. If the VLAN ID does not equal the VLAN ID of the port defined in the VLAN filtering table, the packet is discarded. If the ingress filter is disabled, the preceding described check is not conducted.
Table A-76 Parameters of service mounting Parameter Mount Port Value Range Default Value Description l Only the port that is selected as the mounted port of a bridge functions in the packet forwarding process of the bridge. l Set this parameter according to actual requirements.
Table A-77 Parameters of bound paths Parameter Configurable Ports Value Range Default Value Description This parameter specifies the VCTRUNK whose VC paths are to be configured.
Issue 05 (2010-10-30)
A-231
A Task Collection
Parameter Selected Bound Paths
Value Range -
Default Value -
Description Adhere to the following principles to plan and set this parameter: l The capacity of VCTRUNKs should be determined by the actual bandwidth of the service needs. l Bind only the paths in a VC-4 if possible. If the paths of several VC-4s need to be bound, the VC-4s that have the same transmission path take priority. l Each VC-4 of an Ethernet board can have only VC-3 paths or only VC-12 paths. Therefore, when a VCTRUNK needs to be bound with VC-3 paths, select VC-3 paths first from the VC-4 certain of whose VC-3 paths are already bound; when a VCTRUNK needs to be bound with VC-12 paths, select VC-12 paths first from the VC-4 certain of whose VC-12 paths are already bound. l As the VC-4-1s of the EMS6 board support only VC-3 paths whereas the VC-4-2s support both VC-12 paths and VC-3 paths, give priority to the paths in the VC-4-1 if a VCTRUNK needs to be bound with VC-3 paths. l Generally, bidirectional paths are bound.
A.19.3 Modifying the Mounted Port of a Bridge

This section describes how to modify the mounted port of a bridge, the enabled state of the mounted port, and Hub/Spoke attribute of the port.
Prerequisite
l l l The NE user must have the authority of Operation Level or higher. The corresponding Ethernet switching board must be added to the Slot Layout. The EPLAN service must be created.

Web LCT
A-232
Issue 05 (2010-10-30)
A Task Collection
Precautions
CAUTION
Modifying the ports that are mounted to the bridge may interrupt services. The OptiX RTN 620 supports the Ethernet switching boards EMS6 and EFP6.
Procedure
Step 1 In the NE Explorer, select the Ethernet switching board, and choose Configuration > Ethernet Service > Ethernet LAN Service from the Function Tree. Step 2 Select the bridge that is already created, and click the Service Mount tab. Step 3 Modify the mounted port of this bridge and the related attributes of the mounted port.
----End
Parameters
Parameter VB Port Value Range 1 to 14 (EMS) 1 to 22 (EFP6) Mount Port Default Value Description This parameter specifies the ID of the logical port of the bridge. l Only the port that is selected as the mounted port of a bridge functions in the packet forwarding process of the bridge. l Set this parameter according to actual requirements. Port Enabled Enabled Disabled Hub/Spoke Hub Spoke Hub Enabled Set Port Enabled to Enabled. Otherwise, the port cannot forward the service. l The Spoke ports cannot access each other. The Hub port and the Spoke port can access each other. The Hub ports can access each other. l Set this parameter according to actual requirements.
Issue 05 (2010-10-30)
A-233
A Task Collection
Parameter TAG
Value Range Access Tag Aware Hybrid
Default Value Tag Aware
Description l When ports are configured with TAG flags, the ports process frames by using the methods provided in Table A-78. l When all the accessed services are frames with the VLAN tag (tagged frames), set this parameter to Tag Aware. l When all of the accessed services are not frames with the VLAN tag (untagged frames), set this parameter to Access. l When the accessed services contain tagged frames and untagged frames, set this parameter to Hybrid.
Default VLAN ID
1 to 4095
l This parameter is valid only when TAG is set to Access or Hybrid. l For the usage of this parameter, refer to Table A-78. l Set this parameter according to the service planning information.
Working Mode
l EMS6 AutoNegotiation 10M HalfDuplex 10M FullDuplex 100M HalfDuplex 100M FullDuplex 1000M FullDuplex l EFP6: AutoNegotiation 10M HalfDuplex 10M FullDuplex 100M HalfDuplex 100M FullDuplex
Auto-negotiation
l Ethernet ports of different types support different working modes. l When the equipment on the opposite side works in the auto-negotiation mode, set the working mode of the equipment on the local side to Auto-Negotiation. l When the equipment at the opposite end works in full-duplex mode, set the working mode of the equipment at the local end to 10M Full-Duplex, 1000 Full-Duplex or 1000M Full-Duplex depending on the port rate of the equipment at the opposite end. l When the equipment at the opposite end works in half-duplex mode, set the working mode of the equipment at the local end to 10M Full-Duplex, 100M Full-Duplex, or Auto-Negotiation depending on the port rate of the equipment at the opposite end. l The GE optical interfaces on the EMS6 support only 1000M full duplex.
A-234
Issue 05 (2010-10-30)
A Task Collection
Table A-78 Methods used by ports to process data frames Direction Type of Data Frame Tagged frame Untagged frame Processing Mode Tag Aware Receiving Discarding Access Discarding The port adds the VLAN tag to which Default VLAN ID and VLAN Priority correspond, to the frame, and receives the frame. The port strips the VLAN tag from the frame and then transmits the frame. Hybrid Receiving The port adds the VLAN tag to which Default VLAN ID and VLAN Priority correspond, to the frame, and receives the frame. l If the VLAN ID in the frame is Default VLAN ID, the port strips the VLAN tag from the frame and then transmits the frame. l If the VLAN ID in the frame is not Default VLAN ID, the port directly transmits the frame.
Ingress
Egress
Tagged frame
Transmitting

To create an IEEE 802.1q bridge-based EPLAN service, you need to create the VLAN filtering table.
Prerequisite
l l The NE user must have the authority of Operation Level or higher. The EPLAN service must be created.
Precautions
Issue 05 (2010-10-30)
A-235
A Task Collection
Procedure
Step 1 In the NE Explorer, select the Ethernet switching board, and choose Configuration > Ethernet Service > Ethernet LAN Service from the Function Tree. Step 2 Select the bridge that is already created, and click the VLAN Filtering tab. Step 3 Create a VLAN filtering table. 1. 2. 3. Click New. Then, the Create VLAN dialog box is displayed. Set VLAN ID(e.g:1,3-6). Select a port from the ports listed in Available forwarding ports, and then click . 4. Optional: Repeat step Step 3.3 to select other service forwarding ports.
5.
Click OK.
----End
A-236
Issue 05 (2010-10-30)
A Task Collection
Parameters
Parameter VLAN ID(e.g; 1,3-6) Value Range 1 to 4095 Default Value 1 Description l You can set this parameter to a number or several numbers. When you set this parameter to several numbers, use "," to separate these discrete values and use "-" to indicate continuous numbers. For example, "1, 3-6" indicates numbers 1, 3, 4, 5, and 6. l Set this parameter according to actual requirements. Selected forwarding ports l Packets are forwarded between the Selected forwarding ports only. l The ports that are in Selected forwarding ports can forward only the packet that carries the VLAN ID(e.g; 1,3-6) tag. These ports discard the packet that carries other VLAN tags. l The broadcast packet that is transmitted by the ports in Selected forwarding ports is broadcast only to the ports included in Selected forwarding ports.
A.19.5 Creating QinQ Private Line Services

To enable the Ethernet switching board to transmit QinQ private line services, perform this task to configure the related information such as the service source and service sink.
Prerequisite

Web LCT
Precautions
The OptiX RTN 620, the Ethernet board that supports the QinQ feature are the EMS6 and EFP6.
Procedure
Step 1 In the NE Explorer, select the Ethernet switching board, and choose Configuration > Ethernet Service > Ethernet Line Service from the Function Tree. Step 2 Select Display QinQ Shared Service.
A Task Collection
Step 3 Click New. The Create Ethernet Line Service dialog box is displayed. Step 4 Set the attributes of the QinQ private line service.
Step 5 Optional: Set the port attributes of the source port and sink port.
NOTE
The result of setting the port attributes during the Ethernet line service configuration process is the same as the result of directly setting the Ethernet service port attributes.
Step 6 Optional: Set the bound path. 1. Click Configuration. The Bound Path Configuration dialog box is displayed. Set the attributes of the bound path. In Configurable Ports, select a VCTRUNK as the configurable port. In Available Bound Paths, set Level and Direction of the bound paths. Select required items in Available Resources and Available Timeslots and click . 5. Optional: Repeat step Step 6.4 to bind other VC paths.
2. 3. 4.
A-238
Issue 05 (2010-10-30)
A Task Collection
6.
Click OK.
NOTE
Parameters
Table A-79 Parameters on the main interface Parameter Service Type Value Range EPL EVPL (QinQ) Default Value EPL Description When creating a QinQ private line service, set this parameter to EVPL(QinQ).
Issue 05 (2010-10-30)
A-239
A Task Collection
Parameter Direction
Value Range Bidirectional Unidirectional
Description l After setting this parameter to Unidirectional, create the service only from the service source to the service sink. That is, the service source is forwarded only to the sink port. l After setting this parameter to Bidirectional, create the service from the service source to the service sink and the service from the service sink to the service source. That is, when the service source is forwarded to the sink port, the service sink is forwarded to the source port. l It is recommended that you set this parameter to Bidirectional.
Source Port
l This parameter specifies the port where the service source resides. l When creating the bidirectional Ethernet service from a PORT to a VCTRUNK, it is recommended that you use a specific PORT as the source port.
A-240
Issue 05 (2010-10-30)
A Task Collection
Parameter Operation Type
Value Range EMS6: l Add S-VLAN l Transparently transmit CVLAN l Transparently transmit SVLAN l Translate SVLAN l Strip S-VLAN EFP6: l Add S-VLAN l Transparently transmit CVLAN l Transparently transmit SVLAN l Transparently transmit SVLAN and CVLAN l Translate SVLAN l Translate SVLAN and transparently transmit CVLAN l Strip S-VLAN
Default Value Add S-VLAN
Description l For the meanings of the values, see 19.2.3 Application of the QinQ Technology in Private Line Services. l Operation Type can be set to Strip SVLAN only when Direction is Unidirectional. l Set this parameter according to actual requirements.
Issue 05 (2010-10-30)
A-241
A Task Collection
Parameter Source C-VLAN (e.g.1,3-6)
Default Value -
Description l You can set this parameter to null, a number, or several numbers. When you set this parameter to several numbers, use "," to separate these discrete values and use "-" to indicate continuous numbers. For example, "1, 3-6" indicates numbers 1, 3, 4, 5, and 6. l The number of VLANs set in this parameter should be the same as the number of VLANs set in Sink C-VLAN (e.g.1,3-6). l When you set this parameter to null, all the services of the source port work as the service source. l When you set this parameter to a nonnull value, only the services of the source port whose VLAN IDs are included in the set value of this parameter work as the service source.
Source S-VLAN
1 to 4095
l This parameter must be set to a numerical value. l Only the services of the source port whose S-VLAN IDs are equal to the value of this parameter work as the service source.
Sink Port
l This parameter specifies the port where the service sink resides. l Set the value of this parameter to be different from the value of Source Port. l When creating the bidirectional Ethernet service from a PORT to a VCTRUNK, it is recommended that you use a specific VCTRUNK as the sink port.
A-242
Issue 05 (2010-10-30)
A Task Collection
Parameter Sink C-VLAN(e.g. 1,3-6)
Default Value -
Description l You can set this parameter to null, a number, or several numbers. When you set this parameter to several numbers, use "," to separate these discrete values and use "-" to indicate continuous numbers. For example, "1, 3-6" indicates numbers 1, 3, 4, 5, and 6. l The number of VLANs set in this parameter should be the same as the number of VLANs set in Source CVLAN(e.g.1,3-6). l When you set this parameter to null, all the services of the sink port work as the service sink. l When you set this parameter to a nonnull value, only the services of the sink port whose VLAN IDs are included in the set value of this parameter work as the service sink.
Sink S-VLAN
1 to 4095
l This parameter must be set to a numerical value. l Only the services of the sink port whose S-VLAN IDs are equal to the value of this parameter work as the service sink.
C-VLAN Priority S-VLAN Priority
AUTO AUTO Priority 0 to Priority 7
AUTO AUTO
This parameter specifies the priority of a CVLAN. This parameter specifies the priority of an SVLAN.
Table A-80 Parameters of port attributes Parameter Port Enabled Value Range Enabled Disabled Default Value Description When the source port or the sink port is set to a PORT, set Port Enabled to Enabled.
Issue 05 (2010-10-30)
A-243
A Task Collection
Parameter TAG
Value Range Tag Aware Access Hybrid
Default Value Tag Aware
Description l When all the accessed services are frames with the VLAN tag (tagged frames), set this parameter to Tag Aware. l When all of the accessed services are not frames with the VLAN tag (untagged frames), set this parameter to Access. l When the accessed services contain tagged frames and untagged frames, set this parameter to Hybrid.
Table A-81 Parameters of bound paths Parameter Configurable Ports Selected Bound Paths Value Range Default Value Description This parameter specifies the VCTRUNK whose VC paths are to be configured. Adhere to the following principles to plan and set this parameter: l The capacity of VCTRUNKs should be determined by the actual bandwidth of the service needs. l Bind only the paths in a VC-4 if possible. If the paths of several VC-4s need to be bound, the VC-4s that have the same transmission path take priority. l Each VC-4 of an Ethernet board can have only VC-3 paths or only VC-12 paths. Therefore, when a VCTRUNK needs to be bound with VC-3 paths, select VC-3 paths first from the VC-4 certain of whose VC-3 paths are already bound; when a VCTRUNK needs to be bound with VC-12 paths, select VC-12 paths first from the VC-4 certain of whose VC-12 paths are already bound. l As the VC-4-1s of the EMS6 board support only VC-3 paths whereas the VC-4-2s support both VC-12 paths and VC-3 paths, give priority to the paths in the VC-4-1 if a VCTRUNK needs to be bound with VC-3 paths. l Generally, bidirectional paths are bound.
A-244
Issue 05 (2010-10-30)
A Task Collection
A.19.6 Creating IEEE 802.1ad Bridge-Based EVPLAN Services

To create EVPLAN services that are based on the IEEE 802.1ad bridge, you need to set relevant service information, including the attributes of the bridge and the ports that are mounted to the bridge.
Prerequisite

Web LCT
Precautions
Procedure
Step 1 In the NE Explorer, select the Ethernet switching board, and choose Configuration > Ethernet Service > Ethernet LAN Service from the Function Tree. Step 2 Click New. The Create Ethernet LAN Service dialog box is displayed. Step 3 Set the attributes of the IEEE 802.1ad bridge.
Step 4 Set service mounting relationships. 1. 2. 3. Click Configure Mount. Then, the Service Mount Configuration dialog box is displayed. Set the parameters for configuring the mounted services. Click Add Mount Port.
Issue 05 (2010-10-30)
A-245
A Task Collection
4. 5. 1.
Repeat steps Step 4.2 to Step 4.3 to add the other mounted ports. Click OK. Click Configuration. The Bound Path Configuration dialog box is displayed. Set the attributes of the bound path. In Configurable Ports, select a VCTRUNK as the configurable port. In Available Bound Paths, set Level and Direction of the bound paths. Select required items in Available Resources and Available Timeslots and click .
2. 3. 4.
5.
6.
Click OK.
A-246
Issue 05 (2010-10-30)

NOTE
A Task Collection
Parameters
Table A-82 Parameters on the main interface Parameter VB Name Value Range Default Value Description This parameter is a string that describes the bridge. It is recommended that you set this string to a value that contains the specific purpose of the bridge. l When setting this parameter to 802.1q, create the IEEE 802.1q bridge. l When setting this parameter to 802.1d, create the IEEE 802.1d bridge. l After setting this parameter to 802.1ad, create the IEEE 802.1ad bridge. l The IEEE 802.1q bridge is preferred. If the conditions of the VLAN that is used by the user are not known and if the user does not require the isolation of the data between VLANs, you can also use the 802.1d bridge. l In this example, the IEEE 802.1d bridge and IEEE 802.1q bridge need not be created. Therefore, do not set Bridge Type to 802.1d or 802.1q. Bridge Learning Mode IVL/Ingress Filter Enable SVL/Ingress Filter Disable IVL/Ingress Filter Enable l When the bridge uses the SVL mode, all the VLANs share one MAC address table. When the bridge uses the IVL mode, all the VLANs correspond to their respective MAC address tables. l If the ingress filtering function is enabled, the VLAN tag is checked at the ingress port. If the VLAN ID does not equal the VLAN ID of the port defined in the VLAN filtering table, the packet is discarded. If the ingress filtering function is disabled, the preceding described check is not conducted.
Bridge Type
802.1q 802.1d 802.1ad
802.1q
Issue 05 (2010-10-30)
A-247
A Task Collection
Table A-83 Parameters of service mounting Parameter Operation Type Value Range Add S-VLAN base for port Add S-VLAN base for Port and CVLAN Mount Port Mount Port and base for Port and SVLAN VB Port Mount Port This parameter specifies the ID of the logical port of the bridge. Select the external physical port or internal VCTRUNK port of the Ethernet switching board that is mounted to the IEEE 802.1ad bridge. This parameter is valid only when Operation Type is set to Add S-VLAN base for Port and C-VLAN. This parameter specifies the mapping relation between the C-VLAN tag carried by the data frame and the S-VLAN tag to be added. S-VLAN 1 to 4095 l When Operation Type is set to Add SVLAN base for port, this parameter specifies that the data frames that enter the IEEE 802.1ad bridge need to be added with an S-TAG. l When Operation Type is set to Add SVLAN base for Port and C-VLAN, this parameter and C-VLAN specify the mapping relation between the S-TAG to be added and the C-TAG carried by the data frame that enters the IEEE 802.1ad bridge. l When Operation Type is set to Mount Port, this parameter is invalid. l When Operation Type is set to Mount Port and base for Port and S-VLAN, this parameter specifies the S-TAG carried by the data frames that enter the IEEE 802.1ad bridge. Default Value Add S-VLAN base for port Description For the meaning of each operation type, see 19.2.4 Application of the QinQ Technology in 802.1ad Bridge Services.
C-VLAN
1 to 4095
A-248
Issue 05 (2010-10-30)
A Task Collection
Parameter C-VLAN Priority
Value Range Auto
Default Value Auto
Description This parameter specifies the priority of a CVLAN. This parameter is valid only when Operation Type is set to Add S-VLAN. l This parameter is valid only when Operation Type is set to Add S-VLAN base for port. l This parameter specifies the priority of the newly added S-VLAN. l When QoS operations do not need to be performed according to the S-VLAN priority, it is recommended that this parameter takes the default value.
S-VLAN Priority
Priority 0 to Priority 7
Priority 0
Table A-84 Parameters of bound paths Parameter Configurable Ports Selected Bound Paths Value Range Default Value Description This parameter specifies the VCTRUNK whose VC paths are to be configured. Adhere to the following principles to plan and set this parameter: l The capacity of VCTRUNKs should be determined by the actual bandwidth of the service needs. l Bind only the paths in a VC-4 if possible. If the paths of several VC-4s need to be bound, the VC-4s that have the same transmission path take priority. l Each VC-4 of an Ethernet board can have only VC-3 paths or only VC-12 paths. Therefore, when a VCTRUNK needs to be bound with VC-3 paths, select VC-3 paths first from the VC-4 certain of whose VC-3 paths are already bound; when a VCTRUNK needs to be bound with VC-12 paths, select VC-12 paths first from the VC-4 certain of whose VC-12 paths are already bound. l As the VC-4-1s of the EMS6 board support only VC-3 paths whereas the VC-4-2s support both VC-12 paths and VC-3 paths, give priority to the paths in the VC-4-1 if a VCTRUNK needs to be bound with VC-3 paths. l Generally, bidirectional paths are bound.
Issue 05 (2010-10-30)
A-249
A Task Collection
A.19.7 Deleting an Ethernet Private Line Service

When an Ethernet private line service is not used, you need to delete the Ethernet private line service to release the corresponding resources.
Prerequisite
l l The NE user must have the authority of Operation Level or higher. The Ethernet private line service must be configured and the service is not used.

Web LCT
Procedure
Step 1 In the NE Explorer, select the Ethernet switching board, and choose Configuration > Ethernet Service > Ethernet Line Service from the Function Tree. Step 2 Click Query. Step 3 Select the Ethernet private line service that needs to be deleted and then click Delete. Click OK in the dialog box that is displayed. Step 4 Click Query. At this time, the Ethernet private line service is already deleted. ----End
A.19.8 Creating an Ethernet LAN Service

When an Ethernet LAN service is not used, you need to delete the Ethernet LAN service to release the corresponding resources.
Prerequisite
l l The NE user must have the authority of Operation Level or higher. The Ethernet LAN service must be configured and the service is not used.

Web LCT
Background Information
Deleting an Ethernet LAN service involves the following tasks: 1. 2. Deleting the VLAN filtering table Deleting the service mounting configuration
A-250
Issue 05 (2010-10-30)
A Task Collection
Procedure
Step 1 In the NE Explorer, select the Ethernet switching board, and choose Configuration > Ethernet Service > Ethernet LAN Service from the Function Tree. Step 2 Click Query. Step 3 Click the VLAN Filtering tab. Step 4 Select the VLAN filtering entries that need to be deleted. Then, click Delete. Click Ok in the dialog box that is displayed. Step 5 Click the Service Mount tab. Step 6 Select the Ethernet LAN service that needs to be deleted and then click Delete. Click Ok in the dialog box that is displayed. Step 7 Click Query. At this time, the Ethernet LAN service is already deleted. ----End
A.20 Managing the MAC Address Table

The MAC address table is the core of the EPLAN or EVPLAN service. The OptiX RTN 620 provides various functions for managing the MAC address table. A.20.1 Creating a Static MAC Address Entry A bridge can obtain a dynamic MAC address entry by using the SVL/IVL learning mode. A unicast MAC address entry (namely, a static MAC address entry) can also be created manually, and the static MAC address entry is not aged. If a piece of equipment whose MAC address is known is connected to a port and if the equipment has heavy traffic for a long time, you can specify a static MAC address entry for the equipment. A.20.2 Creating a Blacklist Entry of a MAC Address An entry that is used for discarding data frames that contain the specified MAC addresses is called a disabled MAC address entry (also called a blacklist entry). A blacklist entry is configured by the network administrator and is not aged. A.20.3 Setting the Aging Time of a MAC Address Table Entry In the case of an Ethernet switching board, the aging time of a MAC address table entry is five minutes by default. A.20.4 Querying or Deleting a Dynamic MAC Address By querying a dynamic MAC address, you can learn about all the MAC address entries that are learned by a bridge. A.20.5 Querying the Actual Capacity of a MAC Address Table This topic describes how to query the actual capacity of a MAC address table.
A.20.1 Creating a Static MAC Address Entry

A bridge can obtain a dynamic MAC address entry by using the SVL/IVL learning mode. A unicast MAC address entry (namely, a static MAC address entry) can also be created manually, and the static MAC address entry is not aged. If a piece of equipment whose MAC address is
A Task Collection
known is connected to a port and if the equipment has heavy traffic for a long time, you can specify a static MAC address entry for the equipment.
Prerequisite
The NE user must have the authority of Operation Level or higher. Ethernet boards must be created on the Slot Layout. Ethernet services must be created.

Web LCT
Precautions
Procedure
Step 1 In the NE Explorer, select the required Ethernet switching board, and then choose Configuration > Ethernet Service > Ethernet LAN Service from the Function Free. Step 2 Select a created bridge, and then click the VLAN Unicast tab. Step 3 Click New. The Create VLAN Unicast dialog box is displayed. Step 4 Set the parameters of the unicast MAC address entry.
A-252
Issue 05 (2010-10-30)
A Task Collection
Parameters
Parameter VLAN ID Value Range 1 to 4095 Default Value Description l In the case of IEEE 802.1d and IEEE 802.1ad bridges, this parameter is invalid if you set MAC Address Learning Mode to SVL. That is, the preset static MAC address entries are valid for all VLANs. l In the case of IEEE 802.1d and IEEE 802.1ad bridges, if you set MAC Address Learning Mode to IVL, the preset static MAC address entries are valid for only the VLANs whose VLAN ID is equal to the preset VLAN ID. l You need to set this parameter according to the actual situation. MAC Address Physical Port A port that is mounted to a bridge You need to set this parameter according to the actual situation. Indicates an Ethernet port that corresponds to a MAC address. You need to set this parameter according to the actual situation.
A.20.2 Creating a Blacklist Entry of a MAC Address

An entry that is used for discarding data frames that contain the specified MAC addresses is called a disabled MAC address entry (also called a blacklist entry). A blacklist entry is configured by the network administrator and is not aged.
Prerequisite
The NE user must have the authority of Operation Level or higher. The Ethernet board must be added on the Slot Layout. Ethernet services must be created.

Web LCT
Precautions
Issue 05 (2010-10-30)
A-253
A Task Collection
Procedure
Step 1 In the NE Explorer, select the required Ethernet switching board, and then choose Configuration > Ethernet Service > Ethernet LAN Service from the Function Free. Step 2 Select a created bridge, and then click the Disable MAC Address tab. Step 3 Click New. The Disable MAC Address Creation dialog box is displayed. Step 4 Set the parameters of the disabled MAC address entries.
Parameters
Parameter VLAN ID Value Range 1 to 4095 Default Value Description l In the case of IEEE 802.1d and IEEE 802.1ad bridges, this parameter is invalid if MAC Address Learning Mode is SVL. That is, the preset static MAC address entries are valid for all VLANs. l In the case of IEEE 802.1d and IEEE 802.1ad bridges, if MAC Address Learning Mode is set to IVL, the preset static MAC address entries are valid for only the VLANs whose VLAN ID is equal to the preset VLAN ID. l You need to set this parameter according to the actual situation. MAC Address You need to set this parameter according to the actual situation.
A.20.3 Setting the Aging Time of a MAC Address Table Entry

In the case of an Ethernet switching board, the aging time of a MAC address table entry is five minutes by default.
Prerequisite
A Task Collection
Ethernet switching boards must be created on the Slot Layout. Ethernet services must be created.

Web LCT
Precautions
Procedure
Step 1 In the NE Explorer, select the required Ethernet switching board, and then choose Configuration > Layer-2 Switching Management > Aging Time from the Function Tree. Step 2 Change the aging time of the MAC address table entry. 1. 2. Double-click MAC Address Aging Time corresponding to this Ethernet switching board. The MAC Address Aging Time dialog box is displayed. Set the duration and unit of the aging time.
3.
Click OK.
Issue 05 (2010-10-30)
A-255
A Task Collection
Parameters
Parameter MAC Address Aging Time Value Range 1 Min to 120 Day Default Value 5 Min Description l If one entry is not updated in a certain period, that is, if no new packet from this MAC address is received to enable the re-learning of this MAC address, this entry is deleted automatically. This mechanism is called aging, and this period is called the aging time. l If you set this parameter to a very large value, the bridge stores excessive MAC address table entries that are outdated, which exhausts the resources of the MAC address forwarding table. l If you set this parameter to a very small value, the bridge may delete the MAC address table entry that is required, which reduces the forwarding efficiency. l It is recommended that you use the default value.
A.20.4 Querying or Deleting a Dynamic MAC Address

By querying a dynamic MAC address, you can learn about all the MAC address entries that are learned by a bridge.
Prerequisite

Web LCT
Precautions
Procedure
Step 1 In the NE Explorer, select the required Ethernet switching board, and then choose Configuration > Ethernet Service > Ethernet LAN Service from the Function Free. Step 2 Select a created bridge, and then click the Self-learning MAC Address tab.
A Task Collection
Step 3 Click First Page, Previous, or Next to view the dynamic entries of a MAC address table. Step 4 Optional: Select a MAC address to be deleted, and then click Clear MAC Address. ----End
A.20.5 Querying the Actual Capacity of a MAC Address Table

This topic describes how to query the actual capacity of a MAC address table.
Prerequisite

Web LCT
Precautions
Procedure
Step 1 In the NE Explorer, select the required Ethernet switching board, and then choose Configuration > Ethernet Service > Ethernet LAN Service from the Function Free. Step 2 Select a created bridge, and then click the VLAN MAC Address Table Capacity tab. Step 3 Click Query. Step 4 Query the actual capacity of the MAC address table. ----End
A.21 Testing Ethernet Services

By testing Ethernet services, you can check whether Ethernet services are available on radio links. A.21.1 Testing Ethernet Services by Using the LB Function When both ends of an Ethernet service support ETH-OAM, the LB function is preferred to test the Ethernet service. A.21.2 Testing Ethernet Services by Using the Ping Function When only one end of an Ethernet service supports the ETH-OAM function, the ping function is preferred to test the Ethernet service. A.21.3 Testing Ethernet Services by Using Laptops When neither end of the Ethernet service supports the ETH-OAM function, you can check Ethernet service by using laptops.
A Task Collection
A.21.1 Testing Ethernet Services by Using the LB Function

When both ends of an Ethernet service support ETH-OAM, the LB function is preferred to test the Ethernet service.
Prerequisite
Ethernet services must be configured between sites. Creating the Maintenance Domain (MD), creating the Maintenance Association (MA), and creating the Maintenance Association End Point (MEP) must be complete.

Web LCT
Context
EMS6 and EFP6 support ETH-OAM.
Test Connection Diagram

The following test procedure considers the Ethernet service between PORT1 on NE1 and PORT2 on NE2 as an example, as shown in Figure A-1. Figure A-1 Networking diagram for testing Ethernet services
NE 1 Microwave networking PORT 1
NE 2
PORT 2
An Ethernet link is available from PORT1 on NE1 to PORT2 on NE2. In addition, the MD, MA, and MEP are configured.
Procedure
Step 1 In NE Explorer of NE1, select an Ethernet board, and then choose Configuration > Ethernet Maintenance > Ethernet Service OAM from the Function Tree. Step 2 Select the MD, MA, and MEP that correspond to PORT1, and click OAM Operation. Step 3 Select Start LB. The LB Test window is displayed.
A Task Collection
Step 4 Enter the MP ID of NE2 in LB Sink MP ID. Step 5 Click Start LB. Step 6 Check Test Result. The test results should meet the service requirements. ----End
A.21.2 Testing Ethernet Services by Using the Ping Function

When only one end of an Ethernet service supports the ETH-OAM function, the ping function is preferred to test the Ethernet service.
Prerequisite
l l An Ethernet service must be configured between sites. The maintenance domain, maintenance association, and maintenance point must be created for the NE that supports the ETH-OAM function. For details of the creation, see Creating Maintenance Domain, Creating Maintenance Association, and Creating Maintenance Point.

Web LCT

The following test procedure considers the Ethernet service between PORT1 on NE1 and PORT2 on NE2 as an example, as shown in Figure A-2. Wherein, NE1 supports the ETH-OAM function, and is configured with the maintenance domain, maintenance association, and maintenance point.
A Task Collection
Figure A-2 Networking diagram for testing Ethernet services
Microwave networking PORT 1 NE 1 NE 2 PORT 2 10.1.1.5
10.1.1.2
Precautions
If NE2 is not connected to an Ethernet board or you are not aware of the IP address of the clientside equipment, you must connect the Ethernet service port of the Ethernet board to the ETH port of the SCC board. If TAG of the Ethernet board is set to Tag Aware, see Configuring the External Port of the Ethernet Board to set the TAG of the Ethernet board to Access, and to set Default VLAN ID to the VLAN ID of the accessed service.
Procedure
Step 1 In NE Explorer of NE1, select an Ethernet board, and then choose Configuration > Ethernet Maintenance > Ethernet Maintenance > Ethernet Service OAM from the Function Tree. Step 2 Select the maintenance domain, maintenance association, and maintenance point that correspond to PORT1, and click OAM Operation. Step 3 Select Start Ping. The Start Ping window is displayed.
A-260
Issue 05 (2010-10-30)
A Task Collection
Step 4 In Send Mode, select Burst Mode. Step 5 In IP Address configuration, enter Destination Ip address and Local IP Address.
NOTE
If the Ethernet cable is connected to the ETH port of the SCC board, Destination Ip address is the IP address of the NE.
l Destination Ip address: indicates the IP address of the client-side equipment, which is 10.1.1.5. l Local IP Address: indicates the IP address that is not used on the network segment of the destination IP address. In this example, this parameter takes the value 10.1.1.244. Step 6 Click Start Ping. In Detail, check whether the test result meets the service requirement. ----End
A.21.3 Testing Ethernet Services by Using Laptops

When neither end of the Ethernet service supports the ETH-OAM function, you can check Ethernet service by using laptops.
Prerequisite
An Ethernet service must be configured between sites.

l l Web LCT Laptops

The following test procedure considers the Ethernet service between PORT1 on NE1 and PORT2 on NE2 as an example, as shown in Figure A-3. Figure A-3 Networking diagram for testing Ethernet services
129.9.9.1 Microwave networking PORT 1 10.1.1.2 NE 1 NE 2
129.9.9.2
PORT 2 10.1.1.5
Issue 05 (2010-10-30)
A-261
A Task Collection
Precautions
l If the working mode of the Ethernet board is different from the working mode of the network adapter (the working mode of the network adapter is auto-negotiation by default), see Configuring the External Port of the Ethernet Board to set the working mode of the test port to the same as the working mode of the network adapter. If TAG of the Ethernet board is set to Tag Aware, see Configuring the External Port of the Ethernet Board to set the TAG of the Ethernet board to Access, and to set Default VLAN ID to the VLAN ID of the accessed service.
Procedure
Step 1 Use an Ethernet cable to connect the Ethernet port of the laptop to the Ethernet service port of the IDU, based on the test connection diagram. Step 2 Set the IP addresses of the two laptops and ensure the IP addresses are on the same network segment. Set the IP address for laptop A. l IP address: 10.1.1.2 l Subnet mask: 255.255.0.0 l Default gateway: null Set the IP address for laptop B. l IP address: 10.1.1.5 l Subnet mask: 255.255.0.0 l Default gateway: null Step 3 Start the MS-DOS program of laptop A, and run the ping 10.1.1.5 -n 200 -l 2000 command.
NOTE
l 10.1.1.5: indicates the IP address of laptop B. l -n Num: indicates that Num packets are sent to the opposite computer. l -l Num: indicates that the buffer area for transmission is Num bytes in size.
Step 4 After you run the command, check the result. The result shows that there are no lost packets. That is, the output display should contain the following information: Lost = 0 (0% loss) ----End
A-262
Issue 05 (2010-10-30)
B Glossary
B
Terms are listed in an alphabetical order. B.1 0-9 B.2 A-E B.3 F-J B.4 K-O B.5 P-T B.6 U-Z
Glossary
Issue 05 (2010-10-30)
B-1
B Glossary
B.1 0-9
1+1 protection An architecture that has one normal traffic signal, one working SNC/trail, one protection SNC/trail and a permanent bridge. At the source end, the normal traffic signal is permanently bridged to both the working and protection SNC/trail. At the sink end, the normal traffic signal is selected from the better of the two SNCs/trails. Due to the permanent bridging, the 1+1 architecture does not allow an extra unprotected traffic signal to be provided. The standard electronics industries association (EIA) rack unit (44 mm/1.75 in.) 802.1Q in 802.1Q (QinQ) is a VLAN feature that allows the equipment to add a VLAN tag to a tagged frame.The implementation of QinQ is to add a public VLAN tag to a frame with a private VLAN tag, making the frame encapsulated with two layers of VLAN tags. The frame is forwarded over the service provider's backbone network based on the public VLAN tag. By this, a layer 2 VPN tunnel is provided to customers.The QinQ feature enables the transmission of the private VLANs to the peer end transparently.
1U 802.1Q in 802.1Q
B.2 A-E
A
ABR ACAP Access Control List See Available Bit Rate See adjacent channel alternate polarization Access Control List (ACL) is a list of IP address. The addresses listed in the ACL are used for authentication. If the ACL for the user is not null, it indicates that the address where the user logged in is contained in the list. See Access Control List A technology that is used to automatically adjust the modulation mode according to the channel quality. When the channel quality is favorable, the equipment adopts a highefficiency modulation mode to improve the transmission efficiency and the spectrum utilization of the system. When the channel quality is degraded, the equipment adopts the low-efficiency modulation mode to improve the anti-interference capability of the link that carries high-priority services. See Analog to Digital Converter Add/Drop Multiplexing. Network elements that provide access to all or some subset of the constituent signals contained within an STM-N signal. The constituent signals are added to (inserted), and/or dropped from (extracted) the STM-N signal as it passed through the ADM. Address Resolution Protocol (ARP) is 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. The address resolution is a process in which the host converts the target IP address into a target MAC address before transmitting a frame. The basic function of the ARP is to query the MAC address of the target equipment through its IP address.
ACL adaptive modulation
ADC add/drop multiplexer
Address Resolution Protocol
B-2
Issue 05 (2010-10-30)
B Glossary
adjacent channel alternate polarization ADM Administrative Unit
A channel configuration method, which uses two adjacent channels (a horizontal polarization wave and a vertical polarization wave) to transmit two signals. See add/drop multiplexer 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. See Assured Forwarding See Automatic Gain Control A collection of objects that makes a whole. An aggregation can be a concrete or conceptual set of whole-part relationships among objects. See Alarm Indication Signal When an alarm is generated on the device side, the alarm is reported to the N2000. Then, an alarm panel prompts and the user can view the details of the alarm. The shunt-wound output of the alarm signals of several subracks or cabinets. An NE reports the detected alarm to the element management system (EMS). Based on the filter state of the alarm, the EMS determines whether to display or save the alarm information. If the filter state of an alarm is set to Filter, the alarm is not displayed or stored on the EMS. The alarm, however, is still monitored by the NE. A code sent downstream in a digital network as an indication that an upstream failure has been detected and alarmed. It is associated with multiple transport layers. Note: See ITU-T Rec. G.707/Y.1322 for specific AIS signals. A function used not to monitor alarms for a specific object, which may be the networkwide equipment, a specific NE, a specific board and even a specific function module of a specific board. See adaptive modulation An electronic circuit that converts continuous signals to discrete digital numbers. The reverse operation is performed by a digital-to-analog converter (DAC). See Automatic Protection Switching See Address Resolution Protocol amplitude shift keying Assured Forwarding (AF) is one of the four per-hop behaviors (PHB) defined by the Diff-Serv workgroup of IETF. AF is suitable for certain key data services that require assured bandwidth and short delay. For traffic within the limit, AF assures quality in forwarding. For traffic that exceeds the limit, AF degrades the service class and continues to forward the traffic instead of discarding the packets. A data transfer technology based on cell, in which packets allocation relies on channel demand. It supports fast packet switching to achieve efficient utilization of network resources. The size of a cell is 53 bytes, which consist of 48-byte payload and 5-byte header. See Asynchronous Transfer Mode ATM Permanent Virtual Circuit
AF AGC aggregation AIS Alarm automatic report alarm cascading Alarm Filtering
Alarm Indication Signal Alarm suppression
AM Analog to Digital Converter APS ARP ASK Assured Forwarding
Asynchronous Transfer Mode
ATM ATM PVC
Issue 05 (2010-10-30)
B-3
B Glossary
ATPC attenuator AU Automatic Gain Control Automatic Protection Switching automatic transmit power control Available Bit Rate
See automatic transmit power control A device used to increase the attenuation of an Optical Fibre Link. Generally used to ensure that the signal at the receive end is not too strong. See Administrative Unit A process or means by which gain is automatically adjusted in a specified manner as a function of a specified parameter, such as received signal level. Automatic Protection Switching (APS) is the capability of a transmission system to detect a failure on a working facility and to switch to a standby facility to recover the traffic. A method of adjusting the transmit power based on fading of the transmit signal detected at the receiver 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.
B
Backward Defect Indication bandwidth When detecting a defect, the sink node of a LSP uses backward defect indication (BDI) to inform the upstream end of the LSP of a downstream defect along the return path. 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 Controller A logical entity that connects the BTS with the MSC in a GSM 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. Base Transceiver Station BDI BE BER best effort A Base Transceiver Station terminates the radio interface. It allows transmission of traffic and signaling across the air interface. The BTS includes the baseband processing, radio equipment, and the antenna. See Backward Defect Indication See best effort See Bit Error Rate A kind of PHB (Per-Hop-Behavior). In the forwarding process of a DS domain, the traffic of this PHB type features reachability but the DS node does not guarantee the forwarding quality. Basic Input Output System Bit-Interleaved Parity An incompatibility between a bit in a transmitted digital signal and the corresponding bit in the received digital signal. Bit error rate. Ratio of received bits that contain errors. BER is an important index used to measure the communications quality of a network.
BIOS BIP bit error Bit Error Rate
B-4
Issue 05 (2010-10-30)
B Glossary
blank filler panel BPDU Bridge Protocol Data Unit
A piece of board to cover vacant slots, to keep the frame away from dirt, to keep proper airflow inside the frame, and to beautify the frame appearance. See Bridge Protocol Data Unit 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. A means of delivering information to all members in a network. The broadcast range is determined by the broadcast address. See Base Station Controller See Base Transceiver Station A storage area used for handling data in transit. Buffers are used in internetworking to compensate for differences in processing speed between network devices. Bursts of data can be stored in buffers until they can be handled by slower processing devices.
Broadcast BSC BTS Buffer
C
C-VLAN cable ladder Customer VLAN (1) A cable ladder is a frame which supports electrical cables. (2) Two metal cables usually made of stainless steel with rungs of lightweight metal tubing such as aluminum, six or eight inches wide spaced about eighteen inches apart. It can be rolled into a compact lightweight bundle for transport ease. The tape used to bind the cables. The trough which is used for cable routing in the cabinet. Captive nuts (or as they are more correctly named, 'tee nuts') have a range of uses but are more commonly used in the hobby for engine fixing (securing engine mounts to the firewall), wing fixings, and undercarriage fixing. See committed access rate See Constant Bit Rate See Circuit Cross Connect See Co-Channel Dual Polarization See continuity check message See Customer Edge The CPU is the brains of the computer. Sometimes referred to simply as the processor or central processor, the CPU is where most calculations take place. See Circuit Emulation Service See compact flash Cisco Group Management Protocol Cable distribution plate A component which is used to arrange the cables in order.
cable tie cabling trough captive nut
CAR CBR CCC CCDP CCM CE Central Processing Unit CES CF CGMP
Issue 05 (2010-10-30)
B-5
B Glossary
CIR Circuit Cross Connect Circuit Emulation Service
See Committed Information Rate An implementation of MPLS L2VPN through the static configuration of labels. 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. See Common and Internal Spanning Tree A switch of the highest priority is elected as the root in an MSTP network. A class object that stores the priority mapping rules. When network congestion occurs, the class of service (CoS) first processes services by different priority levels from high to low. If the bandwidth is insufficient to support all services, the CoS dumps the services of low priority. The method to keep the time on each node being synchronized with a clock source in a network. A channel configuration method, which uses a horizontal polarization wave and a vertical polarization wave to transmit two signals. The Co-Channel Dual Polarization is twice the transmission capacity of the single polarization. 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. A packet whose priority is determined by defined colors. Two or multiple BTS cabinets of the same type are combined to serve as one BTS. A traffic control method that uses a set of rate limits to be applied to a router interface. CAR is a configurable method by which incoming and outgoing packets can be classified into QoS (Quality of Service) groups, and by which the input or output transmission rate can be defined. The rate at which a frame relay network agrees to transfer information in normal conditions. Namely, it is the rate, measured in bit/s, at which the token is transferred to the leaky bucket.
CIST CIST root Class of Service
Clock tracing Co-Channel Dual Polarization Coarse Wavelength Division Multiplexing Colored packet Combined cabinet committed access rate
Committed Information Rate
Common and Internal Common and Internal Spanning Tree. The single Spanning Tree calculated by STP and Spanning Tree RSTP together with the logical continuation of that connectivity through MST Bridges and regions, calculatedby MSTP to ensure that all LANs in the Bridged Local Area Network are simply and fully connected. compact flash Compact flash (CF) was originally developed as a type of data storage device used in portable electronic devices. For storage, CompactFlash typically uses flash memory in a standardized enclosure. A process that combines multiple virtual containers. The combined capacities can be used a single capacity. The concatenation also keeps the integrity of bit sequence. A plate that connects two adjacent cabinet together at the cabinet top for fixing.
Concatenation connecting plate for combining cabinets
B-6
Issue 05 (2010-10-30)
B Glossary
Connectivity Check
Ethernet CFM can detect the connectivity between MEPs. The detection is achieved by each MEP transmitting a Continuity Check Message (CCM) periodically. This detection is called CC detection. constant bit rate. 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. An extension of shortest path algorithms like OSPF and IS-IS. The path computed using CSPF is a shortest path fulfilling set of constrains. It simply means that it runs shortest path algorithm after pruning those links that violate a given set of constraints. A constraint could be minimum bandwidth required per link (also know as bandwidth guaranteed constraint), end-to-end delay, maximum number of link traversed etc. CSPF is widely used in MPLS Traffic Engineering. The routing using CSPF is known as Constraint Based Routing (CBR). An alternative to RSVP (Resource ReSerVation Protocol) in MPLS (MultiProtocol Label Switching) networks. RSVP, which works at the IP (Internet Protocol) level, uses IP or UDP datagrams to communicate between LSR (Label Switched Routing) peers. RSVP does not require the maintenance of TCP (Transmission Control Protocol) sessions, although RSVP must assume responsibility for error control. CR-LDP is designed to facilitate the routing of LSPs (Label Switched Paths) through TCP sessions between LSR peers through the communication of label distribution messages during the session. CCM is used to detect the link status. A pipe which is used for fiber routing. See Class of Service See Central Processing Unit See Constraint-based Routed-Label Distribution Protocol See Cyclic Redundancy Check A technology used in the case of the Co-Channel Dual Polarization (CCDP) to eliminate the cross-connect interference between two polarization waves in the CCDP. See Constraint Shortest Path First 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. See Coarse Wavelength Division Multiplexing 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.
Constant Bit Rate
Constraint Shortest Path First
Constraint-based Routed-Label Distribution Protocol
continuity check message corrugated tube CoS CPU CR-LDP CRC cross polarization interference cancellation CSPF Customer Edge CWDM Cyclic Redundancy Check
Issue 05 (2010-10-30)
B-7
B Glossary
D
Data Circuit-terminal Equipment Data Communication Network Also Data Communications Equipment (DCE) and Data Carrier Equipment (DCE). The basic function of a DCE is to convert data from one interface, such as a digital signal, to another interface, such as an analog signal. One example of DCE is a modem. A communication network used in a TMN or between TMNs to support the Data Communication Function (DCF).
Data Communications The data channel that uses the D1-D12 bytes in the overhead of an STM-N signal to Channel transmit information on operation, management, maintenance and provision (OAM&P) between NEs. The DCC channels that are composed of bytes D1-D3 is referred to as the 192 kbit/s DCC-R channel. The other DCC channel that are composed of bytes D4-D12 is referred to as the 576 kbit/s DCC-M channel. Datagram DC DC-C DC-I DC-Return Common (with Ground) DC-Return Isolate (with Ground) DCC DCE DCN DDF DDN DE Detour LSP diamond-shaped nut A kind of PDU which is used in Connectionless Network Protocol, such as IP datagram, UDP datagram. See Direct Current See DC-Return Common (with Ground) See DC-Return Isolate (with Ground) 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. 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 is isolated from the PGND on the line between the output of the power supply cabinet and the electric equipment. See Data Communications Channel See Data Circuit-terminal Equipment See Data Communication Network See Digital Distribution Frame See Digital Data Network See discard eligible The LSP that is used to re-route traffic around a failure in one-to-one backup. A type of nut that is used to fasten the wiring frame to the cabinet.
Differentiated Services A service architecture that provides the end-to-end QoS function. It consists of a series of functional units implemented at the network nodes, including a small group of perhop forwarding behaviors, packet classification functions, and traffic conditioning functions such as metering, marking, shaping and policing. Differentiated Services Differentiated Services CodePoint. A marker in the header of each IP packet using bits Code Point 0-6 in the DS field. Routers provide differentiated classes of services to various service streams/flows based on this marker. In other words, routers select corresponding PHB according to the DSCP value. DiffServ Digital Data Network See Differentiated Services 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.
B-8
Issue 05 (2010-10-30)
B Glossary
Digital Distribution Frame digital modulation
A type of equipment used between the transmission equipment and the exchange with transmission rate of 2 to 155 Mbit/s to provide the functions such as cables connection, cable patching, and test of loops that transmitting digital signals. A digital modulation 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. Electrical current whose direction of flow does not reverse. The current may stop or change amplitude, but it always flows in the same direction. A bit in the frame relay header. It indicates the priority of a packet. If a node supports the FR QoS, the rate of the accessed FR packets is controlled. When the packet traffic exceeds the specified traffic, the DE value of the redundant packets is set to 1. In the case of network congestion, the packets with DE value as 1 are discarded at the node. Distance Vector Multicast Routing Protocol. The DVMRP protocol is 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. A DS node that connects one DS domain to a node either in another DS domain or in a domain that is not DS-capable. In the DifferServ mechanism, the DS domain is a domain consisting of a group of network nodes that share the same service provisioning policy and same PHB. It provides point-to-point QoS guarantees for services transmitted over this domain. A DS node located at the center of a DS domain. It is a non-DS boundary node. A DS-compliant node, which is subdivided into DS boundary node and ID interior node. See Differentiated Services Code Point
Direct Current discard eligible
Distance Vector Multicast Routing Protocol DS boundary node DS domain
DS interior node DS node DSCP
dual-polarized antenna An antenna intended to radiate or receive simultaneously two independent radio waves orthogonally polarized. DVMRP See Distance Vector Multicast Routing Protocol
E
E-AGGR E-LAN E-Tree EBS ECC EF EFM Electro Magnetic Interference Ethernet-Aggregation See Ethernet LAN See Ethernet-Tree See Excess Burst Size See Embedded Control Channel See Expedited Forwarding See Ethernet in the First mile Any electromagnetic disturbance that interrupts, obstructs, or otherwise degrades or limits the effective performance of electronics/electrical equipment.
Issue 05 (2010-10-30)
B-9
B Glossary
electromagnetic compatibility
Electromagnetic compatibility is the 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. [NTIA]
ElectroStatic Discharge The sudden and momentary electric current that flows between two objects at different electrical potentials caused by direct contact or induced by an electrostatic field. Embedded Control Channel EMC EMI Engineering label EPLn equalization ERPS ES-IS ESD ESD jack ETH-CC ETH-LB ETH-LT Ethernet An ECC provides a logical operations channel between SDH NEs, utilizing a data communications channel (DCC) as its physical layer. See electromagnetic compatibility See Electro Magnetic Interference A mark on a cable, a subrack, or a cabinet for identification. See Ethernet Private LAN A method of avoiding selective fading of frequencies. Equalization can compensate for the changes of amplitude frequency caused by frequency selective fading. See ethernet ring protection switching End System to Intermediate System See ElectroStatic Discharge Electrostatic discharge jack. A hole in the cabinet or shelf, which connect the shelf or cabinet to the insertion of ESD wrist strap. Ethernet Continuity Check Ethernet Loopback Ethernet Link Trace A technology complemented in LAN. It adopts 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. The Ethernet network features high reliability and easy maintaining.. Last mile access from the broadband device to the user community. The EFM takes the advantages of the SHDSL.bis technology and the Ethernet technology. The EFM provides both the traditional voice service and internet access service of high speed. In addition, it meets the users' requirements on high definition television system (HDTV) and Video On Demand (VOD). Ethernet LAN. A L2VPN service type that is provided for the user Ethernet in different domains over the PSN network. For the user Ethernet, the entire PSN network serves as a Layer 2 switch. Both a LAN service and a private service. Transport bandwidth is never shared between different customers. protection switching mechanisms for ETH layer Ethernet ring topologies. A service that is both a LAN service and a virtual private service. etherenet tree. An Ethernet service type that is based on a Point-to-multipoint Ethernet Virtual Connection.
Ethernet in the First mile
Ethernet LAN
Ethernet Private LAN ethernet ring protection switching Ethernet Virtual Private LAN Ethernet-Tree
B-10
Issue 05 (2010-10-30)
B Glossary
ETS ETSI ETSI 300mm cabinet European Telecommunications Standards Institute EVPL EVPLn Excess Burst Size
European Telecommunication Standards See European Telecommunications Standards Institute A cabinet which is 600mm in width and 300mm in depth, compliant with the standards of the ETSI. A standards-setting body in Europe. Also the standards body responsible for GSM.
Ethernet Virtual Private Line See Ethernet Virtual Private LAN excess burst size. In the single rate three color marker (srTCM) mode, the traffic control is realized 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. An operation to check if the protection switching protocol functions normally. The protection switching is not really performed.
Exercise Switching
Expedited Forwarding Expedited Forwarding (EF) is 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".
B.3 F-J
F
Failure If the fault persists long enough to consider the ability of an item with a required function to be terminated. The item may be considered as having failed; a fault has now been detected. A type of Ethernet with a maximum transmission rate of 100 Mbit/s. It complies with the IEEE 802.3u standard and extends the traditional media-sharing Ethernet standard. The likn pulse that is used to encode information during automatic negotiation. Frame Check Sequence See frequency diversity See Forward Defect Indication See Fast Ethernet See Forward Error Correction Fast Failure Detection A device installed at the end of a fiber, optical source or receive unit. It is used to couple the optical wave to the fiber when connected to another device of the same type. A connector can either connect two fiber ends or connect a fiber end and a optical source (or a detector).
Fast Ethernet fast link pulse FCS FD FDI FE FEC FFD Fiber Connector
Issue 05 (2010-10-30)
B-11
B Glossary
fiber patch cord Field Programmable Gate Array
A kind of fiber used for connections between the subrack and the ODF, and for connections between subracks or inside a subrack. 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 arraies. See First in First out A member of the TCP/IP suite of protocols, used to copy files between two computers on the Internet. Both computers must support their respective FTP roles: one must be an FTP client and the other an FTP server. A stack management mechanism. The first saved data is first read and invoked. See fast link pulse This function forces the service to switch from the working channel to the protection channel, with the service not to be restored automatically. This switch occurs regardless of the state of the protection channels or boards, unless the protection channels or boards are satisfying a higher priority bridge request. Forward defect indication (FDI) is 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. 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. Also referred to as the data plane. The forwarding plane is connection-oriented, and can be used in Layer 2 networks such as an ATM network. See Field Programmable Gate Array Piece of a larger packet that has been broken down to smaller units. Process of breaking a packet into smaller units when transmitting over a network medium that can not support the original size of the packet. A frame, starting with a header, is a string of bytes with a specified length. Frame length is represented by the sampling circle or the total number of bytes sampled during a circle. A header comprises one or a number of bytes with pre-specified values. In other words, a header is a code segment that reflects the distribution (diagram) of the elements prespecified by the sending and receiving parties. A diversity scheme that enables two or more microwave frequencies with a certain frequency interval are used to transmit/receive the same signal and selection is then performed between the two signals to ease the impact of fading. See File Transfer Protocol The system that can transmit information in both directions on a communication link.On the communication link, both parties can send and receive data at the same time.
FIFO File Transfer Protocol
First in First out FLP Forced switch
Forward Defect Indication
Forward Error Correction Forwarding plane FPGA Fragment Fragmentation frame
frequency diversity
FTP Full duplex
B-12
Issue 05 (2010-10-30)
B Glossary
G
gateway network element GCP GE A network element that is used for communication between the NE application layer and the NM application layer See GMPLS control plan See Gigabit Ethernet
Generic traffic shaping A traffic control measure that initiatively adjusts the output speed of the traffic. This is to adapt the traffic to network resources that can be provided by the downstream router to avoid packet discarding and congestion. GFP Gigabit Ethernet Generic Framing Procedure GE adopts the IEEE 802.3z. GE is compatible with 10 Mbit/s and 100 Mbit/s Ethernet.It runs at 1000Mbit/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. A global navigation satellite system. It provides reliable positioning, navigation, and timing services to worldwide users . The OptiX GMPLS control plan (GCP) is the ASON software developed by Huawei. The OptiX GCP applies to the OptiX OSN product series. By using this software, the traditional network can evolve into the ASON network. The OptiX OSN product series support the ASON features. See gateway network element See Global Positioning System See Graceful Restart In IETF, protocols related to Internet Protocol/Multiprotocol Label Switching (IP/ MPLS) such as Open Shortest Path First (OSPF), Intermediate System-Intermediate System (IS-IS), Border Gateway Protocol (BGP), Label Distribution Protocol (LDP), and Resource Reservation Protocol (RSVP) are extended to ensure that the forwarding is not interrupted when the system is restarted. This reduces the flapping of the protocols at the control plane when the system performs the active/standby switchover. This series of standards is called Graceful Restart. A visual computer enviroment that represents programs, files, and options with graphical images, such as icons, menus, and dialog boxes, on the screen. (electricity) Opposition of the earth to the flow of current through it; its value depends on the nature and moisture content of the soil, on the material, composition, and nature of connections to the earth, and on the electrolytic action present. See Generic traffic shaping See Graphical User Interface Components to guide, position, and support plug-in boards.
Global Positioning System GMPLS control plan
GNE GPS GR Graceful Restart
Graphical User Interface ground resistance
GTS GUI guide rail
Issue 05 (2010-10-30)
B-13
B Glossary
H
H-QoS HA half-duplex Hierarchical Quality of Service See High Availability A transmitting mode in which a half-duplex system provides for communication in both directions, but only one direction at a time (not simultaneously). Typically, once a party begins receiving a signal, it must wait for the transmitter to stop transmitting, before replying. High Density Bipolar Code 3 See High level Data Link Control procedure The ability of a system to continuously perform its functions during a long period, which may exceeds the suggested working time of the independent components. You can obtain the high availability (HA) by using the error tolerance method. Based on learning cases one by one, you must also clearly understand the limitations of the system that requires an HA ability and the degree to which the ability can reach. A data link protocol from ISO for point-to-point communications over serial links. Derived from IBM's SDLC protocol, HDLC has been the basis for numerous protocols including X.25, ISDN, T1, SS7, GSM, CDPD, PPP and others. Various subsets of HDLC have been developed under the name of Link Access Procedure (LAP). 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. The priority of the tunnel with respect to holding resources, ranging from 0 (indicates the highest priority) to 7. It is used to determine whether the resources occupied by the tunnel can be preempted by other tunnels. 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. A mechanism of ensuring device running security. The environment variables and storage information of each running device are synchronized to the standby device. When the faults occur on the running device, the standby device can take over the services in the faulty device in automatic or manual way to ensure the normal running of the entire system. Higher Order Path See High Speed Downlink Packet Access Hitless Switch Mode High Tributary Bus The hybrid transmission of Native E1 and Native Ethernet signals. Hybrid radio supports the AM function.
HDB3 HDLC High Availability
High level Data Link Control procedure
High Speed Downlink Packet Access
Hold priority
Hop hot standby
HP HSDPA HSM HTB hybrid radio
I
ICMP IDU
B-14
See Internet Control Messages Protocol See indoor unit

B Glossary
IEC IEEE IETF IF IGMP IGMP snooping
See International Electrotechnical Commission See Institute of Electrical and Electronics Engineers The Internet Engineering Task Force See intermediate frequency See Internet Group Management Protocol A multicast constraint mechanism running on a layer 2 device. This protocol manages and controls the multicast group by listening to and analyze the Internet Group Management Protocol (IGMP) packet between hosts and layer 3 devices. In this manner, the spread of the multicast data on layer 2 network can be prevented efficiently. See Inverse Multiplexing over ATM The indoor unit of the split-structured radio equipment. It implements accessing, multiplexing/demultiplexing, and IF processing for services. A method of looping the signals from the cross-connect unit back to the cross-connect unit. 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. The area for the interface boards on the subrack.
IMA indoor unit Inloop Institute of Electrical and Electronics Engineers Interface board area
intermediate frequency The transitional frequency between the frequencies of a modulated signal and an RF signal. Intermediate System The basic unit in the IS-IS protocol used to transmit routing information and generate routes.
Intermediate System to A protocol used by network devices (routers) .IS-IS is a kind of Interior Gateway Protocol Intermediate System (IGP), used within the ASs. It is a link status protocol using Shortest Path First (SPF) algorithm to calculate the route. Internal Spanning Tree Internal spanning tree. A segment of CIST in a certain MST region. An IST is a special MSTI whose ID is 0. International Electrotechnical Commission International Organization for Standardization Internet Control Messages Protocol Internet Group Management Protocol Internet Protocol The International Electrotechnical Commission (IEC) is an international and nongovernmental standards organization dealing with electrical and electronical standards. ISO (International Organization for Standardization) is the world's largest developer and publisher of International Standards. ICMP belongs to the TCP/IP protocol suite. It is used to send error and control messages during the transmission of IP-type data packets. The protocol for managing the membership of Internet Protocol multicast groups among the TCP/IP protocols. It is used by IP hosts and adjacent multicast routers to establish and maintain multicast group memberships. The TCP/IP standard protocol that defines the IP packet as the unit of information sent across an internet and provides the basis for connectionless, best-effort packet delivery service. IP includes the ICMP control and error message protocol as an integral part. The entire protocol suite is often referred to as TCP/IP because TCP and IP are the two fundamental protocols. IP is standardized in RFC 791.
Issue 05 (2010-10-30)
B-15
B Glossary
Internet Protocol Version 6
A update version of IPv4. It is also called IP Next Generation (IPng). The specifications and standardizations provided by it are consistent with the Internet Engineering Task Force (IETF).Internet Protocol Version 6 (IPv6) is also called. It is a new version of the Internet Protocol, designed as the successor to IPv4. The specifications and standardizations provided by it are consistent with the Internet Engineering Task Force (IETF).The difference between IPv6 and IPv4 is that an IPv4 address has 32 bits while an IPv6 address has 128 bits. Inverse Multiplexing over ATM. The ATM inverse multiplexing technique 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. This is referred to as an IMA group. See Internet Protocol See Internet Protocol Version 6 See Intermediate System to Intermediate System See International Organization for Standardization See Internal Spanning Tree International Telecommunication Union - Telecommunication Standardization Sector Independence VLAN learning
Inverse Multiplexing over ATM
IP IPv6 IS-IS ISO IST ITU-T IVL
J
Jitter Short waveform variations caused by vibration, voltage fluctuations, and control system instability.
B.4 K-O
L
L2VPN Label Switched Path See Layer 2 virtual private network 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 normal routing mechanisms, or through configuration.
Label Switching Router The Label Switching Router (LSR) is the basic element of 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. LACP LAG LAN LAPD LAPS See Link Aggregation Control Protocol See link aggregation group See Local Area Network Link Access Procedure on the D channel Link Access Procedure-SDH
B-16
Issue 05 (2010-10-30)
B Glossary
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. A data forwarding method. In LAN, a network bridge or 802.3 Ethernet switch transmits and distributes packet data based on the MAC address. Since the MAC address is the second layer of the OSI model, this data forwarding method is called layer 2 switch.
layer 2 switch
Layer 2 virtual private A virtual private network realized in the packet switched (IP/MPLS) network by Layer network 2 switching technologies. LB LCAS LDPC line rate forwarding Link Aggregation Control Protocol See Loopback See Link Capacity Adjustment Scheme Low-Density Parity Check code The line rate equals the maximum transmission rate capable on a given type of media. Link Aggregation Control Protocol (LACP) is part of an IEEE specification (802.3ad) that allows you to bundle several physical ports to form a single logical channel. LACP allows a switch to negotiate an automatic bundle by sending LACP packets to the peer.
link aggregation group An aggregation that allows one or more links to be aggregated together to form a link aggregation group so that a MAC clientcan treat the link aggregation group as if it were a single link. Link Capacity Adjustment Scheme Link Protection The Link Capacity Adjustment Scheme (LCAS) is designed to allow the dynamic provisioning of bandwidth, using VCAT, to meet customer requirements. Protection provided by the bypass tunnel for the link on the working tunnel. The link is a downstream link adjacent to the PLR. When the PLR fails to provide node protection, the link protection should be provided. Linear Multiplex Section Protection 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). When the switching condition is satisfied, this function disables the service from being switched from the working channel to the protection channel. When the service has been switched, the function enables the service to be restored from the protection channel to the working channel. See Loss Of Frame Loss Of Multiframe A troubleshooting technique that returns a transmitted signal to its source so that the signal or message can be analyzed for errors. See Loss Of Pointer See Loss Of Signal A condition at the receiver or a maintenance signal transmitted in the PHY overhead indicating that the receiving equipment has lost frame delineation. This is used to monitor the performance of the PHY layer.
LMSP Local Area Network
Locked switching
LOF LOM Loopback LOP LOS Loss Of Frame
Issue 05 (2010-10-30)
B-17
B Glossary
Loss Of Pointer
Loss of Pointer: A condition at the receiver or a maintenance signal transmitted in the PHY overhead indicating that the receiving equipment has lost the pointer to the start of cell in the payload. This is used to monitor the performance of the PHY layer. Loss of signal (LOS) indicates that there are no transitions occurring in the received signal. The subrack close to the bottom of the cabinet when a cabinet contains several subracks. Lower Order Path Link State Path Through See Label Switched Path See Label Switching Router
Loss Of Signal Lower subrack LP LPT LSP LSR
M
MA MAC MAC MADM Maintenance Association Maintenance association End Point See Maintenance Association See Medium Access Control See Media Access Control Multi Add-Drop Multiplexer That portion of a Service Instance, preferably all of it or as much as possible, the connectivity of which is maintained by CFM. It is also a full mesh of Maintenance Entities. A MEP is an actively managed CFM Entity, associated with a specific DSAP of a Service Instance, which can generate and receive CFM frames and track any responses. It is an end point of a single Maintenance Association, and terminates a separate Maintenance Entity for each of the other MEPs in the same Maintenance Association. The Maintenance Domain (MD) refers to the network or the part of the network for which connectivity is managed by CFM. The devices in an MD are managed by a single ISP. Maintenance Point (MP) is one of either a MEP or a MIP. A type of database used for managing the devices in a communications network. It comprises a collection of objects in a (virtual) database used to manage entities (such as routers and switches) in a network. A protection switching. When the protection path is normal and there is no request of a higher level switching, the service is manually switched from the working path to the protection path, to test whether the network still has the protection capability. The MTU (Maximum Transmission Unit) is the size of the largest datagram that can be sent over a network. Maximum Burst Size See Message Communication Function See Maintenance Domain See Medium Dependent Interface The average time that a device will take to recover from a failure.
Maintenance Domain Maintenance Point Management Information Base Manual switching
Maximum Transfer Unit MBS MCF MD MDI Mean Time To Repair
B-18
Issue 05 (2010-10-30)
B Glossary
Media Access Control
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. A general reference to the low-level hardware protocols used to access a particular network. The term MAC address is often used as a synonym for physical addresses. The electrical and mechanical interface between the equipment and the media transmission. See Maintenance association End Point The MCF is composed of a protocol stack that allows exchange of management information with their prs . See Management Information Base Maintenance Intermediate Point See Multi-link Point to Point Protocol An L-shape steel sheet. One side is fixed on the front panel with screws, and the other side is fixed on the installation hole with screws. On both sides of a rack, there is an Lshaped metal fastener. This ensures that internal components are closely connected with the rack. Normally, an internal component is installed with two mount angles. See Maintenance Point Maintenance Point Identification See Multi-Protocol Label Switch The MPLS L2VPN provides the Layer 2 VPN service based on an MPLS network.In this case, on a uniform MPLS network, the carrier is able to provide Layer 2 VPNs of different media types, such as ATM, FR, VLAN, Ethernet, and PPP. The MPLS OAM provides continuity check for a single LSP, and provides a set of fault detection tools and fault correct mechanisms for MPLS networks. The MPLS OAM and relevant protection switching components implement the detection function for the CRLSP forwarding plane, and perform the protection switching in 50 ms after a fault occurs. In this way, the impact of a fault can be lowered to the minimum. Multiprotocol Label Switching Traffic Engineering In the case of reroute deployment, or when traffic needs to be transported through multiple trails, multiple LSP tunnels might be used. In traffic engineering, such a group of LSP tunnels are referred to as TE tunnels. An LSP tunnel of this kind has two identifiers. One is the Tunnel ID carried by the SENDER object, and is used to uniquely define the TE tunnel. The other is the LSP ID carried by the SENDER_TEMPLATE or FILTER_SPEC object. See Multiplex Section See multiplex section protection
Medium Access Control Medium Dependent Interface MEP Message Communication Function MIB MIP MLPPP mount angle
MP MPID MPLS MPLS L2VPN
MPLS OAM
MPLS TE MPLS TE tunnel
MS MSP
Issue 05 (2010-10-30)
B-19
B Glossary
MSTI MSTP MTBF MTTR MTU Multi-link Point to Point Protocol Multi-Protocol Label Switch
See Multiple Spanning Tree Instance See Multiple Spanning Tree Protocol Mean Time Between Failure See Mean Time To Repair See Maximum Transfer Unit A protocol used in ISDN connections. MLPPP lets two B channels act as a single line, doubling connection rates to 128Kbps. 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. A process of transmitting packets of data 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. Multiple spanning tree instance. One of a number of Spanning Trees calculated by MSTP within an MST Region, to provide a simply 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. Multiple spanning tree protocol. The MSTP 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. The MST region 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. The attributes for the same MST region are as follows: Same region name Same revision level Same mapping relation between the VLAN ID to MSTI The trail between and including two multiplex section trail termination functions. 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.
Multicast
Multiple Spanning Tree Instance
Multiple Spanning Tree Protocol
Multiple Spanning Tree Region
Multiplex Section multiplex section protection
N
N+1 protection NE NE Explorer A radio link protection system composed of N working channels and one protection channel. See Network Element The main operation interface, of the U2000, which is used to manage the OptiX equipment. In the NE Explorer, the user can configure, manage and maintain the NE, boards, and ports on a per-NE basis.
B-20
Issue 05 (2010-10-30)
B Glossary
Network Element
A network element (NE) contains both the hardware and the software running on it. One NE is at least equipped with one system control board which manages and monitors the entire network element. The NE software runs on the system control board. The network management system in charge of the operation, administration, and maintenance of a network.
network management system
Network Service Access A network address defined by ISO, through which entities on the network layer can Point access OSI network services. Network to Network Interface next hop NLP NMS NNHOP NNI Node This is an internal interface within a network linking two or more elements. The next router to which a packet is sent from any given router as it traverses a network on its journey to its final destination. Normal Link Pulse See network management system Next-Next-Hop See Network to Network Interface A node stands for a managed device in the network.For a device with a single frame, one node stands for one device.For a device with multiple frames, one node stands for one frame of the device.Therefore, a node does not always mean a device. A parameter of the FRR protection. It indicates that the bypass tunnel should be able to protect the downstream node that is involved in the working tunnel and adjacent to the PLR. The node cannot be a merge point, and the bypass tunnel should also be able to protect the downstream link that is involved in the working tunnel and adjacent to the PLR. A network element whose communication with the NM application layer must be transferred by the gateway network element application layer. See non-gateway network element See Network Service Access Point Not Stop Forwarding Network Serial Multiplexed Interface
Node Protection
non-gateway network element non-GNE NSAP NSF NSMI
O
OAM ODF ODU One-to-One Backup Open Shortest Path First See Operation, Administration and Maintenanc See Optical Distribution Frame See outdoor unit A local repair method in which a backup tunnel is separately created for each protected tunnel at a PLR. 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 of the network topology which is identical on all routers in the area.
Issue 05 (2010-10-30)
B-21
B Glossary
Open Systems Interconnection
A standard or "reference model" (officially defined by the International Organization of Standards (ISO)) for how messages should be transmitted between any two points in a telecommunication network. The reference model defines seven layers of functions that take place at each end of a communication. Operation, Administration and Maintenance. A group of network support functions that monitor and sustain segment operation, 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. A frame which is used to transfer and spool fibers. A channel that provides voice communication between operation engineers or maintenance engineers of different stations. See Open Systems Interconnection OptiX Software Platform See Open Shortest Path First The outdoor unit of the split-structured radio equipment. It implements frequency conversion and amplification for RF signals. A method of looping back the input signals received at an port to an output port without changing the structure of the signals. The ranger of optical energy level of output signals.
Operation, Administration and Maintenanc
Optical Distribution Frame orderwire OSI OSP OSPF outdoor unit Outloop Output optical power
B.5 P-T
P
Packet over SDH/ SONET packet switched network Packing case Path/Channel 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. A telecommunication network which works in packet switching mode. A case which is used for packing the board or subrack. A logical connection between the point at which a standard frame format for the signal at the given rate is assembled, and the point at which the standard frame format for the signal is disassembled. See peak burst size See Printed Circuit Board PCI (Peripheral Component Interconnect) bus. A high performance bus, 32-bit or 64-bit for interconnecting chips, expansion boards, and processor/memory subsystems. See Plesiochronous Digital Hierarchy Protocol Data Unit See Provider Edge
PBS PCB PCI bus PDH PDU PE

B-22
B Glossary
peak burst size
A parameter 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 this parameter should be not less than the maximum length of the IP packet that might be forwarded.
Peak Information Rate Peak Information Rate . A traffic parameter, expressed in bit/s, whose value should be not less than the committed information rate. Penultimate Hop Popping Penultimate Hop Popping (PHP) is a function performed by certain routers in an MPLS enabled network. It refers to the process whereby the outermost label of an MPLS tagged packet is removed by a Label Switched Router (LSR) before the packet is passed to an adjacent Label Edge Router (LER). A forwarding behavior applied at a DS-compliant node. This behavior belongs to the behavior aggregate defined in the DiffServ domain. See Per-Hop-Behavior See Penultimate Hop Popping Protocol Independent Multicast-Dense Mode See Protocol Independent Multicast-Sparse Mode See Peak Information Rate
Per-Hop-Behavior PHB PHP PIM-DM PIM-SM PIR
Plesiochronous Digital A multiplexing scheme of bit stuffing and byte interleaving. It multiplexes the minimum Hierarchy rate 64 kit/s into the 2 Mbit/s, 34 Mbit/s, 140 Mbit/s, and 565 Mbit/s rates. Point-to-Point Protocol A protocol on the data link layer, provides point-to-point transmission and encapsulates data packets on the network layer. It is located in layer 2 of the IP protocol stack. 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. See Packet over SDH/SONET A direct current power distribution box at the upper part of a cabinet, which supplies power for the subracks in the cabinet. See Point-to-Point Protocol Provider Provisioned VPN See Priority Queuing Pseudo-Random Binary Sequence Primary Reference Clock 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.
POS Power box PPP PPVPN PQ PRBS PRC Printed Circuit Board
Issue 05 (2010-10-30)
B-23
B Glossary
Priority Queuing
A priority queue is an abstract data type in computer programming that supports the following three operations: 1) InsertWithPriority: add an element to the queue with an associated priority 2) GetNext: remove the element from the queue that has the highest priority, and return it (also known as "PopElement(Off)", or "GetMinimum") 3) PeekAtNext (optional): look at the element with highest priority without removing it An area for the processing boards on the subrack. A cable which connects the equipment and the protection grounding bar. Usually, one half of the cable is yellow; while the other half is green. A specific path that is part of a protection group and is labeled protection.
Processing board area protection grounding cable Protection path
Protocol Independent A protocol for efficiently routing to multicast groups that may span wide-area (and interMulticast-Sparse Mode domain) internets. This protocol is named protocol independent because it is not dependent on any particular unicast routing protocol for topology discovery, and sparsemode because it is suitable for groups where a very low percentage of the nodes (and their routers) will subscribe to the multicast session. Unlike earlier dense-mode multicast routing protocols such as DVMRP and PIM-DM which flooded packets everywhere and then pruned off branches where there were no receivers, PIM-SM explicitly constructs a tree from each sender to the receivers in the multicast group. Multicast packets from the sender then follow this tree. Provider Edge A device that is located in the backbone network of the MPLS VPN structure. A PE is responsible for VPN user management, establishment of LSPs between PEs, and exchange of routing information between sites of the same VPN. During the process, 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. 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 Edge to Edge (PWE3) is a type of end-to-end Layer 2 transmitting technology. It emulates the essential attributes of a 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 Multiplexed (TDM) circuit and SONET/SDH. The simulation approximates to the real situation. See packet switched network Packet Transport Network See Pseudo wire See Pseudo Wire Emulation Edge-to-Edge
Pseudo wire
Pseudo Wire Emulation Edge-toEdge
PSN PTN PW PWE3
Q
QoS QPSK See Quality of Service See Quadrature Phase Shift Keying
Quadrature Phase Shift Quadrature Phase Shift Keying (QPSK) is a modulation method of data transmission Keying through the conversion or modulation and the phase determination of the reference signals (carrier). It is also called the fourth period or 4-phase PSK or 4-PSK. QPSK uses four dots in the star diagram. The four dots are evenly distributed on a circle. On these phases, each QPSK character can perform two-bit coding and display the codes in Gray code on graph with the minimum BER.
B-24 Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 05 (2010-10-30)
B Glossary
Quality of Service
Quality of Service, which determines the satisfaction of a subscriber for a service. QoS is influenced by the following factors applicable to all services: service operability, service accessibility, service maintainability, and service integrity.
R
Radio Freqency 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. A device used in the RNS to control the usage and integrity of radio resources. A packet loss algorithm used in congestion avoidance. It discards the packet according to the specified higher limit and lower limit of a queue so that global TCP synchronization resulted in traditional Tail-Drop can be prevented. 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. See Remote Defect Indication The received wide band power, including thermal noise and noise generated in the 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 is defined as the minimum acceptable value of average received power at point R to achieve a 1 x 10-10 BER. See Random Early Detection See Remote Error Indication A signal transmitted at the first opportunity in the outgoing direction when a terminal detects specific defects in the incoming signal. A remote error indication (REI) is sent upstream to signal an error condition. There are two types of REI alarms: Remote error indication line (REI-L) is sent to the upstream LTE when errors are detected in the B2 byte. Remote error indication path (REI-P) is sent to the upstream PTE when errors are detected in the B3 byte. A manage information base (MIB) defined by the Internet Engineering Task Force (IETF). RMON is mainly used to monitor the data flow of one network segment or the entire network. The Resource Reservation Protocol (RSVP) is designed for Integrated Service and is used to reserve resources on every node along a path. RSVP operates on the transport layer; however, RSVP does not transport application data. RSVP is a network control protocol like Internet Control Message Protocol (ICMP). A traffic control method. In telecommunication, when detecting that the transmit end transmits a large volume of traffic, the receive end sends signals to ask the transmit end to slow down the transmission rate. See Radio Freqency Request For Comment
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. B-25
Radio Network Controller Random Early Detection Rapid Spanning Tree Protocol RDI Received Signal Strength Indicator Receiver Sensitivity RED REI Remote Defect Indication Remote Error Indication
remote network monitoring Resource Reservation Protocol
Reverse pressure
RF RFC
Issue 05 (2010-10-30)
B Glossary
RIP RMON RNC Root alarm route Routing Information Protocol
See Routing Information Protocol See remote network monitoring See Radio Network Controller An alarm directly caused by anomaly events or faults in the network. Some lower-level alarms always accompany a root alarm. A route is the path that network traffic takes from its source to its destination. In a TCP/ IP network, each IP packet is routed independently. Routes can change dynamically. Routing Information Protocol: 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. A table that stores and updates the locations (addresses) of network devices. Routers regularly share routing table information to be up to date. A router relies on the destination address and on the information in the table that gives the possible routes--in hops or in number of jumps--between itself, intervening routers, and the destination. Routing tables are updated frequently as new information is available. Reed-Solomon encoding Received Signal Level See Received Signal Strength Indicator See Rapid Spanning Tree Protocol See Resource Reservation Protocol Radio Transmission Node
routing table
RS RSL RSSI RSTP RSVP RTN
S
SD SDH SDP SEMF Service Level Agreement See space diversity See Synchronous Digital Hierarchy Serious Disturbance Period Synchronous Equipment Management Function A management-documented agreement that defines the relationship between service provider and its customer. It also provides specific, quantifiable information about measuring and evaluating the delivery of services. The SLA details the specific operating and support requirements for each service provided. It protects the service provider and customer and allows the service provider to provide evidence that it has achieved the documented target measure. Severely Errored Second The priority of the tunnel with respect to obtaining resources, ranging from 0 (indicates the highest priority) to 7. It is used to determine whether the tunnel can preempt the resources required by other backup tunnels. See Signal Fail See Small Form-Factor Pluggable
SES Setup Priority
SF SFP
B-26
Issue 05 (2010-10-30)
B Glossary
side trough signal cable Signal Fail Signal Noise Ratio
The trough on the side of the cable rack, which is used to place nuts so as to fix the cabinet. Common signal cables cover the E1cable, network cable, and other non-subscriber signal cable. SF is a signal indicating the associated data has failed in the sense that a near-end defect condition (not being the degraded defect) is active. The SNR or S/N (Signal to Noise 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). 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. Of or relating to a telecommunications system in which only one message can be sent in either direction at one time. See Service Level Agreement To divide data into the information units proper for transmission. A specification for a new generation of optical modular transceivers. See SubNetwork Connection See SubNetwork Connection Protection See Simple Network Management Protocol See Signal Noise Ratio Strict Priority A diversity scheme that enables two or more antennas separated by a specific distance to transmit/receive the same signal and selection is then performed between the two signals to ease the impact of fading. Currently, only receive SD is used.
Simple Network Management Protocol
simplex SLA Slicing Small Form-Factor Pluggable SNC SNCP SNMP SNR SP space diversity
Spanning Tree Protocol Spanning Tree Protocol. STP is a protocol that is used in the LAN to remove the loop. STP applies to the redundant network to block some undesirable redundant paths through certain algorithms and prune a loop network into a loop-free tree network. SSM Static Virtual Circuit See Synchronization Status Message Static virtual circuit. A static implementation of MPLS L2VPN that transfers L2VPN information by manual configuration of VC labels, instead of by a signaling protocol.
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. Compare with TDM. STM STM-1 See synchronous transport module SDH Transport Module -1
Issue 05 (2010-10-30)
B-27
B Glossary
STM-1e STM-1o STP sub-network
STM-1 Electrical Interface STM-1 Optical Interface See Spanning Tree Protocol Sub-network is the logical entity in the transmission network and comprises a group of network management objects. The network that consists of a group of interconnected or correlated NEs, according to different functions. For example, protection subnet, clock subnet and so on. A sub-network can contain NEs and other sub-networks. Generally, a sub-network is used to contain the equipments which are located in adjacent regions and closely related with one another, and it is indicated with a sub-network icon on a topological view. The U2000 supports multilevels of sub-networks. A sub-network planning can better the organization of a network view. On the one hand, the view space can be saved, on the other hand, it helps the network management personnel focus on the equipments under their management. 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 and is matched with the IP address. A "transport entity" that transfers information across a subnetwork, it is formed by the association of "ports" on the boundary of the subnetwork.
subnet mask
SubNetwork Connection
SubNetwork A working subnetwork connection is replaced by a protection subnetwork connection if Connection Protection the working subnetwork connection fails, or if its performance falls below a required level. SVC SVL Switch See Static Virtual Circuit Shared VLAN Learning To filter, forward frames based on label or the destination address of each frame. This behavior operates at the data link layer of the OSI model.
Synchronization Status A message that is used to transmit the quality levels of timing signals on the synchronous Message timing link. Through this message, the node clocks of the SDH network and the synchronization network can aquire upper stream clock information, and the two perform operations on the corresponding clocks, such as tracing, switchover, or converting hold), and then forward the synchronization information of this node to down stream. Synchronous Digital Hierarchy SDH is 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 only 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 transport An STM is the information structure used to support section layer connections in the SDH. It consists of information payload and Section Overhead (SOH) information fields module organized in a block frame structure which repeats every 125 . The information is suitably conditioned for serial transmission on the selected media at a rate which is synchronized to the network. A basic STM is defined at 155 520 kbit/s. This is termed STM-1. Higher capacity STMs are formed at rates equivalent to N times this basic rate. STM capacities for N = 4, N = 16 and N = 64 are defined; higher values are under consideration.
B-28
Issue 05 (2010-10-30)
B Glossary
T
tail drop A type of QoS. When a queue within a network router reaches its maximum length, packet drops can occur. When a packet drop occurs, connection-based protocols such as TCP slow down their transmission rates in an attempt to let queued packets be serviced, thereby letting the queue empty. This is also known as tail drop because packets are dropped from the input end (tail) of the queue. 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. Tag Control Information See TransmissionControl Protocol See Time Division Multiplexing See traffic engineering See Traffic Engineering DataBase
Tail drop
TCI TCP TDM TE TEDB
Telecommunication The Telecommunications Management Network is a protocol model defined by ITU-T Management Network 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. TIM Time Division Multiplexing Trace Identifier Mismatch It is 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. 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 field when the packet arrives, and discards any packet if the TTL counter reaches zero. See Telecommunication Management Network A ToS sub-field (the bits 0 to 2 in the ToS field) in the ToS field of the IP packet header. See Tributary Protection Switch A task that effectively maps the service flows to the existing physical topology. TEDB is the abbreviation of the traffic engineering database. MPLS TE needs to know the features of the dynamic TE of every links by expanding the current IGP, which uses the link state algorithm, such as OSPF and IS-IS. The expanded OSPF and IS-IS contain some TE features, such as the link bandwidth and color. The maximum reserved bandwidth of the link and the unreserved bandwidth of every link with priority are rather important. Every router collects the information about TE of every links in its area and generates TE DataBase. TEDB is the base of forming the dynamic TE path in the MPLS TE network. It is 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.
Time To Live
TMN ToS priority TPS traffic engineering Traffic Engineering DataBase
Traffic shaping
Issue 05 (2010-10-30)
B-29
B Glossary
trail
A type of transport entity, mainly engaged in transferring signals from the input of the trail source to the output of the trail sink, and monitoring the integrality of the transferred signals. The protocol within TCP/IP that governs the breakup of data messages into packets to be sent via IP (Internet Protocol), 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. Tributary protection switching, a function provided by the equipment, is intended to protect N tributary processing boards through a standby tributary processing board. See Two Rate Three Color Marker See Time To Live Tributary Unit 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.
TransmissionControl Protocol
Tributary Protection Switch trTCM TTL TU Tunnel
Two Rate Three Color The trTCM meters an IP packet stream and marks its packets based on two rates, Peak Marker 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 doesn't exceed the CIR.
B.6 U-Z
U
UAS UBR UDP underfloor cabling UNI Unicast Unspecified Bit Rate Unavailable Second See Unspecified Bit Rate See User Datagram Protocol The cables connected cabinets and other devices are routed underfloor. See User Network Interface The process of sending data from a source to a single recipient. No commitment to transmission. No feedback to congestion. This type of service is ideal for the transmission of IP datagrams. In case of congestion, UBR cells are discarded, and no feedback or request for slowing down the data rate is delivered to the sender. The subrack close to the top of the cabinet when a cabinet contains several subracks. Uninterruptible Power Supply Cables or fibres connect the cabinet with other equipment from the top of the cabinet.
Upper subrack UPS upward cabling
B-30
Issue 05 (2010-10-30)
B Glossary
User Datagram Protocol
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 datagrams. UDP provides application programs with the unreliable connectionless packet delivery service. Thus, UDP messages can be lost, duplicated, delayed, or delivered out of order.UDP is used to try to transmit the data packet, that is, the destination device does not actively confirm whether the correct data packet is received.
User Network Interface A type of ATM Forum specification that defines an interoperability standard for the interface between ATM-based products (a router or an ATM switch) located in a private network and the ATM switches located within the public carrier networks. Also used to describe similar connections in Frame Relay networks.
V
V-NNI V-UNI Variable Bit Rate See virtual network-network interface See Virtual User-Network Interface 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. See Variable Bit Rate See Virtual Channel Virtual Container -12 Virtual Container -3 Virtual Container -4 Virtual Channel Connection See Virtual Chanel Connection See virtual concatenation group See Virtual Channel Identifier Virtual Channel Connection. The VC logical trail that carries data between two end points in an ATM network. A logical grouping of multiple virtual channel connections into one virtual connection. Any logical connection in the ATM network. A VC is the basic unit of switching in the ATM network uniquely identified by a virtual path identifier (VPI)/virtual channel identifier (VCI) value. It is the channel on which ATM cells are transmitted by the sw virtual channel identifier. A 16-bit field in the header of an ATM cell. The VCI, together with the VPI, is used to identify the next destination of a cell as it passes through a series of ATM switches on its way to its destination. A group of co-located member trail termination functions that are connected to the same virtual concatenation link A point-to-point, layer-2 channel that behaves like a leased line by transparently transporting different protocols with a guaranteed throughput.
VBR VC VC-12 VC-3 VC-4 VCC VCC,VPL VCG VCI Virtual Chanel Connection Virtual Channel
Virtual Channel Identifier virtual concatenation group Virtual Leased Line
Issue 05 (2010-10-30)
B-31
B Glossary
Virtual Local Area Network virtual networknetwork interface
A logical grouping of two or more nodes which are not necessarily on the same physical network segment but which share the same IP network number. This is often associated with switched Ethernet. A virtual network-network interface (V-NNI) is a network-side interface.
Virtual Path Identifier The field in the ATM (Asynchronous Transfer Mode) cell header that identifies to which VP (Virtual Path) the cell belongs. Virtual Private LAN Service Virtual Private Network Virtual Private Wire Service Virtual Routing and Forwarding 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. The extension of a private network that encompasses encapsulated, encrypted, and authenticated links across shared or public networks. VPN connections can provide remote access and routed connections to private networks over the Internet. A technology that bears Layer 2 services. VPWS emulates services such as ATM, FR, Ethernet, low-speed TDM circuit, and SONET/SDH in a PSN. A technology included in IP (Internet Protocol) network routers that allows multiple instances of a routing table to exist in a router and work simultaneously.
Virtual Switch Instance An instance through which the physical access links of VPLS can be mapped to the virtual links. Each VSI provides independent VPLS service. VSI has Ethernet bridge function and can terminate PW. Virtual User-Network Interface VLAN VLL Voice over IP virtual user-network interface. A virtual user-network interface, works as an action point to perform service claissification and traffic control in HQoS. See Virtual Local Area Network See Virtual Leased Line 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). See Voice over IP See Virtual Path Identifier See Virtual Private LAN Service See Virtual Private Network See Virtual Private Wire Service See Virtual Routing and Forwarding See Virtual Switch Instance
VoIP VPI VPLS VPN VPWS VRF VSI
W
Wait to Restore Time A period of time that must elapse before a - from a fault recovered - trail/connection can be used again to transport the normal traffic signal and/or to select the normal traffic signal from. See Wide Area Network
WAN
B-32
Issue 05 (2010-10-30)
B Glossary
Web LCT
The local maintenance terminal of a transport network, which is located on the NE management layer of the transport network
Weighted Fair Queuing Weighted Fair Queuing (WFQ) is 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 Detection WFQ Wide Area Network A packet loss algorithm used for congestion avoidance. It can prevent the global TCP synchronization caused by traditional tail-drop. WRED is favorable for the high-priority packet when calculating the packet loss ratio. See Weighted Fair Queuing 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. A tool for fiber routing, which acts as the corrugated pipe. Wire speed refers to the maximum packet forwarding capacity on a cable. The value of wire speed equals the maximum transmission rate capable on a given type of media. Wholesale Managed Services See Weighted Random Early Detection Weighted Round Robin See Wait to Restore Time
Winding pipe wire speed WMS WRED WRR WTR
X
XPD XPIC Cross-Polarization Discrimination See cross polarization interference cancellation
Issue 05 (2010-10-30)
B-33

RTN 620 Feature Description (V100R005C00 - 05)

Hochgeladen von

Dokumentinformationen

Originalbeschreibung:

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

RTN 620 Feature Description (V100R005C00 - 05)

Hochgeladen von

Copyright:

Verfügbare Formate

OptiX RTN 620 Radio Transmission System V100R005C00

HUAWEI TECHNOLOGIES CO., LTD.

Trademarks and Permissions

Huawei Technologies Co., Ltd.

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

OptiX RTN 620 Radio Transmission System Feature Description

About This Document

About This Document

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

About This Document

OptiX RTN 620 Radio Transmission System Feature Description

Updates in Issue 05 (2010-10-30) Based on Product Version V100R005C00

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

OptiX RTN 620 Radio Transmission System Feature Description

About This Document

Updates in Issue 04 (2010-08-20) Based on Product Version V100R005C00

Updates in Issue 03 (2010-05-30) Based on Product Version V100R005C00

Updates in Issue 02 (2010-03-30) Based on Product Version V100R005C00

23.9.1 Networking Diagram 24.7 Planning Guidelines

24.8 Configuration Procedure

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

About This Document

OptiX RTN 620 Radio Transmission System Feature Description

Update 25.6.2 Point-to-Multipoint Service

Updates in Issue 01 (2009-12-30) Based on Product Version V100R005C00

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

OptiX RTN 620 Radio Transmission System Feature Description

3 IP over DCC Solution................................................................................................................3-1

OptiX RTN 620 Radio Transmission System Feature Description

4 OSI over DCC Solution.............................................................................................................4-1

5 DCC Transparent Transmission Solution.............................................................................5-1

OptiX RTN 620 Radio Transmission System Feature Description

6 DCC Transparent Transmission Through the External Clock Interface Solution........6-1

10 Cross-Polarization Interference Cancellation...................................................................10-1

OptiX RTN 620 Radio Transmission System Feature Description

12 Automatic Transmit Power Control...................................................................................12-1

OptiX RTN 620 Radio Transmission System Feature Description

14 Subnetwork Connection Protection................................................................................... 14-1

OptiX RTN 620 Radio Transmission System Feature Description

16 Two-Fiber Bidirectional Ring MSP....................................................................................16-1

OptiX RTN 620 Radio Transmission System Feature Description

17 Ethernet over SDH/PDH.......................................................................................................17-1

OptiX RTN 620 Radio Transmission System Feature Description

20 Layer 2 Switching................................................................................................................... 20-1

21 Ethernet Ring Protection Switching...................................................................................21-1

24 Link Aggregation Group......................................................................................................24-1

OptiX RTN 620 Radio Transmission System Feature Description

25 Link State Pass Through.......................................................................................................25-1

OptiX RTN 620 Radio Transmission System Feature Description

OptiX RTN 620 Radio Transmission System Feature Description

OptiX RTN 620 Radio Transmission System Feature Description

OptiX RTN 620 Radio Transmission System Feature Description

OptiX RTN 620 Radio Transmission System Feature Description

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

OptiX RTN 620 Radio Transmission System Feature Description

OptiX RTN 620 Radio Transmission System Feature Description

OptiX RTN 620 Radio Transmission System Feature Description

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

OptiX RTN 620 Radio Transmission System Feature Description

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

OptiX RTN 620 Radio Transmission System Feature Description

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.