RTN 980 Feature Description (U2000) - (V100R003C00 - 02)

OptiX RTN 980 Radio Transmission System V100R003C00
Feature Description (U2000)

Issue Date 02 2011-01-20
HUAWEI TECHNOLOGIES CO., LTD.
Copyright Huawei Technologies Co., Ltd. 2011. 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 02 (2011-01-20)
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.
OptiX RTN 980 Radio Transmission System Feature Description (U2000)
About This Document
About This Document

Related Versions
The following table lists the product versions related to this document. Product Name OptiX RTN 980 iManager U2000 Version V100R003C00 V100R003C00
Intended Audience
This document describes the main features of the OptiX RTN 980 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 02 (2011-01-20)
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.
Update History
Updates between document issues are cumulative. Therefore, the latest document issue contains all updates made in previous issues.
Updates in Issue 02 (2011-01-20) Based on Product Version V100R003C00

This document is the second issue for the V100R003C00 product version. Compared with the first release, the updated contents are as follows: Update Location 1.3.2.2 OSPF Protocol 1.3.2.3 Proxy ARP Description Added the introduction to the OSPF protocol in the IP over DCC solution. Added the introduction to the proxy ARP in the IP over DCC solution.
iv
Issue 02 (2011-01-20)
About This Document
Updates in Issue 01 (2010-12-30) Based on Product Version V100R003C00

This document is the first issue for the V100R003C00 product version.
Issue 02 (2011-01-20)
Contents
Contents
About This Document...................................................................................................................iii 1 DCN Features..............................................................................................................................1-1
1.1 Introduction to the DCN..................................................................................................................................1-3 1.1.1 Constitution of the DCN........................................................................................................................1-3 1.1.2 Huawei DCN Solution...........................................................................................................................1-5 1.1.3 Protocol Converter Solution...................................................................................................................1-7 1.2 HWECC Solution..........................................................................................................................................1-15 1.2.1 Introduction..........................................................................................................................................1-16 1.2.2 Basic Concepts.....................................................................................................................................1-17 1.2.2.1 HWECC Protocol Stack....................................................................................................................1-17 1.2.2.2 Extended ECC...................................................................................................................................1-20 1.2.3 Specifications.......................................................................................................................................1-23 1.2.4 Reference Standards and Protocols......................................................................................................1-24 1.2.5 Availability...........................................................................................................................................1-24 1.2.6 Principles..............................................................................................................................................1-25 1.2.6.1 Establishing ECC Routes..................................................................................................................1-25 1.2.6.2 Packet Transfer..................................................................................................................................1-27 1.2.6.3 Extended ECC...................................................................................................................................1-28 1.2.7 Planning Guidelines.............................................................................................................................1-29 1.2.8 Configuration Procedure......................................................................................................................1-30 1.2.9 Configuration Example........................................................................................................................1-32 1.2.9.1 Networking Diagram.........................................................................................................................1-33 1.2.9.2 Service Planning................................................................................................................................1-33 1.2.9.3 Configuration Process.......................................................................................................................1-34 1.2.10 Task Collection..................................................................................................................................1-37 1.2.11 Relevant Alarms and Events..............................................................................................................1-38 1.2.12 FAQs..................................................................................................................................................1-38 1.3 IP over DCC Solution...................................................................................................................................1-39 1.3.1 Introduction..........................................................................................................................................1-40 1.3.2 Basic Concepts.....................................................................................................................................1-41 1.3.2.1 IP over DCC Protocol Stack..............................................................................................................1-41 1.3.2.2 OSPF Protocol...................................................................................................................................1-43 1.3.2.3 Proxy ARP.........................................................................................................................................1-47 Issue 02 (2011-01-20) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. vii
Contents
OptiX RTN 980 Radio Transmission System Feature Description (U2000) 1.3.2.4 NMS Access Modes..........................................................................................................................1-49 1.3.3 Specifications.......................................................................................................................................1-49 1.3.4 Reference Standards and Protocols......................................................................................................1-51 1.3.5 Availability...........................................................................................................................................1-51 1.3.6 Principles..............................................................................................................................................1-52 1.3.7 Planning Guidelines.............................................................................................................................1-54 1.3.7.1 General Planning Guidelines.............................................................................................................1-54 1.3.7.2 Planning of NE IP Addresses and Routes in Typical Network Topologies......................................1-55 1.3.7.3 Planning of NE IP Addresses and Routes in Special Network Topologies......................................1-60 1.3.8 Configuration Procedure......................................................................................................................1-62 1.3.9 Configuration Example........................................................................................................................1-64 1.3.9.1 Networking Diagram.........................................................................................................................1-65 1.3.9.2 Service Planning................................................................................................................................1-65 1.3.9.3 Configuration Process.......................................................................................................................1-66 1.3.10 Task Collection..................................................................................................................................1-69 1.3.11 Relevant Alarms and Events..............................................................................................................1-70 1.3.12 FAQs..................................................................................................................................................1-70
1.4 OSI over DCC Solution.................................................................................................................................1-71 1.4.1 Introduction..........................................................................................................................................1-72 1.4.2 Basic Concepts.....................................................................................................................................1-73 1.4.2.1 OSI over DCC Protocol Stack...........................................................................................................1-73 1.4.2.2 NMS Access Modes..........................................................................................................................1-77 1.4.3 Specifications.......................................................................................................................................1-78 1.4.4 Reference Standards and Protocols......................................................................................................1-79 1.4.5 Availability...........................................................................................................................................1-80 1.4.6 Principles..............................................................................................................................................1-81 1.4.7 Planning Guidelines.............................................................................................................................1-82 1.4.8 Configuration Procedure......................................................................................................................1-83 1.4.9 Configuration Example........................................................................................................................1-85 1.4.9.1 Networking Diagram.........................................................................................................................1-85 1.4.9.2 Service Planning................................................................................................................................1-86 1.4.9.3 Configuration Process.......................................................................................................................1-87 1.4.10 Task Collection..................................................................................................................................1-89 1.4.11 Relevant Alarms and Events..............................................................................................................1-90 1.4.12 FAQs..................................................................................................................................................1-90 1.5 DCC Bytes Transparent Transmission Solution...........................................................................................1-91 1.5.1 Introduction..........................................................................................................................................1-92 1.5.2 Specifications.......................................................................................................................................1-94 1.5.3 Availability...........................................................................................................................................1-95 1.5.4 Principles..............................................................................................................................................1-95 1.5.5 Planning Guidelines.............................................................................................................................1-96 1.5.6 Configuration Procedure......................................................................................................................1-97 viii Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 02 (2011-01-20)
Contents
1.5.7 Configuration Example........................................................................................................................1-98 1.5.7.1 Networking Diagram.........................................................................................................................1-98 1.5.7.2 Service Planning................................................................................................................................1-99 1.5.7.3 Configuration Process.....................................................................................................................1-100 1.5.8 Task Collection..................................................................................................................................1-102 1.5.9 Relevant Alarms and Events..............................................................................................................1-102 1.5.10 FAQs................................................................................................................................................1-103 1.6 DCC Transmission Through the External Clock Interface Solution...........................................................1-103 1.6.1 Introduction........................................................................................................................................1-104 1.6.2 Specifications.....................................................................................................................................1-106 1.6.3 Availability.........................................................................................................................................1-106 1.6.4 Principles............................................................................................................................................1-107 1.6.5 Planning Guidelines...........................................................................................................................1-108 1.6.6 Configuration Procedure....................................................................................................................1-108 1.6.7 Configuration Example......................................................................................................................1-109 1.6.7.1 Networking Diagram.......................................................................................................................1-109 1.6.7.2 Service Planning..............................................................................................................................1-110 1.6.7.3 Configuration Process.....................................................................................................................1-110 1.6.8 Task Collection..................................................................................................................................1-111 1.6.9 Relevant Alarms and Events..............................................................................................................1-111 1.6.10 FAQs................................................................................................................................................1-112 1.7 Inband DCN Solution..................................................................................................................................1-112 1.7.1 Introduction........................................................................................................................................1-113 1.7.2 Basic Concepts...................................................................................................................................1-114 1.7.2.1 Inband DCN Protocol Stack............................................................................................................1-114 1.7.2.2 NMS Access Modes........................................................................................................................1-116 1.7.2.3 Access Control................................................................................................................................1-117 1.7.3 Specifications.....................................................................................................................................1-118 1.7.4 Availability.........................................................................................................................................1-119 1.7.5 Principles............................................................................................................................................1-120 1.7.6 Planning Guidelines...........................................................................................................................1-122 1.7.7 Configuration Procedure....................................................................................................................1-123 1.7.8 Configuration Example......................................................................................................................1-125 1.7.8.1 Networking Diagram.......................................................................................................................1-125 1.7.8.2 Service Planning..............................................................................................................................1-126 1.7.8.3 Configuration Process.....................................................................................................................1-127 1.7.9 Task Collection..................................................................................................................................1-129 1.7.10 Relevant Alarms and Events............................................................................................................1-129 1.7.11 FAQs................................................................................................................................................1-130
2 Microwave Features...................................................................................................................2-1
2.1 1+1 HSB..........................................................................................................................................................2-3 2.1.1 Introduction............................................................................................................................................2-3 Issue 02 (2011-01-20) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. ix
Contents
OptiX RTN 980 Radio Transmission System Feature Description (U2000) 2.1.2 Basic Concepts.......................................................................................................................................2-4 2.1.2.1 System Configuration..........................................................................................................................2-5 2.1.2.2 Protection Type...................................................................................................................................2-6 2.1.2.3 Switching Conditions..........................................................................................................................2-6 2.1.2.4 Switching Impact...............................................................................................................................2-10 2.1.3 Specifications.......................................................................................................................................2-10 2.1.4 Availability...........................................................................................................................................2-10 2.1.5 Principles..............................................................................................................................................2-11 2.1.5.1 SDH/PDH Microwave.......................................................................................................................2-12 2.1.5.2 Integrated IP radio.............................................................................................................................2-14 2.1.6 Planning Guidelines.............................................................................................................................2-17 2.1.7 Configuration Procedure......................................................................................................................2-17 2.1.8 Configuration Example........................................................................................................................2-19 2.1.8.1 Networking Diagram.........................................................................................................................2-19 2.1.8.2 Service Planning................................................................................................................................2-20 2.1.8.3 Configuration Process.......................................................................................................................2-21 2.1.9 Task Collection....................................................................................................................................2-22 2.1.10 Relevant Alarms and Events..............................................................................................................2-23 2.1.11 FAQs..................................................................................................................................................2-23
2.2 1+1 FD...........................................................................................................................................................2-24 2.2.1 Introduction..........................................................................................................................................2-25 2.2.2 Basic Concepts.....................................................................................................................................2-26 2.2.2.1 System Configuration........................................................................................................................2-26 2.2.2.2 Protection Type.................................................................................................................................2-28 2.2.2.3 Switching Conditions........................................................................................................................2-29 2.2.2.4 Switching Impact...............................................................................................................................2-32 2.2.3 Specifications.......................................................................................................................................2-32 2.2.4 Availability...........................................................................................................................................2-33 2.2.5 Principles..............................................................................................................................................2-34 2.2.5.1 SDH/PDH Microwave.......................................................................................................................2-34 2.2.5.2 Integrated IP radio.............................................................................................................................2-36 2.2.6 Planning Guidelines.............................................................................................................................2-40 2.2.7 Configuration Procedure......................................................................................................................2-41 2.2.8 Configuration Example........................................................................................................................2-42 2.2.8.1 Networking Diagram.........................................................................................................................2-43 2.2.8.2 Service Planning................................................................................................................................2-43 2.2.8.3 Configuration Process.......................................................................................................................2-45 2.2.9 Task Collection....................................................................................................................................2-46 2.2.10 Relevant Alarms and Events..............................................................................................................2-47 2.2.11 FAQs..................................................................................................................................................2-47 2.3 1+1 SD...........................................................................................................................................................2-48 2.3.1 Introduction..........................................................................................................................................2-48 x Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 02 (2011-01-20)
Contents
2.3.2 Basic Concepts.....................................................................................................................................2-49 2.3.2.1 System Configuration........................................................................................................................2-50 2.3.2.2 Protection Type.................................................................................................................................2-51 2.3.2.3 Switching Conditions........................................................................................................................2-52 2.3.2.4 Switching Impact...............................................................................................................................2-56 2.3.3 Specifications.......................................................................................................................................2-56 2.3.4 Availability...........................................................................................................................................2-57 2.3.5 Principles..............................................................................................................................................2-58 2.3.5.1 SDH/PDH Microwave.......................................................................................................................2-58 2.3.5.2 Integrated IP radio.............................................................................................................................2-61 2.3.6 Planning Guidelines.............................................................................................................................2-64 2.3.7 Configuration Procedure......................................................................................................................2-65 2.3.8 Configuration Example........................................................................................................................2-67 2.3.8.1 Networking Diagram.........................................................................................................................2-67 2.3.8.2 Service Planning................................................................................................................................2-68 2.3.8.3 Configuration Process.......................................................................................................................2-69 2.3.9 Task Collection....................................................................................................................................2-71 2.3.10 Relevant Alarms and Events..............................................................................................................2-71 2.3.11 FAQs..................................................................................................................................................2-71 2.4 Cross-Polarization Interference Cancellation................................................................................................2-72 2.4.1 Introduction..........................................................................................................................................2-73 2.4.2 Basic Concepts.....................................................................................................................................2-74 2.4.2.1 CCDP and XPIC................................................................................................................................2-74 2.4.2.2 System Configuration........................................................................................................................2-75 2.4.2.3 XPIC Feature and 1+1 Protection Configuration..............................................................................2-77 2.4.3 Specifications.......................................................................................................................................2-78 2.4.4 Availability...........................................................................................................................................2-80 2.4.5 Principles..............................................................................................................................................2-81 2.4.6 Planning Guidelines.............................................................................................................................2-82 2.4.7 Configuration Procedure......................................................................................................................2-83 2.4.8 Configuration Example........................................................................................................................2-85 2.4.8.1 Networking Diagram.........................................................................................................................2-85 2.4.8.2 Service Planning................................................................................................................................2-87 2.4.8.3 Configuration Process.......................................................................................................................2-91 2.4.9 Task Collection....................................................................................................................................2-93 2.4.10 Relevant Alarms and Events..............................................................................................................2-93 2.4.11 FAQs..................................................................................................................................................2-93 2.5 N+1 Protection..............................................................................................................................................2-94 2.5.1 Introduction..........................................................................................................................................2-95 2.5.2 Basic Concepts.....................................................................................................................................2-96 2.5.2.1 System Configuration (SDH Microwave).........................................................................................2-96 2.5.2.2 System Configuration........................................................................................................................2-97 Issue 02 (2011-01-20) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. xi
Contents
OptiX RTN 980 Radio Transmission System Feature Description (U2000) 2.5.2.3 Protection Mode..............................................................................................................................2-100 2.5.2.4 Switching Condition........................................................................................................................2-100 2.5.2.5 Switching Impact.............................................................................................................................2-103 2.5.3 Specifications.....................................................................................................................................2-104 2.5.4 Reference Standards and Protocols....................................................................................................2-105 2.5.5 Availability.........................................................................................................................................2-105 2.5.6 Principles............................................................................................................................................2-107 2.5.6.1 SDH Microwave..............................................................................................................................2-107 2.5.6.2 Integrated IP radio...........................................................................................................................2-109 2.5.7 Planning Guidelines...........................................................................................................................2-112 2.5.8 Configuration Procedure....................................................................................................................2-113 2.5.9 Configuration Example......................................................................................................................2-114 2.5.9.1 Networking Diagram.......................................................................................................................2-115 2.5.9.2 Service Planning..............................................................................................................................2-116 2.5.9.3 Configuration Process.....................................................................................................................2-118 2.5.10 Task Collection................................................................................................................................2-121 2.5.11 Relevant Alarms and Performance Events.......................................................................................2-121 2.5.12 FAQs................................................................................................................................................2-121
2.6 Automatic Transmit Power Control............................................................................................................2-122 2.6.1 Introduction........................................................................................................................................2-123 2.6.2 Specifications.....................................................................................................................................2-124 2.6.3 Availability.........................................................................................................................................2-125 2.6.4 Principles............................................................................................................................................2-125 2.6.5 Planning Guidelines...........................................................................................................................2-127 2.6.6 Configuration Procedure....................................................................................................................2-127 2.6.7 Configuration Example......................................................................................................................2-128 2.6.7.1 Networking Diagram.......................................................................................................................2-128 2.6.7.2 Service Planning..............................................................................................................................2-128 2.6.7.3 Configuration Process.....................................................................................................................2-129 2.6.8 Task Collection..................................................................................................................................2-130 2.6.9 Relevant Alarms and Events..............................................................................................................2-130 2.6.10 FAQs................................................................................................................................................2-130 2.7 Adaptive Modulation...................................................................................................................................2-131 2.7.1 Introduction........................................................................................................................................2-131 2.7.2 Basic Concepts...................................................................................................................................2-133 2.7.2.1 E1 Service Priority..........................................................................................................................2-133 2.7.2.2 Priorities of Ethernet Services.........................................................................................................2-135 2.7.3 Specifications.....................................................................................................................................2-136 2.7.4 Availability.........................................................................................................................................2-137 2.7.5 Principles............................................................................................................................................2-138 2.7.6 Planning Guidelines...........................................................................................................................2-141 2.7.7 Configuration Procedure....................................................................................................................2-142 xii Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 02 (2011-01-20)
Contents
2.7.8 Configuration Example......................................................................................................................2-143 2.7.8.1 Networking Diagram.......................................................................................................................2-143 2.7.8.2 Service Planning..............................................................................................................................2-144 2.7.8.3 Configuration Process.....................................................................................................................2-144 2.7.9 Task Collection..................................................................................................................................2-146 2.7.10 Relevant Alarms and Events............................................................................................................2-146 2.7.11 FAQs................................................................................................................................................2-147
3 1+1 Protection for the Control, Switching, and Timing Board..........................................3-1

3.1 Introduction.....................................................................................................................................................3-3 3.2 Basic Concepts................................................................................................................................................3-4 3.2.1 Protection Type......................................................................................................................................3-4 3.2.2 Switching Conditions.............................................................................................................................3-4 3.2.3 Switching Impact....................................................................................................................................3-5 3.3 Specifications..................................................................................................................................................3-5 3.4 Availability......................................................................................................................................................3-6 3.5 Principles.........................................................................................................................................................3-6 3.6 Planning Principles........................................................................................................................................3-12 3.7 Configuration Procedure...............................................................................................................................3-12 3.8 Task Collection.............................................................................................................................................3-12 3.9 Relevant Alarms and Events.........................................................................................................................3-12 3.10 FAQs...........................................................................................................................................................3-13
4 SDH Protection Features...........................................................................................................4-1

4.1 Subnetwork Connection Protection.................................................................................................................4-2 4.1.1 Introduction............................................................................................................................................4-2 4.1.2 Basic Concepts.......................................................................................................................................4-3 4.1.2.1 Protection Type...................................................................................................................................4-4 4.1.2.2 SNCP Service Pair..............................................................................................................................4-4 4.1.2.3 Hold-Off Time.....................................................................................................................................4-5 4.1.2.4 Switching Conditions..........................................................................................................................4-8 4.1.2.5 Switching Impact...............................................................................................................................4-15 4.1.3 Specifications.......................................................................................................................................4-15 4.1.4 Reference Standards and Protocols......................................................................................................4-16 4.1.5 Availability...........................................................................................................................................4-16 4.1.6 Principles..............................................................................................................................................4-17 4.1.7 Planning Guidelines.............................................................................................................................4-18 4.1.8 Configuration Procedure......................................................................................................................4-18 4.1.9 Configuration Example........................................................................................................................4-19 4.1.9.1 Networking Diagram.........................................................................................................................4-19 4.1.9.2 Service Planning................................................................................................................................4-20 4.1.9.3 Configuration Process (on a Per-NE Basis)......................................................................................4-21 4.1.10 Task Collection..................................................................................................................................4-24 4.1.11 Relevant Alarms and Events..............................................................................................................4-24 Issue 02 (2011-01-20) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. xiii
Contents
OptiX RTN 980 Radio Transmission System Feature Description (U2000) 4.1.12 FAQs.................................................................................................................................................. 4-25
4.2 Linear Multiplex Section Protection.............................................................................................................4-26 4.2.1 Introduction..........................................................................................................................................4-27 4.2.2 Basic Concepts.....................................................................................................................................4-28 4.2.2.1 Protection Type.................................................................................................................................4-29 4.2.2.2 Meanings of K Bytes.........................................................................................................................4-30 4.2.2.3 Switching Conditions........................................................................................................................4-31 4.2.2.4 Switching Impact...............................................................................................................................4-34 4.2.3 Specifications.......................................................................................................................................4-34 4.2.4 Reference Standards and Protocols......................................................................................................4-35 4.2.5 Availability...........................................................................................................................................4-35 4.2.6 Principles..............................................................................................................................................4-35 4.2.6.1 1+1 Linear MSP................................................................................................................................4-36 4.2.6.2 1:N Linear MSP................................................................................................................................ 4-37 4.2.7 Planning Guidelines............................................................................................................................. 4-38 4.2.8 Configuration Procedure......................................................................................................................4-39 4.2.9 Configuration Example........................................................................................................................4-39 4.2.9.1 Networking Diagram.........................................................................................................................4-40 4.2.9.2 Service Planning................................................................................................................................4-40 4.2.9.3 Configuration Procedure...................................................................................................................4-41 4.2.10 Task Collection.................................................................................................................................. 4-42 4.2.11 Relevant Alarms and Events..............................................................................................................4-42 4.2.12 FAQs.................................................................................................................................................. 4-43 4.3 Two-Fiber Bidirectional Ring MSP..............................................................................................................4-44 4.3.1 Introduction..........................................................................................................................................4-45 4.3.2 Basic Concepts.....................................................................................................................................4-47 4.3.2.1 Protection Type.................................................................................................................................4-47 4.3.2.2 Meanings of Byte K.......................................................................................................................... 4-47 4.3.2.3 Switching Conditions........................................................................................................................4-49 4.3.2.4 Switching Impact...............................................................................................................................4-51 4.3.3 Specifications.......................................................................................................................................4-51 4.3.4 Reference Standards and Protocols......................................................................................................4-52 4.3.5 Availability...........................................................................................................................................4-52 4.3.6 Principles..............................................................................................................................................4-52 4.3.7 Planning Guidelines............................................................................................................................. 4-54 4.3.8 Configuration Procedure......................................................................................................................4-55 4.3.9 Configuration Example........................................................................................................................4-55 4.3.9.1 Networking Diagram.........................................................................................................................4-56 4.3.9.2 Service Planning................................................................................................................................4-56 4.3.9.3 Configuration Process.......................................................................................................................4-57 4.3.10 Task Collection.................................................................................................................................. 4-58 4.3.11 Relevant Alarms and Events..............................................................................................................4-58 xiv Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 02 (2011-01-20)
Contents
4.3.12 FAQs.................................................................................................................................................. 4-58
5 Ethernet Features on the Packet Plane...................................................................................5-1

5.1 What's the Packet Plane...................................................................................................................................5-3 5.2 VLAN..............................................................................................................................................................5-4 5.2.1 Introduction............................................................................................................................................5-5 5.2.2 Basic Concepts.......................................................................................................................................5-6 5.2.2.1 Frame Format......................................................................................................................................5-6 5.2.2.2 TAG Attribute.....................................................................................................................................5-7 5.2.2.3 VLAN-based E-Line Services.............................................................................................................5-8 5.2.2.4 E-LAN Services Based on 802.1q Bridge...........................................................................................5-9 5.2.2.5 VLAN Forwarding Table..................................................................................................................5-10 5.2.3 Specifications.......................................................................................................................................5-11 5.2.4 Reference Standards and Protocols......................................................................................................5-12 5.2.5 Availability...........................................................................................................................................5-12 5.2.6 Principles..............................................................................................................................................5-13 5.2.7 Planning Guidelines.............................................................................................................................5-13 5.2.8 Configuration Procedure......................................................................................................................5-13 5.2.8.1 Configuration Procedure (VLAN-Based E-Line Services)...............................................................5-14 5.2.8.2 Configuration Procedure (IEEE 802.1q Bridge-Based E-LAN Services)........................................5-20 5.2.9 Configuration Example........................................................................................................................5-28 5.2.10 Task Collection..................................................................................................................................5-28 5.2.11 Relevant Alarms and Events..............................................................................................................5-29 5.2.12 FAQs..................................................................................................................................................5-29 5.3 QinQ..............................................................................................................................................................5-29 5.3.1 Introduction..........................................................................................................................................5-30 5.3.2 Basic Concepts.....................................................................................................................................5-31 5.3.2.1 Frame Format....................................................................................................................................5-31 5.3.2.2 QinQ-Based E-Line Services............................................................................................................5-32 5.3.2.3 E-LAN Services Based on 802.1ad Bridge.......................................................................................5-36 5.3.3 Specifications.......................................................................................................................................5-37 5.3.4 Reference Standards and Protocols......................................................................................................5-38 5.3.5 Availability...........................................................................................................................................5-39 5.3.6 Principles..............................................................................................................................................5-39 5.3.7 Planning Guidelines.............................................................................................................................5-41 5.3.8 Configuration Procedure......................................................................................................................5-42 5.3.8.1 Configuration Procedure (QinQ-Based E-Line Services).................................................................5-43 5.3.8.2 Configuration Procedure (IEEE 802.1ad Bridge-Based E-LAN Services).......................................5-49 5.3.9 Configuration Example........................................................................................................................5-57 5.3.10 Task Collection..................................................................................................................................5-57 5.3.11 Relevant Alarms and Events..............................................................................................................5-57 5.3.12 FAQs..................................................................................................................................................5-58 5.4 Layer 2 Switching.........................................................................................................................................5-58 Issue 02 (2011-01-20) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. xv
Contents
OptiX RTN 980 Radio Transmission System Feature Description (U2000) 5.4.1 Introduction..........................................................................................................................................5-59 5.4.2 Basic Concepts.....................................................................................................................................5-60 5.4.2.1 Bridge................................................................................................................................................5-61 5.4.2.2 E-LAN Services Based on the 802.1d Bridge...................................................................................5-63 5.4.2.3 E-LAN Services Based on 802.1q Bridge.........................................................................................5-64 5.4.2.4 E-LAN Services Based on 802.1ad Bridge.......................................................................................5-65 5.4.2.5 Split Horizon Group..........................................................................................................................5-67 5.4.2.6 Managing a MAC Address Table......................................................................................................5-68 5.4.3 Specifications.......................................................................................................................................5-69 5.4.4 Reference Standards and Protocols......................................................................................................5-69 5.4.5 Availability...........................................................................................................................................5-69 5.4.6 Principles..............................................................................................................................................5-70 5.4.7 Planning Guidelines............................................................................................................................. 5-71 5.4.8 Configuration Procedure......................................................................................................................5-71 5.4.8.1 Configuration Procedure (IEEE 802.1d Bridge-Based E-LAN Services)........................................ 5-72 5.4.8.2 Configuration Procedure (IEEE 802.1q Bridge-Based E-LAN Services)........................................ 5-79 5.4.8.3 Configuration Procedure (IEEE 802.1ad Bridge-Based E-LAN Services).......................................5-87 5.4.9 Configuration Example........................................................................................................................5-95 5.4.10 Task Collection.................................................................................................................................. 5-95 5.4.11 Relevant Alarms and Events..............................................................................................................5-96 5.4.12 FAQs.................................................................................................................................................. 5-96
5.5 Ethernet Ring Protection Switching..............................................................................................................5-96 5.5.1 Introduction..........................................................................................................................................5-97 5.5.2 Basic Concepts.....................................................................................................................................5-98 5.5.2.1 Protection Instance............................................................................................................................5-99 5.5.2.2 Protection Type...............................................................................................................................5-100 5.5.2.3 R-APS Message...............................................................................................................................5-100 5.5.2.4 R-APS Timer...................................................................................................................................5-102 5.5.2.5 Switching Condition........................................................................................................................5-103 5.5.2.6 Switching Impact.............................................................................................................................5-105 5.5.3 Specifications.....................................................................................................................................5-105 5.5.4 Reference Standards and Protocols....................................................................................................5-106 5.5.5 Availability.........................................................................................................................................5-106 5.5.6 Principles............................................................................................................................................5-107 5.5.7 Planning Principles.............................................................................................................................5-110 5.5.8 Configuration Procedure....................................................................................................................5-111 5.5.9 Configuration Example......................................................................................................................5-112 5.5.9.1 Networking Diagram.......................................................................................................................5-112 5.5.9.2 Service Planning..............................................................................................................................5-113 5.5.9.3 Configuration Process.....................................................................................................................5-113 5.5.10 Task Collection................................................................................................................................5-114 5.5.11 Relevant Alarms and Events............................................................................................................5-114 xvi Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 02 (2011-01-20)
Contents
5.5.12 FAQs................................................................................................................................................5-115 5.6 MSTP..........................................................................................................................................................5-115 5.6.1 Introduction........................................................................................................................................5-116 5.6.2 Basic Concepts...................................................................................................................................5-120 5.6.3 Specifications.....................................................................................................................................5-123 5.6.4 Reference Standards and Protocols....................................................................................................5-124 5.6.5 Availability.........................................................................................................................................5-124 5.6.6 Principles............................................................................................................................................5-125 5.6.7 Planning Principles.............................................................................................................................5-128 5.6.8 Configuration Procedure....................................................................................................................5-128 5.6.9 Configuration Example......................................................................................................................5-128 5.6.9.1 Networking Diagram.......................................................................................................................5-129 5.6.9.2 Service Planning..............................................................................................................................5-129 5.6.9.3 Configuration Process.....................................................................................................................5-131 5.6.10 Task Collection................................................................................................................................5-132 5.6.11 Relevant Alarms and Events............................................................................................................5-132 5.6.12 FAQs................................................................................................................................................5-133 5.7 Link Aggregation Group.............................................................................................................................5-133 5.7.1 Introduction........................................................................................................................................5-134 5.7.2 Basic Concepts...................................................................................................................................5-135 5.7.2.1 LAG Types......................................................................................................................................5-135 5.7.2.2 Port Types.......................................................................................................................................5-136 5.7.2.3 Switching Condition........................................................................................................................5-137 5.7.2.4 Switching Impact.............................................................................................................................5-137 5.7.3 Specifications.....................................................................................................................................5-137 5.7.4 Reference Standards and Protocols....................................................................................................5-138 5.7.5 Availability.........................................................................................................................................5-139 5.7.6 Principles............................................................................................................................................5-140 5.7.7 Planning Guidelines...........................................................................................................................5-143 5.7.8 Configuration Procedure....................................................................................................................5-143 5.7.9 Configuration Example......................................................................................................................5-145 5.7.9.1 Networking Diagram.......................................................................................................................5-145 5.7.9.2 Service Planning..............................................................................................................................5-145 5.7.9.3 Configuration Process.....................................................................................................................5-146 5.7.10 Task Collection................................................................................................................................5-147 5.7.11 Relevant Alarms and Events............................................................................................................5-147 5.7.12 FAQs................................................................................................................................................5-147 5.8 Link State Pass Through.............................................................................................................................5-147 5.8.1 Introduction........................................................................................................................................5-148 5.8.2 Basic Concepts...................................................................................................................................5-149 5.8.2.1 Point-to-Point LPT..........................................................................................................................5-149 5.8.2.2 Point-to-Multipoint LPT.................................................................................................................5-151 Issue 02 (2011-01-20) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. xvii
Contents
OptiX RTN 980 Radio Transmission System Feature Description (U2000) 5.8.3 Specifications.....................................................................................................................................5-152 5.8.4 Reference Standards and Protocols....................................................................................................5-153 5.8.5 Availability.........................................................................................................................................5-153 5.8.6 Principles............................................................................................................................................5-154 5.8.6.1 LPT Fault Detection........................................................................................................................5-154 5.8.6.2 Switching Principles of Point-to-Point LPT....................................................................................5-155 5.8.6.3 Switching Principles of Point-to-Multipoint LPT...........................................................................5-157 5.8.7 Configuration Procedure....................................................................................................................5-159 5.8.8 Configuration Example (LPT for Services Traversing an L2 Network)............................................5-161 5.8.8.1 Network Diagram............................................................................................................................5-161 5.8.8.2 Service Planning..............................................................................................................................5-162 5.8.8.3 Configuration Process.....................................................................................................................5-164 5.8.9 Configuration Example (LPT for Services Traversing a PSN)..........................................................5-165 5.8.9.1 Network Diagram............................................................................................................................5-165 5.8.9.2 Service Planning..............................................................................................................................5-166 5.8.9.3 Configuration Process.....................................................................................................................5-167 5.8.10 Task Collection................................................................................................................................5-168 5.8.11 Relevant Alarms and Events............................................................................................................5-168 5.8.12 FAQs................................................................................................................................................5-168
5.9 QoS..............................................................................................................................................................5-169 5.9.1 Introduction........................................................................................................................................5-169 5.9.2 Basic Concepts...................................................................................................................................5-171 5.9.2.1 QoS Requirements...........................................................................................................................5-171 5.9.2.2 DiffServ...........................................................................................................................................5-172 5.9.2.3 Traffic Classification.......................................................................................................................5-179 5.9.2.4 CAR.................................................................................................................................................5-180 5.9.2.5 Traffic Shaping................................................................................................................................5-181 5.9.2.6 Queue Scheduling...........................................................................................................................5-182 5.9.2.7 QoS Model......................................................................................................................................5-185 5.9.3 Specifications.....................................................................................................................................5-192 5.9.4 Reference Standards and Protocols....................................................................................................5-194 5.9.5 Availability.........................................................................................................................................5-195 5.9.6 Principles............................................................................................................................................5-195 5.9.6.1 CAR.................................................................................................................................................5-196 5.9.6.2 Traffic Shaping................................................................................................................................5-197 5.9.7 Configuration Procedure....................................................................................................................5-199 5.9.8 Configuration Example......................................................................................................................5-201 5.9.8.1 Network Diagram............................................................................................................................5-202 5.9.8.2 Service Planning..............................................................................................................................5-202 5.9.8.3 Configuration Process.....................................................................................................................5-204 5.9.9 Task Collection..................................................................................................................................5-206 5.9.10 Relevant Alarms and Events............................................................................................................5-207 xviii Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 02 (2011-01-20)
Contents
5.9.11 FAQs................................................................................................................................................5-207 5.10 ETH-OAM................................................................................................................................................5-207 5.10.1 Introduction......................................................................................................................................5-208 5.10.2 Basic Concepts.................................................................................................................................5-209 5.10.2.1 IEEE 802.1ag OAM Management ...............................................................................................5-209 5.10.2.2 IEEE 802.1ag OAM Operation ....................................................................................................5-211 5.10.2.3 IEEE 802.3ah OAM Operations....................................................................................................5-213 5.10.3 Specifications...................................................................................................................................5-215 5.10.4 Reference Standards and Protocols..................................................................................................5-216 5.10.5 Availability.......................................................................................................................................5-217 5.10.6 Principles..........................................................................................................................................5-218 5.10.6.1 IEEE 802.1ag OAM......................................................................................................................5-218 5.10.6.2 IEEE 802.3ah OAM......................................................................................................................5-222 5.10.7 Planning Guidelines.........................................................................................................................5-230 5.10.8 Configuration Procedure..................................................................................................................5-231 5.10.8.1 802.1ag OAM................................................................................................................................5-231 5.10.8.2 IEEE 802.3ah OAM......................................................................................................................5-235 5.10.9 Configuration Example (802.1ag OAM).........................................................................................5-237 5.10.9.1 Networking Diagram.....................................................................................................................5-237 5.10.9.2 Service Planning............................................................................................................................5-237 5.10.9.3 Configuration Process...................................................................................................................5-240 5.10.10 Configuration Example (802.3ah OAM).......................................................................................5-243 5.10.10.1 Networking Diagram...................................................................................................................5-244 5.10.10.2 Service Planning..........................................................................................................................5-244 5.10.10.3 Configuration Process.................................................................................................................5-245 5.10.11 Task Collection..............................................................................................................................5-246 5.10.11.1 Task Collection(802.1ag OAM)..................................................................................................5-246 5.10.11.2 Task Collection (802.3ah OAM).................................................................................................5-247 5.10.12 Relevant Alarms and Events..........................................................................................................5-247 5.10.13 FAQs..............................................................................................................................................5-248 5.11 Remote Network Monitoring....................................................................................................................5-248 5.11.1 Introduction......................................................................................................................................5-249 5.11.2 Basic Concepts.................................................................................................................................5-249 5.11.2.1 SNMP............................................................................................................................................5-250 5.11.2.2 RMON Management Groups........................................................................................................5-250 5.11.2.3 List of RMON Alarm Entries........................................................................................................5-252 5.11.2.4 Packet-Plane RMON Performance Entry List..............................................................................5-253 5.11.3 Specifications...................................................................................................................................5-261 5.11.4 Reference Standards and Protocols..................................................................................................5-263 5.11.5 Availability.......................................................................................................................................5-263 5.11.6 Principles..........................................................................................................................................5-264 5.11.7 Planning Guidelines.........................................................................................................................5-265 Issue 02 (2011-01-20) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. xix
Contents
OptiX RTN 980 Radio Transmission System Feature Description (U2000) 5.11.8 Configuration Procedure..................................................................................................................5-265 5.11.9 Configuration Example....................................................................................................................5-266 5.11.9.1 Networking Diagram.....................................................................................................................5-267 5.11.9.2 Troubleshooting Analysis.............................................................................................................5-267 5.11.9.3 Troubleshooting Flow...................................................................................................................5-268 5.11.10 Task Collection..............................................................................................................................5-268 5.11.11 Relevant Alarms and Events..........................................................................................................5-269 5.11.12 FAQs..............................................................................................................................................5-269
6 Packet Features...........................................................................................................................6-1
6.1 MPLS Basics...................................................................................................................................................6-3 6.1.1 Introduction............................................................................................................................................6-3 6.1.2 Basic Concepts.......................................................................................................................................6-4 6.1.2.1 MPLS Network Architecture..............................................................................................................6-5 6.1.2.2 LSP......................................................................................................................................................6-5 6.1.2.3 Bearer Mode for MPLS Packets..........................................................................................................6-7 6.1.2.4 MPLS Label........................................................................................................................................6-9 6.1.3 Specifications.......................................................................................................................................6-10 6.1.4 Reference Standards and Protocols......................................................................................................6-11 6.1.5 Availability...........................................................................................................................................6-11 6.1.6 Principles..............................................................................................................................................6-12 6.1.7 Configuration Procedure......................................................................................................................6-14 6.1.7.1 Configuration Procedure (on a Per-NE Basis)..................................................................................6-15 6.1.8 Configuration Example........................................................................................................................6-20 6.1.9 Task Collection....................................................................................................................................6-20 6.1.10 Relevant Alarms and Events..............................................................................................................6-21 6.1.11 FAQs..................................................................................................................................................6-21 6.2 MPLS OAM..................................................................................................................................................6-21 6.2.1 Introduction..........................................................................................................................................6-22 6.2.2 Basic Concepts.....................................................................................................................................6-22 6.2.2.1 CV/FFD.............................................................................................................................................6-23 6.2.2.2 LSP Defect Type...............................................................................................................................6-25 6.2.2.3 BDI....................................................................................................................................................6-27 6.2.2.4 FDI....................................................................................................................................................6-28 6.2.3 Specifications.......................................................................................................................................6-30 6.2.4 Reference Standards and Protocols......................................................................................................6-31 6.2.5 Availability...........................................................................................................................................6-31 6.2.6 Principles..............................................................................................................................................6-32 6.2.7 Configuration Procedure......................................................................................................................6-33 6.2.8 Configuration Example........................................................................................................................6-33 6.2.8.1 Network Diagram..............................................................................................................................6-33 6.2.8.2 Service Planning................................................................................................................................6-34 6.2.8.3 Configuration Process.......................................................................................................................6-34 xx Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 02 (2011-01-20)
Contents
6.2.9 Task Collection.................................................................................................................................... 6-35 6.2.10 Relevant Alarms and Events..............................................................................................................6-35 6.2.11 FAQs.................................................................................................................................................. 6-36 6.3 LSP Ping/Traceroute.....................................................................................................................................6-37 6.3.1 Introduction..........................................................................................................................................6-38 6.3.2 Specifications.......................................................................................................................................6-39 6.3.3 Reference Standards and Protocols......................................................................................................6-41 6.3.4 Availability...........................................................................................................................................6-41 6.3.5 Principles..............................................................................................................................................6-42 6.3.5.1 LSP Ping............................................................................................................................................6-42 6.3.5.2 LSP Traceroute..................................................................................................................................6-44 6.3.6 Configuration Procedure......................................................................................................................6-45 6.3.7 Configuration Example........................................................................................................................6-46 6.3.7.1 Network Diagram..............................................................................................................................6-46 6.3.7.2 Service Planning................................................................................................................................6-47 6.3.7.3 Configuration Process.......................................................................................................................6-47 6.3.8 Task Collection.................................................................................................................................... 6-48 6.3.9 Relevant Alarms and Events................................................................................................................6-48 6.3.10 FAQs.................................................................................................................................................. 6-48 6.4 MPLS APS....................................................................................................................................................6-49 6.4.1 Introduction..........................................................................................................................................6-50 6.4.2 Basic Concepts.....................................................................................................................................6-51 6.4.2.1 Protection Type.................................................................................................................................6-52 6.4.2.2 Switching Conditions........................................................................................................................6-53 6.4.2.3 Switching Impact...............................................................................................................................6-55 6.4.3 Specifications.......................................................................................................................................6-55 6.4.4 Reference Standards and Protocols......................................................................................................6-55 6.4.5 Availability...........................................................................................................................................6-55 6.4.6 Principles..............................................................................................................................................6-56 6.4.6.1 Single-Ended Switching....................................................................................................................6-57 6.4.6.2 Dual-Ended Switching...................................................................................................................... 6-58 6.4.7 Configuration Procedure......................................................................................................................6-59 6.4.8 Configuration Example........................................................................................................................6-61 6.4.8.1 Network Diagram..............................................................................................................................6-61 6.4.8.2 Service Planning................................................................................................................................6-62 6.4.8.3 Configuration Process.......................................................................................................................6-62 6.4.9 Task Collection.................................................................................................................................... 6-64 6.4.10 Relevant Alarms and Events..............................................................................................................6-64 6.4.11 FAQs.................................................................................................................................................. 6-65 6.5 PWE3 Basics.................................................................................................................................................6-65 6.5.1 Introduction..........................................................................................................................................6-66 6.5.2 Basic Concepts.....................................................................................................................................6-66 Issue 02 (2011-01-20) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. xxi
Contents
OptiX RTN 980 Radio Transmission System Feature Description (U2000) 6.5.2.1 PWE3 Network Reference Model.....................................................................................................6-67 6.5.2.2 PWE3 Protocol Reference Model.....................................................................................................6-68 6.5.2.3 PWE3 Encapsulation Format............................................................................................................6-69 6.5.2.4 MS-PW..............................................................................................................................................6-71 6.5.2.5 VCCV................................................................................................................................................6-73 6.5.3 Specifications.......................................................................................................................................6-74 6.5.4 Reference Standards and Protocols......................................................................................................6-75 6.5.5 Availability...........................................................................................................................................6-75 6.5.6 Principles..............................................................................................................................................6-76 6.5.6.1 Packet Forwarding Process of SS-PW..............................................................................................6-76 6.5.6.2 Packet Forwarding Process of MS-PW.............................................................................................6-77 6.5.7 Configuration Procedure......................................................................................................................6-78 6.5.8 Configuration Example........................................................................................................................6-78 6.5.9 Task Collection....................................................................................................................................6-79 6.5.10 Relevant Alarms and Events..............................................................................................................6-79 6.5.11 FAQs..................................................................................................................................................6-79
6.6 TDM PWE3...................................................................................................................................................6-79 6.6.1 Introduction..........................................................................................................................................6-80 6.6.2 Basic Concepts.....................................................................................................................................6-81 6.6.2.1 E1 Frame Format...............................................................................................................................6-81 6.6.2.2 SAToP...............................................................................................................................................6-82 6.6.2.3 CESoPSN..........................................................................................................................................6-84 6.6.2.4 Data Jitter Buffer...............................................................................................................................6-86 6.6.2.5 CES Alarm Transparent Transmission..............................................................................................6-87 6.6.2.6 Clock Recovery Schemes of TDM PWE3........................................................................................6-89 6.6.2.7 QoS of TDM PWE3..........................................................................................................................6-90 6.6.3 Specifications.......................................................................................................................................6-90 6.6.4 Reference Standards and Protocols......................................................................................................6-91 6.6.5 Availability...........................................................................................................................................6-92 6.6.6 Principles..............................................................................................................................................6-92 6.6.7 Configuration Procedure......................................................................................................................6-93 6.6.8 Configuration Example........................................................................................................................6-96 6.6.9 Task Collection....................................................................................................................................6-97 6.6.10 Relevant Alarms and Events..............................................................................................................6-97 6.6.11 FAQs..................................................................................................................................................6-98 6.7 ATM PWE3...................................................................................................................................................6-99 6.7.1 Introduction........................................................................................................................................6-100 6.7.2 Basic Concepts...................................................................................................................................6-101 6.7.2.1 ATM N-to-One Cell Encapsulation................................................................................................6-102 6.7.2.2 ATM One-to-One Cell Encapsulation.............................................................................................6-103 6.7.2.3 Number of ATM Cells Encapsulated in PWE3 Packets.................................................................6-105 6.7.2.4 QoS of ATM PWE3........................................................................................................................6-106 xxii Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 02 (2011-01-20)
Contents
6.7.3 Specifications.....................................................................................................................................6-106 6.7.4 Reference Standards and Protocols....................................................................................................6-108 6.7.5 Availability.........................................................................................................................................6-108 6.7.6 Principles............................................................................................................................................6-109 6.7.7 Configuration Procedure....................................................................................................................6-110 6.7.8 Configuration Example......................................................................................................................6-117 6.7.9 Task Collection..................................................................................................................................6-117 6.7.10 Relevant Alarms and Events............................................................................................................6-117 6.7.11 FAQs................................................................................................................................................6-118 6.8 ETH PWE3..................................................................................................................................................6-118 6.8.1 Introduction........................................................................................................................................6-119 6.8.2 Basic Concepts...................................................................................................................................6-120 6.8.2.1 Format of an ETH PWE3 Packet....................................................................................................6-120 6.8.2.2 Service-Delimiting Tag and PW Encapsulation Mode...................................................................6-121 6.8.2.3 QoS of ETH PWE3.........................................................................................................................6-123 6.8.2.4 E-Line Services Carried on PWs.....................................................................................................6-124 6.8.3 Specifications.....................................................................................................................................6-127 6.8.4 Reference Standards and Protocols....................................................................................................6-127 6.8.5 Availability.........................................................................................................................................6-128 6.8.6 Principles............................................................................................................................................6-128 6.8.7 Configuration Procedure....................................................................................................................6-129 6.8.8 Configuration Example......................................................................................................................6-137 6.8.9 Task Collection..................................................................................................................................6-137 6.8.10 Relevant Alarms and Events............................................................................................................6-137 6.8.11 FAQs................................................................................................................................................6-138 6.9 PW OAM.....................................................................................................................................................6-138 6.9.1 Introduction........................................................................................................................................6-139 6.9.2 Basic Concepts...................................................................................................................................6-140 6.9.2.1 PW OAM Packet.............................................................................................................................6-140 6.9.2.2 PW Defect Type..............................................................................................................................6-141 6.9.3 Specifications.....................................................................................................................................6-142 6.9.4 Reference Standards and Protocols....................................................................................................6-143 6.9.5 Availability.........................................................................................................................................6-143 6.9.6 Principles............................................................................................................................................6-144 6.9.7 Configuration Procedure....................................................................................................................6-145 6.9.8 Configuration Example......................................................................................................................6-146 6.9.8.1 Network Diagram............................................................................................................................6-146 6.9.8.2 Service Planning..............................................................................................................................6-146 6.9.8.3 Configuration Process.....................................................................................................................6-146 6.9.9 Task Collection..................................................................................................................................6-147 6.9.10 Relevant Alarms and Events............................................................................................................6-147 6.9.11 FAQs................................................................................................................................................6-148 Issue 02 (2011-01-20) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. xxiii
Contents
6.10 PW Ping/Traceroute..................................................................................................................................6-149 6.10.1 Introduction......................................................................................................................................6-150 6.10.2 Specifications...................................................................................................................................6-151 6.10.3 Reference Standards and Protocols..................................................................................................6-153 6.10.4 Availability.......................................................................................................................................6-153 6.10.5 Principles..........................................................................................................................................6-154 6.10.5.1 PW Ping.........................................................................................................................................6-154 6.10.5.2 PW Traceroute...............................................................................................................................6-156 6.10.6 Configuration Procedure..................................................................................................................6-157 6.10.7 Configuration Example....................................................................................................................6-158 6.10.7.1 Network Diagram..........................................................................................................................6-159 6.10.7.2 Service Planning............................................................................................................................6-159 6.10.7.3 Configuration Process...................................................................................................................6-159 6.10.8 Task Collection................................................................................................................................ 6-160 6.10.9 Relevant Alarms and Events............................................................................................................6-160 6.10.10 FAQs.............................................................................................................................................. 6-160 6.11 PW APS.....................................................................................................................................................6-161 6.11.1 Introduction......................................................................................................................................6-161 6.11.2 Basic Concepts.................................................................................................................................6-164 6.11.2.1 Protection Type.............................................................................................................................6-164 6.11.2.2 Switching Conditions....................................................................................................................6-165 6.11.2.3 Switching Impact...........................................................................................................................6-167 6.11.2.4 PW APS Binding...........................................................................................................................6-168 6.11.3 Specifications...................................................................................................................................6-169 6.11.4 Reference Standards and Protocols..................................................................................................6-170 6.11.5 Availability.......................................................................................................................................6-170 6.11.6 Principles..........................................................................................................................................6-171 6.11.6.1 Single-Ended Switching................................................................................................................6-171 6.11.6.2 Dual-Ended Switching.................................................................................................................. 6-172 6.11.7 Configuration Procedure..................................................................................................................6-174 6.11.8 Configuration Example....................................................................................................................6-175 6.11.8.1 Network Diagram..........................................................................................................................6-175 6.11.8.2 Service Planning............................................................................................................................6-176 6.11.8.3 Configuration Process...................................................................................................................6-177 6.11.9 Task Collection................................................................................................................................ 6-178 6.11.10 Relevant Alarms and Events..........................................................................................................6-179 6.11.11 FAQs.............................................................................................................................................. 6-179 6.12 ATM Basics...............................................................................................................................................6-180 6.12.1 Introduction......................................................................................................................................6-180 6.12.2 Basic Concept...................................................................................................................................6-181 6.12.2.1 Architecture and Interfaces of an ATM Network......................................................................... 6-182 6.12.2.2 ATM Link..................................................................................................................................... 6-182 xxiv Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 02 (2011-01-20)
Contents
6.12.2.3 ATM Connection...........................................................................................................................6-183 6.12.2.4 ATM Switching.............................................................................................................................6-185 6.12.2.5 ATM Cell Format..........................................................................................................................6-186 6.12.2.6 ATM Protocol Reference Model...................................................................................................6-188 6.12.3 Specifications...................................................................................................................................6-189 6.12.4 Reference Standards and Protocols..................................................................................................6-190 6.12.5 Availability.......................................................................................................................................6-191 6.12.6 Principles..........................................................................................................................................6-191 6.12.7 Relevant Alarms and Events............................................................................................................6-192 6.12.8 FAQs................................................................................................................................................6-192 6.13 IMA...........................................................................................................................................................6-192 6.13.1 Introduction......................................................................................................................................6-193 6.13.2 Basic Concepts.................................................................................................................................6-194 6.13.2.1 IMA Protocol Reference Model....................................................................................................6-194 6.13.2.2 IMA OAM Cells............................................................................................................................6-195 6.13.2.3 IMA Frame Format.......................................................................................................................6-198 6.13.2.4 IMA Timing..................................................................................................................................6-200 6.13.3 Specifications...................................................................................................................................6-201 6.13.4 Reference Standards and Protocols..................................................................................................6-202 6.13.5 Availability.......................................................................................................................................6-202 6.13.6 Principles..........................................................................................................................................6-203 6.13.7 Configuration Procedure..................................................................................................................6-203 6.13.8 Configuration Example....................................................................................................................6-204 6.13.8.1 Network Diagram..........................................................................................................................6-205 6.13.8.2 Service Planning............................................................................................................................6-205 6.13.8.3 Configuration Process...................................................................................................................6-206 6.13.9 Task Collection................................................................................................................................6-207 6.13.10 Relevant Alarms and Events..........................................................................................................6-207 6.13.11 FAQs..............................................................................................................................................6-208 6.14 ATM OAM................................................................................................................................................6-208 6.14.1 Introduction......................................................................................................................................6-209 6.14.2 Basic Concepts.................................................................................................................................6-209 6.14.2.1 ATM OAM Levels........................................................................................................................6-210 6.14.2.2 Segment and End Attributes and Directions of CPs.....................................................................6-210 6.14.2.3 ATM OAM Functions...................................................................................................................6-212 6.14.3 Specifications...................................................................................................................................6-215 6.14.4 Reference Standards and Protocols..................................................................................................6-215 6.14.5 Availability.......................................................................................................................................6-215 6.14.6 Principles..........................................................................................................................................6-216 6.14.6.1 AIS/RDI........................................................................................................................................6-216 6.14.6.2 CC..................................................................................................................................................6-218 6.14.6.3 LB..................................................................................................................................................6-219 Issue 02 (2011-01-20) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. xxv
Contents
OptiX RTN 980 Radio Transmission System Feature Description (U2000) 6.14.7 Configuration Procedure..................................................................................................................6-220 6.14.8 Configuration Example....................................................................................................................6-222 6.14.8.1 Network Diagram..........................................................................................................................6-222 6.14.8.2 Service Planning............................................................................................................................6-223 6.14.8.3 Configuration Process...................................................................................................................6-223 6.14.9 Task Collection................................................................................................................................ 6-224 6.14.10 Relevant Alarms and Events..........................................................................................................6-224 6.14.11 FAQs.............................................................................................................................................. 6-225
6.15 ATM Traffic Management........................................................................................................................6-225 6.15.1 Introduction......................................................................................................................................6-226 6.15.2 Basic Concepts.................................................................................................................................6-226 6.15.2.1 ATM Traffic Parameters...............................................................................................................6-227 6.15.2.2 ATM Service Categories...............................................................................................................6-228 6.15.2.3 ATM Traffic Categories................................................................................................................6-229 6.15.2.4 ATM Traffic Control Schemes..................................................................................................... 6-230 6.15.3 Specifications...................................................................................................................................6-231 6.15.4 Reference Standards and Protocols..................................................................................................6-232 6.15.5 Availability.......................................................................................................................................6-232 6.15.6 Principles..........................................................................................................................................6-233 6.15.7 Configuration Procedure..................................................................................................................6-236 6.15.8 Configuration Example....................................................................................................................6-237 6.15.8.1 Network Diagram..........................................................................................................................6-237 6.15.8.2 Service Planning............................................................................................................................6-238 6.15.8.3 Configuration Process...................................................................................................................6-239 6.15.9 Task Collection................................................................................................................................ 6-240 6.15.10 Relevant Alarms and Events..........................................................................................................6-240 6.15.11 FAQs.............................................................................................................................................. 6-240
7 Clock Features.............................................................................................................................7-1
7.1 Synchronous Ethernet.....................................................................................................................................7-2 7.1.1 Introduction............................................................................................................................................7-2 7.1.2 Specifications.........................................................................................................................................7-3 7.1.3 Reference Standards and Protocols........................................................................................................7-3 7.1.4 Availability.............................................................................................................................................7-4 7.1.5 Principles................................................................................................................................................7-4 7.1.6 Planning Guidelines...............................................................................................................................7-5 7.1.7 Configuration Procedure........................................................................................................................7-5 7.1.8 Configuration Example..........................................................................................................................7-6 7.1.9 Task Collection......................................................................................................................................7-7 7.1.10 Relevant Alarms and Events................................................................................................................7-7 7.1.11 FAQs....................................................................................................................................................7-7 7.2 CES ACR........................................................................................................................................................7-7 7.2.1 Introduction............................................................................................................................................7-8 xxvi Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 02 (2011-01-20)
Contents
7.2.2 Basic Concepts.......................................................................................................................................7-9 7.2.2.1 CES ACR Clock Domain....................................................................................................................7-9 7.2.2.2 CES ACR Clock Protection..............................................................................................................7-10 7.2.2.3 CES ACR Clock Transparent Transmission Solution.......................................................................7-11 7.2.3 Specifications.......................................................................................................................................7-12 7.2.4 Reference Standards and Protocols......................................................................................................7-13 7.2.5 Availability...........................................................................................................................................7-13 7.2.6 Principles..............................................................................................................................................7-14 7.2.7 Configuration Procedure......................................................................................................................7-15 7.2.8 Configuration Example........................................................................................................................7-16 7.2.8.1 Network Diagram..............................................................................................................................7-16 7.2.8.2 Service Planning................................................................................................................................7-17 7.2.8.3 Configuration Process.......................................................................................................................7-18 7.2.9 Task Collection....................................................................................................................................7-19 7.2.10 Relevant Alarms and Events..............................................................................................................7-19 7.2.11 FAQs..................................................................................................................................................7-19
A Task Collection.........................................................................................................................A-1
A.1 Network Management...................................................................................................................................A-2 A.1.1 Managing NEs......................................................................................................................................A-2 A.1.1.1 Creating NEs by Using the Search Method.......................................................................................A-3 A.1.1.2 Creating NEs by Using the Manual Method.....................................................................................A-4 A.1.1.3 Configuring the Logical Board..........................................................................................................A-6 A.1.1.4 Changing the NE ID..........................................................................................................................A-7 A.1.1.5 Changing the NE Name.....................................................................................................................A-8 A.1.1.6 Synchronizing the NE Time..............................................................................................................A-8 A.1.1.7 Localizing the NE Time..................................................................................................................A-11 A.1.1.8 Configuring Standard NTP Keys.....................................................................................................A-11 A.1.2 Configuring the NE Data....................................................................................................................A-13 A.1.2.1 Uploading the NE Data...................................................................................................................A-13 A.1.2.2 Synchronizing NE Data...................................................................................................................A-14 A.1.3 Configuring the Performance Monitoring Status of NEs...................................................................A-14 A.1.4 Suppressing Alarms for Monitored Objects.......................................................................................A-15 A.1.5 Connecting Fibers or Cables..............................................................................................................A-16 A.1.5.1 Creating an Optical Transmission Line or Radio Link by Using the Search Method.....................A-16 A.1.5.2 Creating a Radio Link by Using the Manual Method.....................................................................A-17 A.1.5.3 Creating an Extended ECC..............................................................................................................A-18 A.1.5.4 Creating a Back-to-Back Radio Connection...................................................................................A-19 A.1.6 Managing Subnets..............................................................................................................................A-20 A.1.6.1 Creating a Subnet............................................................................................................................A-20 A.1.6.2 Copying Topology Objects..............................................................................................................A-21 A.1.6.3 Moving Topology Objects...............................................................................................................A-21 A.1.7 Managing Communications................................................................................................................A-22 Issue 02 (2011-01-20) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. xxvii
Contents
OptiX RTN 980 Radio Transmission System Feature Description (U2000) A.1.7.1 Setting NE Communication Parameters..........................................................................................A-23 A.1.7.2 Configuring DCCs...........................................................................................................................A-24 A.1.7.3 Configuring Extended ECC Communication..................................................................................A-25 A.1.7.4 Configuring DCC Transparent Transmission..................................................................................A-27 A.1.7.5 Creating Static IP Routes.................................................................................................................A-28 A.1.7.6 Setting Parameters of the OSPF Protocol........................................................................................A-29 A.1.7.7 Enabling the ARP Proxy.................................................................................................................A-30 A.1.7.8 Configuring the CLNS Role............................................................................................................A-30 A.1.7.9 Configuring the OSI Tunnel............................................................................................................A-31 A.1.7.10 Configuring the VLAN ID and Bandwidth Used by an Inband DCN..........................................A-32 A.1.7.11 Configuring the Enable Status of the Inband DCN Function on Ports..........................................A-33 A.1.7.12 Configuring the Protocol Type of the Inband DCN......................................................................A-34 A.1.7.13 Querying ECC Routes...................................................................................................................A-34 A.1.7.14 Querying IP Routes.......................................................................................................................A-35 A.1.7.15 Querying OSI Routes....................................................................................................................A-36 A.1.7.16 Configuring Access Control..........................................................................................................A-36 A.1.8 Configuring Service Access of NEs ..................................................................................................A-37 A.1.8.1 Configuring LCT Access to NEs.....................................................................................................A-37 A.1.8.2 Configuring Ethernet Access to NEs...............................................................................................A-38 A.1.8.3 Configuring Serial Interface Access to NEs....................................................................................A-39 A.1.9 Configuring an NE User.....................................................................................................................A-39 A.1.9.1 Creating an NE User........................................................................................................................A-40 A.1.9.2 Changing the Password of an NE User...........................................................................................A-41 A.1.9.3 Setting Warning Screen Parameters................................................................................................A-42 A.1.9.4 Switching NE Users........................................................................................................................A-43 A.1.10 Configuring SSL Protocol Communication.....................................................................................A-44 A.1.10.1 Configuring SSL Protocol Communication Between a U2000 Server and its Clients.................A-44 A.1.10.2 Configuring the Connection Mode Between a U2000 Client and Its Gateway NE......................A-45
A.2 Managing Radio Links................................................................................................................................A-47 A.2.1 Creating an IF 1+1 Protection Group.................................................................................................A-47 A.2.2 Creating an XPIC Protection Group...................................................................................................A-48 A.2.3 Setting the AM Attributes of the XPIC Hybrid Radio Link...............................................................A-49 A.2.4 Configuring the IF/ODU Information of a Radio Link......................................................................A-50 A.2.5 Creating an N+1 Protection Group.....................................................................................................A-51 A.2.6 Querying the IF 1+1 Protection Status...............................................................................................A-53 A.2.7 Querying the IF N+1 Protection Status..............................................................................................A-53 A.2.8 IF 1+1 Protection Switching...............................................................................................................A-54 A.2.9 IF N+1 Protection Switching..............................................................................................................A-55 A.2.10 Starting/Stopping the N+1 Protection Protocol................................................................................A-55 A.3 Managing the MSP......................................................................................................................................A-56 A.3.1 Configuring Linear MSP....................................................................................................................A-56 A.3.2 Querying the Status of the Linear MSP..............................................................................................A-58 xxviii Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 02 (2011-01-20)
Contents
A.3.3 Performing Linear MSP Switching....................................................................................................A-58 A.3.4 Starting/Stopping the Linear MSP Protocol.......................................................................................A-59 A.3.5 Configuring Ring MSP.......................................................................................................................A-60 A.3.6 Querying Ring MSP Status................................................................................................................A-61 A.3.7 Triggering Ring MSP Switching........................................................................................................A-62 A.3.8 Starting/Stopping the Ring MSP Protocol..........................................................................................A-63 A.4 Managing TDM Services............................................................................................................................A-63 A.4.1 Creating the Cross-Connections of Point-to-Point Services..............................................................A-64 A.4.2 Creating Cross-Connections of SNCP Services.................................................................................A-65 A.4.3 Modifying the Priorities of E1 Services.............................................................................................A-66 A.4.4 Inserting TU_AIS...............................................................................................................................A-67 A.4.5 Configuring the Automatic Switching of SNCP Services..................................................................A-68 A.4.6 Deleting Cross-Connections...............................................................................................................A-69 A.4.7 Converting a Normal Service into an SNCP Service.........................................................................A-70 A.4.8 Converting an SNCP Service to a Normal Service............................................................................A-71 A.4.9 Querying TDM Services.....................................................................................................................A-72 A.4.10 Switching SNCP Services................................................................................................................A-72 A.4.11 Querying the Protection Status of SNCP Services...........................................................................A-73 A.5 Managing Ports............................................................................................................................................A-74 A.5.1 Setting the Parameters of SDH Ports..................................................................................................A-74 A.5.2 Setting the Parameters of PDH Ports..................................................................................................A-75 A.5.3 Configuring Overhead Bytes..............................................................................................................A-76 A.5.3.1 Configuring RSOHs........................................................................................................................A-76 A.5.3.2 Configuring VC-4 POHs.................................................................................................................A-77 A.5.3.3 Configuring VC-12 POHs...............................................................................................................A-78 A.5.4 Setting Smart E1 Port Parameters......................................................................................................A-79 A.5.4.1 Setting Basic Attributes of Smart E1 Ports.....................................................................................A-80 A.5.4.2 Setting Advanced Attributes of Smart E1 Ports..............................................................................A-81 A.5.5 Setting Serial Port Parameters............................................................................................................A-81 A.5.5.1 Creating Serial Ports........................................................................................................................A-82 A.5.5.2 Setting Basic Attributes of Serial Ports...........................................................................................A-82 A.5.6 Setting the Parameters of Ethernet Ports............................................................................................A-83 A.5.6.1 Setting the General Attributes of Ethernet Ports.............................................................................A-83 A.5.6.2 Configuring the Traffic Control of Ethernet Ports..........................................................................A-84 A.5.6.3 Setting the Layer 2 Attributes of Ethernet Ports.............................................................................A-85 A.5.6.4 Setting Layer 3 Attributes of Ethernet Ports...................................................................................A-86 A.5.6.5 Setting the Advanced Attributes of Ethernet Ports..........................................................................A-86 A.5.7 Setting the General Attributes of the IF_ETH Port............................................................................A-87 A.5.7.1 Setting the General Attributes of the IF_ETH Port.........................................................................A-87 A.5.7.2 Setting the Layer 2 Attributes of the IF_ETH Port.........................................................................A-88 A.5.7.3 Setting Layer 3 Attributes of IF_ETH Ports....................................................................................A-89 A.5.7.4 Setting the Advanced Attributes of the IF_ETH Port.....................................................................A-89 Issue 02 (2011-01-20) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. xxix
Contents
OptiX RTN 980 Radio Transmission System Feature Description (U2000) A.5.8 Setting Parameters of IF Interfaces....................................................................................................A-90 A.5.8.1 Setting IF Attributes........................................................................................................................A-90 A.5.8.2 Configuring the ATPC Attributes................................................................................................... A-92 A.5.8.3 Setting Advanced AM Attributes....................................................................................................A-92 A.5.8.4 Querying the AM Status..................................................................................................................A-93 A.5.8.5 Querying the ATPC Adjustment Records.......................................................................................A-94 A.5.8.6 Modifying the Hybrid/AM Attributes.............................................................................................A-94 A.5.9 Setting the Parameters of ODU Ports.................................................................................................A-97 A.5.9.1 Setting the Transmit Frequency Attribute of the ODU...................................................................A-97 A.5.9.2 Querying the ODU Attribute...........................................................................................................A-98 A.5.9.3 Setting the Power Attributes of the ODU........................................................................................A-98 A.5.9.4 Setting the Advanced Attributes of the ODU..................................................................................A-99 A.5.9.5 Setting the State of an ODU Transmitter........................................................................................ A-99 A.5.9.6 Querying the History Transmit Power and Receive Power...........................................................A-100
A.6 Configuring Ethernet Services and Features on the Packet Plane.............................................................A-101 A.6.1 Managing the ERPS ........................................................................................................................A-102 A.6.1.1 Creating Ethernet Ring Protection Instances.................................................................................A-102 A.6.1.2 Setting the Parameters of Ethernet Ring Protocol.........................................................................A-103 A.6.1.3 Querying the Status of the Ethernet Ring Protocol.......................................................................A-103 A.6.2 Managing the LAG...........................................................................................................................A-104 A.6.2.1 Creating a LAG.............................................................................................................................A-104 A.6.2.2 Setting Parameters for LAGs.........................................................................................................A-106 A.6.2.3 Querying the Protocol Information of the LAG............................................................................A-107 A.6.3 Configure the Ethernet Service........................................................................................................A-108 A.6.3.1 Configuring the QinQ Link...........................................................................................................A-108 A.6.3.2 Configuring UNI-UNI E-Line Services .......................................................................................A-109 A.6.3.3 Configuring NNI-NNI E-Line Services........................................................................................A-110 A.6.3.4 Configuring UNI-NNI E-Line Services (Carried by QinQ Links)................................................A-111 A.6.3.5 Configuring UNI-NNI E-Line Services (Carried by PWs)...........................................................A-112 A.6.3.6 Creating a VLAN Forwarding Table Item....................................................................................A-114 A.6.3.7 Configuring TPID for a Request VLAN.......................................................................................A-115 A.6.3.8 Configuring IEEE 802.1d Bridge-Based E-LAN Services...........................................................A-115 A.6.3.9 Configuring IEEE 802.1q Bridge-Based E-LAN Services...........................................................A-119 A.6.3.10 Configuring IEEE 802.1ad Bridge-Based E-LAN Services........................................................A-121 A.6.3.11 Changing Logical Ports Connected to a VB................................................................................A-123 A.6.3.12 Deleting an E-Line Service.........................................................................................................A-123 A.6.3.13 Deleting E-LAN Services............................................................................................................A-124 A.6.4 Managing the MAC Address Table..................................................................................................A-125 A.6.4.1 Creating a Static MAC Address Entry..........................................................................................A-125 A.6.4.2 Creating a Blacklist Entry of MAC Addresses..............................................................................A-126 A.6.4.3 Configuring the Aging Parameters of a MAC Address Table.......................................................A-127 A.6.4.4 Querying or Deleting a Dynamic MAC Address..........................................................................A-127 xxx Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 02 (2011-01-20)
Contents
A.6.5 Setting the Mode for Processing an Unknown Frame of the E-LAN Service..................................A-128 A.6.6 Managing the MSTP.........................................................................................................................A-129 A.6.6.1 Creating the MSTP Port Group.....................................................................................................A-129 A.6.6.2 Setting the Bridge Parameters of the MSTP..................................................................................A-130 A.6.6.3 Setting the Parameters of the CIST...............................................................................................A-131 A.6.6.4 Querying the CIST Running Information......................................................................................A-132 A.6.6.5 Changing the Spanning Tree Protocol Used by the Port Group....................................................A-133 A.6.6.6 Enabling/Disabling the MSTP Protocol........................................................................................A-133 A.6.6.7 Modifying the Configuration Data of the MSTP Port Group........................................................A-134 A.6.7 Managing the QoS............................................................................................................................A-135 A.6.7.1 Creating a DS Domain...................................................................................................................A-136 A.6.7.2 Modifying the Mapping Relationships for the DS Domain..........................................................A-138 A.6.7.3 Changing the Ports Applied to a DS Domain and Their Trusted Packet Types............................A-139 A.6.7.4 Creating a Port Policy....................................................................................................................A-140 A.6.7.5 Modifying the Port Policy.............................................................................................................A-141 A.6.7.6 Creating the Traffic.......................................................................................................................A-142 A.6.7.7 Setting the Port That Uses the Port Policy....................................................................................A-143 A.6.7.8 Configuring Port Shaping..............................................................................................................A-145 A.6.7.9 Querying the Port Policy...............................................................................................................A-146 A.6.7.10 Querying the DS Domain of a Port.............................................................................................A-147 A.6.8 Using the IEEE 802.1ag OAM.........................................................................................................A-147 A.6.8.1 Creating an MD.............................................................................................................................A-148 A.6.8.2 Creating an MA.............................................................................................................................A-149 A.6.8.3 Creating an MEP Point..................................................................................................................A-150 A.6.8.4 Creating Remote MEPs in an MA.................................................................................................A-151 A.6.8.5 Creating an MIP............................................................................................................................A-152 A.6.8.6 Performing a CC Test....................................................................................................................A-152 A.6.8.7 Performing an LB Test..................................................................................................................A-153 A.6.8.8 Performing an LT Test..................................................................................................................A-155 A.6.9 Using the IEEE 802.3ah OAM ........................................................................................................A-156 A.6.9.1 Enabling the OAM Auto-Discovery Function..............................................................................A-156 A.6.9.2 Enabling the Link Event Notification ...........................................................................................A-157 A.6.9.3 Modifying the OAM Error Frame Monitoring Threshold ............................................................A-158 A.6.9.4 Performing Remote Loopback......................................................................................................A-159 A.6.9.5 Enabling Self-Loop Detection ......................................................................................................A-160 A.6.10 LPT Configuration..........................................................................................................................A-161 A.6.10.1 Configuring Point-to-Point LPT Traversing an L2 Network......................................................A-161 A.6.10.2 Configuring Point-to-Point LPT Traversing a PSN or QinQ Network.......................................A-162 A.6.10.3 Configuring Point-to-Multipoint LPT.........................................................................................A-163 A.7 Managing MPLS/PWE3 Services and Features........................................................................................A-164 A.7.1 Managing Address Resolution.........................................................................................................A-165 A.7.1.1 Creating ARP Static Entries..........................................................................................................A-165 Issue 02 (2011-01-20) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. xxxi
Contents
OptiX RTN 980 Radio Transmission System Feature Description (U2000) A.7.1.2 Querying ARP Entries...................................................................................................................A-166 A.7.1.3 Converting Dynamic ARP Entries to Static ARP Entries.............................................................A-166 A.7.1.4 Deleting Static ARP Entries..........................................................................................................A-166 A.7.1.5 Setting ARP Aging Time...............................................................................................................A-167 A.7.2 Managing MPLS Tunnels.................................................................................................................A-167 A.7.2.1 Setting Basic MPLS Attributes.....................................................................................................A-168 A.7.2.2 Creating a Unidirectional MPLS Tunnel.......................................................................................A-169 A.7.2.3 Creating a Bidirectional MPLS Tunnel.........................................................................................A-170 A.7.2.4 Querying MPLS Tunnel Information............................................................................................A-172 A.7.2.5 Deleting MPLS Tunnels................................................................................................................A-172 A.7.2.6 Setting MPLS OAM Parameters...................................................................................................A-173 A.7.2.7 Enabling/Disabling FDI.................................................................................................................A-173 A.7.2.8 Starting/Stopping CV/FFD Detection for MPLS Tunnels............................................................A-174 A.7.2.9 Querying LSP Running Status.......................................................................................................A-175 A.7.2.10 Clearing OAM Configuration Data for MPLS Tunnels..............................................................A-176 A.7.2.11 Performing an LSP Ping Test......................................................................................................A-176 A.7.2.12 Performing an LSP Traceroute Test............................................................................................A-177 A.7.3 Managing MPLS APS Protection Groups........................................................................................A-178 A.7.3.1 Creating an MPLS APS Protection Group....................................................................................A-179 A.7.3.2 Querying MPLS APS Status.........................................................................................................A-180 A.7.3.3 Triggering MPLS APS Switching.................................................................................................A-181 A.7.3.4 Enabling/Disabling MPLS APS Protection...................................................................................A-182 A.7.4 Managing PWs.................................................................................................................................A-183 A.7.4.1 Querying Information and Running Status of PWs.......................................................................A-183 A.7.4.2 Creating an MS-PW......................................................................................................................A-184 A.7.4.3 Setting PW OAM Parameters........................................................................................................A-185 A.7.4.4 Performing a PW Ping Test...........................................................................................................A-186 A.7.4.5 Performing a PW Traceroute Test.................................................................................................A-187 A.7.5 Managing a PW APS Protection Group...........................................................................................A-188 A.7.5.1 Creating a PW APS Protection Group...........................................................................................A-188 A.7.5.2 Configuring Slave Protection Pairs of PW APS............................................................................A-191 A.7.5.3 Querying PW APS Status..............................................................................................................A-192 A.7.5.4 Triggering PW APS Switching.....................................................................................................A-193 A.7.5.5 Enabling/Disabling PW APS Protection.......................................................................................A-194 A.7.6 Managing CES Services...................................................................................................................A-195 A.7.6.1 Creating CES Services..................................................................................................................A-195 A.7.6.2 Modifying CES Service Parameters..............................................................................................A-197 A.7.6.3 Querying CES Service Information...............................................................................................A-198 A.7.6.4 Deleting a CES Service.................................................................................................................A-199 A.7.7 Managing ATM/IMA Ports..............................................................................................................A-199 A.7.7.1 Binding ATM TRUNKs................................................................................................................A-200 A.7.7.2 Configuring an IMA group ...........................................................................................................A-201
xxxii
Issue 02 (2011-01-20)
Contents
A.7.7.3 Setting ATM Port Parameters.......................................................................................................A-202 A.7.7.4 Querying Running Status of an IMA Group.................................................................................A-203 A.7.7.5 Querying Link Running Status of an IMA Group.........................................................................A-203 A.7.8 Managing ATM Services.................................................................................................................A-204 A.7.8.1 Creating ATM Services.................................................................................................................A-204 A.7.8.2 Modifying ATM Service Parameters............................................................................................A-207 A.7.8.3 Querying ATM Services................................................................................................................A-207 A.7.8.4 Deleting an ATM Service..............................................................................................................A-208 A.7.9 ATM Traffic Management...............................................................................................................A-208 A.7.9.1 Creating an ATM-DiffServ Domain.............................................................................................A-209 A.7.9.2 Modifying an ATM-Diffserv Domain...........................................................................................A-210 A.7.9.3 Creating an ATM Policy...............................................................................................................A-211 A.7.9.4 Modifying an ATM Policy............................................................................................................A-212 A.7.10 Using ATM OAM..........................................................................................................................A-213 A.7.10.1 Setting Segment and End Attributes of AIS/RDI........................................................................A-213 A.7.10.2 Performing a Continuity Check Test...........................................................................................A-214 A.7.10.3 Querying or Setting LLIDs..........................................................................................................A-215 A.7.10.4 Performing an LB Test................................................................................................................A-215 A.8 Managing the Clock..................................................................................................................................A-216 A.8.1 Managing Clocks at the Physical Layer...........................................................................................A-216 A.8.1.1 Configuring the Clock Sources.....................................................................................................A-217 A.8.1.2 Configuring Clock Subnets...........................................................................................................A-218 A.8.1.3 Self-Defined Clock Quality...........................................................................................................A-219 A.8.1.4 Configuring the SSM Output Status..............................................................................................A-220 A.8.1.5 Configuring the Clock ID Output Status.......................................................................................A-220 A.8.1.6 Modifying the Parameters of the Clock Output............................................................................A-221 A.8.1.7 Changing the Conditions for Clock Source Switching..................................................................A-221 A.8.1.8 Modifying the Recovery Parameter of the Clock Source..............................................................A-222 A.8.1.9 Querying the Clock Synchronization Status..................................................................................A-223 A.8.2 Managing CES ACR Clocks............................................................................................................A-223 A.8.2.1 Configuring the Primary Clock for an ACR Clock Domain.........................................................A-223 A.8.2.2 Configuring Ports Using the Clock Domain.................................................................................A-224 A.9 Using the RMON.......................................................................................................................................A-226 A.9.1 Browsing the Performance Data in the Statistics Group of an Ethernet Port...................................A-226 A.9.2 Configuring an Alarm Group for an Ethernet Port...........................................................................A-227 A.9.3 Configuring a History Control Group..............................................................................................A-227 A.9.4 Browsing the Performance Data in the History Group of an Ethernet Port.....................................A-228 A.10 Configuring Auxiliary Ports and Functions............................................................................................A-229 A.10.1 Configuring the Orderwire.............................................................................................................A-229 A.10.2 Configuring the Synchronous Data Service...................................................................................A-230 A.10.3 Configuring the Asynchronous Data Service.................................................................................A-231 A.10.4 Configuring the Wayside E1 Service.............................................................................................A-232 Issue 02 (2011-01-20) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. xxxiii
Contents
OptiX RTN 980 Radio Transmission System Feature Description (U2000) A.10.5 Configure External Alarms.............................................................................................................A-233
A.11 Verifying Services and Features..............................................................................................................A-234 A.11.1 Testing the E1 Service Through PRBS..........................................................................................A-235 A.11.2 Testing the E1 Service by Using a BER Tester..............................................................................A-236 A.11.3 Testing the Ethernet Service...........................................................................................................A-238 A.11.4 Testing the ATM Service...............................................................................................................A-242 A.11.5 Testing the AM Switching..............................................................................................................A-244 A.11.5.1 Testing the AM Switching by Using a BER Tester....................................................................A-244 A.11.5.2 Testing the AM Switching Without a BER Tester......................................................................A-246 A.11.6 Testing the Protection Switching....................................................................................................A-248 A.11.6.1 Testing the IF 1+1 Switching......................................................................................................A-249 A.11.6.2 Testing the N+1 Protection Switching........................................................................................A-252 A.11.6.3 Testing the SNCP Switching.......................................................................................................A-255 A.11.6.4 Testing the ERPS.........................................................................................................................A-258 A.11.6.5 Testing the MPLS APS Protection Switching.............................................................................A-260 A.11.6.6 Testing the Two-Fiber Bidirectional MSP Switching.................................................................A-263 A.11.6.7 Testing the Linear MSP Switching..............................................................................................A-267 A.11.6.8 Switching the System Control Unit and the Cross-Connect Unit...............................................A-271
B Parameters Description............................................................................................................B-1
B.1 Parameters for Network Management...........................................................................................................B-2 B.1.1 Parameters for NE Management...........................................................................................................B-2 B.1.1.1 Parameter Description: NE Searching...............................................................................................B-2 B.1.1.2 Parameter Description: NE Creation.................................................................................................B-7 B.1.1.3 Parameter Description: Attribute_Changing NE IDs........................................................................B-9 B.1.1.4 Parameter Description: NE Time Synchronization..........................................................................B-10 B.1.1.5 Parameter Description: Localization Management of the NE Time................................................B-13 B.1.1.6 Parameter Description: Standard NTP Key Management...............................................................B-14 B.1.1.7 Parameter Description: License Management.................................................................................B-15 B.1.1.8 Parameter Description: Automatic Disabling of the Functions of NEs...........................................B-16 B.1.2 Parameters for Communications Management...................................................................................B-17 B.1.2.1 Parameter Description: NE Communication Parameter Setting......................................................B-18 B.1.2.2 Parameter Description: DCC Management_DCC Rate Configuration............................................B-19 B.1.2.3 Parameter Description: DCC Management_DCC Transparent Transmission Management...........B-21 B.1.2.4 Parameter Description: ECC Management_Ethernet Port Extended ECC......................................B-23 B.1.2.5 Parameter Description: NE ECC Link Management.......................................................................B-25 B.1.2.6 Parameter Description: IP Protocol Stack Management_IP Route Management............................B-26 B.1.2.7 Parameter Description: IP Protocol Stack Management_IP Route Management Creation.............B-28 B.1.2.8 Parameter Description: IP Protocol Stack Management_OSPF Parameter Settings.......................B-28 B.1.2.9 Parameter Description: IP Protocol Stack_Proxy ARP...................................................................B-32 B.1.2.10 Parameter Description: Port OSPF Setting....................................................................................B-33 B.1.2.11 Parameter Description: OSI Management_Network Layer Parameter..........................................B-34 B.1.2.12 Parameter Description: OSI Management_Routing Table............................................................B-35 xxxiv Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 02 (2011-01-20)
Contents
B.1.2.13 Parameter Description: OSI Management_OSI Tunnel.................................................................B-36 B.1.2.14 Parameter Description: DCN Management_Bandwidth Management..........................................B-40 B.1.2.15 Parameter Description: DCN Management_Port Setting..............................................................B-40 B.1.2.16 Parameter Description: DCN Management_Protocol Setting.......................................................B-41 B.1.2.17 Parameter Description: DCN Management_Access Control.........................................................B-42 B.1.2.18 Parameter Description: Access Control.........................................................................................B-42 B.1.3 Parameters for Network Security Management..................................................................................B-43 B.1.3.1 Parameter Description: NE User Management................................................................................B-43 B.1.3.2 Parameter Description: NE User Management_Creation................................................................B-44 B.1.3.3 Parameter Description: LCT Access Control..................................................................................B-46 B.2 Radio Link Parameters.................................................................................................................................B-47 B.2.1 Parameter Description: Link Configuration_XPIC Workgroup_Creation.........................................B-48 B.2.2 Parameter Description: Link Configuration_XPIC............................................................................B-52 B.2.3 Parameter Description: N+1 Protection_Create..................................................................................B-60 B.2.4 Parameter Description: N+1 Protection..............................................................................................B-61 B.2.5 Parameter: IF 1+1 Protection_Create..................................................................................................B-63 B.2.6 Parameter Description: IF 1+1 Protection..........................................................................................B-65 B.2.7 Parameter: Link Configuration_IF/ODU Configuration....................................................................B-68 B.3 Multiplex Section Protection Parameters.....................................................................................................B-78 B.3.1 Parameter Description: Linear MSP_Creation...................................................................................B-78 B.3.2 Parameter Description: Linear MSP...................................................................................................B-82 B.3.3 Parameter Description: Ring MSP_Creation......................................................................................B-85 B.3.4 Parameter Description: Ring MSP......................................................................................................B-87 B.4 SDH/PDH Service Parameters.....................................................................................................................B-88 B.4.1 Parameter Description: SDH Service Configuration_Creation..........................................................B-89 B.4.2 Parameter Description: SDH Service Configuration_SNCP Service Creation..................................B-91 B.4.3 Parameter Description: SDH Service Configuration_Converting Normal Services Into SNCP Services ......................................................................................................................................................................B-95 B.4.4 Parameter Description: SDH Service Configuration..........................................................................B-99 B.4.5 Parameter Description: SNCP Service Control................................................................................B-101 B.4.6 Parameter Description: TU_AIS Insertion........................................................................................B-104 B.5 Parameters for Board Interfaces.................................................................................................................B-105 B.5.1 PDH Port Parameters........................................................................................................................B-106 B.5.1.1 Parameter Description: PDH Ports_Basic Attributes....................................................................B-106 B.5.1.2 Parameter Description: PDH Ports_Advanced Attributes.............................................................B-107 B.5.2 Parameters for the Ports on Ethernet Boards....................................................................................B-110 B.5.2.1 Parameter Description: Ethernet Interface_Basic Attributes.........................................................B-110 B.5.2.2 Parameter Description: Ethernet Interface_Flow Control.............................................................B-114 B.5.2.3 Parameter Description: Ethernet Interface_Layer 2 Attributes......................................................B-115 B.5.2.4 Parameter Description: Ethernet Port_Layer 3 Attributes.............................................................B-119 B.5.2.5 Parameter Description: Ethernet Interface_Advanced Attributes..................................................B-120 B.5.3 Serial Port Parameters.......................................................................................................................B-123 B.5.3.1 Parameter Description: Serial Port_Basic Attributes.....................................................................B-123 Issue 02 (2011-01-20) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. xxxv
Contents
OptiX RTN 980 Radio Transmission System Feature Description (U2000) B.5.3.2 Parameter Description: Serial Port_Creation of Serial Ports.........................................................B-124 B.5.4 Microwave Interface Parameters......................................................................................................B-125 B.5.4.1 Parameter Description: Microwave Interface_Basic Attributes....................................................B-126 B.5.4.2 Parameter Description: Microwave Interface_Layer 2 Attributes.................................................B-127 B.5.4.3 Parameter Description: Microwave Interface_Layer 3 Attributes.................................................B-129 B.5.4.4 Parameter Description: Microwave Interface_Advanced Attributes.............................................B-130 B.5.5 IF Board Parameters.........................................................................................................................B-134 B.5.5.1 Parameter Description: IF Interface_IF Attribute..........................................................................B-134 B.5.5.2 Parameter Description: IF Interface_ATPC Attribute...................................................................B-142 B.5.5.3 Parameter Description: Hybrid_AM Configuration_Advanced Attributes...................................B-143 B.5.5.4 Parameter Description: ATPC Adjustment Records......................................................................B-144 B.5.5.5 Parameter Description: PRBS Test................................................................................................B-145 B.5.6 ODU Parameters...............................................................................................................................B-146 B.5.6.1 Parameter Description: ODU Interface_Radio Frequency Attribute.............................................B-147 B.5.6.2 Parameter Description: ODU Interface_Power Attributes.............................................................B-148 B.5.6.3 Parameter Description: ODU Interface_Equipment Information..................................................B-152 B.5.6.4 Parameter Description: ODU Interface_Advanced Attributes.......................................................B-154 B.5.7 Parameters for SDH Interface Boards...............................................................................................B-155 B.5.7.1 Parameter Description: SDH Interfaces.........................................................................................B-155 B.5.7.2 Parameter Description: Automatic Laser Shutdown......................................................................B-157 B.5.8 Parameters for PDH Interface Boards...............................................................................................B-157 B.5.8.1 Parameter Description: PDH Interfaces.........................................................................................B-158 B.5.8.2 Parameter Description: PRBS Test................................................................................................B-160 B.5.9 Parameters for Overhead...................................................................................................................B-161 B.5.9.1 Parameter Description: Regenerator Section Overhead.................................................................B-161 B.5.9.2 Parameter Description: VC-4 POHs..............................................................................................B-162 B.5.9.3 Parameter Description: VC-12 POHs............................................................................................B-164
B.6 Parameters for Ethernet Services and Ethernet Features on the Packet Plane...........................................B-165 B.6.1 Parameters for Ethernet Services......................................................................................................B-165 B.6.1.1 Parameter Description: E-Line Service_Creation..........................................................................B-166 B.6.1.2 Parameter Description: E-Line Service..........................................................................................B-185 B.6.1.3 Parameter Description: VLAN Forwarding Table Item_Creation.................................................B-196 B.6.1.4 Parameter Description: E-LAN Service_Creation.........................................................................B-197 B.6.1.5 Parameter Description: E-LAN Service.........................................................................................B-202 B.6.1.6 Parameter Description: QinQ Link_Creation................................................................................B-214 B.6.2 Parameters for Ethernet Protocols....................................................................................................B-215 B.6.2.1 Parameter Description: ERPS Management_Creation..................................................................B-215 B.6.2.2 Parameter Description: ERPS Management..................................................................................B-217 B.6.2.3 Parameter Description: MSTP Configuration_Port Group Creation.............................................B-223 B.6.2.4 Parameter Description: MSTP Configuration_Port Group Configuration....................................B-225 B.6.2.5 Parameter Description: MSTP Configuration_ Bridge Parameters...............................................B-225 B.6.2.6 Parameter Description: MSTP Configuration_CIST Parameters..................................................B-231 xxxvi Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 02 (2011-01-20)
Contents
B.6.2.7 Parameter Description: MSTP Configuration_Running Information About the CIST.................B-233 B.6.2.8 Parameter Description: Ethernet Link Aggregation Management_LAG Creation........................B-241 B.6.2.9 Parameter Description: Ethernet Link Aggregation_Link Aggregation........................................B-248 B.6.2.10 Parameter Description: LPT Management_Point-to-Point LPT..................................................B-249 B.6.2.11 Parameter Description: LPT Management_Creating Point-to-Point LPT...................................B-251 B.6.2.12 Parameter Description: LPT Management_Point-to-Multipoint LPT.........................................B-252 B.6.2.13 Parameter Description: LPT Management_Creating Point-to-Multipoint LPT..........................B-254 B.6.3 Parameters for the Ethernet OAM....................................................................................................B-258 B.6.3.1 Parameter Description: Ethernet Service OAM Management_Maintenance Domain Creation ....................................................................................................................................................................B-259 B.6.3.2 Parameter Description: Ethernet Service OAM Management_Maintenance Association Creation ....................................................................................................................................................................B-260 B.6.3.3 Parameter Description: Ethernet Service OAM Management_MEP Creation..............................B-261 B.6.3.4 Parameter Description: Ethernet Service OAM Management_Remote MEP Creation................B-262 B.6.3.5 Parameter Description: Ethernet Service OAM Management_MIP Creation...............................B-263 B.6.3.6 Parameter Description: Ethernet Service OAM Management_LB Enabling................................B-264 B.6.3.7 Parameter Description: Ethernet Service OAM Management_LT Enabling.................................B-265 B.6.3.8 Parameter Description: Ethernet Port OAM Management_OAM Parameter................................B-267 B.6.3.9 Parameter Description: Ethernet Port OAM Management_OAM Error Frame Monitoring.........B-270 B.6.4 QoS Parameters.................................................................................................................................B-271 B.6.4.1 Parameter Description: Diffserv Domain Management.................................................................B-272 B.6.4.2 Parameter Description: DiffServ Domain Management_Create...................................................B-277 B.6.4.3 Parameter Description: DiffServ Domain Applied Port_Modification.........................................B-284 B.6.4.4 Parameter Description: Policy Management.................................................................................B-286 B.6.4.5 Parameter Description: Port Policy................................................................................................B-291 B.6.4.6 Parameter Description: Port Policy_Traffic Classification Configuration....................................B-296 B.6.4.7 Parameter Description: Port Shaping Management_Creation.......................................................B-307 B.7 RMON Parameters.....................................................................................................................................B-309 B.7.1 Parameter Description: RMON Performance_Statistics Group........................................................B-309 B.7.2 Parameter Description: RMON Performance_History Group..........................................................B-310 B.7.3 Parameter Description: RMON Performance_History Control Group.............................................B-311 B.7.4 Parameter Description: RMON Performance_RMON Setting.........................................................B-312 B.8 Parameters for MPLS/PWE3 Services.......................................................................................................B-314 B.8.1 MPLS Tunnel Parameters.................................................................................................................B-314 B.8.1.1 Parameter Description: Basic Configurations of MPLS Tunnels..................................................B-315 B.8.1.2 Parameter Description: Unicast Tunnel Management_Static Tunnel............................................B-316 B.8.1.3 Parameter Description: Unicast Tunnel Management_Creation of Unidirectional Tunnels.........B-320 B.8.1.4 Parameter Description: Unicast Tunnel Management_Creation of Bidirectional Tunnels...........B-324 B.8.1.5 Parameter Description: Unicast Tunnel Management_OAM Parameters.....................................B-328 B.8.1.6 Parameter Description: Unicast Tunnel Management_FDI...........................................................B-333 B.8.1.7 Parameter Description: Unicast Tunnel Management_LSP Ping..................................................B-334 B.8.1.8 Parameter Description: Unicast Tunnel Management_LSP Traceroute........................................B-337 B.8.1.9 Parameter Description: PW Management_PW Management........................................................B-340 Issue 02 (2011-01-20) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. xxxvii
Contents
OptiX RTN 980 Radio Transmission System Feature Description (U2000) B.8.1.10 Parameter Description: PW Management_MS-PW Creation......................................................B-346 B.8.1.11 Parameter Description: PW Management_PW OAM.................................................................B-355 B.8.1.12 Parameter Description: PW Management_PW Ping...................................................................B-360 B.8.1.13 Parameter Description: PW Management_PW Traceroute.........................................................B-363 B.8.1.14 Parameter Description: MPLS APS Protection Management.....................................................B-366 B.8.1.15 Parameter Description: Tunnel Protection Group_Creation........................................................B-369 B.8.1.16 Parameter Description: PW APS Protection Group_Creation.....................................................B-374 B.8.1.17 Parameter Description: Slave Protection Pair of a PW APS Protection Group_Creation...........B-384 B.8.2 CES Parameters................................................................................................................................B-390 B.8.2.1 Parameter Description: CES Service Management.......................................................................B-390 B.8.2.2 Parameter Description: CES Service Management_Creation........................................................B-400 B.8.3 ATM Parameters...............................................................................................................................B-415 B.8.3.1 Parameter Description: ATM IMA Management_IMA Group Management...............................B-416 B.8.3.2 Parameter Description: ATM IMA Management_Bound Path Configuration..............................B-421 B.8.3.3 Parameter Description: ATM IMA Management_IMA Group Status..........................................B-423 B.8.3.4 Parameter Description: ATM IMA Management_IMA Link Status.............................................B-424 B.8.3.5 Parameter Description: ATM IMA Management_ATM Interface Management..........................B-425 B.8.3.6 Parameter Description: Configuration of ATM Service Class Mapping Table.............................B-427 B.8.3.7 Parameter Description: Configuration of ATM Service Class Mapping Table_Creation.............B-428 B.8.3.8 Parameter Description: ATM Policy Management........................................................................B-430 B.8.3.9 Parameter Description: ATM Policy Management_Creation........................................................B-435 B.8.3.10 Parameter Description: ATM Service Management....................................................................B-440 B.8.3.11 Parameter Description: ATM Service Management_Creation....................................................B-448 B.8.3.12 Parameter Description: ATM OAM Management_Segment and End Attributes.......................B-460 B.8.3.13 Parameter Description: ATM OMA Management_CC Activation Status..................................B-463 B.8.3.14 Parameter Description: ATM OAM Management_Remote End Loopback Status.....................B-466 B.8.3.15 Parameter Description: ATM OAM Management_LLID...........................................................B-468
B.9 Clock Parameters.......................................................................................................................................B-469 B.9.1 Parameter Description: Frequency Selection Mode..........................................................................B-469 B.9.2 Physical Clock Parameters................................................................................................................B-470 B.9.2.1 Parameter Description: Clock Source Priority Table.....................................................................B-471 B.9.2.2 Parameter Description: Clock Subnet Setting_Clock Subnet........................................................B-472 B.9.2.3 Parameter Description: Clock Subnet Setting_Clock Quality.......................................................B-476 B.9.2.4 Parameter Description: Clock Subset Setting_SSM Output Control.............................................B-479 B.9.2.5 Parameter Description: Clock Subset Setting_Clock ID Enabling Status.....................................B-480 B.9.2.6 Parameter Description: Clock Source Switching_Clock Source Restoration Parameters.............B-481 B.9.2.7 Parameter Description: Clock Source Switching_Clock Source Switching..................................B-483 B.9.2.8 Parameter Description: Clock Source Switching_Clock Source Switching Conditions...............B-484 B.9.2.9 Parameter Description: Output Phase-Locked Source of the External Clock Source...................B-486 B.9.2.10 Parameter Description: Clock Synchronization Status................................................................B-488 B.9.3 CES ACR Clock Parameters.............................................................................................................B-490 B.9.3.1 Parameter Description: ACR Clock Source...................................................................................B-490 xxxviii Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 02 (2011-01-20)
Contents
B.9.3.2 Parameter Description: Clock Domain..........................................................................................B-490 B.9.3.3 Parameter Description: Clock Domain_Creation..........................................................................B-491 B.10 Parameters for the Orderwire and Auxiliary Interfaces...........................................................................B-492 B.10.1 Parameter Description: Orderwire_General....................................................................................B-492 B.10.2 Parameter Description: Orderwire_Advanced................................................................................B-494 B.10.3 Parameter Description: Orderwire_F1 Data Port............................................................................B-495 B.10.4 Parameter Description: Orderwire_Broadcast Data Port................................................................B-496 B.10.5 Parameter Description: Environment Monitoring Interface...........................................................B-497
C Glossary......................................................................................................................................C-1
C.1 0-9..................................................................................................................................................................C-2 C.2 A-E.................................................................................................................................................................C-2 C.3 F-J................................................................................................................................................................C-11 C.4 K-O..............................................................................................................................................................C-16 C.5 P-T................................................................................................................................................................C-22 C.6 U-Z...............................................................................................................................................................C-31
Issue 02 (2011-01-20)
xxxix
Figures
Figures
Figure 1-1 DCN....................................................................................................................................................1-4 Figure 1-2 RS-232/Ethernet protocol converter solution (in the case that all the edge equipment is in the same domain)..................................................................................................................................................................1-8 Figure 1-3 RS-232/Ethernet protocol converter solution (in the case that the edge equipment is in multiple domains) ...............................................................................................................................................................................1-9 Figure 1-4 64 k/Ethernet protocol converter solution (in the case that all the edge equipment is in the same domain) .............................................................................................................................................................................1-10 Figure 1-5 64 k/Ethernet protocol converter solution (in the case that all the edge equipment is in multiple domains) .............................................................................................................................................................................1-10 Figure 1-6 E1/Ethernet protocol converter solution (in the case that all the edge equipment is in the same domain) .............................................................................................................................................................................1-11 Figure 1-7 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-12 Figure 1-8 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-12 Figure 1-9 E1/Ethernet protocol converter solution (shared E1).......................................................................1-13 Figure 1-10 E1/Ethernet protocol converter solution (shared BTS service channel).........................................1-14 Figure 1-11 Hybrid Use Solution of Protocol Converters .................................................................................1-15 Figure 1-12 Networking diagram of HWECC...................................................................................................1-16 Figure 1-13 HWECC protocol stack architecture..............................................................................................1-17 Figure 1-14 Networking for the extended ECC (using a network cable)...........................................................1-20 Figure 1-15 Networking for the extended ECC (using a hub)...........................................................................1-21 Figure 1-16 Networking for the extended ECC (using network cables to connect NEs in series)....................1-21 Figure 1-17 Extended ECC network (multi level extended ECC).....................................................................1-23 Figure 1-18 Networking example for establishing ECC routes.........................................................................1-26 Figure 1-19 Realization principle of message transfer (HWECC).....................................................................1-27 Figure 1-20 Networking diagram of the HWECC solution...............................................................................1-33 Figure 1-21 Allocation of IDs/IP addresses for all the NEs...............................................................................1-34 Figure 1-22 Application of the IP over DCC solution.......................................................................................1-40 Figure 1-23 IP over DCC protocol stack architecture........................................................................................1-41 Figure 1-24 OSPF areas and router type............................................................................................................1-46 Figure 1-25 Application example of the proxy ARP.........................................................................................1-48 Figure 1-26 Realization principle of message transfer (gateway mode)............................................................1-53 Figure 1-27 Realization principle of message transfer (direct connection mode)..............................................1-54
Issue 02 (2011-01-20)
xli
Figures
OptiX RTN 980 Radio Transmission System Feature Description (U2000) Figure 1-28 Planning diagram of NE IP addresses and routes (a network consisting of the OptiX equipment only, the NMS and GNE being in the same network segment)...................................................................................1-56
Figure 1-29 Planning diagram of NE IP addresses and routes (a network consisting of the OptiX equipment only, the NMS and GNE being in different network segments)..................................................................................1-57 Figure 1-30 Planning diagram of NE IP addresses and routes (a network consisting of the OptiX equipment and third-party equipment, the third-party NMS and GNE being in the same network segment)............................1-58 Figure 1-31 Planning diagram of NE IP addresses and routes (a network consisting of the OptiX equipment and third-party equipment, the third-party NMS and OptiX GNE being in different network segments)................1-59 Figure 1-32 Planning diagram of NE IP addresses and routes (a network consisting of stacked NEs).............1-60 Figure 1-33 Planning diagram of NE IP addresses and routes (a network where the IP addresses of the NEs being in the same network segment, the NMSs and NEs being in the same network segment)...................................1-61 Figure 1-34 Planning diagram of NE IP addresses and routes (a network where the IP addresses of the NEs being in the same network segment, the third-party NMS and NEs being in different network segments).................1-62 Figure 1-35 Networking diagram.......................................................................................................................1-65 Figure 1-36 Allocation of IDs/IP addresses for all the NEs...............................................................................1-66 Figure 1-37 Application of the OSI over DCC solution....................................................................................1-73 Figure 1-38 OSI over DCC protocol stack architecture.....................................................................................1-74 Figure 1-39 Format of the NSAP address..........................................................................................................1-75 Figure 1-40 Layered routes of IS-IS protocol routes (L2 not consecutive).......................................................1-76 Figure 1-41 Application example of the OSI tunnel..........................................................................................1-77 Figure 1-42 Realization principle of message transferring (gateway mode).....................................................1-81 Figure 1-43 Realization principle of message transferring (direct connection mode).......................................1-82 Figure 1-44 Networking diagram.......................................................................................................................1-86 Figure 1-45 Allocation of NE areas...................................................................................................................1-87 Figure 1-46 DCC bytes transparent transmission solution when the OptiX equipment is at the edge of a network (1)........................................................................................................................................................................1-92 Figure 1-47 DCC bytes transparent transmission solution when the OptiX equipment is at the edge of a network (2)........................................................................................................................................................................1-93 Figure 1-48 DCC bytes transparent transmission solution when the OptiX equipment is in the center of a network (1)........................................................................................................................................................................1-93 Figure 1-49 DCC bytes transparent transmission solution when the OptiX equipment is in the center of a network (2)........................................................................................................................................................................1-94 Figure 1-50 Realization principle of the DCC bytes transparent transmission..................................................1-96 Figure 1-51 Networking diagram of the DCC bytes transparent transmission solution....................................1-99 Figure 1-52 Allocation of IDs/IP addresses for all the NEs.............................................................................1-100 Figure 1-53 Networking example for the DCC transmission through the external clock interface solution (direct access mode).....................................................................................................................................................1-105 Figure 1-54 Networking example for the DCC transmission through the external clock interface solution (indirect access mode).....................................................................................................................................................1-105 Figure 1-55 Realization principle of the DCC transmission through the external clock interface..................1-108 Figure 1-56 Networking example for the DCC transmission through the external clock interface solution ...........................................................................................................................................................................1-109 Figure 1-57 Application of the inband DCN solution......................................................................................1-114 Figure 1-58 Architecture of the inband DCN protocol stack based on the TCP/IP protocol stack..................1-115 Figure 1-59 Architecture of the inband DCN protocol stack based on the HWECC protocol stack...............1-116 Figure 1-60 Access control...............................................................................................................................1-117 xlii Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 02 (2011-01-20)
Figures
Figure 1-61 Realization principle of packet forwarding..................................................................................1-121 Figure 1-62 Networking diagram of the inband DCN solution........................................................................1-126 Figure 1-63 Allocation of IDs/IP addresses for all the NEs.............................................................................1-127 Figure 2-1 1+1 HSB protection............................................................................................................................2-4 Figure 2-2 Typical configuration of one 1+1 HSB protection group...................................................................2-5 Figure 2-3 1+1 HSB realization principle (before the switching, in the transmit direction).............................2-12 Figure 2-4 1+1 HSB realization principle (before the switching, in the receive direction)...............................2-12 Figure 2-5 1+1 HSB realization principle (after the switching, in the receive direction)..................................2-13 Figure 2-6 1+1 HSB realization principle (after the switching, in the transmit direction)................................2-13 Figure 2-7 1+1 HSB realization principle (before the switching, in the transmit direction).............................2-14 Figure 2-8 1+1 HSB realization principle (before the switching, in the receive direction)...............................2-15 Figure 2-9 1+1 HSB realization principle (after the switching, in the receive direction)..................................2-16 Figure 2-10 1+1 HSB realization principle (after the switching, in the transmit direction)..............................2-16 Figure 2-11 Networking diagram of 1+1 HSB protection.................................................................................2-19 Figure 2-12 1+1 FD protection...........................................................................................................................2-25 Figure 2-13 Typical configuration 1 of one 1+1 FD protection group..............................................................2-27 Figure 2-14 Typical configuration 2 of one 1+1 FD protection group..............................................................2-28 Figure 2-15 1+1 FD realization principle (before the switching, in the transmit direction)..............................2-34 Figure 2-16 1+1 FD realization principle (before the switching, in the receive direction)................................2-35 Figure 2-17 1+1 FD HSB realization principle (after the switching, in the receive direction)..........................2-36 Figure 2-18 1+1 FD HSM realization principle (after the switching, in the receive direction).........................2-36 Figure 2-19 1+1 FD realization principle (before the switching, in the transmit direction)..............................2-37 Figure 2-20 1+1 FD realization principle (before the switching, in the receive direction)................................2-38 Figure 2-21 1+1 FD HSB realization principle (after the switching, in the transmit direction)........................2-39 Figure 2-22 1+1 FD HSB realization principle (after the switching, in the receive direction)..........................2-39 Figure 2-23 1+1 FD HSM realization principle (after the switching, in the receive direction).........................2-40 Figure 2-24 Networking diagram of 1+1 FD protection....................................................................................2-43 Figure 2-25 1+1 SD protection...........................................................................................................................2-49 Figure 2-26 Typical configuration of one 1+1 SD protection group.................................................................2-51 Figure 2-27 1+1 SD realization principle (before the switching, in the transmit direction)..............................2-58 Figure 2-28 1+1 SD realization principle (before the switching, in the receive direction)................................2-59 Figure 2-29 1+1 SD HSB realization principle (after the switching, in the receive direction)..........................2-60 Figure 2-30 1+1 SD HSB realization principle (after the switching, in the transmit direction)........................2-60 Figure 2-31 1+1 SD HSM realization principle (after the switching, in the receive direction).........................2-60 Figure 2-32 1+1 SD realization principle (before the switching, in the transmit direction)..............................2-61 Figure 2-33 1+1 SD realization principle (before the switching, in the receive direction)................................2-62 Figure 2-34 1+1 SD HSB realization principle (after the switching, in the receive direction)..........................2-63 Figure 2-35 1+1 SD HSB realization principle (after the switching, in the transmit direction)........................2-63 Figure 2-36 1+1 SD HSM realization principle (after the switching, in the receive direction).........................2-64 Figure 2-37 Networking diagram of the 1+1 SD protection group....................................................................2-67 Figure 2-38 ACAP channel configuration (without the application of the XPIC technology)..........................2-73 Figure 2-39 CCDP channel configuration (with the application of the XPIC technology)...............................2-74 Issue 02 (2011-01-20) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. xliii
Figures
OptiX RTN 980 Radio Transmission System Feature Description (U2000) Figure 2-40 Single-polarized transmission.........................................................................................................2-75 Figure 2-41 CCDP transmission.........................................................................................................................2-75 Figure 2-42 Typical XPIC configuration (1)......................................................................................................2-76 Figure 2-43 Typical XPIC configuration (2)......................................................................................................2-77 Figure 2-44 Typical XPIC configuration (1+1 protection configuration)..........................................................2-78 Figure 2-45 Realization principle of the XPIC..................................................................................................2-82 Figure 2-46 Networking diagram.......................................................................................................................2-86 Figure 2-47 Board configuration........................................................................................................................2-87 Figure 2-48 N+1 protection................................................................................................................................2-95
Figure 2-49 Typical configuration of one 1+1 protection group........................................................................2-96 Figure 2-50 Typical configuration of one 2+1 protection group........................................................................2-98 Figure 2-51 Typical channel configuration of one 2+1 protection group..........................................................2-98 Figure 2-52 Typical configuration of one 3+1 protection group........................................................................2-99 Figure 2-53 Typical channel configuration of one 3+1 protection group........................................................2-100 Figure 2-54 Realization principles of the 2+1 protection (before the switching)............................................2-108 Figure 2-55 Realization principles of the 2+1 protection (after the switching)...............................................2-108 Figure 2-56 Realization principles of the 2+1 protection (before the switching)............................................2-110 Figure 2-57 Realization principles of the 2+1 protection (after the switching)...............................................2-111 Figure 2-58 Networking diagram.....................................................................................................................2-115 Figure 2-59 Relationship between the RSL and TSL.......................................................................................2-124 Figure 2-60 Realization principle of the ATPC...............................................................................................2-126 Figure 2-61 Networking diagram.....................................................................................................................2-128 Figure 2-62 Adaptive modulation....................................................................................................................2-133 Figure 2-63 Applications of E1 Service Priority..............................................................................................2-134 Figure 2-64 AM switching (before the switching)...........................................................................................2-139 Figure 2-65 AM downshift (after the switching).............................................................................................2-140 Figure 2-66 AM upshift (after the switching)..................................................................................................2-141 Figure 2-67 Networking diagram of the AM...................................................................................................2-144 Figure 3-1 Configuration of 1+1 protection of control, switching, and timing boards........................................3-3 Figure 3-2 Principle for Active and Standby Control, Switching, and Timing Boards (before Switching) ...............................................................................................................................................................................3-7 Figure 3-3 Principle for active and standby control, switching, and timing boards (after switching).................3-8 Figure 3-4 Principle for 1+1 backup between the system control units...............................................................3-9 Figure 3-5 Principle for 1+1 backup between the cross-connect/switching units..............................................3-10 Figure 3-6 Principle for 1+1 backup between the timing units..........................................................................3-11 Figure 4-1 SNCP..................................................................................................................................................4-3 Figure 4-2 SNCP service pair...............................................................................................................................4-4 Figure 4-3 Coexisting N+1 protection and SNCP................................................................................................4-5 Figure 4-4 Traffic flow after the SNCP switching and N+1 protection switching..............................................4-6 Figure 4-5 Traffic flow after the revertive SNCP switching................................................................................4-7 Figure 4-6 Traffic flow after the switching when the hold-off time is set ..........................................................4-8 Figure 4-7 Principle of converting E1_AIS alarms into TU-AIS alarms...........................................................4-14 Figure 4-8 SNCP realization principle (before the switching)...........................................................................4-17 xliv Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 02 (2011-01-20)
Figures
Figure 4-9 SNCP realization principle (after the switching)..............................................................................4-17 Figure 4-10 Networking diagram of the SNCP ring ......................................................................................... 4-20 Figure 4-11 Timeslot allocation diagram (TDM services on the Hybrid radio ring network)...........................4-21 Figure 4-12 1+1 linear MSP...............................................................................................................................4-27 Figure 4-13 1:N linear MSP...............................................................................................................................4-28 Figure 4-14 Realization principle of the 1+1 linear MSP (before the switching)..............................................4-36 Figure 4-15 Realization principle of the 1+1 linear MSP (after the switching, in single-ended mode)............ 4-36 Figure 4-16 Realization principle of the 1+1 linear MSP (after the switching, in dual-ended mode)...............4-37 Figure 4-17 Realization principle of the 1:1 linear MSP (before the switching)...............................................4-38 Figure 4-18 Realization principle of the 1:1 linear MSP (after the switching)..................................................4-38 Figure 4-19 Networking diagram of the linear MSP..........................................................................................4-40 Figure 4-20 Two-fiber bidirectional MSP ring.................................................................................................. 4-46 Figure 4-21 Principle of a two-fiber bidirectional MSP ring (before switching)...............................................4-53 Figure 4-22 Principle of a two-fiber bidirectional MSP ring (after switching)..................................................4-53 Figure 4-23 Two-fiber bidirectional MSP ring.................................................................................................. 4-56 Figure 5-1 Packet plane........................................................................................................................................5-4 Figure 5-2 Networking diagram of the VLAN application..................................................................................5-5 Figure 5-3 Format of a tagged frame....................................................................................................................5-7 Figure 5-4 Model of VLAN-based E-Line services.............................................................................................5-9 Figure 5-5 Model of E-LAN services based on 802.1q bridge.......................................................................... 5-10 Figure 5-6 Application of VLAN forwarding tables to E-Line services............................................................5-11 Figure 5-7 Configuration flow chart (VLAN-based E-Line services)............................................................... 5-14 Figure 5-8 Configuration flow chart (IEEE 802.1q bridge-based E-LAN services)..........................................5-21 Figure 5-9 Application of QinQ in E-Line services...........................................................................................5-30 Figure 5-10 Format of the Ethernet frame with only a C-TAG......................................................................... 5-31 Figure 5-11 Format of the Ethernet frame with a C-TAG and an S-TAG ........................................................5-32 Figure 5-12 Format of the Ethernet frame with only an S-TAG........................................................................5-32 Figure 5-13 Typical application of service model 1...........................................................................................5-34 Figure 5-14 Typical application of service model 2...........................................................................................5-35 Figure 5-15 Typical application of service model 3...........................................................................................5-35 Figure 5-16 Typical application of service model 4...........................................................................................5-36 Figure 5-17 Model of E-LAN services based on 802.1ad bridge.......................................................................5-37 Figure 5-18 EVPL (QinQ) services....................................................................................................................5-40 Figure 5-19 EVPLAN (802.1ad Bridge) Service Example................................................................................5-41 Figure 5-20 Configuration flow chart (QinQ-based E-Line services)................................................................5-43 Figure 5-21 Configuration flow chart (IEEE 802.1ad bridge-based E-LAN services)......................................5-50 Figure 5-22 Application of Layer 2 switching...................................................................................................5-60 Figure 5-23 802.1d bridge..................................................................................................................................5-62 Figure 5-24 802.1q bridge..................................................................................................................................5-62 Figure 5-25 802.1ad bridge................................................................................................................................5-63 Figure 5-26 Model of E-LAN services based on the 802.1d bridge.................................................................. 5-64 Figure 5-27 Model of E-LAN services based on 802.1q bridge........................................................................ 5-65 Issue 02 (2011-01-20) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. xlv
Figures
OptiX RTN 980 Radio Transmission System Feature Description (U2000) Figure 5-28 Model of E-LAN services based on 802.1ad bridge.......................................................................5-67 Figure 5-29 Split horizon group.........................................................................................................................5-68
Figure 5-30 Configuration flow chart (IEEE 802.1d bridge-based E-LAN services)........................................5-72 Figure 5-31 Configuration flow chart (IEEE 802.1q bridge-based E-LAN services)........................................5-80 Figure 5-32 Configuration flow chart (IEEE 802.1ad bridge-based E-LAN services)......................................5-88 Figure 5-33 Implementation of the ERPS..........................................................................................................5-98 Figure 5-34 Protection instance of the ERPS.....................................................................................................5-99 Figure 5-35 Frame format of an R-APS message............................................................................................5-101 Figure 5-36 Frame format of the R-APS specific information.........................................................................5-101 Figure 5-37 Realization principle of the ERPS (in the case of a fault on a non-RPL link).............................5-108 Figure 5-38 Realization principle of the ERPS (in the case of a fault on an RPL link)...................................5-109 Figure 5-39 Networking diagram.....................................................................................................................5-112 Figure 5-40 Diagram of the STP......................................................................................................................5-116 Figure 5-41 Limitations of the STP/RSTP.......................................................................................................5-118 Figure 5-42 Improvement in the MSTP...........................................................................................................5-119 Figure 5-43 Typical Application of the MSTP on the OptiX RTN 980...........................................................5-120 Figure 5-44 Networking diagram.....................................................................................................................5-129 Figure 5-45 Link aggregation group................................................................................................................5-134 Figure 5-46 Frame format of the LACP packet ...............................................................................................5-140 Figure 5-47 Application of the LACP protocol................................................................................................5-142 Figure 5-48 Networking diagram.....................................................................................................................5-145 Figure 5-49 Typical application of LPT...........................................................................................................5-149 Figure 5-50 Network diagram of point-to-point LPT......................................................................................5-150 Figure 5-51 Network diagram of point-to-multipoint LPT..............................................................................5-152 Figure 5-52 Point-to-point LPT switching during an access-side fault period................................................5-155 Figure 5-53 Point-to-point LPT switching after rectification of an access-side fault......................................5-156 Figure 5-54 Point-to-point LPT switching during a network-side fault period................................................5-156 Figure 5-55 Point-to-point LPT switching after rectification of a network-side fault.....................................5-157 Figure 5-56 Point-to-multipoint LPT switching during an access-side fault period........................................5-157 Figure 5-57 Point-to-multipoint LPT switching after rectification of an access-side fault..............................5-158 Figure 5-58 Point-to-multipoint LPT switching during a network-side fault period.......................................5-158 Figure 5-59 Point-to-multipoint LPT switching after rectification of a network-side fault.............................5-159 Figure 5-60 Configuration flow chart..............................................................................................................5-159 Figure 5-61 Network diagram of LPT (traversing an L2 network)..................................................................5-162 Figure 5-62 Network diagram of LPT (traversing a PSN)...............................................................................5-166 Figure 5-63 FIFO queue...................................................................................................................................5-170 Figure 5-64 Prioritized queues.........................................................................................................................5-170 Figure 5-65 DiffServ model.............................................................................................................................5-173 Figure 5-66 Mappings between packet priorities and PHBs............................................................................5-174 Figure 5-67 CAR processing............................................................................................................................5-180 Figure 5-68 Processing of traffic shaping........................................................................................................5-181 Figure 5-69 Processing of traffic shaping........................................................................................................5-182 xlvi Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 02 (2011-01-20)
Figures
Figure 5-70 SP queues......................................................................................................................................5-183 Figure 5-71 WRR scheduling algorithm..........................................................................................................5-184 Figure 5-72 SP+WRR scheduling algorithm....................................................................................................5-185 Figure 5-73 QoS model for Native ETH services............................................................................................5-185 Figure 5-74 QoS model for ETH/TDM/ATM PWE3 services (UNI to NNI).................................................5-187 Figure 5-75 QoS model for ETH/TDM/ATM PWE3 services (NNI to NNI).................................................5-187 Figure 5-76 QoS model for ETH/TDM/ATM PWE3 services (NNI to UNI).................................................5-188 Figure 5-77 Basic working principle of the token bucket algorithm................................................................5-196 Figure 5-78 Basic working principle of the CAR algorithm............................................................................5-197 Figure 5-79 Basic working principle of the algorithm used by traffic shaping................................................5-198 Figure 5-80 Basic working principle of the algorithm used by traffic shaping................................................5-199 Figure 5-81 Network diagram..........................................................................................................................5-202 Figure 5-82 ETH-OAM solution......................................................................................................................5-208 Figure 5-83 Logical diagram of maintenance domain layers ..........................................................................5-211 Figure 5-84 IEEE 802.1ag OAMPDU.............................................................................................................5-218 Figure 5-85 Continuity check diagram.............................................................................................................5-220 Figure 5-86 Loopback test diagram..................................................................................................................5-220 Figure 5-87 LT test diagram.............................................................................................................................5-221 Figure 5-88 IEEE 802.3ah OAMPDU.............................................................................................................5-222 Figure 5-89 Packet format of the information OAMPDU...............................................................................5-224 Figure 5-90 Packet format of the event notification OAMPDU......................................................................5-228 Figure 5-91 Packet format of the loopback control OAMPDU.......................................................................5-229 Figure 5-92 Networking diagram of the IEEE 802.1ag OAM.........................................................................5-237 Figure 5-93 Information about the MPs that belong to different VLANs........................................................5-238 Figure 5-94 Networking diagram of the IEEE 802.3ah OAM.........................................................................5-244 Figure 5-95 Networking diagram.....................................................................................................................5-267 Figure 6-1 Typical MPLS application..................................................................................................................6-4 Figure 6-2 MPLS network architecture................................................................................................................6-5 Figure 6-3 Classification of LSRs on an LSP......................................................................................................6-6 Figure 6-4 Bearer mode for MPLS packets..........................................................................................................6-8 Figure 6-5 LSP traversing a Layer 2 network......................................................................................................6-9 Figure 6-6 Format of the MPLS label..................................................................................................................6-9 Figure 6-7 MPLS label stack..............................................................................................................................6-10 Figure 6-8 MPLS packet forwarding process.....................................................................................................6-13 Figure 6-9 Configuration flow chart (MPLS tunnels)........................................................................................6-15 Figure 6-10 Typical application of MPLS OAM...............................................................................................6-22 Figure 6-11 Format of a CV packet....................................................................................................................6-24 Figure 6-12 Format of an FFD packet................................................................................................................6-25 Figure 6-13 Format of a BDI packet..................................................................................................................6-27 Figure 6-14 Typical application of the BDI packet............................................................................................6-28 Figure 6-15 Format of an FDI packet.................................................................................................................6-29 Figure 6-16 Typical application of the FDI packet............................................................................................6-30 Issue 02 (2011-01-20) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. xlvii
Figures
OptiX RTN 980 Radio Transmission System Feature Description (U2000) Figure 6-17 Checking connectivity in MPLS OAM..........................................................................................6-32 Figure 6-18 Network diagram of the MPLS OAM function..............................................................................6-34 Figure 6-19 Typical application of LSP ping.....................................................................................................6-38
Figure 6-20 Typical application of LSP traceroute............................................................................................6-39 Figure 6-21 Checking connectivity in LSP ping................................................................................................6-43 Figure 6-22 Checking connectivity in LSP traceroute.......................................................................................6-44 Figure 6-23 Network diagram of the LSP ping function....................................................................................6-47 Figure 6-24 Application example of MPLS APS...............................................................................................6-51 Figure 6-25 Principle of the single-ended switching..........................................................................................6-57 Figure 6-26 Principle of the dual-ended switching............................................................................................6-58 Figure 6-27 Network diagram of MPLS APS....................................................................................................6-62 Figure 6-28 Typical application of PWE3.........................................................................................................6-66 Figure 6-29 PWE3 network reference model.....................................................................................................6-67 Figure 6-30 PWE3 protocol reference model.....................................................................................................6-69 Figure 6-31 PWE3 encapsulation format...........................................................................................................6-70 Figure 6-32 MS-PW network reference model..................................................................................................6-71 Figure 6-33 SS-PW application..........................................................................................................................6-72 Figure 6-34 MS-PW application........................................................................................................................6-72 Figure 6-35 Format of a VCCV message based on control word......................................................................6-73 Figure 6-36 Format of a VCCV message based on OAM alert label.................................................................6-74 Figure 6-37 SS-PW packet forwarding process.................................................................................................6-77 Figure 6-38 MS-PW packet forwarding process of MS-PW.............................................................................6-78 Figure 6-39 Typical application of TDM PWE3 (CESoPSN mode).................................................................6-80 Figure 6-40 Formats of timeslot 0 in E1 frames................................................................................................6-82 Figure 6-41 Encapsulation format of a SAToP packet.......................................................................................6-83 Figure 6-42 Encapsulation format of a CESoPSN packet..................................................................................6-85 Figure 6-43 Working principle of the data jitter buffer......................................................................................6-87 Figure 6-44 CES alarm transparent transmission between AC sides.................................................................6-88 Figure 6-45 CES alarm transparent transmission from the NNI side to the AC side.........................................6-88 Figure 6-46 Principles of CES retiming.............................................................................................................6-89 Figure 6-47 Principles of TDM PWE3 services (CESoPSN mode)..................................................................6-93 Figure 6-48 Configuration flow chart................................................................................................................6-94 Figure 6-49 Typical application of ATM PWE3 (in the one-to-one encapsulation mode)..............................6-100 Figure 6-50 Typical application of ATM PWE3 (in the N-to-one encapsulation mode).................................6-101 Figure 6-51 ATM N-to-one cell encapsulation................................................................................................6-102 Figure 6-52 ATM one-to-one cell encapsulation.............................................................................................6-104 Figure 6-53 Principles of the ATM PWE3 service (N-to-one VCC)...............................................................6-109 Figure 6-54 Configuration flow chart (ATM services on a per-NE basis).......................................................6-111 Figure 6-55 Typical application of ETH PWE3...............................................................................................6-119 Figure 6-56 Format of an ETH PWE3 packet..................................................................................................6-120 Figure 6-57 Typical application of the PW encapsulation mode.....................................................................6-123 Figure 6-58 Typical application of service model 1.........................................................................................6-125 xlviii Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 02 (2011-01-20)
Figures
Figure 6-59 Typical application of service model 2.........................................................................................6-126 Figure 6-60 Typical application of service model 3.........................................................................................6-127 Figure 6-61 Principles of ETH PWE3..............................................................................................................6-129 Figure 6-62 Per-NE configuration flow chart (E-Line services carried on PWs)............................................6-130 Figure 6-63 Typical application of PW OAM..................................................................................................6-140 Figure 6-64 Continuity check principle of PW OAM......................................................................................6-145 Figure 6-65 Network diagram of the PW OAM function................................................................................6-146 Figure 6-66 Typical application of PW ping....................................................................................................6-150 Figure 6-67 Typical application of PW traceroute...........................................................................................6-151 Figure 6-68 Checking connectivity in PW ping...............................................................................................6-155 Figure 6-69 Checking connectivity in PW traceroute......................................................................................6-156 Figure 6-70 Network diagram of the PW ping function...................................................................................6-159 Figure 6-71 Application example of PW APS.................................................................................................6-163 Figure 6-72 Application example of PW APS.................................................................................................6-164 Figure 6-73 Application example of PW APS.................................................................................................6-169 Figure 6-74 Principle of the single-ended switching........................................................................................6-172 Figure 6-75 Principle of the dual-ended switching..........................................................................................6-173 Figure 6-76 Network diagram of PW APS......................................................................................................6-175 Figure 6-77 Network supporting the ATM function........................................................................................6-181 Figure 6-78 Architecture and interfaces of an ATM network..........................................................................6-182 Figure 6-79 ATM links.....................................................................................................................................6-183 Figure 6-80 VPC..............................................................................................................................................6-184 Figure 6-81 VCC..............................................................................................................................................6-184 Figure 6-82 VCCs sharing a VPC....................................................................................................................6-185 Figure 6-83 ATM switching.............................................................................................................................6-186 Figure 6-84 ATM cell structure........................................................................................................................6-186 Figure 6-85 Header structure at a UNI.............................................................................................................6-187 Figure 6-86 Header structure at an NNI...........................................................................................................6-187 Figure 6-87 Transfer of ATM cells..................................................................................................................6-192 Figure 6-88 IMA..............................................................................................................................................6-193 Figure 6-89 Typical application of the IMA technology..................................................................................6-194 Figure 6-90 IMA protocol reference model.....................................................................................................6-195 Figure 6-91 Transmission of IMA frames over three links in an IMA group..................................................6-199 Figure 6-92 Link differential delay compensation...........................................................................................6-200 Figure 6-93 IMA timing configuration reference model..................................................................................6-201 Figure 6-94 Processing of an ATM cell stream in the IMA technology..........................................................6-203 Figure 6-95 Network diagram of IMA.............................................................................................................6-205 Figure 6-96 Typical application of ATM OAM...............................................................................................6-209 Figure 6-97 Segment and end attributes of CPs...............................................................................................6-211 Figure 6-98 Directions of CPs..........................................................................................................................6-212 Figure 6-99 Principles of AIS/RDI..................................................................................................................6-217 Figure 6-100 Principles of CC..........................................................................................................................6-218 Issue 02 (2011-01-20) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. xlix
Figures
OptiX RTN 980 Radio Transmission System Feature Description (U2000) Figure 6-101 Principles of LB..........................................................................................................................6-220
Figure 6-102 Configuration flow chart............................................................................................................6-221 Figure 6-103 Network diagram........................................................................................................................6-223 Figure 6-104 Functioning point of ATM traffic management.........................................................................6-226 Figure 6-105 Illustration of basic GCRA principles........................................................................................6-234 Figure 6-106 Leaky bucket algorithm..............................................................................................................6-235 Figure 6-107 Two-level leaky bucket algorithm..............................................................................................6-236 Figure 6-108 Configuration flow chart............................................................................................................6-236 Figure 6-109 Network diagram........................................................................................................................6-238 Figure 7-1 Application of the Synchronous Ethernet...........................................................................................7-3 Figure 7-2 Realization principle of the synchronous Ethernet.............................................................................7-5 Figure 7-3 CES ACR clock solution....................................................................................................................7-9 Figure 7-4 CES ACR clock domain...................................................................................................................7-10 Figure 7-5 Principles of CES ACR clock protection.........................................................................................7-11 Figure 7-6 Typical application example of the CES ACR clock transparent transmission solution.................7-12 Figure 7-7 Implementation process on Master...................................................................................................7-14 Figure 7-8 Implementation process on Slave.....................................................................................................7-15 Figure 7-9 Network diagram of CES ACR........................................................................................................7-17 Figure A-1 Connecting the BER tester............................................................................................................A-237 Figure A-2 Networking diagram for testing the Ethernet service...................................................................A-238 Figure A-3 Connection diagram for testing the connectivity of the ATM service..........................................A-243 Figure A-4 Configuration for testing the IF 1+1 switching............................................................................A-249 Figure A-5 Configuration for testing the N+1 protection...............................................................................A-252 Figure A-6 Configuration for testing the SNCP switching.............................................................................A-255 Figure A-7 Configuration for testing the ERPS..............................................................................................A-258 Figure A-8 Connection diagram for testing the MPLS APS protection..........................................................A-261 Figure A-9 Two-fiber bidirectional MSP switching.......................................................................................A-264 Figure A-10 Configuration for testing the Ethernet service............................................................................A-268
Issue 02 (2011-01-20)
Tables
Tables
Table 1-1 Specifications of HWECC.................................................................................................................1-23 Table 1-2 Hardware and version support...........................................................................................................1-24 Table 1-3 Procedure for the HWECC solution...................................................................................................1-31 Table 1-4 OSPF Packet Type.............................................................................................................................1-44 Table 1-5 OSPF LSA type..................................................................................................................................1-44 Table 1-6 OSPF router type................................................................................................................................1-46 Table 1-7 Specifications of IP over DCC...........................................................................................................1-50 Table 1-8 Hardware and version support...........................................................................................................1-51 Table 1-9 Procedure for the IP over DCC solution............................................................................................1-63 Table 1-10 Specifications of OSI over DCC......................................................................................................1-79 Table 1-11 Hardware and version support.........................................................................................................1-80 Table 1-12 Procedure for the OSI over DCC solution.......................................................................................1-83 Table 1-13 Specifications of DCC bytes transparent transmission solution......................................................1-94 Table 1-14 Hardware and version support.........................................................................................................1-95 Table 1-15 Procedure for the DCC bytes transparent transmission solution.....................................................1-97 Table 1-16 Specifications of DCC transmission through the external clock interface.....................................1-106 Table 1-17 Hardware and version support.......................................................................................................1-107 Table 1-18 Procedure for configuring the solution of transparently transmitting DCCs through the external clock interface.............................................................................................................................................................1-108 Table 1-19 Specifications of the inband DCN solution....................................................................................1-118 Table 1-20 Hardware and version support.......................................................................................................1-119 Table 1-21 Procedure for communications data at the near end......................................................................1-123 Table 2-1 Trigger conditions of the 1+1 HSB switching ....................................................................................2-6 Table 2-2 Trigger conditions of the automatic 1+1 HSB switching.....................................................................2-9 Table 2-3 Specifications of 1+1 HSB.................................................................................................................2-10 Table 2-4 Hardware and version support...........................................................................................................2-10 Table 2-5 Procedure for configuring the 1+1 HSB protection mode.................................................................2-17 Table 2-6 IF planning information.....................................................................................................................2-20 Table 2-7 RF planning information....................................................................................................................2-21 Table 2-8 Trigger conditions of the 1+1 FD HSB switching.............................................................................2-29 Table 2-9 Trigger conditions of the automatic HSB switching..........................................................................2-30 Table 2-10 Trigger conditions of the automatic HSM switching.......................................................................2-31 Table 2-11 Specifications of 1+1 FD.................................................................................................................2-32 Table 2-12 Hardware and version support.........................................................................................................2-33 Issue 02 (2011-01-20) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. li
Tables
OptiX RTN 980 Radio Transmission System Feature Description (U2000) Table 2-13 Procedure for configuring the 1+1 FD protection mode..................................................................2-41 Table 2-14 IF planning information...................................................................................................................2-44 Table 2-15 RF planning information..................................................................................................................2-44 Table 2-16 Trigger conditions of the 1+1 SD HSB switching...........................................................................2-52 Table 2-17 Trigger conditions of the automatic HSB switching........................................................................2-54 Table 2-18 Trigger conditions of the automatic HSM switching.......................................................................2-55 Table 2-19 Specifications of 1+1 SD.................................................................................................................2-56 Table 2-20 Hardware and version support.........................................................................................................2-57 Table 2-21 Configuration procedure of 1+1 SD protection...............................................................................2-65 Table 2-22 IF planning information...................................................................................................................2-68 Table 2-23 RF planning information..................................................................................................................2-69 Table 2-24 Specifications of XPIC.....................................................................................................................2-79 Table 2-25 Hardware and version support.........................................................................................................2-80 Table 2-26 Procedure for configuring the XPIC link.........................................................................................2-84 Table 2-27 Basic information about the radio links...........................................................................................2-88 Table 2-28 Information about the Hybrid/AM Configuration............................................................................2-88 Table 2-29 Information about the Power and ATPC .........................................................................................2-89 Table 2-30 Configuration information about the XPIC......................................................................................2-90 Table 2-31 Configuration information about the 1+1 HSB protection group....................................................2-90 Table 2-32 Switching conditions of the N+1 protection..................................................................................2-100 Table 2-33 Specifications of N+1 protection...................................................................................................2-104 Table 2-34 Hardware and version support.......................................................................................................2-106 Table 2-35 Procedure for configuring an N+1 protection group......................................................................2-113 Table 2-36 Basic information about radio links...............................................................................................2-116 Table 2-37 Information about the Hybrid/AM Configuration..........................................................................2-117 Table 2-38 Information about the power and ATPC .......................................................................................2-117 Table 2-39 Information about the N+1 (N=2) protection.................................................................................2-118 Table 2-40 Specifications of ATPC..................................................................................................................2-124 Table 2-41 Hardware and version support.......................................................................................................2-125 Table 2-42 Procedure for configuring the ATPC.............................................................................................2-127 Table 2-43 ATPC information..........................................................................................................................2-129 Table 2-44 Priorities of services at base stations..............................................................................................2-134 Table 2-45 Specifications of AM.....................................................................................................................2-136 Table 2-46 Hardware and version support.......................................................................................................2-137 Table 2-47 Configuration procedure of AM.....................................................................................................2-142 Table 2-48 AM and E1 priority planning information.....................................................................................2-144 Table 3-1 Trigger conditions of the control, switching, and timing boards 1+1 protection switching................3-4 Table 3-2 Specifications of 1+1 protection for the control, switching, and timing board....................................3-5 Table 3-3 Hardware and version support.............................................................................................................3-6 Table 4-1 SNCP switching conditions..................................................................................................................4-9 Table 4-2 Trigger conditions of the automatic SNCP switching (VC-4 services).............................................4-10 Table 4-3 Trigger conditions of the automatic SNCP switching (STM-1 services transmitted over the Integrated IP radio (Native STM-1 + Eth))..........................................................................................................................4-11
lii
Issue 02 (2011-01-20)
Tables
Table 4-4 Trigger conditions of the automatic SNCP switching (VC-3 services).............................................4-12 Table 4-5 Trigger conditions of the automatic SNCP switching (VC-12 services)...........................................4-13 Table 4-6 Trigger conditions of the automatic SNCP switching (E1 services transmitted over the Integrated IP radio (Native E1 + Eth))......................................................................................................................................4-14 Table 4-7 Specifications of SNCP......................................................................................................................4-15 Table 4-8 Hardware and version support...........................................................................................................4-16 Table 4-9 Procedure for configuring the SNCP service.....................................................................................4-18 Table 4-10 SNCP................................................................................................................................................4-21 Table 4-11 Meanings of K bytes (linear MSP)...................................................................................................4-30 Table 4-12 Bridge request code..........................................................................................................................4-31 Table 4-13 Trigger conditions of the linear MSP switching..............................................................................4-32 Table 4-14 Specifications of linear MSP............................................................................................................4-34 Table 4-15 Hardware and version support.........................................................................................................4-35 Table 4-16 Procedure for configuring a linear MSP service..............................................................................4-39 Table 4-17 Linear MSP......................................................................................................................................4-41 Table 4-18 Meanings of byte K (two-fiber bidirectional ring MSP)..................................................................4-47 Table 4-19 Bridging request code......................................................................................................................4-48 Table 4-20 Switching conditions of two-fiber bidirectional ring MSP..............................................................4-49 Table 4-21 Specifications of two-fiber bidirectional ring MSP.........................................................................4-52 Table 4-22 Hardware and version support.........................................................................................................4-52 Table 4-23 Configuration procedure for a ring MSP service.............................................................................4-55 Table 4-24 Information about ring MSP............................................................................................................4-56 Table 5-1 Processing of data frames based on different TAG attributes..............................................................5-7 Table 5-2 Models of VLAN-based E-Line services.............................................................................................5-8 Table 5-3 Model of E-LAN services based on 802.1q bridge..............................................................................5-9 Table 5-4 Specifications of VLANs...................................................................................................................5-11 Table 5-5 Hardware and version support...........................................................................................................5-12 Table 5-6 Procedures for configuring Ethernet ports.........................................................................................5-15 Table 5-7 Procedures for configuring a LAG.....................................................................................................5-17 Table 5-8 Procedures for configuring VLAN-based E-Line services................................................................5-18 Table 5-9 Procedures for configuring QoS.........................................................................................................5-18 Table 5-10 Procedures for verifying Ethernet service configurations................................................................5-19 Table 5-11 Procedures for configuring Ethernet ports.......................................................................................5-22 Table 5-12 Procedures for configuring ERPS protection...................................................................................5-23 Table 5-13 Procedures for configuring a LAG...................................................................................................5-24 Table 5-14 Procedures for configuring IEEE 802.1q bridge-based E-LAN services.........................................5-25 Table 5-15 Procedures for configuring QoS.......................................................................................................5-26 Table 5-16 Procedures for verifying Ethernet service configurations................................................................5-27 Table 5-17 Models of QinQ-based E-Line Services..........................................................................................5-33 Table 5-18 Models of E-LAN services based on 802.1ad bridge.......................................................................5-36 Table 5-19 Specifications of QinQ.....................................................................................................................5-38 Table 5-20 Hardware and version support.........................................................................................................5-39 Table 5-21 Procedures for configuring Ethernet ports.......................................................................................5-44 Issue 02 (2011-01-20) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. liii
Tables
OptiX RTN 980 Radio Transmission System Feature Description (U2000) Table 5-22 Procedures for configuring a LAG...................................................................................................5-46 Table 5-23 Procedures for configuring QinQ-based E-Line services................................................................5-47 Table 5-24 Procedures for configuring QoS.......................................................................................................5-47 Table 5-25 Procedures for verifying Ethernet service configurations................................................................5-48 Table 5-26 Procedures for configuring Ethernet ports.......................................................................................5-51 Table 5-27 Procedures for configuring ERPS protection...................................................................................5-52 Table 5-28 Procedures for configuring a LAG...................................................................................................5-53 Table 5-29 Procedures for configuring IEEE 802.1ad bridge-based E-LAN services.......................................5-54 Table 5-30 Procedures for configuring QoS.......................................................................................................5-55 Table 5-31 Procedures for verifying Ethernet service configurations................................................................5-56 Table 5-32 Bridges.............................................................................................................................................5-61 Table 5-33 Model of E-LAN services based on the 802.1d bridge....................................................................5-63 Table 5-34 Model of E-LAN services based on 802.1q bridge..........................................................................5-64 Table 5-35 Models of E-LAN services based on 802.1ad bridge.......................................................................5-66 Table 5-36 Specifications of Layer 2 switching.................................................................................................5-69 Table 5-37 Hardware and version support.........................................................................................................5-70 Table 5-38 Procedures for configuring Ethernet ports.......................................................................................5-73 Table 5-39 Procedures for configuring a LAG...................................................................................................5-75 Table 5-40 Procedures for configuring ERPS protection...................................................................................5-76 Table 5-41 Procedures for configuring IEEE 802.1d-bridge-based E-LAN services........................................5-76 Table 5-42 Procedures for configuring QoS.......................................................................................................5-77 Table 5-43 Procedures for verifying Ethernet service configurations................................................................5-78 Table 5-44 Procedures for configuring Ethernet ports.......................................................................................5-81 Table 5-45 Procedures for configuring ERPS protection...................................................................................5-82 Table 5-46 Procedures for configuring a LAG...................................................................................................5-83 Table 5-47 Procedures for configuring IEEE 802.1q bridge-based E-LAN services.........................................5-84 Table 5-48 Procedures for configuring QoS.......................................................................................................5-85 Table 5-49 Procedures for verifying Ethernet service configurations................................................................5-86 Table 5-50 Procedures for configuring Ethernet ports.......................................................................................5-89 Table 5-51 Procedures for configuring ERPS protection...................................................................................5-90 Table 5-52 Procedures for configuring a LAG...................................................................................................5-91 Table 5-53 Procedures for configuring IEEE 802.1ad bridge-based E-LAN services.......................................5-92 Table 5-54 Procedures for configuring QoS.......................................................................................................5-93 Table 5-55 Procedures for verifying Ethernet service configurations................................................................5-94 Table 5-56 Description of each field in the R-APS specific information.........................................................5-101 Table 5-57 Trigger conditions of the ERPS.....................................................................................................5-104 Table 5-58 Specifications of ERPS..................................................................................................................5-105 Table 5-59 Hardware and version support.......................................................................................................5-107 Table 5-60 Procedure for configuring the ERPS..............................................................................................5-111 Table 5-61 Configuration information about the ERPS protection instance....................................................5-113 Table 5-62 Configuration information about the ERPS parameters.................................................................5-113 Table 5-63 Specifications of STP.....................................................................................................................5-123
liv
Issue 02 (2011-01-20)
Tables
Table 5-64 Hardware and version support.......................................................................................................5-124 Table 5-65 Procedure for configuring the MSTP.............................................................................................5-128 Table 5-66 Parameters of an MSTP port group................................................................................................5-130 Table 5-67 Bridge parameters..........................................................................................................................5-130 Table 5-68 CIST Parameter..............................................................................................................................5-131 Table 5-69 Switching Conditions.....................................................................................................................5-137 Table 5-70 Specifications of LAGs..................................................................................................................5-137 Table 5-71 Hardware and version support.......................................................................................................5-139 Table 5-72 Parameter Description....................................................................................................................5-141 Table 5-73 Procedure for configuring the LAG...............................................................................................5-144 Table 5-74 LAG information............................................................................................................................5-145 Table 5-75 Specifications for LPT...................................................................................................................5-153 Table 5-76 Hardware and version support.......................................................................................................5-153 Table 5-77 Procedures for configuring LPT for point-to-point services..........................................................5-160 Table 5-78 Procedures for configuring LPT for point-to-multipoint services.................................................5-161 Table 5-79 Configuration information of NE1.................................................................................................5-162 Table 5-80 Configuration information of NE2.................................................................................................5-163 Table 5-81 Configuration information of NE3.................................................................................................5-163 Table 5-82 Configuration information of LPT.................................................................................................5-164 Table 5-83 Configuration information of NE1.................................................................................................5-166 Table 5-84 Configuration information of NE2.................................................................................................5-166 Table 5-85 Configuration information of NE3.................................................................................................5-167 Table 5-86 Configuration information of LPT.................................................................................................5-167 Table 5-87 Service types and QoS requirements..............................................................................................5-172 Table 5-88 Mappings from priorities of ingress packets to PHBs at port 1.....................................................5-174 Table 5-89 Mappings from priorities of ingress packets to PHBs at port 2.....................................................5-174 Table 5-90 Mappings from priorities of egress packets to PHBs at port 3......................................................5-175 Table 5-91 Default mappings from priorities of ingress packets to PHBs.......................................................5-175 Table 5-92 Default mappings from PHBs to priorities of egress packets........................................................5-176 Table 5-93 Mappings between ATM service categories and PHBs.................................................................5-178 Table 5-94 QoS technologies applicable to each QoS application point in the QoS model for Native ETH services ...........................................................................................................................................................................5-186 Table 5-95 QoS technologies applicable to each QoS application point in the QoS model for ETH/TDM/ATM PWE3 services (UNI to NNI)............................................................................................................................5-188 Table 5-96 QoS technologies applicable to each QoS application point in the QoS model for ETH/TDM/ATM PWE3 services (NNI to NNI)............................................................................................................................5-190 Table 5-97 QoS technologies applicable to each QoS application point in the QoS model for ETH/TDM/ATM PWE3 services (NNI to UNI)............................................................................................................................5-191 Table 5-98 QoS specifications..........................................................................................................................5-192 Table 5-99 Hardware and version support.......................................................................................................5-195 Table 5-100 Procedure for configuring QoS for native ETH services.............................................................5-200 Table 5-101 Procedure for configuring QoS for ETH PWE3 services............................................................5-201 Table 5-102 Mappings between service categories and PHBs.........................................................................5-203 Issue 02 (2011-01-20) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. lv
Tables
OptiX RTN 980 Radio Transmission System Feature Description (U2000) Table 5-103 Queue scheduling mode...............................................................................................................5-204 Table 5-104 IEEE 802.1ag ETH-OAM operations and application scenarios.................................................5-212 Table 5-105 IEEE 802.3ah OAM operations and application scenarios..........................................................5-213 Table 5-106 Specifications of ETH-OAM (IEEE 802.1ag).............................................................................5-216 Table 5-107 Specifications of ETH-OAM (IEEE 802.3ah).............................................................................5-216 Table 5-108 Hardware and version support.....................................................................................................5-217 Table 5-109 Mapping between the OAM type values and OAM packet types................................................5-219 Table 5-110 Mapping between the Code values and OMA packet types.........................................................5-223 Table 5-111 Details of OAM configuration bytes............................................................................................5-225 Table 5-112 Mapping between the OAM working modes and the OAM capability.......................................5-227 Table 5-113 Flow for configuring the 802.1ag OAM service..........................................................................5-232 Table 5-114 Description of the configuration flow of the 802.3ah OAM service...........................................5-236 Table 5-115 Information about the MD...........................................................................................................5-238 Table 5-116 Information about the MA...........................................................................................................5-238 Table 5-117 Information about the MEP..........................................................................................................5-239 Table 5-118 Information about the remote MEP..............................................................................................5-239 Table 5-119 Information about the MIP...........................................................................................................5-240 Table 5-120 Information about the LT test......................................................................................................5-240 Table 5-121 Parameters of the OAM...............................................................................................................5-244 Table 5-122 Error frame monitoring information of the OAM........................................................................5-245 Table 5-123 List of RMON alarm entries........................................................................................................5-252 Table 5-124 List of RMON alarm entries........................................................................................................5-252 Table 5-125 Packet-Plane RMON Performance Entry List.............................................................................5-253 Table 5-126 Specifications of RMON..............................................................................................................5-262 Table 5-127 Hardware and version support.....................................................................................................5-263 Table 5-128 Procedure of configuring the RMON...........................................................................................5-266 Table 6-1 LSP types.............................................................................................................................................6-6 Table 6-2 Specifications for MPLS....................................................................................................................6-10 Table 6-3 Hardware and version support...........................................................................................................6-12 Table 6-4 NHLFE for NE A...............................................................................................................................6-13 Table 6-5 NHLFE for NE B...............................................................................................................................6-14 Table 6-6 NHLFE of NE D................................................................................................................................6-14 Table 6-7 Procedure for setting UNI port attributes...........................................................................................6-16 Table 6-8 Procedure for configuring an MPLS tunnel.......................................................................................6-17 Table 6-9 Procedure for configuring protection for MPLS tunnels...................................................................6-18 Table 6-10 Procedure for configuring the QoS policy.......................................................................................6-19 Table 6-11 Procedure for verifying created MPLS tunnels................................................................................6-20 Table 6-12 Format differences between an FFD packet and a CV packet.........................................................6-25 Table 6-13 LSP defect types...............................................................................................................................6-26 Table 6-14 Format differences between an FDI packet and a BDI packet.........................................................6-29 Table 6-15 Specifications for MPLS OAM........................................................................................................6-30 Table 6-16 Hardware and version support.........................................................................................................6-31
lvi
Issue 02 (2011-01-20)
Tables
Table 6-17 Flow for configuring MPLS OAM..................................................................................................6-33 Table 6-18 Differences between MPLS OAM and LSP ping/traceroute...........................................................6-36 Table 6-19 Specifications for LSP ping/traceroute............................................................................................6-39 Table 6-20 Hardware and version support.........................................................................................................6-41 Table 6-21 Flow for configuring LSP ping........................................................................................................6-45 Table 6-22 Flow for configuring LSP traceroute...............................................................................................6-46 Table 6-23 Differences between MPLS OAM and LSP ping/traceroute...........................................................6-48 Table 6-24 Switching conditions for MPLS APS..............................................................................................6-53 Table 6-25 Trigger conditions for MPLS APS SF switching.............................................................................6-54 Table 6-26 Specifications for MPLS APS..........................................................................................................6-55 Table 6-27 Hardware and version support.........................................................................................................6-56 Table 6-28 Flow for configuring MPLS APS....................................................................................................6-60 Table 6-29 Formats of the control word for various services in different encapsulation modes.......................6-70 Table 6-30 Specifications for PWE3..................................................................................................................6-74 Table 6-31 Hardware and version support.........................................................................................................6-75 Table 6-32 Specifications for TDM PWE3........................................................................................................6-91 Table 6-33 Hardware and version support.........................................................................................................6-92 Table 6-34 Setting the attributes of UNI ports...................................................................................................6-94 Table 6-35 Configuring CES services................................................................................................................6-95 Table 6-36 Verifying CES services....................................................................................................................6-96 Table 6-37 Mapping relationships between ATM service categories and PHB service levels........................6-106 Table 6-38 Specifications for ATM PWE3......................................................................................................6-107 Table 6-39 Hardware and version support.......................................................................................................6-108 Table 6-40 Setting attributes of Smart E1 ports...............................................................................................6-111 Table 6-41 Setting attributes of Smart E1 ports...............................................................................................6-112 Table 6-42 Configuring an IMA group ...........................................................................................................6-113 Table 6-43 Configuring ATM QoS..................................................................................................................6-114 Table 6-44 Model of the E-Line services carried on PWs................................................................................6-124 Table 6-45 Specifications for ETH PWE3.......................................................................................................6-127 Table 6-46 Hardware and version support.......................................................................................................6-128 Table 6-47 Procedure for configuring UNI port attributes...............................................................................6-131 Table 6-48 Procedure for configuring a LAG..................................................................................................6-133 Table 6-49 Procedure for configuring UNI-NNI E-Line services carried by PWs..........................................6-134 Table 6-50 Procedure for configuring the QoS................................................................................................6-135 Table 6-51 Procedures for verifying Ethernet service configurations..............................................................6-136 Table 6-52 PW defect types..............................................................................................................................6-141 Table 6-53 Specifications for PW OAM..........................................................................................................6-142 Table 6-54 Hardware and version support.......................................................................................................6-144 Table 6-55 Flow for configuring PW OAM.....................................................................................................6-145 Table 6-56 Differences between MPLS OAM and PW OAM.........................................................................6-148 Table 6-57 Specifications for PW ping/traceroute...........................................................................................6-151 Table 6-58 Hardware and version support.......................................................................................................6-154 Issue 02 (2011-01-20) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. lvii
Tables
OptiX RTN 980 Radio Transmission System Feature Description (U2000) Table 6-59 Flow for configuring PW ping.......................................................................................................6-158 Table 6-60 Flow for configuring PW traceroute..............................................................................................6-158 Table 6-61 Switching conditions for PW APS.................................................................................................6-166 Table 6-62 Trigger conditions for PW APS SF switching...............................................................................6-167 Table 6-63 Specifications for PW APS............................................................................................................6-170 Table 6-64 Hardware and version support.......................................................................................................6-170 Table 6-65 Flow for configuring PW APS.......................................................................................................6-174 Table 6-66 Planning information about PW APS............................................................................................6-176 Table 6-67 Planning information about a protection PW.................................................................................6-176 Table 6-68 Planning information about a PW APS protection group..............................................................6-176 Table 6-69 Planning information about slave protection pairs.........................................................................6-177 Table 6-70 Differences between PW APS and MPLS APS.............................................................................6-179 Table 6-71 Specifications for ATM..................................................................................................................6-190 Table 6-72 Hardware and version support.......................................................................................................6-191 Table 6-73 Filler cell format.............................................................................................................................6-195 Table 6-74 ICP cell format...............................................................................................................................6-196 Table 6-75 Specifications for IMA...................................................................................................................6-201 Table 6-76 Hardware and version support.......................................................................................................6-202 Table 6-77 Information about configuring an IMA group...............................................................................6-204 Table 6-78 ATM/IMA planning information (NE1)........................................................................................6-205 Table 6-79 OAM levels....................................................................................................................................6-210 Table 6-80 AIS/RDI functions.........................................................................................................................6-213 Table 6-81 CC functions...................................................................................................................................6-214 Table 6-82 LB functions...................................................................................................................................6-214 Table 6-83 Specifications for ATM OAM.......................................................................................................6-215 Table 6-84 Hardware and version support.......................................................................................................6-216 Table 6-85 ATM traffic parameters..................................................................................................................6-227 Table 6-86 ATM service categories and ATM traffic parameters...................................................................6-228 Table 6-87 Mapping relationships between ATM service categories, ATM traffic category descriptors, and traffic parameters.........................................................................................................................................................6-230 Table 6-88 Specifications for ATM traffic management.................................................................................6-232 Table 6-89 Hardware and version support.......................................................................................................6-233 Table 6-90 Description of basic GCRA principles...........................................................................................6-234 Table 6-91 ATM policy information................................................................................................................6-238 Table 7-1 Specifications of synchronous Ethernet...............................................................................................7-3 Table 7-2 Hardware and version support.............................................................................................................7-4 Table 7-3 Flow for configuring clocks.................................................................................................................7-5 Table 7-4 Specifications for CES ACR..............................................................................................................7-12 Table 7-5 Hardware and version support...........................................................................................................7-14 Table 7-6 Flow for configuring CES ACR.........................................................................................................7-16 Table 7-7 Planning information about clock extraction on Master....................................................................7-17 Table 7-8 Planning information about the primary clock for ACR clock domain.............................................7-17 Table 7-9 Planning information about the ACR clock domain..........................................................................7-18
lviii
Issue 02 (2011-01-20)
Tables
Table B-1 Parameters on the main interface....................................................................................................B-105 Table B-2 Methods used by Ethernet interfaces to process data frames.........................................................B-118 Table B-3 Data frame processing....................................................................................................................B-128 Table B-4 Service direction of UNI-UNI........................................................................................................B-166 Table B-5 Service direction of UNI-NNI (carried by PWs)............................................................................B-171 Table B-6 Service direction of UNI-NNI (carried by QinQ links)..................................................................B-174 Table B-7 Service direction of NNI-NNI........................................................................................................B-176 Table B-8 CES services...................................................................................................................................B-342 Table B-9 E-Line services...............................................................................................................................B-342 Table B-10 ATM services................................................................................................................................B-343 Table B-11 CES services.................................................................................................................................B-343 Table B-12 E-Line services.............................................................................................................................B-344 Table B-13 ATM services................................................................................................................................B-345 Table B-14 ATM services................................................................................................................................B-350 Table B-15 CES services.................................................................................................................................B-375 Table B-16 E-Line services.............................................................................................................................B-376 Table B-17 ATM services................................................................................................................................B-377 Table B-18 CES services.................................................................................................................................B-378 Table B-19 E-Line services.............................................................................................................................B-379 Table B-20 ATM services................................................................................................................................B-379 Table B-21 CES services.................................................................................................................................B-385 Table B-22 E-Line services.............................................................................................................................B-386 Table B-23 ATM services................................................................................................................................B-387 Table B-24 CES services.................................................................................................................................B-388 Table B-25 E-Line services.............................................................................................................................B-389 Table B-26 ATM services................................................................................................................................B-389 Table B-27 Mapping relationship between ATM service types, traffic types, and traffic parameters............B-434 Table B-28 Mapping relationship between ATM service types, ATM traffic types, and traffic parameters. .B-439 Table B-29 ATM services................................................................................................................................B-453
Issue 02 (2011-01-20)
lix
1 DCN Features
1
About This Chapter
DCN Features
This chapter describes the DCN and various DCN solutions provided by the OptiX RTN 980. 1.1 Introduction to the DCN The network management system (NMS) communicates with a transmission network element (NE) through the data communication network (DCN) to manage and maintain the NE. 1.2 HWECC Solution Using the HWECC solution, NEs use unified DCCs to transmit the data of the HWECC protocol. In this manner, the NMS can manage NEs. 1.3 IP over DCC Solution Using the IP over DCC solution, NEs use unified DCCs to transmit the data of the TCP/IP protocol. In this manner, the NMS can manage NEs. The IP over DCC solution applies to a network that is comprised of the OptiX transmission equipment and the third-party equipment that supports the IP over DCC function. This solution can be adopted when the equipment in the center of the network needs to provide an NM message transmission path over IP for the NE at the edge of the network. 1.4 OSI over DCC Solution Using the OSI over DCC solution, NEs use unified DCCs to transmit the data of the TCP/OSI protocol. In this manner, the NMS can manage NEs. The OSI over DCC solution applies to a network that is comprised of the OptiX equipment and the third-party equipment that supports the OSI over DCC function. 1.5 DCC Bytes Transparent Transmission Solution Using the DCC bytes transparent transmission solution, vendors use different DCCs to transmit data. In this manner, communication of NM messages is realized when the vendors' equipment is used together with third-party equipment to form a network. 1.6 DCC Transmission Through the External Clock Interface Solution Using the DCC transmission through the external clock interface solution, DCC bytes are placed in a specified E1 and then transmitted through third-party network. In this case, the transmission bandwidth of one E1 is occupied. Hence, this solution is adopted only when a PDH network or a network that does not support transparent transmission of DCC bytes exists on the transmission path of NM messages.
Issue 02 (2011-01-20) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 1-1
1 DCN Features
1.7 Inband DCN Solution With the inband DCN solution, certain service bandwidths are used to transmit the NM message between the NEs. This solution is applicable when the network is comprised of the OptiX RTN 980 equipment and the OptiX packet transmission equipment.
1-2
Issue 02 (2011-01-20)
1 DCN Features
1.1 Introduction to the DCN

The network management system (NMS) communicates with a transmission network element (NE) through the data communication network (DCN) to manage and maintain the NE. 1.1.1 Constitution 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 an external DCN, and the DCN between NEs is called an internal DCN. 1.1.2 Huawei DCN Solution For a variety of networks comprised of the transmission equipment, the OptiX transmission equipment of Huawei provides multiple DCN solutions. 1.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.
1.1.1 Constitution 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 an external DCN, and the DCN between NEs is called an internal DCN.
Issue 02 (2011-01-20)
1-3
1 DCN Features
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 is comprised of data communication equipment, such as LAN switches and routers, is required to connect the NMS and the NEs. The external DCN involves data communication knowledge. Hence, no detailed description is provided in this document. Unless otherwise specified, the DCN mentioned in this document refers to the internal DCN.
Internal DCN
In an internal DCN, the NM message supported by the OptiX RTN 980 can be transmitted in the following manner:
1-4
Issue 02 (2011-01-20)
1 DCN Features
l l l l l l l
Using one Huawei-defined DCC byte in the microwave frame to transmit NM message, if the capacity of the PDH microwave is lower than 16xE1. Using three Huawei-defined DCC bytes in the microwave frame to transmit NM message, if the capacity of the PDH microwave is not lower than 16xE1. Using the D1-D3, D4-D12, or D1-D12 bytes in the SDH microwave frame and the SDH frame to transmit NM message. Using three Huawei-defined bytes in the Integrated IP radio frame to transmit NM message. Using the Ethernet NM interface or NE cascade interface to transmit NM message. Using the DCC bytes that are transmitted through the external clock interface to transmit NM message over an SDH/PDH network. Supporting the inband DCN function, and using the Ethernet service bandwidth to transmit NM message through the hybrid microwave port or FE/GE port.
NOTE
l The inband DCN refers to a DCN networking mode that uses partial service bandwidth as a data communication channel. OptiX RTN 980 uses partial Ethernet service bandwidth at a Integrated IP radio port or FE/GE port to transmit NM message. l The outband DCN refers to a DCN networking mode whose data communication channel does not use service bandwidth. OptiX RTN 980 uses DCC bytes (as in the microwave frame, SDH frame, or at the external clock interface), an Ethernet NM interface, or a NE cascading interface to transmit NM message.
Gateway NE and Non-Gateway NE

Generally, a gateway NE (GNE) is connected to an NMS through a LAN/WAN. The application layer of the NMS directly communicates with the application layer of the GNE. One NMS needs to be connected to one or more GNEs. A non-gateway NE (non-GNE) communicates with its GNE through DCN channels between them.
1.1.2 Huawei DCN Solution

For a variety of networks comprised of the transmission equipment, the OptiX transmission equipment of Huawei provides multiple DCN solutions.
HWECC Solution
When the network is only comprised of the OptiX transmission equipment, the HWECC solution is the first choice. With this solution, NEs transmit the data that supports the HWECC protocol through DCCs. Hence, this solution features easy configuration and convenient application. The HWECC protocol is a private protocol. Hence, the network management problem cannot be solved when the network is comprised of both the OptiX equipment and third-party equipment. For details on the HWECC solution, see section 1.2 HWECC Solution.
IP over DCC solution

When the network is comprised of both the OptiX transmission equipment and the third-party equipment that supports the IP over DCC function, the IP over DCC solution is the first choice. The IP over DCC solution can also be adopted when the network is only comprised of the OptiX transmission equipment.
1 DCN Features
With the IP over DCC solution, NEs transmit the data that supports the TCP/IP protocol through DCCs. The TCP/IP is a standard protocol stack. Hence, the network management problem is solved for a network that is comprised of both the OptiX equipment and third-party equipment. The configuration, however, is more complicated than the HWECC solution. For details on the IP over DCC solution, see section 1.3 IP over DCC Solution.
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 is comprised of both the OptiX transmission equipment and the third-party equipment that supports the OSI over DCC function, the OSI over DCC solution is the first choice. With this solution, NEs transmit the data that supports the Open System Interconnection (OSI) protocol through DCCs. The OSI protocol is a standard protocol. Hence, the network management problem is solved for a network that is comprised of both the OptiX equipment and third-party equipment. However, the configuration is more complicated than both the HWECC solution and the IP over DCC solution. For details on the OSI over DCC solution, see section 1.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 Bytes Transparent Transmission Solution

When the network is comprised of the OptiX transmission equipment and the third-party equipment that does not support the IP over DCC function or the OSI over DCC function, the DCC bytes transparent transmission solution is adopted. With this solution, vendors use different DCCs to transmit data. Hence, the network management problem is solved when the vendors' equipment is used together with third-party equipment to form a network. The NMS of a vendor can manage only the NEs of the vendor. Hence, this solution has a great limitation. For details on the DCC bytes transparent transmission solution, see section 1.5 DCC Bytes Transparent Transmission Solution.
DCC 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, the DCC transmission through the external clock interface solution is adopted. With the DCC 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 third-party 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.
1-6 Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 02 (2011-01-20)
1 DCN Features
For details on the DCC transmission through the external clock interface solution, see section 1.6 DCC Transmission Through the External Clock Interface Solution.
Inband DCN Solution

When the network is comprised of the OptiX RTN 980 and the OptiX packet equipment, the inband DCN solution is adopted. With this solution, the NM message is transmitted through the Hybrid microwave port or FE/ GE port by using the Ethernet service bandwidth. When this solution is used on a network comprised of the OptiX equipment and third-party equipment, the third-party equipment needs to transmit the NM message in the manner it transmits the Ethernet service. For details on the inband DCN solution, see section 1.7 Inband DCN 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.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.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.
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 1-7
Issue 02 (2011-01-20)
1 DCN Features
When the equipment in the center of the network supports the 64 kbit/s synchronous data service transmission, the 64 k/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. 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. l When all the edge equipment is in the same domain, the RS-232/Ethernet protocol converter can be used on the NM side and the edge equipment side to establish a DCN channel for the edge equipment, as shown in Figure 1-2. When the edge equipment is in multiple domains and the central equipment supports multiple RS-232 asynchronous data services, the RS-232/Ethernet protocol converter is used to establish DCN channels for the edge equipment in each domain. Then, the services are aggregated to the NMS by using the LAN switch, as shown in Figure 1-3. In this case, the concentrated RS-232/Ethernet protocol converter can be used to aggregate DCN channels from multiple domains to the same NMS.
Figure 1-2 RS-232/Ethernet protocol converter solution (in the case that all the edge equipment is in the same domain)
NMS
RS-232/Ethernet Converter
Central netw ork
RS-232/Ethernet Converter
Edge netw ork
Ethernet link
RS-232 link
Radio link
1-8
Issue 02 (2011-01-20)
1 DCN Features
Figure 1-3 RS-232/Ethernet protocol converter solution (in the case that the edge equipment is in multiple domains)
Edge network1
NMS RS-232/Ethernet Converter 1
RS-232/Ethernet Converter 1
LAN switch RS-232/Ethernet Converter n
Edge network n
Central network
RS-232/Ethernet Converter n
Ethernet link
RS-232 link
Radio link
NOTE
The OptiX RTN 980 supports direct NMS access through the RS-232 serial port. Hence, when the OptiX RTN 980 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.
64 k/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 64 k/Ethernet protocol converter, and the central equipment transparently transmits the data service. In this manner, the DCN transmission of the edge equipment is realized. To the edge equipment, the 64 k/Ethernet protocol converter and the central equipment function as external DCN, which realizes the DCN communication between the NMS and the gateway NE. l When all the edge equipment is in the same domain, the 64 k/Ethernet protocol converter can be used on the NM side and the edge equipment side to establish a DCN channel for the edge equipment, as shown in Figure 1-4. When the edge equipment is in multiple domains and the central equipment supports multiple 64 kbit/s synchronous data services, the 64 k/Ethernet protocol converter is used to establish DCN channels for the edge equipment in each domain. Then, the services are aggregated to the NMS by using the LAN switch, as shown in Figure 1-5.
Issue 02 (2011-01-20)
1-9
1 DCN Features
Figure 1-4 64 k/Ethernet protocol converter solution (in the case that all the edge equipment is in the same domain)
NMS
64k/Ethernet Converter
Central netw ork
Edge netw ork
Ethernet link
64kbps link
Radio link
Figure 1-5 64 k/Ethernet protocol converter solution (in the case that all the edge equipment is in multiple domains)
Edge network1
NMS 64k/Ethernet Converter 1
64k/Ethernet Converter 1
LAN switch 64k/Ethernet Converter n
Edge network n
Central network
64k/Ethernet Converter n Ethernet link 64kbps link Radio link
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.
1-10
Issue 02 (2011-01-20)

NOTE
1 DCN Features
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. l 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-6. 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-7. 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-8.
Figure 1-6 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 02 (2011-01-20)
1-11
1 DCN Features
Figure 1-7 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-8 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
NMS
E1/Ethernet Converter 1 (PTP type)
LAN switch
Edge network n
E1/Ethernet Converter (concentrated type)
Central network
E1/Ethernet Converter n (PTP type)
Ethernet link
E1
Radio link
NOTE
The concentrated E1/Ethernet protocol converter houses several service boards. Each service board equals a PTP E1/Ethernet protocol converter and these protocol converters are independent from each other.
1-12
Issue 02 (2011-01-20)
1 DCN Features
The E1/Ethernet protocol solution is adopted in two special scenarios: shared E1 and shared BTS service channel. l 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-9. 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-9 E1/Ethernet protocol converter solution (shared E1)
NMS E1/Ethernet Converter (concentrated type)
E1/Ethernet Converter (cascade type) TS 1-12 TS 1-8
LAN switch TS 1-12
GNE 1 Central network Edge subnetwork 1
TS 1-8 E1/Ethernet Converter (cascade type) TS 1-4
TS 1-4 GNE 3 Edge subnetwork3 E1/Ethernet Converter (PTP type) E1
GNE 2 Edge subnetwork 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). With this solution, the PTP E1/Ethernet protocol converter on the gateway NE side in each domain/sub-network is used to transmit the Nx64 kbit/s synchronous data services used for the DCN communication to BTS through the E1. The BTS uses the
Issue 02 (2011-01-20)
1-13
1 DCN Features
fractional E1 function to schedule the accessed Nx64 kbit/s data services to the idle timeslots of the BTS service E1. Then, the data services are transmitted to BSC. BSC uses the fractional E1 function to demultiplex Nx64 kbit/s data services from each BTS service E1, and aggregates the data services in one E1 for transmission to the channelized and concentrated E1/Ethernet protocol converter. The protocol converter demultiplexes Nx64 kbit/s data services in the E1 and converts these services into corresponding Ethernet data for transmission to the NMS, as shown in Figure 1-10. Figure 1-10 E1/Ethernet protocol converter solution (shared BTS service channel)
NMS
TS 30 BTS E1/Ethernet GNE 1 Converter Edge network 1 (PTP type) TS 1-3
TS 30 BTS E1/Ethernet GNE 2 Converter Edge network 2 (PTP type)
LAN switch E1/Ethernet BSC Converter (concentrated type)
TS 30 BTS Ethernet link E1 E1/Ethernet Converter (PTP type) GNE 3 GNE n
Edge network 3 Back haul link
Radio 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-11, 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, 64 k/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-14
Issue 02 (2011-01-20)
1 DCN Features
Figure 1-11 Hybrid Use Solution of Protocol Converters
NMS
RS-232/ Ethernet Converter
RS-232/ GNE 1 Ethernet Edge network 1 Converter
LAN switch
64k/Ethernet GNE 2 Converter Edge network 2 Central network
E1/Ethernet Converter (PTP ype)
E1/Ethernet Converter (PTP type) Ethernet link RS-232 link
GNE 3 Edge network 3
Radio link 6kbps link E1
1.2 HWECC Solution

Using the HWECC solution, NEs use unified DCCs to transmit the data of the HWECC protocol. In this manner, the NMS can manage NEs. 1.2.1 Introduction This section provides the definition of HWECC and describes its purpose. 1.2.2 Basic Concepts This section describes the basic concepts associated with the HWECC solution. 1.2.3 Specifications This section describes the specifications of HWECC. 1.2.4 Reference Standards and Protocols This section describes the standards and protocols associated with HWECC. 1.2.5 Availability This section describes the support required by the application of the HWECC solution and its dependencies. 1.2.6 Principles This section describes the principles of the HWECC solution. 1.2.7 Planning Guidelines Follow certain guidelines when you plan HWECC. 1.2.8 Configuration Procedure 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.
1 DCN Features
1.2.9 Configuration Example This topic uses an example to describe how to plan and configure the HWECC solution according to the conditions of the network. 1.2.10 Task Collection This topic provides the hyperlinks of the operation tasks regarding the relevant feature. 1.2.11 Relevant Alarms and Events When the communication between the U2000 and an NE fails, the U2000 reports the corresponding alarm. 1.2.12 FAQs This topic provides the answers to the questions that are frequently raised when the HWECC solution is used.
1.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 1-12 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 1-12 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
1-16
Issue 02 (2011-01-20)
1 DCN Features
Purpose
HWECC is preferred as the DCN solution when the network is comprised of only the OptiX equipment that supports the HWECC protocol stack.
1.2.2 Basic Concepts

This section describes the basic concepts associated with the HWECC solution. 1.2.2.1 HWECC Protocol Stack ITU-T G.784 defines the architecture of the ECC protocol stack based on the OSI seven layer reference model. The HWECC protocol stack is based on the ECC protocol stack. 1.2.2.2 Extended ECC The HWECC 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 cascade ports on the system control unit of the NEs to realize communication through extended ECCs.
1.2.2.1 HWECC Protocol Stack

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

Figure 1-13 HWECC protocol stack architecture
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
Issue 02 (2011-01-20)
1-17
1 DCN Features
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 about the DCC corresponding to each line port. The status information includes the following: 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 physical channels. Physical channels are classified into the following categories: l DCC channel DCCs use the DCC bytes in SDH frames or PDH microwave frames as the channels for communication between NEs. In the HWECC solution: The SDH line port generally uses bytes D1 to D3 as DCCs. The PDH microwave port with capacity of less than 16xE1 always uses byte D1 as the DCC. The PDH microwave port with capacity of not less than 16xE1 always uses bytes D1D3 as DCCs. The SDH line port generally uses bytes D1 to D3 as DCCs. The Hybrid microwave port generally uses bytes D1 to D3 as DCCs. 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.
Media Access Layer

The main function of the media access layer (MAC layer) is to activate and 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.
1 DCN Features
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 Provides the data communication service. The MAC layer receives the data frame transferred from the physical layer. If the destination address is the address of the local station, the MAC layer transfers the data frame to the network layer. Otherwise, the MAC layer discards the data frame. The MAC layer sends the data frame from the network layer. If the destination address of the data frame has a MAC connection, the MAC layer sends the data frame to the corresponding physical channel 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) is to provide the end-to-end communication service for the upper layer. The communication between the OptiX equipment and the NMS is controlled by the end-to-end connection-oriented service in the application layer. Hence, the L4 provides only the end-to-end connectionless communication service, namely, transparent data transfer service.
Issue 02 (2011-01-20)
1-19
1 DCN Features
NOTE
In the HWECC protocol stack, the NE address used by each layer is the ID of the NE. The NE ID has 24 bits. The highest eight bits represent the subnet ID (or the extended ID) and the lowest 16 bits represent the basic ID. For example, if the ID of an NE is 0x090001, the subnet ID of the NE is 9 and the basic ID is 1.
1.2.2.2 Extended ECC

The HWECC 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 cascade ports on the system control unit of the NEs to realize communication through extended ECCs.
Networking
There are two networking modes for the extended ECC: l Using the network cable Use a network cable to directly connect the Ethernet NM interfaces or NE cascade interfaces of the two NEs. l Using the hub Use a hub or other data communication equipment to connect the Ethernet NM ports on the system control unit of related NEs. Figure 1-14 Networking for the extended ECC (using a network cable)
NMS
Network cable
Radio link
1-20
Issue 02 (2011-01-20)
1 DCN Features
Figure 1-15 Networking for the extended ECC (using a hub)

NMS
Hub
Network cable
Radio link
The Ethernet NM port and the NE cascade port on the system control unit of the OptiX RTN 900 are equivalent to two ports on a hub. Hence, you can use network cables to connect NEs in series. Such series connection is equivalent to the hub connection. Figure 1-16 Networking for the extended ECC (using network cables to connect NEs in series)
NMS
Network cable
Radio link
Issue 02 (2011-01-20)
1-21
1 DCN Features
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 system control unit is repeatedly reset. l Both the Ethernet NM port and the NE cascade port on the system control unit of the OptiX RTN 900 have the MDI and MDI-X adaptive capability. Hence, either a straight-through cable or a crossover cable can be used as the network cable for the extended ECC. l The OptiX transmission NE can transmit the network message to the other OptiX transmission NE or OptiX wireless transmission NE through the extended ECC.
Extension Mode
There are two extension modes for the extended ECC: l Automatic mode On 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. They then 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 1-17 shows an example of the multi level 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.
1-22
Issue 02 (2011-01-20)
1 DCN Features
Figure 1-17 Extended ECC network (multi level extended ECC)
NMS
Client 21
Hub
Client 22
Server 1 Client 27 Client 11 Client 12 Client 17 and Server 2
NOTE
The NE starts the automatic extended ECC by default.
1.2.3 Specifications
This section describes the specifications of HWECC. Table 1-1 lists the specifications of HWECC supported by the OptiX RTN 980. Table 1-1 Specifications of HWECC Item Number of DCC bytes STM-1 optical transmission line or SDH microwave PDH microwave (16xE1 or more) PDH microwave (less than 16xE1) Hybrid microwave Extended ECC Extension mode Specifications l 3 bytes (D1-D3) l 9 bytes (D4-D12) l 12 bytes (D1-D12) 3 bytes (D1-D3) 1 byte (D1) 3 bytes (D1-D3) l Automatic mode l Specified mode Number of connected NEs (total number of server and its clients)
Issue 02 (2011-01-20)
l 4 (automatic mode) l 8 (specified mode)
1-23
1 DCN Features
Item Access method DCC bytes transparent transmission Scale of the ECC subnet
Specifications Gateway access mode. That is, the NMS can access a non-GNE only through the GNE. Supported (only for the SDH optic line or SDH radio) 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.
1.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.
1.2.5 Availability
This section describes the support required by the application of the HWECC solution and its dependencies.
Hardware and Version Support

Table 1-2 Hardware and version support Feature HWECC solution Applicable Board CSHN SL4D (a logical board of the CSHN) SL1D IF1 IFU2 IFX2 ISU2 Applicable Hardware Version All the versions All the versions All the versions All the versions All the versions All the versions All the versions Applicable Product Version V100R003C00 and later V100R003C00 and later V100R003C00 and later V100R003C00 and later V100R003C00 and later V100R003C00 and later V100R003C00 and later
Issue 02 (2011-01-20)
1-24
1 DCN Features
Feature
Applicable Board ISX2
Applicable Hardware Version All the versions
Applicable Product Version V100R003C00 and later
Feature Dependencies
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 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. The HWECC protocol stack of NEs can communicate with the IP protocol stack of the inband DCN. 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. When the OptiX RTN 980 houses dual system control, switching, and timing boards, the Ethernet network management interfaces and the Ethernet NE stack interfaces on the two boards are equal to four ports on a hub. Note that an Ethernet loop cannot occur between any two ports.
l l
1.2.6 Principles
This section describes the principles of the HWECC solution. 1.2.6.1 Establishing ECC Routes The HWECC solution adopts the shortest path first algorithm to establish ECC routes. In this context, the shortest path refers to the path with minimum number of stations. 1.2.6.2 Packet Transfer In the HWECC solution, the messages between NEs are transferred in the NET layer of the NEs. 1.2.6.3 Extended ECC The extended ECC realizes the ECC communication by using the TCP connection between adjacent NEs as the MAC connection.
1.2.6.1 Establishing ECC Routes

The HWECC solution adopts the shortest path first algorithm to establish ECC routes. In this context, the shortest path refers to the path with minimum number of stations. The following describes how an NE establishes ECC routes:
1 DCN Features
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 to 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) On 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 to 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 refreshes 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 1-18 Networking example for establishing ECC routes
NE1 NE2 NE5
NE3
NE4
The following describes how to establish ECC routes between NEs. The network shown in Figure 1-18 is provided as an example. 1. The physical layer of each NE maintains the status information about the DCC corresponding to each line port. The physical layer of each NE detects that there are two available DCCs. 2. The MAC layer of the NE establishes the MAC connection to the adjacent NE. NE1 is taken as an example to describe how to establish the MAC connection.
1 DCN Features
(1) NE1 broadcasts the frame MAC_REQ to NE2 and NE5 periodically 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 to NE2 and a MAC connection to 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 taken 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 the other 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 refresh their respective NET layer routing tables. After the refreshing, in the NET layer routing table of NE2, there is a route to NE5 and the transfer NE is NE1; in the NET layer routing table of NE5, there is also a route to NE2 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 that 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 manner as the routes to NE3. (4) If the DCC between NE1 and NE2 becomes faulty, the MAC connection between NE1 and NE2 fails. In this case, NE1 refreshes 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 manner, the ECC route is protected.
1.2.6.2 Packet Transfer

In the HWECC solution, the messages between NEs are transferred in the NET layer of the NEs. Figure 1-19 shows how the HWECC solution transfers the messages from the NMS to the destination NE. Figure 1-19 Realization principle of message transfer (HWECC)
Application TCP IP Application TCP IP L4 NET MAC Ethernet Ethernet DCC NMS Gateway NE DCC Transfer NE DCC Destination NE NET MAC Application L4 NET MAC
Issue 02 (2011-01-20)
1-27
1 DCN Features
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 that 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 1-19 is HWECC. Hence, the gateway NE transfers the messages to the transfer NE through the HWECC protocol stack. On 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 that 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 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
1.2.6.3 Extended ECC

The extended ECC realizes the ECC communication by using the TCP connection between adjacent NEs as the MAC connection.
Automatic Mode
The realization principle of the automatic mode is as follows: 1. 2. 3. 4. 5.
1-28
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 becomes the server and senses the TCP requests from the clients. Other NEs automatically become 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.
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 02 (2011-01-20)
1 DCN Features
Specified Mode
The realization principle of the specified mode is the same as the realization principle of the automatic mode. The difference is that in the specified mode, the server, clients, and IDs of connected ports are manually specified.
1.2.7 Planning Guidelines

Follow certain guidelines when you plan HWECC.
Planning Guidelines on GNEs

l l Select the NE that is the closest to the NMS, the central node of star services, or the NE that accesses the maximum number of DCCs, as the GNE if possible. Set two GNEs, one active and one standby, 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 on External DCNs

l l l For the consideration of stability and security, it is recommended that you not use the office LAN or Internet as the transmission channels of an external DCN. It is recommended that the bandwidth of an external DCN 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 an 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 a monitored network. An external DCN must provide active and standby DCN routes or gateways if possible.
Planning Guidelines on NE IDs

l l l The NEs on one DCN must have unique IDs. If each NE on one DCN can be allocated with a unique basic ID, do not use extended IDs. In the case of a newly-built network, it is recommended that you follow a certain rule to allocate NE IDs. 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. l Allocate unused IDs to the NEs that are added to an existing network.
Planning Guidelines on IP Addresses of NEs

l l l
Issue 02 (2011-01-20)
The IP address, subnet mask, and default gateway of a GNE must meet the planning requirements of the external DCN. The IP addresses of the NEs that use the extended ECC must be on the same network segment. Set the IP addresses of non-GNEs based on their NE IDs.
1 DCN Features
NOTE
l The IP address of a non-GNE is 0x81000000+ID. For example, if an NE ID is 0x090001, set the IP address to 129.9.0.1. l By default, the subnet mask is 255.255.0.0.
Planning Guidelines on Extended ECCs

l l l l l If a site holds multiple OptiX NEs without any DCCs, implement the extended ECC function 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 in extended ECC networking, do not connect the hubs to other equipment. The IP addresses of the NEs that use the extended ECC function must be on the same network segment. By default, the extended ECC feature 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 the specified mode. In addition, if an extended ECC subnet consists of more than eight NEs, specify levels for the extended ECCs to ensure that each server is connected to a maximum of seven clients. When you enable the extended ECC function by using the specified mode, 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 the case of an extended ECC subnet of multiple levels, each ECC group takes a unique port ID.
l l
Planning Guidelines on ECC Subnets

l l l 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. 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.
1.2.8 Configuration Procedure

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.
1-30
Issue 02 (2011-01-20)
1 DCN Features
Table 1-3 Procedure for the HWECC solution Step 1 Operation A.1.1.4 Changing the NE ID 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.1.7.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.1.7.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. 4 A.1.7.3 Configuring Extended ECC Communication 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.
Issue 02 (2011-01-20)
1-31
1 DCN Features
Step
Operation
Remarks 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.1.7.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.1.2 Creating NEs by Using the Manual Method A.1.1.1 Creating NEs by Using the Search 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.1.7.13 Querying ECC Routes
In other cases, this method is preferred.
1.2.9 Configuration Example

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

This section describes the networking information about the NEs. In the networking diagram shown in Figure 1-20, 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. Figure 1-20 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
1.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.
Issue 02 (2011-01-20)
1 DCN Features
l l
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. Figure 1-21 Allocation of IDs/IP addresses for all the NEs
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-205 129.9.0.205 0.0.0.0
9-204 129.9.0.204 0.0.0.0 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-105 129.9.0.105 0.0.0.0
Extended ID-Basic ID IP address Gatew ay
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.
1.2.9.3 Configuration Process

This topic describes the procedure for the data configuration.
1-34
Issue 02 (2011-01-20)
1 DCN Features
Context
NOTE
In this configuration example, only the configuration information about NE201, NE202, and NE203 is provided.
Procedure
Step 1 See A.1.1.4 Changing the NE ID and change the NE ID. The values for the related parameters are provided as follows. Parameter Value Range NE201 New ID New Extended ID 201 9 (default value) NE202 202 9 (default value) NE203 203 9 (default value)
Step 2 See A.1.7.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.1.7.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 Disabled Other Microwave/ Line Ports (NE201) All the Microwave/Line Ports (NE202 and NE203) Enabled (default value)
Enabled (default value)
Issue 02 (2011-01-20)
1-35
1 DCN Features
Parameter
Value Range East and West Ports on the Ring (NE201) Other Microwave/ Line Ports (NE201) All the Microwave/Line Ports (NE202 and NE203) 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)
Channel
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.1.7.3 Configuring Extended ECC Communication and configure the extended ECC. The values for the related parameters are provided as follows. Parameter Value Range NE201 ECC Extended Mode Port (on the server side) Opposite IP (on the client side) Port (on the client side) Auto mode (default value) NE202 Specified mode 1601 (default value) 0.0.0.0 (default value) 1601 (default value) NE203 Auto mode (default value) -
Step 5 See A.1.7.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 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
1-36
Issue 02 (2011-01-20)
1 DCN Features
Parameter Sink Timeslot/Port
Value Range Related parameter values of east ports on the ring D1 Related parameter values of east ports on the ring D2 Related parameter values of east ports on the ring D3
Transparent Transmission of Overhead Bytes at Sink Port
Step 6 See A.1.7.13 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.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 domain when the IP address of the GNE is 10.0.0.101 l The search domain when the IP address of the GNE is 11.0.0.201
NOTE
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
1.2.10 Task Collection

This topic provides the hyperlinks of the operation tasks regarding the relevant feature.
Related Tasks
A.1.1.1 Creating NEs by Using the Search Method A.1.1.2 Creating NEs by Using the Manual Method A.1.1.4 Changing the NE ID A.1.7.1 Setting NE Communication Parameters A.1.7.2 Configuring DCCs A.1.7.3 Configuring Extended ECC Communication A.1.7.4 Configuring DCC Transparent Transmission A.1.7.13 Querying ECC Routes
1 DCN Features
1.2.11 Relevant Alarms and Events

When the communication between the U2000 and an NE fails, the U2000 reports the corresponding alarm.
Relevant Alarms
l GNE_CONNECT_FAIL The GNE_CONNECT_FAIL alarm indicates that the connection to the gateway fails. When the communication between the U2000 and the GNE fails, the U2000 reports this alarm. l NE_COMMU_BREAK The NE_COMMU_BREAK alarm indicates that the NE communication is interrupted. When the communication between the U2000 and the NE is interrupted, the U2000 reports this alarm. l NE_NOT_LOGIN The NE_NOT_LOGIN alarm indicates that the login to the NE fails. When the U2000 cannot log in to the NE, the U2000 reports this alarm.
Relevant Events
None.
1.2.12 FAQs
This topic 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: 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.
1-38
Issue 02 (2011-01-20)
1 DCN Features
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.
1.3 IP over DCC Solution

Using the IP over DCC solution, NEs use unified DCCs to transmit the data of the TCP/IP protocol. In this manner, the NMS can manage NEs. The IP over DCC solution applies to a network that is comprised of the OptiX transmission equipment and the third-party equipment that supports the IP over DCC function. This solution can be adopted when the equipment in the center of the network needs to provide an NM message transmission path over IP for the NE at the edge of the network. 1.3.1 Introduction This section provides the definition of IP over DCC and describes its purpose. 1.3.2 Basic Concepts This topic describes the basic concepts that you need to be familiar with before you use the IP over DCC solution. 1.3.3 Specifications This section describes the specifications of IP over DCC. 1.3.4 Reference Standards and Protocols This section describes the standards and protocols associated with IP over DCC. 1.3.5 Availability This section describes the support required by the application of the IP over DCC solution and its dependency. 1.3.6 Principles This section describes the principles of the IP over DCC solution. 1.3.7 Planning Guidelines Follow certain planning guidelines when you plan IP over DCC. 1.3.8 Configuration Procedure
1 DCN Features
The configuration flow 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. 1.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. 1.3.10 Task Collection This topic provides the hyper links of the operation tasks regarding the relevant feature. 1.3.11 Relevant Alarms and Events When the communication between the U2000 and an NE fails, the U2000 reports the corresponding alarm. 1.3.12 FAQs This topic provides the answers to the questions that are frequently raised when the IP over DCC solution is used.
1.3.1 Introduction
This section provides the definition of IP over DCC and describes its purpose.
Definition
IP 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 IP protocol stack. Figure 1-22 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 1-22 Application of the IP over DCC solution
sg yM art k p c 3rd P sta I C C D
3rd-party Msg IP stack ETH Third-party NMS
g Ms t iX c k p O sta 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
1-40
Issue 02 (2011-01-20)
1 DCN Features
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.

This topic describes the basic concepts that you need to be familiar with before you use the IP over DCC solution. 1.3.2.1 IP over DCC Protocol Stack The IP over DCC adopts the architecture of the standard TCP/IP protocol stack. 1.3.2.2 OSPF Protocol The Open Shortest Path First (OSPF) protocol, developed by the Internet Engineering Task Force (IETF), is a link-state Interior Gateway Protocol (IGP). 1.3.2.3 Proxy ARP The proxy ARP enables the NEs in the same network segment but different physical networks to communicate with each other. 1.3.2.4 NMS Access Modes In the IP over DCC solution, there are two modes for the NMS to access an NE: gateway access mode and direct access mode.
1.3.2.1 IP over DCC Protocol Stack

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

Figure 1-23 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
Issue 02 (2011-01-20)
1-41
1 DCN Features
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.
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
Routes are classified into three types according to their sources: l l Direct route A direct route is discovered by the Data Link Layer protocol. Static route A static route is manually configured by the network administrator.
1 DCN Features
Dynamic route A dynamic route is discovered by the routing protocol.
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. Routers are identified by router IDs. The router ID has the same format as the IP address. For the introduction to OSPF protocol, see 1.3.2.3 Proxy ARP. The OSPF protocol running on the OptiX equipment supports a single OSPF domain. That is, it supports only routes within an area and does not support routes between areas. This means that the OptiX equipment cannot function as an area border router. The OptiX equipment uses the NE IP address as the router ID under the OSPF protocol. By default, only the direct route between two NEs within the area (in addition, the direct route must have the OSPF protocol enabled at its router interfaces of both ends) can function as an LSA for routing computation. If an external route needs to be included in the routing computation, the OSPF route diffusion function must be enabled to diffuse the external route to the other NEs.
Proxy ARP
The OptiX equipment supports the proxy ARP as a supplement to the routing protocol. For the introduction to proxy ARP, see 1.3.2.3 Proxy ARP.
1.3.2.2 OSPF Protocol

The Open Shortest Path First (OSPF) protocol, developed by the Internet Engineering Task Force (IETF), is a link-state Interior Gateway Protocol (IGP).
introduction
OSPF has the following advantages: l l l l Divides an Autonomous System (AS) into one or multiple logical areas. Advertises routes by sending Link State Advertisements (LSAs). Synchronizes routing information by exchanging OSPF packets between routers in OSPF areas. Encapsulates OSPF packets in IP packets and then sends the packets in unicast mode or multicast mode.
Issue 02 (2011-01-20)
1-43
1 DCN Features
OSPF Packet Type

Table 1-4 OSPF Packet Type Packet Hello packet Database Description (DD) packet Function Hello packets are sent periodically to discover and maintain OSPF neighbor relationships. DD packets carry brief information about the local Link State Database (LSDB) and are used to synchronize the LSDBs of two routers. LSR packets are used to request the required LSAs from neighbors. LSR packets are sent only after DD packets are exchanged successfully. Link State Update (LSU) packet Link State Acknowledgment (LSAck) packet LSU packets are used to send the required LSAs to neighbors. LSAck packets are used to acknowledge the received LSAs.
Link State Request (LSR) packet
LSA Type
Table 1-5 OSPF LSA type LSA Router-LSA (Type1) Function Describes the link status and link cost of a router. It is generated by each router and advertised in the area to which the router belongs. Describes the link status of all routers in the local network segment. It is generated by a designated router (DR) and advertised in the area to which the DR belongs. Describes routes in a certain network segment. It is generated by an Area Border Router (ABR) and advertised in related areas. Describes routes to an Autonomous System Boundary Router (ASBR). It is generated by an ABR and advertised in the related areas except the area to which the ASBR belongs. Describes routes to a destination outside the AS. It is generated by an ASBR and advertised in all areas except stub areas and Not-So-Stubby Areas (NSSAs). Describes routes to a destination outside the AS. It is generated by an ASBR and advertised in NSSAs only.
Network-LSA (Type2)
Network-summary-LSA (Type3) ASBR-summary-LSA (Type4) AS-external-LSA (Type5)
NSSA-LSA (Type7)
1-44
Issue 02 (2011-01-20)
1 DCN Features
LSA Opaque-LSA (Type9/ Type10/Type11)
Function Provides a general mechanism for OSPF extension: Type9 LSAs are advertised in the network segment where interfaces reside. Grace LSAs used to support GR are one type of Type9 LSAs. Type10 LSAs are advertised in an area. LSAs used to support TE are one type of Type10 LSAs. Type11 LSAs are advertised in an AS. At present, there are no application examples of Type11 LSAs.
OSPF Areas
Suppose that all routers in a large-scale network run OSPF and the number of routers increases with the unceasing expansion of the network. The large number of routers results in a large LSDB on each router. Such an LSDB occupies a great amount of memory, complicates the operating of the SPF algorithm, and leads to the overload of routers. With the expansion of networks, the possibility of topology changes is on the increase. That is, the network usually confronts "turbulence". A great number of OSPF packets are transmitted on the network, and the utilization of bandwidth is reduced. Each change in topology requires all the routers to recalculate the routes. OSPF addresses the preceding problem by dividing an AS into areas, as shown in Figure 1-24. l Area An area is regarded as a logical router group. Each group is identified by an area ID. At the border of an area resides a router, rather than a link. A network segment (or a link) can belong to only one area. That is, each OSPF interface belongs to an area. l Backbone Area After an OSPF network is divided into different areas, not all areas are equal. Among areas, one area with area ID as 0 is called the backbone area. The backbone area is responsible for forwarding the inter-area routes. The routing information between the non-backbone areas must be forwarded through the backbone area. OSPF defines two rules for a backbone area as below: Connectivity must be available between non-backbone areas and the backbone area. Connectivity must be available over the backbone area.
Issue 02 (2011-01-20)
1-45
1 DCN Features
Figure 1-24 OSPF areas and router type

Static route ASBR Area4
Area1 Internal router Area0
Backebone router
Area2
ABR
Area3
Router Type
Table 1-6 lists the types of common routers in OSPF. Figure 1-24 provides a example of different routers position in network. Table 1-6 OSPF router type Router Internal router Area Border Router (ABR) Description All interfaces of an internal router belong to the same OSPF area. An ABR can belong to two or more areas, and one of the areas must be a backbone area. An ABR is used to connect the backbone area and nonbackbone areas. It can be physically or logically connected to the backbone area. Backbone router At least one interface on a backbone router belongs to the backbone area. All ABRs and internal routers in Area 0, therefore, are backbone routers. AS Boundary Router (ASBR) An ASBR exchanges routing information with other ASs. An ASBR may not reside at the boundary of an AS. It can be an internal router or an ABR. If an OSPF router imports external routes, the router is an ASBR.
1-46
Issue 02 (2011-01-20)
1 DCN Features
Stub Area
A stub area is a special area where the ABRs do not flood the received routes outside the AS. In stub areas, the size of the routing tables of the routers and the routing information in transmission are reduced. A stub area is an optional configuration. Not all areas can be configured as stub areas. Generally, a stub area is a non-backbone area with only one ABR and is located at the AS boundary. To ensure the reachability to a destination outside the AS, the ABR in the stub area originates a default route and advertises it to the non-ABR routers in the Stub area. Note the following when configuring a stub area: l l l The backbone area cannot be configured as the stub area. An ASBR cannot exist in a stub area. That is, external routes are not flooded in the stub area. A virtual link cannot pass through a stub area.
NSSA Area
A new type of an area, Not-So-Stubby Area (NSSA), and a new type of an LSA, NSSA-LSA (or Type-7 LSA) are defined in RFC 1587. As the NSSA is derived from the stub area, it resembles the stub area in many ways. An NSSA does not import AS-external-LSA (that is Type-5 LSA). The Type7 LSA is generated by the ASBR in the NSSA, and is flooded only in the NSSA. When a Type7 LSA reaches the ABR of the NSSA, the ABR translates the Type-7 LSA into an AS-external-LSA and floods it to the other areas. The ABR translating LSAs is also called the translator. Similar with the stub area, an NSSA cannot be configured with virtual links.
Process of Calculating OSPF Routes

The process to calculate OSPF routes is described as follows: l Based on the surrounding network topology, each OSPF router originates Link State Advertisements (LSAs). The router then sends the LSA to other OSPF routers through update packets. Each OSPF router collects the LSAs sent by other routers, and all these LSAs constitute a Link State Database (LSDB). An LSA describes the network topology around a router, while an LSDB describes the network topology of the entire AS. OSPF routers transform the LSDB into a weighted directed map. The weighted directed map reflects the topology of the entire network. All routers have the same map. According to the directed map, each router uses the SPF algorithm to calculate the shortest path tree with itself being the root. The tree shows the routes to each node in the AS.
l l
1.3.2.3 Proxy ARP

The proxy ARP enables the NEs in the same network segment but different physical networks to communicate with each other. For a visit between the NEs on a network segment, the source NE will not look up in its routing table. Instead, it sends ARP broadcast packets to address the route to the sink NE. Being on different physical networks, the sink NE cannot receive MAC-layer broadcast packets from the
1 DCN Features
source NE. Therefore, an ARP proxy NE is required. 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 1-25 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 1-25 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.
1-48

NOTE
1 DCN Features
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 route of NE4. 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.
1.3.2.4 NMS Access Modes

In the IP 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 refers to 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 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 NMS applies the direct access mode to access an NE, there must be an IP route between the NMS and the NE. In the IP over DCC solution, theoretically, the NMS can access any NE using the direct access mode, that is, it 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.
This section describes the specifications of IP over DCC.
1 DCN Features
Table 1-7 lists the specifications of IP over DCC supported by the OptiX RTN 980. Table 1-7 Specifications of IP over DCC Item Number of DCC bytes SDH optical transmission line or SDH microwave PDH microwave (16xE1 or more) PDH microwave (less than 16xE1) Hybrid microwave Route type Specifications l 3 bytes (D1-D3) l 9 bytes (D4-D12) l 12 bytes (D1-D12) 3 bytes (D1-D3) 1 byte (D1) 3 bytes (D1-D3) l Direct route l Static route l Dynamic route Dynamic routing protocol Protocol type l OSPF (default route protocol) l RIP (used when the connected third-party equipment supports the RIP protocol only) OSPF routing type Type of the interface on which the OSPF protocol is enabled Supports only the routes within an area but does not support the routes between areas. l DCC interface (enabled by default) l LAN interface (disabled by default)
NOTE l A DCC interface refers to an interface at which the DCN packet is transmitted through the DCC bytes. l A LAN interface refers to an Ethernet network management interface or NE stack interface.
OSPF parameters
Supports the settings of the following parameters: l Area ID l Packet timer l STUB area enable status l NSSA area enable status l Opaque enable status
OSPF route diffusion
Supports the import of external routes according to the route type. The supported external route types include: l Direct route l Static route l RIP route
1-50
Issue 02 (2011-01-20)
1 DCN Features
Item ARP proxy Access method Scale of the ECC subnet
Specifications Supported Supports the gateway access mode and direct access mode. 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.

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
1.3.5 Availability
This section describes the support required by the application of the IP over DCC solution and its dependency.

Table 1-8 Hardware and version support Feature IP over DCC solution Applicable Board CSHN SL4D (a logical board of the CSHN) SL1D IF1 IFU2 IFX2 ISU2 Applicable Hardware Version All the versions All the versions All the versions All the versions All the versions All the versions All the versions Applicable Product Version V100R003C00 and later V100R003C00 and later V100R003C00 and later V100R003C00 and later V100R003C00 and later V100R003C00 and later V100R003C00 and later
1-51
Issue 02 (2011-01-20)
1 DCN Features
Feature
NOTE
The NMS does not support the setting of the OSPF route diffusion function. When you need the function, contact Huawei engineers who can enable the function by using internal commands.
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 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. The IP over DCC protocol stack of NEs can communicate with the inband DCN 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 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 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. When the OptiX RTN 980 houses dual system control, switching, and timing boards, the Ethernet network management interfaces and the Ethernet NE stack interfaces on the two boards are equal to four ports on a hub. Note that an Ethernet loop cannot occur between any two ports.
1.3.6 Principles
This section describes the principles of the IP over DCC solution.
Principle of the Packet Transfer in Gateway Mode

Figure 1-26 shows how the IP over DCC solution transfers the messages from the NMS to a non-gateway NE when the NMS applies the gateway mode to access the NE.
1-52
Issue 02 (2011-01-20)
1 DCN Features
Figure 1-26 Realization principle of message transfer (gateway mode)

Application TCP IP Application TCP IP UDP IP PPP Ethernet Ethernet DCC NMS Gateway NE DCC Transfer NE DCC Destination NE IP PPP Application UDP 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 1-26 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 packet is the IP address of the local NE. The application layer functions according to the message sent from the NMS.
4.
5.
Principle of the Packet Transfer in Direct Connection Mode

Figure 1-27 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.
Issue 02 (2011-01-20)
1-53
1 DCN Features
Figure 1-27 Realization principle of message transfer (direct connection mode)

Application TCP IP IP PPP Ethernet Ethernet DCC NMS 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. 1.3.7.1 General Planning Guidelines This section describes the general planning guidelines in various scenarios. 1.3.7.2 Planning of NE IP Addresses and Routes in Typical Network Topologies If carriers do not impose special requirements for IP addresses of the NEs, you can set the IP addresses to simplify the settings of routes. 1.3.7.3 Planning of NE IP Addresses and Routes in Special Network Topologies When carriers impose special requirements for IP addresses of the NEs, route planning becomes more complex.
1.3.7.1 General Planning Guidelines

This section describes the general planning guidelines in various scenarios.
NOTE
This section describes the planning guidelines on 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 1.2.7 Planning Guidelines regarding the HWECC solution.

l l l Select the GNE. The GNE can be the NE that is the closest to the NMS, the central node of a star network, or the NE that accesses the maximum number of DCCs. 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. 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.
1-54
Issue 02 (2011-01-20)
1 DCN Features
Planning Guidelines on DCCs

l l If a network is comprised of only the OptiX equipment, 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. In PDH microwave frames, one or three DCC bytes are used for DCCs. In Hybrid microwave frames, three DCC bytes are used for DCCs.
l l

l l l l l l Set the IP addresses of NEs for the most simplified route settings. The IP address, subnet mask, and default gateway of the GNE must meet the planning requirements of the 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 this NE and the other NEs be on different network segments when an NE is connected to the third-party equipment through Ethernet NM interfaces. Set the subnet masks of one network segment to the same value.
Planning Guidelines on Routes

l l One OSPF area has a maximum of 64 NEs. If the OptiX RTN 900 NEs are interconnected through the Ethernet network management interfaces, it is recommended that you enable the OSPF routing function on the Ethernet network management interface. In this manner, the networks that are connected through the Ethernet network management interfaces can belong to the same OSPF area. The route planning allows the communication between the NMS and GNEs, between GNEs and non-GNEs, and between the third-party NMS and third-party GNEs. If the dynamic routing protocol fails to meet the preceding requirements, you need to plan proper 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 agent function on the NE.
l l l
1.3.7.2 Planning of NE IP Addresses and Routes in Typical Network Topologies

If carriers do not impose special requirements for IP addresses of the NEs, you can set the IP addresses to simplify the settings of routes. In this case, follow these principles when planning the IP addresses of the NEs: l l When the network consists of the OptiX equipment only, the IP address of the GNE is not in the same network segment as the IP address of the non-GNE. When the network consists of the OptiX equipment and the third-party equipment, the IP addresses of the GNE, non-GNE that is not connected to the third-party equipment, and GNE of the third-party equipment are not in the same network segment. The IP addresses
Issue 02 (2011-01-20)
1 DCN Features
of the non-GNE that is connected to the third-party equipment and the GNE of the thirdparty equipment are in the same network segment. The following part describes the planning of NE IP addresses and routes in typical network topologies.
Network Consisting of the OptiX Equipment Only, the NMS and GNE Being in the Same Network Segment
Figure 1-28 shows a network consisting of the OptiX equipment only. On the network, the NMS and GNE are in the same network segment. Figure 1-28 Planning diagram of NE IP addresses and routes (a network consisting of the OptiX equipment only, the NMS and GNE being in the same network segment)
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
In this diagram: l l The IP address of the GNE (NE1) is set to the 130.9.0.0 network segment that is different from the network segment (129.9.0.0) used by the non-GNEs. If the NMS needs to directly access the non-GNE (NE2 or NE3), configure a static route from the NMS to the network segment (129.9.0.0) of the non-GNE, or set the IP address of NE1 (130.9.0.1) to the default gateway.
Network Consisting of the OptiX Equipment Only, the NMS and GNE Being in Different Network Segments
Figure 1-29 shows a network consisting of the OptiX equipment only. On the network, the NMS and GNE are in different network segments.
1-56
Issue 02 (2011-01-20)
1 DCN Features
Figure 1-29 Planning diagram of NE IP addresses and routes (a network consisting of the OptiX equipment only, the NMS and GNE being in different network segments)
NMS 10.2.0.200 RT 1 10.2.0.100 NE 1 NE 2 NE 3
130.9.0.100 RT 2 130.9.0.1 129.9.0.2 129.9.0.3
Ethernet link
Radio link
In this diagram: l l l l The IP address of the GNE (NE1) is set to the 130.9.0.0 network segment that is different of the network segment (129.9.0.0) used by the non-GNEs. On NE1, configure a static route to the NMS whose IP address is 10.2.0.100, or set the IP address (130.0.0.100) of the port on RT2 to the default gateway. On the NMS, configure a static route to NE1 whose IP address is 130.9.0.1, or set the IP address (120.2.0.200) of the port on RT1 to the default gateway. When the NMS needs to directly access the non-GNE (NE2 or NE3), you also need to perform the following configurations. On NE1, enable the OSPF route diffusion function to diffuse the static route so that NE2 and NE3 can obtain the route to the NMS. On the NMS, configure a static route to the network segment (129.9.0.0) of the nonGNEs, or set the IP address of NE1 to the default gateway. Configure the routes on RT1 and RT2 according to the network segment (129.9.0.0) of the non-GNEs.
Network Consisting of the OptiX Equipment and Third-Party Equipment, the Third-Party NMS and OptiX GNE Being in the Same Network Segment
Figure 1-30 shows a network consisting of the OptiX equipment and third-party equipment. On the network, the third-party NMS and GNE are in the same network segment.
Issue 02 (2011-01-20)
1-57
1 DCN Features
Figure 1-30 Planning diagram of NE IP addresses and routes (a network consisting of the OptiX equipment and third-party equipment, the third-party NMS and GNE being in the same network segment)
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
In this diagram: l The GNE (NE1), the non-GNE (NE2) that is not connected to the third-party equipment, and the GNE (NE4) of the third-party equipment are in the network segments 130.9.0.0, 129.0.0.0, and 131.9.0.0 respectively. NE3 is in the same network segment as NE4. On the third-party NMS, configure a static route to the GNE (whose IP address is 131.9.0.4) of the third-party, or set the IP address (130.9.0.1) of NE1 to the default gateway. On the third-party equipment, configure a static route to the third-party NMS whose IP address is 130.0.0.200, or set the IP address (131.9.0.3) of NE3 to the default gateway.
l l l
Network Consisting of the OptiX Equipment and Third-Party Equipment, the Third-Party NMS and OptiX GNE Being in Different Network Segments
Figure 1-31 shows a network consisting of the OptiX equipment and third-party equipment. On the network, the third-party NMS and GNE are in different network segments.
1-58
Issue 02 (2011-01-20)
1 DCN Features
Figure 1-31 Planning diagram of NE IP addresses and routes (a network consisting of the OptiX equipment and third-party equipment, the third-party NMS and OptiX GNE being in different network segments)
Third-party NMS 10.2.0.200 RT 1 10.2.0.100
RT 2
130.9.0.100
NE 1
NE 2
NE 3
NE 4
NE 5
NMS
130.9.0.1
129.9.0.2
131.9.0.3
131.9.0.4
131.9.0.5
130.9.0.200 OptiX equipment Ethernet link Third party equipment Radio link
In this diagram: l The GNE (NE1), the non-GNE (NE2) that is not connected to the third-party equipment, and the GNE (NE4) of the third-party equipment are in the network segments 130.9.0.0, 129.0.0.0, and 131.9.0.0 respectively. NE3 is in the same network segment as NE4. On NE1, configure a static route to the third-party NMS whose IP address is 10.2.0.100. On NE1, enable the OSPF route diffusion function to diffuse the static route so that NE2 and NE3 can obtain the route to the NMS. On the third-party NMS, configure a static route to the GNE (whose IP address is 131.9.0.4) of the third-party, or set the IP address (10.2.0.200) of the port on RT1 to the default gateway. On the third-party equipment, configure a static route to the third-party NMS whose IP address is 10.2.0.100, or set the IP address (131.9.0.3) of NE3 to the default gateway. On RT1 and RT2, configure the routes according to the GNE of the third-party equipment (the IP address of the GNE is 131.9.0.4).
l l l l
l l
Network Consisting of Stacked NEs

Figure 1-32 shows a network consisting of stacked NEs.
Issue 02 (2011-01-20)
1-59
1 DCN Features
Figure 1-32 Planning diagram of NE IP addresses and routes (a network consisting of stacked NEs)
NMS NE 1
NE 3
NE 2
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
In this diagram: l l The LAN interfaces on the stacked NEs must be enabled with the OSPF protocol. The automatic extended ECC feature must be disabled on the stacked NEs. Otherwise, the protocols will conflict.
1.3.7.3 Planning of NE IP Addresses and Routes in Special Network Topologies

When carriers impose special requirements for IP addresses of the NEs, route planning becomes more complex. In this case, the GNE, the NEs connected to the third-party equipment, and non-GNEs may need to be in the same network segment. Therefore, more static routes need to be configured or the ARP proxy function needs to be enabled. The following part describes the planning of NE IP addresses and routes in special network topologies.
IP Addresses of the NEs Being in the Same Network Segment, the NMSs and NEs Being in the Same Network Segment
Figure 1-33 shows a network where the IP addresses of the NEs are in the same network segment, and the NMs and NEs are in the same network segment.
1 DCN Features
Figure 1-33 Planning diagram of NE IP addresses and routes (a network where the IP addresses of the NEs being in the same network segment, the NMSs and NEs being in the same network segment)
NMS NE 1 129.9.0.100 NE 2 NE 3 NE 4 NE 5
Third party NMS 129.9.0.1 129.9.0.200
129.9.0.2
129.9.0.3
129.9.0.4
129.9.0.5
In this diagram: l l l l l l l l Since carriers requirement that the IP addresses of all NEs should be in the same network segment (129.9.0.0), you need to perform the following configurations: On the GNE (NE1), enable the ARP proxy function to respond to ARP requests that are sent from the two NMSs to address destination NEs. On NE1, configure a static route to the third-party NMS whose IP address is 129.9.0.200. If Huawei NMS needs to directly access the non-GNE (NE2 or NE3), configure a static route from NE1 to the Huawei NMS whose IP address is 129.9.0.100. On NE1, enable the OSPF route diffusion function to diffuse the static routes so that NE2 and NE3 can obtain the routes to the two NMSs. On NE3 connected to the third-party equipment, configure a static route to the GNE of the third-party equipment (the IP address of the GNE is 129.9.0.4). On NE3, enable the OSPF route diffusion function to diffuse the static route so that NE1 and NE2 can obtain the route to the NMS. On NE3, enable the ARP proxy function so that NE4 can obtain the route to the third-party NMS.
IP Addresses of the NEs Being in the Same Network Segment, the Third-Party NMS and NEs Being in the Different Network Segments
Figure 1-34 shows a network where the IP addresses of the NEs are in the same network segment, and the third-party NM and NEs are in the same network segment.
Issue 02 (2011-01-20)
1-61
1 DCN Features
Figure 1-34 Planning diagram of NE IP addresses and routes (a network where the IP addresses of the NEs being in the same network segment, the third-party NMS and NEs being in different network segments)
Third-party NMS 10.2.0.200 RT 1 10.2.0.100
RT 2
129.9.0.100
NE 1
NE 2
NE 3
NE 4
NE 5
NMS
129.9.0.1
129.9.0.2
129.9.0.3
129.9.0.4
129.9.0.5
129.9.0.200 OptiX equipment Ethernet link Third party equipment Radio link
In this diagram: l l l l l Since carriers requirement that the IP addresses of all NEs should be in the same network segment (129.9.0.0), you need to perform the following configurations: On NE1, enable the ARP proxy function. On NE1, configure a static route to the third-party NMS whose IP address is 10.2.0.100. On NE1, enable the OSPF route diffusion function to diffuse the static route so that NE2 and NE3 can obtain the route to the NMS. If Huawei NMS needs to directly access the non-GNE (NE2 or NE3), configure a static route from NE1 to the Huawei NMS whose IP address is 129.9.0.100. In this manner, NE1 can use the OSPF route diffusion function to enable NE2 and NE3 to obtain the routes to the Huawei NMS. On NE3 connected to the third-party equipment, configure a static route to NE4 whose IP address is 129.9.0.4. On NE3, enable the OSPF route diffusion function to diffuse the static route so that NE1 and NE2 can obtain the route to NE4. On the third-party NMS, configure a static route to NE4 whose IP address is 129.9.0.4. On the GNE of the third-party equipment (NE4), configure a static route to the third-party NMS whose IP address is 10.2.0.100.
l l l l

The configuration flow 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.
1-62
Issue 02 (2011-01-20)
1 DCN Features
Table 1-9 Procedure for the IP over DCC solution Step 1 Operation A.1.1.4 Changing the NE ID 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.1.7.1 Setting NE Communication Parameters Required. Set the parameters as follows: l Set IP and Subnet Mask according to the planning. l Set Gateway IP Address if the default GNE needs to be configured for the non-GNEs. 3 A.1.7.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.1.7.7 Enabling the ARP Proxy l When the IP address of the GNE is in the same network segment as that of the non-GNE, the ARP proxy function can be enabled on the GNE. l When the GNE of the third-party equipment is in the same network segment as the non-GNE that is not connected to the third-party equipment, the ARP proxy function can be enabled on the NE that is connected to the third-party equipment if the GNE of the third-party equipment is in the same network segment as the third-party NMS. 5 A.1.7.6 Setting Parameters of the OSPF Protocol Required. Set the major parameters as follows: l Area and the values of the parameters of the timers on the NEs in an OSPF area should be set to the same values. l When the NEs are stacked, set Used Flag of the stacked NEs to Enabled so that the OSPF function of the LAN interface can be started. l Set OSPF Import Route Type to enable the OSPF route diffusion function if it is required. 6 A.1.7.5 Creating Static IP Routes Configure the static routes of NEs according to the network planning.
Issue 02 (2011-01-20)
1-63
1 DCN Features
Step 7
Operation A.1.7.3 Configuring Extended ECC Communication
Description 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.1.7.14 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.1.2 Creating NEs by Using the Manual Method A.1.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 U2000.

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

This section describes the networking information of the NEs. The OptiX wireless transmission equipment and the third-party wireless transmission equipment form the microwave transmission network, as shown in Figure 1-35. 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. Specifically, the IP address of the GNE of the third-party equipment is 130.9.0.7, and the IP address of the third-party NMS is 11.0.0.100. Figure 1-35 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 between the third-party equipment and the third-party NMS through the IP over DCC solution. Select NE1 that is the closest to the NMS as the GNE.
l
Issue 02 (2011-01-20)
1 DCN Features
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. The planning for the IP addresses of the NEs must meet the following requirements: The IP addresses of the GNE, the non-GNE that is not connected to the third-party equipment, and the GNE of the third-party equipment are in different network segments. The IP addresses of the non-GNE that is connected to the third-party equipment and the GNE of the third-party equipment are in the same network segment. Figure 1-36 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. On NE1, configure a static route to the third-party NMS whose IP address is 11.0.0.100. The gateway is the IP address of the router interface, 11.0.0.200. On NE1, enable the OSPF route diffusion function to diffuse the static route. On NE3 and NE4, enable the OSPF route function of the Ethernet network management interfaces. On the GNE of the third-party equipment, configure a static route to the third-party NMS whose IP address is 11.0.0.100 (the gateway is the IP address of NE6, 129.9.0.6). On the third-party NMS, configure a static route to the GNE of the third-party equipment whose IP address is 130.9.0.7 (the gateway is the IP address of the router interface, 11.0.0.200). Alternatively, you can set the IP address 11.0.0.200 to the default gateway of the third-party NMS. On the router, configure the routes according to the GNE of the third-party equipment (the IP address of the GNE is 130.9.0.7).

1 DCN Features
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.1.4 Changing the NE ID 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.1.7.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 129.9.0.3 0.0.0.0 (default value) 255.255.0.0 (default value) NE4 129.9.0.4 0.0.0.0 (default value) 255.255.0.0 (default value)
Step 3 See A.1.7.2 Configuring DCCs and configure the DCCs. The values for the related parameters are provided as follows. Parameter Value Range All Ports (NE1) Enabled/Disabled Enabled (default value) All Ports (NE3) Enabled (default value) All Ports (NE4) Enabled (default value)
Issue 02 (2011-01-20)
1-67
1 DCN Features
Parameter
Value Range All Ports (NE1) All 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 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
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.1.7.6 Setting Parameters of the OSPF Protocol. The values for the related parameters are provided as follows. Parameter Value Range NE1 Used Flag OSPF Import Route Type Disabled (default value) Select the Static route NE3 Enabled Select none (default value) NE4 Enabled Select none (default value)
Step 5 See A.1.7.5 Creating Static IP Routes and create the static IP routes. The values for the related parameters are provided as follows. Parameter Value Range NE1 Destination Address Subnet Mask Gateway IP Address 11.0.0.100 255.255.0.0 10.0.0.200
Step 6 See A.1.7.3 Configuring Extended ECC Communication and configure the extended ECC. The values for the related parameters are provided as follows. Parameter Value Range NE1 ECC Extended Mode Specified mode NE3 Specified mode NE4 Specified mode
1-68
Issue 02 (2011-01-20)
1 DCN Features
Parameter
Value Range NE1 NE3 1601 (default value) 0.0.0.0 (default value) 1601 (default value) NE4 1601 (default value) 0.0.0.0 (default value) 1601 (default value)
Port (on the server side) Opposite IP (on the client side) Port (on the client side)
1601 (default value) 0.0.0.0 (default value) 1601 (default value)
Step 7 See A.1.7.14 Querying IP Routes and query the ECC routes. The expected result is as follows: On NE1, l The routes to 129.9.0.2, 129.9.0.3, 129.9.0.4, 129.9.0.5, 130.9.0.6, and 130.9.0.0, the gateways are 129.9.0.2. l The route to 10.0.0.0, the gateway is 10.0.0.1. l The route to 11.0.0.100, the gateway is 10.0.0.200. On NE6, l The routes to 129.9.0.2, 130.9.0.3, 129.9.0.4, and 129.9.0.5, the gateways are 129.9.0.5. l The route to 10.0.0.0, 10.0.0.1, and 11.0.0.100, the gateways are 129.9.0.5. l The route to 130.9.0.0, the gateway is 130.9.0.6. Step 8 See A.1.1.1 Creating NEs by Using the Search Method and create the NEs on the centralized NMS. 10.0.0.1 is the search domain 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 On the GNE of the third-party equipment, configure a static route to the third-party NMS whose IP address is 11.0.0.100 (the gateway is the IP address of NE6, 130.9.0.6) On the third-party NMS, configure a static route to the GNE of the third-party equipment whose IP address is 130.9.0.7 (the gateway is the IP address of the router interface, 11.0.0.200). Alternatively, you can set the IP address 11.0.0.200 to the default gateway of the third-party NMS. On the router, configure the routes according to the GNE of the third-party equipment (the IP address of the GNE is 130.9.0.7).

This topic provides the hyper links of the operation tasks regarding the relevant feature.
1 DCN Features
Related Tasks
A.1.1.1 Creating NEs by Using the Search Method A.1.1.2 Creating NEs by Using the Manual Method A.1.1.4 Changing the NE ID A.1.7.1 Setting NE Communication Parameters A.1.7.2 Configuring DCCs A.1.7.5 Creating Static IP Routes A.1.7.6 Setting Parameters of the OSPF Protocol A.1.7.7 Enabling the ARP Proxy A.1.7.14 Querying IP Routes

Relevant Alarms
Relevant Events
None.
1.3.12 FAQs
This topic 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.
1-70
1 DCN Features
l l l l l
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.
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. 3. 4. 5. 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. 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. 6. 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.
1.4 OSI over DCC Solution

Using the OSI over DCC solution, NEs use unified DCCs to transmit the data of the TCP/OSI protocol. In this manner, the NMS can manage NEs. The OSI over DCC solution applies to a network that is comprised of the OptiX equipment and the third-party equipment that supports the OSI over DCC function. 1.4.1 Introduction This section provides the definition of OSI over DCC and describes its purpose. 1.4.2 Basic Concepts This topic describes the basic concepts that you need to be familiar with before you use the OSI over DCC solution. 1.4.3 Specifications
1 DCN Features
This section describes the specifications of OSI over DCC. 1.4.4 Reference Standards and Protocols This section describes the standards and protocols associated with OSI over DCC. 1.4.5 Availability This section describes the support required by the application of the OSI over DCC solution and its dependency. 1.4.6 Principles This section describes the principles of the OSI over DCC solution. 1.4.7 Planning Guidelines Follow certain planning guidelines when you plan OSI over DCC. 1.4.8 Configuration Procedure The configuration flow 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. 1.4.9 Configuration Example This section uses an example to describe how to plan and configure the OSI over DCC solution according to the network conditions. 1.4.10 Task Collection This task collection includes all the tasks related to features. 1.4.11 Relevant Alarms and Events When the communication between the U2000 and an NE fails, the U2000 reports the corresponding alarm. 1.4.12 FAQs This topic provides the answers to the questions that are frequently raised when the OSI over DCC solution is used.
1.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 1-37 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
1-72
Issue 02 (2011-01-20)
1 DCN Features
Figure 1-37 Application of the OSI over DCC solution

g Ms rty ck a -p ta 3rd SI s C O DC
3rd-party Msg OSI stack ETH Third-party NMS
g Ms tiX tack p O Is 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.

This topic describes the basic concepts that you need to be familiar with before you use the OSI over DCC solution. 1.4.2.1 OSI over DCC Protocol Stack The OSI over DCC adopts the architecture of the standard OSI protocol stack. 1.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.
1.4.2.1 OSI over DCC Protocol Stack

The OSI over DCC adopts the architecture of the standard OSI protocol stack.
Issue 02 (2011-01-20)
1-73
1 DCN Features

Figure 1-38 OSI over DCC protocol stack architecture
Transport layer Network layer TP4 IS-IS/ES-IS/CLNP LAPD Ethernet DCC
Data link layer Physical layer
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.
1-74
Issue 02 (2011-01-20)
1 DCN Features
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 1-39. Figure 1-39 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
NSE L
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 1-39 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 1-39 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
1 DCN Features
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 1-40, 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 1-40 Layered routes of IS-IS protocol routes (L2 not consecutive)
OSI DCN U2000
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.
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.
1-76
Issue 02 (2011-01-20)
1 DCN Features
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 1-41 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 1-41 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
NOTE
The LAPD roles of NE1 and NE3 can be exchanged but cannot be the same.

In the OSI over DCC solution, there are two modes for the NMS to access an NE: gateway access mode and direct access mode.
1 DCN Features
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.
This section describes the specifications of OSI over DCC. Table 1-10 lists the specifications of OSI over DCC supported by the OptiX RTN 980.
1-78
Issue 02 (2011-01-20)
1 DCN Features
Table 1-10 Specifications of OSI over DCC Item Number of DCC bytes SDH optical transmission line or SDH microwave Specifications l 3 bytes (D1-D3) l 9 bytes (D4-D12) l 12 bytes (D1-D12) PDH microwave (16xE1 or more) PDH microwave (less than 16xE1) Hybrid microwave CLNS protocol CLNP Format of the NSAP address 3 bytes (D1-D3) 1 byte (D1) 3 bytes (D1-D3) Supported Supports the simplified format consisting of Area ID, SYS ID, and NSEL. Supports Layer 1 and Layer 2 routes. Supported l It is recommended that the number of areas should not exceed 20. The maximum number is 32. l It is recommended that the number of NEs does not exceed 32. The maximum number is 50. Supported Supports the gateway access mode and direct access mode. 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.
IS-IS ES-IS Number of areas
Number of NEs in an area
OSI tunnel Access method Scale of the DCN subnet

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

Table 1-11 Hardware and version support Feature OSI over DCC solution Applicable Board CSHN SL4D (a logical board of the CSHN) SL1D IF1 IFU2 IFX2 ISU2 ISX2 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 V100R003C00 and later V100R003C00 and later V100R003C00 and later V100R003C00 and later V100R003C00 and later V100R003C00 and later V100R003C00 and later V100R003C00 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 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. The OSI protocol stack of NEs cannot communicate with the inband DCN 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.
1-80
1 DCN Features
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 network, you can adopt the OSI protocol to manage the OptiX equipment, but it is recommended that you use the HWECC protocol. 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. When the OptiX RTN 980 houses dual system control, switching, and timing boards, the Ethernet network management interfaces and the Ethernet NE stack interfaces on the two boards are equal to four ports on a hub. Note that an Ethernet loop cannot occur between any two ports.
1.4.6 Principles
This section describes the principles of the OSI over DCC solution.
Gateway Mode
Figure 1-42 illustrates how the OSI over DCC solution transfers NMS messages to a nongateway NE when the NMS adopts the gateway mode to access the NE. Figure 1-42 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
NMS
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 1-42 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
2. 3.
4.
Issue 02 (2011-01-20)
1 DCN Features
same as the address of the local station, the transfer NE queries the L1 routing table or the L2 routing table according to the destination NSAP address to obtain the corresponding route, and then transfers the packet. 5. 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 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 1-43 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 1-43 Realization principle of message transferring (direct connection mode)
Application TP4 ES-IS/CLNP IS-IS/ES-IS/CLNP LAPD Ethernet Ethernet DCC NMS 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 1.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.
1-82
Issue 02 (2011-01-20)
1 DCN Features
Planning Guidelines for GNEs

l l 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 has not more than 120 NEs. The maximum number of NEs on an ECC subnet is 150. 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. 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 meet 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.
Planning Guidelines for DCCs

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 flow 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 1-12 Procedure for the OSI over DCC solution Step 1 Operation A.1.1.4 Changing the NE ID 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.
1 DCN Features
Step 2
Operation A.1.7.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.1.7.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.1.7.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.1.7.9 Configuring the 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.1.7.3 Configuring Extended ECC Communication
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.
1-84
Issue 02 (2011-01-20)
1 DCN Features
Step
Operation
Description In the other cases, all the parameters take the default values.
A.1.7.15 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.
Creating NEs on the U2000
A.1.1.2 Creating NEs by Using the Manual Method A.1.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 U2000.

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

This section describes the networking information of the NEs. The OptiX wireless transmission equipment and the third-party wireless transmission equipment form the microwave transmission network, as shown in Figure 1-44. The total number of equipments on the network is more than 50. The third-party equipment supports only the OSI over DCC solution.
Issue 02 (2011-01-20)
1-85
1 DCN Features
Figure 1-44 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.
1-86
Issue 02 (2011-01-20)
1 DCN Features
Figure 1-45 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.

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.1.4 Changing the NE ID and modify the NE ID. The values for the related parameters are provided as follows.
1 DCN Features
Parameter
Value Range NE101 NE102 102 9 (default value) NE103 103 9 (default value)
New ID New Extended ID
101 9 (default value)
Step 2 See A.1.7.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.1.7.2 Configuring DCCs and configure the DCCs. The values for the related parameters are provided as follows. Parameter Value Range NE101 Enabled/Disabled Channel 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.1.7.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
1-88
NE102 L2
NE103 L1 (default value)

Issue 02 (2011-01-20)
L2
1 DCN Features
Step 5 See A.1.7.3 Configuring Extended ECC Communication 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.1.7.15 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. Step 7 See A.1.1.1 Creating NEs by Using the Search Method and create the NEs on the centralized NMS. 394F1200 is the search domain of NSAP. In normal situations, all the NEs can be created on the centralized NMS. ----End

This task collection includes all the tasks related to features.
Related Tasks
A.1.1.1 Creating NEs by Using the Search Method A.1.1.2 Creating NEs by Using the Manual Method A.1.1.4 Changing the NE ID A.1.7.1 Setting NE Communication Parameters A.1.7.2 Configuring DCCs A.1.7.8 Configuring the CLNS Role A.1.7.9 Configuring the OSI Tunnel A.1.7.15 Querying OSI Routes
Issue 02 (2011-01-20)
1-89
1 DCN Features

Relevant Alarms
Relevant Events
None.
1.4.12 FAQs
This topic 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.
1-90
Issue 02 (2011-01-20)
1 DCN Features
Q: Why does the NMS always fail to log in to an NE? A: Common causes are as follows: l The NMS is not installed with the OSI protocol stack or the router does not support the OSI protocol stack. If this is the case, the U2000 should fail to log in to all the NEs. l OSI routes fail. To locate the fault, query OSI routes on the NE. 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.
1.5 DCC Bytes Transparent Transmission Solution

Using the DCC bytes transparent transmission solution, vendors use different DCCs to transmit data. In this manner, communication of NM messages is realized when the vendors' equipment is used together with third-party equipment to form a network. 1.5.1 Introduction This section provides the definition of DCC bytes transparent transmission and describes its purpose. 1.5.2 Specifications This section describes the specifications of DCC bytes transparent transmission solution. 1.5.3 Availability This section describes the support required by the application of the DCC bytes transparent transmission solution and its dependencies. 1.5.4 Principles The OptiX equipment realizes the transparent transmission of DCC bytes through the overhead cross-connect matrix. 1.5.5 Planning Guidelines
1 DCN Features
Follow certain guidelines when you plan DCC bytes transparent transmission. 1.5.6 Configuration Procedure The configuration of the DCC bytes 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. 1.5.7 Configuration Example This section uses an example to describe how to plan and configure the DCC bytes transparent transmission solution according to network conditions. 1.5.8 Task Collection This topic provides the hyperlinks of the operation tasks regarding the relevant feature. 1.5.9 Relevant Alarms and Events When the communication between the U2000 and an NE fails, the U2000 reports the corresponding alarm. 1.5.10 FAQs This topic provides the answers to the questions that are frequently raised when the DCC bytes transparent transmission solution is used.
1.5.1 Introduction
This section provides the definition of DCC bytes transparent transmission and describes its purpose.
Definition
DCC bytes 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 1-46 DCC bytes 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
1-92
Issue 02 (2011-01-20)
1 DCN Features
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. Figure 1-47 DCC bytes 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 1-48 DCC bytes 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.
1 DCN Features
Figure 1-49 DCC bytes 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 bytes 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.
This section describes the specifications of DCC bytes transparent transmission solution. The OptiX RTN 980 supports the following specifications of DCC bytes transparent transmission solution. Table 1-13 Specifications of DCC bytes transparent transmission solution Item Number of DCC bytes Specifications SDH radio supports 12 DCC bytes, that is, D1-D12. The equipment supports the following modes: D1-D1, 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 980 uses bytes D1-D3, the third-party equipment uses bytes D4D12 as DCCs. l If the OptiX RTN 980 uses bytes D4-D12, the third-party equipment uses bytes D1D3 as DCCs.
Capacity of DCC transparent transmission
1-94
Issue 02 (2011-01-20)
1 DCN Features
1.5.3 Availability
This section describes the support required by the application of the DCC bytes transparent transmission solution and its dependencies.

Table 1-14 Hardware and version support Feature DCC bytes transparent transmission solution Applicable Board SL4D (a logical board of the CSHN) SL1D IF1 ISU2 ISX2 Applicable Hardware Version All the versions All the versions All the versions All the versions All the versions Applicable Product Version V100R003C00 and later V100R003C00 and later V100R003C00 and later V100R003C00 and later V100R003C00 and later
If you apply the DCC bytes 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.
1.5.4 Principles
The OptiX equipment realizes the transparent transmission of DCC bytes through the overhead cross-connect matrix. In the receiving direction: 1. The line unit 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 system control unit 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 unit. The CPU processes the NM messages carried by the DCC bytes according to the protocol stack of the DCCs.
2.
3.
In the transmitting direction:

1 DCN Features
1.
The CPU of the system control unit 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 system control. 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 unit. The line unit 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 1-50 shows how an NE uses bytes D1 to D3 as DCCs to transparently transmit bytes D4 to D12. Figure 1-50 Realization principle of the DCC bytes transparent transmission
D4-D12 Overhead crossconnect matrix D1-D3 CPU
SDH signal
Overhead bus
Overhead bus
SDH signal
Line processing unit
System control unit
Line processing unit

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

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 on DCC Bytes Transparent Transmission Routes

l l Set a DCC bytes 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.
1-96
1 DCN Features

The configuration of the DCC bytes 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 1-15 Procedure for the DCC bytes transparent transmission solution Step 1 Operation A.1.1.4 Changing the NE ID 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.1.7.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.1.7.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.1.7.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.
A.1.7.14 Querying IP Routes
Issue 02 (2011-01-20)
1-97
1 DCN Features
Step 6
Operation Creating NEs on the centralize d NMS A.1.1.2 Creating NEs by Using the Manual Method A.1.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.

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

This section describes the networking information about the NEs. In the networking diagram shown in Figure 1-51, 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.
1-98
Issue 02 (2011-01-20)
1 DCN Features
Figure 1-51 Networking diagram of the DCC bytes 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 bytes 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 02 (2011-01-20)
1-99
1 DCN Features
Figure 1-52 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.1.4 Changing the NE ID and change the NE ID. The values for the related parameters are provided as follows.
1-100
Issue 02 (2011-01-20)
1 DCN Features
Parameter
Value Range NE1
New ID New Extended ID
1 9 (default value)
Step 2 See A.1.7.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.1.7.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 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.1.7.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 02 (2011-01-20)
1-101
1 DCN Features
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.1.7.13 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.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 domain 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

Related Tasks
A.1.1.1 Creating NEs by Using the Search Method A.1.1.2 Creating NEs by Using the Manual Method A.1.7.2 Configuring DCCs A.1.7.4 Configuring DCC Transparent Transmission

Relevant Alarms
l GNE_CONNECT_FAIL The GNE_CONNECT_FAIL alarm indicates that the connection to the gateway fails. When the communication between the U2000 and the GNE fails, the U2000 reports this alarm. l
1-102
NE_COMMU_BREAK
1 DCN Features
The NE_COMMU_BREAK alarm indicates that the NE communication is interrupted. When the communication between the U2000 and the NE is interrupted, the U2000 reports this alarm. l NE_NOT_LOGIN The NE_NOT_LOGIN alarm indicates that the login to the NE fails. When the U2000 cannot log in to the NE, the U2000 reports this alarm.
Relevant Events
None.
1.5.10 FAQs
This topic provides the answers to the questions that are frequently raised when the DCC bytes transparent transmission solution is used. Q: Compared with other solutions for communicating NM information, what advantages and disadvantages does the DCC bytes 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 number 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 bytes 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 bytes transparent transmission with the maintenance staff of third-party 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.
1.6 DCC Transmission Through the External Clock Interface Solution

Using the DCC transmission through the external clock interface solution, DCC bytes are placed in a specified E1 and then transmitted through third-party network. In this case, the transmission bandwidth of one E1 is occupied. Hence, this solution is adopted only when a PDH network or
1 DCN Features
a network that does not support transparent transmission of DCC bytes exists on the transmission path of NM messages. 1.6.1 Introduction This section provides the definition of DCC transmission through the external clock interface and describes its purpose. 1.6.2 Specifications This section describes the specifications of DCC transmission through the external clock interface. 1.6.3 Availability This section describes the support required by the application of the DCC transmission through the external clock interface solution and its dependencies. 1.6.4 Principles This section describes the principles of DCC transmission through the external clock interface. 1.6.5 Planning Guidelines Follow certain guidelines when you plan DCC transmission through the external clock interface. 1.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. 1.6.7 Configuration Example This topic uses an example to describe how to plan and configure the DCC bytes transparent transmission solution according to the actual network conditions through a detailed example. 1.6.8 Task Collection This topic provides the hyperlinks of the operation tasks regarding the DCC transmission through the external clock interface feature. 1.6.9 Relevant Alarms and Events When there is a fault in communication between the U2000 and an NE, the U2000 reports the corresponding alarm. 1.6.10 FAQs This topic provides the answers to the questions that are frequently raised when the DCC transmission through the external clock interface solution is used.
1.6.1 Introduction
This section provides the definition of DCC transmission through the external clock interface and describes its purpose.
Definition
DCC 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 transmission through the external clock interface solution:
1 DCN Features
Direct access mode An NE is directly connected to the third-party network through the external clock interface. Figure 1-53 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 1-53 Networking example for the DCC transmission through the external clock interface solution (direct access mode)
External clock interface DCC bytes E1 cable PDH netw ork External clock interface DCC bytes E1 cable
Indirect access mode An NE is connected to the third-party network through a service interface. Figure 1-54 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. Figure 1-54 Networking example for the DCC 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
Issue 02 (2011-01-20)
1-105
1 DCN Features
Purpose
DCC 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.
This section describes the specifications of DCC transmission through the external clock interface. The OptiX RTN 980 supports the following specifications of DCC transmission through the external clock interface. Table 1-16 Specifications of DCC transmission through the external clock interface Item Number of external clock interfaces Specifications Each board can support one external clock interface. 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. When the OptiX RTN 980 is configured with two CSHN boards. Only the external clock interface of the CSHN in slot 15 can transmit DCC byte transparently. Specifications of external clock interfaces Compliant with ITU-T G.703. The impedance is 120 ohms.
1.6.3 Availability
This section describes the support required by the application of the DCC transmission through the external clock interface solution and its dependencies.
1-106
Issue 02 (2011-01-20)
1 DCN Features

Table 1-17 Hardware and version support Feature DCC transmission through the external clock interface solution Applicable Board CSHN Applicable Hardware Version All the versions Applicable Product Version V100R003C00 and later
l If you apply the DCC 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. When the OptiX RTN 980 is configured with two CSHN boards. Only the external clock interface of the CSHN in slot 15 can transmit DCC byte transparently.
1.6.4 Principles
This section describes the principles of DCC transmission through the external clock interface. In the receiving direction: 1. The clock unit 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 system control unit 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 transmitting direction: 1. The CPU of the system control unit encapsulates the NM messages into the DCC bytes according to the protocol stack and transmits the DCC bytes to the overhead cross-connect matrix. 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 calls and synchronous/ asynchronous data services) to form a 2.048 Mbit/s overhead signal stream, and then transmits the overhead signal stream to the clock unit. Through the external clock interface, the clock unit transmits the 2.048 Mbit/s overhead signals as an E1 service to third-party network.
2.
3.
Figure 1-55 shows how an NE transparently transmits DCC bytes through the external clock interface. In this example, DCC bytes D1 to D3 carry the NM messages.
Issue 02 (2011-01-20)
1-107
1 DCN Features
Figure 1-55 Realization principle of the DCC transmission through the external clock interface
External clock interface Overhead bus Clock unit
Overhead crossconnect matrix D1-D3 CPU
System control unit

Follow certain guidelines when you plan DCC transmission through the external clock interface. l l l l When the OptiX equipment interconnects with third-party network through E1 interfaces, adopt the direct access mode. When the OptiX equipment interconnects with third-party 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. Table 1-18 Procedure for configuring the solution of transparently transmitting DCCs through the external clock interface Step 1 Operation A.1.7.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.
NOTE On the NMS interface, the first interface on the system control, switching, and clock board (like ) corresponds to its external clock interface.
1-108
Issue 02 (2011-01-20)
1 DCN Features
Step 2
Operation A.4.1 Creating the Cross-Connections of Point-to-Point Services
Remarks 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 topic uses an example to describe how to plan and configure the DCC bytes transparent transmission solution according to the actual network conditions through a detailed example. 1.6.7.1 Networking Diagram The section describes the networking information of the NEs. 1.6.7.2 Service Planning The service planning information contains all the parameters required for configuring the NE data. 1.6.7.3 Configuration Process This topic describes the procedure for the data configuration.

The section describes the networking information of the NEs. Figure 1-56 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. Figure 1-56 Networking example for the DCC transmission through the external clock interface solution
NE1 NMS
NE2
NE3
NE4
OptiX equipment
Network cable Radio link
E1 cable Fiber
Issue 02 (2011-01-20)
1-109
1 DCN Features

The service planning information contains all the parameters required for configuring the NE data. l l l NE1 is connected to the third-party equipment through the SDH line, so the indirect connection mode is used. NE2 is connected to the third-party equipment through E1 service transmission, so the direct connection mode is used. NE1 and NE2 use bytes D1 to D3 to transmit NM messages.

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.
Procedure
Step 1 See A.1.7.2 Configuring DCCs and configure the DCC channel. The values for the related parameters are provided as follows. Parameter Value Range (NE1) Enabled/Disabled Channel Protocol Type Enabled D1-D3 (default value) HWECC (default value) (NE2) Enabled D1-D3 (default value) HWECC (default value)
NOTE
On the NMS interface, the first interface on the system control, switching, and clock board (like ) corresponds to its external clock interface.
Step 2 See A.4.1 Creating the 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
1-110
VC-12 (default value)

1 DCN Features
Parameter
Value Range NE1
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)
Bidirectional (default value)
1 1
----End

This topic provides the hyperlinks of the operation tasks regarding the DCC transmission through the external clock interface feature.
Related Tasks
A.1.7.2 Configuring DCCs A.4.1 Creating the Cross-Connections of Point-to-Point Services

When there is a fault in communication between the U2000 and an NE, the U2000 reports the corresponding alarm.
Relevant Alarms
Relevant Events
None.
1 DCN Features
1.6.10 FAQs
This topic provides the answers to the questions that are frequently raised when the DCC transmission through the external clock interface solution is used. Q: Which of the DCC 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 transmission through the external clock interface solution. This is because the extended ECC consumes much less system resources than the DCC transmission through the external clock interface. Q: Can the external clock interface be used to transparently transmit orderwire overhead bytes when the DCC 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 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 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.
1.7 Inband DCN Solution

With the inband DCN solution, certain service bandwidths are used to transmit the NM message between the NEs. This solution is applicable when the network is comprised of the OptiX RTN 980 equipment and the OptiX packet transmission equipment. 1.7.1 Introduction This section provides the definition of inband DCN solution and describes its purpose. 1.7.2 Basic Concepts This topic describes the basic concepts that you need to be familiar with before you use the inband DCN solution. 1.7.3 Specifications
1 DCN Features
This section describes the specifications of inband DCN. 1.7.4 Availability This section describes the support required by the application of the inband DCN solution and its dependency. 1.7.5 Principles This section describes the principles of inband DCN solution. 1.7.6 Planning Guidelines Follow certain guidelines when you plan inband DCN. 1.7.7 Configuration Procedure The configuration of the inband DCN solution consists of two parts, namely, the configuration of communications data at the near end and the creation of NEs on the NMS. 1.7.8 Configuration Example This section uses an example to describe how to plan and configure the inband DCN transmission solution according to network conditions. 1.7.9 Task Collection This topic provides the hyperlinks of the operation tasks regarding the relevant feature. 1.7.10 Relevant Alarms and Events When the communication between the U2000 and an NE fails, the U2000 reports the corresponding alarm. 1.7.11 FAQs This topic provides the answers to the questions that are frequently raised when the inband DCN solution is used.
1.7.1 Introduction
This section provides the definition of inband DCN solution and describes its purpose.
Definition
The inband DCN refers to the DCN communication mode that uses service paths provided by the managed equipment. With the inband DCN solution, the NM message is encapsulated in the specified Ethernet frame and is transmitted with the packet service signal over the service channel. Figure 1-57 shows how network management messages are transmitted by using the inband DCN solution. A characteristic of the inband DCN mode is the convenient and flexible networking that does not require additional equipment.
Issue 02 (2011-01-20)
1-113
1 DCN Features
Figure 1-57 Application of the inband DCN solution

OptiX Msg IP stack Hybrid MW
NMS
OptiX Msg IP stack ETH
OptiX Msg IP stack Inband DCN
OptiX Msg IP stack FE/GE
OptiX RTN 910/950
OptiX PTN equipment
Ethernet link
Purpose
When the OptiX RTN 980 equipment is interconnected with the OptiX packet transmission equipment through the packet microwave or FE/GE interface, the inband DCN solution can be adopted. In addition, the inband DCN solution provides service ports to connect to the network management system. The network management center (NMC) can obtain network management packets after the VLAN switch decapsulates VLAN packets. In this manner, a network management server does not need to be directly connected to the network management port of an OptiX RTN 980.

This topic describes the basic concepts that you need to be familiar with before you use the inband DCN solution. 1.7.2.1 Inband DCN Protocol Stack The inband DCN solution generally uses the optimized TCP/IP protocol stack. Alternatively, the inband DCN solution can use the HWECC protocol stack. 1.7.2.2 NMS Access Modes In the inband DCN solution, there are two modes for the NMS to access an NE: gateway access mode and direct access mode. 1.7.2.3 Access Control The OptiX RTN 980 can use the access control function so that the NE can be connected to the NMS through an Ethernet service port.
1.7.2.1 Inband DCN Protocol Stack

The inband DCN solution generally uses the optimized TCP/IP protocol stack. Alternatively, the inband DCN solution can use the HWECC protocol stack.

NOTE
1 DCN Features
If using the HWECC protocol, the OptiX RTN equipment can exchange network management messages with more types of OptiX equipment. If using the TCP/IP protocol, the OptiX RTN equipment can transparently transmit network management messages to more types of third-party equipment.
Inband DCN Protocol Stack Based on the TCP/IP Protocol Stack

Figure 1-58 Architecture of the inband DCN protocol stack based on the TCP/IP protocol stack
Routing protocol Transport layer Network layer Data link layer Physical layer OSPF TCP/UDP IP
PPP PPPoE MAC
FE/GE/Microwave
Physical Layer The main function of the physical layer is to provide data transmission channels for the data end equipment. The physical layer path used by the inband DCN is the Ethernet path provided by the microwave interface or FE/GE interface.
Data Link Layer The main function of the data link layer is to provide reliable data transmission on physical links. The inband DCN realizes the data link layer function by using the PPPoE protocol and PPP protocol. The PPPoE protocol is used to establish the point-to-point connection, to establish the PPP interface for the PPP protocol, and to encapsulate the PPP packet into the MAC frame for transmission to the opposite end. The PPP protocol controls the creation, removal, and monitoring of the link, coordinates the format and type of the carried network layer data packet, and adopts the handshake mechanism to guarantee the safe transmission of the packet. The inband DCN packet is encapsulated in the specified Ethernet frame: The inband DCN packet has the VLAN ID. This VLAN ID is called the management VLAN ID, which is used to distinguish the inband DCN packet and the service packet. The management VLAN ID is 4094 by default and can be changed as required. The inband DCN packet occupies the specified Ethernet bandwidth. In the transmit direction of the Ethernet port, a specified buffer queue is used to perform the traffic control on the inband DCN packet. The bandwidth of an inband DCN packet takes the value 512 kbit/s by default and can be changed as required.
Network Layer, Transport Layer, and Routing Protocols The inband DCN protocol stack using TCP/IP has the same network layer, transport layer, and routing protocols as the IP over DCC protocol stack. For details, see 1.3.2.1 IP over DCC Protocol Stack.
Issue 02 (2011-01-20)
1-115
1 DCN Features
Inband DCN Protocol Stack Based on the HWECC Protocol Stack

Figure 1-59 Architecture of the inband DCN protocol stack based on the HWECC protocol stack
Transport layer Network layer Data link layer Physical layer L4 Net
PPP PPPoE MAC
FE/GE/Microwave
This type of inband DCN protocol stack has the following features: l The same as the inband DCN protocol stack based on the TCP/IP protocol stack at the physical layer and data link layer, this type of inband DCN protocol stack uses the PPP and PPPoE protocols to maintain point-to-point connections. The same as the HWECC solution at the network layer and transport layer, this type of inband DCN protocol stack uses the Net and L4 protocols to maintain routing information and to forward packets. For details, see 1.2.2.1 HWECC Protocol Stack

In the inband DCN 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 refers to the routing table with NEID as the NE identification, which combines the routing tables of all the 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 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 IP routing protocols. It includes both dynamic routes generated by routing protocols and static routes configured by operators. Each route item includes the following:
1 DCN Features
l l l l
Destination IP address Subnet Mask IP address of the gateway Interface
When the NMS applies the direct access mode to access an NE, there must be an IP route between the NMS and the NE. In the inband DCN 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.
1.7.2.3 Access Control

The OptiX RTN 980 can use the access control function so that the NE can be connected to the NMS through an Ethernet service port. Figure 1-60 shows the typical application of the access control function. The PSN transmits DCN packets between the NMS and the GNE when transmitting Ethernet services. In this case, the Ethernet service port on the GNE can be enabled with the access control function. Figure 1-60 Access control
NMS Inband DCN packets
LAN switch
Packet Switch Network
FE/GE Access enabled
Router Ethernet service packets FE/GE Access enabled
After the Ethernet service port on the GNE is enabled with the access control function, l The Ethernet service port functions as an Ethernet network management interface on the GNE.
Issue 02 (2011-01-20)
1 DCN Features
l l
The IP address of the service port can be specified according to the requirement of the PSN, but cannot be in the same segment as the IP address of the local NE. The DCN packet transmitted/received at the service port is tagged with a VLAN ID. Before the DCN packet arrives at the NMS, the VLAN ID needs to be stripped off by an NE (for example, the LAN switch in the figure). The NMS can communicate with the GNE based on the IP address of the service port on which the access control function is enabled.
This section describes the specifications of inband DCN. Table 1-19 lists the specifications of inband DCN supported by the OptiX RTN 980. Table 1-19 Specifications of the inband DCN solution Item DCC channel Channel type Specifications l FE/GE port l Integrated IP radio microwave port Range of used VLAN IDs Range of bandwidth Protocol stack 2 to 4094 64 kbit/s to 1000 kbit/s. This parameter is set according to the channel type. l IP (by default) l HWECC Route type l Direct route l Static route l Dynamic route Dynami c routing protoco l Protocol type OSPF routing type Type of the interface on which the OSPF protocol is enabled OSPF Supports only the routes within an area but does not support the routes between areas. l DCC interface (enabled by default) l LAN interface (disabled by default)
NOTE l A DCC interface refers to an interface at which the DCN packet is transmitted through the DCC bytes. l A LAN interface refers to an Ethernet network management interface or NE stack interface.
1-118
Issue 02 (2011-01-20)
1 DCN Features
Item OSPF parameters
Specifications Supports the settings of the following parameters: l Area l Hello packet timer l Neighbor failure time l Packet retransmission timer l Transmission hold-off time OSPF route diffusion Supports the import of external routes according to the route type. The supported external route types include: l Direct route l Static route l RIP route
Access method
l Supports the gateway access mode and direct access mode when the IP protocol is used. l Supports the gateway access mode when the HWECC protocol is used.
Access control 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.
1.7.4 Availability
This section describes the support required by the application of the inband DCN solution and its dependency.

Table 1-20 Hardware and version support Feature Inband DCN Solution Applicable Board EG2D (a logical board integrated on the CSHN) IFU2 IFX2 Applicable Hardware Version All the versions Applicable Product Version V100R003C00 and later V100R003C00 and later V100R003C00 and later
All the versions All the versions
Issue 02 (2011-01-20)
1-119
1 DCN Features
Feature
Applicable Board ISU2 ISX2 EM6T EM6F
Applicable Hardware Version All the versions All the versions All the versions All the versions All the versions
Applicable Product Version V100R003C00 and later V100R003C00 and later V100R003C00 and later V100R003C00 and later V100R003C00 and later V100R003C00 and later V100R003C00 and later
Access Control
EG2D (a logical board integrated on the CSHN) EM6T EM6F
All the versions All the versions
Feature Dependency
When the inband DCN solution is used with other DCN solutions, pay attention to the relations between the inband DCN solution and other DCN solutions. l l l l The inband DCN protocol stack of NEs can communicate with the HWECC protocol stack. The inband DCN protocol stack of NEs can communicate with the IP over DCC protocol stack. The inband DCN protocol stack of NEs cannot communicate with the OSI over DCC protocol stack. When the OptiX RTN 980 houses dual system control, switching, and timing boards, the Ethernet network management interfaces and the Ethernet NE stack interfaces on the two boards are equal to four ports on a hub. Note that an Ethernet loop cannot occur between any two ports.
1.7.5 Principles
This section describes the principles of inband DCN solution.
Inband DCN Packet Forwarding Flow

Figure 1-61 illustrates how the inband DCN using the IP protocol transfers the messages originating from the NMS to the destination NE when the NMS applies the gateway mode to access the non-gateway NE. The same realization principle goes to the inband DCN using the HWECC protocol.
1-120
Issue 02 (2011-01-20)
1 DCN Features
Figure 1-61 Realization principle of packet forwarding

Application TCP IP Application TCP IP UDP IP PPP PPPoE
FE/GE/ Microwave
Application UDP IP PPP PPPoE

FE/GE/ Microwave
IP PPP PPPoE
FE/GE/ Microwave
Ethernet
Ethernet
NMS
Gateway NE
Transfer NE
Destination NE
The realization principle is as follows: 1. 2. 3. The NMS transfers application layer messages to the gateway NE through the TCP/IP 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 processes the packet according to the address of the destination NE. (1) 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. (2) The gateway NE encapsulates the packet into the Ethernet data frame again, adds the VLAN ID that indicates a DCN packet, and forward the DCN packet to the corresponding port. 4. On 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 Ethernet data packet, the destination NE sends the DCN packet with a management VLAN ID to the upper layer for processing. The destination IP address of the DCN packet is the IP address of the local NE. Thus, the DCN packet is transmitted from the transmission layer to the application layer. The application layer functions according to the message sent from the NMS.
5.
Inband DCN Packet Forwarding Flow

Inband DCN packets are transmitted and received by the packet switching unit and the system control unit. l Transmit Direction 1. The system control unit encapsulates the inband DCN packets into the Ethernet data frames, adds a management VLAN IDs, and forward the Ethernet frames to the packet switching unit.
Issue 02 (2011-01-20)
1 DCN Features
2.
The packet switching unit puts the Ethernet frames to the DCN buffer queue at the egress port, and transmits the Ethernet frames through the port according to the preset DCN bandwidth. The packet switching unit identifies the Ethernet frames containing the inband DCN packets according to the management VLAN IDs, and then transmits the Ethernet frames to the system control unit. The system control unit decapsulates the inband DCN packets from the Ethernet frames.
Transmit Direction 1.
2.

Follow certain guidelines when you plan inband DCN.
Planning Guidelines on VLAN IDs and Bandwidth

l l l On one subnet (composed of one GNE and the non-GNEs under its control), the management VLAN IDs of all NEs must be the same. The management VLAN ID used for inband DCN must be different from the VLAN ID carried by Ethernet services. It is recommended that you use default values. The bandwidth of inband DCN can be determined according to the number of NEs on a subnet. It is recommended that you use default values.
Planning Guidelines on Inband DCN Channels

l When the equipment is interconnected with the packet equipment that adopts inband DCN through the FE/GE interface or microwave port, you need to enable the inband DCN function on the FE/GE interface or microwave port. In other cases, it is recommended that you disable the inband DCN function on the FE/GE interface or microwave port so that the external DCN scheme can be used only. It is recommended that the number of inband DCN channels between two NEs should not exceed two.
l l
Planning Guidelines on Protection Types

l When the equipment is interconnected with the packet equipment that adopts inband DCN, the types of protocols enabled at both ends should be the same. It is recommended that you adopt the IP protocols. When the number of NEs on an inband DCN exceeds 64, you need to use the HWECC protocol.

l 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 carries the largest number of DCN channels. 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. 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.
1-122
1 DCN Features

Follow these principles when planning the IP addresses of NEs: l l l Set the IP addresses of NEs for the most simplified route settings. The IP address, subnet mask, and default gateway of the GNE must meet the planning requirements of external DCN. Set the IP address of a non-GNE according to the NE ID.
NOTE
l The IP address of a non-GNE is 0x81000000+ID. For example, if the NE ID is 0x090001, set the IP address to 129.9.0.1. l By default, the subnet mask is 255.255.0.0.
Planning Guidelines on Access Control

Follow these principles when planning access control: l l l When the GNE needs to communicate with the NMS through an Ethernet service port, enable the access control function on the service port. The IP address of the service port on which the access control function is enabled cannot be in the same network segment as that of the NMS. When being transmitted/received at the service port on which the access control function is enabled, the DCN packet is tagged with a VLAN ID. Therefore, before the DCN packet arrives at the NMS, the VLAN ID needs to be stripped off by equipment (for example, a LAN switch). It is recommended that the NMS should communicate with the GNE through the IP address of the service port on which the access control function is enabled.

The configuration of the inband DCN solution consists of two parts, namely, the configuration of communications data at the near end and the creation of NEs on the NMS. Table 1-21 Procedure for communications data at the near end Step 1 Operation A.1.1.4 Changing the NE ID 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.
Issue 02 (2011-01-20)
1-123
1 DCN Features
Step 2
Operation A.1.7.1 Setting NE Communication Parameters
Remarks 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 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.
Required on a GNE. Set the major parameters as follows: l Set ECC Extended Mode to Specified mode. l The other parameters take the default values.
NOTE This operation is performed to disable the automatic ECC function of the GNE.
A.1.7.10 Configuring the VLAN ID and Bandwidth Used by an Inband DCN
This operation is performed when the equipment is connected to the packet equipment that adopts inband DCN and the VLAN ID and bandwidth planned for the packet equipment on the inband DCN is not the default value (the default VLAN ID is 4094 and the default bandwidth is 512 kbit/s). Required. Set the parameters as follows: For the Ethernet port that needs to communicate with other NEs through the inband DCN, set Enabled Status to Enabled. When the HWECC protocol is required, set Protocol Type to HWECC. Required when the GNE needs to communicate with the NMS through an Ethernet service port. Set the major parameters as follows: l For the Ethernet service port, set Enabled Status to Enabled. In addition, set IP Address and Subnet Mask according to parameter planning. l Set IP Address to a different network segment from that of the local NE.
A.1.7.11 Configuring the Enable Status of the Inband DCN Function on Ports A.1.7.12 Configuring the Protocol Type of the Inband DCN A.1.7.16 Configuring Access Control
1-124
Issue 02 (2011-01-20)
1 DCN Features
Step 6
Operation Creating NEs on the centralize d NMS A.1.1.2 Creating NEs by Using the Manual Method A.1.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.
NOTE
You can use the Web LCT to configure the communication data on the NE at the near end. For details, see the Feature Description (Web LCT).

This section uses an example to describe how to plan and configure the inband DCN transmission solution according to network conditions. 1.7.8.1 Networking Diagram This section describes the networking information about the NEs. 1.7.8.2 Service Planning The service planning information contains the information about all the parameters required for configuring the NE data. 1.7.8.3 Configuration Process This topic describes the procedure for the data configuration.

This section describes the networking information about the NEs. In the networking diagram shown in Figure 1-62, the OptiX RTN 980 and the OptiX PTN packet transmission equipment form a network. The OptiX RTN 980 is interconnected with the OptiX PTN equipment through the packet microwave link and the GE optical line. The NMS manages the OptiX RTN 980 and the OptiX PTN packet transmission equipment in a unified manner.
Issue 02 (2011-01-20)
1-125
1 DCN Features
Figure 1-62 Networking diagram of the inband DCN solution

NMS
Network cable
GE NE1 GE
Packet radio link
Hybrid Radio Network
NE7 NE2 NE4 GE NE3 GE NE5 NE6 GE
NE8
OptiX RTN 900
OptiX PTN Equipment

GE line
Radio link
Network cable

The service planning information contains the information about all the parameters required for configuring the NE data. l l l The NMS manages the OptiX RTN 980 and the OptiX PTN packet transmission equipment in a unified manner. Select NE1 that is the closest to the NMS as GNE. Allocate IDs and IP addresses for all the NEs according to the conditions of the network.
1-126
Issue 02 (2011-01-20)
1 DCN Features
Figure 1-63 Allocation of IDs/IP addresses for all the NEs

NMS
10.0.0.100
9-1 10.0.0.1 0.0.0.0
GE
Packet radio link GE

9-7 129.9.0.7 0.0.0.0
NE1
9-2 129.9.0.2 0.0.0.0 9-4 129.9.0.4 0.0.0.0
9-7 129.9.0.8 0.0.0.0
NE7
NE8
NE2
9-3 129.9.0.3 0.0.0.0
NE4 GE GE

9-5 129.9.0.5 0.0.0.0 9-6 129.9.0.6 0.0.0.0
NE3 GE
Extended ID-Basic ID IP address Gateway
NE5
NE6
Plan the management VLAN ID and bandwidth of the inband DCN. The management VLAN ID uses the default value 4094. If the number of NEs is not greater than 50, set the bandwidth of the inband DCN to 512 kbit/s (default value).
Plan the channel for the inband DCN. The inband DCN function is enabled on all the service ports on the OptiX PTN packet transmission equipment. For the OptiX RTN 980 that is interconnected with the OptiX PTN packet transmission equipment, enable the inband DCN function on the port that is connected to the OptiX PTN packet transmission equipment and disable the inband DCN function on the other ports. For the OptiX RTN 980 that is not directly interconnected with the OptiX PTN packet transmission equipment, disable the inband DCN function on all the ports. Adopt the HWECC solution between OptiX RTN 980s.

Context
NOTE
In this configuration example, only the configuration information about NE5 and NE7 is provided.
Issue 02 (2011-01-20)
1-127
1 DCN Features
Procedure
Step 1 See A.1.1.4 Changing the NE ID and change the NE ID. The values for the related parameters are provided as follows. Parameter Value Range NE5 New ID New Extended ID 5 9 (default value) NE7 7 9 (default value)
Step 2 See A.1.7.1 Setting NE Communication Parameters and set the communication parameters for the NE. The values for the related parameters are provided as follows. Parameter Value Range NE5 IP Address Gateway IP Address Subnet Mask 129.9.0.5 0.0.0.0 (default value) 255.255.0.0 (default value) NE7 129.9.0.7 0.0.0.0 (default value) 255.255.0.0 (default value)
Step 3 See A.1.7.11 Configuring the Enable Status of the Inband DCN Function on Ports and configure the Enabled Status of the inband DCN function on ports. The values for the related parameters are provided as follows. Parameter Value Range NE5 GE Port That Is Connected to NE3 Other Ports NE7 Internal Ethernet Port (on the IF Board) That Is Connected to NE4 Enabled Other Ports
Enabled Status
Enabled
Disabled
Disabled
Step 4 See A.1.7.10 Configuring the VLAN ID and Bandwidth Used by an Inband DCN and set the VLAN ID and bandwidth used by the inband DCN. The values for the related parameters are provided as follows.
1-128
Issue 02 (2011-01-20)
1 DCN Features
Parameter
Value Range NE5 NE7 4094 (default value) 512 (default value)
Ethernet Board VLAN ID Bandwidth(Kbit/s)
4094 (default value) 512 (default value)
Step 5 See A.1.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 domain 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

Related Tasks
A.1.1.1 Creating NEs by Using the Search Method A.1.1.2 Creating NEs by Using the Manual Method A.1.1.4 Changing the NE ID A.1.7.1 Setting NE Communication Parameters A.1.7.10 Configuring the VLAN ID and Bandwidth Used by an Inband DCN A.1.7.11 Configuring the Enable Status of the Inband DCN Function on Ports A.1.7.12 Configuring the Protocol Type of the Inband DCN A.1.7.16 Configuring Access Control A.1.7.6 Setting Parameters of the OSPF Protocol A.1.7.5 Creating Static IP Routes A.1.7.14 Querying IP Routes A.1.7.13 Querying ECC Routes

Relevant Alarms
l GNE_CONNECT_FAIL The GNE_CONNECT_FAIL alarm indicates that the connection to the gateway fails. When the communication between the U2000 and the GNE fails, the U2000 reports this alarm. l
Issue 02 (2011-01-20)
NE_COMMU_BREAK
1 DCN Features
The NE_COMMU_BREAK alarm indicates that the NE communication is interrupted. When the communication between the U2000 and the NE is interrupted, the U2000 reports this alarm. l NE_NOT_LOGIN The NE_NOT_LOGIN alarm indicates that the login to the NE fails. When the U2000 cannot log in to the NE, the U2000 reports this alarm.
Relevant Events
None.
1.7.11 FAQs
This topic provides the answers to the questions that are frequently raised when the inband DCN solution is used. Q: Compared with other solutions for communicating NM information, what advantages does the inband DCN solution have? A: Main advantages are as follows: l l No special external DCN network is required. The management packet and the service packet are transmitted through the service port. The inband DCN packet can be transmitted over the third-party network. This facilitates the remote access of the NMS.
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 GNE and a non-GNE is faulty. To locate the fault, check the IP route between the GNE and the non-GNE.
1-130
Issue 02 (2011-01-20)
2 Microwave Features
2
About This Chapter
Microwave Features
This chapter describes the microwave features associated with the OptiX RTN 980. 2.1 1+1 HSB The 1+1 HSB is a configuration mode of 1+1 protection. In 1+1 HSB protection mode, the equipment provides a 1+1 hot standby configuration for the IF board and ODU at the two ends of each hop of a radio link to realize the protection. 2.2 1+1 FD The 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 signal. The opposite end selects the signal from the two received signals. With the 1+1 FD protection, the impact of the fading on signal transmission is reduced. 2.3 1+1 SD 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 the 1+1 SD protection, the impact of the fading on signal transmission is reduced. 2.4 Cross-Polarization Interference Cancellation The cross-polarization interference cancellation (XPIC) technology is used together with the cochannel dual-polarization (CCDP) technology. The application of the two technologies doubles the transmission capacity with channel conditions unchanged. 2.5 N+1 Protection The N+1 protection refers to the protection scheme in which N working channels in a microwave direction share one protection channel. When the N+1 protection is configured, the transmission bandwidth in a microwave direction increases and is protected. 2.6 Automatic Transmit Power Control The automatic transmit power control (ATPC) function is an important function of a radio transmission system. The ATPC function reduces the interference of a transmitter to adjacent systems and also reduces the residual bit error rate. 2.7 Adaptive Modulation
Issue 02 (2011-01-20)
2-1
The main feature of the Integrated IP radio is the adaptive modulation (AM) function.
2-2
Issue 02 (2011-01-20)
2.1 1+1 HSB

The 1+1 HSB is a configuration mode of 1+1 protection. In 1+1 HSB protection mode, the equipment provides a 1+1 hot standby configuration for the IF board and ODU at the two ends of each hop of a radio link to realize the protection. 2.1.1 Introduction This section provides the definition of 1+1 HSB and describes its purpose. 2.1.2 Basic Concepts This topic describes the basic concepts that you need to be familiar with before you use the 1+1 HSB feature. 2.1.3 Specifications This topic provides the specifications of 1+1 HSB. 2.1.4 Availability The 1+1 HSB feature requires the support of the applicable boards. 2.1.5 Principles The switching principle of SDH/PDH radio 1+1 HSB is different from the switching principle of Integrated IP radio 1+1 HSB. 2.1.6 Planning Guidelines Follow certain guidelines when you plan 1+1 HSB. 2.1.7 Configuration Procedure When configuring the 1+1 HSB radio link, configure the 1+1 IF protection group first, and then configure the IF/ODU information. 2.1.8 Configuration Example This section uses an example to describe how to plan and configure the 1+1 HSB radio link according to the actual network conditions through a detailed example. 2.1.9 Task Collection This topic provides the hyperlinks of the operation tasks regarding the 1+1 HSB feature. 2.1.10 Relevant Alarms and Events When a 1+1 HSB switching occurs on IF boards, the system reports corresponding alarms and abnormal events. 2.1.11 FAQs This topic provides the answers to the questions that are frequently raised when the 1+1 HSB is used.
2.1.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 2-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 2-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.

This topic describes the basic concepts that you need to be familiar with before you use the 1+1 HSB feature. 2.1.2.1 System Configuration The OptiX RTN 980 supports one to seven 1+1 HSB protection groups. 2.1.2.2 Protection Type The 1+1 HSB protection is classified into the revertive mode and the non-revertive mode. 2.1.2.3 Switching Conditions The switching priority varies according to the switching condition.
2.1.2.4 Switching Impact Within the 1+1 HSB switching time, the service is interrupted.
2.1.2.1 System Configuration

The OptiX RTN 980 supports one to seven 1+1 HSB protection groups. 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
The hybrid coupler can be balanced or unbalanced. Generally, the unbalanced hybrid coupler is used.
Figure 2-2 shows a typical configuration of one 1+1 HSB protection group on the OptiX RTN 980. Figure 2-2 Typical configuration of one 1+1 HSB protection group
ODU
Hybrid coupler
Antenna
ODU
PIU
PIU
FAN
System control, Switch & Clock board
IF board IF board
IDU
Issue 02 (2011-01-20)
2-5
2.1.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.
2.1.2.3 Switching Conditions

The switching priority varies according to the switching condition. Table 2-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.
2-6
Issue 02 (2011-01-20)
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 2-2.
Fault on the main equipment
Issue 02 (2011-01-20)
2-7
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, automatic 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)
2-8
Issue 02 (2011-01-20)
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 2-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 MW_LOF MW_RDI Fault on the IF connection cable R_LOF R_LOS (IF1) XPIC_LOS (IFX2, ISX2) Priority At the same priority
Issue 02 (2011-01-20)
2-9
2.1.2.4 Switching Impact

Within the 1+1 HSB switching time, the service is interrupted.
This topic provides the specifications of 1+1 HSB. Table 2-3 lists the specifications of 1+1 HSB. Table 2-3 Specifications of 1+1 HSB Item Radio type Specification SDH/PDH radio Integrated IP radio Number of protection groups Protection type 1 to 7 Revertive mode Non-revertive mode WTR time Reverse switching Restriction on the available slot of the IF board 5 to 12 minutes Supported The IF boards can be configured in any slots. It is recommended, however, that you configure the IF boards in paired slots, for example, slot 3 and slot 5, slot 7 and slot 9, slot 1 and slot 2, slot 8 and slot 10, slot 4 and slot 6, slot 11 and slot 13, slot 12 and slot 14.
2.1.4 Availability
The 1+1 HSB feature requires the support of the applicable boards.

Table 2-4 Hardware and version support Feature 1+1 HSB Applicable Board IF1 IFU2 IFX2 Applicable Hardware Version All the versions All the versions All the versions Applicable Product Version V100R003C00 and later V100R003C00 and later V100R003C00 and later
Issue 02 (2011-01-20)
2-10
Feature
Applicable Board ISU2 ISX2
Applicable Hardware Version All the versions All the versions
Applicable Product Version V100R003C00 and later V100R003C00 and later
The dependencies between the 1+1 HSB feature and other features are as follows: l l The configuration mode (HSB/FD/SD) of a 1+1 protection group in one direction can be different from that in another direction. The two IF boards in an XPIC working group cannot be configured into one 1+1 HSB protection group, but the two IF boards in different XPIC working groups can be configured into one 1+1 HSB protection group. 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. If the Integrated IP radio links are configured with the 1+1 HSB protection and if the AM function is enabled, the standby link works in original modulation mode of the main link after the HSB switching. When an Integrated IP radio radio 1+1 HSB protection group is created, the NE automatically creates a load non-sharing LAG. In the LAG, the master port is the Integrated IP radio port on the active IF board and the slave port is the Integrated IP radio port on the standby IF board. This LAG can neither be displayed on the NMS nor configured manually. The 1+1 HSB Integrated IP radio link can function as the ring link or ring protection link in the ERPS protection. 1+1 HSB can co-exist with MPLS APS. 1+1 HSB can co-exist with PW APS.
l l l
l l l
2.1.5 Principles
The switching principle of SDH/PDH radio 1+1 HSB is different from the switching principle of Integrated IP radio 1+1 HSB. 2.1.5.1 SDH/PDH Microwave The cross-connect unit realizes the HSB switching by dually transmitting and selectively receiving the TDM service. 2.1.5.2 Integrated IP radio The cross-connect unit realizes the HSB switching on the TDM plane by dually transmitting and selectively receiving the TDM service. The packet switching unit realizes the HSB switching on the packet plane through the LAG switching.
Issue 02 (2011-01-20)
2-11
2.1.5.1 SDH/PDH Microwave

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

Figure 2-3 1+1 HSB realization principle (before the switching, in the transmit direction)
Main ODU Main IF board Cross-connect Unit Service Interface Unit
Antenna
Hybrid coupler
E1/STM-1 Standby ODU Standby IF board
In the transmit direction: 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 2-4 1+1 HSB realization principle (before the switching, in the receive direction)
Main ODU Main IF board Cross-connect Unit Service Interface Unit
Antenna
Hybrid coupler
In the receive direction: 1. 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.
2-12
2. 3. 4. 5.
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 2-5 1+1 HSB realization principle (after the switching, in the receive direction)
Main ODU Antenna Hybrid coupler Main IF board Cross-connect Unit Service Interface Unit
Figure 2-6 1+1 HSB realization principle (after the switching, in the transmit direction)
Main ODU Antenna Hybrid coupler Main IF board Cross-connect Unit Service Interface Unit
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.
Issue 02 (2011-01-20)
2-13
2.1.5.2 Integrated IP radio

The cross-connect unit realizes the HSB switching on the TDM plane by dually transmitting and selectively receiving the TDM service. The packet switching unit realizes the HSB switching on the packet plane through the LAG switching.
NOTE
This section uses the Integrated IP radio simultaneously transmitting Native E1 services and Native Ethernet services as an example to describe the 1+1 HSB protection principle. When the Integrated IP radio transmits PWE3 services, the PWE3 service switching principle is the same as the Native Ethernet service switching principle.

Figure 2-7 1+1 HSB realization principle (before the switching, in the transmit direction)
Main ODU Main IF board Cross-connect Unit
Hybrid coupler Antenna
Service Interface Unit E1
Ethernet
Standby ODU
Standby IF board
Packet switching Unit
In the transmit direction: 1. 2. 3. 4. 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 service interface unit sends the Ethernet service signal to the packet switching unit. The packet switching unit configures the link aggregation function for the GE links that are connected to the main IF board and the standby IF board according to the configuration of the 1+1 microwave protection group. Then, the packet switching unit sends the GE data to the current main IF board. The MUX unit of the main IF board multiplexes the E1 service signal and Ethernet service signal into the Integrated IP radio frame. The Integrated IP radio 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 Integrated IP radio frame that is multiplexed by their corresponding IF board and modulate the Integrated IP radio 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.
5.
6.
2-14
7.
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 2-8 1+1 HSB realization principle (before the switching, in the receive direction)
Main ODU Hybrid coupler Antenna Main IF board Cross-connect Unit
Ethernet
Standby ODU
Standby IF board
In the receive direction: 1. 2. 3. 4. 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 Integrated IP radio frame from the IF signal. The MUX units of the main IF board and the standby IF board receive the Integrated IP radio frame that is demodulated by their corresponding IF board and then separate the Integrated IP radio 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 packet switching unit receives the Ethernet service signal that is separated by the main IF board. The Ethernet service signal that is separated by the standby IF board is not transmitted to the packet switching unit. The packet switching unit sends the Ethernet service signal to the service interface unit.
5. 6. 7.
8.
Issue 02 (2011-01-20)
2-15
After the Switching

Figure 2-9 1+1 HSB realization principle (after the switching, in the receive direction)
Main ODU Hybrid coupler Antenna Main IF board Cross-connect Unit
Service interface Unit E1
Ethernet
Standby ODU
Standby IF board
Figure 2-10 1+1 HSB realization principle (after the switching, in the transmit direction)
Main ODU Main IF board Cross-connect Unit
Hybrid coupler Antenna
Ethernet
Standby ODU
Standby IF board
After the 1+1 HSB switching: l In the receive direction: The MUX unit of the standby IF board separates the IF analog signal into the E1 service signal and Ethernet service signal. After the packet switching unit performs the LAG switching, the GE link corresponding to the main IF board is disconnected and the port status changes to LinkDown; the GE link corresponding to the standby IF board is connected and the port status changes to LinkUp. In this case, the crossconnect unit and the packet switching unit receive the service signal from the standby IF board. In the transmit direction: After the packet switching unit performs the LAG switching, the GE link corresponding to the main IF board is disconnected and the port status changes to LinkDown; the GE link corresponding to the standby IF board is connected and the port status changes to LinkUp. The IF processing units of the main IF board and the standby IF
2-16
board modulate the Integrated IP radio frame that is multiplexed by the MUX unit of their corresponding IF board into the IF analog signal. The main IF board and the standby IF board send the IF analog signal to the main ODU and the standby ODU respectively. 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 guidelines when you plan 1+1 HSB. Plan the parameters relevant to the protection configuration. l l l If the protection is in the revertive mode, set the WTR time to a value, which ranges from 5 minutes to 12 minutes. It is recommended that you set the default value to 10 minutes. It is recommended that you disable reverse switching. This avoids invalid RDI switching that is triggered at the transmit end due to signal fading. In the case of the OptiX RTN 980, it is recommended that a pair of main and standby IF boards be installed in slots 3 and 5 (the IF board in slot 3 is the main board), slots 7 and 9 (the IF board in slot 7 is the main board), slots 1 and 2 (the IF board in slot 1 is the main board), slots 8 and 10 (the IF board in slot 8 is the main board), slots 4 and 6 (the IF board in slot 4 is the main board), slots 11 and 13 (the IF board in slot 11 is the main board), or slots 12 and 14 (the IF board in slot 12 is the main board).

When configuring the 1+1 HSB radio link, configure the 1+1 IF protection group first, and then configure the IF/ODU information. Table 2-5 Procedure for configuring the 1+1 HSB protection mode Step 1 Operation A.2.1 Creating an IF 1+1 Protection Group A.2.4 Configuring the IF/ODU Information of a Radio Link Description The parameters need to be set according to the network planning.
In the case of radio links configured with 1+1 HSB, you need to configure the corresponding IF and ODU information for the main equipment. The parameters need to be set according to the network planning.
Issue 02 (2011-01-20)
2-17
Step 3
Operation A.5.8.3 Setting Advanced AM Attributes
Description Optional. l You can specify the maximum number of E1s that can be transmitted in intermediate modulation schemes, by setting the advanced attributes correspondingly. l Generally, it is recommended that you use the default values. l To ensure that a specific number of E1s can be transmitted in intermediate modulation schemes, adjust the E1 capacity in each modulation scheme according to the network planning information. When a new modulation scheme is adopted, the system transmits only the number of E1 services allowed by the modulation scheme and discards the excess E1 services.
NOTE In the case of the IF boards that are configured with 1+1 protection, only the AM advanced attributes of the main IF board need to be set.
A.5.8.2 Configuring the ATPC Attributes
Required when the ATPC function needs to be used. l If the ATPC function needs to be used, set ATPC Enable Status to Enabled. l During site commissioning, set ATPC Enable Status to Disabled. l It is recommended that you set ATPC Upper Threshold (dBm) to the central value plus 10 dB. l It is recommended that you set ATPC Lower Threshold (dBm) to the central value minus 10 dB. l It is recommended that you set ATPC Automatic Threshold Enable Status to Disabled.
NOTE In the case of the IF boards that are configured with 1+1 protection, configure only the ATPC attributes of the main IF board.
A.5.9.3 Setting the Power Attributes of the ODU
Optional. l To set the maximum transmit power that is supported by the ATPC adjustment function, you need to setMaximum Transmit Power(dBm) according to the actual requirements. 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. Therefore, determine whether to set these parameters according to the actual requirements.
NOTE For 1+1 HSB, only the power attributes of the main ODU need to be set.
2-18
Issue 02 (2011-01-20)
Step 6
Operation Testing IF 1 +1 Protection Switching
Description Perform this operation to test whether the service data is configured correctly.

This section uses an example to describe how to plan and configure the 1+1 HSB radio link according to the actual network conditions through a detailed example.
NOTE
This section considers the Integrated IP radio link created by using the ISU2 board as an example. In the case of the IF1, IFX2, IFU2, ISX2 board, the method of creating the IF 1+1 protection group is the same. The only difference lies in the IF parameter settings. See the corresponding parameter description.
2.1.8.1 Networking Diagram The topic describes the networking information of the NEs. 2.1.8.2 Service Planning The service planning information contains all the parameter information required for configuring the NE data. 2.1.8.3 Configuration Process This topic describes the procedure for the data configuration.

The topic describes the networking information of the NEs. Figure 2-11 shows a hop of important radio link. To ensure the reliable transmission of services, the radio link between NE1 and NE2 adopts the 1+1 HSB protection. Figure 2-11 Networking diagram of 1+1 HSB protection
101 14930M 14510M 28M 1+1 HSB Enabled Disabled H-polarzation
Tx high
Tx low
NE2
NE1
Link ID Tx high station Tx Freq. Tx low station Tx Freq. Chanel spacing RF configuarion
AM enabling
ATPC enabling Polarization
Issue 02 (2011-01-20)
2-19

The service planning information contains all the parameter information required for configuring the NE data. l Plan the slots of the working board and the protection board. According to the board configuration of the equipment, plan the slots of the working board and the protection board. The IF board in slot 3 functions as the working board and the IF board in slot 5 functions as the protection board. l Plan the protection group parameters. The 1+1 protection mode is HSB, providing the equipment protection function. Unless otherwise specified, all parameters except reverse switching parameters take default values. It is recommended that the reverse switching function is disabled to prevent incorrect switching. 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 2-6 IF planning information Parameter NE1 3-ISU2 Radio Link ID IF Channel Bandwidth IF Service Type AM Enable Status Modulation Mode of the Guarantee AM Capacity Modulation Mode of the Full AM Capacity Guaranteed E1 Capacity ATPC Enable Status Enable E1 Priority 101 28 Hybrid(Native E1 + Eth) Enabled QPSK 128QAM 16 Disabled Disabled NE2 3-ISU2 101 28 Hybrid(Native E1 + Eth) Enabled QPSK 128QAM 16 Disabled Disabled
2-20
Issue 02 (2011-01-20)
Table 2-7 RF planning information Parameter NE1 53-ODU Transmit frequency (MHz) T/R spacing (MHz) Transmit power (dBm) Power to be received(dBm) Transmission status 14930 420 10 -45 unmute NE2 53-ODU 14510 420 10 -45 unmute

Procedure
Step 1 See A.2.1 Creating an IF 1+1 Protection Group and create IF 1+1 protection. 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 (default value) 600 (default value) Disable 3-ISU2 5-ISU2 NE2 HSB Revertive (default value) 600 (default value) Disable 3-ISU2 5-ISU2
Step 2 See A.2.4 Configuring the IF/ODU Information of a Radio Link and configure the IF/ODU information of the radio link. The values of the IF board parameters are provided as follows. Parameter Value Range NE1 3-ISU2 IF Service Type AM Enable Status
Issue 02 (2011-01-20)
NE2 3-ISU2 Hybrid(Native E1+ETH) Enable

2-21
Hybrid(Native E1+ETH) Enable
Parameter
Value Range NE1 3-ISU2 NE2 3-ISU2 28 Mbit/s QPSK 128QAM 16 101 Disabled
IF Channel Bandwidth Modulation Mode of the Guarantee AM Capacity Modulation Mode of the Full AM Capacity Guarantee E1 Capacity Link ID Enable E1 Priority
28 Mbit/s QPSK 128QAM 16 101 Disabled
The values of the ODU parameters are provided as follows. Parameter Value Range NE1 53-ODU TX Frequency(MHz) T/R Spacing(MHz) TX Power(dBm) TX Status Power to Be Received (dBm) 14930 420 10 unmute -45 NE2 53-ODU 14510 420 10 unmute -45
Step 3 Test IF 1+1 protection switching. The test results meet the service requirements. ----End

This topic provides the hyperlinks of the operation tasks regarding the 1+1 HSB feature.
Related Tasks
A.2.1 Creating an IF 1+1 Protection Group A.2.6 Querying the IF 1+1 Protection Status A.2.8 IF 1+1 Protection Switching
A.11.6.1 Testing the IF 1+1 Switching

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

IF 1+1 protection switching: This abnormal event indicates that the IF 1+1 protection switching occurs.
2.1.11 FAQs
This topic provides the answers to the questions that are frequently raised when the 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 l l The IF board or 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. The service modes of two ISU2 or ISX2 boards in a 1+1 protection group are inconsistent. The standby IF board has a lower licensed capacity than the main IF board.
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.
Issue 02 (2011-01-20)
2-23
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 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.
2.2 1+1 FD
The 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 signal. The opposite end selects the signal from the two received signals. With the 1+1 FD protection, the impact of the fading on signal transmission is reduced. 2.2.1 Introduction This section provides the definition of 1+1 FD and describes its purpose. 2.2.2 Basic Concepts This topic describes the basic concepts that you need to be familiar with before you use the 1+1 FD feature. 2.2.3 Specifications This topic provides the specifications of 1+1 FD. 2.2.4 Availability The 1+1 FD feature requires the support of the applicable boards. 2.2.5 Principles The switching principle of SDH/PDH radio 1+1 FD is different from the switching principle of Integrated IP radio 1+1 FD. 2.2.6 Planning Guidelines Follow certain guidelines when you plan 1+1 FD. 2.2.7 Configuration Procedure When configuring the 1+1 FD link, configure the 1+1 IF protection group first, and then configure the IF/ODU information. 2.2.8 Configuration Example This topic uses an example to describe how to plan and configure the 1+1 FD radio link according to the actual network conditions through a detailed example. 2.2.9 Task Collection This topic provides the hyperlinks of the operation tasks regarding the 1+1 FD feature. 2.2.10 Relevant Alarms and Events
When a 1+1 FD switching occurs on IF boards, the system reports corresponding alarms and abnormal events. 2.2.11 FAQs This topic provides the answers to the questions that are frequently raised when the 1+1 FD is used.
2.2.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 2-12 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 2-12 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.
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.

This topic describes the basic concepts that you need to be familiar with before you use the 1+1 FD feature. 2.2.2.1 System Configuration The OptiX RTN 980 supports one to seven 1+1 FD protection groups. 2.2.2.2 Protection Type The 1+1 FD protection is classified into the revertive mode and the non-revertive mode. 2.2.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. 2.2.2.4 Switching Impact In the case of the HSB switching, the services are interrupted within the HSB switching time. 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, in a 1+1 protection group consisting of IFU2/IFX2 boards, works in the modulation mode for ensuring capacity after the HSM switching occurs. Therefore, services with a lower priority are damaged. However, in a 1 +1 protection group consisting of ISU2/ISX2 boards, the modulation mode is not changed after the HSM switching occurs.

The OptiX RTN 980 supports one to seven 1+1 FD protection groups. 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
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 2-13 and Figure 2-14 show two typical configurations of one 1+1 FD protection group on the OptiX RTN 980.
2-26
Issue 02 (2011-01-20)
Figure 2-13 Typical configuration 1 of one 1+1 FD protection group
ODU
Hybrid coupler
Antenna
ODU
PIU
PIU
FAN
IF board IF board
IDU
Issue 02 (2011-01-20)
2-27
Figure 2-14 Typical configuration 2 of one 1+1 FD protection group
ODU
Antenna
ODU
Antenna
PIU
PIU
FAN
IF board IF board
IDU

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 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 related only to the HSB switching (switching on the equipment side). In the case of the HSM switching (switching on the channel side), regardless of the revertive mode, the IF board attempts to perform a revertive switching action periodically after the HSM switching occurs.

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 2-8 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.
Forced switching (external switching)
Issue 02 (2011-01-20)
2-29
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 2-9. 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 2-9 Trigger conditions of the automatic HSB switching Switching Condition Hardware fault on the IF board Hardware fault on the ODU
2-30
Description At the same priority
Issue 02 (2011-01-20)
Switching Condition POWER_ALM VOLT_LOS (IF board) RADIO_TSL_HIGH RADIO_TSL_LOW RADIO_RSL_HIGH IF_INPWR_ABN CONFIG_NOSUPPORT Fault on the IF connection cable XPIC_LOS (IFX2, ISX2)
Description
Trigger Conditions of the HSM Switching

The HSM switching occurs on the channel side. The channel-side switching can be classified into 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 the automatic switching, the IF board receives the baseband signal sent from its paired IF board. 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 2-10. Table 2-10 Trigger conditions of the automatic HSM switching Switching Condition R_LOC MW_LOF R_LOS R_LOF MW_FEC_UNCOR MW_BER_SD
Issue 02 (2011-01-20)
Priority High
Medium Low
2-31
Switching Condition B1_SD (IF1)
Priority
NOTE
The trigger conditions of the automatic HSM switching are available at three levels, namely, high, medium, and low. If service alarms are reported on both the main IF board and the standby IF boards, the switching occurs only when the alarm reported on the main IF board has a higher priority than the alarm reported on the standby IF board. For example, if the MW_FEC_UNCOR alarm is reported on the main IF board and the MW_BER_SD alarm is reported on the standby IF board, the switching occurs; if the MW_FEC_UNCOR alarm is reported on both the main IF board and the 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, in a 1+1 protection group consisting of IFU2/IFX2 boards, works in the modulation mode for ensuring capacity after the HSM switching occurs. Therefore, services with a lower priority are damaged. However, in a 1+1 protection group consisting of ISU2/ISX2 boards, the modulation mode is not changed after the HSM switching occurs.

In the case of the HSB switching, the services are interrupted within the HSB switching time. 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, in a 1+1 protection group consisting of IFU2/IFX2 boards, works in the modulation mode for ensuring capacity after the HSM switching occurs. Therefore, services with a lower priority are damaged. However, in a 1 +1 protection group consisting of ISU2/ISX2 boards, the modulation mode is not changed after the HSM switching occurs.
This topic provides the specifications of 1+1 FD. Table 2-11 lists the specifications of 1+1 FD. Table 2-11 Specifications of 1+1 FD Item Radio type Specification SDH/PDH radio Integrated IP radio Number of protection groups Switching mode 1 to 7 HSB HSM
Item Protection type
Specification Revertive mode Non-revertive mode
WTR time Reverse switching Restriction on the available slot of the IF board
5 to 12 minutes Not supported Pairs of IF boards must be configured in paired slots, for example, slot 3 and slot 5, slot 7 and slot 9, slot 1 and slot 2, slot 8 and slot 10, slot 4 and slot 6, slot 11 and slot 13, slot 12 and slot 14.
2.2.4 Availability
The 1+1 FD feature requires the support of the applicable boards.

Table 2-12 Hardware and version support Feature 1+1 FD Applicable Board IF1 IFU2 IFX2 ISU2 ISX2 Applicable Hardware Version All the versions All the versions All the versions All the versions All the versions Applicable Product Version V100R003C00 and later V100R003C00 and later V100R003C00 and later V100R003C00 and later V100R003C00 and later
The dependencies between the 1+1 FD feature and other features are as follows: l l The configuration mode (HSB/FD/SD) of a 1+1 protection group in one direction can be different from that in another direction. The two IF boards in an XPIC workgroup cannot be configured into one 1+1 FD protection group, but the two IF boards in different XPIC workgroups can be configured into one 1 +1 FD protection group.
Issue 02 (2011-01-20)
l l l
l l l
The members of the 1+1 FD protection group cannot participate in the N+1 protection. The Integrated IP radio link with 1+1 FD configuration can function as the working source, protection source, or service sink of SNCP. On the AM-enabled 1+1 FD Integrated IP radio link, after an HSB switching, the standby link works in the modulation mode of the original active link; the standby channel, in a 1 +1 protection group consisting of IFU2/IFX2 boards, works in the modulation mode for ensuring capacity after the HSM switching occurs. Therefore, services with a lower priority are damaged. However, in a 1+1 protection group consisting of ISU2/ISX2 boards, the modulation mode is not changed after the HSM switching occurs. When a Integrated IP radio 1+1 FD protection group is created, the NE automatically creates a load non-sharing LAG. In the LAG, the master port is the Integrated IP radio port on the active IF board and the slave port is the Integrated IP radio port on the standby IF board. This LAG can neither be displayed on the NMS nor configured manually. The 1+1 FD Integrated IP radio link can function as the ring link or ring protection link in the ERPS protection. 1+1 FD can co-exist with PW APS. 1+1 FD can co-exist with MPLS APS.
2.2.5 Principles
The switching principle of SDH/PDH radio 1+1 FD is different from the switching principle of Integrated IP radio 1+1 FD. 2.2.5.1 SDH/PDH Microwave The cross-connect unit realizes the HSB switching by selecting the TDM service from the standby IF board. The IF board realizes the HSM switching by selecting the baseband signal from the standby receive channel. 2.2.5.2 Integrated IP radio The cross-connect unit realizes the HSB switching on the TDM plane by selecting the TDM service from the standby IF board. The packet switching unit realizes the HSB switching on the packet plane through the LAG switching. The IF board realizes the HSM switching by selecting the baseband signal from the standby receive channel.

The cross-connect unit realizes the HSB switching by selecting the TDM service from the standby IF board. The IF board realizes the HSM switching by selecting the baseband signal from the standby receive channel.

Figure 2-15 1+1 FD realization principle (before the switching, in the transmit direction)
Antenna f1 Main ODU Main IF board Cross-connect Unit Service Interface Unit
f2
Antenna
Standby ODU
Standby IF board
2-34
Issue 02 (2011-01-20)
In the transmit direction: 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 and the standby ODU output RF signals at different frequencies and send the signals to their corresponding antennas.
Figure 2-16 1+1 FD realization principle (before the switching, in the receive direction)
Antenna Main ODU Main IF board Cross-connect Unit Service Interface Unit
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.
Issue 02 (2011-01-20)
2-35
After the Switching

Figure 2-17 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: 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 2-18 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.

The cross-connect unit realizes the HSB switching on the TDM plane by selecting the TDM service from the standby IF board. The packet switching unit realizes the HSB switching on the packet plane through the LAG switching. The IF board realizes the HSM switching by selecting the baseband signal from the standby receive channel.

NOTE
This section uses the Integrated IP radio simultaneously transmitting Native E1 services and Native Ethernet services as an example to describe the 1+1 FD protection principle. When the Integrated IP radio transmits PWE3 services, the PWE3 service switching principle is the same as the Native E1 service switching principle.

Figure 2-19 1+1 FD realization principle (before the switching, in the transmit direction)
Antenna f1 Service Interface Unit E1 Main ODU Main IF board Cross-connect Unit
Ethernet
f2 Antenna Standby ODU Standby IF board Packet switching Unit
In the transmit direction: 1. 2. 3. 4. 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 service interface unit sends the Ethernet service signal to the packet switching unit. The packet switching unit configures the link aggregation function for the GE links that are connected to the main IF board and the standby IF board according to the configuration of the 1+1 microwave protection group. Then, the packet switching unit sends the GE data to the current main IF board. The MUX unit of the main IF board multiplexes the E1 service signal and Ethernet service signal into the Integrated IP radio frame. The Integrated IP radio 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 Integrated IP radio frame that is multiplexed by the main IF board and modulate the Integrated IP radio 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 at frequency f1 to the main antenna. The standby ODU transmits the RF signal at frequency f2 to the standby antenna.
5.
6.
7.
Issue 02 (2011-01-20)
2-37
Figure 2-20 1+1 FD realization principle (before the switching, in the receive direction)
Antenna f1 Main ODU Main IF board Cross-connect Unit
Ethernet
Antenna
f2
Standby ODU
Standby IF board
In the receive direction: 1. 2. 3. The antennas receive RF signals at different frequencies 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 and the standby IF board demodulate the Integrated IP radio frame from the IF analog signal. The Integrated IP radio 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 Integrated IP radio frame that is demultiplexed by their corresponding IF board and then separate the Integrated IP radio 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 packet switching unit receives the Ethernet service signal that is separated by the main IF board. The Ethernet service signal that is separated by the standby IF board is not transmitted to the packet switching unit. The packet switching unit sends the processed Ethernet service signal to the service interface unit.
4.
5. 6. 7.
8.
2-38
Issue 02 (2011-01-20)
After the Switching

Figure 2-21 1+1 FD HSB realization principle (after the switching, in the transmit direction)
Antenna f1 Service Interface Unit E1 Main ODU Main IF board Cross-connect Unit
Ethernet
f2 Antenna Standby ODU Standby IF board Packet switching Unit
Figure 2-22 1+1 FD HSB realization principle (after the switching, in the receive direction)
Ethernet
Antenna
f2
Standby ODU
Standby IF board
After the 1+1 FD HSB switching: l In the transmit direction: After the packet switching unit performs the LAG switching, the GE link corresponding to the main IF board is disconnected and the port status changes to LinkDown; the GE link corresponding to the standby IF board is connected and the port status changes to LinkUp. The IF processing units of the main IF board and the standby IF board modulate the Integrated IP radio frame that is multiplexed by the MUX unit of the standby IF board into the IF analog signal. Then, 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 at frequency f1 to the main antenna and the standby ODU transmits the RF signal at frequency f2 to the standby antenna. In the receive direction: The Integrated IP radio frame that is demodulated by the main IF board is transmitted to the standby IF board through the protection bus. The MUX units of
Issue 02 (2011-01-20)
the main IF board and the standby IF board receive the Integrated IP radio frames from their corresponding IF board. Then, these Integrated IP radio frames are separated into the E1 service signal and Ethernet service signal. After the packet switching unit performs the LAG switching, the GE link corresponding to the main IF board is disconnected and the port status changes to LinkDown; the GE link corresponding to the standby IF board is connected and the port status changes to LinkUp. In this case, the cross-connect unit and the packet switching unit receive the service signal from the standby IF board. Figure 2-23 1+1 FD HSM realization principle (after the switching, in the receive direction)
Ethernet
Antenna
f2
Standby ODU
Standby IF board
After the 1+1 FD HSM switching: l l In the transmit direction, signals need not be processed. In the receive direction: The main IF board receives the Integrated IP radio frame modulated by the standby IF board through the protection bus. The MUX unit of the main IF board separates the Integrated IP radio frame into the E1 service signal and Ethernet service signal. The statuses of the GE links corresponding to the main IF board and the standby IF board do not change. The cross-connect unit and the packet switching unit 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 guidelines when you plan 1+1 FD. Plan the parameters relevant to the protection configuration. l l l If the protection is in the revertive mode, set the WTR time to a value, which ranges from 5 minutes to 12 minutes. It is recommended that you set the default value to 10 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 980, a pair of main and standby IF boards must be installed in slots 3 and 5 (the IF board in slot 3 is the main board), slots 7 and 9 (the IF board in slot 7 is the main board), slots 1 and 2 (the IF board in slot 1 is the main board), slots 8 and 10 (the IF board in slot 8 is the main board), slots 4 and 6 (the IF board in slot 4 is the main
2-40
board), slots 11 and 13 (the IF board in slot 11 is the main board), or slots 12 and 14 (the IF board in slot 12 is the main board).

When configuring the 1+1 FD link, configure the 1+1 IF protection group first, and then configure the IF/ODU information. Table 2-13 Procedure for configuring the 1+1 FD protection mode Step 1 Operation A.2.1 Creating an IF 1+1 Protection Group A.2.4 Configuring the IF/ODU Information of a Radio Link A.5.8.3 Setting Advanced AM Attributes Description The parameters need to be set according to the network planning.
In the case of radio links configured with FD, you need to configure the IF/ODU information on the active equipment and the ODU information on the standby equipment. The parameters need to be set according to the network planning. Required. l You can specify the maximum number of E1s that can be transmitted in intermediate modulation schemes, by setting the advanced attributes correspondingly. l Generally, it is recommended that you use the default values. l To ensure that a specific number of E1s can be transmitted in intermediate modulation schemes, adjust the E1 capacity in each modulation scheme according to the network planning information. When a new modulation scheme is adopted, the system transmits only the number of E1 services allowed by the modulation scheme and discards the excess E1 services.
Issue 02 (2011-01-20)
2-41
Step 4
Operation A.5.8.2 Configuring the ATPC Attributes
Description Required when the ATPC function needs to be used. l If the ATPC function needs to be used, set ATPC Enable Status to Enabled. l During site commissioning, set ATPC Enable Status to Disabled. l It is recommended that you set ATPC Upper Threshold (dBm) to the central value plus 10 dB. l It is recommended that you set ATPC Lower Threshold (dBm) to the central value minus 10 dB. l It is recommended that you set ATPC Automatic Threshold Enable Status to Disabled.
Testing IF 1 +1 Protection Switching
Perform this operation to test whether the service data is configured correctly.

This topic uses an example to describe how to plan and configure the 1+1 FD radio link according to the actual network conditions through a detailed example.
NOTE
2.2.8.1 Networking Diagram The topic describes the networking information of the NEs. 2.2.8.2 Service Planning The service planning information contains all the parameter information required for configuring the NE data.
2.2.8.3 Configuration Process This topic describes the procedure for the data configuration.

The topic describes the networking information of the NEs. Figure 2-24 shows a hop of important radio link. To ensure the reliable transmission of services, the radio link between NE1 and NE2 adopts the 1+1 FD protection. Figure 2-24 Networking diagram of 1+1 FD protection
101 14930M 14510M 28M
1+1 FD
Enabled Disabled H-polarzation
Tx high
Tx low
NE2
NE1
AM enabling

The service planning information contains all the parameter information required for configuring the NE data. l Plan the slots of the working board and the protection board. According to the board configuration of the equipment, plan the slots of the working board and the protection board. The IF board in slot 3 functions as the working board and the IF board in slot 5 functions as the protection board. l Plan the protection group parameters. The 1+1 protection mode is FD, providing the channel protection and equipment protection functions. Unless otherwise specified, all the parameters adopt the default values. 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 FD, one protection group maps one link. You need to configure the IF/ODU information on the active equipment and the ODU information on the standby equipment.
Table 2-14 IF planning information Parameter NE1 3-ISU2 Radio Link ID IF Channel Bandwidth (MHz) IF Service Type AM Enable Status Modulation Mode of the Guarantee AM Capacity Modulation Mode of the Full AM Capacity Guaranteed E1 Capacity ATPC Enable Status Enable E1 Priority 101 28 Hybrid(Native E1 + Eth) Enabled QPSK 128QAM 16 Disabled Disabled NE2 3-ISU2 101 28 Hybrid(Native E1 + Eth) Enabled QPSK 128QAM 16 Disabled Disabled
Table 2-15 RF planning information Parameter NE1 53-ODU Transmit frequency (MHz) T/R spacing (MHz) Transmit power (dBm) Power to be received(dBm) Transmission status 14930 55-ODU 15000 NE2 53-ODU 14510 55-ODU 14580
420 10 -45 unmute
420 10 -45 unmute
420 10 -45 unmute
420 10 -45 unmute
2-44
Issue 02 (2011-01-20)

Procedure
Step 1 See A.2.1 Creating an IF 1+1 Protection Group and create IF 1+1 protection. The values for the related parameters are provided as follows. Parameter Value Range NE1 Working Mode Revertive Mode WTR Time(s) Working Board Protection Board FD Revertive (default value) 600 (default value) 3-ISU2 5-ISU2 NE2 FD Revertive (default value) 600 (default value) 3-ISU2 5-ISU2
Step 2 See A.2.4 Configuring the IF/ODU Information of a Radio Link and configure the IF/ODU information of the radio link. The values of the IF board parameters are provided as follows. Parameter Value Range NE1 3-ISU2 IF Service Type AM Enable Status IF Channel Bandwidth Modulation Mode of the Guarantee AM Capacity Modulation Mode of the Full AM Capacity Guarantee E1 Capacity Link ID Hybrid(Native E1+ETH) Enable 28 Mbit/s QPSK 128QAM 16 101 NE2 3-ISU2 Hybrid(Native E1+ETH) Enable 28 Mbit/s QPSK 128QAM 16 101
The values of the ODU parameters are provided as follows.
Issue 02 (2011-01-20)
2-45
Parameter
Value Range NE1 53-ODU 55-ODU 15000 420 10 unmute -45 NE2 53-ODU 14510 420 10 unmute -45 55-ODU 14580 420 10 unmute -45
TX Frequency (MHz) T/R Spacing (MHz) TX Power (dBm) TX Status Power to Be Received (dBm)
14930 420 10 unmute -45
Step 3 A.5.8.2 Configuring the ATPC Attributes. The parameters for configuring the ATPC for the links of NE1 and NE2 need to be set to the same values, as provided in the following table. Parameter Value Range NE1 3-ISU2 ATPC Enable Status Disabled NE2 3-ISU2 Disabled
Step 4 Test IF 1+1 protection switching. The test results meet the service requirements. ----End

This topic provides the hyperlinks of the operation tasks regarding the 1+1 FD feature.
Related Tasks
A.2.1 Creating an IF 1+1 Protection Group A.2.6 Querying the IF 1+1 Protection Status A.2.8 IF 1+1 Protection Switching A.11.6.1 Testing the IF 1+1 Switching
2-46
Issue 02 (2011-01-20)

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

IF 1+1 protection switching: This abnormal event indicates that the IF 1+1 protection switching occurs.
2.2.11 FAQs
This topic provides the answers to the questions that are frequently raised when the 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 or 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. 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 standby IF board has abnormal alarms. If the standby IF board has abnormal alarms, handle the alarms immediately, and then perform a manual switching to verify the 1+1 FD switching function.
2.3 1+1 SD
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 the 1+1 SD protection, the impact of the fading on signal transmission is reduced. 2.3.1 Introduction This section provides the definition of 1+1 SD and describes its purpose. 2.3.2 Basic Concepts This topic describes the basic concepts that you need to be familiar with before you use the 1+1 SD feature. 2.3.3 Specifications This topic provides the specifications of 1+1 SD. 2.3.4 Availability The 1+1 SD feature requires the support of the applicable boards. 2.3.5 Principles The switching principle of SDH/PDH radio 1+1 FD is different from the switching principle of Integrated IP radio radio 1+1 FD. 2.3.6 Planning Guidelines Follow certain guidelines when you plan 1+1 SD. 2.3.7 Configuration Procedure When configuring the radio links in 1+1 SD protection, you need to configure the 1+1 IF protection group followed by the IF/ODU information. 2.3.8 Configuration Example This topic describes how to plan and configure the 1+1 SD radio links by using an example. 2.3.9 Task Collection This topic provides the hyperlinks of the operation tasks regarding the relevant feature. 2.3.10 Relevant Alarms and Events When a 1+1 SD switching occurs on IF boards, the system reports the corresponding alarm and abnormal event. 2.3.11 FAQs This topic provides the answers to the questions that are frequently raised when the 1+1 SD protection is adopted.
2.3.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 2-25 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 2-25 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.
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.

This topic describes the basic concepts that you need to be familiar with before you use the 1+1 SD feature. 2.3.2.1 System Configuration The OptiX RTN 980 supports one to seven 1+1 FD protection groups.
2.3.2.2 Protection Type The 1+1 SD protection is classified into the revertive mode and the non-revertive mode. 2.3.2.3 Switching Conditions 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. 2.3.2.4 Switching Impact In the case of the HSB switching, the services are interrupted within the HSB switching time. 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, in a 1+1 protection group consisting of IFU2/IFX2 boards, works in the modulation mode for ensuring capacity after the HSM switching occurs. Therefore, services with a lower priority are damaged. However, in a 1+1 protection group consisting of ISU2/ISX2 boards, the modulation mode is not changed after the HSM switching occurs.

The OptiX RTN 980 supports one to seven 1+1 FD protection groups. 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
Figure 2-26 shows a typical configuration of one 1+1 SD protection group on the OptiX RTN 980.
2-50
Issue 02 (2011-01-20)
Figure 2-26 Typical configuration of one 1+1 SD protection group
ODU
Antenna
ODU
Antenna
PIU
PIU
FAN
IF board IF board
IDU

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 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
l Both the revertive mode and non-revertive mode are related only to the HSB switching (switching on the equipment side). In the case of the HSM switching (switching on the channel side), regardless of whether the revertive mode, the IF board attempts to perform a revertive switching action periodically after the HSM switching occurs. l 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.

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 2-16 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.
2-52
Issue 02 (2011-01-20)
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 2-17. 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)
Issue 02 (2011-01-20)
2-53
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 2-17 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 MW_RDI Priority At the same priority
2-54
Issue 02 (2011-01-20)
Switching Condition Fault on the IF connection cable R_LOC (IFU2, ISU2, ISX2, and IFX2) R_LOF (IFU2, ISU2, ISX2, and IFX2) XPIC_LOS (IFX2 and ISX2)
Priority
Trigger Conditions of the HSM Switching

The HSM switching occurs on the channel side. The channel-side switching can be classified into the following types: l Forced switching The forced switching refers to the HSM switching that occurs at the same time when 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 by quality degradation of the signal on the main channel. After the automatic switching, the IF board receives the baseband signal sent from its paired IF board. In the case of the Integrated IP radio 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 2-18. Table 2-18 Trigger conditions of the automatic HSM switching Switching Condition R_LOC R_LOF R_LOS MW_LOF MW_FEC_UNCOR MW_BER_SD B1_SD(IF1) Medium Low Priority High
Issue 02 (2011-01-20)
2-55
NOTE
The trigger conditions of the automatic HSM switching are available at three levels, namely, high, medium, and low. If service alarms are reported on both the main IF board and the standby IF boards, the switching occurs only when the alarm reported on the main IF board has a higher priority than the alarm reported on the standby IF board. For example, if the MW_FEC_UNCOR alarm is reported on the main IF board and the MW_BER_SD alarm is reported on the standby IF board, the switching occurs; if the MW_FEC_UNCOR alarm is reported on both the main IF board and the 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, in a 1+1 protection group consisting of IFU2/IFX2 boards, works in the modulation mode for ensuring capacity after the HSM switching occurs. Therefore, services with a lower priority are damaged. However, in a 1+1 protection group consisting of ISU2/ISX2 boards, the modulation mode is not changed after the HSM switching occurs.

In the case of the HSB switching, the services are interrupted within the HSB switching time. 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, in a 1+1 protection group consisting of IFU2/IFX2 boards, works in the modulation mode for ensuring capacity after the HSM switching occurs. Therefore, services with a lower priority are damaged. However, in a 1+1 protection group consisting of ISU2/ISX2 boards, the modulation mode is not changed after the HSM switching occurs.
This topic provides the specifications of 1+1 SD. Table 2-19 lists the specifications of 1+1 SD. Table 2-19 Specifications of 1+1 SD Item Radio type Specification SDH/PDH radio Integrated IP radio Number of protection groups Switching mode 1 to 7 HSB HSM Protection type Revertive mode Non-revertive mode WTR time Reverse switching
2-56
5 to 12 minutes Supported
Issue 02 (2011-01-20)
Item Restriction on the available slot of the IF board
Specification Pairs of IF boards must be configured in paired slots, for example, slot 3 and slot 5, slot 7 and slot 9, slot 1 and slot 2, slot 8 and slot 10, slot 4 and slot 6, slot 11 and slot 13, slot 12 and slot 14.
2.3.4 Availability
The 1+1 SD feature requires the support of the applicable boards.

Table 2-20 Hardware and version support Feature 1+1 SD Applicable Board IF1 IFU2 IFX2 ISU2 ISX2 Applicable Hardware Version All the versions All the versions All the versions All the versions All the versions Applicable Product Version V100R003C00 and later V100R003C00 and later V100R003C00 and later V100R003C00 and later V100R003C00 and later
The dependencies between the 1+1 SD feature and other features are as follows: l l The configuration mode (HSB/FD/SD) of a 1+1 protection group in one direction can be different from that in the other direction. The two IF boards in an XPIC working group cannot form one 1+1 SD protection group, but can work with the IF boards in another XPIC working group to form two 1+1 SD protection groups. The IF boards in a 1+1 SD protection group cannot be configured to provide 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. On the AM-enabled 1+1 SD Integrated IP radio link, after an HSB switching, the standby link works in the modulation mode of the original active link; the standby channel, in a 1
l l l
Issue 02 (2011-01-20)
+1 protection group consisting of IFU2/IFX2 boards, works in the modulation mode for ensuring capacity after the HSM switching occurs. Therefore, services with a lower priority are damaged. However, in a 1+1 protection group consisting of ISU2/ISX2 boards, the modulation mode is not changed after the HSM switching occurs. l When creating a 1+1 SD protection group of the Integrated IP radio, the NE automatically creates a load non-sharing LAG whose main port is the Integrated IP radio port on the main IF board and whose slave port is the Integrated IP radio port on the standby IF board. The LAG is not displayed on the NMS and cannot be configured manually. The Integrated IP radio link that is configured with the 1+1 SD protection can work as the ring link or ring protection link (RPL) in the ERPS protection. 1+1 SD can co-exist with PW APS. 1+1 SD can co-exist with MPLS APS.
l l l
2.3.5 Principles
The switching principle of SDH/PDH radio 1+1 FD is different from the switching principle of Integrated IP radio radio 1+1 FD. 2.3.5.1 SDH/PDH Microwave The cross-connect unit realizes the HSB switching by selecting the TDM service from the standby IF board. The IF board realizes the HSM switching by selecting the baseband signal from the standby receive channel. 2.3.5.2 Integrated IP radio The cross-connect unit realizes the HSB switching on the TDM plane by selecting the TDM service from the standby IF board. The packet switching unit realizes the HSB switching on the packet plane through the LAG switching. The IF board realizes the HSM switching by selecting the baseband signal from the standby receive channel.

The cross-connect unit realizes the HSB switching by selecting the TDM service from the standby IF board. The IF board realizes the HSM switching by selecting the baseband signal from the standby receive channel.

Figure 2-27 1+1 SD realization principle (before the switching, in the transmit direction)
Antenna Main ODU Main IF board Cross-connect Unit Service InterfaceUnit
Antenna
Standby ODU
Standby IF board
2-58
Issue 02 (2011-01-20)
In the transmit direction: 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 sends the RF signal to the antenna. The standby ODU is muted (that is, the standby ODU does not transmit the RF signal).
Figure 2-28 1+1 SD realization principle (before the switching, in the receive direction)
Antenna
Standby ODU
Standby IF board
In the receive direction: 1. 2. 3. 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 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 its own MUX unit and the MUX unit of 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.
4. 5. 6.
Issue 02 (2011-01-20)
2-59
After the Switching

Figure 2-29 1+1 SD HSB realization principle (after the switching, in the receive direction)
Antenna
Standby ODU
Standby IF board
Figure 2-30 1+1 SD HSB realization principle (after the switching, in the transmit direction)
Antenna
Standby ODU
Standby IF board
After the 1+1 SD HSB switching: l l In the receive direction, the IF boards select their own service signals and the cross-connect unit selects the signal from the standby IF board. In the transmit direction, the standby ODU sends the RF signal to the antenna; the main ODU is muted (that is, the main ODU does not send the RF signal).
Figure 2-31 1+1 SD HSM realization principle (after the switching, in the receive direction)
Antenna
Standby ODU
Standby IF board
2-60
Issue 02 (2011-01-20)
After the 1+1 SD HSM switching: l l In the receive direction, the IF boards select the baseband signal from their corresponding paired IF boards. In the transmit direction, signals need not be processed.
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.

The cross-connect unit realizes the HSB switching on the TDM plane by selecting the TDM service from the standby IF board. The packet switching unit realizes the HSB switching on the packet plane through the LAG switching. The IF board realizes the HSM switching by selecting the baseband signal from the standby receive channel.
NOTE
The section uses the Integrated IP radio simultaneously transmitting Native E1 services and Native Ethernet services as an example to describe the 1+1 SD protection principle. When the Integrated IP radio transmits PWE3 services, the PWE3 service switching principle is the same as the Native Ethernet service switching principle.

Figure 2-32 1+1 SD realization principle (before the switching, in the transmit direction)
Antenna Main ODU Main IF board Cross-connect Unit
Ethernet
Antenna
Standby ODU
Standby IF board
In the transmit direction: 1. 2. 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.
Issue 02 (2011-01-20)
3. 4.
The service interface unit sends the Ethernet service signal to the packet switching unit. The packet switching unit configures the link aggregation function for the GE links that are connected to the main IF board and the standby IF board according to the configuration of the 1+1 microwave protection group. Then, the packet switching unit sends the GE data to the current main IF board. The MUX unit of the main IF board multiplexes the E1 service signal and Ethernet service signal into the Integrated IP radio frame. The Integrated IP radio 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 Integrated IP radio frame that is multiplexed by the main IF board and modulate the Integrated IP radio 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 antenna. The standby ODU is muted (that is, the standby ODU does not transmit the RF signal).
5.
6.
7.
Figure 2-33 1+1 SD realization principle (before the switching, in the receive direction)
Ethernet
Antenna
Standby ODU
Standby IF board
In the receive direction: 1. 2. 3. The antennas receive RF signals and transmit 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 and the standby IF board demodulate the IF signal into the Integrated IP radio frame. The Integrated IP radio 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 Integrated IP radio frame that is demultiplexed by their corresponding IF board and then separate the Integrated IP radio frame into the E1 service signal and Ethernet service signal. 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.
4.
5.
2-62
Issue 02 (2011-01-20)
6.
The packet switching unit receives the Ethernet service signal that is separated by the main IF board. The Ethernet service signal that is separated by the standby IF board is not transmitted to the packet switching unit. The packet switching unit sends the processed Ethernet service signal to the service interface unit.
7.
After the Switching

Figure 2-34 1+1 SD HSB realization principle (after the switching, in the receive direction)
Ethernet
Antenna
Standby ODU
Standby IF board
Figure 2-35 1+1 SD HSB realization principle (after the switching, in the transmit direction)
Ethernet
Antenna
Standby ODU
Standby IF board
After the 1+1 SD HSB switching: l In the receive direction: The Integrated IP radio frame that is demodulated by the main IF board is transmitted to the standby IF board through the protection bus. The MUX units of the main IF board and the standby IF board receive the Integrated IP radio frames from
Issue 02 (2011-01-20)
their corresponding IF board. Then, these Integrated IP radio frames are separated into the E1 service signal and Ethernet service signal. After the packet switching unit performs the LAG switching, the GE link corresponding to the main IF board is disconnected and the port status changes to LinkDown; the GE link corresponding to the standby IF board is connected and the port status changes to LinkUp. In this case, the cross-connect unit and the packet switching unit receive the service signal from the standby IF board. l In the transmit direction: After the packet switching unit performs the LAG switching, the GE link corresponding to the main IF board is disconnected and the port status changes to LinkDown; the GE link corresponding to the standby IF board is connected and the port status changes to LinkUp. The main IF board and the standby IF board modulate the Integrated IP radio frame that is multiplexed by the standby IF board and then transmit the modulated service signal to the main ODU and 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.)
Figure 2-36 1+1 SD HSM realization principle (after the switching, in the receive direction)
Ethernet
Antenna
Standby ODU
Standby IF board
After the 1+1 SD HSM switching: l l In the transmit direction, signals need not be processed. In the receive direction, the main IF board receives the Integrated IP radio frame modulated by the standby IF board through the protection bus. The MUX unit of the main IF board separates the Integrated IP radio frame into the E1 service signal and Ethernet service signal. The statuses of the GE links corresponding to the main IF board and the standby IF board do not change. The cross-connect unit and the packet switching unit 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 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 5 minutes to 12 minutes. It is recommended that you set the default value to 10 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 980, a pair of main and standby IF boards must be installed in slots 3 and 5 (the IF board in slot 3 is the main board), slots 7 and 9 (the IF board in slot 7 is the main board), slots 1 and 2 (the IF board in slot 1 is the main board), slots 8 and 10 (the IF board in slot 8 is the main board), slots 4 and 6 (the IF board in slot 4 is the main board), slots 11 and 13 (the IF board in slot 11 is the main board), or slots 12 and 14 (the IF board in slot 12 is the main board).

When configuring the radio links in 1+1 SD protection, you need to configure the 1+1 IF protection group followed by the IF/ODU information. Table 2-21 Configuration procedure of 1+1 SD protection Step 1 Operation A.2.1 Creating an IF 1+1 Protection Group A.2.4 Configuring the IF/ODU Information of a Radio Link Description The parameters need to be set according to the network planning.
If the radio link is configured with 1+1 SD protection, you need to configure the corresponding IF/ODU information of the main equipment. The parameters need to be set according to the network planning.
Issue 02 (2011-01-20)
2-65
Step 3
Description Required. l You can specify the maximum number of E1s that can be transmitted in intermediate modulation schemes, by setting the advanced attributes correspondingly. l Generally, it is recommended that you use the default values. l To ensure that a specific number of E1s can be transmitted in intermediate modulation schemes, adjust the E1 capacity in each modulation scheme according to the network planning information. When a new modulation scheme is adopted, the system transmits only the number of E1 services allowed by the modulation scheme and discards the excess E1 services.
Required when the ATPC function needs to be used. l If the ATPC function needs to be used, set ATPC Enable Status to Enabled. l During site commissioning, set ATPC Enable Status to Disabled. l It is recommended that you set ATPC Upper Threshold (dBm) to the central value plus 10 dB. l It is recommended that you set ATPC Lower Threshold (dBm) to the central value minus 10 dB. l It is recommended that you set ATPC Automatic Threshold Enable Status to Disabled.
NOTE For 1+1 SD, only the power attributes of the main ODU need to be set.
2-66
Issue 02 (2011-01-20)
Step 7
Operation Testing IF 1 +1 Protection Switching
Description Perform this operation to test whether the service data is configured correctly.

This topic describes how to plan and configure the 1+1 SD radio links by using an example.
NOTE
2.3.8.1 Networking Diagram The topic describes the networking information about the NEs. 2.3.8.2 Service Planning The service planning information contains all the parameter information required for configuring the NE data. 2.3.8.3 Configuration Process This topic describes the process for the data configuration.

The topic describes the networking information about the NEs. Figure 2-37 shows an important hop of the radio link. The 1+1 SD protection is adopted for the radio link between NE1 and NE2 to ensure reliable transmission of the service. Figure 2-37 Networking diagram of the 1+1 SD protection group
101 14930M 14510M 28M 1+1 SD Enabled Disabled H-polarzation
Tx high
Tx low
NE2
NE1
AM enabling
Issue 02 (2011-01-20)
2-67

The service planning information contains all the parameter information required for configuring the NE data. l Plan the slots for the working board and protection board. Plan the slots for the working board and protection board based on the board configuration of the equipment. The IF board in slot 3 functions as the working board, and the IF board in slot 5 functions as the protection board. l Plan the parameters for the protection group. The working mode in 1+1 protection is SD to provide the function of protecting the equipment. If no special requirements are proposed, the default values are used for all the parameters. The reverse switching function is enabled. In this case, the source end can perform reverse switching when an alarm is reported by the main or standby IF board at the sink end. l Plan the radio link information. The radio link information needs to be determined according to the network planning, and the relevant parameters are listed in the following table.
NOTE
In the case of radio links in 1+1 SD protection, one protection group corresponds to a link. Hence, you need to configure the corresponding IF/ODU information for the main equipment only.
Table 2-22 IF planning information Parameter NE1 3-ISU2 Radio Link ID IF Channel Bandwidth (MHz) IF Service Type AM Enable Status Modulation Mode of the Guaranteed AM Capacity Modulation Mode of the Full AM Capacity Guaranteed E1 Capacity ATPC Enable Status Enable E1 Priority 101 28 Hybrid(Native E1 + Eth) Enabled QPSK 128QAM 16 Disabled Disabled NE2 3-ISU2 101 28 Hybrid(Native E1 + Eth) Enabled QPSK 128QAM 16 Disabled Disabled
2-68
Issue 02 (2011-01-20)
Table 2-23 RF planning information Parameter NE1 53-ODU TX Frequency(MHz) T/R Spacing(MHz) TX Power(dBm) Power to be received(dBm) TX Status 14930 420 10 -45 Unmute NE2 53-ODU 14510 420 10 -45 Unmute

This topic describes the process for the data configuration.
Procedure
Step 1 See A.2.1 Creating an IF 1+1 Protection Group and create an IF 1+1 protection group. The values for the related parameters that need to be set in the main interface are as follows. Parameter Value Range NE1 Working Mode Revertive Mode WTR Time(s) Enable Reverse Switching Working Board Protection Board SD Revertive (default value) 600 (default value) Enable (default value) 3-IFU2 5-ISU2 NE2 SD Revertive (default value) 600 (default value) Enable (default value) 3-IFU2 5-ISU2
Step 2 See A.2.4 Configuring the IF/ODU Information of a Radio Link and configure the IF/ODU information of the radio link. The values for the related parameters of the IF boards are provided as follows. Parameter Value Range NE1 3-ISU2 IF Service Type AM Enable Status
Issue 02 (2011-01-20)
NE2 3-ISU2 Hybrid(Native E1+ETH) Enable

2-69
Hybrid(Native E1+ETH) Enable
Parameter
Value Range NE1 3-ISU2 NE2 3-ISU2 28 Mbit/s QPSK 128QAM 16 101 Disabled
IF Channel Bandwidth Modulation Mode of the Guarantee AM Capacity Modulation Mode of the Full AM Capacity Guarantee E1 Capacity Link ID Enable E1 Priority
28 Mbit/s QPSK 128QAM 16 101 Disabled
The values for the related parameters of the ODU are provided as follows. Parameter Value Range NE1 53-ODU TX Frequency(MHz) T/R Spacing(MHz) TX Power(dBm) TX Status Power to Be Received (dBm) 14930 420 10 unmute -45 NE2 53-ODU 14510 420 10 unmute -45
Step 3 A.5.8.2 Configuring the ATPC Attributes. The parameters for configuring the ATPC for the links of NE1 and NE2 need to be set to the same values, as provided in the following table. Parameter Value Range NE1 3-ISU2 ATPC Enable Status Disabled NE2 3-ISU2 Disabled
Step 4 Test IF 1+1 protection switching.

The test results meet the service requirements. ----End

Related Tasks
A.2.1 Creating an IF 1+1 Protection Group A.2.6 Querying the IF 1+1 Protection Status A.2.8 IF 1+1 Protection Switching A.11.6.1 Testing the IF 1+1 Switching

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

IF 1+1 protection switching: indicates that an IF 1+1 protection switching occurs.
2.3.11 FAQs
This topic provides the answers to the questions that are frequently raised when the 1+1 SD protection is adopted. 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 or 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. 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 standby ODU reports an alarm. If yes, clear the alarm and then perform a manual switching to check whether the switching is normal.
2.4 Cross-Polarization Interference Cancellation

The cross-polarization interference cancellation (XPIC) technology is used together with the cochannel dual-polarization (CCDP) technology. The application of the two technologies doubles the transmission capacity with channel conditions unchanged. 2.4.1 Introduction This section provides the definition of XPIC and describes its purpose. 2.4.2 Basic Concepts This topic describes the basic concepts that you need to be familiar with before you use the XPIC feature. 2.4.3 Specifications This topic provides the specifications of XPIC. 2.4.4 Availability The XPIC feature requires the support of the applicable boards. 2.4.5 Principles The IF board that supports the XPIC function receives and processes the signals in the horizontal and vertical polarization directions. Hence, the original signals can be recovered from the interfered signals. 2.4.6 Planning Guidelines Follow certain guidelines when you plan XPIC. 2.4.7 Configuration Procedure
To configure an XPIC link with no protection, you only need to configure the XPIC workgroup. To configure an XPIC link with 1+1 protection, you need to configure the 1+1 IF protection group in addition to the XPIC workgroup. 2.4.8 Configuration Example This topic uses an example to describe how to plan and configure the XPIC radio links according to the conditions of the network. 2.4.9 Task Collection This topic provides the hyperlinks of the operation tasks regarding the XPIC feature. 2.4.10 Relevant Alarms and Events When the XPIC compensation signal is lost, the XPIC IF board reports the corresponding alarm. 2.4.11 FAQs This topic describes the answers to the questions that are frequently raised when the XPIC feature is used.
2.4.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 doubles the transmission capacity with channel bandwidth unchanged. The transmission of two service signals in one microwave direction is considered as an example. l When the XPIC technology is not used, the bandwidth of two RF channels is used to transmit two service signals under the adjacent channel alternated polarization (ACAP) channel configuration, as shown in Figure 2-38. When the XPIC technology is used, the bandwidth of one RF channel is used to transmit two service signals under the CCDP channel configuration, as shown in Figure 2-39.
Figure 2-38 ACAP channel configuration (without the application of the XPIC technology)
Site A Modem Service Service Modem ODU 2 ODU 1 f1 H V f2 f2 f2 ODU 2 Modem Service Site B Modem f1 f1 ODU 1 Service
Issue 02 (2011-01-20)
2-73
Figure 2-39 CCDP channel configuration (with the application of the XPIC technology)
Site A Modem Service Service Modem ODU 2 ODU 1 f1 H V f1 f1 ODU 2 Modem Site B Modem f1 f1 ODU 1 Service Service
Purpose
When the XPIC technology is used, the link transmission capacity over the same channel can be doubled.

This topic describes the basic concepts that you need to be familiar with before you use the XPIC feature. 2.4.2.1 CCDP and XPIC The CCDP and XPIC are two technologies that are developed based on microwave polarization characteristics. The CCDP, wherein two signals are transmitted over two orthogonal polarization waves, doubles the transmission capacity; the XPIC cancels the cross-polarization interference between the two polarization waves. 2.4.2.2 System Configuration The OptiX RTN 980 supports one to seven XPIC workgroups. 2.4.2.3 XPIC Feature and 1+1 Protection Configuration One XPIC workgroup cannot form a 1+1 HSB/FD/SD protection group. The radio links in the horizontal and vertical polarization directions of one XPIC workgroup can work with the radio links in the horizontal and vertical polarization directions of another XPIC workgroup to form two 1+1 HSB/FD/SD protection groups.
2.4.2.1 CCDP and XPIC

The CCDP and XPIC are two technologies that are developed based on microwave polarization characteristics. The CCDP, wherein two signals are transmitted over two orthogonal polarization waves, doubles the transmission capacity; the XPIC cancels the cross-polarization interference between the two polarization waves. Microwave transmission can be classified into single-polarized transmission and CCDP transmission by polarization transmission mode. l In the case of the single-polarized transmission, a signal is transmitted over the horizontally polarized wave or the vertically polarized wave on the same channel, as shown in Figure 2-40. In the case of the CCDP transmission, two signals are transmitted over the horizontally polarized wave and the vertically polarized wave on the same channel, as shown in Figure 2-41.
2-74
Therefore, the capacity in CCDP transmission mode is double the capacity in single-polarized transmission mode. Figure 2-40 Single-polarized transmission
Figure 2-41 CCDP transmission
The ideal situation of CCDP transmission is that no interference exists between the two orthogonal signals that operate at the same frequency, and thus the receiver can easily recover the two signals. In actual engineering conditions, however, regardless of the orthogonality of the two signals, certain interference between the signals exists, due to cross-polarization discrimination (XPD) of the antenna and channel degradation. To cancel the interference, the XPIC technology is adopted. In the XPIC technology, the signals in the horizontal and vertical directions are received and then processed. In this manner, the original signals are recovered. The characteristics of the XPIC function supported by the OptiX RTN 980 are as follows: l l l The XPD tolerance is increased, and the notch performance is improved. The maximum difference between the IF cables in two polarization directions of an XPIC workgroup cannot exceed 12 meters in length. The XPIC function is realized completely through hardware.

The OptiX RTN 980 supports one to seven XPIC workgroups. Each XPIC workgroup uses one frequency and consists of the following items: l l l Two XPIC IF boards Two ODUs One dual-polarized antenna (separate mounting mode) or one dual-polarized antenna with an OMT (direct mounting mode)
Issue 02 (2011-01-20)
Figure 2-42 and Figure 2-43 show two typical configurations of one XPIC workgroup on the OptiX RTN 980The two XPIC IF boards are connected through XPIC cables so that the XPIC cancellation signal can be mutually transmitted between the two XPIC IF boards. Figure 2-42 Typical XPIC configuration (1)
ODU
Dual-polarized antenna ODU PIU PIU
FAN
System control, Switch & Timing board
XPIC IF board XPIC IF board
IDU
2-76
Issue 02 (2011-01-20)
Figure 2-43 Typical XPIC configuration (2)
ODU
OMT
Dual-polarized Antenna
ODU
PIU
PIU
FAN
XPIC IF board XPIC IF board
IDU
2.4.2.3 XPIC Feature and 1+1 Protection Configuration

One XPIC workgroup cannot form a 1+1 HSB/FD/SD protection group. The radio links in the horizontal and vertical polarization directions of one XPIC workgroup can work with the radio links in the horizontal and vertical polarization directions of another XPIC workgroup to form two 1+1 HSB/FD/SD protection groups. Figure 2-44 shows an example in which radio links in the horizontal and vertical polarization directions of two XPIC workgroups form two 1+1 HSB protection groups. l The service channels of the XPIC IF boards in slots 3 and 4 form one XPIC workgroup, and the service channels of the XPIC IF boards in slots 5 and 6 form another XPIC workgroup. The service channels of the XPIC IF boards in slots 3 and 5 form one 1+1 HSB protection group, and the service channels of the XPIC IF boards in slots 4 and 6 form another 1+1 HSB protection group. The service channels of the XPIC IF boards in slots 3 and 4 are the main channels of the two 1+1 HSB protection groups. In normal cases, the two main channels (in the horizontal and vertical polarization directions) transmit services.
Issue 02 (2011-01-20)
2-77
The service channels of the XPIC IF boards in slots 5 and 6 are the standby channels of the two 1+1 HSB protection groups, which protect main channels.
Figure 2-44 Typical XPIC configuration (1+1 protection configuration)

V-polarization Dual-polarized antenna
H-polarization
ODU Working channel 1 Hybrid coupler ODU Protection channel 1 PIU
FAN
System control, Switch & Timing board XPIC IF board XPIC IF board SLOT 1 IDU SLOT 5 SLOT 3 XPIC IF board XPIC IF board SLOT 6 SLOT 4 SLOT 2
In the receive direction, if the XPIC IF board in slot 3 is faulty or its connected ODU is faulty, HSB switching occurs on the equipment and the services are switched to the channel of the XPIC IF board in slot 5. The fault also causes loss of the XPIC cancellation signal sent from the XPIC IF board in slot 3 to the XPIC IF board in slot 4. As a result, HSB switching occurs on the XPIC IF board in slot 4 and the services are switched to the channel of the XPIC IF board in slot 6. Thus, the services are switched from one XPIC workgroup to another XPIC workgroup. In the transmit direction, if signal transmission in the polarization direction (vertically, for example) corresponding to the XPIC IF board in slot 3 is faulty (for example, a transmitter of the ODU fails), switching occurs at the local end. That is, services are switched from the XPIC IF board in slot 3 to the XPIC IF board in slot 5. Meanwhile, switching occurs in the horizontal polarization direction. That is, services are switched from the XPIC IF board in slot 4 to the XPIC IF board in slot 6.
This topic provides the specifications of XPIC.
Table 2-24 lists the specifications of XPIC. Table 2-24 Specifications of XPIC Item Specification IFX2 Radio link form Integrated IP radio (Native E1 and Native Ethernet) ISX2 l Integrated IP radio (Native E1 and Native Ethernet) l Integrated IP radio (Native STM-1 and Native Ethernet) l SDH microwave l Mixed microwave
NOTE Mixed microwave has different microwave types in two polarization directions. For example, one polarization direction transmits SDH microwave services, whereas the other polarization direction transmits Native E1 and Native Ethernet services of Integrated IP radio. Alternatively, one polarization direction transmits Native STM-1 and Native Ethernet services of Integrated IP radio, whereas the other polarization direction transmits Native E1 and Native Ethernet services of integrated IP microwave.
Issue 02 (2011-01-20)
2-79
Item
Specification IFX2 ISX2 Integrated IP radio: l Channel spacing: 28 MHz, 40MHz, and 56 MHz l Modulation scheme: adaptive modulation scheme and fixed modulation schemes SDH radio link: l STM-1 microwave: 28 MHz (channel spacing), 128QAM (modulation scheme) l 2xSTM-1 microwave: 56MHz (channel spacing), 128QAM (modulation scheme)
Radio work mode
l Channel spacing: 28 MHz and 56 MHz l Modulation scheme: adaptive modulation scheme and fixed modulation schemes
Number of XPIC workgroupsa Implementation mode
Seven groups Hardware
NOTE
a:
One XPIC workgroup must be configured on the same NE. That is, one XPIC workgroup must not be configured on two or more NEs.
2.4.4 Availability
The XPIC feature requires the support of the applicable boards.

Table 2-25 Hardware and version support Feature XPIC Applicable Board IFX2 ISX2 Applicable Hardware Version All the versions All the versions Applicable Product Version V100R003C00 and later V100R003C00 and later
2-80
Issue 02 (2011-01-20)
The dependencies between the XPIC feature and other features are as follows: l l For the relationship between XPIC feature and 1+1 protection configuration, see 2.4.2.3 XPIC Feature and 1+1 Protection Configuration. The radio links in the horizontal and vertical polarization directions of one XPIC workgroup must be configured with the same ATPC-specific parameters (including the ATPC enabling status and ATPC adjustment thresholds). Relation with the AM Feature You can enable or disable the AM feature for the radio links in the horizontal and vertical polarization directions of one XPIC workgroup. If you disable the AM feature for the radio links in the horizontal and vertical polarization directions of one XPIC workgroup, the modulation scheme of the two radio links must be the same. If you enable the AM feature for the radio links in the horizontal and vertical polarization directions of one XPIC workgroup, the modulation mode of the guarantee AM capacity and modulation mode of the full AM capacity of the two radio links must be the same. l l A radio link that is configured with the XPIC feature can work as the working source, protection source, or service sink of the SNCP. When you configure the XPIC workgroup, the NE does not automatically create a LAG for the two radio links in the horizontal and vertical polarization directions of this XPIC workgroup. If a LAG is required, manually create a LAG in load sharing mode. The guaranteed E1/STM-1 capacity, E1 priority enabling, and full E1 capacity parameters must be set to the same values for the two IF ports in a LAG. As shown in Figure 2-44, on the OptiX RTN 980, the radio links in the horizontal and vertical polarization directions of the two XPIC workgroups form two 1+1 protection groups. In this case, a LAG cannot be created. If N+0 non-protection links are member links in multiple XPIC workgroups, manually create a LAG that consists of all member links in the XPIC workgroups in load sharing mode. Assuming four member links in two XPIC workgroups form 4+0 non-protection links, manually create a LAG that consists of the four member links in load sharing mode. Members in an XPIC workgroup cannot be configured as members in an N+1 protection group.
2.4.5 Principles
The IF board that supports the XPIC function receives and processes the signals in the horizontal and vertical polarization directions. Hence, the original signals can be recovered from the interfered signals.
Issue 02 (2011-01-20)
2-81
Figure 2-45 Realization principle of the XPIC

Horizontal polarization
XPIC module of IF board

A/D Filter Decision Coefficient control Filter
Modem horizontal
Cross interference Cross interference
Filter
XPIC module of IF board

Coefficient control
Modem vertical
A/D
Filter
Decision
Vertical polarization
The realization principle is as follows: 1. 2. The transmitter transmits two co-frequency signals over a horizontal polarization wave and a vertical polarization wave. Due to the XPD of the antenna and channel degradation, cross-polarization interference is generated in the signals received by the ODU and thus results in the cross-polarization interference in the IF signals transmitted from the ODU to the IF board that supports the XPIC function. The XPIC module of the IF board that supports the XPIC function receives the IF signal from the ODU and the IF signal from the other IF board that supports the XPIC function, and processes the IF signals, for example, performs A/D conversion. The XPIC module of the IF board that supports the XPIC function 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 the two IF signals are filtered and combined, the interference is cancelled in the two IF signals.
3.
4.

Follow certain guidelines when you plan XPIC. When you plan XPIC, follow certain guidelines: l l When CCDP is applied to Hybrid radio links, XPIC IF boards must be installed and the XPIC function must be enabled. The transmit frequency, transmit power, T/R spacing, and ATPC parameters (including ATPC enable status and ATPC adjustment thresholds), channel spacing, modulation scheme, and AM parameters (AM enabled status, AM guaranteed capacity, and AM fullcapacity modulation scheme) 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 XPIC IF boards need to be determined based on expansion requirements. To configure an XPIC workgroup under no protection, install the XPIC IF boards as follows.
Slots
Slot for the Board Processing Vertically Polarized Signals Slot 3 Slot 7 Slot 1 Slot 8 Slot 4 Slot 11 Slot 12
Slot for the Board Processing Horizontally Polarized Signals Slot 5 Slot 9 Slot 2 Slot 10 Slot 6 Slot 13 Slot 14
Slots 3 and 5 Slots 7 and 9 Slots 1 and 2 Slots 8 and 10 Slots 4 and 6 Slots 11 and 13 Slots 12 and 14
To configure an XPIC workgroup under 1+1 protection, install the XPIC IF boards as follows. Slots Slot for the Working Board Processing Vertically Polarized Signals Slot 3 Slot 9 Slot 1 Slot for the Working Board Processing Horizontally Polarized Signals Slot 4 Slot 10 Slot 2 Slot for the Protection Board Processing Vertically Polarized Signals Slot 5 Slot 11 Slot 7 Slot for the Protection Board Processing Horizontally Polarized Signals Slot 6 Slot 12 Slot 8
Slots 3, 4, 5, and 6 Slots 9, 10, 11, and 12 Slots 1, 2, 7, and 8
NOTE
Only 1+1 HSB protection can be used when the boards are installed in slots 1, 2, 7, and 8. The board in slot 1 is the working board processing vertically polarized signals, and the board in slot 2 is the working board processing horizontally polarized signals; the board in slot 7 is the protection board processing vertically polarized signals, and the board in slot 8 is the protection board processing horizontally polarized signals.

To configure an XPIC link with no protection, you only need to configure the XPIC workgroup. To configure an XPIC link with 1+1 protection, you need to configure the 1+1 IF protection group in addition to the XPIC workgroup.
Issue 02 (2011-01-20)
2-83
Table 2-26 Procedure for configuring the XPIC link Step 1 Operation A.2.2 Creating an XPIC Protection Group A.2.3 Setting the AM Attributes of the XPIC Hybrid Radio Link A.2.1 Creating an IF 1+1 Protection Group Description Required. The parameters need to be set according to the network planning information.
Required. The parameters need to be set according to the network planning information. The parameters need to be set to the same values for the two polarization directions.
Required when two XPIC workgroups need to form two 1+1 protection groups. The parameters need to be set according to the network planning information.
NOTE One XPIC workgroup cannot form a 1+1 protection group. The radio link in the horizontal/vertical polarization direction of the XPIC workgroup can form a 1+1 protection group with the radio link in the horizontal/ vertical polarization direction of another XPIC workgroup.
A.2.4 Configuring the IF/ODU Information of a Radio Link
Required. l If the IF board is IFX2, set Guarantee E1 Capacity, Enable E1 Priority, Power to Be Received(dBm), and Full E1 Capacity according to the network planning information. l If the IF board is ISX2, set IF Service Type, STM-1 Capacity, Guarantee E1 Capacity, Enable E1 Priority, Power to Be Received(dBm), and Full E1 Capacity according to the network planning information.
NOTE The parameters for IF boards in the two polarization directions both need to be set, and can be set to different values.
A.5.8.3 Setting Advanced AM Attributes
Optional. l You can specify the maximum number of E1s that can be transmitted in intermediate modulation schemes, by setting the advanced attributes correspondingly. l Generally, it is recommended that you use the default values. l To ensure that a specific number of E1s can be transmitted in intermediate modulation schemes, adjust the E1 capacity in each modulation scheme according to the network planning information. When a new modulation scheme is adopted, the system transmits only the number of E1 services allowed by the modulation scheme and discards the excess E1 services.
2-84
Issue 02 (2011-01-20)
Step 6
Operation A.5.9.3 Setting the Power Attributes of the ODU
Description Optional. l To set the maximum transmit power that is supported by the ATPC adjustment function, you need to setMaximum Transmit Power(dBm) according to the actual requirements. 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. Therefore, determine whether to set these parameters according to the actual requirements.
NOTE The parameters for ODUs in the two polarization directions both need to be set.
NOTE
During the configuration of XPIC workgroups, an Integrated IP radio NE will not automatically create LAGs for the links in the horizontal and vertical polarization directions in an XPIC workgroup. If necessary, manually create a load-sharing LAG. Ensure that the AM attributes, channel spacing, modulation modes, and STM-1/E1 capacity of IF ports in a LAG are consistent so that the Ethernet service bandwidths in the two polarization directions can be the same under all conditions.

This topic uses an example to describe how to plan and configure the XPIC radio links according to the conditions of the network.
NOTE
This section describes how to configure XPIC on the ISX2 board. XPIC is configured on the IFX2 board in the same way, but the values of IF parameters are different. For details, see the parameter description.
2.4.8.1 Networking Diagram This topic describes the networking information about the NEs. 2.4.8.2 Service Planning The service planning information contains all the parameter information required for configuring the NE data. 2.4.8.3 Configuration Process This topic describes the procedure for the data configuration.

This topic describes the networking information about the NEs. The service requirements between two sets of OptiX RTN 980 are as follows: l l l
Issue 02 (2011-01-20)
The Integrated IP radio link needs to transmit 32xE1 services and 400 Mbit/s Ethernet services at the same time. The AM function is enabled for each Integrated IP radio link. According to the spectrum planning information, the XPIC function needs to be enabled.
The protection for the Integrated IP radio links must be provided.

101 32660M 31848M 56M 1+1 HSB V-polarization 102 32660M 31848M 56M 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 Integrated IP radio links that adopt the XPIC as shown in Figure 2-46 to meet the requirement for high-capacity transmission, according to the preceding service requirements and the available spectrum resources. As shown in Figure 2-47, NE1 and NE2 have the same board configurations. The EM6T board accesses 400 Mbit/s Ethernet services and the SP3D board accesses 32xE1 services.
2-86
Issue 02 (2011-01-20)
Figure 2-47 Board configuration

V-polarization Dual-polarized antenna
H-polarization
FAN
System control, Switch & Timing board XPIC IF board XPIC IF board SLOT 1 IDU SLOT 5 SLOT 3 XPIC IF board XPIC IF board SLOT 6 SLOT 4 SLOT 2
In this example, two XPIC workgroups form two 1+1 HSB protection groups. l l The service channels on the ISX2 boards in slots 3 and 4 form one XPIC workgroup. The service channels on the ISX2 boards in slots 5 and 6 form the other XPIC workgroup. The service channels on the ISX2 boards in slots 3 and 5 form one 1+1 HSB protection group. The service channels on the ISX2 boards in slots 4 and 6 form the other 1+1 HSB protection group. The service channels on the ISX2 boards in slots 3 and 4 are the working channels of the two 1+1 HSB protection groups. Generally, the two working channels in the vertical and horizontal polarization directions each transmit 16xE1 services and 200 Mbit/s Ethernet services. The service channels on the ISX2 boards in slots 5 and 6 are the protection channels of the two 1+1 HSB protection groups and provides the protection for the working channels.

The service planning information contains all the parameter information required for configuring the NE data.
Issue 02 (2011-01-20)
2-87
Basic Information About Radio Links

According to the spectrum allocation on the radio network and the required radio transmission capacity, you can be familiar with the basic information about the radio links, as provided in Table 2-27. Table 2-27 Basic information about the radio links Parameter Radio 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) IF Channel Bandwidth (MHz) IF Service Type RF configuration mode Polarization direction Link 1 101 NE1 NE2 32660 31848 812 56 Hybrid(Native E1 + Eth) 1+1 HSB V (vertical polarization) Link 2 102 NE1 NE2 32660 31848 812 56 Hybrid(Native E1 + Eth) 1+1 HSB H (horizontal polarization)
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. In this example, two XPIC workgroups need to form two 1+1 HSB protection groups. Hence, the IDs of the radio links in the vertical direction of the two XPIC workgroups must be 101 and the IDs of the radio links in the horizontal direction of the two XPIC workgroups must be 102.
Information About the Hybrid/AM Configuration

According to the capacity of E1 and Ethernet services and the availability requirement, you can calculate the information about the Hybrid/AM Configuration, as provided in Table 2-28. Table 2-28 Information about the Hybrid/AM Configuration Parameter Number of E1 services Capacity of Ethernet services (Mbit/ s) AM Enable Status
2-88
Link 1 16 200 Enabled
Link 2 16 200 Enabled

Issue 02 (2011-01-20)
Parameter Modulation Mode of the Guaranteed AM Capacity Modulation Mode of the Full AM Capacity Enable E1 Priority
Link 1 QPSK 64QAM Disabled
Link 2 QPSK 64QAM Disabled
NOTE
l The Hybrid radio capacity and the AM function require the proper license file. l You can enable or disable the AM feature for the radio links in the horizontal and vertical polarization directions of one XPIC workgroup. l If you disable the AM feature for the radio links in the horizontal and vertical polarization directions of one XPIC workgroup, the modulation scheme of the two radio links must be the same. l If you enable the AM feature for the radio links in the horizontal and vertical polarization directions of one XPIC workgroup, Modulation Mode of the Guarantee AM Capacity and Modulation Mode of the Full AM Capacity of the two radio links must be the same.
Information About the Power and ATPC

By using the radio network planning software such as the Pathloss, you can analyze and compute the parameters of radio links and obtain the information about the radio link power and ATPC, as provided in Table 2-29. Table 2-29 Information about the Power and ATPC Parameter Transmit Power (dBm) Link 1 6.0 (NE1) 6.0 (NE2) Receive Power (dBm) -45.0 (NE1) -45.0 (NE2) ATPC Enabled ATPC Automatic Threshold Enable Status ATPC Upper Threshold (dBm) ATPC Lower Threshold (dBm) Disabled Link 2 6.0 (NE1) 6.0 (NE2) -45.0 (NE1) -45.0 (NE2) Disabled -
NOTE
l The transmit power is calculated in AM guaranteed capacity mode. l The receive power is calculated in AM guaranteed capacity mode. l In this example, the ATPC function is disabled.
Issue 02 (2011-01-20)
2-89
Configuration Information About the XPIC Workgroup

Figure 2-47 shows the board configurations of NE1 and NE2. According to the rules for planning the slot priorities of IF boards and the 1+1 HSB protection, you can obtain the configuration information about the XPIC, as provided in Table 2-30. Table 2-30 Configuration information about the XPIC Parameter XPIC workgroup 1 V (vertical polarization) H (horizontal polarization) XPIC workgroup 2 V (vertical polarization) H (horizontal polarization) NE1 3-ISX2 4-ISX2 5-ISX2 6-ISX2 NE2 3-ISX2 4-ISX2 5-ISX2 6-ISX2
Configuration Information About the 1+1 HSB Protection Group

Figure 2-47 shows the board configurations of NE1 and NE2. According to 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 group, as provided in Table 2-31. Table 2-31 Configuration information about the 1+1 HSB protection group 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 3-ISX2 5-ISX2 HSB Revertive Mode 600 Disabled 4-ISX2 6-ISX2 HSB Revertive Mode 600 Disabled NE2 3-ISX2 5-ISX2 HSB Revertive Mode 600 Disabled 4-ISX2 6-ISX2 HSB Revertive Mode 600 Disabled
2-90
Issue 02 (2011-01-20)

Procedure
Step 1 See A.2.2 Creating an XPIC Protection Group and create the XPIC workgroups. Parameter Value (NE1) XPIC Workgroup 1 IF Channel Bandwidth Polarization direction-H Link ID-V Polarization direction-H Link ID-H Transmit Power(dBm) Transmission Frequency (MHz) T/R Spacing (MHz) Transmission Status ATPC Enabled 56M 3-ISX2-1 101 4-ISX2-1 102 6.0 32660 XPIC Workgroup 2 56M 5-ISX2-1 101 6-ISX2-1 102 6.0 32660 Value (NE2) XPIC Workgroup 1 56M 3-ISX2-1 101 4-ISX2-1 102 6.0 31848 XPIC Workgroup 2 56M 5-ISX2-1 101 6-ISX2-1 102 6.0 31848
812 unmute Disabled
812 unmute Disabled
812 unmute Disabled
812 unmute Disabled
Step 2 See A.2.3 Setting the AM Attributes of the XPIC Hybrid Radio Link and set the Hybrid/ AM attribute of the XPIC Hybrid radio links. The parameters for the Hybrid/AM Configuration of NE1 and NE2 need to be set to the same values, as provided in the following table. Parameter Value Range 3-ISX2-1 AM Enable Status Enabled 4-ISX2-1 Enabled 5-ISX2-1 Enabled 6-ISX2-1 Enabled
Issue 02 (2011-01-20)
2-91
Parameter
Value Range 3-ISX2-1 4-ISX2-1 QPSK 5-ISX2-1 QPSK 6-ISX2-1 QPSK
Modulation Mode of the Guarantee AM Capacity Modulation Mode of the Full AM Capacity
QPSK
64QAM
64QAM
64QAM
64QAM
Step 3 See A.2.1 Creating an IF 1+1 Protection Group and configure the IF 1+1 protection. The parameters for configuring the 1+1 HSB protection group 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 Working Board Protection Board HSB Revertive Mode 600 Disabled 3-ISX2-1 5-ISX2-1 1+1 HSB Protection Group 2 H (Horizontal Polarization) HSB Revertive Mode 600 Disabled 4-ISX2-1 6-ISX2-1
Step 4 A.2.4 Configuring the IF/ODU Information of a Radio Link. Parameter Value (NE1) Working 1+1 HSB Protection Group 3-ISX2-1&53-ODU 5-ISX2-1&55-ODU IF Service Type Guarantee E1 Capacity Enable E1 Priority Hybrid(Native E1+ETH) 16 Disabled Value (NE2) Working 1+1 HSB Protection Group 3-ISX2-1&53-ODU 5-ISX2-1&55-ODU Hybrid(Native E1+ETH) 16 Disabled
2-92
Issue 02 (2011-01-20)
Parameter
Value (NE1) Working 1+1 HSB Protection Group 3-ISX2-1&53-ODU 5-ISX2-1&55-ODU
Value (NE2) Working 1+1 HSB Protection Group 3-ISX2-1&53-ODU 5-ISX2-1&55-ODU -45.0
Power to Be Received(dBm)
-45.0
----End

This topic provides the hyperlinks of the operation tasks regarding the XPIC feature.
Related Tasks
A.2.2 Creating an XPIC Protection Group A.2.3 Setting the AM Attributes of the XPIC Hybrid Radio Link

When the XPIC compensation signal is lost, the XPIC IF board reports the corresponding alarm.
Relevant Alarms
XPIC_LOS The XPIC_LOS alarm indicates that the XPIC compensation signal is lost.
Relevant Events
None.
2.4.11 FAQs
This topic 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 XPIC IF boards that form the XPIC workgroup must have the same transmit frequency and T/R spacing. If you enable the AM feature for the radio links in the horizontal and vertical polarization directions of one XPIC workgroup, Modulation Mode of the Guarantee AM Capacity and Modulation Mode of the Full AM Capacity of the two radio links must be the same. l
Issue 02 (2011-01-20)
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.
2.5 N+1 Protection

The N+1 protection refers to the protection scheme in which N working channels in a microwave direction share one protection channel. When the N+1 protection is configured, the transmission bandwidth in a microwave direction increases and is protected. 2.5.1 Introduction This section provides the definition of N+1 protection and describes its purpose. 2.5.2 Basic Concepts This topic describes the basic concepts with which you should be familiar before you use the N +1 protection. 2.5.3 Specifications This topic provides the specifications of N+1 protection. 2.5.4 Reference Standards and Protocols This section describes the standards and protocols associated with N+1 protection. 2.5.5 Availability The N+1 protection feature requires the support of the applicable boards. 2.5.6 Principles The principles for SDH microwave and Integrated IP radio are different. 2.5.7 Planning Guidelines Follow certain guidelines when you plan N+1 protection. 2.5.8 Configuration Procedure To configure an N+1 protection group of radio links, you need to configure the IF/ODU information of the working links and the protection link and then create the N+1 protection group. 2.5.9 Configuration Example This topic uses an example to describe how to plan and configure the N+1 protection for the Integrated IP radio according to the actual network conditions. The method of configuring the N+1 protection for the SDH microwave is simpler than the method of configuring the N+1 protection for the Integrated IP radio and hence is not described in this topic. 2.5.10 Task Collection This topic provides the hyperlinks of the operation tasks regarding the N+1 protection feature. 2.5.11 Relevant Alarms and Performance Events When an N+1 protection switching occurs, the IF board reports corresponding alarms. 2.5.12 FAQs This topic describes the answers to the questions that are frequently raised when the N+1 protection feature is used.
2.5.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 2-48 shows the application of N+1 protection. Figure 2-48 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.

This topic describes the basic concepts with which you should be familiar before you use the N +1 protection. 2.5.2.1 System Configuration (SDH Microwave) If the OptiX RTN 980 on an SDH radio link uses the IF1 boards, the N+1 protection is supported. 2.5.2.2 System Configuration This section describes 2+1 and 3+1 protection configuration. 2.5.2.3 Protection Mode The protection type of N+1 protection is similar to the dual-ended revertive switching mode of 1:N linear multiplex section protection. 2.5.2.4 Switching Condition Similar to linear multiplex section protection, N+1 protection can be triggered by local SF conditions, local SD conditions, local external switching requests, and byte K sent from the opposite NE. 2.5.2.5 Switching Impact The switching impacts of Integrated IP radio and SDH microwave are different.
2.5.2.1 System Configuration (SDH Microwave)

If the OptiX RTN 980 on an SDH radio link uses the IF1 boards, the N+1 protection is supported.
1+1 Protection Configuration

An IDU 980 supports a maximum of . One 1+1 protection group occupies two channels and requires that the following items are configured: l l l Two IF1 boards Two ODUs One single-polarized antenna (with one balanced hybrid coupler)
Figure 2-49 provides a typical configuration of one 1+1 protection group. The configuration is as follows: l l The IF1 board in slot 3 provides one working channel. The IF1 board in slot provides one protection channel. The spacing between the transmit frequency of the main ODU and the transmit frequency of the standby ODU should be greater than 56 MHz to prevent adjacent-channel interference. The two STM-1 optical ports on the board transmit one working service and one extra service, respectively.
Figure 2-49 Typical configuration of one 1+1 protection group
Special Application of the N+1 Protection for the SDH Microwave

In the case of the OptiX RTN 980, the SDH radio link and the optical fiber link can form an N +1 protection group. In this case, the optical fiber link works as the working link, and the SDH radio link works as the protection link.
Limitations of the N+1 Protection for the SDH Microwave

The limitations of N+1 protection for the SDH microwave are as follows: l The N+1 protection supports only the STM-1 radio working mode.

This section describes 2+1 and 3+1 protection configuration.

An IDU 980 supports a maximum of four 2+1 protection groups. One 2+1 protection group occupies three channels and requires that the following items are configured: l l l Three IF boards Three ODUs One dual-polarized antenna (with one balanced hybrid coupler)
Figure 2-50 provides a typical configuration of one 2+1 protection group. The configuration is as follows: l l l The IF boards in slots 3 and 5 provide two working channels. The IF board in slot 6 provides one protection channel. The three channels are configured in ACAP mode. See Figure 2-51. The radio transmit power of the three channels should be the same if possible to minimize the 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.
Issue 02 (2011-01-20)
2-97
ODU Working channel 1 Hybrid coupler ODU Protection channel ODU Working channel 2 PIU
Dual-polarized antenna
PIU
FAN
IF board IF board
IF board
IDU
Figure 2-51 Typical channel configuration of one 2+1 protection group

Working channel 1 V H Protection channel Working channel 2
2-98
Issue 02 (2011-01-20)

An IDU 980 supports a maximum of three 3+1 protection group. One 3+1 protection group occupies four channels and requires that the following items are configured: l l l Four IF boards Four ODUs One dual-polarized antenna (with two balanced hybrid couplers)
Figure 2-52 provides a typical configuration of one 3+1 protection group. The configuration is as follows: l l l The IF boards in slots 3, 4, and 5 provide three working channels. The IF board in slot 6 provides one protection channel. The four channels are configured in ACAP mode. See Figure 2-53. The radio transmit power of the four channels should be the same if possible to minimize the adjacent-channel interference. That is, the ODU transmit power set for the four channels should be the same.
ODU Working channel 1 Hybrid coupler ODU Working channel 2
ODU Working channel 3 Hybrid coupler ODU Protection channel
PIU
PIU
FAN
System control, Switch & Clock board System control, Switch & Clock board
IF board IF board
IF board IF board
IDU
Issue 02 (2011-01-20)
2-99
Figure 2-53 Typical channel configuration of one 3+1 protection group

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

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 described as follows: l l When a protection switching occurs, the services on the working channels in both directions are switched to the protection channel. 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 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 due to an unstable working channel, it is recommended that you set the WTR time to five to twelve minutes.
2.5.2.4 Switching Condition

Similar to linear multiplex section protection, N+1 protection can be triggered by local SF conditions, local SD conditions, local external switching requests, and byte K sent from the opposite NE. Table 2-32 Switching conditions of the N+1 protection Switching Condition Lockout of protection channel (external switching) Priority From top downwards and from the highest priority to the lowest priority Description The lockout of protection blocks normal services from entering the protection channel but does not block services from being switched from the protection channel to the working channel. The SF condition on the protection channel is equivalent to the lockout of protection.
Issue 02 (2011-01-20)
2-100
Switching Condition Forced switching (external switching) Signal failure (SF)
Priority
Description Services on the working channel are forcibly switched to the protection channel. The SF condition on the working channel enables services to be switched to the protection channel. l In the case of N+1 protection for the SDH microwave, 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. l In the case of N+1 protection for the Integrated IP radio (Native E1+ETH), when there is the VOLT_LOS (reported on the IF board), RADIO_TSL_HIGH, RADIO_TSL_LOW, RADIO_RSL_HIGH, R_LOC, R_LOF, MW_LOF, MW_BER_EXC alarm on the working channel, or when the hardware of an ODU or IF board is faulty, the SF switching is triggered. l In the case of N+1 protection for the Integrated IP radio (Native STM-1+ETH), when there is the MW_LOF, R_LOC, R_LOF, MS_AIS, B2_EXC, MW_BER_EXC alarm on the working channel, the SF switching is triggered.
Issue 02 (2011-01-20)
2-101
Switching Condition Signal degradation (SD)
Priority
Description The SD condition on the working channel enables services to be switched to the protection channel. l In the case of N+1 protection for the SDH microwave, when there is the B2_SD alarm on the working channel, the SD switching is triggered. l In the case of N+1 protection for the Integrated IP radio (Native E1+ETH), when there is the MW_BER_SD alarm on the working channel, the SD switching is triggered. l In the case of N+1 protection for the Integrated IP radio (Native STM-1+ETH), when there is the B2_SD, MW_BER_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 protection channel is faulty, no switching occurs. Otherwise, the system switches services from the working channel to the protection channel or from the protection channel to the working channel according to the command. The switching then changes to the manual switching state.
2-102
Issue 02 (2011-01-20)
Priority
Description After services are switched to the protection channel due to the SF/SD condition on the working channel, the working channel is already restored to normal, and the WTR time expires, a revertive switching occurs. From the time the working channel is restored to normal to the time the revertive switching occurs, the switching is in WTR state. After the revertive switching is complete, the switching changes to the normal state. services are not actually switched. The exercise functionality is used only to check whether an NE can normally implement the N+1 protection protocol.
Exercise switching (external switching)
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 a 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 the 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.

The switching impacts of Integrated IP radio and SDH microwave are different.
Switching Impact of the N+1 Protection (SDH Microwave)

The working TDM services are interrupted within the N+1 protection switching time (shorter than 50 ms). The extra TDM services are interrupted from the time when the normal services are switched to the protection channel to the time when the services are restored to the working channel.
Issue 02 (2011-01-20)
2-103
Switching Impact of the N+1 Protection (Integrated IP radio)

l In the case of TDM services, the working TDM services are interrupted within the N+1 protection switching time (shorter than 50 ms). The extra TDM services are interrupted from the time when the normal services are switched to the protection channel to the time when the services are restored to the working channel. In the case of Ethernet services (including Native Ethernet and packet services), the Ethernet services are interrupted within the air-interface LAG protection switching time (shorter than 500 ms).
This topic provides the specifications of N+1 protection. Table 2-33 lists the specifications of N+1 protection. Table 2-33 Specifications of N+1 protection Item Radio link form Specification SDH radio link Hybrid/Packet radio link Radio work mode IF1 SDH radio link: l Service capacity: STM-1 l Channel spacing: 28 MHz l Modulation scheme: 128QAM (a fixed modulation scheme) IFU2/IFX2 l Integrated IP radio (Native E1 and Native Ethernet) l Integrated IP radio (Native STM-1 and Native Ethernet)
2-104
Issue 02 (2011-01-20)
Item
Specification ISU2/ISX2 l Integrated IP radio (Native E1 and Native Ethernet) l Integrated IP radio (Native STM-1 and Native Ethernet) l SDH radio link: STM-1 radio: The channel spacing is 28 MHz and the modulation scheme is 128QAM. 2xSTM-1 radio: The channel spacing is 56 MHz and the modulation scheme is 128QAM.
Number of N+1 protection groups
l N+1(N=1): Seven groups l N+1(N=2): Four groups l N+1(N=3): Three groups l N+1(4N6): Two groups l N+1(N=7): One group
Protection switching duration
TDM services: less than 50 ms Ethernet services (including Native Ethernet and packet services): less than 500 ms 300 seconds to 720 seconds
WTR time

This section describes the standards and protocols associated with 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."
2.5.5 Availability
The N+1 protection feature requires the support of the applicable boards.
Issue 02 (2011-01-20)
2-105

Table 2-34 Hardware and version support Feature N+1 protection Applicable Board IF1 IFU2 IFX2 ISU2 ISX2 Applicable Hardware Version All the versions All the versions All the versions All the versions All the versions Applicable Product Version V100R003C00 and later V100R003C00 and later V100R003C00 and later V100R003C00 and later V100R003C00 and later
NOTE
The co-existence of N+1 protection and E1 priority is applicable to V100R003C00 and a later version.
The dependencies between the N+1 protection feature and other features are as follows: l l l l l Regarding N+1 protection for SDH microwave, the service capacity, modulation mode, and channel spacing of members must be set to the same. The IF mode, TDM service amount, channel spacing, and modulation mode of members of the Integrated IP radio must be set to the same. 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. The N+1 protection has the following relationships with the AM feature: The AM feature must be enabled or disabled for all the members of an N+1 protection group at the same time. The modulation scheme of all the members of an N+1 protection group must be the same if the AM feature is disabled for all these members. The modulation mode of the guaranteed AM capacity , modulation mode of the full AM capacity, and guaranteed E1 capacity must be the same if the AM feature is enabled for all the members of an N+1 protection group. The members under N+1 protection must be enabled or disabled with E1 priority simultaneously. The members under N+1 protection must be enabled with E1 priority simultaneously, and the E1 full capacity parameters of members must be set to the same.
When you create an N+1 protection group of the Integrated IP radio, the NE automatically creates the LAG in load sharing mode. The main port in the LAG is the Integrated IP radio port with the smallest slot ID on the IF board in the N+1 protection group. The radio link configured with the N+1 protection can work as the working source, protection source, or service sink of an SNCP group. If the AM function is enabled on the Integrated IP radio links of an N+1 protection group, the protection radio link still works in the original modulation mode even after the N+1 protection switching is performed. Members in an XPIC workgroup cannot be configured as members in an N+1 protection group. N+1 protection can co-exist with MPLS APS. N+1 protection can co-exist with PW APS.
l l
l l l
2.5.6 Principles
The principles for SDH microwave and Integrated IP radio are different. 2.5.6.1 SDH Microwave The N+1 protection switching for the SDH microwave is realized based on the automatic bridging of the cross-connect unit. 2.5.6.2 Integrated IP radio In the case of N+1 protection for the Integrated IP radio, the switching on the TDM plane is realized based on the automatic bridging of the cross-connect unit and the switching on the packet plane is realized based on the switching of the LAG.
2.5.6.1 SDH Microwave

The N+1 protection switching for the SDH microwave is realized based on the automatic bridging of the cross-connect unit. The configuration of the 2+1 protection as described in 2.5.2.1 System Configuration (SDH Microwave) is provides as an example to describe the switching principles of the N+1 protection. The switching principles of the 1+1, 3+1, and 4+1 protection are the same as the switching principles of the 2+1 protection.
Issue 02 (2011-01-20)
2-107
Figure 2-54 Realization principles of the 2+1 protection (before the switching)
ODU Antenna IF board Cross-connect Unit Service Interface Unit STM-1 (Normal Service 1) STM-1 (Normal Service 2) STM-1 (Extra Service) NE 1 NE 2 ODU Antenna IF board Cross-connect Unit Service Interface Unit STM-1 (Normal Service 1) STM-1 (Normal Service 2) STM-1 (Extra Service)
Figure 2-55 Realization principles of the 2+1 protection (after the switching)
ODU Antenna IF board Cross-connect Unit Service Interface Unit STM-1 (Normal Service 1) STM-1 (Normal Service 2) STM-1 (Extra Service) NE 1 NE 2 ODU Antenna IF board Cross-connect Unit Service Interface Unit STM-1 (Normal Service 1) STM-1 (Normal Service 2) STM-1 (Extra Service)
2-108
Issue 02 (2011-01-20)
1. 2. 3.
As shown in Figure 2-54, before the switching, the NE sends and receives normal services on the working channel, and sends and receives extra services on the protection channel. After detecting that the signals on the working channel fail, the IF board notifies the system control and communication unit. As shown in Figure 2-55, the system control and communication unit controls the crossconnect unit to cross-connect the working services to the protection channel. The system control and communication unit also interacts with the NE at the opposite end through byte K to enable the NE at the opposite end to perform synchronous switching. In this case, the extra services that are transmitted on the protection channel are interrupted.
NOTE
The interaction of byte K between NEs in the case of N+1 protection is similar to the 1:N MSP protocol. For details, see 4.2.6.2 1:N Linear MSP.

In the case of N+1 protection for the Integrated IP radio, the switching on the TDM plane is realized based on the automatic bridging of the cross-connect unit and the switching on the packet plane is realized based on the switching of the LAG.
NOTE
This section uses the Integrated IP radio simultaneously transmitting Native TDM services and Native Ethernet services as an example to describe the N+1 protection principle. When the Integrated IP radio transmits PWE3 services, the PWE3 service switching principle is the same as the Native Ethernet service switching principle.
The configuration of the 2+1 protection as described in 2.5.2.2 System Configuration is provided as an example to describe the switching principles of the 2+1 protection. The switching principles for the 1+1, 3+1, and 4+1 protection are the same as the switching principles for the 2+1 protection.
Issue 02 (2011-01-20)
2-109
Figure 2-56 Realization principles of the 2+1 protection (before the switching)
ODU IF board Cross-connect Unit Service Interface unit TDM (Normal Service 1) TDM (Normal Service 2) TDM (Extra Service)
Antenna
ODU
IF board
Ethernet
ODU
IF board NE 1 NE 2
Service Interface unit
ODU
IF board
Cross-connect Unit Service Interface unit TDM (Normal Service 1) TDM (Normal Service 2) TDM (Extra Service)
Antenna
ODU
IF board
Ethernet
ODU
IF board
2-110
Issue 02 (2011-01-20)
Figure 2-57 Realization principles of the 2+1 protection (after the switching)
ODU IF board Cross-connect Unit Service Interface unit TDM (Normal Service 1) TDM (Normal Service 2) TDM (Extra Service)
Antenna
ODU
IF board
Ethernet
ODU
IF board NE 1 NE 2
ODU
IF board
Cross-connect Unit Service Interface unit TDM (Normal Service 1) TDM (Normal Service 2) TDM (Extra Service)
Antenna
ODU
IF board
Ethernet
ODU
IF board
In the case of TDM services, the switching principles of the N+1 protection for the Integrated IP radio are the same as the switching principles of the N+1 protection for the SDH microwave. The switching on the TDM plane is realized based on the automatic bridging of the cross-connect unit. 1. As shown in Figure 2-56, before the switching, the NE sends and receives normal services on the working channel, and sends and receives extra services on the protection channel. After detecting that the signals on a working channel fail, the IF board notifies the system control and communication unit. As shown in Figure 2-57, the system control and communication unit controls the cross-connect unit to cross-connect the working services to the protection channel. The system control and communication unit also interacts with the NE at the opposite end through byte K to enable the NE at the opposite end to perform synchronous switching. In this case, the extra services that are transmitted on the protection channel are interrupted.
2. 3.
In the case of Ethernet services, the N+1 protection for the Integrated IP radio realizes the switching on the packet plane by switching the LAG comprising the IF ports.
Issue 02 (2011-01-20)
2-111
1. 2. 3.
As shown in Figure 2-56, before the switching, the LAG uses the load sharing mode to allocate the service traffic to each link according to the result of the hash algorithm. After detecting that the signals on a working channel fail, the IF board notifies the system control and communication unit. As shown in Figure 2-57, the system control and communication unit control the packet switching unit to allocate the service traffic from the failed link to the other normal links according to the result of the hush algorithm. The system control and communication unit also interacts with the NE at the opposite end through byte K to enable the NE at the opposite end to perform synchronous switching.
NOTE
After an N+1 protection group is created on the U2000, the corresponding LAG comprising the IF ports is automatically created. The default main port of the LAG is the port on the IF board whose slot number is the smallest. For example, in the typical configuration of the 2+1 protection described in 2.5.2.2 System Configuration, the default main port of the LAG is the IF port on the IF board in slot 3.

Follow certain guidelines when you plan N+1 protection.
SDH Microwave
When the OptiX RTN 980 transmits multiple SDH microwave services in a point-to-point manner, you can adopt N+1 protection. Follow these principles when you plan N+1 protection for SDH microwave services. l l l Determine the number of working channels based on transmission capacity. Plan the channels that are in use. It is recommended that you configure ACAP for the channels . Plan the parameters associated with N+1 protection. Set the WTR time to a value from 5 minutes to 12 minutes. It is recommended that you set the value to 10 minutes. It is recommended that you set SD as a switching condition. Use IF1, ISU2, or IFX2 boards to form N+1 protection groups for SDH microwave. These three boards all support N+1 protection for STM-1 microwave. In addition, ISU2 and ISX2 boards support N+1 protection for 2xSTM-1 microwave. In one protection group, the IF boards of the members can be of different types or the same type.
Integrated IP radio
When the OptiX RTN 980 transmits large capacity Ethernet services and E1 services in a pointto-point manner, you can adopt N+1 protection. Follow these principles when you plan N+1 protection for Integrated IP radio services. l l l Determine the number of working channels based on transmission capacity. Plan the channels that are in use. It is recommended that you configure ACAP for the channels . Use IF1, IFU2, ISU2, or IFX2 boards to form N+1 protection groups for Integrated IP radio. These four boards all support Integrated IP radio (Native E1 and Native Ethernet). In addition, ISU2 and ISX2 boards support Integrated IP radio (Native STM-1 and Native
2-112
Ethernet). In one protection group, the IF boards of the members can be of different types or the same type. l l Ensure that the working and protection IF boards use the same parameters, including the IF channel bandwidth, modulation scheme or AM attribute, IF service type and E1 capacity. Plan the parameters associated with N+1 protection. Set the WTR time to a value from 5 minutes to 12 minutes. It is recommended that you set the value to 10 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 of the working links and the protection link and then create the N+1 protection group. Table 2-35 Procedure for configuring an N+1 protection group Step 1 Operation A.2.4 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 major parameters as follows: The parameters need to be set according to the network planning information.
NOTE Configure the same IF information for each working link and the protection link.
Optional. l You can specify the maximum number of E1s that can be transmitted in intermediate modulation schemes, by setting the advanced attributes correspondingly. l Generally, it is recommended that you use the default values. l To ensure that a specific number of E1s can be transmitted in intermediate modulation schemes, adjust the E1 capacity in each modulation scheme according to the network planning information. When a new modulation scheme is adopted, the system transmits only the number of E1 services allowed by the modulation scheme and discards the excess E1 services.
NOTE In the case of the IF boards that are configured with 1+1 protection, only the AM advanced attributes of the main IF board need to be set. NOTE Set the AM advanced attributes of each working link and the protection link to the same values.
Issue 02 (2011-01-20)
2-113
Step 3
Operation A.5.8.2 Configuring the ATPC Attributes
Description Required when the ATPC function needs to be enabled. Set the major parameters as follows: l If the ATPC function needs to be used, set ATPC Enable Status to Enabled. l During site commissioning, set ATPC Enable Status to Disabled. l It is recommended that you set ATPC Upper Threshold (dBm) to the central value plus 10 dB. l It is recommended that you set ATPC Lower Threshold (dBm) to the central value minus 10 dB. l It is recommended that you set ATPC Automatic Threshold Enable Status to Disabled.
NOTE In the case of the IF boards that are configured with 1+1 protection, configure only the ATPC attributes of the main IF board. NOTE Set the ATPC attributes of each working link and the protection link to the same values.
Optional. l To set the maximum transmit power that is supported by the ATPC adjustment function, you need to setMaximum Transmit Power(dBm) according to the actual requirements. 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. Therefore, determine whether to set these parameters according to the actual requirements.
NOTE Set the ODU power attributes of each working link and the protection link to the same values.
A.2.5 Creating an N+1 Protection Group
Required. The parameters need to be set according to the network planning information.
NOTE
During the configuration of microwave services under N+1 protection, take note of the following: l If the microwave services are TDM services, only the TDM services on a working link need to be configured. If extra services need to be transmitted, it is necessary to configure extra services on a protection link. l If the microwave services are Native ETH services and packet services, the services only need to be configured on the Integrated IP radio port of an IF board with the smallest slot ID in an N+1 protection group.

This topic uses an example to describe how to plan and configure the N+1 protection for the Integrated IP radio according to the actual network conditions. The method of configuring the
N+1 protection for the SDH microwave is simpler than the method of configuring the N+1 protection for the Integrated IP radio and hence is not described in this topic. 2.5.9.1 Networking Diagram The topic describes the networking information about the NEs. 2.5.9.2 Service Planning The service planning information contains all the parameter information required for configuring the NE data. 2.5.9.3 Configuration Process This topic describes the procedure for the data configuration.

The topic describes the networking information about the NEs. As shown in Figure 2-58, the service requirements between two sets of OptiX RTN 980 are as follows: l The Integrated IP radio link needs to transmit 32xE1 services and 300 Mbit/s Ethernet services at the same time. The service requirements of user A are 16xE1 services and 100 Mbit/s Ethernet services. The service requirements of user B are 16xE1 services and 100 Mbit/s Ethernet services. The service requirements of user C are 100 Mbit/s Ethernet services. l l The AM function needs to be enabled for each Integrated IP radio link. The protection for the Integrated IP radio links must be provided.

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
User A NE1 16E1+FE(100M) User B 16E1+FE(100M) FE(100M) User C
User A NE2
Tx high Tx low Link ID Tx high station Tx Freq. Tx low station Tx Freq. Channel spacing Channel Type Polarization
16E1+FE(100M)
User B 16E1+FE(100M) FE(100M) User C
Plan the Integrated IP radio links that are configured with the N+1 (N=2) (as shown in Figure 2-58) protection according to the preceding service requirements and the available spectrum resources. NE1 and NE2 adopt the typical configuration of the 2+1 protection, which is described in 2.5.2.2 System Configuration. This example uses the ISU2 board. l The two working channels each transmit 16xE1 services whereas the protection channel does not transmit any E1 services.
Issue 02 (2011-01-20)
The three channels (including the working and protection channels) each transmit 100 Mbit/ s Ethernet services in load sharing mode. In this case, when a channel is faulty, the other normal channels can still provide the required bandwidth for the Ethernet services.

Basic Information About Radio Links

According to the spectrum allocation on the microwave network and the required radio transmission capacity, you can obtain the basic information about the radio links, as provided in Table 2-36. Table 2-36 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) IF Channel Bandwidth (MHz) RF configuration mode Polarization direction Link 1 (Working Link 1) 101 NE1 NE2 14935 14515 420 28 N+1 (N=2) V (vertical polarization) H (horizontal polarization) V (vertical polarization) Link 2 (Protection Link) 102 NE1 NE2 14963 14543 420 28 Link 3 (Working Link 2) 103 NE1 NE2 14991 14571 420 28
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.
Information About the Hybrid/AM Configuration

According to the capacity of E1 services and Ethernet services and the availability requirement, you can calculate the information about the Hybrid/AM attributes, as provided in Table 2-37.
2-116
Issue 02 (2011-01-20)
Table 2-37 Information about the Hybrid/AM Configuration Parameter IF Service Type Number of E1 services Capacity of Ethernet services (Mbit/s) Enable AM AM guaranteed capacity mode AM full capacity mode Enable E1 priority Link 1 (Working Link 1) Hybrid(Naive E1+ETH) 16 100 Enabled QPSK 256QAM Disabled Link 2 (Protection Link) Hybrid(Naive E1+ETH) 16 a 100 Enabled QPSK 256QAM Disabled Link 3 (Working Link 2) Hybrid(Naive E1+ETH) 16 100 Enabled QPSK 256QAM Disabled
NOTE
l In the case of the Integrated IP radio N+1 protection, set the number of E1s on the protection link the same as the number of E1s on the working link when you configure Hybrid/AM attributes, regardless of whether the protection link carries extra TDM traffic. l In the case of the Integrated IP radio N+1 protection, do not configure TDM service cross-connections if the protection link does not carry extra TDM traffic.
Information About the Power and ATPC

By using the microwave network planning software such as the Pathloss, you can analyze and compute the parameters of radio links and thus obtain the information about the power and ATPC of the radio links, as provided in Table 2-38. Table 2-38 Information about the power and ATPC Parameter Transmit power (dBm) Link 1 (Working Link 1) 16.5 (NE1) 16.5 (NE2) Power to be received (dBm) ATPC enabling ATPC automatic threshold enabling ATPC Upper threshold (dBm)
Issue 02 (2011-01-20)
Link 2 (Protection Link) 16.5 (NE1) 16.5 (NE2) -46 (NE1) -46 (NE2) Disabled -
Link 3 (Working Link 2) 16.5 (NE1) 16.5 (NE2) -46 (NE1) -46 (NE2) Disabled -
-46 (NE1) -46 (NE2) Disabled -
2-117
Parameter ATPC Lower threshold (dBm)
Link 1 (Working Link 1) -
Link 2 (Protection Link) -
Link 3 (Working Link 2) -
NOTE
l The transmit power is calculated in AM guaranteed capacity mode. l The receive power is calculated in AM guaranteed capacity mode. l In this example, the ATPC function is disabled.
Information About the N+1 Protection

NE1 and NE2 adopt the typical configuration of the 2+1 protection, which is described in 2.5.2.2 System Configuration. According to the microwave type, slot priorities of IF boards, and configuration rules of the N+1 protection, you can obtain the information about the N+1 protection, as provided in Table 2-39. Table 2-39 Information about the N+1 (N=2) protection Parameter Work Unit NE1 3-ISU2 5-ISU2 Protection Unit WTR time(s) 6-ISU2 600 (default value) NE2 3-ISU2 5-ISU2 6-ISU2 600 (default value)

Procedure
Step 1 See A.2.4 Configuring the IF/ODU Information of a Radio Link and configure the IF/ODU information about the radio links. l The values for the relevant parameters of NE1 are provided as follows. Parameter Value Range 3-ISU2 and 53ODU IF Channel Bandwidth AM Enable Status
2-118
5-ISU2 and 55ODU 28M Enabled
6-ISU2 and 56ODU 28M Enabled

Issue 02 (2011-01-20)
28M Enabled
Parameter
Value Range 3-ISU2 and 53ODU 5-ISU2 and 55ODU QPSK 6-ISU2 and 56ODU QPSK
Modulation Mode of the Guarantee AM Capacity Modulation Mode of the Full AM Capacity Enable E1 Priority Guarantee E1 Capacity Link ID TX Frequency (MHz) T/R Spacing(MHz) TX Power(dBm) TX Status Power to Be Received(dBm)
QPSK
256QAM
256QAM
256QAM
Disabled 16 101 14935 420 16.5 unmute -46
Disabled 16 103 14991 420 16.5 unmute -46
Disabled 16 102 14963 420 16.5 unmute -46
l The values for the relevant parameters of NE2 are provided as follows. Parameter Value Range 3-ISU2 and 53ODU IF Channel Bandwidth AM Enable Status Modulation Mode of the Guarantee AM Capacity Modulation Mode of the Full AM Capacity Enable E1 Priority Guarantee E1 Capacity 28M Enabled QPSK 5-ISU2 and 55ODU 28M Enabled QPSK 6-ISU2 and 56ODU 28M Enabled QPSK
256QAM
256QAM
256QAM
Disabled 16
Disabled 16
Disabled 16
Issue 02 (2011-01-20)
2-119
Parameter
Value Range 3-ISU2 and 53ODU 5-ISU2 and 55ODU 103 14571 420 16.5 unmute -46 6-ISU2 and 56ODU 102 14543 420 16.5 unmute -46
Link ID TX Frequency (MHz) T/R Spacing(MHz) TX Power(dBm) TX Status Power to Be Received(dBm)
101 14515 420 16.5 unmute -46
Step 2 A.5.8.2 Configuring the ATPC Attributes. The parameters for configuring the ATPC for the links of NE1 and NE2 need to be set to the same values, as provided in the following table. Parameter Value Range 3-ISU2 ATPC Enable Status Disabled 5-ISU2 Disabled 6-ISU2 Disabled
Step 3 See A.2.5 Creating an N+1 Protection Group and configure the N+1 protection. The parameters for configuring the N+1 protection are set to the same values for NE1 and NE2, as provided in the following table. Parameter WTR time(s) Enabled Select Mapping Direction Select Mapping Way Value Range 600 Enabled Work Unit 3-ISU2-1 5-ISU2-1 Select Mapping Direction Select Mapping Way Protection Unit 6-ISU2-1
----End
2-120
Issue 02 (2011-01-20)

This topic provides the hyperlinks of the operation tasks regarding the N+1 protection feature.
Related Tasks
A.2.5 Creating an N+1 Protection Group A.2.7 Querying the IF N+1 Protection Status A.2.9 IF N+1 Protection Switching A.2.10 Starting/Stopping the N+1 Protection Protocol A.11.6.2 Testing the N+1 Protection Switching
2.5.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 This performance event indicates that the N+1 protection switching occurs.
2.5.12 FAQs
This topic 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
Issue 02 (2011-01-20)
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 l l l l l l 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 l l The radio work mode of the IF board is not configured. In the case of the SDH microwave, the radio work mode of the IF board is not the STM-1 mode. The service modes of ISU2 or ISX2 boards in an N+1 protection group are inconsistent. The microwave interface attributes or licensed capacities of IF boards are inconsistent.
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.
2.6 Automatic Transmit Power Control

The automatic transmit power control (ATPC) function is an important function of a radio transmission system. The ATPC function reduces the interference of a transmitter to adjacent systems and also reduces the residual bit error rate.
2-122
Issue 02 (2011-01-20)
2.6.1 Introduction This section provides the definition of ATPC and describes its purpose. 2.6.2 Specifications This section describes the specifications of ATPC. 2.6.3 Availability This section describes the support required by the application of the ATPC feature and its dependency. 2.6.4 Principles The ATPC function is implemented through the ATPC overhead in the microwave frame. 2.6.5 Planning Guidelines Follow certain guidelines when you plan ATPC. 2.6.6 Configuration Procedure When configuring the ATPC, you need to set the ATPC parameters and the parameters of the IF boards and ODUs according to the actual requirements. 2.6.7 Configuration Example This topic uses an example to describe how to plan and configure the ATPC according to the conditions of the network. 2.6.8 Task Collection This topic provides the hyperlinks of the operation tasks regarding the ATPC feature. 2.6.9 Relevant Alarms and Events When the ATPC adjustment occurs, the IF board reports the relevant performance events. 2.6.10 FAQs This topic describes the answers to the questions that are frequently raised when the ATPC feature is used.
2.6.1 Introduction
This section provides the definition of ATPC and describes its purpose.
Definition
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 2-59.
NOTE
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. 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 maximum transmit power of the ODU is not set, the transmit power of the ODU can increase at most to the rated maximum transmit power of the ODU.
Issue 02 (2011-01-20)
2-123
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 2-59.
Figure 2-59 Relationship between the RSL and TSL

TSL/RSL
TSL
Up-fading Central value of the ATPC upper threshold and the ATPC lower threshold 2 dB RSL 2 dB Down-fading
Purpose
The ATPC technology enables a transmitter to automatically change its output power within the ATPC control range based on the change in the RSL of a receiver. In this way, the RSL of the receiver remains in a fixed range, and the interference with the neighboring system and the residual error rate are reduced.
This section describes the specifications of ATPC. Table 2-40 lists the specifications of ATPC. Table 2-40 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
2-124
Issue 02 (2011-01-20)
Item ATPC adjustment step
Specifications 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 is 10 dB at a time. > 30 dB/s Supported
ATPC adjustment speed Maximum transmit power of ODUs
2.6.3 Availability
This section describes the support required by the application of the ATPC feature and its dependency.

Table 2-41 Hardware and version support Feature ATPC Applicable Board IF1 IFU2 IFX2 ISU2 ISX2 Applicable Hardware Version All the versions All the versions All the versions All the versions All the versions Applicable Product Version V100R003C00 and later V100R003C00 and later V100R003C00 and later V100R003C00 and later V100R003C00 and later
The dependencies between the ATPC feature and other features are as follows: 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 workgroup. 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.
2.6.4 Principles
The ATPC function is implemented through the ATPC overhead in the microwave frame.
Figure 2-60 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) ...........
The realization principle is as follows: 1. 2. The receiver detects the RSL. When the ATPC function is enabled, and 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.
2-126
Issue 02 (2011-01-20)

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. Follow certain guidelines when you plan ATPC parameters: l 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. If no requirements are specified for the RSL after the ATPC function is enabled, it is recommended that you don't use the automatic ATPC thresholds.

When configuring the ATPC, you need to set the ATPC parameters and the parameters of the IF boards and ODUs according to the actual requirements. Table 2-42 Procedure for configuring the ATPC Step 1 Operation A.5.8.2 Configuring the ATPC Attributes Description Required. l If the ATPC function needs to be used, set ATPC Enable Status to Enabled. l During site commissioning, set ATPC Enable Status to Disabled. l It is recommended that you set ATPC Upper Threshold (dBm) to the central value plus 10 dB. l It is recommended that you set ATPC Lower Threshold (dBm) to the central value minus 10 dB. l It is recommended that you set ATPC Automatic Threshold Enable Status to Disabled.
Issue 02 (2011-01-20)
2-127
Step 2
Operation A.5.9.3 Setting the Power Attributes of the ODU
Description Optional. l To set the maximum transmit power that is supported by the ATPC adjustment function, you need to set Maximum Transmit Power(dBm) according to the actual requirements. l TX High Threshold(dBm), TX Low Threshold(dBm), RX High Threshold(dBm), and RX Low Threshold(dBm) affect ATPC performance events. Set these parameters if necessary.

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

This topic describes the networking information about the NEs. As shown in Figure 2-61, the ATPC function needs to be enabled for the radio link between the two sets of OptiX RTN 980. With this function, the RSL at both ends of a radio link can be always about -46 dBm, and the transmit power of the ODU will not exceed 20 dBm. Figure 2-61 Networking diagram
3-ISU2-1(to NE2) 3-ISU2-1(to NE1)
1+0 NE1 NE2

The service planning information contains all the parameter information required for configuring the NE data. Table 2-43 lists the ATPC planning information that aligns with service requirements.
Table 2-43 ATPC information Parameter NE1 3-ISU2-1 & 53-ODU ATPC Enable Status Middle RSL Value (dBm) Maximum Transmit Power of an ODU (dBm) Enabled -46.0 20 NE2 3-ISU2-1 & 53-ODU Enabled -46.0 20

Procedure
Step 1 See A.5.8.2 Configuring the ATPC Attributes. l The values for the relevant parameters of NE1 are provided as follows. Parameter Value Range 3-ISU2 ATPC Enable Status ATPC Upper Threshold(dBm) ATPC Lower Threshold(dBm) ATPC Automatic Threshold Enable Status Enabled -36.0 -56.0 Disabled
l The values for the relevant parameters of NE2 are provided as follows. Parameter Value Range 3-ISU2 ATPC Enable Status ATPC Upper Threshold(dBm) ATPC Lower Threshold(dBm) ATPC Automatic Threshold Enable Status Enabled -36.0 -56.0 Disabled
Step 2 See A.5.9.3 Setting the Power Attributes of the ODU l The values for the relevant parameters of NE1 are provided as follows.
Parameter
Value 53-ODU
Maximum Transmit Power(dBm)
20
l The values for the relevant parameters of NE2 are provided as follows. Parameter Value 53-ODU Maximum Transmit Power(dBm) 20
----End

This topic provides the hyperlinks of the operation tasks regarding the ATPC feature.
Related Tasks
A.5.8.2 Configuring the ATPC Attributes A.5.9.3 Setting the Power Attributes of the ODU A.5.8.5 Querying the 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.
2.6.10 FAQs
This topic describes the answers to the questions that are frequently raised when the ATPC feature 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:
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.
The transmit power reaches the threshold of the ATPC control range, and cannot be increased or decreased.
2.7 Adaptive Modulation

The main feature of the Integrated IP radio is the adaptive modulation (AM) function. 2.7.1 Introduction This section provides the definition of AM and describes its purpose. 2.7.2 Basic Concepts This section describes the basic concepts that you need to be familiar with before you use the AM feature. 2.7.3 Specifications This section describes the specifications of AM. 2.7.4 Availability This section describes the support and dependency that AM requires. 2.7.5 Principles The AM function is implemented mainly through the AM engine in the Modem unit of the IF board. 2.7.6 Planning Guidelines Follow certain guidelines when you plan AM. 2.7.7 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. 2.7.8 Configuration Example This topic uses an example to describe how to plan and configure the AM according to the conditions of the network. 2.7.9 Task Collection This topic provides the hyperlinks of the operation tasks regarding the AM feature. 2.7.10 Relevant Alarms and Events When the AM switching occurs, the IF board reports the relevant alarms and performance events. 2.7.11 FAQs This topic describes the answers to the questions that are frequently raised when the AM feature is used.
2.7.1 Introduction
This section provides the definition of AM and describes its purpose.
Issue 02 (2011-01-20)
2-131
Definition
The AM function helps to adjust the modulation mode according to the quality of channels. When the AM technology is adopted, in the case of the same channel spacing, the microwave service bandwidth varies according to the modulation mode. The higher the modulation efficiency, the higher the bandwidth of the transmitted services. l When the channel quality is good (such as on days when weather conditions are favorable), the equipment adopts a high-efficiency modulation mode to transmit more user services. In this manner, the transmission efficiency and the spectrum utilization of the system are improved. When the channel quality is degraded (such as on days when there is a storm or fog), the equipment adopts a low-efficiency mode to transmit only the services with a high-efficiency priority within the available bandwidth and to discard the services with a lower priority. In this manner, the anti-interference capability of the radio link is improved and the link availability of the services with a high-efficiency priority is ensured.
The Integrated IP radio equipment supports the AM technology, in which the priorities of E1 services and packet services can be set. With the AM technology adopted, service transmission is controlled based on the service bandwidth and QoS policy corresponding to the current modulation scheme. The service with the highest priority is transmitted with preference.
NOTE
When the Hybrid microwave equipment transmits STM-1 services and packet services at the same time, STM-1 services have the highest priority and their transmission is guaranteed.
Priorities of E1 services The priorities of E1 services are assigned based on the number of E1 services that each modulation mode can transmit. When a shift between modulation modes occurs, only the E1 services whose number is specified in the new modulation mode can be transmitted and the excess E1 services are discarded.
Packet service priority Through the QoS technology, packet services are scheduled to queues with different priorities. Then, the services in different queues are transmitted to the microwave port after computation of the SP or WRR algorithm. When a shift between modulation modes occurs, certain queues may be congested due to insufficient capacity at the air interface. In this case, certain services or all the services in these queues are discarded.
Figure 2-62 shows the change in services brought by the AM technology. The orange part indicates E1 services. The blue part indicates Packet services. The closer to the edge, the lower the service priority. Under all channel conditions, the service capacity varies according to the modulation mode. When the channel is in bad conditions, the service with a lower priority is discarded.
2-132
Issue 02 (2011-01-20)
Figure 2-62 Adaptive modulation
256QAM 128QAM 64QAM 32QAM 16QAM
QPSK Channel Capability 16QAM 32QAM 64QAM 128QAM E1 Services Ethernet Services 256QAM
Purpose
After a radio link adopts the AM technology, the availability of links for services with higher priorities is ensured and the bandwidth utilization is improved.

This section describes the basic concepts that you need to be familiar with before you use the AM feature. 2.7.2.1 E1 Service Priority The OptiX RTN 980 allows the setting of priorities for native E1 services over Integrated IP radio (Native E1 and Native Ethernet) and discards the native E1 services with low priorities in guarantee capacity modulation mode. 2.7.2.2 Priorities of Ethernet Services The OptiX RTN 980 supports the scheduling of Ethernet services with different priorities through QoS. Ethernet services supported by the equipment are Native Ethernet services and PWE3 services.
2.7.2.1 E1 Service Priority

The OptiX RTN 980 allows the setting of priorities for native E1 services over Integrated IP radio (Native E1 and Native Ethernet) and discards the native E1 services with low priorities in guarantee capacity modulation mode.
NOTE
Native STM-1 services transmitted over Integrated IP radio (Native STM-1 and Native Ethernet) always have the highest priority, and therefore cannot be discarded in any modulation mode.
Application Scenario
The conventional Hybrid radio assumes that all native E1 services are high-priority services, such as voice services. Therefore, no E1 services can be impaired when the AM mode is downshifted. This assumption, however, does not apply to the Hybrid radio that transmits IMA E1 services. An IMA E1 group includes high-priority services such as voice services and lowpriority services such as webpage browsing services. Therefore, when the AM mode is downshifted, high-priority services are not impaired if the IMA group bandwidth in the lower order modulation mode is higher than the bandwidth requirement of high-priority services. For this purpose, E1 service priorities are introduced. By default, after E1 service priorities are used, different types of services can occupy the IMA group bandwidth in a descending order of priorities: high-priority E1 services and high-priority Ethernet services > low-priority E1 services > low-priority Ethernet services. To be specific, one type can occupy the IMA group bandwidth only after its preceding type is satisfied. In this manner, the requirement for E1 guarantee capacity decreases and a lower order modulation mode can meet this requirement, improving the link availability. Figure 2-63 shows an example of the priorities of E1 services. In this radio transmission network: l l l l The Hybrid radio uses a channel spacing of 7MHz. The R99 base station transmits an IMA group of 7xE1 services. The R4 base station transmits FE services. Table 2-44 lists the priorities of base station services. Table 2-44 Priorities of services at base stations BTS Type R99 Service Priority High-priority service Low-priority service R4 High-priority service Low-priority service Service Bandwidth 4 Mbit/s 10 Mbit/s 4 Mbit/s 10 Mbit/s
Figure 2-63 Applications of E1 Service Priority

Hybrid radio IMA R99 NodeB FE FE RNC IMA
R4 NodeB
2-134
Issue 02 (2011-01-20)
In the case of the Hybrid radio: l If the E1 service priorities are not set The guarantee capacity is higher than 18 Mbit/s (including all E1 services on R99 and the high-priority Ethernet services on R4). The corresponding modulation mode is 16QAM. l If E1 service priorities are set The guarantee capacity is higher than 8 Mbit/s (including the high-priority E1 services on R99 and the high-priority Ethernet services on R4). The corresponding modulation mode is QPSK. The comparison indicates that the setting of E1 service priorities lowers the guarantee capacity and the corresponding modulation mode, thus improving the link availability.
Features
On the OptiX RTN 980, the setting of E1 service priorities have the following features: l E1 service priorities can be set to either High or Low. The transmission of high-priority E1 services is guaranteed in any modulation mode. The transmission of low-priority E1 services is guaranteed only in full-capacity modulation mode. l l The attributes of E1 service priorities are achieved on IF boards, but the configuration of E1 service priorities is achieved through cross-connections. On the OptiX RTN 980, you can set the number of E1 services that are guaranteed in medium modulation mode. However, you cannot specify which low-priority E1 services are discarded and which are not discarded in this modulation mode. By default, on the OptiX RTN 980, the E1 guarantee capacity subtracted from the guarantee capacity is the bandwidth available for high-priority Ethernet services. In other modulation modes, the Ethernet service bandwidth cannot be lower than this value. Hence the formula: E1 service bandwidth in full capacity mode Service bandwidth in full capacity mode - Service bandwidth in guarantee capacity mode + E1 service bandwidth in guarantee capacity mode. In addition, the number of E1 services in full capacity modulation mode should be smaller than or equal to the maximum number of E1 services in full capacity modulation mode. For example, on the Figure 2-63, the guarantee capacity modulation mode is QPSK (corresponding to a service capacity of 10 Mbit/s) and the full capacity modulation mode is 64QAM (corresponding to a service capacity of 32 Mbit/s). The number of E1 services in guarantee capacity modulation mode is 2 (corresponding to a service capacity of 4 Mbit/ s), so the maximum number of E1 services in full capacity modulation mode is (32 - 10 + 4)/2 = 13.
2.7.2.2 Priorities of Ethernet Services

The OptiX RTN 980 supports the scheduling of Ethernet services with different priorities through QoS. Ethernet services supported by the equipment are Native Ethernet services and PWE3 services. When the AM is enabled on an IF board, the Ethernet services with different priorities can be scheduled as follows:
l l
The IF board notifies the packet switching unit of the Ethernet bandwidth supported by the Integrated IP radio. According to the Ethernet bandwidth and the configured queue scheduling mode, the packet switching unit schedules the Ethernet services that are transmitted to the IF board.
When the Ethernet bandwidth decreases due to an AM shift, the packet switching unit schedules the Ethernet services according to the decreased bandwidth and the QoS configuration. In this manner, the high-priority Ethernet services can be scheduled successfully whereas the lowpriority Ethernet services are discarded.
This section describes the specifications of AM. Table 2-45 lists the specifications of AM. Table 2-45 Specifications of AM Item Supported microwave types Specifications Integrated IP radio (Native E1 and Native Ethernet) Integrated IP radio (Native STM-1 and Native Ethernet) Lowest-efficiency modulation modea Highest-efficiency modulation modea Impact of mode switching QPSK/16QAM/32QAM/ 64QAM/128QAM/256QAM QPSK/16QAM/32QAM/ 64QAM/128QAM/256QAM When mode switching occurs, the transmit frequency, receive frequency, and channel spacing are not changed. When the AM scheme is downshifted, high-priority services will not be affected due to the mode switching when the low-priority services are discarded. Switching mode Switching speed Step by step Meeting the requirement of the fast fading at a speed of 100 dB/s. Supported microwave types Supported priority levels Integrated IP radio (Native E1 and Native Ethernet) Two levels
E1 priority
2-136
Issue 02 (2011-01-20)

NOTE
a: Since an Integrated IP radio (Native STM-1 and Native Ethernet) needs to transmit at least one STM-1, the AM function supports modulation modes as follows: l Supports 128QAM or 256QAM when the channel spacing is 28 MHz. l Supports 64QAM, 128QAM, or 256QAM when the channel spacing is 40 MHz. l Supports 16QAM, 32QAM, 64QAM, 128QAM, or 256QAM when the channel spacing is 56 MHz.
2.7.4 Availability
This section describes the support and dependency that AM requires.
Hardware and Version support

Table 2-46 Hardware and version support Feature AM Applicable Board IFU2 IFX2 ISU2 ISX2 E1 priority IFU2 IFX2 ISU2 ISX2 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 V100R003C00 and later V100R003C00 and later V100R003C00 and later V100R003C00 and later V100R003C00 and later V100R003C00 and later V100R003C00 and later V100R003C00 and later
NOTE
The co-existence of N+1 protection and E1 priority is applicable to V100R003C00 and a later version.
The dependencies between the AM feature and other features are as follows: l l l Enable the AM function before enabling the priorities of E1 services. The AM function can work with the 1+1 protection. The AM function can work with the N+1 protection. In this case, the AM parameters (AM enabling, modulation mode of the guaranteed AM capacity, modulation mode of the full
Issue 02 (2011-01-20)
AM capacity) must be set to the same. When the AM function is used with N+1 protection, the members must be enabled or disabled with E1 priority simultaneously. When the E1 priority is enabled, the maximum E1 capacity must be set to the same value. l The AM function can work with the XPIC function. In this case, the AM parameters (AM enabling, modulation mode of the guaranteed AM capacity, modulation mode of the full AM capacity) must be set to the same. An IF port that supports the AM feature can be configured into a LAG for air interfaces. The AM attribute and E1 priority must be set to the same values for the two IF ports in a LAG. When the AM feature is enabled, it is recommended that you configure QoS for Ethernet services transmitted over Integrated IP radio. After QoS is configured, the available bandwidth can be first allocated to transmit Ethernet services with higher priorities when the radio link works in a low-efficiency modulation mode.
2.7.5 Principles
The AM function is implemented mainly through the AM engine in the Modem unit of the IF board.
AM Working Principle (Before the Switching)

1. 2. 3. The service is scheduled to the IF port 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. 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 current modulation mode, the quality of the received signal is considered degraded if the value of the received SNR is lower than the preset threshold; the quality of the receive signal is considered good if the value of the received SNR is higher than the preset threshold. Then, the Rx path transmits a signal indicating the quality of the received signal to the AM engine. After being placed into the overhead of the microwave frame by the AM engine at the opposite end, the switching indication signal is then transmitted to the local end over the Tx path. 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 instruct the MUX unit and the air interface to change the modulation mode, as shown in Figure 2-64.
4.
5. 6.
2-138
Issue 02 (2011-01-20)
Figure 2-64 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 a Downshift)

1. When detecting the SNR threshold-crossing that triggers a downshift of modulation modes, the IF unit instructs the opposite end to perform a modulation mode switchover. At the opposite end, the lower-priority E1 services and Ethernet services are discarded based on the number of E1 services specified in the lower-efficiency modulation mode and the bandwidth of the microwave frame; the higher-priority Ethernet services and the E1 services whose number is specified in the lower-efficiency modulation mode are scheduled to the IF port. Therefore, the bandwidth of the microwave frame decreases, as shown in Figure 2-65.
Issue 02 (2011-01-20)
2-139
Figure 2-65 AM downshift (after the switching)
MUX unit
Microwave frame
IF Module
Tx Path
IF Module
Microwave frame
MUX unit
SNR
AM Messages
Microwave frame
Microwave frame
MUX unit
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 change in the receive mode of the current frame to the MUX unit when detecting the change in the modulation mode. The MUX unit then can receive and process service signals in the new modulation mode. In the lowest-efficiency modulation mode, the Integrated IP radio equipment ensures the transmission of E1 services with a guaranteed capacity and the higher-priority Ethernet services supported by the available bandwidth.
3.
AM Working Principle (After an Upshift)

1. When detecting the SNR threshold-crossing that triggers an upshift of modulation modes, the IF unit instructs the opposite end to perform a modulation mode switchover. Therefore, the bandwidth of the microwave frame increases, and the additional bandwidth can transmit more E1 services or Ethernet services. See Figure 2-66.
2-140
Issue 02 (2011-01-20)
Figure 2-66 AM upshift (after the switching)
MUX unit
Microwave frame
IF Module
Tx Path
IF Module
Microwave frame
MUX unit
SNR
AM Messages
Microwave frame
Microwave frame
MUX unit
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 change in the receive mode of the current frame to the MUX unit when detecting the change in the modulation mode. The MUX unit then can receive and process service signals in the new modulation mode. In the highest-efficiency modulation mode, the Integrated IP radio equipment ensures the transmission of E1 services with a full capacity and the higher-priority Ethernet services supported by the available bandwidth.
3.

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

l If TDM services and Ethernet services both need to meet the same availability requirement, it is recommended that you 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 specified availability requirement (that is, a part of bandwidth can be lost when Ethernet signals degrade), it is recommended that you enable the AM function. If E1 services and Ethernet services need not meet the specified availability requirement (that is, a part of bandwidth can be lost when E1 signals and Ethernet signals degrade), it is recommended that you enable the AM function. In addition, you need to set the number of supported E1s in each modulation mode according to the availability requirement and the capacity of E1 services.
Issue 02 (2011-01-20)
Planning Guidelines on AM Attributes

l Determine the highest-efficiency and lowest-efficiency modulation modes based on service types, service priorities, service capacities, service bandwidths, microwave frequencies, and channel bandwidths. Calculate the availability in each modulation mode by using the network planning documents. Ensure that the availability in each modulation mode meets the requirements of users. Calculate the possibility of the working time in each modulation mode.
Planning Guidelines on E1 Priority

l l l When Hybrid microwave transmits IMA services, E1 priority can be enabled. The E1 priority is enabled, the guaranteed E1 capacity must be more than the required E1 capacity. Full E1 service bandwidth Full service bandwidth - Guaranteed service bandwidth + Guaranteed E1 service bandwidth

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 2-47 Configuration procedure of AM Step 1 Operation A.5.8.6 Modifying the Hybrid/ AM Attributes Description Required. Configure the AM function, E1 priority, and the information related to the IF board and the ODU. The parameters need to be set according to network planning. l Set AM Enable Status to Enabled. l Set Guarantee E1 Capacity according to the network planning. For Packet radio, set Guarantee E1 Capacity to 0. l If the E1 priority function is enabled, set Enable E1 Priority to Enabled, and set Full E1 Capacity according to network planning.
CAUTION If Manually Specified Modulation Mode is higher than the planned guaranteed capacity mode, enable the AM function after setting Manually Specified Modulation Mode to the guaranteed capacity modulation mode and the setting takes effect.
2-142
Issue 02 (2011-01-20)
Step 2
Description Optional. l You can specify the maximum number of E1s that can be transmitted in intermediate modulation schemes, by setting the advanced attributes correspondingly. l Generally, it is recommended that you use the default values. l To ensure that a specific number of E1s can be transmitted in intermediate modulation schemes, adjust the E1 capacity in each modulation scheme according to the network planning information. When a new modulation scheme is adopted, the system transmits only the number of E1 services allowed by the modulation scheme and discards the excess E1 services.
Testing AM
Perform this operation to test whether the service data is configured correctly.
NOTE
When the radio link on which the AM function is enabled is configured with the E1 priority, note the following: l If the cross-connection is configured for a point-to-point service, the E1 priority is configured when the cross-connection is created. l If the cross-connection is configured for an SNCP service, the E1 priority is modified after the crossconnection is created. l If the service priority is not configured when the cross-connection is created (that is, E1 Priority is set to None), E1 Priority of each service must be set to a specific value after the cross-connection is configured.

This topic uses an example to describe how to plan and configure the AM according to the conditions of the network. 2.7.8.1 Networking Diagram This topic describes the networking information about the NEs. 2.7.8.2 Service Planning The service planning information contains all the parameter information required for configuring the NE data. 2.7.8.3 Configuration Process This topic describes the procedure for the data configuration.

This topic describes the networking information about the NEs.
Issue 02 (2011-01-20)
2-143
To balance link availability with service bandwidth, the AM function and E1 priority function need to be enabled for the radio link between NE1 and NE2. See Figure 2-67. The modulation mode of the link is originally 128QAM. Figure 2-67 Networking diagram of the AM
3-ISU2-1(to NE2) 3-ISU2-1(to NE1)
1+0 NE1 NE2
Modulation Mode of the Guarantee Capacity:QPSK Modulation Mode of the Full Capacity:128QAM Guarantee E1 Capacity:1 Full E1 Capacity:4

The service planning information contains all the parameter information required for configuring the NE data. Table 2-48 lists the AM and E1 priority planning information that aligns with service requirements. Table 2-48 AM and E1 priority planning information Parameter NE1 3-ISU2 AM Enable Status Modulation Mode of the Guarantee AM Capacity Modulation Mode of the Full AM Capacity Guaranteed E1 Capacity Enable E1 Priority Full E1 Capacity Enabled QPSK 128QAM 1 Enabled 4 NE2 3-ISU2 Enabled QPSK 128QAM 1 Enabled 4

2-144
Issue 02 (2011-01-20)
Procedure
Step 1 See A.2.4 Configuring the IF/ODU Information of a Radio Link. l The values for the relevant parameters of NE1 are provided as follows. Parameter Value NE1 3-ISU2 AM Enable Status Modulation Mode of the Guarantee AM Capacity Modulation Mode of the Full AM Capacity Guarantee E1 Capacity Enable E1 Priority Full E1 Capacity Enable QPSK 128QAM 1 Enable 4
l The values for the relevant parameters of NE2 are provided as follows. Parameter Value NE2 3-ISU2 AM Enable Status Modulation Mode of the Guarantee AM Capacity Modulation Mode of the Full AM Capacity Guarantee E1 Capacity Enable E1 Priority Full E1 Capacity Enable QPSK 128QAM 1 Enable 4
NOTE
Since the original modulation mode is lower than the planned guaranteed capacity modulation mode, set Manually Specified Modulation Mode to QSPK and click Apply. Then, set the parameters as listed in the table.
----End
Issue 02 (2011-01-20)
2-145

This topic provides the hyperlinks of the operation tasks regarding the AM feature.
Related Tasks
A.5.8.6 Modifying the Hybrid/AM Attributes A.5.8.4 Querying the AM Status A.5.8.3 Setting Advanced AM Attributes A.4.3 Modifying the Priorities of E1 Services A.11.5.1 Testing the AM Switching by Using a BER Tester A.11.5.2 Testing the AM Switching Without a BER Tester

When the AM switching occurs, the IF board reports the relevant alarms and performance events.
Relevant Alarms
l AM_DOWNSHIFT The AM_DOWNSHIFT indicates an AM downshift. This alarm is reported when a downshift of modulation modes occurs. l MW_CFG_MISMATCH The MW_CFG_MISMATCH indicates a configuration mismatch of a radio link. This alarm occurs when an NE detects configuration mismatch on both ends of a radio link. For example, the number of E1 signals, the number of STM-1 signals, AM enabling, 1588 overhead enabling, modulation mode may be configured differently on both ends of a radio link. l MW_E1_LOST The MW_E1_LOST indicates E1 lost. This alarm occurs when the AM downshifts the modulation scheme or the E1 bandwidth decreases in the current modulation scheme.

l l l l l l QPSKWS The QPSKWS indicates the working second in the QPSK modulation mode. QAMWS16 The QAMWS16 indicates the working second in the 16QAM modulation mode. QAMWS32 The QAMWS32 indicates the working second in the 32QAM modulation mode. QAMWS64 The QAMWS64 indicates the working second in the 64QAM modulation mode. QAMWS128 The 128QAMWS indicates the working second in the 128QAM modulation mode. QAMWS256 The QAMWS256 indicates the working second in the 256QAM modulation mode.
2.7.11 FAQs
This topic describes the answers to the questions that are frequently raised when the AM feature is used. Q: What is the method of handling the failure of the AM switching? A: The possible symptoms of a modulation scheme 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 scheme. 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.
Issue 02 (2011-01-20)
2-147
3 1+1 Protection for the Control, Switching, and Timing Board
1+1 Protection for the Control, Switching, and Timing Board
About This Chapter

When two control, switching, and timing boards are configured for 1+1 protection, 1+1 hot backup is implemented between the system control units, the switching units, and the timing units. 3.1 Introduction This section provides the definition of 1+1 protection for the control, switching, and timing board and describes its purpose. 3.2 Basic Concepts This section describes the basic concepts associated with 1+1 protection for the control, switching, and timing board. 3.3 Specifications This section describes the specifications for 1+1 protection for the control, switching, and timing board. 3.4 Availability This section describes the specifications for 1+1 protection for the control, switching, and timing board. 3.5 Principles The switching between active and standby control, switching, and timing boards involves the entire board, including the system control unit, cross-connet unit/switching unit, and timing unit. 3.6 Planning Principles OptiX RTN 980The OptiX RTN 980 is mainly used as a high-capacity Nodal. It is recommended that you configure two control, switching, and timing boards on the OptiX RTN 980 to improve equipment reliability. 3.7 Configuration Procedure When two control, switching, and timing boards are installed, they are automatically configured into 1+1 protection, and therefore no manual operation is required. 3.8 Task Collection This section provides the hyperlinks of the operation tasks associated with the feature.
3.9 Relevant Alarms and Events When the control, switching, and timing boards 1+1 protection switching occurs, the system reports the corresponding abnormal event. 3.10 FAQs This section provides the answers to the questions that are frequently raised when 1+1 backup between active and standby control, switching, and timing boards is used.
3-2
Issue 02 (2011-01-20)
3.1 Introduction
This section provides the definition of 1+1 protection for the control, switching, and timing board and describes its purpose.
Definition
1+1 backup between active and standby control, switching, and timing boards is a hot standby mechanism at the equipment level. The two control, switching, and timing boards are configured to provide 1+1 protection for the system control units, timeslot cross-connect units, packet switching units, and timing units.
NOTE
l The control, switching, and timing board of the OptiX RTN 980 is the CSHN board. The CSHN board has the system control unit, timeslot cross-connect unit, packet switching unit, and timing unit. In addition, it integrates the Ethernet service interface unit and SDH line interface unit. l The system control unit, timeslot cross-connect unit, packet switching unit, and timing unit of the CSHN physical board are presented as a CSHN logical board on the NMS, supporting equipment level 1+1 protection. l The Ethernet service interface unit and SDH line interface unit of the CSHN physical board are presented as an EG2D logical board and an SL4D logical board respectively on the NMS, not supporting equipment level 1+1 protection. The EG2D and SL4D are two independent logical boards on active and standby CSHN boards, which can be considered as common service interface boards. 1+1 protection switching of control, switching, and timing boards does not affect the running of the EG2D and SL4D logical boards.
Figure 3-1 Configuration of 1+1 protection of control, switching, and timing boards
SLOT 26 (PIU) SLOT 28 (FAN) SLOT 13 (EXT) SLOT 11 (EXT) SLOT 9 (EXT) SLOT 20 (CSHN) SLOT 7 (EXT) SLOT 15 (CSHN) SLOT 5 (EXT) SLOT 3 (EXT) SLOT 1 (EXT) SLOT 16 (SL4D) SLOT 21 (SL4D) SLOT 27 (PIU) SLOT 14 (EXT) SLOT 12 (EXT) SLOT 10 (EXT) SLOT 22 (EG2D) SLOT 8 (EXT) SLOT 17 (EG2D) SLOT 6 (EXT) SLOT 4 (EXT) SLOT 2 (EXT)
Board-level 1+1 protection
Issue 02 (2011-01-20)
3-3
Purpose
1+1 backup between active and standby control, switching, and timing boards is provided to improve the reliability of the equipment. When the active board is faulty, the services are automatically switches to the standby board so that the impact on services can be minimized.
3.2 Basic Concepts

This section describes the basic concepts associated with 1+1 protection for the control, switching, and timing board. 3.2.1 Protection Type 1+1 backup between active and standby control, switching, and timing boards is non-revertive protection. 3.2.2 Switching Conditions The switching priority varies with the switching condition. 3.2.3 Switching Impact During the switching of the control, switching, and timing board, the TDM services may be transiently interrupted (< 50 ms), the Ethernet services may be transiently interrupted (< 100 ms).
3.2.1 Protection Type

1+1 backup between active and standby control, switching, and timing boards is non-revertive protection. In non-revertive protection, the equipment does not automatically switch back to the originally working slot even if the originally working slot houses a new board. Generally, the board that starts up first is the active board. l l If only one control, switching, and timing board is properly installed when the equipment is powered on, this board is the active board after 1+1 protection is configured. If two control, switching, and timing boards are properly installed and functioning when the equipment is powered on, the board in slot 15 is generally the active board.
3.2.2 Switching Conditions

The switching priority varies with the switching condition. Table 3-1 Trigger conditions of the control, switching, and timing boards 1+1 protection switching Switching Condition Switching triggered by board removal Priority The priorities are arranged in a descending order. Description The switching is triggered by the removal of the active board when the active and standby boards are properly functioning. The switching is not triggered by the removal of the standby board.
Issue 02 (2011-01-20)
3-4
Switching Condition Automatic switching
Priority
Description The switching is triggered by a hardware failure in the active board. A warm reset is automatically performed for the originally active board after switching. When the active board is in BIOS state for long, the active board cannot manage the NE or communicate with the standby board. When detecting the situation, the standby board automatically functions as the active board to manage the NE. The switching is triggered by an external command that is issued from the NMS. The prerequisite to manual switching is that the standby board is properly functioning, free of hardware alarms, and completed with data backup.
Active board in BIOS state for long
3.2.3 Switching Impact

During the switching of the control, switching, and timing board, the TDM services may be transiently interrupted (< 50 ms), the Ethernet services may be transiently interrupted (< 100 ms).
3.3 Specifications
This section describes the specifications for 1+1 protection for the control, switching, and timing board. Table 3-2 lists the specifications for 1+1 protection for the control, switching, and timing board. Table 3-2 Specifications of 1+1 protection for the control, switching, and timing board Item Protection for the control plane Protection for the service plane 1+1 protection for the system control unit 1+1 protection for the TDM switching unit 1+1 protection for the packet switching unit Specifications Supported
Supported
Supported
Issue 02 (2011-01-20)
3-5
Item 1+1 protection for the timing unit
Specifications Supported
3.4 Availability
This section describes the specifications for 1+1 protection for the control, switching, and timing board.

Table 3-3 Hardware and version support Feature 1+1 backup between active and standby control, switching, and timing boards Applicable Board CSHN Applicable Hardware Version All the versions Applicable Product Version V100R003C00 and later
l When the OptiX RTN 980 houses dual system control, switching, and timing boards, the Ethernet network management interfaces and the Ethernet NE stack interfaces on the two boards are equal to four ports on a hub. Note that an Ethernet loop cannot occur between any two ports. When the OptiX RTN 980 houses dual system control, switching, and timing boards, the external clock ports on the two boards each can input an external clock source. The external clock port only on the CSHN board in slot 15 can transparently transmit overheads (including DCC bytes, synchronous/asynchronous data overheads, and orderwire overheads) or function as a wayside E1 service port.
3.5 Principles
The switching between active and standby control, switching, and timing boards involves the entire board, including the system control unit, cross-connet unit/switching unit, and timing unit.
Switching diagrams
Figure 3-2 and Figure 3-3 show the working status change in the control, switching, and timing boards. After switching, the originally standby board functions as the active board.
3-6
Issue 02 (2011-01-20)
Figure 3-2 Principle for Active and Standby Control, Switching, and Timing Boards (before Switching)
CSHN in slot 15 System control unit Cross-connect/ Switching/ Timing Control bus CSHN in slot 20 System control unit Cross-connect/ Switching/ Timing
Clock
Service board 1
Service board 2
Service board n
Active unit Active service and timing bus Active control bus Standby service and timing bus Standby control bus
Issue 02 (2011-01-20)
3-7
Figure 3-3 Principle for active and standby control, switching, and timing boards (after switching)
CSHN in slot 15 System control unit Cross-connect/ Switching/ Timing Control bus CSHN in slot 20 System control unit Cross-connect/ Switching/ Timing
Clock
Service board 1
Service board 2
Service board n
Active unit Active service and timing bus Active control bus
Failure Standby service and timing bus Standby control bus
Principles for 1+1 Backup

1+1 backup is the basis of the protection mechanism. The following part describes the principles for 1+1 backup between the system control unit, switching unit, and timing units. l 1+1 backup between the system control units Figure 3-4 shows the principles for 1+1 backup between the system control units. The system control unit on the active CSHN board communicates with the NMS, receiving the configuration data from the NMS to provide the control and communication of the equipment. The standby system control unit synchronizes data with the active system control unit so that the data and control signals can be consistent on the active and standby boards.
NOTE
Data can be backed up in batches or in real time. When installed or reset (warm) on the poweredon equipment, the standby board synchronizes data with the active board in batches. After the batch backup is complete, the new configuration data from the NMS is backed up in real time.
The active and standby control, switching, and timing boards check their own hardware and software, and exchange the information so that the active/standby status can be determined. Then, the active/standby status information is sent to each service board and the service board accordingly selects its corresponding working system control unit. In-position status: indicates whether the board is in position (online).
Working status: indicates whether the board is properly functioning. When the board detects a fault, the working status is down. Manual switching is achieved by setting Working Status to Down. Active/standby status: The active and standby boards independently analyze each other's status, and obtain their active/standby status using logical computation. Figure 3-4 Principle for 1+1 backup between the system control units
Inter-board communication In-position status Working status System control unit A Active/Standby status In-position status Working status Active/Standby status
In-position status In-position status Working status Active/Standby status Working status Active/Standby status
System control unit B
Service board
1+1 backup between the cross-connect/switching units Considering a unidirectional service as an example, Figure 3-5 shows the principles for 1 +1 backup between the cross-connect/switching units. After the data backup is complete, the active and standby CSHN boards send the same configuration data to the cross-connect/switching units so that the cross-connect/ switching units can have the same configuration data. If the active cross-connect/ switching unit is faulty, the standby cross-connect/switching unit functions as a substitute. The control buses and service/timing buses are present between the service boards and active and standby CSHN boards. The service board is dually-fed and selectivelyreceiving. That is, the source service board sends a service to the active and standby cross-connect/switching unit, and the sink service board receives the service from the active cross-connect/switching unit.
Issue 02 (2011-01-20)
3-9
Figure 3-5 Principle for 1+1 backup between the cross-connect/switching units
Cross-connect unit A (Switching unit A)
Service board 1
Cross-connect unit B (Switching unit B)
Service board 2
1+1 backup between the timing units Figure 3-6 shows the principles for 1+1 backup between the timing units. The timing unit of the active CSHN board traces a certain reference clock based on the clock source priority list. The timing unit of the standby CSHN board traces the system clock of the active CSHN board to achieve frequency synchronization. By means of phase alignment, the system clocks of the active and standby units retain a very narrow difference in phase (< 3 ns). Therefore, switching between the timing units does not incur service bit errors. Through the active and standby timing buses, the active and standby timing units send the system clocks to each service board. The service board selects a system clock based on the working status of the active and standby system control units and the status of the active and standby system clocks.
3-10
Issue 02 (2011-01-20)
Figure 3-6 Principle for 1+1 backup between the timing units
External clock interface CSHN in slot 15 System clock Timing unit A System clock Timing unit B External clock interface CSHN in slot 20
Other unit System clock
Other unit System clock
Service board
Protection Switching Mechanism

The switching between active and standby control, switching, and timing boards involves the entire board. In normal cases, the system control unit, cross-connect unit/switchingunit, and timing unit on one board are all active units. 1+1 backup between active and standby control, switching, and timing boards requires the cooperation between the control, switching, and timing boards and the service boards. Based on different fault detection mechanisms, protection switching can be triggered by the control, switching, and timing board or service board. l Switching triggered by the control, switching, and timing board The switching is performed in the sequence of cross-connect/switching unit > timing unit > system control unit. 1. 2. After the active and standby CSHN boards determine their active/standby status, the change in active/standby status is sent to the service board through the control bus. The service board detects a change in the active/standby status through the hardware. If the standby service and timing bus is available, the service is switched to the standby service board. Switching is performed for the timing units on the active and standby CSHN boards. That is, the CSHN board in slot 20 does not trace the system clock of the CSHN board in slot 15, but traces a certain reference clock based on the clock source priority list. The CSHN in slot 15 traces the system clock of the CSHN board in slot 20, instead. The system control unit on the CSHN board in slot 15 disconnects from the Ethernet NM port, whereas the system control unit on the CSHN board in slot 20 connects to the Ethernet NM port. The communication and control functions are implemented by the CSHN board in slot 20.
3.
4.
Issue 02 (2011-01-20)
Switching triggered by the service board The service board can detect a fault in the active or standby bus and perform switching. In addition, the service board applies to the system control unit for switching between active and standby control, switching, and timing boards. 1. If the standby service and timing bus is available after the service board detects a fault in the active service and timing bus, switching between the active and standby buses is performed and the service board applies to the active CSHN board for switching between active and standby CSHN boards. After receiving the switching request form the service board, the active CSHN board sets Working Status to Down to trigger switching. The subsequent switching process is the same as the process of a switching triggered by the control, switching, and timing board.
2.
3.6 Planning Principles

OptiX RTN 980The OptiX RTN 980 is mainly used as a high-capacity Nodal. It is recommended that you configure two control, switching, and timing boards on the OptiX RTN 980 to improve equipment reliability.
3.7 Configuration Procedure

When two control, switching, and timing boards are installed, they are automatically configured into 1+1 protection, and therefore no manual operation is required.
NOTE
After a standby control, switching, and timing board is inserted into an NE that is operating normally, its logical board is automatically configured.
3.8 Task Collection

This section provides the hyperlinks of the operation tasks associated with the feature.
Related Tasks
A.11.6.8 Switching the System Control Unit and the Cross-Connect Unit
3.9 Relevant Alarms and Events

When the control, switching, and timing boards 1+1 protection switching occurs, the system reports the corresponding abnormal event.
Relevant Alarms
None.
3-12
Issue 02 (2011-01-20)

System Control Board Switching: This abnormal event indicates that the system control boards are external switched on the equipment that is configured with the control, switching, and timing boards 1+1 protection.
3.10 FAQs
This section provides the answers to the questions that are frequently raised when 1+1 backup between active and standby control, switching, and timing boards is used. Question: When does 1+1 backup between active and standby control, switching, and timing boards fail? Answer: It fails in the following scenarios: l l The batch backup task is incomplete. The standby board is faulty.
Question: Why is 1+1 backup between active and standby control, switching, and timing boards designed to non-revertive? Answer: The non-revertive protection switching has the following advantages: l Compared with protection schemes (such as MSP) that require external cable resources, 1 +1 backup between active and standby control, switching, and timing boards does not require external resources. The services before and after switching are the same. Revertive protection switching involves two switching operations, resulting in one more service interruption action than non-revertive protection switching. For revertive protection switching, the default active board must be specified. As a result, the active and standby boards need to negotiate about the default active board, resulting in more startup time.
l l
Question: Can the control, switching, and timing board be added for 1+1 protection when the equipment is powered off? Answer: This operation is not recommended because the databases of the two boards may be inconsistent. After the equipment is powered on, the new control, switching, and timing board may take over as the active board after relevant negotiation. As a result, the NE loses its configuration data. Question: If a control, switching, and timing board with a version different from that of the current board is added when the NE is properly functioning, can 1+1 protection be achieved? Answer: The data cannot be backed up in batches if the software versions of the two boards are inconsistent, 1+1 protection cannot be achieved. In this case, upgrade the new board to the current software version. Question: Assume the GNE is configured with 1+1 backup between active and standby control, switching, and timing boards and the network cable is connected to the active board. If the network cable is still connected to the active board after switching is performed, can the NMS manage the NE?
Answer: The Ethernet NM port and Ethernet NM cascading ports on the active and standby control, switching, and timing boards are equivalent to four ports on a hub. If the Ethernet NM port and hub are normal, the NMS can manage the NE without the need to change the network cable connection.
3-14
Issue 02 (2011-01-20)
4 SDH Protection Features
4
About This Chapter
SDH Protection Features
The SDH protection features supported by the OptiX RTN 980 include sub-network connection protection (SNCP), two-fiber bidirectional MSP, and linear MSP. 4.1 Subnetwork Connection Protection The subnetwork connection protection (SNCP) scheme protects the services that are transmitted across subnets. The subnetwork can be a chain, a ring, or a more complex network. 4.2 Linear Multiplex Section Protection The linear multiplex section protection (MSP) switching is applicable to point-to-point physical networks. The linear MSP provides protection for the services between two nodes at the multiplex section level. 4.3 Two-Fiber Bidirectional Ring MSP This chapter describes the two-fiber bidirectional ring MSP feature.
Issue 02 (2011-01-20)
4-1
4.1 Subnetwork Connection Protection

The subnetwork connection protection (SNCP) scheme protects the services that are transmitted across subnets. The subnetwork can be a chain, a ring, or a more complex network. 4.1.1 Introduction This section provides the definition of sub-network connection protection (SNCP) and describes its purpose. 4.1.2 Basic Concepts This topic describes the basic concepts that you need to be familiar with before you use the SNCP feature. 4.1.3 Specifications This topic provides the specifications of SNCP. 4.1.4 Reference Standards and Protocols This section describes the standards and protocols associated with SNCP. 4.1.5 Availability The SNCP feature requires the support of the applicable boards. 4.1.6 Principles The SNCP is realized based on the dual fed and selective receiving mechanism. 4.1.7 Planning Guidelines Follow certain guidelines when you plan SNCP. 4.1.8 Configuration Procedure When configuring the SNCP services, you need to create cross-connections of the SNCP services and set the SNCP automatic switching conditions as required. 4.1.9 Configuration Example By using an example, this topic describes how to plan and configure the SNCP according to the network conditions. 4.1.10 Task Collection This topic provides the hyperlinks of the operation tasks regarding the relevant feature. 4.1.11 Relevant Alarms and Events When the SNCP switching occurs, the system control board reports the relevant alarms and performance events. 4.1.12 FAQs This topic provides the answers to the questions that are frequently raised when the SNCP is adopted.
4.1.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 4-1 shows the application of SNCP. Figure 4-1 SNCP
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.

This topic describes the basic concepts that you need to be familiar with before you use the SNCP feature. 4.1.2.1 Protection Type The SNCP is classified into the revertive mode and the non-revertive mode. 4.1.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. 4.1.2.3 Hold-Off Time The SNCP protects services, whereas the 1+1 protection, N+1 protection protect links. Hence, when the SNCP is configured on a link that is already configured with the link-level protection, the hold-off time needs to be set to enable the link-level protection switching to first occur.
Hence, the SNCP switching does not occur repeatedly due to the protection switching that occurs on the link. 4.1.2.4 Switching Conditions The SNCP for different services is triggered by different conditions. 4.1.2.5 Switching Impact The services are interrupted within the SNCP switching time (less than 50 ms).

The 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 and returns to 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 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.
4.1.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 4-2 SNCP service pair
Working source Protection source
Service sink
The line types of the working sources and protection sources of SNCP service pairs can be microwave links or optical lines. l l l l SDH optical lines can be both working sources and protection sources of SNCP service pairs. SDH/PDH microwave links that IF1 boards provide can be both working sources and protection sources of SNCP service pairs. Hybrid microwave links that IFU2/IFX2 boards provide can be both working sources and protection sources of SNCP service pairs. Hybrid/Packet microwave links that ISU2/ISX2 boards provide can be both working sources and protection sources of SNCP service pairs.
4-4
SDH/PDH microwave links that IF1 boards provide can be the working sources of SNCP service pairs, and SDH lines can be the protection sources of the SNCP service pairs. These SNCP service pairs achieve protection for hybrid ring networks. With TU_AIS insertion through E1_AIS, SDH/PDH microwave links that IF1 boards provide can be the working sources of SNCP service pairs, and Hybrid microwave links that IFU2/IFX2/ISU2/ISX2 boards provide can be the protection sources of the SNCP service pairs. These SNCP service pairs achieve protection for hybrid ring networks.
4.1.2.3 Hold-Off Time

The SNCP protects services, whereas the 1+1 protection, N+1 protection protect links. Hence, when the SNCP is configured on a link that is already configured with the link-level protection, the hold-off time needs to be set to enable the link-level protection switching to first occur. Hence, the SNCP switching does not occur repeatedly due to the protection switching that occurs on the link. The following part uses an application scenario wherein the N+1 protection and the SNCP work together to describe the functions of the hold-off time.
Coexisting N+1 protection and SNCP

As shown in Figure 4-3, the service from NE A to NE C is configured with the revertive SNCP. The radio link between the NE B and NE C is configured with the N+1 protection. In normal cases, the working SNC traverses NE B. Figure 4-3 Coexisting N+1 protection and SNCP
NE A
Working SNC
NE B
NE D
The service between NE B and NE C is transmitted on the main link NE C
Issue 02 (2011-01-20)
4-5
Description of the Switching When the Hold-Off Time Is Not Set

If the hold-off time of the SNCP is not set (that is, the hold-off time is set to 0), the SNCP switching and HSM switching are triggered when the services are faulty due to fading on the active radio link between NE B and NE C. The HSM switching enables the service between NE B and NE C to be transmitted on the standby radio link. The SNCP switching enables the service between NE B and NE C to be transmitted on the protection SNC trail. Figure 4-4 shows the traffic flow. Figure 4-4 Traffic flow after the SNCP switching and N+1 protection 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 former active link is rectified, the revertive SNCP switching occurs. Figure 4-5 shows the traffic flow after the switching.
4-6
Issue 02 (2011-01-20)
Figure 4-5 Traffic flow after the revertive SNCP switching

NE A Working SNC
NE B
NE D
NE C
Description of the Switching When the Hold-Off Time Is Set

If the hold-off time is set, the SNCP 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 SNCP switching occurs. If the switching condition disappears, the SNCP switching is not triggered. In the example, the fault on the active radio link between NE B and NE C first triggers the HSM switching if the hold-off time is set. If the HSM switching is complete within the hold-off time, the SNCP switching condition no longer exists when the hold-off time expires. Therefore, the SNCP switching does not occur. Figure 4-6 shows the final traffic flow after the switching. Compared with the switching when the hold-off time is not set, occurrence of two switching events is prevented.
Issue 02 (2011-01-20)
4-7
Figure 4-6 Traffic flow after the switching when the hold-off time is set
NE A Working SNC
NE B
NE D
NE C
Precautions for Setting the Hold-Off Time

l To prevent the repeated occurrence of the SNCP switching, generally, you need to set the hold-off time for the SNCP when the SNCP works with the protection schemes, including the N+1 protection. The hold-off time must be longer than the switching time of the protection scheme that works with the SNCP (generally, it is set to 200 ms). When the SNCP works with the 1+1 HSB/FD/SD, it is recommended that you do not set the hold-off time. The reasons are that the HSB switching time is far longer than the SNCP switching time and therefore setting the hold-off time increases the service interruption duration. If the SNCP works with the 1+1 FD/SD, only HSM switching is triggered when a fault that can trigger HSM switching and SNCP switching occurs in the working channel. This mechanism is not affected by the setting of hold-off time. When only SNCP exists, hold-off time need not be set.

The SNCP for different services is triggered by different conditions.
4-8
Issue 02 (2011-01-20)
Table 4-1 SNCP switching conditions Switching Condition Clear switching (external switching) Lockout of protection channel (external switching) Priority From top downwards, the priority is from the highest to the lowest. Description All external switching states are cleared. 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. 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. The switching then 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 or from the protection SNC to the working SNC. The switching then changes to the automatic switching state. For the trigger conditions of the automatic switching, refer to Table 4-2, Table 4-3, Table 4-4, Table 4-5, and Table 4-6.
Signal failure
Issue 02 (2011-01-20)
4-9
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 changes to 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, the revertive switching occurs. From the time when the former working SNC 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.
NOTE
In the case of the revertive SNCP, if the services are currently on the protection trail, the services cannot be switched to the working trail when you perform the forced switching or manual switching.
SNCP Switching Conditions (Higher Order Services)

NOTE
The higher order services in the following table refer to the VC-4 service that is transmitted over the optical line or SDH microwave, and the Native STM-1 service that is transmitted over Integrated IP radio (Native STM-1 + Eth).
Table 4-2 Trigger conditions of the automatic SNCP switching (VC-4 services) Switching Condition Hardware fault on the IF board and line board R_LOS Description Default condition Default condition
4-10
Issue 02 (2011-01-20)
Switching Condition R_LOF R_LOC MS_AIS B2_EXC AU_LOP AU_AIS HP_LOM MW_LOF
Description Default condition Default condition Default condition Default condition Default condition Default condition Default condition Default condition (applicable only when the IF board functions as the working source or protection source) Default condition (applicable only when the IF board functions as the working source or protection source) Optional condition Optional condition Optional condition Optional condition
MW_LIM
B3_EXC B3_SD HP_TIM HP_UNEQ
Table 4-3 Trigger conditions of the automatic SNCP switching (STM-1 services transmitted over the Integrated IP radio (Native STM-1 + Eth)) Switching Condition Hardware fault on the ODU, IF board, and line board R_LOS R_LOF R_LOC MS_AIS B2_EXC AU_LOP AU_AIS HP_LOM Description Default condition Default condition Default condition Default condition Default condition Default condition Default condition Default condition Default condition
Issue 02 (2011-01-20)
4-11
Switching Condition MW_LOF
Description Default condition (applicable only when the IF board functions as the working source or protection source) Default condition (applicable only when the IF board functions as the working source or protection source) Default condition Default condition Optional condition Optional condition Optional condition Optional condition Optional condition
MW_LIM
TU_LOP TU_AIS MW_BER_EXC B3_EXC B3_SD HP_TIM HP_UNEQ
NOTE
The optional conditions in the preceding table can be the trigger condition of the automatic SNCP switching only after you set automatic switching conditions on the NMS. By default, the optical conditions do not trigger automatic SNCP switching.
SNCP Switching Conditions (Lower Order Services)

Lower order services include VC-3/VC-12 services and E1 services transmitted over the Integrated IP radio (Native E1 + Eth).
NOTE
The VC-3/VC-12 service in the following table refers to the VC-3/VC-12 service that is transmitted over the optical line or SDH microwave and the E1 service on the IF1 board.
Table 4-4 Trigger conditions of the automatic SNCP switching (VC-3 services) Switching Condition Hardware fault on the IF board and the line unit R_LOS R_LOF R_LOC MW_LOF Description Default condition Default condition Default condition Default condition Default condition (applicable only when the IF board functions as the working source or protection source)
4-12
Switching Condition MW_LIM
Description Default condition (applicable only when the IF board functions as the working source or protection source) Default condition Default condition Optional condition Optional condition Optional condition
TU_AIS TU_LOP LP_UNEQ B3_SD B3_EXC
NOTE
Table 4-5 Trigger conditions of the automatic SNCP switching (VC-12 services) Switching Condition Hardware fault on the IF board and the line unit R_LOS R_LOF R_LOC MW_LOF Description Default condition Default condition Default condition Default condition Default condition (applicable only when the IF board functions as the working source or protection source) Default condition (applicable only when the IF board functions as the working source or protection source) Default condition Default condition Optional condition Optional condition Optional condition
MW_LIM
TU_AIS TU_LOP LP_UNEQ BIP_SD BIP_EXC
Issue 02 (2011-01-20)
4-13

NOTE
Table 4-6 Trigger conditions of the automatic SNCP switching (E1 services transmitted over the Integrated IP radio (Native E1 + Eth)) Switching Condition Hardware fault All "1"s in E1 signals R_LOF R_LOC MW_LOF MW_LIM MW_BER_EXC Description Default condition Default condition Default condition Default condition Default condition Default condition Default condition
Converting E1_AIS Alarms into TU-AIS Alarms

According to the preceding switching conditions, the trigger condition of the automatic SNCP switching is the generation of a TU_AIS alarm when the IF1 board transmits TDM microwave services. Therefore, the IF board transmitting Hybrid microwave services must convert E1_AIS alarms into TU_AIS alarms when IF1 boards transmitting TDM microwave services and IF1 boards form an E1 SNCP ring. See Figure 4-7 for the principle of converting E1_AIS alarms into TU-AIS alarms. Figure 4-7 Principle of converting E1_AIS alarms into TU-AIS alarms
NE1 The IFU2 board inserts E1_AIS alarms, and converts E1_AIS alarms into TU_AIS alarms. IFU2 IFU2
IFU2 NE2 IF1 Working SNC Protection SNC
IFU2 NE4
IF1 TU_AIS IF1 IF1 NE3

OptiX equipment
The IF1 board triggers SNCP switching after receiving TU_AIS alarms.
4-14
Issue 02 (2011-01-20)

The services are interrupted within the SNCP switching time (less than 50 ms).
This topic provides the specifications of SNCP. Table 4-7 lists the specifications of SNCP. Table 4-7 Specifications of SNCP Item Maximum number of SNCP protection groups Types of services protected with SNCP Specification 1008 groups l SDH/PDH services on optical transmission links l STM-1/2xSTM-1 services transmitted over SDH microwave by using ISU2/ ISX2 boards l Native E1 services transmitted over Integrated IP radio (Native E1 and Native Ethernet) l STM-1 services transmitted over Integrated IP radio (Native STM-1 and Native Ethernet) Protection type Revertive mode Non-revertive mode WTR time Optional SNCP switching conditions (higher order services)a 5 to 12 minutes B3_EXC B3_SD HP_TIM HP_UNEQ MW_BER_EXC Optional SNCP switching conditions (lower order services)a BIP_EXC BIP_SD LP_TIM LP_UNEQ Switching time Coexistence with 1+1 or N+1 protection < 50 ms Supported
Issue 02 (2011-01-20)
4-15

NOTE
a: For details about SNCP switching conditions, see 4.1.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
4.1.5 Availability
The SNCP feature requires the support of the applicable boards.

Table 4-8 Hardware and version support Feature SNCP Applicable Board SL1D IF1 IFU2 IFX2 ISU2 ISX2 CSHN Applicable Hardware Version All the versions All the versions All the versions All the versions All the versions All the versions All the versions Applicable Product Version V100R003C00 and later V100R003C00 and later V100R003C00 and later V100R003C00 and later V100R003C00 and later V100R003C00 and later V100R003C00 and later
The dependencies between the SNCP feature and other features are as follows: l l l The radio link with the 1+1 protection can work as the working source, protection source, or service sink of the SNCP. The radio link with the N+1 protection can work as the working source, protection source, or service sink of the SNCP. The radio link with the XPIC can work as the working source, protection source, or service sink of the SNCP.
4-16
The Hybrid radio ring can use the SNCP and ERPS simultaneously to separately protect the E1/STM-1 services and Native Ethernet services on the ring.
4.1.6 Principles
The SNCP is realized 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 the SNCP.
Figure 4-8 SNCP realization principle (before the switching)

NE A Protection SNC
NE B
Figure 4-9 SNCP realization principle (after the switching)

NE A Protection SNC
NE B
When the working SNC fails, the SNCP switching principle is as follows: 1. 2. 3. Before the switching, the trail source of the SNC (NE A) sends normal service signals to the trail sink (NE B) through the working SNC and the protection SNC. When the IF unit or line unit of NE B detects that the signal of the working SNC fails, it reports this event to the system control unit. After the system control unit of NE B determines that the signal of the working SNC fails and the signal of the protection SNC is normal, the system control unit enables the crossHuawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 4-17
Issue 02 (2011-01-20)
connect unit to complete the cross-connection between the protection SNC and the service sink.

Follow certain guidelines when you plan SNCP.
Planning Guidelines on the Working SNC and the Protection SNC

l Do not overlap the working SNC and the protection SNC if possible.
Planning Guidelines on Protection Configuration Parameters

l If the protection is in the revertive mode, set the WTR time to a value between five and twelve 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 N+1 protection. The hold-off time must be longer than the switching time of any protection scheme that works with SNCP. 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 the SNCP is configured.

When configuring the SNCP services, you need to create cross-connections of the SNCP services and set the SNCP automatic switching conditions as required. Table 4-9 Procedure for configuring the SNCP service Step 1 Operation Configur ing the crossconnecti ons of TDM services A.4.1 Creating the 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 A.4.5 Configuring the Automatic Switching of SNCP Services Optional when the TDM service is an SNCP service.
A.4.2 Creating CrossConnections of SNCP Services
4-18
Issue 02 (2011-01-20)
Step 3
Operation A.4.4 Inserting TU_AIS
Description Required when the IFU2/IFX2/ ISX2/ISU2 and IF1 boards work as the east interface board and west interface board on the SNCP ring and pass-through services are configured between these interface boards. Perform the operation for the E1 port on the IFU2, IFX2, ISX2, or ISU2 board that the pass-through services involve.
A.4.3 Modifying the Priorities of E1 Services
Required when the working source, protection source, or sink of an SNCP service is a link where the AM function and the E1 priority function are enabled. Modify E1 Priority according to service planning.
NOTE
In the case of TDM services with the 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.

By using an example, this topic describes how to plan and configure the SNCP according to the network conditions. 4.1.9.1 Networking Diagram The topic describes the networking information about the NEs. 4.1.9.2 Service Planning This section provides the information about all the parameters required for configuring the NE data. 4.1.9.3 Configuration Process (on a Per-NE Basis) This section describes the process for the data configuration on a per-NE basis.

The topic describes the networking information about the NEs. As shown in Figure 4-10, four sets of the OptiX RTN 980 compose a Hybrid radio ring with the SNCP. l The links between NE22 and NE23 and between NE23 and NE24 are configured with 1+1 SD protection.
Issue 02 (2011-01-20)
The links between NE22 and NE23 and between NE23 and NE24 are configured and are under 1+0 non-protection.
Figure 4-10 Networking diagram of the SNCP ring

Tributary board: 2-SP3S East IF board: 4-ISU2 (M) and 6-ISU2 (S) West IF board: 3-ISU2 (M) and 5-ISU2 (S) 16E1 BSC 4xE1 BTS1 W SNCP W NE24 BTS4 E 4xE1 E W NE21
4xE1NE22 E BTS2 Tributary board: 2-SP3S East IF board: 4-ISU2 West IF board: 3-ISU2 (M) and 5-ISU2 (S)
Tributary board: 2-SP3S 4xE1 W NE23 E BTS3 Tributary board: 2-SP3S East IF board: 4-ISU2 West IF board: 3-ISU2 East IF board: 4-ISU2 (M) and 6-ISU2 (S) West IF board: 3-ISU2

This section provides the information about all the parameters required for configuring the NE data.
Timeslot Allocation Diagram

Figure 4-11 shows the timeslots that are allocated for the TDM services according to the network planning information.
4-20
Issue 02 (2011-01-20)
Figure 4-11 Timeslot allocation diagram (TDM services on the Hybrid radio ring network)
Station Timeslot NE21 4-ISU2 VC12: 1-2 2-SP3S:1-2 2-SP3S:1-2 2-SP3S:1-2 NE22 3-ISU2 4-ISU2 NE23 3-ISU2 4-ISU2 VC12: 1-2 2-SP3S:1-2 NE24 3-ISU2 4-ISU2 NE21 3-ISU2
Pass through (SNCP working path) Pass through (SNCP protection path) Add/Drop (SNCP working path) Add/Drop (SNCP protection path)
As shown in Figure 4-11, the information about the timeslots that the TDM services occupy on each NE is as follows: E1 services on NE22: l l l The E1 services are added to or dropped from the first to second ports on the SP3S board in slot 2 of NE22. The E1 services are added to or dropped from the first to second ports on the SP3S board in slot 2 of NE21. The E1 services occupy the first to second VC-12 timeslots on the ring.
SNCP
Table 4-10 provides the information about SNCP. Table 4-10 SNCP Parameter Working Source Protection Source Revertive Mode WTR Time Hold-Off Time Switching Condition Value 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.
4.1.9.3 Configuration Process (on a Per-NE Basis)

This section describes the process for the data configuration on a per-NE basis.
Procedure
Step 1 See A.4.2 Creating Cross-Connections of SNCP Services and configure the SNCP service cross-connections. l The values for the relevant parameters of NE21 are provided as follows. Parameter Value NE21 Direction Level Hold-off Time(100ms) Revertive Mode WTR Time(s) Source Slot Bidirectional VC-12 0 Revertive 600 4-ISU2-1 (working service) 3-ISU2-1 (protection service) Source VC4 VC4-1 (working service) VC4-1 (protection service) Source Timeslot Range(e.g.1,3-6) Sink Slot Sink VC4 Sink Timeslot Range(e.g.1,3-6) E1 Priority Activate Immediately 1-2 2-SP3S 1-2 Yes
l The values for the relevant parameters of NE22 are provided as follows. Parameter Value NE22 Direction Level Hold-off Time(100ms) Revertive Mode WTR Time(s) Source Slot Bidirectional VC-12 0 Revertive 600 3-ISU2-1 (working service) 4-ISU2-1 (protection service)
4-22
Issue 02 (2011-01-20)
Parameter
Value NE22
Source VC4
VC4-1 (working service) VC4-1 (protection service)
Source Timeslot Range(e.g.1,3-6) Sink Slot Sink VC4 Sink Timeslot Range(e.g.1,3-6) E1 Priority Activate Immediately
1-2 2-SP3S 1-2 Yes
Step 2 See A.4.1 Creating the Cross-Connections of Point-to-Point Services and configure the service cross-connections on NE23 and NE24. l The values for the relevant parameters of NE23 are provided as follows. Parameter Value NE23 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) Priority VC-12 Bidirectional 3-ISU2-1 VC4-1 1-2 4-ISU2-1 VC4-1 1-2 -
l The values for the relevant parameters of NE24 are provided as follows. Parameter Value NE24 Level Direction Source Slot VC-12 Bidirectional 3-ISU2-1
Issue 02 (2011-01-20)
4-23
Parameter
Value NE24
Source VC4 Source Timeslot Range(e.g.1,3-6) Sink Slot Sink VC4 Sink Timeslot Range(e.g.1,3-6) Priority
VC4-1 1-2 4-ISU2-1 VC4-1 1-2 -
Step 3 See A.11.1 Testing the E1 Service Through PRBS and test the E1 services. Test one E1 service on BTS22. The test results should show that the E1 services contain no bit error. ----End

Related Tasks
A.4.2 Creating Cross-Connections of SNCP Services A.4.5 Configuring the Automatic Switching of SNCP Services A.4.7 Converting a Normal Service into an SNCP Service A.4.8 Converting an SNCP Service to a Normal Service A.4.10 Switching SNCP Services A.4.11 Querying the Protection Status of SNCP Services A.4.4 Inserting TU_AIS A.11.6.3 Testing the SNCP Switching

When the SNCP switching occurs, the system control board reports the relevant alarms and performance events.
Relevant Alarms
None.
Relevant Events
l
4-24
SDH SNCP protection switching

The abnormal event of SDH SNCP protection switching refers to the performance event that the SDH SNCP protection switching is performed for the services configured with the SNCP.
4.1.12 FAQs
This topic provides the answers to the questions that are frequently raised when the SNCP is adopted. Q: What switching states does the SNCP have? A: The SNCP has the following common switching states: l l Normal The state when both 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 Q: What are the differences between a two-fiber bidirectional MSP ring and an SNCP ring? Answer: Item Protection object Protection level Protection mechanism Line rate Switching mode
Issue 02 (2011-01-20)
Two-Fiber Bidirectional MSP Ring A certain section of line Multiplex section level Shared protection STM-4 mode Ring switching
SNCP Ring Services between subnets VC-4 level, VC-3 level, or VC-12 level Dedicated protection PDH microwave, E1 or STM-1 mode Single-ended switching
4-25
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
4.2 Linear Multiplex Section Protection

The linear multiplex section protection (MSP) switching is applicable to point-to-point physical networks. The linear MSP provides protection for the services between two nodes at the multiplex section level. 4.2.1 Introduction This section provides the definition of linear MSP and describes its purpose. 4.2.2 Basic Concepts This topic describes the basic concepts that you need to be familiar with before you use the linear MSP feature. 4.2.3 Specifications This section describes the specifications of linear MSP. 4.2.4 Reference Standards and Protocols This section describes the standards and protocols associated with the linear MSP feature. 4.2.5 Availability This section describes the support required by the application of the LMSP feature and its dependencies. 4.2.6 Principles The 1+1 linear MSP and the 1:N linear MSP have different switching principles. 4.2.7 Planning Guidelines Follow certain guidelines when you plan linear MSP. 4.2.8 Configuration Procedure
To configure a linear MSP service, you need to create the linear MSP protection group and then create the service cross-connections. 4.2.9 Configuration Example This topic uses an example to describe how to plan and configure the AM. 4.2.10 Task Collection This topic provides the hyperlinks of the operation tasks regarding the linear MSP feature. 4.2.11 Relevant Alarms and Events When a linear MSP switching occurs, the system control and communication board reports the corresponding alarms and performance events. 4.2.12 FAQs This topic provides the answers to the questions that are frequently asked when the linear MSP is used.
4.2.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 4-12 shows the application of 1+1 linear MSP. l Figure 4-12 1+1 linear MSP
NE A Working channel NE B
Protection channel
Protection switching NE A Working channel NE B
Protection channel
Issue 02 (2011-01-20)
4-27
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 4-13 shows the application of 1:N linear MSP.
Figure 4-13 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.

This topic describes the basic concepts that you need to be familiar with before you use the linear MSP feature. 4.2.2.1 Protection Type The linear MSP can be classified by protection mechanism, switching mode, and revertive mode. 4.2.2.2 Meanings of K Bytes The linear MSP protocol uses the K1 and K2 bytes in the multiplex section overhead to transfer switching requests. 4.2.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. 4.2.2.4 Switching Impact The services are interrupted within the linear MSP switching time (less than 50 ms). After the 1:N linear MSP switching occurs, the extra services are interrupted. After the revertive switching occurs, the extra services are restored.

The linear MSP can be classified by protection mechanism, switching mode, and revertive mode. With regard to the protection mechanism, the linear MSP is classified into the dedicated protection and the shared protection. l Dedicated protection In the case of the dedicated protection, one working channel exclusively uses one protection channel. The dedicated protection channel cannot carry extra services. The 1+1 protection is the dedicated protection. l Shared protection In the case of the shared protection, one or more working channels share one protection channel. The shared protection channel can carry extra services. The 1:N (including the 1:1) protection is the shared protection. With regard to the switching mode, the linear MSP is classified into the single-ended switching and the dual-ended switching. l Single-ended switching In single-ended switching mode, the switching occurs only at one end and the state of the other end remains unchanged. l Dual-ended switching In dual-ended switching mode, the switching occurs at both ends at the same time. With regard to the revertive mode, the linear MSP 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 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. Hence, the linear MSP is classified into the following modes: l l
Issue 02 (2011-01-20)
1+1 dual-ended revertive mode 1+1 dual-ended non-revertive mode

l l l l l l l l l l l
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 1+1 single-ended revertive mode 1+1 single-ended non-revertive mode 1+1 dual-ended revertive mode 1+1 dual-ended non-revertive mode 1:N dual-ended revertive mode
The OptiX RTN 980 supports the following linear MSP modes:
The 1:N dual-ended revertive mode performs switching according to the MSP protocol of linear MSP specified in ITU-T G.841. The 1+1 dual-ended mode uses the protocol that is compatible with the 1:N mode. The switching in 1+1 single-ended mode does not use protocols.
4.2.2.2 Meanings of K Bytes

The linear MSP protocol uses the K1 and K2 bytes in the multiplex section overhead to transfer switching requests. Table 4-11 Meanings of K bytes (linear MSP) K Byte K1 (bit 1 to bit 4) Meaning The four bits carry the bridge request code. Table 4-12 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 the 1:N). 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.
K1 (bit 5 to bit 8)
K2 (bit 1 to bit 4)
K2 (bit 5)
K2 (bit 6 to bit 8)
4-30
Issue 02 (2011-01-20)
Table 4-12 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 signal Failure of lowpriority signal Degradation of high-priority signal Degradation of low-priority signal Unused Manual switching Unused WTR Unused Exercise Unused Reverse request Non-revertive No request
1 1 1 1
1 1 1 0
1 0 0 1
0 1 0 1
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 980 uses 1101 (failure of high-priority signal) and 1011 (degradation of highpriority signal) as the 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.
Table 4-13 Trigger conditions of the linear MSP switching Switching Condition Lockout of protection channel (external switching) Priority From top downwards, 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, the SF switching is triggered.
Signal failure (SF)
4-32
Issue 02 (2011-01-20)
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, the 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, 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 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, the revertive switching occurs. Within the period 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. Service signals are not actually switched. The exercise functionality is used only to check whether an NE can normally run the MSP protocol.
Issue 02 (2011-01-20)
4-33
NOTE
l The SD is an optional switching condition. You can specify on the NMS whether the SD is used as a switching condition. By default, the 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 the lockout, forced switching, manual switching, or exercise switching. l If an NE needs to perform switching according to the K bytes from the opposite NE, the NE determines the switching priority according to the bridge request code contained in the K bytes. For the meanings of the K bytes, see 4.2.2.2 Meanings of K Bytes. l If the working channels with the same switching priority request 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.

The services are interrupted within the linear MSP switching time (less than 50 ms). After the 1:N linear MSP switching occurs, the extra services are interrupted. After the revertive switching occurs, the extra services are restored.
This section describes the specifications of linear MSP. Table 4-14lists the specifications of linear MSP. Table 4-14 Specifications of linear MSP Item Service type of linear MSP Specification STM-1 optical transmission link STM-4 optical transmission link Maximum number of linear MSP groups STM-1 optical transmission link l Seven groups of 1+1 linear MSP l Seven groups of 1:N (N 7) linear MSP STM-4 optical transmission link l Two groups of 1+1 linear MSP l Two groups of 1:N (N 3) linear MSP Protection type of linear MSP 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
Item WTR time MSP protocol
Specification 5-12 minutes 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.
Switching time
Less than 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
4.2.5 Availability
This section describes the support required by the application of the LMSP feature and its dependencies.

Table 4-15 Hardware and version support Feature LMSP Applicable Board SL1D CSHN Applicable Hardware Version All the versions All the versions Applicable Product Version V100R003C00 and later V100R003C00 and later
The dependencies between the LMSP feature and other features are as follows: l l The port involved in LMSP cannot function as an east or west port of RMSP. The optical ports of CSHN board and those of SL1D board cannot be configured into a linear MSP group at the same time.
4.2.6 Principles
The 1+1 linear MSP and the 1:N linear MSP have different switching principles.
4.2.6.1 1+1 Linear MSP The 1+1 linear MSP adopts the dual fed and selective receiving mechanism to realize the switching. 4.2.6.2 1:N Linear MSP The 1:N linear MSP adopts the automatic bridge mechanism to realize the switching.
4.2.6.1 1+1 Linear MSP

The 1+1 linear MSP adopts the dual fed and selective receiving mechanism to realize the switching.
NOTE
The following part uses the switching that is triggered by the signal failure on the working channel as an example to describe the switching principle of the 1+1 linear MSP.
Figure 4-14 Realization principle of the 1+1 linear MSP (before the switching)
NE B Working NE A
Protection Working
Protection Normal service
Figure 4-15 Realization principle of the 1+1 linear MSP (after the switching, in single-ended mode)
NE B Working NE A
Protection Working
4-36
Issue 02 (2011-01-20)
When the signal on the working channel fails, the switching principle in single-ended mode is described as follows: 1. 2. 3. Before the switching, the source sends service signals to the working channel and the protection channel. The sink selects the service signals from the working channel. When the line unit at the sink in a certain direction (NE A) detects that the signal on the working channel fails, the line unit reports the event to the system control unit. After the system control unit confirms that the signal on the working channel fails and the protection channel is normal, the system control unit enables the cross-connect unit to complete the cross-connection between the protection channel and the service sink.
Figure 4-16 Realization principle of the 1+1 linear MSP (after the switching, in dual-ended mode)
NE B Working NE A
Protection Working
When the signal on the working channel fails, the switching principle in dual-ended mode is described as follows: 1. 2. Before the switching, the source sends service signals to the working channel and the protection channel. The sink selects the service signals 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 also on the protection channel (the request type is "reverse request"). NE A receives the service signals from the protection channel. NE B also receives the service signals from the protection channel.
3. 4. 5.
4.2.6.2 1:N Linear MSP

The 1:N linear MSP adopts the automatic bridge mechanism to realize the switching.
NOTE
The following part uses the 1:1 linear MSP switching that is triggered by the signal failure on the working channel as an example to describe the switching principle of the 1:N linear MSP.
Issue 02 (2011-01-20)
4-37
Figure 4-17 Realization principle of the 1:1 linear MSP (before the switching)
NE B Working NE A
Protection Working
Protection Normal service Extra service
Figure 4-18 Realization principle of the 1:1 linear MSP (after the 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 the 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.
Planning Guidelines on 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 l In 1+1 single-ended non-revertive mode, a switching is performed in a simple manner and the switching time is short. 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 MSP protocols used at both ends must be consistent. It is recommended that you apply the new MS 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 between five and twelve minutes. It is recommended that you set the WTR time to the default value, namely, ten minutes. It is recommended that you set SD as a switching condition.

To configure a linear MSP service, you need to create the linear MSP protection group and then create the service cross-connections. Table 4-16 Procedure for configuring a linear MSP service Step 1 Operation A.3.1 Configuring Linear MSP Description Required when the linear MSP is configured for the optical transmission line. The parameters need to be set according to the service planning. 2 Configur ing the crossconnecti ons of TDM services A.4.1 Creating the CrossConnections of Point-to-Point Services Required when the service is a point-to-point service. The parameters need to be set according to the service planning.
NOTE
a: Under linear MSP, only TDM services on a working link need to be configured. Under 1:N linear MSP, configure extra TDM services on a protection link if required.

This topic uses an example to describe how to plan and configure the AM.
4.2.9.1 Networking Diagram This topic describes the networking information about the NEs. 4.2.9.2 Service Planning The service planning information contains all the parameter information required for configuring the NE data. 4.2.9.3 Configuration Procedure This topic describes the procedure for the data configuration.

This topic describes the networking information about the NEs. As shown in Figure 4-19, the relative networking information is as follows: l l To ensure the reliable transmission of the services between NE11 and NE13, the linear MSP is configured for the optical transmission line between NE11 and NE13. NE11 transmits the services in the first 16 E1s of the STM-1 to NE12.
Figure 4-19 Networking diagram of the linear MSP

16xE1 STM-1
NE12
NE11
NE13
Working port: 16-SL4D-1 Protection port: 16-SL4D-2 Sink board: 3-ISU2

Timeslot Allocation Diagram

The cross-connections are set up for the 16 E1 services from port 1 on the SL1D board in slot 1 of NE11 to the ISU2 board in slot 3 of NE12.
NOTE
In this configuration example, only the configuration information about NE11 is provided.
Linear MSP
In this configuration example, no extra services need to be transmitted. Hence, the single-ended non-revertive 1+1 linear MSP is configured to protect the optical transmission line between NE11 and the third-party network. Table 4-17 provides the related planning information.
Table 4-17 Linear MSP Parameter Protection Type Switching Mode Revertive Mode SD Enable Protocol Type West Working Unit West Protection Unit NE11 1+1 Linear MSP Single-Ended Switching Non-Revertive Enabled (default value) New Protocol (default value) 16-SL4D-1 16-SL4D-2
NOTE
Unless otherwise specified, SD Enable, Protocol Type take the default values.
4.2.9.3 Configuration Procedure

Procedure
Step 1 See A.3.1 Configuring Linear MSP and create the linear MSP. The values for the related parameters are provided as follows. Parameter Value Range NE11 Protection Type Switching Mode Revertive Mode WTR Time(s) SD Enable Mapped Board 1+1 Protection Single-Ended Switching Non-Revertive 600 Enabled l West Working Unit: 16-SL4D-1 l West Protection Unit: 16-SL4D-2
Step 2 See A.4.1 Creating the Cross-Connections of Point-to-Point Services and create the crossconnections of the point-to-point service. l The values for the relevant parameters of NE11 are provided as follows.
Issue 02 (2011-01-20)
4-41
Parameter
Value Range NE11
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 Bidirectional 16-SL4D-1 VC4-1 1-16 3-ISU2-1 VC4-1 1-16
Step 3 See A.11.1 Testing the E1 Service Through PRBS and perform the 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 topic provides the hyperlinks of the operation tasks regarding the linear MSP feature.
Related Tasks
A.3.1 Configuring Linear MSP A.3.2 Querying the Status of the Linear MSP A.3.3 Performing Linear MSP Switching A.3.4 Starting/Stopping the Linear MSP Protocol A.11.6.7 Testing the Linear MSP Switching

When a linear MSP switching occurs, the system control and communication board reports the corresponding alarms and performance 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_MANUAL_STOP alarm indicates that the MSP protocol is manually stopped.
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 sent K1 (bit 5 to bit 8) is different from the signal channel indicated by the received K2 (bit 1 to bit 4), the system control and communication 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 system control and communication 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, and if the received K2 byte indicates a model different from the mode used by the NE, the system control and communication board reports the LPS_UNI_BI_M alarm. This alarm applies only to the restructure protocol.
Relevant Events
None.
4.2.12 FAQs
This topic provides the answers to the questions that are frequently asked when the linear MSP is used. Q: What switching states does the linear MSP have? A: The linear MSP has the following switching states: l l l l l l l l l
Issue 02 (2011-01-20)
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 The state after an exercise switching Signal failure The state after an SF switching Signal degrade
The state after an SD switching l 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 the 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, generally, it is 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 on byte K. By default, the OptiX equipment uses the SF and SD of the higher priority. If the third-party equipment uses the SF and SD of the lower priority, make modifications 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, make modifications accordingly on the OptiX equipment.
l l
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 are services interrupted after the 1+1 unidirectional linear MSP switching? A: During the configuration of the 1+1 linear MSP on the NMS, the unidirectional crossconnection between the service source and the protection channel is not configured. Q: What is the method of handling the failure of a linear MSP switching? A: The steps are as follows: 1. Check the data configuration of the MSP, especially the node ID of each NE. The configured node IDs of the 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 a protection channel, rectify the fault of the protection channel according to the alarm.
4.3 Two-Fiber Bidirectional Ring MSP

This chapter describes the two-fiber bidirectional ring MSP feature. 4.3.1 Introduction
This section provides the definition of two-fiber bidirectional ring MSP and describes its purpose. 4.3.2 Basic Concepts This section describes the basic concepts that you should be familiar with before using two-fiber bidirectional ring MSP. 4.3.3 Specifications This section describes the specifications of two-fiber bidirectional ring MSP. 4.3.4 Reference Standards and Protocols This section describes the standards and protocols associated with two-fiber bidirectional ring MSP. 4.3.5 Availability This section describes the support required by the application of the two-fiber bidirectional ring MSP feature and its dependency. 4.3.6 Principles Two-fiber bidirectional ring MSP uses the automatic bridging mechanism between working channels and protection channels to implement switching. 4.3.7 Planning Guidelines Follow certain rules when you plan two-fiber directional ring MSP. 4.3.8 Configuration Procedure To configure a ring MSP service, you need to create a ring MSP protection group and then create service cross-connections. 4.3.9 Configuration Example This section uses an example to describe how to plan and configure ring MSP according to network conditions. 4.3.10 Task Collection This section provides the hyperlinks of the operation tasks associated with two-fiber bidirectional ring MSP. 4.3.11 Relevant Alarms and Events When a two-fiber bidirectional ring MSP switching occurs, the NE reports relevant alarms and abnormal events. 4.3.12 FAQs This section provides the answers to the questions that are frequently raised when two-fiber bidirectional ring MSP is used.
4.3.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 4-20 shows application of a two-fiber bidirectional MSP ring. Figure 4-20 Two-fiber bidirectional MSP ring
NE A East West
West NE B East
East STM-4 two-fiber bidirectional MSP ring West NE D
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).
4-46
Issue 02 (2011-01-20)

This section describes the basic concepts that you should be familiar with before using two-fiber bidirectional ring MSP. 4.3.2.1 Protection Type Two-fiber bidirectional ring MSP is the most widely used MSP type. 4.3.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. 4.3.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. 4.3.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.
4.3.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 4-18 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 4-19 provides the meanings of the four bits.
4-47
Issue 02 (2011-01-20)
Byte K K1 (bits 5 to 8) K2 (bits 1 to 4) K2 (bit 5) K2 (bits 6 to 8)
Meaning 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. 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 4-19 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
4-48
Issue 02 (2011-01-20)

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.

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 4-20 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.
Issue 02 (2011-01-20)
4-49
Switching Condition Signal failure (SF)
Priority
Description 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. 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.
Signal degradation (SD)
4-50
Issue 02 (2011-01-20)
Priority
Description 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. 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 4.3.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.
This section describes the specifications of two-fiber bidirectional ring MSP.
Table 4-21 lists the specifications of two-fiber bidirectional ring MSP. Table 4-21 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 Two groups STM-4 optical transmission link 5-12 minutes < 50 ms

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
4.3.5 Availability
This section describes the support required by the application of the two-fiber bidirectional ring MSP feature and its dependency.

Table 4-22 Hardware and version support Feature Two-fiber bidirectional MSP ring Applicable Board CSHN Applicable Hardware Version All the versions Applicable Product Version V100R003C00 and later
Feature Dependency
The line of a two-fiber bidirectional MSP ring cannot be configured with linear MSP.
4.3.6 Principles
Two-fiber bidirectional ring MSP uses the automatic bridging mechanism between working channels and protection channels to implement switching.
4-52
Issue 02 (2011-01-20)

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.
Figure 4-21 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 4-22 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 4-21 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).
2.
Issue 02 (2011-01-20)
3. 4.
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 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). 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.
5.
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.
4-54
Issue 02 (2011-01-20)
Planning Guidelines on the Protection Configuration Parameters

l l l The MSP protocols used on a ring network must be consistent. It is recommended that you adopt the new protocol. 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 4-23 Configuration procedure for a ring MSP service Step 1 Operation A.3.5 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 Configuring the crossconnections of TDM services A.4.1 Creating the Cross-Connections of Point-to-Point Services Required when the service is a point-to-point service. You need to set the parameters according to the service planning.
NOTE
a: Under ring MSP, only TDM services on a working link need to be configured.

This section uses an example to describe how to plan and configure ring MSP according to network conditions. 4.3.9.1 Networking Diagram The section describes the networking information about NEs. 4.3.9.2 Service Planning The service planning information contains all the parameters required for configuring the NE data. 4.3.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 4-23, one OptiX RTN 980 (NE4) and three OptiX transmission devices form a two-fiber bidirectional MSP ring. NE4 transmits 16xE1 services between NE1 and NE5. Figure 4-23 Two-fiber bidirectional MSP ring
IF board: 3-ISU2 West line: 16-SL4D-1 East line: 16-SL4D-2 NE 1 NE 2 16E1 MSP ring NE 4 NE 5 NE 3

The service planning information contains all the parameters required for configuring the NE data.
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 4-24 provides the information about ring MSP. Table 4-24 Information about ring MSP Parameter WTR time (s) SD enable Protocol type West line 1 East line 1
4-56
NE4 600 Enabled New protocol 16-SL4D-1 16-SL4D-2


This section describes the process of configuring service data.
Procedure
Step 1 A.3.5 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: 16-SL4D-1 l East line 1: 16-SL4D-2
Step 2 A.4.1 Creating the Cross-Connections of Point-to-Point Services. The following table provides values of parameters. Parameter Value NE4 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 Bidirectional 16-SL4D-2 VC4-1 1-16 3-ISU2-1 VC4-1 1-16
Step 3 A.11.1 Testing the E1 Service Through PRBS.

Test any two E1 services on each base station. The test results show that the E1 services contain no bit errors. ----End

This section provides the hyperlinks of the operation tasks associated with two-fiber bidirectional ring MSP.
Related Tasks
A.3.5 Configuring Ring MSP A.3.6 Querying Ring MSP Status A.3.7 Triggering Ring MSP Switching A.3.8 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.
4.3.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 02 (2011-01-20)
4-59
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.
4-60
Issue 02 (2011-01-20)
5 Ethernet Features on the Packet Plane
Ethernet Features on the Packet Plane
About This Chapter

This section describes the Ethernet features on the packet plane. The packet plane refers to the switching plane provided by the packet switching unit on the system control, cross-connect, and clock board. The Ethernet ports on other Ethernet interface boards, the Integrated IP radio port on the IF board are mounted to this plane.
NOTE
ETH PWE3 is described in the section about the 6 Packet Features.
5.1 What's the Packet Plane The packet plane refers to the switching plane provided by the packet switching unit on a system control, switching, and timing board. The packet plane provides a wide range of services and features based on Native Ethernet, as well as a wide range of services and features based on MPLS/PWE3. 5.2 VLAN This chapter describes the virtual local area network (VLAN) feature. 5.3 QinQ This chapter describes the QinQ (802.Q in 802.Q) feature. 5.4 Layer 2 Switching This chapter describes the Layer 2 switching feature. 5.5 Ethernet Ring Protection Switching Ethernet ring protection switching (ERPS) is applicable to ring physical networks. ERPS protects Ethernet services on an Ethernet ring network. 5.6 MSTP The Multiple Spanning Tree Protocol (MSTP) is a type of spanning tree protocols. The MSTP is compatible with the STP and RSTP, and the defects in the STP and RSTP are fixed in the MSTP. 5.7 Link Aggregation Group Link aggregation allows multiple links that are attached to the same equipment to be aggregated together to form a link aggregation group (LAG) so that the bandwidth is increased and the reliability of the links is improved. The aggregated links can be considered as a single logical link.
5.8 Link State Pass Through This chapter describes the link state pass through (LPT) feature. 5.9 QoS The quality of service (QoS) refers to the ability of a communication network to ensure the expected service quality in the aspects of the bandwidth, delay, delay jitter, and packet loss ratio, and thus 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. 5.10 ETH-OAM 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. 5.11 Remote Network Monitoring The remote network monitoring (RMON) feature is used to monitor the data traffic on a network segment or on an entire network. Currently, the RMON standard is one of the most widely applied network management standards.
5-2
Issue 02 (2011-01-20)
5.1 What's the Packet Plane

The packet plane refers to the switching plane provided by the packet switching unit on a system control, switching, and timing board. The packet plane provides a wide range of services and features based on Native Ethernet, as well as a wide range of services and features based on MPLS/PWE3. As shown in Figure 5-1, the ports connecting to the packet plane are classified into the following types: l l FE/GE ports on a system control, switching, and timing board These ports are directly connected to the packet switching unit. FE/GE ports on an Ethernet interface board In the receive direction, the Ethernet switching unit on an Ethernet interface board adds port tags to the packets received from its internal FE/GE ports. Then, the packets are converged to the GE ports on the board, and then transmitted to the packet switching unit. The packet switching unit processes the packets of each port based on the port tags. In the transmit direction, the packet switching unit adds the port tags to the packets. Then, the packets are transmitted to the Ethernet switching unit through the internal GE ports on the board. The Ethernet switching unit transmits the packets to the ports based on the port tags. Therefore, the FE/GE ports on the Ethernet interface board can be regarded as being directly connected to the packet switching unit. l IF_ETH ports on a general IF board or general XPIC IF board IF_ETH ports are internal GE ports on a general IF board or general XPIC IF board. Ethernet packets are transmitted to the local IF board through its IF_ETH ports, and then mapped into Integrated IP radio frames. Ethernet packets demapped from Integrated IP radio frames are transmitted to the packet switching unit through IF_ETH ports. The main differences between an IF_ETH port and a GE/FE port are as follows: An IF_ETH port is an internal Ethernet port. It transmits and receives MAC frames and does not have PHY-layer functions. The bandwidth at an IF_ETH port is equal to the Ethernet service bandwidth that Integrated IP radio supports. Therefore, when the AM function is enabled in the case of Integrated IP radio, the bandwidth at an IF_ETH port changes according to the modulation scheme.
NOTE
Since an IF port corresponds to an IF_ETH port. the IF ports or the microwave ports corresponding to IF ports can be regarded as being directly connected to the packet plane.
Issue 02 (2011-01-20)
5-3
Figure 5-1 Packet plane

Packet plane Ethernet interface board FE/GE PORT1 Ethernet switching unit IF_ETH GE GE System control, switching, and timing board General IF board or general XPIC IF board IF unit
IF
FE/GE
PORTn
FE/GE
Ethernet interface board PORT1 Ethernet switching unit
Packet switching unit GE GE
IF_ETH
General IF board or general XPIC IF board IF unit
IF
FE/GE
PORTn
FE/GE
FE/GE
5.2 VLAN
This chapter describes the virtual local area network (VLAN) feature. 5.2.1 Introduction This section provides the definition of VLAN and describes its purpose. 5.2.2 Basic Concepts This section describes the basic concepts associated with VLANs. 5.2.3 Specifications This section provides the specifications of VLANs that the equipment supports. 5.2.4 Reference Standards and Protocols This section describes the standards and protocols associated with VLANs. 5.2.5 Availability This section describes the support required by the application of the VLAN feature and its dependency. 5.2.6 Principles Implementation of the VLAN feature is relevant to the port attribute and service type. 5.2.7 Planning Guidelines Follow certain guidelines when you plan VLANs. 5.2.8 Configuration Procedure Based on the VLAN planning information, configure an Ethernet service and set the TAG attribute of an Ethernet port. 5.2.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.
5.2.10 Task Collection This section provides the hyperlinks of the operation tasks associated with VLANs. 5.2.11 Relevant Alarms and Events There are no alarms or performance events relevant to VLANs. 5.2.12 FAQs This section provides the answers to the questions that are frequently raised when the VLAN feature is used.
5.2.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 5-2 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 5-2 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 Isolating users and improving network security 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 LAN, 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.

This section describes the basic concepts associated with VLANs. 5.2.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. 5.2.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. 5.2.2.3 VLAN-based E-Line Services VLANs can be used to separate E-Line services. With the VLAN technology, multiple E-Line services can share one physical channel. These services are VLAN-based E-Line services. 5.2.2.4 E-LAN Services Based on 802.1q Bridge E-LAN services can be separated by setting VLANs. In this case, a bridge is divided into multiple sub-switching domains. Therefore, the E-LAN services separated by setting VLANs are E-LAN services based on 802.1q bridge. 5.2.2.5 VLAN Forwarding Table Generally, the VLAN IDs of VLAN-based E-Line services are not changed. If it is required to change the VLAN IDs, you need to configure a VLAN forwarding table.
5.2.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 5-3 shows the format of the tagged frame.
Figure 5-3 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
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.
5.2.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 5-1 provides the methods for an ingress port and an egress port to process Ethernet frames based on different TAG attributes. Table 5-1 Processing of data frames based on different TAG attributes Direction Type of Data Frame Tagged frame Processing Method Tag Aware Receives the frame. Access Discards the frame. Hybrid Receives the frame.
Ingress port
Issue 02 (2011-01-20)
5-7
Direction
Type of Data Frame Untagged frame
Processing Method Tag Aware Discards the frame. Access Receives the frame after it is added with a port VID (PVID). Transmits the frame after the VID is stripped. Hybrid Receives the frame after it is added with a PVID. Transmits the frame.
Egress port
Tagged frame
Transmits the frame.
NOTE
After being into a port, an untagged frame may be discarded or added with a PVID to form a tagged frame. Thus, an Ethernet frame must be tagged before leaving an egress port.
5.2.2.3 VLAN-based E-Line Services

VLANs can be used to separate E-Line services. With the VLAN technology, multiple E-Line services can share one physical channel. These services are VLAN-based E-Line services.
Models of Services
Table 5-2 shows the models of VLAN-based E-Line services. Table 5-2 Models of VLAN-based E-Line services Type of Service VLAN-based ELine services Flow of Service PORT+VLAN (source) PORT+VLAN (sink)
NOTE The VLAN ID of the source and the VLAN ID of the sink must be the same.
Direction of Service UNI-UNI
Encapsulation Mode of Port 802.1Q (source) 802.1Q (sink)
Description of Service The source port processes the incoming Ethernet frames based on its TAG attribute, and then sends the Ethernet frames with a specific VLAN ID to the sink port. The sink port processes the Ethernet frames based on its TAG attribute, and then exports the processed Ethernet frames.
5-8
Issue 02 (2011-01-20)
Typical Applications
Figure 5-4 shows the typical application of VLAN-based E-Line services. Service 1 and Service 2 carry different VLAN IDs. Therefore, after the two Ethernet services are accessed to NE1 through Port 1 and Port 2 respectively, they can share the same transmission channel at Port 3. On NE1, Port 1 and Port 2 process the incoming packets based on their own TAG attributes. Then, Port 1 and Port 2 send Service 1 and Service 2 to Port 3. Port 3 processes all the outgoing packets based on its TAG attribute, and then sends Service 1 and Service 2 to NE2. Due to the different VLAN IDs, Service 1 and Service 2 can be transmitted through Port 3 at the same time. NE2 processes Service 1 and Service 2 in the same manner as NE1. Figure 5-4 Model of VLAN-based E-Line services
NE 1 Service 1 VLAN ID: 100 Service 2 VLAN ID: 200 Port 1 NE 2 Port 3 Transmission Network Port 3 Service 1 VLAN ID: 100 Service 2 VLAN ID: 200
E-Line
E-Line
e E-Lin
Port 1
Service 1 VLAN ID: 100
Port 2
Service 1 VLAN ID: 100 Service 2 VLAN ID: 200
E-Lin e
Service 2 Port 2 VLAN ID: 200
5.2.2.4 E-LAN Services Based on 802.1q Bridge

E-LAN services can be separated by setting VLANs. In this case, a bridge is divided into multiple sub-switching domains. Therefore, the E-LAN services separated by setting VLANs are E-LAN services based on 802.1q bridge.
Model of Service
Table 5-3 shows the models of E-LAN services based on 802.1q bridge. Table 5-3 Model of E-LAN services based on 802.1q bridge Type of Service E-LAN services based on 802.1q bridge TAG Attribute C-Awared Encapsulation Mode of Port 802.1q Type of Logical Port PORT+VLAN Learning Mode IVL SubSwitching Domain Sub-switching domains are divided based on VLANs.
Figure 5-5 shows the typical application of the model of E-LAN services based on 802.1q bridge. The transport network needs to carry G and H services accessed from NE2 and NE3. Both types of services converge on NE1. G and H services adopt different VLAN planning. Therefore, 802.1q bridge is used on NEs and sub-switching domains are divided based on VLANs, differentiating and separating the two types of services.
Figure 5-5 Model of E-LAN services based on 802.1q bridge

NE 2
VLAN 100
Port 1 User G2
NE 1 Port 1 User G1
VLAN 100
Port 3
VLAN 200
Transmission Network Port 3 802.1q bridge NE 3

VLAN 100
Port 2 User H2
Port 2 User H1
VLAN 200
Port 4 Transmission Network
802.1q bridge
VLAN 200
Port 1 User G3 Port 2 User H3
Port 3
802.1q bridge
NOTE
You can configure 5.2.2.3 VLAN-based E-Line Services on NE2 and NE3 for accessing services.
5.2.2.5 VLAN Forwarding Table

Generally, the VLAN IDs of VLAN-based E-Line services are not changed. If it is required to change the VLAN IDs, you need to configure a VLAN forwarding table. In the case of VLAN-based E-Line services, the VLAN IDs on the source and sink nodes are usually set to the same value. If it is required that packets carry different VLAN IDs on the source and sink nodes, the different VLAN IDs need to be set on the source and sink nodes of the E-Line services. In addition, you need to configure a VLAN forwarding table to achieve the switch of VLAN IDs at the source and sink nodes. Figure 5-6 shows an application of the VLAN forwarding table. In this figure, Service 1 carries a VLAN ID of 100, and it is transmitted to NE1 through Port 1. On a transmission network, the VLAN ID of Service 1 may be in conflict with the VLAN IDs of other services. To avoid this situation, the VLAN ID of Service 1 must be changed to another value before it is transmitted on the transmission network and then be changed to the original value after it is transmitted out of the transmission network. Therefore, a VLAN forwarding table is configured at NE1 and NE2, so that the VLAN IDs of services between Port 1 and Port 3 can be changed as required. With regard to Service 1, when it traverses NE1, the VLAN ID is changed from 100 to 200 and then changes to 100 again at NE2.
5-10
Issue 02 (2011-01-20)
Figure 5-6 Application of VLAN forwarding tables to E-Line services

NE 1 Service 1 VLAN ID: 100 Port 1 Transmission Network NE 2 Port 1 Port 3 Port 3 Service 1 VLAN ID: 100
E-Lin e
e E-Lin
Service 1 VLAN ID: 200 VLAN Forwarding Table Source Interface Port 1 Port 3 Source VLAN ID 100 200 Sink Sink Interface VLAN ID 200 Port 3 Port 1 100
VLAN Forwarding Table Source Interface Port 1 Port 3 Source VLAN ID 100 200 Sink Sink Interface VLAN ID 200 Port 3 Port 1 100
E-Line Service Information Table Source Interface Port 1 Source VLAN ID 100, 200 Sink Sink Interface VLAN ID Port 3 100, 200 Source Interface Port 1
E-Line Service Information Table Source VLAN ID 100, 200 Sink Sink Interface VLAN ID Port 3 100, 200
This section provides the specifications of VLANs that the equipment supports. Table 5-4 lists the specifications of VLANs. Table 5-4 Specifications of VLANs Item Range of VLAN IDs Number of VLAN-based ELine services Number of 802.1q bridges TAG attribute Specification 1 to 4094 1024 1 Tag aware Access Hybrida VLAN transparent transmissionb VLAN switchingc Supported Supported
Issue 02 (2011-01-20)
5-11

NOTE
l a: For the OptiX RTN 980, a tagged frame at an egress port is directly forwarded when the tag attribute of the port is set to Hybrid. l b: In VLAN transparent transmission, the VLAN ID of an Ethernet frame does not change when this frame is forwarded. l c: In VLAN switching, the VLAN ID of an Ethernet frame changes when this frame is forwarded. On the OptiX RTN 980, VLAN switching is implemented by using VLAN forwarding tables.

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
5.2.5 Availability
This section describes the support required by the application of the VLAN feature and its dependency.

Table 5-5 Hardware and version support Feature VLAN Applicable Board CSHN IFU2 IFX2 ISU2 ISX2 EM6T EM6F Applicable Hardware Version All the versions All the versions All the versions All the versions All the versions All the versions All the versions Applicable Product Version V100R003C00 and later V100R003C00 and later V100R003C00 and later V100R003C00 and later V100R003C00 and later V100R003C00 and later V100R003C00 and later
Feature Dependency
The dependency between the VLAN feature and other features is as follows: l
5-12
When the VLAN technology is used in the Layer 2 switching, 802.1q bridges are generated.
l l l
QinQ is a Layer 2 tunnel protocol based on 802.1q encapsulation. In the QinQ application, a packet carries two layers of VLAN tags. The equipment supports simple traffic classification based on VLAN priorities and complex traffic classification based on PORT+VLAN ID or PORT+VLAN ID+VLAN priority. The Ethernet frames with VLAN tags can be carried by PWs.
5.2.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 5-1. Forwards the data frame based on the service type. l In the case of the E-Line service, the Ethernet switching unit forwards the frame to the corresponding ports based on the service configuration. l In the case of the E-LAN service, the Ethernet switching unit forwards the data frame to the corresponding ports based on the MAC address table. For details, see 5.4.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 5-1.

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

l l l Allocate a unique VLAN ID for each type user. Allocate the same VLAN ID for users of the same type. 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. 5.2.8.1 Configuration Procedure (VLAN-Based E-Line Services)
This section describes the procedures for configuring the service information, port information, protection information, and QoS information of an VLAN-based E-Line service and the procedure for verifying the service configurations. 5.2.8.2 Configuration Procedure (IEEE 802.1q Bridge-Based E-LAN Services) This section describes the procedures for configuring the service information, port information, protection information, and QoS information of an IEEE 802.1q bridge-based E-LAN service and the procedure for verifying the service configurations.
5.2.8.1 Configuration Procedure (VLAN-Based E-Line Services)

This section describes the procedures for configuring the service information, port information, protection information, and QoS information of an VLAN-based E-Line service and the procedure for verifying the service configurations.
Configuration Flow Chart

Figure 5-7 provides the procedures for configuring VLAN-based E-Line services. Figure 5-7 Configuration flow chart (VLAN-based E-Line services)
Required Optional Configuring Ethernet ports Start
Configuring LAGs
Configuring E-Line services
Configuring QoS
Verifying Ethernet service configurations
End
5-14
Issue 02 (2011-01-20)
Procedures for Configuring Ethernet Ports

Table 5-6 Procedures for configuring Ethernet ports Operation Setting the parameters of Ethernet ports A.5.6.1 Setting the General Attributes of Ethernet Ports Description Required. Set the parameters as follows: l In the case of used ports, set Enable Port to Enabled. In the case of unused ports, set Enable Port to Disabled. l Set Encapsulation Type to 802.1Q. l In the case of the Ethernet port that is connected to the external equipment, set Working Mode to be the same value as the external equipment (generally, the working mode of the external equipment is auto-negotiation). In the case of the Ethernet ports within the network, set Working Mode to Auto-Negotiation. l When jumbo frames are transmitted, set Max Frame Length(byte) according to the actual length of the jumbo frames. Otherwise, it is recommended that you set Max Frame Length(byte) to 1536. A.5.6.2 Configuring the Traffic Control of Ethernet Ports Required when the flow control function is enabled on the external equipment to which the Ethernet port is connected. Set the parameters as follows: l When the external equipment uses the non-autonegotiation flow control function, set NonAutonegotiation Flow Control Mode to Enable Symmetric Flow Control. l When the external equipment uses the auto-negotiation flow control function, set Auto-Negotiation Flow Control Mode to Enable Symmetric Flow Control. A.5.6.3 Setting the Layer 2 Attributes of Ethernet Ports Required. Set the parameters as follows: l If all the accessed services carry VLAN tags (tagged frames), set TAG to Tag Aware. l If none of the accessed services carries VLAN tags (untagged frames), set TAG to Access, and set Default VLAN ID and VLAN Priority according to the network planning information. l When the accessed services contain tagged frames and untagged frames, set TAG to Hybrid, and set Default VLAN ID and VLAN Priority according to the network planning information. A.5.6.5 Setting the Advanced Attributes of Ethernet Ports Optional.
Issue 02 (2011-01-20)
5-15
Operation Setting the parameters of IF_ETH ports A.5.7.1 Setting the General Attributes of the IF_ETH Port A.5.7.2 Setting the Layer 2 Attributes of the IF_ETH Port
Description Required. Set Encapsulation Type to 802.1Q.
Required. Set the parameters as follows: l If all the accessed services carry VLAN tags (tagged frames), set Tag to Tag Aware. l If none of the accessed services carries VLAN tags (untagged frames), set Tag to Access, and set Default VLAN ID and VLAN Priority according to the network planning information. l When the accessed services contain tagged frames and untagged frames, set Tag to Hybrid, and set Default VLAN ID and VLAN Priority according to the network planning information.
A.5.7.4 Setting the Advanced Attributes of the IF_ETH Port
Optional. When the IF_ETH port transmits an Ethernet service that permits bit errors, such as a voice service or a video service, you can set Error Frame Discard Enabled to Disabled.
NOTE l For the ISU2/ISX2, it is recommended that you set Speed Transmission at L2 and Speed Transmission at L3 to Enabled, if the corresponding permission to enable the two functions is already obtained. l Set Speed Transmission at L2 and Speed Transmission at L3 consistently for both ends of a radio link.
5-16
Issue 02 (2011-01-20)
Procedures for Configuring a LAG

Table 5-7 Procedures for configuring a LAG Operation A.6.2.1 Creating a LAG Description Required if the LAG is configured to protect the FE/GE ports or if the Hybrid radio uses the N+0/XPIC configuration mode. 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 The Hybrid/AM attribute must be set to the same value for the IF ports in a LAG. l In the case of FE/GE ports, set Load Sharing to the same value as the opposite equipment. If the LAG is configured only to realize 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 Hybrid radio uses the N+0/XPIC configuration mode, 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. This parameter is valid to only LAGs whose Load Sharing is set to Non-Sharing. l Set Load Sharing Hash Algorithm to the same value as the opposite equipment. Unless otherwise specified, this parameter adopts the default value. This parameter is valid to only LAGs whose Load Sharing is set to Sharing. l It is recommended that you set the same values for the main and slave ports. In this case, you can set System Priority according to the requirements. It is recommended that this parameter adopts the default value. This parameter is valid only to static LAG. l Set Main Board, Main Port, and Selected Slave Ports according to the planning information. It is recommended that you set this parameter to the same values for the main and slave ports. A.6.2.2 Setting Parameters for LAGs Optional.
Issue 02 (2011-01-20)
5-17
Procedures for Configuring VLAN-Based E-Line Services

Table 5-8 Procedures for configuring VLAN-based E-Line services Operation A.6.3.2 Configuring UNI-UNI ELine Services Description Required. Set the parameters as follows: l Set Direction to UNI-UNI. l Set Source Port and Sink Port according to the network planning information. l Set Source VLANs and Sink VLANs according to the network planning information. The two parameters should be set to the same value. A.6.3.6 Creating a VLAN Forwarding Table Item Required when the VLAN tags of the Ethernet service need to be switched at the source and sink. The parameters need to be set according to the network planning information.
NOTE The corresponding VLAN forwarding table items need to be configured for the source port and sink port.
Procedures for Configuring QoS

Table 5-9 Procedures for configuring QoS Operation A.6.7.2 Modifying the Mapping Relationships for the DS Domain A.6.7.3 Changing the Ports Applied to a DS Domain and Their Trusted Packet Types A.6.7.1 Creating a DS Domain A.6.7.4 Creating a Port Policy Description Required when the default mapping relationships for the DS domain do not meet the actual requirements. Set the parameters according to the network planning information. For the default mapping relationships for the DS domain, see A.6.7.10 Querying the DS Domain of a Port. Required when the packet type trusted by a port is not the default trusted packet type (C-VLAN priority) applied to the DS domain. Set the parameters according to the network planning information.
Required when multiple DS domains are to be created. Set the parameters according to the network planning information. Required when you need to apply QoS policies other than DS and port shaping for a specific port. Set the parameters according to the network planning information.
Issue 02 (2011-01-20)
5-18
Operation A.6.7.6 Creating the Traffic A.6.7.7 Setting the Port That Uses the Port Policy A.6.7.8 Configuring Port Shaping
Description Required when you need to perform the ACL, CoS, CAR or shaping operation for a specific flow over the port. Set the parameters according to the network planning information. Required when the new port policy is created. Set the parameters according to the network planning information.
Required if you need to limit the egress bandwidth that an Ethernet service occupies. Set the parameters according to the network planning information.
Procedures for Verifying Ethernet Service Configurations

Table 5-10 Procedures for verifying Ethernet service configurations Operation A.6.8.1 Creating an MD Description Required in the case of the NEs where the two Ethernet ports involved in the service test are located. Set the parameters as follows: l Set Maintenance Domain Name and Maintenance Domain 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 Domain Level takes the default value 4. In the test of an Ethernet service between two internal NEs on the transport network, set Maintenance Domain Level to a value smaller than 4. In the test of an Ethernet service between two Ethernet ports on the same NE, set Maintenance Domain Level to a value smaller than the value that is set in the test of an Ethernet service between two internal NEs on the transport network. A.6.8.2 Creating an MA Required in the case of the NEs where the two Ethernet ports 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. l Set Relevant Service to the same service for the two NEs. l It is recommended that you set CC Test Transmit Period to 1s.
Issue 02 (2011-01-20)
5-19
Operation A.6.8.3 Creating an MEP Point
Description Required in the case of the NEs where the two Ethernet ports 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 Board and Port to the Ethernet ports that are involved in the service test. l Set MEP ID to different values for MEPs in the same MD. l If the OAM information initiated by the MEP travels through the packet switching unit on the local NE, set Direction of the MEP to Ingress. Otherwise, set Direction to Egress. l The MEP ID is used to identify the MEP during the LB test. Therefore, set CC Status to Active.
A.6.8.4 Creating Remote MEPs in an MA
Required in the case of the NE where the Ethernet ports involved in the OAM operation 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 value of Maintenance Association Name that is set in the preceding step. l To ensure that an MEP can respond to the OAM operations initiated by the other MEPs in the same MA, you need to set the other MEPs to be the remote MEPs of this MEP.
Perform an LB test to test the Ethernet service configurations
Required. The LB test result should show that no packet loss occurs.
5.2.8.2 Configuration Procedure (IEEE 802.1q Bridge-Based E-LAN Services)

This section describes the procedures for configuring the service information, port information, protection information, and QoS information of an IEEE 802.1q bridge-based E-LAN service and the procedure for verifying the service configurations.

Figure 5-8 provides the procedures for configuring IEEE 802.1q bridge-based E-LAN services.
5-20
Issue 02 (2011-01-20)
Figure 5-8 Configuration flow chart (IEEE 802.1q bridge-based E-LAN services)
Configuring LAGs
Configuring ERPS protection
Configuring E-LAN services
Configuring QoS
End
The detailed information about the procedures in the flow chart is provided as follows.
Issue 02 (2011-01-20)
5-21

Table 5-11 Procedures for configuring Ethernet ports Operation Setting the parameters of Ethernet ports A.5.6.1 Setting the General Attributes of Ethernet Ports Description Required. Set the parameters as follows: l In the case of used ports, set Enable Port to Enabled. In the case of unused ports, set Enable Port to Disabled. l Set Encapsulation Type to 802.1Q. l In the case of the Ethernet port that is connected to the external equipment, set Working Mode to be the same value as the external equipment (generally, the working mode of the external equipment is auto-negotiation). In the case of the Ethernet ports within the network, set Working Mode to Auto-Negotiation. l When jumbo frames are transmitted, set Max Frame Length(byte) according to the actual length of the jumbo frames. Otherwise, it is recommended that you set Max Frame Length(byte) to 1536. A.5.6.2 Configuring the Traffic Control of Ethernet Ports A.5.6.3 Setting the Layer 2 Attributes of Ethernet Ports For ports that carry E-LAN services, the flow control function is always disabled.
Required. Set the parameters as follows: l If all the accessed services carry VLAN tags (tagged frames), set TAG to Tag Aware. l If none of the accessed services carries VLAN tags (untagged frames), set TAG to Access, and set Default VLAN ID and VLAN Priority according to the network planning information. l When the accessed services contain tagged frames and untagged frames, set TAG to Hybrid, and set Default VLAN ID and VLAN Priority according to the network planning information.
A.5.6.5 Setting the Advanced Attributes of Ethernet Ports
Required when you need to enable the port self-loop test and automatic loopback shutdown functions or to enable the broadcast packet suppression function. Set Loopback Check, Loopback Port Shutdown, Enabling Broadcast Packet Suppression, and Broadcast Packet Suppression Threshold according to the requirements.
5-22
Issue 02 (2011-01-20)
Procedures for Configuring ERPS Protection

Table 5-12 Procedures for configuring ERPS protection Operation A.6.1.1 Creating Ethernet Ring Protection Instances Description Required when an Ethernet ring needs to be protected and service loops need to be avoided on the Ethernet ring.
Issue 02 (2011-01-20)
5-23
Operation A.6.1.2 Setting the Parameters of Ethernet Ring Protocol
Description Required if the values of the default parameters of the ERPS timers need to be changed. Set Hold-Off Time(ms), Guard Time(ms), WTR Time(mm:ss), and Packet Transmit Interval(s) according to the actual requirements. Set these parameters to the same values for all the NEs on the network.

Table 5-13 Procedures for configuring a LAG Operation A.6.2.1 Creating a LAG Description Required if the LAG is configured to protect the FE/GE ports or if the Hybrid radio uses the N+0/XPIC configuration mode. 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 The Hybrid/AM attributes must be set to the same value for the IF ports in a LAG. l In the case of FE/GE ports, set Load Sharing to the same value as the opposite equipment. If the LAG is configured only 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 the bandwidth, it is recommended that you set Load Sharing to Sharing for the equipment at both ends. l When the Hybrid radio uses the N+0/XPIC configuration mode, 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. This parameter is valid to only LAGs whose Load Sharing is set to Non-Sharing. l Set Load Sharing Hash Algorithm 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 the main and slave ports of the LAG at the local end take the same settings as the main and slave ports of the LAG at the opposite end. In this case, you can set System Priority according to the actual requirements. It is recommended that this parameter takes the default value. This parameter is valid to only static LAGs. l Set Main Board, Main Port, and Selected Slave Ports according to the planning information. It is recommended that the same main and slave ports are used for the LAGs at both ends.
5-24
Issue 02 (2011-01-20)
Operation A.6.2.2 Setting Parameters for LAGs
Description Optional.
Procedures for Configuring IEEE 802.1q Bridge-Based E-LAN Services

Table 5-14 Procedures for configuring IEEE 802.1q bridge-based E-LAN services Operation A.6.3.9 Configuring IEEE 802.1q Bridge-Based ELAN Services Description Required. Set the parameters as follows: l Set Tag Type to C-Awared. l Set Self-Learning MAC Address to Enabled according to the planning information. l In the UNI tab page, set the parameters according to the planning information. l To disable the packet forwarding between certain E-LAN service ports, add the ports to Split Horizon Group Member. Managing the MAC address table A.6.4.2 Creating a Blacklist Entry of MAC Addresses A.6.4.1 Creating a Static MAC Address Entry A.6.4.3 Configuring the Aging Parameters of a MAC Address Table A.6.5 Setting the Mode for Processing an Unknown Frame of the E-LAN Service Required when usage of E-LAN services needs to be disabled on certain MAC address host. Set the parameters according to the network planning information.
Required if you need to set certain MAC address entries not to age. Set the parameters according to the network planning information. Required if the aging function needs to be disabled or if the default aging time (five minutes) needs to be changed. Set the parameters according to the network planning information.
Optional.
Issue 02 (2011-01-20)
5-25

Table 5-15 Procedures for configuring QoS Operation A.6.7.2 Modifying the Mapping Relationships for the DS Domain A.6.7.3 Changing the Ports Applied to a DS Domain and Their Trusted Packet Types A.6.7.1 Creating a DS Domain A.6.7.4 Creating a Port Policy A.6.7.6 Creating the Traffic A.6.7.7 Setting the Port That Uses the Port Policy A.6.7.8 Configuring Port Shaping Description Required when the default mapping relationships for the DS domain do not meet the actual requirements. Set the parameters according to the network planning information. For the default mapping relationships for the DS domain, see A.6.7.10 Querying the DS Domain of a Port. Required when the packet type trusted by a port is not the default trusted packet type (C-VLAN priority) applied to the DS domain. Set the parameters according to the network planning information.
Required when multiple DS domains are to be created. Set the parameters according to the network planning information. Required when you need to apply QoS policies other than DS and port shaping for a specific port. Set the parameters according to the network planning information. Required when you need to perform the ACL, CoS, CAR or shaping operation for a specific flow over the port. Set the parameters according to the network planning information. Required when the new port policy is created. Set the parameters according to the network planning information.
5-26
Issue 02 (2011-01-20)

Table 5-16 Procedures for verifying Ethernet service configurations Operation A.6.8.1 Creating an MD Description Required in the case of the NEs where the two Ethernet ports involved in the service test are located. Set the parameters as follows: l Set Maintenance Domain Name and Maintenance Domain 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 Domain Level takes the default value 4. In the test of an Ethernet service between two internal NEs on the transport network, set Maintenance Domain Level to a value smaller than 4. In the test of an Ethernet service between two Ethernet ports on the same NE, set Maintenance Domain Level to a value smaller than the value that is set in the test of an Ethernet service between two internal NEs on the transport network. A.6.8.2 Creating an MA Required in the case of the NEs where the two Ethernet ports 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. l Set Relevant Service to the same service for the two NEs. l It is recommended that you set CC Test Transmit Period to 1s. A.6.8.3 Creating an MEP Point Required in the case of the NEs where the two Ethernet ports 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 Board and Port to the Ethernet ports that are involved in the service test. l Set MEP ID to different values for MEPs in the same MD. l If the OAM information initiated by the MEP travels through the packet switching unit on the local NE, set Direction of the MEP to Ingress. Otherwise, set Direction to Egress. l The MEP ID is used to identify the MEP during the LB test. Therefore, set CC Status to Active.
Issue 02 (2011-01-20)
5-27
Operation A.6.8.4 Creating Remote MEPs in an MA
Description Required in the case of the NE where the Ethernet ports involved in the OAM operation 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 value of Maintenance Association Name that is set in the preceding step. l To ensure that an MEP can respond to the OAM operations initiated by the other MEPs in the same MA, you need to set the other MEPs to be the remote MEPs of this MEP.

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 l For details on the configuration example of an E-Line service based on the VLAN, see Configuration Example (VLAN-Based E-Line Service) in the Configuration Guide. For details on the configuration example of an E-LAN service based on the VLAN, see Configuration Example (802.1q-Bridge-Based E-LAN Service) in the Configuration Guide.

This section provides the hyperlinks of the operation tasks associated with VLANs.
Related Tasks
A.5.6.1 Setting the General Attributes of Ethernet Ports A.5.6.3 Setting the Layer 2 Attributes of Ethernet Ports A.5.7.1 Setting the General Attributes of the IF_ETH Port A.5.7.2 Setting the Layer 2 Attributes of the IF_ETH Port A.6.3.2 Configuring UNI-UNI E-Line Services A.6.3.6 Creating a VLAN Forwarding Table Item A.6.3.9 Configuring IEEE 802.1q Bridge-Based E-LAN Services A.5.6.1 Setting the General Attributes of Ethernet Ports A.5.7.1 Setting the General Attributes of the IF_ETH Port
5-28
Issue 02 (2011-01-20)

There are no alarms or performance events relevant to VLANs.
Relevant Alarms
None.
Relevant Events
None.
5.2.12 FAQs
This section provides the answers to the questions that are frequently raised when the VLAN feature is used. 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.
5.3 QinQ
This chapter describes the QinQ (802.Q in 802.Q) feature. 5.3.1 Introduction This section provides the definition of QinQ and its purpose. 5.3.2 Basic Concepts This section describes the basic concepts associated with QinQ. 5.3.3 Specifications This section describes the specifications of QinQ. 5.3.4 Reference Standards and Protocols This section describes the standards and protocols associated with QinQ. 5.3.5 Availability This section describes the support required by QinQ and dependency of the feature. 5.3.6 Principles The working principle of QinQ is closely related to service types. 5.3.7 Planning Guidelines Follow certain principles when you plan QinQ. 5.3.8 Configuration Procedure The configuration procedure of QinQ-based Ethernet services is closely associated with the types of Ethernet services. 5.3.9 Configuration Example This section uses examples to describe how to plan and configure QinQ-based Ethernet services according to the network conditions.
5.3.10 Task Collection This section provides the hyperlinks of the operation tasks associated with QinQ. 5.3.11 Relevant Alarms and Events No alarms or performance events are associated with QinQ. 5.3.12 FAQs This section provides answers to the questions that are frequently asked when the QinQ feature is used.
5.3.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 5-9 shows the application of QinQ. Figure 5-9 Application of QinQ in E-Line 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).

This section describes the basic concepts associated with QinQ. 5.3.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. 5.3.2.2 QinQ-Based E-Line Services S-VLAN tags can be used to isolate E-Line services. Therefore, multiple E-Line services can share one physical channel. These services are QinQ-based E-Line services. 5.3.2.3 E-LAN Services Based on 802.1ad Bridge S-VLAN tags can be used to isolate E-LAN services. Therefore, a bridge is divided into multiple independent sub-switching domains. These services are E-LAN services based on 802.1ad bridge.
5.3.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 5-10 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
Issue 02 (2011-01-20)
5-31
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 The TPID is different. 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 5-11 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 5-12 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
5.3.2.2 QinQ-Based E-Line Services

S-VLAN tags can be used to isolate E-Line services. Therefore, multiple E-Line services can share one physical channel. These services are QinQ-based E-Line services.
NOTE
6.8.2.4 E-Line Services Carried on PWs describes QinQ-based E-Line services carried by PWs.
5-32
Issue 02 (2011-01-20)
Model of Service
Table 5-17 shows the models of QinQ-based E-Line services. Table 5-17 Models of QinQ-based E-Line Services Model of Service Model 1 Flow of Service PORT (source) QinQ link (sink) Direction UNI-NNI Encapsulation Mode of a Port Null (source) QinQ (sink) Description of Service The source port adds the S-VLAN tag that corresponds to the QinQ link to all the Ethernet frames, and then transmits the Ethernet frames to the sink port where the QinQ link is configured. The source port accesses only the Ethernet frames that carry C-VLAN tags. It adds the S-VLAN tag that corresponds to the QinQ link to all the Ethernet frames, and then transmits the Ethernet frames to the sink port where the QinQ link is configured. The source port adds the S-VLAN tag that corresponds to the QinQ link to all the Ethernet frames that carry specific CVLAN tags, and then transmits the Ethernet frames to the sink port where the QinQ link is configured.
Model 2
PORT (source) QinQ link (sink)
UNI-NNI
802.1Q (source)a QinQ (sink)
Model 3
PORT+C-VLAN (source) QinQ link (sink)
UNI-NNI
802.1Q (source)a QinQ (sink)
Issue 02 (2011-01-20)
5-33
Model of Service Model 4
Flow of Service QinQ link (source) QinQ link (sink)
Direction NNI-NNI
Encapsulation Mode of a Port QinQ (sink) QinQ (sink)
Description of Service The source port transmits the Ethernet frames that carry the S-VLAN tag to the sink port where the sink QinQ link is configured. The S-VLAN tag carried in the Ethernet frames corresponds to the source QinQ link. If the source and sink QinQ links correspond to different S-VLAN tags, the S-VLAN tags carried in the Ethernet frames are exchanged.
NOTE
a: Set TAG to Tag Aware.
Figure 5-13 shows the typical application of service model 1. Service 1 and Service 2 include tagged frames and untagged frames. Service 1 is accessed to NE1 through Port 1, and Service 2 is accessed to NE1 through Port 2. Port 1 adds the corresponding S-VLAN tag to Service 1, and Port 2 adds the corresponding S-VLAN tag to Service 2. Then, Service 1 and Service 2 are transmitted to Port 3. Port 3 transmits Service 1 and Service 2 to NE2. NE2 processes Service 1 and Service 2 in the same manner as NE1. Figure 5-13 Typical application of service model 1
NE 1 Port 1 Service 1 Service 2 Port 2
Strip S-VLAN Label Data( 1) Data(2)
NE 2 Port 3 Transmission Network Port 3

E-Line
E-Line
e E-Lin
Port 1 Service 1 Service 2 Port 2
E-Lin e
Add S-VLAN Label S-VLAN(300) S-VLAN(400) Data(1) Data(2)
Add S-VLAN Label S-VLAN(300) S-VLAN(400) Data(1) Data(2)
Strip S-VLAN Label Data(1) Data(2)
5-34
Issue 02 (2011-01-20)
Figure 5-14 shows the typical application of service model 2. Service 1 and Service 2 carry different unknown C-VLAN tags. Service 1 is accessed to NE1 through Port 1, and Service 2 is accessed to NE1 through Port 2. Port 1 adds the corresponding S-VLAN tag to Service 1, and Port 2 adds the corresponding S-VLAN tag to Service 2. Then, Service 1 and Service 2 are transmitted to Port 3. Port 3 transmits Service 1 and Service 2 to NE2. NE2 processes Service 1 and Service 2 in the same manner as NE1. Figure 5-14 Typical application of service model 2
Strip S-VLAN Label C-VLAN C-VLAN Data( 1) Data(2) Add S-VLAN Label S-VLAN(300) S-VLAN(400) C-VLAN C-VLAN Data(1) Data(2)
NE 1 Service 1 Unknown CVLAN Service 2 Unknown CVLAN Port 1

E-Line
E-Line
e E-Lin
Port 1
Service 1 Unknown CVLAN Service 2 Unknown CVLAN
Port 2
E-Lin e
Port 2
Add S-VLAN Label S-VLAN(300) S-VLAN(400) C-VLAN C-VLAN Data(1) Data(2)
Strip S-VLAN Label C-VLAN C-VLAN Data( 1) Data(2)
Figure 5-15 shows the typical application of service model 3. Service 1 and Service 2 carry different C-VLAN tags. Service 1 is accessed to NE1 through Port 1, and Service 2 is accessed to NE1 through Port 2. Port 1 adds the corresponding S-VLAN tag to Service 1, and Port 2 adds the corresponding S-VLAN tag to Service 2. Then, Service 1 and Service 2 are transmitted to Port 3. Port 3 transmits Service 1 and Service 2 to NE2. NE2 processes Service 1 and Service 2 in the same manner as NE1. Figure 5-15 Typical application of service model 3
Strip S-VLAN Label C-VLAN(100) C-VLAN(200) Data( 1) Data(2) Add S-VLAN Label S-VLAN(300) S-VLAN(400) C-VLAN(100) C-VLAN(200) Data(1) Data(2)
NE 1 Service 1 VLAN ID: 100 Service 2 VLAN ID: 200 Port 1

E-Line
E-Line
e E-Lin
Port 1
Port 2
E-Lin e
Service 2 Port 2 VLAN ID: 200

Strip S-VLAN Label C-VLAN(100) C-VLAN(200) Data( 1) Data(2)
Add S-VLAN Label S-VLAN(300) S-VLAN(400) C-VLAN(100) C-VLAN(200) Data(1) Data(2)
Figure 5-16 shows the typical application of service model 4.

Service 1 and Service 2 carry a same S-VLAN tag. Service 1 is accessed to NE1 through Port 1, and Service 2 is accessed to NE1 through Port 2. Port 1 changes the S-VLAN tag carried in Service 1 and Port 2 changes the S-VLAN tag carried in Service 2 so that the S-VLAN tags carried in Service 1 and Service 2 are different. Port 3 transmits Service 1 and Service 2 to NE2. NE2 processes Service 1 and Service 2 in the same manner as NE1. Figure 5-16 Typical application of service model 4
Switching S-VLAN Label S-VLAN(100) S-VLAN(100) Data( 1) Data(2) S-VLAN(300) S-VLAN(400) Data(1) Data(2)
NE 1 Service 1 S-VLAN ID: 100 Service 2 S-VLAN ID: 100 Port 1

E-Line
E-Line
e E-Lin
Port 1
Service 1 S-VLAN ID: 100
Port 2
E-Lin e
Service 2 Port 2 S-VLAN ID: 100
Switching S-VLAN Label S-VLAN(300) S-VLAN(400) Data( 1) Data(2) S-VLAN(100) S-VLAN(100) Data(1) Data(2)
5.3.2.3 E-LAN Services Based on 802.1ad Bridge

S-VLAN tags can be used to isolate E-LAN services. Therefore, a bridge is divided into multiple independent sub-switching domains. These services are E-LAN services based on 802.1ad bridge.
Model of Service
Table 5-18 shows the models of E-LAN services based on 802.1ad bridge. Table 5-18 Models of E-LAN services based on 802.1ad bridge Type of Services E-LAN services based on 802.1ad bridge Tag Attribute Encapsulation Mode of Port Null or 802.1q (UNI port) a QinQ (NNI port) Type of Logical Port PORT (The encapsulation mode of the UNI port is Null.) PORT or PORT +C-VLAN (The encapsulation mode of the UNI port is 802.1q.) a PORT+SVLAN (NNI port)
Learning Mode IVL
SubSwitching Domain Sub-switching domains are divided based on S-VLAN tags.
S-Awared
NOTE
a: When the encapsulation mode of port is 802.1q, the tag attribute must be Tag Aware.
Figure 5-17 shows the typical application of the model of service. The transmission network needs to carry G and H services accessed from NE2 and NE3. The two types of services are converged on NE1. Since G and H services have a same C-VLAN tag, you need to add different S-VLAN tags to G and H services for service isolation. Figure 5-17 Model of E-LAN services based on 802.1ad bridge
NE 2
Add S-VLAN Label S-VLAN(300) S-VLAN(400) C-VLAN(100) C-VLAN(100) Data(G) Data(H) Strip S-VLAN Label C-VLAN(100) C-VLAN(100) Data( G) Data(H)
NE 2
SVLAN 300
Port 1 User G2 Port 3 NE 1

SVLAN 300 SVLAN 400 CVLAN 100
Transmission Network Port 3 802.1ad bridge
Port 2 User H2
CVLAN 100
Port 1 User G1
CVLAN 100 SVLAN 400
User H1
Port 2 Port 4 802.1ad bridge Transmission Network
NE 3
SVLAN 300
CVLAN 100
Port 1 User G3
CVLAN 100 SVLAN 400
NE 1
Strip S-VLAN Label C-VLAN(100) C-VLAN(100) Data( G) Data(H) Add S-VLAN Label S-VLAN(300) S-VLAN(400) C-VLAN(100) C-VLAN(100) Data(G) Data(H)
Port 3
Port 2 User H3
CVLAN 100
802.1ad bridge NE 3
Strip S-VLAN Label C-VLAN(100) C-VLAN(100) Data( G) Data(H)
Add S-VLAN Label S-VLAN(300) S-VLAN(400) C-VLAN(100) C-VLAN(100) Data(G) Data(H)
NOTE
You can configure 5.3.2.2 QinQ-Based E-Line Services on NE2 and NE3 for service access.
This section describes the specifications of QinQ.
Table 5-19 lists the specifications of QinQ. Table 5-19 Specifications of QinQ Item Setting of the QinQ type field Range of S-VLAN IDs Number of QinQ-based E-Line services Number of QinQ-based E-LAN services Number of QinQ links Type of service flows carried by QinQ links Specifications Supported. The default value is 88A8. 1 to 4094 1024 1 1024 PORT PORT+CVLAN PORT+SVLAN Type of logical ports mounted to the 802.1ad bridge PORT (The port encapsulation type of the UNI port is Null.) PORT or PORT+CVLAN (The port encapsulation type of the UNI port is 802.1Q.a PORT+SVLAN (NNI port)
NOTE a: If the port encapsulation type is 802.1Q, set TAG to Tag Aware.
QinQ operation type (QinQ-based E-Line services)
Adding S-VLAN tags (UNI-NNI) Stripping S-VLAN tags (NNI-UNI) Transparently transmitting S-VLAN tags (NNI-NNI) Switching S-VLAN tags (NNI-NNI)
QinQ operation type (QinQ-based E-LAN services)
Adding S-VLAN tags based on PORT (UNI port) Adding S-VLAN tags based on PORT+CVLAN (UNI port) Mounting ports based on PORT+S-VLAN (NNI port)

This section describes the standards and protocols associated with QinQ. The following protocols are associated with QinQ: l l
5-38
IEEE 802.1q: Virtual Bridged Local Area Networks IEEE 802.1ad: Virtual Bridged Local Area Networks Amendment 4: Provider Bridges
5.3.5 Availability
This section describes the support required by QinQ and dependency of the feature.

Table 5-20 Hardware and version support Feature QinQ Applicable Board CSHN IFU2 IFX2 ISU2 ISX2 EM6T EM6F Applicable Hardware Version All the versions All the versions All the versions All the versions All the versions All the versions All the versions Applicable Product Version V100R003C00 and later V100R003C00 and later V100R003C00 and later V100R003C00 and later V100R003C00 and later V100R003C00 and later V100R003C00 and later
Feature Dependency
The dependency between the QinQ feature and other features is as follows: l l QinQ-based Ethernet LAN services depend on the 802.1ad bridge. QinQ-based E-Line services can be carried by PWs.
5.3.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 5-18 to describe how data frames are processed on a QinQ network.
Issue 02 (2011-01-20)
5-39
Figure 5-18 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
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 5-19 to describe how data frames are processed on the 802.1ad bridge.
5-40
Issue 02 (2011-01-20)
Figure 5-19 EVPLAN (802.1ad Bridge) Service Example

NE1 VoIP NE3
PORT1 VCTRUNK1
NodeB 1
PORT1
Service C-VLAN 10 VoIP 20 HSI
HSI
PORT2
NE2
VCTRUNK2
NodeB 2
PORT1
Service C-VLAN VoIP 30 HSI 40

NE1 PORT1 NodeB 1
NE3:EMS6 S-VLAN 100 PORT1 VoIP S-VLAN 200 PORT2 HSI VCTRUNK1
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)
As shown in Figure 5-19, 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.
Issue 02 (2011-01-20)
5-41
Planning Guidelines of S-VLAN Tags

Follow these principles when planning S-VLAN tags: l l The S-VLAN tag allocated to each customer must be unique. If a customer has various services that need to be transmitted to different destinations, a unique S-VLAN ID must be allocated to each type of service.
Planning Guidelines of QinQ-Based E-Line Services

Follow these principles when planning QinQ-based Ethernet E-Line services: l l l If the VLAN tag need not be detected on an ingress port, create UNI-NNI E-Line services. The encapsulation type of the UNI port is set to Null. If only the services that carry VLAN tags can be accessed to the NE, create UNI-NNI ELine services based on PORT. The encapsulation mode of the UNI port is set to 802.1Q. If only the services that carry specific C-VLAN tags can be accessed to the NE, create UNINNI E-Line services based on PORT+C-VLAN. The encapsulation mode of the UNI port is set to 802.1Q. If the services that carry S-VLAN tags need to be accessed to the NE or the S-VLAN tags carried in the services need to be switched, create NNI-NNI E-Line services.
Planning Guidelines of QinQ-Based E-LAN Services

Follow these principles when planning QinQ-based E-LAN services: l l l l If the packet that enters the port does not contain a VLAN tag, or contains a C-VLAN tag, set the network attribute of the port to UNI. If the packet that enters the port contains an S-VLAN tag, plan the network attribute of the port as NNI. In the case of a UNI port, create services based on PORT or PORT+C-VLAN. In the case of an NNI port, create services based on PORT+S-VLAN.
In the case of the OptiX RTN 980, follow these principles when planning QinQ: l l QinQ-based E-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. 5.3.8.1 Configuration Procedure (QinQ-Based E-Line Services) This section describes the procedures for configuring the service information, port information, protection information, and QoS information of a QinQ-based E-Line service and the procedure for verifying the service configurations. 5.3.8.2 Configuration Procedure (IEEE 802.1ad Bridge-Based E-LAN Services)
This section describes the procedures for configuring the service information, port information, protection information, and QoS information of an IEEE 802.1ad bridge-based E-LAN service and the procedure for verifying the service configurations.
5.3.8.1 Configuration Procedure (QinQ-Based E-Line Services)

This section describes the procedures for configuring the service information, port information, protection information, and QoS information of a QinQ-based E-Line service and the procedure for verifying the service configurations.

Figure 5-20 provides the procedures for configuring QinQ-based E-Line services. Figure 5-20 Configuration flow chart (QinQ-based E-Line services)
Configuring LAGs
Configuring E-Line services
Configuring QoS
End
Issue 02 (2011-01-20)
5-43

Table 5-21 Procedures for configuring Ethernet ports Operation Setting the parameters of Ethernet ports Description A.5.6.1 Setting the General Attributes of Ethernet Ports Required. Set the parameters as follows: l In the case of used ports, set Enable Port to Enabled. In the case of unused ports, set Enable Port to Disabled. l When jumbo frames are transmitted, set Max Frame Length(byte) according to the actual length of the jumbo frames. Otherwise, it is recommended that you set Max Frame Length (byte) to 1536. A.5.6.2 Configuring the Traffic Control of Ethernet Ports Required when the flow control function is enabled on the external equipment to which the Ethernet port is connected. Set the parameters as follows: l When the external equipment uses the nonauto-negotiation flow control function, set NonAutonegotiation Flow Control Mode to Enable Symmetric Flow Control. l When the external equipment uses the autonegotiation flow control function, set AutoNegotiation Flow Control Mode to Enable Symmetric Flow Control.
5-44
Issue 02 (2011-01-20)
Operation
Description A.5.6.3 Setting the Layer 2 Attributes of Ethernet Ports Required. In the case of an NNI that is connected to the external equipment, set QinQ Type Domain according to the TPID of the S-VLAN that is supported by the external equipment. In the case of NNIs within the network, QinQ Type Domain takes the default value. Optional.
A.5.6.5 Setting the Advanced Attributes of Ethernet Ports Setting the parameters of IF_ETH ports A.5.7.1 Setting the General Attributes of the IF_ETH Port A.5.7.2 Setting the Layer 2 Attributes of the IF_ETH Port
Required. Set Encapsulation Type to QinQ. Optional. In the case of an NNI that is connected to the external equipment, set QinQ Type Domain according to the TPID of the S-VLAN that is supported by the external equipment. In the case of NNIs within the network, QinQ Type Domain takes the default value. Optional.
Issue 02 (2011-01-20)
5-45

Table 5-22 Procedures for configuring a LAG Operation A.6.2.1 Creating a LAG Description Required if the LAG is configured to protect the FE/GE ports or if the Hybrid radio uses the N+0/XPIC configuration mode. 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 The Hybrid/AM attributes must be set to the same value for the IF ports in a LAG. l In the case of FE/GE ports, set Load Sharing to the same value as the opposite equipment. If the LAG is configured only 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 the bandwidth, it is recommended that you set Load Sharing to Sharing for the equipment at both ends. l When the Hybrid radio uses the N+0/XPIC configuration mode, 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. This parameter is valid to only LAGs whose Load Sharing is set to Non-Sharing. l Set Load Sharing Hash Algorithm 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 the main and slave ports of the LAG at the local end take the same settings as the main and slave ports of the LAG at the opposite end. In this case, you can set System Priority according to the actual requirements. It is recommended that this parameter takes the default value. This parameter is valid to only static LAGs. l Set Main Board, Main Port, and Selected Slave Ports according to the planning information. It is recommended that the same main and slave ports are used for the LAGs at both ends. A.6.2.2 Setting Parameters for LAGs Optional.
5-46
Issue 02 (2011-01-20)
Procedures for Configuring QinQ-Based E-Line Services

Table 5-23 Procedures for configuring QinQ-based E-Line services Operation A.6.3.1 Configuring the QinQ Link A.6.3.4 Configuring UNI-NNI ELine Services (Carried by QinQ Links) Description Required. Set the parameters according to the network planning information. Required. Set the parameters according to the network planning information.

Table 5-24 Procedures for configuring QoS Operation A.6.7.2 Modifying the Mapping Relationships for the DS Domain A.6.7.3 Changing the Ports Applied to a DS Domain and Their Trusted Packet Types A.6.7.1 Creating a DS Domain A.6.7.4 Creating a Port Policy A.6.7.6 Creating the Traffic Description Required when the default mapping relationships for the DS domain do not meet the actual requirements. Set the parameters according to the network planning information. For the default mapping relationships for the DS domain, see A.6.7.10 Querying the DS Domain of a Port. Required when the packet type trusted by a port is not the default trusted packet type (C-VLAN priority) applied to the DS domain. Set the parameters according to the network planning information.
Required when multiple DS domains are to be created. Set the parameters according to the network planning information. Required when you need to apply QoS policies other than DS and port shaping for a specific port. Set the parameters according to the network planning information. Required when you need to perform the ACL, CoS, CAR or shaping operation for a specific flow over the port. Set the parameters according to the network planning information.
Issue 02 (2011-01-20)
5-47
Operation A.6.7.7 Setting the Port That Uses the Port Policy A.6.7.8 Configuring Port Shaping
Description Required when the new port policy is created. Set the parameters according to the network planning information.

Table 5-25 Procedures for verifying Ethernet service configurations Operation A.6.8.1 Creating an MD Description Required in the case of the NEs where the two Ethernet ports involved in the service test are located. Set the parameters as follows: l Set Maintenance Domain Name and Maintenance Domain 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 Domain Level takes the default value 4. In the test of an Ethernet service between two internal NEs on the transport network, set Maintenance Domain Level to a value smaller than 4. In the test of an Ethernet service between two Ethernet ports on the same NE, set Maintenance Domain Level to a value smaller than the value that is set in the test of an Ethernet service between two internal NEs on the transport network. A.6.8.2 Creating an MA Required in the case of the NEs where the two Ethernet ports 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. l Set Relevant Service to the same service for the two NEs. l It is recommended that you set CC Test Transmit Period to 1s.
5-48
Issue 02 (2011-01-20)
Description Required in the case of the NEs where the two Ethernet ports 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 Board and Port to the Ethernet ports that are involved in the service test. l Set MEP ID to different values for MEPs in the same MD. l If the OAM information initiated by the MEP travels through the packet switching unit on the local NE, set Direction of the MEP to Ingress. Otherwise, set Direction to Egress. l The MEP ID is used to identify the MEP during the LB test. Therefore, set CC Status to Active.
Required in the case of the NE where the Ethernet ports involved in the OAM operation 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 value of Maintenance Association Name that is set in the preceding step. l To ensure that an MEP can respond to the OAM operations initiated by the other MEPs in the same MA, you need to set the other MEPs to be the remote MEPs of this MEP.
5.3.8.2 Configuration Procedure (IEEE 802.1ad Bridge-Based E-LAN Services)


Figure 5-21 provides the procedures for configuring IEEE 802.1ad bridge-based E-LAN services.
Issue 02 (2011-01-20)
5-49
Figure 5-21 Configuration flow chart (IEEE 802.1ad bridge-based E-LAN services)
Configuring LAGs
Configuring QoS
End
5-50
Issue 02 (2011-01-20)

Table 5-26 Procedures for configuring Ethernet ports Operation Setting the parameters of Ethernet ports A.5.6.1 Setting the General Attributes of Ethernet Ports Description Required. Set the parameters as follows: l In the case of used ports, set Enable Port to Enabled. In the case of unused ports, set Enable Port to Disabled. l If a UNI can access untagged frames, set Encapsulation Type to Null. If a UNI can access tagged frames only, set Encapsulation Type to 802.1Q. l In the case of an NNI, set Encapsulation Type to QinQ. l In the case of the Ethernet port that is connected to the external equipment, set Working Mode to be the same value as the external equipment (generally, the working mode of the external equipment is auto-negotiation). In the case of the Ethernet ports within the network, set Working Mode to Auto-Negotiation. l When jumbo frames are transmitted, set Max Frame Length(byte) according to the actual length of the jumbo frames. Otherwise, it is recommended that you set Max Frame Length(byte) to 1536. A.5.6.2 Configuring the Traffic Control of Ethernet Ports A.5.6.3 Setting the Layer 2 Attributes of Ethernet Ports For ports that carry E-LAN services, the flow control function is always disabled.
Required. Set the parameters as follows: l In the case of a UNI, if Encapsulation Type is set to 802.1Q, set TAG to Tag Aware (default value). l In the case of an NNI that is connected to the external equipment, set QinQ Type Domain according to the TPID of the SVLAN that is supported by the external equipment. Required when you need to enable the port self-loop test and automatic loopback shutdown functions or to enable the broadcast packet suppression function. Set Loopback Check, Loopback Port Shutdown, Enabling Broadcast Packet Suppression, and Broadcast Packet Suppression Threshold according to the requirements.
Issue 02 (2011-01-20)
5-51
Description Required. l If a UNI can access untagged frames, set Encapsulation Type to Null. If a UNI can access tagged frames only, set Encapsulation Type to 802.1Q. l In the case of an NNI, set Encapsulation Type to QinQ.
Required. Set the parameters as follows: l In the case of a UNI, if Encapsulation Type is set to 802.1Q, set Tag to Tag Aware (default value). l In the case of an NNI that is connected to the external equipment, set QinQ Type Domain according to the TPID of the SVLAN that is supported by the external equipment. In the case of an NNI within the network, QinQ Type Domain takes the default value. Optional. When the IF_ETH port transmits an Ethernet service that permits bit errors, such as a voice service or a video service, you can set Error Frame Discard Enabled to Disabled.

Table 5-27 Procedures for configuring ERPS protection Operation A.6.1.1 Creating Ethernet Ring Protection Instances A.6.1.2 Setting the Parameters of Ethernet Ring Protocol Description Required when an Ethernet ring needs to be protected and service loops need to be avoided on the Ethernet ring.
Required if the values of the default parameters of the ERPS timers need to be changed. Set Hold-Off Time(ms), Guard Time(ms), WTR Time(mm:ss), and Packet Transmit Interval(s) according to the actual requirements. Set these parameters to the same values for all the NEs on the network.
5-52
Issue 02 (2011-01-20)

Issue 02 (2011-01-20)
5-53
Procedures for Configuring IEEE 802.1ad Bridge-Based E-LAN Services

Table 5-29 Procedures for configuring IEEE 802.1ad bridge-based E-LAN services Operation A.6.3.10 Configuring IEEE 802.1ad Bridge-Based ELAN Services Description Required. Set the parameters as follows: l Set Tag Type to S-Awared. l Set Self-Learning MAC Address to Enabled according to the planning information. l In the UNI and NNI tab pages, set the parameters according to the planning information. l To disable the packet forwarding between certain E-LAN service ports, add the ports to Split Horizon Group Member. Managing the MAC address table A.6.4.2 Creating a Blacklist Entry of MAC Addresses A.6.4.1 Creating a Static MAC Address Entry A.6.4.3 Configuring the Aging Parameters of a MAC Address Table A.6.5 Setting the Mode for Processing an Unknown Frame of the E-LAN Service Required when usage of E-LAN services needs to be disabled on certain MAC address host. Set the parameters according to the network planning information.
Optional.
5-54
Issue 02 (2011-01-20)

Issue 02 (2011-01-20)
5-55

5-56
Issue 02 (2011-01-20)

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 E-Line service, see Configuration Example (QinQ-Based E-Line Service) in the Configuration Guide. For details on the configuration example of a QinQ-based E-LAN service, see Configuration Example (802.1ad-Bridge-Based E-LAN Service) in the Configuration Guide.

This section provides the hyperlinks of the operation tasks associated with QinQ.
Related Tasks
A.5.6.3 Setting the Layer 2 Attributes of Ethernet Ports A.5.7.2 Setting the Layer 2 Attributes of the IF_ETH Port A.6.3.1 Configuring the QinQ Link A.6.3.4 Configuring UNI-NNI E-Line Services (Carried by QinQ Links) A.6.3.3 Configuring NNI-NNI E-Line Services A.6.3.10 Configuring IEEE 802.1ad Bridge-Based E-LAN Services

No alarms or performance events are associated with QinQ.
Issue 02 (2011-01-20)
5-57
Relevant Alarms
None.
Relevant Events
None.
5.3.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 980, the TPID in an S-TAG is 0x88a8. In the case of other types of equipment, the TPID may adopt a different value, for example, 0x8100. 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.
5.4 Layer 2 Switching

This chapter describes the Layer 2 switching feature. 5.4.1 Introduction This section provides the definition of Layer 2 switching and describes its purpose. 5.4.2 Basic Concepts This section describes the basic concepts related to Layer 2 switching. 5.4.3 Specifications This section describes the specifications of Layer 2 switching. 5.4.4 Reference Standards and Protocols This section describes the standards and protocols associated with Layer 2 switching. 5.4.5 Availability This section describes the support and dependency required by Layer 2 switching. 5.4.6 Principles The key of Layer 2 switching is to forward Ethernet packets based on a MAC address table. 5.4.7 Planning Guidelines Follow certain guidelines when you plan Layer 2 switching. 5.4.8 Configuration Procedure Configuring Ethernet services based on Layer 2 switching involves configuring E-LAN services.
5.4.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. 5.4.10 Task Collection This section provides the hyperlinks of the operation tasks associated with Layer 2 switching. 5.4.11 Relevant Alarms and Events There are no alarms or performance events relevant to Layer 2 switching. 5.4.12 FAQs This section provides the answers to the questions that are frequently raised when Layer 2 switching is used.
5.4.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. A MAC address is a Layer 2 address in the OSI model. Therefore, this data forwarding mode is called Layer 2 switching.
Purpose
If an Ethernet processing unit supports Layer 2 switching, its switching domain can be divided into multiple independent sub-switching domains. With this method, multiple LAN services are isolated and bridge resources are dynamically shared. Figure 5-22 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.
Issue 02 (2011-01-20)
5-59
Figure 5-22 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

This section describes the basic concepts related to Layer 2 switching. 5.4.2.1 Bridge A bridge refers to a functional unit that is used to connect two or more LANs. 5.4.2.2 E-LAN Services Based on the 802.1d Bridge In the case of E-LAN services, packets can be forwarded only based on the MAC address table. This type of E-LAN services is called the E-LAN service based on the 802.1d bridge. 5.4.2.3 E-LAN Services Based on 802.1q Bridge E-LAN services can be separated by setting VLANs. In this case, a bridge is divided into multiple sub-switching domains. Therefore, the E-LAN services separated by setting VLANs are E-LAN services based on 802.1q bridge. 5.4.2.4 E-LAN Services Based on 802.1ad Bridge S-VLAN tags can be used to isolate E-LAN services. Therefore, a bridge is divided into multiple independent sub-switching domains. These services are E-LAN services based on 802.1ad bridge. 5.4.2.5 Split Horizon Group To better isolate services that are converged and to prevent broadcast storm resulting from a service loop, you can configure a split horizon group for the E-LAN services at the specified nodes. The logical ports in one split horizon group cannot forward packets to each other. 5.4.2.6 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.
5.4.2.1 Bridge
A bridge refers to a functional unit that is used to connect two or more LANs. A bridge is the most important part for E-LAN services. Through self-learning, a bridge sets up the mapping relationship between an Ethernet port and the source MAC address contained in an Ethernet frame that enters the bridge through the port. This mapping relationship is an entry in a MAC address table. The self-learning modes are classified into the following types: l Shared VLAN learning (SVL) When a bridge uses the SVL mode, it creates an entry in the MAC address table based on the source MAC address and the source port of a packet. This entry is valid to all VLANs. l Independent VLAN learning (IVL) When a bridge uses the IVL mode, it creates an entry in the MAC address table according to the source MAC address, VLAN ID, and source port of a packet. This entry is valid only to the VLAN represented by the VLAN ID carried in the packet. On the receipt of an Ethernet frame, a bridge processes it as follows: l If the bridge uses the SVL mode, it searches for the destination MAC address of the Ethernet frame in the MAC address table. If the bridge uses the IVL mode, it searches for the VLAN ID and destination MAC address of the Ethernet frame in the MAC address table. If a corresponding entry exists in the MAC address table, the bridge forwards the Ethernet frame to the corresponding Ethernet port. If no corresponding entry is found, the bridge broadcasts the Ethernet frame in the broadcast domain. The bridge adds an entry to the MAC address table or updates the MAC address table based on the source MAC address of the Ethernet frame.
Bridge Types
A bridge supported by the OptiX RTN 900 is available in three types: 802.1d bridge, 802.1q bridge, and 802.1ad bridge. Table 5-32 Bridges Item Type of logical port 802.1d Bridge PORT 802.1q Bridge PORT+VLAN 802.1ad Bridge PORT or PORT+CVLAN (UNI port)a PORT+S-VLAN (NNI port) Learning mode Broadcast domain SVL Entire bridge IVL All the logical ports that have the same VLAN tag IVL All the logical ports that have the same SVLAN tag
5-61
Issue 02 (2011-01-20)
Item Sub-switching domain
802.1d Bridge No division of subswitching domains
802.1q Bridge Division of subswitching domains based on VLAN tags
802.1ad Bridge Division of subswitching domains based on S-VLAN tags
NOTE
a: When a packet enters or exits an 802.1ad bridge through a logical port whose network attribute is UNI, a specified S-VLAN tag is added or stripped.
As shown in Figure 5-23, the services on different 802.1d bridges are isolated, but the services of different VLANs on one bridge are not isolated. Figure 5-23 802.1d bridge
LP3 VLAN1 VLAN2 VLAN3 ... 802.1d bridge LP: Logic Port LP4 LP5 LP6 LP7 LP8
LP1 LP2 LP3
As shown in Figure 5-24, the services on different 802.1q bridges are isolated and the services of different VLANs on one bridge are also isolated. Figure 5-24 802.1q bridge
LP3 LP4 LP5 LP6 LP7 LP8
LP1 LP2 LP3
VLAN1 VLAN2
VLAN3 802.1q bridge LP: Logic Port
As shown in Figure 5-25, the services on different 802.1ad bridges are isolated and the services of different S-VLANs on one bridge are also isolated.
5-62
Issue 02 (2011-01-20)
Figure 5-25 802.1ad bridge

LP1 S-VLAN1 LP4 LP5 LP6 LP7 LP8 LP9
LP2
S-VLAN2 S-VLAN3 802.1ad bridge LP: Logic Port
LP3
Logical Port
The OptiX RTN 980 considers that all the ports that are mounted to a bridge are logical ports. A logical port corresponds to any of the following service flows: l l l l PORT PORT+VLAN PORT+C-VLAN PORT+S-VLAN
A physical port can be mapped into several logical ports. A logical port can be in one or multiple sub-switching domains.
5.4.2.2 E-LAN Services Based on the 802.1d Bridge

In the case of E-LAN services, packets can be forwarded only based on the MAC address table. This type of E-LAN services is called the E-LAN service based on the 802.1d bridge.
Model of Service
Table 5-33 shows the model of E-LAN services based on the 802.1d bridge. Table 5-33 Model of E-LAN services based on the 802.1d bridge Type of Service E-LAN services based on the 802.1d bridge Tag Attribute Encapsulation Mode of Port Null Type of Logical Port PORT Learning Mode SVL SubSwitching Domain No division of sub-switching domains
TagTransparent
Typical Application
Figure 5-26 shows the typical application of the model of service. The transmission network needs to carry the A services accessed from NE2 and NE3. The two A services are converged
at the convergence node NE1. The services need not be isolated. Therefore, an 802.1d bridge is used at NE1 to groom services. Figure 5-26 Model of E-LAN services based on the 802.1d bridge
NE 2
Port 2 NE 1 Transmission Network Port 2 Port 3 802.1d bridge Transmission Network NE 3
Port 1 User A2
Port 1 User A1
Port 2
Port 1 User A3
5.4.2.3 E-LAN Services Based on 802.1q Bridge

E-LAN services can be separated by setting VLANs. In this case, a bridge is divided into multiple sub-switching domains. Therefore, the E-LAN services separated by setting VLANs are E-LAN services based on 802.1q bridge.
Model of Service
Table 5-34 shows the models of E-LAN services based on 802.1q bridge. Table 5-34 Model of E-LAN services based on 802.1q bridge Type of Service E-LAN services based on 802.1q bridge TAG Attribute C-Awared Encapsulation Mode of Port 802.1q Type of Logical Port PORT+VLAN Learning Mode IVL SubSwitching Domain Sub-switching domains are divided based on VLANs.
Figure 5-27 shows the typical application of the model of E-LAN services based on 802.1q bridge. The transport network needs to carry G and H services accessed from NE2 and NE3. Both types of services converge on NE1. G and H services adopt different VLAN planning. Therefore, 802.1q bridge is used on NEs and sub-switching domains are divided based on VLANs, differentiating and separating the two types of services.
Figure 5-27 Model of E-LAN services based on 802.1q bridge

NE 2
VLAN 100
Port 1 User G2
NE 1 Port 1 User G1
VLAN 100
Port 3
VLAN 200
Transmission Network Port 3 802.1q bridge NE 3

VLAN 100
Port 2 User H2
Port 2 User H1
VLAN 200
Port 4 Transmission Network
802.1q bridge
VLAN 200
Port 1 User G3 Port 2 User H3
Port 3
802.1q bridge
NOTE
You can configure 5.2.2.3 VLAN-based E-Line Services on NE2 and NE3 for accessing services.
5.4.2.4 E-LAN Services Based on 802.1ad Bridge

S-VLAN tags can be used to isolate E-LAN services. Therefore, a bridge is divided into multiple independent sub-switching domains. These services are E-LAN services based on 802.1ad bridge.
Model of Service
Table 5-35 shows the models of E-LAN services based on 802.1ad bridge.
Issue 02 (2011-01-20)
5-65
Table 5-35 Models of E-LAN services based on 802.1ad bridge Type of Services E-LAN services based on 802.1ad bridge Tag Attribute Encapsulation Mode of Port Null or 802.1q (UNI port) a QinQ (NNI port) Type of Logical Port PORT (The encapsulation mode of the UNI port is Null.) PORT or PORT +C-VLAN (The encapsulation mode of the UNI port is 802.1q.) a PORT+SVLAN (NNI port) Learning Mode IVL SubSwitching Domain Sub-switching domains are divided based on S-VLAN tags.
S-Awared
NOTE
a: When the encapsulation mode of port is 802.1q, the tag attribute must be Tag Aware.
Figure 5-28 shows the typical application of the model of service. The transmission network needs to carry G and H services accessed from NE2 and NE3. The two types of services are converged on NE1. Since G and H services have a same C-VLAN tag, you need to add different S-VLAN tags to G and H services for service isolation.
5-66
Issue 02 (2011-01-20)
Figure 5-28 Model of E-LAN services based on 802.1ad bridge

NE 2
Add S-VLAN Label S-VLAN(300) S-VLAN(400) C-VLAN(100) C-VLAN(100) Data(G) Data(H) Strip S-VLAN Label C-VLAN(100) C-VLAN(100) Data( G) Data(H)
NE 2
SVLAN 300
Port 1 User G2 Port 3 NE 1

SVLAN 300 SVLAN 400 CVLAN 100
Transmission Network Port 3 802.1ad bridge
Port 2 User H2
CVLAN 100
Port 1 User G1
CVLAN 100 SVLAN 400
User H1
Port 2 Port 4 802.1ad bridge Transmission Network
NE 3
SVLAN 300
CVLAN 100
Port 1 User G3
CVLAN 100 SVLAN 400
NE 1
Strip S-VLAN Label C-VLAN(100) C-VLAN(100) Data( G) Data(H) Add S-VLAN Label S-VLAN(300) S-VLAN(400) C-VLAN(100) C-VLAN(100) Data(G) Data(H)
Port 3
Port 2 User H3
CVLAN 100
802.1ad bridge NE 3
Strip S-VLAN Label C-VLAN(100) C-VLAN(100) Data( G) Data(H)
Add S-VLAN Label S-VLAN(300) S-VLAN(400) C-VLAN(100) C-VLAN(100) Data(G) Data(H)
NOTE
You can configure 5.3.2.2 QinQ-Based E-Line Services on NE2 and NE3 for service access.
5.4.2.5 Split Horizon Group

To better isolate services that are converged and to prevent broadcast storm resulting from a service loop, you can configure a split horizon group for the E-LAN services at the specified nodes. The logical ports in one split horizon group cannot forward packets to each other. Figure 5-29 shows a typical application of the split horizon group. NEs on the network are configured with E-LAN services, and the east and west ports and service access ports are configured as mounted ports of a bridge. In this case, if a split horizon group is not configured at NE1, broadcast storm occurs due to a network loop as the east and west ports can forward packets to each other. If a split horizon group is created at NE1 and the east and west ports are configured as members of the split horizon group, the east and west ports do not forward packets to each other. Therefore, a service loop is prevented.
Issue 02 (2011-01-20)
5-67
Figure 5-29 Split horizon group

NE1 BSC Split horizon group
BTS NE2 BTS NE4 BTS
NE3 BTS
NOTE
l ERPS can prevent a service loop on a ring network. Therefore, if ERPS is already enabled for a ring network, a split horizon group is not needed as it may affect normal operation of ERPS. l On the OptiX RTN 980, only the configuration of a split horizon group based on physical ports is supported. Therefore, if a physical port is mapped into several logical ports and one of these logical ports is a member of a split horizon group, the other logical ports are added to the split horizon group automatically.
5.4.2.6 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. 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. 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.
5-68
Issue 02 (2011-01-20)
This section describes the specifications of Layer 2 switching. Table 5-36 provides the specifications of Layer 2 switching. Table 5-36 Specifications of Layer 2 switching Item Switching capacity Bridge type Specification 22 Gbit/s 802.1d bridge 802.1q bridge 802.1ad bridge Bridge switching mode IVL/Ingress filter enabled (802.1q bridge and 802.1ad bridge) SVL/Ingress filter disabled (802.1d bridge) E-LAN services Number of bridges Number of logical ports mounted to a bridge Maximum number of split horizon groups Number of static entries in the MAC address table Number of blacklist entries in the MAC address table Number of entries in the MAC address table MAC address aging time Broadcast packet suppression function Supported 1 1024 1 512 512 16K 1 minute to 640 minutes Supported

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
5.4.5 Availability
This section describes the support and dependency required by Layer 2 switching.

Table 5-37 Hardware and version support Feature 802.1d bridge 802.1q bridge 802.1ad bridge Applicable Board CSHN IFU2 IFX2 ISU2 ISX2 EM6T EM6F Applicable Hardware Version All the versions All the versions All the versions All the versions All the versions All the versions All the versions Applicable Product Version V100R003C00 and later V100R003C00 and later V100R003C00 and later V100R003C00 and later V100R003C00 and later V100R003C00 and later V100R003C00 and later
Feature Dependency
The dependency between the Layer 2 switching feature and other features is as follows: l l l l The port that is mounted to a bridge cannot be used for E-Line services. The port on a bridge supports the QoS function. A link aggregation group (LAG) can be mounted to only one logical port of a bridge. A PW cannot be mounted to a bridge as a logical port.
5.4.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. 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
2.
3.
5-70
thus establishes the mapping relationship between the MAC address and the destination port. 4. 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. 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). 5. A bridge needs to check whether the source port and the destination port are in the same split horizon group before forwarding data frames. Logical ports that are in the same split horizon group cannot forward packets to each other.
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 5.3.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. In the case of Layer 2 switching services converged from multiple distributed nodes to a convergence node and no communication demand between branch nodes, set these distributed nodes in one split horizon group.
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 E-LAN services. 5.4.8.1 Configuration Procedure (IEEE 802.1d Bridge-Based E-LAN Services) This section describes the procedures for configuring the service information, port information, protection information, and QoS information of an IEEE 802.1d bridge-based E-LAN service and the procedure for verifying the service configurations.
5.4.8.2 Configuration Procedure (IEEE 802.1q Bridge-Based E-LAN Services) This section describes the procedures for configuring the service information, port information, protection information, and QoS information of an IEEE 802.1q bridge-based E-LAN service and the procedure for verifying the service configurations. 5.4.8.3 Configuration Procedure (IEEE 802.1ad Bridge-Based E-LAN Services) This section describes the procedures for configuring the service information, port information, protection information, and QoS information of an IEEE 802.1ad bridge-based E-LAN service and the procedure for verifying the service configurations.
5.4.8.1 Configuration Procedure (IEEE 802.1d Bridge-Based E-LAN Services)

This section describes the procedures for configuring the service information, port information, protection information, and QoS information of an IEEE 802.1d bridge-based E-LAN service and the procedure for verifying the service configurations.

Figure 5-30 provides the procedures for configuring IEEE 802.1d-bridge-based E-LAN services. Figure 5-30 Configuration flow chart (IEEE 802.1d bridge-based E-LAN services)
Configuring LAGs
Configuring QoS
End
The procedures in the configuration flow chart are described as follows.


Table 5-38 Procedures for configuring Ethernet ports Operation Setting the parameters of Ethernet ports A.5.6.1 Setting the General Attributes of Ethernet Ports Description Required. Set the parameters as follows: l In the case of used ports, set Enable Port to Enabled. In the case of unused ports, set Enable Port to Disabled. l Set Encapsulation Type to Null. l In the case of an Ethernet port that is connected to external equipment, set Working Mode to be the same value as the external equipment (generally, the working mode of the external equipment is auto-negotiation). In the case of an Ethernet port within the network, set Working Mode to Auto-Negotiation. l When jumbo frames are transmitted, set Max Frame Length(byte) according to the actual length of the jumbo frames. Otherwise, it is recommended that you set Max Frame Length(byte) to 1536. A.5.6.2 Configuring the Traffic Control of Ethernet Ports A.5.6.5 Setting the Advanced Attributes of Ethernet Ports For ports that carry E-LAN services, the flow control function is always disabled.
Required when you need to enable the port self-loop test and automatic loopback shutdown functions or to enable the broadcast packet suppression function. Set Loopback Check, Loopback Port Shutdown, Enabling Broadcast Packet Suppression, and Broadcast Packet Suppression Threshold according to the actual requirements. Required. Set Encapsulation Type to Null.
Setting the parameters of IF_ETH ports
A.5.7.1 Setting the General Attributes of the IF_ETH Port
Issue 02 (2011-01-20)
5-73
Operation A.5.7.4 Setting the Advanced Attributes of the IF_ETH Port
Description Optional. When the IF_ETH port transmits an Ethernet service that permits bit errors, such as a voice service or a video service, you can set Error Frame Discard Enabled to Disabled.
5-74
Issue 02 (2011-01-20)

Issue 02 (2011-01-20)
5-75

Procedures for Configuring IEEE 802.1d-Bridge-Based E-LAN Services

Table 5-41 Procedures for configuring IEEE 802.1d-bridge-based E-LAN services Operation A.6.3.8 Configuring IEEE 802.1d Bridge-Based ELAN Services Description Required. Set the parameters as follows: l Set Tag Type to Tag-Transparent. l Set Self-Learning MAC Address to Enabled according to the planning information. l In the UNI tab page, set Port according to the planning information and set VLANs/CVLAN to Null. l To disable the packet forwarding between certain E-LAN service ports, add the ports to Split Horizon Group Member. Managing the MAC address table A.6.4.2 Creating a Blacklist Entry of MAC Addresses A.6.4.1 Creating a Static MAC Address Entry Required when usage of E-LAN services needs to be disabled on certain MAC address host. Set the parameters according to the network planning information.
Required if you need to set certain MAC address entries not to age. Set the parameters according to the network planning information.
5-76
Issue 02 (2011-01-20)
Operation A.6.4.3 Configuring the Aging Parameters of a MAC Address Table A.6.5 Setting the Mode for Processing an Unknown Frame of the E-LAN Service
Description Required if the aging function needs to be disabled or if the default aging time (five minutes) needs to be changed. Set the parameters according to the network planning information.
Optional.

Table 5-42 Procedures for configuring QoS Operation A.6.7.2 Modifying the Mapping Relationships for the DS Domain A.6.7.3 Changing the Ports Applied to a DS Domain and Their Trusted Packet Types A.6.7.1 Creating a DS Domain A.6.7.4 Creating a Port Policy A.6.7.6 Creating the Traffic A.6.7.7 Setting the Port That Uses the Port Policy
Issue 02 (2011-01-20)
Description Required when the default mapping relationships for the DS domain do not meet the actual requirements. Set the parameters according to the network planning information. For the default mapping relationships for the DS domain, see A.6.7.10 Querying the DS Domain of a Port. Required when the packet type trusted by a port is not the default trusted packet type (C-VLAN priority) applied to the DS domain. Set the parameters according to the network planning information.
5-77
Operation A.6.7.8 Configuring Port Shaping
Description Required if you need to limit the egress bandwidth that an Ethernet service occupies. Set the parameters according to the network planning information.

5-78
Issue 02 (2011-01-20)
5.4.8.2 Configuration Procedure (IEEE 802.1q Bridge-Based E-LAN Services)

This section describes the procedures for configuring the service information, port information, protection information, and QoS information of an IEEE 802.1q bridge-based E-LAN service and the procedure for verifying the service configurations.

Figure 5-31 provides the procedures for configuring IEEE 802.1q bridge-based E-LAN services.
Issue 02 (2011-01-20)
5-79
Figure 5-31 Configuration flow chart (IEEE 802.1q bridge-based E-LAN services)
Configuring LAGs
Configuring QoS
End
5-80
Issue 02 (2011-01-20)

Table 5-44 Procedures for configuring Ethernet ports Operation Setting the parameters of Ethernet ports A.5.6.1 Setting the General Attributes of Ethernet Ports Description Required. Set the parameters as follows: l In the case of used ports, set Enable Port to Enabled. In the case of unused ports, set Enable Port to Disabled. l Set Encapsulation Type to 802.1Q. l In the case of the Ethernet port that is connected to the external equipment, set Working Mode to be the same value as the external equipment (generally, the working mode of the external equipment is auto-negotiation). In the case of the Ethernet ports within the network, set Working Mode to Auto-Negotiation. l When jumbo frames are transmitted, set Max Frame Length(byte) according to the actual length of the jumbo frames. Otherwise, it is recommended that you set Max Frame Length(byte) to 1536. A.5.6.2 Configuring the Traffic Control of Ethernet Ports A.5.6.3 Setting the Layer 2 Attributes of Ethernet Ports For ports that carry E-LAN services, the flow control function is always disabled.
Required. Set the parameters as follows: l If all the accessed services carry VLAN tags (tagged frames), set TAG to Tag Aware. l If none of the accessed services carries VLAN tags (untagged frames), set TAG to Access, and set Default VLAN ID and VLAN Priority according to the network planning information. l When the accessed services contain tagged frames and untagged frames, set TAG to Hybrid, and set Default VLAN ID and VLAN Priority according to the network planning information.
Required when you need to enable the port self-loop test and automatic loopback shutdown functions or to enable the broadcast packet suppression function. Set Loopback Check, Loopback Port Shutdown, Enabling Broadcast Packet Suppression, and Broadcast Packet Suppression Threshold according to the requirements.
Issue 02 (2011-01-20)
5-81

Table 5-45 Procedures for configuring ERPS protection Operation A.6.1.1 Creating Ethernet Ring Protection Instances Description Required when an Ethernet ring needs to be protected and service loops need to be avoided on the Ethernet ring.
5-82
Issue 02 (2011-01-20)
Operation A.6.1.2 Setting the Parameters of Ethernet Ring Protocol
Description Required if the values of the default parameters of the ERPS timers need to be changed. Set Hold-Off Time(ms), Guard Time(ms), WTR Time(mm:ss), and Packet Transmit Interval(s) according to the actual requirements. Set these parameters to the same values for all the NEs on the network.

Table 5-46 Procedures for configuring a LAG Operation A.6.2.1 Creating a LAG Description Required if the LAG is configured to protect the FE/GE ports or if the Hybrid radio uses the N+0/XPIC configuration mode. 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 The Hybrid/AM attributes must be set to the same value for the IF ports in a LAG. l In the case of FE/GE ports, set Load Sharing to the same value as the opposite equipment. If the LAG is configured only 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 the bandwidth, it is recommended that you set Load Sharing to Sharing for the equipment at both ends. l When the Hybrid radio uses the N+0/XPIC configuration mode, 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. This parameter is valid to only LAGs whose Load Sharing is set to Non-Sharing. l Set Load Sharing Hash Algorithm 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 the main and slave ports of the LAG at the local end take the same settings as the main and slave ports of the LAG at the opposite end. In this case, you can set System Priority according to the actual requirements. It is recommended that this parameter takes the default value. This parameter is valid to only static LAGs. l Set Main Board, Main Port, and Selected Slave Ports according to the planning information. It is recommended that the same main and slave ports are used for the LAGs at both ends.
Issue 02 (2011-01-20)
5-83
Operation A.6.2.2 Setting Parameters for LAGs
Procedures for Configuring IEEE 802.1q Bridge-Based E-LAN Services

Table 5-47 Procedures for configuring IEEE 802.1q bridge-based E-LAN services Operation A.6.3.9 Configuring IEEE 802.1q Bridge-Based ELAN Services Description Required. Set the parameters as follows: l Set Tag Type to C-Awared. l Set Self-Learning MAC Address to Enabled according to the planning information. l In the UNI tab page, set the parameters according to the planning information. l To disable the packet forwarding between certain E-LAN service ports, add the ports to Split Horizon Group Member. Managing the MAC address table A.6.4.2 Creating a Blacklist Entry of MAC Addresses A.6.4.1 Creating a Static MAC Address Entry A.6.4.3 Configuring the Aging Parameters of a MAC Address Table A.6.5 Setting the Mode for Processing an Unknown Frame of the E-LAN Service Required when usage of E-LAN services needs to be disabled on certain MAC address host. Set the parameters according to the network planning information.
Optional.
5-84
Issue 02 (2011-01-20)

Issue 02 (2011-01-20)
5-85

5-86
Issue 02 (2011-01-20)
5.4.8.3 Configuration Procedure (IEEE 802.1ad Bridge-Based E-LAN Services)


Figure 5-32 provides the procedures for configuring IEEE 802.1ad bridge-based E-LAN services.
Issue 02 (2011-01-20)
5-87
Figure 5-32 Configuration flow chart (IEEE 802.1ad bridge-based E-LAN services)
Configuring LAGs
Configuring QoS
End
5-88
Issue 02 (2011-01-20)

Table 5-50 Procedures for configuring Ethernet ports Operation Setting the parameters of Ethernet ports A.5.6.1 Setting the General Attributes of Ethernet Ports Description Required. Set the parameters as follows: l In the case of used ports, set Enable Port to Enabled. In the case of unused ports, set Enable Port to Disabled. l If a UNI can access untagged frames, set Encapsulation Type to Null. If a UNI can access tagged frames only, set Encapsulation Type to 802.1Q. l In the case of an NNI, set Encapsulation Type to QinQ. l In the case of the Ethernet port that is connected to the external equipment, set Working Mode to be the same value as the external equipment (generally, the working mode of the external equipment is auto-negotiation). In the case of the Ethernet ports within the network, set Working Mode to Auto-Negotiation. l When jumbo frames are transmitted, set Max Frame Length(byte) according to the actual length of the jumbo frames. Otherwise, it is recommended that you set Max Frame Length(byte) to 1536. A.5.6.2 Configuring the Traffic Control of Ethernet Ports A.5.6.3 Setting the Layer 2 Attributes of Ethernet Ports For ports that carry E-LAN services, the flow control function is always disabled.
Required. Set the parameters as follows: l In the case of a UNI, if Encapsulation Type is set to 802.1Q, set TAG to Tag Aware (default value). l In the case of an NNI that is connected to the external equipment, set QinQ Type Domain according to the TPID of the SVLAN that is supported by the external equipment. Required when you need to enable the port self-loop test and automatic loopback shutdown functions or to enable the broadcast packet suppression function. Set Loopback Check, Loopback Port Shutdown, Enabling Broadcast Packet Suppression, and Broadcast Packet Suppression Threshold according to the requirements.
Issue 02 (2011-01-20)
5-89
Description Required. l If a UNI can access untagged frames, set Encapsulation Type to Null. If a UNI can access tagged frames only, set Encapsulation Type to 802.1Q. l In the case of an NNI, set Encapsulation Type to QinQ.
Required. Set the parameters as follows: l In the case of a UNI, if Encapsulation Type is set to 802.1Q, set Tag to Tag Aware (default value). l In the case of an NNI that is connected to the external equipment, set QinQ Type Domain according to the TPID of the SVLAN that is supported by the external equipment. In the case of an NNI within the network, QinQ Type Domain takes the default value. Optional. When the IF_ETH port transmits an Ethernet service that permits bit errors, such as a voice service or a video service, you can set Error Frame Discard Enabled to Disabled.

5-90
Issue 02 (2011-01-20)

Issue 02 (2011-01-20)
5-91
Procedures for Configuring IEEE 802.1ad Bridge-Based E-LAN Services

Table 5-53 Procedures for configuring IEEE 802.1ad bridge-based E-LAN services Operation A.6.3.10 Configuring IEEE 802.1ad Bridge-Based ELAN Services Description Required. Set the parameters as follows: l Set Tag Type to S-Awared. l Set Self-Learning MAC Address to Enabled according to the planning information. l In the UNI and NNI tab pages, set the parameters according to the planning information. l To disable the packet forwarding between certain E-LAN service ports, add the ports to Split Horizon Group Member. Managing the MAC address table A.6.4.2 Creating a Blacklist Entry of MAC Addresses A.6.4.1 Creating a Static MAC Address Entry A.6.4.3 Configuring the Aging Parameters of a MAC Address Table A.6.5 Setting the Mode for Processing an Unknown Frame of the E-LAN Service Required when usage of E-LAN services needs to be disabled on certain MAC address host. Set the parameters according to the network planning information.
Optional.
5-92
Issue 02 (2011-01-20)

Issue 02 (2011-01-20)
5-93

5-94
Issue 02 (2011-01-20)

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 (802.1d-Bridge-Based E-LAN Service) in the Configuration Guide. For a configuration example of Ethernet services based on an 802.1q bridge, see Configuration Example (802.1q-Bridge-Based E-LAN Service) in the Configuration Guide. For a configuration example of Ethernet services based on an 802.1ad bridge, see Configuration Example (802.1ad-Bridge-Based E-LAN Service) in the Configuration Guide.

This section provides the hyperlinks of the operation tasks associated with Layer 2 switching.
Related Tasks
A.5.6.5 Setting the Advanced Attributes of Ethernet Ports A.5.7.4 Setting the Advanced Attributes of the IF_ETH Port A.6.3.8 Configuring IEEE 802.1d Bridge-Based E-LAN Services A.6.3.9 Configuring IEEE 802.1q Bridge-Based E-LAN Services A.6.3.10 Configuring IEEE 802.1ad Bridge-Based E-LAN Services A.6.3.11 Changing Logical Ports Connected to a VB A.6.4.1 Creating a Static MAC Address Entry A.6.4.2 Creating a Blacklist Entry of MAC Addresses
A.6.4.3 Configuring the Aging Parameters of a MAC Address Table A.6.5 Setting the Mode for Processing an Unknown Frame of the E-LAN Service

There are no alarms or performance events relevant to Layer 2 switching.
Relevant Alarms
None.
Relevant Events
None.
5.4.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 980, 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.
5.5 Ethernet Ring Protection Switching

Ethernet ring protection switching (ERPS) is applicable to ring physical networks. ERPS protects Ethernet services on an Ethernet ring network. 5.5.1 Introduction This section provides the definition of ERPS and describes its purpose. 5.5.2 Basic Concepts This topic describes the basic concepts that you need to be familiar with before you use the ERPS feature. 5.5.3 Specifications This topic provides the specifications of ERPS. 5.5.4 Reference Standards and Protocols This section describes the standards and protocols associated with ERPS. 5.5.5 Availability This section describes the support required by the application of the ERPS feature and its dependency. 5.5.6 Principles The ERPS uses the R-APS protocol to implement protection switching. 5.5.7 Planning Principles When planning ERPS, abide by the following principles: 5.5.8 Configuration Procedure
The key to configuring the ERPS is creating the ERPS protection instance. 5.5.9 Configuration Example This topic uses an example to describe how to plan and configure the ERPS according to the conditions of the network. 5.5.10 Task Collection This topic provides the hyperlinks of the operation tasks regarding the ERPS feature. 5.5.11 Relevant Alarms and Events When the ERPS is abnormal, the system control and communication board reports the relevant alarms and performance events. 5.5.12 FAQs This topic describes the answers to the questions that are frequently raised when the ERPS feature is used.
5.5.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 main node blocks its port on one 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 5-33 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 02 (2011-01-20)
5-97
Figure 5-33 Implementation of the 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

This topic describes the basic concepts that you need to be familiar with before you use the ERPS feature. 5.5.2.1 Protection Instance A protection instance is the basic unit of the ERPS. 5.5.2.2 Protection Type
The ERPS is revertive. 5.5.2.3 R-APS Message When the ERPS scheme is used, a switching request is transmitted through the ring-APS (RAPS) message. 5.5.2.4 R-APS Timer In the ERPS process, three timers are used, including the guard timer, WTR timer, and holdoff timer. 5.5.2.5 Switching Condition The switching actions of an Ethernet ring consisting of Ethernet ports and an Ethernet ring consisting of radio ports are triggered by different conditions. 5.5.2.6 Switching Impact The services are interrupted within the ERPS time (less than 100 ms).
5.5.2.1 Protection Instance

A protection instance is the basic unit of the ERPS. Figure 5-34 shows a protection instance of the ERPS. The protection instance of the ERPS refers to a node on the Ethernet ring that runs the ERPS protocol. In the protection instance of the ERPS, ring link, ring protection link (RPL), RPL owner, control VLANs, MAC destination address and east (E) ports and west (W) ports enabled with ERPS on the Ethernet ring are defined. Figure 5-34 Protection instance of the 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 service channels of which are blocked when this Ethernet ring is normal. 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 ring node label. When an Ethernet ring is normal, the RPL
connection point on the RPL owner is blocked to prevent the service channels from forming loops. A ring port is an Ethernet connection point on an Ethernet ring node. A ring port can be an FE port, a GE port, or a radio port. The OptiX RTN 980 does not support Ethernet tangent rings or Ethernet intersecting rings. That is, different protection instances of the ERPS cannot contain one or more same ring ports. Consider Figure 5-34 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 counter-clockwise services is a west ring port.

The 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 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 events because the former working channel is not stable, it is recommended that you set the WTR time to 5 to 12 minutes.
5.5.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 complete the ERPS. The frame format of the R-APS message is a type of ETH-OAM frame formats. See Figure 5-35. An R-APS message uses a fixed default MAC destination address, namely, 01-19-A7-00-00-01. An R-APS message also contains a VLAN ID, which identifies an R-APS message from the Ethernet service message and inband DCN message. Hence, the VLAN ID contained in the R-APS message cannot be the same as the VLAN ID contained in the Ethernet service message and inband DCN 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.
5-100
Issue 02 (2011-01-20)
Figure 5-35 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 5-36 shows the frame format of the R-APS specific information. Figure 5-36 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 5-56 provides the details about each field in the R-APS specific information. Table 5-56 Description of each field in the R-APS specific information Field Request/State Value 1011 0000 Others Reserved 1
Issue 02 (2011-01-20)
Description Indicates signal fail (SF). Indicates no request (NR). Reserved. Reserved.
5-101
0000
Field Status RPL blocked (RB)
Value 1 0
Description Indicates that an RPL is blocked. l Indicates that an RPL is not blocked. l In the case of a non-RPL owner node, the value of RB should be 0.
Do not flush (DNF)
1 0
Indicates that the ring node should not empty the MAC address table. Indicates that the ring node should empty the MAC address table. Reserved. Indicates the MAC address of a ring node. The MAC address is unique. Reserved.
Status reserved Node ID Reserved 2
All 0s
According to the values of the fields provided in Table 5-56, 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 informed 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 informed that the Ethernet ring is normal 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 informed 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 informed that it should not empty the MAC address table.
5.5.2.4 R-APS Timer

In the ERPS process, three timers are used, including the guard timer, WTR timer, and holdoff timer.
Guard Timer
A ring node continuously transmits R-APS messages over an Ethernet ring. Hence, outdated RAPS messages may exist on the ring. The reception of these outdated R-APS messages may result in incorrect ERPS actions. The guard timer is a type of R-APS timers and is used to prevent ring nodes from receiving outdated R-APS messages. When a faulty node detects that the switching condition is cleared, it starts the guard timer and starts to forward the R-APS (NR) message. When the guard timer is running, the ring node discards the R-APS message that arrives. When the guard timer expires, the received R-APS message is forwarded.
The period of a guard timer may be set in 10 ms steps between 10 ms and 2000ms, with a default value of 500 ms.
WTR Timer
The 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 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. When the former working 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 of a higher priority is received, the WTR timer running signal is no longer generated but a WTR expire signal is continuously generated.
Holdoff Timer
The holdoff timer is used to adjust the switching sequence between the ERPS scheme and other coexisting protection schemes. The holdoff timer allows a fault that triggers another protection switching (for example, the LAG protection) to be rectified before ERPS switching. When the ring node detects one or more new faults, the holdoff timer is started if the preset value of the holdoff timer 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 the fault persists, the fault 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 with an accuracy of 5 ms. The default value is 0s.

The switching actions of an Ethernet ring consisting of Ethernet ports and an Ethernet ring consisting of radio ports are triggered by different conditions.
Issue 02 (2011-01-20)
5-103
Table 5-57 Trigger conditions of the ERPS Switching Condition Local SF Priority From top downward s, the priority is from the highest to the lowest. Description l In the case of an Ethernet ring consisting of radio links 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. In this case, the two ring ports on this ring node transmit the R-APS (SF) message. The local SF condition enables the ring node to empty the MAC address table. SF switching is triggered when any of the following alarms is reported: hardware fault on the IF board or the IF unit, hardware fault on the ODU, VOLT_LOS (on the IF board), RADIO_TSL_HIGH, RADIO_TSL_LOW, RADIO_RSL_HIGH, RADIO_RSL_HIGH, R_LOC, R_LOF, MW_LOF, MW_BER_EXC, BIP_EXC, and MW_FEC_UNCOR. l In the case of a ring consisting of Ethernet links 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. In this case, the two ring ports on this ring node transmit the R-APS (SF) message. The local SF condition enables the ring node to empty the MAC address table. The SF switching is triggered when the ETH_LOS alarm is reported. Reception of the R-APS (SF) message at the local node l When an RPL owner receives the R-APS (SF) message and does not receive a local switching request of a higher priority, the RPL owner unblocks the RPL connection point that is already blocked and thus connects the service channel on the RPL. l When an RPL owner receives the 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 the 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 the R-APS (SF) message that contains the DNF flag, these ring nodes do not empty their MAC address tables.
5-104
Issue 02 (2011-01-20)
Switching Condition Expiration of the WTR timer
Priority
Description l When a ring node detects that the local SF condition on another ring node is cleared, this ring node continuously transmits the R-APS (NR) message, through its two ring ports, to the Ethernet ring to inform that no switching request exists at the local end. In addition, this ring node starts the guard timer. l On the reception of the R-APS (NR) message, the RPL owner starts the WTR timer. During the duration period of the WTR timer, the reception 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 trigger condition of a higher priority does not exist, the RPL owner blocks the service channel on the RPL and then transmits the R-APS (NR, RB) message, through its two ring ports, to the Ethernet ring to inform that the RPL is blocked. In addition, the RPL owner empties the MAC address table.
Reception of the R-APS (NR, RB) message at the local node
l When the other ring nodes receive the 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 node no longer empties its MAC address table.

The services are interrupted within the ERPS time (less than 100 ms).
This topic provides the specifications of ERPS. Table 5-58 lists the specifications of ERPS. Table 5-58 Specifications of ERPS Item Protection instance of ERPS Maximum number of protection instances supported by a single node Specification 8
Issue 02 (2011-01-20)
5-105
Item Type of supported ERPS east/west port
Specification FE/GE port Integrated IP radio port

NOTE The OptiX RTN 980 does not support Ethernet tangent rings or Ethernet intersecting rings. That is, the west and east ports must belong to the same Ethernet ring.
RPL owner Control VLAN IDs on the R-APS channel Timer Holdoff timer
Only one RPL owner exists on an Ethernet ring. 2-4094

NOTE A control VLAN ID cannot be the same as the VLAN ID in service packets.
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 The default value is 5s. 0 to 7 The default value is 4.
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
5.5.5 Availability
This section describes the support required by the application of the ERPS feature and its dependency.
5-106
Issue 02 (2011-01-20)

Table 5-59 Hardware and version support Feature ERPS Applicable Board CSHN EM6T EM6F IFU2 IFX2 ISU2 ISX2 Applicable Hardware Version All the versions All the versions All the versions All the versions All the versions All the versions All the versions Applicable Product Version V100R003C00 and later V100R003C00 and later V100R003C00 and later V100R003C00 and later V100R003C00 and later V100R003C00 and later V100R003C00 and later
Feature Dependency
The ERPS is associated with the 1+1 protection, LAG, and SNCP. l l l l The 1+1 Hybrid radio link can function as the ring link or ring protection link in the ERPS protection. A link aggregation group (LAG) can function as the ring link or ring protection link in the ERPS protection. The Hybrid microwave ring can use the SNCP and ERPS to respectively protect the E1 services and Ethernet services on the ring. The PWE3 service does not support ERPS.
5.5.6 Principles
The ERPS uses the R-APS protocol to implement protection switching. Figure 5-37 shows the working principle of the ERPS for the OptiX RTN 980.
NOTE
The links on the Ethernet ring as shown in Figure 5-37 and Figure 5-38 can be Ethernet links or radio links. The realization principles of the ERPS in the two cases are the same.
Issue 02 (2011-01-20)
5-107
Figure 5-37 Realization principle of the 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 5-37, the ERPS process is described as follows: 1. 2. 3. 4. 5. When the Ethernet ring is normal, the east (E) port on the RPL owner (NE D) is blocked. The 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 ports that are connected to the faulty link and empty the MAC address table. NE A and NE B keep transmitting the R-APS (SF) message to the Ethernet ring periodically when the SF condition persists. The ring nodes that receive the R-APS (SF) message empty their MAC address tables. When the RPL owner receives the 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. NE A and NE B detect that the SF condition is cleared. In this case, NE A and NE B start the guard timer and start to periodically transmit the R-APS (NR) message the other ring nodes. The guard timer is used to prevent frequent switching events on NE A and NE B
6. 7. 8.
5-108
because of the reception of the R-APS message. After the guard timer expires, NE A and NE B can receive new R-APS messages. 9. When the RPL owner receives the R-APS (NR) message, it starts the WTR timer. After the WTR timer expires, the RPL owner blocks the RPL connection point. In addition, the RPL owner starts to transmit the R-APS (NR, RB) message and empties the MAC address table.
10. When NE A and NE B receive the R-APS (NR, RB) message, they unblock the blocked ring ports and stop transmitting the R-APS (NR, RB) message. In addition, NE A, NE B, and NE C empty their MAC address tables when receiving the R-APS (NR, RB) message. In this case, the Ethernet ring returns to normal. Figure 5-38 Realization principle of the ERPS (in the case of a fault on an RPL link)
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)
Figure 5-38As shown in Figure 5-38, the ERPS process is described as follows: 1. 2. 3. 4. When the Ethernet ring is normal, the east (E) port on the RPL owner (NE D) is blocked. The RPL link between NE A and NE D becomes faulty. NE A and NE D detect the local SF condition. After the holdoff timer expires, NE A and NE D block the ports connecting to the faulty RPL. NE A and NE D keep transmitting the R-APS (SF) message to the Ethernet ring periodically when the SF condition persists. The 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. The RPL owner receives the R-APS (SF) message that contains the DNF flag, but the R-APS (SF) message is ignored because the local SF condition has a higher priority.
Issue 02 (2011-01-20)
When the R-APS (SF) message that contains the DNF flag is received, the other ring nodes are informed that the RPL is faulty and thus do not empty their MAC address tables under any conditions. In this case, the Ethernet ring becomes stable. The SF message that contains the DNF flag exists on the ring. 5. 6. The fault on the RPL between NE A and NE D is rectified. NE A and NE D detect that the switching trigger condition is cleared. In this case, NE A and NE D start the guard timer and start to periodically transmit the R-APS (NR) message to the other ring nodes. The guard timer prevents NE A and NE D from receiving R-APS messages. After the guard timer expires, NE A and NE D can 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 transmit the R-APS (NR, RB) message that contains the DNF flag, informing that all the ring nodes should not empty their MAC address tables under any conditions. When NE A receives the R-APS (NR, RB) message, it unblocks the blocked west (W) ring port and stops transmitting the R-APS (NR) message. When NE A, NE B, and NE C receive the R-APS (NR, RB) message, they are informed that the RPL is restored to normal and required not to empty their MAC address tables under any conditions. In this case, the Ethernet ring returns to normal.
7.
8.
5.5.7 Planning Principles

When planning ERPS, abide by the following principles:
ERPS Application Scenario

When FE/GE ports or Hybrid radio form a ring network, you can adopt the ERPS scheme to protect the Ethernet services on the ring network. A ring network is formed on the basis of the following constraints: Multiple ERPS networks cannot share a port on the ring.
Planning Principles for ERPS IDs

l It is recommended that you allocate an ERPS ID starting from 1 to the ERPS instances on the NE in a sequential manner. You can use other IDs in ascending order only when multiple ERPS instances exist on an NE. A maximum of eight ERPS instances are allowed on an NE. On an ERPS network, the ERPS IDs of the NEs can be different from each other.
l l
Planning Principles for the East-West Ports

Based on the counterclockwise direction of the Ethernet ring, it is recommended that you plan the transmit port on an Ethernet node to be a port on the eastern ring, and the receive port to be a port on the western ring.
Planning Principles for the RPL Owner

l l Only one node on an Ethernet ring can function as the RPL owner. The selected RPL owner needs to balance the traffic on each link of the Ethernet ring. Therefore, it is not recommended that you select an aggregation node as the RPL owner.
5-110
Instead, you need to select the NE that is the farthest away from the aggregation node as the RPL owner.
Planning Principles for RPL Ports

It is recommended that you set the eastern port of the RPL owner to as an RPL port.
Planning Principles for the Control VLAN

The ID of a control VLAN cannot be duplicate with the ID of a service VLAN.
Planning Principles for the ERPS Timer

The parameters of the three ERPS timers must be set to the same values on the NEs of the entire ring network.
Planning Principles for the Entity Level

It is recommended that you set the entity level to the default value 4.
Planning Principles for the Ethernet Services on an ERPS Ring

All the ERPS Ethernet rings transmit the E-LAN service.

The key to configuring the ERPS is creating the ERPS protection instance. Table 5-60 Procedure for configuring the ERPS Step 1 Operation A.6.1.1 Creating Ethernet Ring Protection Instances Description Required when you need to configure the ERPS. Set the parameters as follows: l Set ERPS ID, East Port, West Port, RPLOwner Ring Node Flag, RPL Port, and Control VLAN according to the network planning information. l When setting RPLOwner Ring Node Flag, note that only one RPL owner can exist on one Ethernet ring. l When setting RPL Port, note that different ERPS protection instances cannot contain any same ports. 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 in-band DCN packets. 2 A.6.1.2 Setting the Parameters of Ethernet Ring Protocol Required when you need to configure the ERPS. It is recommended that you adopt the default value or set this parameter according to the network planning information.
Issue 02 (2011-01-20)
5-111

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

This topic describes the networking information about the NEs. As shown in Figure 5-39, NE1, NE2, NE3, and NE4 construct a Hybrid microwave ring network. The ERPS is configured to protect the Ethernet services on the ring network. Generally, when a Hybrid microwave ring network is configured with the ERPS, the RPL owner node (NE1) blocks the east RPL ports and all the services are transmitted through west RPL ports. If a link on the ring network fails or an NE on the ring network becomes faulty, NE1 enables the blocked east RPL ports so that the services can be transmitted through these east RPL ports. Figure 5-39 Networking diagram
Hybrid IF board (E): 3-IFU2 Hybrid IF board (W): 4-IFU2 RPL Owner ETH BSC ETH W NE2 E RPL RPL Port ERPS W NE4 BTS4 E ETH E W NE1
BTS1
Hybrid IF board (E): 3-IFU2 Hybrid IF board (W) 4-IFU2
ETH W NE3 E BTS3 Hybrid IF board (E): 3-IFU2 Hybrid IF board (W): 4-IFU2
Hybrid IF board (E): 3-IFU2 Hybrid IF board (W): 4-IFU2
Bloked port
5-112
Issue 02 (2011-01-20)

The service planning information contains all the parameter information required for configuring the NE data. Table 5-61 Configuration information about the ERPS protection instance Parameter ERPS ID East Port West Port RPL Owner Ring Node Flag RPL Port Control VLAN NE1 1 3-IFU2-1 4-IFU2-1 Yes 3-IFU2-1 4093 NE2 1 3-IFU2-1 4-IFU2-1 No 4093 NE3 1 3-IFU2-1 4-IFU2-1 No 4093 NE4 1 3-IFU2-1 4-IFU2-1 No 4093
Table 5-62 Configuration information about the ERPS parameters Parameter Hold-Off Time (ms) Guard Time (ms) WTR Time (min) Packet Transmit Interval (s) NE1 0 500 5 5 NE2 0 500 5 5 NE3 0 500 5 5 NE4 0 500 5 5

Procedure
Step 1 See A.6.1.1 Creating Ethernet Ring Protection Instances and create the ERPS protection instance. The values for the related parameters are provided as follows.
Issue 02 (2011-01-20)
5-113
Parameter
Value Range NE1 NE2 1 3-IFU2-1 4-IFU2-1 No 4093 NE3 1 3-IFU2-1 4-IFU2-1 No 4093 NE4 1 3-IFU2-1 4-IFU2-1 No 4093
ERPS ID East Port West Port RPLOwner Ring Node Flag RPL Port Control VLAN
1 3-IFU2-1 4-IFU2-1 Yes 3-IFU2-1 4093
Step 2 See A.6.1.2 Setting the Parameters of Ethernet Ring Protocol and set the ERPS parameters. The values for the related parameters are provided as follows. Parameter Value Range NE1 Hold-Off Time(ms) Guard Time(ms) WTR Time (mm:ss) Packet Transmit Interval(s) 0 500 5 5 NE2 0 500 5 5 NE3 0 500 5 5 NE4 0 500 5 5
----End

This topic provides the hyperlinks of the operation tasks regarding the ERPS feature.
Related Tasks
A.6.1.1 Creating Ethernet Ring Protection Instances A.6.1.2 Setting the Parameters of Ethernet Ring Protocol A.6.1.3 Querying the Status of the Ethernet Ring Protocol A.11.6.4 Testing the ERPS

When the ERPS is abnormal, the system control and communication board reports the relevant alarms and performance events.
Relevant Alarms
MULTI_RPL_OWNER The MULTI_RPL_OWNER indicates that more than one RPL owner node exists on the Ethernet ring network.

None.
5.5.12 FAQs
This topic describes the answers to the questions that are frequently raised when the ERPS feature is used. Q: Why is the protection switching not performed when link faults occur on the Ethernet ring network that is configured with the ERPS? A: Possible causes are as follows: l The ERPS parameter Hold-Off Time(ms) is set to a value longer than the permitted delay time. It is recommended that you set Hold-Off Time(ms) to zero on the NMS. l Two or more Ethernet links on the Ethernet ring network are faulty. The ERPS provides protection only against one link failure. That is, the Ethernet services can be protected when only one Ethernet link is faulty. If more than one Ethernet link is faulty, the ERPS fails. l l If Control VLAN of the control nodes in an ERPS protection instance are different, reset Control VLAN on the NMS. The ERPS parameters are not set to the same values for each node on the Ethernet ring network. On the NMS, set the ERPS parameters to the same values for each node on the Ethernet ring network. l More than one RPL owner node is configured on the Ethernet ring network. An Ethernet ring network supports only one RPL owner node.
5.6 MSTP
The Multiple Spanning Tree Protocol (MSTP) is a type of spanning tree protocols. The MSTP is compatible with the STP and RSTP, and the defects in the STP and RSTP are fixed in the MSTP. 5.6.1 Introduction This topic provides the definition of MSTP and describes its purpose. 5.6.2 Basic Concepts This topic describes the basic concepts that you need to be familiar with before you use the MSTP feature. 5.6.3 Specifications This topic provides the specifications of STP.
5.6.4 Reference Standards and Protocols This section describes the standards and protocols associated with MSTP. 5.6.5 Availability This section describes the support required by the application of the MSTP feature and its dependency. 5.6.6 Principles The MSTP complies with IEEE 802.1s. The OptiX RTN 980 supports only the MSTP that generates the CIST. 5.6.7 Planning Principles When planning MSTP, abide by the following principles: 5.6.8 Configuration Procedure To use the MSTP protocol, you need to configure the port group, set the bridge parameters and CIST parameters, and then enable the MSTP protocol. 5.6.9 Configuration Example This topic uses an example to describe how to plan and configure the MSTP according to the conditions of the network. 5.6.10 Task Collection This topic provides the hyperlinks of the operation tasks regarding the MSTP feature. 5.6.11 Relevant Alarms and Events When the status of the MSTP port changes, the system control unit reports the relevant performance events. 5.6.12 FAQs This topic describes the answers to the questions that are frequently raised when the MSTP feature is adopted.
5.6.1 Introduction
This topic provides the definition of MSTP and describes its purpose.
Definition
The spanning tree protocol (STP) is used in the network loop. This protocol adopts certain algorithms to break a loop network into a loop-free tree network and thus prevents packets from increasing and cycling in an endless manner in the loop network. See Figure 5-40. Figure 5-40 Diagram of the STP
Switch A Switch A
Switch B
Switch C
Switch B Root: Switch A
Switch C
5-116
Issue 02 (2011-01-20)
The rapid spanning tree protocol (RSTP) is an optimized version of STP. Compared with the STP, the RSTP can stabilize the network topology in a shorter time. The RSTP is compatible with the STP. The STP packets and RSTP packets can be identified by the bridge that uses the RSTP for calculating the spanning tree. With the defects in the STP and RSTP fixed, the MSTP maximizes the usage of link bandwidths by setting up several independent spanning trees.
Purpose
The STP/RSTP meets the following requirements: l Any activated topology of any bridge can be configured as a single spanning tree. Redundant data loops should be removed if there is any between two stations in a network topology. The spanning tree topology can be configured in the case of a bridge fault or a route interruption. In this manner, protection is provided. Temporary data loops can be prevented by automatically accepting the bridges and ports of the bridges that are newly added into the LAN. The finally activated topology can be predicted and repeated. In addition, the topology can be selected by managing certain parameters of the 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 link bandwidths is used to create or maintain the spanning tree, and the bandwidth does not increase with the expanding network scale.
l l l
During the rapid development of the VLAN technology, the limitation of the STP/RSTP emerges. That is, after the STP/RSTP is enabled, a loop network is broken into a single spanning tree and the blocked links do not carry any traffic, which is a waste of bandwidths. The preceding defect in the STP and RSTP is fixed in the MSTP. That is, in addition to stabilizing the network topology in a short time, the MSTP enables the traffic of different VLANs to be transmitted over their respective trails and thus provides a good load sharing mechanism. l The MSTP classifies a switching network into different regions. Each region is called an MST region. Within each region, multiple spanning trees exist and they are independent from each other. Each spanning tree is called a multiple spanning tree instance (MSTI). In the case of the MSTP, the VLAN mapping table is configured to specify the mapping relations between VLANs and MSTIs. Within an MST region, each VLAN corresponds to one MSTI. That is, the data from the same VLAN can be transmitted only on the same MSTI. One MSTI, however, may correspond to multiple VLANs.
Consider the network in Figure 5-41 as an example. In this network, the packets of VLAN 1 and VLAN 2 are transmitted. After the STP/RSTP is enabled, a single spanning tree that uses switch A as the root switch is generated and the links between switch B and switch C are blocked. Hence, the bandwidth of this link is not utilized.
Issue 02 (2011-01-20)
5-117
Figure 5-41 Limitations of the STP/RSTP

Host A
Switch A
VLAN 1 VLAN 2
Host B
Switch B
Switch C
Host C
Blocked port Spanning tree Root switch
If this network is considered as an MST region in which the MSTP is enabled, VLAN 1 and VLAN 2 are mapped into corresponding MSTIs. Figure 5-42 shows the generated network topology. On the ring: l l MSTI 1 uses switch A as the root switch to forward packets of VLAN 1. MSTI 2 uses switch C as the root switch to forward packets of VLAN 2.
Through this method, packets of all VLANs can be forwarded correctly and packets of different VLANs are forwarded over different trails. In this manner, load sharing is achieved.
5-118
Issue 02 (2011-01-20)
Figure 5-42 Improvement in the MSTP

Host A
Switch A
VLAN 1 VLAN 2
Host B
Switch B
Switch C
Host C
Switch A
Switch A
VLAN 1
VLAN 1
VLAN 2
VLAN 2 Switch B MSTI 1 -> VLAN 1 Switch C Switch B Switch C
MSTI 1 -> VLAN 2
Root switch
NOTE
The OptiX RTN 980 supports only the MSTP that generates the common and internal spanning tree (CIST). Hence, the OptiX RTN 980 does not support the load sharing function that is implemented through forwarding of packets of different VLANs over different trails.
As shown in Figure 5-43, when user equipment accesses the OptiX RTN 980 through two different trails, you can configure the ports on the OptiX RTN 980 that are connected to the user network into a port group. This port group, together with the switch on the user network, can run the MSTP. Hence, if an service access link becomes faulty, the MSTP enables a reconfiguration and thus the spanning tree topology is generated to provide protection for the user network that is configured with multiple access points.
Issue 02 (2011-01-20)
5-119
Figure 5-43 Typical Application of the MSTP on the OptiX RTN 980
Root Root
Port group CIST Blocked Port

This topic describes the basic concepts that you need to be familiar with before you use the MSTP feature.
Basic Concepts of the STP/RSTP

l Bridge protocol data unit (BPDU) In the STP, BPDUs are transmitted between pieces of equipment to determine the network topology. The BPDU contains enough information that is required for computing the spanning tree. BPDUs are classified into the following types: Configuration BPDU (CBPDU) The CBPDU computes the spanning tree and maintains the spanning tree topology. A 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 notifies the relevant equipment of the network topology change. l Bridge ID The bridge ID identifies a bridge. The bridge ID is 64-bit long. The most significant 16 bits indicate the priority of the bridge, and the less 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. When the bridge ID is smaller, the priority of the bridge is higher. l Port ID The port ID identifies 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. When the value of the port ID is smaller, the priority of the port is higher. 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 CBPDUs periodically. The other bridges only relay these CBPDUs. Through this method, a stable network topology is ensured. If the network topology changes, the root bridge may also change. l 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, root path cost of which is the smallest, is selected as the root port. If several ports have the smallest root path cost, the port with the smallest port ID is selected as the root port. l 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 several ports have the smallest root path cost and these ports are on different bridges, the port on the bridge that has the smallest ID is selected as the designated port. If several ports all of which have the smallest root path cost are on the same bridge, the port with the smallest port ID is selected as the designated port. l Path cost The path cost indicates the status of the network to which the port is connected. When the rate of the port is higher, the path cost is smaller. l Root path cost The root path cost refers to the cost of the path from a certain port to the root bridge. That is, the root path cost is equal to the sum of path cost values of all the traversed ports from this port to the root bridge. l Port state In a network that enables the STP, the port can be in any of the following states: Blocking A port in the blocking state receives and processes the BPDU and does not transmit the BPDU. When a port is in the listening state, it neither learns the MAC address nor forwards 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 forwarding state, it learns the MAC address and forwards the user packet. Disabled A port in the disabled state cannot forward frames or implement the spanning tree algorithm and STP.

NOTE
The blocking, listening, and disabled states are combined into the discarding state in 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 rapid transition requests and responses. The point-to-point attribute is defined only in RSTP.
Edge port An 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 BPDUs, 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 defined only in RSTP.
Timer Port timers are classified into the following types: Hold timer The hold timer is used to measure the interval between two CBPDU transmissions. The timeout value is equal to the Hold Time of the bridge. Message timer The message age timer is used to measure the age of the CBPDU recorded by a port. When the age of the CBPDU stored by the bridge exceeds the Message Age parameter, the bridge discards this CBPDU. The Message Age parameter determines the initialization age when the CBPDU is stored in the bridge. The Message Age parameter is 0 when the root bridge generates the CBPDU. Each time when 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. TCN timer The topology change notification (TCN) timer indicates the duration when the bridge periodically transmits the TCN. The timer is used to notify the designated bridge in the 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
5-122
Issue 02 (2011-01-20)
When a TCN is received, the root bridge transmits another 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 the three parameters that are used by the root bridge, with CBPDUs transmitted between these bridges.
Port Group
When multiple ports on the OptiX RTN 980 are connected to the same user network, enable the MSTP for these ports and the user network to prevent the occurrence of loops. These ports that are connected to the user network should be first classified as a port group, and this port group is equivalent to a bridge where the MSTP protocol is running.
CIST
The CIST is generated through the computation of RSTP algorithms. The CIST is a spanning tree that connects all the switches within a switching network.
This topic provides the specifications of STP. Table 5-63 lists the specifications of STP. Table 5-63 Specifications of STP Item Type of the STP Specification STP MSTP
NOTE The OptiX RTN 980 supports only the MSTP that generates the CIST.
Starting/Stopping the STP Application scope of the STP Bridge parameters Port parameters
Supported All the port groups 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
Querying the running information of the STP Interconnection with the equipment on which the STP/RSTP is enabled
Issue 02 (2011-01-20)
5-123
Item Enabling an automatic re-configuration and thus generating the spanning tree topology in the case of a link fault Topology stabilization duration
Specification Supported
In the case of rapid migration under a typical networking scenario, the maximum stabilization duration is less than one second. In the case of non-rapid migration, the maximum stabilization duration is less than one minute. Supported
Hot standby mechanism for STP configuration and status in the case of the switching between the active and standby system control, cross-connect, and timing boards

This section describes the standards and protocols associated with MSTP. The MSTP complies with IEEE 802.1s.
NOTE
The OptiX RTN 980 supports only the MSTP that generates the CIST.
5.6.5 Availability
This section describes the support required by the application of the MSTP feature and its dependency.

Table 5-64 Hardware and version support Feature MSTP Applicable Board CSHN IFU2 IFX2 ISU2 Applicable Hardware Version All the versions All the versions All the versions All the versions Applicable Product Version V100R003C00 and later V100R003C00 and later V100R003C00 and later V100R003C00 and later
Issue 02 (2011-01-20)
5-124
Feature
Applicable Board ISX2 EM6T EM6F
Applicable Hardware Version All the versions All the versions All the versions
Applicable Product Version V100R003C00 and later V100R003C00 and later V100R003C00 and later
Feature Dependency
The MSTP is associated with the LAG and ERPS. l l l One LAG can be a member of the MSTP port group. The members of the MSTP port group cannot be involved in the ERPS. The members of the MSTP port group cannot be involved in the configuration of E-Line services.
5.6.6 Principles
The MSTP complies with IEEE 802.1s. The OptiX RTN 980 supports only the MSTP that generates the CIST.
STP Algorithm
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: (1) The bridge compares the root bridge IDs. When the root bridge ID is smaller, the priority is higher. (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 better, 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, the bridge needs to process it as follows:
2.
Issue 02 (2011-01-20)
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 (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 CBPDU that is stored 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 that is recorded by the port is different from the root bridge ID of the bridge. 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 elapses, 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 Delay parameter, the root port and the designated port change to the forwarding state. The other ports change to the blocking state. 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 computed again, and a new trail will be generated to replace the faulty trail, thus restoring the connectivity of the network.
8.
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. The alternate port refers to a port that is blocked because the BPDU transmitted by another bridge is learnt. The backup port refers
to a port that is blocked because the BPDU transmitted by the bridge where the port resides is learnt. 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 To support the quick migration between port states, the point-to-point attribute of a port and edge port are defined 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 point-to-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 root port or designated port whose actual port-to-point attribute is "True" can transmit the rapid state migration request and response. Edge port The edge port refers to a bridge port that is connected only to the LAN. If a port is set as an edge port and this port does not receive the BPDU, the port is an actual edge port. If the port role of this edge port is a designated port, the actual port state can be quickly migrated. 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 realize quick migration between port states through rapid switching 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.
Computation of the CIST

The bridge IDs contained in the received BPDUs are compared, and the bridge with the smallest ID is selected as the root bridge of the CIST. Computed through the running of the RSTP algorithm, the CIST is a spanning tree that connects all the bridges in a LAN.
5.6.7 Planning Principles

When planning MSTP, abide by the following principles: l l l l It is recommended that you enable the STP if the links that gain access to the customer equipment have loops. When enabling the MSTP, it is recommended that you add only a port that is on the bridge and that is connected to the customer equipment to a port group. It is recommended that you enable the MSTP protocol when the connected customer equipment does not require the STP type. Set the bridge parameters, port parameters, and point-to-point attributes of the spanning tree protocol, according to the requirements of the customer equipment. It is recommended that you use the default values, unless otherwise specified.

To use the MSTP protocol, you need to configure the port group, set the bridge parameters and CIST parameters, and then enable the MSTP protocol. Table 5-65 Procedure for configuring the MSTP Step 1 Operation A.6.6.1 Creating the MSTP Port Group Description Required when you need to configure the MSTP. Set the parameters as follows: l Set Protocol Type, Board, and Selected Port List according to the network planning information. l Subsequent adjustments to the MSTP parameters in the configuration process may affect the use of the MSTP protocol. Hence, it is recommended that you set Enable Protocol to Disabled. 2 A.6.6.2 Setting the Bridge Parameters of the MSTP A.6.6.3 Setting the Parameters of the CIST A.6.6.6 Enabling/ Disabling the MSTP Protocol Optional. Use the default value unless otherwise specified.
Optional. Use the default value unless otherwise specified. Required when you need to configure the MSTP. Set Enable Protocol to Enabled to enable the MSTP protocol.

This topic uses an example to describe how to plan and configure the MSTP according to the conditions of the network.
5-128
Issue 02 (2011-01-20)
5.6.9.1 Networking Diagram This topic describes the networking information about the NEs. 5.6.9.2 Service Planning The service planning information contains all the parameter information required for configuring the NE data. 5.6.9.3 Configuration Process This topic describes the procedure for the data configuration.

This topic describes the networking information about the NEs. As shown in Figure 5-44, NE1 is the OptiX RTN 980, and LAN switch 1 and LAN switch 2 are two Ethernet switches that run the MSTP protocola. l l The Ethernet port on LAN switch 1 is connected to port 1 on the EM6T board in slot 2 of NE1. The Ethernet port on LAN switch 2 is connected to port 2 on the EM6T board in slot 2 of NE1.
After the port group is configured for NE1, NE1 runs the MSTP protocol together with LAN switch 1 and LAN switch 2 on the access side, considering LAN switch 1 as the root. In this manner, no loops will be generated on the network on the access side and thus the protection for the network is realized.
NOTE
a: The OptiX RTN 980 supports only the MSTP that generates the CIST.

ETH LAN Swich 1 Root NE1 ETH NodeB LAN Swich 2 ETH Port group NodeB NodeB
RNC

Information About the Port Group

The parameters of NE1 need to be set according to the network planning information. Refer to Table 5-66. Table 5-66 Parameters of an MSTP port group Parameter Protocol Type Enable Protocol Board where the member ports are located Member ports NE1 MSTP Enableda 2-EM6T 2-EM6T-1 2-EM6T-2
NOTE
a: It is recommended that you set Enable Protocol to Disabled when creating an MSTP port group and that you set Enable Protocol to Enabled after all the MSTP parameters are set. In this manner, the possible impacts on the MSTP protocol are prevented in the case of modifications to the MSTP parameters.
Bridge Parameters
The bridge parameters of NE1 need to be set according to the planning information about the LAN switches on the access side. Refer to Table 5-67. Table 5-67 Bridge parameters Parameter Network Diameter Hello Time (s) Max Age (s) Forward Delay (s) Enable Edge Attribute Point-to-Point Attribute Max Transmit Packet Count NE1 7 2 20 15 Disabled auto 3
CIST Parameters
The CIST parameters of NE1 need to be set according to the planning information about the LAN switches on the access side. Refer to Table 5-68.
Table 5-68 CIST Parameter Parameter Bridge Priority Port Priority Path Cost NE1 32768 128 200000

Procedure
Step 1 See A.6.6.1 Creating the MSTP Port Group and create the MSTP port group. The values for the relevant parameters of NE1 are provided as follows. Parameter Protocol Type Enable Protocol Board Selected Port List Value Range MSTP Disabled 2-EM6T 2-EM6T-1 2-EM6T-2
Step 2 See A.6.6.2 Setting the Bridge Parameters of the MSTP and set bridge parameters of the MSTP. The values for the relevant parameters of NE1 are provided as follows. Parameter Network Diameter Hello Time(s) Max Age(s) Forward Delay(s) Enable Edge Attribute Point-to-Point Attribute Max Transmit Packet Count Value Range 7 2 20 15 Disabled auto 3
Step 3 See A.6.6.3 Setting the Parameters of the CIST and set the CIST parameters.
The values for the relevant parameters of NE1 are provided as follows. Parameter Bridge Priority Priority Path Cost Value Range 32768 128 200000
Step 4 See A.6.6.6 Enabling/Disabling the MSTP Protocol and enable or disable the MSTP protocol. The values for the relevant parameters of NE1 are provided as follows. Parameter Protocol Type Value Range Enabled
----End

This topic provides the hyperlinks of the operation tasks regarding the MSTP feature.
Related Tasks
A.6.6.1 Creating the MSTP Port Group A.6.6.2 Setting the Bridge Parameters of the MSTP A.6.6.3 Setting the Parameters of the CIST A.6.6.4 Querying the CIST Running Information A.6.6.5 Changing the Spanning Tree Protocol Used by the Port Group A.6.6.6 Enabling/Disabling the MSTP Protocol A.6.6.7 Modifying the Configuration Data of the MSTP Port Group

When the status of the MSTP port changes, the system control unit reports the relevant performance events.
Relevant Alarms
None.

MSTP port state change event When the status of the MSTP port changes, the system control unit reports this performance event.
5.6.12 FAQs
This topic describes the answers to the questions that are frequently raised when the MSTP feature is adopted. Q: In the case of the OptiX RTN 980, what are similarities and differences between the MSTP and ERPS features? A: Both the MSTP and ERPS protect against loops on the Ethernet ring network. The realization principles of the MSTP and ERPS, however, are different. Hence, the MSTP and ERPS feature different advantages and disadvantages. l The MSTP supports Ethernet ring networks and mesh networks. The realization principles of the MSTP are complex and the traffic directions are difficult to verify. In addition, large volumes of network resources are required to realize the MSTP. When a fault occurs on the network, the network topology takes a long time to recover to the stable state. The ERPS supports only Ethernet ring networks and does not support intersecting or tangent ring networks. The realization principles of the ERPS are simple. In addition, the ERPS occupies fewer network resources and requires the shorter switching time.
5.7 Link Aggregation Group

Link aggregation allows multiple links that are attached to the same equipment to be aggregated together to form a link aggregation group (LAG) so that the bandwidth is increased and the reliability of the links is improved. The aggregated links can be considered as a single logical link. 5.7.1 Introduction This section provides the definition of LAG and describes its purpose. 5.7.2 Basic Concepts This topic describes the basic concepts that you need to be familiar with before you use the LAG feature. 5.7.3 Specifications This section describes the specifications of LAGs. 5.7.4 Reference Standards and Protocols This section describes the standards and protocols associated with LAGs. 5.7.5 Availability This section describes the support required by the application of the LAG feature and its dependency. 5.7.6 Principles The LACP protocol is used to realize dynamic aggregation and de-aggregation of Ethernet links. The LAG is realized in compliance with IEEE 802.3ad. 5.7.7 Planning Guidelines Follow certain principles when you plan LAGs. 5.7.8 Configuration Procedure When applying the LAG protocol, you need to configure the LAG and configure the priorities of ports in the LAG as required. 5.7.9 Configuration Example
By using an example, this topic describes how to plan and configure LAGs according to the network conditions. 5.7.10 Task Collection This topic provides the hyperlinks of the operation tasks regarding the relevant feature. 5.7.11 Relevant Alarms and Events When the LAG is unavailable or a certain member of the LAG is unavailable, the system control board reports the relevant alarms. 5.7.12 FAQs This topic provides the answers to the questions that are frequently raised when the LAG is adopted.
5.7.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 5-45, 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 5-45 Link aggregation group
Link 1 Link 2 Ethernet packet Link 3 Link aggregation group Ethernet packet
5-134
Issue 02 (2011-01-20)

This topic describes the basic concepts that you need to be familiar with before you use the LAG feature. 5.7.2.1 LAG Types By aggregation type, the LAG is classified into the manual aggregation and the static aggregation. By load type, the LAG is classified into the load sharing and the load non-sharing. 5.7.2.2 Port Types In the LAG, ports are classified into the main port and slave port. 5.7.2.3 Switching Condition A service is switched between ports when a port fails or the key chip of a port is faulty. 5.7.2.4 Switching Impact During a LAG switching (the switching time is less than 500 ms), all the services on the link are interrupted.
5.7.2.1 LAG Types

By aggregation type, the LAG is classified into the manual aggregation and the static aggregation. By load type, the LAG is classified into the load sharing and the load non-sharing.
Aggregation Types
The LAG supports the following aggregation types: l Manual aggregation A user manually creates a LAG. When a user adds or deletes a member port, the LACP protocol 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
The LAG supports the following load sharing modes:
Load sharing Each member link in a LAG carries traffic. That is, the member links in the LAG share the load. In load sharing mode, the bandwidth of the link is increased. When a member in a LAG changes or a certain link fails, the traffic is re-allocated automatically. The load sharing algorithms are as follows: Based on MAC addresses, including the source MAC address, destination MAC address, and source MAC address and destination MAC address. Based on IP addresses, including the source IP address, destination IP address, and source IP address and destination IP address. Based on MPLS labels.
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. This is because when a selected link in a LAG fails, the system selects a link among the standby links in the LAG as an active link to replace the faulty link. The OptiX RTN 980 can be configured with only one active link and one standby link. When a LAG is configured in load non-sharing mode, the LAG can be set to revertive or non-revertive. When a LAG is set to revertive, the services are switched back to the former working channel after this channel is restored to normal. When a LAG is set to nonrevertive, the status of the LAG does not change after the former working channel is restored to normal. That is, the services are still transmitted on the protection channel.
5.7.2.2 Port Types

In the LAG, ports are classified into the main port and slave port.
Main Port
The main port represents a logical port aggregated by ports of the LAG. The main port has the following features: l l l l l The main port represents the LAG to participate in service configuration. A LAG has exactly one main port. The main port can be in selected, standby, or unselected state. The main port must be in the affiliated aggregation group until the aggregation group is deleted. When the aggregation group is deleted, the services in the aggregation group continue to exist on the main port .
Slave Port
In a LAG, the ports rather than the main port are slave ports. The slave port has the following features: l l l l
5-136
The 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/deleted from the 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 5-69 Switching Conditions Switching Condition The Ethernet port is in the link down state. Description If the member port of a LAG is an Ethernet port and is in the link down state, the ETH_LOS or ETH_LINK_DOWN alarm is reported. If the member port of a LAG is a microwave port and when the POWER_ALM, VOLT_LOS,RADIO_TSL_HIGH, RADIO_TSL_LOW, RADIO_RSL_HIGH, IF_INPWR_ABN, CONFIG_NOSUPPORT, R_LOC, MW_LOF, IF_INPWR_ABN, IF_CABLE_OPEN, or MW_BER_SD alarm is reported, the system control unit considers that the microwave port is in the link down state, and thus a LAG switching is triggered.
NOTE The MW_BER_SD alarm is an optional condition.
The microwave port is in the link down state.
The hardware of a data unit, IF unit or ODU is faulty. The LACP detects a failure in the link.
If the hardware of a data unit, IF unit or ODU is faulty, the HARD_BAD or BD_STATUS alarm is reported. If the protocol packets are not received for three consecutive periods (3s), the LACP considers that the link is not available, and thus a LAG switching is triggered.

During a LAG switching (the switching time is less than 500 ms), all the services on the link are interrupted.
This section describes the specifications of LAGs. Table 5-70 lists the specifications of LAGs. Table 5-70 Specifications of LAGs Item Maximum number of supported LAGs
Issue 02 (2011-01-20)
Specification 20
5-137
Item Type of supported ports in a LAG
Specification FE/GE port Integrated IP radio port
Load sharing
Sharing Non-sharing
Number of slave ports in a LAG
7 (Sharing) 1 (Non-sharing)
LAG type
Manual aggregation Static aggregation
Load sharing
Load sharing Load non-sharing
Load sharing type (in load sharing mode only)a
Based on the source MAC address Based on the destination MAC address Based on the source IP address Based on the destination IP address Based on the source MAC address and the destination MAC address Based on the source IP address and the destination IP address Based on MPLS label
Revertive mode (in load non-sharing mode only) Switching time Distributed LAG WTR times
Revertive Non-revertive Less than 500 ms Supported 1 to 30 minutes (10 minutes, by default)
NOTE
a: All the LAGs of an NE 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
5-138
Issue 02 (2011-01-20)
5.7.5 Availability
This section describes the support required by the application of the LAG feature and its dependency.

Table 5-71 Hardware and version support Feature LAG Applicable Board CSHN IFU2 IFX2 ISU2 ISX2 EM6T EM6F Applicable Hardware Version All the versions All the versions All the versions All the versions All the versions All the versions All the versions Applicable Product Version V100R003C00 and later V100R003C00 and later V100R003C00 and later V100R003C00 and later V100R003C00 and later V100R003C00 and later V100R003C00 and later
Feature Dependency
The LAG feature has the following relationships with other features: l When you create a 1+1 HSB/FD/SD protection group of the Integrated IP radio, the NE automatically creates a LAG in non-load sharing mode. The main port is the Integrated IP radio port on the main IF board and the slave port is the Integrated IP radio port on the standby IF board. The LAG is not displayed on the NMS and cannot be configured manually. When you create an N+1 protection group of the Integrated IP radio, the NE automatically creates a LAG in load sharing mode. By default, the main port is the Integrated IP radio port on the IF board with the smallest slot ID. The LAG is not displayed on the NMS and cannot be configured manually. When you create one XPIC protection group of the Integrated IP radio, manually create the LAG because the NE does not automatically create a corresponding LAG. The links in the two directions of an XPIC workgroup cannot be configured into two LAGs. One LAG can be a member of an MSTP port group.
l l l
Issue 02 (2011-01-20)
Air interfaces can be configured into a LAG. The AM attribute, channel spacing, modulation scheme, and preset number of E1 services must be set to the same values for the two IF ports in a LAG. Ethernet ports of the same type can be aggregated into a LAG.
5.7.6 Principles
The LACP protocol is used to realize dynamic aggregation and de-aggregation of Ethernet links. The LAG is realized in compliance with IEEE 802.3ad.
LACP Protocol and Packet

In compliance with IEEE802.3ad, the LACP protocol is used to realize dynamic aggregation and de-aggregation of links. In the LACP protocol, information about the local end is sent to the opposite end by using the link aggregation control protocol data unit (LACPDU). Figure 5-46 Frame format of the LACP packet
5-140
Issue 02 (2011-01-20)
Table 5-72 Parameter Description Parameter Actor_Port/Partner_Port Actor_State/Partner_State Meaning Interface at the local end/ opposite end State of the interface at the local end/opposite end Description Indicates the port ID. The port state is 8-bit, representing states of the eight attributes, namely, LACP_Activity, LACP_Timeout, Aggregation, Synchronization, Collecting, Distributing, Defaulted, and Expired. The value of this parameter is specified by the user. Indicates the MAC address of the system. Interfaces that have the same value of this parameter can be aggregated. The operation key is used for aggregation, indicating the aggregation capacity of a port. It is determined by the management key (the value of the static aggregation is the ID of the aggregation group), rate, and duplex mode. Actor_Port_Priority/ Partner_Port_Priority Interface priority at the local end/opposite end The principle for the priorities is as follows: nondefaulted port, port in fullduplex mode, port at high rate, port with high priority, and port with smaller ID.
Actor_System_Priority/ Partner_System_Priority Actor_System/ Partner_System Actor_Key/Partner_Key
System priority at the local end/opposite end System ID at the local end/ opposite end Operation key at the local end/opposite end
Procedure for Creating the Static LAG

As shown in Figure 5-47, the LACP protocol aggregates links as follows: 1. Equipment A and equipment B exchange LACP packets through port 1, port 2, port 3, and port 4. The LACP packet contains the information such as the system priority, system MAC, port priority, port ID, and operation key.
Issue 02 (2011-01-20)
5-141
2.
After equipment B receives 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 equipment A receives 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 to 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 5-47, 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 5-47 Application of the LACP protocol

Equipment A LACP packet PORT 1 PORT 2 PORT 3 PORT 4 PORT 1 PORT 2 PORT 3 PORT 4 Equipment B
Procedure of a LAG Switching

In the case of a non-load sharing LAG, when the NE detects that a certain port in the LAG is in the link down state or that the conditions for triggering a 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 highest priority among the backup links is selected to replace the faulty link among the active links. 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 performs the switching between the ports.
5-142

NOTE
If the LAG is in the 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. l l The type of the LAG configured on the local end must be the same as that configured on the opposite end. It is recommended that both ends adopt static aggregation. The load sharing type of the LAG configured on the local end must be the same as that configured on the opposite end. It is recommended that the LAG used for protection adopt load non-sharing at both ends and that the LAG for increasing bandwidths adopt load sharing at both ends. The OptiX RTN 980 supports the load-sharing algorithm based on MAC address allocation (source MAC address, destination MAC address, AND algorithm to source MAC address and destination MAC address), IP address allocation (source IP address, destination IP address, AND algorithm to source IP address and destination IP address), and MPLS labels. It is recommended that you use the default loading 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

When applying the LAG protocol, you need to configure the LAG and configure the priorities of ports in the LAG as required.
Issue 02 (2011-01-20)
5-143
Table 5-73 Procedure for configuring the LAG St ep 1 Operation A.6.2.1 Creating a LAG Description Required if the LAG is configured to protect the FE/GE ports or if the Hybrid radio uses the N+0 non-protection scheme. 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 In the case of FE/GE ports, set Load Sharing to the same value as the opposite equipment. If the LAG is configured only to realize 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 Hybrid radio uses the N+0 non-protection scheme, 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. This parameter is valid to the non-sharing LAG only. l Set Load Sharing Hash Algorithm to the same value as the opposite equipment. Unless otherwise specified, this parameter adopts the default value. This parameter is valid to the sharing LAG only. l It is recommended that you set this parameter to the same values for the main and slave ports. In this case, you can set System Priority according to the requirements. It is recommended that this parameter adopts the default value. This parameter is valid to the static LAG only. l Set Main Board, Main Port, and Selected Slave Ports according to the planning information. It is recommended that you set these parameters to the same values for the main and slave ports. 2 A.6.2.2 Setting Parameters for LAGs Required if the non-sharing LAG has multiple slave ports and the sequence in which the slave pots take over the main port needs to be specified. Set Port Priority to a lower value for the slave port that first takes over the main port in the case of protection. Set Port Priority to higher values for the other slave ports. The highest value indicates the last slave port to take over the main port.
5-144
Issue 02 (2011-01-20)

By using an example, this topic describes how to plan and configure LAGs according to the network conditions. 5.7.9.1 Networking Diagram The topic describes the networking information about the NEs. 5.7.9.2 Service Planning The service planning information contains all the parameters required for configuring the NE data. 5.7.9.3 Configuration Process This topic describes the process for the data configuration.

The topic describes the networking information about the NEs. As shown in Figure 5-48, the Hybrid radio link between NE1 and NE2 adopts the 2+0 nonprotection scheme. Hence, the Integrated IP radio ports that correspond to the radio link need to be configured as a load-sharing LAG. Figure 5-48 Networking diagram
Link 1 Link 2 NE1 Main port: 3-IFU2-1 Standby port: 4-IFU2-1 LAG NE2 Main port: 3-IFU2-1 Standby port: 4-IFU2-1

The service planning information contains all the parameters required for configuring the NE data. Table 5-74 provides the information about LAG configuration on the NE. Table 5-74 LAG information Parameter LAG Type Load Sharing
Issue 02 (2011-01-20)
NE1 Static (default value) Sharing

ME2 Static (default value) Sharing

5-145
Parameter Load Sharing Hash Algorithm System Priority Main Port Slave Port
NE1 Source MAC (default value) 32768 (default value) 3-IFU2-1 4-IFU2-1
ME2 Source MAC (default value) 32768 (default value) 3-IFU2-1 4-IFU2-1
NOTE
The load sharing hash algorithm can be set to any of the following seven modes: source MAC, destination MAC, source and destination MAC, source IP, destination IP, source and destination IP, and MPLS label. Unless otherwise specified, set the algorithm to the default mode.

This topic describes the process for the data configuration.
Procedure
Step 1 See A.6.2.1 Creating a LAG and configure the LAG. The values for the related parameters that need to be set in the main interface are as follows. Parameter LAG No. LAG Name LAG Type Load Sharing Load Sharing Hash Algorithm System Priority Value Range Selected Automatically Assign LAG_1 Static Sharing Source MAC 65535
The values for the related parameters that need to be set in Port Setting are as follows. Parameter Main Board Main Port Selected Slave Ports Value Range 3-IFU2 1 4-IFU2-1
----End

Related Tasks
A.6.2.1 Creating a LAG A.6.2.2 Setting Parameters for LAGs A.6.2.3 Querying the Protocol Information of the LAG

When the LAG is unavailable or a certain member of the LAG is unavailable, the system control board reports the relevant alarms.
Relevant Alarms
l LAG_DOWN The LAG_DOWN alarm indicates that the LAG is unavailable. This alarm is reported when the number of activated members in the LAG is 0. l LAG_MEMBER_DOWN The LAG_MEMBER_DOWN alarm indicates that at least one member of the LAG is unavailable. The system reports this alarm when any member of the LAG cannot be activated or work as a standby port.

None.
5.7.12 FAQs
This topic provides the answers to the questions that are frequently raised when the LAG is adopted. Q: Does the OptiX RTN 980 support the dynamic LAG? A: The OptiX RTN 980 does not support the dynamic LAG.
5.8 Link State Pass Through

This chapter describes the link state pass through (LPT) feature. 5.8.1 Introduction This section provides the definition of LPT and describes its purpose. 5.8.2 Basic Concepts This section describes the basic concepts associated with LPT. 5.8.3 Specifications This section describes the specifications for LPT. 5.8.4 Reference Standards and Protocols
This section describes the standards and protocols associated with LPT. 5.8.5 Availability This section describes the support required by the application of the LPT feature and its dependencies. 5.8.6 Principles LPT is implemented by transmitting specific packets. The approaches of implementation vary according to faults. 5.8.7 Configuration Procedure The configuration procedure for LPT contains only one configuration task. 5.8.8 Configuration Example (LPT for Services Traversing an L2 Network) With an example, this section describes how to plan and configure LPT according to network conditions. 5.8.9 Configuration Example (LPT for Services Traversing a PSN) With an example, this section describes how to plan and configure LPT according to network conditions. 5.8.10 Task Collection This section provides the hyperlinks of the operation tasks associated with the feature. 5.8.11 Relevant Alarms and Events When a service network fault is detected by using LPT or a notification of a fault detected by LPT is received, the NE reports the corresponding alarm. 5.8.12 FAQs This section provides answers to the questions that are frequently raised when LPT is used.
5.8.1 Introduction
This section provides the definition of LPT and describes its purpose.
Definition
Link State Pass Through (LPT) detects a fault that occurs at a service access node or on a service network, and then instructs the equipment at both ends of a service network to immediately start a backup network for communication. LPT ensures proper transmission of important data. As shown in Figure 5-49, LPT-enabled NE1 and NE2 will disconnect their access links from router A and router B if access link 1, access link 2, or the service network becomes faulty. As a result, router A and router B will immediately detect the link fault between them, and switch to backup networks for communication.
5-148
Issue 02 (2011-01-20)
Figure 5-49 Typical application of LPT
Backup network
Service network Router A Access link 1 Working link Protection link NE1 NE2 Access link 2 Router B
Purpose
With the LPT function enabled, access equipment will immediately detect link faults and switch to backup networks timely.

This section describes the basic concepts associated with LPT. 5.8.2.1 Point-to-Point LPT Point-to-point LPT applies to a network where one access link corresponds to one port/service channel of a service network. 5.8.2.2 Point-to-Multipoint LPT Point-to-multipoint LPT applies to a network where one access link corresponds to multiple ports/service channels of a service network, or a network where multiple access links correspond to one port/service channel of a service network.
5.8.2.1 Point-to-Point LPT

Point-to-point LPT applies to a network where one access link corresponds to one port/service channel of a service network.
Service Types
Point-to-point LPT is applicable to the following service types: l l
Issue 02 (2011-01-20)
L2 services QinQ services exclusively occupying UNIs

E-Line services carried by PWs that exclusively occupy UNIs

NOTE
l L2 services include UNI-UNI E-Line services and UNI-UNI E-LAN services transmitted in a point-to-point manner. l For the service models of QinQ services exclusively occupying UNIs, see Model 1 and Model 2 in 5.3.2.2 QinQ-Based E-Line Services. l For E-Line services carried by PWs that exclusively occupy UNIs, see Model 3 in 6.8.2.4 E-Line Services Carried on PWs.
LPT Application
Figure 5-50 shows an LPT application in point-to-point private line services. Figure 5-50 Network 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 normal cases, router A and router B communicate data through network service devices NE1 and NE2. When the link between router A and router B is faulty (the fault may occur on access link 1, access link 2, or the service network), the communication between router A and router B is interrupted. NE1 and NE2 will notify the routers of the fault by disconnecting the access links if providing the point-to-point LPT function for the Ethernet services between the routers. After receiving the notification, the routers will switch to the backup network for communication.
Service Network Types

Point-to-point LPT packets can traverse the following service networks: l L2 networks The LPT-enabled port on an L2 service network must have unique NET IDs. An LPT packet can carry a VLAN ID according to the requirement of the L2 network.
QinQ networks The LPT-enabled NEs at both ends of a QinQ service network push or pop S-VLAN tags. An LPT packet carries the same S-VLAN ID as the service that is transmitted over the QinQ network.
Packet switched networks (PSNs) The LPT-enabled NEs at both ends of a PSN are provider edges (PEs) that transmit ETH PWE3 services. An LPT packet carries the same PW label as the service that is transmitted over the PSN.
5.8.2.2 Point-to-Multipoint LPT

Point-to-multipoint LPT applies to a network where one access link corresponds to multiple ports/service channels of a service network, or a network where multiple access links correspond to one port/service channel of a service network.
Service Types
Point-to-multipoint LPT is applicable to the following service types: l l l L2 services QinQ services sharing UNIs E-Line services carried on PWs sharing UNIs
NOTE
l L2 services include UNI-UNI E-Line services and UNI-UNI E-LAN services transmitted in a point-tomultipoint manner. l For the service models of QinQ services sharing UNIs, see Model 3 in 5.3.2.2 QinQ-Based E-Line Services. l For the service model of E-Line services carried on PWs sharing UNIs, see Model 1 and Model 2 in 6.8.2.4 E-Line Services Carried on PWs.
LPT Application
Figure 5-51 shows an LPT application in point-to-multipoint convergence services.
Issue 02 (2011-01-20)
5-151
Figure 5-51 Network diagram of point-to-multipoint LPT

Backup network
Port2 Port1 Port3 Port1 Access link 1 NE1 Port2 Port1 NE3 Backup network Port3 Router C Service network Port2 Access link 3 NE2 Access link 2 Router B
Router A
Access link 4 Router D
Protection link Working link
In normal cases, router A communicates with router B, router C, and router D through network service devices NE1, NE2, and NE3. When the link between router A and the other routers is faulty (the fault may occur on access link 1, access link 2, access link 3, access link 4, or the service network), router A cannot communicate with the other routers. NE1, NE2, and NE3 will notify the routers of faults by disconnecting the access links if providing the point-to-multipoint LPT function for the Ethernet services between router A and the other routers. After receiving the notification, the routers will switch to the backup networks for communication.
Service Network Types

Point-to-multipoint LPT packets can traverse the following networks: l L2 networks The LPT-enabled port on an L2 service network must have unique NET IDs. An LPT packet can carry a VLAN ID according to the requirement of the L2 network. l QinQ networks The LPT-enabled NEs at both ends of a QinQ service network push or pop S-VLAN tags. An LPT packet carries the same S-VLAN ID as the service that is transmitted over the QinQ network. l Packet switched networks (PSNs) The LPT-enabled NEs at both ends of a PSN are provider edges (PEs) that transmit ETH PWE3 services. An LPT packet carries the same PW label as the service that is transmitted over the PSN.
This section describes the specifications for LPT. Table 5-75 lists the specifications for LPT.
Table 5-75 Specifications for LPT Item LPT type Specification Point-to-point LPT Point-to-multipoint LPT Applicable service network type Point-to-point LPT Point-to-multipoint LPT L2 network QinQ network PSN 16 Strict mode Non-strict mode (available only to point-tomultipoint LPT) Setting of fault recovery time Setting of hold-off time Setting of LPT OAM detection packet transmission Fault detection method on a service network Supported Supported Supported LPT OAM PW OAM (supported only when the service network is a PSN)
Number of services supporting LPT Switching mode

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

Table 5-76 Hardware and version support Feature LPT Applicable Board IFU2 IFX2 Applicable Hardware Version All the versions All the versions Applicable Product Version V100R003C00 and later V100R003C00 and later
5-153
Issue 02 (2011-01-20)
Feature
Applicable Board ISU2 ISX2 CSHN EM6T EM6F
Applicable Product Version V100R003C00 and later V100R003C00 and later V100R003C00 and later V100R003C00 and later V100R003C00 and later
l l An Ethernet port with LPT enabled must work in auto-negotiation mode. LPT can work together with other protection schemes.
5.8.6 Principles
LPT is implemented by transmitting specific packets. The approaches of implementation vary according to faults. 5.8.6.1 LPT Fault Detection Regarding the LPT feature, it uses different mechanisms for detecting an access-side fault and a network-side fault. 5.8.6.2 Switching Principles of Point-to-Point LPT For point-to-point services, the LPT switching against an access-side fault is implemented differently from the LPT switching against a network-side fault. 5.8.6.3 Switching Principles of Point-to-Multipoint LPT For point-to-multipoint services, the LPT switching against an access-side fault is implemented differently from the LPT switching against a network-side fault.
5.8.6.1 LPT Fault Detection

Regarding the LPT feature, it uses different mechanisms for detecting an access-side fault and a network-side fault.
Mechanism for Detecting an Access-Side Fault

l l If an LPT-enabled port on the access side is not in a LAG, the LPT switching is triggered when the port is in link down state. If an LPT-enabled port on the access side is in a LAG, the LPT switching is triggered when all ports in the LAG are in link down state.
5-154
Mechanism for Detecting a Network-Side Fault

l LPT-enabled NEs periodically transmit LPT OAM packets in specific formats to check the status of an L2 service network or QinQ service network. If the LPT OAM packets are absent for 3.5 fault detection periods or the number and contents of received LPT OAM packets are incorrect, the NEs consider that a network-side fault occurred and the LPT switching is triggered. To detect a network-side fault on a PSN, LPT OAM or PW OAM packets can be used. Note that the PW OAM function must be enabled on NEs before usage of PW OAM packets.
Fault Detection Modes

The strict mode or non-strict mode can be used in point-to-multipoint LPT for detecting faults. l l Strict mode A primary point triggers LPT switching when all of its secondary points detect faults. Non-strict mode A primary point triggers LPT switching when anyone of its secondary points detects a fault. In the point-to-point LPT mechanism, one primary point corresponds to one secondary point. Therefore, only the strict mode is available for point-to-point LPT.
5.8.6.2 Switching Principles of Point-to-Point LPT

For point-to-point services, the LPT switching against an access-side fault is implemented differently from the LPT switching against a network-side fault.
NOTE
Pertaining to different service networks, the LPT switching principles are the same but the LPT packet formats are different.
Point-to-Point LPT Switching Against an Access-Side Fault

l During an access-side fault period Figure 5-52 shows the process. Service equipment A reports a link fault alarm when detecting that the link connected to access node 1 is faulty. In addition, service equipment A transmits Broken packets to service equipment B. On the receipt of the Broken packets, service equipment B shuts down its Ethernet port and reports the LPT_CFG_CLOSEPORT alarm. Figure 5-52 Point-to-point LPT switching during an access-side fault period
Reporting the link fault alarm Access node 1 Service equipment A Disabling the Ethernet port, and reporting the LPT_CFG_CLOSEPORT alarm Service equipment B Access node 2
Service network Broken
Issue 02 (2011-01-20)
5-155
After rectification of an access-side fault Figure 5-53 shows the process. Service equipment A stops reporting the link fault alarm and transmits Non_Broken packets to service equipment B, when detecting that the link fault is rectified. On the receipt of the Non_Broken packets, service equipment B starts up its Ethernet port.
Figure 5-53 Point-to-point LPT switching after rectification of an access-side fault

Stopping reporting the link fault alarm Access node 1 Service equipment A Service network Non_Broken Enabling the Ethernet port again Service equipment B Access node 2
LPT Switching Against a Network-Side Fault

l During a network-side fault period Figure 5-54 shows the process. A fault occurs on the service network in the direction from service equipment A to service equipment B. As a result, service equipment B disconnects its link to access node 2. In addition, service equipment B sends Broken packets to service equipment A. On the receipt of the Broken packets, service equipment A disconnects its link to access node 1. Figure 5-54 Point-to-point LPT switching during a network-side fault period
Service network Access node 1 Service equipment A Service equipment B Access node 2
Broken
NOTE
The mechanism for detecting a bidirectional fault is the same as that for detecting a unidirectional fault. LPT_CFG_CLOSEPORT alarms, however, will not be reported because service equipment A and service equipment B cannot receive Broken packets.
After rectification of a network-side fault Figure 5-55 shows the process. Service equipment A or service equipment B sends Non_Broken packets to each other for notifying link restoration, when detecting that the service network is restored. In addition, service equipment A or service equipment B stops reporting LPT_CFG_CLOSEPORT alarms and restores its connections to the access nodes.
5-156
Issue 02 (2011-01-20)
Figure 5-55 Point-to-point LPT switching after rectification of a network-side fault
Enabling the port and stopping reporting the alarm Access node 1 Service equipment A
Service network
Enabling the port, and stopping reporting the alarm Service equipment B Access node 2
Non_Broken Network restoration
5.8.6.3 Switching Principles of Point-to-Multipoint LPT

For point-to-multipoint services, the LPT switching against an access-side fault is implemented differently from the LPT switching against a network-side fault.
NOTE
Pertaining to different service networks, the LPT switching principles are the same but the LPT packet formats are different.
Point-to-Multipoint LPT Switching Against an Access-Side Fault

l During an access-side fault period Figure 5-56 shows the process. Service equipment A reports a link fault alarm when detecting that the link connected to the convergence node is faulty. 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 shut down their Ethernet ports and report LPT_CFG_CLOSEPORT alarms. Figure 5-56 Point-to-multipoint LPT switching during an access-side fault period
Disabling the port, and reporting the LPT_CFG_CLOSEPORT alarm Broken Service equipment B Access node 1
Disabling the port, and reporting the link fault alarm Convergence node Service equipment A
Broken
Disabling the port, and reporting the LPT_CFG_CLOSEPORT alarm Access Service equipment C node 2
After rectification of an access-side fault Figure 5-57 shows the process. Service equipment A stops reporting the link fault alarm and transmits Non_Broken packets to service equipment B and service equipment C, when detecting that the link fault is rectified. On the receipt of the Non_Broken packets, service equipment B and service equipment C start up their Ethernet ports.
Issue 02 (2011-01-20)
5-157
Figure 5-57 Point-to-multipoint LPT switching after rectification of an access-side fault

Stopping reporting the link fault alarm Convergence node Enabling the port again Non_Broken Service equipment A Non_Broken Service equipment C Service equipment B Access node 1
Enabling the port again Access node 2
NOTE
l Broken packets, Non_Broken packets, and LPT detection packets have the same format but different contents. l In this example, the primary point detects the fault. If the secondary point detects the fault, the LPT switching is similar but pertains to the switching mode. Specifically, if the switching mode is set to the non-strict mode, a primary point triggers LPT switching when anyone of its secondary points detects a fault; if the switching mode is set to the strict mode, a primary point triggers LPT switching when all of its secondary points detect faults.
Point-to-Multipoint LPT Switching Against a Network-Side Fault

l During a network-side fault period Figure 5-58 shows the process. A fault occurs on the service network in the direction from service equipment B to service equipment A. As a result, service equipment A disconnects its links to access node A and access node B. In addition, service equipment A sends Broken packets to service equipment B. On the receipt of the Broken packets, service equipment B disconnects its links to access node A' and access node B'. Figure 5-58 Point-to-multipoint LPT switching during a network-side fault period
Access node A Disabling the port, and reporting Disabling the port, and reporting the LPT_CFG_CLOSEPORT the LPT_CFG_CLOSEPORT alarm alarm Service network Service equipment A Access node B Broken Disabling the port, and reporting the LPT_CFG_CLOSEPORT alarm Disabling the port, and reporting the LPT_CFG_CLOSEPORT alarm Service equipment B Access node B' Access node A'
NOTE
The mechanism for detecting a bidirectional fault is the same as that for detecting a unidirectional fault. LPT_CFG_CLOSEPORT alarms, however, will not be reported because service equipment A and service equipment B cannot receive Broken packets.
After rectification of a network-side fault Figure 5-59 shows the process. Service equipment A or service equipment B sends Non_Broken packets to each other for notifying link restoration, when detecting that the service network is restored. In addition, service equipment A or service equipment B stops reporting LPT_CFG_CLOSEPORT alarms and restores its connections to the access nodes.
5-158
Issue 02 (2011-01-20)
Figure 5-59 Point-to-multipoint LPT switching after rectification of a network-side fault

Access node A Enabling the port, and stops reporting the alarm Service equipment A Access node B Enabling the port, and stops reporting the alarm Non_Broken Enabling the port, and stops reporting the alarm Service equipment B Enabling the port, and stops reporting the alarm Access node B' Access node A'
Network restoration

The configuration procedure for LPT contains only one configuration task.

Figure 5-60 provides procedures for configuring LPT. Figure 5-60 Configuration flow chart
Required Optional Start When the service network is an L2 network Configuring Point-to-Point LPT Traversing an L2 Network When the service network is a PSN or QinQ network Configuring Point-to-Point LPT Traversing a PSN or QinQ Network Configuring Point-toMultipoint LPT Start
End
End
Issue 02 (2011-01-20)
5-159
Configuration Procedure
Table 5-77 Procedures for configuring LPT for point-to-point services Step 1 Operation Configur ing point-topoint LPT A.6.10.1 Configuring Point-toPoint LPT Traversing an L2 Network Description Required when LPT needs to be configured for point-to-point services traversing an L2 network. Set parameters according to the service plan.
NOTE Before configuring LPT for pointto-point services traversing an L2 network, ensure that L2 services have been configured. L2 services include UNI-UNI E-Line services and UNI-UNI E-LAN services transmitted in a point-to-point manner.
A.6.10.2 Configuring Point-toPoint LPT Traversing a PSN or QinQ Network
Required when LPT needs to be configured for point-to-point services traversing a PSN or QinQ network. Set parameters according to the service plan.
NOTE l Before configuring LPT for point-to-point services traversing a PSN, ensure that ELine services carried by PWs that exclusively occupy UNIs have been configured. l Before configuring LPT for point-to-point services traversing a QinQ network, ensure that QinQ services exclusively occupying UNIs have been configured.
5-160
Issue 02 (2011-01-20)
Table 5-78 Procedures for configuring LPT for point-to-multipoint services Step 1 Operation A.6.10.3 Configuring Point-toMultipoint LPT Description Required. Set parameters according to the service plan.
NOTE Before configuring LPT for point-tomultipoint services, ensure that at least one of the following types of services has been configured: l L2 services l QinQ services sharing UNIs l E-Line services carried on PWs sharing UNIs
5.8.8 Configuration Example (LPT for Services Traversing an L2 Network)

With an example, this section describes how to plan and configure LPT according to network conditions. 5.8.8.1 Network Diagram This section describes the networking information about the NEs. 5.8.8.2 Service Planning The service planning information contains all required parameters. 5.8.8.3 Configuration Process This section describes the process of data configuration.
5.8.8.1 Network Diagram

This section describes the networking information about the NEs. On the network as shown in Figure 5-61, NE1, NE2, and NE3 transmit services between routers through VLAN-based E-Lines. When faults occur on the network between NE1 and NE2 and the network between NE1 and NE3, NE1, NE2, and NE3 need to disconnect their access links to instruct router A, router B, and router C respectively to start a backup network for uninterrupted communication. Therefore, point-to-multipoint LPT needs to be configured on NE1, and point-to-point LPT needs to be configured on NE2 and NE3.
Issue 02 (2011-01-20)
5-161
Figure 5-61 Network diagram of LPT (traversing an L2 network)

4-EM6T-1 (to Router A) 1-ISU2-1 (to NE2) 2-ISU2-1 (to NE3) VLAN:100, 200 NE2 Router A Router B 4-EM6T-1 (to Router B) 1-ISU2-1 (to NE1) VLAN:100
NE1
VLAN:200
NE3
Router C
4-EM6T-1 (to Router C) 1-ISU2-1 (to NE1)

The service planning information contains all required parameters.
LPT Configuration Information

Table 5-79 provides LPT configuration information. Table 5-79 Configuration information of NE1 Parameter LPT type Primary point Point type Port Secondary point 1 Point type Port (LPT package out port) Local L2 net ID L2 peer net ID VLAN ID carried by an LPT packet Secondary point 2
5-162
NE1 Point-to-multipoint LPT UNI 4-EM6T-1 L2NET 1-ISU2-1 11 21 100 L2NET

Issue 02 (2011-01-20)
Point type
Parameter Port (LPT package out port) Local L2 net ID L2 peer net ID VLAN ID carried by an LPT packet
NE1 2-ISU2-1 12 31 200
Table 5-80 Configuration information of NE2 Parameter LPT type Port of the primary point Port of the secondary point (LPT package out port) Local L2 net ID L2 peer net ID VLAN ID carried by an LPT packet NE2 Point-to-point LPT 4-EM6T-1 1-ISU2-1 21 11 100
Table 5-81 Configuration information of NE3 Parameter LPT type Port of the primary point Port of the secondary point (LPT package out port) Local L2 net ID L2 peer net ID VLAN ID carried by an LPT packet NE3 Point-to-point LPT 4-EM6T-1 1-ISU2-1 31 12 200
Configuration Information of LPT

In this example, NE1, NE2, and NE3 all take the default LPT parameter values. See Table 5-82.
Issue 02 (2011-01-20)
5-163
Table 5-82 Configuration information of LPT Parameter Recovery Time(s) Hold-Off Time(ms) Switching Mode Fault Detection Mode Fault Detection Period(100ms) NE1 1 1000 Strict mode LPT OAM 10 NE2 1 1000 LPT OAM 10 NE3 1 1000 LPT OAM 10

This section describes the process of data configuration.
Procedure
Step 1 See A.6.10.3 Configuring Point-to-Multipoint LPT and configure point-to-multipoint LPT on NE1. l The values for the relevant parameters of NE1 are provided as follows. Set parameters for the primary point as follows. Parameter Point Type Board Port Value UNI 4-EM6T 4-EM6T(PORT-1)
Set parameters for secondary points 1 and 2 as follows. Parameter Value Available Point 1 Point Type L2 net ID L2 Peer net ID LPT package out port VLAN ID L2NET 11 21 1-ISU2-1 (PORT-1) 100 Available Point 2 L2NET 12 31 2-ISU2-1 (PORT-1) 200
Step 2 See A.6.10.1 Configuring Point-to-Point LPT Traversing an L2 Network and configure point-to-point LPT (traversing an L2 network) on NE2 and NE3.
l The values for the relevant parameters of NE2 and NE3 are provided as follows. Parameter Value NE2 L2 net ID L2 Peer net ID Primary Function Point LPT package out port VLAN ID 21 11 4-EM6T-1 (PORT-1) 1-ISU2-1 (PORT-1) 100 NE3 31 12 4-EM6T-1 (PORT-1) 1-ISU2-1 (PORT-1) 200
----End
5.8.9 Configuration Example (LPT for Services Traversing a PSN)

With an example, this section describes how to plan and configure LPT according to network conditions. 5.8.9.1 Network Diagram This section describes the networking information about the NEs. 5.8.9.2 Service Planning The service planning information contains all required parameters. 5.8.9.3 Configuration Process This section describes the process of data configuration.

This section describes the networking information about the NEs. On the network as shown in Figure 5-62, NE1, NE2, and NE3 transmit E-line services carried by VLAN-based PWs. When faults occur on the network between NE1 and NE2 and the network between NE1 and NE3, NE1, NE2, and NE3 need to disconnect their access links to instruct router A, router B, and router C respectively to start a backup network for uninterrupted communication. Since E-line services carried by VLAN-based PWs share UNI ports, point-tomultipoint LPT needs to be configured on NE1, NE2, and NE3.
Issue 02 (2011-01-20)
5-165
Figure 5-62 Network diagram of LPT (traversing a PSN)

4-EM6T-1 (to Router B) 4-EM6T-1 (to Router A) VLAN:100,200 PW ID: 101 NE2 Router B VLAN:200 VLAN:100
PSN
Router A NE1 PW ID: 102 NE3
Router C
4-EM6T-1 (to Router C)

The service planning information contains all required parameters.
LPT Configuration Information

Table 5-83 provides LPT configuration information. Table 5-83 Configuration information of NE1 Parameter LPT type Primary point Point type Port Secondary point 1 Point type Port Secondary point 2 Point type Port NE1 Point-to-multipoint LPT UNI 4-EM6T-1 PW PW ID: 101 PW PW ID: 102
Table 5-84 Configuration information of NE2 Parameter LPT type Primary point
5-166
NE2 Point-to-multipoint LPT Point type

UNI
Issue 02 (2011-01-20)
Parameter Port Secondary point 1 Point type Port
NE2 4-EM6T-1 PW PW ID: 101
Table 5-85 Configuration information of NE3 Parameter LPT type Primary point Point type Port Secondary point 1 Point type Port NE3 Point-to-multipoint LPT UNI 4-EM6T-1 PW PW ID: 102
Configuration Information of LPT

In this example, NE1, NE2, and NE3 all take the default LPT parameter values. See Table 5-86. Table 5-86 Configuration information of LPT Parameter Recovery Time(s) Hold-Off Time(ms) Switching Mode Fault Detection Mode Fault Detection Period(100ms) Value 1 1000 Strict mode LPT OAM 10

Procedure
Step 1 See A.6.10.3 Configuring Point-to-Multipoint LPT and configure point-to-multipoint LPT. l The values for the relevant parameters of NE1, NE2, and NE3 are provided as follows. Set parameters for the primary points as follows.
Parameter
Value NE1 NE2 UNI 4-EM6T 4-EM6T (PORT-1) NE3 UNI 4-EM6T 4-EM6T (PORT-1)
Point Type Board Port
UNI 4-EM6T 4-EM6T (PORT-1)
Set parameters for the secondary points as follows. Parameter Value NE1 Secondary Point 1 Point Type Available Points PW PW-101 Secondary Point 2 PW PW-102 NE2 Secondary Point 1 PW PW-101 NE3 Secondary Point 1 PW PW-102
----End


When a service network fault is detected by using LPT or a notification of a fault detected by LPT is received, the NE reports the corresponding alarm.
Relevant Alarms
LPT_CFG_CLOSEPORT The LPT_CFG_CLOSEPORT is an alarm indicating that the LPT closes the access port of the local NE. Upon detecting that the convergence port of the local NE or the access port of the remote NE is faulty, the LPT automatically closes the access port of the local NE. Then, the LPT_CFG_CLOSEPORT alarm is reported.
Relevant Events
None.
5.8.12 FAQs
This section provides answers to the questions that are frequently raised when LPT is used. Q: Why can services of all types use LPT when they traverse an L2 network?
A: When LPT is configured for services traversing an L2 network, LPT does not need to be bound with the services and service types do not affect LPT. Therefore, deploy LPT only based on network topologies.
5.9 QoS
The quality of service (QoS) refers to the ability of a communication network to ensure the expected service quality in the aspects of the bandwidth, delay, delay jitter, and packet loss ratio, and thus 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. 5.9.1 Introduction This section provides the definition of QoS and describes its purpose. 5.9.2 Basic Concepts This topic describes the basic concepts that you need to be familiar with before you use the QoS feature. 5.9.3 Specifications This topic provides QoS specifications. 5.9.4 Reference Standards and Protocols This section describes the standards and protocols associated with QoS. 5.9.5 Availability This section describes the support required by the application of the QoS feature and its dependency. 5.9.6 Principles The CAR and traffic shaping functions are implemented based on the token bucket algorithm. 5.9.7 Configuration Procedure Before applying a QoS policy to a specific QoS object, you need to set the QoS policy. 5.9.8 Configuration Example This topic uses an example to describe how to plan and configure the QoS according to the conditions of the network. 5.9.9 Task Collection This topic provides the hyperlinks of the operation tasks regarding the relevant feature. 5.9.10 Relevant Alarms and Events There are not any QoS-related alarms or abnormal events. 5.9.11 FAQs This topic describes the answers to the questions that are frequently raised when the QoS feature is used.
5.9.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 packet 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 5-63 shows how packets are transmitted through an interface that does not support QoS when the network is congested. Figure 5-63 FIFO queue
Packets to be transmitted through this interface Queue Packets transmitted out of the interface Egress queue scheduling
FIFO
Queue in which the priorities of packets are in a descending order 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 5-64 shows how packets of different QoS levels are transmitted through queues with different priorities. Figure 5-64 Prioritized queues
Queues Packets to be transmitted through this interface
Classific ation
Priorities
Queue 8 Highest Queue 7 Queue 2 Higher Normal
Packets transmitted out of the interface Egress queue scheduling
Queue 1
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
...
Lowest
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.

This topic describes the basic concepts that you need to be familiar with before you use the QoS feature. 5.9.2.1 QoS Requirements Various services provide different requirements for bandwidths, delay, jitter, and packet loss ratio. Therefore, these services require different QoS operations for differentiated services. 5.9.2.2 DiffServ Differentiated service (namely, DiffServ) provides an easy-to-implement and scalable architecture for end-to-end QoS. 5.9.2.3 Traffic Classification The OptiX RTN 980 supports two traffic classification methods: simple traffic classification and complex traffic classification. In the case of simple traffic classification, different services on specified ports are mapped to different PHB service levels according to packet priorities by means of DiffServ. In the case of complex traffic classification, specified services are classified by the C-VLAN/S-VLAN ID, C-VLAN/S-VLAN priority, or IP DSCP value. 5.9.2.4 CAR The CAR is a type of traffic policing technology. When the CAR is used, the rate of the traffic after traffic classification is assessed in a certain period (including in the long term and in the short term); the packet rate of which does not exceed the specified value is set to a high priority and the packet rate of which exceeds the specified value is discarded or downgraded. In this manner, the CAR restricts the traffic into the transmission network. 5.9.2.5 Traffic Shaping When the traffic shaping function is used, the traffic and burst size of an outgoing connection of a network can be restricted. In this manner, the packet can be transmitted at an even rate. 5.9.2.6 Queue Scheduling The OptiX RTN 980 supports three queue scheduling methods, namely, strict-priority (SP), weighted round robin (WRR), and SP+WRR. 5.9.2.7 QoS Model Services of different categories are handled based on different QoS models.
5.9.2.1 QoS Requirements

Various services provide different requirements for bandwidths, delay, jitter, and packet loss ratio. Therefore, these services require different QoS operations for differentiated services.
Specifications in QoS Measurement

l Delay Indicates the time elapsed after a service is transmitted at a reference point and before the service is received at another reference point. l Jitter Indicates the time difference between packets that are received at the user receive side when these packets are transmitted over the same route. l Packet loss ratio Indicates the maximum ratio of the discarded packets to the total number of transmitted packets. Packet discarding generally results from network congestion.
Service Types and QoS Requirements

Taking typical 3G Ethernet services as an example, Table 5-87 provides the various service types and corresponding QoS requirements. Table 5-87 Service types and QoS requirements Type of Service Control Information From top to down wards, servic e priorit ies are in a desce nding order. Typical Service Ethernet protocol packet Ethernet OAM packet VoIP Videophone Interactive game VOD Web page browsing Email/Film/ MP3 downloading FTP service Not sensitive Not sensitive Not sensitive Sensitive Not sensitive Not sensitive Not sensitive Sensitive Sensitive Sensitive Sensitive Sensitive Delay Sensitive Jitter Sensitive Packet Loss Sensitive
Conversatio nal service and signaling service Streaming service Interactive service Background service
5.9.2.2 DiffServ
Differentiated service (namely, DiffServ) provides an easy-to-implement and scalable architecture for end-to-end QoS.
5-172
Issue 02 (2011-01-20)
DiffServ Domain
A DiffServ (DS) domain consists of a group of network nodes (DS nodes) that provide the same service policy and implement the same per-hop behavior (PHB). DS nodes are classified into DS boundary nodes and DS interior nodes. In a DS domain as shown in Figure 5-65, a DS boundary node identifies the priorities of the packets that are transmitted to the DS domain and then marks mapping PHBs for these packets; a DS interior node performs traffic control based on packets' PHBs and forwards the packets to the DS boundary node of next hop. Figure 5-65 DiffServ model
DS interior node
DS domain Non-DS node DS edge node DS edge node Non-DS node
A PHB indicates specific forwarding treatments applied by a DS node on a collection of packets with the same QoS service class. To ensure different QoS objectives, eight PHBs are provided: BE, AF1, AF2, AF3, AF4, EF, CS6, and CS7. The mappings between the eight PHBs and packet priorities (C-VLAN priorities, S-VLAN priorities, DSCP values, or MPLS EXP values) can be specified by a DS domain. A DS domain defines how to map the priority of a packet to a specific PHB upon its arrival at a port, and how to map the PHB of the packet to a specific priority upon its leave. As shown in Figure 5-66, port 1, port 2, and port 3 are in the same DS domain; packets are transmitted to port 1 and port 2 and then are sent out from port 3 after scheduling. l l l Port 1 trusts packets with C-VLAN priorities. Port 2 trusts packets with DSCP values. Port 3 trusts packets with MPLS EXP values.
Issue 02 (2011-01-20)
5-173
Figure 5-66 Mappings between packet priorities and PHBs

Port 1 1 2 3 Port 2 1 2 3 AF1 A F2 AF3 1 2 3 1 2 3 Port 3 1 1 1 1 2 2 2 2 3 3 3 3
Packets carrying C-VLAN priorities Packets carrying DSCP values Packets carrying MPLS EXP values
Port 1 specifies PHBs of ingress packets with different C-VLAN priorities according to Table 5-88. Port 3 writes the priority information into the EXP fields of egress MPLS packets according to Table 5-90. Port 2 specifies PHBs of ingress packets with different DSCP values according to Table 5-89. Port 3 writes the priority information into the EXP fields of egress MPLS packets according to Table 5-90. Table 5-88 Mappings from priorities of ingress packets to PHBs at port 1 Packet Priority Type C-VLAN priority C-VLAN Priority 1 2 3 PHB AF1 AF2 AF3
Table 5-89 Mappings from priorities of ingress packets to PHBs at port 2 Packet Priority Type DSCP value DSCP Value 1 2 3 PHB AF1 AF2 AF3
5-174
Issue 02 (2011-01-20)
Table 5-90 Mappings from priorities of egress packets to PHBs at port 3 Packet Priority Type MPLS EXP value MPLS EXP Value 1 2 3 PHB AF1 AF2 AF3
NOTE
All ports that a service traverses must be configured into the same DS domain.
Default DS Domain
A default DS domain is available on the OptiX RTN equipment, and all Ethernet ports and Integrated IP radio ports belong to this domain unless other DS domains are configured. In this default DS domain, default mappings are defined. Table 5-91 and Table 5-92 provide default mappings from priorities of ingress packets to PHBs and from PHBs to priorities of egress packets on the OptiX RTN 980. BE is a default PHB.
NOTE
The OptiX RTN 980 trusts packets with C-VLAN priorities, S-VLAN priorities, DSCP values, or MPLS EXP values. Untrusted packets receive BE treatment, indicating that they are forwarded with best effort.
Table 5-91 Default mappings from priorities of ingress packets to PHBs C-VLAN Priority 0 S-VLAN Priority 0 DSCP Value (Decimal) 0-7, 9, 11, 13, 15, 17, 19, 21, 23, 25, 27, 29, 31, 33, 35, 37, 39, 41-45, 47, 49-55, 57-63 8, 10, 12, 14 16, 18, 20, 22 24, 26, 28, 30 32, 34, 36, 38 40, 46 48 56 MPLS EXP Value 0 PHB BE
1 2 3 4 5 6 7
1 2 3 4 5 6 7
1 2 3 4 5 6 7
AF1 AF2 AF3 AF4 EF CS6 CS7
Issue 02 (2011-01-20)
5-175
Table 5-92 Default mappings from PHBs to priorities of egress packets PHB BE AF1 AF2 AF3 AF4 EF CS6 CS7 C-VLAN Priority 0 1 2 3 4 5 6 7 S-VLAN Priority 0 1 2 3 4 5 6 7 DSCP Value (Decimal) 0 8, 12, 14 16, 20, 22 24, 28, 30 32, 36, 38 40 48 56 MPLS EXP Value 0 1 2 3 4 5 6 7
NOTE
AF1 defines three sub-classes: AF11, AF12, and A13. Only AF11 can take effect. This rule also applies to AF2, AF3, and AF4. To be specific, only AF21, AF31, and AF41 can take effect.
Native ETH Service and PHB

l When a packet arrives at a port, the port obtains the packet priority value depending on its trusted packet priority type (DSCP value, C-VLAN priority, or S-VLAN priority) and specifies the PHB of the packet according to the mappings from packet priorities to PHBs. When a packet in an egress queue leaves a port, the port obtains the packet priority value according to the mappings from PHBs of egress queues to egress packet priorities (DSCP values, C-VLAN priorities, or S-VLAN priorities), and replaces the original DSCP value or VLAN priority of the packet with the obtained one. Regarding UNI ports carrying QinQ private line services or being mounted to IEEE 802.1ad bridges, note that if such a UNI port trusts packets with C-VLAN priorities, it cannot modify the C-VLAN priorities in its egress packets based on the mappings from C-VLAN priorities to PHBs configured in a DS domain.
NOTE
Regarding point-to-point transparent transmission E-Line services, a port trusts only packets with DSCP values.
ETH PWE3 Service and PHB

Packet priority mapping is performed differently at various nodes. At an ingress node l When a packet arrives at a UNI port, the UNI port obtains the packet priority value depending on its trusted priority type (DSCP value, C-VLAN priority, or S-VLAN priority) and specifies the PHB of the packet according to the mappings from packet priorities to PHBs. When a packet in an egress queue leaves an NNI port, the NNI port obtains the packet priority value according to the mappings from PHBs of egress queues to egress packet
5-176
priorities (MPLS EXP values), and writes the obtained priority value into the EXP field of the egress MPLS packet. At a transit node l When a packet arrives at an NNI port, the NNI port obtains the packet priority value depending on its trusted priority type (MPLS EXP value) and specifies the PHB of the packet according to the mappings from packet priorities to PHBs. When a packet in an egress queue leaves an NNI port, the NNI port obtains the packet priority value according to the mappings from PHBs of egress queues to egress packet priorities (MPLS EXP values), and replaces the original EXP value of the packet with the obtained one.
At an egress node l When a packet arrives at an NNI port, the NNI port obtains the packet priority value depending on its trusted priority type (MPLS EXP value) and specifies the PHB of the packet according to the mappings from packet priorities to PHBs. When a packet in an egress queue leaves a UNI port, the UNI port obtains the packet priority value according to the mappings from PHBs of egress queues to egress packet priorities (DSCP values or S-VLAN priorities), and replaces the original DSCP value or S-VLAN priority of the packet with the obtained one. Note that if a UNI port trusts packets with CVLAN priorities, it cannot modify the C-VLAN priorities in its egress packets based on the mappings from C-VLAN priorities to PHBs configured in a DS domain.
NOTE
l A UNI port carrying ETH PWE3 services trusts packets with DSCP values, C-VLAN priorities, or S-VLAN priorities. l An NNI port carrying ETH PWE3 services trusts only packets with MPLS EXP values.
CES Service and PHB

Packet priority mapping is performed differently at various nodes. At an ingress node l l A port specifies the PHB of a packet. When a packet in an egress queue leaves an NNI port, the NNI port obtains the packet priority value according to the mappings from PHBs of egress queues to egress packet priorities (MPLS EXP values), and writes the obtained priority value into the EXP field of the egress MPLS packet.
NOTE
CES services require low delay, low jitter, and fixed bandwidth. Therefore, a high enough priority needs to be assigned to CES services so that forwarding/processing CES services takes precedence. By default, the OptiX RTN 980 assigns the EF PHB to CES services.
At a transit node l When a packet arrives at an NNI port, the NNI port obtains the packet priority value depending on its trusted packet priority type (MPLS EXP value) and specifies the PHB of the packet according to the mappings from packet priorities to PHBs. When a packet in an egress queue leaves an NNI port, the NNI port obtains the packet priority value according to the mappings from PHBs of egress queues to egress packet
Issue 02 (2011-01-20)
priorities (MPLS EXP values), and replaces the original EXP value of the packet with the obtained one. At an egress node No priority mapping operation is performed.
NOTE
An NNI port carrying CES services trusts only packets with MPLS EXP values.
ATM PWE3 Service and PHB

Packet priority mapping is performed differently at various nodes. At an ingress node l When a PW packet carrying an ATM service arrives at a port, the port specifies the PHB of the packet according to the mappings from ATM service categories to PHBs (Table 5-93 provides the default mappings). When a packet in an egress queue leaves an NNI port, the NNI port obtains the packet priority value according to the mappings from PHBs of egress queues to egress packet priorities (MPLS EXP values), and writes the obtained priority value into the EXP field of the egress MPLS packet.
NOTE
If packets in a PW carry ATM services of various categories, the mapping highest PHB is assigned to these PW packets.
Table 5-93 Mappings between ATM service categories and PHBs ATM Service Category CBR RT-VBR NRT-VBR UBR+ UBR PORT-TRANS PHB EF AF3 AF2 AF1 BE BE
At a transit node l When a packet arrives at an NNI port, the NNI port obtains the packet priority value depending on its trusted priority type (MPLS EXP value) and specifies the PHB of the packet according to the mappings from packet priorities to PHBs. When a packet in an egress queue leaves an NNI port, the NNI port obtains the packet priority value according to the mappings from PHBs of egress queues to egress packet priorities (MPLS EXP values), and replaces the original EXP value of the packet with the obtained one.
At an egress node
No priority mapping operation is performed.

NOTE
An NNI port carrying ATM PWE3 services trusts only packets with MPLS EXP values.
5.9.2.3 Traffic Classification

The OptiX RTN 980 supports two traffic classification methods: simple traffic classification and complex traffic classification. In the case of simple traffic classification, different services on specified ports are mapped to different PHB service levels according to packet priorities by means of DiffServ. In the case of complex traffic classification, specified services are classified by the C-VLAN/S-VLAN ID, C-VLAN/S-VLAN priority, or IP DSCP value. Simple traffic classification is for Ethernet services, CES services, and ATM services, whereas complex traffic classification is only for Ethernet services.
Simple Traffic Classification

The simple traffic classification is based on the DS domain. In the case of simple traffic classification, different services on specified ports are mapped to different PHB service levels according to their carried QoS information. For basic concepts of the simple traffic classification, see 5.9.2.2 DiffServ.
Complex Traffic Classification

In the case of complex traffic classification, specified services are classified according to the CVLAN/S-VLAN ID, C-VLAN/S-VLAN priority, or DSCP value. The flow type is based on the associated Ethernet service type of the traffic. The OptiX RTN 980 supports the following flow types: l l Flow classified according to the specified C-VLAN ID The packets that carry the specified C-VLAN ID are classified as a flow. Flow classified according to the C-VLAN priority The packets that are from a certain port and have a specified C-VLAN priority are classified as a flow. l Flow classified according to the specified S-VLAN ID The packets that are from a certain port and have a specified S-VLAN ID are classified as a flow. l Flow classified according to the specified S-VLAN priority The packets that are from a certain port and have a specified S-VLAN priority are classified as a flow. l Flow according to the DSCP value The packets that are from a certain port and have a specified DSCP value are classified as a flow.
NOTE
The flow can be further classified according to the combination of the C-VLAN ID and CVLAN priority or SVLAN ID and SVLAN priority. The OptiX RTN 980 supports the logical AND setting for the two matching rules.
A complex flow supports the following QoS processing operations:

l l l l
The flow is passed or discarded based on the ACL. The flow is mapped to a new PHB service class. In the ingress direction, the rate of the flow is restricted through the CAR mechanism. In the egress direction, traffic shaping is performed on the flow.
5.9.2.4 CAR
The CAR is a type of traffic policing technology. When the CAR is used, the rate of the traffic after traffic classification is assessed in a certain period (including in the long term and in the short term); the packet rate of which does not exceed the specified value is set to a high priority and the packet rate of which exceeds the specified value is discarded or downgraded. In this manner, the CAR restricts the traffic into the transmission network. The OptiX RTN 980 supports the CAR processing for a complex flow in the ingress direction. 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 rate of which is higher than the PIR are marked red and directly discarded. When the rate of packets is higher than the CIR but is lower than the PIR, the packets at a rate higher than the CIR can pass the restriction but are marked yellow. Yellow packets can be set to "discard", "pass", or "remark". If packets are set to "remark", these packets are mapped to another specified queue with a certain priority (that is, the priority of these packets are changed) and then forwarded. When the rate of packets that pass the restriction of the CAR 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 the burst packets is determined by the committed burst size (CBS). When the rate of packets that pass the restriction of the CAR 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 the burst packets is determined by the peak burst size (PBS).
l l
Figure 5-67 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. Figure 5-67 CAR processing
MBS PIR CBS CIR PIR CIR PIR MBS CBS CIR
CAR
5-180
Issue 02 (2011-01-20)
5.9.2.5 Traffic Shaping

When the traffic shaping function is used, the traffic and burst size of an outgoing connection of a network can be restricted. In this manner, the packet can be transmitted at an even rate. The OptiX RTN 980 can perform traffic shaping for complex flows, and for egress queues and egress ports corresponding to PHB service classes. To perform traffic shaping for complex flows, the dual token bucket three color marker algorithm, which is similar to the algorithm used by CAR, is used, and a buffer queue is added before the Tc token bucket. To perform traffic shaping for the egress queues or egress ports that correspond to PHB service classes, the single token bucket two color marker algorithm is used and a buffer queue is added before the Tp token bucket.
Traffic Shaping for Complex Flows

After the traffic shaping function is enabled, the OptiX RTN 980 processes the packets as follows if the buffer queue is empty: l l If the rate of the packets is equal to or lower than the preset CIR, the packets are directly forwarded. If the rate of the packets is higher than the CIR but is equal to or lower than the PIR, the packets at a rate higher than the CIR enter the buffer queue and then are forwarded at a rate equal to the CIR. If the rate of the packets is higher than the PIR, these packets are directly discarded. If the rate of the packets in a certain period is equal to or lower than the CIR, certain packets can burst and be directly forwarded. The maximum traffic of the burst packets is determined by the CBS. If the rate of the packets in a certain period is higher than the CIR but is equal to or lower than the PIR, certain packets can burst and enter the buffer queue. The maximum traffic of the burst packets is determined by the PBS.
l l
When the buffer queue is not empty, the packets whose rate passes the restriction of the PIR enter the buffer queue and then are forwarded at a rate equal to the CIR. Figure 5-68 shows the traffic change after traffic shaping. During traffic shaping, the green part indicates the traffic that is directly forwarded without traversing the buffer queue, the yellow part indicates the traffic that is forwarded after traversing the buffer queue, and the red part indicates the traffic that is discarded. Figure 5-68 Processing of traffic shaping
PBS PIR CBS CIR
PIR CIR
PIR
Shaping
CIR
Issue 02 (2011-01-20)
5-181
Traffic Shaping for Egress Queues and Egress Ports

After the traffic shaping function is enabled, the OptiX RTN 980 processes the packets as follows if the buffer queue is empty: l If the rate of the packets is equal to or lower than the preset PIR, these packets are directly forwarded. Note that the values of the CIR and PIR are equal in this case, and only the PIR is valid. If the rate of the packets is higher than the PIR, these packets enter the buffer queue. If the rate of the packets is equal to or lower than the PIR in a certain period, certain burst packets can be forwarded. The maximum traffic of the burst packets is determined by the PBS.
l l
When the buffer queue is not empty, the packets whose rate passes the restriction of the PIR enter the buffer queue and then are forwarded at a rate equal to the PIR. Figure 5-69 Processing of traffic shaping
PBS PIR
PIR
PIR
Shaping
Difference Between Traffic Shaping and CAR

As is evident from the preceding processing mechanism, the differences of traffic shaping from CAR are as follows: l l l CAR is applicable to service flows in the ingress direction, whereas traffic shaping is applicable to service flows in the egress direction. CAR is mainly used to restrict the access traffic of a certain service flow, and traffic shaping helps to transmit a service flow (or a flow at a port) at an even rate. The implementation of traffic shaping uses a buffer, which may increase delay of services, whereas CAR does not increase delay of services.
5.9.2.6 Queue Scheduling

The OptiX RTN 980 supports three queue scheduling methods, namely, strict-priority (SP), weighted round robin (WRR), and SP+WRR.
Basic Concept
Available bandwidth at a port: refers to the bandwidth that the system allocates to a port.
In the case of an FE/GE 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 full-duplex, the available bandwidth of the port is 1000 Mbit/s. The IF_ETH port is an internal Ethernet port on the Integrated IP radio IF board. In the transmit direction of Hybrid/Packet microwave, the Ethernet services are transmitted to the MUX/DEMUX unit of the Integrated IP radio IF board through the IF_ETH port and then mapped into the microwave frames. In the receive direction of Integrated IP radio microwave, the Ethernet services are demapped from the microwave frames and then transmitted to the packet switching unit through the IF_ETH port. The main differences between the IF_ETH port and the GE/FE port are as follows: The IF_ETH port is an internal Ethernet port. It transmits and receives MAC frames and does not have PHY-layer functions. The bandwidth over the IF_ETH port is equal to the Ethernet service bandwidth that the Integrated IP radio supports. Hence, when the AM function is enabled in the case of Integrated IP radio, the bandwidth over the IF_ETH port changes according to the modulation mode.
SP Scheduling Algorithm
Figure 5-70 illustrates the SP scheduling algorithm. Figure 5-70 SP queues
Queues Packets to be transmitted through this interface
Classific ation
Priorities
Queue 8 Highest Queue 7 Queue 2 Higher Normal
Packets transmitted out of the interface Egress queue scheduling
Queue 1
During the SP queue scheduling, packets are transmitted in a descending order of priority. 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. Hence, 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.
...
Lowest
WRR Scheduling Algorithm

Figure 5-71 illustrates the WRR scheduling algorithm.
Figure 5-71 WRR scheduling algorithm

Packets to be transmitted through this interface Queues Queue 4
Classific ation
Weights 50 30 10 10 Egress queue scheduling Packets transmitted out of the interface
Queue 3 Queue 2 Queue 1
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. In addition, the WRR allocates a weight value for each queue and then allocates the service time period for each queue according to the weight value. The port transmits the Ethernet frames of the corresponding queue in the corresponding service period. If the queue to which the service period corresponds contains no Ethernet frames, a time period is extracted to transmit the Ethernet frames that correspond to the subsequent time periods. That is, the WRR ensures the bandwidth resource allocation based on the weight values of the queues in the case of a link congestion and full bandwidth utilization in the case of no link congestion. For example, a port provides four queues. The weight proportion of the four queues is 5:3:1:1. Hence, when congestions occur in all the queues, the four queues are allocated with the 50 Mbit/s, 30 Mbit/ s, 10 Mbit/s, and 10 Mbit/s bandwidths respectively. If the first queue contains no Ethernet frames and congestions occur in the other three queues, the other three queues are allocated with the 60 Mbit/s, 20 Mbit/s, and 20 Mbit/s bandwidths respectively. Compared with the SP scheduling algorithm, the WRR scheduling algorithm prevents the disadvantage that packets in the queues with lower priorities may fail to obtain service for a long time. In the case of the WRR algorithm, however, all the bandwidth resources cannot be used when congestions occur in the services of higher priorities.
SP+WRR Scheduling Algorithm

Figure 5-72 shows the SP+WRR scheduling algorithm. In the case of SP+WRR scheduling algorithm, a group of WRR queues must be allocated with the same queue priority. The SP +WRR scheduling algorithm is described as follows: l If the queues that have higher priorities than the WRR queues contain Ethernet frames, the Ethernet frames are transmitted according to the SP scheduling algorithm. In this case, the Ethernet frames in the WRR queues are not transmitted. If the queues that have higher priorities than the WRR queues do not contain Ethernet frames, the Ethernet frames in the WRR queues are transmitted according to the WRR scheduling algorithm. If the WRR queues and the queues that have higher priorities than the WRR queues do not contain Ethernet frames, the Ethernet frames in the queues that have lower priorities than the WRR queues are transmitted according to the SP algorithm.
5-184
Figure 5-72 SP+WRR scheduling algorithm

SP Queues Packets to be transmitted through this interface Weights (%) 25 Classifi cation 25 25 25 WRR Queues Queue 8 Queue 7 Queue 6 WRR Queue Priorities Highest Higher Normal lower Egress queue scheduling Packets transmitted out of the interface
Queue 5 Queue 4 Queue 3 Queue 2
Queue 1
Lowest
In the case of the OptiX RTN 980, the SP+WRR scheduling algorithm is the default queue scheduling mode for each Ethernet port. The queue priority levels are CS7, CS6, EF, AF4, AF3, AF2, AF1, and BE in the descending order or priority. AF1 to AF4 are WRR queues. Except for the default settings, the WRR queues and SP queues cannot be interleaved if you set the SP +WRR scheduling algorithm manually.
5.9.2.7 QoS Model

Services of different categories are handled based on different QoS models.
QoS Model for Native ETH Services

Figure 5-73 shows the QoS model for Native ETH services that the OptiX RTN 980 supports. Figure 5-73 QoS model for Native ETH services
Packets are scheduled to specific egress queues based on their PHBs Port Apply a DiffServ policy Port
Apply a port policy
Apply a DiffServ policy
Apply a port policy
Apply a port shaping policy
Apply a port policy
Apply a port policy
QoS application point QoS processing Service direction
Issue 02 (2011-01-20)
5-185
Table 5-94 provides QoS technologies applicable to each QoS application point in the model. Table 5-94 QoS technologies applicable to each QoS application point in the QoS model for Native ETH services QoS Applicatio n Point Service ingress port Policy Applicable QoS Technology
DiffServ
Simple traffic classification: specifies PHBs of packets with different priorities. For default mappings from priorities of ingress packets to PHBs, see Table 5-91.
Port policy
Complex traffic classification: classifies specific services by C-VLAN/S-VLAN ID, C-VLAN/S-VLAN priority, or DSCP value. ACL based on complex traffic classification: allows/ prohibits access of specific service flows to a transport network. CAR based on complex traffic classification: restricts the volumes of specific service flows on a transport network. Respecifies PHBs based on complex traffic classification.
Service egress port
DiffServ
The port obtains the priority value of a packet in an egress queue according to the mappings from PHBs of egress queues to trusted packet priorities of the port and replaces the original priority value of the packet with the obtained one. For default mappings from PHBs to egress packet priorities, see Table 5-92.
Port policy
Shaping based on complex traffic classification Shaping based on egress queues Schedules packets in egress queue by means of a preset scheduling algorithm.
Port shaping
Shaping
QoS Models for ETH/TDM/ATM PWE3 Services

Figure 5-74, Figure 5-75, and Figure 5-76 show QoS models for ETH/TDM/ATM PWE3 services that the OptiX RTN 980 supports.
5-186
Issue 02 (2011-01-20)
Figure 5-74 QoS model for ETH/TDM/ATM PWE3 services (UNI to NNI)
Packets are scheduled to specific egress queues based on their PHBs UNI Port Specify the mappings from ATM service categories to PHBs Apply a PW bandwidth control policy ETH PWE3 encapsulation Apply a port policy ETH PWE3 NNI PW Port
ATM service
ATM traffic management
ATM PWE3 encapsulation
ATM PWE3
Apply a DiffServ policy Ethernet service
Apply a port policy
TDM service
TDM PWE3 TDM PWE3 encapsulation
Specify the PHBs of CES services
QoS application point QoS processing Functions related to QoS processing Service direction
Figure 5-75 QoS model for ETH/TDM/ATM PWE3 services (NNI to NNI)
Packets are scheduled to specific egress queues based on their PHBs NNI Port NNI Port
Apply a port policy
Apply a port policy
QoS application point QoS processing Service direction
Issue 02 (2011-01-20)
5-187
Figure 5-76 QoS model for ETH/TDM/ATM PWE3 services (NNI to UNI)
Packets are scheduled to corresponding egress queues based on their PHBs UNI Port Apply a port policy ETH PWE3 NNI PW Port
Ethernet service
ETH PWE3 decapsulation
ATM service
ATM PWE3 decapsulation
ATM PWE3
TDM service
TDM PWE3 decapsulation
TDM PWE3
QoS application point QoS processing Functions related to QoS processing Service direction
Table 5-95, Table 5-96, and Table 5-97 provide QoS technologies applicable to each QoS application point in these models. Table 5-95 QoS technologies applicable to each QoS application point in the QoS model for ETH/TDM/ATM PWE3 services (UNI to NNI) QoS Application Point Service direction (UNI to NNI) UNI Service ATM service Policy ATM traffic managem ent Applicable QoS Technology Before being encapsulated into PW packets, ATM cells (carried by VPCs/ VCCs) are provided with specific service policies based on their categories. Generally, ATM traffic management is implemented in the ingress direction on the UNI side of a PE. -
ATM PWE3 encapsula tion
5-188
Issue 02 (2011-01-20)
QoS Application Point
Service
Policy ATM CoS mapping
Applicable QoS Technology Specifies PHBs of PW packets carrying ATM services of different categories according to ATM CoS mappings. For default mappings between ATM service categories and PHBs, see Table 5-93.
NOTE If a PW carries ATM services of various categories, the mapping highest PHB is assigned to these PW packets.
TDM service
TDM PWE3 encapsula tion Specifying PHBs of TDM PWE3 services
By default, the EF PHB is assigned to TDM PWE3 services.
Ethernet service
DiffServ
Simple traffic classification: specifies PHBs of packets with different priorities. For default mappings from priorities of ingress packets to PHBs, see Table 5-91.
Port policy
Complex traffic classification: classifies specific services by CVLAN/S-VLAN ID, C-VLAN/SVLAN priority, or DSCP value. ACL based on complex traffic classification: allows/prohibits access of specific service flows to a transport network. CAR based on complex traffic classification: restricts the volumes of specific service flows on a transport network. Respecifies PHBs based on complex traffic classification.
ETH PWE3 encapsula tion
Issue 02 (2011-01-20)
5-189
QoS Application Point NNI
Service ATM/ETH PWE3
Policy PW bandwidth control
Applicable QoS Technology Controls the bandwidth of one or more PWs as required.
NOTE To enable the bandwidth limiting function to take effect for a PW, first configure a maximum bandwidth for the tunnel that carries the PW.
ATM/ TDM/ETH PWE3
DiffServ
Obtains the priority value of a packet in an egress queue according to the mappings from PHBs of egress queues to priorities of egress packets (MPLS EXP values) and writes the priority value into the EXP field of the egress MPLS packet. For default mappings from PHBs to priorities of egress packets, see Table 5-92.
Port policy
Shaping (based on egress queues) Schedules packets in egress queues by means of a preset scheduling algorithm.
Port shaping
Shaping
Table 5-96 QoS technologies applicable to each QoS application point in the QoS model for ETH/TDM/ATM PWE3 services (NNI to NNI) QoS Application Point Service direction (NNI to NNI) NNI Service ATM/TDM/ ETH PWE3 Policy DiffServ Applicable QoS Technology Specifies PHBs of ingress packets according to their MPLS EXP values. For default mappings from priorities of ingress packets to PHBs, see Table 5-91.
5-190
Issue 02 (2011-01-20)
QoS Application Point NNI
Service ATM/TDM/ ETH PWE3
Policy DiffServ
Applicable QoS Technology Obtains the priority value of a packet in an egress queue according to the mappings from PHBs of egress queues to priorities of egress packets (MPLS EXP values) and replaces the original MPLS EXP value of the packet with the obtained one. For default mappings from PHBs to priorities of egress packets, see Table 5-92.
Port policy
Port shaping
Shaping
Table 5-97 QoS technologies applicable to each QoS application point in the QoS model for ETH/TDM/ATM PWE3 services (NNI to UNI) QoS Application Point Service direction (NNI to UNI) NNI Service ETH PWE3 Policy DiffServ Applicable QoS Technology Specifies PHBs of ingress packets according to their MPLS EXP values. For default mappings from priorities of ingress packets to PHBs, see Table 5-91. UNI ATM service ATM PWE3 decapsulatio n TDM PWE3 decapsulatio n ETH PWE3 decapsulatio n -
TDM service
Ethernet service
Issue 02 (2011-01-20)
5-191
QoS Application Point
Service
Policy DiffServ
Applicable QoS Technology Obtains the priority value of a packet in an egress queue according to the mappings from PHBs of egress queues to priorities of egress packets and replaces the original priority value of the packet with the obtained one. For default mappings from PHBs to priorities of egress packets, see Table 5-92.
Port policy
Port shaping
Shaping
This topic provides QoS specifications. Table 5-98 lists QoS specifications. Table 5-98 QoS specifications Item DiffServ Maximum number of supported DiffServ (DS) domains PHBs 8 Specification
CS7 CS6 EF AF4 AF3 AF2 AF1 BE
5-192
Issue 02 (2011-01-20)
Item Applicable port types Ethernet port Integrated IP radio port
Specification
NOTE All ports that a service traverses must be configured into the same DS domain.
Types of trusted packet priorities
C-VLAN priority S-VLAN priority DSCP values MPLS EXP values

NOTE l Regarding point-to-point transparent transmission Ethernet services (UNI-UNI), a UNI port trusts only packets with DSCP values if the encapsulation type of the UNI port is set to Null. l A QinQ-based NNI port trusts only packets with DSCP values or S-VLAN priorities. l An MPLS-based NNI port trusts only packets with MPLS EXP values.
Comple x traffic classific ation
Application point Traffic classification methods
Ingress port Based on port+C-VLAN ID Based on port+C-VLAN priority Based on port+S-VLAN ID Based on port+S-VLAN priority Based on port+DSCP value Based on port+C-VLAN ID+C-VLAN priority Based on port+S-VLAN ID+S-VLAN priority
NOTE An MPLS-based NNI port does not support complex traffic classification but supports only simple traffic classification based on DiffServ. A port with the encapsulation type set to null supports the traffic classification based on port+DSCP value. A port with the encapsulation type set to EEE 802.1Q supports the following traffic classification methods: l Based on port+C-VLAN ID l Based on port+C-VLAN ID+C-VLAN priority l Based on port+DSCP value A port with the encapsulation type set to QinQ supports the following traffic classification methods: l Based on port+S-VLAN ID l Based on port+S-VLAN ID+S-VLAN priority l Based on port+DSCP value
Issue 02 (2011-01-20)
5-193
Item QoS operations based on complex traffic classification
Specification ACL based on complex traffic classification Specifying a new PHB service class for a service flow based on complex traffic classification CAR based on complex traffic classification (ingress direction) Shaping based on complex traffic classification (egress direction)
CAR
Traffic type Maximum number of CAR policies CIR increment PIR increment
Service flows based on complex traffic classification 512
64 kbit/s 64 kbit/s Service flows based on complex traffic classification Service flows based on egress queues Service flows based on an egress port
Traffic shaping
Traffic types
CIR increment PIR increment Queue scheduli ng Number of egress queues Queue scheduling schemes Weight allocation of WRR
64 kbit/s 64 kbit/s 8 SP WRR SP+WRR The default weight can be changed.

This section describes the standards and protocols associated with QoS. The following protocol is associated with QoS: l l l l l l
5-194
IETF RFC 2309: Recommendations on Queue Management and Congestion Avoidance in the Internet IETF RFC 2697: A Single Rate Three Color Marker IETF RFC 2698: A Two Rate Three Color Marker IETF RFC 2597: Assured Forwarding PHB Group IETF RFC 2598: An Expedited Forwarding PHB IEEE 802.1p: Traffic Class Expediting and Dynamic Multicast Filtering
5.9.5 Availability
This section describes the support required by the application of the QoS feature and its dependency.

Table 5-99 Hardware and version support Feature DiffServ a Applicable Board EM6T/EM6F IFU2/IFX2 ISU2/ISX2 CSHN Traffic classification EM6T/EM6F IFU2/IFX2 ISU2/ISX2 CSHN CAR EM6T/EM6F IFU2/IFX2 ISU2/ISX2 CSHN Traffic shaping EM6T/EM6F IFU2/IFX2 ISU2/ISX2 CSHN Queue scheduling EM6T/EM6F IFU2/IFX2 ISU2/ISX2 CSHN All the versions V100R003C00 and later All the versions V100R003C00 and later All the versions V100R003C00 and later All the versions V100R003C00 and later Applicable Hardware Version All the versions Applicable Product Version V100R003C00 and later
Feature Dependency
The QoS feature has the following relationships with other features: When the AM function is enabled, it is recommended that you configure the QoS for the Ethernet services over the Integrated IP radio. After the QoS is configured, the bandwidth for Ethernet services of higher priorities is guaranteed first if the radio link works in a low modulation mode.
5.9.6 Principles
The CAR and traffic shaping functions are implemented based on the token bucket algorithm.
5.9.6.1 CAR The CAR uses the dual token bucket three color marker algorithm. 5.9.6.2 Traffic Shaping To perform traffic shaping, the dual token bucket three color marker algorithm or single token bucket two color marker algorithm is used, with a buffer queue is added before the Tc token bucket or Tp token bucket.
5.9.6.1 CAR
The CAR uses the dual token bucket three color marker algorithm.
Token Bucket Algorithm

Figure 5-77 shows the basic working principle of the token bucket algorithm. Figure 5-77 Basic working principle of the token bucket algorithm
...
Packets to be transmitted through this interface Classifi cation
Tokens are placed into the token bucket at the specified rate
Tokens
Packets transmitted out of the interface
Token bucket
Packets are discared or processed in another manner
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 transmission of the packets, these packets are discarded or processed in another manner. When the token bucket is filled with tokens, the traffic of the packets 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 5-78 shows the basic working principle of the dual token bucket three color marker algorithm that is used by the CAR.
5-196
Issue 02 (2011-01-20)
Figure 5-78 Basic working principle of the CAR algorithm
...
PIR
...
CIR
Classifi cation
Tp
Tc
In the case of the dual token bucket three color marker algorithm, two token buckets Tc and Tp are used and packets are marked 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 packets can pass the restriction of the CAR and is always 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 packets can pass the restriction of the CAR but is always 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 packets is directly discarded.
5.9.6.2 Traffic Shaping

To perform traffic shaping, the dual token bucket three color marker algorithm or single token bucket two color marker algorithm is used, with a buffer queue is added before the Tc token bucket or Tp token bucket.
Dual Token Bucket Three Color Marker Algorithm

Figure 5-79 shows the basic working principle of the dual token bucket three color marker algorithm that is used by traffic shaping.
Figure 5-79 Basic working principle of the algorithm used by traffic shaping
...
PIR Tp token bucket Buffer queue
Tc token bucket
In the case of the dual token bucket three color marker algorithm, two token buckets Tc and Tp are used and packets are placed 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 packets are placed into the Tc token bucket at a rate equal to the CIR, and the capacity of the Tc token bucket is equal to the CBS. The packets are placed into the Tp token bucket at a rate equal to the PIR, and the capacity of the Tp token bucket is equal to the PBS.
When the buffer queue is empty, the packets are processed as follows: l l l If a packet does not obtain the Tp token, it is directly discarded. If a packet obtains the Tp and Tc tokens, it is directly forwarded. If a packet obtains the Tp token but does not obtain the Tc token, it enters the buffer queue.
When the buffer queue is not empty, the packets are processed as follows: l l l If a packet obtains the Tp token but does not obtain the Tc token, it directly enters the buffer queue. Otherwise, it is directly discarded. If a packet in the buffer queue obtains the Tc token, it is directly forwarded. If a packet in the buffer queue does not obtain the Tc token, it is retained in the buffer queue. When the length of the buffer queue reaches the specified threshold, the packets in the buffer queue are discarded based on the congestion avoidance algorithm. In this manner, the forwarding efficiency and bandwidth utilization of the buffer queue are ensured.
...
CIR
Single Token Bucket Two Color Marker Algorithm

The Figure 5-80 shows the basic working principle of the single token bucket two color marker algorithm that is used by traffic shaping.
5-198
Issue 02 (2011-01-20)
Figure 5-80 Basic working principle of the algorithm used by traffic shaping
Buffer queue
Tp token bucket
In the case of the single token bucket two color marker algorithm, a Tp token bucket is used and packets are placed into different queues according to the situations when these packets pass the token bucket. The packets are placed into the Tp token bucket at a rate equal to the PIR, and the capacity of the Tp token bucket is equal to the PBS. In this case, the values of the CIR and PIR are equal, and only the PIR is valid. When the buffer queue is empty, the packets are processed as follows: l l If a packet obtains the Tp token, it is directly forwarded. If a packet does not obtain the Tp token, it enters the buffer queue.
When the buffer queue is not empty, the packets are processed as follows: l l l If a packet obtains the Tp token, it directly enters the buffer queue. If this packet does not obtain the Tp token, it is directly discarded. If a packet in the buffer queue obtains the Tp token, it is directly forwarded. If a packet in the buffer queue does not obtain the Tp token, it is retained in the buffer queue. When the length of the buffer queue reaches the preset threshold, the packets in the buffer queue are discarded based on the congestion avoidance algorithm. In this manner, the forwarding efficiency and bandwidth utilization of the buffer queue are ensured.
...
PIR

Before applying a QoS policy to a specific QoS object, you need to set the QoS policy.
Issue 02 (2011-01-20)
5-199
Procedure for Configuring QoS for Native ETH Services

Table 5-100 Procedure for configuring QoS for native ETH services Step 1 Operation Using the default DS domain of the OptiX RTN equipment Remarks Use the default DS domain of the OptiX RTN equipment if possible, to reduce work load for configuring network-wide QoS. Set the parameters according to the network planning information. 1. If the mappings from packet priorities to PHBs planned for wireless base stations or interconnected equipment are different from the mappings configured in the default DS domain of the OptiX RTN equipment (as provided in Table 5-91 and Table 5-92), modify the latter and ensure that the latter is the same as the former. 2. If the packet priority type (that is, trusted packet type) planned for wireless base stations or interconnected equipment is not the same as the default trusted packet type (C-VLAN priority) configured in the default DS domain of the OptiX RTN equipment, change the trusted packet type for the UNI port receiving the Ethernet service in the DS domain of the OptiX RTN equipment, and ensure that the new value is the same as that planned for wireless base stations or interconnected equipment. 2 A.6.7.1 Creating a DS Domain A.6.7.4 Creating a Port Policy Required if the default DS domain does not meet requirements. Set the parameters according to the network planning information. Required when you need to apply QoS policies other than DS and port shaping for a specific port. Set the parameters according to the network planning information. Required when you need to perform the CAR or shaping operation for a specific flow over the port. Set the parameters according to the network planning information. Required after you create a port policy.
A.6.7.6 Creating the Traffic
A.6.7.7 Setting the Port That Uses the Port Policy A.6.7.8 Configuring Port Shaping
Required when you need to limit the egress bandwidth of the Ethernet service. Set the parameters according to the network planning information.
5-200
Issue 02 (2011-01-20)
Procedure for Configuring QoS for ETH PWE3 Services

Table 5-101 Procedure for configuring QoS for ETH PWE3 services Step 1 Operation Using the default DS domain of the OptiX RTN equipment Remarks Required. 1. If the mappings from packet priorities to PHBs planned for wireless base stations or interconnected equipment are different from the mappings configured in the default DS domain of the OptiX RTN equipment (as provided in Table 5-91 and Table 5-92), modify the latter and ensure that the latter is the same as the former. 2. If the packet priority type (that is, trusted packet type) planned for wireless base stations or interconnected equipment is not the same as the default trusted packet type (C-VLAN priority) configured in the default DS domain of the OptiX RTN equipment, change the trusted packet type for the UNI port receiving the Ethernet service in the DS domain of the OptiX RTN equipment, and ensure that the new value is the same as that planned for wireless base stations or interconnected equipment. 3. The NNI ports associated with PW-carried UNI-NNI E-Line services trust only packets with MPLS EXP values. Therefore, change the trusted packet type to MPLS EXP value for the NNI ports in the default DS domain. 2 A.6.7.4 Creating a Port Policy Required when you need to apply QoS policies other than DS and port shaping for a specific port. Set the parameters according to the network planning information. Required when you need to perform the CAR or shaping operation for a specific flow over the port. Set the parameters according to the network planning information. Required after you create a port policy.
A.6.7.7 Setting the Port That Uses the Port Policy A.6.7.8 Configuring Port Shaping
Required when you need to limit the egress bandwidth of the Ethernet service. Set the parameters according to the network planning information.

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

This section describes the networking information about the NEs. In a packet microwave network as shown in Figure 5-81, the networking information and QoS requirements are as follows: l Ethernet services of different categories (real-time voice services, real-time HSDPA services, non-real-time R99 services, and HSDPA data services) from BTSs carry VLAN IDs and different VLAN priorities. Ethernet services from BTSs are transmitted to the RNC over PWs on the packet microwave network. On the packet microwave network, Ethernet services require end-to-end QoS management based on their VLAN priorities (planned at the BTSs).
l l
Figure 5-81 Network diagram

To NE33:3-ISU2-1 To BTS33:7-EM6X-1 To NE34:3-ISU2-1 To NE32:4-ISU2-1
BTS33 VLAN 330

FE
NE34
NE33
To NE33:3-ISU2-1 To NE31:17-EG2D-2 To BTS31:2-EM6T-3
To NE32:1-EM6F-1 To RNC:3-EM6T-1
R4
NE32
GE
NE31
GE
RNC
RTN 910
BTS31 VLAN 310

FE
RTN 950
R4
RTN 980

QoS (DiffServ)
Differentiated service (DiffServ) configuration is essential to QoS configuration. As such, it is recommended that services at BTSs be allocated with VLAN priorities or DSCP values by
service category, so that appropriate DiffServ (DS) domains are created on the transmission network. All Ethernet ports and Integrated IP radio ports involved in transmission of these services are in the same DiffServ configurations. In the example, Ethernet services from BTSs are carried by PWs on the packet microwave network. Regarding the UNI ports and NNI ports carrying services, they must be in the same DiffServ configurations (as shown in Table 5-102); in addition, UNI ports must trust packets with C-VLAN priorities and NNI ports must trust packets with MPLS EXP values. This helps establish the mappings from UNI-side C-VLAN priorities of services to NNI-side MPLS EXP values, simplifying end-to-end QoS control. Table 5-102 Mappings between service categories and PHBs PHB CS7 CS6 EF VLAN Priority 7 6 5 MPLS EXP Value 7 6 5 Service Category Real-time voice services, signaling (R99 conversational, R99 streaming) OM, real-time HSDPA services (OM, HSPA streaming) Non-real-time R99 services (R99 interactive, R99 background) HSDPA data services (HSPA interactive, background)
AF4 AF3
4 3
4 3
AF2
AF1 BE
1 0
1 0
QoS (Queue Scheduling Mode)

Generally, each Ethernet port involved in the service uses the same queue scheduling mode. Table 5-103 lists the queue scheduling mode used by each Ethernet port involved in the service in this example.
Issue 02 (2011-01-20)
5-203
Table 5-103 Queue scheduling mode PHB Service Class CS7 CS6 EF AF4 AF3 AF2 AF1 BE Queue Scheduling Mode SP SP SP WRR (weight = 5) WRR (weight = 60) WRR (weight = 30) WRR (weight = 5) SP
QoS (CAR or Shaping Based on Complex Traffic Classification)

Generally, 2G/3G BTSs and BSCs/RNCs will perform traffic control; microwave backhaul networks do not need to perform CAR or traffic shaping.
QoS (Port Shaping)

If the Ethernet bandwidth planned for the aggregation link is lower than the total bandwidth of the aggregation services, you can 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 do not need to perform port shaping.
NOTE
When port shaping is not configured, the OptiX RTN 980 automatically performs port shaping according to the bandwidth over the IF_ETH ports.

This section describes the procedure for data configuration.
Procedure
Step 1 See A.6.7.2 Modifying the Mapping Relationships for the DS Domain, and set Packet Type to cvlan for UNI ports carrying ETH PWE3 services and to mpls-exp for NNI ports carrying ETH PWE3 services. 1. Select the default DS domain of the OptiX RTN equipment.
NOTE
In this example, use the default DS domain because the mappings from trusted packet types (C-VLAN priorities) to PHBs planned for base stations are the same as the mappings configured in the default DS domain of the OptiX RTN equipment.
5-204
Issue 02 (2011-01-20)
Parameter Mapping Relation ID Mapping Relation Name 2.
Value 1 DefaultMap
Set Packet Type to cvlan for UNI ports carrying ETH PWE3 services and to mpls-exp for NNI ports carrying ETH PWE3 services. Param eter Value NE34 (UNI) 7EM6X1 NE34 (NNI) 3ISU2-1 NE33 (NNI) 3ISU2-1 4ISU2-1 mplsexp mplsexp cvlan NE32 (UNI) 2EM6T-3 NE32 (NNI) 3-ISU2-1 17EG2D-2 mpls-exp NE31 (UNI) 3EM6T1 NE31 (NNI) 1EM6F1
Port
Packet Type
cvlan
cvlan
mplsexp
Step 2 See A.6.7.4 Creating a Port Policy and create a port policy. l The values for the related parameters of NE34, NE33, NE32, and NE31 are provided as follows. Parameter Policy ID Policy Name Grooming Police After Reloading Value 1 Port_Comm SP (CS7, CS6, EF) WRR (AF4 to AF1) SP (BE) Policy Weight(%) 5 (AF4) 60 (AF3) 30 (AF2) 5 (AF1) Bandwidth Limit Disabled (all PHBs)
Step 3 See A.6.7.7 Setting the Port That Uses the Port Policy and set the port that uses the port policy. l The values for the related parameters of NE34 are provided as follows.
Issue 02 (2011-01-20)
5-205
Parameter
Value Port_Comm (Policy ID = 1)
Port
7-EM6X-1 3-ISU2-1
l The values for the related parameters of NE33 are provided as follows. Parameter Value Port_Comm (Policy ID = 1) Port 3-ISU2-1 4-ISU2-1 l The values for the related parameters of NE32 are provided as follows. Parameter Value Port_Comm (Policy ID = 1) Port 2-EM6T-3 3-ISU2-1 17-EG2D-2 l The values for the related parameters of NE31 are provided as follows. Parameter Value Port_Comm (Policy ID = 1) Port 3-EM6T-1 1-EM6F-1
----End

Related Tasks
A.6.7.1 Creating a DS Domain A.6.7.3 Changing the Ports Applied to a DS Domain and Their Trusted Packet Types A.6.7.4 Creating a Port Policy A.6.7.6 Creating the Traffic A.6.7.7 Setting the Port That Uses the Port Policy A.6.7.8 Configuring Port Shaping
A.6.7.9 Querying the Port Policy A.6.7.10 Querying the DS Domain of a Port

There are not any QoS-related alarms or abnormal events.
Relevant Alarms
None.

None.
5.9.11 FAQs
This topic describes the answers to the questions that are frequently raised when the QoS feature is used. Q: Why are Ethernet services interrupted after port shaping is enabled? A: Generally, this problem occurs because the CIR and PIR are not set. 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.
5.10 ETH-OAM
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. 5.10.1 Introduction This section provides the definition of ETH-OAM and describes its purpose. 5.10.2 Basic Concepts This topic describes the basic concepts that you need to be familiar with before you use the ETHOAM. 5.10.3 Specifications This section describes the specifications of ETH-OAM. 5.10.4 Reference Standards and Protocols This section describes the standards and protocols associated with ETH-OAM. 5.10.5 Availability This section describes the support required by the application of the ETH-OAM feature and its dependency. 5.10.6 Principles
The ETH-OAM realizes different OAM operations through different OAM packets. 5.10.7 Planning Guidelines Follow certain guidelines when you plan ETH-OAM. 5.10.8 Configuration Procedure The configuration procedure of 802.1ag OAM and the configuration procedure of 802.3ah OAM are independent of each other. 5.10.9 Configuration Example (802.1ag OAM) This section uses an example to describe how to plan and configure the 802.3ag OAM feature. 5.10.10 Configuration Example (802.3ah OAM) This topic describes how to plan and configure 802.3ah OAM by using an example. 5.10.11 Task Collection The operation tasks related to 802.1ag OAM and the operation tasks related to 802.3ah OAM are independent of each other. 5.10.12 Relevant Alarms and Events When an NE detects an abnormality by using ETH-OAM operations, the NE reports the corresponding alarm. 5.10.13 FAQs This topic provides the answers to the questions that are frequently raised when the ETH-OAM is used.
5.10.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. OptiX RTN 980 provides a complete Ethernet OAM solution according to the ETH-OAM standard specified in IEEE 802.1ag and IEEE 802.3ah. See Figure 5-82. Figure 5-82 ETH-OAM solution
IEEE 802.3ah IEEE 802.1ag IEEE 802.3ah
Transmission network
Customer Ethernet equipment Microwave equipment
5-208
Issue 02 (2011-01-20)
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.

This topic describes the basic concepts that you need to be familiar with before you use the ETHOAM. 5.10.2.1 IEEE 802.1ag OAM Management The IEEE 802.1ag OAM focuses on the maintenance of end-to-end Ethernet links. It realizes the sectional and segmental management over the service flow by specifying the maintenance domain, maintenance association, and maintenance point. 5.10.2.2 IEEE 802.1ag OAM Operation The Ethernet unit supports the IEEE 802.1ag ETH-OAM operations, including the continuity check (CC), link trace (LT), and loopback (LB). 5.10.2.3 IEEE 802.3ah OAM Operations The Ethernet unit supports the IEEE 802.3ah Ethernet OAM operations, including the OAM auto-discovery, link performance monitoring, remote loopback, and self-loop test.
5.10.2.1 IEEE 802.1ag OAM Management

The IEEE 802.1ag OAM focuses on the maintenance of end-to-end Ethernet links. It realizes the sectional and segmental management over the service flow by specifying the maintenance domain, maintenance association, and maintenance point.
MP
The maintenance point (MP) is the functional entity of the IEEE 802.1ag OAM. Each MP has a maintenance point identification (MPID). This ID is unique on the entire network. The information about the MP is recorded in the MAC address table, MP table , and router 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 the MPs related to the service periodically. Then, the other MPs receive the protocol packet and record the information for spare use. MPs are classified into the MEP and MIP: l
Issue 02 (2011-01-20)
MEP
The maintenance association end point (MEP) specifies the starting position of the MA. It is the starting and end positions of the OAM packet and is related to services. l MIP The maintenance association intermediate point (MIP) cannot start an OAM packet. The MIP can respond to and forward an LB or LT packet, and can forward a CC packet.
NOTE
All the OAM operations must be started by the MEP. The MIP cannot start any OAM operation or send any OAM packet, but can respond to an OAM test.
MD
The maintenance domain (MD) refers to a network that requires the OAM. In a network, the network segments focused on by users, service providers, and operators are different. Thus, the management should be based on network segment to perform maintenance on network segments where a service passes through in the network. At the same time, different service traffics need be managed separately. l The IEEE 802.1ag OAM realizes the Ethernet maintenance by performing the end-to-end check based on the maintenance domain. For OAM, maintenance domain is a collection of all MPs in a service application. The MPs consist of the MEPs and MIPs. For the management segment to be maintained, establish MEPs at both ends and set the range of the maintenance domain. Moreover, establish MIPs at other positions in this management segment. Perform the operations on these maintenance points. Based on relations and responses among these MPs, the state of the whole management segment is under control. In this manner, the fault detection and location are realized.
MA
The maintenance association (MA) is a service-related domain, which consists of several MEPs and MIPs. In the network of a carrier, a VLAN is corresponding to a service instance. On the equipment, a VLAN is corresponding to an MA or multiple MAs. By dividing MAs, you can check the connectivity of the network that transmits a certain service instance and detect faults in the network. 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 the MA belongs.
NOTE
An MEP responds only to OAM operations initiated by the MEPs that belong to the same MA. To ensure correct responses to OAM operations between different MEPs in an MA, each MEP in the MA needs to be configured with the corresponding remote MEPs. That is, an MEP in the MA can respond to the OAM operations initiated by its remote MEPs in the MA.
Layered Management
The IEEE 802.1ag OAM adds the management level fields to OAM protocol packets. In this manner, the layered management is realized. The higher management domain can cross the lower management domain, but the lower management domain cannot cross the higher management domain. Based on such layered management, the maintenance of a service traffic can be realized segmentally. In addition, the management of different service traffics can be realized.
Figure 5-83 shows the logical diagram of the maintenance domain layers. Figure 5-83 Logical diagram of maintenance domain 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, the protocol supports the eight-layer division from layer 0 to layer 7. "0" indicates the lowest level and "7" indicates the highest level. Eight maintenance entities (MEs) levels correspond to the user, supplier, and operator accordingly. l l l ME levels for the user: 7, 6, 5 ME levels for the supplier: 4, 3 ME levels for the operator: 2, 1, 0
Layer levels from the higher to the lower: User ME level > Supplier ME level > Operator ME level. The dashed lines in the diagram show the logic channels where IEEE 802.1ag OAM packets pass through. Methods of maintenance points at different layers to process OAM protocol packets are as follows. l l l In the case of the OAM protocol packets whose level is higher, the maintenance points transparently transmit them. In the case of the OAM protocol packets whose level is lower, the maintenance points discard them directly. In the case of the OAM protocol packets whose level is the same, the maintenance points respond to or end the packets according to the messages types of the OAM protocol packets.
5.10.2.2 IEEE 802.1ag OAM Operation

The Ethernet unit supports the IEEE 802.1ag ETH-OAM operations, including the continuity check (CC), link trace (LT), and loopback (LB).
Table 5-104 shows the IEEE 802.1ag ETH-OAM operations and application scenarios. Table 5-104 IEEE 802.1ag ETH-OAM operations and application scenarios Operation Name CC Explanation The connectivity between the MEPs are detected through continuity check messages (CCMs) that are transmitted between MEPs periodically. This testing method is called CC.
NOTE Only an MEP can initiate or respond to a CC.
Application Scenario l The CC method is used to test unidirectional connectivity of links in real time. l To further locate the faulty link on a network, the LT method needs to be used as well.
LB
The LB can be used to test the status of the link from the source MEP to any MP in the maintenance domain.
NOTE Only an MEP can initiate or terminate an LB test.
l The LB method is used to test bidirectional connectivity of links. l Unlike a CC, the LB method provides onetime detection. You need to issue a command to initiate an LB test. l The LB method fails to locate the specific faulty link on a network in one attempt.
LT
Compared with the LB test, the LT test provides enhanced fault locating capability. That is, the faulty network segment can be located the first time in the LT test.
NOTE Only an MEP can initiate or terminate an LT test.
l The remote loopback 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.
5-212
Issue 02 (2011-01-20)
Operation Name AIS Activation
Explanation The alarm indication signal (AIS) is used to report errors to a higher level node in the case of ETH-OAM. 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 should be set to n+1.
Application Scenario The AIS activation method is used when the fault information needs to be reported to a higher level MP. If several MDs exist on links, to locate a fault accurately, activate the AIS and set the level of the customer layer that functions to suppress the AIS information.
5.10.2.3 IEEE 802.3ah OAM Operations

The Ethernet unit supports the IEEE 802.3ah Ethernet OAM operations, including the OAM auto-discovery, link performance monitoring, remote loopback, and self-loop test. Table 5-105 shows the IEEE 802.3ah ETH-OAM operations and application scenarios. Table 5-105 IEEE 802.3ah OAM operations and application scenarios Operation Name OAM AutoDiscovery Explanation By exchanging the information OAM protocol data unit (OAMPDU) periodically, the equipment at local end is informed whether and how the opposite end supports the IEEE 802.3ah OAM protocol. Application Scenario l The equipment that supports the IEEE 802.3ah OAM protocol is identified. l If the autodiscovery fails, the related alarm is reported. Description OAM autodiscovery is a prerequisite to realizing the link performance monitoring and remote loopback. The link performance monitoring and loopback functions are available at the port only when the OAM autodiscovery is successful.
Issue 02 (2011-01-20)
5-213
Operation Name Link Performance Monitoring
Explanation Link performance monitoring is used to monitor the bit error performance (error frames or error signals). When the local end detects that the bit errors exceed the threshold, the bit error event is transmitted to the opposite end over the specified OAMPDU. In this case, the opposite end reports the alarm accordingly.
Application Scenario l The service performance of the link is monitored in real time. l The link performance within a specific range is precisely analyzed and monitored. l According to actual requirements, you can configure window values and threshold values of three link performance events respectively on the NMS. In this manner, whether the link performance degrades to the threshold can be detected.
NOTE To perform performance statistics from different aspects, the link performance monitoring is classified into bit error frame event monitoring, error frame second event monitoring, and error frame period event monitoring.
Description
5-214
Issue 02 (2011-01-20)
Operation Name Remote Loopback
Explanation The OAM entity at the local end transmits the loopback control OAMPDU packets to the remote OAM to request a loopback. According to loopback data analysis, the fault locating and link performance test are performed.
Application Scenario l The problem can be located on site. l By comparing the number of transmitted packets with the number of received packets in the loopback, you can detect the link performance and link faults in this link bidirectionally from the loopback initiation end to the loopback response end. l The loopback on the port and the intra-board loopback can be tested. l Once a loop occurs during the networking operation, it is detected and the related alarm is reported.
Description
Self-Loop Test
After the self-loop test function is enabled on an Ethernet unit, you can detect the selfloop that occurs when the fiber in the transmit direction of a port is connected to the same port in the receive direction, and the intra-board loopback between two connected port on the same board.
This section describes the specifications of ETH-OAM. Table 5-106 and Table 5-107 list the specifications of ETH-OAM.
Issue 02 (2011-01-20)
5-215
Table 5-106 Specifications of ETH-OAM (IEEE 802.1ag) Item OAM operation Specification CC LB LT AIS activation Number of supported MDs Number of supported MAs Number of supported MPs Supported MP type CCM transmission interval (in the case of a standard MP) 32 32 32 Standard MP (in compliance with IEEE 802.1ag Draft 8.0) 1s 10s 1m 10m
Table 5-107 Specifications of ETH-OAM (IEEE 802.3ah) Item OAM operation Specification Auto-discovery Link performance monitoring Remote loopback Self-loop test 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:
5-216
Issue 02 (2011-01-20)
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
5.10.5 Availability
This section describes the support required by the application of the ETH-OAM feature and its dependency.

Table 5-108 Hardware and version support Feature ETH-OAM (802.1ag) Applicable Board CSHN EM6T EM6F IFU2 IFX2 ISU2 ISX2 ETH-OAM (802.3ah) CSHN EM6T EM6F IFU2 IFX2 ISU2 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 V100R003C00 and later V100R003C00 and later V100R003C00 and later V100R003C00 and later V100R003C00 and later V100R003C00 and later V100R003C00 and later V100R003C00 and later V100R003C00 and later V100R003C00 and later V100R003C00 and later V100R003C00 and later V100R003C00 and later
Issue 02 (2011-01-20)
5-217
Feature
Feature Dependency
When IEEE 802.1ag OAM is used for ETH PWE3 packets, an MEP or MIP can only be created on a UNI port but not on an NNI port.
5.10.6 Principles
The ETH-OAM realizes different OAM operations through different OAM packets. 5.10.6.1 IEEE 802.1ag OAM When the IEEE 802.1ag OAM protocol is used, OAM operations are realized through the communication of the OAMPDUs between MPs. 5.10.6.2 IEEE 802.3ah OAM When the IEEE 802.3ah OAM protocol is used, OAM operations are realized through the communication of the OAMPDUs between the equipment at both ends.
5.10.6.1 IEEE 802.1ag OAM

When the IEEE 802.1ag OAM protocol is used, OAM operations are realized through the communication of the OAMPDUs between MPs.
IEEE 802.1ag OAMPDU

The maintenance functions of IEEE 802.1ag OAM are realized through the communication of OAMPDUs between the maintenance points. Understanding the IEEE 802.1ag OAM protocol packets helps you understand how the maintenance functions of the IEEE 802.1ag OAM are realized. Figure 5-84 shows the IEEE 802.1ag OAMPDU. Figure 5-84 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
5-218
Issue 02 (2011-01-20)
l l l l l l
OAM Mac Destination Address: Indicates the broadcast address (in the case of CC) or MAC address of the destination MP (in the case of LB and LT). OAM Mac Source Address: Indicates the MAC address of the source MP. Ether Type(VLAN): Indicates the Ethernet data type, such as 0x8100. VLAN tag: Indicates the VLAN value of the service traffic. Ether Type (OAM): Indicates the packet type of the ETH-OAM protocol. OAM Type: Indicates that the MP differs and responds to various OAM operations according to the types of OAM packets. For details on the mapping between the OAM type values and OAM packet types, see Table 5-109. Table 5-109 Mapping between the OAM type values and OAM packet types 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 LB LT LT
CC
The CC is used to test the link status unidirectionally. The realization principle is as follows: 1. The source MEP constructs the CCM packets and transmits them periodically. After receiving the CCM packets 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 packets from the source MEP within the check period (that is, 3.5 times of the transmit period), it reports the alarm automatically. The alarm is cleared until the link is restored and the sink MEP receives the CCM packets from the source MEP.
2.
As shown in Figure 5-85, the realization principle of the CC is as follows: 1. 2. MEP1 transmits the CCM packets externally. MEP2, MEP3 and MEP4 in the same maintenance domain start the timers respectively to receive the CCM packets from MEP1 periodically. (1) Once the link is faulty, MEP2, MEP3, or MEP4 fails to receive the CCM packets within the check period. In this case, MEP2, MEP3, or MEP4 reports the related alarm. (2) This alarm is cleared after the link is restored.
Issue 02 (2011-01-20)
5-219
Figure 5-85 Continuity check diagram

MEP1
VB
MEP2 MEP4 VB VB MEP3
NOTE
Only the MEP can enable the continuity check and function as the receive respond end for the check.
LB Test
Based on the bidirectional service, the LB is a test performed manually at one time. The realization principle is as follows: 1. 2. The source MEP constructs the LBM packets and starts the timer at the same time. After receiving the LBM packets, the sink MP constructs the LBR packets and transmits them back to the source MEP. After the source MEP receives the LBR packet, the loopback test is successful. If the source MEP timer times out and fails to receive the LBR from the sink MP, the loopback test fails. MEP1 transmits the LBM packets to MEP4. After receiving the packets, MIP2 and MIP3 in the same maintenance domain transparently transmit the packets if the sink MAC addresses contained in the packets are different from their own MAC addresses. After receiving the packets, the sink MEP4 transmits the LBR packets back to the source MEP1. After MEIP1 receives the LBR packet, the loopback test is complete.
As shown in Figure 5-86, the realization principle of the LB is as follows: 1. 2.
3.
Figure 5-86 Loopback test diagram
MEP1
MIP2 LBM LBR
MIP3
MEP4
5-220
Issue 02 (2011-01-20)
LT Test
The realization principle of the LT test is as follows: 1. 2. The source MEP constructs the LTM packets and starts the timer at the same time. All MIPs that belong to this maintenance domain in the link continue to transmit the received LTM packets to the sink MEP. At the same time, an LTR packet is returned to the source MEP. After the sink MEP receives the LTM packets, the packet transmission is complete. Then, the sink MEP transmits LTR packets back to the source MEP. After the source MEP receives the LTR packet, the link trace test is successful. If the source MEP timer times out and fails to receive the LTR packet from the sink MEP, the loopback test fails.
NOTE
3.
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 in the link. Every time an LTR packet is returned, the number of hops is increased by one. l The function of the LT test is similar to the function of the LB test. The difference is with regard to the response to the frame. Specifically, in the LB test, only the sink MP responds to the LBM frames. In the LT test, all the MPs in the link respond to the LTM frames. According to these response messages, all the MIPs that are involved from the source MEP to the destination MEP can be identified.
As shown in Figure 5-87, the realization principle of the LT is as follows: 1. 2. 3. The source MEP1 transmits the LTM packet to the sink MEP3. After receiving the LTM packet, MIP2 transmits the LTR packet to the source MEP1 and forwards the LTM packet at the same time. After receiving the LTM packet, the sink MEP3 terminates the LTM packet and transmits the LTR packet to the source MEP1. After MEP1 receives the LTR packet, the LT test is complete.
Figure 5-87 LT test diagram
MEP1
1
MIP2 LTM LTR LTM LTR
MEP3
3
NOTE
Only an MEP can initiate or terminate an LT test.
Issue 02 (2011-01-20)
5-221
5.10.6.2 IEEE 802.3ah OAM

When the IEEE 802.3ah OAM protocol is used, OAM operations are realized through the communication of the OAMPDUs between the equipment at both ends.
IEEE 802.3ah OAMPDU

When the IEEE 802.3ah OAM protocol is used, OAM operations are realized through the communication of the OAMPDUs between the equipment at both ends. Figure 5-88 shows the IEEE 802.3ah OAMPDU. Figure 5-88 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
Mac Destination Address: Is always set to 0x01-80-C2-00-00-02. Mac Source Address: Indicates the MAC address of the port. Type: Is always set to 0x8809. Subtype: Is always set to 0x03. Flags Field: Specifies some important state information such as link fault, dying gasp, and critical event. The realization of the fault locating function depends on the state information mentioned previously. Code: Identifies the 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 related to the realization of auto-discovery, link performance monitoring, and remote loopback respectively. For details on the mapping between the Code values and OMA packet types, see Table 5-110.
5-222
Issue 02 (2011-01-20)
Table 5-110 Mapping between the Code values and OMA 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. Responds to one or multiple specific MIB messages. Enables or disables the remote OAM loopback. Reserved. Indicates the selective extended OAMPDU function used by different equipment manufacturers. Reserved.
0x02 0x03 0x04 0x05-0x FD 0xFE
Variable request Variable response Loopback control Reserved Organization specific
0xFF l
Reserved
Data/Pad Field: Indicates the OAMPDU data whose fields can be extended, with a length range from 42 bytes to 1496 types. When the OAMPDU packet length is less than 64 bytes (that is, the minimum length), the extended bytes are contained in the field. Frame Check Sequence: Indicates the frame check.
Auto-Discovery
The realization principle of the OAM auto-discovery is as follows: 1. As shown in Figure 5-89, when the Code field of the OAMPDU is 0x00, it indicates that the OAMPDU is the information OAMPDU and is used for OAM auto-discovery.
NOTE
The Data field of the information OAMPDU includes the local information type-length-value (TLV) domain and remote information type-length-value (TLV) domain. An OAM configuration byte is contained in the TLV domain. When the link is normal, successful OAM auto-discovery depends on information of bit digits in the OAM configuration bytes. In addition, the information of bit digits decides what functions are performed after the OAM auto-discovery succeeds. The Table 5-111 lists details of OAM configuration bytes.
Issue 02 (2011-01-20)
5-223
Figure 5-89 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
2.
After the IEEE 802.3ah OAM protocol is enabled, the Active end starts the discovery and broadcasts the information OAMPDU carrying the local OAM information periodically.
NOTE
The discovery can only be started by the Active end. 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.
3.
After receiving the packet from the Active end, the opposite end compares the packet with its own configuration and transmits the information OAMPDU of both ends to the initiative end. After receiving the information OAMPDU from the opposite end, the Active end updates the information about the opposite end and transmits the information OAMPDU of both ends. By exchanging the OAM information (including the OAM configuration information and OAM status information), the OAM connection is established between the two ends.
4.
5-224
Table 5-111 Details of OAM configuration bytes Bit Digit 7-5 Name Reserved Description These bits are set to 0s when the OAMPDU is transmitted and ignores these bits 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 the variable response OAMPDU. l When this bit is set to 0, it indicates that the DTE does not support the transmission of the variable response OAMPDU. 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 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.
Variable retrieval
Issue 02 (2011-01-20)
5-225
Bit Digit 2
Name OAM remote loopback support
Description l When this bit is set to 1, it indicates that the DTE supports the loopback request of the remote end. When the loopback command is issued at the remote end, the local end transmits all packets back to the remote end for loopback, excluding OAMPDU packets. l When this bit is set to 0, it indicates that the DTE does not support the remote loopback.
Unidirectional support
l When this bit is set to 1, it indicates that the local end can continue to transmit the 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 the OAMPDU packets to the remote end when the route does not work in the receive direction.
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 the Passive mode, certain OAM functions are not supported. For details, see Table 5-112.
5-226
Issue 02 (2011-01-20)
Table 5-112 Mapping between the OAM working modes and the OAM capability OAM Capability OAM Mode Active Mode Initiates the OAM autodiscovery process. Responds to the OAM autodiscovery process. Sends the information OAMPDU. Sends the event notification OAMPDU. Sends the variable request OAMPDU. Sends the variable response OAMPDU. Sends the loopback control OAMPDU. Responds to the loopback control OAMPDU. Sends the organization specific OAMPDU. Yes Yes Yes Yes Yes Yes Yes Yes Yes Passive Mode No Yes Yes Yes No Yes No Yes Yes
Link Performance Monitoring

The realization principle of the link performance monitoring is as follows. 1. As shown in Figure 5-90, when the Code filed of the OAMPDU is 0x01, it indicates that the OAMPDU is the event notification OAMPDU and is used for notifying the bit error performance event mutually.
Issue 02 (2011-01-20)
5-227
Figure 5-90 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
2.
When the IEEE 802.3ah OAM protocol is enabled at a port, the protocol queries the RMON statistic count of the hardware chip periodically to obtain the information such as the number of correct packets and the number of error packets. You can find out whether the preceding three performance events occur after processing the information. 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 related alarm for maintenance personnel to perform troubleshooting.
3.
5-228
Issue 02 (2011-01-20)

NOTE
To perform performance statistics from different aspects, the link performance monitoring is classified into bit error frame event monitoring, error frame second event monitoring, and error frame period event monitoring. l Condition for triggering error frame events: Within a period of the error frame monitor window, the number of actually received error frames is more than the pre-set threshold value. l Condition for triggering error frame second events: Within the specific seconds, the number of detected error frame seconds is more than pre-set threshold value. l Condition for triggering error frame second events: Within the specific seconds, the number of detected error frame seconds is more than pre-set threshold value.
Remote Loopback
The realization principle of the remote loopback is as follows: 1. As shown in Figure 5-91, when the Code field of the OAMPDU is 0x04, it indicates that the OAMPDU is the loopback control OAMPDU and is used for loopback tests. Figure 5-91 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
2. 3.
The loopback transmit 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 it can respond to the remote loopback, the opposite end starts remote loopback and transmits a response packet to the end that initiates the loopback. After receiving the response packet from the response end, the transmit end analyzes the packet to confirm that the opposite end is in the response loopback state. Then, the transmit end starts the loopback. In this manner, the whole process of loopback initiation is complete.
4.
Self-Loop Test
The realization principle of the self-loop test is as follows: 1. The self-loop test packet is constructed as the IEEE 802.3ah OAM protocol packet. The packet type is set to the reserved type 6. The first eight significant reserved bits in the flag field are used to carry the ID of the transmit port.
Issue 02 (2011-01-20)
2. 3.
When the self-loop test is enabled at a port, the specified self-loop check packets are transmitted from the port. One packet is transmitted every second. When a port receives the self-loop check packet, it compares the source MAC address carried in the packet 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 unit. Then, it compares the IDs of two ports. 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 self-loop.

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

When you create an MD, follow certain guidelines: 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.
When you create an MA, follow certain guidelines: 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.
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. For the NE where the source MEP is, you must configure the sink MEP as the remote MP. Before performing an LB or LT test, you must activate the CC function if you use an MP ID to identify the sink. The MAC addresses of the MEP and MIP involved in an OAM test cannot be the same.
l l l l
Select various detection functions as required. Table 5-104 provides details on IEEE 802.1ag ETH-OAM operations and application scenarios.
5-230
Issue 02 (2011-01-20)
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 5-105 details IEEE 802.3ah ETHOAM operations and application scenarios.

The configuration procedure of 802.1ag OAM and the configuration procedure of 802.3ah OAM are independent of each other. 5.10.8.1 802.1ag OAM When you use the 802.1ag OAM function, you need to define appropriate OAM maintenance points according to the actual situation and then perform OAM operations as required. 5.10.8.2 IEEE 802.3ah OAM When you use the 802.1ag OAM function, you can perform appropriate OAM operations as required.
5.10.8.1 802.1ag OAM

When you use the 802.1ag OAM function, you need to define appropriate OAM maintenance points according to the actual situation and then perform OAM operations as required.
Issue 02 (2011-01-20)
5-231
Table 5-113 Flow for configuring the 802.1ag OAM service Step 1 Operation A.6.8.1 Creating an MD Remarks Required in the case of the NE where the Ethernet ports involved in the service test are located. Set the parameters as follows: l Set Maintenance Domain Name and Maintenance Domain Level to the same values for the NEs for which OAM operations are performed. l In the test of Ethernet services between two edge nodes on the transport network, it is recommended that Maintenance Domain Level should take the value of 4. In the test of Ethernet services between two NEs within the transport network, set Maintenance Domain Level to a value less than 4. In the test of Ethernet services between two Ethernet ports on the same NE, set Maintenance Domain Level to a value less than the value that is set in the test of Ethernet services between two NEs within the transport network.
5-232
Issue 02 (2011-01-20)
Step 2
Operation A.6.8.2 Creating an MA
Remarks Required in the case of the NE where the Ethernet ports 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 previous step. l Set Maintenance Association Name to the same value for the NEs for which OAM operations are performed. l Set Relevant Service to the same service for the NEs for which OAM operations are performed.
Issue 02 (2011-01-20)
5-233
Step 3
Remarks Required in the case of the NE where the Ethernet ports 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 previous step. l Set Board and Port to the board and port where the OAM operation is started or terminated. l Set VLAN to a VLAN. The settings of the source and sink MEPs must be the same. l In the same MA, the value of MEP ID must be unique. l If the traffic flow between the MEPs that perform the OAM operation is towards the packet switching unit, the direction is set to Ingress. Otherwise, the direction is set to Egress. Generally, the ETH OAM function is applied to endto-end maintenance of a certain service. Thus, Direction is always set to Ingress for the MPs. l If the sink maintenance point is identified based on the MP ID, CC Status must be set to Active.
5-234
Issue 02 (2011-01-20)
Step 4
Remarks Required in the case of the NE where the Ethernet ports involved in the OAM operation are located. Set the parameters as follows: l Set Maintenance Domain Name to the value of Maintenance Domain Name that is set in the first step. l Set Maintenance Association Name to the value of Maintenance Association Name that is set in the second step. l If other MEPs may initiate OAM operations to an MEP in the same MA, set the other MEPs to be the remote MEPs.
A.6.8.5 Creating an MIP
Required when you need to perform LT tests and divide the faulty part into sections. l Set Maintenance Domain Name to the value of Maintenance Domain Name that is set in the first step. l Set Board and Port to the board and port through which the Ethernet service passes. l In the same MA, the value of MP ID must be unique.
A.6.8.6 Performing a CC Test A.6.8.7 Performing an LB Test A.6.8.8 Performing an LT Test
Required when you need to perform a CC test. Required when you need to perform an LB test. Required when you need to perform an LT test.
5.10.8.2 IEEE 802.3ah OAM

When you use the 802.1ag OAM function, you can perform appropriate OAM operations as required.
Table 5-114 Description of the configuration flow of the 802.3ah OAM service Step 1 Operation Enabling OAM Auto-Discovery Description Required. Set the parameters as follows: l Set Enable OAM Protocol to Enabled. l Set OAM Working Mode to Active for the NE that starts the discovery. 2 Link Performance Monitoring A.6.9.2 Enabling the Link Event Notification Optional. Set Link Event Notification to Enabled if the opposite NE needs to be informed of the faults or performance events that are detected. Optional. You can perform this operation when you need to adjust the thresholds of the performance events. Optional. Set Remote Side Loopback Response to Enabled when you need to perform a remote loopback operation. Optional. Set Loopback Check to Enabled when you need to perform self-loop tests for the ports.
A.6.9.3 Modifying the OAM Error Frame Monitoring Threshold
Remote Loopback
A.6.9.4 Performing Remote Loopback
Self-Loop Test
A.6.9.5 Enabling Self-Loop Detection
5-236
Issue 02 (2011-01-20)
5.10.9 Configuration Example (802.1ag OAM)

This section uses an example to describe how to plan and configure the 802.3ag OAM feature. 5.10.9.1 Networking Diagram The topic describes the networking information of the NEs. 5.10.9.2 Service Planning The service planning information contains all the parameter information required for configuring the NE data. 5.10.9.3 Configuration Process This topic describes the procedure for the data configuration.

The topic describes the networking information of the NEs. Figure 5-92 shows a radio network that transmits Ethernet services for base station backhauls. The network is divided into VLANs. VLANs 100 to 109 process the traffic of NodeB A, and VLANs 110 to 119 process the traffic of NodeB B. After faults occur in VLAN 100 and VALN 110, LT tests should be performed to identify the faults. l On NE1, the service from NodeB A to NE2 is named NodeAtoNE2_Vline, with an ID of 1. Whereas the service from NodeB B to NE2 is named NodeBtoNE2_Vline, with an ID of 2. ON NE2, the Ethernet service from NE1 to NE3 is named NE1toNE3_Vline_NodeA and NE1toNE3_Vline_NodeB, with an ID of 1 and 2, respectively. On NE3, the service from NE2 to RNC is a transparent point-to-point EPL service. The service is named NE2toRNC_Tline, with an ID of 1.
l l
Figure 5-92 Networking diagram of the IEEE 802.1ag OAM

NodeB A VLAN 100-109
4-IFU2-1(to NE2) 1-EM6T-1(to NodeB A) 1-EM6T-5(to NodeB B) 4-IFU2-1(to NE3) 3-IFU2-1(to NE1) 4-IFU2-1(to NE2) 1-EM6T-1(to RNC)
NE 1 NodeB B VLAN 110-119
NE 2
NE 3
RNC
Ethernet link
Radio link

Planning Information About the MP

Figure 5-93 shows the planning information about the MP. Figure 5-93 Information about the MPs that belong to different VLANs
MA1
1-EM6T-1
4-IFU2-1
3-IFU2-1
4-IFU2-1
4-IFU2-1
1-EM6T-1
VLAN100 MEP1 MIP5 MA2 MIP6 MIP7 MIP8 MEP2
1-EM6T-5
4-IFU2-1
3-IFU2-1
4-IFU2-1
4-IFU2-1
1-EM6T-1
VLAN110 MEP3 MIP5 MIP6 MIP7 MIP8 MEP4
OAM Configuration Information

Table 5-115, Table 5-116, Table 5-117, Table 5-118, Table 5-119, and Table 5-120 provide the information about the maintenance domain (MD), maintenance association (MA), maintenance end point (MEP), remote MEPs, maintenance intermediate point (MIP), and LT test. Table 5-115 Information about the MD Parameter Maintenance Domain Name Protection Level NE1 MD1 4 NE2 MD1 4 NE3 MD1 4
Table 5-116 Information about the MA Paramete r Maintenan ce Domain Name NE1 MD1 MD1 NE2 MD1 MD1 NE3 MD1 MD1
5-238
Issue 02 (2011-01-20)
Paramete r Maintenan ce Associatio n Name Relevant Service
NE1 MA1 MA2
NE2 MA1 MA2
NE3 MA1 MA2
1NodeAto NE2_Vlin e 1s
2NodeBtoN E2_Vline 1s
1NE1toNE 3_Vline_ NodeA 1s
2NE1toNE 3_Vline_ NodeB 1s
1NE2toRN C_Tline 1s
1NE2toRN C_Tline 1s
CC Test Period
Table 5-117 Information about the MEP Parameter Maintenance Domain Name Maintenance Association Name Port VLAN MP ID Direction Enable CC Test NE1 MD1 MA1 MD1 MA2 NE3 MD1 MA1 MD1 MA2
1-EM6T-1 100 1 Ingress Yes
1-EM6T-5 110 3 Ingress Yes
1-EM6T-1 2 Ingress Yes
1-EM6T-1 4 Ingress Yes
NOTE
If the sink maintenance point is identified based on the MP ID, CC Status must be set to Active.
Table 5-118 Information about the remote MEP Parameter Maintenance Domain Name Maintenance Association Name NE1 MD1 MA1 MD1 MA2 NE3 MD1 MA1 MD1 MA2
Issue 02 (2011-01-20)
5-239
Parameter Remote Maintenance Point ID
NE1 2 4
NE3 1 3
Table 5-119 Information about the MIP Parameter Maintenance Domain Name Port MP ID NE1 MD1 4-IFU2-1 5 NE2 MD1 3-IFU2-1 6 MD1 4-IFU2-1 7 NE3 MD1 4-IFU2-1 8
Table 5-120 Information about the LT test Parameter Maintenance Domain Name Maintenance Association Name Source Maintenance Point ID Sink Maintenance Point ID Node A to RNC MD1 MA1 1 2 Node B to RNC MD1 MA2 3 4

Procedure
Step 1 See A.6.8.1 Creating an MD and create the MDs. The values for the related parameters are provided as follows. Parameter Value Range NE1 Maintenance Domain Name Maintenance Domain Level
5-240
NE2 MD1 4
NE3 MD1 4
MD1 4
Issue 02 (2011-01-20)
Step 2 See A.6.8.2 Creating an MA and create the MAs. The values for the related parameters are provided as follows. Paramete r Maintena nce Domain Name Maintena nce Associatio n Name Relevant Service Value Range NE1 MD1 MD1 NE2 MD1 MD1 NE3 MD1 MD1
MA1
MA2
MA1
MA2
MA1
MA2
1NodeAto NE2_Vlin e 1s
2NodeBtoN E2_Vline 1s
1NE1toNE 3_Vline_ NodeA 1s
2NE1toNE 3_Vline_ NodeB 1s
1NE2toRN C_Tline 1s
1NE2toRN C_Tline 1s
CC Test Transmit Period
Step 3 See A.6.8.3 Creating an MEP Point and create the MEPs. The values for the relevant parameters are provided as follows, Parameter Value Range NE1 Maintenance Domain Name Maintenance Association Name Board Port VLAN MEP ID Direction CC Status
Issue 02 (2011-01-20)
NE3 MD1 MA2 MD1 MA1 MD1 MA2
MD1 MA1
1-EM6T 1-EM6T-1 (Port-1) 100 1 Ingress Active
1-EM6T 1-EM6T-5 (Port-5) 110 3 Ingress Active
1-EM6T 1-EM6T-1 (Port-1) 2 Ingress Active
1-EM6T 1-EM6T-1 (Port-1) 4 Ingress Active

5-241
Step 4 See A.6.8.4 Creating Remote MEPs in an MA and create the MEP points at the remote end. The values for the relevant parameters are provided as follows, Parameter Value Range NE1 Maintenance Domain Name Maintenance Association Name Remote Maintenance Point ID(e.g: 1,3-6) MD1 MA1 MD1 MA2 NE3 MD1 MA1 MD1 MA2
Step 5 See A.6.8.5 Creating an MIP and create the MIP. l The values for the relevant parameters of NE1 are provided as follows, Parameter Maintenance Domain Name Board Port MP ID Value Range MD1 4-IFU2 4-IFU2-1(port-1) 5
l The values for the relevant parameters of NE2 are provided as follows. Parameter Maintenance Domain Name Board Port MP ID Value Range MD1 3-IFU2 3-IFU2-1(port-1) 6 MD1 4-IFU2 4-IFU2-1(port-1) 7
l The values for the relevant parameters of NE3 are provided as follows. Parameter Maintenance Domain Name Board
5-242
Value Range MD1 4-IFU2
Issue 02 (2011-01-20)
Parameter Port MP ID
Value Range 4-IFU2-1(port-1) 8
Step 6 See A.6.8.8 Performing an LT Test and perform the LT test. l The values for the parameters that are related to the LT tests of Ethernet services from NodeB A to the RNC are provided as follows. Parameter Maintenance Domain Name Maintenance Association Name Source Maintenance Point ID Destination Maintenance Point ID Value Range MD1 MA1 1 2
l The values for the parameters that are related to the LT tests of Ethernet services from NodeB B to the RNC are provided as follows. Parameter Maintenance Domain Name Maintenance Association Name Source Maintenance Point ID Destination Maintenance Point ID Value Range MD1 MA2 3 4
In normal cases, no packets should be lost. In the case of faults, locate the faults based on the test results. ----End
5.10.10 Configuration Example (802.3ah OAM)

This topic describes how to plan and configure 802.3ah OAM by using an example. 5.10.10.1 Networking Diagram The topic describes the networking information of the NEs. 5.10.10.2 Service Planning The service planning information contains all the parameter information required for configuring the NE data. 5.10.10.3 Configuration Process This topic describes the procedure for configuring the relevant data. This topic illustrates only how to configure NE1 because NE1 and NE2 are configured in the same manner.

The topic describes the networking information of the NEs. The application of the IEEE 802.3ah OAM function does not focus on specific services. Instead, the application of the IEEE 802.3ah OAM function focuses on the maintenance of the point-topoint Ethernet link between two sets of equipment that are directly connected to each other. When 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 two ports that are connected to each other. If the OAM auto-discovery is successful, you can perform OAM operations as required. As shown in Figure 5-94, you can enable the IEEE 802.3ah OAM protocol if you need to monitor the performance over the Ethernet link between NE1 and NE2, which are connected directly to each other. Figure 5-94 Networking diagram of the IEEE 802.3ah OAM
IEEE 802.3ah 7-EM6T-1 (to NE2) 7-EM6T-1 (to NE1)
NodeB A
NE3
NE1
NE2
NE4
NodeB B
Client Ethernet equipment Microwave equipment

Parameters of the OAM

Table 5-121 provides the parameters of the OAM. Table 5-121 Parameters of the OAM Parameter Port OAM Protocol Enabled
5-244
NE1 1-EM6T-1(Port-1) Enabled
NE2 1-EM6T-1(Port-1) Enabled

Issue 02 (2011-01-20)
Parameter OAM Working Mode Link Event Notification
NE1 Active Enabled
NE2 Active Enabled
Error Frame Monitoring Information of the OAM

Table 5-122 provides the error frame monitoring information of the OAM. Table 5-122 Error frame monitoring information of the OAM Parameter Port Error Frame Monitor Window(ms) Error Frame Monitor Threshold(frame) Error Frame Period Window (frame) Error Frame Period Threshold(frame) Error Frame Second Window (s) Error Frame Second Threshold(s) NE1 1-EM6T-1(Port-1) 2000 2 2976 2 120 2 NE2 1-EM6T-1(Port-1) 2000 2 2976 2 120 2
NOTE
In normal cases, it is recommended that you use the default error frame monitoring information.

This topic describes the procedure for configuring the relevant data. This topic illustrates only how to configure NE1 because NE1 and NE2 are configured in the same manner.
Procedure
Step 1 See A.6.9.1 Enabling the OAM Auto-Discovery Function and enable the OAM auto-discovery function. The values for the related parameters are provided as follows. Parameter Enable OAM Protocol OAM Working Mode
Issue 02 (2011-01-20)
Value Range Enabled Active

5-245
Step 2 See A.6.9.2 Enabling the Link Event Notification and enable the link event notification. The values for the related parameters are provided as follows. Parameter Link Event Notification Value Range Enabled
Step 3 See A.6.9.3 Modifying the OAM Error Frame Monitoring Threshold and modify the OAM error frame monitoring threshold. The values for the related parameters are provided as follows. Parameter Port Error Frame Monitor Window(ms) Error Frame Monitor Threshold(frame) Error Frame Period Window(frame) Error Frame Period Threshold(frame) Error Frame Second Window(s) Error Frame Second Threshold(s) Value Range 1-EM6T-1(Port-1) 2000 2 2976 2 120 2
----End

The operation tasks related to 802.1ag OAM and the operation tasks related to 802.3ah OAM are independent of each other. 5.10.11.1 Task Collection(802.1ag OAM) This topic provides the hyperlinks of the operation tasks regarding 802.1ag OAM. 5.10.11.2 Task Collection (802.3ah OAM) This topic provides the hyperlinks of the operation tasks regarding 802.3ah OAM.
5.10.11.1 Task Collection(802.1ag OAM)

This topic provides the hyperlinks of the operation tasks regarding 802.1ag OAM.
Related Tasks
A.6.8.1 Creating an MD A.6.8.2 Creating an MA A.6.8.3 Creating an MEP Point
A.6.8.5 Creating an MIP A.6.8.4 Creating Remote MEPs in an MA A.6.8.6 Performing a CC Test A.6.8.7 Performing an LB Test A.6.8.8 Performing an LT Test
5.10.11.2 Task Collection (802.3ah OAM)

This topic provides the hyperlinks of the operation tasks regarding 802.3ah OAM.
Related Tasks
A.6.9.1 Enabling the OAM Auto-Discovery Function A.6.9.2 Enabling the Link Event Notification A.6.9.3 Modifying the OAM Error Frame Monitoring Threshold A.6.9.4 Performing Remote Loopback A.6.9.5 Enabling Self-Loop Detection

When an NE detects an abnormality by using ETH-OAM operations, the NE reports the corresponding alarm.
Relevant Alarms
l ETH_CFM_LOC The ETH_CFM_LOC is an alarm indicating the loss of continuity. When the system does not receive the continuity check message (CCM) packets from the remote maintenance end point (MEP) within 3.5 times the continuity check period, this alarm is reported. l ETH_CFM_MISMERGE The ETH_CFM_MISMERGE is an alarm indicating incorrect connection. When the system receives a CCM packet with a mismatched MA ID or a CCM packet with a lower priority, this alarm is reported. l ETH_CFM_RDI The ETH_CFM_RDI is an alarm indicating that the remote MEP fails to receive CCM packets. When the system receives a CCM packet that contains the RDI sent from the remote end, this alarm is reported. l ETH_CFM_UNEXPERI The ETH_CFM_UNEXPERI is an alarm indicating errored frames. When the system receives an invalid CCM packet, this alarm is reported. l ETH_EFM_DF The ETH_EFM_Discover is an alarm indicating discovery failure. When the point-to-point OAM negotiation over the Ethernet port fails, this alarm is reported. l ETH_EFM_EVENT The ETH_EFM_Event is an alarm indicating events at the opposite end. When the local end receives an OAMPDU message indicating link errors from the opposite end, this alarm is reported.
ETH_EFM_LOOPBACK The ETH_EFM_LOOPBACK is an alarm indicating loopbacks. When the local end initiates a loopback or responds to the loopback command of the opposite end, this alarm is reported.
ETH_EFM_REMFAULT The ETH_EFM_Fault is an alarm indicating faults at the opposite end. When the local end receives an OAMPDU message indicating faults from the opposite end, this alarm is reported.
ETHOAM_SELF_LOOP The ETHOAM_SELF_LOOP is an alarm indicating that loopback is performed over a MAC port when the point-to-point Ethernet OAM function is enabled. After the loopback detection function is enabled, this alarm is reported if a MAC port of a board receives the OAM protocol packets sent by the MAC port or the board.
Relevant Events
None.
5.10.13 FAQs
This topic provides the answers to the questions that are frequently raised when the 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.
5.11 Remote Network Monitoring

The remote network monitoring (RMON) feature is used to monitor the data traffic on a network segment or on an entire network. Currently, the RMON standard is one of the most widely applied network management standards. 5.11.1 Introduction This section provides the definition of RMON and describes its purpose. 5.11.2 Basic Concepts This topic describes the basic concepts that you need to be familiar with before you use the RMON feature. 5.11.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. 5.11.4 Reference Standards and Protocols This section describes the standards and protocols associated with RMON. 5.11.5 Availability This section describes the support required by the application of the RMON feature and its dependency. 5.11.6 Principles
The RMON agent is embedded in an Ethernet unit. The NMS exchanges data information with the agent through basic SNMP commands. Thus, the statistical network data is collected. 5.11.7 Planning Guidelines Follow certain guidelines when you plan RMON. 5.11.8 Configuration Procedure When applying the RMON, you need to perform different operations as required. 5.11.9 Configuration Example By using an example, this topic describes how to plan and configure the synchronous Ethernet according to the network conditions. 5.11.10 Task Collection This topic provides the hyperlinks of the operation tasks regarding the relevant feature. 5.11.11 Relevant Alarms and Events When the items in the RMON alarm group exceed the preset threshold, the relevant performance events are reported, indicating that the RMON module performance value is below the lower limit or above the upper limit. 5.11.12 FAQs This topic provides the answers to the questions that are frequently raised when the RMON is adopted.
5.11.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.

This topic describes the basic concepts that you need to be familiar with before you use the RMON feature. 5.11.2.1 SNMP Currently, the Simple Network Management Protocol (SNMP) is the most widely used network management protocol in the network. The SNMP is used to ensure transport of the management information between any two nodes in the network. This facilitates the network administrator to retrieve information, modify information, locate a fault, perform fault diagnosis, plan capacity, and generate a report on any node in the network. 5.11.2.2 RMON Management Groups The Ethernet unit realizes the following RMON management groups specified in IETF RFC2819: statistics group, history group, alarm group, and history control group.
5.11.2.3 List of RMON Alarm Entries The RMON alarm entries refer to the table entries in the RMON alarm group. 5.11.2.4 Packet-Plane RMON Performance Entry List The RMON performance entries on the packet plane refer to the table entries in the RMON statistics group or history group.
5.11.2.1 SNMP
Currently, the Simple Network Management Protocol (SNMP) is the most widely used network management protocol in the network. The SNMP is used to ensure transport of the management information between any two nodes in the network. This facilitates the network administrator to retrieve information, modify information, locate a fault, perform fault diagnosis, plan capacity, and generate a report on any node in the network.
Architecture of the SNMP

The SNMP is divided into the network management station (NMS) and the agent. NMS l l The NMS is a workstation where the client program is running. The NMS can send the request packets to the agent. After receiving these request packets, the agent performs corresponding operations according to the packet types, generates the response packets, and send the response packets to the NMS.
Agent l l The agent is server software that is running on the network equipment. It is embedded in the Ethernet unit. When an exception occurs in the equipment or the state of the equipment changes (for example, the equipment restarts), the agent sends the Trap packet to the NMS and reports the event to the NMS.
The transmission of SNMP packets is based on the connectionless transport layer UDP. Hence, the equipment can be connected to a wide variety of equipment without a block.
MIB
The management information base (MIB) refers to the managed variables in SNMP packets that are used to describe the managed objects in the equipment. The SNMP uses the architecture naming solution to uniquely identify each managed object in the equipment. The overall architecture is like a tree. The nodes on the tree indicate the managed objects. Each node can be uniquely identified by a path starting from the root. The MIB is used to describe the architecture of the tree and is the collection of the definitions of the standard variables of the monitored network equipment. The RMON is a common MIB defined according to IETF RFC2819.
5.11.2.2 RMON Management Groups

The Ethernet unit realizes the following RMON management groups specified in IETF RFC2819: statistics group, history group, alarm group, and history control group.
5-250
Issue 02 (2011-01-20)
Statistics Group
The statistics group counts the absolute performance values from the time the statistics group is created until the current time. The Ethernet unit supports statistics group based on port. The sampling interval of a statistics group can be set. The value range of the sampling interval is from 1 second to 100 seconds. For the performance entries that can be added to a statistics group, refer to 5.11.2.4 Packet-Plane RMON Performance Entry List.
Alarm Group
The alarm group monitors the specified alarm objects (for example, the performance data of ports). When the value of the monitored data crosses the configured threshold, an alarm event is generated. The Ethernet unit supports port-based alarm groups. You can create only one alarm group for a board. The number of alarm entries in an alarm group must not exceed ten. You can set the following items to which the alarm object corresponds: monitored object, sampling interval, report mode (report in case of upper threshold-crossing, report in case of lower thresholdcrossing, report all), upper threshold, and lower threshold. For the alarm entries that can be added to an alarm group, refer to 5.11.2.3 List of RMON Alarm Entries.
History Control Group

The history control group specifies the methods of monitoring history performance data. The Ethernet unit periodically collects the required statistical network information and temporarily stores the information in the board according to the attributes of the history control group. The 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 on which performance data is collected. You can set monitored objects for each history table type. l Number of items This specifies the number of history performance data entries that are stored in the Ethernet unit. Because the history performance data is stored in the wrap mode, the stored data is the latest history performance data. For example, if the number of items is set to 10, the Ethernet unit stores the latest ten history performance data entries. You can set the number of items for each history table type. The number of items can be set to 50 at most.
History Group
The history group specifies the methods of querying history performance data. The Ethernet unit filters the history performance data stored in the board according to the attributes of the history group and returns the history performance data that meets the filtering conditions. The history group has the following attributes: l
Issue 02 (2011-01-20)
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 oldest item. You can query a maximum of ten entries at one time.
NOTE
You can query performances in the history group only after the performance monitoring parameter in the history control group is pre-set.
5.11.2.3 List of RMON Alarm Entries

The RMON alarm entries refer to the table entries in the RMON alarm group. Table 5-123 List of RMON alarm entries Alarm Name ETHDROP RXBBAD ETHFCS Description The number of packet loss events crosses the threshold. The number of received bad packets crosses the threshold. The number of frames that have FCS check errors crosses the threshold. Source IFU2, IFX2, ISU2 and ISX2
Table 5-124 List of RMON alarm entries Alarm Name ETHDROP ETHEXCCO L ETHLATECO L RXBBAD Description The number of packet loss events crosses the threshold. The number of frames that fail to be transmitted after continuous collisions crosses the threshold. The number of collisions that are detected after a timeslot period elapses crosses the threshold. The number of received bad packets crosses the threshold.
Source EM6T, EM6F, EG2D
5-252
Alarm Name TXDEFFRM
Description The number of frames whose transmission is delayed crosses the threshold. The number of received undersized packets crosses the threshold. The number of received oversized packets crosses the threshold. The number of received fragmented packets crosses the threshold. The number of received errored oversized packets crosses the threshold. The number of frames that have FCS check errors crosses the threshold.
Source
ETHUNDER ETHOVER ETHFRG ETHJAB
ETHFCS
5.11.2.4 Packet-Plane RMON Performance Entry List

The RMON performance entries on the packet plane refer to the table entries in the RMON statistics group or history group. Table 5-125 Packet-Plane RMON Performance Entry List Perfor manc e Type Basic perfor mance Performance Name Description Source
RXPKTS ETHDROP RXOCTETS RXMULCAST
Indicates the packets received (packets). Indicates the packet loss events (times). Indicates the bytes received (bytes). Indicates the multicast packets received (packets). Indicates the broadcast packets received (packets). Indicates the oversized packets received (packets).
EM6T, EM6F, IFU2, IFX2, ISU2, ISX2, EG2D
RXBRDCAST
ETHOVER
EM6T, EM6F,EG2D
Issue 02 (2011-01-20)
5-253
Perfor manc e Type
Performance Name
Description
Source
ETHJAB
Indicates the oversized error packets received (packets). Indicates the undersized packets received (packets). Indicates the fragments received (packets). Indicates the collisions (times). Indicates the FCS errored frames (frames). Indicates the bytes in received good packets (bytes). Indicates the bytes in transmitted good packets (bytes). Indicates the bytes in received bad packets (bytes). Indicates the unicast packets transmitted (packets). Indicates the unicast packets received (packets). Indicates the multicast packets transmitted (packets). Indicates the broadcast packets transmitted (packets). Indicates the rate of good full-frame bytes received (bytes/second). EM6T, EM6F, IFU2, IFX2, ISU2, ISX2, EG2D EM6T, EM6F, EG2D
ETHUNDER
ETHFRG ETHCOL Extend ed perfor mance ETHFCS RXBGOOD
TXBGOOD
RXBBAD
TXUNICAST
RXUNICAST
TXMULCAST
TXBRDCAST
RXGOODFULLFRAME SPEED
5-254
Issue 02 (2011-01-20)
Perfor manc e Type
Performance Name
Description
Source
TXGOODFULLFRAME SPEED
Indicates the rate of good full-frame bytes transmitted (bytes/ second). Indicates the good fullframe bytes received (bytes). Indicates the good fullframe bytes transmitted (bytes). Indicates the pause frames received (frames). Indicates the pause frames transmitted (frames). Indicates the late collisions (times). Indicates the frames unsuccessfully transmitted after consecutive collisions (frames). Indicates the frames that are deferred in transmission (frames). Indicates the count of received 64-byte packets (errored packets included) Indicates the count of received packets with a length of 65 to 127 bytes (errored packets included) Indicates the count of received packets with a length of 128 to 255 bytes (errored packets included) ISU2, ISX2 EM6T, EM6F, EG2D EM6T, EM6F, EG2D
RXFULLBGOOD
TXFULLBGOOD
RXPAUSE TXPAUSE
ETHLATECOL ETHEXCCOL
TXDEFFRM
RXPKT64
RXPKT65
RXPKT128
Issue 02 (2011-01-20)
5-255
Perfor manc e Type
Performance Name
Description
Source
RXPKT256
Indicates the count of received packets with a length of 256 to 511 bytes (errored packets included) Indicates the count of received packets with a length of 512 to 1023 bytes (errored packets included) Indicates the count of received packets with a length of 1024 to 1518 bytes (errored packets included) Indicates the count of received packets with a length of 1519 to MTU bytes (errored packets included) Indicates the count of transmitted 64-byte packets (errored packets included) Indicates the count of transmitted packets with a length of 65 to 127 bytes (errored packets included) Indicates the count of transmitted packets with a length of 128 to 255 bytes (errored packets included) Indicates the count of transmitted packets with a length of 256 to 511 bytes (errored packets included)
RXPKT512
RXPKT1024
RXPKT1519
TXPKT64
TXPKT65
TXPKT128
TXPKT256
5-256
Issue 02 (2011-01-20)
Perfor manc e Type
Performance Name
Description
Source
TXPKT512
Indicates the count of transmitted packets with a length of 512 to 1023 bytes (errored packets included) Indicates the count of transmitted packets with a length of 1024 to 1518 bytes (errored packets included) Indicates the count of transmitted packets with a length of 1519 to MTU bytes (errored packets included) Indicates the count of transmitted cells. Indicates the count of received cells. Indicates the count of unknown cells. Indicates the number of correctable HCS error cells received. Indicates the number of uncorrectable HCS error cells received. Indicates the total number of received cells. Indicates the total number of received idle cells. Indicates the total number of transmitted cells. Indicates the maximum rate of normal cells received on the port. Indicates the minimum rate of normal cells received on the port. ML1, MD1
TXPKT1024
TXPKT1519
ATM PWE3 perfor mance
ATMPW_SNDCELLS ATMPW_RCVCELLS ATMPW_UNKNOWNCELLS
ATM/ IMA perfor mance events on the access side
ATM_CORRECTED_H CSERR ATM_UNCORRECTED _HCSERR ATM_RCVCELLS ATM_RCVIDLECELLS ATM_SNDCELLS ATM_IF_INRATE_MA X ATM_IF_INRATE_MIN
Issue 02 (2011-01-20)
5-257
Perfor manc e Type
Performance Name
Description
Source
ATM_IF_INRATE_AV G ATM_IF_OUTRATE_M AX ATM_IF_OUTRATE_M IN ATM_IF_OUTRATE_A VG ATM_CELL_AVAILABILITY PORT_RX_BW_UTILIZATION
Indicates the average rate of normal cells received on the port. Indicates the maximum rate of normal cells transmitted on the port. Indicates the minimum rate of normal cells transmitted on the port. Indicates the average rate of normal cells transmitted on the port. Indicates the percentage of valid cells. Indicates the bandwidth utilization rate (0.01%) of the port in the receive direction. Indicates the bandwidth utilization rate (0.01%) of the port in the transmit direction. Indicates the maximum rate of receiving correct cells on the UNI1 side of ATM connections. Indicates the minimum rate of receiving correct cells on the UNI1 side of ATM connections. Indicates the average rate of receiving correct cells on the UNI1 side of ATM connections. Indicates the maximum rate of transmitting correct cells on the UNI1 side of ATM connections.
PORT_TX_BW_UTILIZATION
ATM_UNI1_INRATE_ MAX
ATM_UNI1_INRATE_ MIN
ATM_UNI1_INRATE_ AVG
ATM_UNI1_OUTRATE _MAX
5-258
Issue 02 (2011-01-20)
Perfor manc e Type
Performance Name
Description
Source
ATM_UNI1_OUTRATE _MIN
Indicates the minimum rate of transmitting correct cells on the UNI1 side of ATM connections. Indicates the average rate of transmitting correct cells on the UNI1 side of ATM connections. Indicates the maximum rate of receiving correct cells on the UNI2 side of ATM connections. Indicates the minimum rate of receiving correct cells on the UNI2 side of ATM connections. Indicates the average rate of receiving correct cells on the UNI2 side of ATM connections. Indicates the maximum rate of transmitting correct cells on the UNI2 side of ATM connections. Indicates the minimum rate of transmitting correct cells on the UNI2 side of ATM connections. Indicates the average rate of transmitting correct cells on the UNI2 side of ATM connections. Indicates the total number of receiving correct cells on the UNI1 side of ATM connections. Indicates the total number of transmitting correct cells on the UNI1 side of ATM connections.
ATM_UNI1_OUTRATE _AVG
ATM_UNI2_INRATE_ MAX
ATM_UNI2_INRATE_ MIN
ATM_UNI2_INRATE_ AVG
ATM_UNI2_OUTRATE _MAX
ATM_UNI2_OUTRATE _MIN
ATM_UNI2_OUTRATE _AVG
ATM_UNI1_INCELLS
ATM_UNI1_OUTCELLS
Issue 02 (2011-01-20)
5-259
Perfor manc e Type
Performance Name
Description
Source
ATM_UNI2_INCELLS
Indicates the total number of receiving correct cells on the UNI2 side of ATM connections. Indicates the total number of transmitting correct cells on the UNI2 side of ATM connections. Indicates the number of lost disordered packets. Indicates the number of mis-connected packets. Indicates the number of deformed frames. Indicates the number of jitter buffer underflows. Indicates the number of jitter buffer overflows. Indicates the number of lost packets. Indicates the number of received packets. Indicates the number of packets received from PWs. Indicates the number of bytes received from PWs. Indicates the number of packets received on the V-UNI. Indicates the number of bytes received on the VUNI. Indicates the number of packets received in the reverse tunnel. CSHN
ATM_UNI2_OUTCELLS
CES perfor mance event
CES_MISORDERPKTS CES_STRAYPKTS CES_MALPKTS CES_JTRUDR CES_JTROVR CES_LOSPKTS CES_RX_PKTS
ATM/ CES
PW_RCVPKTS
PW_RCVBYTES L2VP Na perfor mance VUNI_RCVPKTS
VUNI_RCVBYTES
Tunnel perfor mance
TUNNEL_REVERSE_R CVPKTS
5-260
Issue 02 (2011-01-20)
Perfor manc e Type
Performance Name
Description
Source
TUNNEL_REVERSE_R CVBYTES TUNNEL_RCVPKTS
Indicates the number of bytes received in the reverse tunnel. Indicates the number of packets received in the tunnel. Indicates the number of bytes received in the tunnel. Indicates the number of packets received on the PW. Indicates the number of bytes received on the PW.
TUNNEL_RCVBYTES
PW perfor mance of L2VP N
PW_RCVPKTS
PW_RCVBYTES
NOTE
l a: L2VPN services include a variety of E-Line and E-LAN services supported by the equipment. l VUNI represents virtual UNI, corresponding to the source or sink of a service. l The E-Line services transmitted by the OptiX RTN 980 do not support the VUNI-based RMON performance statistics. l l Integrated IP radio ports support this parameter.
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 5-126 lists the specifications of RMON.
Issue 02 (2011-01-20)
5-261
Table 5-126 Specifications of RMON Item Statistical object Specification l Ethernet port l Integrated IP radio port l VCG port l PW carrying ATM services l ATM trunk l ATM connection l PW carrying CES services l UNI port of an E-Line service carried by a PW l PW carrying E-Line services l MPLS tunnel Statistics group Querying the realtime performance statistics of each statistical object Sampling interval (s) Resetting statistics group counter Alarm group Querying the realtime alarm statistics of each statistical object Sampling interval (s) Supported
5-150 Supported Supported
30-second 30-minute Custom period 1 (300 seconds to 43200 seconds) Custom period 2 (300 seconds to 86400 seconds)
Setting the upper and lower thresholds of performance statistics History control group Setting the sampling period of history performance statistics History register counter
Supported
30-second 30-minute Custom period 1 (300 seconds to 43200 seconds) Custom period 2 (300 seconds to 86400 seconds) 1-50
5-262
Issue 02 (2011-01-20)
Item History group Querying the history performance statistics of each statistical object Setting the sampling period of history performance statistics
Specification Supported
30-second 30-minute Custom period 1 (300 seconds to 43200 seconds) Custom period 2 (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
5.11.5 Availability
This section describes the support required by the application of the RMON feature and its dependency.

Table 5-127 Hardware and version support Feature RMON Applicable Board CSHN EM6T EM6F IFU2 IFX2 ISU2 Applicable Hardware Version All the versions All the versions All the versions All the versions All the versions All the versions Applicable Product Version V100R003C00 and later V100R003C00 and later V100R003C00 and later V100R003C00 and later V100R003C00 and later V100R003C00 and later
5-263
Issue 02 (2011-01-20)
Feature
Feature Dependency
RMON does not affect other features.
5.11.6 Principles
The RMON agent is embedded in an Ethernet unit. The NMS exchanges data information with the agent through basic SNMP commands. Thus, the statistical network data is collected.
Statistics Group
The realization principle of the statistics group 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 unit resets the corresponding current performance counting register and returns the corresponding response packet to the NMS according to the information about 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.
l If the maintenance engineer clicks Start, the RMON agent does not reset the performance counting register. l If the maintenance engineer does not select Display Accumulated Value, the NMS obtains the performance value of a sampling interval by performing a subtraction operation between the sampled value returned at the end of the sampling interval and the sampled value returned at the end of the previous sampling interval.
Alarm Group
The realization principle of the alarm group 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 unit monitors the corresponding alarm object according to the information about the alarm group in the request packet. When the alarm object exceeds the configured 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.
5-264
History Control Group

The realization principle of the history control group 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 unit 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.
History Group
The realization principle of the history group is as follows: 1. 2. 3. The maintenance engineer clicks Query. The NMS sends the corresponding request packet to the RMON agent. The RMON agent embedded in the Ethernet unit 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 the RMON, you need to perform different operations as required.
Table 5-128 Procedure of configuring the RMON Step 1 Operation A.9.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 Period as required. l If you need to browse over 10 performance events, set Display Mode to List. 2 A.9.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 Set History Table Type as required. l If you need to browse over 10 performance events, set Display Mode to List. 3 A.9.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 specify certain alarms to be monitored. Set the parameters according to the requirement.
A.9.2 Configuring an Alarm Group for an Ethernet Port

By using an example, this topic describes how to plan and configure the synchronous Ethernet according to the network conditions. 5.11.9.1 Networking Diagram
The topic describes the networking information about the NEs. 5.11.9.2 Troubleshooting Analysis This topic describes the basic thoughts when you use the RMON function to rectify Ethernet faults. 5.11.9.3 Troubleshooting Flow This topic describes how to rectify service faults.

The topic describes the networking information about the NEs. As shown in Figure 5-95, the point-to-point private line service between NE2 and the BSC is configured on the 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 5-95 Networking diagram
4-IFU2-1(to NE1) 1-EM6F-5(to BTS1) 1-EM6F-6(to BTS2)
Tranparent transmission E-LINE service
4-IFU2-1(to NE2) 1-EM6F-5(to BSC)
BTS1 BTS2 NE2

Ethernet link
NE1
Radio link
BSC
5.11.9.2 Troubleshooting Analysis

This topic describes the basic thoughts when you use the RMON function to rectify Ethernet faults.
Procedure
Step 1 Check the traffic of each Ethernet port and Hybrid IF board along the signal flow of the faulty service, to determine the port where the fault occurs. l If the traffic transmitted from the transmit port is almost equal to the traffic received at the receive port, it indicates that no anomalies occur. l If the traffic transmitted from the transmit port is largely different from the traffic received at the receive port, it indicates that an anomaly occurs. Step 2 Browse the count of the performance threshold-crossing events at the faulty port, and determine the cause of the fault. For details on operations, see the description of the RMON alarms and performance events in the Alarms and Performance Events References. Step 3 Rectify the fault. For details on operations, see the description of the RMON alarms and performance events in the Alarms and Performance Events References. ----End
5.11.9.3 Troubleshooting Flow

This topic describes how to rectify service faults.
Procedure
Step 1 Count the received packets and transmitted packets of each Ethernet port and Hybrid IF board during the same period. For details on operations, see Browsing the Performance Data in the History Group of an Ethernet Port. The result is as follows: l The traffic transmitted from BTS1 is almost equal to the traffic received at 1-EM6F-5 on NE2. The traffic transmitted from BTS2 is almost equal to the traffic received at 1EM6F-6 on NE2. l The sum of traffic transmitted from 1-EM6F-5 and 1-EM6F-6 on NE 2 is almost equal to the traffic received at 4-IFU2-1 on NE2. l The traffic transmitted from 4-IFU2-1 on NE2 is almost equal to the traffic received at 4IFU2-1 on the opposite NE1. l The traffic transmitted from 4-IFU2-1 on NE1 is almost equal to the traffic received at 1EM6F-5 on NE1. l The traffic received at the BSC is largely different from the traffic transmitted from 1EM6F-5. Thus, it can be inferred that the link between NE1 and the BSC is faulty. Step 2 Browse the abnormal events of the BSC and NE1. It is found that the BSC and NE1 report the abnormal event indicating the RMON module performance higher than the upper threshold for many times. The abnormal event is caused by an RMON entry, namely, the received fragmented packet (ETHFRG). See the Alarms and Performance Events References, and the possible causes of the fault are as follows: l The devices at both ends work in different modes. l A hardware fault occurs at the local end. Step 3 See the Alarms and Performance Events References for handling the fault. 1. Query the Ethernet working mode of the 1-EM6F-5 port on NE1 and the Ethernet port on the BSC. For details on operations, see A.5.6.1 Setting the General Attributes of Ethernet Ports in the Configuration Guide. The Ethernet ports on NE1 and the BSC work in different modes. Change the working mode of the 1-EM6F-5 port on NE1 so that it can work in the same mode as the Ethernet port on the BSC. For details on operations, see A.5.6.1 Setting the General Attributes of Ethernet Ports in the Configuration Guide.
2.
----End

Related Tasks
A.9.1 Browsing the Performance Data in the Statistics Group of an Ethernet Port A.9.2 Configuring an Alarm Group for an Ethernet Port
A.9.3 Configuring a History Control Group A.9.4 Browsing the Performance Data in the History Group of an Ethernet Port

When the items in the RMON alarm group exceed the preset threshold, the relevant performance events are reported, indicating that the RMON module performance value is below the lower limit or above the upper limit.
Relevant Alarms
None.
Relevant Events
l RMON Performance Value Below the Lower Limit This abnormal event indicates that the current RMON performance value is lower than the preset lower limit. l RMON Performance Value Above the Upper Limit This abnormal event indicates that the current RMON performance value is higher than the preset upper limit.
5.11.12 FAQs
This topic provides the answers to the questions that are frequently raised when the RMON is adopted. Q: How does one use the statistical items obtained with the RMON function? A: The statistical items obtained with the RMON function are primarily applied in the following scenarios: l Analyzing the abnormal statistical items of the port. The key abnormal statistical items are as follows: Fragments received Generally, fragments are caused by inconsistent working modes at both ends. Fragments occur most commonly when the working mode at one end is set to auto-negotiation but the working mode at the other end is set to full-duplex. Undersized packets received When the undersized packets are received, 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. Oversized packets received Generally, the oversized packets are caused by the over low value of MTU. Frames with FCS errors 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. Received frames with the PAUSE operation code, transmitted frames with the PAUSE operation code If the frames with the PAUSE operation code are received or transmitted, first check the settings of flow control, and then suggest that the customer adjust the service load or perform flow shaping to avoid the fault. l Analyzing the transmission and receiving of data packets at each port For example, you can count the packets at the receive port and compare the count with the number of packets at the transmit port to determine whether packet loss occurs. l Analyzing the traffic at a port For example, in the case of a transparently transmitted service from a port to an IF port, you can count the bytes received and the bytes transmitted on the port and compare the number of bytes with the bandwidth of the IF port to determine whether the bandwidth bound to the IF port is appropriate. l Analyzing the types of packets For example, in the case of a PORT mounted by a bridge, you can count the received broadcast packets and the total received packets and calculate the ratio of the broadcast packets to the total received packets to judge whether a broadcast storm occurs on the opposite equipment.
5-270
Issue 02 (2011-01-20)
6 Packet Features
6
About This Chapter
6.2 MPLS OAM This chapter describes the MPLS OAM feature.
Packet Features
This chapter describes the MPLS/PWE3 and ATM features that pertain to the products. 6.1 MPLS Basics This chapter describes the basics of the Multiprotocol Label Switching (MPLS) technology.
6.3 LSP Ping/Traceroute This chapter describes the LSP ping and LSP traceroute features. 6.4 MPLS APS This chapter describes the MPLS automatic protection switching (APS) feature. 6.5 PWE3 Basics This chapter describes the basics of pseudo wire emulation edge-to-edge (PWE3). 6.6 TDM PWE3 This chapter describes the TDM PWE3 feature. 6.7 ATM PWE3 This chapter describes the ATM PWE3 feature. 6.8 ETH PWE3 This chapter describes the ETH PWE3 feature. 6.9 PW OAM This chapter describes the PW OAM feature. 6.10 PW Ping/Traceroute This chapter describes the PW ping and PW traceroute features. 6.11 PW APS This chapter describes the PW automatic protection switching (APS) feature. 6.12 ATM Basics This chapter describes the basics of asynchronous transfer mode (ATM).
6 Packet Features
6.13 IMA This chapter describes the inverse multiplexing for ATM (IMA) feature. 6.14 ATM OAM This chapter describes the ATM OAM feature. 6.15 ATM Traffic Management This chapter describes the ATM traffic management feature.
6-2
Issue 02 (2011-01-20)
6 Packet Features
6.1 MPLS Basics

This chapter describes the basics of the Multiprotocol Label Switching (MPLS) technology. 6.1.1 Introduction This section provides the definition of MPLS and describes its purpose. 6.1.2 Basic Concepts This section describes the basic concepts associated with MPLS. 6.1.3 Specifications This section describes the specifications for MPLS. 6.1.4 Reference Standards and Protocols This section describes the standards and protocols associated with MPLS basics. 6.1.5 Availability This section describes the support required by the application of the MPLS feature and its dependencies. 6.1.6 Principles On an MPLS network, LSRs enable the packets with the same characteristics to be transmitted on one LSP based on a unified forwarding mechanism. 6.1.7 Configuration Procedure MPLS tunnels can be configured in end-to-end mode or on a per-NE basis. 6.1.8 Configuration Example This section uses an example to describe how to plan and configure MPLS tunnels according to network conditions. 6.1.9 Task Collection This section provides the hyperlinks of the operation tasks associated with the feature. 6.1.10 Relevant Alarms and Events When an exception is detected in the MPLS tunnel, an NE reports the specific alarm. 6.1.11 FAQs This section provides answers to the questions that are frequently raised when MPLS is used.
6.1.1 Introduction
This section provides the definition of MPLS and describes its purpose.
Definition
Based on IP routes and control protocols, MPLS is a connection-oriented switching technology for the network layer. MPLS uses short and fixed-length labels at different link layers for packet encapsulation, and switches packets based on the encapsulated labels. MPLS has two planes: control plane and forwarding plane. The control plane is connectionless, featuring powerful and flexible routing functions to meet network requirements for a variety of new applications. This plane is mainly responsible for label distribution, setup of label forwarding tables, and setup and removal of label switched paths (LSPs). The forwarding plane is also called the data plane. It is connection-oriented and supports Layer 2 networks such as
6 Packet Features
ATM and Ethernet networks. The forwarding plane adds or deletes IP packet labels, and forwards the packets according to the label forwarding table.
Purpose
In the packet domain, MPLS helps to set up MPLS tunnels to carry PWs that transmit a variety of services on a PSN in an end-to-end manner. These services include TDM, ATM, and Ethernet services. Figure 6-1 shows the typical MPLS application in the packet domain. In the figure, the services between the NodeBs and RNCs are transmitted by PW1 and PW2 carried by the MPLS tunnel. Figure 6-1 Typical MPLS application
Ethernet, ATM, TDM Ethernet, ATM, TDM
PSN
NodeB
PW1 PW2
RNC MPLS tunnel NE2 RNC Ethernet, ATM, TDM
NE1 NodeB Ethernet, ATM, TDM Packet transmission equipment

This section describes the basic concepts associated with MPLS. 6.1.2.1 MPLS Network Architecture An MPLS network, also called an MPLS domain, is a network area that consists of interconnected label switching routers (LSRs). An LSR, also called an MPLS node, is a network device that performs MPLS label switching and packet forwarding. 6.1.2.2 LSP Label switched paths (LSPs), also called MPLS tunnels, are classified into various types depending on different classification criteria. 6.1.2.3 Bearer Mode for MPLS Packets The OptiX RTN 980 uses Ethernet frames to bear MPLS packets. 6.1.2.4 MPLS Label MPLS uses short and fixed-length labels at different link layers for packet encapsulation, and supports MPLS label stacking to form label stacks.
6-4
Issue 02 (2011-01-20)
6 Packet Features
6.1.2.1 MPLS Network Architecture

An MPLS network, also called an MPLS domain, is a network area that consists of interconnected label switching routers (LSRs). An LSR, also called an MPLS node, is a network device that performs MPLS label switching and packet forwarding. Figure 6-2 shows the MPLS network architecture. On an MPLS network, LSRs on the network edge are called label edge routers (LERs), and LSRs within the network range are called core LSRs. An LER may have one or more adjacent non-LSR nodes, but all the adjacent nodes of a core LSR are LSRs. Figure 6-2 MPLS network architecture
LER Other MPLS network
MPLS network
Other MPLS network LER
LER
LSR
Core LSR
LSR
LER
Other MPLS network
Packet transmission equipment
On an MPLS network, each LSR has a unique identifier; that is, a 16-byte LSR ID. An LSR ID can be based on the IPv4 address or IPv6 address.
NOTE
Currently, the OptiX RTN 980 supports only LSR IDs based on the IPv4 address.
6.1.2.2 LSP
Label switched paths (LSPs), also called MPLS tunnels, are classified into various types depending on different classification criteria.
Basic Concepts of LSPs

On an MPLS network, an LSR adopts the same label switching mechanism to forward packets with the same characteristics. The packets with the same characteristics are called a forwarding equivalence class (FEC). The path along which an FEC travels through the MPLS network is called an LSP, or an MPLS tunnel. To provide a unified interface for upper-level applications of an LSP, the system needs to assign an ID to the LSP. This ID is called an LSP ID or tunnel ID. An LSP ID is 4-byte long, and is only valid for the local LSR. An LSP is unidirectional. As shown in Figure 6-3, LSRs on an LSP can be classified into the following types:
6 Packet Features
Ingress An LSP ingress node pushes a label onto the packet for MPLS packet encapsulation and forwarding. One LSP has only one ingress node.
Transit An LSP transit node swaps labels and forwards MPLS packets according to the label forwarding table. One LSP may have one or more transits nodes.
Egress An LSP egress node pops the label and recovers the packet for forwarding. One LSP has only one egress node.
Figure 6-3 Classification of LSRs on an LSP
MPLS network
Other MPLS network Other MPLS network
Ingress
Transit
Transit
Egress
LSP
LSP Types
LSPs are classified into various types depending on different classification criteria. For details, see Table 6-1. Table 6-1 LSP types Aspect Setup mode LSP Type Static tunnel Definition A static tunnel is set up according to the data configurations. A dynamic tunnel is set up by running the Label Distribution Protocol (LDP). A unidirectional tunnel is an LSP with one specific direction. The OptiX RTN 980 supports both types. Support Capability The OptiX RTN 980 supports static tunnels.
Dynamic tunnel
Direction
Unidirectional tunnel
6-6
Issue 02 (2011-01-20)
6 Packet Features
Aspect
LSP Type Bidirectional tunnel
Definition A bidirectional tunnel is actually a pair of LSPs that have the same path but different directions. An E-LSP uses the EXP field for prioritizing packet scheduling. One ELSP supports PWs belonging to up to eight scheduling types. An L-LSP uses the MPLS label value for prioritizing packet scheduling priority. One L-LSP supports PWs belonging to one scheduling type. The TE tunnel has the preset bandwidth. The bandwidth is unlimited. When an egress node pops the MPLS tunnel label, it renews the packet scheduling priority according to the EXP field in the label. When an egress pops the MPLS tunnel label, it does not renew the packet scheduling priority.
Support Capability
DiffServ identification mode
E-LSP
The OptiX RTN 980 supports both types. However, the OptiX RTN 980 does not support prioritizing packet discarding.
L-LSP
Bandwidth limit
TE tunnel Bandwidthunlimited tunnel
The OptiX RTN 980 supports both types.
LSP mode
Uniform
The OptiX RTN 980 supports the Pipe mode only.
Pipe
6.1.2.3 Bearer Mode for MPLS Packets

The OptiX RTN 980 uses Ethernet frames to bear MPLS packets. Figure 6-4 shows how an Ethernet frame bears an MPLS packet.
Issue 02 (2011-01-20)
6-7
6 Packet Features
Figure 6-4 Bearer mode for MPLS packets

Ethernet header MPLS packet FCS (CRC-32)
Destination address
Source address
802.1q header Length/Type
l l l
Destination address: It is the MAC address of the opposite interface, learnt through the Address Resolution Protocol (ARP). Source address: It always takes the MAC address of the system. 802.1q header: The OptiX RTN 980 determines whether an Ethernet frame at the egress port carries the 802.1q header based on the TAG attribute of an Ethernet port. If the TAG attribute is Access, the Ethernet frame will not carry the 802.1q header; if the TAG attribute is Tag aware, the VLAN ID of the 802.1q header in an MPLS packet is the tunnel VLAN ID that is set on the NMS; if the tunnel VLAN ID is absent, the VLAN ID of the 802.1q header is the default VLAN ID (that is, 1) at the NNI port transmitting MPLS packets. Length/Type: It is always set to 0x8847. After detecting the value, the OptiX RTN 980 considers the packet is the Ethernet frame carrying MPLS packet. The NE will not detect MPLS packets at the ingress port based on the TAG attribute and VID of an LSP. MPLS packet: It consists of the MPLS label and Layer 3 user packet. For details on its format, see 6.1.2.4 MPLS Label. Frame check sequence (FCS): It is used to verify that the Ethernet frame is correct.
NOTE
l l
The ARP is used to translate the IP address at the network layer (that is, logical address) into the MAC address at the data link layer (that is, physical address). By default when the TAG attribute of a UNI port is Tag ware, an ARP packet that is transmitted or received through an NNI port has an VLAN ID that is the default value of the NNI port. Therefore, the TAG attribute and default VLAN ID of a NNI port must be the same as those of a peer NNI port. All the ports on the packet plane take the same MAC address, that is, the MAC address of the system. The FE, GE, and microwave ports all use Ethernet frames to bear MPLS packets.
As shown in Figure 6-5, to allow the LSPs to traverse the Layer 2 network, the VLAN subinterface function must be enabled for the ports on NE2, NE3, and NE5 for carrying the LSPs, and VLAN IDs must be specified for the services. The VLAN IDs carried by the services must be different from the VLAN IDs carried by the other services on the Layer 2 network. In this manner, the services on the LSPs will not conflict with the services on the Layer 2 network.
6-8
Issue 02 (2011-01-20)
6 Packet Features
Figure 6-5 LSP traversing a Layer 2 network

LSP1
LSP1 LSP2 NE1 NE2
VLA
N4
060
NE5
NE6
L2 network
VLA N4 090
LSP2 NE3 NE4
6.1.2.4 MPLS Label

MPLS uses short and fixed-length labels at different link layers for packet encapsulation, and supports MPLS label stacking to form label stacks.
Label Format
The OptiX RTN 980 uses Ethernet frames to bear MPLS packets. Figure 6-6 shows the format of the MPLS label. Figure 6-6 Format of the MPLS label
0 Label 20 EXP 23 24 S TTL 31bit
MPLS label
Layer 3 Payload
MPLS packet
l l
Label: This 20-bit field indicates the actual label value. EXP: Theis 3-bit field is reserved for experimental use. On the OptiX RTN 980, the EXP is used to identify the priority of an MPLS packet, similar to the VLAN priority specified in IEEE 802.1p. S: This 1-bit field identifies the bottom of stack. MPLS supports multiple labels, that is, label stacking. This bit is set to 1 for the bottom label in the label stack. Time to Live (TTL): This 8-bit field has the same meaning as the TTL specified for IP packets.
l l
Label Stack
A label stack refers to an ordered set of labels. MPLS allows a packet to carry multiple labels. The label next to the Layer 2 header is called the top label or outer label, and the label next to
6 Packet Features
the IP header is called the bottom label or inner label. Theoretically, an unlimited number of MPLS labels can be stacked. Figure 6-7 MPLS label stack
Label stack Ethernet header /PPP header
Outer label
Inner label
Layer 3 Payload
The label stack is organized as a Last In, First Out stack. The top label is always processed first.
Label Space
The value range for label distribution is called a label space. Two types of label space are available: l l Per-platform label space An LSR uses one label space; that is, the labels are unique per LSR. Per-interface label space Each interface on an LSR uses a label space; that is, the labels are unique per interface, but can be repeated on different interfaces. The OptiX RTN 980 supports only the per-platform label space with a fixed value range of 16 to 1048575. Values of 0 to 15 are reserved for special use and cannot be assigned to LSPs.
This section describes the specifications for MPLS. Table 6-2 lists the specifications for MPLS. Table 6-2 Specifications for MPLS Item Type of port carrying the LSP Specifications l FE/GE l IP microwave port Maximum number of MPLS tunnels 1024
NOTE The total number of tunnels and PWs cannot exceed 1024. The tunnels carrying PWs are not included.
LSP type
Setup mode Direction
Static tunnel Unidirectional tunnel Bidirectional tunnel
6-10
Issue 02 (2011-01-20)
6 Packet Features
Item Scheduling attribute
Specifications l E-LSP l L-LSP LSP mode Pipe 32768 Based on the IPv4 address Maximum number of static entries Maximum number of dynamic entries Setting of aging time 256 64 at each port Supported Supported
NOTE For details, see 6.4.3 Specifications.
Per-platform label space size Format of LSR ID ARP
MPLS APS
MPLS OAM
Supported
LSP ping/traceroute
Supported
QoS
l Restricting LSP bandwidth l Mapping between the EXP values and the PHB levels

This section describes the standards and protocols associated with MPLS basics. The following standards and protocols are associated with MPLS: l l IETF RFC 3031: Multiprotocol Label Switching Architecture IETF RFC 3032: MPLS Label Stack Encoding
6.1.5 Availability
This section describes the support required by the application of the MPLS feature and its dependencies.
Issue 02 (2011-01-20)
6-11
6 Packet Features

Table 6-3 Hardware and version support Feature MPLS Applicable Board CSHN IFU2 IFX2 ISU2 ISX2 EM6T EM6F Applicable Hardware Version All the versions All the versions All the versions All the versions All the versions All the versions All the versions Applicable Product Version V100R003C00 and later V100R003C00 and later V100R003C00 and later V100R003C00 and later V100R003C00 and later V100R003C00 and later V100R003C00 and later
The dependencies between the MPLS feature and other features are as follows: l l l MPLS tunnels carry TDM PWE3, ETH PWE3, and ATM PWE3 services. The mapping relations in the Diffserv domain for performing QoS can be created based on the EXP values of MPLS labels. LAGs support the load-sharing algorithm based on MPLS label.
6.1.6 Principles
On an MPLS network, LSRs enable the packets with the same characteristics to be transmitted on one LSP based on a unified forwarding mechanism.
Basic Concepts of Packet Forwarding

l Next Hop Label Forwarding Entry (NHLFE) The NHLFE is fundamental to packet forwarding implemented by an LSR. An NHLFE contains the following information: the next hop address, interface address, operation type for labels, and the data link layer protocol to use. The operations to perform on the label may be Push, Pop, Swap, and Null (retaining a label). l FEC to NHLFE (FTN) The FTN maps each FEC to a set of NHLFEs. Only an ingress node supports this operation.
6 Packet Features
Incoming Label Map (ILM) The ILM maps each incoming label to a set of NHLFEs. Only transit and egress nodes support this operation.
MPLS Packet Forwarding Process

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

Table 6-4 provides the NHLFE for NE A (ingress node). Table 6-4 NHLFE for NE A LSP ID 101 Outgoing Interface PORT 1 Next Hop PORT 2 Outgoing Label 20 Operation Push
NE A process an MPLS packet as follows: 1. 2. Receives a packet, and finds the LSP ID based on the FEC of the packet. Finds the NHLFE based on the LSP ID and then obtains the information such as outgoing interface, next hop, outgoing label, and operation. The label operation for an ingress node is Push. Pushes an MPLS label to the packet, and forwards the encapsulated MPLS packet to the next hop.
3.
Procedure on a Transit Node

Table 6-5 provides the NHLFE for NE B (transit node).
6 Packet Features
Table 6-5 NHLFE for NE B LSP ID 101 Outgoing Interface PORT 3 Next Hop PORT 4 Outgoing Label 21 Operation Swap
NE B processes an MPLS packet as follows: 1. 2. Finds the LSP ID based on the label value of the MPLS packet received at the incoming interface. Finds the NHLFE based on the LSP ID and then obtains the information such as outgoing interface, next hop, outgoing label, and operation. The label operation for a transit node is Swap. The outgoing label value of the NHLFE is 21. Thus, NE B replaces the old label value of 20 with a new label value of 21 and then sends the MPLS packet carrying the new label to the next hop.
NOTE
3.
If the value of the new label is equal to or greater than 16, the label operation is Swap. If the value of the new label is less than 16, this label is special and needs to be processed according to the specific value of the label.
The processing of an MPLS packet on NE C is similar to the that of an MPLS packet on NE B.
Procedure on an Egress Node

Table 6-6 provides the NHLFE for NE D (egress node). Table 6-6 NHLFE of NE D LSP ID 101 Outgoing Interface Next Hop Outgoing Label Operation Pop
NE D processes an MPLS packet as follows: 1. 2. 3. Finds the LSP ID based on the label value of the MPLS packet received at the incoming interface. Finds the NHLFE based on the LSP ID and then determines that the label operation is Pop. Pops the MPLS label and forwards the MPLS packet.

MPLS tunnels can be configured in end-to-end mode or on a per-NE basis. 6.1.7.1 Configuration Procedure (on a Per-NE Basis) This section describes the procedures for configuring MPLS tunnels, MPLS OAM, MPLS APS, QoS, and the procedure for verifying the configurations.
6 Packet Features
6.1.7.1 Configuration Procedure (on a Per-NE Basis)

This section describes the procedures for configuring MPLS tunnels, MPLS OAM, MPLS APS, QoS, and the procedure for verifying the configurations. Figure 6-9 provides the procedures for configuring MPLS tunnels. Figure 6-9 Configuration flow chart (MPLS tunnels)
Required Optional Set NNI port attributes Start
Create MPLS tunnels
Create MPLS protection groups
Set the QoS policy for NNI ports Verify configured MPLS tunnels End
Issue 02 (2011-01-20)
6-15
6 Packet Features
Table 6-7 Procedure for setting UNI port attributes Operation Setting attributes of Ethernet ports A.5.6.1 Setting the General Attributes of Ethernet Ports Description Required. Set the major parameters as follows: l In the case of used ports, set Enable Port to Enabled. In the case of unused ports, set Enable Port to Disabled. l Set Port Mode to Layer 3. l In the case of an Ethernet port that is connected to external equipment, set Working Mode to be the same value as the external equipment (generally, the working mode of the external equipment is autonegotiation). In the case of Ethernet ports for connection within the network, set Working Mode to Auto-Negotiation. l Set Max Frame Length(byte) according to the service packet length. It is recommended that you set Max Frame Length(byte) to 1620. A.5.6.2 Configuring the Traffic Control of Ethernet Ports Required when the flow control function is enabled on the external equipment to which the Ethernet port is connected. Set the major parameters as follows: l When the external equipment uses the non-autonegotiation flow control function, set NonAutonegotiation Flow Control Mode to Enabled . l When the external equipment uses the autonegotiation flow control function, set AutoNegotiation Flow Control Mode to Enabled. A.5.6.4 Setting Layer 3 Attributes of Ethernet Ports Required. Set the major parameters as follows: l In the case of used ports, set Enable Tunnel to Enabled. l Set Specify IP Address and IP Address according to planning information. The IP addresses of different ports on the NE cannot be in the same network segment, but the IP addresses of the ports at both ends of the MPLS tunnel must be in the same network segment. Optional.
A.5.6.5 Setting the Advanced Attributes of Ethernet Ports Setting attributes of IF_ETH ports A.5.7.1 Setting the General Attributes of the IF_ETH Port
Required. Set the major parameters as follows: Set Port Mode to Layer 3.
6-16
Issue 02 (2011-01-20)
6 Packet Features
Operation A.5.7.3 Setting Layer 3 Attributes of IF_ETH Ports
Description l In the case of used ports, set Enable Tunnel to Enabled. l Set Specify IP Address and IP Address according to planning information. The IP addresses of different ports on the NE cannot be in the same network segment, but the IP addresses of the ports at both ends of the MPLS tunnel must be in the same network segment. Optional.
Procedure for Configuring an MPLS Tunnel

Table 6-8 Procedure for configuring an MPLS tunnel Operation A.7.2.1 Setting Basic MPLS Attributes Description Required. Set the major parameters as follows: l Set LSR ID according to planning information and ensure that the value is unique on the entire network. l Set Start of Global Label Space according to planning information. On an MPLS-enabled network, global label spaces of NEs are recommended to overlap each other if possible. Configuring an MPLS tunnel A.7.2.2 Creating a Unidirectional MPLS Tunnel Required if you need to configure a unidirectional MPLS tunnel. Set this parameter according to network planning information. Required if you need to configure a bidirectional MPLS tunnel. Set this parameter according to network planning information. Required when the dynamic ARP protocol cannot obtain the next-hop MAC address. Set the parameters as follows: l ARP List IP Address: Specifies the IP address of the next-hop port. l ARP List MAC: Specifies the MAC address of the next-hop port.
A.7.2.3 Creating a Bidirectional MPLS Tunnel
A.7.1.1 Creating ARP Static Entries
Issue 02 (2011-01-20)
6-17
6 Packet Features
Procedure for Configuring Protection for MPLS Tunnels

Table 6-9 Procedure for configuring protection for MPLS tunnels Operation A.7.2.6 Setting MPLS OAM Parameters Description Required when you need to configure an MPLS APS protection group. l For a bidirectional MPLS tunnel, set the parameters as follows: Set OAM Status to Enabled for a tunnel where an OAM test needs to be performed. It is recommended that you set Detection Mode to Auto-Sensing. When you need to create an MPLS APS protection group, set Detection Packet Type to FFD and set Detection Packet Period(ms) to 3.3. This ensures that the switching time is less than 100 ms. Set SD Threshold and SF Threshold as required. l For the ingress node of a unidirectional MPLS tunnel, set the parameters as follows: Set OAM Status to Enabled for a tunnel where an OAM test needs to be performed. When you need to create an MPLS APS protection group, set Detection Packet Type to FFD and set Detection Packet Period(ms) to 3.3. This ensures that the switching time is less than 100 ms. Select the corresponding reverse tunnel. l For the egress node of a unidirectional MPLS tunnel, set the parameters as follows: Set OAM Status to Enabled for a tunnel where an OAM test needs to be performed. Set Detection Mode to Auto-Sensing. Select the corresponding reverse tunnel. Set SD Threshold and SF Threshold as required.
6-18
Issue 02 (2011-01-20)
6 Packet Features
Operation A.7.3.1 Creating an MPLS APS Protection Group
Description Required when you need to configure protection for services carried on an MPLS tunnel. l The protection tunnel must be created. l When creating an APS protection group, set Protocol Status to Disabled. Start the protocol only when the APS protection group is successfully created on nodes at both ends. l Set the parameters of the protection group according to network planning information.
Procedure for Configuring the QoS Policy

Table 6-10 Procedure for configuring the QoS policy Operation A.6.7.2 Modifying the Mapping Relationships for the DS Domain A.6.7.3 Changing the Ports Applied to a DS Domain and Their Trusted Packet Types A.6.7.1 Creating a DS Domain A.6.7.4 Creating a Port Policy A.6.7.7 Setting the Port That Uses the Port Policy Description Required when the default mapping relationships for the DS domain do not meet the actual requirements. Set the parameters according to the network planning information. For the default mapping relationships for the DS domain, see A.6.7.10 Querying the DS Domain of a Port. Required when the packet type trusted by a port is not the default trusted packet type (C-VLAN priority) applied to the DS domain. Set the parameters according to the network planning information.
Required when multiple DS domains are to be created. Set the parameters according to the network planning information. Required when you need to apply QoS policies other than DS and port shaping for a specific port. Set the parameters according to the network planning information. Required when a port policy is created. Set the relevant parameters according to the network planning information.
Issue 02 (2011-01-20)
6-19
6 Packet Features
Procedure for Verifying Created MPLS Tunnels

Table 6-11 Procedure for verifying created MPLS tunnels Operation A.7.2.6 Setting MPLS OAM Parameters Description Required. Before you create an MPLS APS protection group, you need to enable the MPLS OAM function to detect the tunnel status. When you need to check availability of MPLS tunnels, it is recommended that you set Detection Packet Type to CV. A.7.2.9 Querying LSP Running Status Required.

This section uses an example to describe how to plan and configure MPLS tunnels according to network conditions. For the configuration example of MPLS tunnels under MPLS APS protection, see Configuration Example (MPLS Tunnels with MPLS APS Protection) in the Configuration Guide. For the configuration example of MPLS tunnels under no protection, see Configuration Example (MPLS Tunnels with No Protection) in the Configuration Guide.

Related Tasks
A.7.2.1 Setting Basic MPLS Attributes A.5.6.1 Setting the General Attributes of Ethernet Ports A.5.6.4 Setting Layer 3 Attributes of Ethernet Ports A.5.7.1 Setting the General Attributes of the IF_ETH Port A.5.7.3 Setting Layer 3 Attributes of IF_ETH Ports A.7.2.2 Creating a Unidirectional MPLS Tunnel A.7.2.3 Creating a Bidirectional MPLS Tunnel A.7.2.4 Querying MPLS Tunnel Information A.7.2.5 Deleting MPLS Tunnels A.7.1.1 Creating ARP Static Entries A.7.1.2 Querying ARP Entries A.7.1.3 Converting Dynamic ARP Entries to Static ARP Entries A.7.1.4 Deleting Static ARP Entries A.7.1.5 Setting ARP Aging Time
6 Packet Features

When an exception is detected in the MPLS tunnel, an NE reports the specific alarm. l l For the alarms associated with MPLS OAM, see 6.2.10 Relevant Alarms and Events. For the alarms associated with MPLS APS, see 6.4.10 Relevant Alarms and Events.
6.1.11 FAQs
This section provides answers to the questions that are frequently raised when MPLS is used. Question: Does the OptiX RTN 980 support dynamic MPLS tunnels? Answer: The OptiX RTN 980 does not support dynamic MPLS tunnel.
6.2 MPLS OAM

This chapter describes the MPLS OAM feature. 6.2.1 Introduction This section provides the definition of MPLS OAM and describes its purpose. 6.2.2 Basic Concepts This section describes the basic concepts associated with MPLS OAM. 6.2.3 Specifications This section describes the specifications for MPLS OAM. 6.2.4 Reference Standards and Protocols This section describes the standards and protocols associated with MPLS OAM. 6.2.5 Availability This section describes the support required by the application of the MPLS OAM feature and its dependencies. 6.2.6 Principles In the MPLS OAM mechanism, after the ingress node sends CV or FFD packets periodically, the egress node checks the number and contents of the received CV or FFD packets within a detection period to check the connectivity of an LSP. 6.2.7 Configuration Procedure The OAM configurations for MPLS APS are different from those for LSP long-term monitoring. 6.2.8 Configuration Example This section uses an example to describe how to plan and configure MPLS OAM for long-term LSP monitoring according to network conditions. 6.2.9 Task Collection This section provides the hyperlinks of the operation tasks associated with the feature. 6.2.10 Relevant Alarms and Events When the MPLS OAM mechanism detects a fault in the LSP, an NE reports the specific alarm. 6.2.11 FAQs This section provides answers to the questions that are frequently raised when MPLS OAM is used.
6 Packet Features
6.2.1 Introduction
This section provides the definition of MPLS OAM and describes its purpose.
Definition
MPLS OAM can be used to detect and locate faults within an MPLS network and monitor the performance of MPLS networks. In this document, MPLS OAM refers to the OAM on the data plane, which checks a label switched path (LSP) on the data plane by means of specific MPLS OAM packets. MPLS OAM has the following features: l l MPLS OAM packets are processed only at the MPLS layer, without affecting other layers. MPLS OAM packets are transmitted on a service channel requiring low bandwidth, without affecting the services carried on the same channel.
Purpose
MPLS OAM can quickly check LSP connectivity. Based on the results of OAM checks, the equipment determines whether to trigger protection switching or not. As shown in Figure 6-10, in the MPLS OAM mechanism, the ingress node transmits detection packets and the egress node detects defects. This is how the LSP connectivity is checked. Figure 6-10 Typical application of MPLS OAM
Transmitting packets PSN
Detecting defects
Ingress
Transit
Transit
Egress
LSP Packet transmission equipment

This section describes the basic concepts associated with MPLS OAM.
6-22
Issue 02 (2011-01-20)
6 Packet Features
6.2.2.1 CV/FFD To check defects of an LSP continuously, the ingress node transmits connectivity verification (CV) or fast failure detection (FFD) packets periodically on the checked LSP. Both CV and FFD packets can be used to check and diagnose all types of defects for an LSP. The transmit period of CV packets is longer and cannot be adjusted, but the transmit period of FFD packets is shorter and can be adjusted. 6.2.2.2 LSP Defect Type During any given detection period, the egress node will report an LSP defect if receiving an expected number of CV/FFD packets or CV/FFD packets with unexpected contents. 6.2.2.3 BDI After checking a defect, the egress node generates a backward defect indication (BDI) packet to inform the ingress node of the LSP defect. 6.2.2.4 FDI A node that detects a defect generates a forward defect indication (FDI) packet to suppress other LSP layer alarms.
6.2.2.1 CV/FFD
To check defects of an LSP continuously, the ingress node transmits connectivity verification (CV) or fast failure detection (FFD) packets periodically on the checked LSP. Both CV and FFD packets can be used to check and diagnose all types of defects for an LSP. The transmit period of CV packets is longer and cannot be adjusted, but the transmit period of FFD packets is shorter and can be adjusted.
CV
Since the transmit period of CV packets is longer and cannot be adjusted, CV packets are applicable to connectivity check for an LSP that does not have a stringent requirement for defect detection. The ingress node sends CV packets at an interval of 1s, and the egress node checks the number and contents of received CV packets at an interval of 3s. The ingress node pushes an LSP label to a CV packet before transmitting the packet. Figure 6-11 shows the format of a CV packet.
Issue 02 (2011-01-20)
6-23
6 Packet Features
Figure 6-11 Format of a CV packet

0 Label: 14 (OAM alert label) Function type (0x01) 7 TTSI (20 octets) 19 22 23 EXP S Reserved (all 0x00) TTL: 1 31 bit
Padding (all 0x00) (18 octets)
BIP 16 (2 octets)
OAM packet header
The fields of a CV packet are as follows: l l l l l Label: The value of the field is 14 and indicates an OAM packet. Time to Live (TTL): The value of the field is set to 1, to ensure that the MPLS OAM packet is not transmitted beyond the sink end of the monitored LSP. Function type: The value of the field is set to 0x01, indicating that the OAM packet type is CV. Trail termination source identifier (TTSI): TTSI consists of the LSR ID and LSP ID of the ingress node. It is used to uniquely identify an LSP on a network. 16-bit interleaved parity (BIP 16): If a CV packet contains an incorrect BIP 16, the receiver discards the packet. When CV packets are continuously discarded due to incorrect BIP 16s, the equipment will notify the NMS. Reserved: The reserved field is reserved for future use and is set to all 0s. Padding: The field is for padding bytes and is set to all 0s.
l l
FFD
Since the transmit period of FFD packets is shorter and can be adjusted, FFD packets are applicable to connectivity check for an LSP that has a stringent requirement for defect detection. The ingress node transmits FFD packets periodically, and the egress node checks the number and contents of received FFD packets at an interval of three transmit periods. The ingress node pushes an LSP label to an FFD packet before transmitting the packet. Figure 6-12 shows the format of an FFD packet.
6-24
Issue 02 (2011-01-20)
6 Packet Features
Figure 6-12 Format of an FFD packet

0 Label: 14 (OAM alert label) Function type (0x07) 7 TTSI (20 octets) 19 22 23 EXP S Reserved (all 0x00) TTL: 1 31 bit
Frequency (1 octet) Padding (all 0x00) (17 octets)
BIP 16 (2 octets)
OAM packet header
Table 6-12 provides the differences between an FFD packet and a CV packet. Table 6-12 Format differences between an FFD packet and a CV packet Field Function type CV Packet The field is set to 0x01, indicating that the OAM packet type is CV. None. FFD Packet The field is set to 0x07, indicating that the OAM packet type is FFD. The frequency field indicates that the FFD packet can support several transmit intervals.
Frequency
6.2.2.2 LSP Defect Type

During any given detection period, the egress node will report an LSP defect if receiving an expected number of CV/FFD packets or CV/FFD packets with unexpected contents.
Defect Type
During any given detection period, the egress node should receive two to four CV or FFD packets with the expected TTSI and should not receive CV/FFD packets with the unexpected TTSI. If the egress node receives an unexpected number of CV/FFD packets or CV/FFD packets with unexpected contents, it reports an LSP defect. Table 6-13 provides the defect types supported by the OptiX RTN 980.
6 Packet Features
Table 6-13 LSP defect types Defect Type NonMPLS layer defect MPLS layer defect dServer Valu e 0x010 1 Meaning Any server layer defect arising from below the MPLS layer network Loss of connectivity verification packets Trigger Condition The defect is reported by the server layer network for MPLS OAM. The defect is generated due to missing FDI packets and missing CV or FFD packets with the expected TTSI within a detection period. The defect is generated due to receiving CV or FFD packets with unexpected TTSI and missing CV or FFD packets with the expected TTSI within a detection period. The defect is generated due to receiving CV or FFD packets with unexpected TSSI and with excepted TTSI within a detection period. The defect is generated due to receiving five or more CV or FFD packets with the expected TTSI within a detection period. For example, the defect is generated when the type and period of received CV or FFD packets do not match the expected values within a detection period.
dLOCV
0x020 1
dTTSI_ Mismatc h
0x020 2
TTSI mismatch defect
dTTSI_ Mismer ge
0x020 3
TTSI mismerge defect
dExcess
0x020 4
Defect of CV or FFD packets with an excessive rate
Others
dUnkno wn
0x02F F
Undefined or unknown defect
NOTE
The OptiX RTN 980 allows setting SD and SF thresholds. When the packet loss ratio of OAM packets exceeds the preset thresholds, the specific alarm is reported. If all the preceding trigger conditions are met, the MPLS layer defects are reported in descending order of priorities: dTTSI_Mismatch > dTTSI_Mismerge > dLOCV > dExcess.
Detection Mechanism
The egress node checks packets in two modes: adaptive mode and manual mode.
6-26
Issue 02 (2011-01-20)
6 Packet Features
Adaptive mode: The detection period is once every three transmit periods of received CV or FFD packets. When receiving the first CV or FFD packet, the egress node records the type and transmit period of the packet and starts to check connectivity. Manual mode: The detection period is once every three periods that are manually set.
6.2.2.3 BDI
After checking a defect, the egress node generates a backward defect indication (BDI) packet to inform the ingress node of the LSP defect.
Format of a BDI Packet

The egress node pushes an LSP label to a BDI packet before transmitting the packet. Figure 6-13 shows the format of a BDI packet. Figure 6-13 Format of a BDI packet
0 Label: 14 (OAM alert label) Function type (0x03) Reserved (all 0x00) 19 22 EXP S 23 TTL: 1 31 bit
Defect type (2 octets)
TTSI (20 octets)
Defect location (4 octets)
BIP 16 (2 octets) OAM packet header
The fields of a BDI packet are as follows: l l l l Label: The value of the field is 14 and indicates an OAM packet. Time to Live (TTL): The value of the field is set to 1, to ensure that the MPLS OAM packet is not transmitted beyond the sink end of the monitored LSP. Function type: The value of the field is set to 0x03, indicating that the OAM packet type is BDI. Defect type and defect location: The defect type field indicates the type of the generated defect. For details, see 6.2.2.2 LSP Defect Type. The defect location field indicates the LSR ID of the node that generates the defect.
6 Packet Features
Trail termination source identifier (TTSI): TTSI consists of the LSR ID and LSP ID of the ingress node of an LSP. In the case of the OptiX RTN 980, TTSI is not required in the BDI packet. Therefore, the TTSI bits are set to all 0s. 16-bit interleaved parity (BIP 16): If a BDI packet contains an incorrect BIP 16, the receiver discards the packet. When BDI packets are continuously discarded due to incorrect BIP 16s, the equipment will notify the NMS. Reserved: The reserved field is reserved for future use and is set to all 0s. Padding: The field is for padding bytes and is set to all 0s.
l l
Typical Application of a BDI Packet

Figure 6-14 shows the typical application of a BDI packet. When checking an LSP defect, the egress node informs the ingress node of the LSP defect by generating a BDI packet and transmitting the BDI packet over the preset reverse LSP. Figure 6-14 Typical application of the BDI packet
Returning a BDI
Ingress Forward LSP Reverse LSP
Transit
Egress
6.2.2.4 FDI
A node that detects a defect generates a forward defect indication (FDI) packet to suppress other LSP layer alarms.
Format of an FDI Packet Format

The node that detects a defect pushes an LSP label to an FDI packet before transmitting it. Figure 6-15 shows the format of an FDI packet.
6-28
Issue 02 (2011-01-20)
6 Packet Features
Figure 6-15 Format of an FDI packet

0 Label: 14 (OAM alert label) Function type (0x02) 7 TTSI (20 octets) Reserved (all 0x00) 19 22 EXP S 23 TTL: 1 31 bit
Defect type (2 octets)
Defect location (4 octets)
BIP 16 (2 octets) OAM packet header
Table 6-14 provides the differences between an FFD packet and a CV packet. Table 6-14 Format differences between an FDI packet and a BDI packet Field Function type BDI Packet The field is set to 0x03, indicating that the OAM packet type is BDI. FDI Packet The field is set to 0x02, indicating that the OAM packet type is FDI.
Typical Application of an FDI Packet

Figure 6-16 shows an application of the FDI packet on the OptiX RTN 980. In this application scenario, FDI enables more rapid fault locating and protection switching. After the FDI function is enabled for the transit node, the transit node inserts an FDI packet on all LSPs that travel through the transit node when a fault occurs on the link between the ingress and transit nodes. On reception of the FDI packet, the egress node reports an alarm. In addition, if MPLS APS is configured correctly, protection switching is directly triggered without waiting for the egress node to detect the LSP defect within a detection period.
Issue 02 (2011-01-20)
6-29
6 Packet Features
Figure 6-16 Typical application of the FDI packet

Inserting an FDI
Ingress LSP
Transit
Egress
This section describes the specifications for MPLS OAM. Table 6-15 lists the specifications for MPLS OAM. Table 6-15 Specifications for MPLS OAM Item Maximum number of MPLS OAM resources Specifications 64
NOTE MPLS OAM and PW OAM share 64 OAM resources.
Type of OAM packet
CV FFD
Transmission frequency of OAM packets
CV FFD
1s l 3.3 ms l 10 ms l 20 ms l 50 ms l 100 ms l 200 ms l 500 ms
OAM detection mode
l Adaptive mode l Manual mode
6-30
Issue 02 (2011-01-20)
6 Packet Features
Item LSP defect type
Specifications l dLOCV l dTTSI_Mismatch l dTTSI_Mismerge l dExcess l dUnknown l dServer
OAM packet loss threshold BDI
SD and SF thresholds Supports the reverse tunnel so that the BDI packet can be returned after the LSP defect is detected. Supported
FDI defect information enabled

This section describes the standards and protocols associated with MPLS OAM. The following standards and protocols are associated with MPLS OAM: l l ITU-T Y.1710: Requirements for Operation & Maintenance functionality for MPLS networks ITU-T Y.1711: Operation & Maintenance mechanism for MPLS networks
6.2.5 Availability
This section describes the support required by the application of the MPLS OAM feature and its dependencies.

Table 6-16 Hardware and version support Feature MPLS OAM Applicable Board CSHN IFU2 IFX2 ISU2 Applicable Hardware Version All the versions All the versions All the versions All the versions Applicable Product Version V100R003C00 and later V100R003C00 and later V100R003C00 and later V100R003C00 and later
6-31
Issue 02 (2011-01-20)
6 Packet Features
Feature
The dependencies between the MPLS OAM feature and other features are as follows: l l l MPLS OAM is the prerequisite and basis for MPLS APS. MPLS OAM can co-exist with other OAM mechanisms. MPLS OAM and PW OAM share 64 OAM resources.
6.2.6 Principles
In the MPLS OAM mechanism, after the ingress node sends CV or FFD packets periodically, the egress node checks the number and contents of the received CV or FFD packets within a detection period to check the connectivity of an LSP. Figure 6-17 shows how the continuity of an LSP (that is, LSP1) is checked. LSP1 is the check object, and LSP2 is the reverse LSP that transmits the BDI packet. Figure 6-17 Checking connectivity in MPLS OAM
Ingress
Transit
Egress
CV/FFD BDI Packet transmission direction
LSP1 LSP2 Packet transmission equipment
The process for checking the connectivity is as follows:

6 Packet Features
1. 2. 3.
After the OAM function is enabled for the ingress and egress nodes, the ingress node transmits CV or FFD packets periodically and the egress node waits to receive packets. CV or FFD packets are transparently transmitted on the transit node. The packets arrive at the egress node along LSP1. The egress node checks the information about the received packets (such as packet type, frequency, and TTSI) to determine the correctness of the packets and also checks the number of received packets within a detection period. The operations help to monitor the connectivity of an LSP. If a defect is detected, the egress node reports an alarm according to the defect type. The egress node also transmits a BDI packet with the defect information to the ingress node along LSP2 so that the ingress node is timely informed of the defect status.
4.

The OAM configurations for MPLS APS are different from those for LSP long-term monitoring.
NOTE
This section describes only the OAM configurations for LSP long-term monitoring. The OAM parameters for MPLS APS are configured during the configuration of MPLS APS.
Table 6-17 Flow for configuring MPLS OAM Step 1 Operation A.7.2.6 Setting MPLS OAM Parameters Description Required. Set the major parameters as follows: l Set OAM Status of the required LSP to Enabled. l Set Detection Packet Type of the ingress node of the required LSP to CV. l Set Detection Mode of the node of the required LSP to Auto-Sensing.

This section uses an example to describe how to plan and configure MPLS OAM for long-term LSP monitoring according to network conditions. 6.2.8.1 Network Diagram This section describes the networking information about the NEs. 6.2.8.2 Service Planning The service planning information contains all the parameters required for configuring the NE data. 6.2.8.3 Configuration Process This section describes the process of data configuration.

This section describes the networking information about the NEs.
6 Packet Features
On a PSN shown in Figure 6-18, CV packets in the MPLS OAM mechanism are used to continuously test LSP connectivity in order to avoid a fault in the LSP between NE1 and NE3. Figure 6-18 Network diagram of the MPLS OAM function
NE1
NE2
NE3
LSP Bidirectional Tunnel (ID=1501) Ingress Egress

The service planning information contains all the parameters required for configuring the NE data. In this example, the planning information about MPLS OAM for NE1 and NE3 is as follows. l CV packets are used for a connectivity check, because only LSP connectivity needs to be continuously tested and the connectivity check does not have a requirement for the packet transmission interval. The auto-sensing mode is used for a connectivity check.

Procedure
Step 1 See A.7.2.6 Setting MPLS OAM Parameters, and configure MPLS OAM parameters. The values for the required parameters are provided as follows. Parameter Value NE1 Bidirectional tunnel (ID = 1501) OAM Status Detection Mode
6-34
NE3 Bidirectional tunnel (ID = 1501) Enabled Auto-Sensing

Issue 02 (2011-01-20)
Enabled Auto-Sensing
6 Packet Features
Parameter
Value NE1 Bidirectional tunnel (ID = 1501) NE3 Bidirectional tunnel (ID = 1501) CV 0 0
Detection Packet Type SD Threshold SF Threshold
CV 0 0
----End

Related Tasks
A.7.2.6 Setting MPLS OAM Parameters A.7.2.7 Enabling/Disabling FDI A.7.2.6 Setting MPLS OAM Parameters A.7.2.7 Enabling/Disabling FDI A.7.2.8 Starting/Stopping CV/FFD Detection for MPLS Tunnels A.7.2.9 Querying LSP Running Status A.7.2.10 Clearing OAM Configuration Data for MPLS Tunnels

When the MPLS OAM mechanism detects a fault in the LSP, an NE reports the specific alarm.
Relevant Alarms
l MPLS_TUNNEL_BDI The MPLS_TUNNEL_BDI alarm indicates that a defect occurs in the reverse direction of an LSP. If an Ethernet port receives a BDI packet, the alarm is reported to indicate a default in the forward direction of an LSP. l MPLS_TUNNEL_Excess The MPLS_TUNNEL_Excess alarm indicates that excessive TTSIs are received. This alarm is reported if an Ethernet port receives five or more CV or FFD packets with expected TTSI within a detection period. l MPLS_TUNNEL_FDI The MPLS_TUNNEL_FDI alarm indicates that a defect occurs in the forward direction of an LSP. If an Ethernet port receives a FDI packet, the alarm is reported to indicate that a fault occurs in the LSP at the physical layer of the upstream equipment. l
Issue 02 (2011-01-20)
MPLS_TUNNEL_LOCV
6 Packet Features
The MPLS_TUNNEL_LOCV alarm indicates that a continuity check packet is lost. This alarm is reported if an Ethernet port fails to receive CV or FFD packets with expected TTSI within a detection period. l MPLS_TUNNEL_MISMATCH The MPLS_TUNNEL_MISMATCH alarm indicates that the TTSI is not a match. This alarm is reported if an Ethernet port receives CV or FFD packets with unexpected TTSI but fails to receive CV or FFD packets with expected TTSI within a detection period. l MPLS_TUNNEL_MISMERGE The MPLS_TUNNEL_MISMERGE alarm indicates that the TTSIs are incorrectly merged. This alarm is reported if an Ethernet port receives CV or FFD packets with unexpected TTSI, and CV packets with expected TTSI within a detection period. l MPLS_TUNNEL_OAMFAIL The MPLS_TUNNEL_OAMFAIL alarm indicates that at the two ends of the LSP, the OAM protocol negotiation fails. l MPLS_TUNNEL_SD The MPLS_TUNNEL_SD alarm indicates that the signal in the LSP degrades. This alarm is reported when the loss ratio of the continuity check packets is higher than the SD threshold but is lower than the SF threshold. l MPLS_TUNNEL_SF The MPLS_TUNNEL_SF alarm indicates that the signal in the LSP severely degrades. This alarm is reported when the loss ratio of the continuity check packets is higher than the SF threshold. l MPLS_TUNNEL_UNKNOWN The MPLS_TUNNEL_UNKNOWN alarm indicates that a certain unknown defect exists in the LSP. This alarm is reported if an Ethernet port receives continuity check packets with expected TTSI but with different types or transmission periods within a detection period.
Relevant Events
None.
6.2.11 FAQs
This section provides answers to the questions that are frequently raised when MPLS OAM is used. Question: What are the differences between MPLS OAM and LSP ping/traceroute? Answer: Table 6-18 lists the main differences between MPLS OAM and LSP ping/traceroute. Table 6-18 Differences between MPLS OAM and LSP ping/traceroute Item Implementation principle MPLS OAM The source end transmits CV/ FFD packets, and the sink end detects a defect. LSP Ping/Traceroute MPLS echo request and MPLS echo reply packets are exchanged.
Issue 02 (2011-01-20)
6-36
6 Packet Features
Item Typical application
MPLS OAM Testing unidirectional continuity
LSP Ping/Traceroute l Testing bidirectional continuity l Locating a fault point
Prerequisite
MPLS OAM is configured at both ends of a link.
l LSP ping/Traceroute needs to be configured only at the ingress node. l If LSP ping/traceroute uses the IPv4 UDP response mode, all the nodes on the LSP must support DCN communication by means of IP protocols.
6.3 LSP Ping/Traceroute

This chapter describes the LSP ping and LSP traceroute features. 6.3.1 Introduction This section provides the definitions of LSP ping and LSP traceroute and describes their purposes. 6.3.2 Specifications This section describes the specifications for LSP ping/traceroute. 6.3.3 Reference Standards and Protocols This section provides the standards and protocols associated with LSP ping/traceroute. 6.3.4 Availability This section describes the support required by the application of the LSP ping/traceroute feature and its dependencies. 6.3.5 Principles The LSP ping/traceroute operations are implemented with the exchange of MPLS echo request and echo reply packets. 6.3.6 Configuration Procedure The configuration procedure of LSP ping/traceroute contains only one configuration task. 6.3.7 Configuration Example This section uses an example to describe how to plan and configure LSP ping/traceroute according to network conditions. 6.3.8 Task Collection This section provides the hyperlinks of the operation tasks associated with the feature. 6.3.9 Relevant Alarms and Events There is no alarm or event associated with the LSP ping/traceroute feature. 6.3.10 FAQs
6 Packet Features
This section provides answers to the questions that are frequently asked when LSP ping/ traceroute is used.
6.3.1 Introduction
This section provides the definitions of LSP ping and LSP traceroute and describes their purposes.
Definition
LSP ping and LSP traceroute are used to check and locate faults within an MPLS network and monitor the MPLS network performance. LSP ping/traceroute is similar to IP ping/traceroute regarding the principles.
Purpose
LSP ping allows connectivity check of forward and reverse LSPs. As shown in Figure 6-19, in the LSP ping mechanism, the ingress node sends a request packet and the egress node returns a reply packet to check the connectivity of an LSP. Figure 6-19 Typical application of LSP ping
Ingress Transit Transit Egress
NE1 Request Reply NE2 NE N-1 NE N
Forward LSP Reverse LSP Packet transmission equipment
In addition to connectivity check of forward and reverse LSPs, LSP traceroute can provide the specific routing information about an LSP or helps to locate faults of an LSP. As shown in Figure 6-20, in the LSP traceroute mechanism, the ingress node sends a request packet, and other nodes on the LSP take turns to return a reply packet. The connectivity of an LSP is checked section by section, helping you learn about the specific routing information and locate a fault.
6-38
Issue 02 (2011-01-20)
6 Packet Features
Figure 6-20 Typical application of LSP traceroute

NE1 Request Reply NE2 NE N-1 NE N
Request Reply Request Reply
LSP ping/traceroute has the following advantages: l l Compared with IP ping/traceroute, LSP ping/traceroute can locate an LSP fault that IP ping/ traceroute cannot locate, such as a label mismatch or a hardware error. MPLS OAM enables unidirectional connectivity check of an LSP by means of CV or FFD packets, but LSP ping/traceroute enables bidirectional connectivity check of an LSP. Moreover, LSP traceroute offers the fault locating feature. LSP ping/traceroute is also used to check packet loss ratio, latency, and jitter.
This section describes the specifications for LSP ping/traceroute. Table 6-19 lists the specifications for LSP ping/traceroute. Table 6-19 Specifications for LSP ping/traceroute Item LSP ping Setting the number of transmitted MPLS echo request packets Length of transmitted MPLS echo request packets
Issue 02 (2011-01-20)
64 to 1400
6-39
6 Packet Features
Item Interval for transmitting MPLS echo request packets Setting the EXP value of MPLS label of transmitted MPLS echo request packets Setting the TTL value of MPLS label of transmitted MPLS echo request packets Response mode
Specifications 10 ms to 10000 ms Supported
Supported
l No response l Application control channel (supported only by a bidirectional tunnel) l The response is provided by sending the IPv4 UDP packet that encapsulates the MPLS echo reply.
NOTE l "No response" indicates that the destination node involved in an LSP ping operation does not return a response packet, but directly reports the event. l "Application control channel" indicates that a response packet is returned through a reverse channel.
Wait-to-response timeout time Response event reported by the source end Response timeout event reported by the source end Statistics event reported by the source end LSP traceroute Length of transmitted MPLS echo request packets Setting the EXP value of MPLS label of transmitted MPLS echo request packets Setting the TTL value of MPLS label of transmitted MPLS echo request packets
10 ms to 60000 ms Supported Supported Supported 84 to 1400 Supported
Supported
6-40
Issue 02 (2011-01-20)
6 Packet Features
Item Response mode
Specifications l No response l Application control channel (supported only by a bidirectional tunnel) l The response is provided by sending the IPv4 UDP packet that encapsulates the MPLS echo reply.
NOTE l "No response" indicates that the destination node involved in an LSP traceroute operation does not return a response packet, but directly reports the event. l "Application control channel" indicates that a response packet is returned through a reverse channel.
Wait-to-response timeout time Response event reported by the source end Response timeout event reported by the source end End event reported by the source end
10 ms to 60000 ms Supported Supported Supported

This section provides the standards and protocols associated with LSP ping/traceroute. The following standard is associated with LSP ping/traceroute: IETF RFC 4379: Detecting Multi-Protocol Label Switched (MPLS) Data Plane Failures
6.3.4 Availability
This section describes the support required by the application of the LSP ping/traceroute feature and its dependencies.

Table 6-20 Hardware and version support Feature LSP ping/traceroute Applicable Board CSHN Applicable Hardware Version All the versions Applicable Product Version V100R003C00 and later
6-41
Issue 02 (2011-01-20)
6 Packet Features
Feature
Applicable Board IFU2 IFX2 ISU2 ISX2 EM6T EM6F
Applicable Hardware Version All the versions All the versions All the versions All the versions All the versions All the versions
Applicable Product Version V100R003C00 and later V100R003C00 and later V100R003C00 and later V100R003C00 and later V100R003C00 and later V100R003C00 and later
The dependencies between the LSP ping/traceroute feature and other features are as follows: l l If LSP ping/traceroute uses the IPv4 UDP response mode, all the nodes on the LSP must support DCN communication through IP protocols. LSP ping/traceroute operations can be performed on the Ingress node of an MPLS tunnel only.
6.3.5 Principles
The LSP ping/traceroute operations are implemented with the exchange of MPLS echo request and echo reply packets. 6.3.5.1 LSP Ping In the LSP ping mechanism, the ingress node sends an MPLS echo request packet and the egress returns an MPLS echo reply packet to check the connectivity of an LSP. 6.3.5.2 LSP Traceroute In the LSP traceroute mechanism, the ingress node sends MPLS echo request packets and other nodes take turns to return an MPLS echo reply packet in response to the received request packet. The connectivity of an LSP is checked section by section.
6.3.5.1 LSP Ping

In the LSP ping mechanism, the ingress node sends an MPLS echo request packet and the egress returns an MPLS echo reply packet to check the connectivity of an LSP. The MPLS echo request and MPLS echo reply packets are sent in User Datagram Protocol (UDP) format. The MPLS echo request packet carries the information about the timestamp and Time to Live (TTL).
6 Packet Features
l l
The timestamp contains the time when the packet is sent and received. Timestamp tells the LSP latency. The TTL value in the IP packet header is set to 1, to ensure that the test packet is not transmitted beyond the sink end of the monitored LSP.
As shown in Figure 6-21, LSP ping operations are performed to check the connectivity of the forward and reverse LSPs. Figure 6-21 Checking connectivity in LSP ping
NE1 MPLS echo request MPLS echo reply Forward LSP Reverse LSP Packet transmission equipment NE2 NE N-1 NE N
The process for checking the connectivity is as follows: 1. The ingress node structures the MPLS echo request packet in the UDP packet format based on LSP ping parameters, and pushes the LSP label. Then, the ingress node transmits the packet based on the preset packet quantity and transmit interval. The packet carries the transmission timestamp. Each transit node forwards the MPLS echo request packet in the same manner as it forwards common MPLS packet.
NOTE
2.
If a transit node fails to forward the MPLS echo request packet, it returns a reply message containing an error code and notifies the NMS.
3.
After receiving the MPLS echo request packet, the egress node structures the MPLS echo reply packet, and pushes the reception timestamp. Then, the egress node transmits the MPLS echo reply packet through the preset reverse LSP.
NOTE
If the IPv4 UDP response mode is used, the egress and transit nodes address the ingress node based on the IP routing table of DCN to transmit the MPLS echo reply packet.
4.
After the ingress node successfully receives the MPLS echo reply packet returned from the egress node, the request packet is no longer transmitted and the bidirectional connectivity check is completed. In addition, the ingress node determines the packet loss ratio and latency based on the information carried by the reply packet and notifies the NMS.
Issue 02 (2011-01-20)
6-43
6 Packet Features
6.3.5.2 LSP Traceroute

In the LSP traceroute mechanism, the ingress node sends MPLS echo request packets and other nodes take turns to return an MPLS echo reply packet in response to the received request packet. The connectivity of an LSP is checked section by section. The MPLS echo request and MPLS echo reply packets are sent in User Datagram Protocol (UDP) format. The MPLS echo request packet carries the information about the timestamp, Time to Live (TTL), and next hop. l l The timestamp contains the time when the packet is sent and received. Timestamp tells the LSP latency. The TTL value in the IP packet header is set to 1, to ensure that the test packet is not transmitted beyond the sink end of the monitored LSP.
As shown in Figure 6-22, LSP traceroute operations are performed to check the connectivity of the forward and reverse LSPs. Figure 6-22 Checking connectivity in LSP traceroute
...
NE1 TTL=1 NE2 MPLS echo request MPLS echo reply NE N-1 NE N
. . .
TTL=N-2
. . .
MPLS echo request MPLS echo reply
TTL=N-1
The process for checking the connectivity is as follows: 1. The ingress node structures the MPLS echo request packet in the UDP packet format based on LSP traceroute parameters, and pushes the LSP label. Then, the ingress node transmits the packet based on the preset packet quantity and transmit interval. The packets carries the transmission timestamp. The destination node of the MPLS echo request packet is determined by the TTL value in the LSP label. The TTL value N indicates the destination node of the request packet is the N+1 node along the LSP. When the first request packet is
6-44
6 Packet Features
transmitted, the TTL value of the LSP label is set to 1, indicating that the next hop (a transit or egress node) of the ingress node is the destination node of the request packet. 2. If the destination node of the request packet is a transit node, after receiving the MPLS echo request packet, the transit node finds the information about the next hop of the LSP, structures the MPLS echo reply packet, and pushes the reception timestamp. Then, the transit node transmits the MPLS echo reply packet through the preset reverse LSP. On reception of the MPLS echo reply packet returned from the transit node each time, the ingress node adds 1 to the TTL value in the LSP label and retransmits the MPLS echo request packet. After receiving the MPLS echo request packet, the egress node structures the MPLS echo reply packet and pushes the reception timestamp. Then, the egress node transmits the MPLS echo reply packet through the preset reverse LSP.
NOTE
3.
4.
5.
After the ingress node successfully receives the MPLS echo reply packet returned from the egress node, the request packet is no longer transmitted and the bidirectional connectivity check is completed.
NOTE
On reception of the MPLS echo reply packet returned from an LSP node, the ingress node reports information about the node type, next hop, LSP status, and latency to the NMS. In this manner, a fault on the LSP can be located.

The configuration procedure of LSP ping/traceroute contains only one configuration task. Table 6-21 Flow for configuring LSP ping Step 1 Operation A.7.2.11 Performing an LSP Ping Test Description Required. Regarding a MPLS tunnel, perform the operation on the required LSP on the ingress node. Set the major parameters as follows: l Set Packet Count to the default value. l Set Packet Length and EXP Value as required. l Set Response Mode based on the support capacity of the egress node: If the egress node supports the reverse channel response, set Response Mode to Application Control Channel. If the egress node does not support the reverse channel response but supports DCN channel response by using IP protocols, set Response Mode to IPv4 UDP Response.
Issue 02 (2011-01-20)
6-45
6 Packet Features
Table 6-22 Flow for configuring LSP traceroute Step 1 Operation A.7.2.12 Performing an LSP Traceroute Test Description Required. Regarding a MPLS tunnel, perform the operation on the required LSP on the ingress node. Set the major parameters as follows: l Set Packet Length and EXP Value as required. l Set Response Mode based on the support capacity of the egress node: If the egress node supports the reverse channel response, set Response Mode to Application Control Channel. If the egress node does not support the reverse channel response but supports DCN channel response by using IP protocols, set Response Mode to IPv4 UDP Response.

This section uses an example to describe how to plan and configure LSP ping/traceroute according to network conditions.
NOTE
This example describes only the application of LSP ping. The application of LSP traceroute is similar, and therefore is not described.
6.3.7.1 Network Diagram This section describes the networking information about the NEs. 6.3.7.2 Service Planning The service planning information contains all the parameters required for configuring the NE data. 6.3.7.3 Configuration Process This section describes the process of data configuration.

This section describes the networking information about the NEs. On a PSN as shown in Figure 6-23, LSP ping is used to test the connectivity of a bidirectional tunnel (ID = 1501) between NE1 and NE3.
6-46
Issue 02 (2011-01-20)
6 Packet Features
Figure 6-23 Network diagram of the LSP ping function
NE1
NE2
NE3
LSP Bidirectional Tunnel (ID=1501) Ingress
Egress

The service planning information contains all the parameters required for configuring the NE data. In this example, the planning information about LSP ping for NE1 and NE3 is as follows. l l Only LSP ping is used, because the LSP requires a connectivity check but not fault locating. Set EXP Value to 7 to prevent packets from being affected by QoS operations, because the MPLS tunnel in this example does not specify its MPLS EXP value, and tests only the LSP connectivity. This example uses 64-byte packets (short packets) and 1400-byte packets (long packets), to respectively test the connectivity of the MPLS tunnel. As an OptiX RTN 980, NE3 supports a reverse tunnel responding to LSP ping/traceroute requests. Therefore, on NE1 that initiates a test, set Response Mode to Application Control Channel.
l l

Procedure
Step 1 See A.7.2.11 Performing an LSP Ping Test, and start an LSP ping packet detection on NE1. The values for the required parameters are provided as follows. Parameter Value Short Packet Test Packet Count EXP Value TTL
Issue 02 (2011-01-20)
Long Packet Test 3 7 255

6-47
3 7 255
6 Packet Features
Parameter
Value Short Packet Test Long Packet Test 100 1400 300 Application Control Channel
Transmit Interval(10ms) Packet Length Wait-to-Response Timeout Time(10ms) Response Mode
100 64 300 Application Control Channel
----End

Related Tasks
A.7.2.11 Performing an LSP Ping Test A.7.2.12 Performing an LSP Traceroute Test

There is no alarm or event associated with the LSP ping/traceroute feature.
6.3.10 FAQs
This section provides answers to the questions that are frequently asked when LSP ping/ traceroute is used. Question: What are the differences between MPLS OAM and LSP ping/traceroute? Answer: Table 6-23 lists the main differences between MPLS OAM and LSP ping/traceroute. Table 6-23 Differences between MPLS OAM and LSP ping/traceroute Item Implementation principle MPLS OAM The source end transmits CV/ FFD packets, and the sink end detects a defect. Testing unidirectional continuity LSP Ping/Traceroute MPLS echo request and MPLS echo reply packets are exchanged. l Testing bidirectional continuity l Locating a fault point
Typical application
6-48
Issue 02 (2011-01-20)
6 Packet Features
Item Prerequisite
MPLS OAM MPLS OAM is configured at both ends of a link.
LSP Ping/Traceroute l LSP ping/Traceroute needs to be configured only at the ingress node. l If LSP ping/traceroute uses the IPv4 UDP response mode, all the nodes on the LSP must support DCN communication by means of IP protocols.
Question: Why should the ping or traceroute operation be performed for only one LSP at a time? Answer: If the ping or traceroute operation is performed for multiple LSPs at a time, the CPU processing capability may be insufficient. Therefore, the packets may fail to be transmitted or received within the specified time interval. In this case, the ping or traceroute operation times out. Question: RTN 900 V100R003 NEs and RTN 900 V100R001 NEs both support IPv4 UDP response. But why do PW ping/traceroute operations that are performed between an RTN 900 V100R003 NE and an RTN 900 V100R001 NE fail when in this response mode? Answer: Regarding an RTN 900 V100R001 NE, IPv4 UDP response means that the response NE addresses the source NE by using the ISIS protocol. Regarding an RTN 900 V100R003 NE, IPv4 UDP response means that the response NE addresses the source NE by using the IP over DCC protocol. Therefore the PW ping/traceroute operations will fail since the two response mechanisms are totally different.
NOTE
However, thanks to the same response mechanisms, the PW ping/traceroute operations performed between an MSTP+ NE and an RTN 900 V100R003 NE, and those performed between a PTN NE and an RTN 900 V100R001 will succeed. This is, the PW ping/traceroute operations performed between an RTN 900 V100R003 NE and a PTN NE will also fail.
6.4 MPLS APS

This chapter describes the MPLS automatic protection switching (APS) feature. 6.4.1 Introduction This section provides the definition of MPLS APS and describes its purpose. 6.4.2 Basic Concepts This section describes the basic concepts associated with MPLS APS. 6.4.3 Specifications This section describes the specifications for MPLS APS. 6.4.4 Reference Standards and Protocols This section describes the standards and protocols associated with MPLS APS.
6 Packet Features
6.4.5 Availability This section describes the support required by the application of the MPLS APS feature and its dependencies. 6.4.6 Principles MPLS APS uses the MPLS OAM mechanism to detect faults in tunnels, and the ingress and egress nodes exchange APS protocol packets for protection switching. 6.4.7 Configuration Procedure When MPLS APS is configured, MPLS OAM is configured simultaneously. 6.4.8 Configuration Example This section uses an example to describe how to plan and configure MPLS APS according to network conditions. 6.4.9 Task Collection This section provides the hyperlinks of the operation tasks associated with the feature. 6.4.10 Relevant Alarms and Events When detecting an exception by performing MPLS APS operations, an NE reports the specific alarm. 6.4.11 FAQs This section provides answers to the questions that are frequently raised when MPLS APS is used.
6.4.1 Introduction
This section provides the definition of MPLS APS and describes its purpose.
Definition
MPLS APS is a function that protects MPLS tunnels based on the APS protocol. With this function, when the working tunnel is faulty, the service can be switched to the preconfigured protection tunnel. The MPLS APS function supported by the OptiX RTN 980 has the following features: l l l l The MPLS APS provides end-to-end protection for tunnels. The working tunnel and protection tunnel have the same ingress and egress nodes. The protection tunnel in the MPLS APS protection pair does not carry extra traffic. In MPLS APS, the MPLS OAM mechanism is used to detect faults in tunnels, and the ingress and egress nodes exchange APS protocol packets to achieve protection switching.
Purpose
MPLS APS improves reliability for service transmission in tunnels. As shown in Figure 6-24, when the MPLS OAM mechanism detects a fault in the working tunnel, the service is switched to the protection tunnel for transmission.
6-50
Issue 02 (2011-01-20)
6 Packet Features
Figure 6-24 Application example of MPLS APS

Transit
Working Tunnel Ingress Egress Protection Tunnel
Transit Protect switching Transit
Working Tunnel Ingress Egress Protection Tunnel
Transit Service Packet transmission equipment

This section describes the basic concepts associated with MPLS APS. 6.4.2.1 Protection Type MPLS APS can be classified by protection mechanism, switching mode, and revertive mode. 6.4.2.2 Switching Conditions MPLS APS can be locally triggered by a signal fail (SF) condition or by an external switching command. In dual-ended switching mode, the local NE can also perform switching according to the notification returned from the remote NE. 6.4.2.3 Switching Impact The service carried by the tunnel is unavailable during the switching (less than 100 ms).
Issue 02 (2011-01-20)
6-51
6 Packet Features

MPLS APS can be classified by protection mechanism, switching mode, and revertive mode.
Protection Mechanism
MPLS APS is classified into 1+1 protection and 1:1 protection by protection mechanism. l 1+1 protection Normally, the transmit end transmits services to the working tunnel and protection tunnel, and the receive end receives services from the working tunnel. When the working tunnel is faulty, the receive end receives services from the protection tunnel. l 1:1 protection Normally, services are transmitted in the working tunnel. The protection tunnel is idle. When the working tunnel is faulty, services are transmitted in the protection tunnel.
NOTE
The OptiX RTN 980 supports only 1:1 protection.
Switching Mode
MPLS APS is classified into the single-ended switching and the dual-ended switching by switching mode. l Single-ended switching Single-ended switching is unidirectional switching. That is, when the forward or reverse working tunnel is faulty, only the service in the direction where the fault occurs is switched to the protection tunnel. In regards to the single-ended switching, the switching operations in the two directions are not associated with each other. l Dual-ended switching Dual-ended switching is bidirectional switching. That is, when the forward or reverse working tunnel is faulty, the service in both directions is switched to the protection tunnel. Dual-ended switching ensures that the service is transmitted and received along one trail, facilitating service management and maintenance.
Revertive Mode
MPLS APS is classified into the revertive mode and the non-revertive mode by revertive mode. l Revertive mode In revertive mode, the service is automatically switched back to the working tunnel after the working tunnel is restored and the normal state lasts for a certain period. The period after the working tunnel is restored and before the service is switched back to the working tunnel is called the wait-to-restore (WTR) time. To prevent frequent switching events due to an unstable working tunnel, the WTR time is generally 5 to 12 minutes. l Non-revertive mode In non-revertive mode, the service is not automatically switched back to the working tunnel even after the working tunnel is restored. However, the service will be switched back if the protection tunnel fails or an external command triggers protection switching.
6 Packet Features

MPLS APS can be locally triggered by a signal fail (SF) condition or by an external switching command. In dual-ended switching mode, the local NE can also perform switching according to the notification returned from the remote NE.
NOTE
If two switching conditions exist at the same time, the higher-priority switching condition preempts the other one.
Table 6-24 Switching conditions for MPLS APS Switching Condition Clear switching (external switching) Lockout of protection channel (external switching) Prior ity The priorit ies are arrang ed in desce nding order. Description This command clears all the other external switching operations.
When the protection tunnel is locked out, the service is not allowed to be switched from the working tunnel to the protection tunnel. If the service is already switched to the protection tunnel, the command will forcibly switch it back to the working tunnel even when the working tunnel is not restored. Therefore, if the protection switching has been performed, running this command may interrupt the service. The signal fail for protection (SF-P) condition indicates that the protection tunnel fails. If the protection tunnel fails, the service carried by the protection tunnel is automatically switched to the working tunnel. If the lockout of protection channel condition or the SF-P condition exists, no forced switching occurs. This command forcibly switches the service from the working tunnel to the protection tunnel. Afterwards, the service will not be switched back to the working tunnel even when the working tunnel is restored. However, when a switching condition has a higher priority, the forced switching is preempted. If the lockout of protection channel condition, SF-P condition, or forced switching condition exists, no SF switching occurs. The SF switching is triggered by the MPLS OAM detection mechanism. For the conditions triggering the SF switching, see Table 6-25.
SF-P switching (automatic switching) Forced switching (external switching)
SF switching (automatic switching)
Issue 02 (2011-01-20)
6-53
6 Packet Features
Prior ity
Description If the lockout of protection channel condition, SF-P condition, forced switching condition, or SF switching condition exists, no manual switching occurs. Manual switching is available in two types: manual switching to protection and manual switching to working. l In response to the manual switching to protection command, the service is switched from the working tunnel to the protection tunnel. l In response to the manual switching to working command, the service is switched from the protection tunnel to the working tunnel.
If SF switching occurs, the service is switched from the working tunnel to the protection tunnel. If the working tunnel is restored to normal afterwards and the normal state lasts until the WTR time elapses, the service is switched back to the working tunnel. The switching remains in the WTR state after the working tunnel is restored to normal and before revertive switching occurs. After the revertive switching, the switching changes to the normal state.
This command is used to test whether the APS protocol works normally. Actually, no switching occurs and the service will not be affected.
Table 6-25 Trigger conditions for MPLS APS SF switching Switching Condition Board software or hardware failure Cold reset on board MPLS_Tunnel_Excess MPLS_Tunnel_LOCV MPLS_Tunnel_MISMATCH MPLS_Tunnel_MISMERGE MPLS_Tunnel_SF MPLS_Tunnel_FDI MPLS_Tunnel_BDI MPLS_Tunnel_SD Description Default condition Default condition Default condition Default condition Default condition Default condition Default condition Optional condition Optional condition Optional condition
6-54
Issue 02 (2011-01-20)

NOTE
6 Packet Features
An optional condition can trigger MPLS APS SF switching only after it is selected. By default, the alarms do not trigger MPLS APS SF switching.

The service carried by the tunnel is unavailable during the switching (less than 100 ms).
This section describes the specifications for MPLS APS. Table 6-26 list the specifications for MPLS APS. Table 6-26 Specifications for MPLS APS Item Maximum number of MPLS APS protection groups Specifications 32
NOTE MPLS APS and PW APS share 32 protection group resources
Supported MPLS APS protection types
l 1:1 dual-ended revertive mode l 1:1 dual-ended non-revertive mode l 1:1 single-ended revertive mode l 1:1 single-ended non-revertive mode
Protection switching duration WTR time Hold-off time Switching triggered by the BDI packet
< 100 ms 1 min to 12 min 0 ms to 10000 ms Supported

NOTE This function is supported when MPLS APS is in 1:1 single-ended revertive mode or 1:1 singleended non-revertive mode.

This section describes the standards and protocols associated with MPLS APS. The following standards and protocols are associated with MPLS APS: l l ITU-T Y.1720: Protection switching for MPLS networks ITU-T G.8131: Linear protection switching for transport MPLS(T-MPLS) networks
6.4.5 Availability
This section describes the support required by the application of the MPLS APS feature and its dependencies.
6 Packet Features

Table 6-27 Hardware and version support Feature MPLS APS Applicable Board CSHN IFU2 IFX2 ISU2 ISX2 EM6T EM6F Applicable Hardware Version All the versions All the versions All the versions All the versions All the versions All the versions All the versions Applicable Product Version V100R003C00 and later V100R003C00 and later V100R003C00 and later V100R003C00 and later V100R003C00 and later V100R003C00 and later V100R003C00 and later
The dependencies between the MPLS APS feature and other features are as follows: l l l l MPLS APS cannot co-exist with PW APS. MPLS APS can co-exist with IF 1+1 protection. MPLS APS can co-exist with IF N+1 protection. MPLS APS can co-exist with LAGs.
6.4.6 Principles
MPLS APS uses the MPLS OAM mechanism to detect faults in tunnels, and the ingress and egress nodes exchange APS protocol packets for protection switching. 6.4.6.1 Single-Ended Switching When MPLS APS is in single-ended switching mode, only the service in the direction where the fault occurs is switched to the protection tunnel. 6.4.6.2 Dual-Ended Switching When MPLS APS is in dual-ended switching mode, the service is switched to the forward and reverse protection tunnels.
6-56
Issue 02 (2011-01-20)
6 Packet Features
6.4.6.1 Single-Ended Switching

When MPLS APS is in single-ended switching mode, only the service in the direction where the fault occurs is switched to the protection tunnel.
Before Switching
l The ingress and egress nodes exchange APS protocol packets over the protection tunnel, and then they are aware of the status of each other. When the working tunnel is found faulty, the ingress and egress nodes can perform the protection switching, switching hold-off, and wait-to-restore (WTR) functions. In this case, the request state of the APS protocol packet should be No Request. The MPLS OAM mechanism is used to perform connectivity checks on all the tunnels.
During Switching
Figure 6-25 shows the principle of the single-ended switching, assuming a fault in the forward working tunnel. Figure 6-25 Principle of the single-ended switching
Ingress Forward working tunnel Forward protection tunnel Reverse working tunnel Reverse protection tunnel Switching Egress Ingress Forward working tunnel Forward protection tunnel Reverse working tunnel Reverse protection tunnel Egress
Service
Forward working tunnel label Reverse working tunnel label
Forward protection tunnel label
The single-ended switching is implemented as follows: 1. 2. The egress node detects a fault in the forward working tunnel and then it is switched to the forward protection tunnel. Afterwards, the egress node sends a bridging request to the ingress node by means of the APS protocol packet.
NOTE
l "Bridging" means that the equipment transmits the service to the protection tunnel instead of the working tunnel. l "Switching" means that the equipment receives the service from the protection tunnel instead of the working tunnel.
3.
On the reception of the bridging request, the ingress node modifies the MPLS tunnel that the FEC travels through. That is, the tunnel that the FEC travels through is changed from the forward working tunnel to the forward protection tunnel. In this case, the packet in the
Issue 02 (2011-01-20)
6 Packet Features
FEC encapsulates the MPLS label corresponding to the forward protection tunnel so that the service can be bridged to the forward protection tunnel. 4. The service is transmitted in the forward protection tunnel and the reverse working tunnel.
After Switching
If MPLS APS 1:1 single-ended switching is in revertive mode, the service in the protection tunnel is switched back to the normal working tunnel after the WTR time elapses.
6.4.6.2 Dual-Ended Switching

When MPLS APS is in dual-ended switching mode, the service is switched to the forward and reverse protection tunnels.
Before Switching
l The ingress and egress nodes exchange APS protocol packets over the protection tunnel, and then they are aware of the status of each other. When the working tunnel is found faulty, the ingress and egress nodes can perform the protection switching, switching hold-off, and wait-to-restore (WTR) functions. In this case, the request state of the APS protocol packet should be No Request. The MPLS OAM mechanism is used to perform unidirectional continuity checks on all the tunnels.
During Switching
Figure 6-26 shows the principle of the dual-ended switching, assuming a fault in the forward working tunnel. Figure 6-26 Principle of the dual-ended switching
Ingress Forward working tunnel Forward protection tunnel Reverse working tunnel Reverse protection tunnel Switching Egress Ingress Forward working tunnel Forward protection tunnel Reverse working tunnel Reverse protection tunnel Egress
Service
Forward working tunnel label Reverse working tunnel label
Forward protection tunnel label Reverse protection tunnel label
The dual-ended switching is implemented as follows: 1. When the egress node detects a fault in the forward working tunnel, it is switched to the forward protection tunnel and is bridged to the reverse protection tunnel at the same time.
6-58
6 Packet Features
l The egress node receives the service from the forward protection tunnel instead of the forward working tunnel. In addition, the egress node sends the APS protocol packet carrying a bridging request to the ingress node. l The egress node modifies the MPLS tunnel that the FEC travels through. That is, the tunnel that the FEC travels through is changed from the reverse working tunnel to the reverse protection tunnel. In this case, the packet in the FEC encapsulates the MPLS label corresponding to the reverse protection tunnel so that the service can be bridged to the reverse protection tunnel. Meanwhile, the egress node sends the APS protocol packet carrying a switching request to the ingress node.
NOTE
l "Bridging" means that the equipment transmits the service to the protection tunnel instead of the working tunnel. l "Switching" means that the equipment receives the service from the protection tunnel instead of the working tunnel.
2.
On the reception of the APS protocol packet carrying a switching request, the ingress node performs the following operations: l The ingress node modifies the MPLS tunnel that the FEC travels through. That is, the tunnel that the FEC travels through is changed from the forward working tunnel to the forward protection tunnel. In this case, the packet in the FEC encapsulates the MPLS label corresponding to the forward protection tunnel so that the service can be bridged to the forward protection tunnel. l The ingress node receives the service from the reverse protection tunnel instead of the reverse working tunnel.
3.
The service is transmitted in the forward and reverse protection tunnels.
After Switching
If MPLS APS 1:1 dual-ended switching is in revertive mode, the service is switched back to the normal forward and reverse working tunnels after the WTR time elapses.

When MPLS APS is configured, MPLS OAM is configured simultaneously.
Issue 02 (2011-01-20)
6-59
6 Packet Features
Table 6-28 Flow for configuring MPLS APS Step 1 Operation A.7.2.6 Setting MPLS OAM Parameters Description Required. Set the major parameters as follows: l On the Ingress/Egress node of the required LSP, set OAM Status to Enabled. l Regarding a unidirectional tunnel, set Detection Packet Type of the Ingress node to FFD; regarding a bidirectional tunnel, set Detection Packet Type of the Ingress/Egress node to FFD. It is recommended that you set Detection Packet Period(ms) to 3.3 ms. If this parameter of an MPLS tunnel exceeds 3.3 ms, set the packet transmission interval to a value greater than the delay. l It is recommended that you set Detection Mode of the Egress node to Auto-Sensing. l Regarding a unidirectional tunnel, set Reverse Tunnel. l It is recommended that you set SD Threshold and SF Threshold to 0.
NOTE If Detection Packet Period(ms) needs to be set as required, set Detection Packet Type to FFD.
A.7.2.7 Enabling/ Disabling FDI
Optional. Enable FDI is enabled by default. Therefore, the FDI packet is transmitted to the downstream when the port detects a fault. Then, switching will be performed on the egress node after the FDI packet arrives at the egress node.
6-60
Issue 02 (2011-01-20)
6 Packet Features
Step 3
Operation A.7.3.1 Creating an MPLS APS Protection Group
Description Required. The parameters of the Ingress node and Egress node must be set to the same values. Set the major parameters as follows: l Set Protection Type to 1:1. l Set Switching Mode to Dual-Ended. l Set Working Ingress Tunnel ID and Working Egress Tunnel ID for the working tunnel according to the planning information.
NOTE Regarding a bidirectional tunnel, Working Ingress Tunnel ID and Protection Ingress Tunnel ID need to be set, but Working Egress Tunnel ID and Protection Egress Tunnel ID do not need to be set.
l Set Protection Ingress Tunnel ID and Protection Egress Tunnel ID for the protection tunnel according to the network planning. l It is recommended that you set Revertive Mode to Revertive. l It is recommended that you set WTR Time (min) to 5. l It is recommended that you set Hold-Time (100ms) to 0. l Set Protocol Status to Disabled. 4 A.7.3.4 Enabling/ Disabling MPLS APS Protection After the Ingress node and Egress node are configured, set Protocol Status of the APS protection groups on the two nodes to Enabled.

This section uses an example to describe how to plan and configure MPLS APS according to network conditions. 6.4.8.1 Network Diagram This section describes the networking information about the NEs. 6.4.8.2 Service Planning The service planning information contains all the parameters required for configuring the NE data. 6.4.8.3 Configuration Process This section describes the process of data configuration.

This section describes the networking information about the NEs.
6 Packet Features
On a PSN shown in Figure 6-27, the LSP between NE1 and NE4 is under 1:1 protection to improve service transmission reliability. Figure 6-27 Network diagram of MPLS APS
NE2 Working Tunnel ID: 1501
NE1
NE4
Protection Tunnel ID: 1502 NE3

The service planning information contains all the parameters required for configuring the NE data. In this example, the planning information about MPLS APS for NE1 and NE4 is as follows. l l l Since the network delay jitter in this example is small, MPLS OAM packets are transmitted at an interval of 3.3 ms. MPLS APS switching can be performed not according to the packet loss ratio threshold. The MPLS APS protection group in this example is in 1:1 dual-ended revertive mode. The default switchover restoration time is five minutes.

Procedure
Step 1 See A.7.2.6 Setting MPLS OAM Parameters, and configure MPLS OAM parameters. The values for the required parameters are provided as follows.
6-62
Issue 02 (2011-01-20)
6 Packet Features
Parameter
Value NE1 Tunnel ID = 1501 (Working Tunnel) Tunnel ID = 1502 (Protection Tunnel) Enabled Auto-Sensing FFD 0 0 NE4 Tunnel ID = 1501 (Working Tunnel) Enabled Auto-Sensing FFD 0 0 Tunnel ID = 1502 (Protection Tunnel) Enabled Auto-Sensing FFD 0 0
OAM Status Detection Mode Detection Packet Type SD Threshold SF Threshold
Enabled Auto-Sensing FFD 0 0
Step 2 See A.7.3.1 Creating an MPLS APS Protection Group, and create an MPLS APS protection group. The values for the required parameters are provided as follows.
NOTE
Before configuring the following parameters, set Protocol Status to Disabled.
Parameter
Value NE1 NE4 1:1 Dual-ended MPLS Tunnel 1501 1502 Revertive 5 0 Disabled
Protection Type Switching Mode Working Tunnel Type Working Ingress Tunnel ID Protection Ingress Tunnel ID Revertive Mode WTR Time(min) Hold-Time(100ms) Protocol Status
1:1 Dual-ended MPLS Tunnel 1501 1502 Revertive 5 0 Disabled
Step 3 See A.7.3.4 Enabling/Disabling MPLS APS Protection, and enable or disable MPLS APS protection. The values for the required parameters are provided as follows.
6 Packet Features
Parameter
Value NE1 NE4 Enabled
Protocol Status
Enabled
----End

Related Tasks
A.7.3.1 Creating an MPLS APS Protection Group A.7.3.2 Querying MPLS APS Status A.7.3.3 Triggering MPLS APS Switching A.7.3.4 Enabling/Disabling MPLS APS Protection

When detecting an exception by performing MPLS APS operations, an NE reports the specific alarm.
Relevant Alarms
l ETH_APS_LOST The ETH_APS_LOST alarm indicates that the APS frame is lost. This alarm is reported when the APS frame is not received from the protection tunnel. l ETH_APS_PATH_MISMATCH The ETH_APS_PATH_MISMATCH alarm indicates a mismatch between the working tunnel and protection tunnel of the APS. This alarm is reported when the working and protection tunnels that are selected by the equipment at both ends of a protection group are not consistent. l ETH_APS_SWITCH_FAIL The ETH_APS_SWITCH_FAIL alarm indicates a protection switching failure. When a request signal contained in the APS frame that is sent from a port is not consistent with the bridge signal contained in the APS frame that is received at this port, if this condition lasts for more than 50 ms, the switching fails. In this case, this alarm is reported. l ETH_APS_TYPE_MISMATCH The ETH_APS_TYPE_MISMATCH alarm indicates a protection type mismatch. This alarm is reported when the APS protection type information contained in the APS frame that is received at the local end is inconsistent with the APS protection type that is configured.
Relevant Events
Change in the switching state of APS protection group This event indicates that MPLS APS protection switching occurs.
6 Packet Features
6.4.11 FAQs
This section provides answers to the questions that are frequently raised when MPLS APS is used. Question: What should be done when MPLS APS protection switching fails? Answer: The steps are as follows: 1. 2. Check the configurations of the MPLS APS protection group. The configurations of the MPLS APS protection group at both ends of the link should be consistent. If the configurations are inconsistent, reconfigure the MPLS APS protection group. After the MPLS APS protection group is reconfigured at both ends, deactivate and then activate the MPLS APS protection group.
Question: Why must the transmission period of FFD packets be 3.3 ms to support MPLS APS? Answer: Because the time of detecting a fault in an LSP is shorter and the protection switching time can be less than 100 ms.
6.5 PWE3 Basics

This chapter describes the basics of pseudo wire emulation edge-to-edge (PWE3). 6.5.1 Introduction This section provides the definition of pseudo wire emulation edge-to-edge (PWE3) and describes its purpose. 6.5.2 Basic Concepts This section describes the basic concepts associated with PWE3. 6.5.3 Specifications This section describes the specifications for PWE3. 6.5.4 Reference Standards and Protocols This section describes the standards and protocols associated with PWE3 basics. 6.5.5 Availability This section describes the support required by the application of the PWE3 feature and its dependencies. 6.5.6 Principles The SS-PW and MS-PW use different packet forwarding mechanisms. 6.5.7 Configuration Procedure The configuration procedure of different PWE3 services are different. 6.5.8 Configuration Example This section uses several examples to describe how to plan and configure PWE3 according to network conditions. 6.5.9 Task Collection This section provides the hyperlinks of the operation tasks associated with the feature. 6.5.10 Relevant Alarms and Events
6 Packet Features
When an exception is detected in the PW, an NE reports the specific alarm. 6.5.11 FAQs This section provides answers to the questions that are frequently raised when PWs are used.
6.5.1 Introduction
This section provides the definition of pseudo wire emulation edge-to-edge (PWE3) and describes its purpose.
Definition
PWE3 is a Layer 2 service bearer technology that emulates the basic behaviors and characteristics of services such as ATM/IMA, Ethernet, and TDM on a packet switched network (PSN). Aided by the PWE3 technology, conventional networks can be connected by a PSN. Therefore, resource sharing and network scaling can be achieved.
Purpose
PWE3 aims to transmit various services such as ATM, Ethernet, and TDM over a PSN. Figure 6-28 shows the PWE3 application. The Ethernet, ATM, and TDM services between NodeBs and RNCs are emulated by means of PWE3 on NE1 and NE2, and then are transmitted on the pseudo wires (PWs) between NE1 and NE2. Figure 6-28 Typical application of PWE3
Ethernet, ATM, TDM Ethernet, ATM, TDM
PSN
NodeB
PW1 PW2
RNC MPLS tunnel NE2 RNC Ethernet, ATM, TDM
NE1 NodeB Ethernet, ATM, TDM Packet transmission equipment

This section describes the basic concepts associated with PWE3. 6.5.2.1 PWE3 Network Reference Model In the PWE3 network reference model, a PW connects two provider edges (PEs), and an attachment circuit (AC) connects a PE device and a customer edge (CE) device. 6.5.2.2 PWE3 Protocol Reference Model
6 Packet Features
The protocol reference model used by the OptiX RTN 980 includes pre-processing of native services. 6.5.2.3 PWE3 Encapsulation Format The specific PWE3 encapsulation format varies slightly according to the type of emulated service, but a generic encapsulation format is also available. 6.5.2.4 MS-PW A PW that is carried in a PSN tunnel is called a single-segment PW (SS-PW). If a PW is carried in multiple PSN tunnels, the PW is called a multi-segment PW (MS-PW). 6.5.2.5 VCCV As specified in IETF RFC5085, virtual circuit connectivity verification (VCCV) is an end-toend fault detection and diagnostics mechanism for a PW. The VCCV mechanism is, in its simplest description, a control channel between a PW's ingress and egress points over which connectivity verification messages can be sent. The OptiX RTN 980 supports VCCV that uses the control word as the control channel and the LSP ping as the verification method.
6.5.2.1 PWE3 Network Reference Model

In the PWE3 network reference model, a PW connects two provider edges (PEs), and an attachment circuit (AC) connects a PE device and a customer edge (CE) device. Figure 6-29 shows the PWE3 network reference model. One or more PWs are created between PE1 and PE2 based on the service access requirements at the CEs. Several PWs can be carried in one or more PSN tunnels. In this manner, native services can be transmitted over a PSN. Figure 6-29 PWE3 network reference model
Emulated service PW Native service PE1 CE1 PW2 PSN tunnel Native service PE2 CE2
PW1
AC
AC
AC: attachment circuit PE: provider edge
CE: customer edge PW: pseudo wire
NOTE
In the network reference model, PWs are carried in a PSN tunnel; that is, a single-segment PW (SS-PW).
The concepts found in the network reference model shown in Figure 6-29 are defined as follows.
6 Packet Features
CE
A CE is a device where one end of a service originates and/or terminates. The CE is not aware that it is using an emulated service rather than a native service.
PE
A PE is a device that provides PWE3 to a CE. Located at the edge of a network, a PE is connected with a CE through an AC. In the PWE3 network reference model, the mapping relationship between an AC and a PW is determined once a PW is created between two PEs. As a result, Layer 2 services on CEs can be transmitted over a PSN.
AC
An AC is a physical or virtual circuit attaching a CE to a PE. An AC can be, for example, an Ethernet port, a VLAN, or a TDM link.
PW
A PW is a mechanism that carries emulated services from one PE to another PE over a PSN. By means of PWE3, point-to-point channels are created, separated from each other. Users' Layer 2 packets are transparently transmitted on a PW. PWs are available in two types depending on whether signaling protocols are used or not. Specifically, a PW that does not use signaling protocols is called a static PW, whereas a PW that does use signaling protocols is called a dynamic PW.
NOTE
The OptiX RTN 980 supports only static PWs.
Tunnel
A tunnel provides a mechanism that transparently transmits information over a network. In a tunnel, one or more PWs can be carried. A tunnel connects a local PE and a remote PE for transparently transmitting data. PSN tunnels are available in several types, but the OptiX RTN 980 supports only MPLS tunnels. In this document, PWE3 is generally based on the MPLS tunnel (LSP), unless otherwise specified.
6.5.2.2 PWE3 Protocol Reference Model

The protocol reference model used by the OptiX RTN 980 includes pre-processing of native services. Figure 6-30 shows the PWE3 protocol reference model.
6-68
Issue 02 (2011-01-20)
6 Packet Features
Figure 6-30 PWE3 protocol reference model

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

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

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

The specific PWE3 encapsulation format varies slightly according to the type of emulated service, but a generic encapsulation format is also available.
6 Packet Features
Figure 6-31 shows the generic PWE3 encapsulation format. A PWE3 packet contains the MPLS label, control word, and payload. Figure 6-31 PWE3 encapsulation format
0 Tunnel label PW label Control Word Laye 2 r PDU Payload MPLS label Control word Payload 20 23 24 EXP EX P EXP S S S TTL TT L TTL 31bit
MPLS Label
The MPLS labels include tunnel labels and PW labels, which are used to identify tunnels and PWs respectively. The format of the tunnel label is the same as that of the PW label. For details, see 6.1.2.4 MPLS Label.
Control Word
The 4-byte control word is a header used to carry packet information over an MPLS PSN. The control word is used to check the packet sequence, to fragment packets, and to restructure packets. As shown in Table 6-29, the specific format of the control word is determined by the service type carried by PWE3 and the encapsulation mode adopted. Table 6-29 Formats of the control word for various services in different encapsulation modes Service Type TDM PWE3 Format of Control Word SAToP CESoPSN ATM PWE3 ATM N-to-one cell encapsulation ATM one-to-one cell encapsulation ETH PWE3 Ethernet encapsulation
6-70
Issue 02 (2011-01-20)
6 Packet Features
Payload
Payload indicates the payload of a service in a PWE3 packet.
6.5.2.4 MS-PW
A PW that is carried in a PSN tunnel is called a single-segment PW (SS-PW). If a PW is carried in multiple PSN tunnels, the PW is called a multi-segment PW (MS-PW).
NOTE
For the SS-PW network reference model, see 6.5.2.1 PWE3 Network Reference Model.
MS-PW Network Reference Model

Figure 6-32 shows the MS-PW network reference model. Figure 6-32 MS-PW network reference model
Emulated service MS-PW Native service T-PE1 CE1 PW2 PW4 PSN tunnel 1 PW1 S-PE1 PSN tunnel 2 PW3 T-PE2 CE2 Native service
AC PW switching point T-PE: terminating provider edge S-PE: switching provider edge
AC
NOTE
PSN tunnels are available in several types, but the OptiX RTN 980 supports only MPLS tunnels. In this document, PWE3 is based on MPLS tunnels (LSPs), unless otherwise specified.
In the preceding network reference model, T-PE1 and T-PE2 provide PWE3 services to CE1 and CE2. The PWs are carried in two PSN tunnels, and constitute the MS-PW. The two tunnels (PSN tunnel 1 and PSN tunnel 2) that are used to carry PWs reside in different PSN domains. PSN tunnel 1 extends from T-PE1 to S-PE1, and PSN tunnel 2 extends from SPE1 to T-PE2. Labels of PW1 carried in PSN tunnel 1 and PW3 carried in PSN tunnel 2 are swapped at S-PE1. Similarly, labels of PW2 carried in PSN tunnel 1 and PW4 carried in PSN tunnel 2 are swapped at S-PE1.
MS-PW Application
Compared with the SS-PW, the MS-PW has the following characteristics:
6 Packet Features
l l l
Reduces required tunnel resources. Traverses different PSNs. Provides segment-based protection for tunnels.
The following paragraphs and figures compare the application scenarios of the SS-PW and MSPW to show that it is easier for the MS-PW to implement segment-based protection for tunnels. Figure 6-33 shows the SS-PW networking mode. The services between PE1 and PE2 are transmitted on PW1 carried in MPLS tunnel 1. Both MPLS tunnel 1 and MPLS tunnel 2 are configured with 1:1 protection. Protection, however, fails to be provided if disconnection faults occur on different sides of the operator device (called the P device). Figure 6-33 SS-PW application
SS-PW
PW1
MPLS tunnel 1
PW1
PE1
PW1
P MPLS tunnel 2
PE2
PW1
NOTE
The PWs are invisible to the P device on a PSN; the P device provides transparent transport in tunnels.
Figure 6-34 shows the MS-PW networking mode. The services between T-PE1 and T-PE2 are transmitted on PW1 carried in MPLS tunnel 1 and PW2 carried on MPLS tunnel 2. The paired tunnels (MPLS tunnel 1 and MPLS tunnel 3; MPLS tunnel 2 and MPLS tunnel 4) are configured with 1:1 protection. In this configuration, protection can still be provided even when disconnection faults occur on different sides of the S-PE1 device. Figure 6-34 MS-PW application
MS-PW MPLS tunnel 1
PW1
MPLS tunnel 2
PW2
PW1
PW2
T-PE1
MPLS tunnel 3
S-PE1
MPLS tunnel 4
T-PE2
6-72
Issue 02 (2011-01-20)
6 Packet Features
6.5.2.5 VCCV
As specified in IETF RFC5085, virtual circuit connectivity verification (VCCV) is an end-toend fault detection and diagnostics mechanism for a PW. The VCCV mechanism is, in its simplest description, a control channel between a PW's ingress and egress points over which connectivity verification messages can be sent. The OptiX RTN 980 supports VCCV that uses the control word as the control channel and the LSP ping as the verification method. The VCCV messages are exchanged between PEs to verify connectivity of PWs. To ensure that VCCV messages and PW packets traverse the same path, VCCV messages must be encapsulated in the same manner as PW packets and be transmitted in the same tunnel as the PW packets. VCCV messages have the following formats.
Format of a VCCV Message Based on Control Word

Figure 6-35 Format of a VCCV message based on control word
0 Tunnel label PW label 0001 Version Reserved 20 23 24 EXP EX P EXP S S S TTL TT L TTL 31bit
Channel type
Laye MPLS echor message (IPv4 UDP)
The control word in a VCCV message is defined as follows: l l l l Header: This field is always 0001. Version: This field is always 0. Reserved: This field is always 0. Channel type: The Channel Type is set to 0x0021 for IPv4 payloads and 0x0057 for IPv6 payloads.
The payloads are MPLS echo packets encapsulated in IPv4 UDP.
Issue 02 (2011-01-20)
6-73
6 Packet Features
Format of a VCCV Message Based on OAM Alert Label

Figure 6-36 Format of a VCCV message based on OAM alert label
0 Tunnel label PW label Label : 1 (OAM Alert Label) 20 23 24 EXP EX P EXP EXP S S S S TTL TT L TTL TTL: 1 31bit
MPLS echo packet (IPv4 UDP)
The main fields in a VCCV message based on OAM alert label are defined as follows: l l Label: The value of this field is 14 and indicates an OAM packet. Time to Live (TTL): The value of this field is set to 1, to ensure that the MPLS OAM packet is not transmitted beyond the sink end of the monitored LSP.
The payloads are MPLS echo packets encapsulated in IPv4 UDP. VCCV is implemented based on the extension of the LSP ping mechanism. For specific principles, see 6.10.5 Principles.
This section describes the specifications for PWE3. Table 6-30 lists the specifications for PWE3. Table 6-30 Specifications for PWE3 Item Maximum number of PWs Specifications 1024
NOTE The total number of tunnels and PWs cannot exceed 1024. The tunnels carrying PWs are not included when the local NE is an ingress or egress node.
Bearer type PW service type
MPLS tunnel TDM PWE3 ETH PWE3 ATM PWE3
MS-PW
6-74
Supported
6 Packet Features
Item VCCV
Specifications l Supported by TDM PWE3 l Supported by ATM PWE3 l Supported by ETH PWE3
PW APS
Supported
PW OAM
Supported
PW ping/traceroute
l Supported by TDM PWE3 l Supported by ATM PWE3 l Supported by ETH PWE3


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

Table 6-31 Hardware and version support Feature PWE3 Applicable Board CSHN IFU2 Applicable Hardware Version All the versions All the versions Applicable Product Version V100R003C00 and later V100R003C00 and later
6-75
Issue 02 (2011-01-20)
6 Packet Features
Feature
Applicable Board IFX2 ISU2 ISX2 EM6T EM6F
Applicable Product Version V100R003C00 and later V100R003C00 and later V100R003C00 and later V100R003C00 and later V100R003C00 and later
The dependencies between the PWE3 feature and other features are as follows: l l The OptiX RTN 980 supports PWs carried by MPLS tunnels. PWs cannot participate in Layer 2 switching.
6.5.6 Principles
The SS-PW and MS-PW use different packet forwarding mechanisms. 6.5.6.1 Packet Forwarding Process of SS-PW In the SS-PW networking mode, the PW label is not swapped during the packet forwarding process. 6.5.6.2 Packet Forwarding Process of MS-PW In the MS-PW networking mode, the PW label is swapped at S-PE during the packet forwarding process.
6.5.6.1 Packet Forwarding Process of SS-PW

In the SS-PW networking mode, the PW label is not swapped during the packet forwarding process. Figure 6-37 shows the packet forwarding process in the SS-PW networking mode.
6-76
Issue 02 (2011-01-20)
6 Packet Features
Figure 6-37 SS-PW packet forwarding process
PSN
MPLS tunnel AC PE1
A PW1 PW1
AC PE2 CE2 (RNC)
CE1 (NodeB) Payload PW label

A B
P
B
Tunnel label A Tunnel label B Packet transmission equipment
NOTE
The PWs are invisible to the P device on a PSN; the P device provides transparent transport in tunnels.
The local PE (PE1) forwards packets as follows: 1. 2. 3. 4. Extracts the local service packets that are transmitted by CE1 from the AC. Pre-processes the service payloads before PWE3 emulation. Uses the forwarder to map service payloads to the corresponding PW. Encapsulates the data transmitted on a PW into PWE3 packets in standard format. The process involves generation of the control word, and adding of the PW label and tunnel label (tunnel label A) to the data. Maps the PW into the MPLS tunnel for transmission.
5.
The P device forwards packets as follows: When PWE3 packets transmitted from PE1 to PE2 traverse the P device, the tunnel label in the packets is swapped. That is, tunnel label A is changed to tunnel label B. The remote PE (PE2) forwards packets as follows: 1. 2. 3. 4. 5. Demultiplexes the PW from the MPLS tunnel. Decapsulates the PW, and removes the tunnel label (tunnel label B), PW label, and control word. Extracts service payloads from the PW. Restores service payloads to the local service packets. Selects an AC by using the forwarder, and forwards the packets to CE2 at the remote end over the AC.
6.5.6.2 Packet Forwarding Process of MS-PW

In the MS-PW networking mode, the PW label is swapped at S-PE during the packet forwarding process. Figure 6-38 shows the packet forwarding process in the MS-PW networking mode.
6 Packet Features
Figure 6-38 MS-PW packet forwarding process of MS-PW
PSN
AC Tunnel 1
PW1
Tunnel 2
PW2
AC
CE1 (NodeB)
A B A B
T-PE1
A A
S-PE1
B B
T-PE2
CE2 (RNC)
Payload PW label A PW label B Tunnel label A Tunnel label B Packet transmission equipment
The T-PE in the MS-PW networking mode forwards packets in the same manner as PE in the SS-PW networking mode. In the MS-PW networking mode, S-PE needs to swap the tunnel label and PW label. The S-PE device (S-PE1) forwards packets as follows: When PWE3 packets transmitted from PE1 to PE2 traverse the P device, the tunnel label in the packets is swapped. That is, tunnel label A is changed to tunnel label B. In addition, the PW label in the packets is swapped. That is, PW label A is changed to PW label B.

The configuration procedure of different PWE3 services are different. l l l For the configuration procedure of TDM PWE3 services, see 6.6.7 Configuration Procedure regarding the TDM PWE3 feature. For the configuration procedure of ATM PWE3 services, see 6.7.7 Configuration Procedure regarding the ATM PWE3 feature. For the configuration procedure of ETH PWE3 services, see 6.8.7 Configuration Procedure regarding the ETH PWE3 feature.

This section uses several examples to describe how to plan and configure PWE3 according to network conditions. For the configuration example of TDM PWE3, see Configuration Example (Common CES Services) in the Configuration Guide. For the configuration example of ATM PWE3, see Configuration Example (Common ATM Services) in the Configuration Guide. For the configuration example of ETH PWE3, see Configuration Example (E-Line Services Carried on PWs, a Simple Example) in the Configuration Guide.
6 Packet Features

Related Tasks
A.7.4.1 Querying Information and Running Status of PWs A.7.4.2 Creating an MS-PW

When an exception is detected in the PW, an NE reports the specific alarm. l l l l For the alarms associated with PW OAM, see 6.9.10 Relevant Alarms and Events. For the alarms associated with PW APS, see 6.11.10 Relevant Alarms and Events. For the alarms associated with TDM PWE3, see 6.6.10 Relevant Alarms and Events. For the alarms associated with ATM PWE3, see 6.7.10 Relevant Alarms and Events.
6.5.11 FAQs
This section provides answers to the questions that are frequently raised when PWs are used. Question: Does the PWE3 technology provided by the OptiX RTN 980 support packet fragmentation and restructuring that are specified in RFC 4623? Answer: No. It does not support packet fragmentation or restructuring that are specified in RFC 4623.
6.6 TDM PWE3

This chapter describes the TDM PWE3 feature. 6.6.1 Introduction This section provides the definition of TDM PWE3 and describes its purpose. 6.6.2 Basic Concepts This section describes the basic concepts associated with TDM PWE3. 6.6.3 Specifications This section describes the specifications for TDM PWE3. 6.6.4 Reference Standards and Protocols This section describes the standards and protocols associated with TDM PWE3. 6.6.5 Availability This section describes the support required by the application of the TDM PWE3 feature and its dependencies. 6.6.6 Principles This section describes the principles of TDM PWE3. 6.6.7 Configuration Procedure The port attributes of a UNI port are configured during the configuration of TDM PWE3. 6.6.8 Configuration Example
6 Packet Features
This section uses an example to describe how to plan and configure TDM PWE3 according to network conditions. 6.6.9 Task Collection This section provides the hyperlinks of the operation tasks associated with the feature. 6.6.10 Relevant Alarms and Events When an exception is detected in the TDM PWE3 packet, an NE reports the specific alarm. 6.6.11 FAQs This section provides answers to the questions that are frequently raised when TDM PWE3 is used.
6.6.1 Introduction
This section provides the definition of TDM PWE3 and describes its purpose.
Definition
The TDM PWE3 technology emulates the basic behaviors and characteristics of TDM services on a packet switched network (PSN) by using the PWE3 mechanism, so that the emulated TDM services can be transmitted on a PSN. TDM PWE3 services are also called CES services carried by PWE3. In this document, all the CES services are carried by PWE3.
Purpose
TDM PWE3 aims to transmit TDM services over a PSN. Especially, the 6.6.2.3 CESoPSN mode can compress idle timeslots to reduce the required transmission bandwidth. Figure 6-39 shows the typical application of TDM PWE3. The native TDM services between the BTS and the BSC are transmitted over a PSN. PE1 emulates the native TDM services from the BTS into CES services by using the CESoPSN technology. Then, the CES services are transmitted to PE2 over the PSN. Finally, PE2 restores the CES services to the native TDM services for transmission to the BSC. Figure 6-39 Typical application of TDM PWE3 (CESoPSN mode)
Framed E1
-Service TS Idle TS
PSN
LSP
AC CE1 (BTS) PE1
PW PE2
AC CE2 (BSC)
Native TDM service
TDM PWE3
Native TDM service
Framed E1
TDM PWE3 packet
6-80
Issue 02 (2011-01-20)
6 Packet Features
Aided by the TDM PWE3 technology, conventional TDM networks can be connected by a PSN. In this manner, PWE3 protects customer investment in TDM networks and constructs all-IP network architecture.

This section describes the basic concepts associated with TDM PWE3. 6.6.2.1 E1 Frame Format An E1 frame consists of 32 timeslots. E1 frames are available in different formats when classified based on the usage of timeslot 0 and timeslot 16. 6.6.2.2 SAToP Structure Agnostic TDM over Packet Switched Network (SAToP) is a method for encapsulating TDM serial bit streams as pseudo wires. 6.6.2.3 CESoPSN Circuit Emulation Service over Packet Switched Network (CESoPSN) is a method for encapsulating TDM frames as pseudo wires. 6.6.2.4 Data Jitter Buffer After CES packets are transmitted over a PSN, the intervals between packet arrivals may be different and the packets may be misordered. To ensure that the TDM bit streams can be reconstructed on the egress PE, a jitter buffer is required to smooth the intervals between packet arrivals and to reorder the misordered packets. 6.6.2.5 CES Alarm Transparent Transmission The OptiX RTN 980 uses the L/M and R fields in the control word to transparently transmit alarms. 6.6.2.6 Clock Recovery Schemes of TDM PWE3 When clocks need to be transmitted with CES services, you can adopt CES retiming or CES adaptive clock recovery (ACR) as required. 6.6.2.7 QoS of TDM PWE3 The QoS of TDM services features low delay, low jitter, and fixed bandwidth. Therefore, a high enough per-hop behavior (PHB) level needs to be assigned to CES packets.
6.6.2.1 E1 Frame Format

An E1 frame consists of 32 timeslots. E1 frames are available in different formats when classified based on the usage of timeslot 0 and timeslot 16.
Frame Formats Based on the Usage of Timeslot 0

Figure 6-40 shows the formats of timeslot 0 in E1 frames.
Issue 02 (2011-01-20)
6-81
6 Packet Features
Figure 6-40 Formats of timeslot 0 in E1 frames

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

E1 frames can be classified into PCM30 frames and PCM31 frames, depending on whether timeslot 16 transmits voice or signaling. l A PCM30 frame uses channel associated signaling (CAS). In this mode, timeslot 0, as a synchronous timeslot, cannot carry voice; timeslot 16, to carry CAS, cannot carry voice either. As a result, one E1 frame can carry only 30 voice signals, and it is therefore called a PCM30 frame. A PCM31 frame uses common channel signaling (CCS). A multiframe in CCS mode does not need to transmit CAS. In this mode, except for timeslot 0 that carries synchronous signals, one E1 frame can carry 31 voice signals and it is therefore called a PCM31 frame.
The two classification methods focus on two attributes of E1 frames, and they can be combined. Specifically, there are four E1 frame formats in actual application: l l l l PCM30CRC (PCM30 + CRC-4 multiframe) PCM30NOCRC (PCM30 + generic dual-frame) PCM31CRC (PCM31 + CRC-4 multiframe) PCM31NOCRC (PCM31 + generic dual-frame)
6.6.2.2 SAToP
Structure Agnostic TDM over Packet Switched Network (SAToP) is a method for encapsulating TDM serial bit streams as pseudo wires.
6 Packet Features
SAToP provides the emulation and transport functions for unchannelized TDM services. That is, it addresses only structure-agnostic transport. Therefore, SAToP can meet the transport needs when a user needs services based on E1s. SAToP segments and encapsulates TDM services as serial bit streams, and then transmits the bit streams in PW tunnels. Although it disregards the TDM frame structure, it supports transmission of synchronous information. Figure 6-41 shows the encapsulation format of a SAToP packet. Figure 6-41 Encapsulation format of a SAToP packet
0 Tunnel label PW label 0000 L R RSV FRG LEN RTP header TDM data 20 23 24 EXP EX P EXP S S S TTL TT L TTL 31bit
Sequence number
MPLS label Control word RTP header/TDM data
A SAToP packet contains the MPLS label, control word, RTP header, and TDM data.
MPLS Label
MPLS labels include tunnel labels and PW labels, which are used to identify tunnels and PWs respectively. The format of the tunnel label is the same as that of the PW label. For details, see 6.1.2.4 MPLS Label.
Control Word
The control word of a SAToP packet is 4-byte long and contains the following fields: l 0000: The 4 bits are generally set to all 0s. They are used to indicate the start of an Associated Channel Header (ACH). The ACH is needed if the state of the SAToP PW is monitored using virtual circuit connectivity verification (VCCV). L: This bit indicates whether the TDM data carried in a packet is valid. If set to 1, it indicates that the TDM data is omitted in order to conserve bandwidth. R: This bit indicates whether its local CE-side interworking function (IWF) is in the packet loss state. If set to 0, it indicates that a preconfigured number of consecutive packets are received.
l l
Issue 02 (2011-01-20)
6 Packet Features
l l
RSV: The 2 bits are reserved. FRG: The 2 bits indicate fragmentation with the following values: 00: indicates that the entire TDM data is encapsulated in the packet. 01: indicates that the first fragmentation of the TDM data is encapsulated in the packet. 10: indicates that the last fragmentation of the TDM data is encapsulated in the packet. 11: indicates that the middle fragmentation of the TDM data is encapsulated in the packet.
LEN: The 6 bits indicate the length of the SAToP packet (including the SAToP header and TDM data). The minimum length of a transport unit on a PSN is 64 bytes. When a packet is shorter than 64 bytes, LEN indicates the actual length of the packet, representing padding bits. If a packet is longer than 64 bytes, LEN is set to all 0s. Sequence number: The 16 bits indicate the transmission sequence number of a SAToP packet. Its initial value is random, and is incremented by one with each SAToP data packet sent. If the sequence number of a packet reaches the maximum (65535), the sequence number of its next packet will start with the minimum. The sequence number can be in Huawei mode or standard mode. In Huawei mode, the minimum sequence number is 0; in standard mode, the minimum sequence number is 1.
RTP Header
The Real-time Transport Protocol (RTP) header is used to carry timestamp information to the remote end so that the packet clock can be restored. The RTP header is 12-byte long. The 32bit timestamp field in the RTP header represents the timestamp information. For the specific format of the RTP header, see RFC 3550.
NOTE
On the OptiX RTN 980, you can set whether the RTP header is encapsulated into the SAToP packet.
TDM Data
"TDM data" indicates the TDM data payload in the form of serial bit stream. When a PW packet is shorter than 64 bytes, fixed bits are padded to meet Ethernet transmission requirements. The amount of E1 bit streams that are encapsulated in a PW packet is determined by Packet Loading Time. Packet Loading Time indicates the duration for a PW packet to load TDM bit streams. Regarding that the number of loaded TDM bit streams is equal to Packet Loading Time multiplied by the E1 rate, Packet Loading Time limits the number of loaded TDM bit streams. For instance, when the packet loading time is 1 ms, each PW packet can load 2048-bitlong E1 payloads.
6.6.2.3 CESoPSN
Circuit Emulation Service over Packet Switched Network (CESoPSN) is a method for encapsulating TDM frames as pseudo wires. CESoPSN provides the emulation and transport functions for channelized TDM services. That is, it identifies the TDM frame format and signaling in the frame. Therefore, CESoPSN can meet the transport needs when a user needs services based on timeslots. With the frame format of the TDM service identified, CESoPSN does not transmit idle timeslot channels; instead, CESoPSN extracts only the usable timeslots from the service flow and then encapsulates these timeslots as PW packets for transmission.
6 Packet Features
Figure 6-42 shows the encapsulation format of a CESoPSN packet. Figure 6-42 Encapsulation format of a CESoPSN packet
0 Tunnel label PW label 0000 L R M FRG LEN RTP header Timeslot 1 Timeslot 5 Timeslot 1 Timeslot 5 Timeslot 3 ... Timeslot n (frame 1#) Timeslot 2 Timeslot 3 ... Timeslot n (frame 2#) ... Timeslot n (frame m #) MPLS label Control word RTP header/TDM data Timeslot 2 Timeslot 4 Timeslot 4 20 23 24 EXP EX P EXP S S S TTL TT L TTL 31bit
Sequence number
A CESoPSN packet contains the MPLS label, control word, RTP header, and TDM data.
MPLS Label
Control Word
The control word of a CESoPSN packet is 4-byte long and contains the following fields: l 0000: The 4 bits are generally set to all 0s. They are used to indicate the start of an Associated Channel Header (ACH). The ACH is needed if the state of the CESoPSN PW is monitored using virtual circuit connectivity verification (VCCV). L: This bit indicates whether the TDM data carried in a packet is valid. If set to 1, it indicates that the TDM data is omitted in order to conserve bandwidth. R: This bit indicates whether its local CE-side interworking function (IWF) is in the packet loss state. If set to 0, it indicates that a preconfigured number of consecutive packets are received. M: The 2 bits are used for alarm transparent transmission, indicating that the CE end or AC side of the uplink PE detects a critical alarm.
l l
Issue 02 (2011-01-20)
6 Packet Features
l l
RSV: The 2 bits are reserved. FRG: The 2 bits indicate fragmentation with the following values: 00: indicates that the entire TDM data is encapsulated in the packet. 01: indicates that the first fragmentation of the TDM data is encapsulated in the packet. 10: indicates that the last fragmentation of the TDM data is encapsulated in the packet. 11: indicates that the middle fragmentation of the TDM data is encapsulated in the packet.
LEN: The 6 bits indicate the length of the CESoPSN packet (including the CESoPSN header and TDM data). The minimum length of a transport unit on a PSN is 64 bytes. When a packet is shorter than 64 bytes, LEN indicates the actual length of the packet, representing padding bits. If a packet is longer than 64 bytes, LEN is set to all 0s. Sequence number: The 16 bits indicate the transmission sequence number of a CESoPSN packet. Its initial value is random, and is incremented by one with each CESoPSN data packet sent. If the sequence number of a packet reaches the maximum (65535), the sequence number of its next packet will start with the minimum. The sequence number can be in Huawei mode or standard mode. In Huawei mode, the minimum sequence number is 0; in standard mode, the minimum sequence number is 1.
RTP Header
The Real-time Transport Protocol (RTP) header is used to carry timestamp information to the remote end so that the packet clock can be restored. The RTP header is 12-byte long. The 32bit timestamp field in the RTP header represents the timestamp information. For the specific format of the RTP header, see RFC 3550.
NOTE
On the OptiX RTN 980, you can set whether the RTP header is encapsulated into the CESoPSN packet.
TDM Data
"TDM data" indicates TDM data payloads. When a PW packet is shorter than 64 bytes, fixed bits are padded to meet Ethernet transmission requirements. "Timeslot" indicates the timeslot in TDM frames. Each timeslot uses 8 bits. All the timeslots are encapsulated as TDM data payloads (excluding the CRC bit). The number of encapsulated frames and the number of timeslots in each frame can be set as required.
NOTE
On the OptiX RTN 980: CESoPSN does not encapsulate timeslot 0 of E1 into the payload, and the remote PE restructure the timeslots.
The amount of E1 frames that are encapsulated in a PW packet is determined by Packet Loading Time. Packet Loading Time indicates the duration for a PW packet to load TDM frames, and therefore limits the number of loaded TDM frames. The period of a TDM frame is 125 s. As a result, if the packet loading time is 1 ms, each PW packet loads eight TDM frames.
6.6.2.4 Data Jitter Buffer

After CES packets are transmitted over a PSN, the intervals between packet arrivals may be different and the packets may be misordered. To ensure that the TDM bit streams can be reconstructed on the egress PE, a jitter buffer is required to smooth the intervals between packet arrivals and to reorder the misordered packets.
6 Packet Features
Figure 6-43 shows the working principle of the data jitter buffer. Figure 6-43 Working principle of the data jitter buffer
1 Ingress queue Write Data packets in order n Queue tail 6 5 4 3 2 1 Queue head 0 Egress queue
Read
2 Ingress queue
Write Data packets not in order n Queue tail 6 5 4 0 2 1 Queue head 3 Egress queue
Read
The data jitter buffer works as follows: l The data jitter buffer enables the packets to enter the queue in the order that the packets arrive at the interface. At the same time, data jitter buffer enables the packets to leave the queue in the order that the packets enter the queue. When the packets are received with consecutive sequence numbers, the write pointer writes data into the queue, beginning at the tail of the queue; the read pointer reads data from the queue, beginning at the head of the queue. When the received packets are misordered, the read pointer automatically accommodates to reading packets in the correct order.
The size of the data jitter buffer can be set as required. A low-capacity jitter buffer easily overflows, and as a result data may be lost at different degrees; a high-capacity jitter buffer can absorb jitters resulting from larger packet transmission intervals on the network, but a large delay may be generated when the TDM bit streams are reconstructed. Therefore, during service deployment, you need to properly configure the data jitter buffer based on the actual network delay and jitter conditions.
6.6.2.5 CES Alarm Transparent Transmission

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

Figure 6-44 shows the CES alarm transparent transmission can be between AC sides.
6 Packet Features
Figure 6-44 CES alarm transparent transmission between AC sides
PSN
AC1 NodeB PW PE1 LSP PE2 S-VLAN: 200 AC2
RNC
The service alarms on the AC side are transparently transmitted through the PSN as follows: When receiving TDM signals carrying AIS/RAI alarms from AC1 side, PE1 uses the L or M field in the control word to respectively transmit AIS and RAI alarms to PE2. Then, PE2 inserts AIS/RAI alarms into AC2 based on the received L or M field.
NOTE
The SAToP encapsulation mode does not support the M field, and therefore cannot transparently transmit the RAI alarm.
The fault information on the AC link or port is transmitted to the remote AC as follows: When detecting an AC link fault or E1 port fault in AC1, PE1 uses the L field in the control word to transmit the fault information to PE2. Then, PE2 inserts alarms into AC2 based on the received L or M fields.
CES Alarm Transparent Transmission from the NNI Side to the AC Side
Figure 6-45 shows the CES alarm transparent transmission from the NNI side to the AC side. Figure 6-45 CES alarm transparent transmission from the NNI side to the AC side
PSN
AC1 NodeB PW PE1 LSP PE2 S-VLAN: 200 AC2
RNC
When detecting that packet loss ratio continuously beyond the preset threshold, PE2 inserts the AIS alarm into AC2, and uses the R field in the control word to transmit the information to PE1. Then, PE1 reports the RDI alarm based on the R field, and inserts the RAI alarm into the AC1 side.
6 Packet Features
6.6.2.6 Clock Recovery Schemes of TDM PWE3

When clocks need to be transmitted with CES services, you can adopt CES retiming or CES adaptive clock recovery (ACR) as required.
CES Retiming
CES retiming is an approach to reduce signal jitter after CES services traverse a transmission network. It combines the timing reference signal and CES service signal for transmission. Therefore, the transmitted CES service signal carries the timing information that is synchronized with the timing reference signal. CES retiming is applicable when the following conditions are met: l l All the clocks on the PSN are synchronous. All the clocks on the PSN are synchronized with the clock of the incoming service.
Figure 6-46 shows a clock solution wherein the BSC transmits synchronization information to the BTS over the PSN with CES retiming enabled. In this solution: l PE1 receives an E1 service from the BSC, and extracts the clock from the CES service (the E1 service is emulated into the CES service after entering the PSN). The extracted clock functions as the primary reference clock, and is traced by the other NEs on the PSN. In this manner, all the clocks on the PSN are synchronized with the clock of the BSC. CES retiming is enabled on PE2 so that the system clock of PE2 can be carried in the E1 service sent to the BTS (the CES service is restored to the E1 service after leaving the PSN). The clock of PE2 is synchronized with that of the BSC, so the BTS can extract the clock of the BSC from the received E1 service.
Figure 6-46 Principles of CES retiming
PSN
E1 service E1 service
CE1 (BSC)
PE1
LSP
PE2
CE2 (BTS)
Read clock (System clock) Clock CES service Packet transmission equipment E1 service FIFO E1 service
CES retiming is implemented as follows: The E1 bit streams restored from the CES service are written into a First In, First Out (FIFO) queue, and then are read out from the FIFO queue by using the retiming clock. The output signal contains the retiming clock; therefore, it is synchronized with the primary reference clock, with the jitter and wander in the original E1 service absorbed by the data jitter buffer.
6 Packet Features
CES ACR
CES ACR is a technology wherein the CES service is used to restore the clock of the source end in an adaptive manner. The sink end recovers the clock based on the packet received on its NNI side. l l All the clocks on the PSN are not synchronous. All the clocks on the PSN are synchronous, but the clocks on the PSN are not synchronized with the clock of the incoming service.
For the principle and implementation process of CES ACR, see 7.2 CES ACR.
6.6.2.7 QoS of TDM PWE3

The QoS of TDM services features low delay, low jitter, and fixed bandwidth. Therefore, a high enough per-hop behavior (PHB) level needs to be assigned to CES packets. The OptiX RTN 980 performs QoS for TDM PWE3 packets as follows. l Ingress node The PHB service class of a TDM PWE3 packet can be manually specified (the PHB service class is set to EF, by default). When a packet leaves an ingress node, the EXP value of the packet is determined according to the mapping (between PHB service classes and EXP values) defined by the DiffServ domain of the egress port. l Transit node When a packet enters a transit node, the PHB service class of the packet is determined according to the mapping (between EXP values and PHB service classes) defined by the DiffServ domain of the ingress port. When a packet leaves a transit node, the EXP value of the packet is determined according to the mapping (between PHB service classes and EXP values) defined by the DiffServ domain of the egress port.
NOTE
When an MPLS tunnel uses a manually specified EXP value, the EXP value of TDM PWE3 packets is fixed, not affected by a DiffServ domain.
In addition, the OptiX RTN 980 supports the CES CAC function. If bandwidth resources are insufficient when CES services are created, the services cannot be created and the system will display a prompt message.
NOTE
l To enable the CES CAC function, set the bandwidth of tunnel carrying CES services, and PW bandwidth of other PWE3 services carried on the tunnel. l If CES services are transmitted on the ISU2/ISX2, set the PHB service class to CS7 to decrease the CES service transmission delay and jitters.
This section describes the specifications for TDM PWE3. Table 6-32 lists the specifications for TDM PWE3.
6-90
Issue 02 (2011-01-20)
6 Packet Features
Table 6-32 Specifications for TDM PWE3 Item Maximum number of CES services Specifications l MD1: 32 l ML1: 16 Emulation mode l SAToP l CESoPSN Timing mode l CES ACR l CES retiming Jitter buffer time Packet loading time Enabling the encapsulation of RTP packet header CAC Padding the idle timeslot in 8-bit pattern 375 us to 16000 us, in steps of 125 us 125 us to 5000 us, in steps of 125 us Supported Supported Supported
NOTE This mode is used for padding the idle timeslot on the remote PE when the emulation mode is CESoPSN.
Service type Fractional E1 MS-PW PW OAM PW APS VCCV PW ping/traceroute
Point-to-point service (One service port corresponds to one PW.) Supported Supported Supported Supported Supported Supported

This section describes the standards and protocols associated with TDM PWE3. The following standards and protocols are associated with TDM PWE3: l l l IETF RFC 3550: RTP: A Transport Protocol for Real-Time Applications IETF RFC 4197: Requirements for Edge-to-Edge Emulation of Time Division Multiplexed (TDM) Circuits over Packet Switching Networks IETF RFC 4553: Structure-Agnostic Time Division Multiplexing (TDM) over Packet (SAToP)
Issue 02 (2011-01-20)
6-91
6 Packet Features
l l
IETF RFC 5086: Structure-Aware Time Division Multiplexed (TDM) Circuit Emulation Service over Packet Switched Network (CESoPSN) ITU-T G.704: Synchronous frame structures used at 1544, 6312, 2048, 8448 and 44 736 kbit/s hierarchical levels
6.6.5 Availability
This section describes the support required by the application of the TDM PWE3 feature and its dependencies.

Table 6-33 Hardware and version support Feature TDM PWE3 Applicable Board ML1 MD1 Applicable Hardware Version All the versions All the versions Applicable Product Version V100R003C00 and later V100R003C00 and later
The dependencies between the TDM PWE3 feature and other features are as follows: l l l l l TDM PWE3 supports PWE3 OAM. TDM PWE3 supports PWE3 APS. TDM PWE3 supports PW ping/traceroute. TDM PWE3 supports MS-PW. TDM PWE3 supports VCCV.
6.6.6 Principles
This section describes the principles of TDM PWE3. As shown in Figure 6-47, the PE device uses 6.6.2.3 CESoPSN to emulate native TDM services. 6.6.2.2 SAToP uses a similar encapsulation process, but does not identify the E1 frame format or process the timeslots of the E1 frame.
6-92
Issue 02 (2011-01-20)
6 Packet Features
Figure 6-47 Principles of TDM PWE3 services (CESoPSN mode)

Framed E1
-Service TS Idle TS
PSN
LSP
AC CE1 (BTS) PE1
PW PE2
AC CE2 (BSC)
Native TDM service
TDM PWE3
Native TDM service
Framed E1
TDM PWE3 packet
The local PE (PE1) forwards packets as follows: 1. 2. 3. 4. Extracts the E1 bit streams that are transmitted by CE1 from the AC. Segments the E1 bit streams, with a specified number of E1 frames contained in each segmentation. Extracts valid payloads from the specified timeslots in each segment, and encapsulates the valid payloads into a PWE3 packet in standard format. Maps the PWE3 packets to an LSP for transmission.
The remote PE (PE2) forwards packets as follows: 1. 2. 3. Demultiplexes the PW from the LSP. Extracts the valid payloads from the PWE3 packets carried on the PW. Restores E1 frames based on the valid payloads (the unused timeslots are padded based on the preconfigured 8-bit pattern), and reconstructs the E1 bit streams.
NOTE
Timeslot 0 is not padded based on the preconfigured 8-bit pattern, but is regenerated based on the preconfigured PCM format.
4. 5.
Forwards the E1 bit streams to CE2 over the AC. Combines the CES clocks into bit streams.

The port attributes of a UNI port are configured during the configuration of TDM PWE3.

Figure 6-48 provides the procedures for configuring CES services on a single NE.
Issue 02 (2011-01-20)
6-93
6 Packet Features
Figure 6-48 Configuration flow chart

Mandatory Optional Configure UNI ports Start
Configure CES services
Configure PW APS
Verify CES services
End
Setting the Attributes of UNI Ports

Setting the attributes of UNI ports carrying CES services mainly involves setting the attributes of Smart E1 ports. Table 6-34 Setting the attributes of UNI ports Operation Setting the attributes of Smart E1 ports A.5.4.1 Setting Basic Attributes of Smart E1 Ports A.5.4.2 Setting Advanced Attributes of Smart E1 Ports Remarks Required. Set the parameters as follows: Set Port Mode to Layer 1.
Optional. Set the parameters as follows: l When PW Type is CESoPSN, set Frame Format to CRC-4 Multiframe or Double Frame as planned. The value CRC-4 Multiframe is recommended for securing transmission quality. When PW Type is SAToP, set Frame Format to Unframe. l Set Frame Mode to PCM31. If Frame Mode of the opposite end is PCM30, you need to configure timeslot 16 in addition to the timeslots carrying services.
6-94
Issue 02 (2011-01-20)

NOTE
6 Packet Features
When E1 ports on the MP1 board are used as Smart E1 port for transmitting packet services, ensure that Service Mode of the E1 ports is CES (default value).
Configuring CES Services

Table 6-35 Configuring CES services Operation A.7.6.1 Creating CES Services Setting the general attributes of services Remarks Required. Set the parameters as follows: l Set Service ID(e.g.1,3-6), Service name, Source Board, Source Low Channel(e.g.1,3-6), and Source 64K Timeslot(e.g.1,3-6) according to service planning information. Source 64K Timeslot(e.g.1,3-6) is valid only for the CESoPSN mode. If the Frame Mode at the opposite end is set to PCM30, the source 64 kbit/s timeslots at the local end must include the 16th timeslot. l Set Priority List. Priority List indicates the PHB service class for CES services. The default PHB service class for CES services is EF. If CES services are transmitted on the ISU2/ISX2, set the PHB service class to CS7 to decrease the CES service transmission delay and jitters. l Set Mode to UNI-NNI.
Issue 02 (2011-01-20)
6-95
6 Packet Features
Operation Configuring PWs
Remarks l Required. Set the basic attributes of PWs. Set PW ID according to planning information. Set PW Type according to planning information. If PCM timeslots are used for service access, select CESoPSN; otherwise, select SAToP. For Fractional E1, select CESoPSN. Set PW Ingress Label/Source Port and PW Egress Label/ Sink Port according to planning information. Select the Tunnel according to planning information. For a unidirectional tunnel, select or create an egress tunnel. l Optional. Set advanced attributes of PWs. Advanced attributes of PWs take their default values.
Procedure for Configuring PW Protection

For details about how to configure PW protection, see 6.11.7 Configuration Procedure in 6.11 PW APS of the Feature Description.
Verifying CES Services

Table 6-36 Verifying CES services Operation A.11.2 Testing the E1 Service by Using a BER Tester Remarks Test CES services at each E1 port by using BER testers. The BER testers that support Nx64 kbit/s are required to test CES services in CESoPSN mode.

This section uses an example to describe how to plan and configure TDM PWE3 according to network conditions.
6 Packet Features
l l l
For the configuration example of common CES services, see Configuration Example (Common CES Services) in the Configuration Guide. For the configuration example of Fractional CES services, see Configuration Example (Fractional CES Services) in the Configuration Guide. For the configuration example of CES services on MS-PWs, see Configuration Example (MS-PW-based CES Services) in the Configuration Guide.

Related Tasks
A.5.4.1 Setting Basic Attributes of Smart E1 Ports A.5.4.2 Setting Advanced Attributes of Smart E1 Ports A.7.6.1 Creating CES Services A.7.6.2 Modifying CES Service Parameters A.7.6.3 Querying CES Service Information A.7.6.4 Deleting a CES Service.

When an exception is detected in the TDM PWE3 packet, an NE reports the specific alarm.
Relevant Alarms
l CES_JTROVR_EXC The CES_JTROVR_EXC alarm indicates that the number of overflows in the jitter buffer exceeds the threshold. This alarm is reported when the board detects that the number of overflows in the jitter buffer exceeds the threshold within a period of 1s. l CES_JTRUDR_EXC The CES_JTRUDR_EXC alarm indicates that the number of underflows in the jitter buffer exceeds the threshold. This alarm is reported when the board detects that the number of underflows in the jitter buffer exceeds the threshold within a period of 1s. l CES_LOSPKT_EXC The CES_LOSPKT_EXC alarm indicates that the number of lost CES packets exceeds the threshold. This alarm is reported when the board detects that the number of lost CES packets exceeds the threshold within a period of 1s. l CES_MALPKT_EXC The CES_MALPKT_EXC alarm indicates that the number of malformed CES packets exceeds the threshold. This alarm is reported when the board detects that the number of malformed CES packets exceeds the threshold within a period of 1s. l CES_MISORDERPKT_EXC The CES_MISORDERPKT_EXC alarm indicates that the number of disordered CES packets exceeds the threshold. This alarm is reported when the board detects that the number of disordered CES packets exceeds the threshold within a period of 1s. l CES_RDI The CES_RDI alarm indicates a fault in the received service at the remote end. When the packet loss ratio exceeds the threshold, the remote end sets the R bit in the control word to
6 Packet Features
1. Then, when receiving a packet in which R = 1 in the control word, the local end reports this alarm. l CES_STRAYPKT_EXC The CES_STRAYPKT_EXC alarm indicates that the number of errored CES packets exceeds the threshold. This alarm is reported when the board detects that the number of errored CES packets exceeds the threshold within a period of 1s. l CESPW_OPPOSITE_ACFAULT The CESPW_OPPOSITE_ACFAULT alarm indicates that the AC at the remote end is faulty. When detecting a fault in the AC, the remote end sets the L bit in the control word to 1. Then, when receiving a packet in which L = 1 in the control word, the local end reports this alarm. l CESPW_OPPOSITE_RAI The CESPW_OPPOSITE_RAI alarm is a remote alarm indication of the remote end. When receiving the RAI alarm, the remote end sets the L bit in the control word to 0, and the M bit in the control word to 10. Then, when receiving a packet in which L = 0 and M = 10 in the control word, the local end reports this alarm.
Relevant Events
None.
6.6.11 FAQs
This section provides answers to the questions that are frequently raised when TDM PWE3 is used. Question: How is timeslot 0 in E1 of the CES service processed? Answer: The OptiX RTN 980 processes it as follows: l l If SAToP is used, the equipment transparently transmits timeslot 0 of E1. If CESoPSN is used, the equipment does not encapsulate timeslot 0 of E1 into the payload, and the remote PE restructures the timeslot.
Question: How to configure CES services in CESoPSN mode if E1 frames are PCM30? Answer: If E1 frames are PCM30, take note of the following: l l The frame mode of the local E1 port must be PCM31. Timeslot 16 must be bound for the configuration of CES services.
Question: How to calculate the transmission efficiency of a CES service? Answer: You can calculate the transmission efficiency of a CES service as follows:a Transmission efficiency = Payload length/(Payload length + PWE3 overhead length + Ethernet Layer 2 overhead length) l Payload length = Packet loading time (s)/125(s) x N N is equal to 32 when SAToP is used. N is equal to the number of timeslots in each TDM frame when CESoPSN is used. The packet loading time is 1000 s by default. l PWE3 overhead length = MPLS label length + PW label length + CW length + RTP header length
6-98
6 Packet Features
An MPLS label, PW label, CW, and RTP header are all four bytes. By default, a CES packet does not contain an RTP header. Therefore, the PWE3 overhead is 12 bytes by default. l Ethernet Layer 2 overhead length = Ethernet frame header length + FCS length An untagged Ethernet frame header is 14 bytes. A tagged Ethernet frame header is 18 bytes. An FCS is 4 bytes. By default, an Ethernet packet carrying the MPLS packet is tagged. Therefore, the Ethernet Layer 2 overhead is 22 bytes. By default, CES service transmission efficiency = 8 x N/(8 x N + 34) Assuming that 15 service timeslots are transmitted in CESoPSN mode, the payload transmission efficiency is 8 x 15/(8 x 15 + 34) = 77.9%. Assuming 15 service timeslots are transmitted in Native E1 mode, the payload transmission efficiency is 15/32 = 46.9%.
NOTE
When CES services are transmitted over radio links or Ethernet links, the CES service transmission efficiency pertains to the efficiency of physical links transmitting Ethernet frames.
6.7 ATM PWE3

This chapter describes the ATM PWE3 feature. 6.7.1 Introduction This section provides the definition of ATM PWE3 and describes its purpose. 6.7.2 Basic Concepts This section describes the basic concepts associated with ATM PWE3. 6.7.3 Specifications This section describes the specifications for ATM PWE3. 6.7.4 Reference Standards and Protocols This section describes the standards and protocols associated with ATM PWE3. 6.7.5 Availability This section describes the support required by the application of the ATM PWE3 feature and its dependencies. 6.7.6 Principles This section describes the principles of ATM PWE3. 6.7.7 Configuration Procedure The port attributes of a UNI port are configured when ATM PWE3 is configured. 6.7.8 Configuration Example This section uses an example to describe how to plan and configure ATM PWE3 according to network conditions. 6.7.9 Task Collection This section provides the hyperlinks of the operation tasks associated with the feature. 6.7.10 Relevant Alarms and Events
6 Packet Features
When detecting an exception by performing ATM PWE3 operations, an NE reports the specific alarm. 6.7.11 FAQs This section provides answers to the questions that are frequently raised when ATM PWE3 is used.
6.7.1 Introduction
This section provides the definition of ATM PWE3 and describes its purpose.
Definition
The ATM PWE3 technology emulates the basic behaviors and characteristics of ATM services on a packet switched network (PSN) by using the PWE3 mechanism, so that the emulated ATM services can be transmitted on a PSN.
Purpose
Aided by the ATM PWE3 technology, conventional ATM networks can be connected by a PSN. Specifically, ATM PWE3 allows transmitting conventional ATM services over a PSN by emulating the ATM services. The networking type of ATM PWE3 can be one-to-one or N-to-one depending on the encapsulation type of ATM PWE3 packets. It is obvious that ATM PWE3 helps to transmit ATM services over the PSN, without adding ATM equipment or changing the configuration of the ATM CE equipment. Figure 6-49 Typical application of ATM PWE3 (in the one-to-one encapsulation mode)
PSN PW AC CE1 PE1 AC LSP PE2 CE2
ATM PWE3 1-to-1 ATM PWE3 service 1-to-1 ATM PWE3 service
NodeB
RNC
6-100
Issue 02 (2011-01-20)
6 Packet Features
Figure 6-50 Typical application of ATM PWE3 (in the N-to-one encapsulation mode)
CE1 PSN PW AC CE2 PE1 AC LSP PE2 CE4
ATM PWE3 N-to-1 ATM PWE3 service N-to-1 ATM PWE3 service
CE3
NodeB
RNC
NOTE
The cell encapsulation modes at both ends of a PW must be the same.

This section describes the basic concepts associated with ATM PWE3. 6.7.2.1 ATM N-to-One Cell Encapsulation The ATM N-to-one cell encapsulation modes are classified into N-to-one VPC and N-to-one VCC. In N-to-one VPC mode, one PW carries one or more VPCs; in N-to-one VCC mode, one PW carries one or more VCCs. 6.7.2.2 ATM One-to-One Cell Encapsulation ATM one-to-one cell encapsulation modes are classified into one-to-one VPC and one-to-one VCC. In one-to-one VPC mode, one PW carries one VPC; in one-to-one VCC mode, one PW carries one VCC. The two modes adopt different encapsulation modes. 6.7.2.3 Number of ATM Cells Encapsulated in PWE3 Packets The number of ATM cells encapsulated in PWE3 packets is determined by the parameters Maximum Number of Concatenated Cells and Loading Time. 6.7.2.4 QoS of ATM PWE3 The QoS requirements depend on the category of the ATM service. As such, set the PHB service level of an ATM PWE3 packet based on the category of the emulated ATM service to ensure specific QoS objectives.
Issue 02 (2011-01-20)
6-101
6 Packet Features
6.7.2.1 ATM N-to-One Cell Encapsulation

The ATM N-to-one cell encapsulation modes are classified into N-to-one VPC and N-to-one VCC. In N-to-one VPC mode, one PW carries one or more VPCs; in N-to-one VCC mode, one PW carries one or more VCCs. Figure 6-51 shows the ATM N-to-one cell encapsulation. The PWE3 packet contains the MPLS label, control word, and payload. Figure 6-51 ATM N-to-one cell encapsulation
0 Tunnel label PW label 0000 Flags Rsv Length VPI 20 23 24 EXP EX P EXP S S S TTL TT L TTL 31bit
Sequence number VCI PTI C
ATM cell payload (48 bytes)
. . .
Concatenated cells VCI PTI C
VPI
ATM cell payload (48 bytes)
. . .
MPLS label Control word (optional) ATM service payload
Format of the MPLS Label

Control Word
The meanings of the fields in the control word are as follows: l l l
6-102
Flags: This field has a length of 4 bits. The 4 bits are not used and are set to 0s. Rsv: This field has a length of 2 bits. The 2 bits are reserved and are generally set to 0s. Length: This field has a length of 6 bits. The 6 bits are not used and are set to 0s.
6 Packet Features
Sequence number: This field has a length of 16 bits. It is optional and used to guarantee ordered packet delivery. If the 16 bits are set to 0s, the algorithm for checking sequence numbers is not used.
ATM Service Payload

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

ATM one-to-one cell encapsulation modes are classified into one-to-one VPC and one-to-one VCC. In one-to-one VPC mode, one PW carries one VPC; in one-to-one VCC mode, one PW carries one VCC. The two modes adopt different encapsulation modes. Figure 6-52 shows the encapsulation modes of one-to-one VPC and one-to-one VCC, including the MPLS label, control word, ATM specific, and payload. ATM specific contains control information required by the ATM service. ATM specific may be longer than one byte, which is determined by the type of ATM service.
Issue 02 (2011-01-20)
6-103
6 Packet Features
Figure 6-52 ATM one-to-one cell encapsulation

1-to-1 VCC ATM
Control Word Required 0 Tunnel label PW label 0000 Rsv 20 23 24 EXP S EX S EXP P S TTL TT TTL L 0000 31bit 0 Tunnel label PW label Rsv VCI ATM cell payload (48 bytes) . . . M V Rsv PTI C ATM cell payload (48 bytes) . . . VCI ATM cell payload (48 bytes) . . . ATM cell payload (48 bytes) M VRsv PTI C VCI
1-to-1 VPC ATM

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

NOTE
6 Packet Features
The VCC is an ATM connection mode that is based on the VCI value of the ATM cell header. That is, it does not use the VCI field ( V = 0). VPC is an ATM connection mode that is based on the VPI value of the ATM cell header. That is, each cell contains the VCI field (V = 1).
l l
Rsv: This field has a length of 2 bits. The 2 bits are reserved and are generally set to 0. PTI: This field indicates the bit payload type identifier and has a length of 3 bits. The ingress PE copies the PTI field contained in the ATM service payload of the incoming ATM cell into this field. C: This field indicates the cell loss priority (CLP) and has a length of 1 bit. The C field is used for congestion control. When the network becomes congested, cells with CLP = 1 are discarded first. The ingress PE copies the CLP field contained in the ATM service payload of the incoming ATM cell into this field.
ATM Service Payload

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

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

The QoS requirements depend on the category of the ATM service. As such, set the PHB service level of an ATM PWE3 packet based on the category of the emulated ATM service to ensure specific QoS objectives. Specify an appropriate PHB service level for an ATM service based on its category. The following table provides the default mapping relationships between ATM service categories and PHB service levels. Table 6-37 Mapping relationships between ATM service categories and PHB service levels ATM Service Category CBR rt-VBR nrt-VBR UBR+ UBR PORT-TRANS PHB Service Level EF AF3 AF2 AF1 BE BE
The OptiX RTN 980 performs QoS for ATM PWE3 packets as follows. l Ingress node The PHB service class of an ATM PWE3 packet can be manually specified. When a packet leaves an ingress node, the EXP value of the packet is determined according to the mapping (between PHB service classes and EXP values) defined by the DiffServ domain of the egress port. l Transit node When a packet enters a transit node, the PHB service class of the packet is determined according to the mapping (between EXP values and PHB service classes) defined by the DiffServ domain of the ingress port. When a packet leaves a transit node, the EXP value of the packet is determined according to the mapping (between PHB service classes and EXP values) defined by the DiffServ domain of the egress port.
NOTE
When an MPLS tunnel uses a manually specified EXP value, the EXP value of ATM PWE3 packets is fixed, not affected by a DiffServ domain.
This section describes the specifications for ATM PWE3. Table 6-38 lists the specifications for ATM PWE3.
6 Packet Features
Table 6-38 Specifications for ATM PWE3 Item Service type Specifications l Point-to-point service based on ATM connections. That is, several ATM connections on one service port correspond to one PW. l Convergence service based on ATM connections. That is, several ATM connections on different service ports correspond to one PW. l ATM transparent transmission service based on port. That is, all the ATM connections on one port correspond to one PW. Service access mode l ATM l IMA l Fractional ATM l Fractional IMA Maximum number of ATM services supported by one board Maximum number of ATM connections supported by one board Maximum number of ATM connections carried by one PW Encapsulation type 64 256 32 ATM N-to-one VCC cell encapsulation ATM N-to-one VPC cell encapsulation ATM one-to-one VCC cell encapsulation ATM one-to-one VPC cell encapsulation Maximum number of concatenated ATM cells ATM cell concatenation waiting time ATM traffic management 31 100 s to 50000 s, in steps of 100 s Supported
MS-PW PW OAM PW APS
Supported Supported Supported
Issue 02 (2011-01-20)
6-107
6 Packet Features
Item VCCV
NOTE Valid when the control word is encapsulated in ATM PWE3 packets
PW ping/traceroute
Supported
NOTE Valid when the control word is encapsulated in ATM PWE3 packets

This section describes the standards and protocols associated with ATM PWE3. The following standard is associated with ATM PWE3: IETF RFC 4717: Definitions of Textual Conventions and Object-identities for ATM Management
6.7.5 Availability
This section describes the support required by the application of the ATM PWE3 feature and its dependencies.

Table 6-39 Hardware and version support Feature ATM PWE3 Applicable Board ML1 MD1 Applicable Hardware Version All the versions All the versions Applicable Product Version V100R003C00 and late V100R003C00 and late
The dependencies between the ATM PWE3 feature and other features are as follows: l l l l l
6-108
ATM PWE3 services can be carried by a single link or an IMA group. ATM PWE3 supports ATM traffic management. ATM PWE3 supports PWE3 OAM. ATM PWE3 supports PWE3 APS. ATM PWE3 supports MS-PW.
6 Packet Features
l l
PW ping/traceroute is supported when the control word is encapsulated in ATM PWE3 packets. VCCV is supported when the control word is encapsulated in ATM PWE3 packets.
6.7.6 Principles
This section describes the principles of ATM PWE3.
NOTE
The ATM PWE3 in the encapsulation format of one-to-one VPC can be replaced by the ATM PWE3 in the encapsulation format of N-to-one VPC; the ATM PWE3 in the encapsulation format of one-to-one VCC can be replaced by the ATM PWE3 in the encapsulation format of N-to-one VCC. This section considers the ATM PWE3 in the encapsulation format of N-to-one VCC as an example, which functions as a reference for the other ATM types.
In the scenario as shown in Figure 6-53, the PEs emulate Ethernet services in the encapsulation format of N-to-one VCC. Figure 6-53 Principles of the ATM PWE3 service (N-to-one VCC)
VPI=10 VCI=10
VPI=20 VCI=20 CE1 AC PW AC AC PE1 LSP PE2 VPI=21 VCI=21 MPLS Label CE2 VPI=11 VCI=11 ATM control word ATM service payload PSN CE3
Packet transmission equipment NodeB RNC ATM service ATM PWE3 service
Issue 02 (2011-01-20)
6-109
6 Packet Features
The local PE (PE1) forwards packets as follows: 1. 2. 3. 4. 5. Extracts the ATM service packets that are transmitted by CE1 and CE2 from the ACs. Pre-processes the service payloads prior to PWE3, including set-up of the ATM connections and QoS policies between CE1 and PE1, and between CE2 and PE1. Maps ATM service payloads to the corresponding PW. Encapsulates the ATM services into PWE3 packets in standard format. Maps the PW into the LSP for transmission.
The remote PE (PE2) forwards packets as follows: 1. 2. 3. 4. Demultiplexes the PW from the LSP. Decapsulates the PW, and extracts service payloads from the PW. Restores the ATM services based on the service payloads. Selects the AC for forwarding packets, performs corresponding QoS processing, and forwards the ATM service cells to CE3, based on the created ATM connections and QoS policies between PE2 and CE3.

The port attributes of a UNI port are configured when ATM PWE3 is configured.

The procedure for configuring ATM/IMA E1 services is different from the procedure for configuring Fractional ATM/IMA services. See Figure 6-54.
6-110
Issue 02 (2011-01-20)
6 Packet Features
Figure 6-54 Configuration flow chart (ATM services on a per-NE basis)

Flow chart for configuring ATM/IMA E1 services Required Optional Start Flow chart for configuring Fractional ATM/IMA services Start
Set UNI port attributes of ATM/IMA E1 services
Set UNI port attributes of Fractional E1 services
Configure IMA group information
Configure IMA group information
Configure ATM QoS
Configure ATM QoS
Configure ATM services
Configure ATM services
Configure PW APS
Configure PW APS
Verify ATM service configurations
Verify ATM service configurations
End
End
Setting UNI Port Attributes for ATM/IMA E1 Services

Table 6-40 Setting attributes of Smart E1 ports Operation Setting attributes of Smart E1 ports A.5.4.1 Setting Basic Attributes of Smart E1 Ports Description Required. Set the parameters as follows: l Set Name according to service planning information. l Set Port Mode to Layer 2.
Issue 02 (2011-01-20)
6-111
6 Packet Features
Operation A.5.4.2 Setting Advanced Attributes of Smart E1 Ports
Description Optional. Set the parameters as follows: Set Frame Format and Frame Mode according to service planning information. Ensure that the same frame mode is used at both ends. Normally, the port that transmits ATM/IMA services uses the CRC-4 multi-frame format and the PCM30 frame mode.
Setting UNI Port Attributes for Fractional E1 Services

Setting the UNI port attributes for Fractional E1 services involves setting Smart E1 port attributes, creating serial ports, and configuring serial ports. Table 6-41 Setting attributes of Smart E1 ports Operation Setting attributes of Smart E1 ports A.5.4.1 Setting Basic Attributes of Smart E1 Ports A.5.4.2 Setting Advanced Attributes of Smart E1 Ports Description Required. Set the parameters as follows: l Set Name according to service planning information. l Set Port Mode to Layer 1. Optional. Set the parameters as follows: Set Frame Format and Frame Mode according to service planning information. Ensure that the same frame mode is used at both ends. Normally, the port that transmits Fractional ATM services uses the CRC-4 multi-frame format and the PCM31 frame mode. Creating and configuring serial ports A.5.5.1 Creating Serial Ports Required. Set the parameters as follows: l Set the parameters according to service planning information. Port and Name Used Board and Used Port 64K Timeslot l Set Level to 64K Timeslot.
NOTE When the E1 frame mode is PCM30, timeslot 0 and timeslot 16 cannot be used to carry services. When the E1 frame mode is PCM31, timeslot 0 cannot be used to carry services.
A.5.5.2 Setting Basic Attributes of Serial Ports
Required. Set Port Mode to Layer 2.
6-112
Issue 02 (2011-01-20)
6 Packet Features
Setting IMA Group Information

Configuring IMA group information involves binding ATM trunks, configuring an IMA group, and configuring ATM ports. Table 6-42 Configuring an IMA group Operation A.7.7.1 Binding ATM TRUNKs Description Required. l For ATM/IMA services, set Level to E1. For Fractional E1 services, set Level to Fractional E1. l Set the other parameters according to service planning information.
NOTE When the E1 frame mode is PCM30, timeslot 16 cannot be bound to an ATM trunk.
A.7.7.2 Configuring an IMA group
Required. Set the parameters as follows: l Set IMA Protocol Enable Status. For ATM E1 and Fractional ATM, set IMA Protocol Enable Status to Disabled. For IMA E1 and Fractional IMA, set IMA Protocol Enable Status to Enabled. l Set Clock Mode of the local NE and the NE at the opposite end of the IMA trunk to be the same as Clock Mode of the interconnected BTS. l The other parameters are valid only for IMA E1 and Fractional IMA. Parameters must be set to the same values for equipment at both ends of an IMA link. It is recommended that the parameters take their default values.
A.7.7.3 Setting ATM Port Parameters
Optional. l Set Port Type and ATM Cell Payload Scrambling according to the type of access equipment. It is recommended that the parameters take their default values. The parameter values must be the same for both ends of a link. l The other parameters take their default values.
Configuring ATM QoS

Configuring ATM QoS involves configuring the ATM policy and configuring the CoS mapping table. For transparently transmitted ATM services, you do not need to configure the ATM traffic
6 Packet Features
management policy. For ATM connection-based services, the ATM traffic management policy must be configured. Table 6-43 Configuring ATM QoS Operation A.7.9.3 Creating an ATM Policy Description Required for services that are not transparently transmitted ATM services. Set parameters according to the type of the ATM service access equipment. l Set Policy ID. Alternatively, you can select Automatically Assign so that the policy ID is automatically assigned. l Select or assign a value for Policy Name. l Set Service Type according to service planning information. l Set Traffic Type and corresponding traffic parameters based on Service Type. l Set the enabled status of Discard Traffic Frame and UPC/NPC according to planning information. A.7.9.1 Creating an ATM-DiffServ Domain Required if "DefaultAtmCosMap" does not meet requirements. Set parameters according to service planning information.
6-114
Issue 02 (2011-01-20)
6 Packet Features
Configuring an ATM Service

Operation A.7.8.1 Creating ATM Services Setting service attributes Description Set the basic attributes for ATM services. Required. Set the parameters as follows: l Set Service ID and Service Name. l Set Service Type to UNIs-NNI. l Set Connection Type. If services are transmitted based on VP connections, set Connection Type to PVP. If services are transmitted based on VC connections, set Connection Type to PVC. If services are transparently transmitted over ports, set Connection Type to Port Transparent. Configuring ATM connections Creating ATM connections Required. Set connection parameters according to service planning information. l For ATM connection-based services, the connection parameters need to be configured. Uplink Policy and Down link Policy are specified for ATM connections during configuration of ATM policies. l For services transparently transmitted through ATM ports, only Source Board, Source Port, and PW ID need to be configured.
Issue 02 (2011-01-20)
6-115
6 Packet Features
Operation Configuring PWs
Description l Setting basic attributes of PWs Required. Set PW ID, PW Ingress Label / Source Port, and PW Egress Label / Sink Port according to service planning information. Set PW Type according to planning information. Select a value for Tunnel according to service planning information. For unidirectional tunnels, you also need to set Egress Tunnel. l Setting advanced attributes of PWs Optional. If Control Word is No Use, set Control Channel Type to Alert Label. Other advanced attributes generally take their default values. Advanced attributes of PWs take their default values. l Optional. Configure the QoS. The QoS parameters take their default values. Configuring CoS mapping Required if "DefaultAtmCosMap" does not meet requirements. Set CoS Mapping according to planning information. Set the mapping between PW ID and CoS Mapping. Select the policy for mapping different ATM service levels to CoS priorities. In this way, different quality levels are provided for different ATM services.

6-116
Issue 02 (2011-01-20)
6 Packet Features
Verifying ATM Service Configurations

Operation A.11.4 Testing the ATM Service Description Use the ATM OAM function to test ATM service connectivity.
NOTE For transparently transmitted ATM services, service verification needs to be conducted on the ATM service access equipment.

This section uses an example to describe how to plan and configure ATM PWE3 according to network conditions. For the configuration example of ATM PWE3, see Configuration Example (Common ATM Services), Configuration Example (Fractional ATM Services), Configuration Example (ATM Services on MS-PWs), and Configuration Example (Transparently Transmitted ATM Services) in the OptiX RTN 980Configuration Guide.

Related Tasks
A.7.8.1 Creating ATM Services A.7.8.2 Modifying ATM Service Parameters A.7.8.3 Querying ATM Services A.7.8.4 Deleting an ATM Service

When detecting an exception by performing ATM PWE3 operations, an NE reports the specific alarm.
Relevant Alarms
ATMPW_UNKNOWNCELL_EXC The ATMPW_UNKNOWNCELL_EXC is an alarm indicating that the number of unknown cells exceeds the specified threshold in a time unit. This alarm occurs when the board detects that, within a period (2.5s), the number of unknown cells crosses the specified threshold.

None.
6 Packet Features
6.7.11 FAQs
This section provides answers to the questions that are frequently raised when ATM PWE3 is used. Question: Why is the packet loss ratio of a high-priority ATM connection the same as that of a low-priority ATM connection in one PW? Answer: In the uplink direction, the ATM PWE3 mechanism grooms packets based on PW. That is, all the ATM connections in one PW have the same forwarding priority. Therefore, all the ATM connections in the PW have the same packet loss ratio. To differentiate between ATM connections with different traffic policies, configure the ATM connections into different PWs. Question: How to calculate PW traffic based on ATM traffic? Answer: The calculation pertains to the encapsulation type of ATM PWE3 services and whether the cells are concatenated. The calculation methods are as follows: l l If the ATM PWE3 encapsulation is ATM one-to-one VCC and no cell is concatenated, the ratio of the PW traffic to the encapsulated ATM traffic is 77.9%. If the ATM PWE3 encapsulation is ATM one-to-one VCC and the cells are concatenated, the ratio of the PW traffic to the encapsulated ATM traffic is N x 53/(19 + N x 49). N is the number of concatenated cells. If the ATM PWE3 encapsulation is ATM one-to-one VPC and no cells are concatenated, the ratio of the PW traffic to the encapsulated ATM traffic is 75.7%. If the ATM PWE3 encapsulation is ATM one-to-one VPC and the cells are concatenated, the ratio of the PW traffic to the encapsulated ATM traffic is N x 53/(19 + N x 51). N is the number of concatenated cells (N 31). If the ATM PWE3 encapsulation is ATM N-to-one VPC/VCC and no cells are concatenated, the ratio of the PW traffic to the encapsulated ATM traffic is 74.6%. If the ATM PWE3 encapsulation is ATM N-to-one VPC and the cells are concatenated, the ratio of the PW traffic to the encapsulated ATM traffic is N x 53/(19 + N x 52). N is the number of concatenated cells (N 31).
l l
l l
6.8 ETH PWE3

This chapter describes the ETH PWE3 feature. 6.8.1 Introduction This section provides the definition of ETH PWE3 and describes its purpose. 6.8.2 Basic Concepts This section describes the basic concepts associated with ETH PWE3. 6.8.3 Specifications This section describes the specifications for ETH PWE3. 6.8.4 Reference Standards and Protocols This section describes the standards and protocols associated with ETH PWE3. 6.8.5 Availability This section describes the support required by the application of the ETH PWE3 feature and its dependencies. 6.8.6 Principles
6 Packet Features
This section describes the principles of ETH PWE3. 6.8.7 Configuration Procedure The port attributes of a UNI port are configured during the configuration of ETH PWE3. 6.8.8 Configuration Example This section uses an example to describe how to plan and configure ETH PWE3 according to network conditions. 6.8.9 Task Collection This section provides the hyperlinks of the operation tasks associated with the feature. 6.8.10 Relevant Alarms and Events When an exception is detected in the ETH PWE3 packet, an NE reports the specific alarm. 6.8.11 FAQs This section provides answers to the questions that are frequently raised when ETH PWE3 is used.
6.8.1 Introduction
This section provides the definition of ETH PWE3 and describes its purpose.
Definition
The ETH PWE3 technology emulates the basic behaviors and characteristics of Ethernet services on a packet switched network (PSN) by using the PWE3 mechanism, so that the emulated Ethernet services can be transmitted on a PSN.
Purpose
ETH PWE3 aims to transmit Ethernet services over a PSN. Figure 6-55 shows the typical application of ETH PWE3. Figure 6-55 Typical application of ETH PWE3
PSN
PW CE1 (NodeB) AC PE1 Native Ethernet service AC LSP PE2 Native Ethernet service CE2 (RNC)
ETH PWE3
Ethernet frame
ETH PWE3 packet
For the Ethernet services carried on PWs that the OptiX RTN 980 supports, see 6.8.2.4 E-Line Services Carried on PWs.
6 Packet Features

This section describes the basic concepts associated with ETH PWE3. 6.8.2.1 Format of an ETH PWE3 Packet After an Ethernet frame is encapsulated into a PWE3 packet, the PWE3 packet contains the MPLS label, control word (optional), and payload. 6.8.2.2 Service-Delimiting Tag and PW Encapsulation Mode The service-delimiting tag and PW encapsulation mode are used to indicate how the outer layer of the C-/S-VLAN tag of an Ethernet packet is processed when the Ethernet packet is forwarded. 6.8.2.3 QoS of ETH PWE3 After being encapsulated into ETH PWE3 packets, Ethernet services still retain the original PHB service levels. 6.8.2.4 E-Line Services Carried on PWs For the E-Line service category, a PW can be used to carry Ethernet services on an Ethernet port. In this scenario, this type of Ethernet service is called the E-Line service carried on PWs.
6.8.2.1 Format of an ETH PWE3 Packet

After an Ethernet frame is encapsulated into a PWE3 packet, the PWE3 packet contains the MPLS label, control word (optional), and payload.
Packet Format
Figure 6-56 shows the format of an ETH PWE3 packet, consisting of the MPLS label, control word, and payload. Figure 6-56 Format of an ETH PWE3 packet
0 Tunnel label PW label 0000 Reserved 20 23 24 EXP EX P EXP S S S TTL TT L TTL 31bit
Sequence number Payload (Ethernet frame)
MPLS label Control word (optional) Payload
6-120
Issue 02 (2011-01-20)
6 Packet Features
MPLS Label
Control Word
The 4-byte control word within an ETH PWE3 packet is optional and contains the following fields: l l l 0000: This field indicates the first 4 bits and they must be set to 0. Reserved: This field has a length of 16 bits and is reserved. Sequence number: This field has a length of 16 bits and indicates the delivery sequence number of an ETH PWE3 packet. Its initial value is random, and is increased by one integer with each ETH PWE3 packet sent.
NOTE
The OptiX RTN 980 does not support the control word during the encapsulation of an ETH PWE3 packet.
Payload
The payload refers to the Ethernet frame that is encapsulated into an ETH PWE3 packet. One ETH PWE3 packet can encapsulate only one Ethernet frame. During the encapsulation, the preset PW Encapsulation Mode is adopted.
6.8.2.2 Service-Delimiting Tag and PW Encapsulation Mode

The service-delimiting tag and PW encapsulation mode are used to indicate how the outer layer of the C-/S-VLAN tag of an Ethernet packet is processed when the Ethernet packet is forwarded.
Service-Delimiting Tag
The service-delimiting tag is used to indicate the user access mode, that is, the encapsulation mode when the Ethernet service is received by the AC. Service-delimiting tags are classified into two categories: l User If the service-delimiting tag is User, the user access mode is Ethernet. In this case, the Ethernet frame that the CE sends to the PE does not carry a provider-tag (P-Tag). If the frame header contains the VLAN tag, the VLAN tag is the inner VLAN tag of the user packet, which is called user-tag (U-Tag). The PE does not identify or process a U-Tag. l Service If the service-delimiting tag is Service, the user access mode is VLAN. In this case, the Ethernet frame that the CE sends to the PE carries a provider-tag (P-Tag), which is provided for the carrier to differentiate users. The PE identifies and processes a P-Tag based on the PW encapsulation mode.
NOTE
l On the OptiX RTN 980, the supported service-delimiting tag is User. l The structure of a P-Tag is the same as that of an S-Tag.
Issue 02 (2011-01-20)
6-121
6 Packet Features
PW Encapsulation Mode
The PW encapsulation mode is used to indicate whether a P-Tag is added when an Ethernet frame is encapsulated into an ETH PWE3 packet. The PW encapsulation modes are classified into two categories: l Raw mode In this mode: When the service-delimiting tag is User, in the direction that an Ethernet frame enters the PW, the PE directly encapsulates the Ethernet frame into a PWE3 packet after receiving it from the AC; in the direction that an Ethernet frame leaves the PW, the PE decapsulates the Ethernet frame before transmitting it to the AC. When the service-delimiting tag is Service, in the direction that an Ethernet frame enters the PW, the PE strips the outer tag (P-Tag) of the Ethernet frame and encapsulates it into a PWE3 packet after receiving it from the AC; in the direction that an Ethernet frame leaves the PW, the PE decapsulates the Ethernet frame and adds a P-Tag before transmitting it to the AC. l Tagged mode In this mode: When the service-delimiting tag is User, in the direction that an Ethernet frame enters the PW, the PE adds a P-Tag and encapsulates the Ethernet frame into a PWE3 packet after receiving it from the AC (the added P-Tag is called request VLAN); in the direction that an Ethernet frame leaves the PW, the PE decapsulates the Ethernet frame and strips the P-Tag before transmitting it to the AC. When the service-delimiting tag is Service, in the direction that an Ethernet frame enters the PW, the PE directly encapsulates the Ethernet frame into a PWE3 packet after receiving it from the AC; in the direction that an Ethernet frame leaves the PW, the PE decapsulates the Ethernet frame before transmitting it to the AC.
NOTE
For the OptiX RTN 980, you can set a request VLAN value for each PW whose encapsulation mode is the Ethernet tagged mode, but the T-PID value in the request VLAN must be unique on the NE.
Typical Application
Figure 6-57 shows a NodeB backhaul network. l l The RNC can process S-VLAN tags. It allocates an S-VLAN ID to each NodeB to separate the services of a NodeB from those of another. The NodeB can process C-VLAN tags only. It allocates an C-VLAN ID to each type of service on a NodeB.
Therefore, the request VLAN function must be enabled to add S-VLAN IDs to isolate the services on different NodeBs. Set the request VLAN values on NE1 and NE2 as follows: l l If the PW1 encapsulation mode of NE1 is the tagged mode, set the request VLAN to 100; if PW2 encapsulation mode of NE1 is the tagged mode, set the request VLAN to 200. The PW1 and PW2 encapsulation mode of NE2 is the raw mode.
NE1 and NE2 process the services as follows:

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

PW1: tagged mode Request VLAN: 100 C-VLAN: 100-200 PSN NodeB 1 AC AC PW1 PW2 LSP PW1: raw mode PORT 1 S-VLAN: 100 AC AC NE2 S-VLAN: 200 C-VLAN: 100-200 NodeB 2 PW2: tagged mode Request VLAN: 200 Packet transmission equipment PW2: raw mode RNC
NE1
6.8.2.3 QoS of ETH PWE3

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

For the E-Line service category, a PW can be used to carry Ethernet services on an Ethernet port. In this scenario, this type of Ethernet service is called the E-Line service carried on PWs.
Service Mode
Table 6-44 defines the model of the E-Line services carried on PWs. Table 6-44 Model of the E-Line services carried on PWs Service Model Model 1 Service Flow PORT+CVLAN (source) PW (sink) Service Direction UNI-NNI Port Mode Layer 2 (source) Layer 3 (sink) Encapsulation Mode of Port IEEE 802.1q (source) - (sink) Service Description A UNI port processes the packets carrying a specific CVLAN ID based on its tag attribute, and then sends the packets to the NNI side for transmission on PWs. A UNI port processes the packets carrying a specific SVLAN ID based on its QinQ attribute, and then sends the packets to the NNI side for transmission on PWs.
Model 2
PORT+SVLAN (source) PW (sink)
UNI-NNI
Layer 2 (source) Layer 3 (sink)
QinQ (source) - (sink)
6-124
Issue 02 (2011-01-20)
6 Packet Features
Service Model Model 3
Service Flow PORT (source) PW (sink)
Service Direction UNI-NNI
Port Mode Layer 2 (source) Layer 3 (sink)
Encapsulation Mode of Port 802.1Q or QinQ (source) - (sink)
Service Description A UNI port processes the packets carrying a specific CVLAN ID based on its tag attribute or QinQ type domain, and then sends the packets to the NNI side for transmission on PWs.
Typical Application
Figure 6-58 shows the typical application of service model 1. Service 1 is present between the NodeB 1 and the RNC, and service 2 is present between the NodeB 2 and the RNC. The two services have different VLAN IDs and need to be transmitted over the PSN. On the UNI side of NE1, service 1 is transmitted to port 1 and service 2 is transmitted to port 2. On the NNI side of NE1, service 1 and service 2 are transmitted on different PWs. In this manner, the two services are separately transmitted. NE2 processes the two services in the same manner as NE1. Figure 6-58 Typical application of service model 1
Service 1 Port: 1(802.1Q) VLAN ID: 100 Service 1 Port: 1(802.1Q) VLAN ID: 100
PSN
NodeB 1 AC AC NE1 NodeB 2 UNI Service 2 Port: 2(802.1Q) VLAN ID: 200 Packet transmission equipment NNI PW1 PW2 LSP NNI NE2 UNI Service 2 Port: 2(802.1Q) VLAN ID: 200 AC AC RNC
Figure 6-59 shows the typical application of service model 2. Service 1 (QinQ service) is present between NodeB 1 and the RNC, and service 2 (QinQ service) is present between the NodeB 2
6 Packet Features
and the RNC. The two services have different S-VLAN IDs and need to be transmitted over the PSN. On the UNI side of NE1, service 1 is transmitted to port 1 and service 2 is transmitted to port 2. On the NNI side of NE1, service 1 and service 2 are transmitted on different PWs. In this manner, the two services are separately transmitted. NE2 processes the two services in the same manner as NE1. Figure 6-59 Typical application of service model 2
Service 1 Port: 1(QinQ) S-VLAN ID: 100 Service 1 Port: 1(QinQ) S-VLAN ID: 100
PSN
NodeB 1 AC AC NE1 NodeB 2 UNI Service 2 Port: 2(QinQ) S-VLAN ID: 200 Packet transmission equipment NNI PW1 PW2 LSP NNI NE2 UNI Service 2 Port: 2(QinQ) S-VLAN ID: 200 AC AC RNC
Figure 6-60 shows the typical application of service model 3. Service 1 (Ethernet service) is present between the NodeB 1 and the RNC, and service 2 (Ethernet service) is present between the NodeB 2 and the RNC. Service 1 carries various C-VLAN IDs, and service 2 carries various S-VLAN IDs. The two services need to be transmitted over the PSN. On the UNI side of NE1, service 1 is transmitted to port 1 and service 2 is transmitted to port 2. On the NNI side of NE1, service 1 and service 2 are transmitted on different PWs. In this manner, the two services are separately transmitted. NE2 processes the two services in the same manner as NE1.
6-126
Issue 02 (2011-01-20)
6 Packet Features
Figure 6-60 Typical application of service model 3

Service 1 Port: 1 (802.1Q) Service 1 Port: 1 (802.1Q)
PSN
NodeB 1 AC AC NE1 NodeB 2 UNI Service 2 Port: 2(QinQ) NNI PW1 PW2 LSP NNI NE2 UNI Service 2 Port: 2(QinQ) AC AC RNC
This section describes the specifications for ETH PWE3. Table 6-45 lists the specifications for ETH PWE3. Table 6-45 Specifications for ETH PWE3 Item Service type PW encapsulation mode Specifications E-Line service Raw mode Tagged mode Service flow type PORT+CVLAN PORT+SVLAN MS-PW PW OAM PW APS VCCV PW ping/traceroute Supported Supported Supported Supported Supported

This section describes the standards and protocols associated with ETH PWE3. The following standard is associated with ETH PWE3:
6 Packet Features
IETF RFC 4448: Encapsulation Methods for Transport of Ethernet over MPLS Networks
6.8.5 Availability
This section describes the support required by the application of the ETH PWE3 feature and its dependencies.

Table 6-46 Hardware and version support Feature ETH PWE3 Applicable Board CSHN IFU2 IFX2 ISU2 ISX2 EM6T EM6F Applicable Hardware Version All the versions All the versions All the versions All the versions All the versions All the versions All the versions Applicable Product Version V100R003C00 and later V100R003C00 and later V100R003C00 and later V100R003C00 and later V100R003C00 and later V100R003C00 and later V100R003C00 and later
The dependencies between the ETH PWE3 feature and other features are as follows: l l l l l ETH PWE3 supports PWE3 OAM. ETH PWE3 supports PWE3 APS. ETH PWE3 supports MS-PW. ETH PWE3 support VCCV. When IEEE 802.1ag OAM is used for ETH PWE3 packets, an MEP or MIP can only be created on a UNI port but not on an NNI port.
6.8.6 Principles
This section describes the principles of ETH PWE3. In the scenario as shown in Figure 6-61, the PE devices emulate Ethernet services.
6 Packet Features
Figure 6-61 Principles of ETH PWE3
PSN
PW CE1 (NodeB) AC PE1 Native Ethernet service AC LSP PE2 Native Ethernet service CE2 (RNC)
ETH PWE3
Ethernet frame
ETH PWE3 packet
The local PE (PE1) forwards packets as follows: 1. 2. 3. Extracts the Ethernet frames that are transmitted by CE1 from the AC. Encapsulates the Ethernet frames into PWE3 packets in standard format. Maps the PWE3 packets to an LSP for transmission.
The remote PE (PE2) forwards packets as follows: 1. 2. 3. Demultiplexes the PW from the LSP. Extracts Ethernet frames from the PWE3 packets carried on the PW. Forwards the Ethernet frames to CE2 over the AC.

The port attributes of a UNI port are configured during the configuration of ETH PWE3.

Figure 6-62 provides the procedures for configuring E-Line services carried PWs.
Issue 02 (2011-01-20)
6-129
6 Packet Features
Figure 6-62 Per-NE configuration flow chart (E-Line services carried on PWs)
Required Optional Configuring UNI Port Attributes Start
Configuring LAGs of UNI Ports
Configuring UNI-NNI E-Line Services Carried on PWs
Configuring PW Protection Groups
Configuring Affiliation Protection Pairs of PWs
Configurig QoS Policies
Verifying E-Line Service Configurations
End
6-130
Issue 02 (2011-01-20)
6 Packet Features
Procedure for Configuring UNI Port Attributes

Table 6-47 Procedure for configuring UNI port attributes Operation Setting attributes of Ethernet ports A.5.6.1 Setting the General Attributes of Ethernet Ports Description Required when an Ethernet port is enabled to access Ethernet services. Set the major parameters as follows: l In the case of used UNI ports, set Enable Port to Enabled. l Set Port Mode to Layer 2. l Set Encapsulation Type to 802.1Q. l In the case of an Ethernet port that is connected to external equipment (BTS or RNC), set Working Mode to be the same value as the external equipment (generally, the working mode of the external equipment is autonegotiation). In the case of an Ethernet port within the network, set Working Mode to Auto-Negotiation. l When jumbo frames are transmitted, set Max Frame Length(byte) according to the actual length of the jumbo frames. Otherwise, it is recommended that you set Max Frame Length(byte) to 1536. A.5.6.2 Configuring the Traffic Control of Ethernet Ports Required when the flow control function is enabled on the external equipment to which the Ethernet port is connected. Set the major parameters as follows: l When the external equipment uses the non-autonegotiation flow control function, set NonAutonegotiation Flow Control Mode to Enabled. l When the external equipment uses the auto-negotiation flow control function, set Auto-Negotiation Flow Control Mode to Enabled. A.5.6.3 Setting the Layer 2 Attributes of Ethernet Ports Required. Set the major parameters as follows: l If all the accessed services carry VLAN tags (tagged frames), set TAG to Tag Aware. l If none of the accessed services carries VLAN tags (untagged frames), set TAG to Access, and set Default VLAN ID and VLAN Priority according to the network planning information. l When the accessed services contain tagged frames and untagged frames, set TAG to Hybrid, and set Default VLAN ID and VLAN Priority according to the network planning information.
Issue 02 (2011-01-20)
6-131
6 Packet Features
Operation A.5.6.5 Setting the Advanced Attributes of Ethernet Ports Setting attributes of IF_ETH ports A.5.7.1 Setting the General Attributes of the IF_ETH Port A.5.7.2 Setting the Layer 2 Attributes of the IF_ETH Port
Required when an IF_ETH port is enabled to access Ethernet services. Set the major parameters as follows: l Set Port Mode to Layer 2. l Set Encapsulation Type to 802.1Q.
Required. Set the major parameters as follows: l If all the accessed services carry VLAN tags (tagged frames), set Tag to Tag Aware. l If none of the accessed services carries VLAN tags (untagged frames), set Tag to Access, and set Default VLAN ID and VLAN Priority according to the network planning information. l When the accessed services contain tagged frames and untagged frames, set Tag to Hybrid, and set Default VLAN ID and VLAN Priority according to the network planning information.
6-132
Issue 02 (2011-01-20)
6 Packet Features
Procedure for Configuring a LAG

Table 6-48 Procedure for configuring a LAG Operation A.6.2.1 Creating a LAG Description Required if the LAG is configured to protect the FE/GE ports. Set the major 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 In the case of FE/GE ports, 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 NonSharing 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 Set Revertive Mode to the same value as the opposite equipment. Generally, set Revertive Mode to Revertive Mode for the equipment at both ends. This parameter is only valid to LAGs whose Load Sharing is set to Non-Sharing. l Set Load Sharing Hash Algorithm to the same value as the opposite equipment. Unless otherwise specified, this parameter adopts the default value. This parameter is valid only to LAGs whose Load Sharing is set to Sharing. l It is recommended that you set this parameter to the same value for the main and slave ports. In this case, you can set System Priority as required. It is recommended that you set this parameter to the default value. This parameter is valid only to a static LAG. l Set Main Board, 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 ports. A.6.2.2 Setting Parameters for LAGs Optional.
Issue 02 (2011-01-20)
6-133
6 Packet Features
Procedure for Configuring UNI-NNI E-Line Services Carried by PWs

Table 6-49 Procedure for configuring UNI-NNI E-Line services carried by PWs Operation A.6.3.5 Configuring UNI-NNI ELine Services (Carried by PWs) Description Required. Set the major parameters of E-Line services as follows: l Set Direction to UNI-NNI. l Set BPDU to Not Transparently transmitted. l Set Source Port and Source VLANs according to the network planning information. l Set Bearer Type to PW. l It is recommended that you set Protection Type to No Protection. Although a PW protection scheme needs to be created, it is recommended that you create it after creating E-Line services carried by PWs. Set the major parameters for a PW in the General Attributes tab as follows: l Set PW ID according to the service planning information. l Set PW Signaling Type to Static. l PW Type indicates whether to add P-TAG when Ethernet frames are encapsulated on a PW. When no request is proposed to add VLAN IDs, set this parameter to Ethernet. When a request is proposed to add VLAN IDs, set this parameter to Ethernet Tagged Mode. In the Advanced Attributes tab page, set Request VLAN to be added. l Set PW Ingress Label/Source Port and PW Egress Label/Sink Port according to the service planning information. l Set Tunnel Type to MPLS. l Select the Tunnel that carries PWs according to the service planning information. Set the major parameters for a PW in the Advanced Attributes tab as follows: l The control word is not supported during ETH PWE3 packet encapsulation on the OptiX RTN 980. Therefore, set Control Word to No Use. l Set Control Channel Type to Alert Label. l Set VCCV Verification Mode to Ping. Set the major parameters for a PW in the QoS tab as follows: l Set Bandwidth Limit for a PW according to the service planning information. Its default value is Disabled. l To enable Bandwidth Limit to take effect for a PW, first configure a maximum bandwidth for the tunnel that carries the PW.
6-134
Issue 02 (2011-01-20)
6 Packet Features

Procedure for Configuring the QoS

Table 6-50 Procedure for configuring the QoS Operation Using the default DS domain for OptiX RTN equipment Description Required. 1. If the mappings that are planned between the packet priority and PHB service classes for base stations or interconnected equipment are different from the mappings that are configured for the default DS domain of the OptiX RTN equipment, change the mappings of the OptiX RTN equipment to be the same as the mappings planned for the base stations or interconnected equipment. 2. If the packet priority type (namely, the trusted packet type) supported by base stations or interconnected equipment is different from the trusted packet type (C-VLAN priority, by default) for the default DS domain of the OptiX RTN equipment, change the trusted packet type of the UNI port in the DS domain that receives the Ethernet service packets to be the same as the trusted packet type of the base stations or interconnected equipment. 3. When transmitting the PW-carried UNI-NNI E-Line service packets, an NNI port supports only packets with the MPLS EXP priority. Therefore, you need to change the trusted packet type of the NNI port in the default DS domain to MPLS EXP. A.6.7.4 Creating a Port Policy A.6.7.6 Creating the Traffic A.6.7.7 Setting the Port That Uses the Port Policy A.6.7.8 Configuring Port Shaping Required when you need to apply QoS policies other than Diffserv and port shaping for a specific port. Set the relevant parameters according to the network planning information. Required when you need to perform the CAR or shaping operation for a specific flow over the port. Set the relevant parameters according to the network planning information. Required when a port policy is created. 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.
Issue 02 (2011-01-20)
6-135
6 Packet Features

6-136
Issue 02 (2011-01-20)
6 Packet Features

This section uses an example to describe how to plan and configure ETH PWE3 according to network conditions. For the configuration example of ETH PWE3, see Configuration Example (E-Line Services Carried on PWs, a Simple Example) in the Configuration Guide.

Related Tasks
A.5.6.1 Setting the General Attributes of Ethernet Ports A.5.6.3 Setting the Layer 2 Attributes of Ethernet Ports A.5.7.1 Setting the General Attributes of the IF_ETH Port A.5.7.2 Setting the Layer 2 Attributes of the IF_ETH Port A.6.3.5 Configuring UNI-NNI E-Line Services (Carried by PWs)

When an exception is detected in the ETH PWE3 packet, an NE reports the specific alarm.
Relevant Alarms
None.
Relevant Events
None.
6 Packet Features
6.8.11 FAQs
This section provides answers to the questions that are frequently raised when ETH PWE3 is used. Question: Does ETH PWE3 support PW ping/traceroute and VCCV? Answer: Yes. But it supports PW ping/traceroute and VCCV only based on OAM Alert Label. It does not support PW ping/traceroute and VCCV based on control word. Question: How to calculate the transmission efficiency of an ETH PWE3 service? Answer: You can calculate the transmission efficiency of an ETH PWE3 service as follows:a Transmission efficiency = Ethernet frame length/(Payload length + PWE3 overhead length + Ethernet Layer 2 overhead length) l Ethernet frame length Untagged Ethernet frame length = 18 + Ethernet payload length Tagged Ethernet frame length = 22 + Ethernet payload length QinQ frame length = 26 + Ethernet payload length l PWE3 overhead length = MPLS label length + PW label length + CW length An MPLS label, PW label, and CW are all four bytes. A PWE3 overhead is 8 bytes as the OptiX RTN 980 does not support a CW. l Ethernet Layer 2 overhead length = Ethernet frame header length + FCS length An untagged Ethernet frame header is 14 bytes. A tagged Ethernet frame header is 18 bytes. An FCS is 4 bytes. By default, an Ethernet packet carrying the MPLS packet is tagged. Therefore, the Ethernet Layer 2 overhead is 22 bytes. By default, ETH PWE3 transmission efficiency = Ethernet frame length/(Ethernet frame length + 30) Assuming that a 64-byte Ethernet service is transmitted in ETH PWE3 mode, the payload transmission efficiency is 64/(64 + 30) = 68.1%.
NOTE
l The previous formula computes the payload transmission efficiency, without the consideration of the 20-byte interframe gap and preamble. These 20 bytes are omitted in ETH PWE3. l When ETH PWE3 services are transmitted over radio links or Ethernet links, the ETH PWE3 service transmission efficiency pertains to the efficiency of physical links transmitting Ethernet frames.
6.9 PW OAM
This chapter describes the PW OAM feature. 6.9.1 Introduction This section provides the definition of PW OAM and describes its purpose. 6.9.2 Basic Concepts This section describes the basic concepts associated with PW OAM.
6 Packet Features
6.9.3 Specifications This section describes the specifications for PW OAM. 6.9.4 Reference Standards and Protocols This section describes the standards and protocols associated with PW OAM. 6.9.5 Availability This section describes the support required by the application of the PW OAM feature and its dependencies. 6.9.6 Principles In the PW OAM mechanism, after the local PE sends CV or FFD packets periodically, the remote PE on the forward PW checks the number and contents of the received CV/FFD packets within a detection period to check the connectivity of a PW. 6.9.7 Configuration Procedure The OAM configurations of PW APS are different from those of the PW long-term monitoring. 6.9.8 Configuration Example This section uses an example to describe how to plan and configure PW OAM for long-term PW monitoring according to network conditions. 6.9.9 Task Collection This section provides the hyperlinks of the operation tasks associated with the feature. 6.9.10 Relevant Alarms and Events When the PW OAM mechanism detects a fault in the LSP, an NE reports the specific alarm. 6.9.11 FAQs This section provides answers to the questions that are frequently raised when PW OAM is used.
6.9.1 Introduction
This section provides the definition of PW OAM and describes its purpose.
Definition
PW OAM is used to detect and locate PW faults and monitor the performance of PWs. In this document, PW OAM refers to the OAM for PWs that are carried in MPLS tunnels. PW OAM checks unidirectional connectivity of PWs by means of specific PW OAM packets. PW OAM has the following features: l l PW OAM packets are processed only at the PW layer, without affecting other layers. PW OAM packets are transmitted on a service channel requiring low bandwidth, without affecting the services carried on the same channel.
Purpose
PW OAM can quickly check the PW connectivity by means of CV/FFD packets. Based on the results of OAM checks, the equipment determines whether to trigger protection switching or not. PW OAM can quickly locate faults and implement service protection. As shown in Figure 6-63, in the PW OAM mechanism, the source end (PE1) transmits test packets and the sink end (PE2) checks defects. This is how the PW connectivity is checked.
6 Packet Features
Figure 6-63 Typical application of PW OAM

Transmitting packets Detecting defects
PSN
NodeB
PW1 PW2
RNC LSP PE2 RNC
PE1 NodeB

This section describes the basic concepts associated with PW OAM. 6.9.2.1 PW OAM Packet The PW OAM packet that the OptiX RTN 980 supports includes the CV/FFD packet and BDI packet. 6.9.2.2 PW Defect Type During any given detection period, the remote PE will report a PW defect if receiving an unexpected number of CV/FFD packets or CV/FFD packets with unexpected contents.
6.9.2.1 PW OAM Packet

The PW OAM packet that the OptiX RTN 980 supports includes the CV/FFD packet and BDI packet.
CV/FFD
Both connectivity verification (CV) packets and fast failure detection (FFD) packets are used to check connectivity. The transmit period of CV packets is longer and always 1s, but the transmit period of FFD packets is shorter and can be adjusted. Therefore, CV packets are applicable to connectivity check of a PW that does not have a stringent requirement for defect detection, and FFD packets are applicable to connectivity check of a PW that has a stringent requirement for defect detection. The local PE periodically generates CV packets and FFD packets. The remote PE checks the number and contents of received CV packets or FFD packets at an interval of three times the packet transmit period. Before transmitting a CV or FFD packet, the local PE pushes two layers of labels to the packet: PW label and label of the LSP that carries the PW. In addition to the label, the CV and FFD packets used in PW OAM have the same formats as the CV and FFD packets used in MPLS OAM. For details, see 6.2.2.1 CV/FFD.
6 Packet Features
BDI
Backward defect indication (BDI) packets are used to inform PW defects. When checking a PW defect, the remote PE generates a BDI packet to inform the local PE of the defect by transmitting the BDI packet over the preset reverse PW. Before transmitting a BDI packet, the remote PE pushes two layers of labels to the BDI packet: PW label and label of the LSP that carries the PW. In addition to the label, the BDI packet used in PW OAM have the same format as the BDI packet used in MPLS OAM. For details, see 6.2.2.3 BDI.
6.9.2.2 PW Defect Type

During any given detection period, the remote PE will report a PW defect if receiving an unexpected number of CV/FFD packets or CV/FFD packets with unexpected contents.
Defect Type
During any given detection period, the remote PE should receive two to four CV or FFD packets with the expected TTSI and should not receive CV or FFD packets with unexpected TTSI. If the remote PE receives an unexpected number of CV/FFD packets or CV/FFD packets with unexpected contents, it reports a PW defect. Table 6-52 provides the defect types supported by the OptiX RTN 980. Table 6-52 PW defect types Defect Type NonPW layer defect PW layer defect dServer Valu e 0x010 1 Meaning Any server layer defect arising below the PW layer network Loss of connectivity verification packets Trigger Condition The defect is reported by the server layer network for PW OAM. The defect is generated due to missing CV or FFD packets with expected TTSI within a detection period. The defect is generated due to receiving CV or FFD packets with unexpected TTSI and missing CV or FFD packets with expected TTSI within a detection period. The defect is generated due to receiving CV or FFD packets with unexpected TTSI and with the expected TTSI within a detection period.
dLOCV
0x020 1
dTTSI_ Mismatc h
0x020 2
TTSI mismatch defect
dTTSI_ Mismerg e
0x020 3
TTSI mismerge defect
Issue 02 (2011-01-20)
6-141
6 Packet Features
Defect Type dExcess
Valu e 0x020 4
Meaning Defect of CV or FFD packets with an excessive rate
Trigger Condition The defect is generated due to receiving five or more CV or FFD packets with the expected TTSI within a detection period. For example, the defect is generated when the type and period of received CV or FFD packets do not match the expected values within a detection period.
Others
dUnkno wn
0x02F F
Undefined or unknown defect
NOTE
The OptiX RTN 980 allows to set SD and SF thresholds. When the packet loss ratio of OAM packets exceeds the preset thresholds, the specific alarm is reported. If all the preceding trigger conditions are met, the PW layer defects are reported in descending order of priorities: dTTSI_Mismatch > dTTSI_Mismerge > dLOCV > dExcess.
Detection Mechanism
The remote PE checks packets in two modes: adaptive mode and manual mode. l Adaptive mode: The detection period is once every three transmit periods of received CV or FFD packets. When receiving the first CV or FFD packet, the remote PE records the type and transmit period of the packet and starts to check connectivity. Manual mode: The detection period is once every three transmit periods that are manually set.
This section describes the specifications for PW OAM. Table 6-53 list the specifications for PW OAM. Table 6-53 Specifications for PW OAM Item Maximum number of PW OAM resources Specifications 64
NOTE MPLS OAM and PW OAM share 64 OAM resources.
Type of OAM packet
CV FFD
6-142
Issue 02 (2011-01-20)
6 Packet Features
Item Transmission frequency of OAM packets CV FFD
Specifications 1s l 3.3 ms l 10 ms l 20 ms l 50 ms l 100 ms l 200 ms l 500 ms
OAM detection mode
l Adaptive mode l Manual mode
Setting the TTSI bits in OAM packets PW defect type
Supported l dLOCV l dTTSI_Mismatch l dTTSI_Mismerge l dExcess l dUnknown l dServer
Setting SD and SF thresholds
Supported

This section describes the standards and protocols associated with PW OAM. The following standards and protocols are associated with PW OAM: l l ITU-T Y.1710: Requirements for Operation & Maintenance functionality for MPLS networks ITU-T Y.1711: Operation & Maintenance mechanism for MPLS networks
6.9.5 Availability
This section describes the support required by the application of the PW OAM feature and its dependencies.
Issue 02 (2011-01-20)
6-143
6 Packet Features

Table 6-54 Hardware and version support Feature PW OAM Applicable Board CSHN IFU2 IFX2 ISU2 ISX2 EM6T EM6F Applicable Hardware Version All the versions All the versions All the versions All the versions All the versions All the versions All the versions Applicable Product Version V100R003C00 and later V100R003C00 and later V100R003C00 and later V100R003C00 and later V100R003C00 and later V100R003C00 and later V100R003C00 and later
The dependencies between the PW OAM feature and other features are as follows: l l l PW OAM is the prerequisite and basis for PW APS. PW OAM can co-exist with other OAM mechanisms. MPLS OAM and PW OAM share 64 OAM resources.
6.9.6 Principles
In the PW OAM mechanism, after the local PE sends CV or FFD packets periodically, the remote PE on the forward PW checks the number and contents of the received CV/FFD packets within a detection period to check the connectivity of a PW. Figure 6-64 shows how the connectivity of a PW is checked. The PW is bidirectional, and therefore a reverse PW is not needed.
6-144
Issue 02 (2011-01-20)
6 Packet Features
Figure 6-64 Continuity check principle of PW OAM
PW
PE1 Packet transmission direction Packet transmission equipment
PE2
CV/FFD BDI
The check principle is as follows: 1. 2. After the OAM function is enabled for the local PE (PE1) and remote PE (PE2), PE1 transmits CV packets or FFD packets periodically at a fixed interval. The packets arrive at the remote PE (PE2) along the tested PW. PE2 checks the information about the received packets, such as packet type, frequency, and TTSI to judge the correctness of the packets and also checks the number of received packets within a detection period. The operations help to monitor connectivity of a PW. When a defect is detected, the remote PE (PE2) reports an alarm according to the defect type. The remote PE (PE2) also transmits a BDI packet with the defect information to the local PE (PE1) along the reverse PW so that the local PE (PE1) is timely informed of the defect status.
3.

The OAM configurations of PW APS are different from those of the PW long-term monitoring.
NOTE
This section describes only the OAM configurations for PW long-term monitoring. The OAM parameters for PW APS are configured during the configuration of PW APS.
Table 6-55 Flow for configuring PW OAM Step 1 Operation A.7.4.3 Setting PW OAM Parameters Description Required. Set the major parameters as follows: l Set OAM Status of the required PW to Enabled. l Set Detection Packet Type of the required PW to CV. l Set Detection Mode of the required PW to AutoSensing.
NOTE If Detection Packet Period (ms) needs to be set as required, set Detection Packet Type to FFD.
Issue 02 (2011-01-20)
6-145
6 Packet Features

This section uses an example to describe how to plan and configure PW OAM for long-term PW monitoring according to network conditions. 6.9.8.1 Network Diagram This section describes the networking information about the NEs. 6.9.8.2 Service Planning The service planning information contains all the parameters required for configuring the NE data. 6.9.8.3 Configuration Process This section describes the process of data configuration.

This section describes the networking information about the NEs. On a PSN shown in Figure 6-65, CV packets in the PW OAM mechanism are used to continuously test the connectivity of the PW between NE1 and NE3. Figure 6-65 Network diagram of the PW OAM function
NE1
NE2 LSP
NE3
PW (ID=1501) Ingress Egress

The service planning information contains all the parameters required for configuring the NE data. In this example, the planning information about LSP ping for NE1 and NE3 is as follows. l CV packets are used for a connectivity check, because only PW connectivity needs to be continuously tested and the connectivity check does not have a requirement for the packet transmission interval. The auto-sensing mode is used for a connectivity check.

6 Packet Features
Procedure
Step 1 See Starting/Stopping CV/FFD Detection for PWs, and start or cancel a CV/FFD packet detection. The values for the required parameters are provided as follows. Parameter Value NE1 OAM Status Detection Mode Detection Packet Type SD Threshold SF Threshold Enabled Auto-Sensing CV 0 0 NE3 Enabled Auto-Sensing CV 0 0
----End

Related Tasks
A.7.4.3 Setting PW OAM Parameters

When the PW OAM mechanism detects a fault in the LSP, an NE reports the specific alarm.
Relevant Alarms
l MPLS_PW_BDI The MPLS_PW_BDI alarm indicates that a defect occurs in the reverse direction of a PW. If an Ethernet port receives a BDI packet, the alarm is reported to indicate a default in the forward direction of an PW. l MPLS_PW_Excess The MPLS_PW_Excess alarm indicates that excessive TTSIs are received. This alarm is reported if an Ethernet port receives five or more CV or FFD packets with expected TTSI within a detection period. l MPLS_PW_LOCV The MPLS_PW_LOCV alarm indicates that a continuity check packet is lost. This alarm is reported if an Ethernet port fails to receive CV or FFD packets with expected TTSI within a detection period. l
Issue 02 (2011-01-20)
MPLS_PW_MISMATCH
6 Packet Features
The MPLS_PW_MISMATCH alarm indicates that the TTSI is not a match. This alarm is reported if an Ethernet port receives CV or FFD packets with unexpected TTSI and fails to receive CV or FFD packets with expected TTSI within a detection period. l MPLS_PW_MISMERGE The MPLS_PW_MISMERGE alarm indicates that the TTSIs are incorrectly merged. This alarm is reported if an Ethernet port receives CV or FFD packets with unexpected TTSI, and CV packets with expected TTSI within a detection period. l MPLS_PW_SD The MPLS_PW_SD alarm indicates that the signal in the PW degrades. This alarm is reported when the loss ratio of the continuity check packets is higher than the SD threshold but is lower than the SF threshold. l MPLS_PW_SF The MPLS_PW_SF alarm indicates that the signal in the PW severely degrades. This alarm is reported when the loss ratio of the continuity check packets is higher than the SF threshold. l MPLS_PW_UNKNOWN The MPLS_PW_UNKNOWN alarm indicates that a certain unknown defects exists in the PW. This alarm is reported if an Ethernet port receives continuity check packets with expected TTSI but with different types or transmission periods within a detection period.
Relevant Events
None.
6.9.11 FAQs
This section provides answers to the questions that are frequently raised when PW OAM is used. Question: What are the differences between MPLS OAM and PW OAM? Answer: Table 6-56 lists the main differences between MPLS OAM and PW OAM. Table 6-56 Differences between MPLS OAM and PW OAM Item Detection object Packet processing at the OAM initiation end MPLS OAM LSP Adding an LSP label PW OAM PW Adding two layers of labels: One is a PW label, and the other is label of LSP carrying the PW. A PW is bidirectional. Its reverse tunnel is automatically created. Not supported
Reverse tunnel
An LSP is unidirectional. Its reverse tunnel is manually created. Supported
FDI defect information
6-148
Issue 02 (2011-01-20)
6 Packet Features
Item Relevant alarms
MPLS OAM l MPLS_TUNNEL_BDI l MPLS_TUNNEL_Excess l MPLS_TUNNEL_LOC V l MPLS_TUNNEL_MISMATCH l MPLS_TUNNEL_MISMERGE l MPLS_TUNNEL_SD l MPLS_TUNNEL_SF l MPLS_TUNNEL_OAM FAIL l MPLS_TUNNEL_UNKNOWN l MPLS_TUNNEL_FDI
PW OAM l MPLS_PW_BDI l MPLS_PW_Excess l MPLS_PW_LOCV l MPLS_PW_MISMATC H l MPLS_PW_MISMERG E l MPLS_PW_SD l MPLS_PW_SF l MPLS_PW_UNKNOW N l MPLS_PW_OAMFAIL
6.10 PW Ping/Traceroute
This chapter describes the PW ping and PW traceroute features. 6.10.1 Introduction This section provides the definitions of PW ping and PW traceroute and describes their purposes. 6.10.2 Specifications This section describes the specifications for PW ping/traceroute. 6.10.3 Reference Standards and Protocols This section provides the standards and protocols associated with PW ping/traceroute. 6.10.4 Availability This section describes the support required by the application of the PW ping/traceroute feature and its dependencies. 6.10.5 Principles The PW ping/traceroute operations are implemented with the exchange of MPLS echo request and echo reply packets. 6.10.6 Configuration Procedure The configuration procedure of PW ping/traceroute contains only one configuration task. 6.10.7 Configuration Example This section uses an example to describe how to plan and configure PW ping/traceroute according to network conditions. 6.10.8 Task Collection This section provides the hyperlinks of the operation tasks associated with the feature. 6.10.9 Relevant Alarms and Events
6 Packet Features
There is no alarm or event associated with the PW ping/traceroute feature. 6.10.10 FAQs This section provides answers to the questions that are frequently asked when PW ping/ traceroute is used.
6.10.1 Introduction
This section provides the definitions of PW ping and PW traceroute and describes their purposes.
Definition
PW ping and PW traceroute are used to check and locate faults in a PW and monitor the PW performance. PW ping/traceroute is similar to IP ping/traceroute regarding the principles. Like VCCV, PW ping and PW traceroute can be based on control word or alert label on the OptiX RTN 980.
Purpose
PW ping allows bidirectional connectivity check of the single-segment PW (SS-PW) and multisegment PW (MS-PW). As shown in Figure 6-66, in the PW ping mechanism, the local PE (PE1) sends a request packet and the remote PE (PE3) returns a reply packet to check the connectivity of a PW. Figure 6-66 Typical application of PW ping
PSN LSP PW PW
PE1
PE2
PE3
Request Reply
PW traceroute provides the specific routing information about an MS-PW or locate faults in an MS-PW by checking connectivity of each PW segment in the MS-PW. As shown in Figure 6-67, in the PW traceroute mechanism, the terminating PE1 at the local end (T-PE1) sends a request packet, and all the switching provider edges (S-PEs) on the PW and the
6 Packet Features
remote T-PE2 take turns to return a reply packet. In this manner, connectivity of PW1 and PW2 is checked section by section, helping you learn about the specific routing information and locate a fault. Figure 6-67 Typical application of PW traceroute
PSN LSP PW1 PW PW2
T-PE1
S-PE
T-PE2
Request Reply Request Reply
PW ping/traceroute has the following advantages: l l Compared with IP ping/traceroute, PW ping/traceroute can locate a PW fault that IP ping/ traceroute cannot locate, such as a label mismatch or a hardware error. PW OAM enables unidirectional connectivity check of a PW by means of CV or FFD packets, but PW ping/traceroute enables bidirectional connectivity check of a PW. Moreover, PW traceroute offers the fault locating feature. PW ping/traceroute is also used to check packet loss ratio and latency.
This section describes the specifications for PW ping/traceroute. Table 6-57 lists the specifications for PW ping/traceroute. Table 6-57 Specifications for PW ping/traceroute Item PW ping Setting the number of transmitted MPLS echo request packets Specifications Supported
Issue 02 (2011-01-20)
6-151
6 Packet Features
Item Length of transmitted MPLS echo request packets Interval for transmitting MPLS echo request packets Setting the EXP value of MPLS label of transmitted MPLS echo request packets Setting the TTL value of MPLS label of transmitted MPLS echo request packets Response mode
Specifications 64 to 1400 10 ms to 10000 ms Supported
Supported
l No response l Application Control Channel l The response is provided by sending the IPv4 UDP packet (that is, the MPLS echo reply packet).
NOTE l "No response" indicates that the destination node involved in a PW ping operation does not return a response packet, but directly reports the event. l "Application control channel" indicates that a response packet is returned through a reverse channel.
Wait-to-response timeout time Response event reported by the source end Response timeout event reported by the source end Statistics event reported by the source end Control channel type
10 ms to 60000 ms Supported Supported Supported Control Word Alert Label
PW traceroute
Length of transmitted MPLS echo request packets Setting the EXP value of MPLS label of transmitted MPLS echo request packets Setting the TTL value of MPLS label of transmitted MPLS echo request packets
84 to 1400 Supported
Supported
6-152
Issue 02 (2011-01-20)
6 Packet Features
Item Response mode
Specifications l No response l Application Control Channel l The response is provided by sending the IPv4 UDP packet (that is, the MPLS echo reply packet).
NOTE l "No response" indicates that the destination node involved in a PW traceroute operation does not return a response packet, but directly reports the event. l "Application control channel" indicates that a response packet is returned through a reverse channel.
Wait-to-response timeout time Response event reported by the source end Response timeout event reported by the source end End event reported by the source end Control channel type
10 ms to 60000 ms Supported Supported Supported Control Word Alert Label

This section provides the standards and protocols associated with PW ping/traceroute. The following standard is associated with PW ping/traceroute: IETF RFC 4379: Detecting Multi-Protocol Label Switched (MPLS) Data Plane Failures
6.10.4 Availability
This section describes the support required by the application of the PW ping/traceroute feature and its dependencies.
Issue 02 (2011-01-20)
6-153
6 Packet Features

Table 6-58 Hardware and version support Feature PW ping/traceroute Applicable Board CSHN IFU2 IFX2 ISU2 ISX2 EM6T EM6F Applicable Hardware Version All the versions All the versions All the versions All the versions All the versions All the versions All the versions Applicable Product Version V100R003C00 and later V100R003C00 and later V100R003C00 and later V100R003C00 and later V100R003C00 and later V100R003C00 and later V100R003C00 and later
The dependencies between the PW ping/traceroute feature and other features are as follows: If PW ping/traceroute uses the IPv4 UDP response mode, all the nodes on the PW must support DCN communication through IP protocols.
6.10.5 Principles
The PW ping/traceroute operations are implemented with the exchange of MPLS echo request and echo reply packets. 6.10.5.1 PW Ping In the PW ping mechanism, the local PE sends an MPLS echo request packet and the remote PE returns an MPLS echo reply packet to check the connectivity of a PW. 6.10.5.2 PW Traceroute In the PW traceroute mechanism, the local T-PE sends an MPLS echo request packet, and all the S-PEs on the PW and remote T-PE take turns to return an MPLS echo reply packet in response to the received request packet. The connectivity of a PW is checked section by section.
6.10.5.1 PW Ping
In the PW ping mechanism, the local PE sends an MPLS echo request packet and the remote PE returns an MPLS echo reply packet to check the connectivity of a PW.
6 Packet Features
The MPLS echo request and MPLS echo reply packets are sent in User Datagram Protocol (UDP) format. The MPLS echo request packet and MPLS echo reply packet carry the information about the timestamp and Time to Live (TTL). l l The timestamp contains the time when the packet is sent and received. Timestamp tells the PW latency. The TTL value in the IP packet header is set to 1, to ensure that the test packet is not transmitted beyond the sink end of the monitored PW.
The SS-PW ping operations are implemented in the same manner as the MS-PW ping operations. That is, the local PE sends an MPLS echo request packet and the remote PE returns an MPLS echo reply packet. This section considers the SS-PW ping operations as an example. As shown in Figure 6-68, PW ping operations are performed to check the bidirectional connectivity of the PWs. Figure 6-68 Checking connectivity in PW ping
PSN LSP PW PW
PE1
PE2
The process for checking the connectivity is as follows: 1. The local PE (PE1) starts a PW ping test, pushes a PW label and LSP label to an MPLS echo request packet, and sends out the packet. The local PE (PE1) structures the MPLS echo request packet in the UDP packet format based on PW ping parameters, and pushes the PW and LSP labels. Then, the local PE transmits the packet based on the preset packet quantity and transmit interval. The packet carries the transmission timestamp. The node P forwards the MPLS echo request packet in the same manner as it forwards a common PWE3 packet.
NOTE
2.
If the node P fails to forward the MPLS echo request packet, it returns a reply message containing an error code and notifies the NMS.
3.
After receiving the MPLS echo request packet, the remote PE (PE2) structures the MPLS echo reply packet, and pushes the reception timestamp. Then, the remote PE transmits the MPLS echo reply packet through the preset reverse PW.
Issue 02 (2011-01-20)
6 Packet Features
NOTE
If the IPv4 UDP response mode is used, the node P and the remote PE address the local PE based on the IP routing table of DCN to transmit the MPLS echo reply packet.
4.
After the local PE (PE1) successfully receives the MPLS echo reply packet returned from the remote PE (PE2), the request packet is no longer transmitted and the bidirectional connectivity is completed. In addition, the local PE (PE1) determines the packet loss ratio and latency based on the information carried by the reply packet and notifies the NMS.
6.10.5.2 PW Traceroute
In the PW traceroute mechanism, the local T-PE sends an MPLS echo request packet, and all the S-PEs on the PW and remote T-PE take turns to return an MPLS echo reply packet in response to the received request packet. The connectivity of a PW is checked section by section. The MPLS echo request and MPLS echo reply are sent User Datagram Protocol (UDP) format. The MPLS echo request and MPLS echo reply packets carry the information about the timestamp, Time to Live (TTL), and next hop. l l The timestamp contains the time when the packet is sent and received. Timestamp tells the PW latency. The TTL value of the IP packet header is set to 1, to ensure that the test packet is not transmitted beyond the sink end of the PW.
As shown in Figure 6-69, PW traceroute operations are performed to check the bidirectional connectivity of the MS-PW. Figure 6-69 Checking connectivity in PW traceroute
PSN LSP PW1 PW PW2
T-PE1
S-PE
T-PE2
TTL=1
MPLS echo request MPLS echo reply MPLS echo request MPLS echo reply
TTL=2
6-156
Issue 02 (2011-01-20)
6 Packet Features
This section considers two hops of PWs as an example. The process for checking the connectivity is as follows: 1. The local T-PE (T-PE1) structures the MPLS echo request packet in the UDP packet format based on PW traceroute parameters, and pushes the PW and LSP labels. Then, the local TPE transmits the packet based on the preset packet quantity and transmit interval. The packet carries the transmission timestamp. The destination node of the MPLS echo request packet is determined by the TTL value in the PW label. When the first request packet is transmitted, the TTL value in the PW label is set to 1, indicating that the next hop (S-PE) of the local T-PE is the destination node of the request packet. After receiving the MPLS echo request packet, S-PE finds the information about the next hop of the PW, structures the MPLS echo reply packet, and pushes the reception timestamp. Then, S-PE transmits the MPLS echo reply packet through the preset reverse PW. On reception of the MPLS echo reply packet returned from the local T-PE each time, the local T-PE (T-PE1) adds 1 to the TTL value in the PW label and retransmits the MPLS echo request packet. After receiving the MPLS echo request packet, the remote T-PE (T-PE2) structures the MPLS echo reply packet, and pushes the reception timestamp. Then, the remote T-PE (TPE2) transmits the MPLS echo reply packet through the preset reverse PW.
NOTE
2.
3.
4.
5.
After the local T-PE (T-PE1) successfully receives the MPLS echo reply packet returned from the remote T-PE (T-PE2), the request packet is no longer transmitted and the bidirectional connectivity check is completed.
NOTE
On reception of the MPLS echo reply packet returned from the other T-PEs, the local T-PE (T-PE1) reports information about the node type, next hop, PW status, and latency to the NMS. In this manner, a fault on the PW can be located.

The configuration procedure of PW ping/traceroute contains only one configuration task.
CAUTION
Prior to PW ping/traceroute operations, set the control channel types of VCCV to the same at both ends. Otherwise, PW ping/traceroute operations will fail.
Issue 02 (2011-01-20)
6-157
6 Packet Features
Table 6-59 Flow for configuring PW ping Step 1 Operation A.7.4.4 Performing a PW Ping Test Description Required. Set the major parameters as follows: l Set Packet Count and EXP Value to the default values. l Set Packet Length as required. l Set Response Mode to Application Control Channel depending on the support capability of the remote PE. If the remote PE supports the reverse channel response, set Response Mode to Application Control Channel. If the remote PE does not support the reverse channel response but supports DCN channel response by using IP protocols, set Response Mode to IPv4 UDP Response.
Table 6-60 Flow for configuring PW traceroute Step 1 Operation A.7.4.5 Performing a PW Traceroute Test Description Required. Set the major parameters as follows: l Set Packet Length as required. l Set EXP Value to the default value. l Set Response Mode to Application Control Channel depending on the support capability of the remote PE. If the remote PE supports the reverse channel response, set Response Mode to Application Control Channel. If the remote PE does not support the reverse channel response but supports DCN channel response by using IP protocols, set Response Mode to IPv4 UDP Response.

This section uses an example to describe how to plan and configure PW ping/traceroute according to network conditions.
NOTE
This example describes the application of PW ping. The application of PW traceroute is similar, and therefore is not described.
6.10.7.1 Network Diagram This section describes the networking information about the NEs.
6 Packet Features
6.10.7.2 Service Planning The service planning information contains all the parameters required for configuring the NE data. 6.10.7.3 Configuration Process This section describes the process of data configuration.

This section describes the networking information about the NEs. On a PSN as shown in Figure 6-70, PW ping is used to test the connectivity of a PW between NE1 and NE3. Figure 6-70 Network diagram of the PW ping function
NE1
NE2 LSP
NE3
PW (ID=201) Ingress Egress

The service planning information contains all the parameters required for configuring the NE data. In this example, the planning information about PW ping for NE1 and NE3 is as follows. l l l Only PW ping is used, because the PW requires a connectivity check but not fault locating. This example uses 64-byte packets (short packets) and 1400-byte packets (long packets), to respectively test the connectivity of the PW. As an OptiX RTN 980, NE3 allows its reverse channel to respond to PW ping/traceroute requests. Therefore, set Response Mode to Application Control Channel when starting a test on NE1.

Procedure
Step 1 See A.7.4.4 Performing a PW Ping Test, and start a PW ping packet detection on NE1. The values for the required parameters are provided as follows.
6 Packet Features
Parameter
Value Short Packet Test Long Packet Test 3 7 255 100 1400 300 Application Control Channel
Packet Count EXP Value TTL Transmit Interval(10ms) Packet Length Wait-to-Response Timeout Time(10ms) Response Mode
3 7 255 100 64 300 Application Control Channel
----End

Related Tasks
A.7.4.4 Performing a PW Ping Test A.7.4.5 Performing a PW Traceroute Test

There is no alarm or event associated with the PW ping/traceroute feature.
6.10.10 FAQs
This section provides answers to the questions that are frequently asked when PW ping/ traceroute is used. Question: Why should the ping or traceroute operation be performed for only one LSP or PW at a time? Answer: If the ping or traceroute operation is performed for multiple LSPs or PWs at a time, the CPU processing capability may be insufficient. Therefore, the packets may fail to be transmitted or received within the specified time interval. In this case, the ping or traceroute operation times out. Question: RTN 900 V100R003 NEs and RTN 900 V100R001 NEs both support IPv4 UDP response. But why do PW ping/traceroute operations that are performed between an RTN 900 V100R003 NE and an RTN 900 V100R001 NE fail when in this response mode? Answer: Regarding an RTN 900 V100R001 NE, IPv4 UDP response means that the response NE addresses the source NE by using the ISIS protocol. Regarding an RTN 900 V100R003 NE, IPv4 UDP response means that the response NE addresses the source NE by using the IP over
6 Packet Features
DCC protocol. Therefore the PW ping/traceroute operations will fail since the two response mechanisms are totally different.
NOTE
However, thanks to the same response mechanisms, the PW ping/traceroute operations performed between an MSTP+ NE and an RTN 900 V100R003 NE, and those performed between a PTN NE and an RTN 900 V100R001 will succeed. This is, the PW ping/traceroute operations performed between an RTN 900 V100R003 NE and a PTN NE will also fail.
6.11 PW APS
This chapter describes the PW automatic protection switching (APS) feature. 6.11.1 Introduction This section provides the definition of PW APS and describes its purpose. 6.11.2 Basic Concepts This section describes the basic concepts associated with PW APS. 6.11.3 Specifications This section describes the specifications for PW APS. 6.11.4 Reference Standards and Protocols This section describes the standards and protocols associated with PW APS. 6.11.5 Availability This section describes the support required by the application of the PW APS feature and its dependencies. 6.11.6 Principles PW APS uses the PW OAM mechanism to detect faults in PWs, and PEs exchange APS protocol packets for protection switching. 6.11.7 Configuration Procedure When PW APS is configured, PW OAM is configured simultaneously. 6.11.8 Configuration Example This section uses an example to describe how to plan and configure PW APS according to network conditions. 6.11.9 Task Collection This section provides the hyperlinks of the operation tasks associated with the feature. 6.11.10 Relevant Alarms and Events When detecting an exception by performing PW APS operations, an NE reports the specific alarm. 6.11.11 FAQs This section provides answers to the questions that are frequently raised when PW APS is used.
6.11.1 Introduction
This section provides the definition of PW APS and describes its purpose.
Issue 02 (2011-01-20)
6-161
6 Packet Features
Definition
PW APS is a function that protects PWs based on the APS protocol. With this function, when the working PW is faulty, the service can be switched to the preconfigured protection PW. The PW APS function supported by the OptiX RTN 980 has the following features: l l l l The PW APS function provides end-to-end protection for PWs. The working PW and protection PW are carried in different tunnels but have the same local and remote PEs. The protection PW in the PW APS protection pair does not carry extra traffic. In PW APS, the PW OAM mechanism is used to detect faults in PWs, and the PEs exchange APS protocol packets to achieve protection switching.
Purpose
PW APS improves reliability for service transmission in PWs. As shown in Figure 6-71, when the PW OAM mechanism detects a fault in the working PW, the service is switched to the protection PW for transmission.
6-162
Issue 02 (2011-01-20)
6 Packet Features
Figure 6-71 Application example of PW APS

PE2
Working PW PE1 PE4 Protection PW
PE3 Protect switching PE2
Working PW PE1 PE4 Protection PW
PE3 Service Packet transmission equipment
In actual application, the OptiX RTN 980 (for example, PE1 in Figure 6-72) can work with the multi-chassis PW APS mechanism to achieve PW APS. PE2 and PE3 are the packet devices that support MC-PW APS, and communicate with each other through the dual node interconnection PW (DNI-PW). For PE1, PE2 and PE3 are considered as one packet device.
Issue 02 (2011-01-20)
6-163
6 Packet Features

MC-PW APS
PW APS Working PW
PE2
PE1
DNI-PW
Protection PW
PE3
Packet transmission equipment Packet transmission equipment

This section describes the basic concepts associated with PW APS. 6.11.2.1 Protection Type PW APS can be classified by protection mechanism, switching mode, and revertive mode. 6.11.2.2 Switching Conditions PW APS can be locally triggered by a signal fail (SF) condition or by an external switching command. In dual-ended switching mode, the local NE can also perform switching according to the notification returned from the remote NE. 6.11.2.3 Switching Impact The service carried by the PW is unavailable during the switching (less than 100 ms). 6.11.2.4 PW APS Binding When multiple PW pairs require protection and the working and protection PWs of the PW pairs are both carried by the same LSPs, the PW APS binding technology can be used so that these PWs can participate in the protection switching according to the status of one PW pair.

PW APS can be classified by protection mechanism, switching mode, and revertive mode.
Protection Mechanism
PW APS is classified into 1+1 protection and 1:1 protection by protection mechanism. l
6-164
1+1 protection
6 Packet Features
Normally, the transmit end transmits services to the working PW and protection PW, and the receive end receives services from the working PW. When the working PW is faulty, the receive end receives services from the protection PW. l 1:1 protection Normally, services are transmitted in the working PW. The protection PW is idle. When the working PW is faulty, services are transmitted in the protection PW.
NOTE
The OptiX RTN 980 support only 1:1 protection.
Switching Mode
PW APS is classified into the single-ended switching and the dual-ended switching by switching mode. l Single-ended switching Single-ended switching is unidirectional switching. That is, when the forward or reverse working PW is faulty, only the service in the direction where the fault occurs is switched to the protection PW. In regards to the single-ended switching, the switching operations in the two directions are not associated with each other. l Dual-ended switching Dual-ended switching is bidirectional switching. That is, when the forward or reverse working PW is faulty, the service in both directions is switched to the protection PW. Dual-ended switching ensures that the service is transmitted and received along one trail, facilitating service management and maintenance.
Revertive Mode
PW APS is classified into the revertive mode and the non-revertive mode by revertive mode. l Revertive mode In revertive mode, the service is automatically switched back to the working PW after the working PW is restored and the normal state lasts for a certain period. The period after the working PW is restored and before the service is switched back to the working PW is called the wait-to-restore (WTR) time. To prevent frequent switching events due to an unstable working PW, the WTR time is generally 5 to 12 minutes. l Non-revertive mode In non-revertive mode, the service is not automatically switched back to the working PW even after the working PW is restored. However, the service will be switched back if the protection PW fails or an external command triggers protection switching.

PW APS can be locally triggered by a signal fail (SF) condition or by an external switching command. In dual-ended switching mode, the local NE can also perform switching according to the notification returned from the remote NE.
NOTE
If two switching conditions exist at the same time, the higher-priority switching condition preempts the other one.
Issue 02 (2011-01-20)
6-165
6 Packet Features
Table 6-61 Switching conditions for PW APS Switching Condition Clear switching (external switching) Lockout of protection channel (external switching) Prior ity The priorit ies are arrang ed in desce nding order. Description This command clears all the other external switching operations.
When the protection PW is locked out, the service is not allowed to be switched from the working PW to the protection PW. If the service is already switched to the protection PW, the command will forcibly switch it back to the working PW even when the working PW is not restored. Therefore, if the protection switching has been performed, running this command may interrupt the service. The signal fail for protection (SF-P) condition indicates that the protection PW fails. If the protection PW fails, the service carried by the protection PW is automatically switched to the working PW. If the lockout of protection channel condition or the SF-P condition exists, no forced switching occurs. This command forcibly switches the service from the working PW to the protection PW. Afterwards, the service will not be switched back to the working PW even when the working PW is restored. However, when a switching condition has a higher priority, the forced switching is preempted. If the lockout of protection channel condition, SF-P condition, or forced switching condition exists, no SF switching occurs. The SF switching is triggered by the PW OAM detection mechanism. When the working PW fails, the service is switched to the protection PW. For the conditions triggering the SF switching, see Table 6-62. If the lockout of protection channel condition, SF-P condition, forced switching condition, or SF switching condition exists, no manual switching occurs. Manual switching is available in two types: manual switching to protection and manual switching to working. l In response to the manual switching to protection command, the service is switched from the working PW to the protection PW. l In response to the manual switching to working command, the service is switched from the protection PW to the working PW.
SF-P switching (automatic switching) Forced switching (external switching)
SF switching (automatic switching)
6-166
Issue 02 (2011-01-20)
6 Packet Features
Prior ity
Description If SF switching occurs, the service is switched from the working PW to the protection PW. If the working PW is restored to normal afterwards and the normal state lasts until the WTR time elapses, the service is switched back to the working PW. The switching remains in the WTR state after the working PW is restored to normal and before revertive switching occurs. After the revertive switching, the switching changes to the normal state.
This command is used to test whether the APS protocol works normally. Actually, no switching occurs and the service will not be affected.
Table 6-62 Trigger conditions for PW APS SF switching Switching Condition Board software or hardware failure Cold reset on board MPLS_PW_Excess MPLS_PW_LOCV MPLS_PW_MISMATCH MPLS_PW_MISMERGE MPLS_PW_SF MPLS_PW_BDI MPLS_PW_SD Description Default condition Default condition Default condition Default condition Default condition Default condition Default condition Optional condition Optional condition
NOTE
An optional condition can trigger PW APS SF switching only after it is selected. By default, the alarms do not trigger PW APS SF switching.

The service carried by the PW is unavailable during the switching (less than 100 ms).
Issue 02 (2011-01-20)
6-167
6 Packet Features
6.11.2.4 PW APS Binding

When multiple PW pairs require protection and the working and protection PWs of the PW pairs are both carried by the same LSPs, the PW APS binding technology can be used so that these PWs can participate in the protection switching according to the status of one PW pair. In actual application, the OptiX RTN 980 needs to support a large number of PW APS protection groups, but may encounter the following problems: l l If each PW APS protection group starts a state machine, the resources and capability of the system may fail to support all the PW APS protection groups. When a PW is faulty, the other PWs carried in the same LSP may be faulty. Then, switching occurs on the PWs one after another, resulting in a long switching time in total.
PW APS binding allows multiple PW pairs to share one APS state machine, so that the APS state machine can process the protection switching for multiple PW pairs. All the PW pairs that are bound to one PW APS protection group are called slave protection pairs. PW APS binding has the following advantages: l l The slave protection pairs share one state machine with the PW APS protection group. Therefore, less system resources are consumed. When the working PW in the PW APS protection group is faulty, protection switching occurs on the PW APS protection group as well as on all its slave protection pairs. In this manner, switching efficiency is improved.
NOTE
When the working PW in a slave protection pair is faulty, protection switching does not occur.
Figure 6-73 considers two PWs as an example to describe how PW APS binding is applied. Wherein, the working PW1 and protection PW1 form a PW APS protection group, and the working PW2 and protection PW2 form a slave protection pair of the protection group. When the working PW1 is faulty, the services carried by the working PW1 and PW2 are switched to their protection PWs at the same time.
6-168
Issue 02 (2011-01-20)
6 Packet Features

MC-PW APS Slave protection pair PW APS
PW1 PW2
LSP
Wor
king
king Wor
DNI-PW
Protec Protec
tion P
W1
tion
Protect switching
MC-PW APS
PW APS
LSP
king Wor
PW1 PW2
king Wor
DNI-PW
Prote ction Prote ction
Packet transmission equipment Third-party packet transmission equipment
Service
This section describes the specifications for PW APS. Table 6-63 lists the specifications for PW APS.
Issue 02 (2011-01-20)
6-169
6 Packet Features
Table 6-63 Specifications for PW APS Item Maximum number of PW APS protection groups Specifications 32
NOTE MPLS APS and PW APS share 32 protection group resources
Supported PW APS protection types
l 1:1 dual-ended revertive mode l 1:1 dual-ended non-revertive mode
Protection switching duration WTR time Hold-off time PW APS binding
< 100 ms 1 min to 12 min 0 ms to 10000 ms Supported

This section describes the standards and protocols associated with PW APS. The following standards and protocols are associated with PW APS: l l ITU-T Y.1720: Protection switching for MPLS networks ITU-T G.8131: Linear protection switching for transport MPLS(T-MPLS) networks
6.11.5 Availability
This section describes the support required by the application of the PW APS feature and its dependencies.

Table 6-64 Hardware and version support Feature PW APS Applicable Board CSHN IFU2 IFX2 ISU2 Applicable Hardware Version All the versions All the versions All the versions All the versions Applicable Product Version V100R003C00 and later V100R003C00 and later V100R003C00 and later V100R003C00 and later
Issue 02 (2011-01-20)
6-170
6 Packet Features
Feature
The dependencies between the PW APS feature and other features are as follows: l l l l PW APS cannot co-exist with MPLS APS. PW APS can co-exist with IF 1+1 protection. PW APS can co-exist with IF N+1 protection. PW APS can co-exist with LAGs.
6.11.6 Principles
PW APS uses the PW OAM mechanism to detect faults in PWs, and PEs exchange APS protocol packets for protection switching. 6.11.6.1 Single-Ended Switching When PW APS is in single-ended switching mode, only the service in the direction where the fault occurs is switched to the protection PW. 6.11.6.2 Dual-Ended Switching When PW APS is in dual-ended switching mode, the service is switched to the forward and reverse protection PWs.
6.11.6.1 Single-Ended Switching

When PW APS is in single-ended switching mode, only the service in the direction where the fault occurs is switched to the protection PW.
Before Switching
l The local and remote PEs exchange APS protocol packets over the protection PW, and then they are aware of the status of each other. When the working PW is found faulty, the local and remote PEs can perform the protection switching, switching hold-off, and wait-torestore (WTR) functions. In this case, the request state of the APS protocol packet should be No Request. The PW OAM mechanism is used to perform connectivity checks on all the PWs.
During Switching
Figure 6-74 shows the principle of the single-ended switching, assuming a fault in the forward working PW.
6 Packet Features
Figure 6-74 Principle of the single-ended switching

Local PE Forward working PW Forward protection PW Reverse working PW Reverse protection PW Switching Remote PE Local PE Forward working PW Forward protection PW Reverse working PW Reverse protection PW Remote PE
Service
Forward working PW label Reverse working PW label
Forward protection PW label
The principle of the single-ended switching is as follows: 1. 2. The remote PE detects a fault in the forward working PW and then it is switched to the forward protection PW. Afterwards, the remote PE sends a bridging request to the local PE by means of the APS protocol packet.
NOTE
l "Bridging" means that the equipment transmits the service to the protection PW instead of the working PW. l "Switching" means that the equipment receives the service from the protection PW instead of the working PW.
3.
On the reception of the bridging request, the local PE pushes the label of the forward protection PW to the service packet so that the service can be bridged to the forward protection PW. The service is transmitted in the forward protection PW and the reverse working PW.
4.
After Switching
If PW APS 1:1 single-ended switching is in revertive mode, the service in the protection PW is switched back to the normal working PW after the WTR time elapses.
6.11.6.2 Dual-Ended Switching

When PW APS is in dual-ended switching mode, the service is switched to the forward and reverse protection PWs.
Before Switching
l The local and remote PEs exchange APS protocol packets over the protection PW, and then they are aware of the status of each other. When the working PW is found faulty, the local and remote PEs can perform the protection switching, switching hold-off, and wait-torestore (WTR) functions. In this case, the request state of the APS protocol packet should be No Request.
6-172
6 Packet Features
The PW OAM mechanism is used to perform connectivity checks on all the PWs.
During Switching
Figure 6-75 shows the principle of the dual-ended switching, assuming a fault in the forward working PW. Figure 6-75 Principle of the dual-ended switching
Local PE Forward working PW Forward protection PW Reverse working PW Reverse protection PW Switching Remote PE Local PE Forward working PW Forward protection PW Reverse working PW Reverse protection PW Remote PE
Service
Forward working PW label Reverse working PW label
Forward protection PW label Reverse protection PW label
The dual-ended switching is implemented as follows: 1. When the remote PE detects a fault in the forward working PW, it is switched to the forward protection PW and is bridged to the reverse protection PW at the same time. l The remote PE receives the service from the forward protection PW instead of the forward working PW. In addition, the remote PE sends the APS protocol packet carrying a bridging request to the local PE. l The remote PE pushes the label of the reverse protection PW to the service packet so that the service can be bridged to the reverse protection PW. Meanwhile, the remote PE sends the APS protocol packet carrying a switching request to the local PE.
NOTE
l "Bridging" means that the equipment transmits the service to the protection PW instead of the working PW. l "Switching" means that the equipment receives the service from the protection PW instead of the working PW.
2.
On the reception of the APS protocol packet carrying a switching request, the local PE performs the following operations: l The local PE pushes the label of the forward protection PW to the service packet so that the service can be bridged to the forward protection PW. l The local PE receives the service from the reverse protection PW instead of the reverse working PW.
3.
The service is transmitted in the forward and reverse protection PWs.
Issue 02 (2011-01-20)
6-173
6 Packet Features
After Switching
If PW APS 1:1 dual-ended switching is in revertive mode, the service is switched back to the normal forward and reverse working PWs after the WTR time elapses.

When PW APS is configured, PW OAM is configured simultaneously. Table 6-65 Flow for configuring PW APS Step 1 Operation A.7.5.1 Creating a PW APS Protection Group Description Required. Select a service from those that are configured with the same working and protection PWs. Configure a PW APS protection group for the selected service. l Set the major parameters in the General Attributes tab as follows. Set PW ID for the protection PW according to the planning information. Set PW Signaling Type to Static. Set PW Encapsulation Type to MPLS. Set PW Ingress Label/Source Port and PW Egress Label/Sink Port according to the planning information. l Set the major parameters in the Protect Group tab as follows. Set Protection Group ID to a protection group ID that is planned. Set Enabling Status to Disabled. Set Switching Mode to Dual-ended Switching. Set Revertive Mode to Revertive. Set Switchover Restoration Time(min) to 5. Set Switchover Delay Time(100ms) to 0. l Set the major parameters in the PW OAM tab as follows. Set Detection Mode to Auto-Sensing. Set Detection Packet Type to FFD. Set Detection Packet Period(ms) to 3.3. Set PW ID to be Received according to the planning information.
6-174
Issue 02 (2011-01-20)
6 Packet Features
Step 2
Operation A.7.5.2 Configuring Slave Protection Pairs of PW APS
Description Optional. Configure slave protection pairs for the other services that are configured with the same working and protection PWs. In the Slave Protection Pair tab, set Protection Group ID for the PW APS protection group that the slave protection pairs belong to.
A.7.5.5 Enabling/ Disabling PW APS Protection
Required. In the Protect Group tab, set Enabling Status to Enabled for the APS protection groups on the two nodes.

This section uses an example to describe how to plan and configure PW APS according to network conditions. 6.11.8.1 Network Diagram This section describes the networking information about the NEs. 6.11.8.2 Service Planning The service planning information contains all the parameters required for configuring the NE data. 6.11.8.3 Configuration Process This section describes the process of data configuration.

This section describes the networking information about the NEs. In Figure 6-76, PW APS is configured for NE1 to achieve RNC dual-homing. Figure 6-76 Network diagram of PW APS
MC-PW APS Working Tunnel ID: 1501
NE2
DNI-PW NodeB NE1 Protection Tunnel ID: 1502 NE3 RNC
Issue 02 (2011-01-20)
6-175
6 Packet Features
The service requirements are as follows: l l l A working tunnel is configured with an ID of 1501, and a protection tunnel is configured with an ID of 1502. Three unprotected PWE3 services are created on the working tunnel. Table 6-66 provides the service planning information. Only one PWE3 service is configured into a PW APS protection group. The other two services are configured into its slave protection pairs. This means that the two services will be switched if the PWE3 service in the PW APS protection group is switched.
Table 6-66 Planning information about PW APS Parameter Service ID Protection type CES Service 201 PW APS protection Ethernet Service 202 Slave protection pair ATM Service 203 Slave protection pair

Planning Information About a Protection PW

Table 6-67 Planning information about a protection PW Parameter Protection type Protection PW ID Incoming label Outgoing label Protection tunnel CES Service (ID = 201) PW APS protection 801 801 801 1502 Ethernet Service (ID = 202) Slave protection pair 802 802 802 1502 ATM Service (ID = 203) Slave protection pair 803 803 803 1502
Planning Information About a PW APS Protection

Table 6-68 Planning information about a PW APS protection group Parameter Protection type Protection Group ID
6-176
CES Service (ID = 201) PW APS protection 1

Issue 02 (2011-01-20)
6 Packet Features
Parameter Protection Mode Switching Mode Revertive Mode Switchover Restoration Time Switchover Delay Time
CES Service (ID = 201) 1:1 Dual-ended switching Revertive 5 min 0
Table 6-69 Planning information about slave protection pairs Parameter Protection type Protection Group ID Ethernet Service (ID = 202) Slave protection pair 1 ATM Service (ID = 203) Slave protection pair 1

Procedure
Step 1 See A.7.5.1 Creating a PW APS Protection Group, and create a PW APS protection group for the CES service (ID = 201). l The values of parameters in the General Attributes tab are provided as follows. Parameter PW ID PW Signaling Type PW Encapsulation Type Direction PW Ingress Label/Source Port PW Egress Label/Sink Port Tunnel Type Tunnel Protection PW 801 Static MPLS Bidirectional 801 801 MPLS 1501
l The values of parameters in the Protection Group tab are provided as follows.
Issue 02 (2011-01-20)
6-177
6 Packet Features
Parameter Protection Group ID Enabling Status Switching Mode Revertive Mode Switchover Restoration Time(min) Switchover Delay Time(100ms)
Value 1 Disabled Dual-ended switching Revertive 5 0
l The values of parameters in the PW OAM tab are provided as follows. Parameter Detection Mode Detection Packet Type Detection Packet Period (ms) PW ID to be Received Working PW Auto-Sensing FFD 3.3 201 Protection PW Auto-Sensing FFD 3.3 801
Step 2 See A.7.5.2 Configuring Slave Protection Pairs of PW APS, and configure slave protection pairs for the Ethernet service (ID = 202) and ATM service (ID = 203). The values of parameters in the Slave Protection Pair tab are provided as follows. Parameter Protection Group ID Value 1
Step 3 See A.7.5.5 Enabling/Disabling PW APS Protection, and enable PW APS protection. ----End

Related Tasks
A.7.5.1 Creating a PW APS Protection Group A.7.5.2 Configuring Slave Protection Pairs of PW APS A.7.5.3 Querying PW APS Status A.7.5.4 Triggering PW APS Switching A.7.5.5 Enabling/Disabling PW APS Protection
6 Packet Features

When detecting an exception by performing PW APS operations, an NE reports the specific alarm.
Relevant Alarms
l PWAPS_LOST The PWAPS_LOST alarm indicates that the PW APS frame is lost. This alarm is reported when the APS frame is not received in the protection PW. l PWAPS_TYPE_MISMATCH The PWAPS_TYPE_MISMATCH alarm indicates the protection type mismatch. This alarm is reported when the PW APS protection type information contained in the PW APS frame that is received at the local end is inconsistent with the PW APS protection type that is configured. l PWAPS_PATH_MISMATCH The PWAPS_PATH_MISMATCH alarm indicates a mismatch between the working PW and protection PW of the APS. This alarm is reported when the working and protection PWs that are selected by the equipment at both ends of a protection group are not consistent. l PWAPS_SWITCH_FAIL The PWAPS_SWITCH_FAIL alarm indicates a protection switching failure. When a request signal contained in the APS frame that is sent from a port is not consistent with the bridge signal contained in the APS frame that is received at this port, if this condition lasts for more than 50 ms, the switching fails. In this case, this alarm is reported.
Relevant Events
Reporting of the PW APS protection switching This event indicates that PW APS protection switching occurs.
6.11.11 FAQs
This section provides answers to the questions that are frequently raised when PW APS is used. Question: What are the differences between PW APS and MPLS APS? Answer: Table 6-70 lists the main differences between PW APS and MPLS APS. Table 6-70 Differences between PW APS and MPLS APS Item Protection object Detection mechanism MPLS APS LSP MPLS OAM PW APS PW PW OAM
Issue 02 (2011-01-20)
6-179
6 Packet Features
Item Typical application
MPLS APS Implementing MPLS APS for two LSPs that are cosourced and co-sinked
PW APS There are mainly two typical applications: l Implementing MPLS APS for two PWs that are co-sourced and co-sinked l Implementing PW APS with the cooperation of MC-PW APS
6.12 ATM Basics

This chapter describes the basics of asynchronous transfer mode (ATM). 6.12.1 Introduction This section provides the definition of ATM and describes its purpose. 6.12.2 Basic Concept This section describes the basic concepts associated with ATM. 6.12.3 Specifications This section describes the specifications for ATM. 6.12.4 Reference Standards and Protocols This section describes the standards and protocols associated with ATM basics. 6.12.5 Availability This section describes the support required by the application of the ATM feature and its dependencies. 6.12.6 Principles This section describes the basic transfer process of ATM cells. 6.12.7 Relevant Alarms and Events When a fault is detected in AT services, an NE reports the specific alarm. 6.12.8 FAQs This section provides the answers to the questions that are frequently raised when ATM is adopted.
6.12.1 Introduction
This section provides the definition of ATM and describes its purpose.
Definition
ATM is implemented based on cells. It adopts the fast packet switching technology and statistical multiplexing approach to transmit a wide range of services such as voice, data, and video. ATM has the following features:
6 Packet Features
l l l
An ATM network is connection-oriented. This means that two ATM end users can communicate with each other only after a connection is established. Fixed-length ATM cells are packet switched. A service contract (see 6.15 ATM Traffic Management) is established at the time a connection is set up to assure ATM services of expected QoS objectives.
Purpose
If the NEs on a network do not support the ATM function, the ATM services carried on PDH/ SDH are transmitted as ordinary PDH/SDH services. Nevertheless, if the NEs on the network support the ATM function, the ATM services can be transmitted in form of ATM cells, as shown in Figure 6-77. This method allows more efficient transmission by using the features of ATM packet switching, provides ATM-layer protection, and assures ATM services of expected QoS objectives. Figure 6-77 Network supporting the ATM function
transport network NodeB
ATM cell stream
ATM switch
6.12.2 Basic Concept

This section describes the basic concepts associated with ATM. 6.12.2.1 Architecture and Interfaces of an ATM Network An ATM network comprises a number of ATM switches that are interconnected through various ATM interfaces. 6.12.2.2 ATM Link ATM links, classified into virtual channel (VC) links and virtual path (VP) links, extend between two adjacent ATM switches. 6.12.2.3 ATM Connection ATM links are concatenated to form an ATM connection, which provides the end-to-end transmission function. 6.12.2.4 ATM Switching ATM switching allows one ATM switch to switch the cells on an ATM link to another ATM link for establishment of an ATM connection.
6 Packet Features
6.12.2.5 ATM Cell Format The ATM cell consists of a 5-octet header and a 48-octet payload field. 6.12.2.6 ATM Protocol Reference Model The ATM protocol reference model is composed of a user plane, a control plane, and a management plane.
6.12.2.1 Architecture and Interfaces of an ATM Network

An ATM network comprises a number of ATM switches that are interconnected through various ATM interfaces. Figure 6-78 Architecture and interfaces of an ATM network
NNI
NNI B-ICI
NNI
NNI NNI
UNI
NNI ATM network 1 UNI
ATM network 2
User equipment
ATM switch
As shown in Figure 6-78, the interfaces used on an ATM network are classified into the following types. l l l User-to-Network Interface (UNI) A UNI connects customer equipment to an ATM switch. Network-to-Network Interface (NNI) An NNI connects one ATM switch to another ATM switch. B-ISDN Inter Carrier Interface (B-ICI) A B-ICI connects ATM switches from different network carriers for internal connections between multiple ATM network carriers.
6.12.2.2 ATM Link

ATM links, classified into virtual channel (VC) links and virtual path (VP) links, extend between two adjacent ATM switches.
6-182
Issue 02 (2011-01-20)
6 Packet Features
Figure 6-79 ATM links
VC VC VC VC
VP VP VP VP Transmission path
ATM swtich
As shown in Figure 6-79, VC links are virtual links transmitting ATM cells between two adjacent ATM switches. Multiple VC links with the same attributes can be bound to form a VP link. A VP link is identified by a virtual path identifier (VPI). That is, each VP link transmits ATM cells that carry its VPI value. A VC link is identified by a virtual channel identifier (VCI). That is, each VC link transmits ATM cells that carry its VPI and VCI values. VPI and VCI are only valid on the local interface. That is, another physical channel may have a VP link with the same VPI value and a VC link with the same VCI value.
6.12.2.3 ATM Connection

ATM links are concatenated to form an ATM connection, which provides the end-to-end transmission function. ATM connections are available in two categories. l Virtual path connection (VPC) VP links are concatenated to form a VPC, as shown in Figure 6-80. The VP links in the same VPC can have the same or different VPI values.
Issue 02 (2011-01-20)
6-183
6 Packet Features
Figure 6-80 VPC

VPC VPI=12 VCI=35 VPI=12 VCI=40 VPI=22 VCI=35 VPI=22 VCI=40
VP link(VPI=12) ATM cell ATM switch
VP link(VPI=22)
Virtual channel connection (VCC) VC links are concatenated to form a VCC, as shown in Figure 6-81. The VC links in the same VCC can have the same or different VCI values. Figure 6-81 VCC
VCC VPI=12 VCI=35 VPI=22 VCI=40
VC link ( VPI=12, VCI=35) ATM cell ATM switch
VC link ( VPI=22, VCI=40)
As shown in Figure 6-82, if multiple VCCs have the overlapped transmission path, the overlapped connections can be consolidated into a VPC so that these VCCs can share one VPC. This method simplifies the processing of ATM connections at the intermediate ATM switches.
6-184
Issue 02 (2011-01-20)
6 Packet Features
Figure 6-82 VCCs sharing a VPC

VCC1
VPI=2 VCI=30
VPI=32 VCI=45
VP link ( VPI=12)
VP link ( VPI=22)
(V PI VC =4 l 2, ink VC I= 50 )
(V
VPI=42 VCI=50
VPI=12 VPI=12 VCI=55 VCI=35 VPC VCC2
VPI=22
VPI=22
VCI=55 VCI=35
VPI=52 VCI=65
ATM cell ATM switch
6.12.2.4 ATM Switching

ATM switching allows one ATM switch to switch the cells on an ATM link to another ATM link for establishment of an ATM connection. ATM switching is available in two types, namely, VC switching and VP switching, as shown in Figure 6-83. l VC switching In VC switching, an ATM switch switches the cells on a VC link to another VC link. In this case, both the VPI and VCI values of the cells are exchanged. l VP switching In VP switching, an ATM switch switches the cells on a VP link to another VP link. In this case, only the VPI values of the cells are exchanged.
Issue 02 (2011-01-20)
PI VC =3 l 2, ink VC I= 45 )
(V
) k 30 lin CI= VC 2, V = PI
(V k 6 lin CI= VC 2, V =5 PI 5)
6-185
6 Packet Features
Figure 6-83 ATM switching

VC switch
VCI 1 VPI 1
VCI 2
VCI 3 VPI 3
VCI 4 VPI 2 VPI 2 VCI 4 VCI 3 Port 2
Port 1 VCI 1 VCI 2
VPI 1
VPI 3
VCI 1 VCI 1 VCI 2 VPI 4 VP switch VPI 5 VCI 2 Port 3
Port
6.12.2.5 ATM Cell Format

The ATM cell consists of a 5-octet header and a 48-octet payload field.
ATM Cell Structure

Figure 6-84 shows the ATM cell structure. Figure 6-84 ATM cell structure
Bits: 8 7 6 5 4 3 2 1 1
...
Header (5 octets) Payload (48 octets)
5 6
...
53-octet cell
53
Transmission of ATM cells adheres to the following conventions: l l

6-186
Bits within an octet are sent in descending order by number, starting from bit 8. Octets are sent in ascending order by number, starting from octet 1.
6 Packet Features
Cell Header Format

The header structure at a UNI is slightly different from the header structure at an NNI, as shown in Figure 6-85 and Figure 6-86. Figure 6-85 Header structure at a UNI
8 7 6 GFC VPI VCI VCI Laye 2 r PDU Laye 2 r HEC PDU PT CLP EX P 5 4 3 VPI S VCI TT L 2 1 Octet 1 2 3 4 5
Figure 6-86 Header structure at an NNI

8 7 6 5 VPI VPI VCI VCI Laye 2 r PDU Laye 2 r HEC PDU PT CLP EX P S VCI TT L 4 3 2 1 Octet 1 2 3 4 5
The cell header consists of the following fields: l VPI The virtual path identifier (VPI) field, identifying a VP link that carries the cell. At an NNI, the VPI field contains 12 bits, whereas the VPI field at UNI contains 8 bits. l VCI The virtual channel identifier (VCI) field identifies a VC link with the VPI field. The VCI field contains 16 bits. l HEC The header error control (HEC) field contains 8 bits. If a cell with header errors is detected, HEC performs single-bit error correction for the cell. HEC also performs cell delineation. The header of a cell can be positioned based on the relationship between the HEC field and
6 Packet Features
its previous 4 octets. HEC, however, needs to be computed for each link because different links have different VPI/VCI values. l PT The payload type (PT) field contains 3 bits. When bit 3 is 0, the cell is a data cell; when bit 3 is 1, the cell is an OAM cell. In regards to an OAM cell, the last 2 bits indicate the type of the OAM cell. In regards to a data cell, bit 2 is an explicit forward congestion indication (EFCI) and bit 1 is used for ATM adaptation layer 5 (AAL5). l l CLP The cell loss priority (CLP) field contains 1 bit and is used for congestion control. GFC The generic flow control (GFC) field contains 4 bits and is used for UNIs only. When this function is disabled, the GFC field is set to 0000.
6.12.2.6 ATM Protocol Reference Model

The ATM protocol reference model is composed of a user plane, a control plane, and a management plane.
NOTE
This section describes only the functions of the user plane.
Physical Layer
The physical layer primarily provides transmission paths for ATM cells. It adds transmission overheads to the cells from the ATM layer to form continuous bit streams. It also extracts valid cells from the received continuous bit streams transmitted on a physical medium and sends the valid cells to the ATM layer. The physical layer consists of two sublayers, namely, transmission convergence (TC) sublayer and physical medium (PM) sublayer. The PM sublayer is below the TC sublayer. l PM sublayer The PM sublayer defines physical medium interfaces, line coding, and bit timing. Currently, ITU-T defines only SDH-based and cell-based 155/622/51 Mbit/s interfaces and PDHbased E1 interfaces. Other physical medium interfaces are defined by other organizations such as ATM forum. l TC sublayer The TC sublayer primarily performs the following functions: Cell rate decoupling Cell rate decoupling includes insertion of idle cells, in order to adapt the rate of valid ATM cells to the payload capacity of the transmission system. Header error control (HEC) sequence generation and cell header verification The HEC mechanism is used for cell delineation. Specifically, the cyclic redundancy check (CRC) is performed for every 32 bits and the result is compared with the next 8 bits. If the two values are identical, a cell header is considered found. The HEC mechanism also performs single-bit error correction and multi-bit error detection, and discards cells with erroneous headers. Transmission frame adaptation and transmission frame generation/recovery Transmission frame adaptation and transmission frame generation/recovery apply to a transmission system based on frames. When such a transmission system transports ATM
6 Packet Features
cells, the ATM cells must be loaded into transmission frames. For example, ITU-T G. 804 recommends that ATM cells be mapped into timeslots 1-15 and 17-31 in E1 frames as specified by ITU-T G.704, that is, voice timeslots in PCM30 CRC-4 frames. When an ATM cell is mapped, its 8-bit code must be aligned with the 8-bit code in the E1 frame. Before being mapped into the E1 frame, the payload of the ATM cell (48 bytes) must be scrambled.
ATM Layer
Residing above the physical layer, the ATM layer uses the service provided by the physical layer to communicate with the peer layer by means of cells and to provide services for the AAL. The characteristics of the ATM layer are independent of the physical medium or the service transmitted at the physical layer. The ATM layer only identifies and processes cell headers. ATM layer functions include the following categories. l Cell multiplexing/demultiplexing Cell multiplexing/demultiplexing is implemented at the interface between the ATM layer and the TC sublayer of the physical layer. In the transmit direction, the ATM layer combines cells with different VPI/VCI values into a cell flow and sends the cell flow to the physical layer. In the receive direction, the ATM layer identifies cell VPI/VCI values from the physical layer and directs the cells to appropriate modules. For example, if the ATM layer identifies signaling cells, it sends the cells to the control plane; if the ATM layer identifies management cells such as OAM cells, it sends the cells to the management plane. l Cell header operation Cell header operations include VPI/VCI filling and payload type filling at user terminals, and VPI/VCI translation at network nodes. l Generic flow control The generic flow control (GFC) function is maintained by using the GFC bits in the header. The OptiX RTN 980 does not support this function.
AAL
Residing above the ATM layer, the AAL provides various services with different processing methods because the AAL is dependent on services. Though the methods vary in different services, the AAL has to perform certain common operations, including dividing the information flows from the upper layer into 48-octet ATM service data units (SDU), and reassembling and recovering ATM-SDUs from the ATM layer for retransmission to the upper layer. As different services require different adaptation functions, ITU-T defines AAL1, AAL2, AAL3/4, and AAL5 according to the timing, bit rates, and connection modes of the source and sink.
NOTE
The OptiX RTN 980 does not provide AAL processing.
This section describes the specifications for ATM. Table 6-71 lists the specifications for ATM.
6 Packet Features
Table 6-71 Specifications for ATM Item Maximum number of ATM services Maximum number of ATM connections ATM service type Specifications 64 256 UNI-UNI UNI-NNI
NOTE l UNI-UNI services correspond to ordinary ATM connections. l UNI-NNI services correspond to ATM PWE3 connections.
ATM service transparent transmission Maximum number of transparently transmitted ATM services Range of VPI value
Supported only by the MD1/ML1 board ML1: 16 MD1: 32 UNI port: 0 to 255 NNI port: 0 to 4095
Range of VCI value VC switching VP switching ATM traffic management
32 to 65535 Supported Supported Supported

ATM OAM
Supported
ATM PWE3
Supported

This section describes the standards and protocols associated with ATM basics. The following standards and protocols are associated with ATM basics: l l l l l
6-190
ITU-T I.311: B-ISDN General Network Aspects ITU-T I.327: B-ISDN Functional Architecture ITU-T I.361: B-ISDN ATM Layer Specification ITU-T I.413: B-ISDN User-network Interface ITU-T I.460: Multiplexing, Rate Adaption and Support of Existing Interfaces
6 Packet Features
ITU-T I.500: General Structure of the ISDN Interworking Recommendations
6.12.5 Availability
This section describes the support required by the application of the ATM feature and its dependencies.

Table 6-72 Hardware and version support Feature ATM Applicable Board CSHN ML1 MD1 Applicable Hardware Version All the versions All the versions All the versions Applicable Product Version V100R003C00 and later V100R003C00 and later V100R003C00 and later
The dependencies between the ATM feature and other features are as follows: l l l The ATM PWE3 feature is used to emulate ATM services on a PSN. The IMA feature is used to demultiplex and multiplex ATM services over multiple lowspeed links. The QoS of ATM services can be guaranteed by using ATM traffic management policies.
6.12.6 Principles
This section describes the basic transfer process of ATM cells. As shown in Figure 6-87, the NodeB backhauls base station services in ATM mode. The ATM cells from the NodeB are forwarded hop by hop and finally arrive at the RNC by using ATM switches. During the backhaul, an ATM switch forwards the ATM cells as follows: l Sets up the ATM connection routing table in a static manner or by means of signaling. The routing table records the connection relationships of VP links and VC links between interfaces. Extracts ATM cells from the received transmission frame, and performs cell delineation and error control. Identifies the VPI and VCI values in the ATM cells. If the ATM cells are identified as OAM cells, the ATM switch performs OAM processing; if the ATM cells are identified as user cells, the ATM switch translates the VPI and VCI values in the ATM cells based on the ATM connection routing table.
l l
Issue 02 (2011-01-20)
6 Packet Features
l l
Forwards ATM cells in the light of preset ATM traffic management policies. Performs rate decoupling for the ATM cells based on the type of sink interface, and then encapsulates and maps the ATM cells into transmission frames for transmission to the next hop.
Figure 6-87 Transfer of ATM cells

VPI = 40 VCI = 15 1 2 VPI = 45 VCI = 20 1 2 VPI = 55 VCI = 25 1 2 VPI = 60 VCI = 30
NodeB
ATM switch
ATM switch ATM connection routing table Source port Source VCI Source VPI Port 1 20 45 Sink port Port 2 Sink VCI 25 Sink VPI 55
ATM switch ATM connection routing table Source port Source VCI Source VPI Port 1 25 55 Sink port Port 2 Sink VCI 30 Sink VPI 60
RNC
ATM connection routing table Source port Source VCI Source VPI Port 1 15 40 Sink port Port 2 Sink VCI 20 Sink VPI 45
ATM cell 1 2 Port 1 Port 2

When a fault is detected in AT services, an NE reports the specific alarm.
Relevant Alarms
l l l There is no alarm associated with common ATM services. For the alarms associated with ATM PWE3 services, see 6.7.10 Relevant Alarms and Events. For the alarms associated with IMA, see 6.13.10 Relevant Alarms and Events.

None.
6.12.8 FAQs
This section provides the answers to the questions that are frequently raised when ATM is adopted. Question: Can the range of VCI value be set on the OptiX RTN 980? Answer: You cannot set the range of VCI values on the OptiX RTN 980.
6.13 IMA
This chapter describes the inverse multiplexing for ATM (IMA) feature. 6.13.1 Introduction
6 Packet Features
This section provides the definition of IMA and describes its purpose. 6.13.2 Basic Concepts This section describes the basic concepts associated with IMA. 6.13.3 Specifications This section describes the specifications for IMA. 6.13.4 Reference Standards and Protocols This section describes the standards and protocols associated with IMA. 6.13.5 Availability This section describes the support required by the application of the IMA feature and its dependencies. 6.13.6 Principles This section describes the principles of the IMA feature. 6.13.7 Configuration Procedure On an OptiX RTN 980, an ATM trunk is used to describe an IMA group. Therefore, the key to configuring IMA is to configuring an ATM trunk. 6.13.8 Configuration Example This section uses an example to describe how to plan and configure IMA according to network conditions. 6.13.9 Task Collection This section provides the hyperlinks of the operation tasks associated with the feature. 6.13.10 Relevant Alarms and Events When a fault is detected in an IMA group, an NE reports the specific alarm. 6.13.11 FAQs This section provides answers to the questions that are frequently raised when IMA is used.
6.13.1 Introduction
This section provides the definition of IMA and describes its purpose.
Definition
The IMA technology multiplexes multiple low-speed ATM links into a high-speed link. Specifically, the IMA technology provides inverse multiplexing of an ATM cell stream over multiple low-speed links and retrieves the original stream at the far-end from these physical links. Figure 6-88 IMA
IMA group PHY Link 0 PHY Link 1 PHY PHY PHY PHY IMA group
Link 2
TRUNK link
ATM layer cells
Issue 02 (2011-01-20)
6-193
6 Packet Features
The IMA technology helps to group multiple physical links to form a higher bandwidth logical link whose rate is approximately the sum of the link rates. When the member links in the IMA group are dynamically added/deleted, or fail/recover, the logical link changes only in bandwidth. The services on the logical link are not interrupted only if the bandwidth of the logical link is not lower than the required minimum bandwidth.
Purpose
With the IMA technology, the transport network can transmit ATM services from customer equipment on an IMA group formed by multiple low-speed links (for example, the three E1 links shown in Figure 6-89), therefore increasing link bandwidth and providing link protection. Figure 6-89 Typical application of the IMA technology
IMA group
NodeB
E1 link Packet transmission equipment

This section describes the basic concepts associated with IMA. 6.13.2.1 IMA Protocol Reference Model To implement the IMA technology, the ATM protocol reference model defines an IMA sublayer between the transmission convergence (TC) sublayer and the ATM layer. 6.13.2.2 IMA OAM Cells IMA OAM cells are transmitted at the ATM physical layer. By processing IMA OAM cells, the IMA sublayer provides inverse multiplexing for ATM. Two IMA OAM cells are defined: filler cells and IMA control protocol (ICP) cells. 6.13.2.3 IMA Frame Format To retrieve the original ATM cell stream from links with differential delays, the receive end needs to receive ATM cells according to the IMA frame format. 6.13.2.4 IMA Timing For synchronization between links of an IMA group, the IMA group needs to adjust cell transmit rates on the links according to the timing information. Two IMA timing configuration modes are available: common transmit clock (CTC) configuration and independent transmit clock (ITC) configuration.
6.13.2.1 IMA Protocol Reference Model

To implement the IMA technology, the ATM protocol reference model defines an IMA sublayer between the transmission convergence (TC) sublayer and the ATM layer. Figure 6-90 provides the positions and functions of the IMA sublayer in the ATM protocol reference model.
6 Packet Features
Figure 6-90 IMA protocol reference model

User plane functions ATM layer ATM cell stream splitting and reconstruction ICP cell insertion/removal Cell rate decoupling IMA frame synchronization Stuffing Discarding of cells with bad HEC IMA connectivity ICP cell errors (OIF) LIF/LODS/RDI-IMA defect processing RDI-IMA alarm generation Tx/Rx IMA link state report IMA group configuration Link addition/deletion ATM cell rate change IMA group failure notification IMA statistics Control plane functions Management plane functions
IMA specific TC sublayer
Physical layer
Interface specific TC sublayer
Physical medium dependent sublayer
6.13.2.2 IMA OAM Cells

IMA OAM cells are transmitted at the ATM physical layer. By processing IMA OAM cells, the IMA sublayer provides inverse multiplexing for ATM. Two IMA OAM cells are defined: filler cells and IMA control protocol (ICP) cells.
Filler Cell
Filler cells are used to stuff IMA frames when no ATM cell arrives at the ATM layer. Table 6-73 provides the format definition of the filler cell. Table 6-73 Filler cell format Octet 1-5 6 Label ATM cell header OAM label Comment Octet 1 = 00000000, octet 2 = 00000000, octet 3 = 00000000, octet 4 = 00000001, octet 5 = valid HEC IMA version value l 00000001: version 1.0 l 00000011: version 1.1 7 Cell ID Link ID 8-51 52-53 Unused CRC error control Bit 7: IMA OAM cell type (0: filler cell; 1: ICP cell) Bits 6-0: unused and set to 0 Set to 0x6A as defined in ITU-T I.432 for unused bytes Bits 15-10: reserved for future use and set to 0 Bits 9-0: CRC-10 as specified in ITU-T I.610
Issue 02 (2011-01-20)
6-195
6 Packet Features
ICP Cell
ICP cells are used to communicate information for setting up the IMA protocol between two IMA units. Table 6-74 provides the format definition of the ICP cell. Table 6-74 ICP cell format Octet 1-5 6 Label ATM cell header OAM label Comment Octet 1 = 00000000, octet 2 = 00000000, octet 3 = 00000000, octet 4 = 00000001, octet 5 = valid HEC IMA version value l 00000001: version 1.0 l 00000011: version 1.1 7 Cell ID Link ID Bit 7: IMA OAM cell type (1: ICP cell; 0: filler cell) Bits 6-5: unused and set to 0 Bits 4-0: logical ID for physical link range 8 IMA frame sequence number (IFSN) ICP cell offset 0 to 255 and cycling
Range: 0 to M-1 Indicates position of ICP cell within the IMA frame. M indicates the length of the IMA frame.
10
Link stuff indication (LSI)
Bits 7-3: unused and set to 0 Bits 2-0: link stuffing indication l 111 = no imminent stuff event l 100 = stuff event in 4 ICP cell locations (optional) l 011 = stuff event in 3 ICP cell locations (optional) l 010 = stuff event in 2 ICP cell locations (optional) l 001 = stuff event at the next ICP cell location l 000 = one out of the 2 ICP cells comprising the stuff event
11
Status and control change indication (SCCI) IMA ID
Bits 7-0: status change indication; 0 to 255 and cycling (count to be incremented every change of octets 12-49)
12
Bits 7-0: IMA ID
6-196
Issue 02 (2011-01-20)
6 Packet Features
Octet 13
Label IMA group status and control
Comment Bits 7-4: IMA group state l 0000 = start-up l 0001 = start-up-ack l 0010 = config-aborted - unsupported M l 0011 = config-aborted - incompatible group symmetry l 01XX = config-aborted - other reasons l 1000 = insufficient-links l 1001 = blocked l 1010 = operational l Others: reserved Bits 3-2: IMA group symmetry mode l 00 = symmetrical configuration and operation l 01 = symmetrical configuration and asymmetrical operation (optional) l 10 = asymmetrical configuration and asymmetrical operation (optional) l 11 = reserved Bits 1-0: IMA frame length (M) l 00: M = 32 l 01: M = 64 l 10: M = 128 l 11: M = 256
14
Transmit timing information Tx test control
Bits 7-6: unused and set to 0 Bit 5: transmit clock mode (0: ITC mode; 1: CTC mode) Bits 4-0: Tx LID of the timing reference (0 to 31) Bit 5: test link command (0: inactive; l: active) Bits 4-0: Tx LID of test link (0 to 31)
15
16 17 18
Tx test pattern Rx test pattern Link 0 information
Bits 7-0: Tx test pattern (0 to 255) Bits 7-0: Rx test pattern (0 to 255) Bits 7-5: transmit state Bits 4-2: receive state Bits 1-0: Rx defect indicators
19-49 50 51
Link 1-31 information Unused End-to-end channel
Status and control of link with LID in the range 1-31 Set to 0x6A as defined in ITU-T I.432 for unused bytes Proprietary channel (set to 0 if unused)
Issue 02 (2011-01-20)
6-197
6 Packet Features
Octet 52-53
Label CRC error control
Comment Bits 15-10: reserved for future use and set to 0 Bits 9-0: CRC-10 as specified in ITU-T I.610
6.13.2.3 IMA Frame Format

To retrieve the original ATM cell stream from links with differential delays, the receive end needs to receive ATM cells according to the IMA frame format.
IMA Frame
The IMA frame is used as the unit of control in the IMA protocol. An IMA frame is defined as M consecutive cells (numbered 0 to M-1) on each link, across the linksa in an IMA group. M is called the length of an IMA frame.
NOTE
a: "Across the links" in an IMA group is the same as the mechanism in which the transmit end distributes cells from link to link within an IMA group. That is, ATM cells are placed on each link in a circulating manner.
One of the M cells on each link within an IMA group is an ICP cell; that is, the ICP cell is sent once on each link per IMA frame. The ICP cell may be at different positions on different links. In addition to ICP cells, each IMA frame has filler cells and ATM layer cells. The filler cells are used to fill IMA frames when no ATM cell is received, and are discarded at the receive end. The IFSN field in the ICP cell, indicating the sequence number of the IMA frame, increments from 0 to 255 and repeats the sequence. Within an IMA frame period, the ICP cells on all the links have the same IFSN value. Figure 6-91 shows an example of the transmission of IMA frames over three links in an IMA group. In IMA frame 0, the IFSN of the ICP cell is 0; in IMA frame 1, the IFSN of the ICP cell is 1; in IMA frame 2, the IFSN of the ICP cell is 2.
6-198
Issue 02 (2011-01-20)
6 Packet Features
Figure 6-91 Transmission of IMA frames over three links in an IMA group
IMA frame 2 ATM ... ATM ATM 2 F 1 F ICP2 0 F F IMA frame 1 ... F ATM 2 F 1 ICP1 ATM 0 IMA frame 0 ... F ATM 2 F 1 F ICP0 0 F Link 1
Link 0
M-1 F
M-1 ATM
M-1
... ICP2 ATM
... ICP1 ATM ATM ATM ATM
... ICP0 ATM
... ATM ATM ICP2
ATM
...
ATM ICP1 ATM ATM
...
ATM ICP0 ATM
Link 2
Time
ICP1 F ATM
1# ICP cell Filler cell ATM layer cell
ICP Cell Offset

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

The delay of each link in the IMA group is different (differential delay), so compensation must be performed at the receive end. The principle of the link differential delay compensation is using the buffer mechanism for compensation as the ICP cell offset of each link is fixed. Figure 6-92 shows the methods of compensating for the link differential delay. l l l The transmit end allocates the ICP cell offsets of 1, 0, and 2 to links 0, 1, and 2 respectively. During transmission, link 0 and link 2 have the same amount of propagation delay but link 1 has a delay one cell time longer than link 0 and link 2. At the receive end, the cells from each link enter the delay compensation buffer (DCB). In the DCB, the ICP cell of each link obtains its offset based on the IMA frame header. In this manner, the entire IMA frame is aligned. In this example, the offset of ICP1 is 0. Therefore, ICP1 in the DCB is moved to the frame header so that the entire IMA frame is aligned.
Issue 02 (2011-01-20)
6 Packet Features
Figure 6-92 Link differential delay compensation

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

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

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

Tx clock unit Local oscillator External source . . . Sw (1) 0 1 Rx Tx Link 1 Sw 0 1 Rx Link 0 Sw (0) Tx
...
Sw (N-1) 0 1
Tx Rx Link N-1
This section describes the specifications for IMA. Table 6-75 lists the specifications for IMA. Table 6-75 Specifications for IMA Item IMA protocol version Specifications Version 1.0 Version 1.1 Type of link carrying IMA services E1 Fractional E1
NOTE When Fractional E1 carries IMA services, the number of 64 kbit/s bound to each Fractional E1 must be the same and cannot be less than three.
Restarting the IMA protocol Dynamically adding/deleting IMA group members
Supported Supported
Issue 02 (2011-01-20)
6-201
6 Packet Features
Item Length of frame at the transmit end of an IMA group
Specifications 32 64 128 256
Symmetry mode Maximum delay between links Minimum number of active Tx/Rx links IMA timing mode
Symmetrical mode and symmetrical operation 1 ms to 120 ms ML1/MD1 board: 16 CTC ITC

This section describes the standards and protocols associated with IMA. The following standard is associated with IMA: The ATM Forum Technical Committee: Inverse Multiplexing for ATM (IMA) Specification Version 1.1 AF-PHY-0086.001
6.13.5 Availability
This section describes the support required by the application of the IMA feature and its dependencies.

Table 6-76 Hardware and version support Feature IMA Applicable Board CSHN ML1 MD1 Applicable Hardware Version All the versions All the versions All the versions Applicable Product Version V100R003C00 and later V100R003C00 and later V100R003C00 and later
The dependencies between the IMA feature and other features are as follows:
6 Packet Features
The IMA feature is used to demultiplex and multiplex ATM services over multiple low-speed links.
6.13.6 Principles
This section describes the principles of the IMA feature. Figure 6-94 shows the processing of an ATM cell stream in the IMA technology. l The IMA transmitter sends the ATM user cells and ICP cells from the ATM layer to the active member links within an IMA group. When the ATM user cells need to be transmitted but no cell is received from the ATM layer, filler cells are transmitted to maintain a continuous stream of IMA cells. The IMA receiver retrieves the original ATM cell stream by using the link differential delay compensation technique and then transmits the ATM cell stream to the ATM layer. When a member link in the IMA group is faulty, the transmitter and receiver transmit the new IMA frame wherein the member link is removed. In this manner, link protection is achieved.
l l
Figure 6-94 Processing of an ATM cell stream in the IMA technology

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

On an OptiX RTN 980, an ATM trunk is used to describe an IMA group. Therefore, the key to configuring IMA is to configuring an ATM trunk.
Information About Configuring an IMA Group

Information about configuring an IMA group involves binding an ATM trunk, configuring an IMA group, and configuring an ATM interface.
Issue 02 (2011-01-20)
6-203
6 Packet Features
Table 6-77 Information about configuring an IMA group Operation A.7.7.1 Binding ATM TRUNKs Description Required. l For ATM/IMA services, set Level to E1. For Fractional E1 services, set Level to Fractional E1. l Set the other parameters according to the planning information.
NOTE When the E1 frame mode is PCM 30, timeslot 16 cannot be bound.
Required. l For an ATM trunk requiring the IMA function, set IMA Protocol Enable Status to Enabled. l Set Clock Mode of the local NE and the NE at the opposite end of the IMA trunk to be the same as Clock Mode of the interconnected NodeB. l The other parameters are only valid for IMA E1 and Fractional IMA. The parameters at both ends of an IMA link must be set to the same, which are recommended to set to default values.
Optional. l It is recommended that you set Port Type and ATM Cell Payload Scrambling by default based on the type of access equipment. The parameter values must be the same for both ends of a link. l The other parameters take the default values.

This section uses an example to describe how to plan and configure IMA according to network conditions. 6.13.8.1 Network Diagram This section describes the networking information about NEs. 6.13.8.2 Service Planning The service planning information contains all the parameters required for configuring the NE data. 6.13.8.3 Configuration Process
6 Packet Features

This section describes the networking information about NEs. As shown in Figure 6-95, NE1 (an OptiX RTN 980) receives ATM services from the NodeB. The IMA group binds three E1 links to transmit services from the NodeB. IMA 1 connects to port 1 to port 3 on an ML1 board. NE1 has been configured with E1 port parameters based on E1 link conditions. Figure 6-95 Network diagram of IMA
IMA 1
R99
NodeB
NE1

Planning Information About an IMA Group

Table 6-78 ATM/IMA planning information (NE1) Parameter Bound port IMA protocol enabled status IMA protocol version IMA frame length IMA symmetric mode Minimum number of active links Differentiated delay tolerance Clock mode ATM port name Port type ATM cell payload scrambling
Issue 02 (2011-01-20)
4-ML1-1(TRUNK1) 4-ML1-1 to 4-ML1-3 Enabled 1.1 128 Symmetric 1 25 ITC conn_nodeb_trunk1 UNI Enabled
6-205
6 Packet Features
NOTE
l If carried over a single E1, ATM services from a NodeB are transmitted and received through UNI ports. In this case, the IMA protocol needs to be disabled. If carried over multiple E1s, ATM services from a NodeB are transmitted and received through IMA trunks. l Normally, set the IMA protocol version, IMA frame length, IMA symmetric mode, and differentiated delay tolerance of an NE (with IMA protocol enabled) to the same values as those of its interconnected equipment. Normally, the NodeB configurations are as follows: l IMA protocol version: 1.1 l IMA frame length: 128 l IMA symmetric mode: symmetrical mode and symmetrical operation l Differentiated delay tolerance: 25 l The clock modes must be the same at both ends of an IMA trunk. The default clock mode for a BTS is ITC. Therefore, the clock mode is set to ITC for the NE that is interconnected with the BTS and the NE at the opposite end of the IMA link.

Procedure
Step 1 Configure IMA information. 1. A.7.7.1 Binding ATM TRUNKs Parameter Available Boards Configuration Ports Level Available Resources Trunk1 4-ML1 4-ML1-1(Trunk1) E1 4-ML1-1(conn_nodeb_ima1) to 4-ML1-3 (conn_nodeb_ima3)
2.
A.7.7.2 Configuring an IMA group Parameter IMA Protocol Enable Status IMA Protocol Version IMA Transmit Frame Length IMA Symmetry Mode Maximum Delay Between Links (ms) Clock Mode 4-ML1-1(Trunk1) Enabled 1.1 128 Symmetrical Mode and Symmetrical Operational 25 ITC
Issue 02 (2011-01-20)
6-206
6 Packet Features
3.
A.7.7.3 Setting ATM Port Parameters Parameter Name Port Type ATM Cell Payload Scrambling 4-ML1-1(Trunk1) conn_nodeb_trunk1 UNI Enabled
----End

Related Tasks
A.7.7.1 Binding ATM TRUNKs A.7.7.2 Configuring an IMA group A.7.7.3 Setting ATM Port Parameters A.7.7.4 Querying Running Status of an IMA Group A.7.7.5 Querying Link Running Status of an IMA Group

When a fault is detected in an IMA group, an NE reports the specific alarm.
Relevant Alarms
l IMA_GROUP_LE_DOWN The IMA_GROUP_LE_DOWN alarm indicates that the IMA group at the local end fails. This alarm indicates that at the local end, the IMA protocol is not activated, or that the actual number of active links in the IMA group is less than the minimum number of active links in the IMA group. l IMA_GROUP_RE_DOWN The IMA_GROUP_RE_DOWN alarm indicates that the IMA group at the remote end fails. This alarm indicates that at the remote end, the IMA protocol is not activated, or that the actual number of active links in the IMA group is less than the minimum number of active links in the IMA group. l IMA_TXCLK_MISMATCH The IMA_TXCLK_MISMATCH alarm indicates that transmit clock modes of an IMA group are inconsistent at the two ends.

None.
6 Packet Features
6.13.11 FAQs
This section provides answers to the questions that are frequently raised when IMA is used. Question: Why are the corresponding alarms reported when the E1s in one IMA group are interconnected with the E1s in different IMA groups? Answer: The E1s in one IMA group cannot be interconnected with the E1s in different IMA groups. Otherwise, the alarms associated with E1 links persist. If the E1s in one IMA group are interconnected with the E1s in different IMA groups, reconfigure the E1 links in the IMA group, or successfully negotiate the E1s in the IMA group with the E1s in another group. For example, the IMA1 group has multiple E1 link members. One E1 in the IMA1 group is interconnected with an E1 in the IMA2 group. The other E1s in the IMA1 group are idle, and the statuses of the IMA1 and IMA2 groups and E1 links are normal. If an idle E1 in the IMA1 group is interconnected with an E1 in the IMA3 group, the E1 in the IMA1 group may report the corresponding alarms. Even if the E1 in the IMA1 group is disconnected from the E1 in the IMA3 group, the alarms persist. In this case, the E1 link member must be reconfigured in the IMA1 group. Alternatively, correctly activate its corresponding E1 in the IMA3 group. Afterwards, the alarms can be cleared.
6.14 ATM OAM

This chapter describes the ATM OAM feature. 6.14.1 Introduction This section provides the definition of ATM OAM and describes its purpose. 6.14.2 Basic Concepts This section describes the basic concepts associated with ATM OAM. 6.14.3 Specifications This section describes the specifications for ATM OAM. 6.14.4 Reference Standards and Protocols This section describes the standards and protocols associated with ATM OAM. 6.14.5 Availability This section describes the support required by the application of the ATM OAM feature and its dependencies. 6.14.6 Principles The functions of ATM OAM are implemented by means of specific ATM OAM cells. 6.14.7 Configuration Procedure The ATM OAM configurations of an F4 flow are the same as those of an F5 flow. 6.14.8 Configuration Example This section uses an example to describe how to plan and configure ATM OAM according to network conditions. 6.14.9 Task Collection This section provides the hyperlinks of the operation tasks associated with the feature. 6.14.10 Relevant Alarms and Events When ATM OAM detects a fault, an NE reports the specific alarm.
6 Packet Features
6.14.11 FAQs This section provides answers to the questions that are frequently raised when ATM OAM is used.
6.14.1 Introduction
This section provides the definition of ATM OAM and describes its purpose.
Definition
ATM OAM is used for detecting and locating ATM faults, and monitoring ATM performance. In this document, ATM OAM refers to OAM only at the ATM layer and implements various OAM functions by means of specific ATM OAM cells.
Purpose
ATM OAM provides segment-based ATM OAM between the CE and the PE and end-to-endbased ATM OAM between CEs. As shown in Figure 6-96, ATM OAM cells are transmitted and detected between the CE and the PE, or between the CEs to monitor the ATM link. Figure 6-96 Typical application of ATM OAM
CE1 (NodeB)
PE1
PE2
CE2 (RNC)
Segment check End-to-end check

This section describes the basic concepts associated with ATM OAM. 6.14.2.1 ATM OAM Levels ATM OAM is performed on five OAM hierarchical levels. Three levels are associated with the physical layer, and two levels are associated with the ATM layer. 6.14.2.2 Segment and End Attributes and Directions of CPs Connection points (CPs) are reference points which are defined along a VPC/VCC. 6.14.2.3 ATM OAM Functions The equipment supports the following ATM OAM functions: alarm indication signal (AIS), remote defect indication (RDI), continuity check (CC), and loopback (LB).
6 Packet Features
6.14.2.1 ATM OAM Levels

ATM OAM is performed on five OAM hierarchical levels. Three levels are associated with the physical layer, and two levels are associated with the ATM layer. ATM OAM checks an ATM link by inserting certain OAM cells of the standard cell structure into the user cell flow. As specified in Table 6-79, ATM OAM is classified into five hierarchical levels. Table 6-79 OAM levels Flow F1 F2 F3 Level Regenerator section level Digital section level Transmission path level Description F1, F2, and F3 are OAM flows at the physical layer. The generation of OAM flows at the physical layer and the implementation of the OAM functions depend on the transport mechanism of the transmission system. Three types of transmission can be provided on ATM networks: l SDH-based transmission system l Cell-based transmission system l PDH-based transmission system F4 and F5 are OAM flows at the ATM layer. Independent of a transmission system, implementation of the OAM functions at the ATM layer is based on VPs/VCs. As an OAM cell flow in the virtual path connection (VPC), F4 provides VP-level operation management and maintenance functions. As an OAM cell flow in the virtual channel connection (VCC), F5 provides VC-level operation management and maintenance functions. After the OAM function in F4 and F5 flows is activated, corresponding OAM cells are inserted into user cells. From the perspective of the functioning span, there are two types of F4 flows and two types of F5 flows. These are: l End-to-end F4 flow and end-to-end F5 flow, which are used for end-to-end communication of virtual connections. l Segment F4 flow and segment F5 flow, which are used for communication within the bounds of one virtual connection or multiple interconnected virtual connections.
F4 F5
Virtual path level Virtual channel level
6.14.2.2 Segment and End Attributes and Directions of CPs

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

The segment and end attributes include:
6 Packet Features
l l l l
End point: refers to the end point for an ATM network connection or generally refers to the edge on an ATM network. Segment point: refers to the end point of a segment. One ATM link consists of multiple segments. Segment-end point: refers to the edge of a segment and an end. Intermediate point: refers to the OAM node between segment points or end points. Therefore, intermediate points can be further classified into intermediate points between segment points and intermediate points between end points.
The segment and end attributes are set to intercept ATM OAM cells in the expected direction and location. Figure 6-97 shows the segment and end attributes of CPs. Figure 6-97 Segment and end attributes of CPs
End points Segment Points
Segment-end Points Intermediate Points Packet Transmission Equipment
Directions of CPs
The directions of CPs are classified into forward and backward directions. Figure 6-98 shows the directions of CPs.
Issue 02 (2011-01-20)
6-211
6 Packet Features
Figure 6-98 Directions of CPs
End points Segment Points Intermediate Points Packet Transmission Equipment
Forward direction Sink Source
Backward direction ATM connection Direction
6.14.2.3 ATM OAM Functions

The equipment supports the following ATM OAM functions: alarm indication signal (AIS), remote defect indication (RDI), continuity check (CC), and loopback (LB).
AIS/RDI
AIS cells are used for reporting defect indications in the forward direction. Table 6-80 lists the types and functions of AIS cells.
6-212
Issue 02 (2011-01-20)
6 Packet Features
Table 6-80 AIS/RDI functions Cell Generation and Transmission Mechanism l Upon detecting a fault, an intermediate point reports the corresponding alarms and inserts segment AIS cells and end AIS cells to the downstream. Afterwards, the intermediate point periodically sends these cells. An intermediate point does not catch any AIS/RDI cells. l Upon detecting a fault, a segment point reports the corresponding alarms and inserts segment AIS cells and end AIS cells to the downstream. Afterwards, the segment point periodically sends these cells. A segment point catches segment AIS/RDI cells only. l Upon detecting a fault, an end point reports the corresponding alarms but does not insert any AIS cells. An end point catches end AIS/RDI cells only. l Upon detecting a fault, a segment-end point reports the corresponding alarms but does not insert any AIS cells. A segment-end point catches the AIS/RDI cells of a segment and an end. AIS State Release Condition l The AIS state is released when a user cell or CC cell is received. l If the CC function is not activated, the AIS state is also released when AIS cells are absent for 2.5 seconds, with a margin of 0.5 seconds. RDI State Release Condition The RDI state is released when RDI cells are absent for 2.5 seconds, with a margin of 0.5 seconds.
CC
CC is used for continuously monitoring link continuity. With the CC function, unexpected interruption of a link (the link is intermittently disconnected) during a continuous period can be detected. Table 6-81 lists the types and functions of CC cells.
Issue 02 (2011-01-20)
6-213
6 Packet Features
Table 6-81 CC functions Insertion Mode of CC Cells Two alternative modes are available for the insertion of the CC cells after the activation of the CC function: l CC cells are inserted with a periodicity of nominally one cell per second when no user cells have been sent on the link. l CC cells are sent repetitively with a periodicity of nominally one cell per second independent of the user cells flow. Segment and End Attribute of CC Segment points or end points support activation of the CC function. l seg_CC is responsible for transmitting or receiving segment CC cells. l ete_CC is responsible for transmitting or receiving end-to-end CC cells. Source and Sink of CC l The source point with CC activated only transmits CC cells. l The sink point with CC activated only receives CC cells. l The source point+sink point with CC activated transmit and receive CC cells. Description of CC l When the specified receive point does not receive any service cell or CC cell within a time interval of 3.5 seconds, with a margin of 0.5 seconds, it reports the LOC alarm and transmits AIS cells in the forward direction. l When the specified receive point receives CC cells or service cells again, the LOC alarm is released.
LB
LB is used for detecting link continuity and locating faults. LB cells can be inserted at one location on which the segment and end attribute is set along a virtual connection and looped back at different downstream locations on which the segment and end attributes are set, eliminating the need to interrupt services. Table 6-82 LB functions Loopback Location Identifier (LLID) Loopback Indication (LI) LI is used to identify the loopback status of LB cells. l LI = 1: indicates that LB cells are not looped back. l LI = 0: indicates that LB cells are looped back. Segment and End Attribute of LB seg_LB cells can be looped back at segment points, segment-end points or intermediate points. e-t-e_LB cells can be looped back at segment-end points or end points. Test Result
The LLID field is used to identify the location where the loopback is to occur.
NOTE Actually, the LLID field can be set to any value. The LLID field is designed according to the second coding mode (0x01) specified in ITU-T I.610. For this reason, you can enter 15 bytes, which consist of 2-byte country code (the default value is 0000 in the hexadecimal system), 2-byte network code (the default value is 0000 in the BCD code pattern), and 11-byte NE code (by default, the first four bytes use the NE ID and the last seven bytes are 0s). In addition, once the LLID field is set, the LLID field does not vary with the NE ID even if the NE ID changes. The last byte of the LLID field is unused.
Success/Failure
NOTE If the test fails, the error code and failure cause are displayed; if the test is successful, the message indicating a successful test is displayed. The LB test result can be found in the network management events.
6-214
Issue 02 (2011-01-20)
6 Packet Features
In F4 flows, the VCI value of a segment OAM cell is 3 (VCI = 3) and the VCI value of an endto-end OAM cell is 4 (VCI = 4). In F5 flows, the payload type identifier (PTI) value of a segment OAM cell is 4 (PTI = 4), and the PTI value of an end-to-end OAM cell is 5 (PTI = 5).
This section describes the specifications for ATM OAM. Table 6-83 lists the specifications for ATM OAM. Table 6-83 Specifications for ATM OAM Item Maximum number of ATM connections supported by ATM OAM Direction of ATM OAM Specifications 256
Forward direction Reverse direction
Segment and end attributes of ATM OAM
Intermediate point Segment point End point Segment and end point
AIS RDI CC LB
Supported Supported Supported Supported

This section describes the standards and protocols associated with ATM OAM. The following standard is associated with ATM OAM: ITU-T I.610: B-ISDN operation and maintenance principles and functions
6.14.5 Availability
This section describes the support required by the application of the ATM OAM feature and its dependencies.
Issue 02 (2011-01-20)
6-215
6 Packet Features

Table 6-84 Hardware and version support Feature ATM OAM Applicable Board CSHN ML1 MD1 Applicable Hardware Version All the versions All the versions All the versions Applicable Product Version V100R003C00 and later V100R003C00 and later V100R003C00 and later
The dependencies between the ATM OAM feature and other features are as follows: l l ATM OAM is used to detect and locate a fault in the ATM service, and monitor the performance of the ATM service. ATM OAM can be used for common ATM connections corresponding to UNI-UNI services, or for ATM PWE3 connections corresponding to UNI-NNI services.
6.14.6 Principles
The functions of ATM OAM are implemented by means of specific ATM OAM cells. 6.14.6.1 AIS/RDI This section provides an example wherein an intermediate point detects a VPC/VCC fault to describe how the AIS/RDI functions are implemented. 6.14.6.2 CC This section provides an example to describe the CC function at the segment and end-to-end levels. 6.14.6.3 LB This section provides an example wherein the LB function is enabled on segment points to describe how the LB function is implemented.
6.14.6.1 AIS/RDI
This section provides an example wherein an intermediate point detects a VPC/VCC fault to describe how the AIS/RDI functions are implemented. As shown in Figure 6-99, on the ATM network, the end-to-end points are set up in the backward direction of NE1 and in the forward direction of NE5, the segment points are set up in the backward direction of NE2 and in the forward direction of NE4, and NE3 is the intermediate point. The VPC from NE2 to NE3 breaks due to a fault. In this case, the AIS/RDI function is implemented as follows:
6 Packet Features
NE3 immediately reports the LCD alarm. Since NE3 is an intermediate point, it immediately inserts seg_VP-AIS and e-t-e_VP-AIS cells in the forward direction. Then, it continues to periodically transmit these cells. After the forward segment point of NE4 captures seg_VP-AIS cells, NE4 immediately reports the VP-AIS status. Meanwhile, the forward segment point of NE4 immediately transmits seg_VP-RDI cells to the upstream.
NOTE
The forward segment points of NE4 do not capture e-t-e_VP-AIS cells.
After the forward segment point of NE5 captures e-t-e_VP-AIS cells, NE5 immediately reports the VP-AIS status. Meanwhile, the forward segment point of NE5 immediately transmits e-t-e_VP-RDI cells to the upstream. Since NE3 is an intermediate point, it does not capture any RDI cell. After the backward segment point of NE2 captures seg_VP-RDI cells from NE4, NE2 immediately reports the VP-RDI status.
NOTE
l l
The backward segment point of NE2 does not capture e-t-e_VP-RDI cells.
After the backward end-to-end point of NE1 captures e-t-e_VP-RDI cells from NE5, NE1 immediately reports the RDI status.
Figure 6-99 Principles of AIS/RDI

Reporting the AIS status Reporting the AIS status NE1 end-to-end point Reporting the LCD alarm seg_VP-AIS cell NE3 intermediate point e-t-e_VP-AIS cell NE5 end-to-end point
NE2 segment point seg_VP-RDI cell e-t-e_VP-RDI cell Reporting the RDI status Reporting the RDI status VPC VPC direction
NE4 segment point
Issue 02 (2011-01-20)
6-217
6 Packet Features
NOTE
If the ATM trunks at both ends of NE2 and NE3 are enabled with the IMA protocol, a unidirectional VPC interruption from NE2 to NE3 will result in a bidirectional VPC interruption between NE2 and NE3 because the OptiX RTN 980 supports only Symmetrical Mode and Symmetrical Operation. In this case, NE1 and NE2 as shown in Figure 6-99 cannot capture any RDI cells, and will not report any RDI status.
6.14.6.2 CC
This section provides an example to describe the CC function at the segment and end-to-end levels. As shown in Figure 6-100, on the ATM network, the ATM link is enabled with the CC function at the segment and end-to-end levels. Wherein, NE1 initiates an end-to-end CC test to NE5, and NE2 initiates a segment CC test to NE4. CC cells are then continuously transmitted between end-to-end points, and between segment points. The VPC between NE3 and NE4 breaks due to a fault. In this case, the CC function is implemented as follows: l l NE4 fails to receive user cells or seg_CC cells, so NE4 immediately reports the VP_LOC alarm and transmits VP_AIS cells to the downstream. NE5 receives only VP_AIS cells, but fails to receive e-t-e_CC cells or user cells. Therefore, NE5 immediately reports the VP_AIS status.
Figure 6-100 Principles of CC

Reporting the AIS status Reporting the VP_LOC alarm NE1 end point NE5 end point
NE3 intermediate point
NE2 segment point
NE4 segment point
Sending the seg_CC cell Sending the e-t-e_CC cell CC
Receiving the seg_CC cell Receiving the e-t-e_CC cell
6-218
Issue 02 (2011-01-20)
6 Packet Features
6.14.6.3 LB
This section provides an example wherein the LB function is enabled on segment points to describe how the LB function is implemented. As shown in Figure 6-101, segment points are set up in the backward direction of NE2 and in the forward direction of NE4, and NE3 is the intermediate point. 1. When the backward segment point of NE2 initiates an LB test to NE3, it inserts a seg_LB cell whose LLID value is the same as that of NE3; after the backward segment point of NE2 initiates an LB test to NE4, it inserts a seg_LB cell whose LLID value is the same as that of NE4. Before a cell is looped back, its LI value is equal to 1. When the intermediate point (NE3) receives a seg_LB cell, it first analyzes whether the LLID value of the cell is the same as the local LLID value. l If the LLID values are different, the cell is transmitted to the downstream without being processed. l If the LLID values are the same, NE3 analyzes whether the LI value of the cell is equal to 1. If the LI value of the cell is equal to 1, the cell is not looped back yet. NE3 then sets the LI value to 0 and returns the cell, so that the backward segment point of NE2 can receive the returned cell within 6 (+/-1) seconds. If the LI value of the cell is equal to 0, the cell is transmitted to the downstream without being processed. 3. When the forward segment point of NE4 receives a seg_LB cell, it first analyzes whether the LLID value of the cell is the same as the local LLID value. l If the LLID values are different, the cell is discarded. l If the LLID values are the same, the forward segment point of NE4 analyzes whether the LI value of the cell is equal to 1. If the LI value of the cell is equal to 1, the cell is not looped back yet. The forward segment point of NE4 then sets the LI value to 0 and returns the cell, so that the backward segment point of NE2 can receive the returned cell within 6 (+/-1) seconds. If the LI value of the cell is equal to 0, the cell is discarded. 4. If an LB cell fails to be looped back to the backward segment of NE2 within 6 (+/-1) seconds seconds, the failure of the LB test is reported.
2.
Issue 02 (2011-01-20)
6-219
6 Packet Features
Figure 6-101 Principles of LB

NE1 end-to-end point NE5 end-to-end point
LLID="NE4", LI="1"
LLID="NE3", LI="1" NE3 intermediate point NE2 segment point LLID="NE3", LI="0" NE4 segment point
LLID="NE4", LI="0"
Inserting the LB cell Extracting and analyzing the LB cell LB cell (before loopback) LB cell (after loopback) Packet transmission equipment

The ATM OAM configurations of an F4 flow are the same as those of an F5 flow.
6-220
Issue 02 (2011-01-20)
6 Packet Features

Start
Query and set a mark for a loopback point
Set segment and end attributes
Conduct a CC
Conduct an LB test
End Required Optional
NOTE
When the segment and end attributes of connection points are set, the AIS/RDI OAM is automatically enabled.
Setting Segment and End Attributes of CPs

Operation A.7.10.1 Setting Segment and End Attributes of AIS/RDI Description Required. Set the parameters as follows: Set Segment and End Attribute of each connection direction according to planning information.
Flow for configuring a CC

Operation A.7.10.2 Performing a Continuity Check Test Description Required. A CC is used to test link connectivity, but not to locate a fault. Set the parameters as follows: l Segment and End Attribute. Specify the links for the CC. l CC Activate Flag
Issue 02 (2011-01-20)
6-221
6 Packet Features
Flow for configuring an LB test

Operation A.7.10.3 Querying or Setting LLIDs Description Required by an NE responding to an LB packet. Set the LLID of an NE to the default value if it is unique on the network. Otherwise, reset the LLID as required. A.7.10.4 Performing an LB Test Required by an NE transmits an LB packet. Set the parameters as follows: l Segment and End Attribute l NE on which a loopback is performed l Test result It should be Success.

This section uses an example to describe how to plan and configure ATM OAM according to network conditions. 6.14.8.1 Network Diagram This section describes the networking information about NEs. 6.14.8.2 Service Planning The service planning information contains all the parameters required for configuring the NE data. 6.14.8.3 Configuration Process This section describes the process of data configuration.

This section describes the networking information about NEs. As shown in Figure 6-103, one ATM service is present between the NodeB and the RNC. The details are provided as follows. l l l The 4-ML1-1(TRUNK1) port on NE1 (NE ID: 120-1) receives an ATM service from the NodeB. VPI = 1, and VCI = 15. The 4-ML1-1(TRUNK1) port on NE2 (NE ID: 120-2) receives the ATM service from the RNC. VPI = 1, and VCI = 15. The PW between NE1 and NE2 transmits the ATM service. PW ID = 101.
To test service connectivity between NE1 and NE2, perform an LB test on NE1.
6-222
Issue 02 (2011-01-20)
6 Packet Features

UNI VPI 1 IMA VCI 15 PSN PW ID=101 NodeB UNI VPI 1 VCI 15 IMA RNC
NE1
NE2

The service planning information contains all the parameters required for configuring the NE data. For ATM services, set the segment and end attributes for each connection point and the LLID of the NE that responds to LB cells, and start an LB test at the end that sends LB cells. This section provides only the planning information about the segment and end attributes. Set the LLID of an NE to the default value if it is unique on the network.
Planning information about segment and end attributes

Parameter Value NE1 Segment and End Attribute Segment point NE2 Segment point

Procedure
Step 1 See A.7.10.1 Setting Segment and End Attributes of AIS/RDI, and configure the segment and end attributes of connection points. Parameter Value NE1 Segment and End Attribute Segment point NE2 Segment point
Step 2 See A.7.10.3 Querying or Setting LLIDs, and set the mark (LLID) for the specific loopback point. The LLID of NE2 is 00 09 78 02 00 00 00 00 00 00 00.
6 Packet Features
Step 3 Start an A.7.10.4 Performing an LB Test on NE1. Parameter Value NE1 Segment and End Attribute Loopback point NE Segment point NE(120-2)
Normally, the test result is Success. ----End

Related Tasks
A.7.10.1 Setting Segment and End Attributes of AIS/RDI A.7.10.2 Performing a Continuity Check Test A.7.10.3 Querying or Setting LLIDs A.7.10.4 Performing an LB Test

When ATM OAM detects a fault, an NE reports the specific alarm.
Relevant Alarms
l VP_AIS The VP_AIS alarm indicates the VPC is abnormal. If the VPC that is configured with the segment and end attributes receives AIS cells, this alarm is reported to indicate that the upstream service is abnormal. l VP_RDI The VP_RDI alarm indicates a remote defect in the VPC. If the VPC that is configured with the segment and end attributes receives RDI cells, this alarm is reported to indicate that the downstream service is abnormal. l VP_LOC The VP_LOC alarm indicates that a VP continuity check packet is lost. This alarm is reported when a CC cell or user cell is not received within a time interval of 3.5 seconds, with a margin of 0.5 seconds. l VC_AIS The VC_AIS alarm indicates the VCC is abnormal. If the VCC that is configured with the segment and end attributes receives AIS cells, this alarm is reported to indicate that the upstream service is abnormal. l
6-224
VC_RDI
6 Packet Features
The VC_RDI alarm indicates a remote defect in the VCC. If the VCC that is configured with the segment and end attributes receives RDI cells, this alarm is reported to indicate that the downstream service is abnormal. l VC_LOC The VC_LOC alarm indicates that a VC continuity check packet is lost. This alarm is reported when a CC cell or user cell is not received within a time interval of 3.5 seconds, with a margin of 0.5 seconds.

None.
6.14.11 FAQs
This section provides answers to the questions that are frequently raised when ATM OAM is used. None.
6.15 ATM Traffic Management

This chapter describes the ATM traffic management feature. 6.15.1 Introduction This section provides the definition of ATM traffic management and describes its purpose. 6.15.2 Basic Concepts This section describes the basic concepts associated with ATM traffic management. 6.15.3 Specifications +This section describes the specifications for ATM traffic management. 6.15.4 Reference Standards and Protocols This section describes the standards and protocols associated with ATM traffic management. 6.15.5 Availability This section describes the support required by the application of the ATM traffic management feature and its dependencies. 6.15.6 Principles ATM traffic management is achieved by using the generic cell rate algorithm (GCRA). 6.15.7 Configuration Procedure ATM traffic management is configured based on ATM connections. 6.15.8 Configuration Example This section uses an example to describe how to plan and configure ATM traffic management according to network conditions. 6.15.9 Task Collection This section provides the hyperlinks of the operation tasks associated with the feature. 6.15.10 Relevant Alarms and Events There is no alarm or event associated with the ATM traffic management feature. 6.15.11 FAQs
6 Packet Features
This section provides answers to the questions that are frequently raised when ATM traffic management is used.
6.15.1 Introduction
This section provides the definition of ATM traffic management and describes its purpose.
Definition
ATM traffic management is a mechanism provided by the ATM network. With the mechanism, an ATM network assures services of expected QoS objectives such as amount of bandwidth, delay, delay variation, and packet loss ratio in whatever situations, so that users can know the expected service level. The equipment can provide ATM services with ensured quality levels by applying ATM traffic control policies.
Purpose
ATM traffic management aims to prevent occurrence of congestion in ATM services and improve utilization of resources. If ATM services are transmitted in PWE3 mode, service policies with appropriate priorities can be provided for various categories of ATM services carried by VPCs or VCCs before the ATM cells are encapsulated into PW packets. As shown in Figure 6-104, ATM traffic management generally functions in the ingress direction of a UNI on a PE. Figure 6-104 Functioning point of ATM traffic management
Functioning point of ATM traffic control
ATM cells
Ingress PSN
CE
PE

This section describes the basic concepts associated with ATM traffic management. 6.15.2.1 ATM Traffic Parameters ATM traffic parameters are grouped into an ATM QoS descriptor. 6.15.2.2 ATM Service Categories ATM Forum defines five service categories, each of which has different conformance definitions regarding traffic parameters.
6 Packet Features
6.15.2.3 ATM Traffic Categories Directly apply an appropriate ATM traffic category descriptor to provide traffic management for a specific ATM service category. 6.15.2.4 ATM Traffic Control Schemes The equipment supports the following ATM traffic control schemes: connection admission control (CAC), usage parameter control (UPC)/network parameter control (NPC), and early packet discard (EPD)/partial packet discard (PDD).
6.15.2.1 ATM Traffic Parameters

ATM traffic parameters are grouped into an ATM QoS descriptor. ATM traffic parameters include peak cell rate (PCR), sustained cell rate (SCR), cell delay variation tolerance (CDVT), and maximum burst size (MBS). For information about each traffic parameter, see Table 6-85. Table 6-85 ATM traffic parameters ATM Traffic Parameter PCR Full Name Description
Peak cell rate
The PCR traffic parameter specifies an upper bound on the rate at which traffic can be transmitted to a network. An increased PCR allows a higher cell burst rate for a connection but also results in utilization of more resources. It is recommended that you set the value of the PCR twice that of the SCR.
SCR
Sustained cell rate
The SCR traffic parameter specifies an upper bound on the sustained average rate at which traffic can be transmitted to a network. An increased SCR directly increases the connection rate but also results in utilization of more resources. It is recommended that you set the SCR to the required amount of bandwidth.
CDVT
Cell delay variation tolerance
When cells from two or more connections are multiplexed, transmission of cells in a given connection may be delayed as cells of another connection are being inserted at the output of the multiplexer. Similarly, transmission of some cells may be delayed as physical layer overhead or OAM cells are inserted. Consequently, from the perspective of a receive site, the inter-arrival time between consecutive cells varies in different periods of time. The CDVT parameter specifies an upper limit on the variation tolerance. An increased CDVT enhances the ability of a system to protect against cell delay variation and allows a larger link differential delay for cells. When the PCR and SCR are correctly set, you can increase the CDVT if some cells are still discarded.
Issue 02 (2011-01-20)
6-227
6 Packet Features
ATM Traffic Parameter MBS
Full Name
Description
Maximum burst size
The MBS traffic parameter specifies an upper bound on the number of burst cells that are transmitted at an allowed rate. An increased MBS helps a system be more tolerant of bursts on a particular connection; that is, a connection is allowed to transmit more burst cells. Increase the MBS if traffic burst is likely to occur within a certain period of time.
MCR
Minimum Cell Rate
The MCR traffic parameter specifies the minimum cell rate. The rate at which traffic can be transmitted to a network cannot be less than this value.
6.15.2.2 ATM Service Categories

ATM Forum defines five service categories, each of which has different conformance definitions regarding traffic parameters. ATM Forum defines five service categories, namely, CBR, UBR, UBR+, rt-VBR, and nrt-VBR, as provided in Table 6-86. If the equipment needs to control traffic, set traffic parameters for each service category on the equipment. Table 6-86 ATM service categories and ATM traffic parameters ATM Service Catego ry CBR Full Name Applicat ion Example Voice, CBR video, and circuit emulation ATM Traffic Paramete r PCR and CDVT Description
Constant bit rate
The CBR service requires tightly constrained delay variation and requires that data be transmitted at a constant rate. In addition, the CBR service requests a static amount of bandwidth and the highest priority. The CBR service is characterized by stable traffic and few bursts.
6-228
Issue 02 (2011-01-20)
6 Packet Features
ATM Service Catego ry UBR
Full Name
Applicat ion Example LAN emulation , IP over ATM, and unspecifie d traffic (such as file transfer and email) LAN emulation , IP over ATM, and unspecifie d traffic (such as file transfer and email) Voice and VBR video
ATM Traffic Paramete r PCR and CDVT
Description
Unspecifi ed bit rate
The UBR service is intended for non-realtime applications that allow many bursts. The UBR service does not specify traffic related service guarantees. Instead, the UBR service only requires that the network side provide the service with the best effort (BE) guarantee, and the network side does not provide any guarantee for the UBR service. In the case of network congestion, the UBR cells are discarded first. The UBR+ service is supplementary to the UBR service and is intended for applications that require an ensured minimum cell rate, which is indicated by the minimum cell rate (MCR) parameter. The other characteristics of the UBR+ service are the same as the corresponding characteristics of the UBR service.
UBR+
Unspecifi ed bit rate plus
PCR, CDVT, and MCR
rt-VBR
Real-time variable bit rate
PCR, SCR, CDVT, and MBS
The rt-VBR service requires tightly constrained delay and delay variation. Compared with the CBR service, the rtVBR service allows sources to transmit data at a rate that varies with time. Equivalently, the sources can be described as bursty. In addition, the rtVBR service does not require a static amount of bandwidth. Compared with the rt-VBR service, the nrt-VBR service does not require tightly constrained delay or delay variation, and is intended for non-real-time applications. The nrt-VBR service has a lower priority than the rt-VBR service but still has variable bit rate and bursty traffic characteristics.
nrt-VBR
Non-realtime variable bit rate
Packet transmissi on, terminal meeting, and file transfer
PCR, SCR, and MBS
6.15.2.3 ATM Traffic Categories

Directly apply an appropriate ATM traffic category descriptor to provide traffic management for a specific ATM service category.
Issue 02 (2011-01-20)
6-229
6 Packet Features
Table 6-87 provides the mapping relationships between ATM service categories, ATM traffic category descriptors, and traffic parameters. The mapping relationships provide a basis for ATM policy configuration. Table 6-87 Mapping relationships between ATM service categories, ATM traffic category descriptors, and traffic parameters ATM Service Category UBR ATM Traffic Category Descriptor NoTrafficDescriptor NoClpTaggingNoScr NoClpNoScr NoClpNoScrCdvt CBR ClpTransparentNoScr ClpNoTaggingNoScr ClpTaggingNoScr NoClpNoScr NoClpNoScrCdvt nrtVBR NoClpScr ClpNoTaggingScr ClpTaggingScr rtVBR ClpTransparentScr NoClpScrCdvt ClpNoTaggingScrCdvt ClpTaggingScrCdvt UBR+ atmnotrafficdescriptormcr atmnoclpmcr atmnoclpmcrcdvt Traffic Parameter 1 Clp01Pcr Clp01Pcr Clp01Pcr Clp01Pcr Clp01Pcr Clp01Pcr Clp01Pcr Clp01Pcr Clp01Pcr Clp01Pcr Clp01Pcr Clp01Pcr Clp01Pcr Clp01Pcr Clp01Pcr Clp01Mcr Clp01Pcr Clp01Pcr Traffic Parameter 2 CDVT CDVT CDVT Clp0Pcr Clp0Pcr CDVT Clp01Scr Clp0Scr Clp0Scr Clp01Scr Clp01Scr Clp0Scr Clp0Scr Clp01Mcr Clp01Mcr Traffic Parameter 3 MBS MBS MBS MBS MBS MBS MBS CDVT Traffic Parameter 4 CDVT CDVT CDVT CDVT -
NOTE
"-" indicates that the traffic parameter is unused.
6.15.2.4 ATM Traffic Control Schemes

The equipment supports the following ATM traffic control schemes: connection admission control (CAC), usage parameter control (UPC)/network parameter control (NPC), and early packet discard (EPD)/partial packet discard (PDD).
6 Packet Features
CAC
The CAC function is used to determine whether a connection can be progressed or should be rejected. A connection request is progressed only when sufficient resources are available, in order to maintain the agreed QoS of established connections. The equipment determines whether a connection can be progressed or should be rejected according to the following principle: The SCR sum of all the connections does not exceed the maximum service access bandwidth of the equipment.
UPC/NPC
UPC/NPC is defined as the set of actions taken to monitor traffic and enforce the traffic contract. Its main purpose is to monitor the cells received on ATM virtual connections according to negotiated traffic parameters, thus to avoid possible network congestion. Connection monitoring at a UNI (private or public) is referred to as UPC. Connection monitoring at an NNI (private or public) is referred to as NPC. At the cell level, actions of the UPC function may include: l Cell passing The UPC function considers that the cell conforms to the negotiated traffic contract and therefore allows the cell to pass. l Cell tagging Cell tagging is operated for CLP = 0 cells only, by converting CLP = 0 into CLP = 1. The UPC function considers that the tagged cell conforms to the negotiated traffic contract and therefore allows the cell to pass. In the case of network congestion, however, the tagged cell is discarded. l Cell discarding The UPC function considers that the cell violates conformance to the negotiated traffic contract and therefore discards the cell.
EPD/PPD
l EPD If the EPD function is enabled, the system always monitors the status of the cell buffer. Once the network is detected congested, the system discards all the cells in the next ATM Adaptation Layer Type 5 (AAL5) packet. The EPD function is effective for congestion prevention because cell discarding is performed at the packet level. The system, however, cannot selectively discard packets because the EPD function cannot differentiate a good packet from a bad packet. l PPD The system starts to discard an ATM cell and all the following cells in the same AAL5 packet, to reduce the load on the network if all the following conditions are met: (1) The PPD function is enabled; (2) AAL5 packets are used to carry ATM cells; (3) Network congestion occurs or the transmit traffic volume exceeds the amount of allocated bandwidth. The AAL5 packet, however, may fail to be restored and results in a bad packet due to loss of an ATM cell. Therefore, the AAL5 packet needs to be retransmitted.
+This section describes the specifications for ATM traffic management.
6 Packet Features
Table 6-88 lists the specifications for ATM traffic management. Table 6-88 Specifications for ATM traffic management Item ATM traffic management policy Specifications CBR UBR UBR+ rt-VBR nrt-VBR ATM flow type Supported
NOTE For the mapping relationships between ATM service categories, ATM traffic category descriptors, and traffic parameters, see Table 6-87. The mapping relationships provide a basis for ATM policy configuration.
UPC/NPC ATM frame discarding flag Flexible mapping between ATM traffic management policies and PHB service levels
Supported Supported Supported

This section describes the standards and protocols associated with ATM traffic management. The following standards and protocols are associated with ATM traffic management: l l ATM Forum AF-TM-0121.000: Traffic Management Specification Version 4.1 IETF RFC 2514: Definitions of Textual Conventions and Object-identities for ATM Management
6.15.5 Availability
This section describes the support required by the application of the ATM traffic management feature and its dependencies.
6-232
Issue 02 (2011-01-20)
6 Packet Features

Table 6-89 Hardware and version support Feature ATM traffic management Applicable Board CSHN ML1 MD1 Applicable Hardware Version All the versions All the versions All the versions Applicable Product Version V100R003C00 and later V100R003C00 and later V100R003C00 and later
The dependencies between the ATM traffic management feature and other features are as follows: The QoS of ATM services can be guaranteed by using ATM traffic management policies.
6.15.6 Principles
ATM traffic management is achieved by using the generic cell rate algorithm (GCRA).
Basic GCRA Principles

The GCRA is used to determine whether ATM traffic conforms to the traffic contract. If the ATM network becomes congested because the received cells within a short period of time exceed the contract or the affordable capability of the receive equipment due to very heavy ATM traffic, the GCRA takes some punishment actions. Fundamentally, the GCRA complies with the following principles: The GCRA allows the actual inter-arrival time between cells to be equal to (arrival on schedule) or vary from the expected inter-arrival time. The variation can be a negative value (arrival ahead of schedule) or a positive value (delayed arrival). If a cell arrives ahead of schedule, however, the variation must not exceed the preset CDVT. Otherwise, the GCRA considers that the cell violates conformance to the contract. Figure 6-105 uses an example to describe how the equipment performs traffic management on cell 2 in four arrival scenarios based on the principles of the GCRA. Assume the following conditions: The contracted maximum traffic rate is PCR; the UPC/NPC function is enabled; variable T is equal to 1/PCR, that is, a cell is transmitted to the network at an interval not shorter than T; cell 1 arrives at time t1; cell 2 is expected to arrive at time t2 (t2 = t1 + T).
Issue 02 (2011-01-20)
6-233
6 Packet Features
Figure 6-105 Illustration of basic GCRA principles

T L 1 Cell 1 1 t1 1 t1 e 3 t1 1 2 d 2 t2 T 2 2 t2 + d Cell 2 arrives d late. Cell 3 is expected to arrive at time t2 + d + T. T Cell 2 arrives T after the arrival of cell 1 (on schedule). Cell 3 is expected to arrive at time t2 + T. T
Cell 2 arrives e early and the variation can be tolerated. t2 - e Cell 3 is expected to arrive at time t2 + T. T
4 t1
Cell 2 arrives very early and the variation exceeds the preset CDVT, and therefore the equipment discards or remarks the cell. Cell 3 is expected to arrive at time t2.
Table 6-90 describes the preceding example. Table 6-90 Description of basic GCRA principles Cell Arrival 1 Normal (arrival on schedule ) Normal (delayed arrival) Description Cell 2 arrives T after the arrival of cell 1 (on schedule). Cell 3 is expected to arrive at time t2 + T. UPC/NPC Operation Cell passing
Cell 2 is expected to arrive at time t1 + T but actually arrives at time t2 + d. The time variation is d. Cell 3 is expected to arrive at time t2 + d + T (not t1 + 2 x T). Cell 2 is expected to arrive at time t1 + T but arrives e early because the cell rate exceeds the contracted PCR. e, however, is smaller than L (representing the preset CDVT), and therefore the GCRA considers that cell 2 does not violate conformance to the contract. Note that cell 3 is expected to arrive at time t2 + T (not t2 - e + T). This prevents cells from being transmitted at a rate higher than the contracted PCR within a period of time.
Cell passing
Burst (arrival ahead of schedule )
Cell passing
6-234
Issue 02 (2011-01-20)
6 Packet Features
Cell Arrival 4 Violatio n
Description Cell 2 is transmitted at a very high rate and as a result, cell 2 arrives very early and the time variation exceeds L. Therefore, the GCRA considers that cell 2 violates conformance to the contract.
UPC/NPC Operation Cell tagging or discarding
Leaky Bucket Algorithm of the GCRA

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

Cells at each arrival uses a capacity T. Contract conformance violation cell
One unit of cells leaks per time-unit.
ATM Traffic Management by Using the Two-Level Leaky Bucket Algorithm

The equipment monitors ATM traffic by using the two-level leaky bucket algorithm, as shown in Figure 6-107. Cells leak from the level-1 bucket at the PCR and leak from the level-2 bucket
6 Packet Features
at the SCR. Regarding the level-1 bucket, T is equal to 1/PCR and L is equal to the CDVT; regarding the level-2 bucket, T is equal to 1/SCR and L is equal to (MBS - 1) x (1/SCR + 1/ PCR). Contract conformance violation cells are discarded or tagged according to UPC/NPC actions. Figure 6-107 Two-level leaky bucket algorithm
Level-1 bucket
PCR
Contract conformance violation cell
Level-2 bucket
SCR
Contract conformance violation cell

ATM traffic management is configured based on ATM connections.

Required Optional Start
Create an ATM policy
Configure an ATM service
End
6-236
Issue 02 (2011-01-20)
6 Packet Features
Configuration procedure
Operation A.7.9.3 Creating an ATM Policy Description Required if the ATM service is based on ATM connections Set the parameters according to the planning information. l Set Policy ID, or select Automatically Assign. l Select or assign a value for Policy Name. l Set Service Type according to the planning information. l Set Traffic Type and corresponding traffic parameters based on Service Type. l Set the enabled status of Discard Traffic Frame and UPC/NPC according to planning information. A.7.8.1 Creating ATM Services Required. Set the service parameters according to the planning information, and bind a corresponding ATM policy for each connection of the ATM service.

This section uses an example to describe how to plan and configure ATM traffic management according to network conditions. This example describes the configurations of ATM traffic management. For a complete configuration example, see Configuration Example (Common ATM Services) in the OptiX RTN 980Configuration Guide. 6.15.8.1 Network Diagram This section describes the networking information about NEs. 6.15.8.2 Service Planning The service planning information contains all the parameters required for configuring the NE data. 6.15.8.3 Configuration Process This section describes the process of data configuration.

This section describes the networking information about NEs. As shown in Figure 6-109, one ATM service is present between the NodeB and the RNC. The details are provided as follows.
6 Packet Features
l l l l
The 4-ML1-1(TRUNK1) port on NE1 receives an ATM service from the NodeB. The 4-ML1-1(TRUNK1) port on NE2 receives the ATM service from the RNC. The PW between NE1 and NE2 transmits the ATM service in the N-to-one encapsulation mode. Each NodeB transmits real-time voice services, signaling services (CBR services), HSDPA data services (UBR services), OM and HSDPA real-time services (rt-VBR services), and R99 non-real-time services (nrt-VBR services). To ensure the QoS of different services, the RTN equipment specifies different ATM policies for the services.

IMA PSN PW NodeB NE1 NE2 IMA RNC

Planning Information About ATM Policies

Table 6-91 ATM policy information Parameter Service Type CBR Service Policy ID Policy name Service type Traffic type Clp01Pcr(cell/ s) Clp01Scr(cell/ s) Clp0Pcr(cell/s) Clp0Scr(cell/s)
6-238
rt-VBR Service 2 1e1_rtvbr RT-VBR ClpTransparentScr 1859 1685 -
nrt-VBR Service 3 1e1_nrtvbr NRT-VBR NoClpScr 1859 1685 -
UBR Service 4 1e1_ubr UBR NoClpNoScr 1859 Issue 02 (2011-01-20)
1 1e1_cbr CBR ClpTransparent NoScr 175 -
6 Packet Features
Parameter
Service Type CBR Service rt-VBR Service 1000 10240 Disabled Disabled nrt-VBR Service 1000 Disabled Disabled UBR Service Disabled Disabled
Clp01Mcr(cell/ s) MBS (cell) CDVT (us) Discard Traffic Frame UPC/NPC
102400 Disabled Disabled

Procedure
Step 1 See A.7.9.3 Creating an ATM Policy, and create ATM policies on NE1 and NE2. Parameter NE1 and NE2 CBR Service Policy ID Policy Name Service Type Traffic Type Clp01Pcr(cell/ s) Clp01Scr(cell/ s) Max. Cell Burst Size (cell) Cell Delay Variation Tolerance (0.1us) Discard Traffic Frame
Issue 02 (2011-01-20)
rt-VBR Service 2 1e1_rtvbr RT-VBR ClpTransparentScr 1859 1685 1000 10240
nrt-VBR Service 3 1e1_nrtvbr NRT-VBR NoClpScr 1859 1685 1000 -
UBR Service 4 1e1_ubr UBR NoClpNoScr 1859 -
1 1e1_cbr CBR ClpTransparent NoScr 175 102400
Disabled
Disabled
Disabled
Disabled
6-239
6 Packet Features
Parameter
NE1 and NE2 CBR Service rt-VBR Service Disabled nrt-VBR Service Disabled UBR Service Disabled
UPC/NPC
Disabled
Step 2 A.7.8.1 Creating ATM Services Bind a corresponding ATM policy to each connection of an ATM service. l Specify upstream and downstream ATM policy 1 for the ATM connections of real-time voice services and signaling (CBR services). l Specify upstream and downstream ATM policy 2 for the ATM connections of OM services and HSDPA real-time services. l Specify upstream and downstream ATM policy 3 for the ATM connections of R99 non-realtime services (nrt-VBR services). l Specify upstream and downstream ATM policy 4 for the ATM connections of HSDPA data services (UBR services). ----End

Related Tasks
A.7.9.1 Creating an ATM-DiffServ Domain A.7.9.2 Modifying an ATM-Diffserv Domain A.7.9.3 Creating an ATM Policy A.7.9.4 Modifying an ATM Policy

There is no alarm or event associated with the ATM traffic management feature.
Relevant Alarms
None.

None.
6.15.11 FAQs
This section provides answers to the questions that are frequently raised when ATM traffic management is used. Question: What are the differences between the GCRA algorithm used in ATM traffic management and the dual token bucket three color marker algorithm used in QoS?
6 Packet Features
Answer: Definition GCRA GCRA determines whether the ATM traffic conforms to the contract. If the ATM traffic from the UNI side is too heavy, the number of received cells violates the contract or the equipment cannot receive so many cells. As a result, the network is congested. In this case, GCRA takes some penalties. Similarity l Traffic classification is the prerequisite to the two algorithms. l The two algorithms are a traffic policy for limiting the rate of a certain flow. When the traffic exceeds the specified rate, the services are reduced in priority or discarded. l The two algorithms are implemented at ingress ports. Difference l The traffic classification of GCRA is based on the ATM service categories, namely, CBR, UBR, UBR+, rt-VBR, and nrtVBR. l The traffic control of GCRA is based on the ATM services configured with different ATM traffic parameters. l The traffic control scheme of GCRA is UPC/NPC. l GCRA controls ATM service flows at ingress ports.
Issue 02 (2011-01-20)
6-241
6 Packet Features
Definition Dual token bucket three color marker algorithm The dual token bucket three color marker algorithm is a type of traffic policing technology. When the dual token bucket three color marker algorithm is used, the rate of the traffic after traffic classification is assessed in a certain period; the packet rate of which does not exceed the specified value is set to a high priority (marked green) and the packet rate of which exceeds the specified value is discarded (marked red) or downgraded (marked yellow). In this manner, the traffic that enters the transmission network is restricted.
Similarity
Difference l The dual token bucket three color marker algorithm is used for Ethernet service flows after complex traffic classification. l The traffic control of the dual token bucket three color marker algorithm is based on PCR, PBS, CIR, and CBS. l The traffic control schemes of the dual token bucket three color marker algorithm are based on the discarding policies for green, red, and yellow packets. l The dual token bucket three color marker algorithm controls Ethernet service flows at ingress ports.
6-242
Issue 02 (2011-01-20)
7 Clock Features
7
About This Chapter
7.2 CES ACR This chapter describes the CES ACR feature.
Clock Features
This chapter describes the basics of clock synchronization, and Huawei's clock synchronization solutions and relevant clock features. 7.1 Synchronous Ethernet The synchronous Ethernet technology realizes the transfer of the clock signal through the Ethernet interface so that the clock frequencies of the equipment are synchronous.
Issue 02 (2011-01-20)
7-1
7 Clock Features
7.1 Synchronous Ethernet

The synchronous Ethernet technology realizes the transfer of the clock signal through the Ethernet interface so that the clock frequencies of the equipment are synchronous. 7.1.1 Introduction This section describes the definition of synchronous Ethernet and describes its purpose. 7.1.2 Specifications This section describes the specifications of synchronous Ethernet. 7.1.3 Reference Standards and Protocols This section describes the standards and protocols associated with synchronous Ethernet. 7.1.4 Availability This section describes the support required by the application of the synchronous Ethernet feature and its dependency. 7.1.5 Principles The realization of the synchronous Ethernet feature complies with ITU-T G.8261 and ITU-T G. 8262. 7.1.6 Planning Guidelines Follow certain rules when you plan synchronous Ethernet. 7.1.7 Configuration Procedure By default, NEs consider that all Ethernet links provide clock signals. Thus, you need only to configure the synchronous Ethernet clock source and related protection information for the NEs that require synchronous Ethernet. 7.1.8 Configuration Example This section uses an example to describe how to plan and configure synchronous Ethernet according to network conditions. 7.1.9 Task Collection This topic provides the hyperlinks of the operation tasks regarding the synchronous Ethernet feature. 7.1.10 Relevant Alarms and Events When the Ethernet link provides the clock source and an anomaly occurs, the NE reports the corresponding alarm. 7.1.11 FAQs This topic provides the answers to the questions that are frequently asked when the synchronous Ethernet is used.
7.1.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.
7 Clock Features
Synchronous Ethernet is essentially a physical-layer clock synchronization solution that transmits physical signals of clock reference through Ethernet links.
Purpose
The synchronous Ethernet technology is used to transfer clock signals through Ethernet links. As shown in Figure 7-1, the OptiX RTN 980s form a synchronous Ethernet. The synchronous Ethernet transfers the clock information between the RNC equipment and the NodeB. Figure 7-1 Application of the Synchronous Ethernet
FE NodeB
NE2
NE1 FE/GE
FE
RNC
NodeB
Ethernet clock signal Ethernet link
This section describes the specifications of synchronous Ethernet. Table 7-1 lists the specifications of synchronous Ethernet. Table 7-1 Specifications of synchronous Ethernet Item Port receiving or transmitting synchronous Ethernet clock signals Specification Supported by FE/GE ports
NOTE l Unsupported by SFP electrical modules. l When the FE/GE port works in 10BASE-T mode, it does not support the synchronous Ethernet clock.
Input/Output of SSM packets Clock frequency stability (locked mode)
Supported Less than 50 ppb

This section describes the standards and protocols associated with synchronous Ethernet.
7 Clock Features
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
7.1.4 Availability
This section describes the support required by the application of the synchronous Ethernet feature and its dependency.

Table 7-2 Hardware and version support Feature Synchronous Ethernet Applicable Board CSHN EM6T EM6F Applicable Hardware Version All the versions All the versions All the versions Applicable Product Version V100R003C00 and later V100R003C00 and later V100R003C00 and later
Feature Dependency
The synchronous Ethernet feature does not affect the other features.
7.1.5 Principles
The realization of the synchronous Ethernet feature complies with ITU-T G.8261 and ITU-T G. 8262. As shown in Figure 7-2, the synchronous Ethernet function of the OptiX RTN 980 is realized 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 checks the quality of the clocks reported by the interfaces. Then, the system clock module selects the most accurate clock and synchronizes it to be the system clock. To choose a clock source correctly, the NE constructs a specified SSM packet to inform the downstream equipment of the clock quality when sending the clock information to the downstream equipment.
NOTE
2.
For details of SSM protection, see Clock Protection Schemes.
When the Ethernet interface is the clock source of the local NE that outputs clock signals to the downstream equipment:
7 Clock Features
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 7-2 Realization principle of the synchronous Ethernet

Clock recovery Uplink of the line clock
Frequency division
System clock module
PHY
MAC
System clock PLL Ethernet interface module Uplink direction Downlink 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).

By default, NEs consider that all Ethernet links provide clock signals. Thus, you need only to configure the synchronous Ethernet clock source and related protection information for the NEs that require synchronous Ethernet. Table 7-3 Flow for configuring clocks Step 1 Operation A.8.1.1 Configuring the Clock Sources Description 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.
Issue 02 (2011-01-20)
7-5
7 Clock Features
Step 2
Operation Configuri ng the SSM or extended SSM protection A.8.1.2 Configuri ng Clock Subnets
Description Required when the SSM or extended SSM protection is used. Set the parameters as follows: l Set Protection Status according to the used protocol type. l If the clock uses the extended SSM protection, set Clock Source ID for the following clock sources: External clock source Internal clock source of the NE that accesses the external clock source Internal clock source of the NE that connects the intersecting ring and chain or connects the intersecting rings Line clock source that is accessed to the ring through the NE that connects the intersecting ring and chain or connects the intersecting rings and is configured with the line clock source on the ring The values of Clock Source ID for these clock sources should be different. A.8.1.4 Configuri ng the SSM Output Status A.8.1.5 Configuri ng the Clock ID Output Status A.8.1.3 SelfDefined Clock Quality Required when the SSM or extended SSM protection. When a line port is connected to the NE on the same clock subnet, set Control Status to Enabled. In other cases, set Control Status to Disabled. Required when the SSM or extended SSM protection is used. When a line port is connected to the NE on the same clock subnet, set Enabled Status to Enabled. In other cases, set Enabled Status to Disabled. Optional.

This section uses an example to describe how to plan and configure synchronous Ethernet according to network conditions. For the configuration example of synchronous Ethernet, see Configuration Example (Clocks for a PSN) in the Configuration Guide.
7 Clock Features

This topic provides the hyperlinks of the operation tasks regarding the synchronous Ethernet feature.
Related Tasks
A.8.1.1 Configuring the Clock Sources A.8.1.2 Configuring Clock Subnets A.8.1.3 Self-Defined Clock Quality A.8.1.4 Configuring the SSM Output Status A.8.1.5 Configuring the Clock ID Output Status A.8.1.9 Querying the Clock Synchronization Status

When the Ethernet link provides the clock source and an anomaly occurs, the NE reports the corresponding alarm.
Relevant Alarms
l l SYNC_C_LOS The SYNC_C_LOS alarm indicates that the class of the synchronization source is lost. S1_SYN_CHANGE The S1_SYN_CHANGE is an alarm indicating that the clock source is switched in S1 byte mode. l LTI The LTI alarm indicates that the synchronization source is lost. When all the synchronization sources of an NE (including the Ethernet clock source) are lost, the NE reports this alarm.
Relevant Events
None.
7.1.11 FAQs
This topic provides the answers to the questions that are frequently asked when the synchronous Ethernet is used. Q: Does the synchronous Ethernet support the transmission of clock quality information? A: Yes. To select the proper clock source, the NE constructs a specified SSM packet to inform the downstream equipment of the clock quality when sending the clock information to the downstream equipment.
7.2 CES ACR

This chapter describes the CES ACR feature.
Issue 02 (2011-01-20)
7-7
7 Clock Features
7.2.1 Introduction This section provides the definition of CES ACR and describes its purpose. 7.2.2 Basic Concepts This section describes the basic concepts associated with CES ACR. 7.2.3 Specifications This section describes the specifications for CES ACR. 7.2.4 Reference Standards and Protocols This section describes the standards and protocols associated with CES ACR. 7.2.5 Availability This section describes the support required by the application of the CES ACR feature and its dependencies. 7.2.6 Principles In the enhanced timestamp solution, CES ACR uses SN carried by CES packets to recover time information. 7.2.7 Configuration Procedure Configurations of CES ACR at master equipment are different from those at slave equipment. 7.2.8 Configuration Example This section uses an example to describe how to plan and configure CES ACR according to network conditions. 7.2.9 Task Collection This section provides the hyperlinks of the operation tasks associated with the feature. 7.2.10 Relevant Alarms and Events There is no alarm or event associated with the CES ACR management feature. 7.2.11 FAQs This section provides the answers to the questions that are frequently raised when CES ACR is adopted.
7.2.1 Introduction
This section provides the definition of CES ACR and describes its purpose.
Definition
CES ACR is a function that uses the adaptive clock recovery (ACR) technology to recover clock synchronization information carried by CES packets. In the standard CES ACR solution, the source end (Master) considers the local clock as the timestamp in the Real-time Transport Protocol (RTP) packet header and encapsulates it in the CES packet; the sink end (Slave) recovers the clock according to the timestamp in the packet. In this manner, signal impairment during the transmission is prevented. The OptiX RTN 980 adopts the enhanced timestamp clock solution. That is, clocks can be recovered based on SN in CES packets rather than timestamps in RTP packet headers. See Figure 7-3.
7-8
Issue 02 (2011-01-20)
7 Clock Features
Figure 7-3 CES ACR clock solution

Slave
SN
Master
SN
E1
Processing
CES
CES
Processing
E1
Primary reference clock
PSN
E1 CES PE2 E1
BTS
PE1
BSC
SN: Sequnce Number
Purpose
In the packet domain, CES ACR is mainly used to transparently transmit E1 clocks in the PSN. For details, see 7.2.2.3 CES ACR Clock Transparent Transmission Solution.

This section describes the basic concepts associated with CES ACR. 7.2.2.1 CES ACR Clock Domain A product supports a limited number of ACR clocks, and therefore the ACR clock domain mechanism is introduced on the OptiX RTN 980. Specifically, one ACR clock domain represents an ACR clock supported by the board, and each E1 port or CES service with CES ACR enabled must belong to an ACR clock domain. 7.2.2.2 CES ACR Clock Protection On Slave of CES ACR, a CES ACR clock domain can protect CES ACR clocks based on the corresponding protection mechanism. 7.2.2.3 CES ACR Clock Transparent Transmission Solution The CES ACR clock transparent transmission solution uses sequence numbers (SNs) in CES packets to recover service clocks. With this solution, clocks are transparently transmitted on a PSN.
7.2.2.1 CES ACR Clock Domain

A product supports a limited number of ACR clocks, and therefore the ACR clock domain mechanism is introduced on the OptiX RTN 980. Specifically, one ACR clock domain represents an ACR clock supported by the board, and each E1 port or CES service with CES ACR enabled must belong to an ACR clock domain. Figure 7-4 shows the application of a CES ACR clock domain. Assuming that Slave receives eight co-sourced CES services from Master, the E1 ports corresponding to the eight CES services all belong to ACR1. ACR1 selects one service from the eight CES services (for example, CES
7 Clock Features
service 1 corresponding to port 1) based on the ACR protection algorithm, and recovers the ACR clock from the selected service. Then, the ACR clock is used for all the E1 ports that belong to ACR1. Figure 7-4 CES ACR clock domain
Slave Clock recovery ACR1
CES
CES
E1 E1
CES packet processing
7.2.2.2 CES ACR Clock Protection

On Slave of CES ACR, a CES ACR clock domain can protect CES ACR clocks based on the corresponding protection mechanism. By default, a CES ACR clock domain recovers an ACR clock from the selected CES service, and uses the recovered ACR clock as the primary clock. Then, the ACR clock is used for all the E1 ports that belong to the ACR clock domain. The E1 ports of the selected CES service must belong to the ACR clock domain. The services from the other E1 ports in the ACR clock domain are standby services for recovering ACR clocks. When the CES service where the primary clock is from becomes abnormal, the CES ACR clock domain recovers the ACR clock from a standby service. As shown in Figure 7-5, the CES ACR clock domain has eight E1 ports corresponding to CES01 to CES08 services. CES01 is the CES service where the primary clock is from. When CES01 is normal, the ACR clock domain extracts the clock from CES01, and applies the clock to the eight E1 ports. If CES01 is abnormal, the following protection mechanism is provided. l Protection mechanism used when a fault occurs in an AC link on the Master side When detecting that a fault (fault point 1) has occurred in the AC link transmitting the service CES01, Master transparently transmits CES service alarms to Slave, and shuts down CES01. After receiving the alarms, Slave selects CES02, which is with the smallest PW ID, as the service for recovering the ACR clock. CES03 to CES08 are considered as the standby services for recovering the ACR clock.
NOTE
If the CES alarm transparent transmission function is disabled, Master will shut down all the CES services. Then, Slave will detect a PW fault. As a result, ACR clock protection switching is triggered.
Protection mechanism used to resist a PW fault When detecting that a fault (fault point 2) has occurred in the PW carrying CES01, Slave selects a service that is with the smallest PW ID as the service for recovering the ACR clock. The other CES services are considered as the standby services for recovering the ACR clock.
7-10
Issue 02 (2011-01-20)
7 Clock Features
Figure 7-5 Principles of CES ACR clock protection

Clock recovery Slave ACR1
1 2 1 2
CES
E1 E1 E1
CES CES
CES packet processing
E1 E1
AC
1 8
PSN
PW
CES01 CES08 PE (Slave)
E1
E1
8 CE
CE
PE (Master)
7.2.2.3 CES ACR Clock Transparent Transmission Solution

The CES ACR clock transparent transmission solution uses sequence numbers (SNs) in CES packets to recover service clocks. With this solution, clocks are transparently transmitted on a PSN. In the packet domain, CES ACR, as a clock transparent transmission solution, is mainly used in the following scenarios: l l All the clocks on the PSN are not synchronous. All the clocks on the PSN are synchronous, but the clocks on the PSN are not synchronized with the clock of the incoming service.
Figure 7-6 is a typical application example of the CES ACR clock transparent transmission solution.
Issue 02 (2011-01-20)
7-11
7 Clock Features
Figure 7-6 Typical application example of the CES ACR clock transparent transmission solution
SN SN
E1
Processing
CES
CES
Processing
E1
Primary reference clock
PSN
E1 BTS CES PE2 (Master) E1
PE1 (Slave)
BSC
SN: Sequnce Number
In this example, the clock of the BSC needs to be transparently transmitted to the BTS along with the CES service, but the clock of PE1 is not synchronous with the clock of PE2. In this case, PE2 (Master) extracts the clock of the BSC from the E1 port, and controls the transmission interval of CES packets according to the extracted clock. PE1 (Slave) recovers the clock of the BSC according to the SN in the received CES packet, and transmits the recovered clock to the BTS through the E1 port. In this manner, the clock of the BTS is synchronized with the clock of BSC.
NOTE
l If the clock of PE1 is synchronous with the clock of PE2 but the two clocks are asynchronous with the reference clock of the BSC, the CES ACR clock transparent transmission solution can also be used to transmit the clock of the BSC. l If the clock of PE1 is synchronous with the clock of PE2 and the two clocks are also synchronous with the reference clock of the BSC, CES retiming is used to transmit the clock of the BSC.
This section describes the specifications for CES ACR. Table 7-4 lists the specifications for CES ACR. Table 7-4 Specifications for CES ACR Item CES ACR clock solution Specifications Enhanced timestamp solution (CES ACR clock based on the SN of a CES packet)
7-12
Issue 02 (2011-01-20)
7 Clock Features
Item Number of clock domains
Specifications 4 (ML1/MD1)
NOTE l Only four ACR clock domains can take effect on an NE. l One clock domain can bind E1 ports only on the local board. l On the MD1 board, the four ACR clock domains can bind the CES services of the former 16 E1 ports or those of the latter 16 E1 ports. That is, the four ACR clock domains cannot bind the CES services of the former 16 E1 ports and those of the latter 16 E1 ports at the same time.
CES ACR clock protection CES ACR clock transparent transmission CES ACR clock as an NE clock Clock performance
Supported Supported Not supported The clock recovery specifications comply with the G.823 Traffic/SYNC template.

This section describes the standards and protocols associated with CES ACR. The following standards and protocols are associated with CES ACR: l l l l ITU-T G.8261: Timing and Synchronization aspects in Packet Networks IETF RFC 4197: Requirements for Edge-to-Edge Emulation of Time Division Multiplexed (TDM) Circuits over Packet Switching Networks IETF RFC 4553: Structure-Agnostic Time Division Multiplexing (TDM) over Packet (SAToP) IETF RFC 5086: Structure-Aware Time Division Multiplexed (TDM) Circuit Emulation Service over Packet Switched Network (CESoPSN)
7.2.5 Availability
This section describes the support required by the application of the CES ACR feature and its dependencies.
Issue 02 (2011-01-20)
7-13
7 Clock Features

Table 7-5 Hardware and version support Feature CES ACR Applicable Board ML1 MD1 Applicable Hardware Version All the versions All the versions Applicable Product Version V100R003C00 and later V100R003C00 and later
The dependencies between the CES ACR feature and other features are as follows: Only CES services support CES ACR clocks.
7.2.6 Principles
In the enhanced timestamp solution, CES ACR uses SN carried by CES packets to recover time information.
Implementation on Master
Figure 7-7 shows the ACR implementation process on Master. Figure 7-7 Implementation process on Master
Master
E1 line clock
E1
CES Encapsualting Transmitting packets packets
Master extracts clock frequency information from an E1 signal, and transmit a CES packet based on the clock frequency information.
Implementation on Slave
Figure 7-8 shows the ACR implementation process on Slave.
7 Clock Features
Figure 7-8 Implementation process on Slave

Slave ACR clock Generating timestamps
Recording arrival time
Local timestamp SN
ACR clock computing module ACR clock Buffer
CES
Receiving Decapsualting E1 packets packets
E1
1. 2. 3. 4.
The clock module uses the ACR clock to count tick values at a certain frequency. The clock module records the tick value corresponding to the arrival time of each CES packet, and outputs the tick values to the ACR clock computing module. Slave decapsulates the CES services and recovers the SNs of the CES packets. Then, Slave outputs the SNs to the ACR clock computing module. The ACR clock computing module recovers the ACR clock based on the tick values, SNs, and packet loading time. The ACR clock computing principles are as follows. l Assume that the tick value increases by 1 every 10 us and that the packet loading time is 1000 us. l Assume that the tick value corresponding to the arrival time of previous packet is t1, and that the tick value corresponding to the arrival time of current packet is t2. l If the SNs of two packets are consecutive, the packet loading time is 1000 us. Then, the tick difference should be 100 when the ACR clock is synchronized with the E1 clock that is extracted on Master. l If t2 - t1 < 100, the ACR clock frequency is lower than that of the E1 clock extracted on Master. In this case, the ACR clock computing module will increase the ACR clock frequency. If t2 - t1 > 100, the ACR clock frequency is higher than that of the E1 clock extracted on Master. In this case, the ACR clock computing module will decrease the ACR clock frequency. By increasing or decreasing the ACR clock frequency, the difference of t2 minus t1 is always 100.
5.
After the CES packet on Slave is recovered to an E1 bit stream, it is written into the First In, First Out (FIFO) queue. Then, the E1 signal is read from the FIFO queue based on the ACR clock. As a result, the output E1 signal contains the ACR clock information (that is, the ACR clock is synchronized with the E1 clock of Master). In this manner, the E1 clock is transparently transmitted.

Configurations of CES ACR at master equipment are different from those at slave equipment.
7 Clock Features
Table 7-6 Flow for configuring CES ACR Step 1 Operation A.7.6.2 Modifying CES Service Parameters Description Required by a master PE. Set Ingress Clock Mode of the CES services configured with CES ACR to Adaptive Clock Mode. Required by master and slave PEs. Configure the primary clock for an ACR clock domain. Set the major parameters as follows. Set CES Service corresponding to ACR Clock Source. 3 A.8.2.2 Configuring Ports Using the Clock Domain A.5.4.2 Setting Advanced Attributes of Smart E1 Ports Required by a slave PE. Group the E1 ports with the same clock source and from the same Master into one clock domain. Required by master and slave PEs. On Master, set Clock Mode of a port inputting E1 clocks to System Clock Mode. On Slave, set Clock Mode of a port inputting E1 clocks to Slave Mode.
A.8.2.1 Configuring the Primary Clock for an ACR Clock Domain

This section uses an example to describe how to plan and configure CES ACR according to network conditions. 7.2.8.1 Network Diagram This section describes the networking information about the NEs. 7.2.8.2 Service Planning The service planning information contains all the parameters required for configuring the NE data. 7.2.8.3 Configuration Process This section describes the process of data configuration.

This section describes the networking information about the NEs. As shown in Figure 7-9, CES services need to transparently transmit clocks from the BSC to BTS1 and BTS2, but the clocks of NE1 and NE2 are not synchronous. Therefore, NE1 and NE2 need to be configured with CES ACR. As a Slave, NE1 recovers clocks based on the SN information in the CES packets that are received by port 1 on the ML1 board in slot 4, and transmits the clocks to port 2 on the ML1 board in slot 4. In this way, the clocks of BTS1 and BTS2 are synchronized with the clock of the BSC.
7-16
Issue 02 (2011-01-20)
7 Clock Features
Figure 7-9 Network diagram of CES ACR

CES service: CES_BTS1 E1 BTS1 E1 NE1 (Slave) BTS2 CES service: CES_BTS2 4-ML1-1(to BTS1) 4-ML1-2(to BTS2) NE2 (Master) 4-ML1-1(to BSC) 4-ML1-2(to BSC) CES service: CES_BSC2 CES CES service: CES_BSC1
PSN
E1 E1
BSC

Planning Information About Clock Extraction on Master

On NE2, set the timing modes of the two CES services to the adaptive clock recover mode. Table 7-7 provides the clock extraction information on Master. Table 7-7 Planning information about clock extraction on Master Parameter Ingress Clock Mode Value Adaptive Clock Mode
Planning Information About the Primary Clock for the ACR Clock Domain on Slave
Table 7-8 provides the planning information about the primary clock for ACR clock domain 1 on NE 1 (Slave). Table 7-8 Planning information about the primary clock for ACR clock domain Parameter Clock Domain Service where the primary clock resides Value CES ACR1 clock domain CES_BTS1
Planning Information About the ACR Clock Domain on Slave

Table 7-9 provides the planning information about the ACR clock domain on NE1 (Slave).
7 Clock Features
Table 7-9 Planning information about the ACR clock domain Parameter Clock Domain Board in the Clock Domain Port in the Clock Domain Value CES ACR1 clock domain 4-ML1 4-ML1-1(CES_BTS1) 4-ML1-2(CES_BTS2)

Procedure
Step 1 Configure the clock of NE2 (Master). Then, see A.7.6.2 Modifying CES Service Parameters, and reconfigure CES service parameters. On the ML1 board in slot 4 on NE2, set the timing modes of the two CES services to the adaptive clock recover mode. The values of Advanced Attributes are provided as follows. Parameter Ingress Clock Mode Value Adaptive Clock Mode
Step 2 Configure a primary clock in the CES ACR clock domain for NE1 (Slave). Then, see A.8.2.1 Configuring the Primary Clock for an ACR Clock Domain, and configure ACR clock sources. The values of the parameters for the ACR clock domain on NE1 (Slave) are provided as follows. Parameter ACR Clock Source CES Service Value 1-ML1-1 CES_BTS1
Step 3 On NE1 (Slave), configure the ports that use the CES ACR clock domain. Then, see A.8.2.2 Configuring Ports Using the Clock Domain, and configure ports in the clock domain. The values of the parameters for the ACR clock domain are provided as follows. Parameter Clock Domain Clock Domain Board Value CES ACR1 Clock Domain 4-ML1
7-18
Issue 02 (2011-01-20)
7 Clock Features
Parameter Clock Port
Value 4-ML1-1(CES_BTS1) 4-ML1-2(CES_BTS2)
Step 4 Set Advanced Attributes of the ports inputting E1 clocks on NE2 (Master) and NE1 (Slave). For details, see A.5.4.2 Setting Advanced Attributes of Smart E1 Ports. The values of the parameters for the ports inputting E1 clocks on NE2 (Master) and NE1 (Slave) are provided as follows. Parameter Clock Mode NE1 Slave Mode NE2 System Clock Mode
----End

Related Tasks
A.7.6.2 Modifying CES Service Parameters A.8.2.1 Configuring the Primary Clock for an ACR Clock Domain A.8.2.2 Configuring Ports Using the Clock Domain

There is no alarm or event associated with the CES ACR management feature.
Relevant Alarms
CES_ACR_LOCK_ABN The CES_ACR_LOCK_ABN is an alarm indicating that the CES ACR service clock is locked. The alarm is reported when the CES ACR service is unavailable, an NE on the service trail is abnormal, or the network status is unstable.
Relevant Events
None.
7.2.11 FAQs
This section provides the answers to the questions that are frequently raised when CES ACR is adopted. Question: What are the factors that affect the CES ACR clock performance? Answer: The CES ACR clock performance is mainly affected by the following factors of a bearer PSN:
7 Clock Features
l l l
Delay variance Route switching Packet loss
Question: Can time information be restored through CES ACR? Answer: No. CES ACR recovers only frequency information. Question: In the CES ACR mechanism, can clocks be extracted from Fractional CES services? Answer: Since the product uses the enhanced timestamp solution, clocks can be extracted from Fractional CES services.
7-20
Issue 02 (2011-01-20)
A Task Collection
A
A.3 Managing the MSP The OptiX RTN 980 supports the linear MSP.
Task Collection
This document describes various tasks involved in this document. A.1 Network Management Network management involves topology management, communication management, and security management. A.2 Managing Radio Links Before you configure the radio link between two microwave sites, you need to configure the corresponding information about the radio link.
A.4 Managing TDM Services The TDM services involve the SDH service and the PDH service. A.5 Managing Ports Correct parameter settings of ports are the basis of configuring ports that transmit services. A.6 Configuring Ethernet Services and Features on the Packet Plane Configurations of Ethernet services and features on the packet plane include Ethernet port configuration, protection configuration, service configuration, protocol configuration, and OAM configuration. A.7 Managing MPLS/PWE3 Services and Features The OptiX RTN 980 supports multiple MPLS/PWE3 services and features. A.8 Managing the Clock To ensure the clock synchronization between transmission nodes on a transport network, you need to manage the NE clock. A.9 Using the RMON The 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.10 Configuring Auxiliary Ports and Functions The auxiliary ports and functions supported by the OptiX RTN 980 include the orderwire, synchronous data service, asynchronous data service, wayside E1 service, and external alarm. A.11 Verifying Services and Features This topic describes how to verify service and feature configurations.
Issue 02 (2011-01-20)
A-1
A Task Collection
A.1 Network Management

Network management involves topology management, communication management, and security management. A.1.1 Managing NEs Before you configure NEs, ensure that the NEs can be managed on the NMS. A.1.2 Configuring the NE Data If an NE is not configured after being created successfully, you need to configure the NE data so that the NMS can manage this NE. A.1.3 Configuring the 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.1.4 Suppressing Alarms for Monitored Objects This topic describes how to suppress certain alarms for a specific monitored object. A.1.5 Connecting Fibers or Cables To implement the end-to-end management on the NMS, you need to connect fibers or cables. A.1.6 Managing Subnets To facilitate NE management, you can allocate the NEs that are in the same domain or have similar attributes into the same subnet. A.1.7 Managing Communications To manage the NE by the NMS, ensure that the DCN communication is normal. A.1.8 Configuring Service Access of NEs You can ensure the security of a network by setting service access of the NEs on the network. A.1.9 Configuring an NE User NE users refer to the users who log in to and operate NEs. Different types of NE users are assigned different rights to log in and manage NEs. A.1.10 Configuring SSL Protocol Communication The security socket layer (SSL) protocol provides encrypted and reliable communication between entities. Therefore, SSL protocol communication greatly improves the network management security.
A.1.1 Managing NEs

Before you configure NEs, ensure that the NEs can be managed on the NMS. A.1.1.1 Creating NEs by Using the Search Method The U2000 can find all NEs that communicate with a specific gateway NE by using the IP address of the gateway NE, the IP address range of the gateway NE, or the NSAP addresses. In addition, the U2000 can create the NEs that are found in batches. Compared with the method of manually creating NEs, this method is faster and more reliable. A.1.1.2 Creating NEs by Using the Manual Method You can only create NEs one by one by using the manual method. The manual method, unlike the search method, does not allow creating NEs in batches.
A-2 Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 02 (2011-01-20)
A Task Collection
A.1.1.3 Configuring the Logical Board If the logical board corresponding to the 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.1.4 Changing the NE ID Modify the NE ID according to the engineering planning to guarantee that each NE ID is unique. Modifying the NE ID does not interrupt services. A.1.1.5 Changing the NE Name To better identify the NE in the Main Topology, name the NE according to the NE geographical location or the device connected to the NE. A.1.1.6 Synchronizing the NE Time By setting the NE time to be synchronous with the time on the NMS or standard NTP server, you can record the exact time when alarms and abnormal events occur. A.1.1.7 Localizing the 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 time with the local time. A.1.1.8 Configuring Standard NTP Keys When the NE time is synchronized with the time on the NTP server and the identity authentication is required, you need to configure NTP keys.
A.1.1.1 Creating NEs by Using the Search Method

The U2000 can find all NEs that communicate with a specific gateway NE by using the IP address of the gateway NE, the IP address range of the gateway NE, or the NSAP addresses. In addition, the U2000 can create the NEs that are found in batches. Compared with the method of manually creating NEs, this method is faster and more reliable.
Prerequisite
l l The communication between the NMS and the NE must be normal. You must be an NM user with NE operator authority or higher.
Tools, Equipment, and Materials

U2000
Procedure
Step 1 Choose File > Discovery > NE from the Main Menu. Step 2 Select Transport NE Search tab. Step 3 Select Search Mode. Step 4 Optional: If Search Mode is set to Search for NE, you need to add a search domain. 1. 2. Click Add, and then the Input Search Domain dialog box is displayed. Select an address type and enter the search address.
Issue 02 (2011-01-20)
A-3
A Task Collection
NOTE
l When Address Type is set to NSAP Address, ensure that the U2000 is installed with the OSI protocol stack software. l When Address Type is set to IP Address of GNE or IP Address Range of GNE, and the U2000 server and gateway NE are not in the same network segment, ensure that the IP routes of the network segments to which the U2000 server and gateway NE belong are configured on the U2000 and related routers.
3.
Click OK.
Step 5 Optional: Repeat Step 4 to add several search domains. Step 6 In the Search for NE dialog box, perform the operations described in the Note part.
NOTE
l If Create NE after search is selected, you need to specify NE User and Password. l You can select either Create NE after search or Upload after Create or both Create NE after search and Upload after Create. In this manner, after the NE searching is complete, the system automatically creates an NE and uploads the NE.
Step 7 Click Next, and then the Transport NE Search dialog box is displayed. After the search is complete, all the NEs that are found are displayed in the Result list. Step 8 Create NEs. 1. 2. 3. 4. 5. Select an NE that is not created from the Result list. Optional: Select the GNE ID of the NE. Click Create. The Create dialog box is displayed. Specify User Name and Password. Click OK. The icon of the created NE is displayed in the Main Topology.
Step 9 Optional: Repeat Step 8 to create other NEs that are not created. ----End
Related References
B.1.1.1 Parameter Description: NE Searching
A.1.1.2 Creating NEs by Using the Manual Method

You can only create NEs one by one by using the manual method. The manual method, unlike the search method, does not allow creating NEs in batches.
A Task Collection
Prerequisite
l l l You must be an NM user with NE operator authority or higher. The communication between the NMS and the NE to be created must be normal. If the NE to be created is a non-gateway NE, the gateway NE to which the NE to be created belongs must be created.
Procedure
Step 1 In the Physical ViewPhysical Root, right-click New > NE. The Create NE dialog box is displayed. Step 2 Choose RTN Series > OptiX RTN 980 from the Object Tree. Step 3 Enter the following information: ID, Extended ID, Name, and Remarks. Step 4 Set Gateway Type for the NE. If... The Gateway Type parameter is set to Gateway Then... Proceed to the next step.
The Gateway Type parameter is set to Non- Select the gateway to which the NE belongs, Gateway and go to Step 6. Step 5 Specify the protocol and IP address that the NE uses. If... If the Protocol parameter is set to IP If the Protocol parameter is set to OSI Then... Enter the IP Address of the NE. Enter the NSAP Address of the NE.
Issue 02 (2011-01-20)
A-5
A Task Collection
Step 6 Specify NE User and Password. The default user name is root and the default password is password. Step 7 Click OK. Step 8 Click the Main Topology. The icon of the NE is displayed at the cursor position. ----End
Related References
B.1.1.2 Parameter Description: NE Creation
A.1.1.3 Configuring the Logical Board

If the logical board corresponding to the 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 You must be an NM user with NE operator authority or higher. All the boards must be installed correctly.

U2000
Procedure
Step 1 Double-click the NE icon to open the NE layout diagram. Step 2 Optional: On the slot to which the board is to be added, right-click, and then select Add XXX. XXX is the name of the board to be added. Step 3 Optional: On the slot to which the board is to be deleted, right-click, and then select Delete.
A Task Collection
1. 2.
A dialog box is displayed for confirmation, click OK. A dialog box is displayed again for confirmation, click OK.
NOTE
Before deleting the board, delete the data, such as the service, clock, orderwire, and protection, on the board.
Step 4 Optional: Configure the optical module type for the SL4D board. 1. 2. 3. 4. Click the optical module on the SL4D board. Right-click and choose Add Port from the drop-down menu. Set Level for Port according to the type of the actually optical module on the SL4D board. Click OK.
----End
A.1.1.4 Changing the NE ID

Modify the NE ID according to the engineering planning to guarantee that each NE ID is unique. Modifying the NE ID does not interrupt services.
Prerequisite
You must be an NM user with NE operator authority or higher.

U2000
Procedure
Step 1 In the Main Topology, right-click the NE whose ID needs to be modified. Step 2 Choose Object Attributes. The Attribute dialog box is displayed. Step 3 Click the NE Attribute[xxx] tab.
NOTE
xxx indicates the current name of the NE.
Step 4 Click Modify NE ID. The Modify NE ID dialog box is displayed. Step 5 Specify New ID and New Extended ID.
Step 6 Click OK. A dialog box is displayed for confirmation, click OK. Step 7 Click OK. ----End
Issue 02 (2011-01-20) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. A-7
A Task Collection
Related References
B.1.1.3 Parameter Description: Attribute_Changing NE IDs
A.1.1.5 Changing the NE Name

To better identify the NE in the Main Topology, name the NE according to the NE geographical location or the device connected to the NE.
Prerequisite

U2000
Procedure
Step 1 In the Main Topology, select the NE whose name is to be modified, and then right-click. Step 2 Select the Object Attributes, then, the Attributes dialog box is displayed. Step 3 Click the NE Attribute [xxx] tab.
NOTE
xxx is the current name of the NE.
Step 4 Enter the name of the NE in Name.

NOTE
The name of an NE cannot contain any space or Chinese characters.
Step 5 Click OK, and then close the dialog box that is displayed indicating the operation result. The new name of the NE is displayed below the NE icon in the Main Topology. ----End
A.1.1.6 Synchronizing the NE Time

By setting the NE time to be synchronous with the time on the NMS or standard NTP server, you can record the exact time when alarms and abnormal events occur.
Prerequisite
l l You must be an NM user with NE operator authority or higher. When you need to synchronize the NE time with the time on the NMS server, the time zone and time must be set correctly on the PC or server that is installed with the NMS software.
A-8
A Task Collection
When you need to synchronize the NE time with the time on the NTP server, the time on the NTP server must be set correctly and the NTP protocol must be normal.

U2000
Procedure
Step 1 Choose Configuration > NE Batch Configuration > NE Time Synchronization from the Main Menu. Step 2 Click the NE Time Synchronization tab. Step 3 In the physical view, select the NE whose time needs to be synchronized, and then click . Step 4 After the operation is complete, a dialog box is displayed indicating that the operation is successful. Then, click Close. Step 5 When you need to synchronize the NE time with the NMS time, set the time synchronization mode and the related parameters. 1. 2. Set Synchronous Mode to NM. Optional: The NE time is synchronized with the NMS time immediately. a. Right-click the NE whose time needs to be synchronized, and then choose Synchronize with NM Time from the short-cut menu.
b. c. 3. 4.
In the dialog box that is displayed for confirmation, click Yes. Close the dialog box that is displayed indicating the operation result.
Click Apply. Optional: Set auto synchronization parameters. a. Set auto synchronization parameters.
b. c. d.
NOTE
Click Apply. In the dialog box that is displayed for confirmation, click Yes. Close the dialog box that is displayed indicating the operation result.
l When you need to synchronize the NE time with the NMS time, set Synchronous Mode to NM. l When you need to synchronize the NE time with the time on the NTP server, set Synchronous Mode to Standard NTP. Configure Standard NTP Authentication according to the requirements of the NTP server.
Step 6 When you need to synchronize the NE time with the time on the NTP server, set the time synchronization mode and the related parameters.
A Task Collection
1. 2. 3. 4. 5.
Set Synchronous Mode to Standard NTP. Configure Standard NTP Authentication according to the requirements of the NTP server. Click Apply. Click Close, and then close the dialog box that is displayed indicating the operation result. Configure the upper-layer NTP server. a. Select the NE, right-click in the configuration box where the standard NTP server is configured, and then choose New.
b.
Configure the parameters related to the NTP server.
c. d. 6.
Click Apply. Close the dialog box that is displayed indicating the operation result.
Optional: Copy the configuration of the upper-layer NTP server.

NOTE
Before the copy operation, set Synchronous Mode to Standard NTP for the source NE and the target NE.
a.
Select the NE to be copied, right-click, and then choose Copy Standard NTP Server.
A-10
A Task Collection
b. c. d. ----End
Select the NE to be pasted, right-click, and then choose Paste Standard NTP Server. In the dialog box that is displayed for confirmation, click Yes. Close the dialog box that is displayed indicating the operation result.
Related References
B.1.1.4 Parameter Description: NE Time Synchronization
A.1.1.7 Localizing the 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 time with the local time.
Prerequisite

U2000
Procedure
Step 1 Choose Configuration > NE Batch Configuration > NE Time Localization Management from the Main Menu. Step 2 Select the NE for time localization management from the Object Tree, and then click . Step 3 Click the Time Zone drop-down list, and then set the time zone of the NE. Step 4 Optional: Click DST, and then configure the related parameters. Step 5 Click Apply, and then close the dialog box that is displayed. ----End
Related References
B.1.1.5 Parameter Description: Localization Management of the NE Time
A.1.1.8 Configuring Standard NTP Keys

When the NE time is synchronized with the time on the NTP server and the identity authentication is required, you need to configure NTP keys.
Prerequisite
l l You must be an NM user with NE operator authority or higher. Set Synchronous Mode used by the NE to Standard NTP and Standard NTP Authentication to Enabled.
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. A-11
Issue 02 (2011-01-20)
A Task Collection
The NTP protocol is normal and the NTP identity authentication is enabled on the NTP server.

U2000
Procedure
Step 1 Choose Configuration > NE Batch Configuration > NE Time Synchronization from the Main Menu. Step 2 Click the Standard NTP Key Management tab. Step 3 In the physical view, select the NE whose NTP keys need to be configured, and then click . Step 4 Click Add. The Add Key and Password dialog box is displayed.
Step 5 After the related parameters are configured, click OK. ----End
Related References
B.1.1.6 Parameter Description: Standard NTP Key Management
A Task Collection
A.1.2 Configuring the NE Data

If an NE is not configured after being created successfully, you need to configure the NE data so that the NMS can manage this NE. A.1.2.1 Uploading the NE Data Uploading the NE data is commonly used for configuring the NE data. By uploading the NE data, the data such as the configuration, alarm, and performance data of the NE is uploaded to the NMS. A.1.2.2 Synchronizing NE Data Synchronizing NE data is uploading the NE-side data that is different from the NMS-side data (including conflicting data and absent data) to the NMS.
A.1.2.1 Uploading the NE Data

Uploading the NE data is commonly used for configuring the NE data. By uploading the NE data, the data such as the configuration, alarm, and performance data of the NE is uploaded to the NMS.
Prerequisite
l l An NE must be logged in to successfully. You must be an NM user with NE operator authority or higher.

U2000
Procedure
Step 1 Select the corresponding operation steps according to the status of the NE. If... An NE is not configured and the NE data needs to be uploaded. Then... In the Main Topology, double-click the NE that is not configured, and then refer to Step 2-Step 4.
An NE is configured with data and NE data Refer to Step 5-Step 8. needs to be uploaded. Step 2 In the displayed NE Configuration Wizard dialog box, select Upload, and then click Next. A dialog box is displayed for confirmation. Step 3 Click OK. Step 4 Click Close. Step 5 Choose Configuration > NE Configuration Data Management from the Main Menu. Step 6 Select the NE whose data needs to be uploaded from the Object Tree, and then click Step 7 Select the NE, click Upload, a dialog box is displayed for confirmation, and then click OK.
A Task Collection
The uploading is started. After the uploading is complete, the Operation Result dialog box is displayed. Step 8 Click Close. ----End
A.1.2.2 Synchronizing NE Data

Synchronizing NE data is uploading the NE-side data that is different from the NMS-side data (including conflicting data and absent data) to the NMS.
Prerequisite
l l l You must be an NM user with NE operator authority or higher. The NE is created. The NE is in unsynchronized state.
NOTE
When the NE is in unsynchronized state, it carries the
mark.
Procedure
Step 1 Method 1: 1. 2. 3. Choose Configuration > Synchronize NE Data from the Main Menu. Select one or more NEs from the NE list, and click .
Select one or more unsynchronized NEs, click the Synchronize button or select Synchronize from the shortcut menu. The NMS starts synchronizing the configuration data. In the Main Topology, select the NE with the mark, right-click it, and choose Synchronize NE Data from the shortcut menu. The system displays the Synchronize NE Data dialog box. Then, the NMS starts synchronizing the configuration data. Choose Configuration > NE Configuration Data Management from the Main Menu. Select one or more NEs from the NE list, and click .
Step 2 Method 2: 1.
2. 1. 2. 3.
Step 3 Method 3:
Select one or more unsynchronized NEs, click the Synchronize button or select Synchronize from the shortcut menu. A dialog box is displayed for confirmation. Click OK. Then, the NMS starts synchronizing the configuration data.
4.
----End
A.1.3 Configuring the 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 Task Collection
Prerequisite

U2000
Procedure
Step 1 In the NE Explorer, select the NE from the Object Tree, and then choose Performance > NE Performance Monitoring Time from the Function Tree. Step 2 Configure the parameters of the performance monitoring of NEs. 1. 2. 3. Select 15-Minute or 24-Hour. Select Enabled or Disabled in Set 15-Minute Monitoring or Set 24-Hour Monitoring. Set the start time and end time of the performance monitoring of NEs.
NOTE
l Generally, both Set 15-Minute Monitoring and Set 24-Hour Monitoring are enabled. l You can specify the start time of the performance monitoring function, only after selecting Enabled 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 Enabled and then selecting To in the Set 15-Minute Monitoring or Set 24-Hour Monitoring area.
4.
Click Apply, and then close the dialog box that is displayed.
----End
A.1.4 Suppressing Alarms for Monitored Objects

This topic describes how to suppress certain alarms for a specific monitored object.
Prerequisite
You must be an NM user with NE maintainer authority or higher.
A Task Collection
Tools, Instruments and Materials

U2000
Procedure
Step 1 In NE Explorer, select the required board. Step 2 Choose Alarm > Alarm Suppression from the Function Tree. Step 3 Set Monitored Object and click Query. Step 4 Set Status in Alarm Suppression. Step 5 Click Apply. Step 6 Close the prompt dialog box. ----End
A.1.5 Connecting Fibers or Cables

To implement the end-to-end management on the NMS, you need to connect fibers or cables. A.1.5.1 Creating an Optical Transmission Line or Radio Link by Using the Search Method Through the search method, the NMS can check the information about the radio link that is connected to a specified IF port. In this manner, a radio link can be created rapidly. The search method is commonly used for creating a radio link. A.1.5.2 Creating a Radio Link by Using the Manual Method After you manually fill in the table, the NMS can create a radio link according to the configured link information. This method is used when the actual radio link is not formed. A.1.5.3 Creating an Extended ECC Extended ECC connections indicate that the inter-NE DCN communication is implemented through concatenated NM ports. A.1.5.4 Creating a Back-to-Back Radio Connection Back-to-back radio connections indicate the stacking of multiple OptiX RTN NEs on one site.
A.1.5.1 Creating an Optical Transmission Line or Radio Link by Using the Search Method
Through the search method, the NMS can check the information about the radio link that is connected to a specified IF port. In this manner, a radio link can be created rapidly. The search method is commonly used for creating a radio link.
Prerequisite
l l You must be an NM user with NE operator authority or higher. The SDH/IF boards of various NEs must be created on the NMS.

U2000
A Task Collection
Procedure
Step 1 Choose File > Discovery > Fiber from the Main Menu. Step 2 Select the board of the NE on which the fiber needs to be searched for or the IF board of the NE on which radio links need to be searched for from the Subject Tree. Step 3 Click Search.
NOTE
l If Do not search the ports with Fiber/Cable created on NMS is selected, the port whose optical transmission line or radio link is created is not searched on the NMS. l If you need to check whether the connection of an optical transmission line or radio link is the same as the actual connection of the optical transmission line or radio link, do not select Do not search the ports with Fiber/Cable created on NMS. l If Do not search the ports with Fiber/Cable created on NMS is selected and all the selected ports are created with optical transmission line or radio link, a dialog box is displayed after the search, indicating that the search domain is null.
Step 4 After the operation is complete, a dialog box is displayed indicating that the operation is successful. Then, click Close. Step 5 In Physical Fiber/Cable Link List, select one or multiple optical transmission lines or radio links, and then click Create Fiber/Cable.
NOTE
l When you select one or multiple optical transmission lines or radio links from Physical Fiber/Cable Link List, the conflicting optical transmission lines or radio links are automatically displayed in Logical Fiber/Cable Link List. In this manner, you need to delete such conflicting optical transmission lines or radio links by referring to Step 5, and then create the links. l When you create an optical transmission line or radio link, if the selected optical transmission line or radio link is in the Already created state, No fiber to create is displayed.
Step 6 When you select one or multiple conflicting optical transmission lines or radio links from Logical Fiber/Cable Link List, click Delete Fiber/Cable. ----End
Subsequent Handling
If the information about the optical transmission line or radio link that is created through the search method, you can supplement the information by changing the information about the optical transmission line or cable.
A.1.5.2 Creating a Radio Link by Using the Manual Method

After you manually fill in the table, the NMS can create a radio link according to the configured link information. This method is used when the actual radio link is not formed.
Prerequisite
l l You must be an NM user with NE operator authority or higher. The corresponding boards of various NEs must be created on the NMS.

U2000
A Task Collection
Procedure
Step 1 Choose File > Create > Link from the Main Menu. The Create Link dialog box is displayed. Step 2 Choose Fiber/Cable > Microwave Link from the Object Tree. Step 3 Configure the attributes of the created radio link according to the data plan.
Step 4 Click OK. In the Main Topology, the created radio link is displayed between the source NE and the sink NE. ----End
A.1.5.3 Creating an Extended ECC

Extended ECC connections indicate that the inter-NE DCN communication is implemented through concatenated NM ports.
Prerequisite

U2000
A-18
Issue 02 (2011-01-20)
A Task Collection
Procedure
Step 1 Choose File > Create > Link from the Main Menu. The Create Link dialog box is displayed. Step 2 Choose Link > Extended ECC. Step 3 Configure the attributes of the created extended ECC according to the data plan.
Step 4 Click OK. In the Main Topology, the created extended ECC is displayed between the source NE and the sink NE. ----End
A.1.5.4 Creating a Back-to-Back Radio Connection

Back-to-back radio connections indicate the stacking of multiple OptiX RTN NEs on one site.
Prerequisite
l l You must be an NM user with NE operator authority or higher. The corresponding IF board must be added on the NE Panel.

U2000
Procedure
Step 1 In the Main Topology, choose File > Create > Link. The Create Link dialog box is displayed. Step 2 Select Fiber/Cable > Microwave Back To Back. Step 3 Select the source NE from the drop-down list of Source NE. Step 4 Select the sink NE from the drop-down list of Sink NE. Step 5 Configure the attributes of the back-to-back radio connection.
Issue 02 (2011-01-20)
A-19
A Task Collection
Step 6 Click OK. The created back-to-back radio connection is displayed in the Main Topology. ----End
A.1.6 Managing Subnets

To facilitate NE management, you can allocate the NEs that are in the same domain or have similar attributes into the same subnet. A.1.6.1 Creating a Subnet In the Main Topology, you can create a subnet object and allocate an NE to this subnet. A.1.6.2 Copying Topology Objects In the current topology, you can copy topology objects from one subnet to another subnet. A.1.6.3 Moving Topology Objects In the current topology, you can move topology objects from one subnet to another subnet.
A.1.6.1 Creating a Subnet

In the Main Topology, you can create a subnet object and allocate an NE to this subnet.
Prerequisite

U2000
Procedure
Step 1 In the Main Topology, right-click, and then choose New > Subnet. The Create Physical Subnet dialog box is displayed. Step 2 Click the Property tab. Step 3 Enter the attributes of the subnet. Step 4 Click the Select Object tab, select a created NE from Available Objects, and then click to add the NE to Selected Objects.

NOTE
A Task Collection
l Click l Click
to add the selected object in the left pane to the right pane. to add all the objects in the left pane to the right pane.
Step 5 Click OK. Step 6 In the Main Topology, click in a blank area, and then the created subnet is displayed in the position where you click. ----End
A.1.6.2 Copying Topology Objects

In the current topology, you can copy topology objects from one subnet to another subnet.
Prerequisite

U2000
Procedure
Step 1 In the Main Topology, right-click the NE or subnet that needs to be copied. Step 2 Choose Edit > Copy to. The Select a Parent Subnet dialog box is displayed. Step 3 Select the subnet that the NE or subnet needs to be pasted. Step 4 Click OK. ----End
A.1.6.3 Moving Topology Objects

In the current topology, you can move topology objects from one subnet to another subnet.
Prerequisite

U2000
Procedure
Step 1 In the Main Topology, right-click the NE or subnet that needs to be moved. Step 2 Choose Edit > Move to.
A Task Collection
The Select the path of Parent Subnet dialog box is displayed. Step 3 Select the subnet that the NE or subnet needs to be moved to. Step 4 Click OK. ----End
A.1.7 Managing Communications

To manage the NE by the NMS, ensure that the DCN communication is normal. A.1.7.1 Setting NE Communication Parameters The communication parameters of an NE include the IP address of the NE, the gateway IP address, and the subnet mask. A.1.7.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 network planning information. A.1.7.3 Configuring Extended ECC Communication If there is no DCC between two or more NEs, you can connect the Ethernet NM ports or NE cascading ports on the system control boards of the NEs to achieve extended ECC communication. A.1.7.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. A.1.7.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.1.7.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.1.7.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.1.7.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 RTN 980 is L1. A.1.7.9 Configuring the 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.1.7.10 Configuring the VLAN ID and Bandwidth Used by an Inband DCN
A Task Collection
The VLAN ID used by an inband DCN must be different from the VLAN ID used by services and the bandwidth by an inband DCN must meet the requirements of the transmission network for managing messages. A.1.7.11 Configuring the Enable Status of the Inband DCN Function on Ports The network management information can be transmitted over a link by the inband DCN only when the inband DCN function is enabled on the ports at both ends of the link. A.1.7.12 Configuring the Protocol Type of the Inband DCN The inband DCN supports two types of protocol: IP and HWECC. The IP is the default protocol supported by the inband DCN. Generally, it is recommended that you use the default value. A.1.7.13 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.1.7.14 Querying IP Routes By querying IP routes, you can check whether the IP over DCC solution and inband DCN solution is configured correctly and whether the communication between NEs is normal. A.1.7.15 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.1.7.16 Configuring Access Control When the equipment is connected to the NMS through an Ethernet service port, you need to configure access control.
A.1.7.1 Setting NE Communication Parameters

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

U2000
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Communication > Communication Parameters from the Function Tree. Step 2 Configure the communication parameters of the NE. Step 3 Click Apply, and then close the dialog box that is displayed.
NOTE
When you configure multiple parameters, click Apply respectively.
Issue 02 (2011-01-20)
A-23
A Task Collection
----End
Related References
B.1.2.1 Parameter Description: NE Communication Parameter Setting

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 network planning information.
Prerequisite

U2000
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Communication > DCC Management from the Function Tree. Step 2 Click the DCC Rate Configuration tab. Step 3 Optional: Change the enable status of the DCC. 1. 2.
A-24
Double-click the cell in the Enabled/Disabled column to which the DCC corresponds. Select the required state from the drop-down list. Click Apply.
A Task Collection
Step 4 Optional: Change the protocol type of the DCC. 1. 2. Double-click the cell in the Protocol Type column to which the DCC corresponds. Select the required protocol type from the drop-down list. Click Apply.
NOTE
On the NMS interface, the first interface on the system control, switching, and clock board (like ) corresponds to its external clock interface.
Step 5 Optional: Create DCCs. 1. 2. Click Create. Then, the Create dialog box is displayed. Set the attributes of the DCC.
3.
Click OK.
----End
Related References
B.1.2.2 Parameter Description: DCC Management_DCC Rate Configuration

If there is no DCC between two or more NEs, you can connect the Ethernet NM ports or NE cascading ports on the system control boards of the NEs to achieve extended ECC communication.
Prerequisite

U2000
Context
The default extended ECC mode is Auto mode.
A Task Collection
Procedure
Step 1 Click an NE in the NE Explorer. Choose Communication > ECC Management from the Function Tree. Step 2 Optional: You can disable the extended ECC function in Auto mode.
1. 2. 1. 2.
Click Stop. A confirmation dialog box is displayed. Click OK. Set ECC Extended Mode to Specified mode. Set related parameters for the server end.
Step 3 Optional: Set parameters for the extended ECC function in Specified mode at the server end.
3. 4. 1. 2.
Click Apply. A confirmation dialog box is displayed. Click OK. Set ECC Extended Mode to Specified mode. Set related parameters for the client end.
Step 4 Set parameters for the extended ECC function in Specified mode at the client end.
3. 4.
Click Apply. A confirmation dialog box is displayed. Click OK.
Step 5 Enable the automatic extended ECC function.

NOTE
Before enabling the automatic extended ECC function, you need to clear related parameters that are configured in Specified mode for the server end and client end.
1. 2.
A-26
Set ECC Extended Mode to Specified mode. To clear parameters configured for the server end, click Clear Server.
A Task Collection
A confirmation dialog box is displayed. 3. 4. 5. 6. 7. 8. Click OK. To clear parameters configured for the client end, click Clear Client. A confirmation dialog box is displayed. Click OK. Set ECC Extended Mode to Auto mode. Click Apply. A confirmation dialog box is displayed. Click OK.
----End
Related References
B.1.2.4 Parameter Description: ECC Management_Ethernet Port Extended ECC
A.1.7.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
You must be an NM user with NE operator authority or higher. The DCC bytes required by the transparent transmission function must not be used.

U2000
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. 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 02 (2011-01-20)
A-27
A Task Collection
Step 5 Click OK. ----End
Related References
B.1.2.3 Parameter Description: DCC Management_DCC Transparent Transmission Management
A.1.7.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

U2000
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Communication > IP Protocol Stack Management from the Function Tree. Step 2 Click the IP Route Management tab. Step 3 Click New. Then, the Create an IP Route dialog box is displayed. Step 4 Set the parameters of the static IP route.
NOTE
The created static route has a lower priority than a dynamic route.

A Task Collection
Related References
B.1.2.7 Parameter Description: IP Protocol Stack Management_IP Route Management Creation
A.1.7.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

U2000
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Communication > IP Protocol Stack 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.

A Task Collection
Step 5 Optional: Set OSPF parameters for DCC channels. 1. 2. 3. Click the Port OSPF Parameter Settings tab. Set the OSPF parameters for DCC channels. Click Apply.
----End
Related References
B.1.2.8 Parameter Description: IP Protocol Stack Management_OSPF Parameter Settings
A.1.7.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
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Communication > IP Protocol Stack Management from the Function Tree. Step 2 Click the Proxy ARP tab. Step 3 Set the enable status of the proxy ARP.
Step 4 Click Apply. ----End
Related References
B.1.2.9 Parameter Description: IP Protocol Stack_Proxy ARP

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 RTN 980 is L1.
Prerequisite
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Communication > OSI Management from the Function Tree.
A Task Collection
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. The system displays the prompt. Step 5 Click Yes. ----End
Related References
B.1.2.11 Parameter Description: OSI Management_Network Layer Parameter

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

U2000
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Communication > OSI Management from the Function Tree. Step 2 Click the OSI Tunnel tab. Step 3 Click New. Then, the Create OSI Tunnel dialog box is displayed. Step 4 Set Remote IP Address and LAPD Actor.
Issue 02 (2011-01-20)
A-31
A Task Collection
Step 5 Click OK. Step 6 Configure the attributes of the OSI tunnel according to the network planning.
Related References
B.1.2.13 Parameter Description: OSI Management_OSI Tunnel

The VLAN ID used by an inband DCN must be different from the VLAN ID used by services and the bandwidth by an inband DCN must meet the requirements of the transmission network for managing messages.
Prerequisite
You must be an NM user with NE administrator authority or higher.

U2000
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Communication > DCN Management from the Function Tree. Step 2 Click the Bandwidth Management tab. Step 3 Set the VLAN ID and bandwidth used by an inband DCN.
A-32
Issue 02 (2011-01-20)
A Task Collection
Related References
B.1.2.14 Parameter Description: DCN Management_Bandwidth Management
A.1.7.11 Configuring the Enable Status of the Inband DCN Function on Ports
The network management information can be transmitted over a link by the inband DCN only when the inband DCN function is enabled on the ports at both ends of the link.
Prerequisite

U2000
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Communication > DCN Management from the Function Tree. Step 2 Click the Port Settings tab. Step 3 Select FE/GE. Step 4 Configure the enable status of the inband DCN function on ports.
Step 5 Click Apply.

A Task Collection
Step 6 Select IF. Step 7 Configure the enable status of the inband DCN function on ports.
Related References
B.1.2.15 Parameter Description: DCN Management_Port Setting
A.1.7.12 Configuring the Protocol Type of the Inband DCN

The inband DCN supports two types of protocol: IP and HWECC. The IP is the default protocol supported by the inband DCN. Generally, it is recommended that you use the default value.
Prerequisite
l l You must be an NM user with NE operator authority or higher. The corresponding board must be added to the NE Panel.

U2000
Procedure
Step 1 In the NE Explorer, select the required NE from the Object Tree, and then choose Communication > DCN Management from the Function Tree. Step 2 Click the Protocol Settings tab. Step 3 Set the protocol type of the inband DCN.
Related References
B.1.2.16 Parameter Description: DCN Management_Protocol Setting

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

U2000
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Communication > NE ECC Link Management from the Function Tree. Step 2 Check whether the ECC route and related parameters are set correctly in NE ECC Link Management List. ----End
Related References
B.1.2.5 Parameter Description: NE ECC Link Management

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

U2000
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Communication > IP Protocol Stack Management from the Function Tree. Step 2 Click the IP Route Management tab. Step 3 Click Query. Then, close the dialog box that is displayed. Step 4 Check whether the IP routes and related parameters in the routing table are in accordance with the planning information. ----End
Related References
B.1.2.6 Parameter Description: IP Protocol Stack Management_IP Route Management
A Task Collection

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

U2000
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. 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
Related References
B.1.2.12 Parameter Description: OSI Management_Routing Table
A.1.7.16 Configuring Access Control

When the equipment is connected to the NMS through an Ethernet service port, you need to configure access control.
Prerequisite

U2000
Procedure
Step 1 In the NE Explorer, select the NE from the Object Tree and then choose Communication > DCN Management from the Function Tree. Step 2 Click the Access Control tab. Step 3 Set the parameters for configuring access control.
A Task Collection
Related References
B.1.2.17 Parameter Description: DCN Management_Access Control
A.1.8 Configuring Service Access of NEs

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

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

U2000
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.
Issue 02 (2011-01-20)
A Task Collection
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.1.8.2 Configuring Ethernet Access to NEs

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

U2000
Background Information
l l It is recommended that the LCT accesses an NE through Ethernet ports. If you need to initialize an NE or perform software loading by using the LCT, the LCT needs to access the NE through Ethernet ports.
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 Set the status of the network port to Enabled and enable the Ethernet access function of the NE.
NOTE
To disable the Ethernet access function of an NE, set the status of the network port to Disabled.
Step 3 Click Apply. Then, a confirmation dialog box is displayed. Step 4 Click OK. Then, close the operation result dialog box that is displayed. ----End
A Task Collection
A.1.8.3 Configuring Serial Interface Access to NEs

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

U2000
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.
Step 3 Click Apply. and then close the displayed prompt dialog box. Step 4 Optional: Select the baud rate of the serial interface from the Baud Rate drop-down list. Click Apply, and then close the displayed prompt dialog box. ----End
A.1.9 Configuring an NE User

NE users refer to the users who log in to and operate NEs. Different types of NE users are assigned different rights to log in and manage NEs. A.1.9.1 Creating an NE User Based on the operation rights, NE users are divided into five levels, which involve monitoring level, operation level, maintenance level, system level, and debugging level in an ascending order. Different levels of NE users can be created as required. A.1.9.2 Changing the Password of an NE User
A Task Collection
Periodically changing the password of an NE user ensures the NE security. A.1.9.3 Setting Warning Screen Parameters This topic describes how to enable the warning screen function. When a user logs in to an NE, the NMS can display some information to the user. The displayed information can be selfdefined. A.1.9.4 Switching NE Users This section describes how to switch an NE user to a higher-level NE user when the operations on the NMS are beyond the operation rights of the NE user.
A.1.9.1 Creating an NE User

Based on the operation rights, NE users are divided into five levels, which involve monitoring level, operation level, maintenance level, system level, and debugging level in an ascending order. Different levels of NE users can be created as required.
Prerequisite
l l You must be an NM user with NE administrator authority or higher. An online user can create a user at a lower level.

U2000
l l The default NE user is at the monitoring level. For security of NE data, NE users are assigned operation rights based on their responsibilities.
Procedure
Step 1 Select the required NE from the Object Tree in the NE Explorer. Choose Security > NE User Management from the Function Tree.A dialog box is displayed, indicating that the operation is successful. Step 2 Close the dialog box. Step 3 Click Add. The Add NE User dialog box is displayed. Step 4 Set the parameters of the NE user according to the planning information.
A-40
Issue 02 (2011-01-20)
A Task Collection
Step 5 Click OK. Then, close the dialog box that is displayed. ----End
Related References
B.1.3.2 Parameter Description: NE User Management_Creation
A.1.9.2 Changing the Password of an NE User

Periodically changing the password of an NE user ensures the NE security.
Prerequisite
l l l You must be an NM user with NE administrator authority or higher. The NE user is created. An online user can change the password of a user at a lower level.

U2000
NOTE
Periodically change the password of an NE user to avoid password leaks.
Procedure
Step 1 Select the required NE from the Object Tree in the NE Explorer. Choose Security > NE User Management from the Function Tree.A dialog box is displayed, indicating that the operation is successful. Step 2 Close the dialog box.
A Task Collection
Step 3 Select the required NE user from the NE user management list, and click Set Password. The Set Password of NE User dialog box is displayed. Step 4 Input New Password, and input it again in Confirm Password.
A.1.9.3 Setting Warning Screen Parameters

This topic describes how to enable the warning screen function. When a user logs in to an NE, the NMS can display some information to the user. The displayed information can be selfdefined.
Prerequisite
You must be an NM user with NE maintainer authority or higher.

U2000
Procedure
Step 1 In the NE Explorer, select the required NE from the Object Tree. Then, choose Security > NE Security Parameters from the Function Tree. Step 2 Set Warning Screen Switching and Warning Screen Information according to the planning information.
Step 3 Click Apply Then, close the dialog box that is displayed. ----End
A Task Collection
Related References
B.1.3.1 Parameter Description: NE User Management
A.1.9.4 Switching NE Users

This section describes how to switch an NE user to a higher-level NE user when the operations on the NMS are beyond the operation rights of the NE user.
Prerequisite
l l You must be an NM user with NE administrator authority or higher. An NE user is created.

U2000
An NE cannot be logged in to and managed by the same NE user from different servers at the same time. If the same NE user from different servers logs in to an NE at different time, the first online user will be forcibly logged out of the NE.
Procedure
Step 1 In the NE Explorer, select the required NE from the Object Tree. Then, choose Security > NE Login Management from the Function Tree. Step 2 Select the required NE, and click Switch NE User. The Switch Current NE User dialog box is displayed. Step 3 Set User and Password of the user to be switched.
Issue 02 (2011-01-20)
A-43
A Task Collection
A.1.10 Configuring SSL Protocol Communication

The security socket layer (SSL) protocol provides encrypted and reliable communication between entities. Therefore, SSL protocol communication greatly improves the network management security. A.1.10.1 Configuring SSL Protocol Communication Between a U2000 Server and its Clients Secure Sockets Layer (SSL) protocol communication between a U2000 server and its clients is supported only after corresponding configurations are performed on the U2000 server and clients. A.1.10.2 Configuring the Connection Mode Between a U2000 Client and Its Gateway NE Two connection modes are supported between a U2000 client and its gateway NE, namely common connection mode and Secure Sockets Layer (SSL) connection mode.
A.1.10.1 Configuring SSL Protocol Communication Between a U2000 Server and its Clients
Secure Sockets Layer (SSL) protocol communication between a U2000 server and its clients is supported only after corresponding configurations are performed on the U2000 server and clients.
Prerequisite
The connection mode of the U2000 server is set to SSL.

U2000
l l Two connection modes are supported, which are Common and Security(SSL) and which can be queried on the U2000 server by running a query command. The default connection mode is Common.
NOTE
l When the U2000 server and its client are deployed on the same host and the U2000 server uses the SSL connection mode, the client can log in to the server by using the common or SSL connection mode. When the U2000 server and its client are deployed on the same host and the U2000 server uses the common connection mode, the client can log in to the server only by using the common connection mode. l When the U2000 server and its client are deployed on different hosts, the client can log in to the U2000 server only by using the same connection mode as the U2000 server.
Procedure
Step 1 Start the U2000 client. Step 2 In the Login interface, click
A-44
.
Issue 02 (2011-01-20)
A Task Collection
Then, the Server List dialog box is displayed. Step 3 Select the required U2000 server and click Modify. Then, the Modify Server Information dialog box is displayed.
Step 4 Set Mode to Security(SSL). Step 5 Click OK. Step 6 Click OK. ----End
A.1.10.2 Configuring the Connection Mode Between a U2000 Client and Its Gateway NE
Two connection modes are supported between a U2000 client and its gateway NE, namely common connection mode and Secure Sockets Layer (SSL) connection mode.
Prerequisite
l l You must be an NM user with NE maintainer authority or higher. SSL licenses have been deployed on the gateway NE and the U2000 client according to the SSL loading guide.

U2000
Procedure
Step 1 Configure the connection mode of the U2000 client. 1. 2. Choose Administration > DCN Management from Main Menu. Then, the Filter NE dialog box is displayed. Click Cancel and then click the GNE tab. Then, the Filter NE dialog box is displayed. Click Click OK. Select the required NE, right-click the NE, and choose Modify GNE from the shortcut menu. Then, the Modify GNE dialog box is displayed. Change the value of Connection Mode to Security SSL.
3. 4. 5.
, choose the required gateway NE, and then click OK.
6.
Issue 02 (2011-01-20)
A Task Collection
7. 8. 1. 2.
Click OK. A warning dialog box is displayed. Click OK. Then, close the dialog box that is displayed. Select the NE from the Object Tree in the NE Explorer. Choose Communication > Communication Parameters from the Function Tree. Set Connection Mode to Security SSL or Common + Security SSL.
NOTE
Step 2 Configure the connection mode of the gateway NE.
If Connection Mode of a gateway NE is Security SSL, tools (such as the Web LCT and DC) that use the common connection mode cannot communicate with the gateway NE.
3.
Click Apply. Then, close the dialog box that is displayed.
----End
A-46
Issue 02 (2011-01-20)
A Task Collection
A.2 Managing Radio Links

Before you configure the radio link between two microwave sites, you need to configure the corresponding information about the radio link. A.2.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.2.2 Creating an XPIC Protection Group If you configure two XPIC radio links after binding the two radio links as an XPIC workgroup, the parameter settings including the channel bandwidth, transmit frequency, transmit power, and ATPC attribute are ensured to be the same for the two radio links. A.2.3 Setting the AM Attributes of the XPIC Hybrid Radio Link After the XPIC protection group is created, you need to configure the AM attributes of the XPIC Integrated IP radio link according to the planned values. A.2.4 Configuring the IF/ODU Information of a Radio Link By performing this operation, you can configure the IF/ODU information for a radio link. A.2.5 Creating an N+1 Protection Group When multiple STM-1 or Hybrid microwave services are transmitted in the point-to-point mode, you can adopt the N+1 protection configuration. A.2.6 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.2.7 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.2.8 IF 1+1 Protection Switching You can perform external switching on the IF 1+1 protection by performing IF 1+1 protection switching. A.2.9 IF N+1 Protection Switching You can perform external switching on the IF N+1 protection by performing IF N+1 protection switching. A.2.10 Starting/Stopping the N+1 Protection Protocol If you stop the N+1 protection protocol and then restart it, the N+1 protection protocol can be restored to the initial state.
A.2.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 You must be an NM user with NE operator authority or higher. The IF boards and the ODUs to which the IF boards are connected must be added on the NE Panel.
Issue 02 (2011-01-20)
A Task Collection
The IF boards of an IF 1+1 FD/SD protection group must be configured in two paired slots.

U2000
When a 1+0 service is converted into a 1+1 HSB protection through the configuration of the IF 1+1 protection group, the original service is not interrupted. The board where the original service exists, however, needs to be set to the working board.
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > IF 1+1 Protection from the Function Tree. Step 2 Click Create. The Create IF 1+1 Protection dialog box is displayed. Step 3 Configure the parameters of the IF 1+1 protection group.
Step 4 Click OK, and then close the dialog box that is displayed indicating the operation result. ----End
Related References
B.2.5 Parameter: IF 1+1 Protection_Create
A.2.2 Creating an XPIC Protection Group

If you configure two XPIC radio links after binding the two radio links as an XPIC workgroup, the parameter settings including the channel bandwidth, transmit frequency, transmit power, and ATPC attribute are ensured to be the same for the two radio links.
Prerequisite
l l You must be an NM user with NE operator authority or higher. The corresponding XPIC IF boards and the ODUs connected to the XPIC IF boards are added to the NE Panel.

U2000
A Task Collection
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Link Configuration from the Function Tree. Step 2 Click the XPIC tab. Step 3 Click New. The Create XPIC Protection Group dialog box is displayed. Step 4 Configure the parameters for the XPIC protection group.
Related References
B.2.1 Parameter Description: Link Configuration_XPIC Workgroup_Creation
A.2.3 Setting the AM Attributes of the XPIC Hybrid Radio Link

After the XPIC protection group is created, you need to configure the AM attributes of the XPIC Integrated IP radio link according to the planned values.
Prerequisite
l l You must be an NM user with NE operator authority or higher. The XPIC protection group must be created.

U2000
A Task Collection
The XPIC IF boards, IFX2 and ISX2, support Integrated IP radio, and the AM attributes can be configured.
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Link Configuration from the Function Tree. Step 2 Click the XPIC tab. Step 3 Click the Hybrid/AM Configuration tab. Step 4 Configure the AM attributes of the XPIC Hybrid radio link.
Related References
B.2.2 Parameter Description: Link Configuration_XPIC

By performing this operation, you can configure the IF/ODU information for a radio link.
Prerequisite

U2000
Precautions
l l In the case of 1+1 HSB/SD protection, you need to configure only the IF/ODU information of the main radio link. In the case of 1+1 FD protection, you need to configure the IF/ODU information of the main radio link and the ODU information of the standby radio link.
A-50
A Task Collection
l l l
In the case of XPIC configuration, you need to configure the IF/ODU information of the two radio links in different polarization directions separately. In the case of N+1 protection, you need to configure the IF/ODU information of the N+1 radio links respectively. The MW_CFG_MISMATCH alarm is reported, if the E1 count, AM enabled status, 1588 timeslot enabled status, modulation mode, or IF bandwidth is set inconsistently for both ends of a Integrated IP radio link.
Procedure
Step 1 In the NE Explorer, select the NE 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. ----End
Related References
B.2.7 Parameter: Link Configuration_IF/ODU Configuration

When multiple STM-1 or Hybrid microwave services are transmitted in the point-to-point mode, you can adopt the N+1 protection configuration.
A Task Collection
Prerequisite
l l l You must be an NM user with NE operator authority or higher. The IF boards and the ODUs to which the IF boards are connected must be added on the NE Panel. The IF1 boards must work in the STM-1 mode.

U2000
l l When an N+0 service is converted into an N+1 service through the configuration of the N +1 protection group, the original service is not interrupted. In the case of Integrated IP radio, the Hybrid/AM attributes must be the same for all the N +1 radio links in the N+1 protection group.
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > N+1 Protection from the Function Tree. Step 2 Click Create. The Create N+1 Protection dialog box is displayed.
Step 3 Configure the Attribute of the N+1 protection group. Step 4 Configure the mapping relation between the board and the slot. 1. 2. Select Work Unit from Select Mapping Direction. Select a port to which a working channel corresponds from Select Mapping Way, and then click 3. .
Repeat Step 4.2 to select the ports to which other working channels correspond. Click .
A-52
Issue 02 (2011-01-20)
A Task Collection
4. 5.
Select Protection Unit from Select Mapping Direction. Select a port to which a protection channel corresponds from Select Mapping Way, and then click .
Step 5 Click OK. Then, click OK to close the dialog box that is displayed, indicating that the operation is successful. ----End
Related References
B.2.3 Parameter Description: N+1 Protection_Create
A.2.6 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 You must be an NM user with NE administrator authority or higher. The IF 1+1 protection must be configured.

U2000
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > IF 1+1 Protection from the Function Tree. Step 2 Click Query, and then close the displayed prompt dialog box. In Protection Group, check the IF 1+1 protection groups. Step 3 Select the IF 1+1 protection group whose protection status needs to be queried. Step 4 Click Query Switch Status, and then close the displayed prompt dialog box. In Slot Mapping Relation, check the protection status of the IF 1+1 protection group. ----End
Related References
B.2.6 Parameter Description: IF 1+1 Protection
A.2.7 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
Issue 02 (2011-01-20)

A Task Collection
The IF N+1 protection must be configured.

U2000
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > N+1 Protection from the Function Tree. Step 2 Click Query, and then close the displayed prompt dialog box. In Protection Group, check the IF N+1 protection groups. Step 3 Select the protection group whose protection status needs to be queried. Step 4 Click Query Switch Status, and then close the displayed dialog box. In Slot Mapping Relation, check the IF N+1 protection status. ----End
Related References
B.2.4 Parameter Description: N+1 Protection
A.2.8 IF 1+1 Protection Switching

You can perform external switching on the IF 1+1 protection by performing IF 1+1 protection switching.
Prerequisite
l l You must be an NM user with NE operator authority or higher. The IF 1+1 protection must be configured.

U2000
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > IF 1+1 Protection from the Function Tree. Step 2 In Protection Group, select the protection group for protection switching. Step 3 In Slot Mapping Relation, select a working unit or the protection unit of the protection group, and then right-click the selected unit. Step 4 Choose the required switching mode from the shortcut menu. Step 5 Click Close. Step 6 Click Query Switching Status and check whether the switching is successful, and then close the displayed prompt dialog box. ----End
A Task Collection
A.2.9 IF N+1 Protection Switching

You can perform external switching on the IF N+1 protection by performing IF N+1 protection switching.
Prerequisite
l l You must be an NM user with NE operator authority or higher. The IF N+1 protection must be configured.

U2000
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > N+1 Protection from the Function Tree. Step 2 In Protection Group, select the protection group for protection switching. Step 3 In Slot Mapping Relation, select a working unit or the protection unit of the protection group, and then right-click the selected unit. Step 4 Choose the required switching mode from the shortcut menu. Step 5 In the dialog box that is displayed, click OK. The system displays the dialog box that indicates the successful operation. Step 6 Click Close. Step 7 Click Query Switch Status to check whether the switching operation is successful. ----End
A.2.10 Starting/Stopping the N+1 Protection Protocol

If you stop the N+1 protection protocol and then restart it, the N+1 protection protocol can be restored to the initial state.
Prerequisite
l l l You must be an NM user with NE operator authority or higher. The IF N+1 protection must be configured. The N+1 protection protocol is enabled.

U2000
Precautions
l l Stopping the N+1 protection protocol causes a failure of the N+1 protection. When services are switched onto the protection channel, stopping the N+1 protection protocol causes switchover of the services back to the working tunnel. At this time, if the
Issue 02 (2011-01-20)
A Task Collection
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 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > N+1 Protection from the Function Tree. Step 2 In Protection Group, select the protection group whose N+1 protection protocol needs to be started. Step 3 Click Start Protocol or Stop Protocol. Then, close the displayed prompt dialog box. Step 4 Click Query to check the protocol status. ----End
A.3 Managing the MSP

The OptiX RTN 980 supports the linear MSP. A.3.1 Configuring Linear MSP You can configure linear MSP to protect services over the optical fibers between two nodes. A.3.2 Querying the Status of the Linear MSP By using this operation, you can know the current information about the linear MSP. A.3.3 Performing Linear MSP Switching By using this operation, you can perform the external switching on the linear MSP. A.3.4 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.3.5 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.3.6 Querying Ring MSP Status This topic describes how to check the current status of a ring MSP protection group. A.3.7 Triggering Ring MSP Switching This topic describes how to trigger external ring MSP switching. A.3.8 Starting/Stopping the Ring MSP Protocol If you first stop the ring MSP protocol and then start it, the ring MSP protocol is restored to its initial state.
A.3.1 Configuring Linear MSP

You can configure linear MSP to protect services over the optical fibers between two nodes.
Prerequisite
l
A-56

A Task Collection
The corresponding board must be added on the NE Panel.

U2000
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 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Linear MS from the Function Tree. Step 2 Click Create. The system displays the Create a Linear Multiplex Section dialog box. Step 3 Set the parameters of the linear MSP group.
Step 4 Click OK, and then close the dialog box that is displayed. ----End
A Task Collection
Follow-up Procedure
l In the case of the 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. In the case of the 1+1 linear MSP, you need to configure bidirectional cross-connections between the services and the working channels later.
Related References
B.3.1 Parameter Description: Linear MSP_Creation
A.3.2 Querying the Status of the Linear MSP

By using this operation, you can know the current information about the linear MSP.
Prerequisite
l l You must be an NM user with NE operator authority or higher. The linear MSP must be configured.

U2000
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Linear MS from the Function Tree. Step 2 Click Query > Query Protection Group to query the current linear MSP group. Then close the dialog box that is displayed. Step 3 In Protection Group, click the linear MSP group to be queried. Step 4 Click Query > Query Switching Status In Slot Mapping Relation, query the status of the linear MSP. ----End
Related References
B.3.2 Parameter Description: Linear MSP
A.3.3 Performing Linear MSP Switching

By using this operation, you can perform the external switching on the linear MSP.
Prerequisite
l l l
A-58
You must be an NM user with NE operator authority or higher. The linear MSP must be configured. The protection protocol is enabled.
A Task Collection

U2000
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Linear MS from the Function Tree. Step 2 In Protection Group, select the MSP group to be switched. In Slot Mapping Relation, select the working unit or protection unit, and then right-click. Step 3 Right-click and select the required switching mode.
The confirmation dialog box is displayed. Step 4 Click OK, and close the dialog box that is displayed.
NOTE
If the switching of a higher priority occurs in a channel, the switching of a lower priority will not occur in the channel.
----End
A.3.4 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 You must be an NM user with NE administrator authority or higher. The linear MSP must be configured.

U2000
Precautions
l l Stopping the ring MSP protocol causes failure of 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,
Issue 02 (2011-01-20)
A Task Collection
the services are interrupted until the working channel is restored to normal or the protocol is started.
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Linear MS from the Function Tree. Step 2 In Protection Group, select the MSP group for which the linear MSP protocol is to be stopped. Step 3 Click Start Protocol or Stop Protocol, and then close the prompt dialog box that is displayed. Step 4 Click Query > Query Protection Group, close the dialog box that is displayed, and check Protocol Status. ----End
A.3.5 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

U2000
The number of nodes on an MSP ring should not exceed 16.
Procedure
Step 1 In the NE Explorer, select the required NE from the Object Tree and choose Configuration > Ring MS from the Function Tree. Step 2 Click Create. A confirmation dialog box is displayed. Step 3 Click OK. The Create a Multiplex Section Ring dialog box is displayed. Step 4 Set parameters of the ring MSP protection group as planned.
A-60
Issue 02 (2011-01-20)
A Task Collection
Related References
B.3.3 Parameter Description: Ring MSP_Creation
A.3.6 Querying Ring MSP Status

This topic describes how to check the current status of a ring MSP protection group.
Prerequisite
l l You must be an NM user with NE administrator authority or higher. A ring MSP protection group has been configured.

U2000
A Task Collection
Procedure
Step 1 In the NE Explorer, select the required NE from the Object Tree and choose Configuration > Ring MS from the Function Tree. Step 2 Click Query. Step 3 Select Query Protection Group from the drop-down list. Then, close the dialog box that is displayed. In Protection Group, check basic information about the protection group. Step 4 Select the required protection group and click Query. Step 5 Select Query Switching Status from the drop-down list. Then, close the dialog box that is displayed. In Slot Mapping Relation, check the switching status of the protection group. ----End
Related References
B.3.4 Parameter Description: Ring MSP
A.3.7 Triggering Ring MSP Switching

This topic describes how to trigger external ring MSP switching.
Prerequisite
l l l You must be an NM user with NE administrator authority or higher. Ring MSP has been configured for a service. The ring MSP protocol has been enabled.

U2000
CAUTION
All switching operations except exercise switching may interrupt services.
Procedure
Step 1 In the NE Explorer, select the required NE from the Object Tree and choose Configuration > Ring MS from the Function Tree. Step 2 Select the required service, right-click the service, and select a switching mode from the dropdown list. Then, a confirmation dialog box is displayed. Step 3 Click Yes Then, close the dialog box that is displayed.
A Task Collection
Step 4 Click Query. Step 5 Select Query Switching Status from the drop-down list. Then, close the dialog box that is displayed. Step 6 Check whether the service is already switched to the protection channel. ----End
A.3.8 Starting/Stopping the Ring MSP Protocol

If you first stop the ring MSP protocol and then start it, the ring MSP protocol is restored to its initial state.
Prerequisite
l l You must be an NM user with NE administrator authority or higher. Ring MSP has been configured for a service.

U2000
Procedure
Step 1 In the NE Explorer, select the required NE from the Object Tree and choose Configuration > Ring MS from the Function Tree. Step 2 Stop the ring MSP protocol. 1. Select the required protection group and click Stop Protocol.
CAUTION
After the ring MSP protocol is stopped, the protection group fails. In addition, services are unavailable until the working channel is restored or the ring MSP protocol is restarted, if services have been switched to the protection channel. A confirmation dialog box is displayed. 2. 1. Click Yes Then, close the dialog box that is displayed. Select the required protection group. Click Start Protocol Then, close the dialog box that is displayed. Step 3 Start the ring MSP protocol.
----End
A.4 Managing TDM Services

The TDM services involve the SDH service and the PDH service. A.4.1 Creating the Cross-Connections of Point-to-Point Services
A Task Collection
In a cross-connection of point-to-point services, one service source corresponds to one service sink. A.4.2 Creating Cross-Connections of 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.4.3 Modifying the Priorities of E1 Services This section describes how to adjust the priorities of E1 services. A.4.4 Inserting TU_AIS On an SNCP ring that adopt the IF1 board and Hybrid IF boards, if an NE houses a Hybrid IF board and an IF1 board as its east and west IF interface boards, you need to enable the E1_AIS insertion function for the pass-through E1 services (that is, the services cross-connected to the IF1 board). A.4.5 Configuring the Automatic Switching of SNCP Services You can manually add certain alarms for the automatic switching of SNCP services. A.4.6 Deleting Cross-Connections When a service is not used, you can delete the cross-connections of this service to release the corresponding resources. A.4.7 Converting a Normal Service into an SNCP Service By converting a normal service into an SNCP service, you can convert the unidirectional crossconnections of a normal service into the unidirectional cross-connection in the receive direction of the SNCP service. A.4.8 Converting an SNCP Service to a Normal Service By converting an SNCP service to a normal service, you can convert the SNCP cross-connection in the receive direction into the unidirectional cross-connection of the normal service. A.4.9 Querying TDM Services You can learn about the TDM services that are configured for an NE by querying TDM services. A.4.10 Switching SNCP Services You can perform external switching on SNCP services by performing this operation. A.4.11 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.4.1 Creating the 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 You must be an NM user with NE operator authority or higher. The corresponding source and sink boards must be added on NE Panel.

U2000
A-64
Issue 02 (2011-01-20)
A Task Collection
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > SDH Service Configuration from the Function Tree. Step 2 Click Options to change the VC-12 timeslot numbering policy used by the cross-connection.
Step 3 Click Create. The Create SDH Service dialog box is displayed. Step 4 Configure the parameters of a new SDH service.
Related References
B.4.1 Parameter Description: SDH Service Configuration_Creation
A.4.2 Creating Cross-Connections of 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 You must be an NM user with NE operator authority or higher. The corresponding source and sink boards must be added on NE Panel.

U2000
A Task Collection
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > SDH Service Configuration from the Function Tree. Step 2 Click Options to change the VC-12 timeslot numbering policy used by the cross-connection.
Step 3 Click Create SNCP Service. The Create SNCP Service dialog box is displayed. Step 4 Configure the parameters of a new SNCP service.
Related References
B.4.2 Parameter Description: SDH Service Configuration_SNCP Service Creation
A.4.3 Modifying the Priorities of E1 Services

This section describes how to adjust the priorities of E1 services.
Prerequisite
l l l You must be an NM user with NE operator authority or higher. The corresponding source and sink boards must be added in the NE Panel. The E1 cross-connections must be created. The IF boards in the cross-connections must support the E1 priority function. The E1 priorities must be set already and need to be modified.

U2000
A Task Collection
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > SDH Service Configuration from the Function Tree. Step 2 Click Query. Step 3 Select an E1 service in Cross-Connection. Step 4 Right-click the E1 service and choose Expand from the shortcut menu. Step 5 If the number of E1 services configured on an IF board is smaller than Full E1 Capacity, select the required E1 service, right-click the service, and choose Modify from the short-cut menu. Then, change the E1 priority of each timeslot in the dialog box that is displayed..
NOTE
For an SNCP service, you need to modify E1 Priority of only the services that are transmitted to the working source and the protection source of the SNCP service.
Step 6 If the number of E1 services configured on an IF board is the same as Full E1 Capacity, do as follows to interchange the priority levels of two E1 services: 1. 2. 3. 4. Add one to Full E1 Capacity for both ends of the radio link. Change E1 Priority of the E1 service with a higher priority to Low. Change E1 Priority of the E1 service with a lower priority to High. Change Full E1 Capacity to the original values for both ends of the radio link.
NOTE
If Full E1 Capacity uses its maximum value, do as follows to interchange the priority levels of two services. 1. Delete either E1 service. 2. Change the priority of the other E1 service. 3. Add the E1 service that was deleted, setting its E1 Priority to the required value.
Step 7 Click Apply. Then, close the dialog box that is displayed. ----End
A.4.4 Inserting TU_AIS

On an SNCP ring that adopt the IF1 board and Hybrid IF boards, if an NE houses a Hybrid IF board and an IF1 board as its east and west IF interface boards, you need to enable the E1_AIS
A Task Collection
insertion function for the pass-through E1 services (that is, the services cross-connected to the IF1 board).
Prerequisite
l l You must be an NM user with NE operator authority or higher. The IFU2, IFX2, ISU2, or ISX2 board is added to NE Panel.

U2000
Procedure
Step 1 In the NE Explorer, select the IF board from the Object Tree and choose Alarm > Triggered Alarm Insertion from the Function Tree. Step 2 Select the E1 channels on the IF board that are involved in the SNCP and then set Insert TU_AIS to E1_AIS to Enable. Step 3 Click Apply. ----End
Related References
B.4.6 Parameter Description: TU_AIS Insertion B.4.6 Parameter Description: TU_AIS Insertion
A.4.5 Configuring the Automatic Switching of SNCP Services

You can manually add certain alarms for the automatic switching of SNCP services.
Prerequisite
l l You must be an NM user with NE operator authority or higher. The SNCP protection group must be configured.

U2000
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > SNCP Service Control from the Function Tree. Step 2 Select the SNCP protection group, and then right-click SD Initiation Condition to which the working service corresponds. Step 3 Set the initiation condition for the working service. Click OK.
A Task Collection
Step 4 Right-click SD Initiation Condition to which the protection service corresponds. Step 5 Set the initiation condition for the protection service. Click OK.
NOTE
It is recommended that you set SD Initiation Condition of the working service to be the same as SD Initiation Condition of the protection service.
Step 6 Click Apply, and then close the dialog box that is displayed. ----End
Related References
B.4.5 Parameter Description: SNCP Service Control
A.4.6 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 You must be an NM user with NE operator authority or higher. The cross-connections of the service must be configured and the service must not be used.

U2000
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > SDH Service Configuration from the Function Tree. Step 2 Query the related data. 1. Click Query. Then, a dialog box is displayed, indicating that this operation will update the service data saved on the NMS. 2. 1.
Issue 02 (2011-01-20)
Click OK. Then, close the dialog box that is displayed. Right-click the service and choose Deactivate from the shortcut menu.
Step 3 Deactivate the service.
A Task Collection
Then, a dialog box is displayed, querying whether you need to deactivate the selected service. 2. Click OK. Then, a dialog box is displayed, indicating that this operation will clear the corresponding service data on the NE side. 3. Click OK. Then, close the dialog box that is displayed. Step 4 Delete the service. 1. 2. Right-click the service and choose Delete from the shortcut menu. Then, a dialog box is displayed, querying whether you need to delete the selected service. Click OK. Then, close the dialog box that is displayed. Step 5 Click Query. The queried information should show that the cross-connection is already deleted. ----End
A.4.7 Converting a Normal Service into an SNCP Service

By converting a normal service into an SNCP service, you can convert the unidirectional crossconnections of a normal service into the unidirectional cross-connection in the receive direction of the SNCP service.
Prerequisite
l l You must be an NM user with NE operator authority or higher. The unidirectional cross-connection of the normal service must be configured and the source of the cross-connection must be a line board.

U2000
When this task is performed to convert a normal service into an SNCP service, the original services are not interrupted.
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > SDH Service Configuration from the Function Tree. Step 2 Optional: If a bidirectional SDH service is created, select this service in Cross-Connection. Right-click the selected service and choose Expand to Unidirectional from the shortcut menu. Step 3 Select the unidirectional service. Right-click the selected service and choose Convert to SNCP Service from the shortcut menu. Then, a dialog box is displayed, querying whether you need to perform this operation.Then, the Convert to SNCP Service dialog box is displayed. Step 4 Click OK. Then, the Create SNCP Service dialog box is displayed.
A Task Collection
Step 5 Set the parameters of the SNCP service.
Related References
B.4.3 Parameter Description: SDH Service Configuration_Converting Normal Services Into SNCP Services
A.4.8 Converting an SNCP Service to a Normal Service

By converting an SNCP service to a normal service, you can convert the SNCP cross-connection in the receive direction into the unidirectional cross-connection of the normal service.
Prerequisite
l l l You must be an NM user with NE operator authority or higher. The SNCP cross-connection in the receive direction must be configured. The current service must be transmitted on the working path.

U2000
When this task is performed to convert an SNCP service into a normal service, the original services are not interrupted.
Issue 02 (2011-01-20)
A-71
A Task Collection
Procedure
Step 1 Select the corresponding board from the Object Tree in the NE Explorer. Choose Configuration > SDH Service Configuration > Cross-Connection Configuration from the Function Tree. Step 2 In Auto-Created Cross-Connection, select the configured service. Right-click and choose Convert to Non-Protection Service from the shortcut menu. Then, a dialog box is displayed, querying whether you need to perform this operation. Step 3 Click OK. ----End
Follow-up Procedure
You also need to delete the unidirectional cross-connection between the service source and the working path or the unidirectional cross-connection between the service source 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.4.9 Querying TDM Services

You can learn about the TDM services that are configured for an NE by querying TDM services.
Prerequisite
l l You must be an NM user with NE administrator authority or higher. TDM services must be configured.

U2000
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > SDH Service Configuration from the Function Tree. Step 2 Click Query. Step 3 In the displayed dialog box for confirmation, click OK. Step 4 Close the displayed prompt dialog box. In Cross-Connection, query the TDM services. ----End
Related References
B.4.4 Parameter Description: SDH Service Configuration
A.4.10 Switching SNCP Services

You can perform external switching on SNCP services by performing this operation.
A Task Collection
Prerequisite

U2000
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > SNCP Service Control from the Function Tree. Step 2 Select the SNCP protection group for SNCP service switching. Step 3 Click Function. Select the required switching mode from the displayed menu. Step 4 In the displayed dialog box for confirmation, click OK. Step 5 The system displays a prompt dialog box, indicating that the operation is successful. Then, close the displayed prompt dialog box. Step 6 Choose Function > Query Switch Status to check whether the switching operation is successful. ----End
A.4.11 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

U2000
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > SNCP Service Control from the Function Tree. Step 2 Select the SNCP protection group whose service protection status needs to be queried. Step 3 Click Function > Query Switch Status, and then close the displayed prompt dialog box. ----End
Related References
A Task Collection
A.5 Managing Ports

Correct parameter settings of ports are the basis of configuring ports that transmit services. A.5.1 Setting the Parameters of SDH Ports The parameters of SDH ports are used to configure the loopback on the SDH interface board and the laser status. A.5.2 Setting the Parameters of PDH Ports The parameters of PDH ports are used to configure the tributary loopback, service load indication, and tributary retiming. A.5.3 Configuring Overhead Bytes Generally, the default overload bytes can meet the requirements of the device. In certain special application scenarios, however, such as device interconnection, you need to change the overload bytes according to the requirements of the interconnected device. A.5.4 Setting Smart E1 Port Parameters Smart E1 ports can be configured as CES E1 ports or ATM E1 ports. A.5.5 Setting Serial Port Parameters When some 64 kbit/s timeslots of an Smart E1 port are used for transmission of ATM services, these timeslots can be considered as a serial port. A.5.6 Setting the Parameters of Ethernet Ports The parameters of Ethernet ports include basic attributes, traffic control, Layer-2 attributes, Layer-3 attributes, and advanced attributes. A.5.7 Setting the General Attributes of the IF_ETH Port This topic describes how to set the general attributes of IF_ETH ports. The IF_ETH ports are the internal Ethernet ports on the IF board of the IP radio and they are used to access Native ETH services or packet services. A.5.8 Setting Parameters of IF Interfaces This topic describes how to set the parameters of IF interfaces, including IF attributes, ATPC attributes, and AM attributes. A.5.9 Setting the Parameters of ODU Ports This section describes how to configure the parameters of ODU ports, including the transmit frequency attribute, power attribute, ODU attribute, and advanced attributes.
A.5.1 Setting the Parameters of SDH Ports

The parameters of SDH ports are used to configure the loopback on the SDH interface board and the laser status.
Prerequisite
l l You must be an NM user with NE operator authority or higher. The corresponding board must be added on the NE Panel.

U2000
A Task Collection
Procedure
Step 1 Select the corresponding board from the Object Tree in the NE Explorer. Choose Configuration > SDH Interface from the Function Tree. Step 2 Select By Board/Port(Channel), and select Port or VC4 Channel from the list box. Step 3 Set the parameters of SDH ports.
1.
Choose Port from the drop-down list, and then configure the parameters of SDH ports. Click Apply. A dialog box is displayed for confirmation. Click OK. The dialog box is displayed again for confirmation. Click OK, and then close the dialog box that is displayed indicating the operation result.
2. 3.
Step 4 Set the parameters of VC-4 paths.
1. 2. 3.
Choose VC4 Channel from the drop-down list, and then configure the parameters of VC-4 paths. Click Apply, and then close the dialog box that is displayed indicating the operation result. Click OK.
----End
Related References
B.5.7.1 Parameter Description: SDH Interfaces
A.5.2 Setting the Parameters of PDH Ports

The parameters of PDH ports are used to configure the tributary loopback, service load indication, and tributary retiming.
Prerequisite

U2000
Issue 02 (2011-01-20)
A-75
A Task Collection
Procedure
Step 1 Select the corresponding board from the Object Tree in the NE Explorer. Choose Configuration > PDH Interface from the Function Tree. Step 2 Select By Board/Port(Channel). Step 3 Select Port from the list box. Step 4 Configure the parameters of PDH ports.
Step 5 Click Apply, and then close the dialog box that is displayed indicating the operation result. ----End
Related References
B.5.8.1 Parameter Description: PDH Interfaces
A.5.3 Configuring Overhead Bytes

Generally, the default overload bytes can meet the requirements of the device. In certain special application scenarios, however, such as device interconnection, you need to change the overload bytes according to the requirements of the interconnected device. A.5.3.1 Configuring RSOHs When the local or remote NE reports the J0_MM alarm, you need to configure the J0 byte in regenerator section overheads (RSOHs). A.5.3.2 Configuring VC-4 POHs When the HP_TIM, LP_TIM, or HP_SLM alarm is reported by the line board of the local or peer NE, you need to configure the J1 or C2 byte in VC-4 path overheads (POHs). A.5.3.3 Configuring VC-12 POHs When the E1 port board of the local or remote NE reports the LP_TIM or LP_TIM_VC12 alarm, you need to configure the signal flag in the J2 byte in VC-12 path overheads (POHs).
A.5.3.1 Configuring RSOHs

When the local or remote NE reports the J0_MM alarm, you need to configure the J0 byte in regenerator section overheads (RSOHs).
Prerequisite
Procedure
Step 1 Select an SDH interface board in the NE Explorer Choose Configuration > Overhead Management > Regenerator Section Overhead from the Function Tree. Step 2 Choose Display in Text Format or Display in Hexadecimal.
A Task Collection
Step 3 Configure the J0 byte. 1. 2. Double-click the parameter whose value needs to be changed. The Please input the overhead byte dialog box is displayed. Configure overhead bytes.
3.
Click OK.
Step 4 Click Apply. A dialog box is displayed for confirmation. Step 5 Click OK, and then close the dialog box that is displayed indicating the operation result. ----End
Related References
B.5.9.1 Parameter Description: Regenerator Section Overhead
A.5.3.2 Configuring VC-4 POHs

When the HP_TIM, LP_TIM, or HP_SLM alarm is reported by the line board of the local or peer NE, you need to configure the J1 or C2 byte in VC-4 path overheads (POHs).
Prerequisite
Issue 02 (2011-01-20)
A-77
A Task Collection
Procedure
Step 1 Select SDH interface board from the Object Tree in the NE Explorer. Choose Configuration > Overhead Management > VC4 Path Overhead from the Function Tree. Step 2 Choose Display in Text Format or Display in Hexadecimal. Step 3 Optional: Configure the J1 byte. 1. 2. 3. 4. 5. 6. Click the Trace Byte J1 tab. Double-click the parameter whose value needs to be changed. The Please Input Overhead Byte dialog box is displayed. Configure overhead bytes. Click OK. Click Apply. A dialog box is displayed for confirmation. Click OK, and then close the dialog box that is displayed indicating the operation result.
Step 4 Optional: Configure the C2 byte. 1. 2. 3. 4. Click the Signal Flag C2 tab. Configure the required parameters. Click Apply. A dialog box is displayed for confirmation. Click OK. Close the dialog box that is displayed indicating the operation result.
Step 5 Configure the termination mode of the VC-4 overhead. 1. 2. 3. 4. Click the Overhead Termination tab. Configure VC4 Overhead Termination. Click Apply. A dialog box is displayed for confirmation. Click OK, and then close the dialog box that is displayed indicating the operation result.
----End
Related References
B.5.9.2 Parameter Description: VC-4 POHs

When the E1 port board of the local or remote NE reports the LP_TIM or LP_TIM_VC12 alarm, you need to configure the signal flag in the J2 byte in VC-12 path overheads (POHs).
Prerequisite
l l
A-78
You must be an NM user with NE operator authority or higher. The corresponding board must be added on the NE Panel.
A Task Collection
Procedure
Step 1 Select the corresponding board from the Object Tree in the NE Explorer. Choose Configuration > Overhead Management > VC12 Path Overhead from the Function Tree. Step 2 Configure the J2 byte. 1. 2. 3. 4. Click the Trace Byte J2 tab. Choose Display in Text Format or Display in Hexadecimal. Double-click the parameter whose value needs to be changed. The Please input the overhead byte dialog box is displayed. Configure overhead bytes.
5. 6. 7.
Click OK. Click Apply. A dialog box is displayed for confirmation. Click OK, and then close the dialog box that is displayed.
----End
Related References
A.5.4 Setting Smart E1 Port Parameters

Smart E1 ports can be configured as CES E1 ports or ATM E1 ports. A.5.4.1 Setting Basic Attributes of Smart E1 Ports
A Task Collection
The basic attributes of Smart E1 ports involve parameters such as the port name, port mode, and encapsulation type. A.5.4.2 Setting Advanced Attributes of Smart E1 Ports The alarm attributes of Smart E1 ports define the parameters such as E1 frame type and loopback mode.
A.5.4.1 Setting Basic Attributes of Smart E1 Ports

The basic attributes of Smart E1 ports involve parameters such as the port name, port mode, and encapsulation type.
Prerequisite

U2000
Procedure
Step 1 In the NE Explorer, select the NE from the Object Tree and choose Configuration > Interface Management > PDH Interface from the Function Tree. Step 2 Click the General Attributes tab. Step 3 Select the required port and set the parameters.
A Task Collection
Related References
B.5.1.1 Parameter Description: PDH Ports_Basic Attributes
A.5.4.2 Setting Advanced Attributes of Smart E1 Ports

The alarm attributes of Smart E1 ports define the parameters such as E1 frame type and loopback mode.
Prerequisite

U2000
Procedure
Step 1 In the NE Explorer, select the NE from the Object Tree and choose Configuration > Interface Management > PDH Interface from the Function Tree. Step 2 Click the Advanced Attributes tab. Step 3 Select the required port and set the parameters for its advanced attributes.
Step 4 Click Apply. A confirmation dialog box is displayed. Step 5 Click Yes. Then, close the dialog box that is displayed. ----End
Related References
B.5.1.2 Parameter Description: PDH Ports_Advanced Attributes
A.5.5 Setting Serial Port Parameters

When some 64 kbit/s timeslots of an Smart E1 port are used for transmission of ATM services, these timeslots can be considered as a serial port. A.5.5.1 Creating Serial Ports When creating a serial port, you can set the 64 kbit/s timeslots to be bound with the serial port. A.5.5.2 Setting Basic Attributes of Serial Ports The basic attributes of serial ports involve the parameters such as port mode and encapsulation type.
A Task Collection
A.5.5.1 Creating Serial Ports

When creating a serial port, you can set the 64 kbit/s timeslots to be bound with the serial port.
Prerequisite
l l You must be an NM user with NE administrator authority or higher. The ports that travel services are set to Layer 1.

U2000
Procedure
Step 1 In the NE Explorer, select the required NE from the Object Tree and choose Configuration > Interface Management > Serial Port from the Function Tree. Step 2 Click the General Attributes tab. Step 3 Click New. The New Serial Interface dialog box is displayed. Step 4 Set the parameters for the serial port according to the planning information.
Related References
B.5.3.2 Parameter Description: Serial Port_Creation of Serial Ports

The basic attributes of serial ports involve the parameters such as port mode and encapsulation type.
Prerequisite
l l
A-82
You must be an NM user with NE administrator authority or higher. Serial ports are added.
A Task Collection

U2000
Procedure
Step 1 In the NE Explorer, select the required NE from the Object Tree and choose Configuration > Interface Management > Serial Port from the Function Tree. Step 2 Click the General Attributes tab. Step 3 Select the required port and set the parameters for the serial port according to the planning information.
Related References
B.5.3.1 Parameter Description: Serial Port_Basic Attributes
A.5.6 Setting the Parameters of Ethernet Ports

The parameters of Ethernet ports include basic attributes, traffic control, Layer-2 attributes, Layer-3 attributes, and advanced attributes. A.5.6.1 Setting the General Attributes of Ethernet Ports The general attributes of Ethernet ports define the physical-layer information, such as the interface mode, encapsulation type, and maximum frame length. A.5.6.2 Configuring the Traffic Control of Ethernet Ports After the traffic control is enabled, the Ethernet port sends the pause frame to notify the peer end of stop sending Ethernet packets for a period if the link is congested, thus eliminating link congestion. A.5.6.3 Setting the Layer 2 Attributes of Ethernet Ports The L2 attributes of Ethernet ports define the link-layer information. A.5.6.4 Setting Layer 3 Attributes of Ethernet Ports The Layer 3 attributes of Ethernet ports define the relevant information used for carrying MPLS tunnels, such as MPLS tunnel statuses and Ethernet port IP addresses. A.5.6.5 Setting the Advanced Attributes of Ethernet Ports This topic describes how to set the advanced attributes of Ethernet ports.
A.5.6.1 Setting the General Attributes of Ethernet Ports

The general attributes of Ethernet ports define the physical-layer information, such as the interface mode, encapsulation type, and maximum frame length.
A Task Collection
Prerequisite
l l You must be an NM user with NE operator authority or higher. The Ethernet board must be added on the NE Panel.

U2000
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Interface Management > Ethernet Interface from the Function Tree. Step 2 Click the General Attributes tab. Step 3 Configure the general attributes of Ethernet ports.
Related References
B.5.2.1 Parameter Description: Ethernet Interface_Basic Attributes
A.5.6.2 Configuring the Traffic Control of Ethernet Ports

After the traffic control is enabled, the Ethernet port sends the pause frame to notify the peer end of stop sending Ethernet packets for a period if the link is congested, thus eliminating link congestion.
Prerequisite

U2000
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Interface Management > Ethernet Interface from the Function Tree. Step 2 Click the Flow Control tab. Step 3 Configure the traffic control of Ethernet ports.
A Task Collection
Related References
B.5.2.2 Parameter Description: Ethernet Interface_Flow Control
A.5.6.3 Setting the Layer 2 Attributes of Ethernet Ports

The L2 attributes of Ethernet ports define the link-layer information.
Prerequisite
l l l You must be an NM user with NE operator authority or higher. The Ethernet board must be added on the NE Panel. Port Mode of Ethernet ports are set to Layer 2.

U2000
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Interface Management > Ethernet Interface from the Function Tree. Step 2 Click the Layer 2 Attributes tab. Step 3 Configure the L2 attributes of Ethernet ports.
A Task Collection
Related References
B.5.2.3 Parameter Description: Ethernet Interface_Layer 2 Attributes
A.5.6.4 Setting Layer 3 Attributes of Ethernet Ports

The Layer 3 attributes of Ethernet ports define the relevant information used for carrying MPLS tunnels, such as MPLS tunnel statuses and Ethernet port IP addresses.
Prerequisite
l l You must be an NM user with NE administrator authority or higher. Port Mode of Ethernet ports are set to Layer 3.

U2000
Procedure
Step 1 In the NE Explorer, select the NE from the Object Tree and choose Configuration > Interface Management > Ethernet Interface from the Function Tree. Step 2 Click the Layer 3 Attributes tab.
Step 3 Set the parameters for Ethernet ports according to the planning information. Step 4 Click Apply. The Warning dialog box is displayed. Step 5 Click Yes. The Operation Result dialog box is displayed. Step 6 Click Close. ----End
Related References
B.5.2.4 Parameter Description: Ethernet Port_Layer 3 Attributes

This topic describes how to set the advanced attributes of Ethernet ports.
A Task Collection
Prerequisite

U2000
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Interface Management > Ethernet Interface from the Function Tree. Step 2 Click the Advanced Attributes tab. Step 3 Configure the advanced attributes of Ethernet ports.
Related References
B.5.2.5 Parameter Description: Ethernet Interface_Advanced Attributes
A.5.7 Setting the General Attributes of the IF_ETH Port

This topic describes how to set the general attributes of IF_ETH ports. The IF_ETH ports are the internal Ethernet ports on the IF board of the IP radio and they are used to access Native ETH services or packet services. A.5.7.1 Setting the General Attributes of the IF_ETH Port The general attributes of the IF_ETH port specify the basic information, including the port mode and encapsulation mode. A.5.7.2 Setting the Layer 2 Attributes of the IF_ETH Port The Layer 2 attributes of the IF_ETH port specify the relevant information about the link layer, including the tag attribute and QinQ type domain. A.5.7.3 Setting Layer 3 Attributes of IF_ETH Ports The Layer 3 attributes of IF_ETH ports define the relevant information used for carrying MPLS tunnels, such as MPLS tunnel statuses and IF_ETH port IP addresses. A.5.7.4 Setting the Advanced Attributes of the IF_ETH Port This topic describes how to set the advanced attributes of IF_ETH ports.

The general attributes of the IF_ETH port specify the basic information, including the port mode and encapsulation mode.
A Task Collection
Prerequisite
l l You must be an NM user with NE operator authority or higher. The corresponding IF board must be added to NE Panel.

U2000
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Interface Management > Microwave Interface from the Function Tree. Step 2 Click the General Attributes tab. Step 3 Set the general attributes of the IF_ETH port.
Step 4 Click Apply.Then, close the dialog box that is displayed. ----End
Related References
B.5.4.1 Parameter Description: Microwave Interface_Basic Attributes
A.5.7.2 Setting the Layer 2 Attributes of the IF_ETH Port

The Layer 2 attributes of the IF_ETH port specify the relevant information about the link layer, including the tag attribute and QinQ type domain.
Prerequisite
l l l You must be an NM user with NE operator authority or higher. The corresponding IF board must be added to NE Panel. The parameter Port Mode is set to Layer 2.

U2000
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Interface Management > Microwave Interface from the Function Tree. Step 2 Click the Layer 2 Attributes tab. Step 3 Setting the Layer 2 attributes of the IF_ETH port.
A-88
Issue 02 (2011-01-20)
A Task Collection
Related References
B.5.4.2 Parameter Description: Microwave Interface_Layer 2 Attributes
A.5.7.3 Setting Layer 3 Attributes of IF_ETH Ports

The Layer 3 attributes of IF_ETH ports define the relevant information used for carrying MPLS tunnels, such as MPLS tunnel statuses and IF_ETH port IP addresses.
Prerequisite
l l You must be an NM user with NE administrator authority or higher. Port Mode of the ports on IF boards are set to Layer 3.

U2000
Procedure
Step 1 In the NE Explorer, select the required NE from the Object Tree and choose Configuration > Interface Management > Microwave Interface from the Function Tree. Step 2 Click the Layer 3 Attributes tab. Step 3 Set parameters for Layer 3 attributes of the ports on IF boards according to the planning information.
Related References

This topic describes how to set the advanced attributes of IF_ETH ports.
Prerequisite
l l You must be an NM user with NE operator authority or higher. The corresponding IF board must be added to NE Panel.

U2000
A Task Collection
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Interface Management > Microwave Interface from the Function Tree. Step 2 Click the Advanced Attributes tab. Step 3 Setting the advanced attributes of the IF_ETH port.
Related References
B.5.4.4 Parameter Description: Microwave Interface_Advanced Attributes
A.5.8 Setting Parameters of IF Interfaces

This topic describes how to set the parameters of IF interfaces, including IF attributes, ATPC attributes, and AM attributes. A.5.8.1 Setting IF Attributes In the case of different IF boards, different parameters need to be set. A.5.8.2 Configuring the ATPC Attributes To configure the ATPC function, set the ATPC attributes of the IF board. A.5.8.3 Setting Advanced AM Attributes By performing this operation, you can query and adjust the E1 capacity in each modulation scheme. A.5.8.4 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.8.5 Querying the ATPC Adjustment Records By querying the ATPC adjustment records, you can be familiar with the running status of the ATPC function. A.5.8.6 Modifying the Hybrid/AM Attributes Any modifications to Hybrid/AM attributes must ensure that the Hybrid/AM attribute settings are the same for both ends of the adjusted radio link. Otherwise, the modifications do not take effect or services are interrupted.
A.5.8.1 Setting IF Attributes

In the case of different IF boards, different parameters need to be set.
Prerequisite
l l
A-90
You must be an NM user with NE operator authority or higher. The corresponding IF board must be added on the NE Panel.
A Task Collection

U2000
Context
l l l The IF1 board is used for TDM microwave. The IFU2 and ISU2 boards are general-purpose IF boards. The IFX2 and ISX2 boards are general-purpose XPIC IF boards.
Procedure
Step 1 Select the corresponding board from the Object Tree in the NE Explorer. Choose Configuration > IF Interface from the Function Tree. Step 2 Click the IF Attributes tab. Step 3 Configure the parameters of general attributes. l In the case of the IF1:
l In the case of the IFU2:
l In the case of the IFX2:
l For the ISU2 board:
l For the ISX2 board:
Step 4 Configure the parameters of Hybrid/AM attributes for different IF services. l For the IFU2 and IFX2 boards:
l For the ISU2 and ISX2 boards:
Related References
B.5.5.1 Parameter Description: IF Interface_IF Attribute
A Task Collection

To configure the ATPC function, set the ATPC attributes of the IF board.
Prerequisite
l l You must be an NM user with NE operator authority or higher. The corresponding IF board must be added on the NE Panel.
Precautions
l l For the IF boards that are configured with 1+1 protection, configure only the ATPC attributes of the main IF board. The following procedure describes the configuration of ATPC parameters in the IF interface configuration dialog box of the IF board. You can also configure ATPC parameters in the following configuration dialog boxes: Create an XPIC working group

U2000
Procedure
Step 1 Select the corresponding board from the Object Tree in the NE Explorer. Choose Configuration > IF Interface from the Function Tree. Step 2 Click the ATPC Attributes tab. Step 3 Configure the parameters of ATPC attributes.
Related References
B.5.5.2 Parameter Description: IF Interface_ATPC Attribute

By performing this operation, you can query and adjust the E1 capacity in each modulation scheme.
Prerequisite
l l l
A-92
You must be an NM user with NE operator authority or higher. The corresponding IF boards must be added in the NE Panel. The E1 priority function must be enabled.
A Task Collection

U2000
l l The OptiX RTN 980 supports the configuration of E1 priorities. The IF boards that support this function are IFU2, IFX2, ISU2, and ISX2. For the ISU2 and ISX2 boards, only the Integrated IP radio that transmits Native E1 services supports the configuration of E1 priorities.
Procedure
Step 1 In the NE Explorer, select the IF board, and then choose Configuration > IF Interface from the Function Tree. Step 2 Click the AM Advanced Attributes tab. Step 3 Set each parameter for the advanced AM attributes.
Related References
B.5.5.3 Parameter Description: Hybrid_AM Configuration_Advanced Attributes
A.5.8.4 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
l l You must be an NM user with NE operator authority or higher. The corresponding IF boards must be added in the NE Panel.

U2000
Issue 02 (2011-01-20)
A-93
A Task Collection
Procedure
Step 1 Select the corresponding board from the Object Tree in the NE Explorer. Choose Configuration > IF Interface from the Function Tree. Step 2 Click the IF Attributes tab. Step 3 Click Query. Step 4 Query the AM information in Hybrid/AM Configuration. ----End
Related References
A.5.8.5 Querying the ATPC Adjustment Records

By querying the ATPC adjustment records, you can be familiar with the running status of the ATPC function.
Prerequisite
l l You must be an NM user with NE operator authority or higher. The corresponding IF board must be added.

U2000
Procedure
Step 1 Select the corresponding board from the Object Tree in the NE Explorer. Choose Configuration > ATPC Adjustment Records from the Function Tree. Step 2 Click Query to query the running information of the ATPC function. ----End
Related References
B.5.5.4 Parameter Description: ATPC Adjustment Records
A.5.8.6 Modifying the Hybrid/AM Attributes

Any modifications to Hybrid/AM attributes must ensure that the Hybrid/AM attribute settings are the same for both ends of the adjusted radio link. Otherwise, the modifications do not take effect or services are interrupted.
Prerequisite
l l
A-94
You must be an NM user with NE operator authority or higher. The corresponding IF boards have been added in the NE Panel.
A Task Collection

U2000
Procedure
Step 1 Select the corresponding board from the Object Tree in the NE Explorer. Choose Configuration > IF Interface from the Function Tree. Step 2 Click the IF Attributes tab. Step 3 Optional: Change the channel bandwidth. 1. 2. Set IF Channel Bandwidth to its planned value. Click Apply.
Step 4 Optional: When the AM function is disabled, adjust the modulation mode. 1. 2. Set Manually Specified Modulation Mode to its planned value. Click Apply.
Step 5 Disable the AM function. 1. 2. Set AM Enable Status to Disabled and set Manually Specified Modulation Mode to its planned value. Click Apply.
Step 6 Optional: Enable the AM function. 1. If the planned Modulation Mode of the Guarantee AM Capacity is lower than Manually Specified Modulation Mode, perform Step 4 and then change Manually Specified Modulation Modeto the planned Modulation Mode of the Guarantee AM Capacity. Set AM Enable Status to Enabled, and set Modulation Mode of the Guarantee AM Capacity and Modulation Mode of the Full AM Capacity to their planned values. Click Apply.
2. 3.
Step 7 Optional: When the AM function is enabled, adjust the modulation mode. If... You need to lower Modulation Mode of the Guarantee AM Capacity Then... 1. Perform Step 5 to disable the AM function, and change Manually Specified Modulation Mode to the lowered Modulation Mode of the Guarantee AM Capacity. 2. Perform Step 6 to enable the AM function. In other cases 1. Set Modulation Mode of the Guarantee AM Capacity and Modulation Mode of the Full AM Capacity to their planned values. 2. Click Apply. Step 8 Optional: Change the number of high-priority E1 services (namely, Guarantee E1 Capacity) in a radio link.
A Task Collection
If...
Then...
You need to reduce the number of high- 1. Perform A.4.6 Deleting Cross-Connections priority E1 services to delete unnecessary E1 services. 2. Decrease Guarantee E1 Capacity. 3. Click Apply. You need to increase the number of high-priority E1 services 1. Increase Guarantee E1 Capacity. 2. If Enable E1 Priority is Enabled, increase Full E1 Capacity accordingly. 3. Click Apply. 4. Perform A.4.1 Creating the CrossConnections of Point-to-Point Services or A. 4.2 Creating Cross-Connections of SNCP Services to add required E1 services.
NOTE l Full E1 Capacity is the total number of highpriority E1 services and low-priority E1 services. l Adding high-priority E1 services does not affect original E1 services.
Step 9 Optional: Change the number of low-priority E1 services (namely, Guarantee E1 Capacity) in a radio link. If... Then...
You need to reduce the number of low- 1. Perform A.4.6 Deleting Cross-Connections priority E1 services to delete unnecessary E1 services. 2. Decrease Full E1 Capacity. 3. Click Apply. You need to increase the number of low- 1. If Enable E1 Priority is Disabled, change priority E1 services Enable E1 Priority to Enabled. 2. Increase Full E1 Capacity. 3. Click Apply. 4. Perform A.4.1 Creating the CrossConnections of Point-to-Point Services or A. 4.2 Creating Cross-Connections of SNCP Services to add required E1 services. l Full E1 Capacity is the total number of highpriority E1 services and low-priority E1 services. l Adding low-priority E1 services does not affect original E1 services. ----End
Related References
A Task Collection
A.5.9 Setting the Parameters of ODU Ports

This section describes how to configure the parameters of ODU ports, including the transmit frequency attribute, power attribute, ODU attribute, and advanced attributes. A.5.9.1 Setting the Transmit Frequency Attribute of the ODU The transmit frequency attribute of the ODU is used to configure the transmit frequency of the ODU and T/R spacing. A.5.9.2 Querying the ODU Attribute The ODU attribute is used to query the information about the ODU. A.5.9.3 Setting the Power Attributes of the ODU The power attribute of the ODU is used to configure the transmit power and receive power of the ODU. A.5.9.4 Setting the Advanced Attributes of the ODU The advanced attributes of the ODU are used to configure the transmit status of the ODU. A.5.9.5 Setting the State of an ODU Transmitter The state of an ODU transmitter can be mute or unmute. When the ODU transmitter is in the unmute state, the ODU transmits and receives microwave signals normally. When the ODU transmitter is in the mute state, the ODU transmitter does not work, but the ODU can receive microwave signals. A.5.9.6 Querying the History Transmit Power and Receive Power Querying the change trend of the history transmit power and receive power can provide reference for radio link troubleshooting.
A.5.9.1 Setting the Transmit Frequency Attribute of the ODU

The transmit frequency attribute of the ODU is used to configure the transmit frequency of the ODU and T/R spacing.
Prerequisite

U2000
Procedure
Step 1 Select the ODU from the Object Tree in the NE Explorer. Choose Configuration > ODU Interface from the Function Tree. Step 2 Click the Radio Frequency Attributes tab. Step 3 Configure Transmit Frequency(MHz) and T/R Spacing(MHz) of the ODU.
Issue 02 (2011-01-20)
A-97
A Task Collection
Related References
B.5.6.1 Parameter Description: ODU Interface_Radio Frequency Attribute
A.5.9.2 Querying the ODU Attribute

The ODU attribute is used to query the information about the ODU.
Prerequisite

U2000
Procedure
Step 1 Select the corresponding board from the Object Tree in the NE Explorer. Choose Configuration > ODU Interface from the Function Tree. Step 2 Click the Equipment Information tab. Step 3 Click Query to obtain the information about the ODU.
----End
Related References
B.5.6.3 Parameter Description: ODU Interface_Equipment Information

The power attribute of the ODU is used to configure the transmit power and receive power of the ODU.
Prerequisite
l l l You must be an NM user with NE operator authority or higher. The related IF board must be added. The corresponding board must be added on the NE Panel.

U2000
A Task Collection
Procedure
Step 1 Select the ODU from the Object Tree in the NE Explorer. Choose Configuration > ODU Interface from the Function Tree. Step 2 Click the Power Attributes tab. Step 3 Configure the power attribute parameters of the ODU.
Related References
B.5.6.2 Parameter Description: ODU Interface_Power Attributes
A.5.9.4 Setting the Advanced Attributes of the ODU

The advanced attributes of the ODU are used to configure the transmit status of the ODU.
Prerequisite

U2000
Procedure
Step 1 Select the ODU from the Object Tree in the NE Explorer. Choose Configuration > ODU Interface from the Function Tree. Step 2 Click the Advanced Attributes tab. Step 3 Configure the parameters of the ODU, such as Configure Transmission Status.
Related References
B.5.6.4 Parameter Description: ODU Interface_Advanced Attributes
A.5.9.5 Setting the State of an ODU Transmitter

The state of an ODU transmitter can be mute or unmute. When the ODU transmitter is in the unmute state, the ODU transmits and receives microwave signals normally. When the ODU
A Task Collection
transmitter is in the mute state, the ODU transmitter does not work, but the ODU can receive microwave signals.
Prerequisite
l l You must be an NM user with NE operator authority or higher. The corresponding IF boards and the ODUs connected to the IF boards must be added to the NE Panel.

U2000
Procedure
Step 1 Select the ODU from the Object Tree in the NE Explorer. Choose Configuration > ODU Interface from the Function Tree. Step 2 Click the Advanced Attributes tab. Step 3 Set Configure Transmission Status for the ODU.
A.5.9.6 Querying the History Transmit Power and Receive Power

Querying the change trend of the history transmit power and receive power can provide reference for radio link troubleshooting.
Prerequisite
l l You must be an NM user with NE operator authority or higher. The corresponding IF boards and the ODUs connected to the IF boards must be added to the NE Panel.

U2000
Procedure
Step 1 Select the ODU from the Object Tree in the NE Explorer. Choose Configuration > Performance Graph Analyse from the Function Tree. Step 2 Specify the start time and end time of a specific time span.
NOTE
The time span starts from the last routine maintenance time to the current time.
A-100
Issue 02 (2011-01-20)
A Task Collection
Step 3 Set Monitoring Period and Power. Step 4 Click Draw. The history transmit and receive power curve of the ODU in the specified time span is displayed. ----End
A.6 Configuring Ethernet Services and Features on the Packet Plane

Configurations of Ethernet services and features on the packet plane include Ethernet port configuration, protection configuration, service configuration, protocol configuration, and OAM configuration. A.6.1 Managing the ERPS The Ethernet ring protection switching (ERPS) on the FE/GE ring or integrated IP radio ring can be configured to protect the Ethernet service. A.6.2 Managing the LAG Link aggregation allows one or multiple links that are attached to the same equipment to be aggregated together to form a LAG. The aggregated links can be considered as a single logical link by the MAC address. In this manner, the bandwidth is increased and the availability of the links is improved. A.6.3 Configure the Ethernet Service The Ethernet service is classified into two types, namely, E-Line service and E-LAN service. A.6.4 Managing the MAC Address Table The MAC address table is the core of the E-LAN service. The OptiX RTN 980 provides various functions for managing the MAC address table. A.6.5 Setting the Mode for Processing an Unknown Frame of the E-LAN Service An unknown frame is a unicast frame whose destination MAC address is not listed in the MAC address table or a multicast frame whose destination MAC address is not listed in the multicast group. By default, the NE broadcasts the unknown frame. By setting the mode for processing an unknown frame of the E-LAN service, you can change the processing mode so that unknown frame can be discarded. A.6.6 Managing the MSTP The OptiX RTN 980 supports only the MSTP that generates the CIST. A.6.7 Managing the QoS By managing the QoS, you can provide the services of different levels for different service types. A.6.8 Using the IEEE 802.1ag OAM By using the 802.1ag OAM, you can maintain Ethernet services in an end-to-end manner. A.6.9 Using the IEEE 802.3ah OAM By using the IEEE 802.1ag OAM, you can maintain the point-to-point Ethernet links. A.6.10 LPT Configuration When you use LPT function, you need to configure the relationship between LPT ports and the related information of LPT ports.
Issue 02 (2011-01-20)
A-101
A Task Collection
A.6.1 Managing the ERPS

The Ethernet ring protection switching (ERPS) on the FE/GE ring or integrated IP radio ring can be configured to protect the Ethernet service. A.6.1.1 Creating Ethernet Ring Protection Instances The Ethernet ring protection switching (ERPS) protection is configured through creation of Ethernet ring protection instances. A.6.1.2 Setting the Parameters of Ethernet Ring Protocol The parameters to be set include the hold-off time, WTR time, and guard time. A.6.1.3 Querying the Status of the Ethernet Ring Protocol By using this operation, you can know the current status of the Ethernet ring protection switching (ERPS).
A.6.1.1 Creating Ethernet Ring Protection Instances

The Ethernet ring protection switching (ERPS) protection is configured through creation of Ethernet ring protection instances.
Prerequisite
l l You must be an NM user with NE operator authority or higher. The Ethernet boards or hybrid IF boards must be added to the NE Panel.

U2000
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Ethernet Protection > ERPS Management. 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
Related References
B.6.2.1 Parameter Description: ERPS Management_Creation
A.6.1.2 Setting the Parameters of Ethernet Ring Protocol

The parameters to be set include the hold-off time, WTR time, and guard time.
Prerequisite
l l You must be an NM user with NE operator authority or higher. The protection instance of the ERPS must be created.

U2000
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Ethernet Protection > ERPS Management from the Function Tree. Step 2 Optional: Double-click Control VLAN, and then modify the VLAN ID.
Step 3 Optional: Set the parameters of Ethernet ring protocol.
Related References
B.6.2.2 Parameter Description: ERPS Management
A.6.1.3 Querying the Status of the Ethernet Ring Protocol

By using this operation, you can know the current status of the Ethernet ring protection switching (ERPS).
Prerequisite
A Task Collection

U2000
Procedure
Step 1 Select the NE 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 protocol. ----End
Related References
A.6.2 Managing the LAG

Link aggregation allows one or multiple links that are attached to the same equipment to be aggregated together to form a LAG. The aggregated links can be considered as a single logical link by the MAC address. In this manner, the bandwidth is increased and the availability of the links is improved. A.6.2.1 Creating a LAG Between two NEs, if the bandwidth and availability of the Ethernet links need to be improved, the new LAG must be created. A.6.2.2 Setting Parameters for LAGs The parameters for a LAG include port priorities. In a static LAG, traffic is always carried by a port with a higher priority. A.6.2.3 Querying the Protocol Information of the LAG Through this operation, you can learn about the running information of the LACP used for the LAG.
A.6.2.1 Creating a LAG

Between two NEs, if the bandwidth and availability of the Ethernet links need to be improved, the new LAG must be created.
Prerequisite
l l You must be an NM user with NE operator authority or higher. The board on which the LAG port to be created must be added to the NE Panel.

U2000
A-104
Issue 02 (2011-01-20)
A Task Collection
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Interface Management > Link Aggregation Group Management from the Function Tree. Step 2 Click the Link Aggregation Group Management tab. Step 3 Click New. The system displays the Create Link Aggregation Group dialog box. Step 4 Set the attributes of the LAG in Attribute Settings.
Step 5 Set the LAG port in Port Settings. 1. 2. 3. Set Main Board and Main Port. In Available Slave Ports, select Board of the slave port. In Port, select the slave port, and then click
TIP
Hold on the Ctrl key or the Shift key on the keyboard to select multiple ports.
Issue 02 (2011-01-20)
A-105
A Task Collection
4.
Click OK. A dialog box is displayed for confirmation. Click OK. Then, a dialog box is displayed, indicating that the operation is successful. Close this dialog box.
----End
Related References
B.6.2.8 Parameter Description: Ethernet Link Aggregation Management_LAG Creation
A.6.2.2 Setting Parameters for LAGs

The parameters for a LAG include port priorities. In a static LAG, traffic is always carried by a port with a higher priority.
Prerequisite
l l You must be an NM user with NE operator authority or higher. The board on which the LAG to be created must be added to NE Panel.

U2000
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Interface Management > Link Aggregation Group Management from the Function Tree. Step 2 Click the Port Priority tab. Step 3 Set the port priority. Step 4 Click Apply, and then close the dialog box that is displayed. ----End
A Task Collection
Related References
B.6.2.9 Parameter Description: Ethernet Link Aggregation_Link Aggregation
A.6.2.3 Querying the Protocol Information of the LAG

Through this operation, you can learn about the running information of the LACP used for the LAG.
Prerequisite
l l You must be an NM user with NE operator authority or higher. The LAG must be created.

U2000
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Interface Management > Link Aggregation Group Management from the Function Tree. Step 2 Click the Link Aggregation Group Management tab. Step 3 Click Query. A dialog box is displayed, indicating that the operation is successful. Then, close this dialog box. Step 4 In the Main Interface, select the LAG to be queried. Step 5 Query port status of the main and slave ports.
NOTE
The system displays the information about the slave port in the lower part of the Main Interface.
Step 6 Right-click on the selected LAG and choose the specific information about the LAG from the shortcut menu.
Step 7 Click the Port Priority tab. Step 8 Click Query. A dialog box is displayed, indicating that the operation is successful. Close this dialog box. Step 9 Query the port priority of the LAG. ----End
A Task Collection
A.6.3 Configure the Ethernet Service

The Ethernet service is classified into two types, namely, E-Line service and E-LAN service. A.6.3.1 Configuring the QinQ Link Configuring the QinQ link is the prerequisite for configuring QinQ private line services. A.6.3.2 Configuring UNI-UNI E-Line Services This topic describes how to create an E-Line service that is transparently transmitted end to end or is transmitted based on VLANs. A.6.3.3 Configuring NNI-NNI E-Line Services This topic describes how to configure S-VLAN-based E-Line services. A.6.3.4 Configuring UNI-NNI E-Line Services (Carried by QinQ Links) This topic describes how to configure E-Line services carried by QinQ links. A.6.3.5 Configuring UNI-NNI E-Line Services (Carried by PWs) This section describes how to configure E-Line services carried by PWs. A.6.3.6 Creating a VLAN Forwarding Table Item After the corresponding VLAN forwarding table item is created, the VLAN IDs of the service packets can be switched at the source or sink end of the E-Line service. A.6.3.7 Configuring TPID for a Request VLAN When a request VLAN is used for E-Line services transmitted by PWs, the TPID in the request VLAN is defaulted to be 0x88A8. The TPID can be set for an NE. A.6.3.8 Configuring IEEE 802.1d Bridge-Based E-LAN Services The E-LAN service refers to the dynamic transmission of the Ethernet service in the multipointto-multipoint mode through MAC address. A.6.3.9 Configuring IEEE 802.1q Bridge-Based E-LAN Services An IEEE 802.1q bridge is a virtual bridge (VB), which can be divided by VLAN into several switching domains. A.6.3.10 Configuring IEEE 802.1ad Bridge-Based E-LAN Services An IEEE 802.1ad bridge is a provider bridge (PB), which can be divided by SVLAN into several switching domains. A.6.3.11 Changing Logical Ports Connected to a VB This section describes how to change the logical ports connected to a VB and the attributes of the ports. A.6.3.12 Deleting an E-Line Service When an E-Line service is not used, you need to delete the E-line service to release the corresponding resources. A.6.3.13 Deleting E-LAN Services When an E-LAN service is not required, you can delete this E-LAN service to release corresponding Ethernet resources.
A.6.3.1 Configuring the QinQ Link

Configuring the QinQ link is the prerequisite for configuring QinQ private line services.
A-108
Issue 02 (2011-01-20)
A Task Collection
Prerequisite
l l l You must be an NM user with NE operator authority or higher. The Ethernet board must be added on the NE Panel. On associated ports, the Encapsulation Type is set to QinQ.

U2000
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Ethernet Service Management > QinQ Link from the Function Tree. Step 2 Click New. Step 3 Configure the basic attributes of the QinQ link.
Related References
B.6.1.6 Parameter Description: QinQ Link_Creation
A.6.3.2 Configuring UNI-UNI E-Line Services

This topic describes how to create an E-Line service that is transparently transmitted end to end or is transmitted based on VLANs.
Prerequisite
l l l You must be an NM user with NE operator authority or higher. The Ethernet board must be added on the NE Panel. The parameter Port Mode is set to Layer 2 for the UNI port that carries the E-Line service.

U2000
Issue 02 (2011-01-20)
A-109
A Task Collection
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Ethernet Service Management > E-Line Service from the Function Tree. Step 2 Click New. The New E-Line Service dialog box is displayed. Step 3 Set Direction to UNI-UNI. Step 4 Configure the attributes of the E-Line service.
Related References
B.6.1.1 Parameter Description: E-Line Service_Creation
A.6.3.3 Configuring NNI-NNI E-Line Services

This topic describes how to configure S-VLAN-based E-Line services.
Prerequisite
l l l You must be an NM user with NE operator authority or higher. Ethernet boards have been added on the NE Panel. For ports that carry services, Port Mode has been set to Layer 2 and Encapsulation Type has been set to QinQ.

U2000
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Ethernet Service Management > E-Line Service from the Function Tree.
A Task Collection
Step 2 Click New. The New E-Line Service dialog box is displayed. Step 3 Set Direction to NNI-NNI. Step 4 Set relevant attributes of the E-Line service.
Related References
A.6.3.4 Configuring UNI-NNI E-Line Services (Carried by QinQ Links)

This topic describes how to configure E-Line services carried by QinQ links.
Prerequisite
l l l You must be an NM user with NE operator authority or higher. Ethernet boards have been added on the NE Panel. For UNI and NNI ports that carry services, Port Mode has been set to Layer 2. For NNI ports, Encapsulation Type has been set to QinQ.

U2000
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Ethernet Service Management > E-Line Service from the Function Tree. Step 2 Click New. The New E-Line Service dialog box is displayed. Step 3 Set Direction to UNI-NNI and set Bearer Type to QinQ Link.
A Task Collection
Step 4 Set relevant attributes of the E-Line service.

NOTE
You can configure QinQ links during service creation or before service creation by choosing Configuration > Ethernet Service Management > QinQ Link.
Related References
A.6.3.5 Configuring UNI-NNI E-Line Services (Carried by PWs)

This section describes how to configure E-Line services carried by PWs.
Prerequisite
l l l l You must be an NM user with NE operator authority or higher. The Ethernet board is added on the NE Panel. Port Mode is set to Layer 2 for the UNI ports that carry services. The tunnel that carries PWs is configured.

U2000
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Ethernet Service Management > E-Line Service from the Function Tree. Step 2 Click New. The New E-Line Service dialog box is displayed. Step 3 Set Direction to UNI-NNI, Bearer Type to PW, and Protection Type to No Protection for E-Line services.

NOTE
A Task Collection
When E-Line services are initially configured, it is recommended that you set Protection Type to No Protection for the services. After successful service creation, add the APS protection when necessary. For details on how to add APS protection, see A.7.5.1 Creating a PW APS Protection Group.
Step 4 Set the basic attributes of E-Line services.
Step 5 Click Configure PW. The Configure PW dialog box is displayed. Step 6 Click the General Attributes tab and set the basic parameters for PWs.
Step 7 Click the QoS tab and set the QoS parameters for PWs.
Issue 02 (2011-01-20)
A-113
A Task Collection
Step 8 Click the Advanced Attributes tab and set the advanced parameters for PWs.
Step 9 Click OK, and close the Configure PW dialog box. Step 10 Click OK. Then, close the dialog box that is displayed. ----End
Related References
A.6.3.6 Creating a VLAN Forwarding Table Item

After the corresponding VLAN forwarding table item is created, the VLAN IDs of the service packets can be switched at the source or sink end of the E-Line service.
Prerequisite
l l l You must be an NM user with NE operator authority or higher. The corresponding Ethernet board must be added to NE Panel. The UNI-UNI E-Line service must be created.

U2000
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Ethernet Service Management > E-Line Service from the Function Tree. Step 2 Select the E-Line service whose VLAN forwarding table entries need to be configured. Step 3 Click the VLAN Forwarding Table Item tab. Step 4 Click New.
A Task Collection
Step 5 Set the attributes of the new VLAN forwarding table item. Step 6 Click OK.Then, close the dialog box that is displayed. ----End
Related References
B.6.1.3 Parameter Description: VLAN Forwarding Table Item_Creation
A.6.3.7 Configuring TPID for a Request VLAN

When a request VLAN is used for E-Line services transmitted by PWs, the TPID in the request VLAN is defaulted to be 0x88A8. The TPID can be set for an NE.
Prerequisite

U2000
Procedure
Step 1 In the NE Explorer, select the required NE from the Object Tree, and then choose Configuration > TPID Configuration from the Function Tree. Step 2 Set TPID(Hexadecimal) according to planning information.
A.6.3.8 Configuring IEEE 802.1d Bridge-Based E-LAN Services

The E-LAN service refers to the dynamic transmission of the Ethernet service in the multipointto-multipoint mode through MAC address.
Prerequisite
l l l You must be an NM user with NE operator authority or higher. The Ethernet board has been added on the NE Panel. For ports carrying IEEE 802.1d bridge-based E-LAN services, Port Mode has been set to Layer 2 and Encapsulation Type has been set to Null.

U2000
A Task Collection
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Ethernet Service Management > E-LAN Service from the Function Tree. Step 2 Click New. The New E-LAN Service dialog box is displayed. Step 3 Configure the attributes of the bridge.
NOTE
l The port parameter varies according to Tag Type.
A-116
Issue 02 (2011-01-20)
A Task Collection
Issue 02 (2011-01-20)
A-117
A Task Collection
Step 4 Configure the port that is mounted to the bridge on the UNI side of the E-LAN service. 1. 2. Click the UNI tab. Click Configuration, and then select the port that needs to be mounted to the bridge in the Configure Port dialog box that is displayed.
TIP
Hold on the Ctrl key on the keyboard to select multiple ports.
3. 4.
Click
Optional: Configure the attributes of the port that needs to be mounted to the bridge in the Selected Ports dialog box.
NOTE
The parameter that can be configured varies according to Tag Type.
5.
Click OK.
Step 5 Optional: Configure the logical port on the NNI side.

NOTE
This step takes effect only when Tag Type is set to S-Awared.
Step 6 Optional: Configure the split horizon group. 1.

A-118
Click the Split Horizon Group tab.

A Task Collection
2. 3.
Click New, then the New Split Horizon Group dialog box is displayed. Select a port from Available Interfaces, and then click
TIP
4.
Click OK.
Step 7 Click OK. Step 8 Optional: Select Split Horizon Group. 1. Click Create. Then, the Create Split Horizon Group dialog box is displayed. Select the port to be added from Available Port List and then click
NOTE
2.
To select more than one port at a time, press and hold the Ctrl key when selecting the ports.
3.
Click OK.
----End
Related References
B.6.1.4 Parameter Description: E-LAN Service_Creation
A.6.3.9 Configuring IEEE 802.1q Bridge-Based E-LAN Services

An IEEE 802.1q bridge is a virtual bridge (VB), which can be divided by VLAN into several switching domains.
Prerequisite
l l You must be an NM user with NE administrator authority or higher. For the ports that carry the IEEE 802.1q bridge-based E-LAN services, Port Mode has been set to Layer 2 and Encapsulation Type has been set to 802.1Q.

U2000
A Task Collection
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Ethernet Service Management > E-LAN Service from the Function Tree. Step 2 Click New. The New E-LAN Service dialog box is displayed. Step 3 Set basic attributes of the E-LAN service as planned.
NOTE
Set Tag Type to C-Awared.
Step 4 Configure the ports mounted to the bridge on the UNI side. 1. 2. 3. 4.
A-120
Click UNI. Click Configuration. The Configure Port dialog box is displayed. Configure the ports mounted to the bridge on the UNI side. Click OK.
A Task Collection
Step 5 Optional: Configure split horizon groups. 1. Click the Split Horizon Group tab and click New. The New Split Horizon Group dialog box is displayed.
2. 3. 4.
Set port parameters for the split horizon group as planned. Click Click OK. .
Related References
A.6.3.10 Configuring IEEE 802.1ad Bridge-Based E-LAN Services

An IEEE 802.1ad bridge is a provider bridge (PB), which can be divided by SVLAN into several switching domains.
Prerequisite
l l You must be an NM user with NE administrator authority or higher. For the board that transmits the IEEE 802.1ad bridge-based E-LAN service, Port Mode has been set to Layer 2.

U2000
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Ethernet Service Management > E-LAN Service from the Function Tree. Step 2 Click New. The New E-LAN Service dialog box is displayed.
A Task Collection
Step 3 Set parameters of the E-LAN service as planned.

NOTE
Set Tag Type to S-Awared.
Step 4 Configure the ports mounted to the bridge on the UNI side. 1. 2. 3. 4. 1. 2. 3. 4. 1. Click UNI. Click Configuration. The Configure Port dialog box is displayed. Configure the ports mounted to the bridge on the UNI side. Click OK. Click NNI. Click Configuration. The Configure Port dialog box is displayed. Configure the ports mounted to the bridge on the NNI side. Click OK. Click the Split Horizon Group tab and click New. The New Split Horizon Group dialog box is displayed.
Step 5 Configure the ports mounted to the bridge on the NNI side.
Step 6 Optional: Configure split horizon groups.
2. 3.
A-122
Set port parameters for the split horizon group as planned. Click .
A Task Collection
4.
Click OK.
Related References
A.6.3.11 Changing Logical Ports Connected to a VB

This section describes how to change the logical ports connected to a VB and the attributes of the ports.
Prerequisite
l l You must be an NM user with NE operator authority or higher. The E-LAN services must be created.

U2000
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Ethernet Service Management > E-LAN Service from the Function Tree. Step 2 Add or delete logical ports connected to a VB.
NOTE
l To add or delete ports connected to the VB on the UNI side, click the UNI tab. l To add or delete ports connected to the VB on the NNI side, click the NNI tab.
1.
Click Configuration. In the Configure Port dialog box that is displayed, select the port to be added to or deleted from the list of ports connected to the VB. Optional: Click Optional: Click
TIP
2. 3.
to add ports to the list of ports connected to the VB. to delete ports from the list of ports connected to the VB.
4. 5. 6.
In Selected Port List, set the attributes of the ports connected to the VB. Click OK. A dialog box is displayed for confirmation. Click Yes. Then, close the dialog box that is displayed.
----End
A.6.3.12 Deleting an E-Line Service

When an E-Line service is not used, you need to delete the E-line service to release the corresponding resources.
A Task Collection
Prerequisite
l l You must be an NM user with NE operator authority or higher. The E-Line service must be configured and the service is not used.

U2000
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Ethernet Service Management > E-Line Service from the Function Tree. Step 2 Click Query, and then close the dialog box that is displayed. Step 3 Select the Ethernet-line service that needs to be deleted and then click Delete. Then, a dialog box is displayed, querying whether you need to perform this operation. Step 4 Click OK. Then, close the dialog box that is displayed. Step 5 Click Query. At this time, the E-line service is already deleted. ----End
A.6.3.13 Deleting E-LAN Services

When an E-LAN service is not required, you can delete this E-LAN service to release corresponding Ethernet resources.
Prerequisite
l l You must be an NM user with NE operator authority or higher. A configured E-LAN service is not required.

U2000
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Ethernet Service Management > E-LAN Service from the Function Tree. Step 2 Click Query. Then, close the dialog box that is displayed. Step 3 Select the E-LAN service to be deleted and click Delete. Then, a confirmation dialog box is displayed. Step 4 Click Yes. Then, close the dialog box that is displayed. Step 5 Click Query. At this time, the E-LAN service is already deleted. ----End
A Task Collection
A.6.4 Managing the MAC Address Table

The MAC address table is the core of the E-LAN service. The OptiX RTN 980 provides various functions for managing the MAC address table. A.6.4.1 Creating a Static MAC Address Entry Through the creation of a static MAC address entry, the host with a specified MAC address is not affected by MAC address aging. In addition, the E-LAN service can be supported by the host that receives packets only. A.6.4.2 Creating a Blacklist Entry of MAC Addresses Through the creation of a blacklist entry of MAC addresses, the host with a specified MAC address can be prohibited from using the E-LAN service. A.6.4.3 Configuring the Aging Parameters of a MAC Address Table By default, the aging function of a MAC address table is enabled and the aging time is five minutes. By configuring the aging parameters of a MAC address table, you can modify such parameters. A.6.4.4 Querying or Deleting a Dynamic MAC Address By querying or deleting a dynamic MAC address, you can query or delete all the MAC address entries that are learned by the E-LAN service.
A.6.4.1 Creating a Static MAC Address Entry

Through the creation of a static MAC address entry, the host with a specified MAC address is not affected by MAC address aging. In addition, the E-LAN service can be supported by the host that receives packets only.
Prerequisite
l l The E-LAN service must be created. You must be an NM user with NE operator authority or higher.

U2000
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Ethernet Service Management > E-LAN Service from the Function Tree. Step 2 On the main interface, select the E-LAN service whose static MAC address entry needs to be created. Step 3 Click the Static MAC Address tab. Step 4 Click New. The New Static MAC Address dialog box is displayed. Step 5 Configure the parameters of the static MAC address entry.
A Task Collection
Related References
B.6.1.5 Parameter Description: E-LAN Service
A.6.4.2 Creating a Blacklist Entry of MAC Addresses

Through the creation of a blacklist entry of MAC addresses, the host with a specified MAC address can be prohibited from using the E-LAN service.
Prerequisite

U2000
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Ethernet Service Management > E-LAN Service from the Function Tree. Step 2 On the main interface, select the E-LAN service whose blacklist entry of MAC addresses needs to be created. Step 3 Click the Disabled MAC Address tab. Step 4 Click New. The Create Disabled MAC Address dialog box is displayed. Step 5 Configure the blacklist entry of MAC addresses.
Related References
A Task Collection
A.6.4.3 Configuring the Aging Parameters of a MAC Address Table

By default, the aging function of a MAC address table is enabled and the aging time is five minutes. By configuring the aging parameters of a MAC address table, you can modify such parameters.
Prerequisite

U2000
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Ethernet Service Management > E-LAN Service from the Function Tree. Step 2 On the main interface, select the E-LAN service whose aging parameters of the MAC address table need to be configured. Step 3 Click the MAC Address Learning Parameters tab. Step 4 Configure the status of the aging function and set the aging time.
Related References
A.6.4.4 Querying or Deleting a Dynamic MAC Address

By querying or deleting a dynamic MAC address, you can query or delete all the MAC address entries that are learned by the E-LAN service.
Prerequisite

U2000
A Task Collection
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Ethernet Service Management > E-LAN Service from the Function Tree. Step 2 On the main interface, select the E-LAN service whose dynamic MAC address needs to be queried or cleared. Step 3 Click the Self-Learning MAC Address tab. Step 4 Optional: Select the board whose dynamic MAC address needs to be queried and then check the dynamic MAC addresses in the MAC address table that is displayed. Step 5 Optional: Click Clear MAC Address to clear the dynamic MAC addresses. Then, click OK in the dialog box that is displayed for confirmation. ----End
Related References
A.6.5 Setting the Mode for Processing an Unknown Frame of the ELAN Service
An unknown frame is a unicast frame whose destination MAC address is not listed in the MAC address table or a multicast frame whose destination MAC address is not listed in the multicast group. By default, the NE broadcasts the unknown frame. By setting the mode for processing an unknown frame of the E-LAN service, you can change the processing mode so that unknown frame can be discarded.
Prerequisite

U2000
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Ethernet Service Management > E-LAN Service from the Function Tree. Step 2 On the main interface, select the E-LAN service, the mode for processing whose unknown frame needs to be set. Step 3 Click the Unknown Frame Processing tab. Step 4 Set the mode for processing an unknown frame of the E-LAN service.
A-128
Issue 02 (2011-01-20)
A Task Collection
Related References
A.6.6 Managing the MSTP

The OptiX RTN 980 supports only the MSTP that generates the CIST. A.6.6.1 Creating the MSTP Port Group When the NE needs to run the MSTP protocol together with the user network, the ports on the NE that are connected to the user network need to be configured as a port group. All the members in the port group are involved in the spanning tree algorithm of the user network. A.6.6.2 Setting the Bridge Parameters of the MSTP This topic describes how to set the bridge parameters and port parameters of the MSTP. A.6.6.3 Setting the Parameters of the CIST This topic describes how to set the CIST parameters, including the bridge priority, port priority, and path overheads. A.6.6.4 Querying the CIST Running Information By querying the CIST running information, you can be familiar with the current information of the CIST. A.6.6.5 Changing the Spanning Tree Protocol Used by the Port Group When the spanning tree protocol is upgraded (for example, from the STP protocol to the MSTP protocol) for the equipment that runs the spanning tree together with the local NE, you need to change the spanning tree protocol used by the port group on the local NE to be the same. A.6.6.6 Enabling/Disabling the MSTP Protocol This topic describes how to enable or disable the MSTP protocol of a port group or members of the port group. A.6.6.7 Modifying the Configuration Data of the MSTP Port Group This topic describes how to modify the configuration data of the MSTP port group.
A.6.6.1 Creating the MSTP Port Group

When the NE needs to run the MSTP protocol together with the user network, the ports on the NE that are connected to the user network need to be configured as a port group. All the members in the port group are involved in the spanning tree algorithm of the user network.
Prerequisite
l l You must be an NM user with NE operator authority or higher. The boards where the member ports are located must be added in NE Panel.

U2000
A Task Collection
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Ethernet Protocol Configuration > MSTP Configuration from the Function Tree. Step 2 Click the Port Group Parameters tab. Step 3 Click Create. The Create Port Group dialog box is displayed. Then, the Create Port Group dialog box is displayed. Step 4 Set the attributes of the port group. 1. 2. 3. Set Protocol Type and Enable Protocol. Select the board where the member port is located from the drop-down list of Board under Apply Port. Select the member port from Available Port List. Then, click .
TIP
To select more than one port at a time, press and hold the Ctrl key or the Shift key when selecting the ports.
4.
Click OK.
----End
Related References
B.6.2.3 Parameter Description: MSTP Configuration_Port Group Creation
A.6.6.2 Setting the Bridge Parameters of the MSTP

This topic describes how to set the bridge parameters and port parameters of the MSTP.
Prerequisite
l l
A-130
You must be an NM user with NE operator authority or higher. The port group must be created.
A Task Collection

U2000
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Ethernet Protocol Configuration > MSTP Configuration from the Function Tree. Step 2 Click the Bridge Parameters tab. Step 3 Select the port group ID. Step 4 Click the Bridge Parameters tab. Step 5 Set the attributes of the bridge.
Step 6 Click Apply. Step 7 Click the Port Parameter tab. Step 8 Set the parameters of each member of the port group.
Related References
B.6.2.5 Parameter Description: MSTP Configuration_ Bridge Parameters
A.6.6.3 Setting the Parameters of the CIST

This topic describes how to set the CIST parameters, including the bridge priority, port priority, and path overheads.
Prerequisite
l l You must be an NM user with NE operator authority or higher. The port group must be created.

U2000
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Ethernet Protocol Configuration > MSTP Configuration from the Function Tree.
A Task Collection
Step 2 Click the CIST&MSTI Parameters tab. Step 3 Select the port group from the drop-down list of Port Group. Step 4 Set the parameters of the port group.
Related References
B.6.2.6 Parameter Description: MSTP Configuration_CIST Parameters
A.6.6.4 Querying the CIST Running Information

By querying the CIST running information, you can be familiar with the current information of the CIST.
Prerequisite
l l You must be an NM user with NE operator authority or higher. The MSTP port group must be created.

U2000
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Ethernet Protocol Configuration > MSTP Configuration from the Function Tree. Step 2 Click the CIST Running Information tab.
A Task Collection
Step 3 Click Query. Step 4 Query the CIST running information. ----End
Related References
B.6.2.7 Parameter Description: MSTP Configuration_Running Information About the CIST
A.6.6.5 Changing the Spanning Tree Protocol Used by the Port Group
When the spanning tree protocol is upgraded (for example, from the STP protocol to the MSTP protocol) for the equipment that runs the spanning tree together with the local NE, you need to change the spanning tree protocol used by the port group on the local NE to be the same.
Prerequisite

U2000
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Ethernet Protocol Configuration > MSTP Configuration from the Function Tree. Step 2 Click the Port Group Parameters tab. Step 3 Select the target protocol type from the Protocol Type drop-down list of the port group whose spanning tree protocol needs to be changed.
A.6.6.6 Enabling/Disabling the MSTP Protocol

This topic describes how to enable or disable the MSTP protocol of a port group or members of the port group.
Prerequisite

U2000
A Task Collection
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Ethernet Protocol Configuration > MSTP Configuration from the Function Tree. Step 2 Click the Port Group Parameters tab. Step 3 Select Enabled or Disabled from the Enable Protocol drop-down list of the port group for which the MSTP protocol needs to be enabled or disabled.
Step 4 Click Apply. Step 5 Select Enabled or Disabled from the Enable Protocol drop-down list in Port Group to enable or disable the MSTP protocol of a port.
A.6.6.7 Modifying the Configuration Data of the MSTP Port Group

This topic describes how to modify the configuration data of the MSTP port group.
Prerequisite

U2000
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Ethernet Protocol Configuration > MSTP Configuration from the Function Tree. Step 2 Click the Port Group Parameters tab. Step 3 Click Configuration. Then, the Configure Port Group dialog box is displayed. Step 4 Modify the configuration data of the MSTP port group. Option If...
A-134
Description Then...
A Task Collection
Option A member port needs to be added
Description 1. Select the board where the member ports are located from the drop-down list of Board. 2. Select the port to be added from Available Port List. 3. Click .
A member port needs to be deleted 1. Select the port to be deleted from Selected Port List. 2. Click
TIP
To select more than one port at a time, press and hold the Ctrl key or Shift key when selecting the ports.
Related References
B.6.2.4 Parameter Description: MSTP Configuration_Port Group Configuration
A.6.7 Managing the QoS

By managing the QoS, you can provide the services of different levels for different service types. A.6.7.1 Creating a DS Domain By creating a DS domain, you can create the mapping relation of a new DS domain and configure the ports that use this mapping relationship. A.6.7.2 Modifying the Mapping Relationships for the DS Domain This topic describes how to modify the mapping relationships between packet priorities and PHB service classes in the ingress or egress direction of a DS domain. A.6.7.3 Changing the Ports Applied to a DS Domain and Their Trusted Packet Types
A Task Collection
This topic describes how to add or delete a port that uses the DS domain and set the packet type over the port. A.6.7.4 Creating a Port Policy By creating a port policy, you can create a new port policy. A.6.7.5 Modifying the Port Policy This section describes how to change the parameter values of a created DS domain. A.6.7.6 Creating the Traffic By creating the traffic, you can configure ACL, CAR and shaping for a specified traffic stream on a specified port. A.6.7.7 Setting the Port That Uses the Port Policy This section describes how to set the port that uses the port policy. A.6.7.8 Configuring Port Shaping This topic describes how to configure the traffic shaping for an egress port. A.6.7.9 Querying the Port Policy This topic describes how to query the port policy of a port. A.6.7.10 Querying the DS Domain of a Port This topic describes how to query the mapping relation between a port and a DS domain.
A.6.7.1 Creating a DS Domain

By creating a DS domain, you can create the mapping relation of a new DS domain and configure the ports that use this mapping relationship.
Prerequisite
l l You must be an NM user with NE operator authority or higher. The board of the Ethernet ports must be added on NE Panel.

U2000
The OptiX RTN 980 has a default DS domain, whose Mapping Relation ID is 1 and Mapping Relation Name is default map. Before another DS domain is created, all the ports belong to this default DS domain.
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > QoS Management > Diffserv Domain Management > Diffserv Domain Management from the Function Tree. Step 2 Click New. The Create DS Domain dialog box is displayed. Step 3 On the main interface, configure the attributes of the DS domain.

NOTE
A Task Collection
The MPLS EXP value can be modified in the default Diffserv domain (Default Map) only.
Step 4 Click the Inbound Mapping Relation tab. Step 5 Configure the mapping relations between the priorities of ingress packets and PHB service classes. Step 6 Click the Inbound Mapping Relation tab. Step 7 Configure the mapping relations between the priorities of egress packets and PHB service classes. Step 8 Select Board where the application ports exist from Application Port. Step 9 Select a port from Available Port, and then click
TIP
A Task Collection
Related References
B.6.4.2 Parameter Description: DiffServ Domain Management_Create
A.6.7.2 Modifying the Mapping Relationships for the DS Domain

This topic describes how to modify the mapping relationships between packet priorities and PHB service classes in the ingress or egress direction of a DS domain.
Prerequisite
l l You must be an NM user with NE operator authority or higher. The DS domain must be created.

U2000
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > QoS Management > Diffserv Domain Management > Diffserv Domain Management from the Function Tree. Step 2 Select the created DS domain and change its attributes on the main interface.
NOTE
The MPLS EXP value can be modified in the default Diffserv domain (Default Map) only.
Step 3 Optional: Change the mapping relationship in the ingress direction. 1. 2. 3. 1. 2. 3. Click the Inbound Mapping Relation tab. Double-click the parameters whose values need to be changed and change the mapping relationship between the packet priorities and PHB classes in the ingress direction. Click Apply. Then, close the dialog box that is displayed. Click the Outbound Mapping Relation tab. Double-click the parameters whose values need to be changed and change the mapping relationship between the packet priorities and PHB classes in the egress direction. Click Apply. Then, close the dialog box that is displayed.
Step 4 Optional: Change the mapping relationship in the egress direction.
Related References
B.6.4.1 Parameter Description: Diffserv Domain Management
A Task Collection
A.6.7.3 Changing the Ports Applied to a DS Domain and Their Trusted Packet Types
This topic describes how to add or delete a port that uses the DS domain and set the packet type over the port.
Prerequisite
l l You must be an NM user with NE operator authority or higher. The DS domain must be created.

U2000
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > QoS Management > Diffserv Domain Management > Diffserv Domain Management from the Function Tree. Step 2 Select the DS domain for which you need to add or delete an application port on the main interface. Step 3 Click the Application Object tab. Step 4 Click Modify. Step 5 Add or delete a port that uses the DS domain. Option If... You need to add a port that uses the DS domain Description Then ... 1. Select the board where the application port is located from the drop-down list of Board. 2. Select the port to be added from the dropdown list of Available Ports. 3. Click .
You need to delete a port that uses the DS 1. Select the board where the application port is domain located from the drop-down list of Board. 2. Select the port to be deleted from the port list of Selected Ports. 3. Click
Issue 02 (2011-01-20) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.
.
A-139
A Task Collection
Option You need to change the packet type identified by the port
Description Select a new packet type from the drop-down list of Packet Type.
TIP
Related References
B.6.4.3 Parameter Description: DiffServ Domain Applied Port_Modification
A.6.7.4 Creating a Port Policy

By creating a port policy, you can create a new port policy.
Prerequisite
l l You must be an NM user with NE operator authority or higher. The board of the Ethernet ports must be added on NE Panel.

U2000
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > QoS Management > Policy Management > Port Policy from the Function Tree. Step 2 Create a port policy by adding a port policy on the NMS.
A Task Collection
1. 2. 3.
Click New. The Create Port Policy dialog box is displayed. Set the ID and name of the port policy. Configure the scheduling, weight, and shaping of the egress queues.
4. 1. 2. 3. 4. 5.
Click OK. Then, close the dialog box that is displayed. Select a similar port policy and click Copy. Then, the Duplicate QoS Policy dialog box is displayed. Change the name of the port policy. Click OK. Then, close the dialog box that is displayed. Select the duplicated port policy and change the scheduling, weight, and shaping of the egress queues. Click Apply. Then, close the dialog box that is displayed.
Step 3 Create a port policy by duplicating an existing port policy.
----End
Related References
B.6.4.5 Parameter Description: Port Policy
A.6.7.5 Modifying the Port Policy

This section describes how to change the parameter values of a created DS domain.
Prerequisite
l l You must be an NM user with NE operator authority or higher. The port policy must be created.

U2000
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > QoS Management > Policy Management > Port Policy from the Function Tree. Step 2 Select the port policy whose parameter values need to be changed.
A Task Collection
Step 3 Double-click the parameters whose values need to be changed and change the queue scheduling, weight, and queue shaping of the port queues. Step 4 Click Apply. Then, close the dialog box that is displayed. ----End
Related References
B.6.4.4 Parameter Description: Policy Management

By creating the traffic, you can configure ACL, CAR and shaping for a specified traffic stream on a specified port.
Prerequisite
l l l You must be an NM user with NE operator authority or higher. The Ethernet board must be added on the NE Panel. The port policy must be created.

U2000
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > QoS Management > Policy Management > Port Policy from the Function Tree. Step 2 Click the Traffic Classification Configuration tab. Step 3 Click New. The Create Traffic Classification dialog box is displayed. Step 4 Configure the attributes of a new traffic.
A-142
Issue 02 (2011-01-20)
A Task Collection
Step 5 Click OK. Step 6 Click OK. Step 7 Click Apply. ----End
Related References
B.6.4.6 Parameter Description: Port Policy_Traffic Classification Configuration
A.6.7.7 Setting the Port That Uses the Port Policy

This section describes how to set the port that uses the port policy.
Prerequisite
Tools, Instruments, and Materials

U2000
Issue 02 (2011-01-20)
A-143
A Task Collection
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > QoS Management > Policy Management > Port Policy from the Function Tree. Step 2 Click the Application Object tab. Step 3 Click Modify. Then, the Configure Port dialog box is displayed. Step 4 Set the port that uses the port policy. 1. 2. Select Board where the port that needs to use the port policy from Application Object. Select a port from Available Ports, and then click
TIP
3.
Click OK. Then, close the dialog box that is displayed.
Step 5 Delete the port that uses the port policy. 1. Select the port to be deleted from Selected Ports and click
TIP
A-144
Issue 02 (2011-01-20)
A Task Collection
2.
Click OK. Then, close the dialog box that is displayed.
----End
Related References
A.6.7.8 Configuring Port Shaping

This topic describes how to configure the traffic shaping for an egress port.
Prerequisite
l l You must be an NM user with NE operator authority or higher. The Ethernet board must be created on the NE Panel.

U2000
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > QoS Management > Port Shaping Management from the Function Tree. Step 2 Click New. The New dialog box is displayed. Step 3 Set the parameters for the shaping of a port.
Issue 02 (2011-01-20)
A-145
A Task Collection
Related References
B.6.4.7 Parameter Description: Port Shaping Management_Creation
A.6.7.9 Querying the Port Policy

This topic describes how to query the port policy of a port.
Prerequisite

U2000
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > QoS Management > Policy Management > Port Policy from the Function Tree. Step 2 Select the created port policy. Step 3 Click the CoS Configuration tab. Step 4 Click Query. Then, close the dialog box that is displayed. Step 5 Query the CoS configuration of the port policy. Step 6 Click the Traffic Classification Configuration tab. Step 7 Click Query. Then, close the dialog box that is displayed. Step 8 Query the traffic classification of the port policy. Step 9 Click the Applied Object tab. Step 10 Click Query. Then, close the dialog box that is displayed. Step 11 Query the ports that use the port policy. ----End
A Task Collection
Related References
A.6.7.10 Querying the DS Domain of a Port

This topic describes how to query the mapping relation between a port and a DS domain.
Prerequisite

U2000
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > QoS Management > Diffserv Domain Management from the Function Tree. Step 2 Click the Inbound Mapping Relation tab. Step 3 Click Query. Then, close the dialog box that is displayed. Step 4 Query the attributes of the DS domain and the mapping relation between the priority level of the packets in the ingress direction and the PHB service class. Step 5 Click the Outbound Mapping Relation tab. Step 6 Click Query. Then, close the dialog box that is displayed. Step 7 Query the attributes of the DS domain and the mapping relation between the priority level of the packets in the egress direction and the PHB service class. Step 8 Click the Application Object tab. Step 9 Click Query. Then, close the dialog box that is displayed. Step 10 Query the ports that use the DS domain. ----End
Related References
A.6.8 Using the IEEE 802.1ag OAM

By using the 802.1ag OAM, you can maintain Ethernet services in an end-to-end manner. A.6.8.1 Creating an MD
A Task Collection
A maintenance domain (MD) defines the range and level of the Ethernet OAM. MDs of different ranges and levels can provide users with differentiated OAM services. A.6.8.2 Creating an MA An MD can be divided into several independent maintenance associations (MAs). By creating MAs, you can associate specific Ethernet services with MAs. This facilitates Ethernet OAM operations. A.6.8.3 Creating an MEP Point An MEP is the starting and end positions of all the OAM packets. By creating an MEP, you can check the Ethernet channel of the MEPs that belong to a same MA through the OAM operation. A.6.8.4 Creating Remote MEPs in an MA To ensure that an MEP can respond to the OAM operations initiated by the other MEPs in the same MA, you need to set the other MEPs to be the remote MEPs of this MEP. A.6.8.5 Creating an MIP The maintenance association intermediate points (MIPs) can respond to specific OAM packets. By creating an MIP, you can divide the Ethernet link between the MEPs in the same MA into several segments, thus facilitating the detection of the Ethernet link. A.6.8.6 Performing a CC Test After the continuity check (CC) test, the unidirectional link status can be checked automatically and periodically. If the link is fault after the CC test is started at the source end, the sink equipment reports the corresponding alarm. A.6.8.7 Performing an LB Test During a loopback (LB) test, you can check the bidirectional connectivity between the source MEP and any MEP in the same maintenance association (MA). A.6.8.8 Performing an LT Test Based on the LB test, the link trace (LT) test further improves the capability to locate faults. That is, the faulty network segment can be located according to the MIP through only one test.
A.6.8.1 Creating an MD
A maintenance domain (MD) defines the range and level of the Ethernet OAM. MDs of different ranges and levels can provide users with differentiated OAM services.
Prerequisite

U2000
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Ethernet OAM Management > Ethernet Service OAM Management from the Function Tree. Step 2 Click the Maintenance Association tab. Step 3 Choose New > New Maintenance Domain.
A Task Collection
The system displays the New Maintenance Domain dialog box. Step 4 Set the parameters of the MD.
Related References
B.6.3.1 Parameter Description: Ethernet Service OAM Management_Maintenance Domain Creation
A.6.8.2 Creating an MA
An MD can be divided into several independent maintenance associations (MAs). By creating MAs, you can associate specific Ethernet services with MAs. This facilitates Ethernet OAM operations.
Prerequisite
l l l You must be an NM user with NE operator authority or higher. The MD must be created. The Ethernet service must be created.

U2000
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Ethernet OAM Management > Ethernet Service OAM Management from the Function Tree. Step 2 Click the Maintenance Association tab. Step 3 Select the maintenance domain in which a maintenance association needs to be created. Choose New > New Maintenance Association. The system displays the New Maintenance Association dialog box. Step 4 Set the parameters of the MA.
NOTE
Click in Relevant Service. Select the corresponding services in the Select Service dialog box that is displayed.
Issue 02 (2011-01-20)
A-149
A Task Collection
Related References
B.6.3.2 Parameter Description: Ethernet Service OAM Management_Maintenance Association Creation
A.6.8.3 Creating an MEP Point

An MEP is the starting and end positions of all the OAM packets. By creating an MEP, you can check the Ethernet channel of the MEPs that belong to a same MA through the OAM operation.
Prerequisite
l l You must be an NM user with NE operator authority or higher. The MA must be created.

U2000
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Ethernet OAM Management > Ethernet Service OAM Management from the Function Tree. Step 2 Click the Maintenance Association tab. Step 3 Select the maintenance association in which an MEP needs to be created. Choose New > New MEP Point. The system displays the New MEP Point dialog box. Step 4 Set the parameters of the MEP point.
A-150
Issue 02 (2011-01-20)
A Task Collection
Related References
B.6.3.3 Parameter Description: Ethernet Service OAM Management_MEP Creation

To ensure that an MEP can respond to the OAM operations initiated by the other MEPs in the same MA, you need to set the other MEPs to be the remote MEPs of this MEP.
Prerequisite

U2000
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Ethernet OAM Management > Ethernet Service OAM Management from the Function Tree. Step 2 Click the Maintenance Association tab. Step 3 Choose OAM > Manage Remote MEP Point. Then, the Manage Remote MEP Point dialog box is displayed. Step 4 Click New. Then, the Add Maintenance Association Remote Maintenance Point dialog box is displayed. Step 5 Set the parameters of the new remote MEPs.
Issue 02 (2011-01-20)
A-151
A Task Collection
Related References
B.6.3.4 Parameter Description: Ethernet Service OAM Management_Remote MEP Creation

The maintenance association intermediate points (MIPs) can respond to specific OAM packets. By creating an MIP, you can divide the Ethernet link between the MEPs in the same MA into several segments, thus facilitating the detection of the Ethernet link.
Prerequisite

U2000
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Ethernet OAM Management > Ethernet Service OAM Management from the Function Tree. Step 2 Click the MIP Point tab. Step 3 Select the maintenance domain in which an MIP needs to be created, and then click New. Then, the New MIP Maintenance Point dialog box is displayed. Step 4 Set the parameters of the new MIP. Step 5 Click OK. Then, close the dialog box that is displayed. ----End
Related References
B.6.3.5 Parameter Description: Ethernet Service OAM Management_MIP Creation
A.6.8.6 Performing a CC Test

After the continuity check (CC) test, the unidirectional link status can be checked automatically and periodically. If the link is fault after the CC test is started at the source end, the sink equipment reports the corresponding alarm.
A Task Collection
Prerequisite
l l l You must be an NM user with NE operator authority or higher. The MEP must be created. The remote MEPs must be created.

U2000
l l Only the MEP can enable the CC test and function as the receiving and responding end in the test. During the CC check, the source MEP constructs and transmits continuity check message (CCM) packets periodically. After receiving the CCM packets from the source MEP, the sink MEP directly enables the CC function for this source MEP. If the sink MEP fails to receive the CCM packets from the source MEP within the check period (that is, 3.5 times of the transmit period), it reports the alarm automatically. Performing a CC test does not affect the services.
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Ethernet OAM Management > Ethernet Service OAM Management from the Function Tree. Step 2 Click the Maintenance Association tab. Step 3 Select the MEP where you need to perform the CC test and then choose OAM > Activate CC. Then, a dialog box is displayed, indicating that the operation is successful.
NOTE
l Before the CC test, you can set CC Test Transmit Period according to the actual requirements. l To disable a CC test, select the MEP where the CC test is performed and then choose OAM > Deactivate.
TIP
l Alternatively, you can enable a CC test by right-clicking an MEP and then choosing Activate CC from the shortcut menu. l Alternatively, you can disable a CC test by right-clicking an MEP and then choosing Deactivate CC from the shortcut menu.
Step 4 Click Close. ----End
A.6.8.7 Performing an LB Test

During a loopback (LB) test, you can check the bidirectional connectivity between the source MEP and any MEP in the same maintenance association (MA).
A Task Collection
Prerequisite
l l l l You must be an NM user with NE operator authority or higher. The source and sink MEPs in the same maintenance domain must be created. The remote MEPs must be created. The CC function must be enabled.

U2000
l l Only MEPs can initiate the LB test and function as the receive end in the test. During the LB test, the source MEP constructs and transmits the LBM frames and starts the timer. If the sink 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. Performing a LB test does not affect the services.
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Ethernet OAM Management > Ethernet Service OAM Management from the Function Tree. Step 2 Click the Maintenance Association tab. Step 3 Select the maintenance domain and maintenance association for the LB test. Step 4 Choose OAM > Start LB. Then, the LB Test dialog box is displayed.
TIP
To enable a LB test, you can also right-click an MEP and then choose Start LB from the shortcut menu.
Step 5 Select the method for identifying the destination MP and set the parameters involved in the LB test.
NOTE
l To identify the destination MP according to the MP ID, select MP ID. l To identify the destination MP according to the MAC address, select Maintenance Point MAC Address.
Step 6 Click Start Test. Then, the LB test result is displayed in the Detection Result window. ----End
A Task Collection
Related References
B.6.3.6 Parameter Description: Ethernet Service OAM Management_LB Enabling
A.6.8.8 Performing an LT Test

Based on the LB test, the link trace (LT) test further improves the capability to locate faults. That is, the faulty network segment can be located according to the MIP through only one test.
Prerequisite
l l l l You must be an NM user with NE operator authority or higher. The source and sink MEPs in the same MD must be created. The remote MEPs must be created. The CC function must be enabled.

U2000
l l Only MEPs can initiate the LT test and work as the termination point in the test. During the LT test, the source MEP constructs and transmits the 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 sink MEP. Performing a LT test does not affect the services.
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Ethernet OAM Management > Ethernet Service OAM Management from the Function Tree. Step 2 Click the Maintenance Association tab. Step 3 Select the maintenance domain and maintenance association for the LT test. Step 4 Choose OAM > Start LT. Then, the LT Test dialog box is displayed.
TIP
To enable a LT test, you can also right-click an MEP and then choose Start LT from the shortcut menu.
Step 5 Select the method for identifying the destination MP and set the parameters involved in the LT test.
NOTE
l To identify the destination MP according to the MP ID, select MP ID. l To identify the destination MP according to the MAC address, select Maintenance Point MAC Address.
Issue 02 (2011-01-20)
A-155
A Task Collection
Step 6 Click Start Test. Then, the LT test result is displayed in the Detection Result window. ----End
Related References
B.6.3.7 Parameter Description: Ethernet Service OAM Management_LT Enabling
A.6.9 Using the IEEE 802.3ah OAM

By using the IEEE 802.1ag OAM, you can maintain the point-to-point Ethernet links. A.6.9.1 Enabling the OAM Auto-Discovery Function The IEEE 802.3ah OAM is realized based on the OAM auto-discovery. After the OAM autodiscovery succeeds, the equipment automatically monitors the fault and performance of the link. A.6.9.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.6.9.3 Modifying 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. Generally, the default value is used. You can modify the value according to the situation of the link. A.6.9.4 Performing 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.6.9.5 Enabling Self-Loop Detection After enabling the self-loop detection on an Ethernet port, you can check the loopback of the port and the loopback between the port and other Ethernet ports on the board.
A.6.9.1 Enabling the OAM Auto-Discovery Function

The IEEE 802.3ah OAM is realized based on the OAM auto-discovery. After the OAM autodiscovery succeeds, the equipment automatically monitors the fault and performance of the link.
Prerequisite

U2000
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
A Task Collection
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.
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Ethernet OAM Management > Ethernet Port OAM Management from the Function Tree. Step 2 Click the OAM Parameter tab. Step 3 Select the port, and set OAM Working Mode.
NOTE
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. l If the OAM modes of the two systems are both 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 autodiscovery fails.
Step 4 Set Enable OAM Protocol to Enabled.
Step 5 Click Apply, and then close the displayed prompt dialog box. Step 6 Click the Remote OAM Parameter tab. Click Query to obtain the OAM capability of the opposite end, and then close the displayed prompt dialog box. ----End
Related References
B.6.3.8 Parameter Description: Ethernet Port OAM Management_OAM Parameter
A.6.9.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 You must be an NM user with NE operator authority or higher. The OAM auto-discovery operation must successful on the equipment at both ends.

U2000
A Task Collection
After the OAM auto-discovery operation is successful 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, you need to set Link Event Notification to Enabled for the local equipment. To report the detected link fault event to the opposite equipment, you need to set Link Event Notification to Enabled and set Error Frame Period Window (ms) and Error Frame Monitor Threshold (frame) for the local equipment. After Link Event Notification is set to Enabled at the opposite port, if the opposite end detects link performance degradation, you can query the ETH_EFM_EVENT alarm, which is reported on the local end, by using the NMS. According to the alarm, you can determine the type of the link performance event. After Link Event Notification is set to Enabled at the opposite port, if the opposite equipment detects a link fault event, you can query the ETH_EFM_REMFAULT alarm, which is reported at the local end, by using the NMS. According to the alarm, you can determine the fault type.
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Ethernet OAM Management > Ethernet Port OAM Management from the Function Tree. Step 2 Click the OAM Parameter tab. Step 3 Select the corresponding port and set Link Event Notification to Enabled.
Related References

The threshold for the OAM error frame monitoring is a standard for the OAM to detect the link performance. Generally, the default value is used. You can modify the value according to the situation of the link.
Prerequisite
l l You must be an NM user with NE operator authority or higher. The IEEE 802.3ah OAM function must be enabled on the remote equipment and the OAM auto-discovery operation must be successful on the equipment at both ends.
A-158
A Task Collection

U2000
After the OAM auto-discovery operation is successful, the remote link event notification function is enabled and the monitoring time and errored frame threshold are set at the local end. If the local equipment detects a link event in the receive direction, it informs the opposite equipment of the link event. If the remote alarm for the link event is also supported at the opposite end, the opposite equipment can also inform the local equipment of the link event that is detected at the opposite end. Then, the corresponding alarm is reported at the local end.
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Ethernet OAM Management > Ethernet Port OAM Management from the Function Tree. Step 2 Click the OAM Error Frame Monitor tab. Step 3 Select the port and set the parameters in the OAM Error Frame Monitor tab page.
Related References
B.6.3.9 Parameter Description: Ethernet Port OAM Management_OAM Error Frame Monitoring
A.6.9.4 Performing 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 You must be an NM user with NE operator authority or higher. The OAM auto-discovery operation must be successful at both ends of the link. On the equipment that initiates the loopback, OAM Working Mode must be set to Active. The equipment that responds to the loopback must support the remote loopback.

U2000
A Task Collection
l If a port is capable of responding to loopbacks, it enters the loopback responding state and reports the loopback responding alarm after 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. Generally, 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 complete the fault locating and the link performance detection, you need to disable the remote loopback function at the end where the loopback is initiated and then restore the services. At this time, the alarm is automatically cleared.
l l
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Ethernet OAM Management > Ethernet Port OAM Management from the Function Tree. Step 2 Click the OAM Parameter tab. Step 3 Select the port and set Remote Side Loopback Response to Enabled.
Step 4 Click Apply. Then, close the dialog box that is displayed. Step 5 Choose Enable Remote Loopback from the drop-down menu of OAM. Then, close the dialog box that is displayed.
----End
A.6.9.5 Enabling Self-Loop Detection

After enabling the self-loop detection on an Ethernet port, you can check the loopback of the port and the loopback between the port and other Ethernet ports on the board.
Prerequisite
l l l
A-160
You must be an NM user with NE operator authority or higher. The required board is already added on the NE Panel. All the external physical ports on the Ethernet service processing board must be enabled.
A Task Collection

U2000
l After the loopback detection is enabled at an Ethernet port, the ETHOAM_SELF_LOOP alarm is reported if a loopback occurs at the port.
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Interface Management > Ethernet Interface from the Function Tree. Step 2 Click the Advanced Attributes tab. Step 3 Set Loopback Check to Enabled. Step 4 Click Apply. Then, close the dialog box that is displayed. ----End
A.6.10 LPT Configuration

When you use LPT function, you need to configure the relationship between LPT ports and the related information of LPT ports. A.6.10.1 Configuring Point-to-Point LPT Traversing an L2 Network When you configure point-to-point LPT traversing an L2 network, it is unnecessary to bind LPT with Ethernet services. A.6.10.2 Configuring Point-to-Point LPT Traversing a PSN or QinQ Network When you configure point-to-point LPT traversing a PSN or QinQ network, it is necessary to bind LPT with services. A.6.10.3 Configuring Point-to-Multipoint LPT When you configure point-to-multipoint LPT, it is necessary to configure the primary and secondary points.
A.6.10.1 Configuring Point-to-Point LPT Traversing an L2 Network

When you configure point-to-point LPT traversing an L2 network, it is unnecessary to bind LPT with Ethernet services.
Prerequisite
l l You must be an NM user with NE administrator authority or higher. L2 services are configured.
NOTE
L2 services include UNI-UNI E-Line services and UNI-UNI E-LAN services transmitted in a point-to-point manner.

U2000
A Task Collection
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > LPT Management from the Function Tree. Step 2 Click the Point-to-Point LPT tab. Step 3 Click Bind in the lower right corner of the pane based on the type of service network. Step 4 Choose L2 net from the shortcut menu. The Bind L2 net dialog box is displayed. Step 5 Set the parameters of the primary and secondary points of LPT.
Step 6 Click OK, and close the dialog box that is displayed. Step 7 Optional: Reset Recovery Time(s), Hold-Off Time(ms), and Fault Detection Period (100ms). Step 8 Set LPT Enabled to Enabled. Then, click Apply. ----End
Related References
B.6.2.11 Parameter Description: LPT Management_Creating Point-to-Point LPT B.6.2.10 Parameter Description: LPT Management_Point-to-Point LPT
A.6.10.2 Configuring Point-to-Point LPT Traversing a PSN or QinQ Network

When you configure point-to-point LPT traversing a PSN or QinQ network, it is necessary to bind LPT with services.
Prerequisite
l l l You must be an NM user with NE administrator authority or higher. QinQ services exclusively occupying UNI ports have been configured. E-Line services carried by PWs exclusively occupying UNI ports have been configured.
NOTE
l For the service models of QinQ services exclusively occupying UNI ports, see Model 1 and Model 2 in 5.3.2.2 QinQ-Based E-Line Services. l For the service models of E-Line services carried by PWs exclusively occupying UNI ports, see Model 3 in 6.8.2.4 E-Line Services Carried on PWs.

U2000
A Task Collection
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > LPT Management from the Function Tree. Step 2 Click the Point-to-Point LPT tab. Step 3 Select PW or QinQ services that require the LPT function. Step 4 Click Bind in the lower right corner of the pane. Then, choose PW+QinQ from the shortcut menu. Step 5 Optional: Reset Recovery Time(s), Hold-Off Time(ms), and Fault Detection Period (100ms). Step 6 Set LPT Enabled to Enabled. Then, click Apply. ----End
Related References
B.6.2.10 Parameter Description: LPT Management_Point-to-Point LPT
A.6.10.3 Configuring Point-to-Multipoint LPT

When you configure point-to-multipoint LPT, it is necessary to configure the primary and secondary points.
Prerequisite
l l You must be an NM user with NE administrator authority or higher. At least one of the following services has been configured. L2 services QinQ services sharing UNI ports E-Line services carried by PWs sharing UNI ports
NOTE
l L2 services include UNI-UNI E-Line services and UNI-UNI E-LAN services transmitted in a point-tomultipoint manner. l For the service models of QinQ services sharing UNI ports, see Model 3 in 5.3.2.2 QinQ-Based E-Line Services. l For the service models of E-Line services carried by PWs sharing UNI ports, see Model 1 and Model 2 in 6.8.2.4 E-Line Services Carried on PWs.

U2000
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > LPT Management from the Function Tree. Step 2 Click the Point-to-Multipoint LPT tab.
A Task Collection
Step 3 Click New in the lower right corner of the pane based on the type of service network. Step 4 Choose PW, QinQ, or L2 net from the shortcut menu based on the type of service network. The Create LPT dialog box is displayed. Step 5 Set the parameters of the primary and secondary points of LPT. Step 6 Click OK, and close the dialog box that is displayed. Step 7 Optional: Reset Recovery Time(s), Hold-Off Time(ms), and Fault Detection Period (100ms). Step 8 Set LPT Enabled to Enabled. Then, click Apply. ----End
Related References
B.6.2.13 Parameter Description: LPT Management_Creating Point-to-Multipoint LPT B.6.2.12 Parameter Description: LPT Management_Point-to-Multipoint LPT
A.7 Managing MPLS/PWE3 Services and Features

The OptiX RTN 980 supports multiple MPLS/PWE3 services and features. A.7.1 Managing Address Resolution The OptiX RTN 980 runs the Address Resolution Protocol (ARP) to set up mapping between MAC addresses and IP addresses of ports. A.7.2 Managing MPLS Tunnels Managing MPLS tunnels include managing MPLS OAM functions. A.7.3 Managing MPLS APS Protection Groups MPLS APS is the commonest protection mode for MPLS tunnels. A.7.4 Managing PWs All types of PWE3 services are carried by PWs. A.7.5 Managing a PW APS Protection Group PW APS provides protection for PWs. A.7.6 Managing CES Services The OptiX RTN 980 supports PWE3-based CES services. A.7.7 Managing ATM/IMA Ports On the OptiX RTN 980, ATM/IMA ports are mapped into one ATM TRUNK. A.7.8 Managing ATM Services The OptiX RTN 980 supports common ATM services (UNI-UNI) and PW-carried ATM services (UNI-NNI). A.7.9 ATM Traffic Management ATM traffic management includes ATM-Diffserv management and ATM policy management. A.7.10 Using ATM OAM ATM OAM is an OAM mechanism that is used for detecting and locating ATM faults, and monitoring ATM performance.
A Task Collection
A.7.1 Managing Address Resolution

The OptiX RTN 980 runs the Address Resolution Protocol (ARP) to set up mapping between MAC addresses and IP addresses of ports. A.7.1.1 Creating ARP Static Entries This topic describes how to create ARP entries that are not aged. A.7.1.2 Querying ARP Entries You can learn about ARP information. A.7.1.3 Converting Dynamic ARP Entries to Static ARP Entries During the equipment operation phase, you can change dynamic entries in the ARP table to static entries to improve stability of tunnels. A.7.1.4 Deleting Static ARP Entries When MAC addresses of interconnected ports change, you can delete the existing static ARP entries of the network element (NE) and create other ARP entries. A.7.1.5 Setting ARP Aging Time This topic describes how to set the ARP aging time. The default aging time is 20 minutes.
A.7.1.1 Creating ARP Static Entries

This topic describes how to create ARP entries that are not aged.
Prerequisite

U2000
Procedure
Step 1 In the NE Explorer, select the required NE from the Object Tree and then choose Configuration > Control Plane Configuration > Address Parse from the Function Tree. Step 2 Click Create. The Add Address Parse dialog box is displayed. Step 3 Set the parameters for address resolution.
NOTE
When you configure an MAC address in the ARP entries, the first digit of the MAC address must be an even numeral.
Step 4 Click OK. Then, the static ARP entry is successfully created. ----End
A Task Collection
A.7.1.2 Querying ARP Entries

You can learn about ARP information.
Prerequisite

U2000
Procedure
Step 1 In the NE Explorer, select the required NE from the Object Tree and then choose Configuration > Control Plane Configuration > Address Parse from the Function Tree. Step 2 Click Query and query ARP entries in the main interface. ----End
A.7.1.3 Converting Dynamic ARP Entries to Static ARP Entries

During the equipment operation phase, you can change dynamic entries in the ARP table to static entries to improve stability of tunnels.
Prerequisite

U2000
Procedure
Step 1 In the NE Explorer, select the required NE from the Object Tree and then choose Configuration > Control Plane Configuration > Address Parse from the Function Tree. Step 2 Select the required dynamic ARP entry and click Switch to Static Type. Step 3 Click Query. Then, ARP List Type changes to Static for the selected dynamic ARP entry. ----End
A.7.1.4 Deleting Static ARP Entries

When MAC addresses of interconnected ports change, you can delete the existing static ARP entries of the network element (NE) and create other ARP entries.
Prerequisite
A Task Collection

U2000
Procedure
Step 1 In the NE Explorer, select the required NE from the Object Tree and then choose Configuration > Control Plane Configuration > Address Parse from the Function Tree. Step 2 Select the required static ARP entry and click Delete.
NOTE
When deleting dynamic ARP entries, click Clear. Exercise caution when performing this operation to avoid service interruption.
A confirmation dialog box is displayed. Step 3 Click OK. Step 4 Click Query. The selected static ARP entry is deleted. ----End
A.7.1.5 Setting ARP Aging Time

This topic describes how to set the ARP aging time. The default aging time is 20 minutes.
Prerequisite

U2000
Procedure
Step 1 In the NE Explorer, select the NE from the Object Tree and choose Configuration > Control Plane Configuration > Aging Time from the Function Tree. Step 2 Select the required port, double-click it, and modify the parameter Dynamic ARP Entry Aging Time(min). Step 3 Click Apply. ----End
A.7.2 Managing MPLS Tunnels

Managing MPLS tunnels include managing MPLS OAM functions. A.7.2.1 Setting Basic MPLS Attributes This topic describes how to set basic MPLS attributes, including the LSR ID and the global label space. A.7.2.2 Creating a Unidirectional MPLS Tunnel
A Task Collection
When creating a unidirectional MPLS tunnel, you need to manually create a MPLS tunnel in the reverse direction. A.7.2.3 Creating a Bidirectional MPLS Tunnel During creation of a bidirectional MPLS tunnel, both the forward and reverse tunnels are created. A.7.2.4 Querying MPLS Tunnel Information You can learn about information about all MPLS tunnels configured for an NE. A.7.2.5 Deleting MPLS Tunnels If a tunnel is no longer used, you can delete it to free the corresponding transmission resources. A.7.2.6 Setting MPLS OAM Parameters This section describes how to set OAM parameters for MPLS tunnel availability test. A.7.2.7 Enabling/Disabling FDI When the FDI function of an NE is enabled, fault locating and protection switching can be performed more quickly. A.7.2.8 Starting/Stopping CV/FFD Detection for MPLS Tunnels Before enabling CV/FD detection, you need to set MPLS OAM parameters. A.7.2.9 Querying LSP Running Status This topic describes how to query the MPLS tunnel status detected by MPLS OAM. A.7.2.10 Clearing OAM Configuration Data for MPLS Tunnels This topic describes how to restart MPLS OAM detection by clearing MPLS OAM configuration data. A.7.2.11 Performing an LSP Ping Test This topic describes how to detect whether an MPLS tunnel is available. A.7.2.12 Performing an LSP Traceroute Test You can detect fault points on an MPLS tunnel by performing LSP traceroute tests.
A.7.2.1 Setting Basic MPLS Attributes

This topic describes how to set basic MPLS attributes, including the LSR ID and the global label space.
Prerequisite

U2000
Procedure
Step 1 In the NE Explorer, select the required NE from the Object Tree and choose Configuration > MPLS Management > Basic Configuration from the Function Tree. Step 2 Double-click LSR ID and set the LSR ID of the NE according to the planning information.
A-168
Issue 02 (2011-01-20)
A Task Collection
CAUTION
When services are available on an NE, a value change of LSR ID causes a reset of the NE and service interruption.
Step 3 Click Apply. A confirmation dialog box is displayed. Step 4 Click Yes. Then, close the dialog box that is displayed. ----End
Related References
B.8.1.1 Parameter Description: Basic Configurations of MPLS Tunnels
A.7.2.2 Creating a Unidirectional MPLS Tunnel

When creating a unidirectional MPLS tunnel, you need to manually create a MPLS tunnel in the reverse direction.
Prerequisite
l l l You must be an NM user with NE operator authority or higher. The port attributes are set correctly. The LSR ID of each NE is set correctly.

U2000
Procedure
Step 1 In the NE Explorer, select the required NE from the Object Tree and choose Configuration > MPLS Management > Unicast Tunnel Management from the Function Tree. Step 2 Click the Static Tunnel tab. Step 3 Click New and choose Unidirectional Tunnel from the drop-down list. Step 4 Select New Reverse Tunnel. Step 5 Set parameters for the new MPLS tunnel.
Issue 02 (2011-01-20)
A-169
A Task Collection
Related References
B.8.1.3 Parameter Description: Unicast Tunnel Management_Creation of Unidirectional Tunnels

During creation of a bidirectional MPLS tunnel, both the forward and reverse tunnels are created.
Prerequisite
l
A-170

A Task Collection
l l
The port attributes have been correctly configured. The LSR ID of each NE has been correctly configured.

U2000
Procedure
Step 1 In the NE Explorer, select the required NE from the Object Tree and choose Configuration > MPLS Management > Unicast Tunnel Management from the Function Tree. Step 2 Click the Static Tunnel tab. Step 3 Click New and choose Bidirectional Tunnel from the drop-down list. The New Unicast Bidirectional Tunnel dialog box is displayed. Step 4 Set parameters for the bidirectional MPLS tunnel.
Issue 02 (2011-01-20)
A-171
A Task Collection
Related References
B.8.1.4 Parameter Description: Unicast Tunnel Management_Creation of Bidirectional Tunnels
A.7.2.4 Querying MPLS Tunnel Information

You can learn about information about all MPLS tunnels configured for an NE.
Prerequisite
l l You must be an NM user with NE operator authority or higher. MPLS tunnels are configured correctly.

U2000
Procedure
Step 1 In the NE Explorer, select the required NE from the Object Tree and choose Configuration > MPLS Management > Unicast Tunnel Management from the Function Tree. Step 2 Click the Static Tunnel tab. Step 3 Click Query.Then, close the dialog box that is displayed. Step 4 View the information about all MPLS tunnels configured for the NE in the main interface. ----End
Related References
B.8.1.2 Parameter Description: Unicast Tunnel Management_Static Tunnel
A.7.2.5 Deleting MPLS Tunnels

If a tunnel is no longer used, you can delete it to free the corresponding transmission resources.
Prerequisite
l l You must be an NM user with NE operator authority or higher. An MPLS tunnel is configured correctly and is no longer used to transmit services.

U2000
A-172
Issue 02 (2011-01-20)
A Task Collection
Procedure
Step 1 In the NE Explorer, select the required NE from the Object Tree and choose Configuration > MPLS Management > Unicast Tunnel Management from the Function Tree. Step 2 Click the Static Tunnel tab. Step 3 Click Query.Then, close the dialog box that is displayed. Step 4 Select the required MPLS tunnel and click Delete. A confirmation dialog box is displayed. Step 5 Click Yes. Then, close the dialog box that is displayed. Step 6 Click Query and find that the selected MPLS tunnel does not exist. ----End
A.7.2.6 Setting MPLS OAM Parameters

This section describes how to set OAM parameters for MPLS tunnel availability test.
Prerequisite
l l l You must be an NM user with NE operator authority or higher. MPLS tunnels are created and enabled. Node Type is set to Ingress or Egress for tunnels.

U2000
Procedure
Step 1 In the NE Explorer, select the required NE from the Object Tree and choose Configuration > MPLS Management > Unicast Tunnel Management from the Function Tree. Step 2 Click the OAM Parameter tab. Step 3 Select the required MPLS tunnel and set MPLS OAM parameters.
Related References
B.8.1.5 Parameter Description: Unicast Tunnel Management_OAM Parameters
A.7.2.7 Enabling/Disabling FDI

When the FDI function of an NE is enabled, fault locating and protection switching can be performed more quickly.
A Task Collection
Prerequisite
l l You must be an NM user with NE operator authority or higher. MPLS tunnels are created and enabled.
Procedure
Step 1 In the NE Explorer, select the required NE from the Object Tree and choose Configuration > MPLS Management > Unicast Tunnel Management from the Function Tree. Step 2 Click the FDI tab. Step 3 Set Enable FDI based on the applications.
Related References
B.8.1.6 Parameter Description: Unicast Tunnel Management_FDI
A.7.2.8 Starting/Stopping CV/FFD Detection for MPLS Tunnels

Before enabling CV/FD detection, you need to set MPLS OAM parameters.
Prerequisite
l l You must be an NM user with NE operator authority or higher. The MPLS OAM function has been enabled and related parameters have been configured.

U2000
Procedure
Step 1 In the NE Explorer, select the required NE from the Object Tree and choose Configuration > MPLS Management > Unicast Tunnel Management from the Function Tree. Step 2 Click the OAM Parameter tab. Step 3 Select the required tunnel and click OAM Operation. Step 4 Select the required operation from the drop-down list. 1. 2. To enable CV/FFD detection, click Start CV/FFD. Then, close the dialog box that is displayed. To disable CV/FFD detection, click Stop CV/FFD. Then, close the dialog box that is displayed.
A-174

NOTE
A Task Collection
l For unidirectional tunnels, this operation task can be performed only for a tunnel whose Node Type is Ingress. l For bidirectional tunnels, this operation task cannot be performed if Node Type is Transit. l After the MPLS OAM function is enabled, CV/FFD detection is enabled by default.
TIP
l You can select more than one tunnel at a time by pressing and holding down the Ctrl key. l Alternatively, you can select the required tunnel, right-click the tunnel, and then select Start CV/ FFD or Stop CV/FFD from the drop-down list.
----End
A.7.2.9 Querying LSP Running Status

This topic describes how to query the MPLS tunnel status detected by MPLS OAM.
Prerequisite
l l You must be an NM user with NE operator authority or higher. The MPLS OAM detection function has been enabled.

U2000
Procedure
Step 1 In the NE Explorer, select the required NE from the Object Tree and choose Configuration > MPLS Management > Unicast Tunnel Management from the Function Tree. Step 2 Click the OAM Parameter tab. Step 3 Select the required tunnel and click OAM Operation at lower right of the main interface. Step 4 Select Query LSP Status from the drop-down list. Then, close the dialog box that is displayed. Step 5 Check the tunnel status according to the LSP Status parameter value in the main interface.
TIP
l You can select more than one tunnel at a time by pressing and holding down the Ctrl key. l Alternatively, you can select a tunnel, right-click the tunnel, and select LSP Status from the drop-down list.
----End
A Task Collection
A.7.2.10 Clearing OAM Configuration Data for MPLS Tunnels

This topic describes how to restart MPLS OAM detection by clearing MPLS OAM configuration data.
Prerequisite
l l l You must be an NM user with NE operator authority or higher. The MPLS OAM detection function has been enabled. The tunnel is not configured in any protection group.

U2000
Procedure
Step 1 In the NE Explorer, select the required NE from the Object Tree and choose Configuration > MPLS Management > Unicast Tunnel Management from the Function Tree. Step 2 Click the OAM Parameter tab. Step 3 Select the required tunnel and click OAM Operation at lower right of the main interface. Step 4 Select Clear OAM from the drop-down list. Then, close the dialog box that is displayed.
NOTE
After this step is performed, OAM parameters for the tunnel are restored to default values. If OAM operations need to be performed, you need to re-enable and configure the OAM functions.
TIP
l You can select more than one tunnel at a time by pressing and holding down the Ctrl key. l Alternatively, you can select a tunnel, right-click the tunnel, and select Clear OAM from the dropdown list.
----End
A.7.2.11 Performing an LSP Ping Test

This topic describes how to detect whether an MPLS tunnel is available.
Prerequisite

U2000
Procedure
Step 1 In the NE Explorer, select the required NE from the Object Tree and choose Configuration > MPLS Management > Unicast Tunnel Management from the Function Tree. Step 2 Click the OAM Parameters tab.
A Task Collection
Step 3 Select the required tunnel, click OAM Operation in the lower right corner, and choose Ping Test from the drop-down list.
NOTE
The test can be initiated only by an ingress node.

TIP
Alternatively, you can select a tunnel, right-click the tunnel, and select Ping Test from the drop-down list.
The Ping Test dialog box is displayed. Step 4 Set parameters for a ping test.
Step 5 Click Start Test to check the test result.

NOTE
l If LSP ping uses the IPv4 UDP response mode, all the nodes on the tunnel must support DCN communication over IP protocols. l To stop a test, click Stop Test.
----End
Related References
B.8.1.7 Parameter Description: Unicast Tunnel Management_LSP Ping
A.7.2.12 Performing an LSP Traceroute Test

You can detect fault points on an MPLS tunnel by performing LSP traceroute tests.
Prerequisite

U2000
Procedure
Step 1 In the NE Explorer, select the required NE from the Object Tree and choose Configuration > MPLS Management > Unicast Tunnel Management from the Function Tree.
A Task Collection
Step 2 Click the OAM Parameters tab. Step 3 Select the required tunnel, click OAM Operation in the lower right corner, and choose Traceroute Test from the drop-down list.
NOTE
The test can be initiated only by an ingress node.

TIP
Alternatively, you can select a tunnel, right-click the tunnel, and select Traceroute Test from the dropdown list.
The Traceroute Test dialog box is displayed. Step 4 Set parameters for the traceroute test.

NOTE
l If LSP traceroute uses the IPv4 UDP response mode, all the nodes on the tunnel must support DCN communication over IP protocols. l To stop a test, click Stop Test.
----End
Related References
B.8.1.8 Parameter Description: Unicast Tunnel Management_LSP Traceroute
A.7.3 Managing MPLS APS Protection Groups

MPLS APS is the commonest protection mode for MPLS tunnels. A.7.3.1 Creating an MPLS APS Protection Group An MPLS APS protection group needs to be configured if a service carried by an MPLS tunnel needs to be protected. A.7.3.2 Querying MPLS APS Status You can know current information about MPLS APS by querying MPLS APS status on the NMS. A.7.3.3 Triggering MPLS APS Switching This topic describes how to trigger an external PW APS switching. A.7.3.4 Enabling/Disabling MPLS APS Protection If you first stop the MPLS APS protection protocol and then start it, the MPLS APS protection protocol is restored to its initial state.
A Task Collection
A.7.3.1 Creating an MPLS APS Protection Group

An MPLS APS protection group needs to be configured if a service carried by an MPLS tunnel needs to be protected.
Prerequisite
l l l l l l You must be an NM user with NE operator authority or higher. The working and protection MPLS tunnels have been created. MPLS OAM as been enabled for both working and protection MPLS tunnel in the protection group. The MPLS OAM packet type has been set to FFD and the detection interval has been set to 3.3 ms. The protection tunnel cannot carry extra services. PW APS protection is not configured for the service.

U2000
Procedure
Step 1 In the NE Explorer, select the NE from the Object Tree and choose Configuration > APS Protection Management from the Function Tree. Step 2 Click the Tunnel APS Management tab. Step 3 Click New. The New Tunnel Protection Group dialog box is displayed. Step 4 Set parameters for the MPLS APS protection group.
NOTE
When creating an MPLS APS protection group, set Protocol Status to Disabled. Start the protocol only when the MPLS APS protection group is successfully created on nodes at both ends.
Issue 02 (2011-01-20)
A-179
A Task Collection
Related References
B.8.1.15 Parameter Description: Tunnel Protection Group_Creation
A.7.3.2 Querying MPLS APS Status

You can know current information about MPLS APS by querying MPLS APS status on the NMS.
Prerequisite
l l l You must be an NM user with NE operator authority or higher. The MPLS APS protection group has been created. The MPLS APS protocol has been enabled.

U2000
Procedure
Step 1 In the NE Explorer, select the required NE from the Object Tree and choose Configuration > APS Protection Management from the Function Tree.
A Task Collection
Step 2 Click the Tunnel APS Management tab. Step 3 Click Query, and then close the dialog box that is displayed. Check basic information about the protection group. Step 4 Select the required protection group and click Function. Step 5 Select Query Switching Status from the drop-down list. Then, close the dialog box that is displayed. Check the status of the protection group. ----End
Related References
B.8.1.14 Parameter Description: MPLS APS Protection Management
A.7.3.3 Triggering MPLS APS Switching

This topic describes how to trigger an external PW APS switching.
Prerequisite
l l l You must be an NM user with NE operator authority or higher. The MPLS APS protection group has been created. The MPLS APS protocol has been enabled.

U2000
Procedure
Step 1 In the NE Explorer, select the required NE from the Object Tree and choose Configuration > APS Protection Management from the Function Tree. Step 2 Click the Tunnel APS Management tab. Step 3 Select the required protection group, click Function, and then select the required switching mode from the drop-down list.
TIP
Alternatively, you can select the required protection group, right-click the protection group, and then select the required switching mode from the drop-down list.
Issue 02 (2011-01-20)
A-181
A Task Collection
Then, a confirmation dialog box is displayed. Step 4 Click OK. Then, close the dialog box that is displayed. Step 5 Click Function. Step 6 Select Query Switching Status from the drop-down list. Then, close the dialog box that is displayed. Check whether switching is performed successfully. ----End
A.7.3.4 Enabling/Disabling MPLS APS Protection

If you first stop the MPLS APS protection protocol and then start it, the MPLS APS protection protocol is restored to its initial state.
Prerequisite
l l You must be an NM user with NE operator authority or higher. The MPLS APS protection group has been created.

U2000
Procedure
Step 1 In the NE Explorer, select the required NE from the Object Tree and choose Configuration > APS Protection Management from the Function Tree. Step 2 Click the Tunnel APS Management tab. Step 3 Stop the MPLS APS protocol. 1. 2. Select the required protection group and click Function. Select Stop Protocol from the drop-down list.
CAUTION
After the MPLS APS protocol is stopped, the protection group fails. In addition, services are unavailable until the working channel is restored or the MPLS APS protocol is restarted, if services have been switched to the protection channel.
A-182
Issue 02 (2011-01-20)
A Task Collection
A confirmation dialog box is displayed. 3. Click Yes. Then, close the dialog box that is displayed.
Step 4 Start the MPLS APS protocol. 1. 2. Select the required protection group and click Function. Select Start Protocol from the drop-down list. Then, close the dialog box that is displayed.
TIP
Alternatively, you can select the required protection group, right-click the protection group, and choose Start Protocol or Stop Protocol from the shortcut menu.
----End
A.7.4 Managing PWs

All types of PWE3 services are carried by PWs. A.7.4.1 Querying Information and Running Status of PWs This topic describes how to query information and running status of PWs. A.7.4.2 Creating an MS-PW This topic describes how to configure cross-connections for front-end and rear-end PWs at an S-PE node and create an MS-PW. A.7.4.3 Setting PW OAM Parameters This topic describes how to set OAM parameters for PW availability test. A.7.4.4 Performing a PW Ping Test This topic describes how to detect whether a PW is available. A.7.4.5 Performing a PW Traceroute Test You can detect fault points on an MS-PW by performing PW traceroute tests.
A.7.4.1 Querying Information and Running Status of PWs

This topic describes how to query information and running status of PWs.
Prerequisite
l l You must be an NM user with NE operator authority or higher. PW-carried services have been configured.

U2000
Procedure
Step 1 In the NE Explorer, select the required NE from the Object Tree and choose Configuration > MPLS Management > PW Management from the Function Tree. Step 2 Click the PW Management tab. Step 3 Click Query Then, close the dialog box that is displayed.
A Task Collection
Step 4 In the main interface, check the basic information and running status of each PW. Step 5 After selecting a PW, to query other PW information, do as follows: 1. 2. Click the QoS Information tab and check QoS information of the PW. Click the Advanced Attributes tab and check the advanced attributes of the PW.
----End
Related References
B.8.1.9 Parameter Description: PW Management_PW Management
A.7.4.2 Creating an MS-PW

This topic describes how to configure cross-connections for front-end and rear-end PWs at an S-PE node and create an MS-PW.
Prerequisite

U2000
The steps for creating MS-PWs vary according to service types. This topic uses an Ethernet service as an example to describe how to create MS-PWs.
Procedure
Step 1 In the NE Explorer, select the required NE from the Object Tree and choose Configuration > MPLS Management > PW Management from the Function Tree. Step 2 Click the MS PW tab. Step 3 Click New. The Create MS PW dialog box is displayed. Step 4 In the main interface, configure basic service information.
Step 5 Click the PW Basic Attributes tab and set PW parameters.
A-184
Issue 02 (2011-01-20)
A Task Collection
Step 6 Click the QoS tab and set QoS parameters.
Step 7 Click the Advanced Attributes tab and set advanced attributes.
Related References
B.8.1.10 Parameter Description: PW Management_MS-PW Creation

This topic describes how to set OAM parameters for PW availability test.
Prerequisite
l
Issue 02 (2011-01-20)

A Task Collection
PW-carried services have been configured.

U2000
Procedure
Step 1 In the NE Explorer, select the required NE from the Object Tree and choose Configuration > MPLS Management > PW Management from the Function Tree. Step 2 Click the PW OAM Parameter tab. Step 3 Select the required PW and set PW OAM parameters.
Related References
B.8.1.11 Parameter Description: PW Management_PW OAM
A.7.4.4 Performing a PW Ping Test

This topic describes how to detect whether a PW is available.
Prerequisite
l l You must be an NM user with NE operator authority or higher. A PW has been created and enabled.

U2000
Procedure
Step 1 In the NE Explorer, select the required NE from the Object Tree and choose Configuration > MPLS Management > PW Management from the Function Tree. Step 2 Click the PW OAM Parameter tab. Step 3 Select the required PW and click OAM Operation > Ping Test.
TIP
Alternatively, you can select a PW, right-click the PW, and select Ping Test from the drop-down list.
The Ping Test dialog box is displayed. Step 4 Set parameters for a ping test.
A Task Collection

NOTE
l If PW ping/traceroute uses the IPv4 UDP response mode, all the nodes on the PW must support DCN communication over IP protocols. l To stop a test, click Stop Test.
----End
Related References
B.8.1.12 Parameter Description: PW Management_PW Ping
A.7.4.5 Performing a PW Traceroute Test

You can detect fault points on an MS-PW by performing PW traceroute tests.
Prerequisite
l l You must be an NM user with NE operator authority or higher. A PW has been created and enabled.

U2000
Procedure
Step 1 In the NE Explorer, select the required NE from the Object Tree and choose Configuration > MPLS Management > PW Management from the Function Tree. Step 2 Click the PW OAM Parameter tab. Step 3 Select the required PW, click OAM Operation in the lower right corner, and choose Traceroute Test from the drop-down list.
TIP
Alternatively, you can select a PW, right-click the PW, and select Traceroute Test from the drop-down list.
Issue 02 (2011-01-20)
A-187
A Task Collection
The Traceroute Test dialog box is displayed. Step 4 Set parameters for the traceroute test.

NOTE
l If PW ping/traceroute uses the IPv4 UDP response mode, all the nodes on the PW must support DCN communication over IP protocols. l To stop a test, click Stop Test.
----End
Related References
B.8.1.13 Parameter Description: PW Management_PW Traceroute
A.7.5 Managing a PW APS Protection Group

PW APS provides protection for PWs. A.7.5.1 Creating a PW APS Protection Group If MPLS APS cannot be configured to protect a PW-carried service, you can configure PW APS to protect the service. A.7.5.2 Configuring Slave Protection Pairs of PW APS During PW APS switching, the PWs in the slave protection pair are also switched. A.7.5.3 Querying PW APS Status You can know current information about a PW APS protection group by querying PW APS status on the NMS. A.7.5.4 Triggering PW APS Switching This topic describes how to trigger an external PW APS switching. A.7.5.5 Enabling/Disabling PW APS Protection If you first stop the PW APS protection protocol and then start it, the PW APS protection protocol is restored to its initial state.
A.7.5.1 Creating a PW APS Protection Group

If MPLS APS cannot be configured to protect a PW-carried service, you can configure PW APS to protect the service.
A-188
Issue 02 (2011-01-20)
A Task Collection
Prerequisite
l l l You must be an NM user with NE operator authority or higher. MPLS APS protection is not configured for the service. The tunnel carrying the working and protection PWs has been created.

U2000
CES services, ATM services, and E-Line services carried by PWs support PW APS. You can create a PW APS protection group during initial service configuration or after service configuration. l l l During initial service configuration, set Protection Type to PW APS, create the working and protection PWs, use the PWs to configure a PW APS protection group. If services are already configured, create the PW APS protection group in the Protection Group tab page. For SS-PWs and MS-PWs, configuration of the PW APS protection group needs to be done on both source NE and sink NE.
NOTE
l This topic describes how to configure PW APS after services are configured. l This topic uses a PW-carried E-Line service as an example to describe how to configure PW APS protection. The methods of configuring PW APS protection for other types of service are similar.
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Ethernet Service Management > E-Line Service from the Function Tree. Step 2 Select the required services and click the Protection Group tab. Step 3 Click PW APS. Step 4 Click New. The Configure PW dialog box is displayed. Step 5 Click the General Attributes tab and set the basic attributes of the protection PW.
Issue 02 (2011-01-20)
A-189
A Task Collection
Step 6 Click the Protection Group tab and set information about the PW APS protection group.
NOTE
When creating a PW APS protection group, set Enabling Status to Disabled. Start the protocol only when the PW APS protection group is successfully created on nodes at both ends.
Step 7 Click PW OAM and configure OAM information.

NOTE
l When the PW APS protection group is created, the PW OAM function is automatically enabled to detect the PW status. l You can also configure OAM information by choosing Configuration > MPLS Management > PW Management > PW OAM Parameter.
A-190
Issue 02 (2011-01-20)
A Task Collection
Related References
B.8.1.16 Parameter Description: PW APS Protection Group_Creation
A.7.5.2 Configuring Slave Protection Pairs of PW APS

During PW APS switching, the PWs in the slave protection pair are also switched.
Prerequisite
l l l l You must be an NM user with NE operator authority or higher. The mapping between a slave protection pair and a PW APS protection group has been specified. MPLS APS protection is not configured for the service. The tunnel carrying the working and protection PWs has been created.

U2000
CES services, ATM services, and E-Line services carried by PWs support PW APS slave protection pairs. The slave protection pairs are bound with a PW APS protection group. You can create a slave protection pair during initial service configuration or after service configuration. l l l During initial service configuration, set Protection Type to Slave Protection Pair, create the working and protection PWs, use the PWs to configure a slave protection pair. If services are already configured, create the slave protection pair in the Protection Group tab page. For SS-PWs and MS-PWs, binding of a slave protection pair to a PW APS protection group requires that the slave protection pair is added on both the source NE and sink NE.
NOTE
l This topic describes how to configure a slave protection pair after services are configured. l This topic uses a PW-carried E-Line service as an example to describe how to configure a slave protection pair. The methods of configuring slave protection pairs for other types of service are similar.
Issue 02 (2011-01-20)
A-191
A Task Collection
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Ethernet Service Management > E-Line Service from the Function Tree. Step 2 Select the required services and click the Protection Group tab. Step 3 Click Slave Protection Pair. Step 4 Click New. The Configure PW dialog box is displayed. Step 5 Click the General Attributes tab and set the basic attributes of the protection PW.
Step 6 Click the Protect Group tab and set the ID of the PW APS protection group to which the slave protection pair is bound.
NOTE
You can manually enter an ID, or double-click the ID parameter and select from the drop-down list.
Related References
B.8.1.17 Parameter Description: Slave Protection Pair of a PW APS Protection Group_Creation
A.7.5.3 Querying PW APS Status

You can know current information about a PW APS protection group by querying PW APS status on the NMS.
A Task Collection
Prerequisite
l l You must be an NM user with NE operator authority or higher. The PW APS protection group has been created.

U2000
Procedure
Step 1 In the NE Explorer, select the NE from the Object Tree and choose Configuration > APS Protection Management from the Function Tree. Step 2 Click the PW APS Management tab. Step 3 Click Query, and then close the dialog box that is displayed. Check basic information about the protection group.
NOTE
If a slave protection pair is configured, information about the slave protection pair is displayed at the lower part of the main interface after you select the protection group.
Step 4 Select the required protection group. Click Function > Query Switching Status, and then close the dialog box that is displayed. Check the status of the protection group. ----End
A.7.5.4 Triggering PW APS Switching

This topic describes how to trigger an external PW APS switching.
Prerequisite
l l l You must be an NM user with NE operator authority or higher. The PW APS protection group has been created. The PW APS protocol has been enabled.

U2000
Procedure
Step 1 In the NE Explorer, select the NE from the Object Tree and choose Configuration > APS Protection Management from the Function Tree. Step 2 Click the PW APS Management tab. Step 3 Select the required protection group, click Function, and then select the required switching mode from the drop-down list.
TIP
Alternatively, you can select the required protection group, right-click the protection group, and then select the required switching mode from the drop-down list.
Issue 02 (2011-01-20)
A-193
A Task Collection
Then, a confirmation dialog box is displayed. Step 4 Click OK. Then, close the dialog box that is displayed. Step 5 Click Function and choose Query Switching Status from the drop-down list. Then, close the dialog box that is displayed. Check whether switching is performed successfully. ----End
A.7.5.5 Enabling/Disabling PW APS Protection

If you first stop the PW APS protection protocol and then start it, the PW APS protection protocol is restored to its initial state.
Prerequisite
l l You must be an NM user with NE operator authority or higher. The PW APS protection group has been created.

U2000
Procedure
Step 1 In the NE Explorer, select the NE from the Object Tree and choose Configuration > APS Protection Management from the Function Tree. Step 2 Click the PW APS Management tab. Step 3 Stop the PW APS protocol. 1. 2. Select the required protection group and click Function. Select Stop Protocol from the drop-down list.
CAUTION
After the PW APS protocol is stopped, the protection group fails. In addition, services are unavailable until the working channel is restored or the PW APS protocol is restarted, if services have been switched to the protection channel.
A-194
Issue 02 (2011-01-20)
A Task Collection
A confirmation dialog box is displayed. 3. Click Yes Then, close the dialog box that is displayed.
Step 4 Start the PW APS protocol. 1. 2. Select the required protection group and click Function. Select Start Protocol from the drop-down list. Then, close the dialog box that is displayed.
TIP
You can enable or disable the PW APS protocol by using either of the following methods: l Select the required protection group, right-click the protection group, and choose Start Protocol or Stop Protocol from the short-cut menu. l Set Enabling Status to Enabled or Disabled.
----End
A.7.6 Managing CES Services

The OptiX RTN 980 supports PWE3-based CES services. A.7.6.1 Creating CES Services This topic describes how to create a CES service. During creation of a CES service, the PW for carrying the CES service is also created. A.7.6.2 Modifying CES Service Parameters This topic describes how to modify parameters related to CES services, such as CES alarm transparent transmission parameters. A.7.6.3 Querying CES Service Information This topic describes how to query information about a CES service. A.7.6.4 Deleting a CES Service. If a CES service is no longer used, you can delete it to free up the corresponding transmission resources. To delete a CES service, you need to delete the corresponding ACR clock configuration at both the source and sink nodes of the CES service. After the CES service is deleted, the corresponding PW is automatically deleted.
A.7.6.1 Creating CES Services

This topic describes how to create a CES service. During creation of a CES service, the PW for carrying the CES service is also created.
Prerequisite
l l You must be an NM user with NE operator authority or higher. The attributes of the UNI port that carries the CES service have been configured. That is, Port Mode has been set to Layer 1, and Frame Format and Frame Mode have also been configured. The MPLS tunnel that carries the PW has been configured.

U2000
A Task Collection
l Generally, UNI-NNI CES services are configured on the OptiX RTN 980. Therefore, this topic uses a UNI-NNI CES service as an example to describe how to configure CES services. It is recommended that you create protection information before creating a CES service. In this configuration example, Protection Type is set to No Protection. For details on how to configure protection information, see A.7.5.1 Creating a PW APS Protection Group and A.7.5.2 Configuring Slave Protection Pairs of PW APS.
Procedure
Step 1 In the NE Explorer, select the NE from the Object Tree and choose Configuration > CES Service Management from the Function Tree. Step 2 Click New. The Create CES Service dialog box is displayed. Step 3 Set Mode to UNI-NNI. Configure basic information about the CES service carried by a PW.
NOTE
l If Mode is UNI-NNI, you can configure QoS information and advanced attributes of the PW. l Set Protection Type to No Protection.
Step 4 Click Configure PW, and set the basic attributes of the PW.
A-196
Issue 02 (2011-01-20)
A Task Collection
Step 5 Click Advanced and set parameters for the advanced attributes.
Step 6 Click OK. Step 7 Click OK Then, close the dialog box that is displayed. ----End
Related References
B.8.2.2 Parameter Description: CES Service Management_Creation
A.7.6.2 Modifying CES Service Parameters

This topic describes how to modify parameters related to CES services, such as CES alarm transparent transmission parameters.
Prerequisite
l l
Issue 02 (2011-01-20)
You must be an NM user with NE operator authority or higher. CES services have been created.
A Task Collection

U2000
Procedure
Step 1 In the NE Explorer, select the NE from the Object Tree and choose Configuration > CES Service Management from the Function Tree. Step 2 Select the required CES service and click Query. Then, click the dialog box that is displayed. In the main interface, check basic service information. Step 3 Click PW General Attributes to query information about the PW that carry the service. Step 4 Modify advanced parameters. 1. 2. Click the Advanced Attributes tab. Select the required PW, double-click a required advance attribute, and change the attribute value. Click the Protection Group tab. Click PW APS. Change values of protection group parameters, such as Restoration Mode.
Step 5 Change protection group information. 1. 2. 3.
----End
Related References
B.8.2.1 Parameter Description: CES Service Management
A.7.6.3 Querying CES Service Information

This topic describes how to query information about a CES service.
Prerequisite
l l You must be an NM user with NE operator authority or higher. CES services have been created.

U2000
Procedure
Step 1 In the NE Explorer, select the NE from the Object Tree and choose Configuration > CES Service Management from the Function Tree. Step 2 Select the required CES service and click Query. Then, close the dialog box that is displayed. In the main interface, check basic service information. Step 3 Click PW General Attributes to query information about the PW that carry the service. Step 4 Click QoS to check the QoS information of the CES service.
A Task Collection
Step 5 Click Advanced Attributes to check advanced attributes of the CES service. Step 6 Click Protection Group to check whether a protection group is configured and to check information about the protection group if configured. ----End
Related References
A.7.6.4 Deleting a CES Service.

If a CES service is no longer used, you can delete it to free up the corresponding transmission resources. To delete a CES service, you need to delete the corresponding ACR clock configuration at both the source and sink nodes of the CES service. After the CES service is deleted, the corresponding PW is automatically deleted.
Prerequisite
l l l You must be an NM user with NE operator authority or higher. The CES service has been created and will no longer be used. No ACR clock has been configured for the CES service.
Procedure
Step 1 In the NE Explorer, select the NE from the Object Tree and choose Configuration > CES Service Management from the Function Tree. Step 2 Select the required CES service and click Delete. A confirmation dialog box is displayed. Step 3 Click OK. Then, close the dialog box that is displayed. Step 4 Click Query, and then close the dialog box that is displayed to check whether the CES service is successfully deleted. ----End
A.7.7 Managing ATM/IMA Ports

On the OptiX RTN 980, ATM/IMA ports are mapped into one ATM TRUNK. A.7.7.1 Binding ATM TRUNKs An ATM TRUNK can bind one or more E1 ports that transmit ATM/IMA services, or serial ports (SPs) that transmit ATM/IMA services. A.7.7.2 Configuring an IMA group If the ATM TRUNK binds IAM E1 links or Fractional IMA links, you need to configure the parameters of the IMA group. A.7.7.3 Setting ATM Port Parameters This topic describes how to configure ATM port parameters. A.7.7.4 Querying Running Status of an IMA Group This topic describes how to query the running status of an IMA group.
A Task Collection
A.7.7.5 Querying Link Running Status of an IMA Group This topic describes how to query the running status of the member links of an IMA group.
A.7.7.1 Binding ATM TRUNKs

An ATM TRUNK can bind one or more E1 ports that transmit ATM/IMA services, or serial ports (SPs) that transmit ATM/IMA services.
Prerequisite
l l l You must be an NM user with NE operator authority or higher. For ATM/IMA E1 services, set Port Mode in PDH Interface to Layer 2. For Fractional ATM/IMA services, set Port Mode in PDH Interface to Layer 1 and configure A.5.5 Setting Serial Port Parameters.

U2000
Procedure
Step 1 In the NE Explorer, select the NE from the Object Tree and choose Configuration > Interface Management > ATM IMA Management from the Function Tree. Step 2 Click the Binding tab. Step 3 Click Configuration. The Bound Path dialog box is displayed. Step 4 Configure the related parameters according to planning information. Then, click bind the required E1 ports or SPs to the ATM TRUNK. to
A-200
Issue 02 (2011-01-20)

NOTE
A Task Collection
l If ATM/IMA services need to be mapped into the ATM TRUNK that binds one or more E1 ports, select E1 in Level. l If ATM/IMA services need to be mapped into the ATM TRUNK that binds one or more serial ports, select Fractional E1 in Level.
Follow-up Procedure
If the IMA group is required, you need to bind the member links of the IMA group with the ATM TRUNK, enable the IMA protocol for the ATM TRUNK, and then configure the parameters of the IMA group.
Related References
B.8.3.2 Parameter Description: ATM IMA Management_Bound Path Configuration

If the ATM TRUNK binds IAM E1 links or Fractional IMA links, you need to configure the parameters of the IMA group.
Prerequisite

U2000
Procedure
Step 1 In the NE Explorer, select the NE from the Object Tree and choose Configuration > Interface Management > ATM IMA Management from the Function Tree. Step 2 Click the IMA Group Management tab. Step 3 Configure the parameters of the IMA group according to planning information.
Issue 02 (2011-01-20)
A-201
A Task Collection
NOTE
l Set IMA Protocol Enable Status to Enabled if the links bound in the ATM TRUNK require the IMA protocol; otherwise, set this parameter to Disabled. l After IMA Protocol Enable Status is set to Enabled, the E1 links or Fractional E1 timeslots bound in the ATM TRUNK start running the IMA protocol. l The values of Minimum Number of Active Transmitting Links and Minimum Number of Active Receiving Links must be the same because the OptiX RTN 980 supports Symmetrical Mode and Symmetrical Operation only. The parameters Minimum Number of Active Transmitting Links and Minimum Number of Active Receiving Links must assume the same value on the two ends of an IMA link. l On the two ends of the IMA link, you need to set IMA Protocol Version, IMA Transmit Frame Length, and Maximum Delay Between Links (ms) to the same values. l Clock Mode is set to the same value for the interconnected ends of IMA links.
Step 4 Click Apply, and close the dialog box that is displayed. ----End
Related References
B.8.3.1 Parameter Description: ATM IMA Management_IMA Group Management

This topic describes how to configure ATM port parameters.
Prerequisite

U2000
Procedure
Step 1 In the NE Explorer, select the NE from the Object Tree and choose Configuration > Interface Management > ATM IMA Management from the Function Tree. Step 2 Click the ATM Interface Management tab. Step 3 Configure and adjust the ATM port attributes.
A-202
Issue 02 (2011-01-20)

NOTE
A Task Collection
l UNI: the port connecting user-side devices. For example, the UNI port applies to the user-side interface on the common ATM network or to the user-side interface of the PE on the PSN network that transmits ATM PWE3 services. l NNI: the port connecting network-side devices. For example, the NNI port applies to the network-side interface on the common ATM network. l The ITU-T G.804 stipulates that the payload (48 bytes) of ATM cells must be scrambled before it is mapped into E1 signals. Therefore, it is recommended that you set ATM Cell Payload Scrambling to Enabled. l ATM Cell Payload Scrambling must assume the same value on the two ends of an ATM link. Otherwise, packet loss will occur.
Related References
B.8.3.5 Parameter Description: ATM IMA Management_ATM Interface Management
A.7.7.4 Querying Running Status of an IMA Group

This topic describes how to query the running status of an IMA group.
Prerequisite

U2000
Procedure
Step 1 In the NE Explorer, select the NE from the Object Tree and choose Configuration > Interface Management > ATM IMA Management from the Function Tree. Step 2 Click the IMA Group States tab.Then, close the dialog box that is displayed. Step 3 Click Query, and then close the dialog box that is displayed. Step 4 Query the running status of an IMA group. ----End
Related References
B.8.3.3 Parameter Description: ATM IMA Management_IMA Group Status
A.7.7.5 Querying Link Running Status of an IMA Group

This topic describes how to query the running status of the member links of an IMA group.
Prerequisite
A Task Collection

U2000
Procedure
Step 1 In the NE Explorer, select the NE from the Object Tree and choose Configuration > Interface Management > ATM IMA Management from the Function Tree. Step 2 Click the IMA Link States tab.Then, close the dialog box that is displayed. Step 3 Click Query, and then close the dialog box that is displayed. Step 4 Query the running status of the member links of an IMA group. ----End
Related References
B.8.3.4 Parameter Description: ATM IMA Management_IMA Link Status
A.7.8 Managing ATM Services

The OptiX RTN 980 supports common ATM services (UNI-UNI) and PW-carried ATM services (UNI-NNI). A.7.8.1 Creating ATM Services To create common ATM services, you only need to configure ATM connections and CoS mapping. To create ATM PWE3 services, you also need to configure the PW that carries ATM services. A.7.8.2 Modifying ATM Service Parameters This topic describes how to modify ATM service parameters. A.7.8.3 Querying ATM Services This topic describes how to query ATM services. A.7.8.4 Deleting an ATM Service This topic describes how to delete an ATM service. If an ATM service is no longer used, you can delete it to release its resources.
A.7.8.1 Creating ATM Services

To create common ATM services, you only need to configure ATM connections and CoS mapping. To create ATM PWE3 services, you also need to configure the PW that carries ATM services.
Prerequisite
l l You must be an NM user with NE operator authority or higher. Generally, UNIs-NNI ATM services are configured on the OptiX RTN 980. Therefore, this topic uses a UNIs-NNI ATM service as an example to describe how to configure ATM PWE3 services. Before creating ATM PWE3 services, you need to bind member links to the ATM TRUNK, set the parameters of the IMA group, and create the MPLS tunnels that carries PWs.
A-204
A Task Collection

U2000
l l To create ATM PWE3 services (UNIs-NNI), it is recommended that you create services before configuring PW protection. Configuration will be simplified in this manner. In this configuration example, Protection Type is set to No Protection. For details on how to configure PW protection, see A.7.5.1 Creating a PW APS Protection Group and A. 7.5.2 Configuring Slave Protection Pairs of PW APS.
Procedure
Step 1 In the NE Explorer, select the NE from the Object Tree and choose Configuration > ATM Service Management from the Function Tree. Step 2 Click New. The New ATM Service dialog box is displayed. Step 3 Configure the basic information about the ATM PWE3 service according to the planning information.
Step 4 Click the Connection tab and configure the attributes of the ATM connection.
NOTE
For ATM PWE3 services, it is recommended that you set the VPIs/VCIs to the same value for the source and sink of the ATM connection.
Issue 02 (2011-01-20)
A-205
A Task Collection
Step 5 Click PW, and click Add to configure the attributes of PWs. 1. Click the General Attributes tab and set the basic attributes of PWs.
2.
Click the QoS tab and enable the PW bandwidth restriction.
3.
Click the Advanced Attributes tab to configure the advanced attributes of PWs.
4.
Click OK, and close the dialog box that is displayed.
Step 6 Click the CoS Mapping tab and click Add to configure the CoS mapping of PWs.
Step 7 Click OK, and close the dialog box that is displayed. Step 8 Click OK, and close the dialog box that is displayed. ----End
A-206
Issue 02 (2011-01-20)
A Task Collection
Related References
B.8.3.11 Parameter Description: ATM Service Management_Creation
A.7.8.2 Modifying ATM Service Parameters

This topic describes how to modify ATM service parameters.
Prerequisite
l l You must be an NM user with NE operator authority or higher. ATM PWE3 services are already created and their parameters need to be modified according to the planning information.

U2000
Procedure
Step 1 In the NE Explorer, select the NE from the Object Tree and choose Configuration > ATM Service Management from the Function Tree. Step 2 Click Query, and close the dialog box that is displayed. Step 3 Select the required ATM service and modify the parameters of the ATM service. Step 4 Click Apply, and close the dialog box that is displayed. ----End
Related References
B.8.3.10 Parameter Description: ATM Service Management
A.7.8.3 Querying ATM Services

This topic describes how to query ATM services.
Prerequisite

U2000
Procedure
Step 1 In the NE Explorer, select the NE from the Object Tree and choose Configuration > ATM Service Management from the Function Tree. Step 2 Click Query, and close the dialog box that is displayed.
A Task Collection
Step 3 Select the required ATM service and query the parameters of the ATM service. ----End
Related References
A.7.8.4 Deleting an ATM Service

This topic describes how to delete an ATM service. If an ATM service is no longer used, you can delete it to release its resources.
Prerequisite

U2000
Procedure
Step 1 In the NE Explorer, select the NE from the Object Tree and choose Configuration > ATM Service Management from the Function Tree. Step 2 Click Query, and close the dialog box that is displayed. Step 3 Select the required ATM service and click Delete. Step 4 In the confirmation dialog box, click OK. Step 5 After the service is deleted, close the dialog box that is displayed. ----End
A.7.9 ATM Traffic Management

ATM traffic management includes ATM-Diffserv management and ATM policy management. A.7.9.1 Creating an ATM-DiffServ Domain This topic describes how to create an ATM-DiffServ domain. If the default ATM-Diffserv domain does not serve the purpose, a new ATM-Diffserv needs to be created. A.7.9.2 Modifying an ATM-Diffserv Domain This topic describes how to modify an ATM-Diffserv domain. By performing this operation, you can modify the mapping relationship between ATM service types and PHB service classes. A.7.9.3 Creating an ATM Policy This topic describes how to create an ATM policy for an ATM connection. A.7.9.4 Modifying an ATM Policy This topic describes how to modify the QoS parameters of an ATM policy.
A Task Collection
A.7.9.1 Creating an ATM-DiffServ Domain

This topic describes how to create an ATM-DiffServ domain. If the default ATM-Diffserv domain does not serve the purpose, a new ATM-Diffserv needs to be created.
Prerequisite

U2000
Procedure
Step 1 In the NE Explorer, select the NE from the Object Tree and choose Configuration > QoS Management > Diffserv domain Management > ATM COS Mapping Configuration from the Function Tree. Step 2 Click New. The New ATM CoS Mapping dialog box is displayed. Step 3 Configure the ATM-Diffserv domain according to the planning information.
NOTE
l Eight PHB service classes are available: BE, AF1, AF2, AF3, AF4, EF, CS6, and CS7. The OptiX RTN 980 provides different QoS policies for the queues of different service classes. l CS6 to CS7: highest service classes, mainly applicable to signaling transmission. l EF: fast forwarding, applicable to services of low transmission delays and low packet loss rates. l AF1 to AF4: assured forwarding, applicable to services that require an assured transmission rate rather than delay or jitter limits.
NOTE
The AF1 class includes three subclasses: AF11, AF12, and AF13. Only one of these subclasses can take effect for one queue. It is the same case with AF2, AF3, and AF4. l BE: best effort, applicable to services that do not require special processing.
Issue 02 (2011-01-20)
A-209
A Task Collection
Step 4 Click OK, and close the dialog box that is displayed. ----End
Related References
B.8.3.7 Parameter Description: Configuration of ATM Service Class Mapping Table_Creation
A.7.9.2 Modifying an ATM-Diffserv Domain

This topic describes how to modify an ATM-Diffserv domain. By performing this operation, you can modify the mapping relationship between ATM service types and PHB service classes.
Prerequisite

U2000
Procedure
Step 1 In the NE Explorer, select the NE from the Object Tree and choose Configuration > QoS Management > Diffserv domain Management > ATM COS Mapping Configuration from the Function Tree. Step 2 Click Query, and close the dialog box that is displayed. Step 3 Select the required ATM-Diffserv domain and modify its parameters according to the planning information.
A-210
Issue 02 (2011-01-20)
A Task Collection
NOTE
l Eight PHB service classes are available: BE, AF1, AF2, AF3, AF4, EF, CS6, and CS7. The OptiX RTN 980 provides different QoS policies for the queues of different service classes. l CS6 to CS7: highest service classes, mainly applicable to signaling transmission. l EF: fast forwarding, applicable to services of low transmission delays and low packet loss rates. l AF1 to AF4: assured forwarding, applicable to services that require an assured transmission rate rather than delay or jitter limits.
NOTE
The AF1 class includes three subclasses: AF11, AF12, and AF13. Only one of these subclasses can take effect for one queue. It is the same case with AF2, AF3, and AF4. l BE: best effort, applicable to services that do not require special processing.
Related References
B.8.3.6 Parameter Description: Configuration of ATM Service Class Mapping Table
A.7.9.3 Creating an ATM Policy

This topic describes how to create an ATM policy for an ATM connection.
A Task Collection
Prerequisite

U2000
Procedure
Step 1 In the NE Explorer, select the NE from the Object Tree and choose Configuration > QoS Management > Policy Management > ATM Policy from the Function Tree. Step 2 Click New. The Create ATM Policy dialog box is displayed. Step 3 Configure the parameters of the ATM policy according to the planning information.
Related References
B.8.3.9 Parameter Description: ATM Policy Management_Creation
A.7.9.4 Modifying an ATM Policy

This topic describes how to modify the QoS parameters of an ATM policy.
Prerequisite
A Task Collection

U2000
Procedure
Step 1 In the NE Explorer, select the NE from the Object Tree and choose Configuration > QoS Management > Policy Management > ATM Policy from the Function Tree. Step 2 Click Query, and close the dialog box that is displayed. Step 3 Select the required ATM policy and modify its parameters according to the planning information. Step 4 Click Apply, and close the dialog box that is displayed. ----End
Related References
B.8.3.8 Parameter Description: ATM Policy Management
A.7.10 Using ATM OAM

ATM OAM is an OAM mechanism that is used for detecting and locating ATM faults, and monitoring ATM performance. A.7.10.1 Setting Segment and End Attributes of AIS/RDI This topic describes how to set the segment and end attributes of AIS/RDI. A.7.10.2 Performing a Continuity Check Test This topic describes how to perform a continuity check (CC) test. A CC test can be performed to continuously check the unidirectional connectivity of an ATM link. A.7.10.3 Querying or Setting LLIDs This topic describes how to query or set locate loopback IDs (LLIDs). LLIDs need to be configured before an LB test. A.7.10.4 Performing an LB Test This topic describes how to perform a loopback (LB) test. An LB test can be performed to continuously check the bidirectional connectivity of an ATM link.
A.7.10.1 Setting Segment and End Attributes of AIS/RDI

This topic describes how to set the segment and end attributes of AIS/RDI.
Prerequisite

U2000
A Task Collection
Procedure
Step 1 In the NE Explorer, select the NE from the Object Tree and choose Configuration > ATM OAM Management from the Function Tree. Step 2 Click the Segment End Attributes tab. Step 3 Set the segment and end attributes of AIS/RDI according to the planning information.
Related References
B.8.3.12 Parameter Description: ATM OAM Management_Segment and End Attributes
A.7.10.2 Performing a Continuity Check Test

This topic describes how to perform a continuity check (CC) test. A CC test can be performed to continuously check the unidirectional connectivity of an ATM link.
Prerequisite

U2000
Procedure
Step 1 In the NE Explorer, select the NE from the Object Tree and choose Configuration > ATM OAM Management from the Function Tree. Step 2 Click the CC Activation Status tab. Step 3 Configure the parameters of the CC test according to the planning information.
Related References
B.8.3.13 Parameter Description: ATM OMA Management_CC Activation Status
A Task Collection
A.7.10.3 Querying or Setting LLIDs

This topic describes how to query or set locate loopback IDs (LLIDs). LLIDs need to be configured before an LB test.
Prerequisite

U2000
Procedure
Step 1 In the NE Explorer, select the NE from the Object Tree and choose Configuration > ATM OAM Management from the Function Tree. Step 2 Click the LLID tab. Step 3 Set the LLIDs according to the planning information.
Related References
B.8.3.15 Parameter Description: ATM OAM Management_LLID

This topic describes how to perform a loopback (LB) test. An LB test can be performed to continuously check the bidirectional connectivity of an ATM link.
Prerequisite

U2000
Procedure
Step 1 In the NE Explorer, select the NE from the Object Tree and choose Configuration > ATM OAM Management from the Function Tree. Step 2 Click the Remote Loopback Test tab. Step 3 Configure the attributes of the LB test according to the planning information. Step 4 Select an ATM connection for which an LB test needs to be performed.
A Task Collection
TIP
By pressing the Ctrl key on the keyboard, you can select multiple ATM connections at one time.
Step 5 Click Test, and close the dialog box that is displayed. Step 6 Check Test Result.
----End
Related References
B.8.3.14 Parameter Description: ATM OAM Management_Remote End Loopback Status
A.8 Managing the Clock

To ensure the clock synchronization between transmission nodes on a transport network, you need to manage the NE clock. A.8.1 Managing Clocks at the Physical Layer This section describes how to synchronize clock signals by transmission of reference clock signals at the physical layer. A.8.2 Managing CES ACR Clocks CES ACR refers to a function that uses the adaptive clock recovery (ACR) technology to recover clock synchronization information carried by CES packets.
A.8.1 Managing Clocks at the Physical Layer

This section describes how to synchronize clock signals by transmission of reference clock signals at the physical layer. A.8.1.1 Configuring the Clock Sources This topic describes how to configure the clock source according to the planned clock synchronization scheme to ensure that all the NEs on the network trace the same clock. A.8.1.2 Configuring Clock Subnets For simple networks, such as chain networks, you need not configure the clock source protection or you only need to configure the clock priority to implement the clock source protection. For complex networks, such as ring networks or intersecting and tangent rings that are derived from ring networks, you need to configure clock subnets and enable the standard SSM protocol or extended SSM protocol to implement the clock source protection. A.8.1.3 Self-Defined Clock Quality By default, the NE considers the clock quality extracted from the clock source as the clock quality. If the clock quality is zero (the synchronization quality is unknown), the clock is considered as unavailable clock. In the case of any special requirements, the user can define the clock quality for which the source clock quality and clock quality are zero. A.8.1.4 Configuring the SSM Output Status After the SSM protocol is enabled or extended, the NE transmits the SSM to other NEs through the SDH radio link or optical line by default. To prevent two clock subnets from affecting each
A Task Collection
other, the NE needs to forbid the SSM bytes from being transmitted on the link that is connected to other clock subnets. A.8.1.5 Configuring the Clock ID Output Status After the SSM protocol is enabled or is extended, the NE transmits the clock ID to other NEs through the radio link or optical line by default. To prevent two clock subnets from affecting each other, the NE needs to forbid the clock ID from being transmitted on the link that is connected to other clock subnets. A.8.1.6 Modifying the Parameters of the Clock Output The NE outputs the 2-Mbit/s external clock regardless of the clock quality. A.8.1.7 Changing the Conditions for Clock Source Switching You can change the default conditions for clock source switching of the NE for special purposes. A.8.1.8 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.1.9 Querying the Clock Synchronization Status You can know the current clock synchronization status of an NE by querying the clock synchronization status.
A.8.1.1 Configuring the Clock Sources

This topic describes how to configure the clock source according to the planned clock synchronization scheme to ensure that all the NEs on the network trace the same clock.
Prerequisite

U2000
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Clock > Physical Clock > Clock Source Priority. Step 2 Click the System Clock Source Priority List tab. Step 3 Click Create. The Add Clock Source dialog box is displayed. Step 4 Select the clock sources.
TIP
By pressing the Ctrl key on the keyboard, you can select multiple clock sources at one time.
Step 5 Click OK. Step 6 Optional: Repeat Step 3 to Step 5 to add other clock sources. Step 7 Optional: Select a clock source and click clock source.
Issue 02 (2011-01-20)
or
to adjust the priority of this
A-217
A Task Collection
NOTE
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 8 Optional: Set External Clock Source Mode and Synchronous Status Byte for the external clock sources.
Related References
B.9.2.1 Parameter Description: Clock Source Priority Table
A.8.1.2 Configuring Clock Subnets

For simple networks, such as chain networks, you need not configure the clock source protection or you only need to configure the clock priority to implement the clock source protection. For complex networks, such as ring networks or intersecting and tangent rings that are derived from ring networks, you need to configure clock subnets and enable the standard SSM protocol or extended SSM protocol to implement the clock source protection.
Prerequisite
l l You must be an NM user with NE operator authority or higher. The priority list of the clock source must be configured.

U2000
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Clock > Physical Clock > Clock Subnet Configuration. Step 2 Click the Clock Subnet tab. Step 3 Start the clock protection protocol and configure its parameters.

A Task Collection
Related References
B.9.2.2 Parameter Description: Clock Subnet Setting_Clock Subnet
A.8.1.3 Self-Defined Clock Quality

By default, the NE considers the clock quality extracted from the clock source as the clock quality. If the clock quality is zero (the synchronization quality is unknown), the clock is considered as unavailable clock. In the case of any special requirements, the user can define the clock quality for which the source clock quality and clock quality are zero.
Prerequisite
l l You must be an NM user with NE operator authority or higher. The priority level of a clock source must be set.

U2000
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Clock > Physical Clock > Clock Subnet Configuration. Step 2 Click the Clock Quality tab. Step 3 Click the Clock Source Quality tab. Step 4 Set the self-defined clock quality.
NOTE
Generally, it is recommended that you use the default value.
Step 5 Click Apply. Step 6 Click the Manual Setting of 0 Quality Level tab. Step 7 Set the clock quality for which the quality level is zero.
NOTE
Generally, it is recommended that you use the default value.
Related References
B.9.2.3 Parameter Description: Clock Subnet Setting_Clock Quality
A Task Collection
A.8.1.4 Configuring the SSM Output Status

After the SSM protocol is enabled or extended, the NE transmits the SSM to other NEs through the SDH radio link or optical line by default. To prevent two clock subnets from affecting each other, the NE needs to forbid the SSM bytes from being transmitted on the link that is connected to other clock subnets.
Prerequisite
l l l You must be an NM user with NE operator authority or higher. The priority level of a clock source must be set. The SSM protocol must be enabled or extended.

U2000
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Clock > Physical Clock > Clock Subnet Configuration. Step 2 Click the SSM Output Control tab. Step 3 Set the SSM control status.
Related References
B.9.2.4 Parameter Description: Clock Subset Setting_SSM Output Control
A.8.1.5 Configuring the Clock ID Output Status

After the SSM protocol is enabled or is extended, the NE transmits the clock ID to other NEs through the radio link or optical line by default. To prevent two clock subnets from affecting each other, the NE needs to forbid the clock ID from being transmitted on the link that is connected to other clock subnets.
Prerequisite
l l l You must be an NM user with NE operator authority or higher. The priority level of a clock source must be set. The extended SSM protocol must be enabled.

U2000
A Task Collection
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Clock > Physical Clock > Clock Subnet Configuration. Step 2 Click the Clock ID Status tab. Step 3 Set the clock ID control status.
Related References
B.9.2.5 Parameter Description: Clock Subset Setting_Clock ID Enabling Status
A.8.1.6 Modifying the Parameters of the Clock Output

The NE outputs the 2-Mbit/s external clock regardless of the clock quality.
Prerequisite

U2000
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Clock > Physical Clock > Phase-Locked Source Output by External Clock. Step 2 Modify the parameters of the clock output. Step 3 Click Apply. ----End
Related References
B.9.2.9 Parameter Description: Output Phase-Locked Source of the External Clock Source
A.8.1.7 Changing the Conditions for Clock Source Switching

You can change the default conditions for clock source switching of the NE for special purposes.
Prerequisite
A Task Collection

U2000
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Clock > Physical Clock > Clock Source Switching. Step 2 Click the Clock Source Switching Condition tab. Step 3 Change the conditions for clock source switching.
Related References
B.9.2.8 Parameter Description: Clock Source Switching_Clock Source Switching Conditions
A.8.1.8 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

U2000
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Clock > Physical Clock > Clock Source Switching. Step 2 Click the Clock Source Reversion Parameter tab. Step 3 Set the recovery parameter of the clock source.
Related References
B.9.2.6 Parameter Description: Clock Source Switching_Clock Source Restoration Parameters
A Task Collection
A.8.1.9 Querying the Clock Synchronization Status

You can know the current clock synchronization status of an NE by querying the clock synchronization status.
Prerequisite

U2000
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Clock > Physical Clock > Clock Synchronization Status. Step 2 Query the clock synchronization status. ----End
Related References
B.9.2.10 Parameter Description: Clock Synchronization Status
A.8.2 Managing CES ACR Clocks

CES ACR refers to a function that uses the adaptive clock recovery (ACR) technology to recover clock synchronization information carried by CES packets. A.8.2.1 Configuring the Primary Clock for an ACR Clock Domain An ACR clock domain can use the clock extracted from a CES service as its primary clock. A.8.2.2 Configuring Ports Using the Clock Domain An CES E1 port can transmit the clock information in the system clock domain or CES ACR clock domain.

An ACR clock domain can use the clock extracted from a CES service as its primary clock.
Prerequisite
l l You must be an NM user with NE administrator authority or higher. CES services are configured.
Issue 02 (2011-01-20)
A-223
A Task Collection
Precautions
CAUTION
l An ACR clock domain can bind only the CES services from the E1 ports on a local board. l On the MD1 board, the four ACR clock domains can bind the CES services either from the former 16 E1 ports or from the latter 16 E1 ports on a local board. That is, the four ACR clock domains cannot simultaneously bind the CES services from the former 16 E1 ports and from the latter 16 E1 ports on a local board. l A maximum of four ACR clock domains can bind CES services.

U2000
Procedure
Step 1 In the NE Explorer, select the required NE from the Object Tree and choose Configuration > Clock > ACR Clock from the Function Tree. Step 2 In CES Service, select an CES service for primary clock extraction.
Related References
B.9.3.1 Parameter Description: ACR Clock Source
A.8.2.2 Configuring Ports Using the Clock Domain

An CES E1 port can transmit the clock information in the system clock domain or CES ACR clock domain.
Prerequisite
l l You must be an NM user with NE administrator authority or higher. CES services are configured.
A-224
Issue 02 (2011-01-20)
A Task Collection
Precautions
CAUTION
l E1 ports output clocks from the system clock domain by default. Therefore, it is unnecessary to set application ports to the system clock domain if system clocks are to be used. l An ACR clock domain can only be applied to the E1 ports on a local board. l The E1 ports corresponding to the primary clock for an ACR clock domain must be added to the ACR clock domain. l On the MD1 board, the four ACR clock domains can bind the CES services either from the former 16 E1 ports or from the latter 16 E1 ports on a local board. That is, the four ACR clock domains cannot simultaneously bind the CES services from the former 16 E1 ports and from the latter 16 E1 ports on a local board.

U2000
Procedure
Step 1 In the NE Explorer, select the required NE from the Object Tree and choose Configuration > Clock > Clock Domain from the Function Tree. Step 2 Click New. The Create Clock Domain Port dialog box is displayed.
Step 3 In Clock Domain Board, select the board where the ACR clock domain resides. Step 4 Select Clock Domain. Step 5 Set the application ports to the ACR clock domain. 1.
Issue 02 (2011-01-20)
In Board, select a board that uses the ACR clock domain.

A Task Collection
2. 3.
In Available Port, select a port that transmits CES services. Click .
Related References
B.9.3.3 Parameter Description: Clock Domain_Creation
A.9 Using the RMON

The 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.9.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.9.2 Configuring an Alarm Group for an Ethernet Port After you configure an RMON alarm group for an Ethernet port, you can monitor whether the performance value of the port crosses the configured thresholds in the long term. A.9.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. A maximum of 50 historical performance entries can be saved. A.9.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.9.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 You must be an NM user with NE operator authority or higher. The corresponding board must be added in the NE Panel.

U2000
A-226
Issue 02 (2011-01-20)
A Task Collection
Procedure
Step 1 Select the corresponding board from the Object Tree in the 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
Related References
B.7.1 Parameter Description: RMON Performance_Statistics Group
A.9.2 Configuring an Alarm Group for an Ethernet Port

After you configure an RMON alarm group for an Ethernet port, you can monitor whether the performance value of the port crosses the configured thresholds in the long term.
Prerequisite
l l You must be an NM user with NE operator authority or higher. The corresponding boards must be added in the NE Panel.

U2000
Procedure
Step 1 Select the corresponding board from the Object Tree in the NE Explorer. Choose Performance > RMON Performance from the Function Tree. Step 2 Click the RMON Setting tab. Step 3 Click the Object tab and set the corresponding parameters. Step 4 Click the Event tab and set the corresponding parameters. Step 5 Click Apply. Then, close the dialog box that is displayed. ----End
Related References
B.7.4 Parameter Description: RMON Performance_RMON Setting
A.9.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. A maximum of 50 historical performance entries can be saved.
Prerequisite
l l You must be an NM user with NE operator authority or higher. The corresponding boards must be added in the NE Panel.

U2000
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Performance > RMON History Control Group. Step 2 Set the parameters of the history control group. Step 3 Click Apply. Then, close the dialog box that is displayed. ----End
Related References
B.7.3 Parameter Description: RMON Performance_History Control Group
A.9.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 You must be an NM user with NE operator authority or higher. The corresponding boards must be added in the NE Panel. The objects and performance events to be monitored must be set.

U2000
Procedure
Step 1 Select the corresponding board from the Object Tree in the NE Explorer. Choose Performance > RMON Performance from the Function Tree. Step 2 Click the History Group tab. Step 3 Set the parameters of the history group. Step 4 Click Apply. ----End
A Task Collection
Related References
A.10 Configuring Auxiliary Ports and Functions

The auxiliary ports and functions supported by the OptiX RTN 980 include the orderwire, synchronous data service, asynchronous data service, wayside E1 service, and external alarm. A.10.1 Configuring the Orderwire The orderwire for an NE provides a dedicated communication channel that the network maintenance personnel can use. A.10.2 Configuring the Synchronous Data Service The OptiX RTN 980 supports the transmission of a channel of 64-kbit/s synchronous data service through a user-defined byte in the microwave frame or the F1 overhead byte in the STM-N frame. Such a service is also called F1 data port service. A.10.3 Configuring the Asynchronous Data Service The OptiX RTN 980 supports the transmission of a channel of asynchronous data service with a maximum rate of 64 kbit/s through a user-defined byte in the microwave frame or any byte within the range of SERIAL1-SERIAL4 in the STM-N frame. Such a service is also called broadcast data port service. A.10.4 Configuring the Wayside E1 Service The OptiX RTN 980 supports the transmission of a channel of 2.048-Mbit/s wayside E1 service through 32 user-defined bytes in the SDH microwave frame. A.10.5 Configure External Alarms After the outputting of external alarms is configured, the alarm information of the OptiX RTN 980 can be output to other equipment. After the inputting of external alarms is configured, the alarm information of other equipment can be input to the OptiX RTN 980.
A.10.1 Configuring the Orderwire

The orderwire for an NE provides a dedicated communication channel that the network maintenance personnel can use.
Prerequisite

U2000
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Orderwire from the Function Tree. Step 2 Click the General tab. Step 3 Configure the orderwire information.
A Task Collection
Step 4 Click Apply. Step 5 Optional: Change the overhead bytes occupied by the orderwire. 1. 2. Click the Advanced tab. Configure Orderwire Occupied Bytes.
3.
Click Apply.
----End
Related References
B.10.1 Parameter Description: Orderwire_General B.10.2 Parameter Description: Orderwire_Advanced
A.10.2 Configuring the Synchronous Data Service

The OptiX RTN 980 supports the transmission of a channel of 64-kbit/s synchronous data service through a user-defined byte in the microwave frame or the F1 overhead byte in the STM-N frame. Such a service is also called F1 data port service.
Prerequisite
l l You must be an NM user with NE operator authority or higher. The board involved in the synchronous data service must be configured.

U2000
A-230
Issue 02 (2011-01-20)
A Task Collection
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Orderwire from the Function Tree. Step 2 Click the F1 Data Port tab. Step 3 Hold on the Ctrl key, select two data channels from Available Data Path, and then click .
Related References
B.10.3 Parameter Description: Orderwire_F1 Data Port
A.10.3 Configuring the Asynchronous Data Service

The OptiX RTN 980 supports the transmission of a channel of asynchronous data service with a maximum rate of 64 kbit/s through a user-defined byte in the microwave frame or any byte within the range of SERIAL1-SERIAL4 in the STM-N frame. Such a service is also called broadcast data port service.
Prerequisite
l l You must be an NM user with NE operator authority or higher. The board involved in the asynchronous data service must be configured.

U2000
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Orderwire from the Function Tree. Step 2 Click the Broadcast Data Port tab.
A Task Collection
Step 3 Configure the parameters of the broadcast data port.
Related References
B.10.4 Parameter Description: Orderwire_Broadcast Data Port
A.10.4 Configuring the Wayside E1 Service

The OptiX RTN 980 supports the transmission of a channel of 2.048-Mbit/s wayside E1 service through 32 user-defined bytes in the SDH microwave frame.
Prerequisite
l l l You must be an NM user with NE operator authority or higher. The IF1 board must be added on the NE Panel. The DCC channels corresponding to external clocks must be disabled.

U2000
The wayside E1 service can be supported by the IF1 board in the 7,STM-1,28MHz,128QAM, 8,E3,28MHz,QPSK, or 9,E3,14MHz,16QAM mode.
A-232
Issue 02 (2011-01-20)
A Task Collection
Procedure
Step 1 Select the corresponding board from the Object Tree in the NE Explorer. Choose Configuration > IF Interface from the Function Tree. Step 2 Click the IF Attributes tab. Step 3 Configure the enable status of the wayside E1 service and set the slot that houses the board.
Related References
A.10.5 Configure External Alarms

After the outputting of external alarms is configured, the alarm information of the OptiX RTN 980 can be output to other equipment. After the inputting of external alarms is configured, the alarm information of other equipment can be input to the OptiX RTN 980.
Prerequisite
l l You must be an NM user with NE operator authority or higher. The AUX board must be added on the NE Panel.

U2000
Context
The external alarms of the OptiX RTN 980 are also considered as housekeeping alarms. The external alarm port of the OptiX RTN 980 is a relay port. This port can be either in the "on" state or in the "off" state. The alarm input ports report the RELAY_ALARM alarm (the alarm parameter indicates the port number of the input alarm) after the external alarm is triggered. To ensure that the external alarm port works normally, the external alarm cables must be correctly connected.
Procedure
Step 1 Select the AUX board from the Object Tree in the NE Explorer. Choose Configuration > Environment Monitor Configuration > Environment Monitor Interface from the Function Tree. Step 2 Configure the input alarm. 1. 2.
Issue 02 (2011-01-20)
Select Input Relay from the drop-down list. Configure the parameters of the input alarm.
A Task Collection
3. 1. 2.
Click Apply, and then close the dialog box that is displayed. Select Output Relay from the drop-down list. Configure the parameters of the output alarm.
Step 3 Configure the output alarm.
3.
Click Apply, and then close the dialog box that is displayed.
----End
Related References
B.10.5 Parameter Description: Environment Monitoring Interface
A.11 Verifying Services and Features

This topic describes how to verify service and feature configurations. A.11.1 Testing the E1 Service Through PRBS If no BER tester is available, you can test the E1 service by using the PRBS test system embedded in the equipment. A.11.2 Testing the E1 Service by Using a BER Tester If a BER tester is available, the BER tester can be used to test the E1 service. A.11.3 Testing the Ethernet Service By testing the Ethernet service, you can check whether the Ethernet service is available over radio links. The Ethernet service can be tested through the ETH-OAM function. Thus, no tester is required. A.11.4 Testing the ATM Service By testing the ATM service, you can check whether the ATM service is available over radio links. The ATM service can be tested through the ATM OAM function. Thus, no tester is required. A.11.5 Testing the AM Switching By testing the AM switching, you can check whether the AM switching is normal over radio links. A.11.6 Testing the Protection Switching By testing the protection switching, you can check whether the protection switching is normal over radio links.
A-234
Issue 02 (2011-01-20)
A Task Collection
A.11.1 Testing the E1 Service Through PRBS

If no BER tester is available, you can test the E1 service by using the PRBS test system embedded in the equipment.
Prerequisite
l l The NE equipment must be configured with E1 services, and the E1 services must be transmitted through the DDF. The communication between the NMS and the NE must be normal.

U2000
Precautions
CAUTION
l When a PRBS test is performed, the services carried on the tested path are interrupted. l The PRBS test can be performed only in a unidirectional manner and on one path at a time. l CES services do not support a PRBS test.
Procedure
Step 1 On the NMS, perform an inloop for the corresponding E1 port at the remote site. 1. 2. 3. 4. 5. 6. 7. 8. Select the PDH interface board in the Object Tree. In the Function Tree, choose Configuration > PDH Interface. Select By Function and select Tributary Loopback from the drop-down menu. In Tributary Loopback, select Inloop. Click Apply. The Confirm dialog box is displayed. Click OK. The Confirm dialog box is displayed. Click OK. The Operation Result dialog box is displayed. Click Close.
Step 2 At the central site, on the NMS, select the PDH interface board in the Object Tree. Step 3 In the Function Tree, choose Configuration > PRBS Test. Step 4 Select the first E1 port, and then set the following PRBS-related parameters: l Direction: Cross l Duration: a value from 120 to 180 l Measured in Time: seconds
A Task Collection
Step 5 Click Start to Test. The system displays a dialog box indicating The operation may interrupt the service, Are you sure to continue? Step 6 Click OK. Step 7 When the Progress column is 100%, click Query to check the test result. The curve diagram should be green. Step 8 Release the inloop set in Step 1. 1. 2. 3. 4. 5. 6. 7. 8. Select the PDH interface board in the Object Tree. In the Function Tree, choose Configuration > PDH Interface. Select By Function and select Tributary Loopback from the drop-down menu. In Tributary Loopback, select Non-Loopback. Click Apply. The Confirm dialog box is displayed. Click OK. The Confirm dialog box is displayed. Click OK. The Operation Result dialog box is displayed. Click Close.
Step 9 Repeat Step 1 through Step 8 to test all other E1 ports. ----End
A.11.2 Testing the E1 Service by Using a BER Tester

If a BER tester is available, the BER tester can be used to test the E1 service.
Prerequisite
The NE must be configured with E1 services, and the E1 services must be transmitted through the DDF.

l l
A-236
U2000 BER tester


NOTE
A Task Collection
For a test of CES services in CES/PSN mode, a BER tester supporting Nx64 Kbps timeslot setting is necessary.
Procedure
Step 1 On the DDF at the central site, connect the BER tester to the first E1 port of the IDU. The BER tester indicates the AIS alarm. Figure A-1 Connecting the BER tester
DDF
RX TX
RX
TX
. . . .
1 2 3 4
BER tester
Step 2 On the NMS, perform an inloop for the corresponding E1 port at the remote site. 1. 2. 3. 4. 5. 6. 7. 8. Select the PDH interface board in the Object Tree. In the Function Tree, choose Configuration > PDH Interface. Select By Function and select Tributary Loopback from the drop-down menu. In Tributary Loopback, select Inloop. Click Apply. The Confirm dialog box is displayed. Click OK. The Confirm dialog box is displayed. Click OK. The Operation Result dialog box is displayed. Click Close. Step 3 Test the bit errors for two minutes. There should be no bit errors.
NOTE
For a test of CES services, it is necessary to configure 64 Kbps timeslots on a BER tester to align with the timeslots carrying CES services.
Step 4 Release the inloop set in Step 2. 1. 2.

Issue 02 (2011-01-20)
Select the PDH interface board in the Object Tree. In the Function Tree, choose Configuration > PDH Interface.
A Task Collection
3. 4. 5. 6. 7. 8.
Select By Function and select Tributary Loopback from the drop-down menu. In Tributary Loopback, select Non-Loopback. Click Apply. The Confirm dialog box is displayed. Click OK. The Confirm dialog box is displayed. Click OK. The Operation Result dialog box is displayed. Click Close.
Step 5 Repeat Step 1 through Step 4 to test all other E1 ports. ----End
A.11.3 Testing the Ethernet Service

By testing the Ethernet service, you can check whether the Ethernet service is available over radio links. The Ethernet service can be tested through the ETH-OAM function. Thus, no tester is required.
Prerequisite
Ethernet services must be configured.
NOTE
l It is recommended that you test low-priority Ethernet services in good weather conditions, where the AM function works in the highest modulation mode. l The tested Ethernet service can be the Native Ethernet service, or the Ethernet service carried by PWs.

U2000
Test Connection Diagram

The following test procedure considers the Ethernet service from PORT2 on NE2 and PORT3 on NE3 to PORT1 on NE1 as an example, as shown in Figure A-2. Figure A-2 Networking diagram for testing the Ethernet service
NE 2 PORT 2
VLAN ID=100 PORT 1 NE 1
NE 3 Microwave network
PORT 3
VLAN ID=200
A-238
Issue 02 (2011-01-20)
A Task Collection
The VLAN ID of the Ethernet service from NE2 to NE1 is 100, and the VLAN ID of the Ethernet service from NE3 to NE1 is 200.
Procedure
Step 1 Configure the maintenance domains of NE1, NE2, and NE3. 1. 2. 3. Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Ethernet OAM Management > Ethernet Service OAM Management from the Function Tree. Choose New > New Maintenance Domain. The New Maintenance Domain dialog box is displayed. Configure the parameters of the new maintenance domains. l Maintenance Domain Name: MD1 for NE1, NE2, and NE3 l Maintenance Domain Level: 4 for NE1, NE2, and NE3
NOTE
The maintenance domain names and the maintenance domain levels of the NEs must be the same.
4. 1. 2.
Click OK to close the displayed dialog box. Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Ethernet OAM Management > Ethernet Service OAM Management from the Function Tree. Select the maintenance domain in which a maintenance association needs to be created. Choose New > New Maintenance Association. The New Maintenance Association dialog box is displayed. Configure the parameters of the new maintenance associations. l Maintenance Association Name: MA1 for NE1, NE2, and NE3 l Relevant Service: services from NE1 to NE2 and NE3
NOTE
Step 2 Configure the maintenance associations of NE1, NE2, and NE3.
3.
Click in Relevant Service, and select relevant services in the New Maintenance Association dialog box.
4.
Issue 02 (2011-01-20)
Click OK to close the displayed dialog box.

A Task Collection
Step 3 Configure the MEPs of NE1, NE2, and NE3. 1. 2. 3. Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Ethernet OAM Management > Ethernet Service OAM Management from the Function Tree. Click the Maintenance Association tab. Select the maintenance association in which an MEP needs to be created. Choose New > New MEP Point. The system displays the New MEP Point dialog box. Configure the parameters of the new MEPs. l MP ID: 101 for NE1, 102 for NE2, and 103 for NE3 l Direction: Ingress for NE1, NE2, and NE3 l CC Status: activation for NE1, NE2, and NE3
4.
5. 1. 2. 3. 4.
Click OK to close the displayed dialog box. Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Ethernet OAM Management > Ethernet Service OAM Management from the Function Tree. Click the Maintenance Association tab. Choose OAM > Manage Remote MEP Point. Then, the Manage Remote MEP Point dialog box is displayed. Click New. Then, the Add Maintenance Association Remote Maintenance Point dialog box is displayed. Set the parameters of the new remote MEPs. l Remote Maintenance Point ID: 102 and 103 for NE1, and 101 for NE2 and NE3
NOTE
Step 4 Configure the remote MEPs for the maintenance associations of NE1, NE2, and NE3.
5.
Set the Remote Maintenance Point ID of NE1 to the MP ID of NE2 and NE3, and set the Remote Maintenance Point ID of NE2 and NE3 to the MP ID of NE1.
6.
A-240
Click OK to close the displayed dialog box.

A Task Collection
Step 5 Test the availability of the Ethernet services from NE1 to NE2 and NE3. 1. 2. 3. 4. Select an NE from the Object Tree in the NE Explorer of the NE1, and then choose Configuration > Ethernet OAM Management > Ethernet Service OAM. Select the MD, MA, and MEP that correspond to Port 1, click OAM. Select Start LB. The LB Test window is displayed. Select Destination Maintenance Point ID, and set the parameters in Test Node. l Source Maintenance Point ID: 101 (maintenance point ID of NE1) l Destination Maintenance Point ID: 102 (maintenance point ID of NE2) l Transmitted Packet Count: 20 (recommended) l Transmitted Packet Length: 64 (64 is a recommended value, and the parameter can also be set to 128, 256, 512, 1024, and 1280 for testing the Ethernet services of different packet lengths.)
NOTE
The maximum Packet Length is 1400.
l Transmitted Packet Priority: 7 (recommended)
5. 6.
Click Start Test. Check Detection Result. The LossRate in the Detection Result should be 0.
7.
Repeat Step 5.4 to Step 5.6 to test the Ethernet services from NE1 to NE3. l Source Maintenance Point ID: 101 (maintenance point ID of NE1) l Destination Maintenance Point ID: 103 (maintenance point ID of NE3) l Transmitted Packet Count: 20 (recommended) l Transmitted Packet Length: 64 (recommended) l Transmitted Packet Priority: 7 (recommended)
Issue 02 (2011-01-20)
A-241
A Task Collection
The LossRate in the Detection Result should be 0. ----End
A.11.4 Testing the ATM Service

By testing the ATM service, you can check whether the ATM service is available over radio links. The ATM service can be tested through the ATM OAM function. Thus, no tester is required.
Prerequisite
l l End-to-end ATM services must be configured. You must be an NM user with NE operator authority or higher.

U2000
When an LB test is performed on the ATM service, the segment and end attribute is set to specify the types of transmitted ATM OAM cells. l l When Segment End Attribute is set to Segment point, segment LB cells are transmitted. When Segment End Attribute is set to Endpoint, end-to-end LB cells are transmitted.

This example shows how to test the ATM service over a radio link hop. The method for testing the ATM services over multiple radio link hops is the same. Figure A-3 shows the test connection diagram. NE A and NE B are the OptiX RTN 980. The services of the boards on the NE1 and NE2 are configured as follows: Attribute UNI Service source Bound port NE A 3-MD1-1 (Trunk-1) 3-MD1-1 (Port-1) 3-MD1-2 (Port-2) VPI VCI NNI PW ID Service source Bound port VPI VCI 1 51 1 101 501 NE B 3-MD1-1 (Trunk-1) 3-MD1-1 (Port-1) 3-MD1-2 (Port-2) 101 501 1 101 501
A-242
Issue 02 (2011-01-20)
A Task Collection
Figure A-3 Connection diagram for testing the connectivity of the ATM service
UNI VPI 1 VCI 51 NNI VPI 101 VCI 501 VPI 101 NNI VCI 501 UNI VPI 101 VCI 501
NodeB
NE A
NE B
RNC
Procedure
Step 1 Set the segment and end attributes of the ATM services on the NE A and NE B. 1. 2. 3. 4. 5. In the NE Explorer, select an NE and then choose Configuration > ATM OAM Management from the Function Tree. Click the Segment and End Attribute tab, and choose the ATM service to be tested. As for NE A and NE B, set Segment and End Attribute to Segment point. As for NE A and NE B, set Connection Direction to Backward. Click Apply.
Step 2 Set the identifier at the loopback point from NE A to NE B. 1. 2. In the NE Explorer, select an NE and then choose Configuration > ATM OAM Management from the Function Tree. Click the LLID tab. Set Country Code, Network Code, and NE Code. Set the parameters of NE A as follows: l Set Country Code to 00 86. l Set Network Code to 00 16. l Set NE Code to 00 09 78 01 00 00 00 00 00 00 00. Set the parameters of NE B as follows: l Set Country Code to 00 86. l Set Network Code to 00 16. l Set NE Code to 00 09 78 02 00 00 00 00 00 00 00.
NOTE
If the default LLID is unique on a network, the default LLID can also be used.
3. 4.
Click Apply. Click Close.
Step 3 Test the ATM service from NE A to NE B. 1. 2.

Issue 02 (2011-01-20)
In the NE Explorer, select NE A and then choose Configuration > ATM OAM Management from the Function Tree. Click the Remote Loopback Test tab, and choose the ATM service to be tested.
A Task Collection
3. 4. 5.
Set Loopback Point NE of the ATM service to be tested to NE B. Click Test to start an LB test. In normal situations, Test Result should be Test succeeded. If the test is not successful, see Maintenance Guide and rectify the fault based on the test result.
Step 4 Test the ATM service from NE B to NE A. 1. 2. 3. 4. 5. 6. With reference of Step 1, set Connection Direction of NE A to Backward; set Connection Direction of NE B to Forward. Select NE B from the NE Explorer. Then, choose Configuration > ATM OAM Management from the Function Tree. Click the Remote Loopback Test tab, and choose the ATM service to be tested. Set Loopback Point NE of the ATM service to be tested to NE B. Click Test to start an LB test. In normal situations, Test Result should be Test succeeded. If the test is not successful, see Maintenance Guide and rectify the fault based on the test result. ----End
A.11.5 Testing the AM Switching

By testing the AM switching, you can check whether the AM switching is normal over radio links. A.11.5.1 Testing the AM Switching by Using a BER Tester If a BER tester is available, the BER tester can be used to test the AM switching. A.11.5.2 Testing the AM Switching Without a BER Tester If no BER tester is available, you can test the AM switching by querying the bit errors over radio links.
A.11.5.1 Testing the AM Switching by Using a BER Tester

If a BER tester is available, the BER tester can be used to test the AM switching.
Prerequisite
l l l l Aligning the antennas must be complete. The radio links must be the Integrated IP radio links for which the AM function is enabled. The E1 service must be configured. The weather is favorable.

l l U2000 BER tester
Precautions
The following test procedure considers the E1 service between NEs as an example.
A Task Collection
Procedure
Step 1 Connect the BER tester to an E1 port on the local NE.
NOTE
Test the E1 services with the highest priority, which are not discarded in the lowest-order modulation mode.
Step 2 On the remote NE, perform an inloop at the E1 port by using the NMS. 1. 2. 3. 4. 5. 6. 7. 8. Select the PDH interface board in the Object Tree. In the Function Tree, choose Configuration > PDH Interface. Select By Function and select Tributary Loopback from the drop-down menu. In Tributary Loopback, select Inloop. Click Apply. The Confirm dialog box is displayed. Click OK. The Confirm dialog box is displayed. Click OK. The Operation Result dialog box is displayed. Click Close.
Step 3 Configure the Hybrid/AM attribute on the local NE. 1. 2. 3. 4. Select the IF board from the NE Explorer, and then choose Configuration > IF Interface from the Function Tree. Click the IF Attributes tab. On the local NE, set the AM attribute to Disable, and set Manually Specified Modulation Mode to the same value as Modulation Mode of the Guarantee AM Capacity. Click Apply.
Step 4 Querying the AM working status on the local NE. 1. 2. 3. Select the IF board from the NE Explorer, and then choose Configuration > IF Interface from the Function Tree. Click the IF Attributes tab. Click Query. Transmit-End Modulation Mode should be Manually Specified Modulation Mode of a pre-set value.
Step 5 Use the BER tester to test the bit errors. The test result should show that no bit error occurs. Step 6 Configure the Hybrid/AM attribute to the planned values on the local NE. 1. 2.
Issue 02 (2011-01-20)
Select the IF board from the NE Explorer, and then choose Configuration > IF Interface from the Function Tree. Click the IF Attributes tab.
A Task Collection
3.
On the local NE, set the AM attribute to Enable, and set Modulation Mode of the Guarantee AM Capacity and Modulation Mode of the Full AM Capacity to the planned values. Click Apply.
4.
Step 7 Querying the AM working status on the local NE. 1. 2. 3. Select the IF board from the NE Explorer, and then choose Configuration > IF Interface from the Function Tree. Click the IF Attributes tab. Click Query. Transmit-End Modulation mode should be Modulation Mode of the Full AM Capacity of a preset value.
NOTE
In the case of unfavorable weather, the current modulation mode may be lower than the value of Modulation Mode of the Full AM Capacity.
Step 8 Check the BER test result. There should be no bit errors. Step 9 Release the inloop set in Step 2. 1. 2. 3. 4. 5. 6. 7. 8. Select the PDH interface board in the Object Tree. In the Function Tree, choose Configuration > PDH Interface. Select By Function and select Tributary Loopback from the drop-down menu. In Tributary Loopback, select Non-Loopback. Click Apply. The Confirm dialog box is displayed. Click OK. The Confirm dialog box is displayed. Click OK. The Operation Result dialog box is displayed. Click Close.
----End
A.11.5.2 Testing the AM Switching Without a BER Tester

If no BER tester is available, you can test the AM switching by querying the bit errors over radio links.
Prerequisite
l l l
A-246
Aligning the antennas must be complete. The radio links must be the Integrated IP radio links for which the AM function is enabled. The weather is favorable.
A Task Collection

U2000
Procedure
Step 1 Configure the Hybrid/AM attribute on the local NE. 1. 2. 3. 4. Select the IF board from the NE Explorer, and then choose Configuration > IF Interface from the Function Tree. Click the IF Attributes tab. On the local NE, set the AM attribute to Disable, and set Manually Specified Modulation Mode to the same value as Modulation Mode of the Guarantee AM Capacity. Click Apply.
Step 2 Query the 15-minute performance value of the IF board on the local NE. 1. 2. 3. 4. 5. 6. Select the required IF board from the Object Tree in NE Explorer. In the Function Tree, choose Performance > Current Performance. In Monitored Object Filter Condition, select All. Set Monitor Period to 15-Minute. In Count, select Other Errors. In Display Options, select Consecutive Severely Errored Seconds Second. Click Query. In performance events, the value of FEC_BEF_COR_ER should be 0.
Step 3 Querying the AM working status on the local NE. 1. 2. 3. Select the IF board from the NE Explorer, and then choose Configuration > IF Interface from the Function Tree. Click the IF Attributes tab. Click Query. Transmit-End Modulation Mode should be Manually Specified Modulation Mode of a pre-set value.
Step 4 Reset the performance event register. 1. 2. 3. 4. Select the required IF board from the Object Tree in NE Explorer. In the Function Tree, choose Performance > Current Performance. Click Reset. The confirmation dialog box is displayed. Click OK.
Step 5 Configure the Hybrid/AM attribute to the planned values on the local NE.
A Task Collection
1. 2. 3.
Select the IF board from the NE Explorer, and then choose Configuration > IF Interface from the Function Tree. Click the IF Attributes tab. On the local NE, set the AM attribute to Enable, and set Modulation Mode of the Guarantee AM Capacity and Modulation Mode of the Full AM Capacity to the planned values. Click Apply.
4.
Step 6 Repeat Step 2. Wait for a period, and query the 15-minute performance value of the IF board on the local NE. In performance events, the value of FEC_BEF_COR_ER should be 0. Step 7 Querying the AM working status on the local NE. 1. 2. 3. Select the IF board from the NE Explorer, and then choose Configuration > IF Interface from the Function Tree. Click the IF Attributes tab. Click Query. Transmit-End Modulation mode should be Modulation Mode of the Full AM Capacity of a preset value.
NOTE
In the case of unfavorable weather, the current modulation mode may be lower than the value of Modulation Mode of the Full AM Capacity.
----End
A.11.6 Testing the Protection Switching

By testing the protection switching, you can check whether the protection switching is normal over radio links. A.11.6.1 Testing the IF 1+1 Switching You can verify whether the IF 1+1 protection works normally by checking the working board of the IF 1+1 protection group before and after the switching. A.11.6.2 Testing the N+1 Protection Switching You can verify whether the IF N+1 protection works normally by checking the working board of the IF N+1 protection group before and after the switching. A.11.6.3 Testing the SNCP Switching You can verify whether the SNCP works normally by checking the working port of the SNCP protection group before and after the switching. A.11.6.4 Testing the ERPS You can verify whether the ERPS works normally by checking the port status of the ERPS protection group before and after the switching. A.11.6.5 Testing the MPLS APS Protection Switching By checking the change in the status of the MPLS tunnels before and after the MPLS APS switching, you can verify whether the MPLS APS protection function is normal. A.11.6.6 Testing the Two-Fiber Bidirectional MSP Switching
A Task Collection
By checking the change in the current working port in a ring MSP switching before and after switching, to verify whether the two-fiber bidirectional MSP function is normal. A.11.6.7 Testing the Linear MSP Switching You can verify whether the linear MSP group works normally by checking the working port of the linear MSP group before and after the switching. A.11.6.8 Switching the System Control Unit and the Cross-Connect Unit When the OptiX RTN 980 is configured with two system control, cross-connect, and timing boards, you can manually switch the system control unit and the cross-connect unit as required.
A.11.6.1 Testing the IF 1+1 Switching

You can verify whether the IF 1+1 protection works normally by checking the working board of the IF 1+1 protection group before and after the switching.
Prerequisite
l l l Aligning the antennas is complete. The equipment is configured with the IF 1+1 protection. The E1 service is configured.


Figure A-4 Configuration for testing the IF 1+1 switching NE A and NE B are configured as follows: l l l l Main IF board: ISU2 in slot 3 Standby IF board: ISU2 in slot 5 Main ODU: ODU in slot 53 Standby ODU: ODU in slot 55
NE A
NE B
As shown in Figure A-4, the following procedures consider the E1 service between NE A and NE B that is configured with the 1+1 HSB protection as an example.
A Task Collection
Precautions
NOTE
If no BER tester is available on site, you can compare the values of Active Board of Device or Active Board of Channel in Protection Group before the protection switching occurs and after the protection switching is complete.
Procedure
Step 1 Check whether a BER tester is available at the central site. If... A BER tester is available on site No BER tester is available on site Then... Perform Step 2 to Step 11. Perform Step 6 to Step 10.
Step 2 At the central site NE A, connect one E1 port to the BER tester. Step 3 At the remote site NE B, perform a software inloop at the E1 port by using the NMS. 1. 2. 3. 4. 5. 6. 7. 8. Select the PDH interface board in the Object Tree. In the Function Tree, choose Configuration > PDH Interface. Select By Function and select Tributary Loopback from the drop-down menu. In Tributary Loopback, select Inloop. Click Apply. The Confirm dialog box is displayed. Click OK. The Confirm dialog box is displayed. Click OK. The Operation Result dialog box is displayed. Click Close.
Step 4 Test the BER by using the BER tester. The BER tester should show that no bit errors occur. Step 5 Set Enable Reverse Switching in the 1+1 HSB protection group for NE A. 1. 2. 3. 1. 2. 3. Select the required NE from the Object Tree in the NE Explorer of NE A, and then choose Configuration > IF 1+1 Protection from the Function Tree. Select the corresponding protection group in Protection Group, and set Enable Reverse Switching to Enable. Click Apply. Select the NE from the Object Tree in the NE Explorer of NE A, and then choose Configuration > IF 1+1 Protection from the Function Tree. Select the corresponding protection group in Protection Group, and then click Query. In Protection Group, the value of Active Board of Device should be the main IF board 3-ISU2.
Step 6 Before the switching, query the status of the protection group that is configured on NE A.
A-250
Issue 02 (2011-01-20)
A Task Collection
Step 7 Set TX Status to mute for the main ODU 53-ODU of NE A. 1. 2. 3. 4. Select the NE from the Object Tree in the NE Explorer of NE A, and then choose Configuration > Link Configuration from the Function Tree. Click the IF/ODU Configuration tab. Select the required ODU, and set TX Status to mute. Click Apply.
Step 8 Check the availability of the service after the switching. If... A BER tester is available on site Then... Check the test result on the BER tester. It should show that the service is restored after a transient interruption.
No BER tester is available on site, and the See A.11.1 Testing the E1 Service Through E1 service is transmitted on the radio link. PRBS to test the availability of the E1 service. No BER tester is available on site, and the See A.11.3 Testing the Ethernet Service to Ethernet service is transmitted on the radio test the availability of the Ethernet service. link. Step 9 After the switching, query the status of the protection group that is configured on NE A. 1. 2. 3. Select the NE from the Object Tree in the NE Explorer of NE A, and then choose Configuration > IF 1+1 Protection from the Function Tree. Select the corresponding protection group in Protection Group, and then click Query. In Protection Group, the value of Active Board of Device should be the standby IF board 5-ISU2.
Step 10 Set TX Status to Unmute for the main ODU 53-ODU of NE A. 1. 2. 3. 4. 1. 2. 3. 4. 5. 6. 7. Select the NE from the Object Tree in the NE Explorer of NE A, and then choose Configuration > Link Configuration from the Function Tree. Click the IF/ODU Configuration tab. Select the required ODU, and set TX Status to Unmute. Click Apply. Select the PDH interface board in the Object Tree. In the Function Tree, choose Configuration > PDH Interface. Select By Function and select Tributary Loopback from the drop-down menu. In Tributary Loopback, select Non-Loopback. Click Apply. The Confirm dialog box is displayed. Click OK. The Confirm dialog box is displayed. Click OK. The Operation Result dialog box is displayed.
Step 11 Release the loopback set in Step 3.
Issue 02 (2011-01-20)
A Task Collection
8.
Click Close.
Step 12 Restore the setting of Enable Reverse Switching in Step 5. 1. 2. 3. Select the required NE from the Object Tree in the NE Explorer of NE A, and then choose Configuration > IF 1+1 Protection from the Function Tree. Select the corresponding protection group in Protection Group, and set Enable Reverse Switching to Disable. Click Apply.
----End
A.11.6.2 Testing the N+1 Protection Switching

You can verify whether the IF N+1 protection works normally by checking the working board of the IF N+1 protection group before and after the switching.
Prerequisite
l l Aligning the antennas must be complete. The equipment must be configured with the N+1 protection.


Figure A-5 Configuration for testing the N+1 protection NE A and NE B are configured as follows: l l l l Main IF boards: ISU2 in slot 3 and ISU2 in slot 5 Standby IF board: ISU2 in slot 4 Main ODUs: ODU in slot 53 and ODU in slot 55 Standby ODU: ODU in slot 54
NE A
NE B
As shown in Figure A-5, the following procedures consider the E1 service between NE A and NE B that is configured with the N+1 (N=2) configuration as an example.
A Task Collection
Precautions
NOTE
If no BER tester is available on site, you can compare the values of Switching Status in Slot Mapping Relation before the protection switching occurs and after the protection switching is complete.
Procedure
Step 2 At the central site NE A, connect one E1 port to the BER tester. Step 3 At the remote site NE B, perform a software inloop at the E1 port by using the NMS. 1. 2. 3. 4. 5. 6. 7. 8. Select the PDH interface board in the Object Tree. In the Function Tree, choose Configuration > PDH Interface. Select By Function and select Tributary Loopback from the drop-down menu. In Tributary Loopback, select Inloop. Click Apply. The Confirm dialog box is displayed. Click OK. The Confirm dialog box is displayed. Click OK. The Operation Result dialog box is displayed. Click Close. Step 4 Test the BER by using the BER tester. The BER tester should show that no bit errors occur. Step 5 Before the switching, query the status of the protection group that is configured on NE B. 1. 2. 3. Select the NE from the Object Tree in the NE Explorer of NE B, and then choose Configuration > N+1 protection from the Function Tree. Select the ID of the protection group to be queried, and then click Query. In Slot Mapping Relation, Switching Status of the working units 3-ISU2-1 and 5ISU2-1 and the protection unit 4-ISU2-1 should be Normal.
NOTE
If a fault arises, you must rectify the fault and then proceed with the N+1 protection testing.
Step 6 Set TX Status to mute for the main ODU 53-ODU of NE A. 1. Select the NE from the Object Tree in the NE Explorer of NE A, and then choose Configuration > Link Configuration from the Function Tree.
Issue 02 (2011-01-20)
A Task Collection
2. 3. 4.
Click the IF/ODU Configuration tab. Select the required ODU, and set TX Status to mute. Click Apply.
No BER tester is available on site, and the See A.11.1 Testing the E1 Service Through E1 service is transmitted on the radio link. PRBS to test the availability of the E1 service. No BER tester is available on site, and the See A.11.3 Testing the Ethernet Service to Ethernet service is transmitted on the radio test the availability of the Ethernet service. link. Step 8 After the switching, query the status of the protection group that is configured on NE B. 1. 2. 3. Select the NE from the Object Tree in the NE Explorer of NE B, and then choose Configuration > N+1 protection from the Function Tree. Select the ID of the protection group to be queried, and then click Query. In Slot Mapping Relation, the Switching Status of the working unit 3-ISU2-1 for the service that is configured with the N+1 protection should be SF.
Step 9 Set TX Status to Unmute for the main ODU 53-ODU of NE A. 1. 2. 3. 4. 1. 2. 3. 4. 5. 6. 7. 8. Select the NE from the Object Tree in the NE Explorer of NE A, and then choose Configuration > Link Configuration from the Function Tree. Click the IF/ODU Configuration tab. Select the required ODU, and set TX Status to Unmute. Click Apply. Select the PDH interface board in the Object Tree. In the Function Tree, choose Configuration > PDH Interface. Select By Function and select Tributary Loopback from the drop-down menu. In Tributary Loopback, select Non-Loopback. Click Apply. The Confirm dialog box is displayed. Click OK. The Confirm dialog box is displayed. Click OK. The Operation Result dialog box is displayed. Click Close.
----End
A Task Collection
A.11.6.3 Testing the SNCP Switching

You can verify whether the SNCP works normally by checking the working port of the SNCP protection group before and after the switching.
Prerequisite
l l Aligning the antennas must be complete. The equipment must be configured with the SNCP.


As shown in Figure A-6, the following procedures consider the E1 service between NE A and NE C that is configured with the SNCP as an example. Figure A-6 shows a network composed of radio links, and the test procedures are similar in the case of a network composed of optical fiber links. Figure A-6 Configuration for testing the SNCP switching NE A and NE C are configured as follows: l l l l West IF board: ISU2 in slot 3 East IF board: ISU2 in slot 4 West ODU: ODU in slot 53 East ODU: ODU in slot 54
NE A
Protecting SNC
Working SNC
NE D NE B
NE C
Issue 02 (2011-01-20)
A-255
A Task Collection
Precautions
NOTE
If no BER tester is available on site, you can compare the values of Active Channel in Working Service before the protection switching occurs and after the protection switching is complete.
Procedure
Step 2 At the central site NE A, connect one E1 port to the BER tester. Step 3 At the remote site NE C, perform a software inloop at the E1 port by using the NMS. 1. 2. 3. 4. 5. 6. 7. 8. Select the PDH interface board in the Object Tree. In the Function Tree, choose Configuration > PDH Interface. Select By Function and select Tributary Loopback from the drop-down menu. In Tributary Loopback, select Inloop. Click Apply. The Confirm dialog box is displayed. Click OK. The Confirm dialog box is displayed. Click OK. The Operation Result dialog box is displayed. Click Close.
Step 4 Test the BER by using the BER tester. The BER tester should show that no bit errors occur. Step 5 Before the switching, query the status of the protection group that is configured on NE C. 1. 2. 3. Select the NE from the Object Tree in the NE Explorer of NE C, and then choose Configuration > SNCP Service Control from the Function Tree. In Working Service, select an SNCP service that is already created, then click Function, and finally select Query Switching Status. The current SNCP status of the equipment is displayed in Working Service and Protection Service. In Current Status, Normal should be displayed. In Active Channel, Working Channel should be displayed.
A-256
Issue 02 (2011-01-20)
A Task Collection
Step 6 Set TX Status to mute for the west ODU 53-ODU of NE A. 1. 2. 3. 4. Select the NE from the Object Tree in the NE Explorer of NE A, and then choose Configuration > Link Configuration from the Function Tree. Click the IF/ODU Configuration tab. Select the required ODU, and set TX Status to mute. Click Apply.
No BER tester is available on site, and the See A.11.1 Testing the E1 Service Through E1 service is transmitted on the radio link. PRBS to test the availability of the E1 service. Step 8 After the switching, query the status of the protection group that is configured on NE C. 1. 2. 3. Select the NE from the Object Tree in the NE Explorer of NE C, and then choose Configuration > SNCP Service Control from the Function Tree. Click Function, and then select Query Switching Status. The current SNCP status of the equipment is displayed in Working Service and Protection Service. In Current Status, the service switching mode is displayed. In Active Channel, Protection Channel should be displayed.
Step 9 Set TX Status to unmute for the west ODU 53-ODU of NE A.

A Task Collection
1. 2. 3. 4. 1. 2. 3. 4. 5. 6. 7. 8.
Select the NE from the Object Tree in the NE Explorer of NE A, and then choose Configuration > Link Configuration from the Function Tree. Click the IF/ODU Configuration tab. Select the required ODU, and set TX Status to Unmute. Click Apply. Select the PDH interface board in the Object Tree. In the Function Tree, choose Configuration > PDH Interface. Select By Function and select Tributary Loopback from the drop-down menu. In Tributary Loopback, select Non-Loopback. Click Apply. The Confirm dialog box is displayed. Click OK. The Confirm dialog box is displayed. Click OK. The Operation Result dialog box is displayed. Click Close.
----End
A.11.6.4 Testing the ERPS

You can verify whether the ERPS works normally by checking the port status of the ERPS protection group before and after the switching.
Prerequisite
l l The equipment must be configured with the ERPS. The network cable for carrying the working and protection Ethernet services of the ERPS must be properly connected.

U2000

As shown in Figure A-7, the following procedures consider the Ethernet service between NE A and NE D that is configured with the ERPS as an example, the owner node is NE D. Figure A-7 Configuration for testing the ERPS NE A, NE B, NE C and NE D are configured as follows: l l l l
A-258
Main IF board: ISU2 in slot 3 Standby IF board: ISU2 in slot 5 Main ODU: ODU in slot 53 Standby ODU: ODU in slot 55
A Task Collection
East
West
NE B Protection channel West NE A
East
NE D
East Working channel West NE C East West
Procedure
Step 1 Before the switching, query the status of the protection group that is configured on NE D. 1. 2. 3. Select the NE from the Object Tree in the NE Explorer of NE D, and then choose Configuration > Ethernet Protection > ERPS Management from the Function Tree. Select the ERPS protection group to be queried, and then click Query. The value of Status of State Machine should be Idle.
Step 2 See A.11.3 Testing the Ethernet Service to test the availability of the Ethernet service. The LossRate in the Detection Result should be 0. Step 3 Set TX Status to mute for the west ODU 53-ODU of NE A.
A Task Collection
1. 2. 3. 4. 1. 2. 3.
Select the NE from the Object Tree in the NE Explorer of NE A, and then choose Configuration > Link Configuration from the Function Tree. Click the IF/ODU Configuration tab. Select the required ODU, and set TX Status to mute. Click Apply. Select the NE from the Object Tree in the NE Explorer of NE D, and then choose Configuration > Ethernet Protection > ERPS Management from the Function Tree. Select the ERPS protection group to be queried, and then click Query. The value of Status of State Machine should be Protection.
Step 4 After the switching, query the status of the protection group that is configured on NE D.
Step 5 See A.11.3 Testing the Ethernet Service to test the availability of the Ethernet service. The LossRate in the Detection Result should be 0. Step 6 Set TX Status to unmute for the west ODU 53-ODU of NE A. 1. 2. 3. 4. Select the NE from the Object Tree in the NE Explorer of NE A, and then choose Configuration > Link Configuration from the Function Tree. Click the IF/ODU Configuration tab. Select the required ODU, and set TX Status to Unmute. Click Apply.
----End
A.11.6.5 Testing the MPLS APS Protection Switching

By checking the change in the status of the MPLS tunnels before and after the MPLS APS switching, you can verify whether the MPLS APS protection function is normal.
Prerequisite
l l The MPLS tunnel protection group must be created properly. You must be an NM user with NE operator authority or higher.

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

Figure A-8 shows the test connection diagram for the MPLS APS protection. NE A and NE B are the OptiX RTN 980.
A Task Collection
Figure A-8 Connection diagram for testing the MPLS APS protection
Working Tunnel NE A NE B
Protection Tunnel
Procedure
Step 1 Query the switching status of the current MPLS tunnel 1:1 protection group on NE A and NE B. 1. 2. In the NE Explorer, select NE A and then choose Configuration > APS Protection Management from the Function Tree. Click the Tunnel APS Management tab, right-click the tested protection group, and then choose Query Switching Status from the short-cut menu, to check the MPLS protection group configured on the NE.
3.
Choose the protection group for switching, and check its switching status. In normal situations, the switching status should be Normal.
Issue 02 (2011-01-20)
A-261
A Task Collection
Step 2 Switch the services to the protection tunnel manually and forcedly. 1. 2. 3. In the NE Explorer, select NE A and then choose Configuration > APS Protection Management from the Function Tree. Click the Tunnel APS Management tab and choose the protection group for switching. Right-click the tested protection group, and then choose Forced Switching from the shortcut menu.
NOTE
l Forced switching: With the highest priority, the operation is performed no matter whether the current status of the protection tunnel is normal. l Manual switching: The operation is performed only when the status of the protection tunnel is normal.
The Confirm dialog box is displayed. 4. 5. 1. 2. 3. Click OK. The Operation Result dialog box is displayed. Click Close. In the NE Explorer, select NE A and then choose Configuration > APS Protection Management from the Function Tree. Click the Tunnel APS Management tab and choose the protection group for switching. Right-click the tested protection group and then choose Query Switching Status from the short-cut menu, to check Switching Status of the tunnel protection group. In normal situations, the switching status should be Forced Switching. Query Active Tunnel of the tunnel protection group. In normal situation, Working should be Standby, and Protection should be Active.
Step 3 Query the switching status of the MPLS 1:1 protection groups on NE A and NE B after switching.
4.
A-262
Issue 02 (2011-01-20)

NOTE
A Task Collection
l If Forced Switching is performed at the previous step, the state of the protection group should be Forced Switching. l If Manual Switching to Protection is performed at the previous step, the state of the protection group should be Manual (Working to Protection) Switching.
Step 4 Restore the services on NE A and NE B to the working tunnel. 1. 2. 3. 4. 5. 6. In the NE Explorer, select NE A and then choose Configuration > APS Protection Management from the Function Tree. Click the Tunnel APS Management tab and choose the protection group for switching. Right-click the tested protection group and then choose Clear from the short-cut menu. The Confirm dialog box is displayed. Click OK. The Operation Result dialog box is displayed. Click Close. Click Query. Services is restored to the working tunnel. ----End
A.11.6.6 Testing the Two-Fiber Bidirectional MSP Switching

By checking the change in the current working port in a ring MSP switching before and after switching, to verify whether the two-fiber bidirectional MSP function is normal.
Prerequisite
l l l l You must be an NM user with NE operator authority or higher. The equipment must be configured with the two-fiber bidirectional MSP and corresponding services. The optical fibers on the equipment must be connected properly.

l l BER tester U2000

Figure A-9 shows a two-fiber bidirectional MSP ring that comprises the OptiX RTN 980. The following steps consider the E1 services from NE A to NE C as an example.
NOTE
Only the logical board SL4D of the CSHN board supports the two-fiber bidirectional MSP.
Issue 02 (2011-01-20)
A-263
A Task Collection
Figure A-9 Two-fiber bidirectional MSP switching

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
Procedure
Step 1 Check whether a BER tester is available at the central site. If... If a BER tester is available on site If no BER tester is available on site Then... Perform Step 2 to Step 13. Perform Step 6 to Step 12.
Step 2 On the NE A side at the central site, connect the E1 port to be tested with the BER tester. Step 3 Cancel the loopback automatic disabling function for NE A and NE C. 1. Choose Configuration > NE Batch Configuration > Automatic Disabling of NE Function from the Main Menu to display the Automatic Disabling of NE Function window. Select the NE A and NE C in the left-hand object tree and click are displayed in Automatic Disabling of NE Function on the right. . The selected NEs
2. 3.
Set Auto Disabling of SDH Optical/Electrical Interface Loopback on the NE to Disabled.
A-264
Issue 02 (2011-01-20)

NOTE
A Task Collection
When the automatic disabling function of SDH Optical/Electrical Interface Loopback on the NE is set to Disabled, the loopback automatic disabling function for all of the SDH optical interfaces, PDH electrical interfaces and ATM IMA groups on the NE is disabled.
4.
Click Apply.
Step 4 On the NE C side at the remote site, use the U2000 to perform the inloop on the software of the corresponding E1 port. 1. 2. 3. 4. 5. 6. 7. 8. Select the PDH interface board in the Object Tree. In the Function Tree, choose Configuration > PDH Interface. Select By Function and select Tributary Loopback from the drop-down menu. In Tributary Loopback, select Inloop. Click Apply. The Confirm dialog box is displayed. Click OK. The Confirm dialog box is displayed. Click OK. The Operation Result dialog box is displayed. Click Close. Step 5 Use the BER tester to perform the bit error test. The BER tester should indicate that no bit error occurs. If a bit error occurs, see Maintenance Guide to rectify the fault. Step 6 Query the working status of the protection group on NE A before switching. 1. 2. Select the NE from the Object Tree in the NE Explorer of NE A, and then choose Configuration > Ring MS from the Function Tree. Click Query, and then select Query Switching Status. In Slot Mapping Relation, the Switching Status of east line and west line should be Idle.
NOTE
If exceptions occur, you must rectify the fault first, and then continue to test the linear MSP switching.
Step 7 Shut down the laser on the optical interface board (east) on NE A to trigger the two-fiber bidirectional MSP switching. 1. 2. 3. 4. 5. 6.
Issue 02 (2011-01-20)
Select the required optical interface board from the Object Tree in the NE Explorer of NE A. Choose Configuration > SDH Interface from the Function Tree. Select By Function and then select Laser Switch from the drop-down list. Select the laser port that corresponds to the working unit, and then set Laser Switch to Close. Click Apply. The Confirm dialog box is displayed. Click OK.
A Task Collection
The Confirm dialog box is displayed. 7. 8. Click OK. The Operation Result dialog box is displayed. Click Close.
TIP
You can also disconnect the optical fiber to trigger the two-fiber bidirectional MSP switching.
Step 8 Verify the availability of the services after switching. If... If a BER tester is available on site Then... Check the result on the BER tester. The result should indicate that the service recovers after transient interruption.
If no BER tester is available on site and E1 See A.11.1 Testing the E1 Service Through service transmitted on the fiber links PRBS to test the availability of the E1 services. Step 9 Query the working status of the protection group on NE A after switching. 1. 2. Select the NE from the Object Tree in the NE Explorer of NE A, and then choose Configuration > Ring MS from the Function Tree. Click Query, and then select Query Switching Status. In Slot Mapping Relation, the value of Switching Status should be Signal Fail-Ring.
Step 10 Re-enable the laser on the optical interface board (east) on NE A. 1. 2. 3. 4. 5. 6. 7. 8. Select the required optical interface board from the Object Tree in the NE Explorer of NE A. Choose Configuration > SDH Interface from the Function Tree. Select By Function and then select Laser Switch from the drop-down list. Select the laser port that corresponds to the working unit, and then set Laser Switch to Open. Click Apply. The Confirm dialog box is displayed. Click OK. The Confirm dialog box is displayed. Click OK. The Operation Result dialog box is displayed. Click Close. Step 11 Query the working status of protection group on NE A after switching restoration. 1. 2. Select the NE from the Object Tree in the NE Explorer of NE A, and then choose Configuration > Ring MS from the Function Tree. Click Query, and then select Query Switching Status. In Slot Mapping Relation, the Switching Status of east line and west line should be Idle.

NOTE
A Task Collection
After the service is restored, you can query Switching Status after the WTR time expires. The default value of WTR Time is 600s.
Step 12 Verify the availability of the services after switching restoration. If... If a BER tester is available on site. Then... Check the result on the BER tester. When WTR time expires, the result should indicate that the service recovers after transient interruption. WTR Time is 600s by default.
If no BER tester on site and E1 services are See A.11.1 Testing the E1 Service Through transmitted on the fiber links PRBS to test the availability of the E1 services.
NOTE
Revertive Mode of the two-fiber bidirectional MSP is always set to Revertive.
Step 13 Release the loopback that is set in Step 4. 1. 2. 3. 4. 5. 6. 7. 8. Select the PDH interface board in the Object Tree. In the Function Tree, choose Configuration > PDH Interface. Select By Function and select Tributary Loopback from the drop-down menu. In Tributary Loopback, select Non-Loopback. Click Apply. The Confirm dialog box is displayed. Click OK. The Confirm dialog box is displayed. Click OK. The Operation Result dialog box is displayed. Click Close.
----End
A.11.6.7 Testing the Linear MSP Switching

You can verify whether the linear MSP group works normally by checking the working port of the linear MSP group before and after the switching.
Prerequisite
l l The equipment must be configured with the linear MSP. The working and protection optical fibers of the linear MSP are connected properly.

l l
Issue 02 (2011-01-20)
U2000 BER tester

A Task Collection

Figure A-10 shows the linear MSP composed of the OptiX RTN equipment through the connection of optical fibers. The following procedures consider the E1 service from NE A to NE B as an example. Figure A-10 Configuration for testing the Ethernet service
NE A Working channel NE B
Protection channel
Precautions
NOTE
If no BER tester is available on site, you can compare the values of West Switching Status in Slot Mapping Relation before the protection switching occurs and after the protection switching is complete.
Procedure
Step 2 At the central site NE A, connect one E1 port to the BER tester. Step 3 At the remote site NE B, perform a software inloop at the corresponding E1 port by using the NMS. 1. 2. 3. 4. 5. 6. 7. 8.
A-268
Select the PDH interface board in the Object Tree. In the Function Tree, choose Configuration > PDH Interface. Select By Function and select Tributary Loopback from the drop-down menu. In Tributary Loopback, select Inloop. Click Apply. The Confirm dialog box is displayed. Click OK. The Confirm dialog box is displayed. Click OK. The Operation Result dialog box is displayed. Click Close.
A Task Collection
Step 4 Test the BER by using the BER tester. The BER tester should show that no bit errors occur. If bit errors occur, see the Maintenance Guide for handling the bit errors. Step 5 Before the switching, query the status of the protection group that is configured on NE A. 1. 2. 3. Select the NE from the Object Tree in the NE Explorer of NE A, and then choose Configuration > Linear MS from the Function Tree. In Slot Mapping Relation, select Working Unit. Click Query, and then select Query Switching Status. In Slot Mapping Relation, the value of West Switching Status should be Idle.
NOTE
In the case of the working and protection units of the service that is configured with the linear MSP, the values of West Switching Status should be Idle. If a fault arises, you must rectify the fault and proceed with the linear MSP switching testing.
Step 6 Shut down the laser for the working unit on NE A. 1. 2. 3. 4. 5. 6. 7. 8. Select the required optical interface board from the Object Tree in the NE Explorer of NE A. Choose Configuration > SDH Interface from the Function Tree. Select By Function and then select Laser Switch from the drop-down list. Select the laser port that corresponds to the working unit, and then set Laser Switch to Close. Click Apply. The Confirm dialog box is displayed. Click OK. The Confirm dialog box is displayed. Click OK. The Operation Result dialog box is displayed. Click Close.
Step 7 Check the availability of the service after the switching. If... The BER tester is available on site Then... Check the test result on the BER tester. It should show that the service is restored after a transient interruption.
No BER tester is available on site, and the See A.11.1 Testing the E1 Service Through E1 service is transmitted on the optical fiber PRBS to test the availability of the E1 service. link. Step 8 After the switching, query the status of the protection group that is configured on NE A. 1. 2.
Issue 02 (2011-01-20)
Select the NE from the Object Tree in the NE Explorer of NE A, and then choose Configuration > Linear MS from the Function Tree. In Slot Mapping Relation, select Working Unit.
A Task Collection
3.
Click Query, and then select Query Switching Status. In Slot Mapping Relation, the value of West Switching Status should be Switch upon signal failure.
NOTE
In the case of the 1+1 linear MSP, Revertive Mode can be set to Revertive or Non-Revertive. In the case of the 1:N linear MSP, Revertive Mode is always set to Revertive. l After the automatic switching occurs on the equipment, the service is restored. If Revertive Mode is set to Revertive for the linear MSP, the change in values of West Switching Status and Protected Unit can be queried after the WTR time expires. l After the automatic switching occurs on the equipment, the service is restored. If Revertive Mode is set to Non-Revertive for the linear MSP, stop and then start the MSP protocol to restore the value of West Switching Status to Idle.
Step 9 Turn on the laser for the working unit on NE A. 1. 2. 3. 4. 5. 6. 7. 8. Select the required optical interface board from the Object Tree in the NE Explorer of NE A. Choose Configuration > SDH Interface from the Function Tree. Select By Function and then select Laser Switch from the drop-down list. Select the laser port that corresponds to the working unit, and then set Laser Switch to Open. Click Apply. The Confirm dialog box is displayed. Click OK. The Confirm dialog box is displayed. Click OK. The Operation Result dialog box is displayed. Click Close. Step 10 Release the loopback set in Step 3. 1. 2. 3. 4. 5. 6. 7. 8. Select the PDH interface board in the Object Tree. In the Function Tree, choose Configuration > PDH Interface. Select By Function and select Tributary Loopback from the drop-down menu. In Tributary Loopback, select Non-Loopback. Click Apply. The Confirm dialog box is displayed. Click OK. The Confirm dialog box is displayed. Click OK. The Operation Result dialog box is displayed. Click Close.
----End
A Task Collection
A.11.6.8 Switching the System Control Unit and the Cross-Connect Unit
When the OptiX RTN 980 is configured with two system control, cross-connect, and timing boards, you can manually switch the system control unit and the cross-connect unit as required.
Prerequisite

U2000
Procedure
Step 1 Select the desired NE from the Object Tree. Step 2 Choose Configuration > Board 1+1 Protection from the Function Tree. Step 3 In 1+1 Protection List, select Cross-Connect Protection Pair. Step 4 Perform the 1+1 protection switching on the board. Option If... Active Board is set to Working Board Active Board is set to Protection Board Step 5 In the prompt that is displayed, click OK. ----End Description Then... Click Working/Protection Switching. Click Restore Working/Protection.
Issue 02 (2011-01-20)
A-271
B Parameters Description
Parameters Description
This topic describes the parameters used in this document. B.1 Parameters for Network Management This topic describes the parameters that are related to network management. B.2 Radio Link Parameters This topic describes the parameters that are related to radio links. B.3 Multiplex Section Protection Parameters This topic describes the parameters that are related to multiplex section protection (MSP). B.4 SDH/PDH Service Parameters This topic describes the parameters that are related to SDH/PDH services. B.5 Parameters for Board Interfaces This topic describes the parameters that are related to board interfaces. B.6 Parameters for Ethernet Services and Ethernet Features on the Packet Plane This section describes the parameters for the Ethernet services and Ethernet features on the packet plane, including service parameters, protocol parameters, OAM parameters, Ethernet port parameters, and QoS parameters. B.7 RMON Parameters This topic describes the parameters that are related to RMON performances. B.8 Parameters for MPLS/PWE3 Services This topic describes parameters that are related to MPLS/PWE3 services. B.9 Clock Parameters This topic describes the parameters that are related to clocks. B.10 Parameters for the Orderwire and Auxiliary Interfaces This topic describes the parameters that are related to the orderwire and auxiliary interfaces.
Issue 02 (2011-01-20)
B-1
B.1 Parameters for Network Management

This topic describes the parameters that are related to network management. B.1.1 Parameters for NE Management This topic describes the parameters that are used for managing network elements (NEs). B.1.2 Parameters for Communications Management This topic describes the parameters that are used for communications management. B.1.3 Parameters for Network Security Management This topic describes the parameters that are related to network security management.
B.1.1 Parameters for NE Management

This topic describes the parameters that are used for managing network elements (NEs). B.1.1.1 Parameter Description: NE Searching This topic describes the parameters that are used for searching for NEs. B.1.1.2 Parameter Description: NE Creation This topic describes the parameters that are related to NE creation. B.1.1.3 Parameter Description: Attribute_Changing NE IDs This topic describes the parameters that are used for changing NE IDs. B.1.1.4 Parameter Description: NE Time Synchronization This topic describes the parameters that are used for synchronizing the time of NEs. B.1.1.5 Parameter Description: Localization Management of the NE Time This parameter describes the parameters that are used for localization management of the NE time. B.1.1.6 Parameter Description: Standard NTP Key Management This topic describes the parameters that are used for managing the standard NTP key. B.1.1.7 Parameter Description: License Management This topic describes the parameters that are used for managing the license. B.1.1.8 Parameter Description: Automatic Disabling of the Functions of NEs This parameter describes the parameters that are used for automatically disabling the functions of an NE.
B.1.1.1 Parameter Description: NE Searching

This topic describes the parameters that are used for searching for NEs.
Navigation Path
Choose File > Discovery > NE from the Main Menu.
B-2
Issue 02 (2011-01-20)
Parameters for the Search Field

Parameter Address Type Value Range IP Address of GNE NSAP Address IP Address Range of GNE Default Value IP Address Range of GNE Description l If the OSI protocol is used on the DCN, you can search for an NE based on NSAP Address only. l If the IP protocol is used on the DCN, you can search for an NE based on IP Address of GNE or IP Address Range of GNE. l To search for all the NEs that communicate with the gateway NE, select IP Address Range of GNE. l To select the gateway NE only, select IP Address of GNE.
NOTE If Address Type is set to IP Address of GNE or IP Address Range of GNE, and if the U2000 (server) and the gateway NE are located in different network segments, ensure that the U2000 and relevant routers are configured with the IP routes for the network segment in which the U2000 and gateway NE are located. If Address Type is set to NSAP Address, ensure that the OSI protocol stack is installed.
Issue 02 (2011-01-20)
B-3
Parameter Search Address
Value Range -
Default Value -
Description l If Address Type is set to IP Address of GNE, enter the IP address of the gateway NE, such as 129.9.x.x. l If Address Type is set to IP Address Range of GNE, enter the number of the IP network segment in which the gateway NE is located, such as 129.9.255.255. l If Address Type is set to NSAP Address, enter the NSAP address of the gateway NE.
User Name
This parameter specifies the user name of the gateway NE. This parameter specifies the password of the gateway NE.
Password
B-4
Issue 02 (2011-01-20)
Parameter for Searching for NEs

Parameter Create NE after search Value Range Selected Deselected Default Value Deselected Description l To create NEs in batches, it is recommended that you select Create NE after search. The NEs are automatically created after they are found. l After Create NE after search is selected, enter NE User and Password that are used for creating an NE.
NOTE If only Create NE after search is selected, Search for NE is selected automatically.
NE User
l This parameter specifies the user name to be entered when an NE is created. l This parameter is valid only when Create NE after search is selected.
Password
l This parameter specifies the password to be entered when an NE is created. l This parameter is valid only when Create NE after search is selected.
Issue 02 (2011-01-20)
B-5
Parameter Upload after create
Value Range Selected Deselected
Default Value Deselected
Description l This parameter specifies whether to automatically upload the NE data after the NE is found and created. l If only Upload after create is selected, Search for NE and Create NE after search are selected automatically.
Parameter for the Found NEs

Parameter NE ID Value Range Default Value Description This parameter indicates the ID of the found NE, which consists of extended ID and NE ID. For example, in the case of NE9-25, the value 9 indicates the extended ID, and the value 25 indicates the NE ID. This parameter indicates the address of the gateway NE that is connected to the found NE. This parameter indicates the ID of the gateway NE that is connected to the found NE. l This parameter specifies the password to be entered when an NE is created. l This parameter is valid only when Create NE after search is selected.
GNE Address
GNE ID
Created As GNE
Yes No
Yes
B-6
Issue 02 (2011-01-20)
Parameter Connection Mode
Value Range Common Security SSL
Default Value Common
Description The communication between the client and the server is encrypted if this parameter is set to Security SSL. This parameter specifies the communication port. This parameter indicates whether the found NE is created.
Port NE Status
Created Uncreated
1400 -
Related Tasks
A.1.1.1 Creating NEs by Using the Search Method
B.1.1.2 Parameter Description: NE Creation

This topic describes the parameters that are related to NE creation.
Navigation Path
1. 2. In the Physical ViewPhysical Root, right-click New > NE. Choose RTN Series > OptiX RTN 980 from the Object Tree.
Parameters on the Main Interface

Parameter Type Value Range Default Value Description This parameter indicates the type of the NE to be created. l The ID refers to the basic ID. If the extended ID is not used, the basic ID of an NE must be unique on the networks that are managed by the same NMS. l This parameter is set according to the planning information.
NOTE The NE ID consisting of the basic ID and extended ID identifies an NE on the NMS.
ID
1 to 49135
Issue 02 (2011-01-20)
B-7
Parameter Extended ID
Value Range 1 to 254
Default Value 9
Description If the number of existing NEs does not exceed the range represented by the basic ID, do not change the extended ID. l This parameter specifies the name of the NE. l After you have specified the name of the NE, the name is displayed under the icon of the NE.
Name
Remarks Gateway Type
Non-Gateway Gateway
Non-Gateway
This parameter specifies the remarks of the NE. l This parameter is set to Gateway if the new NE is a gateway NE. l This parameter is set to Non-Gateway if the new NE is a nongateway NE. l This parameter is set according to the DCN planning if the new NE can function as a gateway NE or a nongateway NE.
Affiliated Gateway
This parameter indicates the gateway NE of the new NE when Gateway Type is set to Non-Gateway. l This parameter needs to be set when Gateway Type is set to Gateway. l When the OSI over DCC solution is used, this parameter is set to OSI. l In other cases, this parameter is set to IP.
Affiliated Gateway Protocol
IP OSI
IP
B-8
Issue 02 (2011-01-20)
Parameter IP Address
Value Range -
Default Value -
Description This parameter indicates the IP address of the new NE. This parameter needs to be set when Affiliated Gateway Protocol is set to IP. The communication between the client and the server is encrypted if this parameter is set to Security SSL. This parameter specifies the communication port. This parameter specifies the user name to be entered when an NE is created. This parameter specifies the password to be entered when an NE is created. This parameter indicates the NSAP address of the new NE. This parameter needs to be set when Affiliated Gateway Protocol is set to OSI. You need to set the area ID only, and the other parts are automatically generated by the NE.
Connection Mode
Common Security SSL
Common
Port NE User
1400 -
Password
NSAP Address
Related Tasks
A.1.1.2 Creating NEs by Using the Manual Method
B.1.1.3 Parameter Description: Attribute_Changing NE IDs

This topic describes the parameters that are used for changing NE IDs.
Navigation Path
1. 2. 3.
Issue 02 (2011-01-20)
In the Main Topology, right-click the NE whose ID needs to be modified. Choose Object Attributes. Click Modify NE ID.
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. B-9
Parameters for Changing NE IDs

Parameter New ID Value Range Default Value Description l The new ID refers to the basic ID. If the extended ID is not used, the basic ID of an NE must be unique on the networks that are managed by the same NMS. l This parameter is set according to the planning information.
NOTE The NE ID consisting of the basic ID and extended ID identifies an NE on the NMS.
New Extended ID
1 to 254
If the number of existing NEs does not exceed the range represented by the basic ID, do not change the extended ID.
Related Tasks
A.1.1.4 Changing the NE ID
B.1.1.4 Parameter Description: NE Time Synchronization

This topic describes the parameters that are used for synchronizing the time of NEs.
Navigation Path
1. 2. Choose Configuration > NE Batch Configuration > NE Time Synchronization from the Main Menu. Click the NE Time Synchronization tab.
Parameters for NE Time Synchronization

Parameter NE Name NE ID Value Range Default Value Description This parameter indicates the name of the NE. This parameter indicates the ID of the NE.
B-10
Issue 02 (2011-01-20)
Parameter Synchronous Mode
Value Range Standard NTP NM Null
Default Value Null
Description l If this parameter is set to NM, the NE synchronizes the time of the NMS server. l If this parameter is set to Standard NTP, the NE synchronizes the Network Time Protocol (NTP) server through the standard NTP.
Standard NTP Authentication
Enabled Disabled
Disabled
This parameter is valid only when Synchronous Mode is set to Standard NTP.
Parameters for the Standard NTP Server

Parameter Standard NTP Server Identifier Value Range NE ID IP Default Value NE ID Description l If the NE functions as the gateway NE, this parameter is set to IP. l If the NE functions as a non-gateway NE and communicates with the gateway NE through the HWECC protocol, this parameter is set to NE ID. l If the NE functions as a non-gateway NE and communicates with the gateway NE through the IP protocol, this parameter is set to IP.
Issue 02 (2011-01-20)
B-11
Parameter Standard NTP Server
Value Range -
Default Value -
Description l If the NE functions as the gateway NE, this parameter is set to the IP address of the external NTP server. l If the NE functions as a non-gateway NE, this parameter is set to the ID or IP address of the gateway NE.
Standard NTP Server Key
0 to 1024
l If the NTP server does not need to authenticated, this parameter is set to the value "0". l If the NTP server needs to be authenticated, the authentication is performed according to the allocated key of the NTP server. In this case, the NE authenticates the NTP server based on the key and the corresponding password (specified in the management of the standard NTP key).
Parameters for Setting Automatic Synchronization

Parameter Synchronization Starting Time Value Range Default Value Description l This parameter specifies the start time of the synchronization period. After this parameter is specified, the NMS and the NE synchronize the time once at the intervals of Synchronization Period(days). l It is recommended that you use the default value.
B-12
Issue 02 (2011-01-20)
Parameter DST
Description l This parameter indicates whether Synchronization Starting Time is the daylight saving time. l This parameter is set according to the actual situation.
Synchronization Period (days)
1 to 300
l This parameter indicates the period of synchronizing the time of the NE with the time of the NMS. l It is recommended that you use the default value.
Related Tasks
A.1.1.6 Synchronizing the NE Time
B.1.1.5 Parameter Description: Localization Management of the NE Time

This parameter describes the parameters that are used for localization management of the NE time.
Navigation Path
1. 2. Choose Configuration > NE Batch Configuration > NE Time Localization Management from the Main Menu. Select the NE for time localization management from the Object Tree, and then click .
Parameters for Localization Management of the NE Time

Parameter NE TimeZone DST Value Range Default Value Description This parameter indicates the name of the NE. This parameter indicates the time zone. This parameter indicates whether DST is enabled.
Issue 02 (2011-01-20)
B-13
Parameters for Time Zone

Parameter Time Zone Value Range Default Value Description l After the time zone is changed, the current time of the NE is changed accordingly. l This parameter is set according to the place where the NE is located. DST Selected Deselected Deselected l The parameters related to daylight saving time can be valid only when this parameter is selected. l This parameter is set according to the situation whether daylight saving time is used in the place where the NE is located. Offset 1 to 120 Unit: minute(s) Start Rule WEEK DATE Start Time End Rule WEEK DATE End Time WEEK WEEK This parameter specifies the offset value of the daylight saving time. This parameter specifies the method of adjusting the daylight saving time. This parameter specifies the start daylight saving time. This parameter specifies the method of adjusting the daylight saving time. This parameter specifies the end daylight saving time.
Related Tasks
A.1.1.7 Localizing the NE Time
B.1.1.6 Parameter Description: Standard NTP Key Management

This topic describes the parameters that are used for managing the standard NTP key.
Navigation Path
1. 2. Choose Configuration > NE Batch Configuration > NE Time Synchronization from the Main Menu. Click the Standard NTP Key Management tab.
B-14
Issue 02 (2011-01-20)

Parameter Key Value Range 1 to 1024 Default Value Description l This parameter indicates the key for NTP authentication. l This parameter is set according to the requirements of the external NTP server. Password l This parameter indicates the password that corresponds to Key. l This parameter is set according to the requirements of the external NTP server. Trusted Yes No Yes l When this parameter is set to No, the key verification is not trusted. After receiving the key, the NE rejects the clock synchronization service. l When this parameter is set to Yes, the key verification is trusted. After receiving the key, the NE provides the clock synchronization service. l After receiving an unknown or incorrect key, the NE rejects the clock synchronization service. Hence, it is recommended that you set a trusted key only.
Related Tasks
A.1.1.8 Configuring Standard NTP Keys
B.1.1.7 Parameter Description: License Management

This topic describes the parameters that are used for managing the license.
Issue 02 (2011-01-20) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. B-15
Navigation Path
1. 2. In the NE Explorer, select the NE and then choose Configuration > License Management from the Function Tree. Click the License Management tab.
Parameters for Managing Licenses

Parameter Board File Type Capacity Load Value Range Yes No Default Value Description This parameter displays the boards that need to be supported by licenses. This parameter displays the license type corresponding to each board. This parameter displays the capacity of each board. This parameter displays whether the corresponding license file is loaded to each board.
B.1.1.8 Parameter Description: Automatic Disabling of the Functions of NEs

This parameter describes the parameters that are used for automatically disabling the functions of an NE.
Navigation Path
1. 2. On the Main Topology, choose Configuration > NE Batch Configuration > Automatic Disabling of NE Function. Select the NE whose functions need to be automatically disabled from the Object Tree, and then click .
Parameters for Automatically Disabling the Functions of NEs

Parameter NE Name NE Type Operation Type Value Range OptiX RTN 980 Default Value Description This parameter indicates the name of the NE. This parameter indicates the type of the NE. This parameter indicates the type of the operation, such as loopback, and shutdown of the laser. This parameter specifies whether to automatically disable the operations such as loopback, and shutdown of the laser.
Issue 02 (2011-01-20)
Auto Disabling
Disabled Enabled
Enabled
B-16
Parameter Auto Disabling Time(min)
Default Value 5
Description This parameter specifies the time of automatically disabling the operations such as loopback, and shutdown of the laser.
B.1.2 Parameters for Communications Management

This topic describes the parameters that are used for communications management. B.1.2.1 Parameter Description: NE Communication Parameter Setting This topic describes the parameters that are used for NE communication setting. B.1.2.2 Parameter Description: DCC Management_DCC Rate Configuration This topic describes the parameters that are used for configuring the DCC rate. B.1.2.3 Parameter Description: DCC Management_DCC Transparent Transmission Management This topic describes the parameters that are used for DCC transparent transmission management. B.1.2.4 Parameter Description: ECC Management_Ethernet Port Extended ECC This topic describes the parameters that are related to the extended ECCs of Ethernet ports. B.1.2.5 Parameter Description: NE ECC Link Management This topic describes the parameters that are used for NE ECC link management. B.1.2.6 Parameter Description: IP Protocol Stack Management_IP Route Management This topic describes the parameters that are used for IP route management. B.1.2.7 Parameter Description: IP Protocol Stack Management_IP Route Management Creation This topic describes the parameters that are used for new static IP routes. B.1.2.8 Parameter Description: IP Protocol Stack Management_OSPF Parameter Settings This topic describes the parameters that are used for OSPF settings. B.1.2.9 Parameter Description: IP Protocol Stack_Proxy ARP This topic describes the parameters that are used for configuring the proxy ARP. B.1.2.10 Parameter Description: Port OSPF Setting This section describes the parameters that are used for setting port OSPF parameters. B.1.2.11 Parameter Description: OSI Management_Network Layer Parameter This topic describes the parameters that are related to the network layer of the OSI protocol model. B.1.2.12 Parameter Description: OSI Management_Routing Table This topic describes the parameters that are related to OSI routing tables. B.1.2.13 Parameter Description: OSI Management_OSI Tunnel This topic describes the parameters that are related to the OSI tunnels. B.1.2.14 Parameter Description: DCN Management_Bandwidth Management This topic describes the parameters that are used for bandwidth management of the inband DCN. B.1.2.15 Parameter Description: DCN Management_Port Setting This topic describes the parameters that are used for setting ports of the inband DCN.
B.1.2.16 Parameter Description: DCN Management_Protocol Setting This topic describes the parameters that are used for setting a protocol of the inband DCN. B.1.2.17 Parameter Description: DCN Management_Access Control This section describes the parameters for configuring access control. B.1.2.18 Parameter Description: Access Control This topic describes the parameters that are used for access control of the NMS.
B.1.2.1 Parameter Description: NE Communication Parameter Setting

This topic describes the parameters that are used for NE communication setting.
Navigation Path
Select the NE from the Object Tree in the NE Explorer. Choose Communication > Communication Parameters from the Function Tree.
Parameters for NE Communication Setting

Parameter IP Address 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 should meet the planning requirements of the external DCN. l If an NE uses the extended ECC, the IP address must be in the same network segment. l The IP address of other NEs should be set according to the NE ID. In this case, the IP address of an NE should be set in the format of 0x81000000+ID. That is, if the ID is 0x090001, the IP address should be set to 129.9.0.1. 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 IP Address Subnet Mask
Extended ID
1 to 254
B-18
Issue 02 (2011-01-20)
Parameter Connection Mode
Value Range Common + Security SSL Common Security SSL
Default Value Common + Security SSL
Description l Specifies the connection mode that the gateway NE allows the NMS to use for connecting to the gateway NE. l If the gateway NE has no special security requirement for connection to the NMS, Connection Mode can be set to Common. l If the gateway NE requests secure connection to the NMS for preventing information interception and cracking, Connection Mode needs to be set to Security SSL. l If NE communication security level needs to be the same as NMS communication security level, Connection Mode needs to be set to Common + Security SSL. l The default parameter value is recommended unless the gateway NE requires that the NMS use the SSL connection mode. l The parameter value takes effect only when it is set for a gateway NE and the gateway NE is connected to the NMS by means of the IP protocol.
Related Tasks
A.1.7.1 Setting NE Communication Parameters
B.1.2.2 Parameter Description: DCC Management_DCC Rate Configuration

This topic describes the parameters that are used for configuring the DCC rate.
Navigation Path
1. 2. Select the NE from the Object Tree in the NE Explorer. Choose Communication > DCC Management from the Function Tree. Click the DCC Rate Configuration tab.
Issue 02 (2011-01-20)
B-19
Parameters for DCC Rate Configuration

Parameter Port Value Range Default Value Description This parameter indicates the port that is connected to the DCC channel.
NOTE On the NMS interface, the first interface on the system control, switching, and clock board (like ) corresponds to its external clock interface.
Enabled/Disabled
Enabled Disabled
Enabled
It is recommended that you use the default value, except for the following cases: l If the port is connected to the other ECC subnet, Enabled/Disabled is set to Disabled. l If the port is connected to a third-party network and does not exchange the network management information with other ports, Enabled/Disabled is set to Disabled.
Channel
D1-D3 D4-D12 D1-D12 D1-D1
D1-D1 (for the PDH radio whose transmission capacity is less than 16xE1) D1-D3 (for other cases)
It is recommended that you use the default value, except for the following cases: l If the IP over DCC or OSI over DCC solution is adopted, Channel for the SDH line ports is set to a value that is the same as the value for third-party network. l If the DCC transparent transmission solution is adopted, the value of Channel for the SDH line ports should not conflict with the value that is set for the third-party network.
DCC Resources Communication Status Protocol Type
HWECC TCP/IP OSI
HWECC
This parameter indicates the DCC resources. This parameter indicates the communication status. It is recommended that you use the default value, except for the following cases: l If the IP over DCC solution is adopted, Protocol Type is set to TCP/IP. l If the OSI over DCC solution is adopted, Protocol Type is set to OSI.
LAPD Role
User Network
User
l This parameter is valid only when Protocol Type is set to OSI. l In the case of a DCC channel, LAPD Role must be set to User for one end and must be set to Network for the other end.
B-20
Issue 02 (2011-01-20)
Parameter LAPD MTU
Value Range -
Default Value -
Description Displays the maximum LAPD packet size.
Related Tasks
B.1.2.3 Parameter Description: DCC Management_DCC Transparent Transmission Management

This topic describes the parameters that are used for DCC transparent transmission management.
Navigation Path
1. 2. 3. Select the NE from the Object Tree in the NE Explorer. Choose Communication > DCC Management from the Function Tree. Click the DCC Transparent Transmission Management tab. Click Create.
Parameters for DCC Transparent Transmission Management

Parameter Source Timeslot/ Porta Value Range Default Value Description This parameter specifies the source timeslot or port.
Issue 02 (2011-01-20)
B-21
Parameter Transparent Transmission of Overhead Bytes at Source Port
Value Range D1 D2 D3 D4 D5 D6 D7 D8 D9 D10 D11 D12 E1 E2 F1 K1 K2 X1 X2 X3 X4
Default Value -
Description l Only one overhead byte can be selected each time. l X1, X2, X3, and X4 indicate the customized overhead bytes that are used for transmitting asynchronous data services. l An overhead byte cannot be a byte that is used. For example, an overhead byte cannot be a byte in the used DCC channel.
Sink Timeslot/ Porta
This parameter specifies the sink timeslot or port.
B-22
Issue 02 (2011-01-20)
Parameter Transparent Transmission of Overhead Bytes at Sink Port
Value Range D1 D2 D3 D4 D5 D6 D7 D8 D9 D10 D11 D12 E1 E2 F1 K1 K2 X1 X2 X3 X4
Default Value -
Description l Only one overhead byte can be selected each time. l An overhead byte cannot be a byte that is used. For example, an overhead byte cannot be a byte in the used DCC channel. l Generally, Transparent Transmission of Overhead Bytes at Sink Port can be set to a value that is the same as or different from the value in the case of Transparent Transmission of Overhead Bytes at Source Port.
NOTE
a. A bidirectional cross-connection is set up between the source port and the sink port. Hence, a port functions the same regardless of the source port or sink port.
Related Tasks
A.1.7.4 Configuring DCC Transparent Transmission
B.1.2.4 Parameter Description: ECC Management_Ethernet Port Extended ECC

This topic describes the parameters that are related to the extended ECCs of Ethernet ports.
Navigation Path
Click an NE in the NE Explorer. Choose Communication > ECC Management from the Function Tree.
Issue 02 (2011-01-20)
B-23
Parameters for the ECC Extended Mode

Parameter ECC Extended Mode Value Range Auto mode Specified mode Default Value Auto mode Description It is recommended that you use the default value.
Parameters for Setting the Server

Parameter IP Port Value Range 1601 to 1699 Default Value 0 Description This parameter indicates the IP address of the server. l This parameter is valid only when ECC Extended Mode is set to Specified mode. l This parameter can be set only when the NE functions as the server of the extended ECC. In normal cases, the NE that is close to the NMS functions as the server. l This parameter can be set to any value from 1601 to 1699.
Parameters for Setting the Client

Parameter Opposite IP Port Value Range 1601 to 1699 Default Value 0.0.0.0 0 Description l This parameter is valid only when ECC Extended Mode is set to Specified mode. l This parameter can be set only when the NE functions as the client of the extended ECC. Except for the NE that functions as the server, all other NEs that use the extended ECC can function as the client. l Opposite IP and Port are respectively set to the IP address of the server NE and the specified port number.
Related Tasks
B-24
Issue 02 (2011-01-20)
B.1.2.5 Parameter Description: NE ECC Link Management

This topic describes the parameters that are used for NE ECC link management.
Navigation Path
Select the NE from the Object Tree in the NE Explorer. Choose Communication > NE ECC Link Management from the Function Tree.
Parameter for NE ECC Link Management

Parameter Destination NE Transfer NE Distance Value Range 0 to 64 Default Value Description This parameter specifies the sink NE of the ECC connection. This parameter specifies the next transfer NE and the direction of the ECC route. l This parameter specifies the number of NEs (excluding the source NE and sink NE) through which the ECC route passes, namely, the number of ECC packet forwarding attempts. The value can be set to a value that is greater than the number of actual ECC packet forwarding attempts. If the value is set to a value that is less than the number of actual ECC packet forwarding attempts, however, the destination NE fails to be accessed. l If the value is set to 0, it indicates that the source NE is adjacent to the destination NE. Level 4 5 l This parameter indicates that multiple ECC routes from the source NE to the destination NE may be available. An ECC route of a higher priority is selected to transmit the packets to the destination NE. l If the ECC route is generated automatically, the priority is 4. l If the ECC route is added manually, the priority is 5. Mode Manual Automatic SCC No. This parameter indicates the ECC routing mode. This parameter specifies the physical port through which the ECC route passes. The value of this parameter is automatically assigned the NE.
B-25
Issue 02 (2011-01-20)
Related Tasks
B.1.2.6 Parameter Description: IP Protocol Stack Management_IP Route Management

This topic describes the parameters that are used for IP route management.
Navigation Path
1. 2. Select the NE from the Object Tree in the NE Explorer. Choose Communication > IP Protocol Stack Management from the Function Tree. Click the IP Route Management tab.
Parameters for IP Route Management

Parameter Destination Address Value Range Default Value Description This parameter indicates the destination address of the packets. This parameter can be set to a valid IP address of class A, B, or C only, but cannot be set to the IP address of the local host or the loopback address with the 127 field. This parameter indicates the subnet mask of the destination address of the packets. This parameter indicates the IP address of the gateway on the subnetwork where the NE is located, namely, the IP address of the next hop of the packets.
Subnet Mask Gateway
B-26
Issue 02 (2011-01-20)
Parameter Protocol
Value Range DIRECT STATIC OSPF RIP OSPF_ASE OSPF_NSSA
Default Value -
Description l DIRECT: indicates the route between the local NE and an adjacent NE. l STATIC: indicates the route that is created manually. l OSPF: indicates the route between the local NE and a non-adjacent NE. l RIP: indicates the route that is discovered by the routing information protocol. l OSPF_ASE: indicates the route whose Destination Address is beyond the OSPF domain. l OSPF_NSSA: indicates the route whose Destination Address is in a not so stubby area (NSSA). l A route can be deleted in the case of STATIC only, but cannot be edited in the other cases. l Compared with a dynamic route, a static route has a higher priority. If any conflict occurs, the static route is preferred.
Interface
This parameter indicates the interface that is used on the route. Interface is a concept specified in the TCP/IP protocol stack. In the TCP/IP protocol stack, you can create multiple types of interface, such as a loopback interface (namely, the interface whose IP address is 127.0.0.1), an Ethernet interface, and PPP interface. Each interface must have a unique interface name. This parameter indicates the maximum number of routers through which the packets are transmitted. Metric is used to indicate the overhead bytes that are transmitted to the destination address. The smaller the value, the less the overhead bytes. If multiple routes can reach the same destination address, a route whose overhead is less is preferred to transmit the packets.
Metric
0 to 65535
Related Tasks
Issue 02 (2011-01-20)
B-27
B.1.2.7 Parameter Description: IP Protocol Stack Management_IP Route Management Creation

This topic describes the parameters that are used for new static IP routes.
Navigation Path
1. 2. 3. Select the NE from the Object Tree in the NE Explorer. Choose Communication > IP Protocol Stack Management from the Function Tree. Click the IP Route Management tab. Click New.
Parameters for Creating IP Routes

Parameter Destination Address Value Range Default Value Description This parameter specifies the destination address of the packets. This parameter can be set to a valid IP address of class A, B, or C only, but cannot be set to the IP address of the local host or the loopback address with the 127 field. This parameter indicates the subnet mask of the destination address of the packets. This parameter specifies the IP address of the gateway on the subnetwork where the NE is located, namely, the IP address of the next hop of the packets.
Subnet Mask Gateway
Related Tasks
A.1.7.5 Creating Static IP Routes
B.1.2.8 Parameter Description: IP Protocol Stack Management_OSPF Parameter Settings

This topic describes the parameters that are used for OSPF settings.
Navigation Path
1. 2. Select the NE from the Object Tree in the NE Explorer. Choose Communication > IP Protocol Stack Management from the Function Tree. Click the OSPF Parameter Settings tab.
B-28
Issue 02 (2011-01-20)
OSPF Parameters
Parameter Area Value Range Default Value 0.0.0.0 Description l The OSPF protocol supports the division of NEs into multiple areas. Only the NEs in the same area can transmit the OSPF packets to each other to generate the route. l When setting the area for the NEs, you need to set the NEs that run the OSPF protocol to the same area. DCC Hello Timer (s) 1 to 255 10 l DCC Hello Timer(s) specifies the Hello packet timer at the DCC interface. l The Hello packets are used for detecting the neighbor router on the network that is connected to the router. By periodically transmitting the hello packets, you can determine whether the interface on the neighbor router is still in the active status. l DCC Hello Timer(s) determines the interval for the hello packet timer to transmit the hello packets. l In the case of two interconnected NEs, DCC Hello Timer(s) must be set to the same value. DCC Neighbor Dead Time(s) 1 to 65535 40 l DCC Neighbor Dead Time(s) specifies the dead time of a neighbor router at the DCC interface. l If the local router fails to receive the hello packets from the connected neighbor router within the time specified in DCC Neighbor Dead Time(s), it considers that the neighbor router is unavailable. l DCC Neighbor Dead Time(s) should be set to a value that is a minimum of twice the value of DCC Hello Timer (s). l In the case of adjacent NEs, DCC Neighbor Dead Time(s) must be set to the same value. Otherwise, the OSPF protocol fails to operate normally. DCC Retransmission Timer(s) 1 to 65535 5 DCC Retransmission Timer(s) specifies the interval for transmitting a request through the DCC interface to retransmit the link state advertisement (LSA) packets.
Issue 02 (2011-01-20)
B-29
Parameter DCC Delay(s)
Default Value 1
Description l DCC Delay(s) specifies the delay time to transmit the LSA packets through the DCC interface. l The LSA packets in the LSA database of the local router are aged as the time elapses, but are not aged when they are being transmitted on the network. Hence, before the LSA packets are transmitted, you need to increase the age of the LSA packets based on the value of DCC Delay(s).
LAN Hello Timer (s)
1 to 255
10
l DCC Hello Timer(s) specifies the hello packet timer at the LAN interfaces. l The hello packets are used for detecting the neighbor router on the network that is connected to the router. By periodically transmitting the hello packets, you can determine whether the interface on the neighbor router is still in the active status. l LAN Hello Timer(s) determines the interval for the hello packet timer of the NE to transmit the hello packets. l In the case of two interconnected NEs, LAN Hello Timer(s) must be set to the same value.
LAN Neighbor Dead Time(s)
1 to 65535
40
l LAN Neighbor Dead Time(s) specifies the dead time of a neighbor router at the LAN interface. l If the local router fails to receive the hello packets from the connected neighbor router within the time specified in LAN Neighbor Dead Time(s), it considers that the neighbor router is unavailable. l LAN Neighbor Dead Time(s) should be set to a value that is a minimum of two times the value of LAN Neighbor Dead Time(s). l In the case of adjacent NEs, DCC Neighbor Dead Time(s) must be set to the same value. Otherwise, the OSPF protocol fails to operate normally.
B-30
Issue 02 (2011-01-20)
Parameter LAN Retransmission Timer(s) LAN Delay(s)
Default Value 5
Description LAN Retransmission Timer(s) specifies the time for transmitting a request for retransmission of the LSA packets through the LAN interface. l LAN Delay(s) specifies the delay time to transmit the LSA packets through the LAN interface. l The LSA packets in the LSA database of the local router are aged as the time elapses, but are not aged when they are being transmitted on the network. Hence, before the LSA packets are transmitted, you need to increase the age of the LSA packets based on the value of LAN Delay(s).
1 to 3600
OSPF Status
Enabled Disabled
Disabled
l Specifies whether to enable the OSPF. l Set this parameter as required.
STUB Area
Enabled Disabled
Disabled
l Specifies whether to enable the STUB Area. l Set this parameter as required.
NSSA Area
Enabled Disabled
Disabled
l Specifies whether to enable the NSSA Area. l Set this parameter as required.
Direct route
Enabled Disabled
Disabled
l Specifies whether to enable the Direct route. l Direct route: the route detected by the link layer protocol. l Set this parameter as required.
Static route
Enabled Disabled
Disabled
l Specifies whether to enable the Static route. l Static route: the route manually configured by the network administrator. l Set this parameter as required.
RIP route
Enabled Disabled
Disabled
l Specifies whether to enable the RIP route. l RIP route: the route detected by the routing protocol. l Set this parameter as required.
Issue 02 (2011-01-20)
B-31
Parameter Opaque LSA of External Network Port
Value Range Enabled Disabled
Default Value Disabled
Description l Specifies whether to enable the Opaque LSA of External Network Port. l If this parameter is set to Enabled, it indicates that the Ethernet NM interface is used to transmit NM message. l Set this parameter as required.
LAN Interface
Enabled Disabled
Disabled
l Specifies whether to enable the OSPF at the Ethernet NM interface. l If this parameter is set to Enabled, it indicates that the Ethernet NM interface is interconnected with other equipment.
Related Tasks
A.1.7.6 Setting Parameters of the OSPF Protocol
B.1.2.9 Parameter Description: IP Protocol Stack_Proxy ARP

This topic describes the parameters that are used for configuring the proxy ARP.
Navigation Path
1. 2. Select the NE from the Object Tree in the NE Explorer. Choose Communication > IP Protocol Stack Management from the Function Tree. Click the Proxy ARP tab.
B-32
Issue 02 (2011-01-20)
Parameters for configuring the proxy ARP

Parameter Proxy ARP Value Range Disabled Enabled Default Value Disabled Description l The proxy ARP enables the NEs in the same network segment but different domains to communicate with each other. l To realize communication between such NEs, the source NE sends the ARP broadcast packet to address the route to the destination NE. The NE with the proxy ARP function enabled checks the routing table after sensing the ARP broadcast packet. If the routing table contains the destination address that the ARP broadcast packet looks for, the NE returns an ARP spoofing packet, which enables the NE that sends the ARP broadcast packet to consider that the MAC address of the NE that returns the ARP spoofing packet is the MAC address of the destination NE. In this manner, the packet that is to be sent to the destination NE is first sent to the NE with the proxy ARP function enabled and then forwarded to the destination NE.
Related Tasks
A.1.7.7 Enabling the ARP Proxy
B.1.2.10 Parameter Description: Port OSPF Setting

This section describes the parameters that are used for setting port OSPF parameters.
Navigation Path
1. 2. In the NE Explorer, select the required NE and choose Communication > IP Protocol Stack Management from the Function Tree. Click the Port OSPF Parameter Settings tab.
Port OSPF Parameters

Parameter Port Path Type
Issue 02 (2011-01-20)
Value Range -
Default Value -
Description Displays the ports that allow OSPF parameters to be set. Displays the current DCC channel type.
B-33
Parameter OSPF Status
Description l Specifies whether to enable the OSPF. l Set this parameter as required.
Opaque LSA of External Network Port
Enabled Disabled
Disabled
l Specifies whether DCC channels support Opaque LSAs. l Set this parameter as required.
B.1.2.11 Parameter Description: OSI Management_Network Layer Parameter

This topic describes the parameters that are related to the network layer of the OSI protocol model.
Navigation Path
1. 2. Select the NE from the Object Tree in the NE Explorer. Choose Communication > OSI Management from the Function Tree. Click the Network Layer Parameters tab.
Network Layer Parameters

Parameter NE Configuration Role Value Range ES L1 L2 Default Value L1 Description This parameter indicates the name of the NE. l Configuration Role cannot be set to ES. 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 accesses 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). Current Role This parameter indicates the current role.
Related Tasks
B-34 Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 02 (2011-01-20)
B.1.2.12 Parameter Description: OSI Management_Routing Table

This topic describes the parameters that are related to OSI routing tables.
Navigation Path
1. 2. Select the NE from the Object Tree in the NE Explorer. Choose Communication > OSI Management from the Function Tree. Click the Routing Table tab.
Parameters for Routing Tables

Parameter Port Data Link Layer Adjacency No. Value Range Default Value Description This parameter indicates the port used for OSI communication. This parameter indicates the protocol that is used at the data link layer. l This parameter specifies the identifier of the adjacency that is set up by two NEs through the OSI protocol. One adjacency number corresponds to an OSI adjacency. l The value is dynamically allocated by the NE. Adjacency Type Adjacency State Peer End Area ID This parameter indicates the type of the adjacency. This parameter indicates the state of the adjacency. This parameter indicates the area ID that is contained in the NSAP address of the opposite NE. This parameter indicates the system ID of the opposite NE. Generally, the system ID is the MAC address.
Peer End System ID
Parameters for L1 and L2 Routing Tables

Parameter Destination Area ID Destination SYSID Value Range Default Value Description This parameter indicates the area ID of the destination NE. This parameter indicates the system ID of the destination NE. Generally, the system ID is the MAC address.
B-35
Issue 02 (2011-01-20)
Parameter Metric
Value Range -
Default Value -
Description This parameter indicates the number of hops that reach the destination NE or destination area. This parameter indicates the number of the adjacent link that is connected to the destination NE. This parameter indicates the number of the adjacent link that is connected to the destination NE.
Adjacency No.1
Adjacency No.2
Related Tasks
B.1.2.13 Parameter Description: OSI Management_OSI Tunnel

This topic describes the parameters that are related to the OSI tunnels.
Navigation Path
1. 2. Select the NE from the Object Tree in the NE Explorer. Choose Communication > OSI Management from the Function Tree. Click the OSI Tunnel tab.
Parameters for OSI Tunnel Attributes

Parameter Remote IP Address LAPD Actor Value Range User Network Default Value User Description This parameter indicates the IP address of the opposite end of the OSI tunnel. l This parameter specifies the LAPD actor. l If the adjacent NEs run the OSI protocol, they can perform the LAPD negotiation only when the LAPD actor is set to User at one end and is set to Network at the other end. Efficient LAPD Enable Configurable LAPD Enable Enabled Disabled Enabled This parameter indicates whether the current LAPD is enabled. This parameter specifies whether the LAPD is enabled.
B-36
Issue 02 (2011-01-20)
LAPD Parameters
Parameter Remote IP Address L2 Wait Time to Retry(s) Value Range 1 to 20 Default Value 1 Description This parameter indicates the IP address of the opposite end of the OSI tunnel. l This parameter specifies L2 Wait Time to Retry(s). l L2 Wait Time to Retry(s) indicates the interval for retransmitting packets at the LAPD link layer. l L2 Wait Time to Retry(s) needs to be set according to the network situation. If the network is in good situation, L2 Wait Time to Retry(s) can be set to a smaller value. Otherwise, it is recommended that you set L2 Wait Time to Retry(s) to a greater value. l This parameter needs to be set according to the planning information. In normal cases, it is recommended that you use the default value. L2 Retry Times 2 to 6 3 l This parameter specifies L2 Retry Times. l L2 Retry Times indicates the maximum number of packet retransmission attempts at the LAPD link layer. l L2 Retry Times needs to be set according to the network situation. If the network is in good situation, L2 Retry Times can be set to a smaller value. Otherwise, it is recommended that you set L2 Retry Times to a greater value. l This parameter needs to be set according to the planning information. In normal cases, it is recommended that you use the default value.
Issue 02 (2011-01-20)
B-37
Parameter L3 Hello Timer(s)
Default Value 3
Description l This parameter specifies L3 Hello Timer(s). l L3 Hello Timer(s) indicates the Hello packet timer at the LAPD link network layer. It is used for periodical transmission of the Hello packets. l The Hello timer determines the interval for transmitting the Hello packets once. L3 Hello Timer(s) needs to be set according to the network situation. If the network is in good situation, L3 Hello Timer(s) can be set to a greater value. Otherwise, it is recommended that you set L3 Hello Timer(s) to a smaller value. l This parameter needs to be set according to the planning information. In normal cases, it is recommended that you use the default value.
L3 ES Timer(s)
1 to 200
50
l This parameter specifies L3 ES Timer (s). l L3 ES Timer(s) indicates the ES configuration timer at the LAPD link network layer. It is used for setting the time to transmit the configuration information on the ES route. l L3 ES Timer(s) needs to be set according to the network situation. If the network is in good situation, L3 ES Timer(s) can be set to a greater value. Otherwise, it is recommended that you set L3 Hello Timer(s) to a smaller value. l This parameter needs to be set according to the planning information. In normal cases, it is recommended that you use the default value.
B-38
Issue 02 (2011-01-20)
Parameter L3 IS Timer(s)
Default Value 10
Description l This parameter specifies L3 IS Timer (s). l L3 IS Timer(s) indicates the IS configuration timer at the LAPD link network layer. It is used for setting the time to transmit the configuration information through the L1/L2 router. l L3 IS Timer(s) needs to be set according to the network situation. If the network is in good situation, L3 IS Timer(s) can be set to a greater value. Otherwise, it is recommended that you set L3 IS Timer (s) to a smaller value. l This parameter needs to be set according to the planning information. In normal cases, it is recommended that you use the default value.
L3 Hold Timer(s)
2 to 63
l This parameter specifies L3 Hold Timer (s). l L3 Hold Timer(s) indicates the hold timer at the LAPD link network layer. l L3 Hold Timer(s) needs to be set according to the network situation. If the network is in good situation, L3 Hold Timer(s) can be set to a smaller value. Otherwise, it is recommended that you set L3 IS Timer(s) to a greater value. l This parameter needs to be set according to the planning information. In normal cases, it is recommended that you use the default value.
COST
1 to 63
20
l This parameter specifies COST. l COST indicates the overhead value of the virtual LAPD that corresponds to the OSI tunnel. l The overhead value determines whether this link is perverted. If the overhead value is smaller, this link has a higher priority to be selected. l This parameter needs to set according to the planning information.
Related Tasks
B.1.2.14 Parameter Description: DCN Management_Bandwidth Management

This topic describes the parameters that are used for bandwidth management of the inband DCN.
Navigation Path
1. 2. Select the NE from the Object Tree in the NE Explorer. Choose Communication > DCN Management from the Function Tree. Click the Bandwidth Management tab.
Parameters for Bandwidth Management

Parameter Ethernet Board VLAN ID Value Range 2 to 4094 Default Value 4094 Description l The equipment on the traditional DCN can be connected to the NMS through the SCC board, but the OptiX RTN 980 can also be connected to the NMS through an Ethernet interface. If an Ethernet port is used to carry the network management information, the NE differentiates the network management information and Ethernet service information according to the VLAN ID. l If the default VLAN ID of the inband DCN conflicts with the VLAN ID in the service, the VLAN ID of the inband DCN can be changed manually. The same VLAN ID must be, however, is used on the network-wide inband DCN. Bandwidth(Kbit/s) E1 Port Bandwidth(Kbit/s) Tunnel Bandwidth (Kbit/s) IF Port Bandwidth (Kbit/s) 64 to 1000 64 to 1000 512 512 Specifies the bandwidth for inband DCN messaging on the Ethernet link. The OptiX RTN 980 does not support this parameter. The OptiX RTN 980 does not support this parameter. Specifies the bandwidth for inband DCN messaging on the radio link.
Related Tasks
B.1.2.15 Parameter Description: DCN Management_Port Setting

This topic describes the parameters that are used for setting ports of the inband DCN.
B-40
Issue 02 (2011-01-20)
Navigation Path
1. 2. Select the NE from the Object Tree in the NE Explorer. Choose Communication > DCN Management from the Function Tree. Click the Port Settings tab.
Parameters for Setting Ports

Parameter Port Name Enabled Status Value Range Enabled Disabled Default Value Enabled Description This parameter indicates the port name. l Specifies the enabling status of the port. l The network management information can be transmitted over the inband DCN when the DCN function is enabled for the ports at both ends of a link.
Related Tasks
A.1.7.11 Configuring the Enable Status of the Inband DCN Function on Ports
B.1.2.16 Parameter Description: DCN Management_Protocol Setting

This topic describes the parameters that are used for setting a protocol of the inband DCN.
Navigation Path
1. 2. In the NE Explorer, select the required NE from the Object Tree, and then choose Communication > DCN Management from the Function Tree. Click the Protocol Settings tab.
Parameters for Setting a Protocol

Parameter Port Name Protocol Type Value Range IP HWECC Default Value IP Description Displays the port name. l If the values of Protocol Type are different from each other, the equipment at both ends cannot be interconnected with each other. Therefore, Protocol Type must be set to the same value for the equipment at both ends of a link. l This parameter needs to be set according to the planning information. Generally, it is recommended that you set this parameter to IP.
Issue 02 (2011-01-20)
B-41
Related Tasks
A.1.7.12 Configuring the Protocol Type of the Inband DCN
B.1.2.17 Parameter Description: DCN Management_Access Control

This section describes the parameters for configuring access control.
Navigation Path
l l In the NE Explorer, select the NE from the Object Tree and then choose Communication > DCN Management from the Function Tree. Click the Access Control tab.
Parameters
Parameter Port Name Enabled Status Value Range Disabled Enabled Default Value Disabled Description Displays the Ethernet ports that support this function. l Specifies the enabling status of the port. l If this parameter is set to Enabled, this port can be used to support access of the management information from the NMS. l If this parameter is set to Disabled, this port cannot be used to support access of the management information from the NMS. IP Address Subnet Mask 0.0.0.0 0.0.0.0 Specifies the IP address of the port. Specifies the submask of the port.
Related Tasks
A.1.7.16 Configuring Access Control
B.1.2.18 Parameter Description: Access Control

This topic describes the parameters that are used for access control of the NMS.
Navigation Path
Select the NE from the Object Tree in the NE Explorer. Choose Communication > Access Control from the Function Tree.
B-42
Issue 02 (2011-01-20)
Parameters for Ethernet Access Control

Parameter The First Network Port Value Range Enabled Disabled Default Value Enabled Description After The First Network Port is set to Enabled for Ethernet access, the NE can access the NMS through the Ethernet port.
Parameters for Access Control over Serial Ports

Parameter Enable Serial Port Access Access Command Line Access NM Value Range Selected Deselected Selected Deselected Selected Deselected Baud Rate 1200 2400 4800 9600 19200 38400 57600 115200 9600 Selected Deselected Default Value Selected Description After Enable Serial Port Access is selected, the NE can access the NMS or command lines through the serial port. 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. l This parameter specifies the data transmission rate in the communications through serial ports. l This parameter is set according to the rate of the serial port at the opposite end, and the rates at both ends must be the same.
B.1.3 Parameters for Network Security Management

This topic describes the parameters that are related to network security management. B.1.3.1 Parameter Description: NE User Management This topic describes the parameters that are related to NE user management. B.1.3.2 Parameter Description: NE User Management_Creation This topic describes the parameters that are used for creating an NE user. B.1.3.3 Parameter Description: LCT Access Control This topic describes the parameters that are used for LCT access control.
B.1.3.1 Parameter Description: NE User Management

This topic describes the parameters that are related to NE user management.
Navigation Path
1. Select the required NE from the Object Tree in the NE Explorer. Choose Security > NE User Management from the Function Tree. A dialog box is displayed, indicating that the operation is successful. 2. Close the dialog box.
Parameters for NE user management

Parameter NE NE User User Level NE User Flag Value Range Default Value Description Displays the current NE name. Displays the registered NE user name. Displays the registered NE user level. Displays whether a registered NE user is logged in.
Related Tasks
A.1.9.3 Setting Warning Screen Parameters
B.1.3.2 Parameter Description: NE User Management_Creation

This topic describes the parameters that are used for creating an NE user.
Navigation Path
1. Select the required NE from the Object Tree in the NE Explorer. Choose Security > NE User Management from the Function Tree.A dialog box is displayed, indicating that the operation is successful. Close the dialog box. Click Add.
2. 3.

Parameter NE User Value Range Default Value Description Specifies the name of a registered NE user.
NOTE The name of an NE cannot contain any space or Chinese characters.
B-44
Issue 02 (2011-01-20)
Parameter User Level
Value Range Monitor Level Operation Level Maintenance Level System Level Debug Level
Default Value Monitor Level
Description l Displays the registered NE user level. l A Debug Level NE user has all security and configuration authorities, and has the right to run debugging commands. l A System Level NE user has all security and configuration authorities. l A Maintenance Level NE user has some security authorities, some configuration authorities, the communication setting authority, and the log management authority. l An Operation Level NE user has all fault performance authorities, some security authorities, and some configuration authorities. l A Monitor Level NE user has the right to use all query commands, to log in, to log out, and to change its own password.
Issue 02 (2011-01-20)
B-45
Parameter NE User Flag
Value Range LCT NE User EMS NE User CMD NE User General NE User
Default Value LCT NE User
Description l Specifies the NE user flag. l LCT NE User indicates NE users for NE management on the U2000 Local Craft Terminal (U2000 LCT). l EMS NE User indicates NE users for NE management on the U2000. l CMD NE User indicates NE users for NE management on the CMD. l General NE User indicates NE users for all NMS types.
Detailed Description New Password Confirm Password Whether the password is allowed to be modified immediately
Yes No
Yes
Describes a configured NE user. l Specifies the password for a new NE user. Enter the same value as New Password. Specifies whether the password of a registered NE user can be changed.
Related Tasks
A.1.9.1 Creating an NE User
B.1.3.3 Parameter Description: LCT Access Control

This topic describes the parameters that are used for LCT access control.
Navigation Path
Select the NE from the Object Tree in the NE Explorer. Choose Security > LCT Access Control from the Function Tree.
B-46
Issue 02 (2011-01-20)
Parameters for LCT Access Control

Parameter NE LCT Access Control Switch Value Range Access Allowed Disable Access Default Value Access Allowed Description This parameter indicates the name of the NE. l No NMS user logs in to the NE. In this case, when the LCT requests an LCT user to log in to the NE, the NE does not check the status of LCT Access Control Switch, and directly allows the LCT user to log in to the NE. l An NMS user first logs in to the NE. In this case, when the LCT requests an LCT user to log in to the NE, the NE determines whether to allow the LCT user to log in to the NE through the LCT according to the status of LCT Access Control Switch. l An LCT user first logs in to the NE. In this case, when the NMS requests an NMS user to log in to the NE, the NMS user can directly log in to the NE. After the NMS user successfully logs in to the NE, the online LCT user is not affected. l When both the LCT user and NMS user log in to the NE, the online LCT user is not affected after LCT Access Control Switch is set to Disable Access.
B.2 Radio Link Parameters

This topic describes the parameters that are related to radio links. B.2.1 Parameter Description: Link Configuration_XPIC Workgroup_Creation This topic describes the parameters that are related to the XPIC function. B.2.2 Parameter Description: Link Configuration_XPIC This topic describes the parameters that are related to the XPIC function. B.2.3 Parameter Description: N+1 Protection_Create This topic describes the parameters that are used for creating an IF N+1 protection group. B.2.4 Parameter Description: N+1 Protection This topic describes the parameters that are related to IF N+1 protection. B.2.5 Parameter: IF 1+1 Protection_Create This topic describes the parameters that are used for creating an IF 1+1 protection group. B.2.6 Parameter Description: IF 1+1 Protection This topic describes the parameters that are related to IF 1+1 protection. B.2.7 Parameter: Link Configuration_IF/ODU Configuration
This topic describes the parameters that are used for configuring the IF/ODU.
B.2.1 Parameter Description: Link Configuration_XPIC Workgroup_Creation

This topic describes the parameters that are related to the XPIC function.
Navigation Path
1. 2. 3. Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Link Configuration from the Function Tree. Click the XPIC tab. Click New.
Parameters
Parameter IF Channel Bandwidth Value Range 28M 40M 56M Default Value Description l This parameter specifies the working bandwidth of the radio link. l When this parameter is set to 56M, the high-power ODU must be used.
NOTE The IFX2 board does not support the value 40M.
Polarization direction-V Polarization direction-H
l This parameter indicates the polarization direction of a radio link. l It is recommended that you set the IF port on the XPIC IF board that has a smaller slot number to Link ID-V and the IF port on the other XPIC IF board to Link IDH. l Set Link ID-V and Link ID-H. l A link ID is an identifier of a radio link and is used to prevent the 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 These two parameters are set according to the 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 link and Link ID-H must also be set to the same value at both ends of a link.
Link ID-V Link ID-H
1 to 4094
1 2
B-48
Issue 02 (2011-01-20)
Parameter Transmit Power (dBm)
Value Range -
Default Value -
Description l This parameter specifies the transmit power of an ODU. The value of this parameter must not exceed the rated power range supported by the ODU. l It is recommended that you set the transmit power of the ODU to the same value at both ends of a radio link. l Consider the receive power of the ODU at the opposite end when you set this parameter. Ensure that the receive power of the ODU at the opposite end can ensure stable radio services. l This parameter is set according to the planning information.
Maximum Transmit Power (dBm)
l This parameter specifies the maximum transmit power of the ODU. This parameter cannot be set to a value that exceeds the nominal power rang of the ODU in the guaranteed capacity modulation module. l This parameter is set to limit the maximum transmit power of the ODU within this preset range. l The maximum transmit power adjusted by using the ATPC function should not exceed this value. l This parameter is set according to the planning information.
Transmission Frequency(MHz)
l This parameter indicates the channel central 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 This parameter is set according to the planning information.
Issue 02 (2011-01-20)
B-49
Parameter T/R Spacing(MHz)
Value Range -
Default Value -
Description l This parameter specifies the spacing between the transmit frequency and the receive frequency of an ODU to prevent mutual interference between the transmitter and the receiver. l If Station Type of the ODU is TX high, the transmit frequency is one T/R spacing higher than the receive frequency. If Station Type of the ODU is TX low, the transmit frequency is one T/R spacing lower than the receive frequency. 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 A valid T/R spacing value is determined by the ODU itself, and the T/R spacing should be set according to the technical specifications of the ODU. l The T/R spacing of the ODU should be set to the same value at both the ends of a radio link.
Transmission Status
unmute mute
unmute
l When this parameter is set to mute, the ODU does not transmit microwave signals but can normally receive microwave signals. l When this parameter is set to unmute, the ODU normally transmits and receives microwave signals. l In normal cases, this parameter is set to unmute.
B-50
Issue 02 (2011-01-20)
Parameter ATPC Enabled
Value Range Disabled Enabled
Description l This parameter specifies whether the ATPC function is enabled. l When this parameter is set to Enabled and if the RSL at the receive end is 2 dB higher or lower than the central value between the ATPC upper threshold and the ATPC lower threshold at the receive end, the receiver notifies the transmitter to decrease or increase the transmit power until the RSL is within the range that is 2 dB higher or lower than the central value between the ATPC upper threshold and the ATPC lower threshold. l The settings of the ATPC attributes must be consistent at both ends of a radio link. l In the case of areas where fast fading severely affects the radio transmission, it is recommended that you set this parameter to Disabled. l During the commissioning process, set this parameter to Disabled to ensure that the transmit power is not changed. After the commissioning, re-set the ATPC attributes.
ATPC Upper Threshold(dBm) ATPC Lower Threshold(dBm)
-45.0 -70.0
l The central value between the ATPC upper threshold and the ATPC lower threshold is set as the expected receive power. l It is recommended that you set ATPC Upper Threshold(dBm) to the sum of the planned central value between the ATPC upper threshold and the ATPC lower threshold and 10 dB, and ATPC Lower Threshold(dBm) to the difference between the planned central value between the ATPC upper threshold and the ATPC lower threshold and 10 dB. l You can set the ATPC upper threshold only when ATPC Automatic Threshold Enable Status is set to Disabled.
Issue 02 (2011-01-20)
B-51
Parameter ATPC Automatic Threshold Enable Status
Description l This parameter specifies whether the 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.
Related Tasks
A.2.2 Creating an XPIC Protection Group
B.2.2 Parameter Description: Link Configuration_XPIC

This topic describes the parameters that are related to the XPIC function.
Navigation Path
1. 2. Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Link Configuration from the Function Tree. Click the XPIC tab.

Parameter Group ID Polarization direction-V Link ID-V Value Range Default Value Description This parameter indicates the ID of the work group. This parameter indicates the IF port to which the polarization direction V corresponds. This parameter indicates the link ID to which the polarization direction V corresponds. This parameter indicates the IF port to which the polarization direction H corresponds. This parameter indicates the link ID to which the polarization direction H corresponds.
Polarization direction-H Link ID-H
B-52
Issue 02 (2011-01-20)
Parameter IF Channel Bandwidth
Value Range 28M 40M 56M
Default Value -
Description l IF Channel Bandwidth refers to the channel spacing of the corresponding radio links. l When this parameter is set to 56M, the high-power ODU must be used. l This parameter is set according to the planning information.
NOTE The IFX2 board does not support the value 40M.
Power to Be Received -V(dBm)
-90.0 to -20.0
-10.0
l This parameter is used to set 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 misalignment indicating function. l When the antenna misalignment indicating function is enabled, if the actual receive power of the ODU is 3 dB lower than the power expected to be received, the ODU indicator on the IF board connected to the ODU blinks yellow (300 ms on, 300 ms off), indicating that the antenna is not aligned. l After the antenna alignment, after the state that the antenna is aligned lasts for 30 minutes, the NE automatically disables the antenna misalignment indicating function. l When this parameter takes the default value, the antenna misalignment indicating function is disabled. l This parameter is set according to the planning information.
Issue 02 (2011-01-20)
B-53
Parameter Power to Be Received -H(dBm)
Value Range -90.0 to -20.0
Default Value -10.0
Description l This parameter is used to set 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 misalignment indicating function. l When the antenna misalignment indicating function is enabled, if the actual receive power of the ODU is 3 dB lower than the power expected to be received, the ODU indicator on the IF board connected to the ODU blinks yellow (300 ms on, 300 ms off), indicating that the antenna is not aligned. l After the antenna alignment, after the state that the antenna is aligned lasts for 30 minutes, the NE automatically disables the antenna misalignment indicating function. l When this parameter takes the default value, the antenna misalignment indicating function is disabled. l This parameter is set according to the planning information.
Maximum Transmit Power (dBm)
l This parameter specifies the maximum transmit power of the ODU. This parameter cannot be set to a value that exceeds the nominal power rang of the ODU in the guaranteed capacity modulation module. l This parameter is set to limit the maximum transmit power of the ODU within this preset range. l The maximum transmit power adjusted by using the ATPC function should not exceed this value. l This parameter is set according to the planning information.
B-54
Issue 02 (2011-01-20)
Parameter Transmit Power (dBm)
Value Range -
Default Value -
Description l This parameter indicates or specifies the transmit power of the ODU. This parameter cannot be set to a value that exceeds the nominal power range of the ODU. l It is recommended that you set the transmit power of the ODU to the same value at both ends of a radio link. l Consider the receive power of the ODU at the opposite end when you set this parameter. Ensure that the receive power of the ODU at the opposite end can ensure stable radio services. l This parameter is set according to the planning information.
Transmission Frequency(MHz)
l This parameter indicates or specifies the transmit frequency of the ODU, namely, the channel central frequency. l The value of this parameter must not be less than the sum of the lower TX frequency limit supported by the ODU and a half of the channel spacing, and must not be more than the difference between the upper TX frequency limit supported by the ODU and a half of the channel spacing. l The difference between the transmit frequencies of both the ends of a radio link should be one T/R spacing. l This parameter needs to be set according to the planning information.
Issue 02 (2011-01-20)
B-55
Value Range -
Default Value -
Description l This parameter indicates or specifies the spacing between the transmit frequency and receive frequency of the ODU to prevent mutual interference between the transmitter and receiver. l If the ODU is a Tx high station, the transmit frequency is one T/R spacing higher than the receive frequency. If the ODU is a Tx low station, the transmit frequency is one T/R spacing lower than the receive frequency. l If the ODU supports only one T/R spacing, this parameter is set to 0, indicating that the T/R spacing supported by the ODU is used. l A valid T/R spacing value is determined by the ODU itself, and the T/R spacing should be set according to the technical specifications of the ODU. l The T/R spacing of the ODU should be set to the same value at both ends of a radio link.
Transmission Status
unmute mute
unmute
l This parameter indicates or specifies the transmit status of the ODU. l If this parameter is set to mute, the transmitter of the ODU does not work but can normally receive microwave signals. l If this parameter is set to unmute, the ODU can normally transmit and receive microwave signals. l In normal cases, this parameter is set to unmute.
Parameters for Hybrid/AM Configuration

Parameter Group ID Polarization direction Value Range Default Value Description This parameter indicates the ID of the work group. This parameter indicates the IF port to which the polarization direction H or the polarization direction V corresponds.
B-56
Issue 02 (2011-01-20)
Parameter AM Enable Status
Description l When this parameter is set to Disabled, the radio link uses only the specified modulation scheme. In this case, you need to select Manually Specified Modulation Mode. l When this parameter is set to Enabled, the radio link uses the corresponding modulation scheme according to the channel conditions. Hence, the Hybrid radio can ensure the reliable transmission of the E1 services and provide bandwidth adaptively for the Ethernet services when the AM function is enabled.
Modulation Mode of the Guarantee AM Capacity
QPSK 16QAM 32QAM 64QAM 128QAM 256QAM
This parameter specifies the highest-gain modulation scheme that the AM function supports. This parameter is set according to the planning information. 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 scheme.
NOTE Modulation Mode of the Full AM Capacity must be higher than Modulation Mode of the Guarantee AM Capacity.
This parameter is valid only when AM Enable Status is set to Enabled. Modulation Mode of the Full AM Capacity QPSK 16QAM 32QAM 64QAM 128QAM 256QAM This parameter specifies the highest-gain modulation scheme that the AM function supports. This parameter is set according to the planning information. 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 scheme.
This parameter is valid only when AM Enable Status is set to Enabled.
Issue 02 (2011-01-20)
B-57
Parameter Manually Specified Modulation Mode
Value Range QPSK 16QAM 32QAM 64QAM 128QAM 256QAM
Default Value QPSK
Description This parameter specifies the modulation scheme that the radio link uses for signal transmission. This parameter is valid only when AM Enable Status is set to Disabled.
Transmit-End Modulation Mode Receive-End Modulation Mode Guarantee E1 Capacity
Displays the modulation mode at the transmit end. Displays the modulation mode at the receive end. l When AM Enable Status is set to Enabled, this parameter depends on IF Channel Bandwidth and Modulation Mode of the Guarantee AM Capacity and cannot be set. l When AM Enable Status is set to Disabled, this parameter depends on IF Channel Bandwidth and Manually Specified Modulation Mode and cannot be set.
Full E1 Capacity
1 to 75
This parameter specifies the number of E1 services that can be transmitted in Hybrid work mode. The value of this parameter cannot exceed the Guarantee E1 Capacity. The Full E1 Capacity must be set to the same value at both ends of a radio link.
Parameters for ATPC Management

Parameter Group ID Value Range Default Value Description This parameter indicates the object to be set.
B-58
Issue 02 (2011-01-20)
Parameter ATPC Enable Status
Default Value -
Description l This parameter specifies whether the ATPC function is enabled. l If this parameter is set to Enabled and if the RSL at the receive end is 2 dB higher or lower than the central value between the ATPC upper threshold and the ATPC lower threshold at the receive end, the receiver notifies the transmitter to decrease or increase the transmit power until the RSL is within the range that is 2 dB higher or lower than the central value between the ATPC upper threshold and the ATPC lower threshold. l The settings of the ATPC attributes must be consistent at both ends of a radio link. l In the case of areas where fast fading severely affects the radio transmission, it is recommended that you set this parameter to Disabled. l During the commissioning process, set this parameter to Disabled to ensure that the transmit power is not changed. After the commissioning, re-set the ATPC attributes.
ATPC Upper Threshold(dBm) ATPC Lower Threshold(dBm)
l Set the central value between the ATPC upper threshold and the ATPC lower threshold to a value for the expected receive power. l It is recommended that you set ATPC Upper Threshold(dBm) to the sum of the planned central value between the ATPC upper threshold and the ATPC lower threshold and 10 dB, and ATPC Lower Threshold(dBm) o the difference between the planned central value between the ATPC upper threshold and the ATPC lower threshold and 10 dB. l You can set this parameter only when ATPC Automatic Threshold Enable Status is set to Disabled.
Issue 02 (2011-01-20)
B-59
Parameter ATPC Automatic Threshold Enable Status
Default Value -
Description 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).
Related Tasks
A.2.3 Setting the AM Attributes of the XPIC Hybrid Radio Link
B.2.3 Parameter Description: N+1 Protection_Create

This topic describes the parameters that are used for creating an IF N+1 protection group.
Navigation Path
1. 2. Select the NE from the Object Tree in the NE Explorer. Choose Configuration > N+1 Protection from the Function Tree. Click Create.

Parameter WTR time(s) Value Range 300 to 720 Default Value 600 Description l This parameter specifies the wait-torestore (WTR) time. l When the time after the former working channel is restored to normal reaches the set WTR time, a revertive switching occurs. l It is recommended that you use the default value.
B-60
Issue 02 (2011-01-20)
Parameter Enabled
Default Value Enabled
Description l This parameter specifies whether the SD switching function of N+1 protection is enabled. l When this parameter is set to Enabled, the SD condition is considered as a trigger condition of protection switching. l It is recommended that you set this parameter to Enabled.
Slot Mapping Relation Parameters

Parameter Select Mapping Direction Value Range Work Unit Protection Unit Default Value Work Unit Description l This parameter specifies the mapping direction of N+1 protection. l This parameter is set according to the planning information. Select Mapping Way l In the case of N+1 protection, map N IF ports as Work Unit and map the remaining IF port as Protection Unit. l This parameter is set according to the planning information. Mapped Board This parameter indicates the working unit and protection unit that have been set.
Related Tasks
B.2.4 Parameter Description: N+1 Protection

This topic describes the parameters that are related to IF N+1 protection.
Navigation Path
1. Select the NE from the Object Tree in the NE Explorer. Choose Configuration > N+1 Protection from the Function Tree.
Issue 02 (2011-01-20)
B-61
Protection Group Parameters

Parameter Protection Group ID WTR Time(s) Value Range 300 to 720 Default Value Description This parameter indicates the ID of the protection group. l This parameter indicates or specifies the WTR time. l When the time after the former working channel is restored to normal reaches the set WTR time, a revertive switching occurs. l It is recommended that you use the default value. SD Enable Enabled Disabled l This parameter indicates or specifies whether the SD switching function of N +1 protection is enabled. l When this parameter is set to Enabled, the SD condition is considered as a trigger condition of protection switching. l It is recommended that you set this parameter to Enabled. Protocol Status This parameter indicates the status of the switching control protocol.
Protection Unit Parameters

Parameter Protection Unit Line Value Range Default Value Description This parameter indicates the protection unit. This parameter indicates the information about the working board or protection board. This parameter indicates the switching state. This parameter indicates the protected unit. This parameter indicates the local end or remote end.
Switching Status Protected Unit Remote/Local End Indication
Related Tasks
A.2.7 Querying the IF N+1 Protection Status
B-62
Issue 02 (2011-01-20)
B.2.5 Parameter: IF 1+1 Protection_Create

This topic describes the parameters that are used for creating an IF 1+1 protection group.
Navigation Path
1. 2. Select the NE from the Object Tree in the NE Explorer. Choose Configuration > IF 1+1 Protection from the Function Tree. Click Create.
Parameters
Parameter Working Mode Value Range HSB FD SD Default Value HSB Description l This parameter specifies the working mode of the IF 1+1 protection. l In HSB mode, the equipment provides a 1+1 hot standby configuration for the IF board and ODU at both ends of each hop of a radio link to realize the protection. l In FD 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 FD protection, the impact of the fading on signal transmission is reduced. l In SD 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 SD protection, the impact of the fading on signal transmission is reduced. l The FD mode and SD mode are compatible with the HSB switching function. l This parameter is set according to the planning information.
Issue 02 (2011-01-20)
B-63
Parameter Revertive Mode
Value Range Revertive Mode Non-Revertive
Default Value Revertive Mode
Description l This parameter specifies the revertive mode of the IF 1+1 protection. l When this parameter is set to Revertive Mode, 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 you set this parameter to Revertive Mode.
WTR Time(s)
300 to 720
600
l This parameter specifies the wait-torestore (WTR) time. l When the time after the former working channel is restored to normal reaches the set WTR time, a revertive switching occurs. l You can set WTR Time(s) only when Revertive Mode is set to Revertive Mode. l It is recommended that you use the default value.
Enable Reverse Switching
Enabled Disabled
Enabled
l This parameter indicates whether the reverse switching function is enabled. 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 Enabled 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.
B-64
Issue 02 (2011-01-20)
Parameter Working Board Protection Board
Value Range -
Default Value -
Description This parameter specifies the working board of the protection group. This parameter specifies the protection board of the protection group.
NOTE
Each of the parameters Working Mode, Revertive Mode, WTR Time(s), and Enable Reverse Switching must be set to the same value at both ends of a radio hop.
Related Tasks
A.2.1 Creating an IF 1+1 Protection Group
B.2.6 Parameter Description: IF 1+1 Protection

This topic describes the parameters that are related to IF 1+1 protection.
Navigation Path
1. Select the NE from the Object Tree in the NE Explorer. Choose Configuration > IF 1+1 Protection from the Function Tree.

Parameter Protection Group ID Value Range Default Value Description This parameter indicates the ID of the protection group.
Issue 02 (2011-01-20)
B-65
Parameter Working Mode
Value Range HSB FD SD
Default Value -
Description l This parameter indicates the working mode of the created IF 1+1 protection group. l In HSB mode, the equipment provides a 1+1 hot standby configuration for the IF board and ODU at both ends of each hop of a radio link to realize the protection. l In FD 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 FD protection, the impact of the fading on signal transmission is reduced. l In SD 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 SD protection, the impact of the fading on signal transmission is reduced. l The FD mode and SD mode are compatible with the HSB switching function. l This parameter is set according to the planning information.
Revertive Mode
Revertive Mode Non-Revertive Mode
l This parameter indicates or specifies the revertive mode of the protection group. l When this parameter is set to Revertive Mode, 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 Mode, 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 you set this parameter to Revertive Mode.
B-66
Issue 02 (2011-01-20)
Parameter WTR Time(s)
Default Value -
Description l This parameter indicates or specifies the WTR time. l When the time after the former working channel is restored to normal reaches the set WTR time, a revertive switching occurs. l You can set WTR Time(s) only when Revertive Mode is set to Revertive Mode. l It is recommended that you use the default value.
Enable Reverse Switching
Enabled Disabled
l This parameter indicates or specifies whether the reverse switching function is enabled. 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 Enabled 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.
Switching Status of Device
l This parameter indicates the switching state on the equipment side. l Unknown is displayed when the switching state on the channel side is not queried or not obtained after a query.
Switching Status of Channel
l This parameter indicates the switching state on the channel side. l Unknown is displayed when the switching state on the channel side is not queried or not obtained after a query.
Active Board of Device Active Board of Channel
This parameter indicates the current working board on the equipment side. This parameter indicates the current working board on the channel side.
NOTE
Each of the parameters Working Mode, Revertive Mode, and WTR Time(s) must be set to the same value at both ends of a radio hop.
Issue 02 (2011-01-20)
B-67

Parameter Unit Slot Mapping Relation Working Status of Device Signal Status of Channel Value Range Default Value Description This parameter indicates the working board and protection board. This parameter indicates the names and ports of the working board and protection board. This parameter indicates the working state on the equipment side. This parameter indicates the status of the link signal.
Related Tasks
A.2.6 Querying the IF 1+1 Protection Status
B.2.7 Parameter: Link Configuration_IF/ODU Configuration

This topic describes the parameters that are used for configuring the IF/ODU.
Navigation Path
1. 2. In the NE Explorer, select the NE and then choose Configuration > Link Configuration from the Function Tree. Click the IF/ODU Configuration tab.
B-68
Issue 02 (2011-01-20)
Parameters for Configuring the IF

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 Default Value Description l This parameter indicates or specifies the work mode of the radio link in "work mode number, service capacity, channel spacing, modulation mode" format. l This parameter is set according to the planning information. The work modes of the IF boards at the two ends of a radio link must be the same.
NOTE The IF1 board supports this parameter.
Issue 02 (2011-01-20)
B-69
Parameter Link ID
Default Value 1
Description l This parameter indicates or specifies the ID of a radio link. As the identifier of a radio link, this parameter is used to prevent incorrect connections of radio links between sites. l If the value of Received Radio Link ID does not match the preset value of Link ID at the local end, the local end inserts the AIS signal to the downstream direction of the service. At the same time, the local end reports MW_LIM alarm to the NMS, indicating that the link IDs do not match. l Each radio link of an NE should have a unique link ID, and the link IDs at both ends of a radio link should be the same.
Received Link ID
l This parameter indicates the received ID of the radio link. l If the value of Received Radio Link ID does not match the preset value of Radio Link ID at the local end, the local end inserts the AIS signal to the downstream direction of the service. At the same time, the local end reports an alarm to the NMS, indicating that the link IDs do not match. l When the radio link becomes faulty, this parameter is displayed as an invalid value.
IF Service Type
Hybrid(Native E1 +ETH) Hybrid(Native STM-1+ETH) SDH
Hybrid(Native E1 +ETH)
l Displays or specifies the type of services carried by the IF board. l If the Integrated IP radio transmits Native E1 services, set this parameter to Hybrid(Native E1+ETH). l If the Integrated IP radio transmits Native STM-1 services, set this parameter to Hybrid(Native STM-1 +ETH). l If the SDH radio transmits SDH services, set this parameter to SDH.
NOTE The ISU2 and ISX2 boards support this parameter.
B-70
Issue 02 (2011-01-20)
Parameter IF Channel Bandwidth
Value Range 7M 14M 28M 40M 56M
Default Value -
Description IF Channel Bandwidth indicates the channel spacing of the corresponding radio link. This parameter is set according to the planning information.
NOTE l This parameter is not applicable to the IF1 board. l The IFU2 board does not support the value 40M. l The IFX2 board does not support the values 7M, 14M, and 40M. l The ISX2 board does not support the values 7M and 14M.
AM Mode AM Enable Status
Disabled Enabled
Disabled
This parameter is not applicable to the OptiX RTN 980. l When this parameter is set to Disabled, the radio link uses only the specified modulation scheme. In this case, you need to select Manually Specified Modulation Mode. l When this parameter is set to Enabled, the radio link uses the corresponding modulation scheme according to the channel conditions. l Hence, the Integrated IP radio can ensure the reliable transmission of the E1 services and provide bandwidth adaptively for the Ethernet services when the AM function is enabled. l The ISX2/ISU2 does not support the AM function when IF Service Type is SDH.
NOTE This parameter is not applicable to the IF1 board.
Manually Specified Modulation Mode
QPSK
l This parameter specifies the modulation scheme that the radio link uses for signal transmission. l This parameter is valid only when AM Enable Status is set to Disabled.
Issue 02 (2011-01-20)
B-71
Parameter Modulation Mode of the Guarantee AM Capacity
Default Value QPSK
Description l This parameter is valid only when AM Enable Status is set to Enabled. l This parameter specifies the lowest-gain modulation scheme that the AM function supports. This parameter is set according to the planning information. 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 scheme.
Modulation Mode of the Full AM Capacity
QPSK
l This parameter is valid only when AM Enable Status is set to Enabled. l This parameter specifies the highestgain modulation scheme that the AM function supports. This parameter is set according to the planning information. 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 scheme.
NOTE Modulation Mode of the Full AM Capacity must be higher than Modulation Mode of the Guarantee AM Capacity. NOTE This parameter is not applicable to the IF1 board.
STM-1 Capacity
l Specifies the STM-1 capacity of the IF board. l This parameter is available only when IF Service Type is set to Hybrid(Native STM-1+ETH) and SDH. l If IF Service Type is Hybrid(Native STM-1+ETH), this parameter can be set to 0 or 1. l If IF Service Type is SDH, this parameter can be set to 1 or 2.
NOTE The IF1, IFU2, and IFX2 boards do not support this parameter.
B-72
Issue 02 (2011-01-20)
Parameter Guarantee E1 Capacity
Value Range -
Default Value -
Description l If AM Enable Status is set to Enabled, this parameter needs to be set according to IF Channel Bandwidth, Modulation Mode of the Guarantee AM Capacity, and the actually transmitted services. l If AM Enable Status is set to Disabled, this parameter needs to be set according to IF Channel Bandwidth, Manually Specified Modulation Mode, and the actually transmitted services. l For the ISU2 and ISX2 boards, this parameter is available when IF Service Type is Hybrid(Native E1+ETH).
Guarantee E1 Capacity Range Data Service Bandwidth(Mbit/ s) Enable E1 Priority
Displays the E1 capacity range of the IF board in guarantee capacity modulation mode. Displays the data service bandwidth of the IF board. l This parameter specifies whether to enable the E1 priority function. l This parameter is valid only when AM Enable Status is set to Enabled. l For the ISU2 and ISX2 boards, this parameter is available when IF Service Type is Hybrid(Native E1+ETH).
Disabled Enabled
Disabled
Issue 02 (2011-01-20)
B-73
Parameter Full E1 Capacity
Value Range -
Default Value -
Description l This parameter specifies the number of transmitted E1 services in Modulation Mode of the Full AM Capacity. l This parameter is valid if Enable E1 Priority is set to Enabled. l E1 service bandwidth in full capacity mode Service bandwidth in full capacity mode - Service bandwidth in guarantee capacity mode + E1 service bandwidth in guarantee capacity mode. In addition, the number of E1 services in full capacity modulation mode should be smaller than or equal to the maximum number of E1 services in full capacity modulation mode. l The Full E1 Capacity must be set to the same value at both ends of a radio link. l For the ISU2 and ISX2 boards, this parameter is available when IF Service Type is Hybrid(Native E1+ETH).
Full E1 Capacity Range
Displays the E1 capacity range of the IF board in full capacity modulation mode.
Parameters for Configuring the RF

Parameter TX Frequency (MHz) Value Range Default Value Description l This parameter indicates or specifies the transmit frequency of the ODU, namely, the channel central frequency. l The value of this parameter must not be less than the sum of the lower TX frequency limit supported by the ODU and a half of the channel spacing, and must not be more than the difference between the upper TX frequency limit supported by the ODU and a half of the channel spacing. l The difference between the transmit frequencies of both the ends of a radio link should be one T/R spacing. l This parameter needs to be set according to the planning information.
B-74
Issue 02 (2011-01-20)
Parameter Range of TX Frequency(MHz)
Value Range -
Default Value -
Description l This parameter indicates the range of the transmit frequency of the ODU. l The Range of Frequency(MHz) depends on the specifications of the ODU.
Actual TX Frequency(MHz) Actual RX Frequency(MHz) T/R Spacing(MHz)
This parameter indicates the actual transmit frequency of the ODU. This parameter indicates the actual receive frequency of the ODU. l This parameter specifies the spacing between the transmit frequency and the receive frequency of an ODU to prevent interference between them. l If Station Type of the ODU is TX high, the TX frequency is one T/R spacing higher than the receive frequency. If Station Type of the ODU is TX low, the TX frequency is one T/R spacing lower than the receive frequency. 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 A valid T/R spacing value is determined by the ODU itself, and the T/R spacing should be set according to the technical specifications of the ODU. 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)
This parameter indicates the actual T/R spacing of the ODU.
Issue 02 (2011-01-20)
B-75
Parameters for Configuring the Power

Parameter TX Power(dBm) Value Range Default Value Description l This parameter indicates or specifies the transmit power of the ODU. This parameter cannot be set to a value that exceeds the nominal power range of the ODU. l This parameter cannot take a value greater than the preset value of Maximum Transmit Power(dBm). l It is recommended that you set the transmit power of the ODU to the same value at both ends of a radio link. l Consider the receive power of the ODU at the opposite end when you set this parameter. Ensure that the receive power of the ODU at the opposite end can ensure stable radio services. l This parameter needs to be set according to the planning information. Range of TX Power(dBm) Actual TX Power (dBm) This parameter indicates the range of the transmit power of the ODU. l This parameter indicates the actual transmit power of the ODU. l If the ATPC function is enabled, the queried actual transmit power may be different from the preset value.
B-76
Issue 02 (2011-01-20)
Parameter Power to Be Received(dBm)
Default Value -10.0
Description l This parameter is used to set 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 misalignment indicating function. l When the antenna misalignment indicating function is enabled, When the antenna non-alignment indication function is enabled, if the actual receive power of the ODU is 3 dB lower than the power expected to be received, the ODU indicator on the IF board connected to the ODU blinks yellow (300 ms on, 300 ms off), indicating that the antenna is not aligned. l After the antenna alignment, after the state that the antenna is aligned lasts for 30 minutes, the NE automatically disables the antenna misalignment indicating function. l When this parameter takes the default value, the antenna misalignment indicating function is disabled. l This parameter is set according to the planning information.
Actual RX Power (dBm) TX Status
Unmute Mute
Unmute
This parameter indicates the actual receive power of the ODU. l This parameter indicates or specifies the transmit status of the ODU. l When this parameter is set to Mute, the transmitter of the ODU does not work but can normally receive microwave signals. l When this parameter is set to Unmute, the ODU can normally transmit and receive microwave signals. l In normal cases, it is recommended that you set this parameter to unmute.
Actual TX Status
This parameter indicates the actual transmit status of the ODU.
Issue 02 (2011-01-20)
B-77
Equipment Information
Parameter Frequency(GHz) Equip Type Value Range Default Value Description This parameter indicates the frequency band where the ODU operates. l This parameter indicates the equipment type of the ODU. l PDH and SDH indicate the transmission capacity only and are irrelevant to the type of transmitted service. Station Type l This parameter indicates whether the ODU is a Tx high station or a Tx low station. l The transmit frequency of a Tx high station is one T/R spacing higher than the transmit frequency of a Tx low station. Produce SN This parameter indicates the manufacturing serial number and the manufacturer code of the ODU. This parameter indicates the level of the output power of the ODU.
Transmission Power Type
Related Tasks
B.3 Multiplex Section Protection Parameters

This topic describes the parameters that are related to multiplex section protection (MSP). B.3.1 Parameter Description: Linear MSP_Creation This topic describes the parameters that are used for creating linear MSP groups. B.3.2 Parameter Description: Linear MSP This topic describes the parameters that are related to linear MSP groups. B.3.3 Parameter Description: Ring MSP_Creation This topic describes the parameters that are used for creating ring MSP groups. B.3.4 Parameter Description: Ring MSP This topic describes the parameters that are related to ring MSP.
B.3.1 Parameter Description: Linear MSP_Creation

This topic describes the parameters that are used for creating linear MSP groups.
B-78
Issue 02 (2011-01-20)
Navigation Path
1. 2. Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Linear MS from the Function Tree. Click Create.

Parameter Protection Type Value Range 1+1 Protection 1:N Protection Default Value 1+1 Protection Description l This parameter specifies the protection type of the linear MSP group. l In the case of 1+1 linear MSP, one working channel and one protection channel are required. When the working channel fails, the service is switched from the working channel to the protection channel. l In the case of 1:N linear MSP, N working channels and one protection channel are required. Normal services are transmitted on the working channels and extra services are transmitted on the protection channel. When one working channel fails, the services are switched from this working channel to the protection channel, and the extra services are interrupted. l If extra services need to be transmitted or several working channels are required, select 1:N Protection. l This parameter is set according to the planning information. Switching Mode Single-Ended Switching Dual-Ended Switching Single-Ended Switching (1+1 Protection) Dual-Ended Switching (1:N Protection) l This parameter specifies the switching mode of the linear MSP. l In single-ended mode, the switching occurs only at one end and the state of the other end remains unchanged. l In dual-ended mode, the switching occurs at both ends at the same time. l If the linear MSP type is set to 1:N Protection, Switching Mode can be set to Dual-Ended Switching only.
Issue 02 (2011-01-20)
B-79
Value Range Non-Revertive Revertive
Default Value Non-Revertive (1+1 Protection) Revertive (1:N Protection)
Description l This parameter specifies the revertive mode of the linear MSP. 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 you set this parameter to Revertive. l If the linear MSP type is set to 1:N Protection, Revertive Mode can be set to Revertive only.
WTR Time(s)
300 to 720
600
l This parameter specifies the WTR time. l When the time after the former working channel is restored to normal reaches the preset WTR time, a revertive switching occurs. l You can set WTR Time(s) only when Revertive Mode is set to Revertive. l It is recommended that you use the default value.
SD Enable
Enabled Disabled
Enabled
l This parameter indicates or specifies whether the switching at the SD alarm of the linear MSP is enabled. l When this parameter is set to Enabled, the B2_SD alarm is considered as a switching condition. l It is recommended that you set this parameter to Enabled.
B-80
Issue 02 (2011-01-20)
Parameter Protocol Type
Value Range New Protocol Restructure Protocol
Default Value New Protocol
Description l The new protocol is supported at the early stage, and the mainstream protocol version is used currently. l The restructure protocol optimizes the new protocol and provides better measures to protect the new protocol, thus ensuring that the new protocol runs in a better manner. l The new protocol is more mature, and the restructure protocol complies with the standard. It is recommended that you use the new protocol. l You must ensure that the interconnected NEs run the protocols of the same type.

Parameter Select Mapping Direction Value Range West Working Unit West Protection Unit Default Value West Working Unit Description This parameter specifies the mapping direction of the linear MSP.
Select Mapping Mode
l This parameter specifies the mapping board and port in the mapping direction. l If the protection type is set to 1+1 Protection, only one line port can be mapped as West Working Unit. l Only one line port can be mapped as West Protection Unit. l The line port mapped as West Protection Unit and the line port mapped as West Working Unit should be configured for different boards if possible.
Mapped Board
This parameter indicates the preset slot mapping relations, including the mapping direction and the corresponding mapping mode.
Related Tasks
A.3.1 Configuring Linear MSP
Issue 02 (2011-01-20)
B-81
B.3.2 Parameter Description: Linear MSP

This topic describes the parameters that are related to linear MSP groups.
Navigation Path
Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Linear MS from the Function Tree.

Parameter Protection Group ID Protection Type Value Range Default Value Description This parameter indicates the ID of the protection group. l This parameter indicates the protection type of the linear MSP group. l In the case of 1+1 linear MSP, one working channel and one protection channel are required. When the working channel fails, the service is switched from the working channel to the protection channel. l In the case of 1:N linear MSP, N working channels and one protection channel are required. Normal services are transmitted on the working channels and extra services are transmitted on the protection channel. When one working channel fails, the services are switched from this working channel to the protection channel, and the extra services are interrupted. l If extra services need to be transmitted or several working channels are required, select 1:N Protection. Switching Mode Single-Ended Switching Dual-Ended Switching l This parameter indicates or specifies the switching mode of the linear MSP. l In single-ended mode, the switching occurs only at one end and the state of the other end remains unchanged. l In dual-ended mode, the switching occurs at both ends at the same time. l If the linear MSP type is set to 1:N Protection, Switching Mode can be set to Dual-Ended Switching only.
B-82
Issue 02 (2011-01-20)
Value Range Non-Revertive Revertive
Default Value -
Description l This parameter indicates or specifies the revertive mode of the linear MSP. 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 you set this parameter to Revertive. l If the linear MSP type is set to 1:N Protection, Revertive Mode can be set to Revertive only.
WTR Time(s)
300 to 720
l This parameter indicates or specifies the WTR time. l When the time after the former working channel is restored to normal reaches the preset WTR time, a revertive switching occurs. l You can set WTR Time(s) only when Revertive Mode is set to Revertive. l It is recommended that you use the default value.
SD Enable
Enabled Disabled
l This parameter indicates or specifies whether the reverse switching function is enabled. l When this parameter is set to Enabled, the B2_SD alarm is considered as a switching condition. l It is recommended that you set this parameter to Enabled.
Issue 02 (2011-01-20)
B-83
Value Range New Protocol Restructure Protocol
Default Value -
Description l The new protocol is supported at the early stage, and the mainstream protocol version is used currently. l The restructure protocol optimizes the new protocol and provides better measures to protect the new protocol, thus ensuring that the new protocol runs in a better manner. l You must ensure that the interconnected NEs run the protocols of the same type. l The new protocol is more mature, and the restructure protocol complies with the standard. It is recommended that you use the new protocol.
Protocol Status Protection Subnet
This parameter indicates the protocol status of the linear MSP. This parameter displays the protection subnet where the MS protection is configured.

Parameter Protection Unit Value Range Default Value Description This parameter indicates that which of the units, namely, the west protection unit or the west working unit, is currently in the protection status. This parameter indicates the west protection unit and the west working unit of the linear MSP. This parameter indicates the switching status of the line. This parameter indicates the working channel protected by the current protection channel. When Switching Mode is set to DualEnded Switching, the central office end that issues the switching command is displayed.
West Line
West Switching Status Protected Unit
Remote/Local End Indication
B-84
Issue 02 (2011-01-20)
Related Tasks
A.3.2 Querying the Status of the Linear MSP
B.3.3 Parameter Description: Ring MSP_Creation

This topic describes the parameters that are used for creating ring MSP groups.
Navigation Path
1. 2. 3. In the NE Explorer, select the required NE from the Object Tree and choose Configuration > Ring MS from the Function Tree. Click Create. A dialog box is displayed, prompting for confirmation. Click OK.

Parameter Level Value Range STM-4 Default Value STM-4 Description Specifies the transmission level of ring MSP services. The parameter value is always STM-4. Specifies the ring MSP protection type. The parameter value is always 2-fiber Bidirectional Multiplex Section. Specifies the node ID that the local NE uses on the MSP ring. Node IDs of NEs on the ring must be different from each other. Specifies the node ID of the NE that is connected to the west line board on the local NE. The parameter value must be different from Local Node. Specifies the node ID of the NE that is connected to the east line board on the local NE. The parameter value must be different from Local Node. l Specifies the WTR time for the local NE. After the working channel recovers, services are switched back from the protection channel to the working channel when the WTR time expires. l Prevents frequent service switches. The default value is recommended.
Protection Type
2-fiber Bidirectional Multiplex Section 0-15
2-fiber Bidirectional Multiplex Section 0
Local Node
West Node
0-15
East Node
0-15
WTR Time(s)
300-720
600
Issue 02 (2011-01-20)
B-85
Parameter SD Enable
Description l Specifies whether the B2_SD alarm on the local NE functions as a switching trigger condition. When the parameter value is Enabled, the B2_SD alarm on the local NE functions as a switching trigger condition. l It is recommended that you set this parameter to Enabled.
Protocol Type
New Protocol Restructure Protocol
New Protocol
l The new MSP protocol is supported from an early stage, and is still widely used. l Compared with the new MSP protocol, the restructure MSP protocol is optimized and more stable, incorporating better protection measures. l The new MSP protocol has higher technology maturity than the restructure MSP protocol, and therefore is generally recommended. The restructure MSP protocol, however, features higher standard compliance than the new MSP protocol. Therefore, the restructure MSP protocol is used when the new MSP protocol fails to support interconnection between Huawei RTN equipment and third-party equipment. l Two interconnected NEs must use the same MSP protocol type.
Parameters for Slot Mapping Relationships

Parameter Select Mapping Direction Select Mapping Mode Value Range West Line 1 East Line 1 Default Value West Line 1 Description Specifies the mapping direction of a member in a ring MSP protection group. l Specifies the mapped board and port in the mapping direction. l It is recommended that you map the SL4D-1 port to West Line 1 and map the SL4D-2 port to East Line 1. Mapped Board Displays the configured slot mapping relationship, including the mapping direction and the mapping mode.
B-86
Issue 02 (2011-01-20)
Related Tasks
A.3.5 Configuring Ring MSP
B.3.4 Parameter Description: Ring MSP

This topic describes the parameters that are related to ring MSP.
Navigation Path
In the NE Explorer, select the required NE from the Object Tree and choose Configuration > Ring MS from the Function Tree.

Parameter Protection Group ID Level Value Range Default Value Description Displays the ID of a ring MSP protection group. Displays the transmission level of ring MSP services. The parameter value is always STM-4. Displays the ring MSP protection type. The parameter value is always 2-fiber Bidirectional Multiplex Section. Displays the node ID that the local NE uses on the MSP ring. Displays the node ID of the NE that is connected to the west line board on the local NE. Displays the node ID of the NE that is connected to the east line board on the local NE. Displays the wait-to-restore (WTR) time of the local NE. After the working channel is restored, revertive switching occurs when the WTR time expires. Displays whether SD Enable is Enabled for the local NE. If SD Enable is Enabled, the B2_SD alarm is regarded as a switching trigger condition.
Protection Type
Local Node West Node
East Node
WTR Time(s)
SD Enable
Issue 02 (2011-01-20)
B-87
Value Range -
Default Value -
Description l Displays the protocol type used by the local NE. l The new MSP protocol is supported from an early stage, and is still widely used. l Compared with the new MSP protocol, the restructure MSP protocol is optimized and more stable, incorporating better protection measures.
Protocol Status Protection Subnet
Displays the current protocol status of the local NE. Displays the current protection subnet.
Parameters for Slot Mapping Relationships

Parameter Mapping Direction Slot Mapping Switching Status Value Range Default Value Description Displays the direction of an MSP ring. Displays the slot mapping relationship in a ring MSP protection group. Displays the current switching status of the local NE.
Related Tasks
A.3.6 Querying Ring MSP Status
B.4 SDH/PDH Service Parameters

This topic describes the parameters that are related to SDH/PDH services. B.4.1 Parameter Description: SDH Service Configuration_Creation This parameter describes the parameters that are used for creating point-to-point crossconnections. B.4.2 Parameter Description: SDH Service Configuration_SNCP Service Creation This topic describes the parameters that are used for creating SNCP services. B.4.3 Parameter Description: SDH Service Configuration_Converting Normal Services Into SNCP Services This topic describes the parameters that are used for converting normal services into SNCP services. B.4.4 Parameter Description: SDH Service Configuration
This topic describes the parameters that are used for configuring SDH services (namely, configuring cross-connections). B.4.5 Parameter Description: SNCP Service Control This topic describes the parameters that are used for controlling SNCP services. B.4.6 Parameter Description: TU_AIS Insertion This section describes the parameters for TU_AIS insertion.
B.4.1 Parameter Description: SDH Service Configuration_Creation

This parameter describes the parameters that are used for creating point-to-point crossconnections.
Navigation Path
l l l Select the NE from the Object Tree in the NE Explorer. Choose Configuration > SDH Service Configuration from the Function Tree. Click Options to change the VC-12 timeslot numbering policy used by the crossconnection. Click Create.
Parameters
Parameter Level Value Range VC12 VC3 VC4 Default Value VC12 Description l This parameter specifies the level of the service to be created. l If the service is an E1 service or a data service that is bound with VC-12 channels, set this parameter to VC12. l If the service is a data service that is bound with VC-3 channels, set this parameter to VC3. l If all the services on a VC-4 channel pass through the NE, set this parameter to VC4. Direction Bidirectional Unidirectional Bidirectional l When this parameter is set to Unidirectional, create only the crossconnections from the service source to the service sink. l When this parameter is set to Bidirectional, create the crossconnections from the service source to the service sink and the crossconnections from the service sink to the service source. l In normal cases, it is recommended that you set this parameter to Bidirectional.
Issue 02 (2011-01-20)
B-89
Parameter Source Slot Source VC4
Value Range -
Default Value -
Description This parameter specifies the slot of the service source. l This parameter specifies the number of the VC-4 channel where the service source is located. l This parameter cannot be set when Source Slot is set to the slot of the tributary board.
Source Timeslot Range(e.g.1,3-6)
l This parameter indicates the timeslot range of the service source. l This parameter can be set to a number or several numbers. When setting this parameter to several numbers, use the comma (,) to separate the discrete numbers, or use the endash (-) to represent a consecutive number. For example, the numbers 1, and 3-6 indicate 1, 3, 4, 5, and 6. l This parameter is set according to the planning information.
Sink Slot Sink VC4
This parameter specifies the slot of the service sink. l This parameter specifies the number of the VC-4 channel where the service sink is located. l This parameter cannot be set when Sink Slot is set to the slot of the tributary board.
Sink Timeslot Range(e.g.1,3-6)
l This parameter specifies the timeslot range of the service sink. l This parameter can be set to a number or several numbers. When setting this parameter to several numbers, use the comma (,) to separate the discrete numbers, or use the endash (-) to represent a consecutive number. For example, the numbers 1, and 3-6 indicate 1, 3, 4, 5, and 6. l This parameter is set according to the planning information.
B-90
Issue 02 (2011-01-20)
Parameter E1 Priority
Value Range High Low None
Default Value -
Description l This parameter specifies the priority of an E1 service. l This parameter is available only if the E1 priority function is enabled for the ports configured in the cross-connections. l If E1 Priority is set to High, transmission of the E1 service is ensured in any modulation scheme. l If E1 Priority is set to Low, transmission of the E1 service is ensured only in fullcapacity modulation scheme l If the service priority is not specified during service creation, E1 Priority is None. In this case, the E1 priority of a service needs to be changed after the service is created.
Activate Immediately
Yes No
Yes
l This parameter specifies whether to immediately activate the configured service. l To immediately deliver the configured SDH service to the NE, set this parameter to Yes.
Related Tasks
A.4.1 Creating the Cross-Connections of Point-to-Point Services
B.4.2 Parameter Description: SDH Service Configuration_SNCP Service Creation

This topic describes the parameters that are used for creating SNCP services.
Navigation Path
l l l Select the NE from the Object Tree in the NE Explorer. Choose Configuration > SDH Service Configuration from the Function Tree. Click Options to change the VC-12 timeslot numbering policy used by the crossconnection. Click Create SNCP Service.

Parameter Service Type Value Range SNCP Default Value SNCP Description This parameter indicates that the type of the service to be created is SNCP.
B-91
Issue 02 (2011-01-20)
Parameter Direction
Value Range Bidirectional Unidirectional
Default Value Bidirectional
Description l When this parameter is set to Unidirectional, create only the crossconnections from the SNCP service source to the SNCP service sink. l When this parameter is set to Bidirectional, create the crossconnections from the SNCP service source to the service sink and the crossconnections from the SNCP service sink to the service source. l In normal cases, it is recommended that you set this parameter to Bidirectional.
Level
VC12 VC3 VC4
VC12
l This parameter specifies the level of the SCNP service to be created. l If the service is an E1 service or a data service that is bound with VC-12 channels, set this parameter to VC12. l If the service is a data service that is bound with VC-3 channels, set this parameter to VC3. l If all the services on a VC-4 channel pass through the NE, set this parameter to VC4.
B-92
Issue 02 (2011-01-20)
Parameter Hold-off Time (100ms)
Default Value 0
Description l This parameter specifies the duration of the hold-off time. l When a line is faulty, SNCP switching can be performed on the NE after a delay of time to prevent the situation where the NE performs SNCP switching and other protection switching at the same time. l Hold-off Time(100ms) is generally set to prevent SNCP protection switching, when SNCP works with N+1 protection. Hold-off Time(100ms) must be longer than the switching time of any protection mode that works with SNCP. Generally, Hold-off Time(100ms) is set to 200 ms. l When SNCP works with 1+1 FD/SD, trigger conditions for HSM switching or SNCP switching trigger HSM switching but do not trigger SNCP switching. Therefore, Hold-off Time(100ms) does not need to be set in this case. l The switching time of 1+1 HSB/FD/SD protection is much longer than that of SNCP. Therefore, to shorten service interruptions, it is recommended that you do not set Hold-off Time(100ms) when SNCP works with 1+1 HSB/FD/SD protection. l If only the SNCP scheme is available, it is recommended that you set the hold-off time to 0.
Revertive Mode
Non-Revertive Revertive
Non-Revertive
l This parameter specifies whether to switch the service to the original working channel after the fault is rectified. l If this parameter is set to Revertive, the service is switched from the protection channel to the original working channel. If this parameter is set to NonRevertive, the service is not switched from the protection channel to the original working channel. l It is recommended that you set this parameter to Revertive.
Issue 02 (2011-01-20)
B-93
Default Value 600
Description l This parameter specifies the WTR time. l When the time after the former working channel is restored to normal reaches the preset WTR time, a revertive switching occurs. l You can set WTR Time(s) only when Revertive Mode is set to Revertive. l It is recommended that you use the default value.
Source Slot Source VC4
This parameter specifies the slot of the service source. l This parameter specifies the number of the VC-4 channel where the service source is located. l This parameter cannot be set when Source Slot is set to the slot of the tributary board.
Sink Slot Sink VC4
B-94
Issue 02 (2011-01-20)
Parameter Sink Timeslot Range(e.g.1,3-6)
Value Range -
Default Value -
Description l This parameter specifies the timeslot range of the service sink. l This parameter can be set to a number or several numbers. When setting this parameter to several numbers, use the comma (,) to separate the discrete numbers, or use the endash (-) to represent a consecutive number. For example, the numbers 1, and 3-6 indicate 1, 3, 4, 5, and 6. l This parameter is set according to the planning information.
Configure SNCP Tangent Ring
Selected Deselected
Deselected
l After the Configure SNCP Tangent Ring checkbox is selected, you can quickly configure the SNCP service for the SNCP ring tangent point. l In normal cases, it is recommended that you do not select this checkbox.
Selected Deselected
Selected
l This parameter specifies whether to immediately activate the configured SNCP service. l After the Activate Immediately checkbox is selected, you can immediately activate the created SNCP service.
Related Tasks
A.4.2 Creating Cross-Connections of SNCP Services
B.4.3 Parameter Description: SDH Service Configuration_Converting Normal Services Into SNCP Services
This topic describes the parameters that are used for converting normal services into SNCP services.
Navigation Path
1. 2. 3. Select the NE from the Object Tree in the NE Explorer. Choose Configuration > SDH Service Configuration from the Function Tree. If a bidirectional SDH service is created, select this service in Cross-Connection. Rightclick the selected service and choose Expand to Unidirectional from the shortcut menu. Select the unidirectional service. Right-click the selected service and choose Convert to SNCP Service from the shortcut menu.
Issue 02 (2011-01-20)
B-95

Parameter Service Type Direction Level Value Range SNCP Unidirectional Default Value SNCP Description This parameter indicates that the type of the service to be created is SNCP. This parameter indicates the direction of the SNCP service. l This parameter indicates the level of the SNCP service. l If the service is an E1 service or a data service that is bound with VC-12 channels, the parameter value is VC12. l If the service is a data service that is bound with VC-3 channels, the parameter value is VC3. l If all the services on a VC-4 channel pass through the NE, the parameter value is VC4.
B-96
Issue 02 (2011-01-20)
Parameter Hold-off Time (100ms)
Default Value 0
Description l This parameter specifies the duration of the hold-off time. l When a line is faulty, SNCP switching can be performed on the NE after a delay of time to prevent the situation where the NE performs SNCP switching and other protection switching at the same time. l Hold-off Time(100ms) is generally set to prevent SNCP protection switching, when SNCP works with N+1 protection. Hold-off Time(100ms) must be longer than the switching time of any protection mode that works with SNCP. Generally, Hold-off Time(100ms) is set to 200 ms. l When SNCP works with 1+1 FD/SD, trigger conditions for HSM switching or SNCP switching trigger HSM switching but do not trigger SNCP switching. Therefore, Hold-off Time(100ms) does not need to be set in this case. l The switching time of 1+1 HSB/FD/SD protection is much longer than that of SNCP. Therefore, to shorten service interruptions, it is recommended that you do not set Hold-off Time(100ms) when SNCP works with 1+1 HSB/FD/SD protection. l If only the SNCP scheme is available, it is recommended that you set the hold-off time to 0.
Revertive Mode
Non-Revertive
l This parameter specifies whether to switch the service to the original working channel after the fault is rectified. If this parameter is set to "Revertive", the service is switched from the protection channel to the original working channel. l If this parameter is set to Revertive, the service is switched from the protection channel to the original working channel. If this parameter is set to NonRevertive, the service is not switched from the protection channel to the original working channel. l It is recommended that you set this parameter to Revertive.
Issue 02 (2011-01-20)
B-97
Default Value 600
Description l This parameter specifies the WTR time. l When the time after the former working channel is restored to normal reaches the preset WTR time, a revertive switching occurs. l You can set WTR Time(s) only when Revertive Mode is set to Revertive. l It is recommended that you use the default value.
Source Slot Source VC4
This parameter specifies the slot of the service source. l This parameter specifies the number of the VC-4 channel where the service source is located. l This parameter cannot be set when Source Slot is set to the slot of the tributary board.
Sink Slot Sink VC4
B-98
Issue 02 (2011-01-20)
Parameter Sink Timeslot Range(e.g.1,3-6)
Value Range -
Default Value -
Description l This parameter specifies the timeslot range of the service sink. l This parameter can be set to a number or several numbers. When setting this parameter to several numbers, use the comma (,) to separate the discrete numbers, or use the endash (-) to represent a consecutive number. For example, the numbers 1, and 3-6 indicate 1, 3, 4, 5, and 6. l This parameter is set according to the planning information.
Configure SNCP Tangent Ring
After the Configure SNCP Tangent Ring checkbox is selected, you can quickly configure the SNCP service for the SNCP ring tangent point. l This parameter indicates whether to immediately activate the configured SNCP service. l After the Activate Immediately checkbox is selected, you can immediately activate the created SNCP service.
Related Tasks
A.4.7 Converting a Normal Service into an SNCP Service
B.4.4 Parameter Description: SDH Service Configuration

This topic describes the parameters that are used for configuring SDH services (namely, configuring cross-connections).
Navigation Path
Select the NE from the Object Tree in the NE Explorer. Choose Configuration > SDH Service Configuration from the Function Tree.
Issue 02 (2011-01-20)
B-99
Cross-Connection Parameters
Parameter Level Value Range VC12 VC3 VC4 Default Value Description l This parameter indicates the level of the service. l If the service is an E1 service or a data service that is bound with VC-12 channels, VC12 is displayed. l If the service is a data service that is bound with VC-3 channels, VC3 is displayed. l If all the services on a VC-4 channel pass through the NE, VC4 is displayed. Source Slot Source Timeslot/ Path Sink Slot Sink Timeslot/ Path E1 Priority High Low None This parameter indicates the slot of the service source. This parameter indicates the timeslot or timeslot range of the service source. This parameter indicates the slot of the source sink. This parameter indicates the timeslot or timeslot range of the service sink. l This parameter specifies the priority of an E1 service. l This parameter is available only if the E1 priority function is enabled for the ports configured in the cross-connections. l If E1 Priority is set to High, transmission of the E1 service is ensured in any modulation scheme. l If E1 Priority is set to Low, transmission of the E1 service is ensured only in fullcapacity modulation scheme l If the service priority is not specified during service creation, E1 Priority is None. In this case, the E1 priority of a service needs to be changed after the service is created. Activation Status Yes No Bound Group Number Lockout Status This parameter indicates whether to activate the service. The OptiX RTN 980 does not support this parameter. The OptiX RTN 980 does not support this parameter.
B-100
Issue 02 (2011-01-20)
Parameter Trail Name Schedule No.
Value Range -
Default Value -
Description The OptiX RTN 980 does not support this parameter. The OptiX RTN 980 does not support this parameter.
Parameters for Automatically Generated Cross-Connections

Parameter Level Value Range VC12 VC3 VC4 Default Value Description l This parameter indicates the level of the service. l If the service is an E1 service or a data service that is bound with VC-12 channels, VC12 is displayed. l If the service is a data service that is bound with VC-3 channels, VC3 is displayed. l If all the services on a VC-4 channel pass through the NE, VC4 is displayed. Source Slot Source Timeslot/ Path Sink Slot Sink Timeslot/ Path Lockout Status Trail Name Schedule No. This parameter indicates the slot of the service source. This parameter indicates the timeslot or timeslot range of the service source. This parameter indicates the slot of the source sink. This parameter indicates the timeslot or timeslot range of the service sink. The OptiX RTN 980 does not support this parameter. The OptiX RTN 980 does not support this parameter. The OptiX RTN 980 does not support this parameter.
Related Tasks
A.4.9 Querying TDM Services

This topic describes the parameters that are used for controlling SNCP services.
Navigation Path
Select the NE from the Object Tree in the NE Explorer. Choose Configuration > SNCP Service Control from the Function Tree.

Parameter Service Type Source Value Range Default Value Description This parameter indicates the service protection type of the protection group. This parameter indicates the timeslots where the working service source and protection service source of the protection group are located. This parameter indicates the timeslots where the working service sink and protection service sink of the protection group are located. l This parameter indicates the level of the service. l If the service is an E1 service or a data service that is bound with VC-12 channels, VC12 is displayed. l If the service is a data service that is bound with VC-3 channels, VC3 is displayed. l If all the services on a VC-4 channel pass through the NE, VC4 is displayed. Current Status This parameter indicates the current switching mode and switching status of the services of the protection group. l This parameter indicates or specifies the revertive mode of the service. l This parameter determines whether to switch the service from the protection channel to the original working channel after the fault is rectified. l If this parameter is set to Revertive, the service is switched from the protection channel to the original working channel. If this parameter is set to NonRevertive, the service is not switched from the protection channel to the original working channel. l It is recommended that you set this parameter to Revertive.
Sink
Level
VC12 VC3 VC4
Revertive Mode
Revertive Non-Revertive
B-102
Issue 02 (2011-01-20)
Default Value -
Description l This parameter indicates or specifies the WTR time. l When the time after the former working channel is restored to normal reaches the preset WTR time, a revertive switching occurs. l You can set WTR Time(s) only when Revertive Mode is set to Revertive. l It is recommended that you use the default value.
Hold-off Time (100ms)
0 to 100
l This parameter specifies the duration of the hold-off time. l When a line is faulty, SNCP switching can be performed on the NE after a delay of time to prevent the situation where the NE performs SNCP switching and other protection switching at the same time. l Hold-off Time(100ms) is generally set to prevent SNCP protection switching, when SNCP works with N+1 protection. Hold-off Time(100ms) must be longer than the switching time of any protection mode that works with SNCP. Generally, Hold-off Time(100ms) is set to 200 ms. l When SNCP works with 1+1 FD/SD, trigger conditions for HSM switching or SNCP switching trigger HSM switching but do not trigger SNCP switching. Therefore, Hold-off Time(100ms) does not need to be set in this case. l The switching time of 1+1 HSB/FD/SD protection is much longer than that of SNCP. Therefore, to shorten service interruptions, it is recommended that you do not set Hold-off Time(100ms) when SNCP works with 1+1 HSB/FD/SD protection. l If only the SNCP scheme is available, it is recommended that you set the hold-off time to 0.
Issue 02 (2011-01-20)
B-103
Parameter SD Initiation Condition
Value Range TIM EXC SD UNEQ Null
Default Value Null
Description l This parameter indicates or specifies the conditions that trigger the protection switching of the service. l If TIM is selected, the SNCP service considers the HP_TIM alarm as an automatic switching condition. l If EXC is selected, the SNCP service considers the B3_EXC or BIP_EXC alarm as an automatic switching condition. l If SD is selected, the SNCP service considers the B3_SD or BIP_SD alarm as an automatic switching condition. l If UNEQ is selected, the SNCP service considers the HP_UNEQ or LP_UNEQ alarm as an automatic switching condition. l It is recommended that you set SD Initiation Condition to the same condition for Working Service and Protection Service. l The protection switching conditions in SD Initiation Condition are optional values not included in the default values, and they are set according to the planning information.
Trail Status
This parameter indicates the status of the working service and protection service of the protection group. The OptiX RTN 980 does not support this parameter. This parameter indicates whether the working service or protection service is currently received by the protection group. Displays the trail name.
Service Grouping Active Channel
Trail Name
Related Tasks
A.4.5 Configuring the Automatic Switching of SNCP Services A.4.11 Querying the Protection Status of SNCP Services
B.4.6 Parameter Description: TU_AIS Insertion

This section describes the parameters for TU_AIS insertion.
Navigation Path
In the NE Explorer, select the IF board from the Object Tree and choose Alarm > Triggered Alarm Insertion from the Function Tree.

Table B-1 Parameters on the main interface Parameter Port High Channel Low Channel Insert TU_AIS to E1_AIS Value Range Enable Disable Default Value Disable Description Displays the slot ID of the IF board and the ID of the IF port. Displays the higher order path number of the IF board. Displays the lower order path number of the IF board. If this parameter is set to Enable for an E1 path and the E1 path detects the E1_AIS alarm, the TU_AIS alarm is inserted into this path.
Related Tasks
A.4.4 Inserting TU_AIS A.4.4 Inserting TU_AIS
B.5 Parameters for Board Interfaces

This topic describes the parameters that are related to board interfaces. B.5.1 PDH Port Parameters This topic describes the parameters that are related to PDH ports supported by Smart E1 interface boards. B.5.2 Parameters for the Ports on Ethernet Boards This section describes the parameters for the Ethernet ports on the packet plane. B.5.3 Serial Port Parameters This topic describes the parameters that are related to serial ports. B.5.4 Microwave Interface Parameters This topic describes the parameters that are related to IF_ETH interfaces. B.5.5 IF Board Parameters This topic describes parameters that are related to IF boards. B.5.6 ODU Parameters This topic describes parameters that are related to ODUs. B.5.7 Parameters for SDH Interface Boards
This topic describes parameters that are related to SDH interface boards. B.5.8 Parameters for PDH Interface Boards This topic describes parameters that are related to PDH interface boards. B.5.9 Parameters for Overhead This topic describes the parameters that are related to overhead.
B.5.1 PDH Port Parameters

This topic describes the parameters that are related to PDH ports supported by Smart E1 interface boards. B.5.1.1 Parameter Description: PDH Ports_Basic Attributes This topic describes the parameters that are related to the basic attributes of PDH ports. B.5.1.2 Parameter Description: PDH Ports_Advanced Attributes This topic describes the parameters that are related to the advanced attributes of PDH ports.
B.5.1.1 Parameter Description: PDH Ports_Basic Attributes

This topic describes the parameters that are related to the basic attributes of PDH ports.
Navigation Path
1. 2. In the NE Explorer, select the NE from the Object Tree and choose Configuration > Interface Management > PDH Interface from the Function Tree. Click the General Attributes tab.

Parameter Port Name Value Range Default Value Description Displays the ID of a service port. Specifies or displays the customized port name.
B-106
Issue 02 (2011-01-20)
Parameter Port Mode
Value Range Layer 1 Layer 2 Layer 3
Default Value Layer 3
Description l Specifies the working mode of a PDH port. l When this parameter is set to Layer 1, the port can transmit TDM signals. A port can transmit CES and serial services only if this parameter is set to Layer 1. l When this parameter is set to Layer 2, the port can transmit ATM signals. l For a PDH port, this parameter cannot be set to Layer 3.
Encapsulation Type
l Displays Encapsulation Type of a PDH port. l When Port Mode is Layer 1, Encapsulation Type takes its default value Null. l When Port Mode is Layer 2, Encapsulation Type takes its default value ATM.
Related Tasks
A.5.4.1 Setting Basic Attributes of Smart E1 Ports
B.5.1.2 Parameter Description: PDH Ports_Advanced Attributes

This topic describes the parameters that are related to the advanced attributes of PDH ports.
Navigation Path
1. 2. In the NE Explorer, select the NE from the Object Tree and choose Configuration > Interface Management > PDH Interface from the Function Tree. Click the Advanced Attributes tab.
Issue 02 (2011-01-20)
B-107

Parameter Port Frame Format Value Range Unframe Double Frame CRC-4 Multiframe Default Value CRC-4 Multiframe Description Displays the name of a service port. l Specifies the frame format. l If a CES service uses the emulation mode of CESoPSN, this parameter can assume the value CRC-4 Multiframe or Double Frame. The value CRC-4 Multiframe is recommended. l If a CES service uses the emulation mode of SAToP, this parameter needs to assume the value Unframe. l The value of Frame Format must be the same at the local and opposite ends. Line Encoding Format Displays the line encoding format. The parameter value is always HDB3.
B-108
Issue 02 (2011-01-20)
Parameter Clock Mode
Value Range Master Mode Slave Mode System Clock Mode
Default Value Master Mode
Description l Master Mode: The system clock is used as the output clock of services. l Slave Mode: The CES ACR clock is used as the output clock of services. The port inputting E1 clocks on Slave is set to Slave Mode. l System Clock Mode: The upstream E1 line clock of the opposite equipment is used as the output clock of services. The port inputting E1 clocks on Master is set to System Clock Mode.
Loopback Mode
Non-Loopback Inloop Outloop
Non-Loopback
l Specifies the loopback status for a port. l Non-Loopback indicates that loopbacks are cancelled or not performed. l Inloop indicates that the signals that need to be transmitted to the opposite end are looped back. l Outloop indicates that the received signals are looped back. l This function is used for fault locating for the PDH ports. This function affects services over related ports. Therefore, exercise precaution before starting this function. l Generally, this parameter is set to Non-Loopback.
Issue 02 (2011-01-20)
B-109
Parameter Impedance Frame Mode
Value Range 30 31
Default Value 31
Description Displays the port impedance. l 30 timeslots: In an E1 frame format, timeslots 1 to 15 and 17 to 31 are used to transmit service data, and timeslot 16 is used to transmit signaling. l 31 timeslots: In an E1 frame format, timeslots 1 to 31 are used to transmit service data. l This parameter is unavailable if Frame Format is Unframe. l The port frame modes need to be the same at the local and opposite ends.
Related Tasks
A.5.4.2 Setting Advanced Attributes of Smart E1 Ports
B.5.2 Parameters for the Ports on Ethernet Boards

This section describes the parameters for the Ethernet ports on the packet plane. B.5.2.1 Parameter Description: Ethernet Interface_Basic Attributes This topic describes the parameters that are related to the basic attributes of an Ethernet interface. B.5.2.2 Parameter Description: Ethernet Interface_Flow Control This topic describes the parameters that are related to flow control. B.5.2.3 Parameter Description: Ethernet Interface_Layer 2 Attributes This topic describes the parameters that are related to the Layer 2 attributes. B.5.2.4 Parameter Description: Ethernet Port_Layer 3 Attributes This topic describes the parameters that are related to the Layer 3 attributes of Ethernet ports. B.5.2.5 Parameter Description: Ethernet Interface_Advanced Attributes This topic describes the parameters that are used for configuring the advanced attributes.
B.5.2.1 Parameter Description: Ethernet Interface_Basic Attributes

This topic describes the parameters that are related to the basic attributes of an Ethernet interface.
Navigation Path
1. 2. Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Interface Management > Ethernet Interface from the Function Tree. Click the General Attributes tab.

Parameter Port Name Enable Port Value Range Enabled Disabled Default Value Enabled Description Displays the port name. Specifies the port name. l Specifies whether an Ethernet port is enabled. An Ethernet port can receive, process, and forward Ethernet services only if this parameter is set to Enabled. l Set this parameter according to the planning information. Port Mode Layer 2 Layer 3 Layer 2 l Specifies the mode of the Ethernet port. l If Port Mode is Layer 2, Encapsulation Type can be set to Null, 802.1Q, or QinQ. l If Port Mode is Layer 3, Encapsulation Type can be set to 802.1Q only and the port can carry tunnels.
Issue 02 (2011-01-20)
B-111
Parameter Encapsulation Type
Value Range Null 802.1Q QinQ
Default Value -
Description l This parameter specifies the method of the port to process the received packets. l If you set this parameter to Null, the port transparently transmits the received packets. l If you set this parameter to 802.1Q, the port identifies the packets that comply with the IEEE 802.1q standard. l If you set this parameter to QinQ, the port identifies the packets that comply with the IEEE 802.1ad QinQ standard.
B-112
Issue 02 (2011-01-20)
Parameter Working Mode
Value Range Auto-Negotiation 10M Half-Duplex 10M Full-Duplex 100M Half-Duplex 100M Full-Duplex 1000M Full-Duplex
Default Value Auto-Negotiation
Description l The Ethernet ports of different types support different working modes. l When the equipment on the opposite side works in autonegotiation mode, set the working mode of the equipment on the local side to AutoNegotiation. l When the equipment on the opposite side works in full-duplex mode, set the working mode of the equipment on the local side to 10M Full-Duplex, 100M Full-Duplex, or 1000M Full-Duplex depending on the port rate of the equipment on the opposite side. l When the equipment on the opposite side works in half-duplex mode, set the working mode of the equipment on the local side to 10M Half-Duplex, 100M Half-Duplex, or Auto-Negotiation depending on the port rate of the equipment on the opposite side. l GE electrical ports support 10M fullduplex, 10M halfduplex, 100M fullduplex, 100M halfduplex, 1000M fullduplex, and autonegotiation. l GE optical ports support 1000M fullduplex and autonegotiation.
Issue 02 (2011-01-20)
B-113
Parameter
Value Range
Default Value
Description
NOTE The logical EG2D board does not support halfduplex.
Max Frame Length (byte)
1518 to 9600
1522
The value of this parameter should be greater than the length of any frame to be transported. l This parameter specifies the autonegotiation capability of the Ethernet port. l For GE optical ports, this parameter can be set to 1000M FullDuplex only. l This parameter is valid only when Working Mode is set to AutoNegotiation.
Auto-Negotiation Ability
Auto-Negotiation 10M Half-Duplex 10M Full-Duplex 100M Half-Duplex 100M Full-Duplex 1000M Full-Duplex
FE: 100M Full-Duplex GE: 1000M Full-Duplex
Logical Port Attribute
Optical Port Electrical Port
l This parameter specifies the attribute of the logical port. l The SFP on the EM6F, CSHN board supports the optical port and electrical port.
Physical Port Attribute
This parameter indicates the attribute of the physical port.
Related Tasks
A.5.6.1 Setting the General Attributes of Ethernet Ports
B.5.2.2 Parameter Description: Ethernet Interface_Flow Control

This topic describes the parameters that are related to flow control.
Navigation Path
1. Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Interface Management > Ethernet Interface from the Function Tree.
B-114
2.
Click the Flow Control tab.

Parameter Port Non-Autonegotiation Flow Control Mode Value Range Enable Symmetric Flow Control Disabled Default Value Disabled Description This parameter indicates the port name. l This parameter is valid only when Working Mode is not set to Auto-Negotiation. l The nonautonegotiation flow control mode of the equipment on the local side must be consistent with the nonautonegotiation flow control mode of the equipment on the opposite side Auto-Negotiation Flow Control Mode Enable Symmetric Flow Control Disabled Disabled l This parameter is valid only when Working Mode is set to AutoNegotiation. l The auto-negotiation flow control mode of the equipment on the local side must be consistent with the auto-negotiation flow control mode of the equipment on the opposite side
Related Tasks
A.5.6.2 Configuring the Traffic Control of Ethernet Ports
B.5.2.3 Parameter Description: Ethernet Interface_Layer 2 Attributes

This topic describes the parameters that are related to the Layer 2 attributes.
Navigation Path
1. 2.
Issue 02 (2011-01-20)
Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Interface Management > Ethernet Interface from the Function Tree. Click the Layer 2 Attributes tab.

NOTE
The parameter Layer 2 Attributes is meaningful only when Port Mode is set to Layer 2.
Parameter Port QinQ Type Domain
Value Range -
Default Value -
Description This parameter indicates the port name. l This parameter specifies the QinQ type domain. l When Encapsulation Type in the General Attributes tab page is set to QinQ, you need to set QinQ Type Domain. The default value is 88A8. l When Encapsulation Type in the General Attributes tab page is set to Null or 802.1Q, you cannot set QinQ Type Domain. In this case, QinQ Type Domain is displayed as FFFF and cannot be changed. l QinQ Type Domain should be set to the same value for all the ports on the EM6T/ EM6F board or the EG2D logical board.
B-116
Issue 02 (2011-01-20)
Parameter TAG
Value Range Tag Aware Access Hybrid
Default Value Tag Aware
Description l This parameter specifies the TAG flag of a port. For details about the TAG flags and associated frameprocessing methods, see Table B-2. l If all the accessed services are frames with the VLAN tag (tagged frames), this parameter is set to Tag Aware. l If all the accessed services are frames without the VLAN tag (untagged frames), this parameter is set to Access. l If the accessed services contain tagged frames and untagged frames, this parameter is set to Hybrid.
Default VLAN ID
1 to 4094
l This parameter is valid only when TAG is set to Access or Hybrid. l For details about the functions of this parameter, see Table B-2. l This parameter is set according to the actual situations.
Issue 02 (2011-01-20)
B-117
Parameter VLAN Priority
Value Range 0 to 7
Default Value 0
Description l This parameter is valid only when TAG is set to Access or Hybrid. l For details about the functions of this parameter, see Table B-2. l When the VLAN priority is required to divide streams or to be used for other purposes, this parameter is set according to the planning information. In normal cases, it is recommended that you use the default value.
Table B-2 Methods used by Ethernet interfaces to process data frames Port 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 ports add the VLAN tag, to which Default VLAN ID and VLAN Priority correspond, to the frame and receive the frame. Hybrid The port receives the frame. The ports add the VLAN tag, to which Default VLAN ID and VLAN Priority correspond, to the frame and receive the frame.
Ingress UNI
B-118
Issue 02 (2011-01-20)
Port
Type of Data Frame Tagged frame
Processing Method Tag Aware The port transmits the frame. Access The port strips the VLAN tag from the frame and then transmits the frame. Hybrid 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.
Egress UNI
Related Tasks
A.5.6.3 Setting the Layer 2 Attributes of Ethernet Ports
B.5.2.4 Parameter Description: Ethernet Port_Layer 3 Attributes

This topic describes the parameters that are related to the Layer 3 attributes of Ethernet ports.
Navigation Path
1. 2. In the NE Explorer, select the NE from the Object Tree and choose Configuration > Interface Management > Ethernet Interface from the Function Tree. Click the Layer 3 Attributes tab.

Parameter Port Enable Tunnel Value Range Disabled Enabled Default Value Disabled Description Displays the port name. l If Enable Tunnel is set Enabled, a port identifies and processes MPLS labels. l Enable Tunnel is available if you set Port Mode to Layer 3 in the General Attributes tab.
Parameter Specify IP Address
Value Range Manually Unspecified
Default Value Unspecified
Description l Specifies the method of setting the IP address of a port. l The value Unspecified indicates that the IP addresses do not need to be configured. l The value Manually indicates that the IP address of the port can be manually configured.
IP Address
0.0.0.0
l Specifies the IP address of a port. l This parameter is available when Specify IP Address is Manually. l The IP addresses of different ports on the NE cannot be in the same network segment, but the IP addresses of the ports at both ends of the MPLS tunnel must be in the same network segment.
IP Mask
255.255.255.252
l Specifies the subnet mask of a port. l This parameter is available when Specify IP Address is Manually.
Related Tasks
A.5.6.4 Setting Layer 3 Attributes of Ethernet Ports
B.5.2.5 Parameter Description: Ethernet Interface_Advanced Attributes

This topic describes the parameters that are used for configuring the advanced attributes.
B-120
Issue 02 (2011-01-20)
Navigation Path
1. 2. Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Interface Management > Ethernet Interface from the Function Tree. Click the Advanced Attributes tab.

Parameter Port Port Physical Parameters MAC Loopback Value Range Default Value Description This parameter indicates the port name. This parameter indicates the physical parameters of the port. l This parameter specifies the loopback state at the MAC layer. When this parameter is set to Inloop, the Ethernet signals transmitted to the opposite end are looped back. l In normal cases, it is recommended that you use the default value. PHY Loopback Non-Loopback Inloop Non-Loopback l This parameter specifies the loopback state at the PHY layer. When this parameter is set to Inloop, the Ethernet physical signals transmitted to the opposite end are looped back. l In normal cases, it is recommended that you use the default value. MAC Address This parameter indicates the MAC address of the port. This parameter indicates the rate at which the data packets are transmitted. This parameter indicates the rate at which the data packets are received.
B-121
Non-Loopback Inloop
Non-Loopback
Transmitting Rate(kbit/ s) Receiving Rate(kbit/s)
Issue 02 (2011-01-20)
Parameter Loopback Check
Description This parameter specifies whether to enable loop detection, which is used to check whether a loop exists on the port. This parameter indicates whether to enable the loop port shutdown function. This parameter indicates the egress PIR bandwidth. l This parameter specifies whether to limit the traffic rate of the broadcast packets according to the proportion of the broadcast packets in the total packets. When the equipment at the opposite end may encounter a broadcast storm, this parameter is set to Enabled. l If Ethernet services are E-LAN services, the recommended value is Enabled. l This parameter takes effect only for E-LAN services in the ingress direction.
Loopback Port Shutdown Egress PIR Bandwidth (Kbit/s) Enabling Broadcast Packet Suppression
Enabled Disabled Disabled Enabled
Disabled
Disabled
Broadcast Packet Suppression Threshold
0 to 100
30
When the proportion of the broadcast packets in the total packets exceeds the value of this parameter, the received broadcast packets are discarded. The value of this parameter should be more than the proportion of the broadcast packets in the total packets before the broadcast storm occurs. In normal cases, this parameter is set to default value.
B-122
Issue 02 (2011-01-20)
Related Tasks
B.5.3 Serial Port Parameters

This topic describes the parameters that are related to serial ports. B.5.3.1 Parameter Description: Serial Port_Basic Attributes This topic describes the parameters that are related to the basic attributes of series ports. B.5.3.2 Parameter Description: Serial Port_Creation of Serial Ports This topic describes parameters that are used for creating serial ports.
B.5.3.1 Parameter Description: Serial Port_Basic Attributes

This topic describes the parameters that are related to the basic attributes of series ports.
Navigation Path
1. 2. In the NE Explorer, select the required NE from the Object Tree and choose Configuration > Interface Management > Serial Port from the Function Tree. Click the General Attributes tab.

Parameter Port Value Range Default Value Description Displays the name of the port where a serial service is configured. Specifies or displays the customized port name. l Specifies or displays the serial port level. l 64K Timeslot: 64 kbit/ s timeslots of E1 signals can be bound.
NOTE The OptiX RTN 980 supports 64K Timeslot only.
Name Level
Used Port
Displays the physical port that carries a serial service. Displays the timeslots that a serial service occupies. The timeslots can be consecutive or not.
B-123
64K Timeslot
Issue 02 (2011-01-20)
Parameter Port Mode
Value Range Layer 2 Layer 3
Default Value Layer 3
Description l Displays or specifies the port mode. l A port supports ATM encapsulation if its Port Mode is Layer 2. A port does not support encapsulation if its Port Mode is Layer 3.
Encapsulation Type
l Displays and specifies the encapsulation type of a PW. l When Port Mode is Layer 2, this parameter displays ATM; when Port Mode is Layer 3, this parameter displays Null.
Related Tasks
B.5.3.2 Parameter Description: Serial Port_Creation of Serial Ports

This topic describes parameters that are used for creating serial ports.
Navigation Path
1. 2. In the NE Explorer, select the required NE from the Object Tree and choose Configuration > Interface Management > Microwave Interface from the Function Tree. Click the New tab.

Parameter Port Number(e.g:1,3-6) Value Range Default Value Description Specifies the port where the serial service is configured. Specifies the customized port name.
Name
B-124
Issue 02 (2011-01-20)
Parameter Level
Value Range 64K Timeslot
Default Value 64K Timeslot
Description l Specifies the serial port level. l When this parameter is set to 64K Timeslot , E1 timeslots can be bound.
NOTE The OptiX RTN 980 supports only the parameter value 64K Timeslot .
Used Board Used Port High Channel Low Channel(e.g:1,3-6) 64K Timeslot(e.g:1,3-6)
Specifies the board where a serial port is located. Displays the board where a serial port is located. The OptiX RTN 980 does not support this parameter. The OptiX RTN 980 does not support this parameter. Specifies the 64 kbit/s timeslots to be bound with the serial port. The timeslots can be consecutive or not.
Related Tasks
A.5.5.1 Creating Serial Ports
B.5.4 Microwave Interface Parameters

This topic describes the parameters that are related to IF_ETH interfaces. B.5.4.1 Parameter Description: Microwave Interface_Basic Attributes This topic describes the parameters that are related to the basic attributes of microwave interfaces. B.5.4.2 Parameter Description: Microwave Interface_Layer 2 Attributes This topic describes the parameters that are related to the Layer 2 attributes of microwave interfaces. B.5.4.3 Parameter Description: Microwave Interface_Layer 3 Attributes This topic describes the parameters that are related to the Layer 3 attributes of an IF_ETH port. B.5.4.4 Parameter Description: Microwave Interface_Advanced Attributes This topic describes the parameters that are related to the advanced attributes of microwave interfaces.
B.5.4.1 Parameter Description: Microwave Interface_Basic Attributes

This topic describes the parameters that are related to the basic attributes of microwave interfaces.
Navigation Path
1. 2. Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Interface Management > Microwave Interface from the Function Tree. Click the General Attributes tab.
Parameters
Parameter Port Name Port Mode Value Range Layer 2 Layer 3 Default Value Layer 2 Description This parameter indicates the corresponding IF port. This parameter indicates or specifies the customized port name. l This parameter specifies the IF port mode. l If Port Mode is Layer 2, Encapsulation Type can be set to Null, 802.1Q, or QinQ. l If Port Mode is Layer 3, Encapsulation Type can be set to 802.1Q only and the port can carry tunnels. Encapsulation Type Null 802.1Q QinQ 802.1Q l This parameter specifies the method of the port to process the received packets. l If this parameter is set to Null, the port transparently transmits the received packets. l If this parameter is set to 802.1Q, the port identifies the packets that comply with the IEEE 802.1Q standard. l If this parameter is set to QinQ, the port identifies the packets that comply with the IEEE 802.1ad QinQ standard. MTU (byte) 1518 to 9600 1522 Set this parameter to a value greater than the maximum length of all the data frames to be transmitted.
Related Tasks
B-126
Issue 02 (2011-01-20)

This topic describes the parameters that are related to the Layer 2 attributes of microwave interfaces.
Navigation Path
1. 2. Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Interface Management > Microwave Interface from the Function Tree. Click the Layer 2 Attributes tab.
Parameters for Layer 2 Attributes

NOTE
The parameter Layer 2 Attributes is meaningful only when Port Mode is set to Layer 2.
Parameter Port QinQ Type Domain
Value Range -
Default Value -
Description This parameter indicates the corresponding IF port. l This parameter specifies the QinQ type domain. l This parameter can be set only when Encapsulation Type in General Attributes is set to QinQ.
Tag
Tag Aware Access Hybrid
Tag Aware
l This parameter specifies the TAG flag of a port. For details about the TAG flags and associated frame-processing methods, see Table B-3. l If all the accessed services are frames that contain the VLAN tag (tagged frames), set this parameter to "Tag Aware". l If all the accessed services are frames that do not contain 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 4094
l This parameter is valid only when TAG is set to Access or Hybrid. l For details about the functions of this parameter, see Table B-3. l This parameter needs to be set according to the actual situations.
Issue 02 (2011-01-20)
B-127
Parameter VLAN Priority
Value Range 0 1 2 3 4 5 6 7
Default Value 0
Description l This parameter is valid only when TAG is set to Access or Hybrid. l For details about the functions of this parameter, see Table B-3. l When the VLAN priority is required to divide streams or to be used for other purposes, this parameter needs to be set according to the planning information. In normal cases, it is recommended that you use the default value.
Table B-3 Data frame processing Status 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 receives the frame after the VLAN tag that corresponds to "Default VLAN ID" and "VLAN Priority" is added to the frame. The port strips the VLAN tag from the frame and then transmits the frame. Hybrid The port receives the frame. The port receives the frame after the VLAN tag that corresponds to "Default VLAN ID" and "VLAN Priority" is added to the frame. 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 Port
Egress Port
Tagged frame
The port transmits the frame.
B-128
Issue 02 (2011-01-20)
Related Tasks
A.5.7.2 Setting the Layer 2 Attributes of the IF_ETH Port

This topic describes the parameters that are related to the Layer 3 attributes of an IF_ETH port.
Navigation Path
1. 2. In the NE Explorer, select the required NE from the Object Tree and choose Configuration > Interface Management > Microwave Interface from the Function Tree. Click the Layer 3 Attributes tab.

Parameter Port Enable Tunnel Value Range Disabled Enabled Default Value Disabled Description Displays the corresponding IF port. l A port identifies and processes MPLS labels, if its Enable Tunnel is set Enabled. l Enable Tunnel is available if you set Port Mode to Layer 3 in the General Attributes tab. Specify IP Address Manually Unspecified Unspecified l Specifies the method of setting the IP address of a port. l The value Unspecified indicates that the IP addresses do not need to be configured for a port. l The value Manually indicates that the IP address of a port can be manually configured.
Issue 02 (2011-01-20)
B-129
Parameter IP Address
Value Range -
Default Value 0.0.0.0
Description l Specifies the IP address for a port. l This parameter is available when Specify IP Address is Manually. l The IP addresses of different ports on the NE cannot be in the same network segment, but the IP addresses of the ports at both ends of the MPLS tunnel must be in the same network segment.
IP Mask
255.255.255.252
l Specifies the subnet mask of a port. l This parameter is available when Specify IP Address is Manually.
Related Tasks
A.5.7.3 Setting Layer 3 Attributes of IF_ETH Ports
B.5.4.4 Parameter Description: Microwave Interface_Advanced Attributes

This topic describes the parameters that are related to the advanced attributes of microwave interfaces.
Navigation Path
1. 2. Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Interface Management > Microwave Interface from the Function Tree. Click the Advanced Attributes tab.
Parameters for Advanced Attributes

Parameter Port Value Range Default Value Description This parameter indicates the corresponding IF port.
B-130
Issue 02 (2011-01-20)
Parameter Radio Link ID
Default Value 1
Description l This parameter specifies the ID of the radio link. As the identifier of a radio link, this parameter is used to prevent incorrect connections of radio links between sites. l The ID of each radio link of an NE must be unique, and the link IDs at both ends of a radio link must be the same.
Received Radio Link ID
l This parameter indicates the received ID of the radio link. l If the value of Received Radio Link ID does not match with the preset value of Radio Link ID at the local end, the local end inserts the AIS signal to the downstream direction of the service. At the same time, the local end reports an alarm to the NMS, indicating that the link IDs do not match.
IF Port Loopback
Non-Loopback
l This parameter indicates or specifies the loopback status of the IF interface. l Non-Loopback indicates that the loopback is cancelled or not performed. l Inloop indicates that the IF signals transmitted to the opposite end are looped back. l Outloop indicates that the received IF signals are looped back. l Generally, this parameter is used to locate the faults that occur at each IF interface. The IF loopback is used for diagnosis. If this function is enabled, the services at the related ports are affected. In normal cases, this parameter is set to Non-Loopback.
Issue 02 (2011-01-20)
B-131
Parameter Composite Port Loopback
Value Range Non-Loopback Inloop Outloop
Default Value Non-Loopback
Description l This parameter indicates or specifies the loopback status on the composite interface. l Non-Loopback indicates that the loopback is cancelled or not performed. l Inloop indicates that the composite signals transmitted to the opposite end are looped back. l Outloop indicates that the received composite signals are looped back. l In normal cases, this parameter is set to Non-Loopback.
Error Frame Discard Enabled
Enabled Disabled
Enabled
l This parameter indicates or specifies whether to discard the Ethernet frame when a CRC error occurs in an Ethernet frame. l If the Ethernet service transmitted on the IF_ETH port is a voice service or a video service, you can set this parameter to Disabled.
MAC Address Transmitting Rate (Kbit/s) Receiving Rate (Kbit/s) MAC Loopback
Non-Loopback Inloop
Non-Loopback
This parameter indicates the MAC address of the port. This parameter indicates the transmit rate of the local port. This parameter indicates the receive rate of the local port. l This parameter specifies the loopback state at the MAC layer. When this parameter is set to Inloop, the Ethernet signals transmitted to the opposite end are looped back. l In normal cases, it is recommended that you use the default value.
B-132
Issue 02 (2011-01-20)
Parameter Speed Transmission at L2
Description l If this parameter is set to Enabled, the Layer-2 Ethernet packets transmitted at microwave ports will be compressed to improve transmission efficiency. l If the Layer 2 header compression function can be enabled for the ISU2 or ISX2 board, it is recommended that you set Speed Transmission at L2 to Enabled. l The settings of Speed Transmission at L2 must be the same at both ends of a radio link.
Speed Transmission at L3
Disabled Enabled
Disabled
l If this parameter is set to Enabled, the IP packets transmitted at microwave ports will be compressed to improve transmission efficiency. l If the Layer 3 header compression function can be enabled for the ISU2 or ISX2 board, it is recommended that you set Speed Transmission at L3 to Enabled. l The settings of Speed Transmission at L3 must be the same at both ends of a radio link.
Loopback Check
Disabled Enabled
Disabled
This parameter specifies whether to enable loop detection, which is used to check whether a loop exists on the port. This parameter indicates whether to enable the automatic shut-down of looped ports. l This parameter specifies whether to limit the traffic rate of the broadcast packets according to the proportion of the broadcast packets in the total packets. When the equipment at the opposite end may encounter a broadcast storm, this parameter is set to Enabled. l If Ethernet services are E-LAN services, the recommended value is Enabled. l This parameter takes effect only for ELAN services in the ingress direction.
Loopback Port Shutdown Enabling Broadcast Packet Suppression
Disabled Enabled Disabled Enabled
Disabled
Disabled
Issue 02 (2011-01-20)
B-133
Parameter Enabling Broadcast Packet Suppression Threshold
Default Value 30
Description When the proportion of the broadcast packets in the total packets exceeds the value of this parameter, the received broadcast packets are discarded. The value of this parameter should be more than the proportion of the broadcast packets in the total packets before the broadcast storm occurs. In normal cases, this parameter is set to default value.
Related Tasks
B.5.5 IF Board Parameters

This topic describes parameters that are related to IF boards. B.5.5.1 Parameter Description: IF Interface_IF Attribute This topic describes the parameters that are related to IF attributes. B.5.5.2 Parameter Description: IF Interface_ATPC Attribute This topic describes the parameters that are related to the ATPC attributes. B.5.5.3 Parameter Description: Hybrid_AM Configuration_Advanced Attributes This section describes the parameters that are used for configuring the advanced attributes. B.5.5.4 Parameter Description: ATPC Adjustment Records This topic describes the parameters that are related to ATPC adjustment records. B.5.5.5 Parameter Description: PRBS Test This topic describes the parameters that are related to the pseudorandom binary sequence (PRBS) test.

This topic describes the parameters that are related to IF attributes.
Navigation Path
l l Select the corresponding board from the Object Tree in the NE Explorer. Choose Configuration > IF Interface from the Function Tree. Click the IF Attributes tab.
Parameters
Parameter Port Value Range Default Value Description This parameter indicates the corresponding IF interface.
Issue 02 (2011-01-20)
B-134
Parameter Radio Link IDa
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
Default Value -
Description l This parameter indicates or specifies the work mode of the radio link in "work mode number, service capacity, channel spacing, modulation mode" format. l This parameter is set according to the planning information. The work modes of the IF boards at the two ends of a radio link must be the same.
NOTE The IF1 board supports this parameter.
IF Service Type
Hybrid(Native E1 +ETH) Hybrid(Native STM-1+ETH) SDH
Hybrid(Native E1 +ETH)
l Displays or specifies the type of services carried by the IF board. l If the Integrated IP radio transmits Native E1 services, set this parameter to Hybrid(Native E1+ETH). l If the Integrated IP radio transmits Native STM-1 services, set this parameter to Hybrid(Native STM-1 +ETH). l If the SDH radio transmits SDH services, set this parameter to SDH.
Issue 02 (2011-01-20)
B-135
Parameter Radio Link ID
Default Value 1
Description l This parameter indicates or specifies the ID of a radio link. As the identifier of a radio link, this parameter is used to prevent incorrect connections of radio links between sites. l If the value of Received Radio Link ID does not match the preset value of Link ID at the local end, the local end inserts the AIS signal to the downstream direction of the service. At the same time, the local end reports MW_LIM alarm to the NMS, indicating that the link IDs do not match. l Each radio link of an NE should have a unique link ID, and the link IDs at both ends of a radio link should be the same.
Received Radio Link ID
l This parameter indicates the received ID of the radio link. l If the value of Received Radio Link ID does not match the preset value of Radio Link ID at the local end, the local end inserts the AIS signal to the downstream direction of the service. At the same time, the local end reports an alarm to the NMS, indicating that the link IDs do not match. l When the radio link becomes faulty, this parameter is displayed as an invalid value.
IF Port Loopback
Non-Loopback
l This parameter indicates or specifies the loopback status of the IF interface. l Non-Loopback indicates that the loopback is cancelled or not performed. l Inloop indicates that the IF signals transmitted to the opposite end are looped back. l Outloop indicates that the received IF signals are looped back. l Generally, this parameter is used to locate the faults that occur at each IF interface. The IF loopback is used for diagnosis. If this function is enabled, the services at the related ports are affected. In normal cases, this parameter is set to Non-Loopback.
B-136
Issue 02 (2011-01-20)
Parameter 2M Wayside Enable Statusa
Description l This parameter indicates or specifies whether the radio link transmits the wayside E1 service. l The wayside E1 service can be supported by the IF1 board in the 7,STM-1,28MHz,128QAM, 8,E3,28MHz,QPSK, or 9,E3,14MHz, 16QAM mode.
2M Wayside Input Boarda
l This parameter indicates or specifies the slot in which the 2M wayside service is accessed. l This parameter can be set only when 2M Wayside Enable Status is set to Enabled. l The wayside E1 service can be supported by the IF1 board in the 7,STM-1,28MHz,128QAM, 8,E3,28MHz,QPSK, or 9,E3,14MHz, 16QAM mode.
350 MHz Consecutive Wave Status
Stop Start
Stop
l This parameter indicates or specifies the status of transmitting the 350 MHz carrier signals at the IF interface. l This parameter can be set to Start in the commissioning process only. In normal cases, this parameter is set to Stop. Otherwise, the services are interrupted.
XPIC Enabledb
Enabled Disabled
Enabled
l This parameter indicates or specifies whether the XPIC function of the XPIC IF board is enabled. l If the XPIC IF board does not perform the XPIC function, this parameter should be set to Disabled. In this case, the XPIC cable is required to perform self-loop for the XPIC port on the XPIC IF board.
Enable IEEE-1588 Timeslotc
Enabled Disabled
Disabled
If the OptiX RTN 980 is interconnected with the packet radio equipment, this parameter should be set to Enabled. Otherwise, this parameter should be set to Disabled.
NOTE
l a. The IFU2, IFX2, ISU2, and ISX2 boards do not support way-side services. l b. The IFU2, ISU2, and IF1 boards do not support the XPIC function. l c. The IF1 board does not support the IEEE-1588 timeslot function.
Issue 02 (2011-01-20)
B-137
Parameters for Hybrid/AM Configuration

NOTE
The IF1 board does not support Hybrid/AM configuration.
Parameter Port IF Channel Bandwidth
Value Range 7M 14M 28M 40M 56M
Default Value -
Description This parameter indicates the corresponding IF port. IF Channel Bandwidth indicates the channel spacing of the corresponding radio link. This parameter is set according to the planning information.
NOTE l This parameter is not applicable to the IF1 board. l The IFU2 board does not support the value 40M. l The IFX2 board does not support the values 7M, 14M, and 40M. l The ISX2 board does not support the values 7M and 14M.
AM Enable Status
Disabled Enabled
Disabled
l When this parameter is set to Disabled, the radio link uses only the specified modulation scheme. In this case, you need to select Manually Specified Modulation Mode. l When this parameter is set to Enabled, the radio link uses the corresponding modulation scheme according to the channel conditions. l Hence, the Integrated IP radio can ensure the reliable transmission of the E1 services and provide bandwidth adaptively for the Ethernet services when the AM function is enabled. l The ISX2/ISU2 does not support the AM function when IF Service Type is SDH.
B-138
Issue 02 (2011-01-20)
Parameter Modulation Mode of the Guarantee AM Capacity
Default Value QPSK
Description l This parameter is valid only when AM Enable Status is set to Enabled. l This parameter specifies the lowest-gain modulation scheme that the AM function supports. This parameter is set according to the planning information. 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 scheme.
Modulation Mode of the Full AM Capacity
QPSK
l This parameter is valid only when AM Enable Status is set to Enabled. l This parameter specifies the highest-gain modulation scheme that the AM function supports. This parameter is set according to the planning information. 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 scheme.
Manually Specified Modulation Mode
QPSK
l This parameter specifies the modulation scheme that the radio link uses for signal transmission. l This parameter is valid only when AM Enable Status is set to Disabled.
Issue 02 (2011-01-20)
B-139
Parameter STM-1 Capacity
Value Range -
Default Value -
Description l Specifies the STM-1 capacity of the IF board. l This parameter is available only when IF Service Type is set to Hybrid(Native STM-1+ETH) and SDH. l If IF Service Type is Hybrid(Native STM-1+ETH), this parameter can be set to 0 or 1. l If IF Service Type is SDH, this parameter can be set to 1 or 2.
NOTE The IFU2 and IFX2 boards do not support this parameter.
Enable E1 Priority
Disabled Enabled
Disabled
l This parameter specifies whether to enable the E1 priority function. l This parameter is valid only when AM Enable Status is set to Enabled. l For the ISU2 and ISX2 boards, this parameter is available when IF Service Type is Hybrid(Native E1+ETH).
Guarantee E1 Capacity
l If AM Enable Status is set to Enabled, this parameter needs to be set according to IF Channel Bandwidth, Modulation Mode of the Guarantee AM Capacity, and the actually transmitted services. l If AM Enable Status is set to Disabled, this parameter needs to be set according to IF Channel Bandwidth, Manually Specified Modulation Mode, and the actually transmitted services. l For the ISU2 and ISX2 boards, this parameter is available when IF Service Type is Hybrid(Native E1+ETH).
Guarantee E1 Capacity Range Data Service Bandwidth(Mbit/ s)
Displays the E1 capacity range of the IF board in guarantee capacity modulation mode. Displays the data service bandwidth of the IF board.
B-140
Issue 02 (2011-01-20)
Parameter Full E1 Capacity
Value Range -
Default Value -
Description l This parameter specifies the number of transmitted E1 services in Modulation Mode of the Full AM Capacity. l This parameter is valid if Enable E1 Priority is set to Enabled. l E1 service bandwidth in full capacity mode Service bandwidth in full capacity mode - Service bandwidth in guarantee capacity mode + E1 service bandwidth in guarantee capacity mode. In addition, the number of E1 services in full capacity modulation mode should be smaller than or equal to the maximum number of E1 services in full capacity modulation mode. l The Full E1 Capacity must be set to the same value at both ends of a radio link. l For the ISU2 and ISX2 boards, this parameter is available when IF Service Type is Hybrid(Native E1+ETH).
Full E1 Capacity Transmit-End Modulation Mode Receive-End Modulation Mode Guarantee AM Service Capacity (Mbit/s) Full AM Service Capacity(Mbit/s) Transmitted AM Service Capacity (Mbit/s) Received AM Service Capacity (Mbit/s) E1 Capacity For High Priority
Displays the E1 capacity range of the IF board in full capacity modulation mode. Displays the modulation mode at the transmit mode. Displays the modulation mode at the receive mode. Displays the guarantee AM service capacity.
Displays the full AM service capacity. Displays the transmitted AM service capacity. Displays the received AM service capacity.
Displays the number of configured highpriority E1s.
Related Tasks
A.5.8.1 Setting IF Attributes
A.5.8.4 Querying the AM Status A.5.8.6 Modifying the Hybrid/AM Attributes A.10.4 Configuring the Wayside E1 Service
B.5.5.2 Parameter Description: IF Interface_ATPC Attribute

This topic describes the parameters that are related to the ATPC attributes.
Navigation Path
l l Select the corresponding board from the Object Tree in the NE Explorer. Choose Configuration > IF Interface from the Function Tree. Click the ATPC Attributes tab.
Parameters
Parameter Port ATPC Enable Status Value Range Disabled Enabled Default Value Disabled Description This parameter indicates the corresponding IF interface. l This parameter specifies whether the ATPC function is enabled. l When this parameter is set to Enabled and if the RSL at the receive end is 2 dB higher or lower than the central value between the ATPC upper threshold and the ATPC lower threshold at the receive end, the receiver notifies the transmitter to decrease or increase the transmit power until the RSL is within the range that is 2 dB higher or lower than the central value between the ATPC upper threshold and the ATPC lower threshold. l The settings of the ATPC attributes must be consistent at both ends of a radio link. l In the case of areas where fast fading severely affects the radio transmission, it is recommended that you set this parameter to Disabled. l During the commissioning process, set this parameter to Disabled to ensure that the transmit power is not changed. After the commissioning, re-set the ATPC attributes. ATPC Upper Threshold(dBm) -45.0 l Set the central value between the ATPC upper threshold and the ATPC lower threshold to a value for the expected receive power.
B-142
Issue 02 (2011-01-20)
Parameter ATPC Lower Threshold(dBm)
Value Range -
Default Value -70.0
Description l It is recommended that you set ATPC Upper Threshold(dBm) to the sum of the planned central value between the ATPC upper threshold and the ATPC lower threshold and 10 dB, and ATPC Lower Threshold(dBm) to the difference between the planned central value between the ATPC upper threshold and the ATPC lower threshold and 10 dB. 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).
ATPC Upper Automatic Threshold(dBm) ATPC Lower Automatic Threshold(dBm)
l This parameter indicates that the equipment automatically uses the preset ATPC upper and lower thresholds. l This parameter is valid only when ATPC Automatic Threshold Enable Status is set to Enabled.
Related Tasks
B.5.5.3 Parameter Description: Hybrid_AM Configuration_Advanced Attributes

This section describes the parameters that are used for configuring the advanced attributes.
Navigation Path
l In the NE Explorer, select the IF board, and then choose Configuration > IF Interface from the Function Tree.
Issue 02 (2011-01-20)
Click the AM Advanced Attributes tab.
Parameters
Parameter Port Modulation Mode E1 Capacity Value Range Default Value Description This parameter indicates the corresponding IF interface. Displays the modulation schemes. l You can specify the number of E1s that can be transmitted in intermediate modulation scheme, by setting the advanced attributes correspondingly. l Generally, it is recommended that this parameter takes the default value. To ensure that a specific number of E1s can be transmitted in intermediate modulation scheme, adjust the E1 capacity in each modulation scheme according to the network planning information. l If the E1 priority function is enabled, the maximum number of allowed E1 services in the current mode = Min {[Bandwidth of the air interface in the current mode - (Bandwidth for the assured capacity - Assured E1 number x 2Mbps)]/2Mbps, E1 number in the highest-gain modulation mode}. Data Service Bandwidth(Mbit/ s) Displays the data service bandwidth.
Related Tasks
B.5.5.4 Parameter Description: ATPC Adjustment Records

This topic describes the parameters that are related to ATPC adjustment records.
Navigation Path
Select the corresponding board from the Object Tree in the NE Explorer. Choose Configuration > ATPC Adjustment Records from the Function Tree.
B-144
Issue 02 (2011-01-20)
Parameters
Parameter Port Event NO. Adjustment Time Adjustment Direction Switchover Transmitted Power(dBm) Received Power (dBm) Value Range Default Value Description This parameter indicates the port for the ATPC adjustment. This parameter indicates the number of the ATPC adjustment event. This parameter indicates the time of the ATPC adjustment. This parameter indicates the direction of the adjustment at the port. This parameter indicates the switching operation at the port. This parameter indicates the transmitted power of the port to be switched. This parameter indicates the received power of the port to be switched.
Related Tasks
A.5.8.5 Querying the ATPC Adjustment Records
B.5.5.5 Parameter Description: PRBS Test

This topic describes the parameters that are related to the pseudorandom binary sequence (PRBS) test.
Navigation Path
Select the corresponding board from the Object Tree in the NE Explorer. Choose Configuration > PRBS Test from the Function Tree.
Parameters
Parameter Port Value Range Default Value Description This parameter indicates the port for the PRBS test.
Issue 02 (2011-01-20)
B-145
Parameter Direction
Value Range Cross Tributary
Default Value Cross
Description l This parameter indicates or specifies the direction of the PRBS test. l In the tributary direction, the PRBS test is performed to check the connectivity of the cable from the tributary board to the DDF. l In the cross-connect direction, the PRBS test is performed to check the processing of the service from the tributary board to the NE at the remote end.
Duration Measured Time
1 to 255 s 10min h
1 s
This parameter indicates or specifies the duration of the PRBS test. This parameter indicates or specifies the time unit used for the PRBS test.
Start Time Progress Total PRBS Accumulating Mode
Selected Deselected
Deselected
This parameter indicates the start time of the PRBS test. This parameter indicates the progress percentage of the PRBS test. This parameter indicates the number of bit errors that occur in the PRBS test. This parameter specifies whether to display the values in accumulative mode. If Accumulating Mode is selected, it indicates that the values are displayed in accumulative mode.
B.5.6 ODU Parameters

This topic describes parameters that are related to ODUs. B.5.6.1 Parameter Description: ODU Interface_Radio Frequency Attribute This topic describes the parameters that are related to radio frequency attributes of an ODU. B.5.6.2 Parameter Description: ODU Interface_Power Attributes This topic describes the parameters that are used for configuring the power attributes of the ODU. B.5.6.3 Parameter Description: ODU Interface_Equipment Information This topic describes the parameters that are used for configuring the equipment information of the ODU. B.5.6.4 Parameter Description: ODU Interface_Advanced Attributes This topic describes the parameters that are used for configuring the advanced attributes of the ODU.
B.5.6.1 Parameter Description: ODU Interface_Radio Frequency Attribute

This topic describes the parameters that are related to radio frequency attributes of an ODU.
Navigation Path
l l Select the ODU from the Object Tree in the NE Explorer. Choose Configuration > ODU Interface from the Function Tree. Click the Radio Frequency Attributes tab.
Parameters
Parameter Board Transmit Frequency(MHz) Value Range Default Value Description This parameter indicates the corresponding ODU. l This parameter indicates or specifies the transmit frequency of the ODU, namely, the central frequency of the channel. l The value of this parameter must not be less than the sum of the minimum transmit frequency supported by the ODU and a half of the channel spacing, and must not be more than the difference between the maximum transmit frequency supported by the ODU and a half of the channel spacing. l The difference between the transmit frequencies at both ends of a radio link should be one T/R spacing. l This parameter is set according to the planning information.
Issue 02 (2011-01-20)
B-147
Value Range -
Default Value -
Description l This parameter indicates or specifies the spacing between the transmit frequency and receive frequency of the ODU to prevent mutual interference of the transmitter and receiver. l If the ODU is a Tx high station, the transmit frequency is one T/R spacing higher than the receive frequency. If the ODU is a Tx low station, the transmit frequency is one T/R spacing lower than the receive frequency. l If the ODU supports only one T/R spacing, this parameter is set to 0, indicating that the T/R spacing supported by the ODU is used. l A valid T/R spacing value is determined by the ODU itself, and the T/R spacing should be set according to the technical specifications of the ODU. l The T/R spacing of the ODU should be set to the same value at both ends of a radio link.
Actual Transmit Frequency(MHz) Actual Receive Frequency(MHz) Actual T/R Spacing(MHz) The range of frequency point (MHz)
This parameter indicates the actual transmit frequency of the ODU. This parameter indicates the actual receive frequency of the ODU. This parameter indicates the actual T/R spacing of the ODU. This parameter indicates the working range of the frequency of the ODU.
Related Tasks
A.5.9.1 Setting the Transmit Frequency Attribute of the ODU
B.5.6.2 Parameter Description: ODU Interface_Power Attributes

This topic describes the parameters that are used for configuring the power attributes of the ODU.
Navigation Path
l Select the ODU from the Object Tree in the NE Explorer. Choose Configuration > ODU Interface from the Function Tree.
B-148
Click the Power Attributes tab.
Parameters
Parameter Board Maximum Transmit Power (dBm) Value Range Default Value Description This parameter indicates the corresponding ODU. l This parameter specifies the maximum transmit power of the ODU. This parameter cannot be set to a value that exceeds the nominal power rang of the ODU in the guaranteed capacity modulation module. l This parameter is set to limit the maximum transmit power of the ODU within this preset range. l The maximum transmit power adjusted by using the ATPC function should not exceed this value. l This parameter is set according to the planning information. Transmit Power (dBm) l This parameter specifies the transmit power of the ODU. This parameter cannot be set to a value that exceeds the nominal power rang of the ODU or a value that exceeds Maximum Transmit Power(dBm). l It is recommended that you set the transmit power of the ODU to the same value at both ends of a radio link. l Consider the receive power of the ODU at the opposite end when you set this parameter. Ensure that the receive power of the ODU at the opposite end can ensure stable radio services. l This parameter is set according to the planning information.
Issue 02 (2011-01-20)
B-149
Parameter Power to Be Received(dBm)
Default Value -10.0
Description l This parameter is used to set 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 misalignment indicating function. l When the antenna misalignment indicating function is enabled, if the actual receive power of the ODU is 3 dB lower than the power expected to be received, the ODU indicator on the IF board connected to the ODU blinks yellow (300 ms on, 300 ms off), indicating that the antenna is not aligned. l After the antenna alignment, after the state that the antenna is aligned lasts for 30 minutes, the NE automatically disables the antenna misalignment indicating function. l When this parameter takes the default value, the antenna misalignment indicating function is disabled. l This parameter is set according to the planning information.
TX High Threshold(dBm)
l If the value of the actual transmit power of the ODU is greater than the preset value of TX High Threshold(dBm), the system separately records the duration when the value of the actual transmit power of the ODU is greater than the preset value of TX High Threshold (dBm) and the duration when the value of the actual transmit power of the ODU is greater than the preset value of TX Low Threshold(dBm) in the performance events. l If the value of the actual transmit power of the ODU is greater than the preset value of TX Low Threshold(dBm) and is lower than the preset value of TX High Threshold(dBm), the system records the duration when the value of the actual transmit power of the ODU is greater than the preset value of TX Low Threshold(dBm) in the performance events.
B-150
Issue 02 (2011-01-20)
Parameter TX Low Threshold (dBm)
Value Range -
Default Value -
Description l If the value of the actual transmit power of the ODU is lower than the preset value of TX Low Threshold(dBm), the system does not record it. l TX High Threshold(dBm) and TX Low Threshold(dBm) are valid only when the ATPC function is enabled.
RX High Threshold(dBm)
l If the value of the actual receive power of the ODU is lower than the preset value of RX Low Threshold(dBm), the system records the duration when the value of the actual receive power of the ODU is lower than the preset value of RX Low Threshold(dBm) and duration when the value of the actual transmit power of the ODU is lower than the preset value of RX High Threshold (dBm)in the performance events. l If the value of the actual receive power of the ODU is greater than the preset value of RX Low Threshold(dBm) and is lower than the preset value of RX High Threshold(dBm), the system records the duration when the value of the actual receive power of the ODU is Lower than the preset value of RX High Threshold (dBm) in the performance events. l If the value of the actual receive power of the ODU is greater than the preset
Issue 02 (2011-01-20)
B-151
Parameter RX Low Threshold (dBm)
Value Range -
Default Value -
Description value of RX High Threshold(dBm), the system does not record it.
Actual Transmit Power(dBm)
l This parameter indicates the actual transmit power of the ODU. l If the ATPC function is enabled, the queried actual transmit power may be different from the preset value.
Actual Receive Power(dBm) Actual range of Power(dBm) Transmission Power Type
This parameter indicates the actual receive power of the ODU. This parameter indicates the range of the actual transmit power of the ODU. This parameter indicates the level of the output power of the ODU.
Related Tasks
B.5.6.3 Parameter Description: ODU Interface_Equipment Information

This topic describes the parameters that are used for configuring the equipment information of the ODU.
B-152
Issue 02 (2011-01-20)
Navigation Path
l l Select the corresponding board from the Object Tree in the NE Explorer. Choose Configuration > ODU Interface from the Function Tree. Click the Equipment Information tab.
Parameters
Parameter Board Frequency(GHz) Equipment Type Value Range Default Value Description This parameter indicates the corresponding ODU. This parameter indicates the frequency band where the ODU operates. l This parameter indicates the equipment type of the ODU. l PDH and SDH indicate the transmission capacity only and are irrelevant to the type of transmitted service. T/R Spacing(MHz) Intermediate Frequency Bandwidth (MHz) IF Bandwidth Type Station Type This parameter indicates the T/R spacing of the ODU. This parameter indicates the IF frequency bandwidth of the ODU. Displays the IF bandwidth type. l This parameter indicates whether the ODU is a Tx high station or a Tx low station. l The transmit frequency of a Tx high station is one T/R spacing higher than the transmit frequency of a Tx low station. Transmission Power Type Produce Time Produce SN This parameter indicates the level of the output power of the ODU. This parameter indicates the manufacturing time of the ODU. This parameter indicates the manufacturing serial number and the manufacturer code of the ODU.
Related Tasks
A.5.9.2 Querying the ODU Attribute
Issue 02 (2011-01-20)
B-153
B.5.6.4 Parameter Description: ODU Interface_Advanced Attributes

This topic describes the parameters that are used for configuring the advanced attributes of the ODU.
Navigation Path
l l Select the ODU from the Object Tree in the NE Explorer. Choose Configuration > ODU Interface from the Function Tree. Click the Advanced Attributes tab.
Parameters
Parameter Board RF Loopback Value Range Non-Loopback Inloop Default Value Non-Loopback Description This parameter indicates the corresponding ODU. l This parameter indicates or specifies the loopback status of the RF interface of the ODU. l Non-Loopback indicates that the loopback is canceled or not performed. l Inloop indicates that the RF signals transmitted to the opposite end are looped back. l This function is used for fault locating for the RF interfaces. The RF Loopback function is used for diagnosis and may affect the services that are transmitted over the interfaces. Hence, exercise precaution before starting this function. l In normal cases, this parameter is set to Non-Loopback. Configure Transmission Status unmute mute unmute l This parameter indicates or specifies the transmit status of the ODU. l If this parameter is set to mute, the transmitter of the ODU does not work but can normally receive microwave signals. l If this parameter is set to unmute, the ODU can normally transmit and receive microwave signals. l In normal cases, this parameter is set to unmute. Actual Transmission Status
B-154
Displays the ODU manufacturer information.
Issue 02 (2011-01-20)
Parameter Factory Information Remarks
Value Range -
Default Value -
Description This parameter indicates the manufacturer information about the ODU. Specifies the remarks of the ODU. No Chinese character is allowed.
Related Tasks
A.5.9.4 Setting the Advanced Attributes of the ODU
B.5.7 Parameters for SDH Interface Boards

This topic describes parameters that are related to SDH interface boards. B.5.7.1 Parameter Description: SDH Interfaces This topic describes the parameters that are related to the SDH interfaces. B.5.7.2 Parameter Description: Automatic Laser Shutdown This topic describes the parameters that are related to the automatic laser shutdown (ALS) function.
B.5.7.1 Parameter Description: SDH Interfaces

This topic describes the parameters that are related to the SDH interfaces.
Navigation Path
l l Select the corresponding board from the Object Tree in the NE Explorer. Choose Configuration > SDH Interface from the Function Tree. Select By Board/Port(Channel), and select Port or VC4 Channel from the list box.
Parameters
Parameter Port Optical Interface Namea Laser Switcha Value Range On Off Default Value On Description This parameter indicates the corresponding SDH interface. This parameter indicates or specifies the name of the optical interface. l This parameter indicates or specifies the on/off state of the laser. l This parameter is set for SDH optical interfaces only. l In normal cases, this parameter is set to On.
Issue 02 (2011-01-20)
B-155
Parameter Optical(Electrical) Interface Loopbacka
Value Range Non-Loopback Inloop Outloop
Default Value Non-Loopback
Description l This parameter indicates or specifies the loopback status on the SDH interface. l Non-Loopback indicates that the loopback is canceled or not performed. l Inloop indicates that the SDH signals transmitted to the opposite end are looped back. l Outloop indicates that the received SDH signals are looped back. l This function is used for fault locating for the SDH interfaces. The Optical (Electrical) Interface Loopback function is used for diagnosis and may affect the services that are transmitted over the interfaces. Hence, exercise precaution before starting this function. l In normal cases, this parameter is set to Non-Loopback.
VC4 Loopbackb
Non-Loopback
l This parameter indicates or specifies the loopback status in the VC-4 path. l Non-Loopback indicates that the loopback is canceled or not performed. l Inloop indicates that the VC-4 signals transmitted to the opposite end are looped back. l Outloop indicates that the received VC-4 signals are looped back. l This function is used for fault locating for the VC-4 paths. The VC4 Loopback function is used for diagnosis and may affect the services that are transmitted over the interfaces. Hence, exercise precaution before starting this function. l In normal cases, this parameter is set to Non-Loopback.
NOTE
l a: Indicates the parameters that are supported when Port is selected from the list box. l b: Indicates the parameters that are supported when VC4 Channel is selected from the list box.
Related Tasks
A.5.1 Setting the Parameters of SDH Ports
B.5.7.2 Parameter Description: Automatic Laser Shutdown

This topic describes the parameters that are related to the automatic laser shutdown (ALS) function.
Navigation Path
Select the corresponding board from the Object Tree in the NE Explorer. Choose Configuration > Automatic Laser Shutdown from the Function Tree.
Parameters
Parameter Optical Interface Automatic Shutdown Value Range Disabled Enabled Default Value Disabled Description This parameter indicates the corresponding optical interface. l This parameter indicates or specifies whether the Automatic Laser Shutdown function is enabled or disabled for the laser. l The ALS function allows the laser to shut down automatically when an optical port does not carry services, an optical fiber is broken, or no optical signal is received. l You can set On Period(ms), Off Period (ms), and Continuously On-test Period (ms) only when this parameter is set to Enabled. On Period(ms) 1000 to 3000 2000 This parameter indicates or specifies the period when a shutdown laser automatically starts up and tests whether the optical fiber is normal. This parameter indicates or specifies the period when the laser does not work (with the ALS function being enabled). This parameter indicates or specifies the period when a shutdown laser is manually started up and tests whether the optical fiber is normal.
Off Period(ms)
2000 to 300000
60000
Continuously Ontest Period(ms)
2000 to 300000
90000
B.5.8 Parameters for PDH Interface Boards

This topic describes parameters that are related to PDH interface boards. B.5.8.1 Parameter Description: PDH Interfaces This topic describes the parameters that are related to the PDH interfaces. B.5.8.2 Parameter Description: PRBS Test
B.5.8.1 Parameter Description: PDH Interfaces

This topic describes the parameters that are related to the PDH interfaces.
Navigation Path
l l l Select the corresponding board from the Object Tree in the NE Explorer. Choose Configuration > PDH Interface from the Function Tree. Select By Board/Port(Channel). Select Port from the list box.
Parameters
Parameter Port Port Name Tributary Loopback Value Range Non-Loopback Inloop Outloop Default Value Non-Loopback Description This parameter indicates the corresponding port. This parameter indicates or specifies the name of the port. l This parameter indicates or specifies the loopback status in the associated path of the tributary unit. l Non-Loopback indicates that the loopback is canceled or not performed. l Inloop indicates that the PDH signals transmitted to the opposite end are looped back. l Outloop indicates that the received PDH signals are looped back. l This function is used for fault locating for the paths of the tributary unit. The Tributary Loopback function is used for diagnosis and may affect the services that are transmitted over the interfaces. Hence, exercise precaution before starting this function. l In normal cases, this parameter is set to Non-Loopback. Port Impedance This parameter indicates the impedance of a path, which depends on the tributary unit.
B-158
Issue 02 (2011-01-20)
Parameter Service Load Indication
Value Range Load Non-Loaded
Default Value Load
Description l This parameter indicates or specifies the service loading status in a specific path. l When this parameter is set to Load, the board detects whether alarms exist in the path. l When this parameter is set to NonLoaded, the board does not detect whether there are alarms in the path. l If a path does not carry any services, you can set this parameter to Non-Loaded for the path to mask all the alarms. If a path carries services, you need to set this parameter to Load for the path.
Retiming Mode
Normal Retiming Mode of Tributary Clock Retiming Mode of Cross-Connect Clock
Normal
l This parameter indicates or specifies the retiming mode of a specific path. l By using the retiming function, the retiming reference signal from the SDH network and the service data signal are combined and then sent to the client equipment, thus decreasing the output jitter in the signal. In this way, the retiming function ensures that the service code flow can normally transfer the retiming reference signal. l When this parameter is set to Normal, the retiming function is not used. l When this parameter is set to Retiming Mode of Tributary Clock, the retiming function is used with the clock of the upstream tributary unit traced. l When this parameter is set to Retiming Mode of Cross-Connect Clock, the retiming function is used with the clock of the cross-connect unit traced. l It is recommended that the external clock, instead of the retiming function, should be used to provide reference clock signals for the equipment. l If the retiming function is required, it is recommended that you set this parameter to Retiming Mode of Cross-connect Clock.
Port Service Type
This parameter indicates the type of services that are processed in a path. It depends on the services that are transmitted in a path.
Issue 02 (2011-01-20)
B-159
Parameter Input Signal Equalization
Value Range Unequalized Equalized
Default Value Unequalized
Description l This parameter indicates whether the input signals are equalized. l It is recommended that you set this parameter to default value.
Related Tasks
A.5.2 Setting the Parameters of PDH Ports
B.5.8.2 Parameter Description: PRBS Test

Navigation Path
Select the corresponding board from the Object Tree in the NE Explorer. Choose Configuration > PRBS Test from the Function Tree.
Parameters
Parameter Port Direction Value Range Cross Tributary Default Value Cross Description This parameter indicates the port for the PRBS test. l This parameter indicates or specifies the direction of the PRBS test. l In the tributary direction, the PRBS test is performed to check the connectivity of the cable from the tributary board to the DDF. l In the cross-connect direction, the PRBS test is performed to check the processing of the service from the tributary board to the NE at the remote end. Duration Measured Time 1 to 255 s 10min h Start Time Progress This parameter indicates the start time of the PRBS test. This parameter indicates the progress percentage of the PRBS test.
Issue 02 (2011-01-20)
1 s
This parameter indicates or specifies the duration of the PRBS test. This parameter indicates or specifies the time unit used for the PRBS test.
B-160
Parameter Total PRBS Accumulating Mode
Description This parameter indicates the number of bit errors that occur in the PRBS test. This parameter specifies whether to display the values in accumulative mode. If Accumulating Mode is selected, it indicates that the values are displayed in accumulative mode.
B.5.9 Parameters for Overhead

This topic describes the parameters that are related to overhead. B.5.9.1 Parameter Description: Regenerator Section Overhead This topic describes the parameters that are related to the regenerator section overheads (RSOHs). B.5.9.2 Parameter Description: VC-4 POHs This topic describes the parameters that are related to the VC-4 path overheads (POHs). B.5.9.3 Parameter Description: VC-12 POHs This topic describes the parameters that are related to the VC-12 path overheads (POHs).
B.5.9.1 Parameter Description: Regenerator Section Overhead

This topic describes the parameters that are related to the regenerator section overheads (RSOHs).
Navigation Path
1. 2. Select an SDH interface board in the NE Explorer Choose Configuration > Overhead Management > Regenerator Section Overhead from the Function Tree. Choose Display in Text Format or Display in Hexadecimal.
Parameters for Setting the Display Format

Parameter Display in Text Format Display in Hexadecimal Value Range Selected Deselected Selected Deselected Deselected Default Value Selected Description This parameter specifies the display in the text format. This parameter specifies the display in the hexadecimal format.
Issue 02 (2011-01-20)
B-161

Parameter Object J0 to be Sent ([Mode]Content) Value Range Default Value [16 Bytes]HuaWei SBS Description This parameter indicates the object to be set. If the NE at the opposite end reports the J0_MM alarm, this parameter is set according to the J0 byte to be received at the opposite end. l This parameter specifies the J0 byte to be received. l If this parameter is set to [Disabled], the board does not monitor the received J0 byte. l It is recommended that you use the default value. J0 Received ([Mode]Content) This parameter indicates the J0 byte that is actually received.
J0 to be Received ([Mode]Content)
[Disabled]
Related Tasks
A.5.3.1 Configuring RSOHs

This topic describes the parameters that are related to the VC-4 path overheads (POHs).
Navigation Path
1. 2. Select SDH interface board from the Object Tree in the NE Explorer. Choose Configuration > Overhead Management > VC4 Path Overhead from the Function Tree. Choose Display in Text Format or Display in Hexadecimal.

B-162
Issue 02 (2011-01-20)
Parameters for the Trace Byte J1

Parameter Object J1 to be Sent ([Mode]Content) Value Range Default Value [16 Bytes]HuaWei SBS Description This parameter indicates the object to be set. If the NE at the opposite end reports the HP_TIM or LP_TIM alarm, this parameter is set according to the J1 byte to be received at the opposite end. l If this parameter is set to [Disabled], the board does not monitor the received J1 byte. l It is recommended that you use the default value. J1 Received ([Mode]Content) This parameter displays the J1 byte that is actually received.
J1 to be Received ([Mode]Content)
[Disabled]
Parameters for the Signal Flag C2

Parameter Object C2 to be Sent Value Range Default Value Description This parameter indicates the object to be set. If the NE at the opposite end reports the HP_SLM alarm, this parameter is set according to the C2 byte to be received at the opposite end. If the NE at the local end reports the HP_SLM alarm, this parameter is set according to the C2 byte to be sent at the opposite end. This parameter displays the C2 byte that is actually received.
C2 to be Received
C2 Received
Parameters for Overhead Termination

Parameter Object Value Range Default Value Description This parameter indicates the object to be set.
Issue 02 (2011-01-20)
B-163
Parameter VC4 Overhead Termination
Value Range Termination Pass-Through Auto
Default Value Auto
Description l If this parameter is set to PassThrough, the NE forwards the original overhead after monitoring the VC-4 path overhead regardless of the C2 byte. l If this parameter is set to Termination, the NE generates the new VC-4 path overhead according to the board setting after monitoring the VC-4 path overhead regardless of the C2 byte. l If this parameter is set to Auto, the VC-4 path overhead in the VC-4 pass-through service is passed through, and the VC-4 path overhead in the VC-12 service is terminated. l It is recommended that you use the default value.
Related Tasks

This topic describes the parameters that are related to the VC-12 path overheads (POHs).
Navigation Path
1. Select the corresponding board from the Object Tree in the NE Explorer. Choose Configuration > Overhead Management > VC12 Path Overhead from the Function Tree. Choose Display in Text Format or Display in Hexadecimal.
2.

B-164
Issue 02 (2011-01-20)
Parameters for the Trace Byte

Parameter Object J2 to be Sent Value Range Default Value [16 Bytes]HuaWei SBS Description This parameter indicates the object to be set. If the NE at the opposite end reports the LP_TIM or LP_TIM_VC12 alarm, this parameter is set according to the J2 byte to be received by the NE at the opposite end. l If this parameter is set to [Disabled], the board does not monitor the received J2 byte. l It is recommended that you use the default value.
NOTE IF boards do not support this parameter.
J2 to be Received
[Disabled]
J2 Received
This parameter displays the J2 byte that is actually received.
Related Tasks
B.6 Parameters for Ethernet Services and Ethernet Features on the Packet Plane
This section describes the parameters for the Ethernet services and Ethernet features on the packet plane, including service parameters, protocol parameters, OAM parameters, Ethernet port parameters, and QoS parameters. B.6.1 Parameters for Ethernet Services This topic describes the parameters that are related to Ethernet services. B.6.2 Parameters for Ethernet Protocols This topic describes the parameters that are related to the Ethernet protocol. B.6.3 Parameters for the Ethernet OAM This topic describes the parameters that are related to the Ethernet operation, administration and maintenance (OAM). B.6.4 QoS Parameters This topic describes the parameters that are related to QoS.
B.6.1 Parameters for Ethernet Services

This topic describes the parameters that are related to Ethernet services. B.6.1.1 Parameter Description: E-Line Service_Creation
This topic describes the interface parameters that are used for creating an Ethernet line (E-Line) service. B.6.1.2 Parameter Description: E-Line Service This topic describes the parameters that are related to E-Line services. B.6.1.3 Parameter Description: VLAN Forwarding Table Item_Creation This topic describes the parameters that are used for creating VLAN forwarding table items. B.6.1.4 Parameter Description: E-LAN Service_Creation This topic describes the parameters that are used for creating an Ethernet local area network (ELAN) service. B.6.1.5 Parameter Description: E-LAN Service This topic describes the parameters that are related to E-LAN services. B.6.1.6 Parameter Description: QinQ Link_Creation This topic describes the parameters that are used for creating a QinQ link.

This topic describes the interface parameters that are used for creating an Ethernet line (E-Line) service.
Navigation Path
1. 2. Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Ethernet Service Management > E-Line Service from the Function Tree. Click New.

Table B-4 Service direction of UNI-UNI Parameter Service ID Value Range 1 to 4294967294 Default Value Description This parameter specifies the ID of the E-Line service. This parameter specifies the name of the E-Line service. l This parameter specifies the direction of the E-Line service. l Set this parameter to UNI-UNI.
Service Name
Direction
UNI-UNI UNI-NNI NNI-NNI
UNI-UNI
B-166
Issue 02 (2011-01-20)
Parameter BPDU
Value Range Not Transparently Transmitted Transparently Transmitted
Default Value Not Transparently Transmitted
Description l This parameter specifies the transparent transmission ID of the bridge protocol data unit (BPDU) packets. It is used to indicate whether the E-Line service transparently transmits the BPDU packets. l If the BPDU packets are used as the service packets and transparently transmitted to the opposite end, set this parameter to Transparently Transmitted. That is, the parameter value Transparently Transmitted takes effect only if Encapsulation Type of the source and sink ports of the E-Line service are Null. l In other cases, set this parameter to Not Transparently Transmitted. l This parameter is set according to the planning information.
MTU(byte) Service Tag Role
This parameter cannot be set here. The OptiX RTN 980 does not support this parameter.
Issue 02 (2011-01-20)
B-167
Parameter Source Port
Value Range -
Default Value -
Description l Before setting this parameter, check and ensure that the attributes in Ethernet Interface of the port are set correctly and are the same as the planning information. l The value of this parameter cannot be the same as the value of sink port. l The value of this parameter cannot be used for the E-LAN port. l This parameter is set according to the planning information.
B-168
Issue 02 (2011-01-20)
Parameter Source VLANs
Default Value -
Description l This parameter can be set to null, a number, or several numbers. When setting this parameter to several numbers, use the comma (,) to separate the discrete numbers, or use the endash (-) to represent a consecutive number. For example, the numbers 1, and 3-6 indicate 1, 3, 4, 5, and 6. l The number and value of VLANs must be the same value of Sink VLANs. l If this parameter is set to null, all the services at the source port are used as the service source. l If this parameter is not set to null, only the service that contains the VLAN ID at the source port can be used as the service source.
Issue 02 (2011-01-20)
B-169
Parameter Sink Port
Value Range -
Default Value -
Description l Before setting this parameter, check and ensure that the attributes in Ethernet Interface of the port are set correctly and are the same as the planning information. l The value of this parameter cannot be the same as the value of Source Port. l The value of this parameter cannot be used for the E-LAN port. l This parameter is set according to the planning information.
B-170
Issue 02 (2011-01-20)
Parameter Sink VLANs
Default Value -
Description l This parameter can be set to null, a number, or several numbers. When setting this parameter to several numbers, use the comma (,) to separate the discrete numbers, or use the endash (-) to represent a consecutive number. For example, the numbers 1, and 3-6 indicate 1, 3, 4, 5, and 6. l The number and value of VLANs must be the same value of Source VLANs. l If this parameter is set to null, all the services at the sink port are used as the service sink. l If this parameter is not set to null, only the service that contains the VLAN ID at the sink port can be used as the service sink.
Table B-5 Service direction of UNI-NNI (carried by PWs) Parameter Service ID Value Range 1 to 4294967294 Default Value Description This parameter specifies the ID of the E-Line service. This parameter specifies the name of the E-Line service. l This parameter specifies the direction of the E-Line service. l Set this parameter to UNI-NNI.
Service Name
Direction
UNI-UNI
Issue 02 (2011-01-20)
B-171
Parameter BPDU
Value Range Not Transparently Transmitted Transparently Transmitted
Default Value Not Transparently Transmitted
Description For UNI-NNI ETH PWE3 services, the parameter value is always Not Transparently Transmitted . This parameter cannot be set here. The OptiX RTN 980 does not support this parameter. l Before setting this parameter, check and ensure that the attributes in Ethernet Interface of the port are set correctly and are the same as the planning information. l The value of this parameter cannot be the same as the value of sink port. l The value of this parameter cannot be used for the E-LAN port. l This parameter is set according to the planning information.
Source Port
B-172
Issue 02 (2011-01-20)
Parameter Source VLANs
Default Value -
Description l This parameter can be set to null, a number, or several numbers. When setting this parameter to several numbers, use the comma (,) to separate the discrete numbers, or use the endash (-) to represent a consecutive number. For example, the numbers 1, and 3-6 indicate 1, 3, 4, 5, and 6. l If this parameter is set to null, all the services at the source port are used as the service source. l If this parameter is not set to null, only the service that contains the VLAN ID at the source port can be used as the service source.
PRI
The OptiX RTN 980 does not support this parameter. For UNI-NNI ETH PWE3 services, the parameter value is always PW.
Bearer Type
QinQ Link PW
PW
Issue 02 (2011-01-20)
B-173
Parameter Protection Type
Value Range No Protection PW APS Slave Protection Pair
Default Value No Protection
Description l If this parameter is set to PW APS, working and protection PWs need to be configured. l If this parameter is set to Slave Protection Pair, you need to bind the slave PW APS protection group with the master PW APS protection group. The switching of the master PW APS protection group triggers the switching of the slave PW APS protection group simultaneously.
Table B-6 Service direction of UNI-NNI (carried by QinQ links) Parameter Service ID Value Range 1 to 4294967294 Default Value Description This parameter specifies the ID of the E-Line service. This parameter specifies the name of the E-Line service. l This parameter specifies the direction of the E-Line service. l Set this parameter to UNI-NNI. Not Transparently Transmitted For UNI-NNI QinQ services, the parameter value is always Not Transparently Transmitted . This parameter cannot be set here. The OptiX RTN 980 does not support this parameter.
Issue 02 (2011-01-20)
Service Name
Direction
UNI-UNI
BPDU
Not Transparently Transmitted Transparently Transmitted
B-174
Parameter Source Port
Value Range -
Default Value -
Description l Before setting this parameter, check and ensure that the attributes in Ethernet Interface of the port are set correctly and are the same as the planning information. l The value of this parameter cannot be the same as the value of sink port. l The value of this parameter cannot be used for the E-LAN port. l This parameter is set according to the planning information.
Source VLANs
1 to 4094
l This parameter can be set to null, a number, or several numbers. When setting this parameter to several numbers, use the comma (,) to separate the discrete numbers, or use the endash (-) to represent a consecutive number. For example, the numbers 1, and 3-6 indicate 1, 3, 4, 5, and 6. l If this parameter is set to null, all the services at the source port are used as the service source. l If this parameter is not set to null, only the service that contains the VLAN ID at the source port can be used as the service source.
Issue 02 (2011-01-20)
B-175
Parameter Bearer Type
Value Range QinQ Link PW
Default Value PW
Description For NNI-NNI QinQ services, the parameter value is always QinQ Link. Selects or specifies the ID of a QinQ link.
QinQ Link ID
Table B-7 Service direction of NNI-NNI Parameter Service ID Value Range 1 to 4294967294 Default Value Description This parameter specifies the ID of the E-Line service. This parameter specifies the name of the E-Line service. l This parameter specifies the direction of the E-Line service. l Set this parameter to NNI-NNI. Not Transparently Transmitted For NNI-NNI QinQ services, the parameter value is always Not Transparently Transmitted . This parameter cannot be set here. The OptiX RTN 980 does not support this parameter. Uses the QinQ link to carry the E-Line service. l Selects the QinQ link ID of the first QinQ link. l The QinQ link ID is preset in QinQ Link. Bearer Type 2 QinQ Link QinQ Link Uses the QinQ link to carry the E-Line service.
Service Name
Direction
UNI-UNI
BPDU
Bearer Type 1 QinQ Link ID 1
QinQ Link -
QinQ Link -
B-176
Issue 02 (2011-01-20)
Parameter QinQ Link ID 2
Value Range -
Default Value -
Description l Selects the QinQ link ID of the second QinQ link. l The QinQ link ID is preset in QinQ Link.
QinQ Link ID
Selects or specifies the ID of a QinQ link.
Parameters of PWs
NOTE
l Parameters of PWs need to be configured only when Direction is UNI-NNI and Bearer Type is PW. l If the parameter Protection Type of PWs is set to PW APS or Slave Protection Pair, all the parameters of working and protection PWs need to be configured. This section considers the parameters of the working PW as an example.
Parameter PW ID PW Signaling Type PW Type
Value Range Static Ethernet Ethernet Tagged Mode
Default Value Static Ethernet
Description Specifies the ID of the PW that carries services. Labels for static PWs need to be manually assigned. l Specifies the type of the PW. l PW Type indicates whether P-TAG is added to Ethernet frames that are encapsulated for transmission on PWs. If it is not required to add VLAN IDs, set this parameter to Ethernet. If it is required to add VLAN IDs, set this parameter to Ethernet Tagged Mode and then set Request VLAN in the Advanced Attributes tab.
Direction
Bidirectional
Bidirectional
Displays the direction of the PW.
Issue 02 (2011-01-20)
B-177
Parameter PW Encapsulation Type
Value Range MPLS
Default Value MPLS
Description Displays the encapsulation type of the packets on the PW. Specifies the PW Ingress label. Specifies the PW Egress label. Displays the method to select tunnels. Displays the type of the tunnel that carries the PW. A tunnel needs to be selected. If no tunnel is available, creation of a PW will fail. Specifies the LSR ID of the PW at the remote end. If an existing tunnel is selected, the LSR ID will be automatically assigned. For a bidirectional tunnel, the system will configure the egress tunnel automatically.
PW Ingress Label/ Source Port PW Egress Label/Sink Port Tunnel selection mode Tunnel Type Tunnel
16 to 1048575 16 to 1048575 MPLS -
MPLS -
Opposite LSR ID
Egress Tunnel
QoS Parameters
NOTE
QoS parameters need to be configured only when Direction is UNI-NNI and Bearer Type is PW.
B-178
Issue 02 (2011-01-20)
Parameter Bandwidth Limit
Value Range -
Default Value -
Description Specifies whether the bandwidth limit function is enabled. l This function limits the bandwidth of one or more PWs in an MPLS tunnel. l An ETH PWE3 service corresponds to a PW. Therefore, this function can also limit the bandwidth of ETH PWE3 services in an MPLS tunnel.
Policy CIR(Kbit/s)
The OptiX RTN 980 does not support this parameter. Specifies the committed information rate (CIR) of a PW. It is recommended that you set this parameter to the same value as PIR.
CBS(byte) PIR(Kbit/s)
Specifies the committed burst size (CBS) of a PW. Specifies the peak information rate (PIR) of a PW. It is recommended that you set this parameter to the same value as CIR.
PBS(byte) EXP LSP Mode
Pipe
Pipe
Specifies the peak burst size (PBS) of a PW. The OptiX RTN 980 does not support this parameter. Pipe: When stripping MPLS tunnel labels from packets, an egress node does not update the scheduling priority for the packets.
Issue 02 (2011-01-20)
B-179
Parameters of Advanced Attributes

Parameter Control Word Value Range No Use Default Value No Use Description For ETH PWE3 services, the parameter value is always No Use. l Specifies the mode of PW connectivity check. l None indicates that VCCV is not used. l Alert Label indicates VCCV packets in Alert Label encapsulation mode. VCCV Verification Mode Ping None Ping l Specifies the VCCV verification mode. The VCCV verification is used for PW connectivity check. l If the VCCV-Ping test is required, set this parameter to Ping. Request VLAN l Set this parameter when PW Type is Ethernet Tagged Mode. l If the received packets do not carry any VLAN IDs, the PW will add VLAN IDs to the packets as required by the setting of this parameter. TPID The OptiX RTN 980 does not support request VLAN TPID of the PW level.
Control Channel Type
None Alert Label
Alert Label
Protection Group Parameters (PW APS)

NOTE
The parameters of the PW APS protection group need to be configured if the Protection Type of PWs is set to PW APS.
B-180
Issue 02 (2011-01-20)
Parameter Protection Type Protection Group ID Enabling Status
Description Specifies the protection type. Specifies the protection group ID. l Specifies the enabling status of the PW protection group. l During the creation of a protection group, set Enabling Status to Disabled. After the APS protection group is configured at both ends, set Enabling Status to Enabled.
Protection Mode Working PW ID Protection PW ID Switching Mode
Displays the protection mode. Displays the ID of the working PW. Displays the ID of the protection PW. Displays the switching mode to be used when a PW fails.
NOTE The OptiX RTN 980 support dual-ended switching.
Revertive Mode
Non-revertive Revertive
Revertive
l This parameter specifies whether to switch services back to the original working PW after it recovers. l The value Revertive indicates that services are switched to the original working PW and the value Nonrevertive indicates that services are not switched to the original working PW. l The value Revertive is recommended.
Issue 02 (2011-01-20)
B-181
Parameter Switchover Restoration Time(min)
Value Range 1 to 12
Default Value 1
Description l Specifies the WTR time of the protection group. l When the preset WTR time expires after the original working PW recovers, services are switched to the original working PW. l This parameter is available only when Restoration Mode is Revertive. l The default value is recommended.
Switchover Delay Time (100ms)
0 to 100
l Specifies the hold-off time of the protection group. l If this parameter is set to a value other than 0, the protection group does not trigger switching once it detects faults, but waits until the hold-off time expires, and then detects whether any faults persist. If any faults persist, the switching is triggered; otherwise, no switching is triggered. l The default value is recommended.
Detection mode
Displays the detection mode of the PW APS protection group.
OAM Parameters
NOTE
l The OAM parameters of the PW APS protection group need to be configured if the Protection Type of PWs is set to PW APS. l To configure PW OAM parameters, choose Configuration > MPLS Management > PW Management > PW OAM Parameter from the Function Tree.
B-182
Issue 02 (2011-01-20)
Parameter OAM Status Detection Mode
Value Range Auto-Sensing Manual
Default Value Auto-Sensing
Description Displays the enabling status of PW OAM. l Specifies the detection mode of OAM packets. l Manual: The connectivity check (CC) packets are sent at the interval specified by the user. l Auto-Sensing: The connectivity check (CC) packets are sent at the interval of receiving PW OAM packets. l If Detection Mode is set to Manual, you need to set the PW OAM detection packets to be received and transmitted. l The value AutoSensing is recommended.
Issue 02 (2011-01-20)
B-183
Parameter Detection Packet Type
Value Range CV FFD
Default Value CV
Description l CV: The detection packets are sent at a fixed interval. l FFD: The detection packets are sent at the interval specified by the user. l If Detection Mode is set to Auto-Sensing, this parameter specifies the PW OAM detection packets to be transmitted. l If Detection Mode is set to Manual, this parameter specifies the PW OAM detection packets to be received and transmitted. l The value FFD is assumed for PW APS and the value CV is assumed for continuous connectivity check on PWs.
Detection Packet Period (ms)
3.3 10 20 50 100 200 500
50
l Specifies the period of detection packets. l This parameter is configurable when Detection Packet Type is FFD and assumes the fixed value of 1000 when Detection Packet Type is CV. l Set this parameter to 3.3 for PW APS.
LSR ID to be Received PW ID to be Received
Specifies the LSR ID to be received. Specifies the PW ID to be received.
B-184
Issue 02 (2011-01-20)
Protection Group Parameters (Slave Protection Pair)

NOTE
The parameters of the PW APS protection group need to be configured if the Protection Type of PWs is set to Slave Protection Pair.
Parameter Protection Mode Protection Group ID
Value Range -
Default Value -
Description Displays the protection mode. Specifies the ID of the slave protection pair. The switching of the master PW APS protection group triggers the switching of the slave PW APS protection group simultaneously. Displays the ID of the working PW in the slave protection pair. Displays the ID of the protection PW in the slave protection pair.
Working PW ID
Protection PW ID
Related Tasks
A.6.3.2 Configuring UNI-UNI E-Line Services A.6.3.3 Configuring NNI-NNI E-Line Services A.6.3.4 Configuring UNI-NNI E-Line Services (Carried by QinQ Links) A.6.3.5 Configuring UNI-NNI E-Line Services (Carried by PWs)
B.6.1.2 Parameter Description: E-Line Service

This topic describes the parameters that are related to E-Line services.
Navigation Path
Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Ethernet Service Management > E-Line Service from the Function Tree.

Parameter Service ID Value Range 1 to 4294967294 Default Value Description This parameter indicates the ID of the E-Line service.
B-185
Issue 02 (2011-01-20)
Parameter Service Name
Value Range -
Default Value -
Description This parameter indicates or specifies the name of the E-Line service. This parameter indicates the source node. This parameter indicates the sink node. The OptiX RTN 980 does not support this parameter. This parameter cannot be queried here. This parameter indicates the transparent transmission tag of the bridge protocol data unit (BPDU) packets. This parameter is used to indicate whether the Ethernet line transparently transmits the BPDU packets. This parameter indicates whether E-Line service is deployed.
Source Node Sink Node Service Tag Role
MTU(byte) BPDU
Deployment Status
Parameters Associated with UNI Ports

Parameter Port Value Range Default Value Description This parameter indicates the UNI port.
B-186
Issue 02 (2011-01-20)
Parameter VLANs
Default Value -
Description This parameter indicates or specifies the VLAN ID of the UNI port. l This parameter can be set to null, a number, or several numbers. When setting this parameter to several numbers, use the comma (,) to separate the discrete numbers, or use the endash (-) to represent a consecutive number. For example, the numbers 1, and 3-6 indicate 1, 3, 4, 5, and 6. l This parameter is valid only when Direction is set to UNI-UNI or UNI-NNI in the process of creating an E-Line service. l If this parameter is set to null, all the services of the UNI work as the service source or service sink. l If this parameter is not set to null, only the services of the UNI port whose VLAN IDs are included in the set value of this parameter work as the service source or service sink.
NNI Parameters (PW)

Parameter PW ID Working Status Value Range Default Value Description Displays the PW ID. Displays the working status of a PW.
Issue 02 (2011-01-20)
B-187
Parameter Enable Status PW Signaling Type
Value Range -
Default Value -
Description Displays whether a PW is enabled. Displays the PW signaling type.

NOTE The OptiX RTN 980 uses static PWs only.
PW Type Direction PW Encapsulation Type
Displays the configured PW type. Displays the direction of the PW. Displays the PW encapsulation type.
NOTE The OptiX RTN 980 uses MPLS only.
PW Ingress Label/ Source Port PW Egress Label/Sink Port Tunnel Type Tunnel Opposite LSR ID Control Word
MPLS -
MPLS -
Displays the configured PW ingress label. Displays the configured PW egress label. Displays the type of the tunnel that carries a PW. Displays the tunnel ID. Displays the opposite LSR ID. For ETH PWE3 services, the parameter value is always No Use. Displays the control channel type. Displays the VCCV mode. Displays the working status of the PW at the local end. Displays the working status of the PW at the remote end.
Control Channel Type VCCV Verification Mode Local Working Status
Remote Working Status
B-188
Issue 02 (2011-01-20)
Parameter Compositive Working Status Request VLAN Deployment Status Tunnel Automatic Selection Policy TPID
Value Range -
Default Value -
Description Displays the comprehensive working status of the PW. Displays the request VLAN. Displays the deployment status. Displays the automatic tunnel selection policy. The OptiX RTN 980 does not support request VLAN TPID of the PW level.
Parameters Associated with NNI Ports

Parameter QinQ Link ID Value Range 1 to 4294967295 Default Value Description l This parameter indicates the QinQ link ID of the QinQ link connected to the NNI port. l This parameter is valid only when Direction is set to UNI-UNI or UNI-NNI in the process of creating an E-Line service. Port l This parameter indicates the NNI port. l This parameter is valid only when Direction is set to UNI-UNI or UNI-NNI in the process of creating an E-Line service.
Issue 02 (2011-01-20)
B-189
Parameter S-VLAN ID
Value Range -
Default Value -
Description l This parameter indicates or specifies the VLAN ID of the NNI port. l This parameter is valid only when Direction is set to UNI-NNI or NNI-NNI in the process of creating an E-Line service. l This parameter is preset in QinQ Link.
QoS Parameters
Parameter PW ID Direction Value Range Default Value Description Displays the PW ID. l Displays the direction of the PW. l Egress indicates the egress direction of the PW. l Ingress indicates the ingress direction of the PW. Bandwidth Limit Displays or specifies whether the bandwidth limit function is enabled for a PW to prevent network congestion. l Regarding transmission channels, this function can be used to limit the bandwidth of one or more PWs in an MPLS tunnel. l An ETH PWE3 service corresponds to a PW. Therefore, this function can also limit the bandwidth of ETH PWE3 services in an MPLS tunnel.
B-190
Issue 02 (2011-01-20)
Parameter Policy
Value Range -
Default Value -
Description The OptiX RTN 980 does not support this parameter. Displays or specifies the committed information rate (CIR) of a PW. It is recommended that you set this parameter to the same value as PIR.
CIR (Kbit/s)
CBS (kbyte)
Displays or specifies the committed burst size (CBS) of a PW. Displays or specifies the peak information rate (PIR) of a PW. It is recommended that you set this parameter to the same value as CIR.
PIR (kbit/s)
PBS (kbyte)
Displays or specifies the peak burst size (PBS) of a PW. The OptiX RTN 980 does not support this parameter. Pipe: When stripping MPLS tunnel labels from packets, an egress node does not update the scheduling priority for the packets.
EXP
LSP Mode
Pipe
Pipe
Parameters for the Port Attributes

Parameter Port Value Range Default Value Description Displays the port information.
Issue 02 (2011-01-20)
B-191
Parameter Enable Port
Value Range -
Default Value -
Description l This parameter indicates whether to enable the port. l This parameter is preset in General Attributes of Ethernet Interface.
Encapsulation Type
Null 802.1Q QinQ
l This parameter indicates the encapsulation type of the port. l This parameter is valid only when Direction is set to UNI-UNI or UNI-NNI in the process of creating an E-Line service. l If this parameter is set to Null, the port transparently transmits the received packets. l If this parameter is set to 802.1Q, the port identifies the packets that comply with the IEEE 802.1Q standard. l If this parameter is set to QinQ, the port identifies the packets that comply with the IEEE 802.1 QinQ standard. l This parameter is preset in General Attributes of Ethernet Interface.
TAG
Tag Aware Access Hybrid
l This parameter indicates the tag of the port. l This parameter is preset in Layer 2 Attributes of Ethernet Interface .
B-192
Issue 02 (2011-01-20)

NOTE
The following parameters are available only after the PW APS protection group is configured.
Parameter Protection Group ID
Value Range -
Default Value -
Description Displays the ID of the protection group to be created. Displays the ID of the working PW. Displays the ID of the protection PW. Displays the protection mode. l Displays or specifies the enabling status of the PW protection group. l During the creation of a protection group, set Enabling Status to Disabled. After the APS protection group is configured at both ends, set Enabling Status to Enabled.
Working PW ID Protection PW ID Protection Mode Enabling Status
Enabled Disabled
Switchover Mode
Displays the switching mode to be used when a PW fails.

NOTE The OptiX RTN 980 supporting dual-ended switching.
Issue 02 (2011-01-20)
B-193
Parameter Restoration Mode
Value Range Non-revertive Revertive
Default Value -
Description l Specifies whether to switch services to the original working PW after the fault is rectified. l The value Revertive indicates that services are switched to the original working PW and the value Nonrevertive indicates that services are not switched to the original working PW. l The value Revertive is recommended.
Switchover Restoration Time(min)
1 to 12
l Displays or specifies the WTR time of the protection group. l When the preset WTR time expires after the original working PW recovers, services are switched to the original working PW. l This parameter is available only when Restoration Mode is Revertive.
0 to 100
l Displays or specifies the hold-off time of the protection group. l If this parameter is set to a value other than 0, the protection group does not trigger switching once it detects faults, but waits until the hold-off time expires, and then detects whether any faults persist. If any faults persist, the switching is triggered; otherwise, no switching is triggered.
B-194
Issue 02 (2011-01-20)
Parameter Deployment Status
Value Range -
Default Value -
Description Display the deployment status of the protection group. Displays the switchover status of the protection group. Displays the enabling status of the protocol. Displays the status of the current working path. Display the status of the current protection path.
Switchover Status
Protocol Status Working Path Status Protection Path Status

NOTE
The following parameters are available only after the slave protection pair is configured.
Value Range -
Default Value -
Description Specifies the ID of the slave protection pair. The switching of the master PW APS protection group triggers the switching of the slave PW APS protection group simultaneously. Displays the ID of the working PW in the slave protection pair. Displays the ID of the protection PW in the slave protection pair. Displays the DNI PW ID. Displays the PW type. Displays the deployment status of the slave protection pair.
Working PW ID
Protection PW ID
DNI PW ID PW Type Deployment Status
Issue 02 (2011-01-20)
B-195
B.6.1.3 Parameter Description: VLAN Forwarding Table Item_Creation

This topic describes the parameters that are used for creating VLAN forwarding table items.
Navigation Path
1. 2. 3. Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Ethernet Service Management > E-Line Service from the Function Tree. Click the VLAN Forwarding Table Item tab. Click New.
Parameters for VLAN Forwarding Table Item

Parameter Source Interface Type Value Range V-UNI Default Value V-UNI Description This parameter specifies the network attribute of the source interface. This parameter specifies the source interface. This parameter specifies the VLAN ID of the source service. This parameter specifies the network attribute of the sink interface. This parameter specifies the sink interface. This parameter specifies the VLAN ID of the sink service.
Source Interface Source VLAN ID
1 to 4094
Sink Interface Type
V-UNI
V-UNI
Sink Interface Sink VLAN ID
1 to 4094
NOTE
l The VLAN ID of the UNI-UNI E-Line service can be converted after a VLAN forwarding table item is created. In this case, a service from Source Interface to Sink Interface carries the VLAN ID specified in Sink VLAN ID when the service is transmitted from Sink Interface. l The VLAN ID in a VLAN forwarding table item is converted unidirectionally and can be converted from Source VLAN ID to Sink VLAN ID only. The VLAN ID can be converted bidirectionally only when the other VLAN forwarding table item is configured reversely. l In normal cases, Ethernet services are bidirectional. Hence, you need to set bidirectional conversion of VLAN IDs.
Related Tasks
A.6.3.6 Creating a VLAN Forwarding Table Item
B-196
Issue 02 (2011-01-20)

This topic describes the parameters that are used for creating an Ethernet local area network (ELAN) service.
Navigation Path
1. 2. Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Ethernet Service Management > E-LAN Service from the Function Tree. Click New.

Parameter Service ID Value Range 1 to 4294967294 Default Value Description l This parameter specifies the ID of the E-LAN service. l The OptiX RTN 980 supports simultaneous creation of an E-LAN service only. Service Name This parameter specifies the name of the E-LAN service. l This parameter indicates the transparent transmission tag of the BPDU packets. l In the case of an ELAN service, this parameter supports only Not Transparently Transmitted and cannot be set manually. l Not Transparently Transmitted indicates that the BPDU packets are used as the protocol packets to compute the spanning tree topology of the network.
BPDU
Issue 02 (2011-01-20)
B-197
Parameter Tag Type
Value Range C-Awared S-Awared Tag-Transparent
Default Value C-Awared
Description l C-Awared indicates that the packets are learnt according to CTag (the VLAN tag on the client-side). To create the 802.1q bridge, set this parameter to CAwared. l S-Awared indicates that the packets are learnt according to STag (the VLAN tag at the carrier service layer). To create the 802.1ad bridge, set this parameter to SAwared. l Tag-Transparent indicates that only the Ethernet packets that do not contain VLAN tags are accessed. To create the 802.1d bridge, set this parameter to TagTransparent. l This parameter is set according to the planning information.
B-198
Issue 02 (2011-01-20)
Parameter Self-Learning MAC Address
Description l This parameter specifies whether to enable the MAC address self-learning function. l If the MAC selflearning function of an Ethernet LAN is enabled, the Ethernet LAN learns an MAC address according to the original MAC address in the packet and automatically refreshes the MAC address forwarding table. l If the MAC selflearning function of an Ethernet LAN is disabled, a static MAC address forwarding table is recommended to be configured.
MAC Address Learning Mode
l This parameter indicates the mode used to learn an MAC address. l When the bridge uses the SVL mode, all the VLANs share one MAC address table. If the bridge uses the IVL mode, each VLAN has an MAC address table.
Deployment Status
This parameter indicates whether E-LAN service is deployed. This parameter cannot be set here. The OptiX RTN 980 does not support this parameter.
Issue 02 (2011-01-20)
B-199
Parameters for UNIs

Parameter Port SVLAN Value Range 1 to 4094 Default Value Description This parameter indicates the UNI port. l This parameter specifies the S-VLAN ID of the UNI port. l This parameter is valid only when Tag Type is set to S-Awared. l This parameter is set according to the planning information. VLANs/CVLAN 1 to 4094 l This parameter specifies the VLAN ID of the UNI port. l This parameter can be set to null, a number, or several numbers. When setting this parameter to several numbers, use the comma (,) to separate the discrete numbers, or use the endash (-) to represent a consecutive number. For example, the numbers 1, and 3-6 indicate 1, 3, 4, 5, and 6. l If this parameter is set to null, all the services of the UNI work as the service source or service sink. l If this parameter is not set to null, only the services of the UNI port whose VLAN IDs are included in the set value of this parameter work as the service source or service sink.
B-200
Issue 02 (2011-01-20)
Parameters of NNIs
Parameter Port Value Range Default Value Description l This parameter indicates the NNI port. l This parameter is valid only when Tag Type is set to S-Awared. SVLANs l This parameter specifies the S-VLAN ID of the NNI port. l This parameter is valid only when Tag Type is set to S-Awared.
Parameters for the Split Horizon Group

Parameter Split Horizon Group ID Value Range Default Value 1 Description l This parameter indicates the ID of the split horizon group. l The default split horizon group ID is 1 and cannot be set manually.
Issue 02 (2011-01-20)
B-201
Parameter Split Horizon Group Member
Value Range -
Default Value -
Description l A split horizon group member indicates the logical port member in the split horizon group. l The port members that are added to the same split horizon group cannot communicate with each other. l The OptiX RTN 980 supports only the division of the split horizon group members according to the Ethernet physical port. l If a UNI or NNI logical port of the 802.1ad bridge is added to a split horizon group member, the physical port that is mounted with the logical port is automatically added to the split horizon group member.
Related Tasks
A.6.3.8 Configuring IEEE 802.1d Bridge-Based E-LAN Services A.6.3.9 Configuring IEEE 802.1q Bridge-Based E-LAN Services A.6.3.10 Configuring IEEE 802.1ad Bridge-Based E-LAN Services

This topic describes the parameters that are related to E-LAN services.
Navigation Path
Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Ethernet Service Management > E-LAN Service from the Function Tree.
B-202
Issue 02 (2011-01-20)

Parameter Service ID Value Range 1 to 4294967294 Default Value Description l This parameter indicates the ID of the E-LAN service. l The supports simultaneous creation of an E-LAN service only. Service Name This parameter specifies the name of the E-LAN service. l This parameter indicates the transparent transmission tag of the BPDU packets. l In the case of an ELAN service, this parameter supports only Not Transparently Transmitted and cannot be set manually. l Not Transparently Transmitted indicates that the BPDU packets are used as the protocol packets to compute the spanning tree topology of the network.
BPDU
Issue 02 (2011-01-20)
B-203
Parameter Tag Type
Value Range C-Awared S-Awared Tag-Transparent
Default Value C-Awared
Description l C-Awared indicates that the packets are learnt according to CTag (the VLAN tag on the client-side). To create the 802.1q bridge, set this parameter to CAwared. l S-Awared indicates that the packets are learnt according to STag (the VLAN tag at the carrier service layer). To create the 802.1ad bridge, set this parameter to SAwared. l Tag-Transparent indicates that only the Ethernet packets that do not contain VLAN tags are accessed. To create the 802.1d bridge, set this parameter to SAwared.
B-204
Issue 02 (2011-01-20)
Parameter Self-Learning MAC Address
Value Range Enabled
Description l This parameter indicates whether to enable the MAC address self-learning function. l If the MAC selflearning function of an Ethernet LAN is enabled, the Ethernet LAN learns an MAC address according to the original MAC address in the packet and automatically refreshes the MAC address forwarding table. l If the MAC selflearning function of an Ethernet LAN is disabled, a static MAC address forwarding table is recommended to be configured.
MAC Address Learning Mode
l This parameter indicates the mode used to learn an MAC address. l When the bridge uses the SVL mode, all the VLANs share one MAC address table. If the bridge uses the IVL mode, each VLAN has an MAC address table.
This parameter cannot be queried here. The OptiX RTN 980 does not support this parameter. This parameter indicates whether E-LAN service is deployed.
Deployment Status
Issue 02 (2011-01-20)
B-205
Parameters for UNIs

Parameter Port SVLAN Value Range 1 to 4094 Default Value Description This parameter indicates the UNI port. l This parameter specifies the S-VLAN ID of the UNI port. l This parameter is valid only when Tag Type is set to S-Awared. l This parameter is set according to the planning information. VLANs/CVLAN 1 to 4094 l This parameter specifies the VLAN ID of the UNI port. l This parameter can be set to null, a number, or several numbers. When setting this parameter to several numbers, use the comma (,) to separate the discrete numbers, or use the endash (-) to represent a consecutive number. For example, the numbers 1, and 3-6 indicate 1, 3, 4, 5, and 6. l If this parameter is set to null, the E-LAN service exclusively uses the corresponding UNI physical port. That is, the entire port is mounted to the bridge. l If this parameter is set to a non-null value, only the corresponding UNI port whose service packets contain this VLAN ID works as the logical port and is mounted to the bridge.
B-206
Issue 02 (2011-01-20)
Parameters for NNIs

Parameter Port Value Range Default Value Description l This parameter indicates the NNI port. l This parameter is valid only when Tag Type is set to S-Awared. SVLANs l This parameter specifies the S-VLAN ID of the UNI port. l This parameter is valid only when Tag Type is set to S-Awared. l This parameter can be set to null, a number, or several numbers. When setting this parameter to several numbers, use the comma (,) to separate the discrete numbers, or use the endash (-) to represent a consecutive number. For example, the numbers 1, and 3-6 indicate 1, 3, 4, 5, and 6.
Issue 02 (2011-01-20)
B-207
Parameters for Static MAC Addresses

Parameter VLAN ID Value Range Default Value Description l This parameter is invalid if MAC Address Learning Mode is SVL. That is, the preset static MAC address entries are valid for all VLANs. l If MAC Address Learning Mode is set to IVL, the preset static MAC address entries are valid for only the VLANs whose VLAN ID is equal to the preset VLAN ID. l This parameter is set according to the planning information. MAC Address l This parameter indicates or specifies the static MAC address. l A static MAC address is an address that is set manually. It is not aged automatically and needs to be deleted manually. l Generally, a static MAC address is used for the port that receives but does not forward Ethernet service packets or the port whose MAC address need not be aged automatically. Egress Interface l This parameter specifies the Ethernet port that corresponds to the MAC address. l This parameter is set according to the planning information.
B-208
Issue 02 (2011-01-20)
Parameters for Self-Learning MAC Address

Parameter VLAN ID Value Range Default Value Description l This parameter is invalid if MAC Address Learning Mode is SVL. That is, the preset self-learning MAC address entries are valid for all VLANs. l If MAC Address Learning Mode is set to IVL, the preset selflearning MAC address entries are valid for only the VLANs whose VLAN ID is equal to the preset VLAN ID. l This parameter is set according to the planning information. MAC Address l This parameter indicates or specifies the self-learning MAC address. A selflearning MAC address is also called a dynamic MAC address. l A self-learning MAC address is an entry obtained by a bridge in SVL or IVL learning mode. A self-learning MAC address can be aged. Egress Interface l This parameter specifies the Ethernet port that corresponds to the MAC address. l This parameter is set according to the planning information.
Issue 02 (2011-01-20)
B-209
Parameters Associated with MAC Address Learning

Parameter Aging Ability Value Range Enabled Disabled Aging Time(min) 1 to 65535 5 Default Value Enabled Description The OptiX RTN 980 supports enabling/ disabling of the aging function and aging time for the MAC address table. If one routing entry is not updated in a certain period, that is, if no new packet from this MAC address is received to enable the re-learning of this MAC address, this routing entry is automatically deleted. This mechanism is called aging, and this period is called aging time. The aging time of a MAC address table is 5 minutes by default.
Parameters for Disabled MAC Addresses

Parameter VLAN ID Value Range Default Value Description This parameter indicates or specifies the VLAN ID of the service. A disabled MAC address is valid for the VLAN whose VLAN ID is equal to the preset VLAN ID.
B-210
Issue 02 (2011-01-20)
Parameter MAC Address
Value Range -
Default Value -
Description l This parameter specifies or indicates the disabled MAC address. A disabled MAC address is also called a blacklisted MAC address. l This parameter is used for discarding an entry, also called a black hole entry, whose data frame that contains a specific destination MAC address. A disabled MAC address needs to be set manually and cannot be aged.
Parameters for Unknown Frame Processing

Parameter Frame Type Value Range Unicast Multicast Handing Mode Discard Broadcast Broadcast Default Value Description This parameter indicates the type of the received unknown frame. Selects the method of processing the unknown frame. If this parameter is set to Discard, the unknown frame is directly discarded. If this parameter is set to Broadcast, the unknown frame is broadcast at the forwarding port.
Issue 02 (2011-01-20)
B-211
Parameters for the Split Horizon Group

Parameter Split Horizon Group ID Value Range Default Value 1 Description l This parameter indicates the ID of the split horizon group. l The default split horizon group ID is 1 and cannot be set manually. Split Horizon Group Member l A split horizon group member indicates the logical port member in the split horizon group. l The port members that are added to different split horizon groups cannot communicate with each other. l The supports only the division of the split horizon group members according to the Ethernet physical port. l If a UNI or NNI logical port of the 802.1ad bridge is added to a split horizon group member, the physical port that is mounted with the logical port is automatically added to the split horizon group member.
Maintenance Association Parameters

Parameter Maintenance Domain Name Value Range Default Value Description This parameter indicates the maintenance domain of the created maintenance association.
B-212
Issue 02 (2011-01-20)
Parameter Maintenance Association Name
Value Range -
Default Value -
Description l This parameter specifies the name of the maintenance association, which is a domain related to a service. Through maintenance association division, the connectivity check (CC) can be performed on the network that transmits a service instance. l This parameter can contain a maximum of eight bytes.
1s 10s 1m 10m
1s
l This parameter specifies the interval for transmitting packets in the CC test. l The CC is performed to check the availability of the service.
Parameters for the MEP

Parameter Maintenance Domain Name Maintenance Association Name Node VLAN MEP ID Value Range 1 to 2048 Default Value 1 Description This parameter indicates the maintenance domain of the created MEP. This parameter indicates the maintenance association of the created MEP. This parameter indicates the MEP node. This parameter indicates the VLAN ID of the current service. l This parameter specifies the MEP ID. l Each MEP needs to be configured with an MEP ID, which is unique in the maintenance association. The MEP ID is required in the OAM operation. Direction Ingress Egress Ingress l This parameter specifies the direction of the MEP. l "Ingress" indicates the direction in which the packets are transmitted to the port, and "Egress" indicates the direction in which the packets are transmitted from the port. CC Status Active Inactive Active l This parameter specifies whether to enable the CC function of the MEP. l In the case of the tests based on the MP IDs, CC Status must be set to Active.
Issue 02 (2011-01-20)
B-213
Related Tasks
A.6.4.1 Creating a Static MAC Address Entry A.6.4.2 Creating a Blacklist Entry of MAC Addresses A.6.4.3 Configuring the Aging Parameters of a MAC Address Table A.6.4.4 Querying or Deleting a Dynamic MAC Address A.6.5 Setting the Mode for Processing an Unknown Frame of the E-LAN Service
B.6.1.6 Parameter Description: QinQ Link_Creation

This topic describes the parameters that are used for creating a QinQ link.
Navigation Path
1. 2. Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Ethernet Service Management > QinQ Link from the Function Tree. Click New.
Parameters for the General Attributes

Parameter QinQ Link ID Value Range 1 to 4294967295 Default Value Description This parameter specifies the ID of the QinQ link.
NOTE The OptiX RTN 980 supports 1024 QinQ links, whose IDs must be different from each other.
Board
This parameter specifies the board where the QinQ link is located. This parameter specifies the port where the QinQ link is located. l This parameter specifies the VLAN ID (at the network operator side) for the QinQ link. l This parameter is set according to the planning information.
Port
S-Vlan ID
1 to 4094
Related Tasks
A.6.3.1 Configuring the QinQ Link
B.6.2 Parameters for Ethernet Protocols

This topic describes the parameters that are related to the Ethernet protocol. B.6.2.1 Parameter Description: ERPS Management_Creation This topic describes the parameters that are used for creating ERPS management tasks. B.6.2.2 Parameter Description: ERPS Management This topic describes the parameters that are used for Ethernet ring protection switching (ERPS) management. B.6.2.3 Parameter Description: MSTP Configuration_Port Group Creation This topic describes the parameters that are used for creating MSTP port groups. B.6.2.4 Parameter Description: MSTP Configuration_Port Group Configuration This topic describes the parameters that are used for creating MSTP port groups. B.6.2.5 Parameter Description: MSTP Configuration_ Bridge Parameters This topic describes the parameters that are related to MSTP bridges. B.6.2.6 Parameter Description: MSTP Configuration_CIST Parameters This topic describes the parameters that are related to the MSTP CIST. B.6.2.7 Parameter Description: MSTP Configuration_Running Information About the CIST This topic describes the parameters that are related to the running information about the MSTP CIST. B.6.2.8 Parameter Description: Ethernet Link Aggregation Management_LAG Creation This topic describes the parameters that are used for creating a link aggregation group (LAG). B.6.2.9 Parameter Description: Ethernet Link Aggregation_Link Aggregation This section describes the parameters for port priorities and system priorities. B.6.2.10 Parameter Description: LPT Management_Point-to-Point LPT This topic describes the parameters that are related to point-to-point LPT. B.6.2.11 Parameter Description: LPT Management_Creating Point-to-Point LPT This topic describes the parameters that are related to creating point-to-point LPT. B.6.2.12 Parameter Description: LPT Management_Point-to-Multipoint LPT This topic describes the parameters that are related to point-to-multipoint LPT. B.6.2.13 Parameter Description: LPT Management_Creating Point-to-Multipoint LPT This topic describes the parameters that are related to creating point-to-multipoint LPT.
B.6.2.1 Parameter Description: ERPS Management_Creation

This topic describes the parameters that are used for creating ERPS management tasks.
Navigation Path
1. 2. Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Ethernet Protection > ERPS Management. Click New.
Issue 02 (2011-01-20)
B-215
Parameters
Parameter ERPS ID Value Range 1 to 8 Default Value Description l This parameter specifies the ID of the Ethernet ring protection switching (ERPS) instance. l The IDs of ERPS instances on an NE must be different from each other. East Port This parameter specifies the east port of the ERPS instance. This parameter specifies the west port of the ERPS instance. l This parameter specifies whether the node on the ring is the ring protection link (RPL) owner. l Only one node on the ring can be set as the RPL owner for each Ethernet ring. RPL Port l This parameter specifies the RPL port. l There is only one RPL port and this RPL port must be the east or west port on the RPL owner node.
West Port
RPLOwner Ring Node Flag
Yes No
No
B-216
Issue 02 (2011-01-20)
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 R-APS packets on the dedicated ring APS (R-APS) channel to ensure consistency between the nodes when the ERPS switching is performed. Control VLAN is used for isolating the dedicated R-APS channel. Therefore, the VLAN ID in Control VLAN cannot be duplicate with the VLAN IDs that are contained in the service packets. l The Control VLAN must be set to the same value for all the NEs on an ERPS ring.
Destination Node
01-19-A7-00-00-01
01-19-A7-00-00-01
This parameter indicates the MAC address of the destination node. The default destination MAC address in the R-APS packets is always 01-19A7-00-00-01.
Related Tasks
A.6.1.1 Creating Ethernet Ring Protection Instances

This topic describes the parameters that are used for Ethernet ring protection switching (ERPS) management.
Navigation Path
Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Ethernet Protection > ERPS Management from the Function Tree.
Parameters
Parameter ERPS ID Value Range 1 to 8 Default Value Description This parameter indicates the ID of the ERPS instance. This parameter indicates the east port of the ERPS instance. This parameter indicates the west port of the ERPS instance. This parameter indicates whether a node on the ring is the ring protection link (RPL) owner. This parameter indicates the RPL port. l This parameter indicates or specifies the VLAN ID of Control VLAN. l Each node on the Ethernet ring transmits the R-APS packets on the dedicated ring APS (R-APS) channel to ensure consistency between the nodes when the ERPS switching is performed. Control VLAN is used for isolating the dedicated R-APS channel. Therefore, the VLAN ID in Control VLAN cannot be duplicate with the VLAN IDs that are contained in the service packets or inband DCN packets. l The Control VLAN must be set to the same value for all the NEs on an ERPS ring.
East Port
West Port
RPL Owner Ring Node Flag
Yes No
RPL Port Control VLAN
1 to 4094
B-218
Issue 02 (2011-01-20)
Parameter Destination Node
Value Range 01-19-A7-00-00-01
Default Value -
Description This parameter indicates the MAC address of the destination node. The default destination MAC address in the R-APS packets is always 01-19A7-00-00-01. l This parameter indicates or specifies the hold-off time of the ERPS hold-off timer. l The hold-off timer is used for negotiating the protection switching sequence when the ERPS coexists with other protection schemes so that the fault can be rectified in the case of other protection switching (such as LAG protection) before the ERPS occurs. When a node on the ring detects one or more new faults, it starts up the hold-off timer if the preset hold-off time is set to a value that is not 0. During the hold-off time, the fault is not reported to trigger an ERPS. When the holdoff timer times out, the node checks the link status regardless whether the fault that triggers the startup of the timer exists. If the fault exists, the node reports it to trigger an ERPS. This fault can be the same as or different from the fault that triggers the initial startup of the hold-off timer.
Hold-Off Time(ms)
0 to 10000, in step of 100
Issue 02 (2011-01-20)
B-219
Parameter Guard Time(ms)
Value Range 10 to 2000, in step of 10
Default Value -
Description l This parameter indicates or 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.
B-220
Issue 02 (2011-01-20)
Parameter WTR Time(mm:ss)
Default Value -
Description l This parameter indicates or 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 displays or specifies the interval for sending R-APS packets periodically. This parameter indicates or specifies the level of the maintenance entity. This parameter indicates the last switching request.
Entity Level
0 to 7
Last Switching Request
Issue 02 (2011-01-20)
B-221
Parameter RB Status
Value Range -
Default Value -
Description This parameter indicates the RB (RPL Blocked) status of the packets received by the working node. l noRB: The RPL is not blocked. l RB: The RPL is blocked.
DNF Status
This parameter indicates 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.
B-222
Issue 02 (2011-01-20)
Parameter Status of State Machine
Value Range -
Default Value -
Description This parameter indicates the status of the state machine at the working node. l Idle: The Ethernet ring is in normal state. For example, no node on the Ethernet ring detects any faults or receives the R_APS (NR, RB) packets. l Protection: The Ethernet ring is in protected state. For example, a fault on the node triggers the ERPS, or a node on the ring is in the WTR period after the fault is rectified.
Node Carried with Current Packet
This parameter indicates 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. Displays the status of the east port. Displays the status of the west port.
East Port Status West Port Status
Related Tasks
A.6.1.2 Setting the Parameters of Ethernet Ring Protocol A.6.1.3 Querying the Status of the Ethernet Ring Protocol
B.6.2.3 Parameter Description: MSTP Configuration_Port Group Creation

This topic describes the parameters that are used for creating MSTP port groups.
Issue 02 (2011-01-20)
B-223
Navigation Path
1. 2. 3. Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Ethernet Protocol Configuration > MSTP Configuration from the Function Tree. Click the Port Group Parameters tab. Click Create. The Create Port Group dialog box is displayed.

Parameter Protocol Type Value Range MSTP STP Default Value MSTP Description This parameter specifies the protocol type. l MSTP: stands for Multiple Spanning Tree Protocol. The OptiX RTN 980 supports the CIST MSTP only. l STP: stands for Spanning Tree Protocol. Enable Protocol Enabled Disabled Disabled l This parameter specifies whether to enable the protocol of the port group or a member port in the port group. l If the STP or MSTP is enabled, the spanning tree topology is automatically reconfigured. As a result, the services are interrupted.
Parameters for Application Ports

Parameter Board Value Range Default Value Description This parameter specifies the board where the member of port group is located. This parameter indicates the available port list in which a port can be added to the port group.
Issue 02 (2011-01-20)
Available Port List
B-224
Parameter Selected Port List
Value Range -
Default Value -
Description This parameter indicates the selected ports that can be added to the port group.
Related Tasks
A.6.6.1 Creating the MSTP Port Group
B.6.2.4 Parameter Description: MSTP Configuration_Port Group Configuration

This topic describes the parameters that are used for creating MSTP port groups.
Navigation Path
1. 2. 3. 4. Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Ethernet Protocol Configuration > MSTP Configuration from the Function Tree. Click the Port Group Parameters tab. On the main interface, select the port group to be configured. Click Config. The Configure Port Group dialog box is displayed.
Parameters for the Added Port

Parameter Board Value Range Default Value Description This parameter specifies the board where the member of port group is located. This parameter indicates the available port list in which a port needs to be added to the port group. This parameter indicates the selected ports that need to be added to the port group.
Available Port List
Selected Port List
Related Tasks
A.6.6.7 Modifying the Configuration Data of the MSTP Port Group
B.6.2.5 Parameter Description: MSTP Configuration_ Bridge Parameters

This topic describes the parameters that are related to MSTP bridges.
Navigation Path
1. 2. Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Ethernet Protocol Configuration > MSTP Configuration from the Function Tree. Click the Bridge Parameters tab.

Parameter Port Group ID Value Range Default Value Description l This parameter indicates the ID of the port group. l This parameter can be set to only the port group ID that is automatically allocated. MST Domain Name The OptiX RTN 980 does not support this parameter. The OptiX RTN 980 does not support this parameter. The OptiX RTN 980 does not support this parameter.
Redaction Level
Mapping List
Bridge Parameters
Parameter Port Group ID Value Range Default Value Description l This parameter indicates the ID of the port group. l This parameter can be set to only the port Group ID that is automatically allocated. MST Domain Max Hop Count 20 Specifies the maximum hop count of the MSTP.
B-226
Issue 02 (2011-01-20)
Parameter Network Diameter
Value Range 2 to 7
Default Value 7
Description l This parameter specifies the MSTP network diameter. l Network Diameter is related to the link whose number of switches is the most and is indicated by the number of switches that are connected to the link. When you set Network Diameter for the switches, the MSTP automatically sets Max Age(s), Hello Time(s), and Forward Delay(s) to the more appropriate values for the switches. l If the value of Network Diameter is greater, the network is in a larger scale.
Hello Time(s)
1 to 10
l This parameter specifies 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.
Issue 02 (2011-01-20)
B-227
Parameter Max Age(s)
Value Range 6 to 40
Default Value 20
Description l This parameter specifies 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 in a timely manner and thus the network adaptation ability is reduced.
Forward Delay(s)
4 to 30
15
l This parameter specifies the holdoff 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 the recovery in the case of faults is slower.
Port Parameters
Parameter Port Value Range Default Value Description This parameter indicates the port in the port group.
B-228
Issue 02 (2011-01-20)
Parameter Enable Edge Attribute
Description l This parameter specifies the management edge attributes of the port. l This parameter specifies whether to set the port as an edge port. The edge port refers to the bridge port that is connected to the LAN. In normal cases, this port does not receive or transmit BPDU messages. l This parameter can be set to Enabled only when the port is directly connected to the data communications terminal equipment, such as a computer. In other cases, it is recommended that you use the default value.
Actual Edge Attribute
This parameter indicates the actual management edge attributes of the port.
Issue 02 (2011-01-20)
B-229
Parameter Point-to-Point Attribute
Value Range false true auto
Default Value auto
Description l This parameter specifies the point-topoint attribute of the port. l false: forced nonpoint-to-point link attribute l true: forced point-topoint link attribute l auto: automatically detected point-topoint link attribute l If this parameter is set to auto, the bridge determines Actual Point-to-Point Attribute of the port according to the actual working mode. If the actual working mode is full-duplex, the actual point-to-point attribute is true. If the actual working mode is half-duplex, Actual Point-to-Point Attribute is false. l Only the designated port whose Actual Point-to-Point Attribute is "True" can transmit the rapid state migration request and response. l It is recommended that you use the default value.
Actual Point-to-Point Attribute
This parameter indicates the actual point-to-point attribute of the port.
B-230
Issue 02 (2011-01-20)
Parameter Max Transmit Packet Count
Default Value 3
Description l This parameter specifies the maximum number of packets to be transmitted. l The maximum number of packets to be transmitted by the port refers to the maximum number of MSTP packets that the port can transmit within 1s. l This parameter needs to be set according to the planning information.
Related Tasks
A.6.6.2 Setting the Bridge Parameters of the MSTP
B.6.2.6 Parameter Description: MSTP Configuration_CIST Parameters

This topic describes the parameters that are related to the MSTP CIST.
Navigation Path
1. 2. Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Ethernet Protocol Configuration > MSTP Configuration from the Function Tree. Click the CIST&MSTI Parameters tab.

Parameter Port Group MSTI ID Value Range 0 Default Value 0 Description This parameter specifies the port group. This parameter indicates the MSTI ID. The value 0 indicates common and internal spanning tree (CIST). The OptiX RTN 980 supports only the MSTP that uses CIST.
Issue 02 (2011-01-20)
B-231
Parameter Bridge Priority
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 in the STP/ MSTP network use the same value, the bridge whose MAC address is the smallest is selected as the root bridge.
Port Parameters
Parameter Port Priority Value Range 0 to 240, in step of 16 Default Value 128 Description This parameter indicates the port in the port group. l The most significant eight bits of the port ID indicate the port priority. l When the value is smaller, the priority is higher. Path Cost 1 to 200000000 200000 l This parameter 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.
Related Tasks
A.6.6.3 Setting the Parameters of the CIST
B-232
Issue 02 (2011-01-20)
B.6.2.7 Parameter Description: MSTP Configuration_Running Information About the CIST

This topic describes the parameters that are related to the running information about the MSTP CIST.
Navigation Path
1. 2. Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Ethernet Protocol Configuration > MSTP Configuration from the Function Tree. Click the CIST Running Information tab.

Parameter Port Group ID Protocol Running Mode Value Range MSTP STP Default Value Description This parameter indicates the ID of the port group. l This parameter indicates the running mode of the protocol. l MSTP: stands for Multiple Spanning Tree Protocol. The OptiX RTN 980 supports only the CIST-based MSTP. l STP: stands for Spanning Tree Protocol.
Issue 02 (2011-01-20)
B-233
Parameter Bridge Priority
Default Value 32768
Description l This parameter indicates the priority of the bridge. 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 in the STP network use the same value, the bridge whose MAC address is the smallest is selected as the root bridge.
Bridge MAC Address
This parameter indicates the MAC address of the bridge. This parameter indicates the MAC address of the root bridge. The OptiX RTN 980 does not support this parameter. The OptiX RTN 980 does not support this parameter. The OptiX RTN 980 does not support this parameter. The OptiX RTN 980 does not support this parameter.
Root Bridge MAC Address External Path Cost ERPC Domain Root Bridge Priority Domain Root Bridge MAC Address Internal Path Cost IRPC
B-234
Issue 02 (2011-01-20)
Parameter Root Port Priority
Default Value 128
Description l This parameter indicates the priority of the root port. l The most significant eight bits of the ID of the root port indicate the priority of the root port. l When the value is smaller, the priority is higher.
Root Port Hello Time(s)
This parameter indicates the root port. l This parameter indicates the interval for transmitting 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.
Max Age(s)
6 to 40
20
l This parameter specifies 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 in a timely manner and thus the network adaptation ability is reduced.
Issue 02 (2011-01-20)
B-235
Parameter Forward Delay(s)
Value Range 4 to 30
Default Value 15
Description l This parameter specifies the holdoff 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 the recovery in the case of faults is slower.
MST Domain Max Hop Count Topology Change Count
The OptiX RTN 980 does not support this parameter. This parameter indicates the identifier of the topology change. This parameter indicates the duration of the last topology change. This parameter indicates the count of the topology changes.
Last Topology Change Time(s) Topology Change Count
Port Parameters
Parameter Port Enable Protocol Value Range Enabled Disabled Default Value Disabled Description This parameter indicates the port in the port group. This parameter indicates whether the protocol of the port group or a member of the port group is enabled. This parameter indicates the role of a port.
Port Role
Disabled
B-236
Issue 02 (2011-01-20)
Parameter Port Status
Value Range Discarding Learning Forwarding
Default Value Discarding
Description This parameter indicates the state of a port. l Discarding: receives only BPDU packets l Learning: only receives or transmits BPDU packets l Forwarding: forwards user traffic, and transmits/receives BPDU packets
Priority
0 to 240, in step of 16
128
l The most significant eight bits of the port ID indicate the port priority. l When the value is smaller, the priority is higher.
Path Cost
1 to 200000000
200000
l This parameter 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.
Bridge Priority
0 to 61440, in step of 4096
32768
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 in the STP network use the same value, the bridge whose MAC address is the smallest is selected as the root bridge.
Issue 02 (2011-01-20)
B-237
Parameter Bridge MAC Address
Value Range -
Default Value -
Description This parameter indicates the MAC address of the bridge. l The most significant eight bits of the port ID indicate the port priority. l When the value is smaller, the priority is higher.
Designated Port Priority
Design Port Edge Port Attribute
Disabled Enabled
0 Disabled
This parameter indicates the designated port. l This parameter specifies the management edge attributes of the port. l This parameter specifies whether to set the port as an edge port. The edge port refers to the bridge port that is connected to the LAN. In normal cases, this port does not receive or transmit BPDU messages. l This parameter can be set to Enabled only when the port is directly connected to the data communications terminal equipment, such as a computer. In other cases, it is recommended that you use the default value.
Actual Edge Port Attribute
Disabled
This parameter indicates the actual management edge attributes of the port.
B-238
Issue 02 (2011-01-20)
Parameter Point to Point
Value Range false true auto
Default Value auto
Description l This parameter specifies the point-topoint attribute of the port. l false: forced nonpoint-to-point link attribute l true: forced point-topoint link attribute l auto: automatically detected point-topoint link attribute l If this parameter is set to auto, the bridge determines Actual Point to Point Attribute of the port according to the actual working mode. If the actual working mode is full-duplex, the actual point-to-point attribute is true. If the actual working mode is half-duplex, Actual Point to Point Attribute is false. l Only the designated port whose Actual Point-to-Point Attribute is "True" can transmit the rapid state migration request and response. l It is recommended that you use the default value.
Actual Point to Point
This parameter indicates the actual point-to-point attribute of the port.
Issue 02 (2011-01-20)
B-239
Parameter Max Count of Transmitting Message
Default Value 3
Description l This parameter indicates the maximum number of packets to be transmitted. l The maximum number of packets to be transmitted by the port refers to the maximum number of MSTP packets that the port can transmit within 1s.
Protocol Running Mode
STP MSTP
l This parameter indicates the running mode of the protocol. l MSTP: stands for Multiple Spanning Tree Protocol. The OptiX RTN 980 supports only the CIST-based MSTP. l STP: stands for Spanning Tree Protocol.
Hello Time(s)
1 to 10
l This parameter 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.
B-240
Issue 02 (2011-01-20)
Parameter Max Age(s)
Value Range 6 to 40
Default Value 20
Description l This parameter specifies 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 in a timely manner and thus the network adaptation ability is reduced.
Forward Delay(s)
4 to 30
15
l This parameter specifies 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 the recovery in the case of faults is slower.
Remain Hop
The OptiX RTN 980 does not support this parameter.
Related Tasks
A.6.6.4 Querying the CIST Running Information
B.6.2.8 Parameter Description: Ethernet Link Aggregation Management_LAG Creation

This topic describes the parameters that are used for creating a link aggregation group (LAG).
Issue 02 (2011-01-20)
B-241
Navigation Path
1. 2. 3. Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Interface Management > Link Aggregation Group Management from the Function Tree. Click the Link Aggregation Group Management tab. Click New.

Parameter LAG No. Value Range Default Value 1 Description l This parameter specifies the LAG number to be set manually. l This parameter is valid only when Automatically Assign is not selected. Automatically Assign Selected Deselected Selected l This parameter indicates whether LAG No. is allocated automatically. l When Automatically Assign is selected, LAG No. cannot be set. LAG Name This parameter specifies the LAG name.
B-242
Issue 02 (2011-01-20)
Parameter LAG Type
Value Range Static Manual
Default Value Static
Description l Static: You can create a LAG. When you add or delete a member port to or from the LAG, the Link Aggregation Control Protocol (LACP) protocol is required. In a LAG, a port can be in selected, standby, or unselected state. The aggregation information is exchanged among different equipment through the LACP protocol to ensure that the aggregation information is the same among all the nodes. l Manual: You can create a LAG. When you add or delete a member port, the LACP protocol is not required. The port can be in the up or down state. The system determines whether to aggregate a port according to its physical state (UP or DOWN), working mode, and rate.
Switch Protocol
The OptiX RTN 980 does not support this parameter. The OptiX RTN 980 does not support this parameter. The OptiX RTN 980 does not support this parameter.
Switch Mode
Link Trace Protocol
Issue 02 (2011-01-20)
B-243
Value Range Revertive Non-Revertive
Default Value Non-Revertive
Description l This parameter can be set only when Load Sharing is set to NonSharing. l When a LAG is set to Revertive, the services are switched back to the former working channel after this channel is restored to normal. l When a LAG is set to Non-Revertive, the status of the LAG does not change after the former working channel is restored to normal. That is, the services are still transmitted on the protection channel.
Load Sharing
Sharing Non-Sharing
Non-Sharing
l Sharing: Each member link of a LAG processes traffic at the same time and shares the traffic load. The sharing mode can increase a bandwidth utilization for the link. When the LAG members change, or certain links fail, the system automatically re-allocates the traffic. l Non-Sharing: Only one member link of a LAG carries traffic, and the other link is in the standby state. In this case, a hot backup mechanism is provided. When the active link of a LAG is faulty, the system activates the standby link, thus preventing link failure.
B-244
Issue 02 (2011-01-20)
Parameter Load Sharing Hash Algorithm
Value Range Source MAC Destination MAC Source and Destination MAC Source IP Destination IP Source and Destination IP MPLS Label
Default Value Source MAC
Description l This parameter is valid only when Load Sharing of a LAG is set to Sharing. l The load sharing computation methods include computation based on MAC addresses (based on the source MAC address, based on the destination MAC address, and based on the source MAC address + sink MAC address), computation based on IP addresses (based on the source IP address, based on the destination IP address, and based on the source IP address and sink IP address), and computation based on MPLS labels. l After the configuration data is deployed, Load Sharing Hash Algorithm takes effect for the entire NE. l For PW-carried UNINNI E-Line services, Load Sharing Hash Algorithm cannot be set to MPLS Label.
Issue 02 (2011-01-20)
B-245
Parameter System Priority
Default Value 32768
Description l This parameter indicates the priority of a LAG. The smaller the value of System Priority, the higher the priority. l When a local LAG negotiates with an opposite LAG through LACP packets, both LAGs can obtain the system priorities of each other. Then, the LAG of the higher system priority is considered as the comparison result of both LAGs so that the aggregation information is consistent at both LAGs. If the priorities of both LAGs are the same, the system MAC addresses are compared. Then, the comparison result based on the LAG with smaller system MAC address is considered as the result of both LAGs and is used to ensure that the aggregation information is consistent at both LAGs.
WTR Time(min)
1 to 30
10
l Specifies the WTR time for the LAG. l This parameter takes effect only when Revertive Mode is Revertive.
B-246
Issue 02 (2011-01-20)
Parameter Switch LAG upon Air Interface SD
Description l This parameter specifies whether to enable the switching triggered by bit errors. l If this parameter is set to Enabled, the MW_BER_SD alarm will trigger the LAG switching at the air interface.
Port Settings Parameters

Parameter Main Board Value Range Default Value Description l This parameter specifies the main board in a LAG. l This parameter is set according to the planning information. Main Port l This parameter specifies the main port in a LAG. l After a LAG is created, you can add Ethernet services to the main port only. Services cannot be added to a slave port. When Load Sharing is set to NonSharing, the link connected to the main port is used to transmit the services, and the link connected to the slave port is used for protection. Board (Available Slave Ports) l This parameter specifies the slave board in a LAG. l This parameter is set according to the planning information.
Issue 02 (2011-01-20)
B-247
Parameter Port (Available Slave Ports)
Value Range -
Default Value -
Description l This parameter specifies the salve port in a LAG. l The slave ports in a LAG are fixed. Unless they are manually modified, the system does not automatically add them to or delete them from the LAG.
Selected Slave Ports
This parameter indicates the selected slave ports.
Related Tasks
A.6.2.1 Creating a LAG
B.6.2.9 Parameter Description: Ethernet Link Aggregation_Link Aggregation

This section describes the parameters for port priorities and system priorities.
Navigation Path
1. 2. Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Interface Management > Link Aggregation Group Management from the Function Tree. Click the Port Priority tab.

Parameter Port Value Range Default Value Description This parameter indicates the port whose priority can be set. 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
32768
B-248
Issue 02 (2011-01-20)
Related Tasks
A.6.2.2 Setting Parameters for LAGs
B.6.2.10 Parameter Description: LPT Management_Point-to-Point LPT

This topic describes the parameters that are related to point-to-point LPT.
Navigation Path
1. 2. Select the NE from the Object Tree in the NE Explorer. Choose Configuration > LPT Management from the Function Tree. Click the Point-to-Point LPT tab.
Parameters on the main interface

Parameter Binding Status Value Range Default Value Description This parameter displays the binding status of pointto-point services. This parameter displays the port where the primary point of point-to-point LPT resides. This parameter displays the type of secondary point for point-to-point LPT. This parameter displays the port where the secondary point of pointto-point LPT resides. This parameter displays the status of point-to-point LPT. This parameter displays or specifies the enabling status of point-to-point LPT. The LPT function can take effect only when LPT Enabled is set to Enabled. Recovery Times(s) 1-600 1 This parameter displays or specifies the recovery time of point-to-point LPT.
Primary Function Point
Secondary Function Point Type
Secondary Function Point
LPT Instance Status
LPT Enabled
Enabled Disabled
Disabled
Issue 02 (2011-01-20)
B-249
Parameter Hold-Off Times(ms)
Value Range 0-10000
Default Value 1000
Description This parameter displays or specifies the hold-off time of point-to-point LPT. This parameter displays the switching mode of point-to-point LPT. Pointto-point LPT is available only in strict mode. This parameter displays the fault detection mode of point-to-multipoint LPT. l LPT-enabled NEs periodically transmit LPT OAM packets in specific formats to check the status of an L2 service network or QinQ service network. If the LPT OAM packets are absent for 3.5 fault detection periods or the number and contents of received LPT OAM packets are incorrect, the NEs consider that a network-side fault occurred and the LPT switching is triggered. l To detect a networkside fault on a PSN, LPT OAM or PW OAM packets can be used. Note that the PW OAM function must be enabled on NEs before usage of PW OAM packets.
Switching Mode
Fault Detection
PW OAM LPT OAM
Fault Detection Period (100ms)
3-100
This parameter displays or specifies the fault detection period of pointto-point LPT. This parameter displays the status of a user-side port.
User-Side Port
B-250
Issue 02 (2011-01-20)
Parameter L2 net ID-L2 Peer net ID
Value Range -
Default Value -
Description This parameter displays the NET IDs of LPT packet out ports at both ends.
Related Tasks
A.6.10.1 Configuring Point-to-Point LPT Traversing an L2 Network A.6.10.2 Configuring Point-to-Point LPT Traversing a PSN or QinQ Network
B.6.2.11 Parameter Description: LPT Management_Creating Point-to-Point LPT

This topic describes the parameters that are related to creating point-to-point LPT.
Navigation Path
1. 2. 3. 4. Select the NE from the Object Tree in the NE Explorer. Choose Configuration > LPT Management from the Function Tree. Click the Point-to-Point LPT tab. Click Bind in the lower right corner of the pane based on the type of service network. Choose PW+QinQ or L2 net from the shortcut menu based on the type of service network.

Parameter L2 net ID Value Range 1-4294967295 Default Value Description This parameter specifies the NET ID of LPT packet out port at the local end. This parameter specifies the NET ID of LPT packet out port at the opposite end. This parameter specifies the port where the primary point of point-to-point LPT resides. This parameter specifies the VLAN ID that is carried by a point-to-point LPT packet to traverse an L2 network. This parameter specifies the out port of a point-topoint LPT packet.
B-251
L2 Peer net ID
1-4294967295
VLAN ID
1-4094
LPT package out port
Issue 02 (2011-01-20)
Related Tasks
A.6.10.1 Configuring Point-to-Point LPT Traversing an L2 Network
B.6.2.12 Parameter Description: LPT Management_Point-to-Multipoint LPT

This topic describes the parameters that are related to point-to-multipoint LPT.
Navigation Path
1. 2. Select the NE from the Object Tree in the NE Explorer. Choose Configuration > LPT Management from the Function Tree. Click the Point-to-Multipoint LPT tab.
Parameters of Primary Point

Parameter Primary Function Point Type Value Range Default Value Description This parameter displays the type of primary point for point-to-multipoint LPT. This parameter displays the port where the primary point of point-tomultipoint LPT resides. This parameter displays the status of point-tomultipoint LPT. This parameter displays the enabling status of point-to-multipoint LPT. This parameter displays or specifies the recovery time of point-to-multipoint LPT. This parameter displays or specifies the hold-off time of point-to-multipoint LPT.
LPT Instance Status
LPT Enabled
Enabled Disabled
Disabled
Recovery Times(s)
1-600
Hold-Off Times(ms)
0-10000
1000
B-252
Issue 02 (2011-01-20)
Parameter Switching Mode
Value Range Strict mode Non-strict mode
Default Value Strict mode
Description This parameter displays the switching mode of point-to-multipoint LPT. Point-to-point LPT is available only in strict mode. l Strict mode A primary point triggers LPT switching when all its secondary points detect faults. l Non-strict mode A primary point triggers LPT switching when anyone of its secondary points detects a fault.
Fault Detection
PW OAM LPT OAM
This parameter displays the fault detection mode of point-to-multipoint LPT. l LPT-enabled NEs periodically transmit LPT OAM packets in specific formats to check the status of an L2 service network or QinQ service network. If the LPT OAM packets are absent for 3.5 fault detection periods or the number and contents of received LPT OAM packets are incorrect, the NEs consider that a network-side fault occurred and the LPT switching is triggered. l To detect a networkside fault on a PSN, LPT OAM or PW OAM packets can be used. Note that the PW OAM function must be enabled on NEs before usage of PW OAM packets.
Issue 02 (2011-01-20)
B-253
Parameter Fault Detection Period (100ms)
Value Range 3-100
Default Value 3
Description This parameter displays or specifies the fault detection period of pointto-multipoint LPT. This parameter displays the status of a user-side port. This parameter displays the NET IDs of LPT packet out ports at both ends, when the service network is an L2 network.
User-Side Port
L2 net ID-L2 Peer net ID
Parameters of Secondary Point

Parameter Access Point Type Value Range Default Value Description This parameter displays the type of second point for point-to-multipoint LPT. This parameter displays the port or PW ID for the secondary point of pointto-multipoint LPT. This parameter displays the status of a user-side port. This parameter displays the NET IDs of LPT packet out ports at both ends, when the service network is an L2 network.
Access Point
User-Side Port Status
L2 net ID-L2 Peer net ID
Related Tasks
B.6.2.13 Parameter Description: LPT Management_Creating Point-to-Multipoint LPT

This topic describes the parameters that are related to creating point-to-multipoint LPT.
B-254
Issue 02 (2011-01-20)
Navigation Path
1. 2. 3. 4. Select the NE from the Object Tree in the NE Explorer. Choose Configuration > LPT Management from the Function Tree. Click the Point-to-Multipoint LPT tab. Click New in the lower right corner of the pane based on the type of service network. Choose PW, QinQ, or L2 net from the shortcut menu based on the type of service network.
Parameters of primary point

Parameter Point Type Value Range UNI PW QinQ L2 net Default Value Description This parameter specifies the type of primary point for point-to-multipoint LPT. The value range of this parameter pertains to the type of service network. If the primary point is on the access side, select UNI; if the primary point is on the network side, set the parameter as follows. l If the service network is a PSN, select PW. l If the service network is a QinQ network, select QinQ. l If the service network is an L2 network, select L2 net. Board This parameter specifies the board where the primary point of point-tomultipoint LPT resides. This parameter is valid only when Point Type is set to UNI. Port This parameter specifies the port where the primary point of point-tomultipoint LPT resides. This parameter is valid only when Point Type is set to UNI.
Issue 02 (2011-01-20)
B-255
Parameter Point ID
Value Range -
Default Value -
Description This parameter specifies the service ID for the primary point of point-tomultipoint LPT. This parameter is valid only when Point Type is set to PW or QinQ.
L2 net ID
1-4294967295
This parameter specifies the NET ID of a local NE. This parameter is valid only when Point Type of the primary point is set to UNI, and when Point Type of the secondary point is set to L2 net.
L2 Peer net ID
1-4294967295
This parameter specifies the NET ID of an opposite NE. This parameter is valid only when Point Type is set toL2 net.
VLAN ID
1-4094
This parameter specifies the VLAN ID that is carried by an LPT packet to traverse an L2 network. This parameter is valid only when Point Type is set toL2 net.
LPT package out port
This parameter specifies the out port of an LPT packet. This parameter is valid only when Point Type is set toL2 net.
Parameters of secondary point

Parameter Point Type Value Range UNI PW QinQ L2 net Default Value Description This parameter displays or specifies the type of secondary point for pointto-multipoint LPT.
B-256
Issue 02 (2011-01-20)
Parameter Board
Value Range -
Default Value -
Description This parameter specifies the board where the secondary point of pointto-multipoint LPT resides. This parameter is valid only when Point Type is set to PW, QinQ, or L2 net.
Available Points
This parameter displays the available ports where the secondary point of point-to-multipoint LPT can reside. This parameter is valid only when Point Type is set to PW, QinQ, or L2 net.
Selected Points
This parameter displays the selected port where the secondary point of pointto-multipoint LPT resides. This parameter is valid only when Point Type is set to PW, QinQ, or L2 net.
L2 net ID
1-4294967295
This parameter specifies the NET ID of a local NE. This parameter is valid only when Point Type is set to UNI.
L2 Peer net ID
1-4294967295
This parameter specifies the NET ID of an opposite NE. This parameter is valid only when Point Type of the primary point is set to UNI, and when Point Type of the secondary point is set to L2 net.
Issue 02 (2011-01-20)
B-257
Parameter VLAN ID
Value Range 1-4094
Default Value -
Description This parameter specifies the VLAN ID that is carried by an LPT packet to traverse an L2 network. This parameter is valid only when Point Type of the primary point is set to UNI, and when Point Type of the secondary point is set to L2 net.
LPT Package out port
This parameter specifies the out port of an LPT packet. This parameter is valid only when Point Type of the primary point is set to UNI, and when Point Type of the secondary point is set to L2 net.
Related Tasks
B.6.3 Parameters for the Ethernet OAM

This topic describes the parameters that are related to the Ethernet operation, administration and maintenance (OAM). B.6.3.1 Parameter Description: Ethernet Service OAM Management_Maintenance Domain Creation This topic describes the parameters that are used for creating maintenance domains. B.6.3.2 Parameter Description: Ethernet Service OAM Management_Maintenance Association Creation This topic describes the parameters that are used for creating maintenance associations. B.6.3.3 Parameter Description: Ethernet Service OAM Management_MEP Creation This topic describes the parameters that are used for creating a maintenance association end point (MEP). B.6.3.4 Parameter Description: Ethernet Service OAM Management_Remote MEP Creation This topic describes the parameters that are used for creating a remote MEP. B.6.3.5 Parameter Description: Ethernet Service OAM Management_MIP Creation This topic describes the parameters that are used for creating a maintenance association intermediate point (MIP). B.6.3.6 Parameter Description: Ethernet Service OAM Management_LB Enabling This topic describes the parameters that are used for enabling the LB.
B.6.3.7 Parameter Description: Ethernet Service OAM Management_LT Enabling This topic describes the parameters that are used for enabling the LT. B.6.3.8 Parameter Description: Ethernet Port OAM Management_OAM Parameter This topic describes the OAM parameters that are related to Ethernet ports. B.6.3.9 Parameter Description: Ethernet Port OAM Management_OAM Error Frame Monitoring This topic describes the parameters that are used for monitoring the OAM error frames at the Ethernet port.
B.6.3.1 Parameter Description: Ethernet Service OAM Management_Maintenance Domain Creation

This topic describes the parameters that are used for creating maintenance domains.
Navigation Path
1. 2. 3. Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Ethernet OAM Management > Ethernet Service OAM Management from the Function Tree. Click the Maintenance Association tab. Choose New > New Maintenance Domain.

Parameter Maintenance Domain Name Value Range Default Value default Description l This parameter specifies the name of the maintenance domain. l The maintenance domain refers to the network for the Ethernet OAM. l This parameter can contain a maximum of eight bytes.
Issue 02 (2011-01-20)
B-259
Parameter Maintenance Domain Level
Value Range 0 1 2 3 4 5 6 7
Default Value 4
Description l This parameter specifies the level of the maintenance domain. l The values 0-2 indicate the carrier level, the values 3-4 indicate the supplier level, and the values 5-7 indicate the user level. l When the value is set to 0, the maintenance domain is at the lowest level. The values 0-7 indicate that the level increases in a sequential order. l The OAM packets whose level is higher than the preset value are transparently transmitted by the MEPs. The OAM packets whose level is lower than the preset value are directly discarded by the MEPs. The OAM packets whose level is the same as the preset value are responded to or terminated by the MEPs according to the message type.
Related Tasks
A.6.8.1 Creating an MD
B.6.3.2 Parameter Description: Ethernet Service OAM Management_Maintenance Association Creation

This topic describes the parameters that are used for creating maintenance associations.
Navigation Path
1. 2. 3. Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Ethernet OAM Management > Ethernet Service OAM Management from the Function Tree. Click the Maintenance Association tab. Select the maintenance domain in which a maintenance association needs to be created. Choose New > New Maintenance Association.

Parameter Maintenance Domain Name Value Range Default Value Description This parameter indicates the maintenance domain of the created maintenance association.
B-260
Issue 02 (2011-01-20)
Parameter Maintenance Association Name
Value Range -
Default Value -
Description l This parameter specifies the name of the maintenance association, which is a domain related to a service. Through maintenance association division, the connectivity check (CC) can be performed on the network that transmits a service instance. l This parameter can contain a maximum of eight bytes.
Relevant Service
This parameter specifies the service instance that is related to the maintenance association. l This parameter specifies the interval for transmitting packets in the CC. l The CC is performed to check the availability of the service.
1s 10s 1m 10m
1s
Related Tasks
A.6.8.2 Creating an MA
B.6.3.3 Parameter Description: Ethernet Service OAM Management_MEP Creation

This topic describes the parameters that are used for creating a maintenance association end point (MEP).
Navigation Path
1. 2. 3. Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Ethernet OAM Management > Ethernet Service OAM Management from the Function Tree. Click the Maintenance Association tab. Select the maintenance association in which an MEP needs to be created. Choose New > New MEP Point.

Parameter Maintenance Domain Name Maintenance Association Name Board Value Range Default Value Description This parameter indicates the maintenance domain of the created MEP. This parameter indicates the maintenance association of the created MEP. This parameter specifies the board where the MEP is located.
B-261
Issue 02 (2011-01-20)
Parameter Port VLAN MEP ID
Default Value 1
Description This parameter specifies the port where the MEP is located. This parameter indicates the VLAN ID of the current service. l This parameter specifies the MEP ID. l Each MEP needs to be configured with an MEP ID, which is unique in the maintenance association. The MEP ID is required in the OAM operation.
Direction
Ingress Egress
Ingress
l This parameter specifies the direction of the MEP. l Ingress indicates the direction in which the packets are transmitted to the port, and Egress indicates the direction in which the packets are transmitted from the port.
CC Status
Active Inactive
Active
l This parameter specifies whether to enable the CC function of the MEP. l In the case of the tests based on the MP IDs, CC Status must be set to Active.
Related Tasks
A.6.8.3 Creating an MEP Point
B.6.3.4 Parameter Description: Ethernet Service OAM Management_Remote MEP Creation

This topic describes the parameters that are used for creating a remote MEP.
Navigation Path
1. 2. 3. 4. Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Ethernet OAM Management > Ethernet Service OAM Management from the Function Tree. Click the Maintenance Association tab. Choose OAM > Manage Remote MEP Point. Then, the Manage Remote MEP Point dialog box is displayed. Click New.
B-262
Issue 02 (2011-01-20)

Parameter Maintenance Domain Name Maintenance Association Name Remote Maintenance Point ID(e.g:1,3-6) Value Range 1 to 2048 Default Value Description This parameter indicates the maintenance domain of the MEP. This parameter indicates the maintenance association of the created MEP. l This parameter specifies the ID of the remote MEP. l If other MEPs may initiate OAM operations to an MEP in the same MA, set the other MEPs to be the remote MEPs.
Related Tasks
B.6.3.5 Parameter Description: Ethernet Service OAM Management_MIP Creation

This topic describes the parameters that are used for creating a maintenance association intermediate point (MIP).
Navigation Path
1. 2. 3. Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Ethernet OAM Management > Ethernet Service OAM Management from the Function Tree. Click the MIP Point tab. Select the maintenance domain in which an MIP needs to be created, and then click New.

Parameter Maintenance Domain Name Board Port Value Range Default Value Description This parameter indicates the maintenance domain of the MIP. This parameter specifies the board where the MIP is located. This parameter specifies the port where the MIP is located.
Issue 02 (2011-01-20)
B-263
Parameter MP ID
Default Value 1
Description l This parameter specifies the MIP ID. l Each MIP needs to be configured with an MIP ID, which is unique in the maintenance domain. The MIP ID is required in the OAM operation.
NOTE To create MEPs and MIPs in a service at a port, ensure that only one MIP can be created and the level of the MIP must be higher than the level of the MEP.
Related Tasks
B.6.3.6 Parameter Description: Ethernet Service OAM Management_LB Enabling

This topic describes the parameters that are used for enabling the LB.
Navigation Path
1. 2. 3. 4. Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Ethernet OAM Management > Ethernet Service OAM Management from the Function Tree. Click the Maintenance Association tab. Select the maintenance domain and maintenance association for the LB test. Choose OAM > Start LB.

Parameter Destination Maintenance Point ID Destination Maintenance Point MAC Address Maintenance Domain Name Maintenance Association Name Source Maintenance Point ID Value Range Selected Deselected Selected Deselected Selected Default Value Deselected Description This parameter needs to be selected if the LB test is performed on the basis of Destination Maintenance Point IDs. This parameter needs to be selected if the LB test is performed on the basis of MAC addresses. This parameter indicates the name of the maintenance domain for the LB test. This parameter indicates the name of the maintenance association for the LB test. l This parameter specifies the source maintenance point in the LB test. l Only the MEP can be set to the source maintenance point.
B-264
Parameter Destination Maintenance Point ID
Value Range -
Default Value -
Description l This parameter specifies the destination maintenance point in the LB test. l Only the MEP can be set to the destination maintenance point. l Destination Maintenance Point ID can be set only when MP ID is selected.
Destination Maintenance Point MAC Address
00-00-00-00-00-00
l This parameter specifies the MAC address of the port where the destination maintenance point is located in the LB test. l Only the MAC address of the MEP can be set to the MAC address of the destination maintenance point. l Destination Maintenance Point MAC Address can be set only when Sink Maintenance Point MAC Address.
Transmitted Packet Count
1 to 255
l This parameter specifies the number of packets transmitted each time in the LB test. l When the value is greater, the required duration is longer.
Transmitted Packet Length
64 to 1400
64
l This parameter specifies the length of a transmitted LBM packet. l If the packet length is different, the test result may be different. In normal cases, it is recommended that you use the default value.
Transmitted Packet Priority
0 to 7
l This parameter specifies the priority of transmitting packets. l 0 indicates the lowest priority, and 7 indicates the highest priority. In normal cases, this parameter is set to the highest priority.
Detection Result
This parameter indicates the relevant information and result of the LB test.
Related Tasks
B.6.3.7 Parameter Description: Ethernet Service OAM Management_LT Enabling

This topic describes the parameters that are used for enabling the LT.
Navigation Path
1. 2. 3. 4. Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Ethernet OAM Management > Ethernet Service OAM Management from the Function Tree. Click the Maintenance Association tab. Select the maintenance domain and maintenance association for the LT test. Choose OAM > Start LT.
Test Node Parameters

Parameter Destination Maintenance Point ID Destination Maintenance Point MAC Address Maintenance Domain Name Maintenance Association Name Source Maintenance Point ID Value Range Selected Deselected Selected Deselected Selected Default Value Deselected Description This parameter needs to be selected if the LT test is performed on the basis of MP IDs. This parameter needs to be selected if the LT test is performed on the basis of MAC addresses. This parameter indicates the name of the maintenance domain for the LT test. This parameter indicates the name of the maintenance association for the LT test. l This parameter specifies the source maintenance point in the LT test. l Only the MEP can be set to the source maintenance point. l This parameter specifies the destination maintenance point in the LT test. l Only the MEP can be set to the destination maintenance point. l Destination Maintenance Point ID can be set only when MP ID is selected. Destination Maintenance Point MAC Address 00-00-00-00-00-00 l This parameter specifies the MAC address of the port where the destination maintenance point is located in the LT test. l Only the MAC address of the MEP can be set to the MAC address of the destination maintenance point. l Destination Maintenance Point MAC Address can be set only when Sink Maintenance Point MAC Address.
Destination Maintenance Point ID
B-266
Issue 02 (2011-01-20)
Parameters for the Detection Result

Parameter Source Maintenance Point ID Destination Maintenance Point ID/MAC Response Maintenance Point ID/MAC Hop Count Value Range Default Value Description This parameter indicates the source maintenance point in the LT test. This parameter indicates the MAC address of the port where the destination maintenance point is located in the LT test. This parameter indicates the MAC address of the port where the responding maintenance point is located in the LT test. l This parameter indicates the number of hops from the source maintenance point to the responding maintenance point or to the destination maintenance point in the LT test. l The number of hops indicates the adjacent relation between the responding maintenance point to the source maintenance point. The number of hops increases by one when a responding point occurs on the link from the source maintenance point to the destination maintenance point. Test Result This parameter indicates the result of the LT test.
1 to 64
Related Tasks
A.6.8.8 Performing an LT Test

This topic describes the OAM parameters that are related to Ethernet ports.
Navigation Path
1. 2. Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Ethernet OAM Management > Ethernet Port OAM Management from the Function Tree. Click the OAM Parameter tab.
Issue 02 (2011-01-20)
B-267

Parameter Port Enable OAM Protocol Value Range Enabled Disabled Default Value Disabled Description This parameter indicates the corresponding port. l This parameter indicates or specifies whether to enable the OAM protocol. l After the OAM protocol is enabled, the current Ethernet port starts to use the preset mode to create the OAM connection with the opposite end. OAM Working Mode Active Passive Active l This parameter indicates or specifies the working mode of the OAM. l The port whose OAM working mode is set to Active can initiate the OAM connection. l The port whose OAM working mode is set to Passive can only wait for the opposite end to send the OAM connection request. l The OAM working mode of the equipment at only one end can be Passive. Link Event Notification Enabled Disabled Enabled l This parameter indicates or specifies whether the local link events can be notified to the opposite end. l If the alarms caused by link events can be reported, that is, if the number of performance events (for example, error frame period, error frame, error frame second, and error frame signal cycle) at the local end exceeds the preset threshold, these performance events are notified to the port at the opposite end through the link event notification function. l This parameter is set according to the planning information.
B-268
Issue 02 (2011-01-20)
Parameter Remote Side Loopback Response
Description l This parameter indicates or specifies whether the port responds to the remote loopback. l Remote loopback indicates that the local OAM entity transmits packets to the remote OAM entity for loopback. The local OAM entity can locate the fault and test the link performance through loopback data analysis. l If a port does not support remote loopback response, this port does not respond to the loopback request from the remote port regardless of the OAM port status.
Loopback Status
Non-Loopback Initiate Loopback at Local Respond Loopback of Remote
This parameter indicates the loopback status at the local end.

NOTE Loopback Status is valid only after you choose OAM > Enable Remote Loopback.
OAM Discovery Status
FAULT ACTIVE_SEND_L OCAL PASSIVE_WAIT SEND_LOCAL_R EMOTE SEND_LOCAL_R EMOTE_OK SEND_ANY
This parameter indicates the OAM discovery status at the local end.
Port Transmit Status
FWD DISCARD
l This parameter indicates the status of transmitting packets at the local end. l When a port is in the FWD state, the port forwards the non-OAM packets. When a port is in the DISCARD state, the port discards the non-OAM packets.
Port Receive Status
FWD DISCARD LB
l This parameter indicates the status of receiving packets at the local end. l In the FWD state, the port forwards the non-OAM packets. In the LB state, the port loopback the non-OAM packets. In the DISCARD state, the port discards the non-OAM packets.
Issue 02 (2011-01-20)
B-269
Related Tasks
A.6.9.1 Enabling the OAM Auto-Discovery Function A.6.9.2 Enabling the Link Event Notification
B.6.3.9 Parameter Description: Ethernet Port OAM Management_OAM Error Frame Monitoring
This topic describes the parameters that are used for monitoring the OAM error frames at the Ethernet port.
Navigation Path
1. 2. Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Ethernet OAM Management > Ethernet Port OAM Management from the Function Tree. Click the OAM Error Frame Monitor tab.

Parameter Port Error Frame Monitor Window (ms) Error Frame Monitor Threshold (frame) Value Range 1000 to 60000, in step of 100 1 to 4294967295, in step of 1 Default Value 1000 Description This parameter indicates the corresponding port. This parameter specifies the duration of monitoring error frames. l This parameter specifies the threshold of monitoring error frames. l Within the specified value of Error Frame Monitor Window(ms), if the number of error frames on the link exceeds the preset value of Error Frame Monitor Threshold(frame), an alarm is reported. 1488 to 892800000, in step of 1 1 to 892800000, in step of 1 1488 This parameter specifies the window of monitoring the error frame period. l This parameter specifies the threshold of monitoring the error frame period. l 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. 10 to 900, in step of 1 60 This parameter specifies the time window of monitoring the error frame second.
Error Frame Period Window (frame) Error Frame Period Threshold (frame)
Error Frame Second Window(s)
B-270
Issue 02 (2011-01-20)
Parameter Error Frame Second Threshold (s)
Default Value 1
Description l This parameter specifies the threshold of monitoring error frame seconds. l If any error frame occurs in one second, this second is called an errored frame second. Within the specified value of Error Frame Second Window(s), if the number of error frames on the link exceeds the preset value of Error Frame Second Threshold(s), an alarm is reported.
Error Frame Signal Periodic Monitor Window (Entries) Error Frame Signal Periodic Monitor Threshold (Entries)
This parameter specifies the window of monitoring the error frame signal period.
1 to 7500000000, in step of 1
l This parameter specifies the threshold of monitoring the error frame signal period. l Within the specified value of Error Frame Signal Periodic Monitor Window(Entries), if the number of error signals exceeds the preset value of Error Frame Signal Periodic Monitor Threshold(Entries), an alarm is reported.
Related Tasks
B.6.4 QoS Parameters

This topic describes the parameters that are related to QoS. B.6.4.1 Parameter Description: Diffserv Domain Management This topic describes the parameters that are used for managing DiffServ domains. B.6.4.2 Parameter Description: DiffServ Domain Management_Create This parameter describes the parameters that are used for creating DiffServ (DS) domains. B.6.4.3 Parameter Description: DiffServ Domain Applied Port_Modification This topic describes the parameters that are used for changing DiffServ (DS) domain applied ports. B.6.4.4 Parameter Description: Policy Management This topic describes the parameters that are related to port policies. B.6.4.5 Parameter Description: Port Policy This topic describes the parameters that are used for creating port policies. B.6.4.6 Parameter Description: Port Policy_Traffic Classification Configuration
This parameter describes the parameters that are used for creating traffic classification. B.6.4.7 Parameter Description: Port Shaping Management_Creation This topic describes the parameters that are used for creating port shaping management tasks.

This topic describes the parameters that are used for managing DiffServ domains.
Navigation Path
Select the NE from the Object Tree in the NE Explorer. Choose Configuration > QoS Management > Diffserv Domain Management from the Function Tree.

Parameter Mapping Relation ID Value Range 1 to 8 Default Value 1 Description This parameter indicates the ID of the mapping relation between DiffServ domains. This parameter indicates the name of the mapping relation between DiffServ domains.
Mapping Relation Name
Default Map
NOTE
If one default DiffServ domain exists on the OptiX RTN 980 equipment, Mapping Relation ID is set to 1, and Mapping Relation Name is set to Default Map. If these parameters are not set, all the ports belong to this domain.
Parameters for Ingress Mapping Relation

Parameter CVLAN Value Range 0 to 7 Default Value Description l This parameter indicates the priority of the C-VLAN of the ingress packets. l C-VLAN indicates the client-side VLAN, and the value 7 indicates the highest priority.
B-272
Issue 02 (2011-01-20)
Parameter SVLAN
Value Range 0 to 7
Default Value -
Description l This parameter indicates the priority of the S-VLAN of the ingress packets. l S-VLAN indicates the server-side VLAN, and the value 7 indicates the highest priority.
IP DSCP
0 to 63
l This parameter indicates the DSCP priority of the IP addresses of the ingress packets. l The differentiated services code point (DSCP) refers to bits 0-5 of the differentiated services (DS) field in the packet and indicates the service class and discarding priority of the packet.
MPLS EXP
0 to 7
l Displays the MPLS EXP value of ingress packets. l When a packet in an egress queue leaves an NNI port, the NNI port obtains the packet priority value according to the mappings between PHB service classes of egress queues and egress packet priorities (MPLS EXP values), and writes the obtained priority value into the EXP field of the egress MPLS packet.
NOTE The MPLS EXP value can be modified in the default Diffserv domain (Default Map) only.
Issue 02 (2011-01-20)
B-273
Parameter PHB
Value Range BE AF1 AF2 AF3 AF4 EF CS6 CS7
Default Value -
Description l This parameter indicates the per-hop behavior (PHB) service class of the DiffServ domain. l The PHB service class refers to the forwarding behavior of the DiffServ node on the behavior aggregate (BA) operation. The forwarding behavior can meet the specific requirements. l The PHB service classes are BE, AF1, AF2, AF3, AF4, EF, CS6, and CS7. The priorities (C_VLAN priority, S_VLAN priority, DSCP value, and MPLS EXP value) contained in the packets of the DiffServ domain and the eight PHB service classes meet the requirements of the specified or default mapping relation.
NOTE The AF1 is classified into three sub service classes, namely, AF11, AF12, and AF13, only one of which is valid. It is the same case with the AF2, AF3, and AF4.
B-274
Issue 02 (2011-01-20)
Parameters for Egress Mapping Relation

Parameter PHB Value Range BE AF1 AF2 AF3 AF4 EF CS6 CS7 Default Value Description l This parameter indicates the PHB service class of the DiffServ domain. l The PHB service class refers to the forwarding behavior of the DiffServ node on the behavior aggregate (BA) operation. The forwarding behavior can meet the specific requirements. l The PHB service classes are BE, AF1, AF2, AF3, AF4, EF, CS6, and CS7. The priorities (C_VLAN priority, S_VLAN priority, DSCP value and MPLS value) contained in the packets of the DiffServ domain and the eight PHB service classes meet the requirements of the specified or default mapping relation.
CVLAN
0 to 7
l This parameter indicates the priority of the C-VLAN of the egress packets. l C-VLAN indicates the client-side VLAN, and the value 7 indicates the highest priority.
Issue 02 (2011-01-20)
B-275
Parameter SVLAN
Value Range 0 to 7
Default Value -
Description l This parameter indicates the priority of the S-VLAN of the egress packets. l S-VLAN indicates the server-side VLAN, and the value 7 indicates the highest priority.
IP DSCP
0 to 63
l This parameter indicates the DSCP priority of the IP addresses of the ingress packets. l The DSCP refers to bits 0-5 of the DS field in the packet and indicates the service class and discarding priority of the packet.
MPLS EXP
0 to 7
l Displays the MPLS EXP value of egress packets. l When a packet arrives at an NNI port, the NNI port obtains the packet priority value depending on its trusted priority type (MPLS EXP value) and specifies the PHB service class of the packet according to the mappings between packet priorities and PHB service classes.
B-276
Issue 02 (2011-01-20)

Parameter Port Value Range Default Value Description This parameter indicates the port that uses the DiffServ domain. The packets trusted by the OptiX RTN 980 are the C_VLAN, S_VLAN and IP DSCP packets that contain the C_VLAN priority, S_VLAN priority, DSCP value or MPLS value. By default, the untrusted packets are mapped to the BE service class for best-effort forwarding.
NOTE l The trusted packet priorities of a UNI port include DSCP value, CVLAN priority, and SVLAN priority. For the E-Line services that are transparently transmitted end to end (UNI-UNI), a UNI port only trusts DSCP value. l An NNI port carrying MPLS/PWE3 services trusts only packets with MPLS EXP values. l The trusted packet priorities of a QinQ link NNI port are configured according to the planning information.
Packet Type
CVLAN SVLAN IP-DSCP MPLS-EXP
CVLAN
Related Tasks
A.6.7.2 Modifying the Mapping Relationships for the DS Domain A.6.7.10 Querying the DS Domain of a Port
B.6.4.2 Parameter Description: DiffServ Domain Management_Create

This parameter describes the parameters that are used for creating DiffServ (DS) domains.
Issue 02 (2011-01-20)
B-277
Navigation Path
1. Select the NE from the Object Tree in the NE Explorer. Choose Configuration > QoS Management > Diffserv Domain Management > Diffserv Domain Management from the Function Tree. Click New.
2.

Parameter Mapping Relation ID Value Range 2 to 8 Default Value Description This parameter specifies the ID of the mapping relation of a DS domain. This parameter specifies the name of the mapping relation of a DS domain.
Mapping Relation Name
Parameters for Ingress Mapping Relation

Parameter CVLAN Value Range 0 to 7 Default Value Description l This parameter specifies the C-VLAN priority of the ingress packets. l C-VLAN indicates the client-side VLAN, and the value 7 indicates the highest priority. SVLAN 0 to 7 l This parameter specifies the S-VLAN priority of the ingress packets. l S-VLAN indicates the server-side VLAN, and the value 7 indicates the highest priority.
B-278
Issue 02 (2011-01-20)
Parameter IP DSCP
Value Range 0 to 63
Default Value -
Description l This parameter specifies the DSCP priority of the IP addresses of the ingress packets. l The differentiated services code point (DSCP) refers to bits 0-5 of the differentiated services (DS) field in the packet and indicates the service class and discarding priority of the packet.
MPLS EXP
l Displays the MPLS EXP value of ingress packets. l When a packet in an egress queue leaves an NNI port, the NNI port obtains the packet priority value according to the mappings between PHB service classes of egress queues and egress packet priorities (MPLS EXP values), and writes the obtained priority value into the EXP field of the egress MPLS packet.
Issue 02 (2011-01-20)
B-279
Parameter PHB
Value Range BE AF1 AF2 AF3 AF4 EF CS6 CS7
Default Value -
Description l This parameter indicates the PHB service class of the DS domain. l The PHB service class refers to the forwarding behavior of the DS node on the behavior aggregate (BA) operation. The forwarding behavior can meet the specific requirements. l The PHB service classes are BE, AF1, AF2, AF3, AF4, EF, CS6, and CS7. The priorities (C_VLAN priority, S_VLAN priority, DSCP value and MPLS EXP value) contained in the packets of the DS domain and the eight PHB service classes meet the requirements of the specified or default mapping relation.
B-280
Issue 02 (2011-01-20)
Parameters for Egress Mapping Relation

Parameter PHB Value Range BE AF1 AF2 AF3 AF4 EF CS6 CS7 Default Value Description l This parameter indicates the PHB service class of the DS domain. l The PHB service class refers to the forwarding behavior of the DS node on the behavior aggregate (BA) operation. The forwarding behavior can meet the specific requirements. l The PHB service classes are BE, AF1, AF2, AF3, AF4, EF, CS6, and CS7. The priorities (C_VLAN priority, S_VLAN priority, DSCP value and MPLS EXP value) contained in the packets of the DS domain and the eight PDB service classes meet the requirements of the specified or default mapping relation.
CVLAN
0 to 7
l This parameter specifies the C-VLAN priority of the egress packets. l C-VLAN indicates the client-side VLAN, and the value 7 indicates the highest priority.
Issue 02 (2011-01-20)
B-281
Parameter SVLAN
Value Range 0 to 7
Default Value -
Description l This parameter specifies the S-VLAN priority of the egress packets. l S-VLAN indicates the server-side VLAN, and the value 7 indicates the highest priority.
IP DSCP
0 to 63
l This parameter specifies the DSCP priority of the IP addresses of the egress packets. l The differentiated services code point (DSCP) refers to bits 0-5 of the differentiated services (DS) field in the packet and indicates the service class and discarding priority of the packet.
MPLS EXP
l Displays the MPLS EXP value of egress packets. l When a packet in an egress queue leaves an NNI port, the NNI port obtains the packet priority value according to the mappings between PHB service classes of egress queues and egress packet priorities (MPLS EXP values), and writes the obtained priority value into the EXP field of the egress MPLS packet.
B-282
Issue 02 (2011-01-20)

Parameter Board Value Range Default Value Description This parameter specifies the board that uses the mapping relations between DS domains. This parameter displays the available port list from which you can select the port that uses the mapping relations between DS domains. This parameter displays the selected port list. The ports in the list use the mapping relations between DS domains.
Available Ports
Port
Issue 02 (2011-01-20)
B-283
Parameter Packet Type
Value Range cvlan svlan ip-dscp mpls-exp
Default Value cvlan
Description l This parameter specifies the type of the packet. l The packets trusted by the OptiX RTN 980 are the C_VLAN, S_VLAN, IP DSCP and MPLS packets that contain the C_VLAN priority, S_VLAN priority, or DSCP value or MPLS EXP value. By default, the untrusted packets are mapped to the BE service class for besteffort forwarding.
Related Tasks
A.6.7.1 Creating a DS Domain
B.6.4.3 Parameter Description: DiffServ Domain Applied Port_Modification

This topic describes the parameters that are used for changing DiffServ (DS) domain applied ports.
B-284
Issue 02 (2011-01-20)
Navigation Path
1. 2. 3. 4. Select the NE from the Object Tree in the NE Explorer. Choose Configuration > QoS Management > Diffserv Domain Management from the Function Tree. Select the DS domain to be changed in the main interface. Click the Apply Port tab. Click Modify.
Parameters for Configuring the Applied Ports

Parameter Mapping Relation Name Value Range Default Value Description This parameter indicates the name of the mapping relation of a DS domain. The packets trusted by the OptiX RTN 980 are the CVLAN, S-VLAN, IP DSCP packets, and MPLS packets that respectively contain the C-VLAN priority, S-VLAN priority, IP DSCP value and MPLS EXP value. By default, the untrusted packets are mapped to the BE service class for besteffort forwarding.
Packet Type
CVLAN SVLAN IP-DSCP MPLS-EXP
CVLAN
Board
This parameter specifies the board where the port is located.
Issue 02 (2011-01-20)
B-285
Parameter Available Port Selected Port
Value Range -
Default Value -
Description This parameter indicates the available port. This parameter indicates the selected port. The selected port is applied to the DS domain.
NOTE
If one default DS domain exists on the OptiX RTN 980, Mapping Relation ID is set to 1, and Mapping Relation Name is set to Default Map. If these parameters are not set, all the ports belong to this domain.
Related Tasks
A.6.7.3 Changing the Ports Applied to a DS Domain and Their Trusted Packet Types

This topic describes the parameters that are related to port policies.
Navigation Path
Select the NE from the Object Tree in the NE Explorer. Choose Configuration > QoS Management > Policy Management from the Function Tree.
Parameters
Parameter Policy ID Policy Name Value Range Default Value Description This parameter indicates the policy ID of the port. This parameter indicates or specifies the policy name of the port.
B-286
Issue 02 (2011-01-20)
Parameter CoS
Value Range CS7 CS6 EF AF4 AF3 AF2 AF1 BE
Default Value -
Description l The BE, AF1, AF2, AF3, AF4, EF, CS6, and CS7 service classes respectively map eight queuing entities. The OptiX RTN 980 provides different QoS policies for the queues at different service classes. l CS6-CS7: indicates the highest service grade, which is mainly involved in signaling transmission. l EF: indicates fast forwarding. This service class is applicable to the traffic whose delay is small and packet loss ratio is low, for example, voice and video services. l AF1-AF4: indicates assured forwarding. This service class is applicable to the traffic that requires rate guarantee but does not require delay or jitter limit. l BE: indicates that the traffic is forwarded in best-effort manner without special processing.
Issue 02 (2011-01-20)
B-287
Parameter Grooming Police After Reloading
Value Range SP WRR
Default Value CS7, CS6, EF, BE: SP AF4, AF3, AF2, AF1: WRR
Description l The strict priority (SP) scheduling algorithm is designed for the key services. One important characteristic of the key services is that higher priorities are required to minimize the response delay in the case of congestion events. l The weighted round robin (WRR) scheduling algorithm divides each port into multiple output subqueues. The polling scheduling is performed among the output sub-queues to ensure that each subqueue has a certain period of service time. l The OptiX RTN 980 supports the setting of the SP+WRR scheduling algorithm of the CoS queue according to the requirement, and provides one or more queues that comply with the SP algorithm. Except for the default value, however, the value of the WRR scheduling algorithm and the value of the SP scheduling algorithm cannot be interleaved. That is, except for the default value, Grooming Police After Reloading can be changed from SP to WRR according to the queue priorities in a descending order (CS7-BE).
B-288
Issue 02 (2011-01-20)
Parameter
Value Range
Default Value
Description l This parameter is set according to the planning information.
Policy Weight(%)
1 to 100
25
l This parameter specifies the weight of the policy in the WRR queue. The weight indicates the percentage of the bandwidth resources obtained by the WRR queue. l This parameter can be set only when Grooming Police After Reloading is set to WRR. l This parameter is set according to the planning information.
Bandwidth Limit
Disabled Enabled
Disabled
l This parameter indicates or specifies whether traffic shaping is enabled for an egress queue corresponding to a PHB service class. l CIR (kbit/s), PIR (kbit/s), CBS (byte), and PBS (byte) can be set only when Bandwidth Limit is set to Enabled. l This parameter is set according to the planning information.
CIR(kbit/s)
Traffic shaping for an egress queue uses the single token bucket two color marker algorithm. The value of the CIR must be equal to the value of the PIR. In actual traffic shaping processing, only the PIR is valid.
Issue 02 (2011-01-20)
B-289
Parameter PIR(kbit/s)
Value Range -
Default Value -
Description l When the buffer queue is empty, the packets are processed as follows: If the rate of a packet is equal to or lower than the PIR, it is directly forwarded; if the rate of a packet is higher than the PIR, it enters the buffer queue and then is forwarded at a rate equal to the PIR. l When the buffer queue is not empty, the packets whose rate passes the restriction of the PIR directly enter the buffer queue and then are forwarded at a rate equal to the PIR. l This parameter is set according to the planning information.
CBS(byte)
l It is recommended that you set the value of the CBS equal to the value of the PIR. In actual traffic shaping processing, only the PBS is valid. l This parameter is set according to the planning information.
B-290
Issue 02 (2011-01-20)
Parameter PBS(byte)
Value Range -
Default Value -
Description l When the buffer queue is empty, certain burst packets can be forwarded if the rate of the packets is equal to or lower than the PIR in a certain period. The maximum traffic of the burst packets is determined by the PBS. l This parameter is set according to the planning information.
Related Tasks
A.6.7.5 Modifying the Port Policy A.6.7.7 Setting the Port That Uses the Port Policy A.6.7.9 Querying the Port Policy
B.6.4.5 Parameter Description: Port Policy

This topic describes the parameters that are used for creating port policies.
Navigation Path
1. 2. 3. Select the NE from the Object Tree in the NE Explorer. Choose Configuration > QoS Management > Policy Management > Port Policy from the Function Tree. Click the CoS Configuration tab. Click New. The Create Port Policy dialog box is displayed.
Parameters
Parameter Policy ID Automatically Assign Value Range Selected Deselected Default Value Deselected Description This parameter specifies the policy ID of the port. This parameter specifies whether to automatically allocate the policy ID of the port policy. After this parameter is selected, the system automatically allocates the policy ID, and then the policy ID cannot be set manually.
B-291
Issue 02 (2011-01-20)
Parameter Policy Name
Value Range -
Default Value -
Description This parameter specifies the policy name of the port. l The BE, AF1, AF2, AF3, AF4, EF, CS6, and CS7 service classes respectively map eight queuing entities. The OptiX RTN 980 provides different QoS policies for the queues at different service class. l CS6-CS7: indicates the highest service grade, which is mainly involved in signaling transmission. l EF: indicates fast forwarding. This service class is applicable to the traffic whose delay is small and packet loss ratio is low, for example, voice and video services. l AF1-AF4: indicates assured forwarding. This service class is applicable to the traffic that requires rate guarantee but does not require delay or jitter limit. l BE: indicates that the traffic is forwarded in best-effort manner without special processing.
CoS
CS7 CS6 EF AF4 AF3 AF2 AF1 BE
B-292
Issue 02 (2011-01-20)
Parameter Grooming Police After Reloading
Value Range SP WRR
Default Value CS7, CS6, EF, BE: SP AF4, AF3, AF2, AF1: WRR
Description l The strict priority (SP) scheduling algorithm is designed for the key services. One important characteristic of the key services is that higher priorities are required to minimize the response delay in the case of congestion events. l The weighted round robin (WRR) scheduling algorithm divides each port into multiple output subqueues. The polling scheduling is performed among the output sub-queues to ensure that each subqueue has a certain period of service time. l The OptiX RTN 980 supports the setting of the SP+WRR scheduling algorithm of the CoS queue according to the requirement, and provides one or more queues that comply with the SP algorithm. Except for the default value, however, the value of the WRR scheduling algorithm and the value of the SP scheduling algorithm cannot be interleaved. That is, except for the default value, Grooming Police After Reloading can be changed from SP to WRR according to the queue priorities in a descending order (CS7-BE).
Issue 02 (2011-01-20)
B-293
Parameter
Value Range
Default Value
Description l This parameter is set according to the planning information.
Policy Weight(%)
1 to 100
25
l This parameter specifies the weight of the policy in the WRR queue. The weight indicates the percentage of the bandwidth resources obtained by the WRR queue. l This parameter can be set only when Grooming Police After Reloading is set to WRR. l This parameter is set according to the planning information.
Bandwidth Limit
Disabled Enabled
Disabled
l This parameter indicates or specifies whether traffic shaping is enabled for an egress queue corresponding to a PHB service class. l CIR (kbit/s), PIR (kbit/s), CBS (byte), and PBS (byte) can be set only when Bandwidth Limit is set to Enabled. l This parameter is set according to the planning information.
CIR(kbit/s)
Traffic shaping for an egress queue uses the single token bucket two color marker algorithm. The value of the CIR must be equal to the value of the PIR. In actual traffic shaping processing, only the PIR is valid.
B-294
Issue 02 (2011-01-20)
Value Range -
Default Value -
Description l When the buffer queue is empty, the packets are processed as follows: If the rate of a packet is equal to or lower than the PIR, it is directly forwarded; if the rate of a packet is higher than the PIR, it enters the buffer queue and then is forwarded at a rate equal to the PIR. l When the buffer queue is not empty, the packets whose rate passes the restriction of the PIR directly enter the buffer queue and then are forwarded at a rate equal to the PIR. l This parameter is set according to the planning information.
CBS(byte)
l It is recommended that you set the value of the CBS equal to the value of the PIR. In actual traffic shaping processing, only the PBS is valid. l This parameter is set according to the planning information.
Issue 02 (2011-01-20)
B-295
Parameter PBS(byte)
Value Range -
Default Value -
Description l When the buffer queue is empty, certain burst packets can be forwarded if the rate of the packets is equal to or lower than the PIR in a certain period. The maximum traffic of the burst packets is determined by the PBS. l This parameter is set according to the planning information.
Related Tasks
A.6.7.4 Creating a Port Policy
B.6.4.6 Parameter Description: Port Policy_Traffic Classification Configuration

This parameter describes the parameters that are used for creating traffic classification.
Navigation Path
1. 2. 3. Select the NE from the Object Tree in the NE Explorer. Choose Configuration > QoS Management > Policy Management > Port Policy from the Function Tree. Click the Traffic Classification Configuration tab. Click New.

Parameter Traffic Classification ID Value Range 1 to 1024 Default Value Description This parameter specifies the ID of the traffic classification.
B-296
Issue 02 (2011-01-20)
Parameter ACL Action
Value Range Permit Deny
Default Value Permit
Description l The access control list (ACL) determines whether to forward or discard the packets that enter the port according to the specified matching rules. l When ACL Action is set to Permit, the ingress port accepts and then performs QoS processing for only the packets that meet the specified mapping rules. l When ACL Action is set to Deny, the ingress port discards the packets that meet the specified mapping rules.
Ingress Parameters
Parameter Logical Relation Between Matched Rules Value Range And Default Value And Description l This parameter specifies the logical relationship between the traffic classification matching rules. l The OptiX RTN 980 supports the setting of the logical AND between multiple matching rules.
Issue 02 (2011-01-20)
B-297
Parameter Match Type
Value Range DSCP Value CVlan ID CVlan priority SVlan ID SVlan priority
Default Value -
Description l After you click Add or Delete, complex traffic classification can be performed on the traffic that enters the ingress port according to the preset matching rules. l In the case a specific service, complex traffic classification can be divided into basic traffic types according to the DSCP value, C_VLAN ID, C_VLAN priority, S_VLAN ID, or S_VLAN priority. Traffic type is based on the associated Ethernet packets. Therefore, this parameter is set according to the packet type and the planning information.
Match Value
DSCP Value: 0 to 63 CVlan ID: 1 to 4094 CVlan priority: 0 to 7 SVlan ID: 1 to 4094 SVlan priority: 0 to 7
l If the matching value of the packets is the same as the preset Match Value, the packets match the rules of complex traffic classification. l This parameter is set according to the planning information.
B-298
Issue 02 (2011-01-20)
Parameter CoS
Default Value -
Description l This parameter specifies the PHB service class queue mapped by the traffic classification packets. l If this parameter is set to empty (-), the traffic classification packets map the PHB service class queue according the mapping relation specified in the topic about Diffserv domain management. l This parameter is set according to the planning information.
Bandwidth Limit
Disabled Enabled
Enabled
l This parameter indicates or specifies whether the CAR operation is performed for the flow in the ingress direction. l CIR (kbit/s), PIR (kbit/s), CBS (byte), and PBS (byte) can be set only when Bandwidth Limit is set to Enabled. l This parameter is set according to the planning information.
Issue 02 (2011-01-20)
B-299
Parameter CIR(kbit/s)
Value Range -
Default Value -
Description l When the rate of the packets is not more than the CIR, the packets are marked blue and pass the CAR policing. These packets are first forwarded in the case of network congestion. l 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 can pass the restriction of the CAR and are marked yellow. The processing method of the packets marked yellow can be set to "Pass" or "Remark". "Remark" indicates that the packets are mapped into another specified queue of a higher priority (this is equal to changing the priority of the packets) and then forwarded to the next port. If a network congestion event occurs again, the packets marked yellow can be processed according to the new priority. l This parameter is set according to the planning information.
B-300
Issue 02 (2011-01-20)
Value Range -
Default Value -
Description l When the rate of the packets is more than the PIR, the packets that exceed the rate restriction are marked red and directly discarded. l 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 can pass the restriction of the CAR and are marked yellow. The processing method of the packets marked yellow can be set to "Pass" or "Remark". "Remark" indicates that the packets are mapped into another specified queue of a higher priority (this is equal to changing the priority of the packets) and then forwarded to the next port. If a network congestion event occurs again, the packets marked yellow can be processed according to the new priority. l This parameter is set according to the planning information.
Issue 02 (2011-01-20)
B-301
Parameter CBS(byte)
Value Range -
Default Value -
Description l During a certain period, if the rate of the packets whose processing method is marked "Pass" is not more than the CIR, certain burst packets are allowed and can be first forwarded in the case of network congestion. The maximum traffic of the burst packets is determined by the CBS. l This parameter is set according to the planning information.
PBS(byte)
l During a certain period, if the rate of the packets whose processing method is marked "Pass" is more than the CIR but not more than the PIR, certain burst packets are allowed and marked yellow. The maximum traffic of the burst packets is determined by the PBS. l This parameter is set according to the planning information.
B-302
Issue 02 (2011-01-20)
Parameter Coloration Mode
Value Range Color Blindness
Default Value Color Blindness
Description l This parameter specifies the CAR operation performed by the equipment on the packets. The packets are dyed according to the result of the CAR operation. The dying rule is determined by the comparison between the rate of the packets and the preset CAR value. l The OptiX RTN 980 supports Color Blindness only.
Packet Color
Red Yellow Green
Packets can be dyed in three colors: red, yellow, and green. The packets in red are first discarded. l This parameter specifies the method of handling the packets. l Discard: The packets are discarded. l Pass: The packets are forwarded. l Remark: The packets are remarked. "Remark" indicates that the packets are mapped into another specified queue of a higher priority (this is equal to changing the priority of the packets) and then forwarded to the next port.
Handling Mode
Discard Pass Remark
Issue 02 (2011-01-20)
B-303
Parameter Relabeled CoS
Default Value -
Description If the handling method is set to "Remark", you can reset the CoS of the packets.
Egress Parameters
Parameter Bandwidth Limit Value Range Disabled Enable Default Value Enable Description l This parameter indicates or specifies whether the traffic shaping is performed in the egress function. l CIR (kbit/s), PIR (kbit/s), CBS (byte), and PBS (byte) can be set only when Bandwidth Limit is set to Enabled. l This parameter is set according to the planning information.
B-304
Issue 02 (2011-01-20)
Parameter CIR(kbit/s)
Value Range -
Default Value -
Description l In the case that no packets exist in the egress queue: When the rate of the packets is not more than the CIR, these packets directly enter the egress queue. l In the case that certain packets exist in the egress queue: The packets whose rate passes the restriction of the PIR directly enter the egress queue, which forwards the packets to the next port at the CIR. l This parameter is set according to the planning information.
Issue 02 (2011-01-20)
B-305
Value Range -
Default Value -
Description l In the case that no packets exist in the egress queue: If 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 enter the egress queue, which forwards the packets to the next port at the CIR. If the rate of the packets is more than the PIR, the packets are directly discarded. l In the case that certain packets exist in the egress queue: The packets whose rate passes the restriction of the PIR directly enter the egress queue, which forwards the packets to the next port at the CIR. l This parameter is set according to the planning information.
CBS(byte)
l If the rate of the packets is not more than the CIR during a certain period, the burst packets are directly transmitted. The maximum traffic of the burst packets is determined by the CBS. l This parameter is set according to the planning information.
B-306
Issue 02 (2011-01-20)
Parameter PBS(byte)
Value Range -
Default Value -
Description l If the rate of the packets is more than the CIR but is not more than the PIR during a certain period, the burst packets enter the egress queue. The maximum traffic of the burst packets is determined by the PBS. l This parameter is set according to the planning information.
Related Tasks
B.6.4.7 Parameter Description: Port Shaping Management_Creation

This topic describes the parameters that are used for creating port shaping management tasks.
Navigation Path
1. 2. Select the NE from the Object Tree in the NE Explorer. Choose Configuration > QoS Management > Port Shaping Management from the Function Tree. Click New.
Parameters for Port Shaping Management

Parameter Slot No. Port CIR (kbit/s) CBS (byte) PIR (kbit/s) Value Range Default Value Description This parameter specifies the slot ID. This parameter specifies the port. Traffic shaping for an egress queue uses the single token bucket two color marker algorithm. The value of the CIR must be equal to the value of the PIR. In actual traffic shaping processing, only the PIR is valid.
B-307
Issue 02 (2011-01-20)
Parameter PBS (byte)
Value Range -
Default Value -
Description If the traffic shaping function is enabled, OptiX RTN 980 processes the packets in the buffer queue through the following methods when no packets are available in the queue. l When the buffer queue is empty, the packets are processed as follows: If the rate of a packet is equal to or lower than the PIR, it is directly forwarded; if the rate of a packet is higher than the PIR, it enters the buffer queue and then is forwarded at a rate equal to the PIR. l When the buffer queue is empty, certain burst packets can be forwarded if the rate of the packets is equal to or lower than the PIR in a certain period. The maximum traffic of the burst packets is determined by the PBS. l When the buffer queue is not empty, the packets whose rate passes the restriction of the PIR directly enter the buffer queue and then are forwarded at a rate equal to the PIR.
Related Tasks
A.6.7.8 Configuring Port Shaping
B.7 RMON Parameters

This topic describes the parameters that are related to RMON performances. B.7.1 Parameter Description: RMON Performance_Statistics Group This topic describes the parameters that are related to RMON statistics groups. B.7.2 Parameter Description: RMON Performance_History Group This topic describes the parameters that are related to RMON history groups. B.7.3 Parameter Description: RMON Performance_History Control Group This topic describes the parameters that are related to RMON history control groups. B.7.4 Parameter Description: RMON Performance_RMON Setting This topic describes the parameters that are related to RMON setting.
B.7.1 Parameter Description: RMON Performance_Statistics Group

This topic describes the parameters that are related to RMON statistics groups.
Navigation Path
1. 2. Select the corresponding board from the Object Tree in the NE Explorer. Choose Performance > RMON Performance from the Function Tree. Click the Statistics Group tab.
Parameters
Parameter Object Sampling Period Display Accumulated Value Value Range 5 to 150 Selected Deselected Default Value 5 Deselected Description This parameter specifies the object to be monitored. This parameter specifies the duration of the monitoring period. l This parameter specifies the method of displaying the performance events. l If this parameter is not selected, the displayed value is an increment compared to the value that is collected in last sampling period and stored in the register. l If this parameter is selected, the displayed value is an absolute value that is currently stored in the register.
Issue 02 (2011-01-20)
B-309
Parameter Display Mode
Value Range Graphics List
Default Value List
Description l This parameter specifies the method of displaying the performance events. l If this parameter is set to Graphics, the number of performance events to be monitored at each time cannot be more than 10, and the unit should be the same.
Legend
Color Description
l This parameter indicates the description of different colors. l This parameter is valid only when Display Mode is set to Graphics.
Event
l This parameter indicates the queried performance events. l This parameter is valid only when Display Mode is set to List.
Related Tasks
A.9.1 Browsing the Performance Data in the Statistics Group of an Ethernet Port
B.7.2 Parameter Description: RMON Performance_History Group

This topic describes the parameters that are related to RMON history groups.
Navigation Path
1. 2. Select the corresponding board from the Object Tree in the NE Explorer. Choose Performance > RMON Performance from the Function Tree. Click the History Group tab.
Parameters
Parameter Object Ended from/to History Table Type Value Range 30-Second 30-Minute Custom Period 1 Custom Period 2 Default Value 30-Second Description The parameter indicates the object to be monitored. This parameter specifies the start time and end time of the monitoring period. This parameter specifies the monitoring period.
B-310
Issue 02 (2011-01-20)
Parameter Display Mode
Value Range Graphics List
Default Value List
Description l This parameter specifies the method of displaying the performance events. l If this parameter is set to Graphics, the number of performance events to be monitored at each time cannot be more than 10, and the unit should be the same.
Legend
Color Description
l This parameter indicates the description of different colors. l This parameter is valid only when Display Mode is set to Graphics.
Event
l This parameter indicates the queried performance events. l This parameter is valid only when Display Mode is set to List.
Statistical Item Statistical Value Time Flag
This parameter indicates the performance items to be monitored. This parameter indicates the statistical value of the monitored performance items. This parameter indicates the time point of each performance event.
B.7.3 Parameter Description: RMON Performance_History Control Group

This topic describes the parameters that are related to RMON history control groups.
Navigation Path
Select the NE from the Object Tree in the NE Explorer. Choose Performance > RMON History Control Group.
Parameters
Parameter 30-Second Value Range Enabled Disabled 30-Minute Enabled Disabled Enabled Default Value Disabled Description This parameter indicates or specifies whether to enable the 30-Second monitoring function. This parameter indicates or specifies whether to enable the 30-Minute monitoring function.
Issue 02 (2011-01-20)
B-311
Parameter Custom Period 1
Description This parameter indicates or specifies whether to enable Custom Period 1. This parameter indicates or specifies whether to enable Custom Period 2. l This parameter indicates or specifies the monitoring period in Custom Period 1 and Custom Period 2. l The value must be an integer multiple of 30. This parameter indicates or specifies the quantity of the history registers.
Custom Period 2
Enabled Disabled
Disabled
Period Length(s)
300 to 43200 (Custom Period 1) 300 to 86400 (Custom Period 2)
900(Custom Period 1) 86400(Custom Period 2) 16 6(Custom Period 2)
History Register Count
1 to 50
Related Tasks
A.9.3 Configuring a History Control Group

This topic describes the parameters that are related to RMON setting.
Navigation Path
l l Select the corresponding board from the Object Tree in the NE Explorer. Choose Performance > RMON Performance from the Function Tree. Click the RMON Setting tab.
Object Parameters
Parameter Object 30-Second Value Range Enabled Disabled Default Value Description This parameter indicates the object to be collected. This parameter indicates or specifies whether to enable the 30-Second monitoring function.
NOTE In the case of Object, 30-Second cannot be set.
30-Minute
Enabled Disabled
Disabled
l This parameter indicates or specifies whether to enable the 30-Minute monitoring function. l In RMON History Control Group of the NE, if 30-Minute is set to Disabled, Not Supported is displayed for this parameter.
B-312
Issue 02 (2011-01-20)
Parameter Custom Period 1
Default Value -
Description l This parameter indicates or specifies whether to enable the monitoring function based on Custom Period 1. l In RMON History Control Group of the NE, if Custom Period 1 is set to Disabled, Not Supported is displayed for this parameter.
Custom Period 2
Enabled Disabled
l This parameter indicates or specifies whether to enable the monitoring function based on Custom Period 2. l In RMON History Control Group of the NE, if Custom Period 2 is set to Disabled, Not Supported is displayed for this parameter.
Event Parameters
Parameter Event 30-Second Value Range Enabled Disabled 30-Minute Enabled Disabled Custom Period 1 Enabled Disabled Disabled Default Value Disabled Description This parameter indicates the performance event to be monitored. This parameter indicates or specifies whether to enable the monitoring function based on 30-Second. This parameter indicates or specifies whether to enable the 30-Minute monitoring function. This parameter indicates or specifies whether to enable the monitoring function based on Custom Period 1Custom Period 1 Monitor. This parameter indicates or specifies whether to enable the monitoring function based on Custom Period 2Custom Period 2 Monitor. l This parameter indicates or specifies the threshold detection method. l If the number of detected events reaches the preset threshold, the events are reported to the NMS. Otherwise, the events are not reported to the NMS. l If an event does not support this parameter, Not Supported is displayed.
Custom Period 2
Enabled Disabled
Disabled
Threshold Detect
Report All Do Not Detect Report Only the Upper Threshold Report Only the Lower Threshold
Report All
Issue 02 (2011-01-20)
B-313
Parameter Upper Threshold
Value Range -
Default Value -
Description This parameter indicates or specifies the upper threshold. If the number of performance events exceeds the preset upper threshold, the corresponding performance events are reported. This parameter indicates or specifies the lower threshold. If the number of performance events is less than the preset lower threshold, the corresponding performance events are reported. This parameter indicates the unit of each threshold of the performance events.
Lower Threshold
Threshold Unit
Related Tasks
A.9.2 Configuring an Alarm Group for an Ethernet Port A.9.4 Browsing the Performance Data in the History Group of an Ethernet Port
B.8 Parameters for MPLS/PWE3 Services

This topic describes parameters that are related to MPLS/PWE3 services.
NOTE
For parameters for PW-carried E-Line services, see B.6 Parameters for Ethernet Services and Ethernet Features on the Packet Plane.
B.8.1 MPLS Tunnel Parameters This topic describes parameters that are related to MPLS tunnels. B.8.2 CES Parameters This topic describes parameters that are related to CES services. B.8.3 ATM Parameters This topic describes the parameters that are related to ATM services.
B.8.1 MPLS Tunnel Parameters

This topic describes parameters that are related to MPLS tunnels. B.8.1.1 Parameter Description: Basic Configurations of MPLS Tunnels This topic describes parameters that are related to the basic configurations of MPLS tunnels. B.8.1.2 Parameter Description: Unicast Tunnel Management_Static Tunnel This topic describes parameters that are related to static tunnels. B.8.1.3 Parameter Description: Unicast Tunnel Management_Creation of Unidirectional Tunnels This topic describes parameters that are used for creating unidirectional tunnels.
B.8.1.4 Parameter Description: Unicast Tunnel Management_Creation of Bidirectional Tunnels This topic describes the parameters that are related to creating bidirectional tunnels. B.8.1.5 Parameter Description: Unicast Tunnel Management_OAM Parameters This topic describes parameters that are related to MPLS OAM. B.8.1.6 Parameter Description: Unicast Tunnel Management_FDI This topic describes FDI parameters. B.8.1.7 Parameter Description: Unicast Tunnel Management_LSP Ping This topic describes the parameters that are related to the LSP Ping test. B.8.1.8 Parameter Description: Unicast Tunnel Management_LSP Traceroute This topic describes the parameters that are related to the LSP Traceroute test. B.8.1.9 Parameter Description: PW Management_PW Management This topic describes parameters that are related to PW management. B.8.1.10 Parameter Description: PW Management_MS-PW Creation This topic describes the parameters that are related to MS-PW creation. B.8.1.11 Parameter Description: PW Management_PW OAM This topic describes parameters that are related to PW OAM. B.8.1.12 Parameter Description: PW Management_PW Ping This topic describes the parameters that are related to the PW Ping test. B.8.1.13 Parameter Description: PW Management_PW Traceroute This topic describes the parameters that are related to the PW Traceroute test. B.8.1.14 Parameter Description: MPLS APS Protection Management This topic describes parameters that are related to MPLS APS protection management. B.8.1.15 Parameter Description: Tunnel Protection Group_Creation This topic describes the parameters that are related to creating a tunnel protection group. B.8.1.16 Parameter Description: PW APS Protection Group_Creation This topic describes the parameters that are used for creating a PW APS protection group. B.8.1.17 Parameter Description: Slave Protection Pair of a PW APS Protection Group_Creation This topic describes the parameters that are used for creating a slave protection pair of a PW APS protection group.
B.8.1.1 Parameter Description: Basic Configurations of MPLS Tunnels

This topic describes parameters that are related to the basic configurations of MPLS tunnels.
Navigation Path
In the NE Explorer, select the required NE from the Object Tree and choose Configuration > MPLS Management > Basic Configuration from the Function Tree.
Issue 02 (2011-01-20)
B-315

Parameter LSR ID Value Range Default Value 0.0.0.0 Description l Specifies or displays the LSR ID of an NE. On a PSN, each NE is assigned a unique LSR ID. l This parameter must be set in IPv4 address format. Start of Global Label Space 0-1015808 0 l Specifies the start value of a global label space. The OptiX RTN 980 supports a step of 2048. l The start value of a global label space is the smallest unicast tunnel label. When Start of Global Label Space is 0, the smallest unicast tunnel label is 16, with values 0 to 15 reserved. l On an MPLS-enabled network, global label spaces of NEs are recommended to overlap each other if possible. Global Label Space Size Start of Multicast Label Space Displays the size of a global label space. The OptiX RTN 980 does not support this parameter.
Related Tasks
A.7.2.1 Setting Basic MPLS Attributes
B.8.1.2 Parameter Description: Unicast Tunnel Management_Static Tunnel

This topic describes parameters that are related to static tunnels.
B-316
Issue 02 (2011-01-20)
Navigation Path
1. In the NE Explorer, select the required NE from the Object Tree and choose Configuration > MPLS Management > Unicast Tunnel Management from the Function Tree. Click the Static Tunnel tab. Click Query.
2. 3.

Parameter ID Name Enable State Value Range Enabled Disabled Default Value Enabled Description Displays the tunnel ID. Specifies or displays the customized tunnel name. l Specifies or displays whether a tunnel is enabled.
NOTE The OptiX RTN 980 supports only the value Enabled.
Node Type
l Displays the node type. l For bidirectional tunnels, this parameter displays the node types of forward tunnels.
Direction CIR(kbit/s)
No Limit 1024-1024000
No Limit
Displays the direction of a tunnel. l Specifies or displays the committed information rate (CIR) of a tunnel. l Generally, it is recommended that you set this parameter to No Limit. If you need to enable the CES CAC function or limit the PW bandwidth, set this parameter to be the same as the planned tunnel bandwidth.
CBS(kbit/s) PIR(byte)
The OptiX RTN 980 does not support this parameter. The OptiX RTN 980 does not support this parameter.
B-317
Issue 02 (2011-01-20)
Parameter PBS(byte) Bandwidth Remaining (kbit/s) In Port
Value Range -
Default Value -
Description The OptiX RTN 980 does not support this parameter. The OptiX RTN 980 does not support this parameter. Displays the ingress port of a forward tunnel, which is also the egress port of the mapping reverse tunnel. Displays the MPLS label that a forward tunnel carries when entering a node. Specifies the MPLS label that a reverse tunnel carries when entering a tunnel. Displays the egress port of a forward tunnel, which is also the ingress port of the mapping reverse tunnel. Displays the MPLS label that a forward tunnel carries when leaving a node. Displays the MPLS label that a reverse tunnel carries when leaving a node. Displays the IP address of the next-hop port of a forward tunnel. Displays the IP address of the next-hop port of a reverse tunnel. Displays the LSR ID of the ingress node. Displays the LSR ID of the egress node. Displays the tunnel type.
Forward In Label
Reverse Out Label
Out Port
Forward Out Label
Reverse In Label
Forward Next Hop Address Reverse Next Hop Address Source Node Sink Node Tunnel Type
B-318
Issue 02 (2011-01-20)
Parameter EXP
Value Range 0-7 None
Default Value -
Description l Specifies or displays the value of the EXP field in the packets transmitted through MPLS tunnels. l For unidirectional tunnels, this parameter is available only if Node Type is Ingress. l For bidirectional tunnels, this parameter cannot be set if Node Type is Transit. l If this parameter is set to a value from 0 to 7, the EXP field takes its fixed value. l If this parameter takes its default value None, the EXP field varies based on the DiffServ mappings.
LSP Mode
Pipe
Pipe
l Displays or specifies the LSP mode. l Pipe: When stripping MPLS tunnel labels from packets, an egress node does not update the scheduling priority for the packets. l For bidirectional tunnels, this parameter is available only if Node Type is Egress. l For bidirectional tunnels, this parameter cannot be set if Node Type is Transit.
NOTE On the OptiX RTN 980, this parameter can be set to Pipe only.
MTU(byte)
Issue 02 (2011-01-20)
B-319
Parameter Protection Group
Value Range -
Default Value -
Description Displays the MPLS APS protection group to which a tunnel belongs. l Specifies or displays the VLAN ID that Ethernet packets carry when transmitted over MPLS tunnels. l If packets need to traverse a Layer 2 network, set the VLAN ID for the tunnel carried by the NNI port according to the VLAN planning requirements on the Layer 2 network. l Set this parameter to the same value for both ends of a tunnel.
VLAN ID
Deployment
Displays the deployment status of the tunnel.
Related Tasks
A.7.2.4 Querying MPLS Tunnel Information
B.8.1.3 Parameter Description: Unicast Tunnel Management_Creation of Unidirectional Tunnels

This topic describes parameters that are used for creating unidirectional tunnels.
Navigation Path
1. In the NE Explorer, select the required NE from the Object Tree and choose Configuration > MPLS Management > Unicast Tunnel Management from the Function Tree. Click the Static Tunnel tab. Click New and choose Unidirectional Tunnel from the drop-down list. The New Unicast Unidirectional Tunnel dialog box is displayed. 4. Select New Reverse Tunnel.
2. 3.
B-320
Issue 02 (2011-01-20)

Parameter Tunnel ID Value Range 1-65535 Default Value Description l Specifies the tunnel ID. l The total number of tunnels and PWs must be equal to or less than 1024. The number of tunnels that carry PWs are not included in the total. Tunnel Name Node Type Ingress Egress Transit Direction CIR(kbit/s) No Limit 1024-1024000 No Limit Indicates the direction of a tunnel. l Specifies the committed information rate (CIR) of a tunnel. l Generally, it is recommended that you set this parameter to No Limit. If you need to enable the CES CAC function or limit the PW bandwidth, set this parameter to be the same as the planned tunnel bandwidth. CBS(kbit/s) PIR(Byte) PBS(Byte) In Board/Logic Interface Type In Port The OptiX RTN 980 does not support this parameter. The OptiX RTN 980 does not support this parameter. The OptiX RTN 980 does not support this parameter. Specifies the board where the ingress port of a forward tunnel is located. Specifies the ingress port of a forward tunnel, which is also the egress port of the mapping reverse tunnel. Ingress Specifies the tunnel name. Specifies the node type of a forward tunnel.
Issue 02 (2011-01-20)
B-321
Parameter In Labela
Value Range 16-1048575
Default Value -
Description l Specifies the MPLS label that a tunnel carries when entering a node. l This parameter can be set for only egress and transit nodes.
Out Board/Logic Interface Type Out Port
Specifies the board where the egress port of a forward tunnel is located. Specifies the egress port of a forward tunnel, which is also the ingress port of the mapping reverse tunnel. l Specifies the MPLS label that a tunnel carries when leaving a node. l This parameter can be set for only ingress and transit nodes.
Out Labela
16-1048575
Next Hop Address
l Specifies the port IP address of the next-hop node for a tunnel. l This parameter can be set for only ingress and transit nodes.
Source Node
l Specifies the LSR ID of the ingress node. l This parameter can be set for only egress nodes and transit nodes.
Sink Node
l Specifies the LSR ID of the egress node. l This parameter can be set for only ingress and transit nodes.
B-322
Issue 02 (2011-01-20)
Parameter Tunnel Type
Value Range E-LSP L-LSP
Default Value E-LSP
Description l Specifies the tunnel type. l The value E-LSP indicates that the EXP field is used to identify packet scheduling priorities of PWs. An E-LSP tunnel can contain PWs of eight packet scheduling priorities. l The value L-LSP indicates that the MPLS label value is used to identify packet scheduling priorities of PWs. An L-LSP tunnel can contain PWs of the same packet scheduling priority.
EXP
0-7 None
None
l Specifies the value of the EXP field in the packets transmitted through MPLS tunnels. l This parameter is available only if Node Type is Ingress. l If this parameter is set to a value from 0 to 7, the EXP field takes its fixed value. l If this parameter takes its default value None, the EXP field varies based on the DiffServ mappings.
Issue 02 (2011-01-20)
B-323
Parameter LSP Mode
Value Range Pipe
Default Value Pipe
Description l Pipe: When stripping MPLS tunnel labels from packets, an egress node does not update the scheduling priority for the packets. l This parameter is available only if Node Type is Egress.
MTU
NOTE
At an MPLS node, in labels must be different from each other, out labels must also be different from each other, but out labels can be the same as in labels.
Related Tasks
A.7.2.2 Creating a Unidirectional MPLS Tunnel
B.8.1.4 Parameter Description: Unicast Tunnel Management_Creation of Bidirectional Tunnels

This topic describes the parameters that are related to creating bidirectional tunnels.
Navigation Path
1. In the NE Explorer, select the required NE from the Object Tree and choose Configuration > MPLS Management > Unicast Tunnel Management from the Function Tree. Click the Static Tunnel tab. Click New and choose Bidirectional Tunnel from the drop-down list.
2. 3.
B-324
Issue 02 (2011-01-20)

Parameter Tunnel ID Value Range 1 to 65535 Default Value Description l Specifies the tunnel ID. l The total number of tunnels and PWs must be equal to or less than 1024. The number of tunnels that carry PWs is not included in the total. Tunnel Name Node Type Ingress Egress Transit Direction CIR(kbit/s) No Limit 1024-1024000 No Limit Indicates the direction of a tunnel. l Specifies the committed information rate (CIR) of a tunnel. l Generally, it is recommended that you set this parameter to No Limit. If you need to enable the CES CAC function or limit the PW bandwidth, set this parameter to be the same as the planned tunnel bandwidth. CBS(kbit/s) PIR(Byte) PBS(Byte) In Board/Logic Interface Type In Port The OptiX RTN 980 does not support this parameter. The OptiX RTN 980 does not support this parameter. The OptiX RTN 980 does not support this parameter. Specifies the board where the ingress port of a forward tunnel is located. Specifies the ingress port of a forward tunnel, which is also the egress port of the mapping reverse tunnel. Ingress Specifies the tunnel name. Specifies the node type of a forward tunnel.
Issue 02 (2011-01-20)
B-325
Parameter Forward In Labela
Default Value -
Description l Specifies the MPLS label that data carries when entering a forward tunnel. l This parameter can be set for only egress and transit nodes.
Reverse Out Labela
16 to 1048575
l Specifies the MPLS label that data carries when leaving a reverse tunnel. l This parameter can be set for only ingress and transit nodes.
Out Board/Logic Interface Type Out Port
Specifies the board where the egress port of a forward tunnel is located. Specifies the egress port of a forward tunnel, which is also the ingress port of the mapping reverse tunnel. l Specifies the MPLS label that data carries when leaving a forward tunnel. l This parameter can be set for only ingress and transit nodes.
Forward Out Labela
16 to 1048575
Reverse In Labela
16 to 1048575
l Specifies the MPLS label that data carries when entering a reverse tunnel. l This parameter can be set for only egress and transit nodes.
Forward Next Hop Address
l Indicates or specifies the IP address of the next hop in a forward tunnel. l This parameter can be set for only ingress and transit nodes.
B-326
Issue 02 (2011-01-20)
Parameter Reverse Next Hop Address
Value Range -
Default Value -
Description l Indicates or specifies the IP address of the next hop in a reverse tunnel. l This parameter can be set for only egress and transit nodes.
Source Node
l Specifies the LSR ID of the ingress node. l This parameter can be set for only egress nodes and transit nodes.
Sink Node
l Specifies the LSR ID of the egress node. l This parameter can be set for only ingress and transmit nodes.
Tunnel Type
E-LSP L-LSP
E-LSP
l Specifies the tunnel type. l The value E-LSP indicates that the EXP field is used to identify packet scheduling priorities of PWs. An E-LSP tunnel can contain PWs of eight packet scheduling priorities. l The value L-LSP indicates that the MPLS label value is used to identify packet scheduling priorities of PWs. An L-LSP tunnel can contain PWs of the same packet scheduling priority.
Issue 02 (2011-01-20)
B-327
Parameter EXP
Value Range 0 to 7 None
Default Value None
Description l Specifies the value of the EXP field in the packets transmitted through MPLS tunnels. l This parameter cannot be set if Node Type is Transit. l If this parameter is set to a value from 0 to 7, the EXP field assumes the fixed value. l If this parameter takes the default value None, the EXP field is set based on the DiffServ mappings.
LSP Mode
Pipe
Pipe
l Pipe: When stripping MPLS tunnel labels from packets, an egress node does not update the scheduling priority for the packets. l This parameter cannot be set if Node Type is Transit.
MTU
NOTE
At an MPLS node, in labels must be different from each other, out labels must also be different from each other, but out labels can be the same as in labels.
Related Tasks
B.8.1.5 Parameter Description: Unicast Tunnel Management_OAM Parameters

This topic describes parameters that are related to MPLS OAM.
B-328
Issue 02 (2011-01-20)
Navigation Path
1. In the NE Explorer, select the required NE from the Object Tree and choose Configuration > MPLS Management > Unicast Tunnel Management from the Function Tree. Click the OAM Parameter tab.
2.

Parameter Tunnel ID Tunnel Name Node Type Value Range Default Value Description Displays the tunnel ID. Displays the tunnel name. l Displays the node type. l For bidirectional tunnels, this parameter displays the node types of forward tunnels. Tunnel Direction OAM Status Enabled Disabled Disabled Displays the direction of a tunnel. l Specifies or displays whether the local node can perform and respond to OAM operations. l If OAM Status is Enabled, the local NE can perform and respond to OAM operations. l If OAM Status is Disabled, the local NE cannot perform and respond to OAM operations. l If MPLS APS protection needs to be configured or a CC test needs to be performed for the tunnel, OAM Status needs to be set to Enabled.
Issue 02 (2011-01-20)
B-329
Parameter Detection Mode
Description l Specifies or displays the MPLS OAM detection mode. l Manual: During a CC test, MPLS OAM packets are sent at the interval specified by the user. l Auto-Sensing: During a CC test, MPLS OAM packets are sent at the interval for receiving MPLS OAM packets. l For a unidirectional tunnel, this parameter can be set for its egress node only. l For a bidirectional tunnel, if Detection Mode is set to Manual, you need to set the MPLS OAM detection packets to be received and transmitted. l Generally, the value Auto-Sensing is recommended.
B-330
Issue 02 (2011-01-20)
Value Range CV FFD
Default Value CV
Description l CV: The detection packets are sent at a fixed interval. l FFD: The detection packets are sent at the interval specified by the user. l For the egress node of a unidirectional tunnel, if Detection Mode is set to Manual, this parameter specifies the type of MPLS OAM detection packets to be received. l For a bidirectional tunnel, if Detection Mode is set to AutoSensing, this parameter specifies the type of MPLS OAM detection packets to be transmitted. l For a bidirectional tunnel, if Detection Mode is set to Manual, this parameter specifies the types of MPLS OAM detection packets to be received and transmitted. l The value FFD is assumed for MPLS APS and the value CV is assumed for continuous connectivity check on MPLS tunnels.
Issue 02 (2011-01-20)
B-331
Parameter Detection Packet Period (ms)
Value Range 3.3 10 20 50 100 200 500
Default Value 50
Description l Displays or specifies the OAM detection period. l This parameter is available only when Detection Packet Type is FFD. It takes its fixed value of 1000 ms when Detection Packet Type is CV. l Set this parameter to 3.3 for MPLS APS.
Reverse Tunnel
l Specifies the mapping reverse tunnel of a forward tunnel. l For a bidirectional tunnel, this parameter cannot be set.
CV/FFD Status LSP Status LSP Defect Type Disable LSP Duration (ms) LSP Defect Location
Displays whether CV/ FFD is enabled. Displays whether an LSP is available. Displays the LSP defect type. Displays the duration when an LSP is unavailable. Displays the LSR ID of a node where LSP defects are detected.
B-332
Issue 02 (2011-01-20)
Parameter SD Threshold
Value Range 0-100
Default Value 0
Description l Specifies or displays the SD threshold. When the OAM packet loss ratio is higher than the parameter value, the corresponding alarm is reported. l For a unidirectional tunnel, this parameter can be set for its egress node only. l When this parameter is set to 0, SD threshold detection is not supported.
SF Threshold
0-100
l Specifies or displays the SF threshold. When the OAM packet loss ratio is higher than the parameter value, the corresponding alarm is reported. l For a unidirectional tunnel, this parameter can be set for its egress node only. l When this parameter is set to 0, SF threshold detection is not supported. l The SD threshold is not higher than the SF threshold.
Source Node Sink Node
Displays the source node of a tunnel. Displays the sink node of a tunnel.
Related Tasks
A.7.2.6 Setting MPLS OAM Parameters
B.8.1.6 Parameter Description: Unicast Tunnel Management_FDI

This topic describes FDI parameters.
Navigation Path
1. In the NE Explorer, select the required NE from the Object Tree and choose Configuration > MPLS Management > Unicast Tunnel Management from the Function Tree. Click the FDI tab.
2.

Parameter Enable FDI Value Range Selected Not selected Default Value Selected Description l Specifies or displays whether Enable FDI is selected. l If the FDI function is enabled for a transit node, the transit node inserts an FDI packet to all LSPs that travel through the transit node when a fault occurs on the link between the ingress and transit nodes. On reception of the FDI packet, the egress node reports an alarm. In this case, if MPLS APS is configured correctly, protection switching is triggered before the egress node detects an LSP defect within a detection period. l Generally, the default parameter value is recommended.
Related Tasks
A.7.2.7 Enabling/Disabling FDI
B.8.1.7 Parameter Description: Unicast Tunnel Management_LSP Ping

This topic describes the parameters that are related to the LSP Ping test.
B-334
Issue 02 (2011-01-20)
Navigation Path
1. In the NE Explorer, select the required NE from the Object Tree and choose Configuration > MPLS Management > Unicast Tunnel Management from the Function Tree. Click the OAM Parameters tab. Select the required tunnel, click OAM Operation in the lower right corner, and choose Ping Test from the drop-down list.
2. 3.

Parameter Packet Count EXP Value Value Range 1 to 4294967295 0 to 7 Default Value 3 7 Description Specifies the number of test request packets. l Specifies the EXP value of the MPLS label in test request packets. The value 7 indicates the highest priority. l The default value is recommended. TTL 1 to 255 255 l Specifies the time-tolive (TTL) value of the MPLS label in test request packets. l The default value is recommended. Transmit Interval (10ms) 1 to 1000 100 l Specifies the interval for transmitting test request packets. l The default value is recommended. Packet Length 64 to 1400 64 l Specifies the length of test request packets. l The default value is recommended. Wait-to-Response Timeout Time(10ms) 1 to 6000 300 l Specifies the wait-toresponse timeout value. l The default value is recommended.
Issue 02 (2011-01-20)
B-335
Parameter Response Mode
Value Range IPv4 UDP Response No Response Application Control Channel
Default Value IPv4 UDP Response
Description l Specifies the response mode of test request packets. l The value No Response indicates that the test performance event is reported without sending response packets. l The value Application Control Channel indicates that response is performed through the reverse channel. l The value IPv4 UDP Response indicates that the IPv4 UDP packets encapsulating MPLS echo reply messages are sent as response packets. l The value IPv4 UDP Response is reserved for scenarios where all nodes on an LSP communicate with each other over a DCN running IP protocols. l Set this parameter based on the situation of the egress node. If the egress node supports reverse channel response, set this parameter to Application Control Channel. If the egress node does not support reverse channel response but supports DCN channel response by means of IP protocols, set this parameter to IPv4 UDP Response.
B-336
Issue 02 (2011-01-20)
Parameter
Value Range
Default Value
Description
NOTE For a unidirectional tunnel, Response Mode cannot be set to Application Control Channel.
Related Tasks
A.7.2.11 Performing an LSP Ping Test
B.8.1.8 Parameter Description: Unicast Tunnel Management_LSP Traceroute

This topic describes the parameters that are related to the LSP Traceroute test.
Navigation Path
1. In the NE Explorer, select the required NE from the Object Tree and choose Configuration > MPLS Management > Unicast Tunnel Management from the Function Tree. Click the OAM Parameters tab. Select the required tunnel, click OAM Operation in the lower right corner, and choose Traceroute Test from the drop-down list.
2. 3.

Parameter EXP Value Value Range 0 to 7 Default Value 7 Description l Specifies the EXP value of the MPLS label in test request packets. The value 7 indicates the highest priority. l The default value is recommended. TTL 1 to 255 255 l Specifies the time-tolive (TTL) value of the MPLS label in test request packets. l The default value is recommended. Packet Length 84 to 1400 84 l Specifies the length of test request packets. l The default value is recommended.
Parameter Wait-to-Response Timeout Time(10ms)
Default Value 300
Description l Specifies the wait-toresponse timeout value. l The default value is recommended.
B-338
Issue 02 (2011-01-20)
Description l Specifies the response mode of test request packets. l The value No Response indicates that the test performance event is reported without sending response packets. l The value Application Control Channel indicates that response is performed through the reverse channel. l The value IPv4 UDP Response indicates that the IPv4 UDP packets encapsulating MPLS echo reply messages are sent as response packets. l The value IPv4 UDP Response is reserved for scenarios where all nodes on an LSP communicate with each other over a DCN running IP protocols. l Set this parameter based on the situation of the egress node. If the egress node supports reverse channel response, set this parameter to Application Control Channel. If the egress node does not support reverse channel response but supports DCN channel response by means of IP protocols, set this parameter to IPv4 UDP Response.
Issue 02 (2011-01-20)
B-339
Parameter
Value Range
Default Value
Description
NOTE For a unidirectional tunnel, Response Mode cannot be set to Application Control Channel.
Related Tasks
A.7.2.12 Performing an LSP Traceroute Test
B.8.1.9 Parameter Description: PW Management_PW Management

This topic describes parameters that are related to PW management.
Navigation Path
1. 2. In the NE Explorer, select the required NE from the Object Tree and choose Configuration > MPLS Management > PW Management from the Function Tree. Click the PW Management tab.

Parameter PW ID Enable State PW Signaling Type PW Type Value Range Default Value Description Displays the ID of the PW that carries a service. Displays whether a PW is enabled. Displays the PW signaling type.
NOTE The OptiX RTN 980 uses only static PWs.
l Displays the PW type. Different PW types perform different service processing modes. l When a PW transmits E-Line services, set PW Type to Ethernet or Ethernet Tagged Mode. l If a PW transmits CES services, set PW Type to CESoPSN or SATop. l If a PW transmits ATM services, set PW Type to ATM n-to-one VCC Cell transport, ATM one-to-one VCC Cell Mode, ATM n-to-one VPC Cell transport, or ATM one-to-one VPC Cell Mode.
Direction
B-340
Displays the direction of a PW.

Issue 02 (2011-01-20)
Parameter PW Ingress Label/Source Port PW Encapsulation Type
Value Range -
Default Value -
Description Displays the ingress label at the source port of a PW. Displays the encapsulation type of the packets on a PW.
NOTE The OptiX RTN 980 supports only MPLS encapsulation.
PW Egress Label/Sink Port Opposite LSR ID Local Working Status Remote Working Status Compositive Working Status Tunnel Type
Displays the egress label at the sink port of a PW. Displays the LSR ID of the node at the other end of a PW. Displays the working status of the PW at the local end. Displays the working status of the PW at the remote end. Displays the working status of the entire PW.
Displays the type of the tunnel that carries a PW.

NOTE The OptiX RTN 980 supports only MPLS tunnels.
Tunnel Deployment Status Tunnel Automatic Selection Policy
Displays the ID of the tunnel that carries a PW. Displays the deployment status of a PW. The OptiX RTN 980 does not support this parameter.
Issue 02 (2011-01-20)
B-341
QoS Parameters
Table B-8 CES services Parameter PW ID Direction Value Range Default Value Description Displays the ID of the PW that carries the service. Displays the direction of the PW that carries the service. The OptiX RTN 980 does not support this parameter. The OptiX RTN 980 does not support this parameter.
CIR(kbit/s) EXP
Table B-9 E-Line services Parameter PW ID Direction Value Range Default Value Description Displays the ID of the PW that carries the service. Displays the direction of the PW that carries the service. Displays whether the bandwidth is limited. Displays the committed information rate (CIR) of a PW. Displays the committed burst size (CBS) of a PW. Displays the peak information rate (PIR) of a PW Displays the peak burst size (PBS) of a PW. The OptiX RTN 980 does not support this parameter. Displays the LSP mode.
NOTE The OptiX RTN 980 supports only Pipe.
Bandwidth Limit CIR(kbit/s)
CBS(byte) PIR(kbit/s)
PBS(byte) EXP LSP Mode
B-342
Issue 02 (2011-01-20)
Parameter Policy
Value Range -
Default Value -
Description The OptiX RTN 980 does not support this parameter.
Table B-10 ATM services Parameter PW ID Direction Value Range Default Value Description Displays the ID of the PW that carries the service. Displays the direction of the PW that carries the service. Displays whether the bandwidth is limited. Displays the committed information rate (CIR) of a PW. Displays the committed burst size (CBS) of a PW. Displays the peak information rate (PIR) of a PW Displays the peak burst size (PBS) of a PW. The OptiX RTN 980 does not support this parameter. The OptiX RTN 980 does not support this parameter.
Bandwidth Limit CIR(kbit/s)
CBS(byte) PIR(kbit/s)
PBS(byte) EXP Policy

Table B-11 CES services Parameter PW ID RTP Head Value Range Default Value Description Displays the PW ID. Displays whether the CES service packets carry an RTP header.
Issue 02 (2011-01-20)
B-343
Parameter Packet Loading Time (us) Jitter Compensation Buffering Time(us) Ingress Clock Mode
Value Range -
Default Value -
Description Displays the packet loading time. Displays the jitter buffer time for the received CES packets. Displays the mode for extracting clock information from CES services. The OptiX RTN 980 does not support this parameter. Displays whether CES service alarms are transparently transmitted. Displays the threshold of the packet loss ratio of CES services. The corresponding alarm will be reported if the actual packet loss ratio crosses this threshold. Displays the threshold of received CES service packets. The corresponding alarm will be cleared after the actual number of received CES service packets crosses this threshold. Displays the sequence number mode.
Egress Clock Mode Enable CES Service Alarm Transparent Transmission Threshold of Entering R bit Inserting Status
Threshold of Exiting R bit Inserting Status
Sequence Number Mode
Table B-12 E-Line services Parameter PW ID Value Range Default Value Description Displays the PW ID.
B-344
Issue 02 (2011-01-20)
Parameter Control Word
Value Range -
Default Value -
Description Displays whether the control word is used to transfer packet information. For ETH PWE3 services, this parameter is always not used. Displays the control channel type. Displays the VCCV mode. When PW Type is Ethernet Tag, this parameter displays the VLAN ID to be added to packets that are sent from the opposite end and do not carry any VLAN IDs. When PW Type is Ethernet Tag, this parameter displays the TPID.
Control Channel Type VCCV Verification Mode Request VLAN
TPID
Table B-13 ATM services Parameter PW ID Control Word Value Range Default Value Description Displays the PW ID. Displays whether the control word is used to transfer packet information. Displays the control channel type. Displays the VCCV mode. Displays the maximum number of concatenated cells. Displays the packet loading time.
Control Channel Type VCCV Verification Mode Max Concatenated Cell Count Packet Loading Time (us)
Issue 02 (2011-01-20)
B-345
Related Tasks
A.7.4.1 Querying Information and Running Status of PWs
B.8.1.10 Parameter Description: PW Management_MS-PW Creation

This topic describes the parameters that are related to MS-PW creation.
Navigation Path
1. 2. 3. In the NE Explorer, select the required NE from the Object Tree and choose Configuration > MPLS Management > PW Management from the Function Tree. Click the MS PW tab. Click New.

Parameter ID Name MTU(byte) Service Type Value Range ETH Service CES Service ATM Service Connection Type Port Transparent PVP PVC Port Transparent Default Value ETH Service Description Specifies the ID of MS-PW. Specifies the name of MS-PW. The OptiX RTN 980 does not support this parameter. l Specifies the type of services carried by the MS-PW. l Set this parameter according to the planning information. l This parameter is available only when Service Type is ATM Service. l PVP: Only the VPIs of the source and sink are exchanged. l PVP: The VPIs and VCIs of the source and sink are exchanged. l Port Transparent: ATM transparent transmission refers to the transparent transmission of ATM cells that are encapsulated into PWs as payloads.
Parameters for the Basic Attributes of PWs

Parameter PW ID Value Range Default Value Description Specifies the ID of the PW that carries services.
B-346
Issue 02 (2011-01-20)
Parameter PW Signaling Type
Value Range Static
Description Specifies the signaling type of the PW. Labels for static PWs need to be manually assigned. l Specifies the type of the PW. l Set this parameter to Ethernet if Service Type is ETH Service and no VLAN IDs need to be added. If it is required to add VLAN IDs, set this parameter to Ethernet Tag Mode and then set Request VLAN in the Advanced Attribute tab. l If Service Type is CES Service, the value CESoPSN indicates structureaware emulation, which allows timeslot compression; the value SAToP indicates structure-agnostic emulation, which does not allow timeslot compression. l If Service Type is ATM Service, set this parameter according to the value of Connection Type.
PW Type
Direction PW Encapsulation Type
Displays the direction of the PW. Displays the encapsulation type of the PW. Specifies the PW Ingress label. Specifies the PW Egress label.
PW Ingress Label/ Source Port PW Egress Label/Sink Port
16 to 1048575 16 to 1048575
Issue 02 (2011-01-20)
B-347
Parameter Tunnel Selection Mode
Value Range Manually
Default Value Manually
Description Specifies the method to select tunnels.

NOTE The OptiX RTN 980 supports only the value Manually.
Tunnel Type Tunnel
MPLS -
MPLS -
Specifies the type of the tunnel that carries the PW. A created tunnel needs to be selected. If no tunnel is available, no PW can be created. Specifies the LSR ID of the PW at the remote end. If an existing tunnel is selected, the LSR ID will be automatically assigned. For a bidirectional tunnel, the system will configure the reverse tunnel automatically.
Opposite LSR ID
Egress Tunnel
QoS Parameters CES Services

Parameter EXP Value Range Default Value Description The OptiX RTN 980 does not support this parameter.
B-348
Issue 02 (2011-01-20)
Ethernet services
Parameter Bandwidth Limit Value Range Default Value Description Specifies whether the bandwidth limit function is enabled. l This function limits the bandwidth of one or more PWs in an MPLS tunnel. l An ETH PWE3 service corresponds to a PW. Therefore, this function can also limit the bandwidth of ETH PWE3 services in an MPLS tunnel. Policy CIR(Kbit/s) The OptiX RTN 980 does not support this parameter. Specifies the committed information rate (CIR) of a PW. It is recommended that you set this parameter to the same value as PIR. CBS(byte) PIR(Kbit/s) Specifies the committed burst size (CBS) of a PW. Specifies the peak information rate (PIR) of a PW. It is recommended that you set this parameter to the same value as CIR. PBS(byte) EXP LSP Mode Pipe Pipe Specifies the peak burst size (PBS) of a PW. The OptiX RTN 980 does not support this parameter. Pipe: When stripping MPLS tunnel labels from packets, an egress node does not update the scheduling priority for the packets.
Issue 02 (2011-01-20)
B-349
ATM services
Table B-14 ATM services Parameter Bandwidth Limit Value Range Default Value Description Specifies whether the bandwidth limit is enabled. l This function can be used to limit the bandwidth of one or more PWs, or the bandwidth of one or more ATM PWE3 services, in an MPLS tunnel. (One ATM PWE3 service corresponds to one PW.) l Policy CIR (Kbit/s) The OptiX RTN 980 does not support this parameter. Specifies the committed information rate (CIR) of the PW. It is recommended that you set this parameter to the same value as PIR. CBS (kbyte) PIR (kbit/s) Specifies the excess burst size of the PW. Specifies the peak information rate (PIR) of the PW. It is recommended that you set this parameter to the same value as CIR. PBS (kbyte) Specifies the maximum excess burst size of the PW. The OptiX RTN 980 does not support this parameter.
EXP
B-350
Issue 02 (2011-01-20)
Parameters for the Advanced Attributes of PWs CES Services

Parameter RTP Header Value Range Disable Enable Default Value Disable Description l Specifies the RTP header. l The RTP header carries time stamps. l The default value is recommended. Jitter Compensation Buffering Time(us) 375 to 16000 8000 l Specifies the jitter buffer time for the received CES packets. l A greater value of this parameter means fewer impacts of transmission jitters on CES services, greater delays of CES services, and more resources occupied by CES services. l The default value is recommended.
NOTE Set Jitter Compensation Buffering Time(us) to a value greater than the value of Packet Loading Time (us) at the opposite end and the local end.
Packet Loading Time (us)
125 to 5000
1000
l Specifies the length of fragments in the TDM data stream. Each fragment is encapsulated into one PW packet. l A greater value of this parameter means higher encapsulation efficiency but greater delays of CES services. l The default value is recommended.
Issue 02 (2011-01-20)
B-351
Parameter Ingress Clock mode
Value Range Null Adaptive Clock Mode
Default Value Null
Description l Specifies the mode in which CES services extract clocks from TDM services. l The value Null indicates that no clocks are extracted. If this value is assumed, CES services do not transmit clocks. l The value Adaptive Clock Mode indicates that CES services extract clocks from TDM services. If this value is assumed, CES services transmit TDM line clocks to the downstream. l You need to determine the end of master clock. This parameter assumes the value Adaptive Clock Mode at the end of master clock and assumes the value Null at the end of slave clock.
Egress Clock mode 64K Timeslot Number
1 to 31
The OptiX RTN 980 does not support this parameter. l Specifies the number of 64 kbit/s timeslots that transmit service traffic. The value of this parameter must include 16 if Frame Mode is 30. l On the two ends of a radio link, the timeslot lists can be different but the numbers of timeslots must be the same. l This parameter is unavailable if PW Type is SAToP.
B-352
Issue 02 (2011-01-20)
Parameter Sequence Number Mode
Value Range Huawei Mode Standard Mode
Default Value Huawei Mode
Description Specifies the sequence number mode.
Ethernet services and PTP clock services

Parameter Control Word Value Range No Use Default Value No Use Description For ETH PWE3 services, the parameter value is always No Use. l Specifies the mode of PW connectivity check. l None indicates that VCCV is not used. l Alert Label indicates VCCV packets in Alert Label encapsulation mode. VCCV Verification Mode Ping None Ping l Specifies the VCCV verification mode. The VCCV verification is used for PW connectivity check. l If the VCCV-Ping test is required, set this parameter to Ping. Request VLAN l Set this parameter when PW Type is Ethernet Tagged Mode. l If the received packets do not carry any VLAN IDs, the PW will add VLAN IDs to the packets as required by the setting of this parameter. TPID The OptiX RTN 980 does not support request VLAN TPID of the PW level.
None Alert Label
Alert Label
Issue 02 (2011-01-20)
B-353
ATM services
Parameter Control Word Value Range Must Use No Use Default Value Must Use Description l Specifies whether to use the control word. In the MPLS packet switching network, the control word is used to transmit packet information. l Set Control Word to Must Use if PW Type is ATM 1:1. Control Channel Type CW None Alert Label CW l Specifies the mode of PW connectivity check. l The value None indicates that the control word is not supported. That is, the PW connectivity check is not supported. l The value CW indicates that the control word is supported. l The value Alert Label indicates VCCV packets in Alert Label encapsulation mode. VCCV Verification Mode Ping None Ping l Specifies the VCCV verification mode. The VCCV verification is used for PW connectivity check. l If the VCCV-Ping test is required, set this parameter to Ping.
B-354
Issue 02 (2011-01-20)
Parameter Max. Concatenated Cell Count
Value Range 1 to 31
Default Value 10
Description l Specifies the maximum number of concatenated cells. l If the value 1 is assumed, only one ATM cell is encapsulated in one packet. If the value from 2 to 31 is assumed, a maximum of 2 to 31 ATM cells are encapsulated into one packet.
100 to 50000
1000
l Specifies the packet loading time. Once the packet loading time expires, the packet is sent out even if the concatenated cells are less than the maximum. l If Max. Concatenated Cell Count assumes the value 1, this parameter is ineffective. That is, the packet will be sent out once the cell is loaded.
Related Tasks
A.7.4.2 Creating an MS-PW
B.8.1.11 Parameter Description: PW Management_PW OAM

This topic describes parameters that are related to PW OAM.
Navigation Path
1. 2. In the NE Explorer, select the required NE from the Object Tree and choose Configuration > MPLS Management > PW Management from the Function Tree. Click the PW OAM Parameter tab.
Issue 02 (2011-01-20)
B-355

Parameter PW ID PW Type Value Range Default Value Description Displays the ID of the PW that carries the service. Displays the type of the PW that carries the service. l Specifies or displays whether the local node can perform and respond to OAM operations. l If OAM Status is Enabled, the local NE can perform and respond to OAM operations. l If OAM Status is Disabled, the local NE cannot perform and respond to OAM operations. l If PW APS protection needs to be configured or a CC test needs to be performed for the tunnel, OAM Status needs to be set to Enabled. Associate AC State The OptiX RTN 980 does not support this parameter.
OAM Status
Enabled Disabled
Disabled
B-356
Issue 02 (2011-01-20)
Description l Specifies or displays the detection mode for PW OAM packets. l Manual: During a CC test, PW OAM packets are sent at the interval specified by the user. l Auto-Sensing: During a CC test, PW OAM packets are sent at the interval for receiving PW OAM packets. l If Detection Mode is set to Manual, you need to set the type of PW OAM detection packets to be received and transmitted. l The value AutoSensing is recommended.
Issue 02 (2011-01-20)
B-357
Value Range CV FFD
Default Value CV
Description l CV: The detection packets are sent at a fixed interval. l FFD: The detection packets are sent at the interval specified by the user. l If Detection Mode is set to Auto-Sensing, this parameter specifies the type of PW OAM detection packets to be transmitted. l If Detection Mode is set to Manual, this parameter specifies the type of PW OAM detection packets to be received and transmitted. l The value FFD is assumed for PW APS and the value CV is assumed for continuous connectivity check on PWs.
3.3 10 20 50 100 200 500
50
l Displays or specifies the OAM detection period. l If Detection Packet Type is FFD, this parameter can be set; if Detection Packet Type is CV, the value is always 1000. l Set this parameter to 3.3 for PW APS.
B-358
Issue 02 (2011-01-20)
Parameter SD Threshold (%)
Value Range 0-100
Default Value 0
Description l Specifies or displays the SD threshold. When the OAM packet loss ratio is higher than the parameter value, the corresponding alarm is reported. l When this parameter is set to 0, SD threshold detection is not supported.
SF Threshold (%)
0-100
l Specifies or displays the SF threshold. When the OAM packet loss ratio is higher than the parameter value, the corresponding alarm is reported. l When this parameter is set to 0, SF threshold detection is not supported. l The SD threshold is not higher than the SF threshold.
LSR ID to Be Received
l Specifies or displays the LSR ID to be received. l This parameter is available only if OAM Status is Disabled.
PW ID to be Received
l Specifies or displays the PW ID to be received. l This parameter is available only if OAM Status is Disabled.
Local Working Status Local PW Defect Type Local Disable PW Duration(ms)
Displays whether PWs at the local end are available. Displays the local PW defect type. Displays the duration when the local PW is unavailable.
Issue 02 (2011-01-20)
B-359
Parameter Local PW Defect Location Remote Working Status
Value Range -
Default Value -
Description Displays the local PW defect location. Displays whether PWs at the remote end are available. Displays the remote PW defect type. Displays the duration when the remote PW is unavailable. Displays the remote PW defect location.
Remote PW Defect Type Remote Disable PW Duration(ms) Remote PW Defect Location
Related Tasks
B.8.1.12 Parameter Description: PW Management_PW Ping

This topic describes the parameters that are related to the PW Ping test.
Navigation Path
1. 2. 3. In the NE Explorer, select the required NE from the Object Tree and choose Configuration > MPLS Management > PW Management from the Function Tree. Click the PW OAM Parameter tab. Select the required PW and click OAM Operation > Ping Test.

Parameter Packet Count EXP Value Value Range 1 to 4294967295 0 to 7 Default Value 3 7 Description Specifies the number of test request packets. l Specifies the EXP value of the PW label in test request packets. The value 7 indicates the highest priority. l The default value is recommended.
B-360
Issue 02 (2011-01-20)
Parameter TTL
Default Value 255
Description l Specifies the time-tolive (TTL) value of the PW label in test request packets. l The default value is recommended.
Transmit Interval (10ms)
1 to 1000
100
l Specifies the interval for transmitting test request packets. l The default value is recommended.
Packet Length
64 to 1400
64
l Specifies the length of test request packets. l The default value is recommended.
Wait-to-Response Timeout Time(10ms)
1 to 6000
300
l Specifies the wait-toresponse timeout value. l The default value is recommended.
Issue 02 (2011-01-20)
B-361
Description l Specifies the response mode of test request packets. l The value No Response indicates that the test performance event is reported without sending response packets. l The value Application Control Channel indicates that response is performed through the reverse channel. l The value IPv4 UDP indicates that the IPv4 UDP packets encapsulating MPLS echo reply messages are sent as response packets. l The value IPv4 UDP is reserved for scenarios where all nodes on an LSP communicate with each other over a DCN running IP protocols. l Set this parameter based on the situation of the remote PE. If the remote PE supports reverse channel response, set this parameter to Application Control Channel. If the remote PE does not support reverse channel response but supports DCN channel response by means of IP protocols, set this parameter to IPv4 UDP Response.
B-362
Issue 02 (2011-01-20)
Parameter Control Channel Type
Value Range Control Word Alert Label
Default Value -
Description Specifies the control channel type.

NOTE ETH-PWE3 services do not support Control Word.
Peer PW ID Peer IP
Specifies the PW ID of the peer end. Specifies the IP address of the peer port.
Related Tasks
A.7.4.4 Performing a PW Ping Test
B.8.1.13 Parameter Description: PW Management_PW Traceroute

This topic describes the parameters that are related to the PW Traceroute test.
Navigation Path
1. 2. 3. In the NE Explorer, select the required NE from the Object Tree and choose Configuration > MPLS Management > PW Management from the Function Tree. Click the PW OAM Parameter tab. Select the required PW, click OAM Operation in the lower right corner, and choose Traceroute Test from the drop-down list.

Parameter EXP Value Value Range 0 to 7 Default Value 7 Description l Specifies the EXP value of the PW label in test request packets. The value 7 indicates the highest priority. l The default value is recommended. TTL 1 to 255 255 l Specifies the time-tolive (TTL) value of the PW label in test request packets. l The default value is recommended.
Issue 02 (2011-01-20)
B-363
Parameter Packet Length
Default Value 84
Description l Specifies the length of test request packets. l The default value is recommended.
Wait-to-Response Timeout Time(10ms)
1 to 6000
300
l Specifies the wait-toresponse timeout value. l The default value is recommended.
B-364
Issue 02 (2011-01-20)
Description l Specifies the response mode of test request packets. l The value No Response indicates that the test performance event is reported without sending response packets. l The value Application Control Channel indicates that response is performed through the reverse channel. l The value IPv4 UDP indicates that the IPv4 UDP packets encapsulating MPLS echo reply messages are sent as response packets. l The value IPv4 UDP is reserved for scenarios where all nodes on an LSP communicate with each other over a DCN running IP protocols. l Set this parameter based on the situation of the remote PE. If the remote PE supports reverse channel response, set this parameter to Application Control Channel. If the remote PE does not support reverse channel response but supports DCN channel response by means of IP protocols, set this parameter to IPv4 UDP Response.
Issue 02 (2011-01-20)
B-365
Related Tasks
A.7.4.5 Performing a PW Traceroute Test
B.8.1.14 Parameter Description: MPLS APS Protection Management

This topic describes parameters that are related to MPLS APS protection management.
Navigation Path
1. 2. In the NE Explorer, select the required NE from the Object Tree and choose Configuration > APS Protection Management from the Function Tree. Click the Tunnel APS Management tab.

Parameter Protection Group ID Value Range Default Value Description l Displays the protection group ID. l The system automatically assigns IDs to the protection groups according to their creation sequence. Protection Type Switching Mode Dual-Ended Single-Ended Displays the protection group type. l Displays or specifies the switching mode of a protection group. l The value Single-End indicates that services are switched only in the direction where faults occur. l The value Dual-End indicates that services in both positive and reverse directions are switched to their protection channels when faults occur. l It is recommended that you set this parameter to Dual-Ended.
B-366
Issue 02 (2011-01-20)
Parameter BDI Status
Default Value -
Description l Specifies or displays whether the protection switching is triggered upon receiving BDI packets. l This parameter is available only when Switching Mode is set to Single-End. l If BDI Status is set to Enabled, the egress node notifies the ingress node of any detected faults by sending BDI packets; upon receiving BDI packets, the ingress node triggers protection switching.
Transmit and receive Status of Protocol Packet Revertive Mode
Displays the protocol packet status. l Specifies or displays whether to switch services to the original working tunnel after the fault is rectified. l The value Revertive indicates to perform the switching; the value Non-Revertive indicates not to perform the switching. l It is recommended that you set this parameter to Revertive.
Issue 02 (2011-01-20)
B-367
Parameter WTR Time(min)
Value Range 1-12
Default Value -
Description l Specifies and displays the WTR time of the protection group. l When the preset WTR time expires after the original working tunnel recovers, services are switched to the original working tunnel. l This parameter is available only when Revertive Mode is Revertive. l It is recommended that you set this parameter to 5.
Hold-Time(100ms)
0-100
l Specifies the hold-off time of the protection group. l If this parameter is set to a value other than 0, the protection group does not trigger switching once it detects faults, but wait until the hold-off time expires, and then detect whether any faults persist. If any faults persist, the switching is triggered; otherwise, no switching is triggered. l It is recommended that you set this parameter to 0.
Protocol Status Switching Status
Displays the protocol status. Displays the switching status of the protection group. Displays the deployment status of the protection group.
Deployment Status
B-368
Issue 02 (2011-01-20)
Parameter Unit
Value Range -
Default Value -
Description Displays whether a tunnel is a working or protection tunnel. Displays the currently used tunnel. Displays the tunnel status. Displays the tunnel type. Displays the direction of a tunnel. Displays the ingress tunnel. Displays the egress tunnel.
Active Tunnel Tunnel Status Tunnel Type Tunnel Direction Ingress Tunnel Egress Tunnel
Related Tasks
A.7.3.2 Querying MPLS APS Status
B.8.1.15 Parameter Description: Tunnel Protection Group_Creation

This topic describes the parameters that are related to creating a tunnel protection group.
Navigation Path
1. 2. 3. In the NE Explorer, select the NE from the Object Tree and choose Configuration > APS Protection Management from the Function Tree. Click the Tunnel APS Management tab. Click New.

Parameter Protection Type Value Range 1:1 Default Value 1:1 Description Specifies the protection type of the tunnel protection group.
NOTE The OptiX RTN 980 supports only the value 1:1.
Issue 02 (2011-01-20)
B-369
Parameter Switching Mode
Value Range Single-End Dual-End
Default Value Dual-End
Description l Specifies the switching mode to be adopted when a tunnel fails. l The value Single-End indicates that services are switched only in the direction where faults occur. l The value Dual-End indicates that services are switched to the protection channel in both directions when faults occur. l The value Dual-End is recommended.
BDI Status
Enabled Disabled
Disabled
l Specifies whether the protection switching is triggered upon receiving BDI packets. l This parameter is available only when Switching Mode is set to Single-End. l If BDI Status is set to Enabled, the egress node notifies the ingress node of any detected faults by sending BDI packets; upon receiving BDI packets, the ingress node triggers the protection switching.
Working Tunnel Type
MPLS Tunnel
MPLS Tunnel
Specifies the type of the working tunnel.

NOTE The OptiX RTN 980 supports only the value MPLS Tunnel.
B-370
Issue 02 (2011-01-20)
Parameter Working Ingress Tunnel ID
Value Range -
Default Value -
Description l Specifies the working tunnel of the protection group in the ingress direction. l If this parameter is set for a bidirectional tunnel, a value is automatically assigned to the parameter Working Egress Tunnel ID.
Working Ingress Tunnel Name Working Egress Tunnel ID
Displays the name of the working tunnel in the ingress direction. l Specifies the working tunnel of the protection group in the egress direction. l For a bidirectional tunnel, if the parameter Working Ingress Tunnel ID is set, a value is automatically assigned to the parameter Working Egress Tunnel ID.
Working Egress Tunnel Name Protection Tunnel Type
Displays the name of the working tunnel in the egress direction. Displays the type of protection tunnel, which is the same as the type of working tunnel. l Specifies the working tunnel of the protection group in the ingress direction. l If this parameter is set for a bidirectional tunnel, a value is automatically assigned to the parameter Protection Egress Tunnel ID.
Protection Ingress Tunnel ID
Issue 02 (2011-01-20)
B-371
Parameter Protection Ingress Tunnel Name Protection Egress Tunnel ID
Value Range -
Default Value -
Description Displays the name of the protection tunnel in the ingress direction. l Specifies the protection tunnel of the protection group in the egress direction. l For a bidirectional tunnel, if the parameter Protection Ingress Tunnel ID is set, a value is automatically assigned to the parameter Protection Egress Tunnel ID.
Protection Egress Tunnel Name Revertive Mode
Displays the name of the protection tunnel in the egress direction. l This parameter specifies whether to switch services back to the original working tunnel after it recovers. l The value Revertive indicates to switch services back to the original working tunnel after it recovers; the value NonRevertive indicates not to switch services back to the original working tunnel after it recovers. l The value Revertive is recommended.
Non-Revertive
B-372
Issue 02 (2011-01-20)
Parameter WTR Time(min)
Value Range 1 to 12
Default Value 5
Description l Specifies the WTR time of the protection group. l When the preset WTR time expires after the original working tunnel recovers, services are switched to the original working tunnel. l This parameter is available only when Restoration Mode is Revertive. l The default value is recommended.
Hold-Time(100ms)
0 to 100
Protocol Status
Disabled Enabled
Disabled
l Specifies the protocol status. l During the creation of a protection group, set Protocol Status to Disabled. After the APS protection group is configured at both ends, set Protocol Status to Enabled.
Issue 02 (2011-01-20)
B-373
Related Tasks
A.7.3.1 Creating an MPLS APS Protection Group
B.8.1.16 Parameter Description: PW APS Protection Group_Creation

This topic describes the parameters that are used for creating a PW APS protection group.
Navigation Path
The navigation path for CES services is as follows: 1. 2. 3. 4. In the NE Explorer, select the NE from the Object Tree and choose Configuration > CES Service Management from the Function Tree. Click the Protection Group tab. Click the PW APS tab. Click New.
The navigation path for E-Line services is as follows: 1. 2. 3. 4. Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Ethernet Service Management > E-Line Service from the Function Tree. Click the Protection Group tab. Click the PW APS tab. Click New.
The navigation path for ATM services is as follows: 1. 2. 3. 4. In the NE Explorer, select the NE from the Object Tree and choose Configuration > ATM Service Management from the Function Tree. Click the Protection Group tab. Click the PW APS tab. Click New.

Parameter PW ID PW Signaling Type Value Range Static Default Value Static Description Specifies the ID of the PW that carries services. Specifies the signaling type of the PW. Labels for static PWs need to be manually assigned. Displays the PW type. Displays the direction of the PW.
PW Type Direction
B-374
Issue 02 (2011-01-20)
Value Range -
Default Value -
Description Displays the encapsulation type of the PW. Specifies the PW Ingress label. Specifies the PW Egress label. Displays the method to select tunnels. Displays the type of the tunnel that carries the PW. A tunnel needs to be selected. If no tunnel is available, creation of a PW will fail. Specifies the LSR ID of the PW at the remote end. If an existing tunnel is selected, the LSR ID will be automatically assigned. For a bidirectional tunnel, the system will configure the reverse tunnel automatically.
16 to 1048575 16 to 1048575 MPLS -
MPLS -
Opposite LSR ID
Egress Tunnel
QoS Parameters
Table B-15 CES services Parameter EXP Value Range Default Value Description The OptiX RTN 980 does not support this parameter.
Issue 02 (2011-01-20)
B-375
Table B-16 E-Line services Parameter Bandwidth Limit Value Range Disabled Enabled Default Value Description Specifies whether the bandwidth limit function is enabled. l This function limits the bandwidth of one or more PWs in an MPLS tunnel. l An ETH PWE3 service corresponds to a PW. Therefore, this function can also limit the bandwidth of ETH PWE3 services in an MPLS tunnel. Policy CIR(kbit/s) The OptiX RTN 980 does not support this parameter. Specifies the committed information rate (CIR) of a PW. It is recommended that you set this parameter to the same value as PIR. CBS(byte) PIR(kbit/s) Specifies the committed burst size (CBS) of a PW. Specifies the peak information rate (PIR) of a PW. It is recommended that you set this parameter to the same value as CIR. PBS(byte) EXP LSP Mode Specifies the peak burst size (PBS) of a PW. The OptiX RTN 980 does not support this parameter. Displays the LSP mode.
B-376
Issue 02 (2011-01-20)
Table B-17 ATM services Parameter Bandwidth Limit Value Range Disabled Enabled Default Value Description Specifies whether the bandwidth limit function is enabled. l This function limits the bandwidth of one or more PWs in an MPLS tunnel. l An ATM PWE3 service corresponds to a PW. Therefore, this function can also limit the bandwidth of ATM PWE3 services in an MPLS tunnel. CIR(kbit/s) Specifies the committed information rate (CIR) of a PW. It is recommended that you set this parameter to the same value as PIR. CBS(byte) PIR(kbit/s) Specifies the committed burst size (CBS) of a PW. Specifies the peak information rate (PIR) of a PW. It is recommended that you set this parameter to the same value as CIR. PBS(byte) EXP Policy Specifies the peak burst size (PBS) of a PW. The OptiX RTN 980 does not support this parameter. The OptiX RTN 980 does not support this parameter.
Issue 02 (2011-01-20)
B-377

Table B-18 CES services Parameter RTP Head Value Range Default Value Description Displays whether the CES service packets carry an RTP header. Displays the packet loading time. Displays the jitter buffer time for the received CES packets. Displays the mode for extracting clock information from CES services. The OptiX RTN 980 does not support this parameter. Displays whether CES service alarms are transparently transmitted. Displays the threshold of the packet loss ratio of CES services. The corresponding alarm will be reported if the actual packet loss ratio crosses this threshold. Displays the threshold of received CES service packets. The corresponding alarm will be cleared after the actual number of received CES service packets crosses this threshold. Displays the sequence number mode.
Packet Loading Time (us) Jitter Compensation Buffering Time(us) Ingress Clock Mode
B-378
Issue 02 (2011-01-20)
Table B-19 E-Line services Parameter Control Word Value Range Default Value Description Displays whether the control word is used to transfer packet information. For ETH PWE3 services, this parameter is always not used. Displays the control channel type. Displays the VCCV mode. When PW Type is Ethernet Tag, this parameter displays the VLAN ID to be added to packets that are sent from the opposite end and do not carry any VLAN IDs. The OptiX RTN 980 does not support VLAN TPID of the PW level.
TPID
Table B-20 ATM services Parameter Control Word Value Range Default Value Description Displays whether the control word is used to transfer packet information. Displays the control channel type. Displays the VCCV mode. Displays the maximum number of concatenated cells. Displays the packet loading time.
Issue 02 (2011-01-20)
B-379

Parameter Protection Type Protection Group ID Enabling Status Value Range Disabled Enabled Default Value Disabled Description Specifies the protection type. Specifies the protection group ID. l Specifies the enabling status of the PW protection group. l During the creation of a protection group, set Enabling Status to Disabled. After the APS protection group is configured at both ends, set Enabling Status to Enabled. Protection Mode Working PW ID Protection PW ID Switching Mode Displays the protection mode. Displays the ID of the working PW. Displays the ID of the protection PW. Displays the switching mode to be used when a PW fails.
Revertive Mode
Revertive
B-380
Issue 02 (2011-01-20)
Value Range 1 to 12
Default Value 1
0 to 100
Detection mode
OAM Parameters
Parameter OAM Status Value Range Default Value Description Displays the enabling status of PW OAM.
Issue 02 (2011-01-20)
B-381
Description l Specifies the detection mode of OAM packets. l Manual: The connectivity check (CC) packets are sent at the interval specified by the user. l Auto-Sensing: The connectivity check (CC) packets are sent at the interval of receiving PW OAM packets. l If Detection Mode is set to Manual, you need to set the PW OAM detection packets to be received and transmitted. l The value AutoSensing is recommended.
B-382
Issue 02 (2011-01-20)
Value Range CV FFD
Default Value CV
3.3 10 20 50 100 200 500
50
Related Tasks
A.7.5.1 Creating a PW APS Protection Group
B.8.1.17 Parameter Description: Slave Protection Pair of a PW APS Protection Group_Creation

This topic describes the parameters that are used for creating a slave protection pair of a PW APS protection group.
Navigation Path
The navigation path for CES services is as follows: 1. 2. 3. 4. In the NE Explorer, select the NE from the Object Tree and choose Configuration > CES Service Management from the Function Tree. Click the Protection Group tab. Click the Slave Protection Pair tab. Click New.
The navigation path for E-Line services is as follows: 1. 2. 3. 4. Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Ethernet Service Management > E-Line Service from the Function Tree. Click the Protection Group tab. Click the Slave Protection Pair tab. Click New.
The navigation path for ATM services is as follows: 1. 2. 3. 4. In the NE Explorer, select the NE from the Object Tree and choose Configuration > ATM Service Management from the Function Tree. Click the Protection Group tab. Click the Slave Protection Pair tab. Click New.

Parameter PW ID PW Signaling Type Value Range Static Default Value Static Description Specifies the ID of the PW that carries services. Specifies the signaling type of the PW. Labels for static PWs need to be manually assigned. Displays the PW type. Displays the direction of the PW. Displays the encapsulation type of the PW.
Issue 02 (2011-01-20)
PW Type Direction PW Encapsulation Type
B-384
Parameter PW Ingress Label/ Source Port PW Egress Label/Sink Port Tunnel selection mode Tunnel Type Tunnel
Value Range 16 to 1048575 16 to 1048575 MPLS -
Default Value MPLS -
Description Specifies the PW Ingress label. Specifies the PW Egress label. Displays the method to select tunnels. Displays the type of the tunnel that carries the PW. A tunnel needs to be selected. If no tunnel is available, creation of a PW will fail. Specifies the LSR ID of the PW at the remote end. If an existing tunnel is selected, the LSR ID will be automatically assigned. For a bidirectional tunnel, the system will configure the reverse tunnel automatically.
Opposite LSR ID
Egress Tunnel
QoS Parameters
Table B-21 CES services Parameter EXP Value Range Default Value Description The OptiX RTN 980 does not support this parameter.
Issue 02 (2011-01-20)
B-385
Table B-22 E-Line services Parameter Bandwidth Limit Value Range Disabled Enabled Default Value Description Specifies whether the bandwidth limit function is enabled. l This function limits the bandwidth of one or more PWs in an MPLS tunnel. l An ETH PWE3 service corresponds to a PW. Therefore, this function can also limit the bandwidth of ETH PWE3 services in an MPLS tunnel. Policy CIR(kbit/s) The OptiX RTN 980 does not support this parameter. Specifies the committed information rate (CIR) of a PW. It is recommended that you set this parameter to the same value as PIR. CBS(byte) PIR(kbit/s) Specifies the committed burst size (CBS) of a PW. Specifies the peak information rate (PIR) of a PW. It is recommended that you set this parameter to the same value as CIR. PBS(byte) EXP LSP Mode Specifies the peak burst size (PBS) of a PW. The OptiX RTN 980 does not support this parameter. Displays the LSP mode.
B-386
Issue 02 (2011-01-20)
Table B-23 ATM services Parameter Bandwidth Limit Value Range Disabled Enabled Default Value Description Specifies whether the bandwidth limit function is enabled. l This function limits the bandwidth of one or more PWs in an MPLS tunnel. l An ATM PWE3 service corresponds to a PW. Therefore, this function can also limit the bandwidth of ATM PWE3 services in an MPLS tunnel. CIR(kbit/s) Specifies the committed information rate (CIR) of a PW. It is recommended that you set this parameter to the same value as PIR. CBS(byte) PIR(kbit/s) Specifies the committed burst size (CBS) of a PW. Specifies the peak information rate (PIR) of a PW. It is recommended that you set this parameter to the same value as CIR. PBS(byte) EXP Policy Specifies the peak burst size (PBS) of a PW. The OptiX RTN 980 does not support this parameter. The OptiX RTN 980 does not support this parameter.
Issue 02 (2011-01-20)
B-387

Table B-24 CES services Parameter RTP Head Value Range Default Value Description Displays whether the CES service packets carry an RTP header. Displays the packet loading time. Displays the jitter buffer time for the received CES packets. Displays the mode for extracting clock information from CES services. The OptiX RTN 980 does not support this parameter. Displays whether CES service alarms are transparently transmitted. Displays the threshold of the packet loss ratio of CES services. The corresponding alarm will be reported if the actual packet loss ratio crosses this threshold. Displays the threshold of received CES service packets. The corresponding alarm will be cleared after the actual number of received CES service packets crosses this threshold. Displays the sequence number mode.
Packet Loading Time (us) Jitter Compensation Buffering Time(us) Ingress Clock Mode
B-388
Issue 02 (2011-01-20)
Table B-25 E-Line services Parameter Control Word Value Range Default Value Description Displays whether the control word is used to transfer packet information. For ETH PWE3 services, this parameter is always not used. Displays the control channel type. Displays the VCCV mode. When PW Type is Ethernet Tag, this parameter displays the VLAN ID to be added to packets that are sent from the opposite end and do not carry any VLAN IDs. The OptiX RTN 980 does not support VLAN TPID of the PW level.
TPID
Table B-26 ATM services Parameter Control Word Value Range Default Value Description Displays whether the control word is used to transfer packet information. Displays the control channel type. Displays the VCCV mode. Displays the maximum number of concatenated cells. Displays the packet loading time.
Issue 02 (2011-01-20)
B-389

Parameter Protection Mode Protection Group ID Value Range Default Value Description Displays the protection mode. Specifies the ID of the slave protection pair. The switching of the master PW APS protection group triggers the switching of the slave PW APS protection group simultaneously. Displays the ID of the working PW in the slave protection pair. Displays the ID of the protection PW in the slave protection pair.
Working PW ID
Protection PW ID
Related Tasks
A.7.5.2 Configuring Slave Protection Pairs of PW APS
B.8.2 CES Parameters

This topic describes parameters that are related to CES services. B.8.2.1 Parameter Description: CES Service Management This topic describes the parameters that are related to CES service management. B.8.2.2 Parameter Description: CES Service Management_Creation This topic describes the parameters that are related to creating CES services.

This topic describes the parameters that are related to CES service management.
Navigation Path
In the NE Explorer, select the NE from the Object Tree and choose Configuration > CES Service Management from the Function Tree.
B-390
Issue 02 (2011-01-20)

Parameter Service ID Service name Level Source Board Source High Channel Value Range Default Value Description Displays the ID of the CES service to be created. Displays or specifies the service name. Displays the level of the received TDM frames. Displays the source board of the CES service. For the OptiX RTN 980, this parameter cannot be configured. Displays the source lower order path. Displays the source 64 kbit/s timeslot.
Source Low Channel Source 64K Timeslot
Issue 02 (2011-01-20)
B-391
Parameter Priority List
Default Value -
Description l Specifies the priority of a CES service. This parameter is available only when Mode is set to UNI-UNI. l This parameter needs to be configured if QoS processing needs to be performed for different CES services. l CS6-CS7: indicate the highest service classes, which are mainly involved in signaling transmission. l EF: indicates the expedited forwarding of service, which is applicable to services of low transmission delay and low packet loss rate, for example, voice and video services. l AF1-AF4: indicate the assured forwarding classes of service, which are applicable to services that require an assured rate but no delay or jitter limit. l BE: is applicable to services that need not be processed in a special manner. l The default value is recommended.
PW ID
Displays the ID of the PW that carries the CES service. This parameter is meaningful when the CES service type is UNI-NNI.
B-392
Issue 02 (2011-01-20)
Parameter Tunnel
Value Range -
Default Value -
Description Displays the tunnel that carries the PW. The tunnel must have been configured in advance. This parameter is meaningful when the CES service type is UNI-NNI. Displays the sink board of the CES service. This parameter is meaningful when the CES service type is UNI-UNI. For the OptiX RTN 980, this parameter cannot be configured. Displays the sink lower order path. This parameter is meaningful when the CES service type is UNIUNI. Displays the sink 64 kbit/s timeslot. This parameter is meaningful when the CES service type is UNI-UNI. Displays the deployment status of the CES service.
Sink Board
Sink High Channel
Sink Low Channel
Sink 64K Timeslot
Deployment Status

Parameter PW ID Value Range Default Value Description Displays the ID of the PW that carries the CES service. Displays working status of the PW. Displays the enabling status of the PW. Displays the PW signaling type.
NOTE The OptiX RTN 980 supports static PWs only.
Working Status Enable State PW Signaling Type
Issue 02 (2011-01-20)
B-393
Parameter PW Type
Value Range -
Default Value -
Description Displays the PW type for CES service encapsulation. CESoPSN: Indicates structure-aware TDM circuit emulation service over packet switched network. Timeslot compression can be set. SAToP: Indicates structure-agnostic TDM over packet. Timeslot compression cannot be set. Displays the tunnel type for PW encapsulation.
NOTE The OptiX RTN 980 supports MPLS only.
PW Encapsulation Type
PW Ingress Label/ Source Port PW Egress Label/Sink Port Opposite LSR ID Local Working Status
Displays the Ingress label of the PW that carries the CES service. Displays the Egress label of the PW that carries the CES service. Displays the LSR ID of the PW at the remote end. Displays the working status of the PW at the local end. Displays the working status of the PW at the remote end. Displays the compositive working status of the PW. The compositive working status is up when both ends are up, and is down when one end is down. Displays the type of the tunnel that carries the PW.
NOTE The OptiX RTN 980 supports MPLS tunnels only.
Remote Working Status
Compositive Working Status
Tunnel type
B-394
Issue 02 (2011-01-20)
Parameter Tunnel
Value Range -
Default Value -
Description Displays the ID of the tunnel that carries the CES service. Displays the deployment status of the tunnel. The OptiX RTN 980 does not support this parameter.
Deployment Status Tunnel Automatic Selection Policy
QoS Parameters
Parameter PW ID Direction CIR(kbit/s) EXP Value Range Default Value Description Displays the PW ID. Displays the direction of the PW. The OptiX RTN 980 does not support this parameter. The OptiX RTN 980 does not support this parameter.

Parameter PW ID RTP Header Value Range Default Value Description Displays the PW ID. Displays the RTP header. The RTP header carries time stamps. l Displays or specifies the jitter buffer time. l The jitter buffer time guarantees the realtime performance of the CES service.
Jitter Compensation Buffering Time(us)
375 to 16000
Issue 02 (2011-01-20)
B-395
Parameter Packet Loading Time (us) Ingress Clock Mode
Value Range -
Default Value -
Description Displays the packet loading time. Displays the mode in which the CES service extracts the clock signal. This mode ensures that the CES service can be correctly recovered on the sink NE. The OptiX RTN 980 does not support this parameter. Displays the mode of PW connectivity check. Displays the VCCV verification mode. The VCCV verification is used for PW connectivity check. Displays or specifies the enabling status of the transparent transmission of CES service alarms. If this function is enabled, the fault on the AC side of the CES service is notified to the remote end. Upon receiving the fault notification from the network side or the remote end, the local NE inserts the corresponding alarm to the AC side. Displays or specifies the threshold of packet loss ratio of CES services. The corresponding alarm will be reported once the actual packet loss ratio crosses this threshold. This parameter is available only when the transparent transmission of CES service alarms is enabled.
Egress Clock Mode Control Channel Type VCCV Verification Mode
Enable CES Service Alarm Transparent Transmission
Enabled Disabled
Threshold of Entering R Bit Inserting Status
1-65535
B-396
Issue 02 (2011-01-20)
Parameter Threshold of Exiting R Bit Inserting Status
Value Range 1-65535
Default Value -
Description Displays or specifies the threshold of received CES service packets. The corresponding alarm will be cleared after the actual number of received CES service packets crosses this threshold. This parameter is available only when the transparent transmission of CES service alarms is enabled. Specifies the sequence number mode. The Sequence Number Mode must be set to the same value at both ends of a radio link.
Huawei Mode Standard Mode

NOTE
Value Range -
Default Value -
Description Displays the ID of the protection group to be created. Displays the ID of the working PW. Displays the ID of the protection PW. Displays the protection mode.
Working PW ID Protection PW ID Protection Mode
Issue 02 (2011-01-20)
B-397
Parameter Enabling Status
Default Value -
Description l Displays or specifies the enabling status of the PW protection group. l During the creation of a protection group, set Enabling Status to Disabled. After the APS protection group is configured at both ends, set Enabling Status to Enabled.
Switchover Mode
Displays the switching mode to be used when a PW fails.

Restoration Mode
l Specifies whether to switch services to the original working PW after the fault is rectified. l The value Revertive indicates that services are switched to the original working PW and the value Nonrevertive indicates that services are not switched to the original working PW. l The value Revertive is recommended.
B-398
Issue 02 (2011-01-20)
Value Range 1 to 12
Default Value -
Description l Displays or specifies the WTR time of the protection group. l When the preset WTR time expires after the original working PW recovers, services are switched to the original working PW. l This parameter is available only when Restoration Mode is Revertive.
0 to 100
l Displays or specifies the hold-off time of the protection group. l If this parameter is set to a value other than 0, the protection group does not trigger switching once it detects faults, but waits until the hold-off time expires, and then detects whether any faults persist. If any faults persist, the switching is triggered; otherwise, no switching is triggered.
Deployment Status
Display the deployment status of the protection group. Displays the switchover status of the protection group. Displays the enabling status of the protocol. Displays the status of the current working path. Display the status of the current protection path.
Switchover Status
Issue 02 (2011-01-20)
B-399

NOTE
The following parameters are available only after the slave protection pair is configured.
Value Range -
Default Value -
Description Specifies the ID of the slave protection pair. The switching of the master PW APS protection group triggers the switching of the slave PW APS protection group simultaneously. Displays the ID of the working PW in the slave protection pair. Displays the ID of the protection PW in the slave protection pair. Displays the DNI PW ID. Displays the PW type. Displays the deployment status of the slave protection pair.
Working PW ID
Protection PW ID
DNI PW ID PW Type Deployment Status
Related Tasks
A.7.6.2 Modifying CES Service Parameters A.7.6.3 Querying CES Service Information
B.8.2.2 Parameter Description: CES Service Management_Creation

This topic describes the parameters that are related to creating CES services.
Navigation Path
1. 2. In the NE Explorer, select the NE from the Object Tree and choose Configuration > CES Service Management from the Function Tree. Click New.

Parameter Service ID(e.g.1,3-6)
B-400
Default Value -
Description Specifies the service ID.

Issue 02 (2011-01-20)
Parameter Service name Level
Value Range E1
Default Value E1
Description Specifies the service name. The value E1 indicates that the CES service is used to transmit the TDM services from E1 ports. l Specifies the mode of CES service. l The value UNI-NNI indicates that the CES service is carried by a PW. Therefore, the information about the PW needs to be configured.
Mode
UNI-NNI UNI-UNI
UNI-NNI
Source Board
Specifies the board where the source (UNI) of the CES service is located. For the OptiX RTN 980, this parameter cannot be configured. If Level is set to E1, this parameter indicates the E1 port where the service source is located. If Mode is set to UNI-NNI, this parameter can assume only one value.
Source High Channel
Source Low Channel (e.g.1,3-6)
Issue 02 (2011-01-20)
B-401
Parameter Source 64K Timeslot (e.g.1,3-6)
Value Range 1-31
Default Value 1-31
Description l Specifies the 64 kbit/s timeslot that transmits data. This parameter can assume multiple values. The values of this parameter must include 16 if Frame Mode is 30. l On the two ends of a radio link, the timeslot lists can be different but the numbers of timeslots must the same. l This parameter does not need to be set if Mode is UNI-NNI and PW Type is SAToP.
B-402
Issue 02 (2011-01-20)
Parameter Priority List
Default Value EF
Description l Specifies the priority of a CES service. This parameter is available only when Mode is set to UNI-UNI. l This parameter needs to be configured if QoS processing needs to be performed for different CES services. l CS6-CS7: indicate the highest service classes, which are mainly involved in signaling transmission. l EF: indicates the expedited forwarding of service, which is applicable to services of low transmission delay and low packet loss rate, for example, voice and video services. l AF1-AF4: indicate the assured forwarding classes of service, which are applicable to services that require an assured rate but no delay or jitter limit. l BE: is applicable to services that need not be processed in a special manner. l The default value is recommended.
Issue 02 (2011-01-20)
B-403
Parameter PW Type
Value Range CESoPSN SAToP
Default Value CESoPSN
Description l Specifies the type of the PW. This parameter is available only when Mode is UNI-NNI. l CESoPSN: Indicates structure-aware TDM circuit emulation service over packet switched network. Timeslot compression can be set. SAToP: Indicates structureagnostic TDM over packet. Timeslot compression cannot be set.
Protection Type
No Protection PW APS Slave Protection Pair
No Protection
l Specifies the protection mode of the PW. This parameter is available only when Mode is UNI-NNI. l If this parameter is set to PW APS, working and protection PWs need to be configured. l When this parameter is set to Slave Protection Pair , you need to bind the slave PW APS protection group with the master PW APS protection group. The switching of the master PW APS protection group triggers the switching of the slave PW APS protection group simultaneously.
Sink Board
l Specifies the board where the sink of the CES service is located. l This parameter is available only when Mode is set to UNIUNI.
B-404
Issue 02 (2011-01-20)
Parameter Sink High Channel
Value Range -
Default Value -
Description For the OptiX RTN 980, this parameter cannot be configured. l If Level is set to E1, this parameter indicates the E1 port where the service sink is located. l This parameter is available only when Mode is set to UNIUNI.
Sink Low Channel(e.g. 1,3-6)
Sink 64K Timeslot(e.g. 1,3-6)
1-31
1-31
l Specifies the 64 kbit/s timeslot that the service sink occupies. On the two ends of a radio link, the timeslot lists can be different but the numbers of timeslots must the same. l This parameter is available only when Mode is set to UNIUNI.

NOTE
If the parameter Protection Type of PWs is set to PW APS or Slave Protection Pair, all the parameters of working and protection PWs need to be configured. This section considers the parameters of the working PW as an example.
Parameter PW ID PW Signaling Type
Value Range Static
Description Specifies the ID of the PW that carries services. Specifies the signaling type of the PW. Labels for static PWs need to be manually assigned. Displays the PW type. Displays the direction of the PW.
PW Type Direction
Issue 02 (2011-01-20)
B-405
Value Range -
Default Value -
Description Displays the encapsulation type of the PW. Specifies the PW Ingress label. Specifies the PW Egress label. Displays the method to select tunnels. Displays the type of the tunnel that carries the PW. A tunnel needs to be selected. If no tunnel is available, creation of a PW will fail. Specifies the LSR ID of the PW at the remote end. If an existing tunnel is selected, the LSR ID will be automatically assigned. For a bidirectional tunnel, the system will configure the reverse tunnel automatically.
16 to 1048575 16 to 1048575 MPLS -
MPLS -
Opposite LSR ID
Egress Tunnel
QoS Parameters
Parameter EXP Value Range Default Value Description The OptiX RTN 980 does not support this parameter.
B-406
Issue 02 (2011-01-20)
Parameters for the Advanced Attributes of PWs

Parameter RTP Header Value Range Disable Enable Huawei RTP Default Value Disable Description l Specifies the RTP header. l The RTP header carries time stamps. l The default value is recommended. Jitter Compensation Buffering Time (us) 375 to 16000 8000 l Specifies the jitter buffer time for the received CES packets. The step is 125. l A greater value of this parameter means fewer impacts of transmission jitters on CES services, greater delays of CES services, and more resources occupied by CES services. l The default value is recommended.
125 to 5000
1000
l Specifies the length of fragments in the TDM data stream. The step is 125. l A greater value of this parameter means higher encapsulation efficiency but greater delays of CES services. l The default value is recommended.
Issue 02 (2011-01-20)
B-407
Parameter Ingress Clock Mode
Value Range Null Adaptive Clock Mode
Default Value Null
Description l Specifies the mode in which CES services extract clocks from TDM services. l The value Null indicates that no clocks are extracted. If this value is assumed, CES services do not transmit clocks. l The value Adaptive Clock Mode indicates that CES services extract clocks from TDM services. If this value is assumed, CES services transmit TDM line clocks to the downstream. l You need to determine the end of master clock. This parameter assumes the value Adaptive Clock Mode at the end of master clock and assumes the value Null at the end of slave clock.
Egress Clock Mode
B-408
Issue 02 (2011-01-20)
Parameter Control Channel Type
Value Range None CW Alert Label
Default Value None
Description l Specifies the mode of PW connectivity check. l The value None indicates that the control word is not supported. That is, the PW connectivity check is not supported. l Alert Label indicates VCCV packets in Alert Label encapsulation mode. l The value CW indicates that the control word is supported.
VCCV Verification Mode
None Ping
None
l Specifies the VCCV verification mode. The VCCV verification is used for PW connectivity check. l If the VCCV-Ping test is required, set this parameter to Ping.
Enable CES Service Alarm Transparent Transmission
Disabled Enabled
Disabled
If this function is enabled, the fault on the AC side of the CES service is notified to the remote end. On receiving the fault notification from the network side or the remote end, the local NE inserts the corresponding alarm to the AC side.
Issue 02 (2011-01-20)
B-409
Parameter Threshold of Entering R Bit Inserting Status
Value Range 1-65535
Default Value 100
Description l The corresponding alarm will be reported if the number of consecutive lost packets crosses the threshold specified by this parameter. l This function is available only when the transparent transmission of CES service alarms is enabled.
Threshold of Exiting R Bit Inserting Status
1-65535
l The corresponding alarm will be cleared if the number of consecutive received packets crosses the threshold specified by this parameter. l This function is available only when the transparent transmission of CES service alarms is enabled.
Huawei Mode Standard Mode
Standard Mode
Specifies the sequence number mode. The Sequence Number Mode must be set to the same value at both ends of a radio link.

NOTE
Parameter Protection Type Protection Group ID
Value Range -
Default Value -
Description Specifies the protection type. Specifies the protection group ID.
B-410
Issue 02 (2011-01-20)
Parameter Enabling Status
Description l Specifies the enabling status of the PW protection group. l During the creation of a protection group, set Enabling Status to Disabled. After the APS protection group is configured at both ends, set Enabling Status to Enabled.
Revertive Mode
Revertive
Issue 02 (2011-01-20)
B-411
Value Range 1 to 12
Default Value 1
0 to 100
Detection mode
OAM Parameters
NOTE
B-412
Issue 02 (2011-01-20)
Issue 02 (2011-01-20)
B-413
Value Range CV FFD
Default Value CV
3.3 10 20 50 100 200 500
50
B-414
Issue 02 (2011-01-20)

NOTE
Value Range -
Default Value -
Working PW ID
Protection PW ID
Related Tasks
A.7.6.1 Creating CES Services
B.8.3 ATM Parameters

This topic describes the parameters that are related to ATM services. B.8.3.1 Parameter Description: ATM IMA Management_IMA Group Management This topic describes the parameters that are related to IMA group management. B.8.3.2 Parameter Description: ATM IMA Management_Bound Path Configuration This topic describes the parameters that are related to the bound paths in the ATM TRUNK. B.8.3.3 Parameter Description: ATM IMA Management_IMA Group Status This topic describes the parameters that are related to IMA group status. B.8.3.4 Parameter Description: ATM IMA Management_IMA Link Status This topic describes the parameters that are related to IMA link status. B.8.3.5 Parameter Description: ATM IMA Management_ATM Interface Management This topic describes the parameters that are related to ATM interface management. B.8.3.6 Parameter Description: Configuration of ATM Service Class Mapping Table This topic describes the parameters that are related to configuration of the ATM service class mapping table. B.8.3.7 Parameter Description: Configuration of ATM Service Class Mapping Table_Creation
This topic describes the parameters that are related to creation of the ATM service class mapping table. B.8.3.8 Parameter Description: ATM Policy Management This topic describes the parameters that are related to ATM policy management. B.8.3.9 Parameter Description: ATM Policy Management_Creation This topic describes the parameters that are related to creation of ATM policies. B.8.3.10 Parameter Description: ATM Service Management This topic describes the parameters that are related to ATM service management. B.8.3.11 Parameter Description: ATM Service Management_Creation This topic describes the parameters that are related to creation of ATM services. B.8.3.12 Parameter Description: ATM OAM Management_Segment and End Attributes This topic describes the parameters that are related to segment end attributes of ATM OAM. B.8.3.13 Parameter Description: ATM OMA Management_CC Activation Status This topic describes the parameters that are related to the CC activation status of ATM OAM. B.8.3.14 Parameter Description: ATM OAM Management_Remote End Loopback Status This topic describes the parameters that are related to the remote end loopback status of ATM OAM. B.8.3.15 Parameter Description: ATM OAM Management_LLID This topic describes the parameters that are related to LLID configuration.
B.8.3.1 Parameter Description: ATM IMA Management_IMA Group Management

This topic describes the parameters that are related to IMA group management.
Navigation Path
1. 2. In the NE Explorer, select the NE from the Object Tree and choose Configuration > Interface Management > ATM IMA Management from the Function Tree. Click the IMA Group Management tab.

Parameter VCTRUNK Value Range Default Value Description Displays the ATM TRUNK.
B-416
Issue 02 (2011-01-20)
Parameter IMA Protocol Enable Status
Description l Specifies the IMA protocol enable status. l Set IMA Protocol Enable Status to Enabled if the links bound in the ATM TRUNK require the IMA protocol; otherwise, set this parameter to Disabled. l After IMA Protocol Enable Status is set to Enabled, the E1 links or Fractional E1 timeslots bound in the ATM TRUNK start running the IMA protocol.
Minimum Number of Active Transmitting Links
1 to 16
l The links of the IMA group can carry services only when the number of activated links in the transmit/ receive direction is not smaller than the value of Minimum Number of Active Transmitting Links/ Minimum Number of Active Receiving Links. l The values of Minimum Number of Active Transmitting Links and Minimum Number of Active Receiving Links must be the same because the OptiX RTN 980 supports Symmetrical Mode and Symmetrical Operation only. The parameters Minimum Number of Active Transmitting Links and Minimum
Issue 02 (2011-01-20)
B-417
Parameter Minimum Number of Active Receiving Links
Value Range 1 to 16
Default Value 1
Description Number of Active Receiving Links must assume the same value on the two ends of an IMA link. l The default value is recommended.
IMA Protocol Version
1.0 1.1
1.1
l Specifies the IMA protocol version. l The parameter IMA Protocol Version must assume the same value on the two ends of an IMA link. l The default value is recommended.
B-418
Issue 02 (2011-01-20)
Parameter IMA Transmit Frame Length
Value Range 32 64 128 256
Default Value 128
Description l Specifies the IMA transmit frame length. l Based on the IMA frame format, the receive end rebuilds the ATM cell stream with the cells arriving from diverselydelayed links. Longer IMA frames result in higher transmission efficiency and occupy more resources. Once a member link fails, the impact on the entire IMA group increases as the length of IMA frames increases. l The IMA Transmit Frame Length must assume the same value on the two ends of an IMA link. l The default value is recommended.
Issue 02 (2011-01-20)
B-419
Parameter IMA Symmetry Mode
Value Range Symmetrical Mode and Symmetrical Operation
Default Value Symmetrical Mode and Symmetrical Operation
Description l Specifies the symmetrical mode of the IMA group. l If the symmetrical mode and symmetrical operation is adopted, the bandwidth of the IMA group is always consistent in the transmit direction and in the receive direction, even when some member links fail. In symmetrical mode: Bandwidth of the IMA group = min {bandwidth in the transmit direction, bandwidth in the receive direction} The unidirectional failure of one member link is equivalent to the bidirectional failure of one member link.
B-420
Issue 02 (2011-01-20)
Parameter Maximum Delay Between Links (ms)
Default Value 25
Description l Specifies the maximum differential delay that is allowed between the member links. l If the differential delay between a member link and the other member links exceeds the value, this link will be deactivated and deleted from the IMA group. l If this parameter is set to a value higher than the normal value range, the delay of IMA services will be prolonged and even packet loss will occur; if this parameter is set to a value lower than the normal value range, a working link will be deleted by mistake. l The Maximum Delay Between Links (ms) must assume the same value on the two ends of an IMA link. l The default value is recommended.
Clock Mode
CTC Mode ITC Mode
CTC Mode
l Specifies the clock mode of the IMA group. l Clock Mode is set to the same value for the interconnected ends of IMA links.
Related Tasks
B.8.3.2 Parameter Description: ATM IMA Management_Bound Path Configuration

This topic describes the parameters that are related to the bound paths in the ATM TRUNK.
Navigation Path
1. 2. 3. In the NE Explorer, select the NE from the Object Tree and choose Configuration > Interface Management > ATM IMA Management from the Function Tree. Click the Binding tab. Click Configuration.

Parameter Available Boards Configuration Ports Value Range Default Value Description Selects the available boards. Selects the available ports. l For ATM/IMA E1 services, you need to set Port Mode in PDH Interface to Layer 2 in advance. l For Fractional ATM/ IMA services, set Port Mode in PDH Interface to Layer 1 and configure A.5.5 Setting Serial Port Parameters. Level E1 Fractional E1 E1 Specifies the level of bound paths. l If ATM/IMA services need to be mapped into the ATM TRUNK that binds one or more E1 ports, select E1 in Level. l If ATM/IMA services need to be mapped into the ATM TRUNK that binds one or more serial ports, select Fractional E1 in Level. Direction Displays the direction of bound paths. The fixed value is bidirectional. The OptiX RTN 980 does not support this parameter.
Optical Interface
B-422
Issue 02 (2011-01-20)
Parameter Available Resources
Value Range -
Default Value -
Description Displays the ports that carry the available paths for IMA services. The OptiX RTN 980 does not support this parameter. Displays the bound paths. Displays the name of the ATM TRUNK. Displays the level of bound paths. Displays the direction of bound paths. The fixed value is bidirectional. Displays the bound paths. Displays the number of bound paths. Specifies whether to display bound paths in combination.
Available Timeslots Selected Bound Paths VCTRUNK Level Direction
Bound Paths Number of Bound Paths Display in Combination
Selected Not selected
Selected
Related Tasks
A.7.7.1 Binding ATM TRUNKs
B.8.3.3 Parameter Description: ATM IMA Management_IMA Group Status

This topic describes the parameters that are related to IMA group status.
Navigation Path
1. 2. In the NE Explorer, select the NE from the Object Tree and choose Configuration > Interface Management > ATM IMA Management from the Function Tree. Click the IMA Group States tab.

Parameter VCTRUNK Near-End Group Status Value Range Default Value Description Displays the VCTRUNK. Displays the status of the near-end group.
Issue 02 (2011-01-20)
B-423
Parameter Far-End Group Status Transmit Rate (cell/s) Receive Rate (cell/s) Number of Transmit Links Number of Receive Links Number of Activated Transmit Links Number of Activated Receive Links
Value Range -
Default Value -
Description Displays the status of the far-end group. Displays the cell transmission rate. Displays the cell receiving rate. Displays the number of transmit links. Displays the number of receive links. Displays the number of activated transmit links. Displays the number of activated receive links.
Related Tasks
A.7.7.4 Querying Running Status of an IMA Group
B.8.3.4 Parameter Description: ATM IMA Management_IMA Link Status

This topic describes the parameters that are related to IMA link status.
Navigation Path
1. 2. In the NE Explorer, select the NE from the Object Tree and choose Configuration > Interface Management > ATM IMA Management from the Function Tree. Click the IMA Link States tab.

Parameter VCTRUNK E1 Link Differential Delay Check Status Near-End Receiving Status Near-End Transmitting Status
B-424
Value Range -
Default Value -
Description Displays the VCTRUNK. Displays E1 links. Displays the status of the deferential delay check. Displays the near-end receiving status. Displays the near-end transmitting status.
Issue 02 (2011-01-20)
Parameter Far-End Receiving Status Far-End Transmitting Status
Value Range -
Default Value -
Description Displays the far-end receiving status. Displays the far-end transmitting status.
Related Tasks
A.7.7.5 Querying Link Running Status of an IMA Group
B.8.3.5 Parameter Description: ATM IMA Management_ATM Interface Management

This topic describes the parameters that are related to ATM interface management.
Navigation Path
1. 2. In the NE Explorer, select the NE from the Object Tree and choose Configuration > Interface Management > ATM IMA Management from the Function Tree. Click the ATM Interface Management tab.

Parameter Port Name Value Range Default Value Description Displays the port. Displays or specifies the name of port.
Issue 02 (2011-01-20)
B-425
Parameter Port Type
Value Range UNI NNI
Default Value UNI
Description Specifies the type of ATM port. l UNI: the port connecting user-side devices. For example, the UNI port applies to the user-side interface on the common ATM network or to the userside interface of the PE on the PSN network that transmits ATM PWE3 services. l NNI: the port connecting networkside devices. For example, the NNI port applies to the networkside interface on the common ATM network.
ATM Cell Payload Scrambling
Disabled Enabled
Enabled
Specifies whether to enable payload scrambling of ATM cells. l The ITU-T G.804 stipulates that the payload (48 bytes) of ATM cells must be scrambled before it is mapped into E1 signals. Therefore, it is recommended that you set ATM Cell Payload Scrambling to Enabled. l ATM Cell Payload Scrambling must assume the same value on the two ends of an ATM link. Otherwise, packet loss will occur.
Min. VPI Max. VPI
The OptiX RTN 980 does not support this parameter. The OptiX RTN 980 does not support this parameter.
B-426
Issue 02 (2011-01-20)
Parameter Min. VCI Max. VCI VCC-Supported VPI Count Loopback
Value Range No Loopback Outloop Inloop
Default Value Inloop
Description The OptiX RTN 980 does not support this parameter. The OptiX RTN 980 does not support this parameter. The OptiX RTN 980 does not support this parameter. Specifies the loopback status of the port.
Related Tasks
B.8.3.6 Parameter Description: Configuration of ATM Service Class Mapping Table

This topic describes the parameters that are related to configuration of the ATM service class mapping table.
Navigation Path
In the NE Explorer, select the NE from the Object Tree and choose Configuration > QoS Management > Diffserv domain Management > ATM COS Mapping Configuration from the Function Tree.

Parameter Mapping Relation ID Mapping Relation Name UBR CBR RT-VBR NRT-VBR UBR+ Value Range BE AF11 AF12 AF13 AF21 AF22 AF23 AF31 AF32
Issue 02 (2011-01-20) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.
Default Value UBR: BE CBR: EF RT-VBR: AF31 NRT-VBR: AF21 UBR+: AF11 PORT-TRANS: BE
Description Specifies the ID of the mapping table. Specifies the name of the mapping relationship. Displays or specifies the PHB service classes that correspond to different ATM service types. l Eight PHB service classes are available: BE, AF1, AF2, AF3, AF4, EF, CS6, and CS7. The OptiX RTN 980 provides different QoS policies for the
B-427
Parameter PORT-TRANS
Value Range AF33 AF41 AF42 AF43 EF CS6 CS7
Default Value
Description queues of different service classes. l CS6 to CS7: highest service classes, mainly applicable to signaling transmission. l EF: fast forwarding, applicable to services of low transmission delays and low packet loss rates. l AF1 to AF4: assured forwarding, applicable to services that require an assured transmission rate rather than delay or jitter limits.
NOTE The AF1 class includes three subclasses: AF11, AF12, and AF13. Only one of these subclasses can take effect for one queue. It is the same case with AF2, AF3, and AF4.
l BE: best effort, applicable to services that do not require special processing.
Related Tasks
A.7.9.2 Modifying an ATM-Diffserv Domain
B.8.3.7 Parameter Description: Configuration of ATM Service Class Mapping Table_Creation

This topic describes the parameters that are related to creation of the ATM service class mapping table.
B-428
Issue 02 (2011-01-20)
Navigation Path
1. In the NE Explorer, select the NE from the Object Tree and choose Configuration > QoS Management > Diffserv domain Management > ATM COS Mapping Configuration from the Function Tree. Click New.
2.

Parameter Mapping Relation ID Mapping Relation Name UBR CBR RT-VBR NRT-VBR UBR+ Value Range 2 to 8 BE AF11 AF12 AF13 AF21 AF22 AF23 AF31 AF32 AF33 AF41 AF42 AF43 EF CS6 CS7 Default Value UBR: BE CBR: EF RT-VBR: AF31 NRT-VBR: AF21 UBR+: AF11 PORT-TRANS: BE Description Specifies the ID of the mapping table. Specifies the name of the mapping relationship. Specifies the PHB service classes that correspond to different ATM service types. l Eight PHB service classes are available: BE, AF1, AF2, AF3, AF4, EF, CS6, and CS7. The OptiX RTN 980 provides different QoS policies for the queues of different service classes. l CS6 to CS7: highest service classes, mainly applicable to signaling transmission. l EF: fast forwarding, applicable to services of low transmission delays and low packet loss rates. l AF1 to AF4: assured forwarding, applicable to services that require an assured transmission rate rather than delay or jitter limits.
Issue 02 (2011-01-20)
B-429
Parameter PORT-TRANS
Value Range
Default Value
Description
NOTE The AF1 class includes three subclasses: AF11, AF12, and AF13. Only one of these subclasses can take effect for one queue. It is the same case with AF2, AF3, and AF4.
l BE: best effort, applicable to services that do not require special processing.
Related Tasks
A.7.9.1 Creating an ATM-DiffServ Domain
B.8.3.8 Parameter Description: ATM Policy Management

This topic describes the parameters that are related to ATM policy management.
Navigation Path
1. 2.
B-430
In the NE Explorer, select the NE from the Object Tree and choose Configuration > QoS Management > Policy Management > ATM Policy from the Function Tree. Click the ATM Policy tab.

Parameter Policy ID Policy Name Value Range Default Value 1 Description Displays the policy ID of the ATM service. Displays or specifies the policy name of the ATM service. The maximum length of the value is 64 bytes.
Issue 02 (2011-01-20)
B-431
Parameters for Configuring ATM Traffic

Parameter Service Type Value Range UBR CBR RT-VBR NRT-VBR UBR+ Default Value UBR Description Displays or specifies the type of the ATM service. l The UBR service is characterized by nonreal-time applications and many bursts. The UBR service does not specify traffic-related service guarantees. To be specific, the UBR service only requires that the network side provides the service with the best effort. The network side does not provide any assured QoS for the UBR service. In the case of network congestion, the UBR cells are discarded first. l The CBR service requires tightly constrained delay variation and requires that data be transmitted at a constant rate. In addition, the CBR service requests a static amount of bandwidth and the highest priority. The CBR service is characterized by stable traffic and few bursts. l The rt-VBR service requires tightly constrained delay and delay variation. Compared with the CBR service, the rtVBR service allows sources to transmit data at a rate that varies with time. Equivalently, the sources can be
B-432
Issue 02 (2011-01-20)
Parameter
Value Range
Default Value
Description described as bursty. In addition, the rt-VBR service does not require a static amount of bandwidth. l Compared with the rtVBR service, the nrtVBR service does not require tightly constrained delay or delay variation, and is intended for non-realtime applications. l The UBR+ service is supplementary to the UBR service and is intended for applications that require assured minimum cell rate, which is indicated by the minimum cell rate (MCR) parameter. The other characteristics of the UBR+ service are the same as the corresponding characteristics of the UBR service.
Traffic Type Clp01Pcr(cell/s) Clp01Scr(cell/s) Clp0Pcr(cell/s) Clp0Scr(cell/s) Max. Cell Burst Size (cell) Cell Delay Variation Tolerance (0.1us) Discard Traffic Frame
90 to 74539 90 to 74539 90 to 74539 90 to 74539 2 to 200000 7 to 13300000 Enabled Disabled
Disabled
The Table B-27 lists the ATM service type, traffic type descriptor, and the related traffic parameters. ATM policies are configured based on these mapping relationships.
Displays or specifies the frame discarding mark in ATM policies. This parameter is effective to AAL5 traffic.
Issue 02 (2011-01-20)
B-433
Parameter UPC/NPC
Description Displays or specifies UPC/NPC. l UPC is user-side parameter control and NPC is network-side parameter control. l After UPC/NPC is enabled, the cells with a frame discarding mark will be discarded in network congestion.
Table B-27 Mapping relationship between ATM service types, traffic types, and traffic parameters ATM Service Type UBR ATM Traffic Type Descriptor NoTrafficDescriptor NoClpTaggingNoScr NoClpNoScr NoClpNoScrCdvt CBR ClpTransparentNoScr ClpNoTaggingNoScr ClpTaggingNoScr NoClpNoScr NoClpNoScrCdvt nrtVBR NoClpScr ClpNoTaggingScr ClpTaggingScr rtVBR ClpTransparentScr NoClpScrCdvt ClpNoTaggingScrCdvt ClpTaggingScrCdvt UBR+ atmnotrafficdescriptormcr atmnoclpmcr Traffic Parameter 1 Clp01Pcr Clp01Pcr Clp01Pcr Clp01Pcr Clp01Pcr Clp01Pcr Clp01Pcr Clp01Pcr Clp01Pcr Clp01Pcr Clp01Pcr Clp01Pcr Clp01Pcr Clp01Pcr Clp01Pcr Clp01Mcr Clp01Pcr Traffic Parameter 2 CDVT CDVT CDVT Clp0Pcr Clp0Pcr CDVT Clp01Scr Clp0Scr Clp0Scr Clp01Scr Clp01Scr Clp0Scr Clp0Scr Clp01Mcr Traffic Parameter 3 MBS MBS MBS MBS MBS MBS MBS Traffic Parameter 4 CDVT CDVT CDVT CDVT -
B-434
Issue 02 (2011-01-20)
ATM Service Type
ATM Traffic Type Descriptor atmnoclpmcrcdvt
Traffic Parameter 1 Clp01Pcr
Traffic Parameter 2 Clp01Mcr
Traffic Parameter 3 CDVT
Traffic Parameter 4 -
Parameters for the application object

Parameter Service ID Value Range Default Value Description Displays the ID configured for the ATM service. Displays the name configured for the ATM service. Displays the link ID. Displays the direction of the service.
Service Name
Link ID Direction
Related Tasks
A.7.9.4 Modifying an ATM Policy
B.8.3.9 Parameter Description: ATM Policy Management_Creation

This topic describes the parameters that are related to creation of ATM policies.
Navigation Path
1. 2. In the NE Explorer, select the NE from the Object Tree and choose Configuration > QoS Management > Policy Management > ATM Policy from the Function Tree. Click New.

Parameter Policy ID Value Range Default Value 1 Description Specifies the policy ID of the ATM service. The policy ID can also be automatically allocated.
Issue 02 (2011-01-20)
B-435
Parameter Policy Name
Value Range Synchronous signal Signaling Voice Data Video
Default Value Synchronous signal
Description Specifies the policy name of the ATM service. The maximum length of the value is 64 bytes.
NOTE You can select one of the five ATM service policy names from the drop-down list or enter the policy name.
B-436
Issue 02 (2011-01-20)
Parameter Service Type
Value Range UBR CBR RT-VBR NRT-VBR UBR+
Default Value UBR
Description Specifies the type of the ATM service. l The UBR service is characterized by nonreal-time applications and many bursts. The UBR service does not specify traffic-related service guarantees. To be specific, the UBR service only requires that the network side provides the service with the best effort. The network side does not provide any assured QoS for the UBR service. In the case of network congestion, the UBR cells are discarded first. l The CBR service requires tightly constrained delay variation and requires that data be transmitted at a constant rate. In addition, the CBR service requests a static amount of bandwidth and the highest priority. The CBR service is characterized by stable traffic and few bursts. l The rt-VBR service requires tightly constrained delay and delay variation. Compared with the CBR service, the rtVBR service allows sources to transmit data at a rate that varies with time. Equivalently, the sources can be described as bursty. In
Issue 02 (2011-01-20)
B-437
Parameter
Value Range
Default Value
Description addition, the rt-VBR service does not require a static amount of bandwidth. l Compared with the rtVBR service, the nrtVBR service does not require tightly constrained delay or delay variation, and is intended for non-realtime applications. l The UBR+ service is supplementary to the UBR service and is intended for applications that require assured minimum cell rate, which is indicated by the minimum cell rate (MCR) parameter. The other characteristics of the UBR+ service are the same as the corresponding characteristics of the UBR service.
Traffic Type Clp01Pcr(cell/s) Clp01Scr(cell/s) Clp0Pcr(cell/s) Clp0Scr(cell/s) Max. Cell Burst Size (cell) Cell Delay Variation Tolerance (0.1us) Discard Traffic Frame
90 to 74539 90 to 74539 90 to 74539 90 to 74539 2 to 200000 7 to 13300000 Enabled Disabled
Disabled
For the mapping relationships between ATM service types, ATM traffic type descriptors, and traffic parameters, see Table B-28. ATM policies are configured based on these mapping relationships.
Specifies the frame discarding mark in ATM policies. This parameter is effective to AAL5 traffic.
B-438
Issue 02 (2011-01-20)
Parameter UPC/NPC
Description l UPC is user-side parameter control and NPC is network-side parameter control. l After UPC/NPC is enabled, the cells with a frame discarding mark will be discarded in network congestion.
Table B-28 Mapping relationship between ATM service types, ATM traffic types, and traffic parameters ATM Service Type UBR ATM Traffic Type Descriptor NoTrafficDescriptor NoClpTaggingNoScr NoClpNoScr NoClpNoScrCdvt CBR ClpTransparentNoScr ClpNoTaggingNoScr ClpTaggingNoScr NoClpNoScr NoClpNoScrCdvt nrtVBR NoClpScr ClpNoTaggingScr ClpTaggingScr rtVBR ClpTransparentScr NoClpScrCdvt ClpNoTaggingScrCdvt ClpTaggingScrCdvt UBR+ atmnotrafficdescriptormcr atmnoclpmcr atmnoclpmcrcdvt Traffic Parameter 1 Clp01Pcr Clp01Pcr Clp01Pcr Clp01Pcr Clp01Pcr Clp01Pcr Clp01Pcr Clp01Pcr Clp01Pcr Clp01Pcr Clp01Pcr Clp01Pcr Clp01Pcr Clp01Pcr Clp01Pcr Clp01Mcr Clp01Pcr Clp01Pcr Traffic Parameter 2 CDVT CDVT CDVT Clp0Pcr Clp0Pcr CDVT Clp01Scr Clp0Scr Clp0Scr Clp01Scr Clp01Scr Clp0Scr Clp0Scr Clp01Mcr Clp01Mcr Traffic Parameter 3 MBS MBS MBS MBS MBS MBS MBS CDVT Traffic Parameter 4 CDVT CDVT CDVT CDVT -
Issue 02 (2011-01-20)
B-439
Related Tasks
A.7.9.3 Creating an ATM Policy

This topic describes the parameters that are related to ATM service management.
Navigation Path
In the NE Explorer, select the NE from the Object Tree and choose Configuration > ATM Service Management from the Function Tree.

Parameter Service ID Service Name Service Type Deployment Status Value Range Default Value Description Displays the service ID. Displays or specifies the service name. Displays the ATM service type. Displays the deployment status of the ATM service.
Connection Parameters
Parameter Connection ID Connection Name Value Range Default Value Description Displays the connection ID of the ATM service. Displays or specifies the connection name of the ATM service. Displays the source port of the ATM service. Displays the ID of the PW that carries ATM PWE3 services, if any. Displays the sink board of the ATM service. Displays the VPI of the source port of the ATM service.
Source Port PW ID
Sink Port Source VPI
B-440
Issue 02 (2011-01-20)
Parameter Source VCI
Value Range -
Default Value -
Description Displays the VCI of the source port of the ATM service. Displays the VPI of the sink port of the ATM service. Displays the VCI of the sink port of the ATM service. Displays the QoS policy of the uplink ATM connection. Displays the QoS policy of the downlink ATM connection.
Sink VPI
Sink VCI
Uplink Policy
Down link Policy
Parameters for Port Attributes

Parameter Port Port Type Max. VPI Max. VCI VCC-Supported VPI Count Value Range Default Value Description Displays the port of the ATM IMA service. Displays the port type of the ATM IMA service. Displays the maximum VPI. Displays the maximum VCI. Displays the count of VPIs that are used for VC exchange.
Parameters for Bound Paths

Parameter VCTRUNK Level Value Range Default Value Description Displays the VCTRUNK. Displays the level of bound paths.
Issue 02 (2011-01-20)
B-441
Parameter Direction
Value Range -
Default Value -
Description Displays the direction of bound paths. The fixed value is bidirectional. Displays the bound paths. Displays the number of bound paths. Displays the status of the IMA group.
Bound Paths Number of Bound Paths IMA Group Status
Parameters of PWs
Tab General Attributes Parameter PW ID Work Status Enable State PW Signaling Type Value Range Default Value Description Displays the PW ID. Displays the working status of a PW. Displays whether a PW is enabled. Displays the PW signaling type.
NOTE The OptiX RTN 980 uses static PWs only.
PW Type
l Displays the configured PW type. l This parameter corresponds to the connection type. The encapsulation type can be 1:1 or N: 1 if the connection type is PVP or PVC.
Displays the direction of the PW. Displays the encapsulation type of the packets on the PW.
NOTE The OptiX RTN 980 uses MPLS only.
PW Ingress Label / Source Port

B-442
Displays the configured PW Ingress label.

Issue 02 (2011-01-20)
Tab
Parameter PW Egress Label / Sink Port Opposite LSR ID Local Working Status Remote Working Status Compositive Working Status
Value Range -
Default Value -
Description Displays the configured PW Egress label. Displays the opposite LSR ID. Displays the working status of the PW at the local end. Displays the working status of the PW at the remote end. Displays the comprehensive working status of the PW. Displays the deployment status. Displays the PW ID. Displays the direction of the PW. Displays or specifies whether the bandwidth limit is enabled. l This function can be used to limit the bandwidth of one or more PWs, or the bandwidth of one or more ATM PWE3 services, in an MPLS tunnel. (One ATM PWE3 service corresponds to one PW.) l
Deployment Status QoS PW ID Direction Bandwidth Limit
CIR (Kbit/s)
Displays or specifies the committed information rate. It is recommended that you set this parameter to the same value as PIR.
CBS (kbyte)
Displays or specifies the excess burst size of the PW.

B-443
Issue 02 (2011-01-20)
Tab
Parameter PIR (kbit/s)
Value Range -
Default Value -
Description Displays or specifies the peak information rate. It is recommended that you set this parameter to the same value as CIR.
PBS (kbyte)
Displays or specifies the maximum excess burst size of the PW. The OptiX RTN 980 does not support this parameter. The OptiX RTN 980 does not support this parameter. Displays or specifies whether to use the control word. In the MPLS packet switching network, the control word is used to transmit packet information. l Displays or specifies the mode of PW connectivity check. l The value None indicates that the control word is not supported. That is, the PW connectivity check is not supported. l The value CW indicates that the control word is supported. l The value Alert Label indicates VCCV packets in Alert Label encapsulation mode.
EXP
Policy
Advanced Attributes
Control Word
Must Use No Use
CW None Alert Label
B-444
Issue 02 (2011-01-20)
Tab
Parameter VCCV Verification Mode
Value Range Ping None
Default Value -
Description l Displays or specifies the VCCV verification mode. The VCCV verification is used for PW connectivity check. l If the VCCV-Ping test is required, set this parameter to Ping.
Max. Concatenated Cell Count
1 to 31
l Displays or specifies the maximum number of concatenated cells. l If the value 1 is assumed, only one ATM cell is encapsulated in one packet. If the value from 2 to 31 is assumed, a maximum of 2 to 31 ATM cells are encapsulated into one packet.
100 to 50000
l Displays or specifies the packet loading time. Once the packet loading time expires, the packet is sent out even if the concatenated cells are less than the maximum. l If Max. Concatenated Cell Count assumes the value 1, this parameter is ineffective. That is, the packet will be sent out once the cell is loaded.
Issue 02 (2011-01-20)
B-445
Parameters for CoS Mapping

Parameter PW ID CoS Mapping Value Range Default Value Description Displays the ID of the PW that carries the service. Specifies the policy for mapping different ATM service levels to CoS priorities. By setting this parameter, different quality measures are provided for different ATM services.

NOTE
Value Range -
Default Value -
Description Displays the ID of the protection group to be created. Displays the ID of the working PW. Displays the ID of the protection PW. Displays the protection mode. l Displays or specifies the enabling status of the PW protection group. l During the creation of a protection group, set Enabling Status to Disabled. After the APS protection group is configured at both ends, set Enabling Status to Enabled.
Working PW ID Protection PW ID Protection Mode Enabling Status
Enabled Disabled
B-446
Issue 02 (2011-01-20)
Parameter Switchover Mode
Value Range -
Default Value -
Description Displays the switching mode to be used when a PW fails.

Restoration Mode
l Specifies whether to switch services to the original working PW after the fault is rectified. l The value Revertive indicates that services are switched to the original working PW and the value Nonrevertive indicates that services are not switched to the original working PW. l The value Revertive is recommended.
Switchover Restoration Time(min)
1 to 12
l Displays or specifies the WTR time of the protection group. l When the preset WTR time expires after the original working PW recovers, services are switched to the original working PW. l This parameter is available only when Restoration Mode is Revertive.
Issue 02 (2011-01-20)
B-447
Parameter Switchover Delay Time (100ms)
Default Value -
Description l Displays or specifies the hold-off time of the protection group. l If this parameter is set to a value other than 0, the protection group does not trigger switching once it detects faults, but waits until the hold-off time expires, and then detects whether any faults persist. If any faults persist, the switching is triggered; otherwise, no switching is triggered.
Deployment Status
Display the deployment status of the protection group. Displays the switchover status of the protection group. Displays the enabling status of the protocol. Displays the status of the current working path. Display the status of the current protection path.
Switchover Status
Related Tasks
A.7.8.2 Modifying ATM Service Parameters A.7.8.3 Querying ATM Services
B.8.3.11 Parameter Description: ATM Service Management_Creation

This topic describes the parameters that are related to creation of ATM services.
Navigation Path
1. 2.
B-448
In the NE Explorer, select the NE from the Object Tree and choose Configuration > ATM Service Management from the Function Tree. Click New.

Parameter Service ID Service Name Service Type Value Range 1 to 4294967295 UNIs-NNI UNI-UNI Default Value UNIs-NNI Description Specifies the service ID. Specifies the service name. l Specifies the type of the ATM service. l UNIs-NNI: This value applies to ATM PWE3 services. The attributes in Connection, PW, and CoS Mapping need to be configured. l UNI-UNI: This value applies to common ATM services. Only the attributes in Connection need to be configured.
Issue 02 (2011-01-20)
B-449
Parameter Connection Type
Value Range PVC PVP
Default Value UNIs-NNI:PVC UNI-UNI:PVC
Description Specifies the connection type of the ATM service. For common ATM services (UNI-UNI): l PVP: Only the VPIs of the source and sink are exchanged. l PVC: The VPIs and VCIs of the source and sink are exchanged. For ATM PWE3 services (UNIs-NNI): l PVP: This value applies to the N-to-1/1to-1 VPC encapsulation mode. It is recommended that you set the VPIs to the same value on the two ends of the ATM connection. l PVC: This value applies to the N-to-1/1to-1 VCC encapsulation mode. It is recommended that you set the VPIs/VCIs to the same value on the two ends of the ATM connection.
Protection Type
No Protection PW APS
No Protection
l Specifies the protection mode of the PW. This parameter is available only when Service Type is UNIsNNI. l Set this parameter according to the planning information.
Connection Parameters
Parameter Connection Name Value Range Default Value Description Specifies the name of the ATM connection.
Issue 02 (2011-01-20)
B-450
Parameter Source Board Source Port Source VPI(eg.35,36-39)
Value Range UNI: 0 to 255 NNI: 0 to 4095
Default Value -
Description Specifies the source board of the ATM service. Specifies the source port of the ATM service. Specifies the VPI of the source port of the ATM service. Specifies the VCI of the source port of the ATM service. Specifies the ID of the PW that carries services. Specifies the sink board of the ATM service. Specifies the sink board of the ATM service.
NOTE This parameter does not need to be set if Service Type is UNIs-NNI. This parameter needs to be set if Service Type is UNI-UNI and the value must be different from that of the source board.
Source VCI(eg.35,36-39)
32 to 65535
PW ID Sink Board Sink Port
1 to 4294967295 -
Sink VPI(eg.35,36-39)
UNI: 0 to 255 NNI: 0 to 4095
Specifies the VPI of the sink port of the ATM service. Specifies the VCI of the sink port of the ATM service. Specifies the QoS policy of the uplink ATM connection. Specifies the QoS policy of the downlink ATM connection.
Sink VCI(eg.35,36-39)
32 to 65535
Uplink Policy
Down link Policy
Parameters of PWs
NOTE
If the parameter Protection Type of PWs is set to PW APS, all the parameters of working and protection PWs need to be configured. This section considers the parameters of the working PW as an example.
Issue 02 (2011-01-20)
B-451
Parameter PW ID Working Status
Value Range -
Default Value -
Description Specifies the ID of the PW that carries services. Displays the working status of the PW.
NOTE This parameter is available only after the PW parameters are configured.
Enable Status
Displays the enabling status of the PW.

NOTE This parameter is available only after the PW parameters are configured.
PW Signaling Type PW Type
Static The ATM connection type is PVC: l ATM n to one VCC cell transport l ATM one-to-one VCC Cell Mode The ATM connection type is PVP: l ATM n to one VPC cell transport l ATM one-to-one VPC Cell Mode
Static The ATM connection type is PVC: ATM n to one VCC cell transport The ATM connection type is PVP: ATM n to one VPC cell transport
Labels for static PWs need to be manually assigned. l Specifies the type of the PW. l In the case of ATM 1_to_1 encapsulation, one PW carries one VPC or VCC. l In the case of ATM n_to_1 encapsulation, one PW carries one or more VPCs or VCCs.
Bidirectional MPLS
Bidirectional MPLS
Displays the direction of the PW. Displays the encapsulation type of the packets on the PW. Specifies the PW Ingress label. Specifies the PW Egress label. Displays the method to select tunnels. Displays the type of the tunnel that carries the PW.
PW Ingress Label / Source Port PW Egress Label / Sink Port Tunnel Selection Mode Tunnel Type
16 to 1048575 16 to 1048575 Manually MPLS
Manually MPLS
B-452
Issue 02 (2011-01-20)
Parameter Tunnel
Value Range -
Default Value -
Description A tunnel needs to be selected. If no tunnel is available, creation of a PW will fail. Specifies the LSR ID of the PW at the remote end. If an existing tunnel is selected, the LSR ID will be automatically assigned.
Opposite LSR ID
QoS Parameters
Table B-29 ATM services Parameter Bandwidth Limit Value Range Default Value Description Specifies whether the bandwidth limit is enabled. l This function can be used to limit the bandwidth of one or more PWs, or the bandwidth of one or more ATM PWE3 services, in an MPLS tunnel. (One ATM PWE3 service corresponds to one PW.) l Policy CIR (Kbit/s) The OptiX RTN 980 does not support this parameter. Specifies the committed information rate (CIR) of the PW. It is recommended that you set this parameter to the same value as PIR. CBS (kbyte) Specifies the excess burst size of the PW.
Issue 02 (2011-01-20)
B-453
Parameter PIR (kbit/s)
Value Range -
Default Value -
Description Specifies the peak information rate (PIR) of the PW. It is recommended that you set this parameter to the same value as CIR.
PBS (kbyte)
Specifies the maximum excess burst size of the PW. The OptiX RTN 980 does not support this parameter.
EXP

Parameter Control Word Value Range Must Use No Use Default Value Must Use Description l Specifies whether to use the control word. In the MPLS packet switching network, the control word is used to transmit packet information. l Set Control Word to Must Use if PW Type is ATM 1:1. Control Channel Type CW None Alert Label CW l Specifies the mode of PW connectivity check. l The value None indicates that the control word is not supported. That is, the PW connectivity check is not supported. l The value CW indicates that the control word is supported. l The value Alert Label indicates VCCV packets in Alert Label encapsulation mode.
B-454
Issue 02 (2011-01-20)
Parameter VCCV Verification Mode
Value Range Ping None
Default Value Ping
Description l Specifies the VCCV verification mode. The VCCV verification is used for PW connectivity check. l If the VCCV-Ping test is required, set this parameter to Ping.
Max. Concatenated Cell Count
1 to 31
10
l Specifies the maximum number of concatenated cells. l If the value 1 is assumed, only one ATM cell is encapsulated in one packet. If the value from 2 to 31 is assumed, a maximum of 2 to 31 ATM cells are encapsulated into one packet.
100 to 50000
1000
l Specifies the packet loading time. Once the packet loading time expires, the packet is sent out even if the concatenated cells are less than the maximum. l If Max. Concatenated Cell Count assumes the value 1, this parameter is ineffective. That is, the packet will be sent out once the cell is loaded.

NOTE
Parameter Protection Type
Value Range -
Default Value -
Description Specifies the protection type.

B-455
Issue 02 (2011-01-20)
Parameter Protection Group ID Enabling Status
Description Specifies the protection group ID. l Specifies the enabling status of the PW protection group. l During the creation of a protection group, set Enabling Status to Disabled. After the APS protection group is configured at both ends, set Enabling Status to Enabled.
Revertive Mode
Revertive
B-456
Issue 02 (2011-01-20)
Value Range 1 to 12
Default Value 1
0 to 100
Detection mode
OAM Parameters
NOTE
Issue 02 (2011-01-20)
B-457
B-458
Issue 02 (2011-01-20)
Value Range CV FFD
Default Value CV
3.3 10 20 50 100 200 500
50
Issue 02 (2011-01-20)
B-459

NOTE
Value Range -
Default Value -
Working PW ID
Protection PW ID
Parameters for CoS Mapping

Parameter PW ID CoS Mapping Value Range Default Value Description Displays the ID of the PW that carries service. Specifies the policy for mapping different ATM service levels to CoS priorities. By setting this parameter, different quality measures are provided for different ATM services.
Related Tasks
A.7.8.1 Creating ATM Services
B.8.3.12 Parameter Description: ATM OAM Management_Segment and End Attributes

This topic describes the parameters that are related to segment end attributes of ATM OAM.
Navigation Path
1. 2. In the NE Explorer, select the NE from the Object Tree and choose Configuration > ATM OAM Management from the Function Tree. Click the Segment End Attributes tab.

Parameter Source Sink Connection Direction Value Range Source Sink Default Value Description Displays the source node of the ATM/IMA service. Displays the sink node of the ATM/IMA service. Displays the direction of the ATM connection. l Source: the direction in which the ATM OAM cell stream enters the ATM connection. l Sink: the direction in which the ATM OAM cell stream leaves the ATM connection.
Issue 02 (2011-01-20)
B-461
Parameter Segment and End Attribute
Value Range Non segment and Endpoint Segment point Endpoint Segment and Endpoint
Default Value Non segment and Endpoint
Description Specifies the segment and end attributes of the source and sink of the ATM connection. l Non segment and endpoint: intermediate point, which refers to the OAM node between two segment points or two end points. Therefore, intermediate points can be further classified into intermediate points between segment points, and intermediate points between end points. Upon detecting a fault, an intermediate point reports the corresponding alarms and inserts segment AIS cells and end AIS cells to the downstream. Afterwards, the intermediate point periodically sends these cells. An intermediate point does not catch any AIS/RDI cells. l Segment point: an end point of a segment. One ATM link consists of multiple segments. Upon detecting a fault, a segment point reports the corresponding alarms and inserts segment AIS cells and end AIS cells to the downstream. Afterwards, the
B-462
Issue 02 (2011-01-20)
Parameter
Value Range
Default Value
Description segment point periodically sends these cells. A segment point catches segment AIS/RDI cells only. l End point: an end point of an ATM link. It is usually an edge point on the ATM network. Upon detecting a fault, an end point reports the corresponding alarms but does not insert any AIS cells. An end point catches end AIS/ RDI cells only. l Segment and endpoint: a segment-end point, or an edge point of a segment and an end. Upon detecting a fault, a segmentend point reports the corresponding alarms but does not insert any AIS cells. A segment-end point catches the AIS/RDI cells of a segment and an end.
Related Tasks
A.7.10.1 Setting Segment and End Attributes of AIS/RDI
B.8.3.13 Parameter Description: ATM OMA Management_CC Activation Status

This topic describes the parameters that are related to the CC activation status of ATM OAM.
Issue 02 (2011-01-20)
B-463
Navigation Path
1. 2. In the NE Explorer, select the NE from the Object Tree and choose Configuration > ATM OAM Management from the Function Tree. Click the CC Activation Status tab.

Parameter Source Sink Connection Direction Value Range Source Sink Default Value Description Displays the source node of the ATM/IMA service. Displays the sink node of the ATM/IMA service. Specifies the connection direction. l Source: the direction in which the ATM OAM cell stream enters the ATM connection. l Sink: the direction in which the ATM OAM cell stream leaves the ATM connection.
B-464
Issue 02 (2011-01-20)
Parameter Segment and End Attribute
Value Range -
Default Value -
Description Specifies the segment and end attributes of nodes. l Non segment and endpoint: an intermediate OAM point between two end points or two segment points. Therefore, intermediate points can be further classified into intermediate points between segment points, and intermediate points between end points. An intermediate point transparently transmits CC cells. l Segment point: an end point of a segment. One ATM link consists of multiple segments. Segment CC cells are terminated at segment points. l End point: an end point of an ATM link. It is usually an edge point on an ATM network. End-to-end CC cells are terminated at end points. l Segment and endpoint: a segment-end point, or an edge point of a segment and an end. A point needs to be a segment-end point if it serves as an end point and a segment point at the same time.
Issue 02 (2011-01-20)
B-465
Parameter CC Activate Flag
Value Range Deactivate Source activate Sink activate Source + sink activate
Default Value -
Description l Specifies the CC activation flag. l Deactivate: This node does not transmit or receive CC cells. l Source activate: This point transmits but does not receive CC cells. l Sink activate: This point receives but does not transmit CC cells. If this point does not receive any service cells or CC cells within a time interval of 3.5 (0.5) seconds, it will report the LOC alarm and transmit AIS cells in the forward direction. l Source + sink activate: This node transmits and receives CC cells. If this point does not receive any service cells or CC cells within a time interval of 3.5 (0.5) seconds, it will report the LOC alarm and transmit AIS cells in the forward direction. l Once the node receives any CC cells or service cells, the LOC alarm will be cleared.
Related Tasks
A.7.10.2 Performing a Continuity Check Test
B.8.3.14 Parameter Description: ATM OAM Management_Remote End Loopback Status

This topic describes the parameters that are related to the remote end loopback status of ATM OAM.
Navigation Path
1. 2. In the NE Explorer, select the NE from the Object Tree and choose Configuration > ATM OAM Management from the Function Tree. Click the Remote Loopback Test tab.

Parameter Source Sink Connection Direction Value Range Source Sink Default Value Description Displays the source node of the ATM/IMA service. Displays the sink node of the ATM/IMA service. Displays the direction of the ATM connection. l Source: the direction in which the ATM OAM cell stream enters the ATM connection. l Sink: the direction in which the ATM OAM cell stream leaves the ATM connection. Segment and End Attribute Specifies the segment and end attribute. l Segment LB cells are looped back only at a Segment point, Segment and Endpoint, or Non segment and Endpoint. l End-to-end LB cells are looped back only at an Endpoint or Segment and Endpoint.
Issue 02 (2011-01-20)
B-467
Parameter Loopback Point NE
Value Range -
Default Value -
Description l Specifies the NE where the loopback point is located. l Before an end-to-end LB test, you need to set end points in the test domain. After the test, remove the end points. l Before a segment-tosegment LB test, you need to set segment points in the test domain. After the test, remove the segment points.
Test Result
Displays the test result.
Related Tasks
B.8.3.15 Parameter Description: ATM OAM Management_LLID

This topic describes the parameters that are related to LLID configuration.
Navigation Path
1. 2. In the NE Explorer, select the NE from the Object Tree and choose Configuration > ATM OAM Management from the Function Tree. Click the LLID tab.

Parameter Country Code (Hexadecimal Code) Value Range Default Value 00 00 Description Displays or specifies the country code of the ATM service. The value is 2 bytes in length. Displays or specifies the network code of the ATM service. The value is 2 bytes in length.
Network Code (Hexadecimal Code)
00 01
B-468
Issue 02 (2011-01-20)
Parameter NE Code (Hexadecimal Code)
Value Range -
Default Value 00 30 00 04 00 00 00 00 00 00 00
Description l Displays or specifies the NE code of the ATM service. The value is 11 bytes in length. l The default NE code can be used if it is unique on the network. l NE code and NE ID are associated. Therefore, each NE on the network has a unique NE code.
Related Tasks
A.7.10.3 Querying or Setting LLIDs
B.9 Clock Parameters

This topic describes the parameters that are related to clocks. B.9.1 Parameter Description: Frequency Selection Mode This topic describes parameters that are related to frequency selection. B.9.2 Physical Clock Parameters This topic describes physical clock parameters. B.9.3 CES ACR Clock Parameters This topic describes CES ACR clock parameters.
B.9.1 Parameter Description: Frequency Selection Mode

This topic describes parameters that are related to frequency selection.
Navigation Path
In the NE Explorer, select the required NE from the Object Tree and choose Configuration > Clock > Frequency Selection Mode from the Function Tree.

Parameter NE Name Value Range Default Value Description Displays the NE name.
Issue 02 (2011-01-20)
B-469
Parameter Select Frequency Source Mode
Value Range Physical Synchronization PTP Synchronization
Default Value Physical Synchronization
Description Specifies the clock synchronization mode of an NE.

NOTE l For equipment that receives an external clock, set this parameter to Physical Synchronization. l For a 1588 ACR client or a PTP clock used for frequency synchronization, set this parameter to PTP Synchronization. l For IF boards, only Physical Synchronization is supported.
B.9.2 Physical Clock Parameters

This topic describes physical clock parameters. B.9.2.1 Parameter Description: Clock Source Priority Table This topic describes the parameters that are related to the priority table of a clock source. B.9.2.2 Parameter Description: Clock Subnet Setting_Clock Subnet This topic describes the parameters that are related to a clock subnet. B.9.2.3 Parameter Description: Clock Subnet Setting_Clock Quality This topic describes the parameters that are related clock quality. B.9.2.4 Parameter Description: Clock Subset Setting_SSM Output Control This topic describes the parameters that are related to SSM output control. B.9.2.5 Parameter Description: Clock Subset Setting_Clock ID Enabling Status This topic describes the parameters that are used for enabling the clock ID function. B.9.2.6 Parameter Description: Clock Source Switching_Clock Source Restoration Parameters This topic describes the parameters that are related to clock source restoration. B.9.2.7 Parameter Description: Clock Source Switching_Clock Source Switching This topic describes the parameters that are related to the switching status of a clock source. B.9.2.8 Parameter Description: Clock Source Switching_Clock Source Switching Conditions This section describes the parameters that are related to the switching conditions of clock sources. B.9.2.9 Parameter Description: Output Phase-Locked Source of the External Clock Source This topic describes the parameters of the output phase-locked source of the external clock source. B.9.2.10 Parameter Description: Clock Synchronization Status
This topic describes the parameters that are related to the clock synchronization status.
B.9.2.1 Parameter Description: Clock Source Priority Table

This topic describes the parameters that are related to the priority table of a clock source.
Navigation Path
1. 2. Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Clock > Physical Clock > Clock Source Priority. Click the System Clock Source Priority List tab.
Parameters
Parameter Clock Source Value Range Default Value Description l External clock source 1 indicates the external clock source at the CLK/TOD1 port on the CSHN board in physical slot 15. External clock source 2 indicates the external clock source at the CLK/TOD1 port on the CSHN board in physical slot 20. l The internal clock source is always at the lowest priority and indicates that the NE works in the free-run mode. l The clock sources and the corresponding clock source priority levels are determined according to the clock synchronization schemes. External Clock Source Mode 2Mbit/s 2MHz 2Mbit/s l This parameter indicates the type of the external clock source signal. l This parameter is set according to the external clock signal. In normal cases, the external clock signal is a 2 Mbit/s signal.
Parameter Synchronous Status Byte
Value Range SA4 to SA8
Default Value SA4
Description 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. In normal cases, the external clock sources use the SA4 to transmit the SSM.
Clock Source Priority Sequence (1 is the highest)
Displays the priority sequence of clock sources. 1 indicates the highest clock source priority.
Related Tasks
A.8.1.1 Configuring the Clock Sources
B.9.2.2 Parameter Description: Clock Subnet Setting_Clock Subnet

This topic describes the parameters that are related to a clock subnet.
Navigation Path
1. 2. Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Clock > Physical Clock > Clock Subnet Configuration. Click the Clock Subnet tab.
B-472
Issue 02 (2011-01-20)
Parameters for Setting a Clock Subnet

Parameter Affiliated Subnet Value Range 0 to 255 Default Value 0 Description l This parameter is used when the clock subnet needs 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 02 (2011-01-20)
B-473
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 on an SDH network and indicates that the SSM is passed by the lower four bits of the S1 byte and can be exchanged between the nodes. The SSM protocol ensures that the equipment automatically selects the clock source of the highest quality and highest priority, thus preventing mutual clock tracing. l After the standard SSM protocol is started, the NE first performs the protection switching on the clock source according to the clock quality level information provided by the S1 byte. If the quality level of the clock source is the same, the NE then performs the protection switching according to the clock priority table. That is, the NE selects an unlocked clock source that is of the highest quality and highest priority from all the current available clock sources as the clock source to be synchronized and traced by the local station. l If the SSM protocol is stopped, it indicates
B-474
Issue 02 (2011-01-20)
Parameter
Value Range
Default Value
Description that the S1 byte is not used. The NE selects and switches a clock source only according to the sequence specified in the priority table. The clock source of the highest priority is used as the clock source to be traced. l After the SSM protocol is stopped, each NE performs the protection switching on the clock according to the preset priority table of the clock source only when the clock source of a higher priority is lost.
Clock Source
This parameter indicates the clock source that is configured for an NE. In Clock Source Priority, you can set whether to add or delete a clock source.
Issue 02 (2011-01-20)
B-475
Parameter Clock Source ID
Value Range (None) 1 to 15
Default Value (None)
Description l This parameter is valid only when the extended SSM protocol is started. l Clock source IDs are allocated 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
Related Tasks
A.8.1.2 Configuring Clock Subnets
B.9.2.3 Parameter Description: Clock Subnet Setting_Clock Quality

This topic describes the parameters that are related clock quality.
Navigation Path
1. 2. Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Clock > Physical Clock > Clock Subnet Configuration. Click the Clock Quality tab.
B-476
Issue 02 (2011-01-20)
Parameters for Clock Source Quality

Parameter Clock Source Value Range Default Value Description This parameter indicates the name of the configured clock source. In Clock Source Priority, you can set whether to add or delete a clock source. 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.
Configuration Quality
Unknown Synchronization Quality G.811 Clock Signal G.812 Transit Clock Signal G.812 Local Clock Signal G.813 SDH Equipment Timing Source (SETS) Signal Do Not Use For Synchronization Automatic Extraction
Automatic Extraction
Clock Quality
This parameter indicates the clock source quality signal received by the NE. The NE extracts the clock source quality signal from the S1 byte of each clock source.
Parameters for Manual Setting of 0 Quality Level

Parameter NE Name Value Range Default Value Description This parameter indicates the name of the NE.
Issue 02 (2011-01-20)
B-477
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 synchronous equipment timing source (SETS) SETS Clock Between synchronous 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 avoid direct mutual locking of adjacent NEs. l G.811 Reference Clock: the clock signal specified in ITU-T G. 811. l Between G.811 Reference Clock and G.812 Transit Clock: lower than the quality level of the clock signal specified in ITU-T G.811 but higher than the quality level of the transit exchange clock signal specified in ITU-T G. 812. l G.812 Transit Clock: the transit exchange clock signal specified in ITU-T G.812. l Between G.812 Transit Clock and G. 812 Local Clock: 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
B-478
Issue 02 (2011-01-20)
Parameter
Value Range
Default Value
Description clock signal specified in ITU-T G.812. l Between G.812 Local Clock and synchronous equipment timing source (SETS): lower than the quality level of the local exchange 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 synchronous 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.
Related Tasks
A.8.1.3 Self-Defined Clock Quality
B.9.2.4 Parameter Description: Clock Subset Setting_SSM Output Control

This topic describes the parameters that are related to SSM output control.
Navigation Path
1. 2. Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Clock > Physical Clock > Clock Subnet Configuration. Click the SSM Output Control tab.
Issue 02 (2011-01-20)
B-479
Parameters
Parameter Line Port Value Range Default Value Description l This parameter indicates the name of the line clock port. l Line Port: indicates the SSM quality information output port of the current available line clock source and the external clock source. This output port can transmit the quality information of the clock source by outputting the S1 byte to the downstream NE. Control Status Enabled Disabled Enabled l This parameter is valid only when the SSM protocol or the extended SSM protocol is started. l This parameter indicates whether the SSM is output at the line port. l When the line port is connected to an NE in the same clock subnet, set this parameter to Enabled. Otherwise, set this parameter to Disabled.
Related Tasks
A.8.1.4 Configuring the SSM Output Status
B.9.2.5 Parameter Description: Clock Subset Setting_Clock ID Enabling Status

This topic describes the parameters that are used for enabling the clock ID function.
Navigation Path
1. Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Clock > Physical Clock > Clock Subnet Configuration.
B-480
2.
Click the Clock ID Status tab.
Parameters
Parameter Line Port Value Range Default Value Description l This parameter indicates the name of the line clock port. l Line Port: indicates the SSM quality information output port of the current available line clock source and the external clock source. This output port can transmit the quality information of the clock source by outputting the S1 byte to the downstream NE. Enabled Status Enabled Disabled Enabled l This parameter is valid only when the extended SSM protocol is started. l This parameter indicates whether the clock source ID is output at the line port. l If the line ports are connected to the NEs in the same clock subnet and if the extended SSM protocol is started on the opposite NE, this parameter is set to Enabled. Otherwise, this parameter is set to Disabled.
Related Tasks
A.8.1.5 Configuring the Clock ID Output Status
B.9.2.6 Parameter Description: Clock Source Switching_Clock Source Restoration Parameters

This topic describes the parameters that are related to clock source restoration.
Navigation Path
1. 2. Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Clock > Clock Source Switching. Click the Clock Source Reversion Parameter tab.
Parameters
Parameter NE Name Higher Priority Clock Source Reversion Mode Value Range Auto-Revertive Non-Revertive Default Value Auto-Revertive Description This parameter indicates the name of the NE. l When the quality of a higher-priority clock source degrades, the NE automatically switches the clock source to a lowerpriority clock source. If this parameter is set to Auto-Revertive, the NE automatically switches the clock source to the higherpriority clock source when this higherpriority clock source restores. If this parameter is set to Non-Revertive, the NE does not automatically switch the clock source to the 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 AutoRevertive. Otherwise, to prevent jitter of the clock, generally, it is recommended that you set this parameter to Non-Revertive.
B-482
Issue 02 (2011-01-20)
Parameter Clock Source WTR Time(min.)
Value Range 0 to 12
Default Value 5
Description 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.
Related Tasks
A.8.1.8 Modifying the Recovery Parameter of the Clock Source
B.9.2.7 Parameter Description: Clock Source Switching_Clock Source Switching

This topic describes the parameters that are related to the switching status of a clock source.
Navigation Path
1. 2. Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Clock > Physical Clock > Clock Source Switching. Click the Clock Source Switching tab.
Parameters
Parameter Clock Source Value Range Default Value Description This parameter indicates the name of the clock source. This parameter indicates whether the clock source is valid.
Effective Status
Valid Invalid
Issue 02 (2011-01-20)
B-483
Parameter Lock Status
Value Range Lock Unlock
Default Value -
Description l This parameter specifies the locking status of the clock source in the priority table. l Lock: A clock source in the priority table is in the locked state. The clock source in the locked state cannot be switched. l Unlock: A clock source in the priority table is in the unlocked state. The clock source in the unlocked state can be switched.
Switching Source
This parameter indicates the clock source to be traced by the NE after the switching. This parameter indicates the switching status of the current clock source.
Switching Status
Normal Manual Switching Forced Switching
B.9.2.8 Parameter Description: Clock Source Switching_Clock Source Switching Conditions

This section describes the parameters that are related to the switching conditions of clock sources.
Navigation Path
1. 2. In the NE Explorer, select the NE from the Object Tree and choose Configuration > Clock > Clock Source Switching from the Function Tree. Click the Clock Source Switching Condition tab.
Parameters
Parameter NE Name Clock Source Value Range Default Value Description Displays the name of the NE. Displays the clock source.
B-484
Issue 02 (2011-01-20)
Parameter AIS Alarm Generated
Value Range Yes No
Default Value No
Description l The default value is recommended. l When this parameter is set to Yes, it indicates that clock source switching occurs if the clock source reports the AIS alarm. l When this parameter is set to No, it indicates that no clock source switching occurs if the clock source reports the AIS alarm.
B1 BER ThresholdCrossing Generated RLOS,RLOF,OOF/ RLOC Alarms Generated
Yes
Yes
The parameter is invalid. This parameter indicates that clock switching occurs when the clock source reports the RLOS, RLOF, OOF, or LOC alarm. The parameter is invalid. The parameter is invalid. l The default value is recommended. l When this parameter is set to Yes, it indicates that clock source switching occurs if the clock source reports the B2-EXC alarm. l When this parameter is set to No, it indicates that no clock source switching occurs if the clock source reports the B2-EXC alarm.
CV Threshold-Crossing Generated CV Threshold B2-EXC Alarm Generated
Yes No
No
Related Tasks
A.8.1.7 Changing the Conditions for Clock Source Switching
Issue 02 (2011-01-20)
B-485
B.9.2.9 Parameter Description: Output Phase-Locked Source of the External Clock Source
This topic describes the parameters of the output phase-locked source of the external clock source.
Navigation Path
Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Clock > Physical Clock > Phase-Locked Source Output by External Clock.
Parameters
Parameter 2M Phase-Locked Source Number Value Range External Clock Source 1 Default Value Description This parameter indicates the number of the external clock source output of the NE. 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. Generally, the output external clock signal is a 2 Mbit/s signal. External Clock Output Timeslot SA4 to SA8 ALL 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 you use the default value.
External Clock Output Mode
2Mbit/s 2MHz
2Mbit/s
B-486
Issue 02 (2011-01-20)
Parameter External Source Output Threshold
Value Range Threshold Disabled Not Inferior to G.813 SETS Signal Not Inferior to G.812 Local Signal Not Inferior to G.812 Transit Clock Signal Not Inferior to G.811 Clock Signal
Default Value Threshold Disabled
Description 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 you use the default value.
2M Phase-Locked Source Fail Condition
No Failure Condition AIS LOF AIS OR LOF
No Failure Condition
l This parameter specifies the failure condition of the 2 Mbit/s phase-locked clock source. l It is recommended that you use the default value.
2M Phase-Locked Source Fail Action
Shut Down Output 2M Output S1 Byte Unavailable Send AIS
Shut Down Output
l This parameter is valid only when 2M PhaseLocked Source Fail Condition is not set to No Failure Condition. l This parameter specifies the operation of the 2 Mbit/s phaselocked loop (PLL) when the 2 Mbit/s phase-locked clock source meets the failure conditions. l It is recommended that you use the default value.
Issue 02 (2011-01-20)
B-487
Related Tasks
A.8.1.6 Modifying the Parameters of the Clock Output
B.9.2.10 Parameter Description: Clock Synchronization Status

This topic describes the parameters that are related to the clock synchronization status.
Navigation Path
Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Clock > Physical Clock > Clock Synchronization Status.
Parameters
Parameter NE Name NE Clock Working Mode S1 Byte Synchronization Quality Information Value Range Default Value Description This parameter indicates the name of the NE. This parameter indicates the working mode of the NE clock. This parameter indicates the synchronization quality information of the S1 byte. This parameter indicates the clock synchronization source of the S1 byte. This parameter indicates the synchronization source.
S1 Byte Synchronous Source Synchronous Source
B-488
Issue 02 (2011-01-20)
Parameter Data Output Method in Holdover Mode
Value Range Normal Data Output Mode Keep the Latest Data
Default Value Normal Data Output Mode
Description l When all the reference timing signals are lost, the slave clock changes to the holdover mode. At this time, the slave clock works based on the latest frequency information stored before the reference timing signals are lost. Then, the frequency of the oscillator drifts slowly to ensure that the offset between the frequency of the slave clock and the reference frequency is very small. As a result, the impact caused by the drift is limited within the specified requirement. l Normal Data Output Mode: The slave clock works based on the latest frequency information stored before the reference timing signals are lost, and the holdover duration depends on the size of the phaselocked clock register on the equipment. The holdover duration can be up to 24 hours. l Keep the Latest Data: The slave clock works in holdover mode all the time based on the latest frequency information stored before the reference timing signals are lost.
Related Tasks
A.8.1.9 Querying the Clock Synchronization Status
B.9.3 CES ACR Clock Parameters

This topic describes CES ACR clock parameters. B.9.3.1 Parameter Description: ACR Clock Source This topic describes parameters that are related to the ACR clock source. B.9.3.2 Parameter Description: Clock Domain This topic describes parameters that are related to clock domains. B.9.3.3 Parameter Description: Clock Domain_Creation This topic describes the parameters for creating a clock domain.
B.9.3.1 Parameter Description: ACR Clock Source

This topic describes parameters that are related to the ACR clock source.
Navigation Path
In the NE Explorer, select the required NE from the Object Tree and choose Configuration > Clock > ACR Clock from the Function Tree.

Parameter ACR Clock Source Value Range Default Value Description l Identifies the ACR clock domain. l This parameter is displayed in "slot IDboard ID-ACR clock ID" format. CES Service Displays or specifies the CES service that the master ACR clock source uses.
Related Tasks
B.9.3.2 Parameter Description: Clock Domain

This topic describes parameters that are related to clock domains.
Navigation Path
In the NE Explorer, select the required NE from the Object Tree and choose Configuration > Clock > Clock Domain from the Function Tree.

Parameter Clock Domain Clock Domain Board Value Range Default Value Description Displays the clock domain. Displays the board where the clock domain is located. Displays the E1 ports that are bound to a clock domain.
Clock Port
B.9.3.3 Parameter Description: Clock Domain_Creation

This topic describes the parameters for creating a clock domain.
Navigation Path
1. 2. In the NE Explorer, select the required NE from the Object Tree and choose Configuration > Clock > Clock Domain from the Function Tree. Click New.

Parameter Clock Domain Value Range System Clock Domain CES ACR1 Clock Domain CES ACR2 Clock Domain CES ACR3 Clock Domain CES ACR4 Clock Domain Clock Domain Board Displays the board where the clock domain is located. Specifies the board where the E1 port is located. Displays the E1 ports that are not bound to a clock domain. Default Value System Clock Domain Description Specifies the clock domain to be bound.
Board Available Port
Issue 02 (2011-01-20)
B-491
Parameter Selected Port
Value Range -
Default Value -
Description Displays the E1 ports that are bound to a clock domain.
Related Tasks
A.8.2.2 Configuring Ports Using the Clock Domain
B.10 Parameters for the Orderwire and Auxiliary Interfaces

This topic describes the parameters that are related to the orderwire and auxiliary interfaces. B.10.1 Parameter Description: Orderwire_General This topic describes the parameters that are used for general orderwire features. B.10.2 Parameter Description: Orderwire_Advanced This topic describes the parameters that are used for advanced orderwire features. B.10.3 Parameter Description: Orderwire_F1 Data Port This topic describes the parameters that are used for F1 data ports. B.10.4 Parameter Description: Orderwire_Broadcast Data Port This topic describes the parameters that are used for broadcast data ports. B.10.5 Parameter Description: Environment Monitoring Interface This topic describes the parameters that are used for environment monitoring interfaces.
B.10.1 Parameter Description: Orderwire_General

This topic describes the parameters that are used for general orderwire features.
Navigation Path
1. 2. Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Orderwire from the Function Tree. Click the General tab.
B-492
Issue 02 (2011-01-20)
Parameters
Parameter Call Waiting Time (s) Value Range 1 to 9 Default Value 9 Description l This parameter indicates the waiting time after the local station dials the number. If the calling station does not receive the response message from the called station within the call waiting time, it automatically removes the communication connection. l If less than 30 nodes exist in the orderwire subnet, it is recommended that you set this parameter to five seconds. If more than 30 nodes exist in the orderwire subnet, it is recommended that you set this parameter to nine seconds. l The call waiting time should be set to the same for all the NEs. Dialling Mode Pulse Dual-Tone Frequency Conference Call Dual-Tone Frequency This parameter indicates the dialling mode of the orderwire phone.
888
l This parameter indicates the telephone number of the network-wide orderwire conference call. l When an OptiX RTN 980 dials the telephone number 888, the orderwire phones of all the NEs on the orderwire subnet ring. When an OptiX RTN 980 receives the call, the orderwire phones on the other NEs do not ring. In this case, the orderwire point-to-multipoint group call changes to a point-to-point call between two NEs. l The telephone number of the orderwire conference call should be the same for all the nodes on the same subnet. l The telephone number of the orderwire conference call must have the same length as the telephone number of the orderwire phone (phone 1) at the local site.
Issue 02 (2011-01-20)
B-493
Parameter Phone 1
Default Value 101
Description l This parameter specifies the orderwire phone number of the local station. An addressing call refers to a point-to-point call. l The length of the orderwire phone number of each NE should be the same. It is recommended that you set the phone number to a three-digit number. l The orderwire phone number of each NE should be unique. It is recommended that the phone numbers are allocated from 101 for the NEs in a sequential order according to the NE IDs. l The orderwire phone number cannot be set to the group call number 888 and cannot start with 888.
Available Orderwire Port Selected Orderwire Port
This parameter indicates the available port for the orderwire phone. This parameter indicates the selected port for the orderwire phone.
Related Tasks
B.10.2 Parameter Description: Orderwire_Advanced

This topic describes the parameters that are used for advanced orderwire features.
Navigation Path
1. 2. Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Orderwire from the Function Tree. Click the Advanced tab.
B-494
Issue 02 (2011-01-20)
Parameters for Bytes Occupied by Orderwire Phones

Parameter Orderwire Occupied Bytes Value Range E1 E2 Default Value E1 Description l This parameter specifies the overhead byte that is used to transmit the orderwire signals. l Regardless the parameter value, the radio link always uses a customized overhead byte to transmit the orderwire signals. Hence, this parameter should be set according to the occupied SDH overhead bytes in the ordinary SDH.
Related Tasks
B.10.3 Parameter Description: Orderwire_F1 Data Port

This topic describes the parameters that are used for F1 data ports.
Navigation Path
1. 2. Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Orderwire from the Function Tree. Click the F1 Data Port tab.
Parameters
Parameter Available Data Path Value Range Default Value Description l This parameter indicates the available F1 data channel. l Two data channels should be selected for the configuration. Number Data Channel 1 This parameter indicates the number of the F1 data port. l If an SDH optical or electrical line port is selected, this parameter corresponds to the F1 byte in the SDH frame at the line port. l If an IF port is selected, this parameter corresponds to the customized F1 byte in the microwave frame at the IF port. l If F1 is selected, this parameter corresponds to the F1/S1 interface on the . The F1/S1 interface complies with
B-495
Issue 02 (2011-01-20)
Parameter Data Channel 2
Value Range
Default Value
Description ITU-T G.703 and operates at the rate of 64 kbit/s.
Related Tasks
A.10.2 Configuring the Synchronous Data Service
B.10.4 Parameter Description: Orderwire_Broadcast Data Port

This topic describes the parameters that are used for broadcast data ports.
Navigation Path
1. 2. Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Orderwire from the Function Tree. Click the Broadcast Data Port tab.
Parameters for Broadcast Data Ports

Parameter Overhead Byte Value Range SERIAL1 to SERIAL4 Default Value SERIAL1 Description l In the case of an SDH optical/electrical line, the preset overhead byte is used to transmit the asynchronous data services. l In the case of a radio link, a customized serial overhead byte in the microwave frame is used to transmit the asynchronous data services. Broadcast Data Source No Data l When this parameter is set to the SERIAL1, the F1/S1 interface on the corresponding is used. l When this parameter is set to the SDH optical/electrical line port, the value of Overhead Byte of this port is used. l When this parameter is set to the IF port, the customized Serial byte in the microwave frame of this port is used.
B-496
Issue 02 (2011-01-20)
Parameter Available Broadcast Data Sink Selected Broadcast Data Sink
Value Range -
Default Value -
Description This parameter indicates the available broadcast data sink. l When this parameter is set to the SERIAL1, the F1/S1 interface on the corresponding is used. l When this parameter is set to the SDH optical/electrical line port, the value of Overhead Byte of this port is used. l When this parameter is set to the IF port, the customized Serial byte in the microwave frame of this port is used.
Related Tasks
A.10.3 Configuring the Asynchronous Data Service
B.10.5 Parameter Description: Environment Monitoring Interface

This topic describes the parameters that are used for environment monitoring interfaces.
Navigation Path
Select the AUX board from the Object Tree in the NE Explorer. Choose Configuration > Environment Monitor Configuration > Environment Monitor Interface from the Function Tree.
Parameters for the Basic Attributes

Parameter Operation Object Relay Control Mode Value Range Auto Control Manual Control Default Value Auto Control Description This parameter indicates the operation object. l Auto Control: If an alarm is reported, the alarming relay is started up automatically. Otherwise, the alarming relay is shut down. l Manual Control: Relay Status in Major Alarm(K0) and Relay Status in Critical Alarm(K1) need to be set.
Issue 02 (2011-01-20)
B-497
Parameter Relay Status in Major Alarm(K0)
Description l This parameter indicates that the status of the relay is set manually for major alarms. l Enable: The relay is set to the "0N" status for major alarms. l Disabled: The relay is set to the "OFF" status for major alarms. l This parameter is valid only when Relay Control Mode is set to Manual Control.
Relay Status in Critical Alarm(K1)
Disabled Enabled
Disabled
l This parameter indicates that the status of the relay is set manually for critical alarms. l Enable: The relay is set to the enabled status for critical alarms. l Disabled: The relay is set to the disabled status for critical alarms. l This parameter is valid only when Relay Control Mode is set to Manual Control.
Parameters for the Input Relay

Parameter Operation Object Path Name Using Status Value Range Unused Used Alarm Mode Relay Turns Off/ High Level Relay Turns On/ Low Level Relay Turns Off/ High Level Default Value Unused Description This parameter indicates the operation object. This parameter indicates or specifies the name of the channel. This parameter specifies whether the alarm interface of the input relay is used. l If this parameter is set to Relay Turns Off/High Level, an alarm is generated when the relay is turned off. l If this parameter is set to Relay Turns On/Low Level, an alarm is generated when the relay is turned on. l This parameter is valid only when Using Status is set to Used.
B-498
Issue 02 (2011-01-20)
Parameter Alarm Severity
Value Range Critical Alarm Major Alarm Minor Alarm Warning Alarm
Default Value Critical Alarm
Description This parameter specifies the severity of the alarm that is generated at the input relay.
Parameters for the Output Relay

Parameter Operation Object Path Name Use or Not Value Range Unused Used Default Value Unused Description This parameter indicates the operation object. This parameter indicates or specifies the name of the output channel. This parameter specifies whether the alarm interface of the output relay is used.
Parameters for the Temperature Attributes

Parameter Operation Object Monitor Status Temperature Upper Threshold (Deg.C) Temperature Lower Threshold (Deg.C) Value Range Default Value Description This parameter indicates the operation object. This parameter indicates whether the temperature attribute is monitored. This parameter indicates the upper temperature threshold of the board. When the actual temperature is higher than the preset value, an alarm is generated. This parameter indicates the lower temperature threshold of the board. When the actual temperature is lower than the preset value, an alarm is generated.
Issue 02 (2011-01-20)
B-499
Parameters for the Alarm Relay

Parameter Alarm Severity Value Range Critical Alarm Major Alarm Minor Alarm Warning Alarm Alarm Output Channel CSK-1 CSK-2 CSK-3 CSK-4 Default Value Critical Alarm Major Alarm Minor Alarm Warning Alarm CSK-1 This parameter specifies the channel of the output alarm relay. Description This parameter indicates the severity of the alarm.
Related Tasks
A.10.5 Configure External Alarms
B-500
Issue 02 (2011-01-20)
C Glossary
C
Terms are listed in an alphabetical order. C.1 0-9 This section provides the terms starting with numbers. C.2 A-E This section provides the terms starting with letters A to E. C.3 F-J This section provides the terms starting with letters F to J. C.4 K-O This section provides the terms starting with letters K to O. C.5 P-T This section provides the terms starting with letters P to T. C.6 U-Z This section provides the terms starting with letters U to Z.
Glossary
Issue 02 (2011-01-20)
C-1
C Glossary
C.1 0-9
This section provides the terms starting with numbers. 1U The standard electronics industries association (EIA) rack unit (44 mm/1.75 in.)
C.2 A-E
This section provides the terms starting with letters A to E.
A
ABR ACAP access control list ACL adaptive modulation See available bit rate See adjacent channel alternate polarization A list of entities, together with their access rights, which are authorized to have access to a resource. 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 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. 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 A collection of objects that makes a whole. An aggregation can be a concrete or conceptual set of whole-part relationships among objects.
ADC add/drop multiplexer
Address Resolution Protocol
adjacent channel alternate polarization ADM administrative unit
AF aggregation
C-2
C Glossary
AIS
See alarm indication signal
alarm automatic report When an alarm is generated on the device side, the alarm is reported to the Network Management System (NMS). Then, an alarm panel prompts and the user can view the details of the alarm. alarm cascading Alarm Filtering 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.
alarm indication signal 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. alarm suppression 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 One of the four per-hop behaviors (PHB) defined by the Diff-Serv workgroup of IETF. It is suitable for certain key data services that require assured bandwidth and short delay. For traffic within the bandwidth limit, AF assures quality in forwarding. For traffic that exceeds the bandwidth limit, AF degrades the service class and continues to forward the traffic instead of discarding the packets. A protocol for the transmission of a variety of digital signals using uniform 53 byte cells. A transfer mode in which the information is organized into cells; it is asynchronous in the sense that the recurrence of cells depends on the required or instantaneous bit rate. Statistical and deterministic values may also be used to qualify the transfer mode. See Asynchronous Transfer Mode ATM permanent virtual circuit See automatic transmit power control A device used to increase the attenuation of an Optical Fiber Link. Generally used to ensure that the signal at the receive end is not too strong. See administrative unit 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.
AM analog to digital converter APS ARP assured forwarding
Asynchronous Transfer Mode
ATM ATM PVC ATPC attenuator AU automatic protection switching automatic transmit power control available bit rate
Issue 02 (2011-01-20)
C-3
C Glossary
B
backward defect indication bandwidth When detecting a defect, the sink node of an 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. 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 station controller
base transceiver station 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. basic input/output system BDI BE BER best effort A firmware stored in the computer mainboard. It contains basic input/output control programs, power-on self test (POST) programs, bootstraps, and system setting information. The BIOS provides hardware setting and control functions for the computer. See backward defect indication See best effort See bit error rate A traditional IP packet transport service. In this service, the diagrams are forwarded following the sequence of the time they reach. All diagrams share the bandwidth of the network and routers. The amount of resource that a diagram can use depends of the time it reaches. BE service does not ensure any improvement in delay time, jitter, packet loss ratio, and high reliability. The binding strap is 12.7 mm wide, with one hook side (made of transparent polypropylene material) and one mat side (made of black nylon material). See basic input/output system See bit interleaved parity An incompatibility between a bit in a transmitted digital signal and the corresponding bit in the received digital signal. Ratio of received bits that contain errors. BER is an important index used to measure the communications quality of a network. A method of error monitoring. With even parity an X-bit code is generated by the transmitting equipment over a specified portion of the signal in such a manner that the first bit of the code provides even parity over the first bit of all X-bit sequences in the covered portion of the signal, the second bit provides even parity over the second bit of all X-bit sequences within the specified portion, etc. Even parity is generated by setting the BIP-X bits so that there is an even number of 1s in each monitored partition of the signal. A monitored partition comprises all bits which are in the same bit position within the X-bit sequences in the covered portion of the signal. The covered portion includes the BIP-X. See bridge protocol data unit
binding strap BIOS BIP bit error bit error rate bit interleaved parity
BPDU
C-4
Issue 02 (2011-01-20)
C Glossary
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. In a program, buffers are created to hold some amount of data from each of the files that will be read or written. In a streaming media application, the program uses buffers to store an advance supply of audio or video data to compensate for momentary delays.
broadcast BSC BTS buffer
C
cable tie cable tray cable trough CAR CBR CBS CC CCC CCDP CCM CE The tape used to bind the cables. N/A N/A See committed access rate See constant bit rate See committed burst size See connectivity check See circuit cross connect See co-channel dual polarization See continuity check message See customer edge
central processing unit The computational and control unit of a computer. The CPU is the device that interprets and executes instructions. The CPU has the ability to fetch, decode, and execute instructions and to transfer information to and from other resources over the computer's main data-transfer path, the bus. CES CF CGMP channel See circuit emulation service See compact flash See Cisco Group Management Protocol A telecommunication path of a specific capacity and/or at a specific speed between two or more locations in a network. The channel can be established through wire, radio (microwave), fiber or a combination of the three. The amount of information transmitted per second in a channel is the information transmission speed, expressed in bits per second. For example, b/s (100 bit/s), kb/s (103 bit/s), Mb/s (106 bit/s), Gb/s (109 bit/s), and Tb/s (1012 bit/s).
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. C-5
Issue 02 (2011-01-20)
C 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. N/A See common and internal spanning tree A switch of the highest priority is elected as the root in an MSTP network. 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. 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. committed burst size. A parameter used to define the capacity of token bucket C, that is, the maximum burst IP packet size when the information is transferred at the committed information rate. This parameter must be larger than 0. It is recommended that this parameter should be not less than the maximum length of the IP packet that might be forwarded.
Cisco Group Management Protocol CIST CIST root clock tracing co-channel dual polarization coarse wavelength division multiplexing colored packet committed access rate
committed burst size
committed information The rate at which a frame relay network agrees to transfer information in normal rate conditions. Namely, it is the rate, measured in bit/s, at which the token is transferred to the leaky bucket. common and internal spanning tree compact flash The single spanning tree calculated by STP and RSTP together with the logical continuation of that connectivity by using MST Bridges and regions, calculated by MSTP to ensure that all LANs in the bridged local area network are simply and fully connected. 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. Ethernet CFM can detect the connectivity between MEPs. The detection is achieved by each MEP transmitting a Continuity Check Message (CCM) periodically.
concatenation connectivity check
C-6
Issue 02 (2011-01-20)
C Glossary
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. CCM is used to detect the link status. Used to protect optical fibers. See central processing unit 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. 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.
continuity check message corrugated pipe CPU CRC cross polarization interference cancellation customer edge CWDM cyclic redundancy check
D
data communication network data communications channel A communication network used in a TMN or between TMNs to support the Data Communication Function (DCF). The data channel that uses the D1-D12 bytes in the overhead of an STM-N signal to 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. 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) DC-return common (with ground) 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 also on the line between the output of the power supply cabinet and the electric equipment.
Datagram DC DC-C DC-C DC-C DC-I DC-return common (with ground) DC-return common (with ground)
Issue 02 (2011-01-20)
C Glossary
DC-return isolate (with A power system, in which the BGND of the DC return conductor is short-circuited with ground) the PGND on the output side of the power supply cabinet and is isolated from the PGND on the line between the output of the power supply cabinet and the electric equipment. DCC DCN DDF DDN DE differentiated services See data communications channel See data communication network See digital distribution frame See digital data network See discard eligible 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. A marker in the header of each IP packet that prompts network routers to apply differentiated grades of service to various packet streams. It is specified by the DiffServ policy proposed by the IETF (Internet Engineering Task Force). This allows Internet and other IP-based network service providers to offer different levels of service to customers. 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. 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. 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
differentiated services code point
DiffServ digital data network
digital distribution frame digital modulation
direct current discard eligible
Distance Vector Multicast Routing Protocol DS boundary node DS domain
DS interior node DS node DSCP
C-8
Issue 02 (2011-01-20)
C Glossary
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-Line E-Tree EBS ECC EF electromagnetic compatibility See Ethernet aggregation See Ethernet LAN See Ethernet line See Ethernet-tree See excess burst size See embedded control channel See expedited forwarding 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. Any electromagnetic disturbance that interrupts, obstructs, or otherwise degrades or limits the effective performance of electronics/electrical equipment. 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. A logical channel that uses a data communications channel (DCC) as its physical layer, to enable transmission of operation, administration, and maintenance (OAM) information between NEs. See electromagnetic compatibility See electromagnetic interference A mark on a cable, a subrack, or a cabinet for identification. See Ethernet private line See Ethernet private LAN service 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 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. 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. 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..
electromagnetic interference electrostatic discharge embedded control channel EMC EMI Engineering label EPL EPLAN equalization ERPS ESD ESD jack Ethernet
Ethernet
Issue 02 (2011-01-20)
C-9
C Glossary
Ethernet aggregation Ethernet LAN Ethernet line Ethernet private LAN service Ethernet private line Ethernet ring protection switching Ethernet virtual private LAN service Ethernet virtual private line Ethernet-tree ETS ETSI European Telecommunications Standards Institute EVPL EVPLAN excess burst size
A type of Ethernet service that is based on a multipoint-to-point EVC (Ethernet virtual connection). A type of Ethernet service that is based on a multipoint-to-multipoint EVC (Ethernet virtual connection). A type of Ethernet service that is based on a point-to-point EVC (Ethernet virtual connection). An Ethernet service type, which carries Ethernet characteristic information over a dedicated bridge, point-to-multipoint connections, provided by SDH, PDH, ATM, or MPLS server layer networks. A type of Ethernet service that is provided with dedicated bandwidth and point-to-point connections on an SDH, PDH, ATM, or MPLS server layer network. protection switching mechanisms for ETH layer Ethernet ring topologies. An Ethernet service type, which carries Ethernet characteristic information over a shared bridge, point-to-multipoint connections, provided by SDH, PDH, ATM, or MPLS server layer networks. An Ethernet service type, which carries Ethernet characteristic information over shared bandwidth, point-to-point connections, provided by SDH, PDH, ATM, or MPLS server layer networks. An Ethernet service type that is based on a Point-to-multipoint Ethernet Virtual Connection. European Telecommunication Standards See European Telecommunications Standards Institute A standards-setting body in Europe. Also the standards body responsible for GSM.
See Ethernet virtual private line See Ethernet virtual private LAN service A parameter related to traffic. In the single rate three color marker (srTCM) mode, the traffic control is achieved by the token buckets C and E. Excess burst size is a parameter used to define the capacity of token bucket E, that is, the maximum burst IP packet size when the information is transferred at the committed information rate. This parameter must be larger than 0. It is recommended that this parameter should be not less than the maximum length of the IP packet that might be forwarded. An operation to check if the protection switching protocol functions normally. The protection switching is not really performed. Connecting a storage system to more disk enclosures through connection cables, thus expanding the capacity of the storage system. 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".
Exercise Switching expansion expedited forwarding
C-10
Issue 02 (2011-01-20)
C Glossary
C.3 F-J
This section provides the terms starting with letters F to 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. Any network that supports transmission rate of 100Mbits/s. The Fast Ethernet is 10 times faster than 10BaseT, and inherits frame format, MAC addressing scheme, MTU, and so on. Fast Ethernet is extended from the IEEE802.3 standard, and it uses the following three types of transmission media: 100BASE-T4 (4 pairs of phone twisted-pair cables), 100BASE-TX (2 pairs of data twisted-pair cables), and 100BASE-FX (2-core optical fibers). The link pulse that is used to encode information during automatic negotiation. See frequency diversity See forward defect indication See fast Ethernet See forward error correction fast failure detection 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 arrays. 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. For normal traffic signals, switches normal traffic signal to the protection section, unless an equal or higher priority switch command is in effect or SF condition exists on the protection section, by issuing a forced switch request for that traffic signal. 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.
fast Ethernet
fast link pulse FD FDI FE FEC FFD fiber patch cord field programmable gate array
FIFO File Transfer Protocol
First in First out Forced switch
forward defect indication
forward error correction
Issue 02 (2011-01-20)
C Glossary
Forwarding plane FPGA fragment Fragmentation frame
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 cannot 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 A full-duplex, or sometimes double-duplex system, allows communication in both directions, and, unlike half-duplex, allows this to happen simultaneously. Land-line telephone networks are full-duplex, since they allow both callers to speak and be heard at the same time. A good analogy for a full-duplex system would be a two-lane road with one lane for each direction.
frequency diversity
FTP full-duplex
G
gateway network element GE generic framing procedure A network element that is used for communication between the NE application layer and the NM application layer See gigabit Ethernet A framing and encapsulated method which can be applied to any data type. It has been standardized by ITU-T SG15.
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 See generic framing procedure GE adopts the IEEE 802.3z. GE is compatible with 10 Mbit/s and 100 Mbit/s Ethernet. It runs at 1000 Mbit/s. Gigabit Ethernet uses a private medium, and it does not support coaxial cables or other cables. It also supports the channels in the bandwidth mode. If Gigabit Ethernet is, however, deployed to be the private bandwidth system with a bridge (switch) or a router as the center, it gives full play to the performance and the bandwidth. In the network structure, Gigabit Ethernet uses full duplex links that are private, causing the length of the links to be sufficient for backbone applications in a building and campus. A global navigation satellite system. It provides reliable positioning, navigation, and timing services to worldwide users. See gateway network element See Global Positioning System
Global Positioning System GNE GPS
C-12
Issue 02 (2011-01-20)
C Glossary
graphical user interface A visual computer environment that represents programs, files, and options with graphical images, such as icons, menus, and dialog boxes, on the screen. GTS GUI guide rail See generic traffic shaping See graphical user interface Components to guide, position, and support plug-in boards.
H
HA half-duplex 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. See high level data link control A type of QoS that can control the traffic of users, and perform the scheduling according to the priority of user services. HQoS has a perfect traffic statistics function, and the administrator can monitor the usage of bandwidth of each service. Hence, the bandwidth can be allocated reasonably through traffic analysis. Typically, a scheme in which two modules operate in active/standby mode to achieve high availability. When the active module fails, the standby module automatically takes over the system functions of the active module. The HDLC protocol is a general purpose protocol which operates at the data link layer of the OSI reference model. Each piece of data is encapsulated in an HDLC frame by adding a trailer and a header. 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. In an SDH network, the higher order path layers provide a server network from the lower order path layers. 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. See higher order path See hierarchical quality of service See hot standby See High Speed Downlink Packet Access
HDLC hierarchical quality of service
high availability
high level data link control High Speed Downlink Packet Access
higher order path Hold priority
hop hot standby
HP HQoS HSB HSDPA

Issue 02 (2011-01-20)
C Glossary
HSM HTB hybrid radio
hitless switch mode high tributary bus The hybrid transmission of Native E1 and Native Ethernet signals. Hybrid radio supports the AM function.
I
ICMP IDU IEC IEEE IETF IF IGMP IGMP snooping See Internet Control Message Protocol See indoor unit See International Electrotechnical Commission See Institute of Electrical and Electronics Engineers See 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.
IMA indoor unit Inloop Institute of Electrical and Electronics Engineers
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) to determine the best way to forward Intermediate System datagrams or packets through a packet-based network, a process called routing. routing protocol internal spanning tree International Electrotechnical Commission International Organization for Standardization A segment of CIST in a certain MST region. An IST is a special MSTI whose ID is 0. The International Electrotechnical Commission (IEC) is an international and nongovernmental standards organization dealing with electrical and electronic standards. An international association that works to establish global standards for communications and information exchange. Primary among its accomplishments is the widely accepted ISO/OSI reference model, which defines standards for the interaction of computers connected by communications networks.
C-14
Issue 02 (2011-01-20)
C Glossary
International Telecommunication UnionTelecommunication Standardization Sector Internet Control Message Protocol
An international body that develops worldwide standards for telecommunications technologies. These standards are grouped together in series which are prefixed with a letter indicating the general subject and a number specifying the particular standard. For example, X.25 comes from the "X" series which deals with data networks and open system communications and number "25" deals with packet switched networks. A network-layer (ISO/OSI level 3) Internet protocol that provides error correction and other information relevant to IP packet processing. For example, it can let the IP software on one machine inform another machine about an unreachable destination. See also communications protocol, IP, ISO/OSI reference model, packet (definition 1). A worldwide organization of individuals interested in networking and the Internet. Managed by the Internet Engineering Steering Group (IESG), the IETF is charged with studying technical problems facing the Internet and proposing solutions to the Internet Architecture Board (IAB). The work of the IETF is carried out by various working groups that concentrate on specific topics, such as routing and security. The IETF is the publisher of the specifications that led to the TCP/IP protocol standard. 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. 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). IPv6 is also called. It is a new version of the Internet Protocol, designed as the successor to IPv4. The difference between IPv6 and IPv4 is that an IPv4 address has 32 bits while an IPv6 address has 128 bits. 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). IPv6 is also called. It is a new version of the Internet Protocol, designed as the successor to IPv4. The difference between IPv6 and IPv4 is that an IPv4 address has 32 bits while an IPv6 address has 128 bits. The ATM inverse multiplexing technique involves inverse multiplexing and demultiplexing 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 Internet protocol version 6 See Intermediate System to Intermediate System routing protocol See International Organization for Standardization See internal spanning tree See International Telecommunication Union-Telecommunication Standardization Sector
Internet Engineering Task Force
Internet Group Management Protocol Internet Protocol
Internet protocol version 6
Internet protocol version 6
inverse multiplexing over ATM
IP IPV6 IPv6 IS-IS ISO IST ITU-T
Issue 02 (2011-01-20)
C-15
C Glossary
J
Jitter Short waveform variations caused by vibration, voltage fluctuations, and control system instability.
C.4 K-O
This section provides the terms starting with letters K to 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. 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. See Link Aggregation Control Protocol See link aggregation group See local area network See local area network link access protocol-SDH 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.
label switching router
LACP LAG LAN LAN LAPS Laser
layer 2 switch
Layer 2 virtual private A virtual private network achieved by Layer 2 switching technologies in the packet network switched (IP/MPLS) network. LB LCAS LCT line rate line rate forwarding Link Aggregation Control Protocol See loopback See link capacity adjustment scheme local craft terminal The maximum packet forwarding capacity on a cable. The value of line rate equals the maximum transmission rate capable on a given type of media. The line rate equals the maximum transmission rate capable on a given type of media. A method of bundling a group of physical interfaces together as a logical interface to increase bandwidth and reliability. For related protocols and standards, refer to IEEE 802.3ad.
C-16
Issue 02 (2011-01-20)
C Glossary
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 client can treat the link aggregation group as if it were a single link. link capacity adjustment scheme LCAS in the virtual concatenation source and sink adaptation functions provides a control mechanism to hitlessly increase or decrease the capacity of a link to meet the bandwidth needs of the application. It also provides a means of removing member links that have experienced failure. The LCAS assumes that in cases of capacity initiation, increases or decreases, the construction or destruction of the end-to-end path is the responsibility of the Network and Element Management Systems. 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). 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. 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. lower order path link-state pass through See label switched path
Link Protection
LMSP local area network
local area network
Locked switching
LOF LOM loopback LOP LOS Loss Of Frame
loss of pointer
Loss Of Signal LP LPT LSP
Issue 02 (2011-01-20)
C-17
C Glossary
LSR
See label switching router
M
MA MAC MAC MADM main topology See maintenance association See media access control See media access control multiple add/drop multiplexer A interface that displays the connection relation of NEs on the NMS (screen display). The default client interface of the NMS, a basic component of the human-machine interactive interface. The topology clearly shows the structure of the network, the alarms of different NEs, subnets in the network, the communication status as well as the basic network operation status. All topology management functions are accessed here. 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 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. Switches normal traffic signal to the protection section, unless a failure condition exists on other sections (including the protection section) or an equal or higher priority switch command is in effect, by issuing a manual switch request for that normal traffic signal.
maintenance association maintenance association end point
maintenance domain maintenance point management information base manual switch
maximum transmission The largest packet of data that can be transmitted on a network. MTU size varies, unit depending on the network576 bytes on X.25 networks, for example, 1500 bytes on Ethernet, and 17,914 bytes on 16 Mbps Token Ring. Responsibility for determining the size of the MTU lies with the link layer of the network. When packets are transmitted across networks, the path MTU, or PMTU, represents the smallest packet size (the one that all networks can transmit without breaking up the packet) among the networks involved. MBS MCF MD MDI Mean Time Between Failures Mean Time To Repair maximum burst size See message communication function See maintenance domain See medium dependent interface The average time between consecutive failures of a piece of equipment. It is a measure of the reliability of the system. The average time that a device will take to recover from a failure.
C-18
Issue 02 (2011-01-20)
C 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 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. The electrical and mechanical interface between the equipment and the media transmission. See maintenance association end point maintenance 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 A piece of angle plate with holes in it on a rack. It is used to fix network elements or components. See maintenance point maintenance point identification See Multiprotocol Label Switching 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. See multiprotocol label switching traffic engineering
media access control
medium dependent interface MEP MEP message communication function MIB MIP mounting ear MP MPID MPLS MPLS L2VPN
MPLS OAM
MPLS TE
Issue 02 (2011-01-20)
C-19
C Glossary
MPLS TE tunnel
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 See Multiple Spanning Tree Protocol See Mean Time Between Failures See Mean Time To Repair See maximum transmission unit 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 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 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. 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. N/A
MS MSP MSTP MTBF MTTR MTU Multicast
Multiple Spanning Tree Protocol
multiplex section multiplex section protection Multiprotocol Label Switching
multiprotocol label switching traffic engineering
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 NMS, which is used to manage the telecommunication equipment. In the NE Explorer, the user can query, manage and maintain the NE, boards, and ports on a per-NE basis.
C-20
Issue 02 (2011-01-20)
C 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 and communication(SCC) board which manages and monitors the entire network element. The NE software runs on the SCC board.
Network Management A system in charge of the operation, administration, and maintenance of a network. 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 NNI node 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 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
Node Protection
non-gateway network element non-GNE NSAP NSF
O
OAM ODF ODU OM One-to-One Backup See operation, administration and maintenance See optical distribution frame See outdoor unit Operation and maintenance A local repair method in which a backup tunnel is separately created for each protected tunnel at a PLR.
open shortest path first 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 02 (2011-01-20)
C-21
C Glossary
Open Systems Interconnection
A framework of ISO standards for communication between different systems made by different vendors, in which the communications process is organized into seven different categories that are placed in a layered sequence based on their relationship to the user. Each layer uses the layer immediately below it and provides a service to the layer above. Layers 7 through 4 deal with end-to-end communication between the message source and destination, and layers 3 through 1 deal with network functions. 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 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 an optical source (or a detector).+ 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 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 a port to an output port without changing the structure of the signals. The ranger of optical energy level of output signals.
operation, administration and maintenance
optic fiber connector
optical distribution frame orderwire OSI OSPF outdoor unit Outloop Output optical power
C.5 P-T
This section provides the terms starting with letters P to T.
P
packet switched network Packing case Path A telecommunication network which works in packet switching mode. A case which is used for packing the board or subrack. A performance resource object defined in the network management system. The left end of a path is a device node whose port needs to be specified and the right end of a path is a certain IP address which can be configured by the user. By defining a path in the network management system, a user can test the performance of a network path between a device port and an IP address. The tested performance may be the path delay, packet loss ratio or other aspects. See peak burst size See printed circuit board
PBS PCB
C-22
Issue 02 (2011-01-20)
C Glossary
PCI bus PDH PDU PE peak burst size
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 See protocol data unit See provider edge 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. A traffic parameter, expressed in bit/s, whose value should be not less than the committed information rate. 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). IETF Diff-Serv workgroup defines forwarding behaviors of network nodes as per-hop behaviors (PHB), such as, traffic scheduling and policing. A device in the network should select the proper PHB behaviors, based on the value of DSCP. At present, the IETF defines four types of PHB. They are class selector (CS), expedited forwarding (EF), assured forwarding (AF), and best-effort (BE). See per-hop behavior See penultimate hop popping See peak information rate A multiplexing scheme of bit stuffing and byte interleaving. It multiplexes the minimum rate 64 kit/s into the 2 Mbit/s, 34 Mbit/s, 140 Mbit/s, and 565 Mbit/s rates.
peak information rate penultimate hop popping
per-hop behavior
PHB PHP PIR plesiochronous digital hierarchy
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. 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 See priority queue See 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.
Power box PPP PQ PRBS PRC printed circuit board
Issue 02 (2011-01-20)
C-23
C Glossary
priority queue
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 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. It is a data packet at the network layer of the OSI model. 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.
protection ground cable Protection path protocol data unit provider edge
pseudo random binary A sequence that is random in a sense that the value of an element is independent of the sequence values of any of the other elements, similar to real random sequences. pseudo wire 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 A type of end-to-end Layer 2 transmitting technology. It emulates the essential attributes edge-to-edge 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. PSN PTN PW PWE3 See packet switched network packet transport network See pseudo wire See pseudo wire emulation edge-to-edge
Q
QinQ A layer 2 tunnel protocol based on IEEE 802.1Q encapsulation. It encapsulates the tag of the user's private virtual local area network (VLAN) into the tag of the public VLAN. The packet carries two layers of tags to travel through the backbone network of the carrier. In this manner, the layer 2 virtual private network (VPN) is provided for the user. See quality of service See quadrature phase shift keying
QoS QPSK
quadrature phase shift A modulation method of data transmission through the conversion or modulation and keying the phase determination of the reference signals (carrier). It is also called the fourth period or 4-phase PSK or 4-PSK. QPSK uses four dots in the star diagram. The four dots are evenly distributed on a circle. On these phases, each QPSK character can perform twobit coding and display the codes in Gray code on graph with the minimum BER.
C-24
Issue 02 (2011-01-20)
C Glossary
quality of service
A commonly-used performance indicator of a telecommunication system or channel. Depending on the specific system and service, it may relate to jitter, delay, packet loss ratio, bit error ratio, and signal-to-noise ratio. It functions to measure the quality of the transmission system and the effectiveness of the services, as well as the capability of a service provider to meet the demands of users.
R
radio frequency 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 in the RNS which is in charge of controlling the use and the integrity of the radio resources.
radio network controller
random early detection 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. Rapid Spanning Tree Protocol RDI received signal level Received Signal Strength Indicator Receiver Sensitivity RED Reed-Solomon-Code 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 signal level at a receiver input terminal. 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-12 BER (The FEC is open). See random early detection A forward error correction code located before interleaving that enables correction of errors induced by burst noise. Widely used error correction scheme to fight transmission errors at the receiver site. 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.
REI remote defect indication
remote error indication 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. Request For Comments A document in which a standard, a protocol, or other information pertaining to the operation of the Internet is published. The RFC is actually issued, under the control of the IAB, after discussion and serves as the standard. RFCs can be obtained from sources such as InterNIC.
Issue 02 (2011-01-20)
C-25
C Glossary
Resource Reservation Protocol
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 frequency See Request For Comments See Routing Information Protocol remote network monitoring 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. A mapping table that stores the relationship between the original address, destination address, short message (SM) protocol type and account. The SMSC delivers an SM to the designated account according to the information set in the route table. 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. See received signal level See Received Signal Strength Indicator See Rapid Spanning Tree Protocol See Resource Reservation Protocol radio transmission node
reverse pressure
RF RFC RIP RMON RMON RNC Root alarm route route table
Routing Information Protocol
routing table
RSL RSSI RSTP RSVP RTN
S
SD SDH SEMF See space diversity See synchronous digital hierarchy See synchronous equipment management function
C-26
Issue 02 (2011-01-20)
C Glossary
service level agreement A service contract between a customer and a service provider that specifies the forwarding service a customer should receive. A customer may be a user organization (source domain) or another differentiated services domain (upstream domain). A SLA may include traffic conditioning rules which constitute a traffic conditioning agreement as a whole or partially. Service Level Agreement * 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. See 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.
SES Setup Priority
severely errored second A one-second period which has a bit error ratio X 10-3 or at least one defect. Time interval of one second during which a given digital signal is received with an error ratio greater than 1 X 10 -3 (Rec. ITU R F. 592 needs correction). SF SFP side trough signal cable signal fail signal to noise ratio See signal fail See small form-factor pluggable 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 E1 cable, network cable, and other non-subscriber signal cable. A signal that indicates the associated data has failed in the sense that a near-end defect condition (non-degrade defect) is active. The ratio of the amplitude of the desired signal to the amplitude of noise signals at a given point in time. SNR is expressed as 10 times the logarithm of the power ratio and is usually expressed in dB (Decibel). 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. Designating or pertaining to a method of operation in which information can be transmitted in either direction, but not simultaneously, between two points. See service level agreement 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
Simple Network Management Protocol
simplex SLA SLA* Slicing small form-factor pluggable SNC
Issue 02 (2011-01-20)
C-27
C Glossary
SNCP SNMP SNR space diversity
See subnetwork connection protection See Simple Network Management Protocol See signal to noise ratio 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.
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 STM-N STP sub-network See Synchronous Transport Module See synchronous transport mode-1 See synchronous transport module of order N 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.
subnet mask
subnetwork connection A "transport entity" that transfers information across a subnetwork, it is formed by the association of "ports" on the boundary of the subnetwork. subnetwork connection A function, which allows a working subnetwork connection to be replaced by a protection protection subnetwork connection if the working subnetwork connection fails, or if its performance falls below a required level. SVC switch See static virtual circuit 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.
C-28
Issue 02 (2011-01-20)
C Glossary
Synchronization Status A message that carries quality levels of timing signals on a synchronous timing link. Message Nodes on an SDH network and a synchronization network acquire upstream clock information through this message. Then the nodes can perform proper operations on their clocks, such as tracing, switching, or converting to holdoff), and forward the synchronization information to downstream nodes. synchronous digital hierarchy A transmission scheme that follows ITU-T G.707, G.708, and G.709. It defines the transmission features of digital signals such as frame structure, multiplexing mode, transmission rate level, and interface code. SDH is an important part of ISDN and BISDN. It interleaves the bytes of low-speed signals to multiplex the signals to high-speed counterparts, and the line coding of scrambling is used only for signals. SDH is suitable for the fiber communication system with high speed and a large capacity since it uses synchronous multiplexing and flexible mapping structure. The SEMF converts performance data and implementation specific hardware alarms into object-oriented messages for transmission over DCCs and/or a Q interface.
synchronous equipment management function
synchronous transport Synchronous Transfer Mode at 155 Mbit/s. mode-1 Synchronous Transport Module 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 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.
synchronous transport A STM-N is the information structure used to support section layer connections in SDH. See ITU-T Recommendation G. 707 for STM modules of order 1, 4, 16 and 64. module of order N
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 Transmission Control Protocol See time division multiplexing See traffic engineering See traffic engineering database
Tail drop
TCI TCP TDM TE TEDB
Telecommunication A protocol model defined by ITU-T for managing open systems in a communications Management Network network. An architecture for management, including planning, provisioning, installation, maintenance, operation and administration of telecommunications equipment, networks and services.
Issue 02 (2011-01-20) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. C-29
C Glossary
TIM time division multiplexing
trace identifier mismatch 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 technology that is used to dynamically monitor the traffic of the network and the load of the network elements, to adjust in real time the parameters such as traffic management parameters, route parameters and resource restriction parameters, and to optimize the utilization of network resources. The purpose is to prevent the congestion caused by unbalanced loads. 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. 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.
time to live
TMN ToS priority TPS traffic engineering
traffic engineering database
Traffic shaping
Transmission Control Protocol
tributary protection switch trTCM TTL TU Tunnel
C-30
Issue 02 (2011-01-20)
C Glossary
two rate three color marker
The trTCM meters an IP packet stream and marks its packets based on two rates, Peak Information Rate (PIR) and Committed Information Rate (CIR), and their associated burst sizes to be either green, yellow, or red. A packet is marked red if it exceeds the PIR. Otherwise it is marked either yellow or green depending on whether it exceeds or doesn't exceed the CIR.
C.6 U-Z
This section provides the terms starting with letters U to Z.
U
U-VLAN UAS UBR UDP underfloor cabling UNI unicast unspecified bit rate A VLAN attribute indicating that the current VLAN is a user VLAN of an M-VLAN. Multicast services are copied from the M-VLAN to the user VLAN. 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. An operation to report some or all configuration data of an NE to the NMS(Network Management system). The configuration data then covers the configuration data stored at the NMS side. 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.
upload
User Datagram Protocol
user network interface The interface between user equipment and private or public network equipment (for example, ATM switches).
V
V-UNI variable bit rate 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 container
VBR VC
Issue 02 (2011-01-20)
C Glossary
VCC VCG VCI VCTRUNK virtual channel connection virtual channel identifier virtual concatenation group virtual container
See virtual channel connection See virtual concatenation group See virtual channel identifier A virtual concatenation group applied in data service mapping, also called the internal port of a data service processing board 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. 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 The information structure used to support path layer connections in the SDH. It consists of information payload and path Overhead (POH) information fields organized in a block frame structure which repeats every 125 or 500 s. 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. The field in the Asynchronous Transfer Mode (ATM) cell header that identifies to which virtual path the cell belongs. A type of point-to-multipoint L2VPN service provided over the public network. VPLS enables geographically isolated user sites to communicate with each other through the MAN/WAN as if they are on the same LAN.
virtual local area network virtual path identifier virtual private LAN service
virtual private network A system configuration, where the subscriber is able to build a private network via connections to different network switches that may include private network capabilities. virtual route forward VRF performs the function of establishing multiple virtual routing devices on one actual routing device. That is, the L3 interfaces of the device are distributed to different VRFs, performing the function of establishing multiple virtual route forwarding instances on the device. A virtual user-network interface, works as an action point to perform service classification and traffic control in HQoS. See virtual local area network 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 route forward
virtual user-network interface VLAN voice over IP
VoIP VPI VPLS VPN VRF
C-32
Issue 02 (2011-01-20)
C Glossary
W
wait to restore WAN Web LCT weighted fair queuing The number of minutes to wait before services are switched back to the working line. See wide area network The local maintenance terminal of a transport network, which is located on the NE management layer of the transport network A fair queue scheduling algorithm based on bandwidth allocation weights. This scheduling algorithm allocates the total bandwidth of an interface to queues, according to their weights and schedules the queues cyclically. In this manner, packets of all priority queues can be scheduled.
weighted random early A packet loss algorithm used for congestion avoidance. It can prevent the global TCP detection synchronization caused by traditional tail-drop. WRED is favorable for the high-priority packet when calculating the packet loss ratio. weighted round Robin N/A WFQ wide area network 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. See weighted random early detection See weighted round Robin See wait to restore
winding pipe WRED WRR WTR
X
XPIC See cross polarization interference cancellation
Issue 02 (2011-01-20)
C-33

RTN 980 Feature Description (U2000) - (V100R003C00 - 02)

Transféré par

Informations du document

Description originale:

Titre original

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

RTN 980 Feature Description (U2000) - (V100R003C00 - 02)

Transféré par

Droits d'auteur :

Formats disponibles

OptiX RTN 980 Radio Transmission System V100R003C00

Feature Description (U2000)

HUAWEI TECHNOLOGIES CO., LTD.

Trademarks and Permissions

Huawei Technologies Co., Ltd.

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

OptiX RTN 980 Radio Transmission System Feature Description (U2000)

About This Document

About This Document

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

About This Document

OptiX RTN 980 Radio Transmission System Feature Description (U2000)

Updates in Issue 02 (2011-01-20) Based on Product Version V100R003C00

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

OptiX RTN 980 Radio Transmission System Feature Description (U2000)

About This Document

Updates in Issue 01 (2010-12-30) Based on Product Version V100R003C00

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

OptiX RTN 980 Radio Transmission System Feature Description (U2000)

OptiX RTN 980 Radio Transmission System Feature Description (U2000)

OptiX RTN 980 Radio Transmission System Feature Description (U2000)

OptiX RTN 980 Radio Transmission System Feature Description (U2000)

3 1+1 Protection for the Control, Switching, and Timing Board..........................................3-1

4 SDH Protection Features...........................................................................................................4-1

OptiX RTN 980 Radio Transmission System Feature Description (U2000)

4.3.12 FAQs.................................................................................................................................................. 4-58

5 Ethernet Features on the Packet Plane...................................................................................5-1

OptiX RTN 980 Radio Transmission System Feature Description (U2000)

OptiX RTN 980 Radio Transmission System Feature Description (U2000)

OptiX RTN 980 Radio Transmission System Feature Description (U2000)

OptiX RTN 980 Radio Transmission System Feature Description (U2000)

OptiX RTN 980 Radio Transmission System Feature Description (U2000)

OptiX RTN 980 Radio Transmission System Feature Description (U2000)

OptiX RTN 980 Radio Transmission System Feature Description (U2000)

OptiX RTN 980 Radio Transmission System Feature Description (U2000)

OptiX RTN 980 Radio Transmission System Feature Description (U2000)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

OptiX RTN 980 Radio Transmission System Feature Description (U2000)

OptiX RTN 980 Radio Transmission System Feature Description (U2000)

OptiX RTN 980 Radio Transmission System Feature Description (U2000)

OptiX RTN 980 Radio Transmission System Feature Description (U2000)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

OptiX RTN 980 Radio Transmission System Feature Description (U2000)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

OptiX RTN 980 Radio Transmission System Feature Description (U2000)

OptiX RTN 980 Radio Transmission System Feature Description (U2000)

OptiX RTN 980 Radio Transmission System Feature Description (U2000)

OptiX RTN 980 Radio Transmission System Feature Description (U2000)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

OptiX RTN 980 Radio Transmission System Feature Description (U2000)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

OptiX RTN 980 Radio Transmission System Feature Description (U2000)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

OptiX RTN 980 Radio Transmission System Feature Description (U2000)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

OptiX RTN 980 Radio Transmission System Feature Description (U2000)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

OptiX RTN 980 Radio Transmission System Feature Description (U2000)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

OptiX RTN 980 Radio Transmission System Feature Description (U2000)

OptiX RTN 980 Radio Transmission System Feature Description (U2000)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.