OptiX RTN 950 Hybrid Feature Description

OptiX RTN 950 Radio Transmission System V100R002C00
Feature Description
Issue Date 02 2009-10-30
HUAWEI TECHNOLOGIES CO., LTD.
Copyright Huawei Technologies Co., Ltd. 2009-2009. 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 (2009-10-30)
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.
OptiX RTN 950 Feature Description
About This Document
About This Document

Purpose
This document describes the key functions of the OptiX RTN 950 equipment in terms of the basic information, availability and configuration methods. A configuration example is used to illustrate each function.
Related Versions
The following table lists the product versions related to this document. Product Name OptiX RTN 950 iManager U2000 Version V100R002C00 V100R001C00
Intended Audience
The intended audience of this document are:
l l l l
Network Planning Engineer Installation and Commissioning Engineer Data Configuration Engineer System Maintenance Engineer
Organization
This document is organized as follows.
Issue 02 (2009-10-30)
iii
About This Document
Chapter 1 Introduction to the DCN
Description The network management system (NMS) communicates with a transmission network element (NE) through the data communication network (DCN) to manage and maintain the NE. Using the HWECC solution, NEs use unified DCCs to transmit the data of the HWECC protocol. In this manner, the NMS can manage NEs. 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. Using the OSI over DCC solution, NEs use unified DCCs to transmit the data of the TCP/OSI protocol. In this manner, the NMS manages 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. Using the DCC 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. Using the DCC transparent 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. 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 950 equipment and the OptiX packet transmission equipment. 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 HWECC Solution
3 IP over DCC Solution
4 OSI over DCC solution
5 DCC Transparent Transmission Solution
6 DCC Transparent Transmission Through the External Clock Interface Solution
7 Inband DCN Solution
8 1+1 HSB
iv
Issue 02 (2009-10-30)
About This Document
Chapter 9 1+1 FD
Description 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. 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. The cross-polarization interference cancellation (XPIC) technology is used together with the co-channel dualpolarization (CCDP) technology. The application of the two technologies doubles the transmission capacity with channel conditions unchanged. 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. 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. he main feature of the Hybrid microwave is the adaptive modulation (AM) function. 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. 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. The Ethernet ring protection switching (ERPS) is applicable to ring physical networks. The ERPS protects Ethernet services from an owner node to the other nodes on a ring. 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.
10 1+1 SD
11 Cross-Polarization Interference Cancellation
12 N+1 Protection
13 Automatic Transmit Power Control
14 Adaptive Modulation 15 Subnetwork Connection Protection
16 Linear Multiplex Section Protection
17 Ethernet Ring Protection Switching
18 MSTP
Issue 02 (2009-10-30)
About This Document
Chapter 19 IGMP Snooping
Description If the multicast router exists in a network, the bridge can enable the IGMP Snooping protocol to realize the multicast function with the operation of the router. 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. The link state pass through (LPT) is used to detect the faults that occur at the service access node and in the intermediate transmission network. The LPT notifies the equipment that accesses the service of starting the backup link at the earliest time for communication, thus making sure the normal transmission of the important data. 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. 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. 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. 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. This task collection contains all the network management system (NMS) operation tasks related to the product features. This topic describes the parameters used in this document. Terms are listed in an alphabetical order. Acronyms and abbreviations are listed in alphabetical order.
20 Link Aggregation Group
21 Link State Pass Through
22 QoS
23 ETH-OAM
24 Synchronous Ethernet
25 Remote Network Monitoring
A Task Collection
B Parameters Description C Glossary D Acronyms and Abbreviations
vi
Issue 02 (2009-10-30)
About This Document
Conventions
Symbol Conventions
The following symbols may be found in this document. They 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. Indicates a potentially hazardous situation that, if not avoided, could cause equipment damage, data loss, and performance degradation, or unexpected results. Provides additional information to emphasize or supplement important points of the main text. Indicates a tip that may help you solve a problem or save your time.
General Conventions
Convention Times New Roman Boldface Italic Courier New Description Normal paragraphs are in Times New Roman. Names of files, directories, folders, and users are in boldface. For example, log in as user root. Book titles are in italics. Terminal display is in Courier New.
GUI Conventions
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.
Issue 02 (2009-10-30)
vii
About This Document
Keyboard Operation
Format Key Key 1+Key 2 Key 1, Key 2 Description Press the key. For example, press Enter and press Tab. Press the keys concurrently. For example, pressing Ctrl+Alt+A means the three keys should be pressed concurrently. Press the keys in turn. For example, pressing Alt, A means the two keys should be pressed in turn.
Mouse Operation
Action Click Double-click Drag Description Select and release the primary mouse button without moving the pointer. Press the primary mouse button twice continuously and quickly without moving the pointer. Press and hold the primary mouse button and move the pointer to a certain position.
Update History
Updates between document versions are cumulative. Therefore, the latest document version contains all updates made to previous versions.
Updates in Issue 02 (2009-10-30) Based on Product Version V100R002

This document is the second release of the V100R002 version. The updated contents are as follows. Update Location C Glossary D Acronyms and Abbreviations Description Certain terms are added. Certain abbreviations and acronyms are added.
Updates in Issue 01 (2009-06-30) Based on Product Version V100R002

This document is the first release of the V100R002 version.
viii
Issue 02 (2009-10-30)
Contents
Contents
About This Document...................................................................................................................iii 1 Introduction to the DCN...........................................................................................................1-1
1.1 Constitution of the DCN................................................................................................................................. 1-2 1.2 Huawei DCN Solution.................................................................................................................................... 1-3 1.3 Protocol Converter Solution............................................................................................................................1-5
2 HWECC Solution.......................................................................................................................2-1
2.1 Feature Description.........................................................................................................................................2-3 2.2 Basic Concept..................................................................................................................................................2-3 2.2.1 HWECC Protocol Stack.........................................................................................................................2-4 2.2.2 Extended ECC........................................................................................................................................2-6 2.3 Availability......................................................................................................................................................2-9 2.4 Relation with Other Features.........................................................................................................................2-10 2.5 Realization Principle.....................................................................................................................................2-10 2.5.1 Establishing ECC Routes.....................................................................................................................2-10 2.5.2 Packet Transfer.....................................................................................................................................2-12 2.5.3 Extended ECC......................................................................................................................................2-13 2.6 Configuration Flow.......................................................................................................................................2-14 2.7 Configuration Example.................................................................................................................................2-16 2.7.1 Networking Diagram............................................................................................................................2-16 2.7.2 Service Planning...................................................................................................................................2-17 2.7.3 Configuration Process..........................................................................................................................2-18 2.8 Task Collection.............................................................................................................................................2-21 2.9 Relevant Alarms and Events.........................................................................................................................2-21 2.10 FAQs...........................................................................................................................................................2-22
3 IP over DCC Solution................................................................................................................3-1

3.1 Feature Description.........................................................................................................................................3-3 3.2 Basic Concept..................................................................................................................................................3-3 3.2.1 IP over DCC Protocol Stack...................................................................................................................3-3 3.2.2 NMS Access Modes...............................................................................................................................3-6 3.3 Availability......................................................................................................................................................3-7 3.4 Relation with Other Features...........................................................................................................................3-8 3.5 Realization Principle.......................................................................................................................................3-8 Issue 02 (2009-10-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. ix
Contents
3.6 Configuration Flow.........................................................................................................................................3-9 3.7 Configuration Example.................................................................................................................................3-11 3.7.1 Networking Diagram............................................................................................................................3-12 3.7.2 Service Planning...................................................................................................................................3-12 3.7.3 Configuration Process..........................................................................................................................3-13 3.8 Task Collection.............................................................................................................................................3-16 3.9 Relevant Alarms and Events.........................................................................................................................3-16 3.10 FAQs...........................................................................................................................................................3-17
4 OSI over DCC solution.............................................................................................................4-1

4.1 Feature Description.........................................................................................................................................4-3 4.2 Basic Concept..................................................................................................................................................4-3 4.2.1 OSI over DCC Protocol Stack................................................................................................................4-3 4.2.2 NMS Access Modes...............................................................................................................................4-7 4.3 Availability......................................................................................................................................................4-8 4.4 Relation with Other Features...........................................................................................................................4-9 4.5 Realization Principle.......................................................................................................................................4-9 4.6 Configuration Flow.......................................................................................................................................4-11 4.7 Configuration Example.................................................................................................................................4-13 4.7.1 Networking Diagram............................................................................................................................4-13 4.7.2 Service Planning...................................................................................................................................4-14 4.7.3 Configuration Process..........................................................................................................................4-15 4.8 Task Collection.............................................................................................................................................4-17 4.9 Relevant Alarms and Events.........................................................................................................................4-18 4.10 FAQs...........................................................................................................................................................4-18
5 DCC Transparent Transmission Solution.............................................................................5-1

5.1 Feature Description.........................................................................................................................................5-3 5.2 Availability......................................................................................................................................................5-5 5.3 Relation with Other Features...........................................................................................................................5-5 5.4 Realization Principle.......................................................................................................................................5-5 5.5 Configuration Flow.........................................................................................................................................5-6 5.6 Configuration Example...................................................................................................................................5-8 5.6.1 Networking Diagram..............................................................................................................................5-8 5.6.2 Service Planning.....................................................................................................................................5-9 5.6.3 Configuration Process..........................................................................................................................5-10 5.7 Task Collection.............................................................................................................................................5-12 5.8 Relevant Alarms and Events.........................................................................................................................5-12 5.9 FAQs.............................................................................................................................................................5-13
6 DCC Transparent Transmission Through the External Clock Interface Solution........6-1

6.1 Feature Description.........................................................................................................................................6-3 6.2 Availability......................................................................................................................................................6-4 6.3 Relation with Other Features...........................................................................................................................6-4 x Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 02 (2009-10-30)
Contents
6.4 Realization Principle.......................................................................................................................................6-4 6.5 Configuration Procedure.................................................................................................................................6-5 6.6 Configuration Example...................................................................................................................................6-6 6.6.1 Networking Diagram..............................................................................................................................6-6 6.6.2 Service Planning.....................................................................................................................................6-7 6.6.3 Configuration Process............................................................................................................................6-7 6.7 Task Collection............................................................................................................................................... 6-8 6.8 Relevant Alarms and Events...........................................................................................................................6-9 6.9 FAQs............................................................................................................................................................... 6-9
7 Inband DCN Solution...............................................................................................................7-1

7.1 Feature Description.........................................................................................................................................7-3 7.2 Basic Concept..................................................................................................................................................7-3 7.2.1 Inband DCN Protocol Stack...................................................................................................................7-3 7.2.2 NMS Access Modes...............................................................................................................................7-5 7.3 Availability......................................................................................................................................................7-6 7.4 Relation with Other Features...........................................................................................................................7-6 7.5 Realization Principle.......................................................................................................................................7-6 7.6 Configuration Flow.........................................................................................................................................7-8 7.7 Configuration Example...................................................................................................................................7-9 7.7.1 Networking Diagram..............................................................................................................................7-9 7.7.2 Service Planning...................................................................................................................................7-10 7.7.3 Configuration Process..........................................................................................................................7-11 7.8 Task Collection.............................................................................................................................................7-13 7.9 Relevant Alarms and Events.........................................................................................................................7-13 7.10 FAQs...........................................................................................................................................................7-14
8 1+1 HSB........................................................................................................................................8-1
8.1 Feature Description.........................................................................................................................................8-3 8.2 Basic Concepts................................................................................................................................................8-3 8.2.1 System Configuration.............................................................................................................................8-4 8.2.2 Protection Type......................................................................................................................................8-4 8.2.3 Switching Conditions.............................................................................................................................8-5 8.2.4 Switching Impact....................................................................................................................................8-8 8.3 Availability......................................................................................................................................................8-8 8.4 Relation with Other Features...........................................................................................................................8-8 8.5 Realization Principle.......................................................................................................................................8-9 8.5.1 SDH/PDH Microwave............................................................................................................................8-9 8.5.2 Hybrid Microwave...............................................................................................................................8-11 8.6 Configuration Procedure...............................................................................................................................8-14 8.7 Configuration Example.................................................................................................................................8-14 8.7.1 Networking Diagram............................................................................................................................8-15 8.7.2 Service Planning...................................................................................................................................8-15 8.7.3 Configuration Process..........................................................................................................................8-16 Issue 02 (2009-10-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. xi
Contents
8.8 Task Collection.............................................................................................................................................8-18 8.9 Relevant Alarms and Events.........................................................................................................................8-18 8.10 FAQs...........................................................................................................................................................8-18
9 1+1 FD...........................................................................................................................................9-1
9.1 Feature Description.........................................................................................................................................9-3 9.2 Basic Concepts................................................................................................................................................9-3 9.2.1 System Configuration.............................................................................................................................9-4 9.2.2 Protection Type......................................................................................................................................9-5 9.2.3 Switching Conditions.............................................................................................................................9-5 9.2.4 Switching Impact....................................................................................................................................9-9 9.3 Availability......................................................................................................................................................9-9 9.4 Relation with Other Features...........................................................................................................................9-9 9.5 Realization Principle.....................................................................................................................................9-10 9.5.1 SDH/PDH Microwave..........................................................................................................................9-10 9.5.2 Hybrid Microwave...............................................................................................................................9-12 9.6 Configuration Process...................................................................................................................................9-16 9.7 Configuration Example.................................................................................................................................9-16 9.7.1 Networking Diagram............................................................................................................................9-16 9.7.2 Service Planning...................................................................................................................................9-17 9.7.3 Configuration Process..........................................................................................................................9-18 9.8 Task Collection.............................................................................................................................................9-19 9.9 Relevant Alarms and Events.........................................................................................................................9-20 9.10 FAQs...........................................................................................................................................................9-20
10 1+1 SD.......................................................................................................................................10-1
10.1 Feature Description.....................................................................................................................................10-3 10.2 Basic Concepts............................................................................................................................................10-3 10.2.1 System Configuration.........................................................................................................................10-4 10.2.2 Protection Type..................................................................................................................................10-4 10.2.3 Switching Conditions.........................................................................................................................10-5 10.2.4 Switching Impact................................................................................................................................10-9 10.3 Availability................................................................................................................................................10-10 10.4 Relation with Other Features.....................................................................................................................10-10 10.5 Realization Principle.................................................................................................................................10-10 10.5.1 SDH/PDH Microwave......................................................................................................................10-11 10.5.2 Hybrid Microwave...........................................................................................................................10-13 10.6 Configuration Procedure...........................................................................................................................10-17 10.7 Configuration Example.............................................................................................................................10-18 10.7.1 Networking Diagram........................................................................................................................10-18 10.7.2 Service Planning...............................................................................................................................10-18 10.7.3 Configuration Process......................................................................................................................10-20 10.8 Task Collection.........................................................................................................................................10-21 10.9 Relevant Alarms and Events.....................................................................................................................10-21 xii Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 02 (2009-10-30)
Contents
10.10 FAQs.......................................................................................................................................................10-22
11 Cross-Polarization Interference Cancellation...................................................................11-1

11.1 Feature Description.....................................................................................................................................11-3 11.2 Basic Concepts............................................................................................................................................11-3 11.2.1 CCDP and XPIC.................................................................................................................................11-4 11.2.2 System Configuration.........................................................................................................................11-5 11.3 Availability..................................................................................................................................................11-6 11.4 Relation with Other Features.......................................................................................................................11-6 11.5 Realization Principle...................................................................................................................................11-8 11.6 Configuration Procedure.............................................................................................................................11-9 11.7 Configuration Example.............................................................................................................................11-10 11.7.1 Networking Diagram........................................................................................................................11-11 11.7.2 Service Planning...............................................................................................................................11-12 11.7.3 Configuration Process......................................................................................................................11-15 11.8 Task Collection.........................................................................................................................................11-17 11.9 Relevant Alarms and Events.....................................................................................................................11-17 11.10 FAQs.......................................................................................................................................................11-18
12 N+1 Protection........................................................................................................................12-1
12.1 Feature Description.....................................................................................................................................12-3 12.2 Basic Concepts............................................................................................................................................12-3 12.2.1 System Configuration (SDH Microwave)..........................................................................................12-4 12.2.2 System Configuration (Hybrid Microwave)......................................................................................12-8 12.2.3 Protection Mode...............................................................................................................................12-12 12.2.4 Switching Condition.........................................................................................................................12-12 12.2.5 Switching Impact..............................................................................................................................12-15 12.3 Availability................................................................................................................................................12-15 12.4 Relation with Other Features.....................................................................................................................12-16 12.5 Realization Principle.................................................................................................................................12-16 12.5.1 SDH Microwave...............................................................................................................................12-16 12.5.2 Hybrid Microwave...........................................................................................................................12-18 12.6 Configuration Procedure...........................................................................................................................12-21 12.7 Configuration Example.............................................................................................................................12-25 12.7.1 Networking Diagram........................................................................................................................12-26 12.7.2 Service Planning...............................................................................................................................12-26 12.7.3 Configuration Process......................................................................................................................12-31 12.8 Task Collection.........................................................................................................................................12-36 12.9 Relevant Alarms and Performance Events................................................................................................12-36 12.10 FAQs.......................................................................................................................................................12-37
13 Automatic Transmit Power Control...................................................................................13-1

13.1 Feature Description.....................................................................................................................................13-2 13.2 Availability..................................................................................................................................................13-3 Issue 02 (2009-10-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. xiii
Contents
13.3 Relation with Other Features.......................................................................................................................13-3 13.4 Realization Principle...................................................................................................................................13-3 13.5 Configuration Procedure.............................................................................................................................13-5 13.6 Configuration Example...............................................................................................................................13-6 13.6.1 Networking Diagram..........................................................................................................................13-6 13.6.2 Service Planning.................................................................................................................................13-7 13.6.3 Configuration Process........................................................................................................................13-8 13.7 Task Collection........................................................................................................................................... 13-8 13.8 Relevant Alarms and Events.......................................................................................................................13-9 13.9 FAQs........................................................................................................................................................... 13-9
14 Adaptive Modulation............................................................................................................14-1
14.1 Feature Description.....................................................................................................................................14-2 14.2 Availability..................................................................................................................................................14-3 14.3 Relation with Other Features.......................................................................................................................14-4 14.4 Realization Principle...................................................................................................................................14-4 14.5 Configuration Procedure.............................................................................................................................14-6 14.6 Configuration Example...............................................................................................................................14-6 14.6.1 Networking Diagram..........................................................................................................................14-7 14.6.2 Service Planning.................................................................................................................................14-7 14.6.3 Configuration Process........................................................................................................................14-8 14.7 Task Collection........................................................................................................................................... 14-9 14.8 Relevant Alarms and Events.....................................................................................................................14-10 14.9 FAQs.........................................................................................................................................................14-10
15 Subnetwork Connection Protection...................................................................................15-1

15.1 Feature Description.....................................................................................................................................15-3 15.2 Basic Concepts............................................................................................................................................15-3 15.2.1 Protection Type..................................................................................................................................15-4 15.2.2 SNCP Service Pair............................................................................................................................. 15-4 15.2.3 Hold-Off Time....................................................................................................................................15-5 15.2.4 Switching Conditions.........................................................................................................................15-8 15.2.5 Switching Impact..............................................................................................................................15-12 15.3 Availability................................................................................................................................................15-12 15.4 Relation with Other Features.....................................................................................................................15-12 15.5 Realization Principle.................................................................................................................................15-13 15.6 Configuration Procedure...........................................................................................................................15-14 15.7 Configuration Example.............................................................................................................................15-14 15.7.1 Networking Diagram........................................................................................................................15-14 15.7.2 Service Planning...............................................................................................................................15-15 15.7.3 Configuration Process......................................................................................................................15-17 15.8 Task Collection.........................................................................................................................................15-21 15.9 Relevant Alarms and Events.....................................................................................................................15-22 15.10 FAQs.......................................................................................................................................................15-22 xiv Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 02 (2009-10-30)
Contents
16 Linear Multiplex Section Protection...................................................................................16-1

16.1 Feature Description.....................................................................................................................................16-3 16.2 Basic Concepts............................................................................................................................................16-4 16.2.1 Protection Type..................................................................................................................................16-4 16.2.2 Meanings of K Bytes..........................................................................................................................16-6 16.2.3 Switching Conditions.........................................................................................................................16-8 16.2.4 Switching Impact..............................................................................................................................16-10 16.3 Availability................................................................................................................................................16-10 16.4 Relation with Other Features.....................................................................................................................16-10 16.5 Realization Principle.................................................................................................................................16-10 16.5.1 1+1 Linear MSP...............................................................................................................................16-11 16.5.2 1:N Linear MSP...............................................................................................................................16-12 16.6 Configuration Procedure...........................................................................................................................16-14 16.7 Configuration Example.............................................................................................................................16-14 16.7.1 Networking Diagram........................................................................................................................16-14 16.7.2 Service Planning...............................................................................................................................16-15 16.7.3 Configuration Process......................................................................................................................16-16 16.8 Task Collection.........................................................................................................................................16-17 16.9 Relevant Alarms and Events.....................................................................................................................16-17 16.10 FAQs.......................................................................................................................................................16-18
17 Ethernet Ring Protection Switching...................................................................................17-1

17.1 Feature Description.....................................................................................................................................17-3 17.2 Basic Concepts............................................................................................................................................17-4 17.2.1 Protection Instance.............................................................................................................................17-5 17.2.2 Protection Type..................................................................................................................................17-6 17.2.3 R-APS Message..................................................................................................................................17-6 17.2.4 R-APS Timer......................................................................................................................................17-8 17.2.5 Switching Condition...........................................................................................................................17-9 17.2.6 Switching Impact..............................................................................................................................17-11 17.3 Availability................................................................................................................................................17-11 17.4 Relation with Other Features.....................................................................................................................17-12 17.5 Realization Principle.................................................................................................................................17-12 17.6 Configuration Procedure...........................................................................................................................17-15 17.7 Configuration Example.............................................................................................................................17-16 17.7.1 Networking Diagram........................................................................................................................17-16 17.7.2 Service Planning...............................................................................................................................17-17 17.7.3 Configuration Process......................................................................................................................17-18 17.8 Task Collection.........................................................................................................................................17-19 17.9 Relevant Alarms and Events.....................................................................................................................17-19 17.10 FAQs.......................................................................................................................................................17-19
18 MSTP........................................................................................................................................18-1
18.1 Feature Description.....................................................................................................................................18-3 Issue 02 (2009-10-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. xv
Contents
18.2 Basic Concepts............................................................................................................................................18-6 18.3 Availability..................................................................................................................................................18-9 18.4 Relation with Other Features.......................................................................................................................18-9 18.5 Realization Principle...................................................................................................................................18-9 18.6 Configuration Procedure...........................................................................................................................18-12 18.7 Configuration Example.............................................................................................................................18-13 18.7.1 Networking Diagram........................................................................................................................18-13 18.7.2 Service Planning...............................................................................................................................18-14 18.7.3 Configuration Process......................................................................................................................18-15 18.8 Task Collection.........................................................................................................................................18-16 18.9 Relevant Alarms and Events.....................................................................................................................18-17 18.10 FAQs.......................................................................................................................................................18-17
19 IGMP Snooping......................................................................................................................19-1
19.1 Feature Description.....................................................................................................................................19-3 19.2 Basic Concepts............................................................................................................................................19-5 19.3 Availability..................................................................................................................................................19-6 19.4 Relation with Other Features.......................................................................................................................19-6 19.5 Realization Principle...................................................................................................................................19-6 19.6 Configuration Procedure.............................................................................................................................19-8 19.7 Configuration Example...............................................................................................................................19-9 19.7.1 Networking Diagram..........................................................................................................................19-9 19.7.2 Service Planning...............................................................................................................................19-10 19.7.3 Configuration Process......................................................................................................................19-10 19.8 Task Collection.........................................................................................................................................19-11 19.9 Relevant Alarms and Events.....................................................................................................................19-12 19.10 FAQs.......................................................................................................................................................19-12
20 Link Aggregation Group......................................................................................................20-1

20.1 Feature Description.....................................................................................................................................20-3 20.2 Basic Concepts............................................................................................................................................20-3 20.2.1 LAG Types.........................................................................................................................................20-4 20.2.2 Port Types.......................................................................................................................................... 20-5 20.2.3 Switching Condition...........................................................................................................................20-5 20.2.4 Switching Impact................................................................................................................................20-6 20.3 Availability..................................................................................................................................................20-6 20.4 Relation with Other Features.......................................................................................................................20-6 20.5 Realization Principle...................................................................................................................................20-7 20.6 Configuration Procedure...........................................................................................................................20-10 20.7 Configuration Example.............................................................................................................................20-12 20.7.1 Networking Diagram........................................................................................................................20-12 20.7.2 Service Planning...............................................................................................................................20-12 20.7.3 Configuration Process......................................................................................................................20-13 20.8 Task Collection.........................................................................................................................................20-14 xvi Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 02 (2009-10-30)
Contents
20.9 Relevant Alarms and Events.....................................................................................................................20-14 20.10 FAQs.......................................................................................................................................................20-14
21 Link State Pass Through.......................................................................................................21-1

21.1 Feature Description.....................................................................................................................................21-2 21.2 Availability..................................................................................................................................................21-2 21.3 Relation with Other Features.......................................................................................................................21-3 21.4 Realization Principle...................................................................................................................................21-3 21.5 Configuration Procedure.............................................................................................................................21-4 21.6 Configuration Example...............................................................................................................................21-4 21.6.1 Networking Diagram..........................................................................................................................21-5 21.6.2 Service Planning.................................................................................................................................21-5 21.6.3 Configuration Process........................................................................................................................21-6 21.7 Task Collection...........................................................................................................................................21-6 21.8 Relevant Alarms and Events.......................................................................................................................21-6 21.9 FAQs...........................................................................................................................................................21-6
22 QoS............................................................................................................................................22-1
22.1 Feature Description.....................................................................................................................................22-3 22.2 Basic Concepts............................................................................................................................................22-4 22.2.1 DiffServ..............................................................................................................................................22-5 22.2.2 Flow Classification.............................................................................................................................22-6 22.2.3 CAR....................................................................................................................................................22-7 22.2.4 Traffic Shaping...................................................................................................................................22-8 22.2.5 Queue Scheduling..............................................................................................................................22-9 22.2.6 QoS Model.......................................................................................................................................22-12 22.3 Availability................................................................................................................................................22-14 22.4 Relation with Other Features.....................................................................................................................22-14 22.5 Realization Principle.................................................................................................................................22-15 22.5.1 CAR..................................................................................................................................................22-15 22.5.2 Traffic Shaping.................................................................................................................................22-16 22.6 Configuration Procedure...........................................................................................................................22-17 22.7 Configuration Example.............................................................................................................................22-18 22.7.1 Networking Diagram........................................................................................................................22-19 22.7.2 Service Planning...............................................................................................................................22-19 22.7.3 Configuration Process......................................................................................................................22-22 22.8 Task Collection.........................................................................................................................................22-31 22.9 Relevant Alarms and Events.....................................................................................................................22-31 22.10 FAQs.......................................................................................................................................................22-31
23 ETH-OAM................................................................................................................................23-1
23.1 Feature Description.....................................................................................................................................23-3 23.2 Basic Concepts............................................................................................................................................23-4 23.2.1 IEEE 802.1ag OAM Management ....................................................................................................23-5 Issue 02 (2009-10-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. xvii
Contents
OptiX RTN 950 Feature Description 23.2.2 IEEE 802.1ag OAM Operation .........................................................................................................23-7 23.2.3 IEEE 802.3ah OAM Operations.........................................................................................................23-8
23.3 Availability................................................................................................................................................23-10 23.4 Relation with Other Features.....................................................................................................................23-11 23.5 Realization Principle.................................................................................................................................23-11 23.5.1 IEEE 802.1ag OAM.........................................................................................................................23-11 23.5.2 IEEE 802.3ah OAM.........................................................................................................................23-15 23.6 Configuration Procedure...........................................................................................................................23-24 23.6.1 802.1ag OAM...................................................................................................................................23-24 23.6.2 IEEE 802.3ah OAM.........................................................................................................................23-28 23.7 Application Example (802.1ag OAM)......................................................................................................23-30 23.7.1 Networking Diagram........................................................................................................................23-30 23.7.2 Service Planning...............................................................................................................................23-31 23.7.3 Configuration Process......................................................................................................................23-33 23.8 Application Example (802.3ah OAM)......................................................................................................23-36 23.8.1 Networking Diagram........................................................................................................................23-37 23.8.2 Service Planning...............................................................................................................................23-37 23.8.3 Configuration Process......................................................................................................................23-38 23.9 Task Collection.........................................................................................................................................23-39 23.9.1 Task Collection(802.1ag OAM).......................................................................................................23-40 23.9.2 Task Collection (802.3ah OAM)......................................................................................................23-40 23.10 Relevant Alarms and Events...................................................................................................................23-40 23.11 FAQs.......................................................................................................................................................23-41
24 Synchronous Ethernet...........................................................................................................24-1
24.1 Feature Description.....................................................................................................................................24-3 24.2 Availability..................................................................................................................................................24-3 24.3 Relation with Other Features.......................................................................................................................24-4 24.4 Realization Principle...................................................................................................................................24-4 24.5 Configuration Procedure.............................................................................................................................24-5 24.6 Application Example...................................................................................................................................24-5 24.6.1 Networking Diagram..........................................................................................................................24-5 24.6.2 Service Planning.................................................................................................................................24-6 24.6.3 Configuration Process........................................................................................................................24-7 24.7 Task Collection...........................................................................................................................................24-7 24.8 Relevant Alarms and Events.......................................................................................................................24-8 24.9 FAQs...........................................................................................................................................................24-8
25 Remote Network Monitoring..............................................................................................25-1

25.1 Feature Description.....................................................................................................................................25-3 25.2 Basic Concepts............................................................................................................................................25-3 25.2.1 SNMP.................................................................................................................................................25-4 25.2.2 RMON Management Groups.............................................................................................................25-4 25.2.3 List of RMON Alarm Entries.............................................................................................................25-6 xviii Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 02 (2009-10-30)
Contents
25.2.4 List of RMON Performance Entries...................................................................................................25-7 25.3 Availability..................................................................................................................................................25-8 25.4 Relation with Other Features.......................................................................................................................25-9 25.5 Realization Principle...................................................................................................................................25-9 25.6 Configuration Procedure...........................................................................................................................25-10 25.7 Configuration Example.............................................................................................................................25-11 25.7.1 Networking Diagram........................................................................................................................25-11 25.7.2 Troubleshooting Analysis................................................................................................................25-12 25.7.3 Troubleshooting Flow......................................................................................................................25-12 25.8 Task Collection.........................................................................................................................................25-13 25.9 Relevant Alarms and Events.....................................................................................................................25-13 25.10 FAQs.......................................................................................................................................................25-14
A Task Collection.........................................................................................................................A-1
A.1 Managing NEs...............................................................................................................................................A-3 A.1.1 Creating NEs by Using the Search Method..........................................................................................A-3 A.1.2 Creating NEs by Using the Manual Method........................................................................................A-5 A.1.3 Configuring the Logical Board.............................................................................................................A-6 A.1.4 Changing the NE ID.............................................................................................................................A-8 A.1.5 Changing the NE Name........................................................................................................................A-8 A.1.6 Synchronizing the NE Time.................................................................................................................A-9 A.1.7 Configuring Standard NTP Keys........................................................................................................A-12 A.1.8 Localizing the NE Time.....................................................................................................................A-13 A.2 Managing Communications.........................................................................................................................A-14 A.2.1 Setting NE Communication Parameters.............................................................................................A-15 A.2.2 Configuring DCCs..............................................................................................................................A-16 A.2.3 Configuring the Extended ECC..........................................................................................................A-17 A.2.4 Configuring DCC Transparent Transmission.....................................................................................A-17 A.2.5 Creating Static IP Routes....................................................................................................................A-18 A.2.6 Setting Parameters of the OSPF Protocol...........................................................................................A-19 A.2.7 Enabling the ARP Proxy....................................................................................................................A-19 A.2.8 Configuring the CLNS Role...............................................................................................................A-20 A.2.9 Configuring the OSI Tunnel...............................................................................................................A-21 A.2.10 Setting the VLAN ID and Bandwidth Used by an Inband DCN......................................................A-22 A.2.11 Configuring the Enable Status of the Inband DCN Function on Ports.............................................A-22 A.2.12 Querying ECC Routes......................................................................................................................A-23 A.2.13 Querying IP Routes..........................................................................................................................A-24 A.2.14 Querying OSI Routes.......................................................................................................................A-24 A.3 Managing Radio Links................................................................................................................................A-25 A.3.1 Creating an IF 1+1 Protection Group.................................................................................................A-26 A.3.2 Creating an XPIC Protection Group...................................................................................................A-27 A.3.3 Setting the Hybrid/AM Attributes of the XPIC Hybrid Radio Link..................................................A-28 A.3.4 Configuring the IF/ODU Information of a Radio Link......................................................................A-29 Issue 02 (2009-10-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. xix
Contents
OptiX RTN 950 Feature Description A.3.5 Setting the Hybrid/AM Attribute........................................................................................................A-30 A.3.6 Creating an N+1 Protection Group.....................................................................................................A-31 A.3.7 Setting IF Attributes...........................................................................................................................A-32 A.3.8 Configuring the ATPC Function........................................................................................................A-33 A.3.9 Setting the Power Attributes of the ODU...........................................................................................A-34 A.3.10 Setting the State of an ODU Transmitter.........................................................................................A-34 A.3.11 Querying the ATPC Adjustment Records........................................................................................A-35 A.3.12 Querying the History Transmit Power and Receive Power..............................................................A-36 A.3.13 Querying the AM Status...................................................................................................................A-36 A.3.14 Querying the IF 1+1 Protection Status.............................................................................................A-37 A.3.15 Querying the IF N+1 Protection Status............................................................................................A-37 A.3.16 IF 1+1 Protection Switching.............................................................................................................A-38 A.3.17 IF N+1 Protection Switching............................................................................................................A-38 A.3.18 Starting/Stopping the N+1 Protection Protocol................................................................................A-39
A.4 Managing the MSP......................................................................................................................................A-40 A.4.1 Configuring Linear MSP....................................................................................................................A-40 A.4.2 Querying the Status of the Linear MSP..............................................................................................A-41 A.4.3 Performing Linear MSP Switching....................................................................................................A-42 A.4.4 Starting/Stopping the Linear MSP Protocol.......................................................................................A-43 A.5 Managing TDM Services............................................................................................................................A-43 A.5.1 Creating the Cross-Connections of Point-to-Point Services..............................................................A-44 A.5.2 Creating Cross-Connections of SNCP Services.................................................................................A-45 A.5.3 Configuring the Automatic Switching of SNCP Services..................................................................A-46 A.5.4 Deleting Cross-Connections...............................................................................................................A-47 A.5.5 Converting a Normal Service into an SNCP Service.........................................................................A-48 A.5.6 Converting an SNCP Service to a Normal Service............................................................................A-49 A.5.7 Querying TDM Services.....................................................................................................................A-50 A.5.8 Switching SNCP Services..................................................................................................................A-51 A.5.9 Querying the Protection Status of SNCP Services.............................................................................A-51 A.6 Managing the Clock....................................................................................................................................A-52 A.6.1 Configuring the Clock Sources..........................................................................................................A-52 A.6.2 Configuring Clock Subnets................................................................................................................A-54 A.6.3 Self-Defined Clock Quality................................................................................................................A-54 A.6.4 Configuring the SSM Output Status...................................................................................................A-55 A.6.5 Configuring the Clock ID Output Status............................................................................................A-56 A.6.6 Modifying the Parameters of the Clock Output.................................................................................A-57 A.6.7 Changing the Conditions for Clock Source Switching.......................................................................A-57 A.6.8 Modifying the Recovery Parameter of the Clock Source...................................................................A-58 A.6.9 Querying the Clock Synchronization Status.......................................................................................A-59 A.7 Managing the ERPS ...................................................................................................................................A-59 A.7.1 Creating Ethernet Ring Protection Instances......................................................................................A-59 A.7.2 Setting the Parameters of Ethernet Ring Protocol..............................................................................A-60 xx Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 02 (2009-10-30)
Contents
A.7.3 Querying the Status of the Ethernet Ring Protocol............................................................................A-61 A.8 Managing the MSTP....................................................................................................................................A-61 A.8.1 Creating the MSTP Port Group..........................................................................................................A-62 A.8.2 Setting the Bridge Parameters of the MSTP.......................................................................................A-63 A.8.3 Setting the Parameters of the CIST....................................................................................................A-64 A.8.4 Querying the CIST Running Information...........................................................................................A-65 A.8.5 Changing the Spanning Tree Protocol Used by the Port Group.........................................................A-66 A.8.6 Enabling/Disabling the MSTP Protocol.............................................................................................A-66 A.8.7 Modifying the Configuration Data of the MSTP Port Group.............................................................A-67 A.9 Managing the IGMP Snooping....................................................................................................................A-68 A.9.1 Configuring the IGMP Snooping Protocol.........................................................................................A-69 A.9.2 Querying the Port Information of the Routers....................................................................................A-69 A.9.3 Querying the Information About the Multicast Groups.....................................................................A-70 A.9.4 Creating Static Router Ports...............................................................................................................A-71 A.9.5 Creating a Member of a Static Multicast Group.................................................................................A-72 A.9.6 Adding a Quickly Deleted Port..........................................................................................................A-73 A.9.7 Calculating IGMP Packets.................................................................................................................A-73 A.10 Managing the LAG....................................................................................................................................A-74 A.10.1 Creating a LAG................................................................................................................................A-74 A.10.2 Setting the Port Priority....................................................................................................................A-76 A.10.3 Querying the Protocol Information of the LAG...............................................................................A-76 A.11 LPT Configuration.....................................................................................................................................A-77 A.12 Managing the QoS.....................................................................................................................................A-78 A.12.1 Creating a DS Domain......................................................................................................................A-79 A.12.2 Changing the Ports That Use the DS Domain..................................................................................A-80 A.12.3 Creating a Port Policy.......................................................................................................................A-82 A.12.4 Creating the Traffic..........................................................................................................................A-82 A.12.5 Setting the Port That Uses the Port Policy.......................................................................................A-84 A.12.6 Configuring Port Shaping.................................................................................................................A-85 A.12.7 Querying the Port Policy..................................................................................................................A-85 A.12.8 Querying the DS Domain of a Port..................................................................................................A-86 A.13 Using the IEEE 802.1ag OAM..................................................................................................................A-87 A.13.1 Creating an MD................................................................................................................................A-88 A.13.2 Creating an MA................................................................................................................................A-88 A.13.3 Creating an MEP Point.....................................................................................................................A-89 A.13.4 Creating an MIP...............................................................................................................................A-90 A.13.5 Performing a CC Test.......................................................................................................................A-91 A.13.6 Performing an LB Test.....................................................................................................................A-92 A.13.7 Performing an LT Test.....................................................................................................................A-93 A.14 Using the IEEE 802.3ah OAM .................................................................................................................A-94 A.14.1 Enabling the OAM Auto-Discovery Function.................................................................................A-94 A.14.2 Enabling the Link Event Notification ..............................................................................................A-95 Issue 02 (2009-10-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. xxi
Contents
OptiX RTN 950 Feature Description A.14.3 Modifying the OAM Error Frame Monitoring Threshold ...............................................................A-97 A.14.4 Performing Remote Loopback.........................................................................................................A-97 A.14.5 Enabling Self-Loop Detection .........................................................................................................A-98
A.15 Using the RMON.......................................................................................................................................A-99 A.15.1 Browsing the Performance Data in the Statistics Group of an Ethernet Port...................................A-99 A.15.2 Configuring an Alarm Group for an Ethernet Port.........................................................................A-100 A.15.3 Configuring a History Control Group............................................................................................A-101 A.15.4 Browsing the Performance Data in the History Group of an Ethernet Port...................................A-101
B Parameters Description............................................................................................................B-1
B.1 Parameters for NE Management....................................................................................................................B-3 B.1.1 Parameter Description: NE Searching..................................................................................................B-3 B.1.2 Parameter Description: NE Creation....................................................................................................B-7 B.1.3 Parameter Description: NE Attribute_NE ID Change........................................................................B-10 B.1.4 Parameter Description: NE Time Synchronization.............................................................................B-11 B.1.5 Parameter Description: Localization Management of the NE Time...................................................B-13 B.1.6 Parameter Description: Automatic Disabling of the Functions of NEs..............................................B-15 B.2 Parameters for Cable Management..............................................................................................................B-15 B.2.1 Parameter Description: Fiber Search..................................................................................................B-16 B.2.2 Parameter Description: Fiber Creation...............................................................................................B-17 B.2.3 Parameter Description: Radio Link Creation......................................................................................B-19 B.3 Parameters for Communications Management............................................................................................B-20 B.3.1 Parameter Description: NE Communication Parameter Setting.........................................................B-21 B.3.2 Parameter Description: DCC Management_DCC Rate Configuration...............................................B-22 B.3.3 Parameter Description: DCC Management_DCC Transparent Transmission Management..............B-24 B.3.4 Parameter Description: ECC Management_Ethernet Port Extended ECC.........................................B-25 B.3.5 Parameter Description: NE ECC Link Management..........................................................................B-26 B.3.6 Parameter Description: IP Protocol Stack Management_IP Route Management...............................B-28 B.3.7 Parameter Description: IP Protocol Stack Management_IP Route Management Creation................B-29 B.3.8 Parameter Description: IP Protocol Stack Management_OSPF Parameter Settings..........................B-30 B.3.9 Parameter Description: OSI Management_Network Layer Parameter...............................................B-33 B.3.10 Parameter Description: OSI Management_Routing Table...............................................................B-34 B.3.11 Parameter Description: OSI Management_OSI Tunnel....................................................................B-35 B.3.12 Parameter Description: DCN Management_Bandwidth Management.............................................B-39 B.3.13 Parameter Description: DCN Management_Port Setting.................................................................B-39 B.3.14 Parameter Description: Access Control............................................................................................B-40 B.3.15 Parameter Description: LCT Access Control...................................................................................B-41 B.4 Radio Link Parameters.................................................................................................................................B-42 B.4.1 Parameter Description: Link Configuration_XPIC Workgroup_Creation.........................................B-43 B.4.2 Parameter Description: Link Configuration_XPIC............................................................................B-47 B.4.3 Parameter Description: N+1 Protection_Create..................................................................................B-54 B.4.4 Parameter Description: N+1 Protection..............................................................................................B-55 B.4.5 Parameter: IF 1+1 Protection_Create..................................................................................................B-56 xxii Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 02 (2009-10-30)
Contents
B.4.6 Parameter Description: IF 1+1 Protection..........................................................................................B-59 B.4.7 Parameter: Link Configuration_IF/ODU Configuration....................................................................B-62 B.5 Multiplex Section Protection Parameters.....................................................................................................B-73 B.5.1 Parameter Description: Linear MSP_Creation...................................................................................B-73 B.5.2 Parameter Description: Linear MSP...................................................................................................B-76 B.6 SDH/PDH Service Parameters.....................................................................................................................B-80 B.6.1 Parameter Description: SDH Service Configuration_Creation..........................................................B-80 B.6.2 Parameter Description: SDH Service Configuration_SNCP Service Creation..................................B-82 B.6.3 Parameter Description: SDH Service Configuration_Converting Normal Services Into SNCP Services ......................................................................................................................................................................B-85 B.6.4 Parameter Description: SDH Service Configuration_Converting SNCP Services Into Normal Services ......................................................................................................................................................................B-88 B.6.5 Parameter Description: SDH Service Configuration..........................................................................B-92 B.6.6 Parameter Description: SNCP Service Control..................................................................................B-94 B.7 Clock Parameters.........................................................................................................................................B-97 B.7.1 Parameter Description: Clock Source Priority Table..........................................................................B-97 B.7.2 Parameter Description: Clock Subnet Setting_Clock Subnet.............................................................B-99 B.7.3 Parameter Description: Clock Subnet Setting_Clock Quality..........................................................B-103 B.7.4 Parameter Description: Clock Subset Setting_SSM Output Control................................................B-106 B.7.5 Parameter Description: Clock Subset Setting_Clock ID Enabling Status........................................B-107 B.7.6 Parameter Description: Clock Source Switching_Clock Source Restoration Parameters................B-108 B.7.7 Parameter Description: Clock Source Switching_Clock Source Switching.....................................B-110 B.7.8 Parameter Description: Output Phase-Locked Source of the External Clock Source......................B-111 B.7.9 Parameter Description: Clock Synchronization Status.....................................................................B-114 B.8 Parameters for Ethernet Services...............................................................................................................B-116 B.8.1 Parameter Description: E-Line Service_Creation.............................................................................B-116 B.8.2 Parameter Description: E-Line Service.............................................................................................B-122 B.8.3 Parameter Description: VLAN Forwarding Table Item_Creation....................................................B-127 B.8.4 Parameter Description: E-LAN Service_Creation............................................................................B-127 B.8.5 Parameter Description: E-LAN Service............................................................................................B-132 B.8.6 Parameter Description: QinQ Link_Creation...................................................................................B-144 B.9 Ethernet Protocol Parameters.....................................................................................................................B-144 B.9.1 Parameter Description: ERPS Management_Creation.....................................................................B-146 B.9.2 Parameter Description: ERPS Management.....................................................................................B-147 B.9.3 Parameter Description: MSTP Configuration_Port Group Creation................................................B-153 B.9.4 Parameter Description: MSTP Configuration_Port Group Configuration.......................................B-155 B.9.5 Parameter Description: MSTP Configuration_ Bridge Parameters..................................................B-155 B.9.6 Parameter Description: MSTP Configuration_CIST Parameters.....................................................B-160 B.9.7 Parameter Description: MSTP Configuration_Running Information About the CIST....................B-162 B.9.8 Parameter Description: IGMP Snooping Configuration_Protocol Configuration............................B-170 B.9.9 Parameter Description: IGMP Snooping Configuration_Adding Port to Be Quickly Deleted........B-174 B.9.10 Parameter Description: IGMP Snooping Configuration_Route Management...............................B-175 B.9.11 Parameter Description: IGMP Snooping Configuraiton_Static Router Port Creation...................B-176 Issue 02 (2009-10-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. xxiii
Contents
OptiX RTN 950 Feature Description B.9.12 Parameter Description: IGMP Snooping Configuration_Route Member Port Management.........B-177 B.9.13 Parameter Description: IGMP Snooping Configuration_Static Multicast Group Member Creation ....................................................................................................................................................................B-179 B.9.14 Parameter Description: IGMP Snooping Configuration_Data Statistics........................................B-180 B.9.15 Parameter Description: Ethernet Link Aggregation Management_LAG Creation.........................B-182 B.9.16 Parameter Description: Ethernet Link Aggregation_Port Priority..................................................B-186 B.9.17 Parameter Description: LPT Management_Creation......................................................................B-187 B.9.18 Parameter Description: Port Mirroring_Creation...........................................................................B-188
B.10 Parameters for the Ethernet OAM...........................................................................................................B-189 B.10.1 Parameter Description: Ethernet Service OAM Management_Maintenance Domain Creation.....B-190 B.10.2 Parameter Description: Ethernet Service OAM Management_Maintenance Association Creation ....................................................................................................................................................................B-191 B.10.3 Parameter Description: Ethernet Service OAM Management_MEP Creation...............................B-191 B.10.4 Parameter Description: Ethernet Service OAM Management_Remote MEP Creation.................B-193 B.10.5 Parameter Description: Ethernet Service OAM Management_MIP Creation................................B-193 B.10.6 Parameter Description: Ethernet Service OAM Management_LB Enabling.................................B-194 B.10.7 Parameter Description: Ethernet Service OAM Management_LT Enabling..................................B-196 B.10.8 Parameter Description: Ethernet Port OAM Management_OAM Parameter.................................B-197 B.10.9 Parameter Description: Ethernet Port OAM Management_OAM Error Frame Monitoring..........B-200 B.11 QoS Parameters........................................................................................................................................B-201 B.11.1 Parameter Description: Diffserv Domain Management..................................................................B-202 B.11.2 Parameter Description: DiffServ Domain Management_Create....................................................B-206 B.11.3 Parameter Description: DiffServ Domain Applied Port_Modification..........................................B-212 B.11.4 Parameter Description: Policy Management..................................................................................B-213 B.11.5 Parameter Description: Port Policy.................................................................................................B-219 B.11.6 Parameter Description: Port Policy_Traffic Classification Configuration.....................................B-225 B.11.7 Parameter Description: Port Shaping Management_Creation........................................................B-235 B.12 RMON Parameters...................................................................................................................................B-237 B.12.1 Parameter Description: RMON Performance_Statistics Group......................................................B-237 B.12.2 Parameter Description: RMON Performance_History Group........................................................B-238 B.12.3 Parameter Description: RMON Performance_History Control Group...........................................B-239 B.12.4 Parameter Description: RMON Performance_RMON Setting.......................................................B-240 B.13 Parameters for the Orderwire and Auxiliary Interfaces...........................................................................B-242 B.13.1 Parameter Description: Orderwire_General....................................................................................B-243 B.13.2 Parameter Description: Orderwire_Advanced................................................................................B-244 B.13.3 Parameter Description: Orderwire_F1 Data Port............................................................................B-245 B.13.4 Parameter Description: Orderwire_Broadcast Data Port................................................................B-246 B.13.5 Parameter Description: Environment Monitoring Interface...........................................................B-247 B.14 Parameters for Board Interfaces...............................................................................................................B-249 B.14.1 Parameter Description: IF Interface_IF Attribute...........................................................................B-251 B.14.2 Parameter Description: IF Interface_ATPC Attribute....................................................................B-253 B.14.3 Parameter Description: Hybrid/AM Configuration........................................................................B-255 B.14.4 Parameter Description: ATPC Adjustment Records.......................................................................B-257 xxiv Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 02 (2009-10-30)
Contents
B.14.5 Parameter Description: PRBS Test.................................................................................................B-258 B.14.6 Parameter Description: ODU Interface_Radio Frequency Attribute..............................................B-259 B.14.7 Parameter Description: ODU Interface_Power Attributes..............................................................B-261 B.14.8 Parameter Description: ODU Interface_Equipment Information...................................................B-263 B.14.9 Parameter Description: ODU Interface_Advanced Attributes........................................................B-264 B.14.10 Parameter Description: SDH Interfaces........................................................................................B-265 B.14.11 Parameter Description: Automatic Laser Shutdown.....................................................................B-267 B.14.12 Parameter Description: PDH Interfaces........................................................................................B-268 B.14.13 Parameter Description: Ethernet Interface_Basic Attributes........................................................B-270 B.14.14 Parameter Description: Ethernet Interface_Flow Control............................................................B-273 B.14.15 Parameter Description: Ethernet Interface_Layer 2 Attributes.....................................................B-274 B.14.16 Parameter Description: Ethernet Interface_Advanced Attributes.................................................B-278 B.14.17 Parameter Description: Microwave Interface_Basic Attributes...................................................B-280 B.14.18 Parameter Description: Microwave Interface_Layer 2 Attributes................................................B-281 B.14.19 Parameter Description: Microwave Interface_Advanced Attributes............................................B-283 B.15 Parameters for Overhead..........................................................................................................................B-285 B.15.1 Parameter Description: Regenerator Section Overhead..................................................................B-286 B.15.2 Parameter Description: VC-4 POHs...............................................................................................B-286 B.15.3 Parameter Description: VC-12 POHs.............................................................................................B-288
C Glossary......................................................................................................................................C-1 D Acronyms and Abbreviations...............................................................................................D-1
Issue 02 (2009-10-30)
xxv
Figures
Figures
Figure 1-1 DCN....................................................................................................................................................1-2 Figure 1-2 RS-232/Ethernet protocol converter solution (in the case that all the edge equipment is in the same domain)..................................................................................................................................................................1-6 Figure 1-3 RS-232/Ethernet protocol converter solution (in the case that the edge equipment is in multiple domains) ...............................................................................................................................................................................1-7 Figure 1-4 64k/Ethernet protocol converter solution (in the case that all the edge equipment is in the same domain) ...............................................................................................................................................................................1-8 Figure 1-5 64k/Ethernet protocol converter solution (in the case that all the edge equipment is in multiple domains) ...............................................................................................................................................................................1-8 Figure 1-6 E1/Ethernet protocol converter solution (in the case that all the edge equipment is in the same domain) ...............................................................................................................................................................................1-9 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-10 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-11 Figure 1-9 E1/Ethernet protocol converter solution (shared E1).......................................................................1-12 Figure 1-10 E1/Ethernet protocol converter solution (shared BTS service channel).........................................1-13 Figure 1-11 Hybrid Use Solution of Protocol Converters .................................................................................1-14 Figure 2-1 HWECC solution................................................................................................................................2-3 Figure 2-2 HWECC protocol stack architecture..................................................................................................2-4 Figure 2-3 Networking for the extended ECC (using a network cable)...............................................................2-7 Figure 2-4 Networking for the extended ECC (using a hub)...............................................................................2-7 Figure 2-5 Networking for the extended ECC (using network cables to connect NEs in series)........................2-8 Figure 2-6 Extended ECC network (multi level extended ECC).........................................................................2-9 Figure 2-7 Networking example for establishing ECC routes...........................................................................2-11 Figure 2-8 Realization principle of message transfer (HWECC).......................................................................2-12 Figure 2-9 Networking diagram of the HWECC solution.................................................................................2-17 Figure 2-10 Allocation of IDs/IP addresses for all the NEs...............................................................................2-18 Figure 3-1 Application of the IP over DCC solution...........................................................................................3-3 Figure 3-2 IP over DCC protocol stack architecture............................................................................................3-4 Figure 3-3 Application example of the proxy ARP.............................................................................................3-6 Figure 3-4 Realization principle of message transfer (gateway mode)................................................................3-8 Figure 3-5 Realization principle of message transfer (direct connection mode)..................................................3-9 Figure 3-6 Networking diagram.........................................................................................................................3-12 Figure 3-7 Allocation of IDs/IP addresses for all the NEs.................................................................................3-13 Issue 02 (2009-10-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. xxvii
Figures
OptiX RTN 950 Feature Description Figure 4-1 Application of the OSI over DCC solution........................................................................................4-3 Figure 4-2 OSI over DCC protocol stack architecture.........................................................................................4-4 Figure 4-3 Format of the NSAP address..............................................................................................................4-5 Figure 4-4 Layered routes of IS-IS protocol routes (L2 not consecutive)...........................................................4-6 Figure 4-5 Application example of the OSI tunnel..............................................................................................4-7
Figure 4-6 Realization principle of message transferring (gateway mode).......................................................4-10 Figure 4-7 Realization principle of message transferring (direct connection mode).........................................4-11 Figure 4-8 Networking diagram.........................................................................................................................4-14 Figure 4-9 Allocation of NE areas.....................................................................................................................4-15 Figure 5-1 DCC transparent transmission solution when the OptiX equipment is at the edge of a network (1) ...............................................................................................................................................................................5-3 Figure 5-2 DCC transparent transmission solution when the OptiX equipment is at the edge of a network (2) ...............................................................................................................................................................................5-4 Figure 5-3 DCC transparent transmission solution when the OptiX equipment is in the center of a network (1) ...............................................................................................................................................................................5-4 Figure 5-4 DCC transparent transmission solution when the OptiX equipment is in the center of a network (2) ...............................................................................................................................................................................5-5 Figure 5-5 Realization principle of the DCC transparent transmission...............................................................5-6 Figure 5-6 Networking diagram of the DCC transparent transmission solution..................................................5-9 Figure 5-7 Allocation of IDs/IP addresses for all the NEs.................................................................................5-10 Figure 6-1 Networking example for the DCC transparent transmission through the external clock interface solution (direct access mode)..............................................................................................................................................6-3 Figure 6-2 Networking example for the DCC transparent transmission through the external clock interface solution (indirect access mode)...........................................................................................................................................6-4 Figure 6-3 Realization principle of the DCC transparent transmission through the external clock interface ...............................................................................................................................................................................6-5 Figure 6-4 Networking example for the DCC transparent transmission through the external clock interface solution ...............................................................................................................................................................................6-7 Figure 7-1 Application of the inband DCN solution............................................................................................7-3 Figure 7-2 Inband DCN protocol stack architecture............................................................................................7-4 Figure 7-3 Realization principle of packet forwarding........................................................................................7-7 Figure 7-4 Networking diagram of the inband DCN solution............................................................................7-10 Figure 7-5 Allocation of IDs/IP addresses for all the NEs.................................................................................7-11 Figure 8-1 1+1 HSB protection............................................................................................................................8-3 Figure 8-2 Typical configuration of one 1+1 HSB protection group...................................................................8-4 Figure 8-3 1+1 HSB realization principle (before the switching, in the transmit direction)...............................8-9 Figure 8-4 1+1 HSB realization principle (before the switching, in the receive direction)...............................8-10 Figure 8-5 1+1 HSB realization principle (after the switching, in the receive direction)..................................8-10 Figure 8-6 1+1 HSB realization principle (after the switching, in the transmit direction)................................8-11 Figure 8-7 1+1 HSB realization principle (before the switching, in the transmit direction).............................8-11 Figure 8-8 1+1 HSB realization principle (before the switching, in the receive direction)...............................8-12 Figure 8-9 1+1 HSB realization principle (after the switching, in the receive direction)..................................8-13 Figure 8-10 1+1 HSB realization principle (after the switching, in the transmit direction)..............................8-13 Figure 8-11 Networking diagram of 1+1 HSB protection.................................................................................8-15 xxviii Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 02 (2009-10-30)
Figures
Figure 9-1 1+1 FD protection...............................................................................................................................9-3 Figure 9-2 Typical configuration 1 of one 1+1 FD protection group..................................................................9-4 Figure 9-3 Typical configuration 2 of one 1+1 FD protection group..................................................................9-5 Figure 9-4 1+1 FD realization principle (before the switching, in the transmit direction)................................9-10 Figure 9-5 1+1 FD realization principle (before the switching, in the receive direction)..................................9-11 Figure 9-6 1+1 FD HSB realization principle (after the switching, in the receive direction)............................9-11 Figure 9-7 1+1 FD HSM realization principle (after the switching, in the receive direction)...........................9-12 Figure 9-8 1+1 FD realization principle (before the switching, in the transmit direction)................................9-12 Figure 9-9 1+1 FD realization principle (before the switching, in the receive direction)..................................9-13 Figure 9-10 1+1 FD HSB realization principle (after the switching, in the transmit direction)........................9-14 Figure 9-11 1+1 FD HSB realization principle (after the switching, in the receive direction)..........................9-14 Figure 9-12 1+1 FD HSM realization principle (after the switching, in the receive direction).........................9-15 Figure 9-13 Networking diagram of 1+1 FD protection....................................................................................9-17 Figure 10-1 1+1 SD protection...........................................................................................................................10-3 Figure 10-2 Typical configuration of one 1+1 SD protection group.................................................................10-4 Figure 10-3 1+1 SD realization principle (before the switching, in the transmit direction)............................10-11 Figure 10-4 1+1 SD realization principle (before the switching, in the receive direction)..............................10-12 Figure 10-5 1+1 SD HSB realization principle (after the switching, in the receive direction)........................10-12 Figure 10-6 1+1 SD HSB realization principle (after the switching, in the transmit direction)......................10-13 Figure 10-7 1+1 SD HSM realization principle (after the switching, in the receive direction).......................10-13 Figure 10-8 1+1 SD realization principle (before the switching, in the transmit direction)............................10-14 Figure 10-9 1+1 SD realization principle (before the switching, in the receive direction)..............................10-15 Figure 10-10 1+1 SD HSB realization principle (after the switching, in the receive direction)......................10-16 Figure 10-11 1+1 SD HSB realization principle (after the switching, in the transmit direction)....................10-16 Figure 10-12 1+1 SD HSM realization principle (after the switching, in the receive direction).....................10-17 Figure 10-13 Networking diagram of the 1+1 SD protection group................................................................10-18 Figure 11-1 ACAP channel configuration (without the application of the XPIC technology)..........................11-3 Figure 11-2 CCDP channel configuration (with the application of the XPIC technology)...............................11-3 Figure 11-3 Single-polarized transmission.........................................................................................................11-4 Figure 11-4 CCDP transmission.........................................................................................................................11-4 Figure 11-5 Typical configuration of the XPIC.................................................................................................11-5 Figure 11-6 Typical XPIC configuration (1+1 protection configuration)..........................................................11-7 Figure 11-7 Realization principle of the XPIC..................................................................................................11-8 Figure 11-8 Networking diagram.....................................................................................................................11-11 Figure 11-9 Board configuration......................................................................................................................11-12 Figure 12-1 N+1 protection................................................................................................................................12-3 Figure 12-2 Typical configuration of one 1+1 protection group........................................................................12-5 Figure 12-3 Typical configuration of one 2+1 protection group........................................................................12-6 Figure 12-4 Typical channel configuration of one 2+1 protection group..........................................................12-6 Figure 12-5 Typical configuration of one 3+1 protection group........................................................................12-7 Figure 12-6 Typical channel configuration of one 3+1 protection group..........................................................12-7 Figure 12-7 Typical configuration of one 1+1 protection group........................................................................12-9 Issue 02 (2009-10-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. xxix
Figures
OptiX RTN 950 Feature Description Figure 12-8 Typical configuration of one 2+1 protection group......................................................................12-10 Figure 12-9 Typical channel configuration of one 2+1 protection group........................................................12-10
Figure 12-10 Typical configuration of one 3+1 protection group....................................................................12-11 Figure 12-11 Typical channel configuration of one 3+1 protection group......................................................12-11 Figure 12-12 Realization principles of the 2+1 protection (before the switching)..........................................12-17 Figure 12-13 Realization principles of the 2+1 protection (after the switching).............................................12-17 Figure 12-14 Realization principles of the 2+1 protection (before the switching)..........................................12-19 Figure 12-15 Realization principles of the 2+1 protection (after the switching).............................................12-20 Figure 12-16 Networking diagram...................................................................................................................12-26 Figure 12-17 Timeslot allocation diagram.......................................................................................................12-29 Figure 13-1 Relationship between the RSL and TSL.........................................................................................13-2 Figure 13-2 Realization principle of the ATPC.................................................................................................13-4 Figure 13-3 Networking diagram.......................................................................................................................13-7 Figure 14-1 AM..................................................................................................................................................14-3 Figure 14-2 AM switching (before the switching).............................................................................................14-5 Figure 14-3 AM switching (after the switching)................................................................................................14-6 Figure 14-4 Networking diagram of the AM.....................................................................................................14-7 Figure 15-1 SNCP..............................................................................................................................................15-3 Figure 15-2 SNCP service pair...........................................................................................................................15-4 Figure 15-3 Coexisting 1+1 SD and SNCP........................................................................................................15-5 Figure 15-4 Traffic flow after the SNCP switching and 1+1 SD switching......................................................15-6 Figure 15-5 Traffic flow after the revertive SNCP switching............................................................................15-6 Figure 15-6 Traffic flow after the switching when the hold-off time is set ......................................................15-7 Figure 15-7 SNCP realization principle (before the switching).......................................................................15-13 Figure 15-8 SNCP realization principle (after the switching)..........................................................................15-13 Figure 15-9 Networking diagram of the SNCP ring .......................................................................................15-15 Figure 15-10 Timeslot allocation diagram (TDM services on the Hybrid microwave ring network).............15-16 Figure 16-1 1+1 linear MSP...............................................................................................................................16-3 Figure 16-2 1:N linear MSP...............................................................................................................................16-4 Figure 16-3 Realization principle of the 1+1 linear MSP (before the switching)............................................16-11 Figure 16-4 Realization principle of the 1+1 linear MSP (after the switching, in single-ended mode)..........16-11 Figure 16-5 Realization principle of the 1+1 linear MSP (after the switching, in dual-ended mode).............16-12 Figure 16-6 Realization principle of the 1:1 linear MSP (before the switching).............................................16-13 Figure 16-7 Realization principle of the 1:1 linear MSP (after the switching)................................................16-13 Figure 16-8 Networking diagram of the linear MSP........................................................................................16-15 Figure 17-1 Implementation of the ERPS..........................................................................................................17-4 Figure 17-2 Protection instance of the ERPS.....................................................................................................17-5 Figure 17-3 Frame format of an R-APS message..............................................................................................17-7 Figure 17-4 Frame format of the R-APS specific information...........................................................................17-7 Figure 17-5 Realization principle of the ERPS (in the case of a fault on a non-RPL link).............................17-13 Figure 17-6 Realization principle of the ERPS (in the case of a fault on an RPL link)...................................17-14 Figure 17-7 Networking diagram.....................................................................................................................17-17 xxx Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 02 (2009-10-30)
Figures
Figure 18-1 Diagram of the STP........................................................................................................................18-3 Figure 18-2 Limitation of the STP/RSTP...........................................................................................................18-4 Figure 18-3 Improvement in the MSTP.............................................................................................................18-5 Figure 18-4 Prevention of access network loops................................................................................................18-6 Figure 18-5 Networking diagram.....................................................................................................................18-14 Figure 19-1 Transmission of multicast packets (with the IGMP Snooping protocol disabled).........................19-4 Figure 19-2 Transmission of multicast packets (with the IGMP Snooping protocol enabled)..........................19-4 Figure 19-3 Networking Diagram....................................................................................................................19-10 Figure 20-1 Link aggregation group..................................................................................................................20-3 Figure 20-2 Frame format of the LACP packet .................................................................................................20-8 Figure 20-3 Application of the LACP protocol................................................................................................20-10 Figure 20-4 Networking diagram.....................................................................................................................20-12 Figure 21-1 LPT networking diagram................................................................................................................21-2 Figure 21-2 Realization diagram of the LPT function.......................................................................................21-4 Figure 21-3 Networking diagram of the LPT.....................................................................................................21-5 Figure 22-1 FIFO queue.....................................................................................................................................22-3 Figure 22-2 Prioritized queues...........................................................................................................................22-4 Figure 22-3 DiffServ model...............................................................................................................................22-5 Figure 22-4 CAR processing..............................................................................................................................22-8 Figure 22-5 Processing of the traffic shaping....................................................................................................22-9 Figure 22-6 SP queues......................................................................................................................................22-10 Figure 22-7 WRR scheduling algorithm..........................................................................................................22-11 Figure 22-8 SP+WRR scheduling algorithm....................................................................................................22-12 Figure 22-9 QoS model....................................................................................................................................22-13 Figure 22-10 Basic working principle of the token bucket algorithm..............................................................22-15 Figure 22-11 Basic working principle of the CAR algorithm..........................................................................22-16 Figure 22-12 Basic working principle of the algorithm that is used by the traffic shaping.............................22-17 Figure 22-13 Networking diagram...................................................................................................................22-19 Figure 23-1 ETH-OAM solution........................................................................................................................23-4 Figure 23-2 Logical diagram of maintenance domain layers ............................................................................23-6 Figure 23-3 IEEE 802.1ag OAMPDU............................................................................................................. 23-12 Figure 23-4 Continuity check diagram.............................................................................................................23-13 Figure 23-5 Loopback test diagram..................................................................................................................23-14 Figure 23-6 LT test diagram.............................................................................................................................23-15 Figure 23-7 IEEE 802.3ah OAMPDU............................................................................................................. 23-16 Figure 23-8 Packet format of the information OAMPDU............................................................................... 23-18 Figure 23-9 Packet format of the event notification OAMPDU...................................................................... 23-22 Figure 23-10 Packet format of the loopback control OAMPDU..................................................................... 23-23 Figure 23-11 Networking diagram for configuring VLAN-based E-Line services.........................................23-30 Figure 23-12 Information about the MPs that belong to different VLANs......................................................23-31 Figure 23-13 Networking diagram of the IEEE 802.3ah OAM.......................................................................23-37 Figure 24-1 Application of the Synchronous Ethernet.......................................................................................24-3 Issue 02 (2009-10-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. xxxi
Figures
OptiX RTN 950 Feature Description Figure 24-2 Realization principle of the synchronous Ethernet.........................................................................24-4
Figure 24-3 Networking diagram of the synchronous Ethernet.........................................................................24-6 Figure 24-4 Networking diagram (clock for a Hybrid microwave chain network)...........................................24-6 Figure 25-1 Networking diagram.....................................................................................................................25-12
xxxii
Issue 02 (2009-10-30)
Tables
Tables
Table 2-1 Availability of the HWECC solution...................................................................................................2-9 Table 2-2 Configuration flow for the HWECC solution....................................................................................2-14 Table 3-1 Availability of the IP over DCC solution.............................................................................................3-7 Table 3-2 Configuration flow for the IP over DCC solution..............................................................................3-10 Table 4-1 Availability of the OSI over DCC solution..........................................................................................4-8 Table 4-2 Configuration flow for the OSI over DCC solution...........................................................................4-11 Table 5-1 Availability of the DCC Transparent Transmission Solution..............................................................5-5 Table 5-2 Configuration flow for the DCC transparent transmission solution....................................................5-7 Table 6-1 Availability of the DCC transparent transmission through the external clock interface solution ...............................................................................................................................................................................6-4 Table 6-2 Procedure for configuring the solution of transparently transmitting DCCs through the external clock interface.................................................................................................................................................................6-6 Table 7-1 Availability of the IP over DCC solution.............................................................................................7-6 Table 7-2 Configuration flow of communications data at the near end...............................................................7-8 Table 8-1 Trigger conditions of the 1+1 HSB switching ....................................................................................8-5 Table 8-2 Trigger conditions of the automatic 1+1 HSB switching.....................................................................8-7 Table 8-3 Availability of the 1+1 HSB feature....................................................................................................8-8 Table 8-4 Process for configuring the 1+1 HSB protection mode.....................................................................8-14 Table 8-5 IF planning information.....................................................................................................................8-16 Table 8-6 RF planning information....................................................................................................................8-16 Table 9-1 Trigger conditions of the 1+1 FD HSB switching...............................................................................9-6 Table 9-2 Trigger conditions of the automatic HSB switching............................................................................9-7 Table 9-3 Trigger conditions of the automatic HSM switching...........................................................................9-8 Table 9-4 Availability of the 1+1 FD feature.......................................................................................................9-9 Table 9-5 Process for configuring the 1+1 FD protection mode........................................................................9-16 Table 9-6 IF planning information.....................................................................................................................9-17 Table 9-7 RF planning information....................................................................................................................9-18 Table 10-1 Trigger conditions of the 1+1 SD HSB switching...........................................................................10-5 Table 10-2 Trigger conditions of the automatic HSB switching........................................................................10-8 Table 10-3 Trigger conditions of the automatic HSM switching.......................................................................10-9 Table 10-4 Availability of the 1+1 SD feature.................................................................................................10-10 Table 10-5 Configuration procedure of 1+1 SD protection.............................................................................10-18 Table 10-6 IF planning information.................................................................................................................10-19 Table 10-7 RF planning information................................................................................................................10-19 Issue 02 (2009-10-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. xxxiii
Tables
OptiX RTN 950 Feature Description Table 11-1 Availability of the XPIC feature......................................................................................................11-6 Table 11-2 Procedure for configuring the XPIC link.........................................................................................11-9 Table 11-3 Basic information about the radio links.........................................................................................11-12 Table 11-4 Information about the Hybrid/AM attribute...................................................................................11-13 Table 11-5 Information about the Power and ATPC .......................................................................................11-14 Table 11-6 Configuration information about the XPIC....................................................................................11-14 Table 11-7 Configuration information about the 1+1 HSB protection group..................................................11-15 Table 12-1 Switching conditions of the N+1 protection..................................................................................12-12 Table 12-2 Availability of the N+1 protection feature.....................................................................................12-16 Table 12-3 Procedure for configuring an N+1 protection group (SDH microwave).......................................12-22 Table 12-4 Procedure for configuring the N+1 protection (Hybrid microwave).............................................12-23 Table 12-5 Basic information about radio links...............................................................................................12-27 Table 12-6 Information about the Hybrid/AM attributes.................................................................................12-27 Table 12-7 Information about the power and ATPC .......................................................................................12-28 Table 12-8 Information about the N+1 (N=2) protection.................................................................................12-29 Table 12-9 Attributes of Ethernet ports............................................................................................................12-30 Table 12-10 Ethernet attributes of microwave ports........................................................................................12-30 Table 12-11 Information about VLAN-based E-Line services........................................................................12-31 Table 13-1 ATPC performance..........................................................................................................................13-3 Table 13-2 Availability of the ATPC feature.....................................................................................................13-3 Table 13-3 Procedure for configuring the ATPC (TDM microwave)................................................................13-5 Table 13-4 Procedure for configuring the ATPC (Hybrid microwave).............................................................13-6 Table 13-5 Information about the ATPC............................................................................................................13-7 Table 13-6 Information about IF boards.............................................................................................................13-7 Table 14-1 Availability of the AM feature.........................................................................................................14-3 Table 14-2 Procedure for configuring the 1+1 HSB protection.........................................................................14-6 Table 14-3 IF planning information...................................................................................................................14-8 Table 14-4 RF planning information..................................................................................................................14-8 Table 15-1 SNCP switching conditions..............................................................................................................15-8 Table 15-2 Trigger conditions of the automatic SNCP switching (VC-4 services).........................................15-10 Table 15-3 Trigger conditions of the automatic SNCP switching (VC-3/VC-12 services).............................15-11 Table 15-4 Trigger conditions of the automatic SNCP switching (E1 services transmitted over the Hybrid microwave)........................................................................................................................................................15-11 Table 15-5 Availability of the SNCP solution..................................................................................................15-12 Table 15-6 Procedure for configuring the SNCP service.................................................................................15-14 Table 15-7 SNCP..............................................................................................................................................15-17 Table 16-1 Meanings of K bytes (linear MSP)...................................................................................................16-6 Table 16-2 Bridge request code..........................................................................................................................16-7 Table 16-3 Trigger conditions of the linear MSP switching..............................................................................16-8 Table 16-4 Availability of the linear MSP solution.........................................................................................16-10 Table 16-5 Procedure for configuring a linear MSP service............................................................................16-14 Table 16-6 Linear MSP....................................................................................................................................16-15 Table 17-1 Description of each field in the R-APS specific information...........................................................17-7
xxxiv
Issue 02 (2009-10-30)
Tables
Table 17-2 Trigger conditions of the ERPS.....................................................................................................17-10 Table 17-3 Availability of the ERPS Feature...................................................................................................17-11 Table 17-4 Procedure for configuring the ERPS..............................................................................................17-15 Table 17-5 Configuration information about the ERPS protection instance....................................................17-17 Table 17-6 Configuration information about the ERPS parameters.................................................................17-18 Table 18-1 Availability of the MSTP.................................................................................................................18-9 Table 18-2 Procedure for configuring the MSTP.............................................................................................18-12 Table 18-3 Parameters of an MSTP port group................................................................................................18-14 Table 18-4 Bridge parameters..........................................................................................................................18-15 Table 18-5 CIST Parameter..............................................................................................................................18-15 Table 19-1 Availability of the IGMP Snooping.................................................................................................19-6 Table 19-2 Procedure for Configuring the IGMP Snooping..............................................................................19-8 Table 20-1 Switching Conditions.......................................................................................................................20-5 Table 20-2 Availability of the LAG feature.......................................................................................................20-6 Table 20-3 Parameter Description......................................................................................................................20-8 Table 20-4 Procedure for configuring the LAG based on the 802.1q bridge...................................................20-11 Table 20-5 LAG information............................................................................................................................20-12 Table 21-1 Availability of the LPT feature........................................................................................................21-3 Table 21-2 Procedure for configuring the LPT..................................................................................................21-4 Table 21-3 Configuration information about the LPT........................................................................................21-5 Table 22-1 Mapping relations between the priorities of ingress packets and PHB service levels.....................22-6 Table 22-2 Mapping relations between the priorities of egress packets and PHB service levels......................22-6 Table 22-3 QoS technologies supported by each application point of the QoS model....................................22-13 Table 22-4 Availability of the QoS feature......................................................................................................22-14 Table 22-5 Procedure for configuring the QoS ...............................................................................................22-18 Table 22-6 Service class and PHB service class..............................................................................................22-19 Table 22-7 Queue scheduling mode.................................................................................................................22-20 Table 22-8 CAR parameters.............................................................................................................................22-21 Table 22-9 Shaping parameters........................................................................................................................22-21 Table 23-1 IEEE 802.1ag ETH-OAM operations and application scenarios.....................................................23-7 Table 23-2 IEEE 802.3ah OAM operations and application scenarios..............................................................23-8 Table 23-3 Availability of the ETH-OAM Feature..........................................................................................23-10 Table 23-4 Mapping between the OAM type values and OMA packet types..................................................23-12 Table 23-5 Mapping between the Code values and OMA packet types...........................................................23-16 Table 23-6 Details of OAM configuration bytes..............................................................................................23-19 Table 23-7 Mapping between the OAM working modes and the OAM capability.........................................23-21 Table 23-8 Flow for configuring the 802.1ag OAM service............................................................................23-25 Table 23-9 Description of the configuration flow of the 802.3ah OAM service.............................................23-29 Table 23-10 Information about the MD...........................................................................................................23-31 Table 23-11 Information about the MA...........................................................................................................23-31 Table 23-12 Information about the MEP..........................................................................................................23-32 Table 23-13 Information about the remote MEP..............................................................................................23-32 Issue 02 (2009-10-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. xxxv
Tables
OptiX RTN 950 Feature Description Table 23-14 Information about the MIP...........................................................................................................23-33 Table 23-15 Information about the LT test......................................................................................................23-33 Table 23-16 Parameters of the OAM...............................................................................................................23-37 Table 23-17 Error frame monitoring information of the OAM........................................................................23-38 Table 24-1 Availability of the synchronous Ethernet feature.............................................................................24-3 Table 24-2 Procedure for configuring the synchronous Ethernet.......................................................................24-5 Table 25-1 List of RMON alarm entries............................................................................................................25-6 Table 25-2 List of RMON performance entries.................................................................................................25-7 Table 25-3 Availability of the RMON feature...................................................................................................25-8 Table 25-4 Procedure of configuring the RMON.............................................................................................25-10 Table B-1 Methods used by Ethernet interfaces to process data frames.........................................................B-277 Table B-2 Data frame processing....................................................................................................................B-282
xxxvi
Issue 02 (2009-10-30)
1 Introduction to the DCN
1
About This Chapter
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 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.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.3 Protocol Converter Solution To use the protocol converter solution, the corresponding protocol converter is selected according to the bearing capacity of the equipment in the center of the network.
Issue 02 (2009-10-30)
1-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. 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.
1-2 Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 02 (2009-10-30)
Internal DCN
In an internal DCN, the NM message supported by the OptiX RTN 950 can be transmitted in the following manner:
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 Hybrid microwave 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 l l
The inband DCN refers to a DCN networking mode that uses partial service bandwidth as a data communication channel. OptiX RTN 950 uses partial Ethernet service bandwidth at a Hybrid microwave port or FE/GE port to transmit NM message. The outband DCN refers to a DCN networking mode whose data communication channel does not use service bandwidth. OptiX RTN 950 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.
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 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. 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
Issue 02 (2009-10-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 1-3
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 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 4 OSI over DCC solution.
NOTE
If the equipment located in the center of the network supports the OSI over DCC function and the third-party equipment located at the edge of the network supports NM message transmission through the Ethernet, the OSI over DCC solution can be used to realize the DCN communication of the equipment at the edge of a network.
DCC Transparent Transmission Solution

When the network 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 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 transparent transmission solution, see section 5 DCC Transparent Transmission Solution.
DCC Transparent Transmission Through the External Clock Interface Solution

When a PDH network or a network that does not support transparent transmission of DCC bytes exists on the transmission path of NM messages, the DCC transparent transmission through the external clock interface solution is adopted. With the DCC transparent transmission through the external clock interface solution, DCC bytes are loaded into the timeslots of the E1 provided by the external clock interface and the thirdparty equipment transmits the E1 as an ordinary E1 service. When this solution is adopted, the transmission bandwidth of an E1 service needs to be occupied and the NEs connected to Huawei's NMS must be the OptiX equipment.
For details on the DCC transparent transmission through the external clock interface solution, see section 6 DCC Transparent Transmission Through the External Clock Interface Solution.
Inband DCN Solution

When the network is comprised of the OptiX RTN 950 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 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.3 Protocol Converter Solution.
NOTE
When the equipment at the edge of the network carries the NM message by using the RS-232 asynchronous data service, the protocol converter solution can be used for the DCN communication. By using the protocol converters of other types, the asynchronous data service can be converted into a service that can be transparently transmitted by the equipment in the center of the network, such as the 64 kbit/s synchronous data service and Nx64 bit/s data service.
1.3 Protocol Converter Solution

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

l
When the equipment in the center of the network supports the RS-232 asynchronous data service transmission, the RS-232/Ethernet protocol converter is the first choice for realizing the DCN communication.
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. 1-5
Issue 02 (2009-10-30)

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

With this solution, the edge equipment side and the NM side of the edge equipment converts the NM message carried by the Ethernet into the RS-232 asynchronous data service by using the RS-232/Ethernet protocol converter, and the central equipment transparently transmits the data service. 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. 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-6
Issue 02 (2009-10-30)
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
Central network
RS-232/Ethernet Converter n
Ethernet link
RS-232 link
Radio link
NOTE
The OptiX RTN 950 supports direct NMS access through the RS-232 serial port. Hence, when the OptiX RTN 950 is the edge equipment and the central equipment supports the RS-232 asynchronous data service transmission, the protocol converter is not necessary. Instead, the serial ports of the NMS and the NE can be directly connected to the asynchronous data interface of the central equipment.
64k/Ethernet Protocol Converter Solution

With this solution, the edge equipment side and the NM side of the edge equipment converts the NM message carried by the Ethernet into the 64 kbit/s synchronous data service in compliance with ITU-T G.703 by using the 64k/Ethernet protocol converter, and the central equipment transparently transmits the data service. In this manner, the DCN transmission of the edge equipment is realized. To the edge equipment, the 64k/Ethernet protocol converter and the central equipment function as external DCN, which realizes the DCN communication between the NMS and the gateway NE. When all the edge equipment is in the same domain, the 64k/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 64k/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 (2009-10-30)
1-7
Figure 1-4 64k/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 64k/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-8
Issue 02 (2009-10-30)

NOTE
If the central equipment supports the bypass E1 service, the bypass E1 is preferred to transmit the NM message of the edge equipment.
E1/Ethernet protocol converters are classified into four types: point-to-point, concentrated, serially connected, and channelized. When all the edge equipment is in the same domain, the point-to-point E1/Ethernet protocol converter can be used on the NM side and the edge equipment side to establish a DCN channel, as shown in Figure 1-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 (2009-10-30)
1-9
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 network1
NM S E1/Ethernet Converter 1 (PTP type)
E1/Ethernet Converter 1 (PTP type)
LAN switch E1/Ethernet Converter n (PTP type) Edge network1 E1/Ethernet Converter n (PTP type) Central network Edge network 2
Ethernet link
E1
Radio link
1-10
Issue 02 (2009-10-30)
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.
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.
Issue 02 (2009-10-30)
1-11
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 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. 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 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 Nx64kbit/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 Nx64kbit/s data services in the E1 and converts these services into corresponding Ethernet data for transmission to the NMS, as shown in Figure 1-10.
1-12
Issue 02 (2009-10-30)
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, 64k/Ethernet protocol converter, and E1/Ethernet protocol converter respectively to establish DCN communication links. Then, the LAN switch aggregates the services to the NMS.
Issue 02 (2009-10-30)
1-13
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-14
Issue 02 (2009-10-30)
2 HWECC Solution
2
About This Chapter
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. 2.1 Feature Description With the HWECC solution, the NM message is encapsulated in the private HWECC protocol for transmission. Hence, this solution can be adopted only when the network is comprised of only the OptiX equipment that supports the HWECC protocol. 2.2 Basic Concept This topic describes the basic concepts that you need to be familiar with before you use the HWECC solution. 2.3 Availability The HWECC solution needs the support of the corresponding equipment and boards. 2.4 Relation with Other Features When the HWECC solution is used with other DCN solutions, pay attention to the relations between the HWECC solution and other DCN solutions. 2.5 Realization Principle Learning about the realization principle of the HWECC solution can help you know more about this feature. 2.6 Configuration Flow The configuration of the HWECC solution consists of two parts, namely, the configuration of communications data at the near end and the creation of NEs on the NMS. 2.7 Configuration Example This topic uses an example to describe how to plan and configure the HWECC solution according to the conditions of the network. 2.8 Task Collection This topic provides the hyperlinks of the operation tasks regarding the relevant feature. 2.9 Relevant Alarms and Events When the communication between the U2000 and an NE fails, the U2000 reports the corresponding alarm.
2 HWECC Solution
2.10 FAQs This topic provides the answers to the questions that are frequently raised when the HWECC solution is used.
2-2
Issue 02 (2009-10-30)
2 HWECC Solution
2.1 Feature Description

With the HWECC solution, the NM message is encapsulated in the private HWECC protocol for transmission. Hence, this solution can be adopted only when the network is comprised of only the OptiX equipment that supports the HWECC protocol. Figure 2-1 shows how the NM message is transmitted by using the HWECC solution. The NM message encapsulated in compliance with the HWECC protocol can be transmitted on the DCC through the optical fiber or microwave, or be transmitted over the Ethernet between the Ethernet NM interfaces or between the NE cascade interfaces. Figure 2-1 HWECC solution
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
2.2 Basic Concept

This topic describes the basic concepts that you need to be familiar with before you use the HWECC solution. 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. 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
2 HWECC Solution
NM ports or NE cascade ports on the system control unit of the NEs to realize communication through extended ECCs.
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 2-2 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
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 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.
Provides the data communication service.
Physical channels are classified into the following categories:


l
2 HWECC Solution
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.
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. 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. 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:
2 HWECC Solution
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) 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.
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.
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.
Using the hub

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 02 (2009-10-30)
2-6
2 HWECC Solution
Use a hub or other data communication equipment to connect the Ethernet NM ports on the system control unit of related NEs. Figure 2-3 Networking for the extended ECC (using a network cable)
NMS
Network cable
Radio link
Figure 2-4 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.
Issue 02 (2009-10-30)
2-7
2 HWECC Solution
Figure 2-5 Networking for the extended ECC (using network cables to connect NEs in series)
NMS
Network cable
Radio link
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. 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. 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.
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 2-6 shows an example of the multi level
2-8
Issue 02 (2009-10-30)
2 HWECC Solution
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. Figure 2-6 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.
2.3 Availability
The HWECC solution needs the support of the corresponding equipment and boards. Table 2-1 Availability of the HWECC solution Feature HWECC solution Applicable Board CST CSH SL1D IF1 IFU2 IFX2 Applicable Board Version All the functional versions All the functional versions All the functional versions All the functional versions All the functional versions All the functional versions
Issue 02 (2009-10-30)
2-9
2 HWECC Solution
2.4 Relation with Other Features

When the HWECC solution is used with other DCN solutions, pay attention to the relations between the HWECC solution and other DCN solutions.
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.
2.5 Realization Principle

Learning about the realization principle of the HWECC solution can help you know more about this feature. 2.5.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. 2.5.2 Packet Transfer In the HWECC solution, the messages between NEs are transferred in the NET layer of the NEs. 2.5.3 Extended ECC The extended ECC realizes the ECC communication by using the TCP connection between adjacent NEs as the MAC connection.
2.5.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. 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 HWECC Solution
(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 2-7 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 2-7 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) 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.
2 HWECC Solution
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.
2.5.2 Packet Transfer

In the HWECC solution, the messages between NEs are transferred in the NET layer of the NEs. Figure 2-8 shows how the HWECC solution transfers the messages from the NMS to the destination NE. Figure 2-8 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
The realization principle is as follows: 1. 2. 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.
2-12
2 HWECC Solution
3.
The application layer of the gateway NE queries the address of the destination NE in the messages. If the address of the destination NE is not 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 2-8 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 l l l
ID of the destination NE Address of the transfer NE Communication protocol stack of the transfer NE Transfer distance
2.5.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. 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.
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.
2 HWECC Solution
2.6 Configuration Flow

The configuration of the HWECC solution consists of two parts, namely, the configuration of communications data at the near end and the creation of NEs on the NMS. Table 2-2 Configuration flow for the HWECC solution Step 1 Operation A.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. If the special extended ID is required for the NE according to the planning of the DCN, change Extended ID.
A.2.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. For the GNE, set Gateway IP Address if the external DCN requires that the default gateway is configured for the NE. 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.
A.2.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. Adopt the default values for the other parameters.
In the other cases, all the parameters take the default values.
2-14
Issue 02 (2009-10-30)
2 HWECC Solution
Step 4
Operation A.2.3 Configuring the Extended ECC
Remarks Required when the number of NEs accessed through the extended ECC is more than four. Set the parameters as follows:
l l
Set Extended Mode to Specified Mode. 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. Set Opposite IP and Port for the NE that is planned as a client. That is, set Opposite IP to the IP address of the server and set Port to the same as Port of the server.
NOTE When the number of NEs accessed through the extended ECC is more than eight, you need to configure multiplelevel extended ECC.
Required for the GNE. Set the parameters as follows:

l l
Set Extended Mode to Specified Mode. 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.2.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
A.2.12 Querying ECC Routes
There is an ECC route between the GNE and each of its managed non-GNEs. There is no ECC route between the GNE and each NE on other ECC subnets. ECC routes follow the shortest path first principle.
Creating NEs on the centralize d NMS
A.1.2 Creating NEs by Using the Manual Method
It is recommended that you create NEs on the centralized NMS by using this method when you need to add one or more NEs on a large-scale network.
Issue 02 (2009-10-30)
2-15
2 HWECC Solution
Step
Operation A.1.1 Creating NEs by Using the Search Method
Remarks In other cases, this method is preferred.
2.7 Configuration Example

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

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

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

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

This topic describes the procedure for the data configuration.
Context
NOTE
In this configuration example, only the configuration information about NE201, NE202, and NE203 is provided.
Procedure
Step 1 See A.1.4 Changing the NE ID and change the NE ID. The values for the related parameters are provided as follows.
2 HWECC Solution
Parameter
Value Range NE201 NE202 202 9 (default value) NE203 203 9 (default value)
New ID New Extended ID
201 9 (default value)
Step 2 See A.2.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.2.2 Configuring DCCs and configure the DCC. The values for the related parameters are provided as follows. Parameter Value Range East and West Ports on the Ring (NE201) Enabled/Disabled Channel Type Disabled Other Microwave/ Line Ports (NE201) All the Microwave/Line Ports (NE202 and NE203) Enabled (default value) D1 (default value of the PDH microwave port whose capacity is smaller than 16 E1s) D1-D3 (default values of other ports) HWECC (default value)
Enabled (default value) D1 (default value of the PDH microwave port whose capacity is smaller than 16 E1s) D1-D3 (default values of other ports)
Protocol Type
HWECC (default value)
Step 4 See A.2.3 Configuring the Extended ECC and configure the extended ECC. The values for the related parameters are provided as follows.
Issue 02 (2009-10-30)
2-19
2 HWECC Solution
Parameter
Value Range NE201 NE202 Specified mode 1601 (default value) 0.0.0.0 (default value) 1601 (default value) NE203 Auto mode (default value) -
IP Port (on the server side) Opposite IP (on the client side) Port (on the client side)
Auto mode (default value) -
Step 5 See A.2.4 Configuring DCC Transparent Transmission and configure the transparent transmission of the DCC byte on NE201. Parameter Source Timeslot/ Port Transparent Transmission of Overhead Bytes at Source Port Sink Timeslot/Port Value Range Related parameter values of west ports on the ring D1 Related parameter values of west ports on the ring D2 Related parameter values of west ports on the ring D3
Related parameter values of east ports on the ring D1
Transparent Transmission of Overhead Bytes at Sink Port
Step 6 See A.2.12 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. The routes to all the OptiX radio transmission NEs can be queried on NE202 whereas the routes to NE101 and NE102 cannot be queried.
Step 7 See A.1.1 Creating NEs by Using the Search Method and create NEs in the search mode on the centralized NMS. The search domains include the following:
l l
The search domain when the IP address of the GNE is 10.0.0.101 The search domain when the IP address of the GNE is 11.0.0.201
2-20

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

This topic provides the hyperlinks of the operation tasks regarding the relevant feature.
Related Concepts
A.1.2 Creating NEs by Using the Manual Method A.1.4 Changing the NE ID A.2.1 Setting NE Communication Parameters A.2.2 Configuring DCCs A.2.3 Configuring the Extended ECC A.2.4 Configuring DCC Transparent Transmission A.2.12 Querying ECC Routes A.1.1 Creating NEs by Using the Search Method
2.9 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.
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.
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.
2 HWECC Solution
2.10 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
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
The NMS is faulty. In this case, the NMS generally fails to log in to all the NEs. The IP addresses of GNEs conflict. In this case, the NMS generally fails to log in to all the NEs on an ECC subnet. An ECC subnet is of an excessively large scale. In this case, the NMS generally fails to log in to the NEs that access multiple DCCs.
Q: Why does the system control and communication board on the GNE or the NE that uses the extended ECC frequently reset? A: Common causes are as follows:
l
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
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.
l l l l
2-22
3
About This Chapter
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. 3.1 Feature Description With the IP over DCC solution, the NM message is encapsulated in the standard IP protocol stack for transmission. Hence, the NM message can be transmitted only if the equipment supports the IP protocol stack. 3.2 Basic Concept This topic describes the basic concepts that you need to be familiar with before you use the IP over DCC solution. 3.3 Availability The IP over DCC solution needs the support of the corresponding boards. 3.4 Relation with Other Features 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. 3.5 Realization Principle Learning about the realization principle of the IP over DCC solution can help you know more about this feature. 3.6 Configuration Flow The configuration of the IP over DCC solution consists of two parts, that is, the configuration of communications data at the near end of the NE and the creation of the NE on the NMS. 3.7 Configuration Example This topic uses an example to describe how to plan and configure the IP over DCC solution according to the conditions of the network. 3.8 Task Collection This topic provides the hyper links of the operation tasks regarding the relevant feature.
3.9 Relevant Alarms and Events When the communication between the U2000 and an NE fails, the U2000 reports the corresponding alarm. 3.10 FAQs This topic provides the answers to the questions that are frequently raised when the IP over DCC solution is used.
3-2
Issue 02 (2009-10-30)

With the IP over DCC solution, the NM message is encapsulated in the standard IP protocol stack for transmission. Hence, the NM message can be transmitted only if the equipment supports the IP protocol stack. Figure 3-1 shows how the NM message is transmitted by using the IP over DCC solution. The NM message encapsulated in compliance with the IP protocol can be transmitted on the DCC through the optical fiber or microwave, or be transmitted over the Ethernet between the Ethernet NM interfaces or between the NE cascade interfaces. Figure 3-1 Application of the IP over DCC solution
g Ms rty a -p ck 3rd P sta I C C D
3rd-party Msg IP stack ETH Third-party NMS
g Ms t iX Op stack 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
3.2 Basic Concept

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

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

Figure 3-2 IP over DCC protocol stack architecture
Routing protocol Transport layer Network layer Data link layer Ethernet Physical layer DCC OSPF/RIP TCP/UDP IP PPP
Physical Layer
The main function of the physical layer is to provide data transmission channels for the data end equipment. Physical channels are classified into the following categories:
l
DCC channel DCCs use the DCC bytes in SDH frames, PDH or Hybrid microwave frames as the channels for communication between NEs. In the IP over DCC solution:
If the network is only comprised of the OptiX equipment, it is recommended that you use bytes D1 to D3 in SDH frames as DCCs. If the OptiX equipment is connected to the third-party equipment by using the SDH line, it is recommended that you use the DCC bytes that the third-party equipment uses (for example, bytes D1 to D3 or D4 to D12) as DCCs. In the PDH microwave frame, one or three DCC bytes in the frame can always be used as DCCs. In the Hybrid microwave frame, three DCC bytes in the frame can always be used as DCCs.
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
Routing protocols belong to the content of the application layer. The NE supports two routing protocols, namely, the open shortest path first (OSPF) protocol and routing information protocol (RIP). By default, the NE uses the OSPF protocol. The RIP protocol is used only when the interconnected third-party equipment does not support the OSPF protocol. The OSPF protocol is a dynamic routing protocol based on link status. The OSPF protocol divides an autonomous system (AS) into several areas. Route nodes exchange routing information in an area. The route nodes at the edge of an area make summary and exchange information with the routers in other areas. Areas are identified by area IDs. The area ID has the same format as the IP address. Currently, the OSPF protocol of the OptiX equipment supports only the routes within an area and does not support the routes between areas. Hence, the gateway NE and all its managed nongateway NEs must be in the same OSPF area. By default, the microwave or line port of the OptiX equipment is enabled with the OSPF protocol but the Ethernet port is not enabled with the OSPF protocol. Hence, to form a network through the Ethernet port, you need to modify the OSPF setting of the NE. In addition to the dynamic routing protocol, the NE supports static routes. Static routes are manually configured routes.
Proxy ARP
The OptiX equipment supports the proxy ARP as a supplement to the routing protocol. The proxy ARP enables the NEs in the same network segment but different domains to communicate with each other. To realize communication between such NEs, the source NE sends the ARP broadcast packet to address the route to the destination NE. The NE with the proxy ARP function enabled checks the routing table after sensing the ARP broadcast packet. If the routing table contains the destination address that the ARP broadcast packet looks for, the NE returns a ARP spoofing packet, which enables the NE that sends the ARP broadcast packet to consider that the MAC address of the NE that returns the ARP spoofing packet is the MAC address of the destination NE. In this manner, the packet that is to be sent to the destination NE is first sent to the NE with the proxy ARP function enabled and then forwarded to the destination NE. Figure 3-3 is an application example that shows how to use the proxy ARP function to realize communication between the third-party NE and the third-party NMS. In this example, the thirdparty NMS and the third-party GNE (that is, NE4) are in the same network segment (130.9.0.0). In addition, the third-party NMS and NE4 are accessed to the OptiX transmission network through the LAN. Hence, the IP addresses of NE1 and NE3 that are connected to the third-party NMS and NE4 are also in the 130.9.0.0 network segment. To realize communication between the third-party NMS and NE4, you need to enable the proxy ARP function for NE1 and NE3. In addition, on NE1, you need to configure a static route to the third-party NMS; on NE3, you need to configure a route to NE4.
Issue 02 (2009-10-30)
3-5
Figure 3-3 Application example of the proxy ARP

ARP proxy enabled NE 1 Third-party NMS NE 2 ARP proxy enabled NE 3 NE 4 NE 5
130.9.0.100
130.9.0.1
129.9.0.2
130.9.0.3
130.9.0.4
130.9.0.5
OptiX equipment Ethernet link
The corresponding routes in this figure are as follows:

l
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.
NOTE
A static route must be configured between NE1 and NE3. Otherwise, NE1 and NE3 can own local routes only to the 130.9.0.0 network segment. That is, NE3 does not own a route of the third-party NMS and NE1 does not own a local route of NE1. If the third-party NMS owns a static route to NE4 (the IP address of the gateway is the IP address of NE1) and NE4 owns a route to the third-party NMS (the IP address of the gateway is the IP address of NE3), NE1 and NE3 do not require the proxy ARP function.
3.2.2 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
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.
3.3 Availability
The IP over DCC solution needs the support of the corresponding boards. Table 3-1 Availability of the IP over DCC solution Feature IP over DCC solution Applicable Board CST CSH SL1D IF1 IFU2 IFX2 Applicable Board Version All the functional versions All the functional versions All the functional versions All the functional versions All the functional versions All the functional versions
Issue 02 (2009-10-30)
3-7

When the IP over DCC solution is used with other DCN solutions, pay attention to the relations between the IP over DCC and other DCN solutions.
l l l
The IP over DCC protocol stack of NEs can communicate with the HWECC protocol stack. The IP over DCC protocol stack of NEs cannot communicate with the OSI protocol stack. 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.

Learning about the realization principle of the IP over DCC solution can help you know more about this feature.
Principle of the Packet Transfer in Gateway Mode

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

Figure 3-5 shows how the IP over DCC solution transfers the messages originating from the NMS to a destination NE when the NMS applies the direct connection mode to access the NE. Figure 3-5 Realization principle of message transfer (direct connection mode)
Application TCP IP IP PPP Ethernet Ethernet DCC 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.

The configuration of the IP over DCC solution consists of two parts, that is, the configuration of communications data at the near end of the NE and the creation of the NE on the NMS.
Issue 02 (2009-10-30)
3-9
Table 3-2 Configuration flow for the IP over DCC solution Step 1 Operation A.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. If the extended NE ID specified during the DN planning is required, change Extended ID.

l
Set IP and Subnet Mask according to the planning of the external DCN. Set Gateway IP Address if the default GNE needs to be configured for the non-GNEs.

l
Set Protocol Type of the SDH line port and microwave port on which the IP over DCC is enabled to TCP/IP. 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. Adopt the default values for the other parameters.
A.2.7 Enabling the ARP Proxy
When the third-party NMS and the third-party GNE are in the same network segment, if the third-party NMS does not support the setting of the static route and is in the same network segment as the OptiX GNE is, the proxy ARP is enabled on the OptiX GNE; if the third-party GNE does not support the setting of the static route and is connected to the OptiX NE through the Ethernet NMS interface, the proxy ARP is enabled on the OptiX NE that is connected to the third-party GNE. Required when the OSPF protocol needs to be used between the NE and the third-party equipment. The values of the parameters are consistent with those of the third-party equipment. In the other cases, all the parameters take the default values.
A.2.6 Setting Parameters of the OSPF Protocol
A.2.5 Creating Static IP Routes
Configure the static routes of NEs according to the network planning.
3-10
Issue 02 (2009-10-30)
Step 7
Operation A.2.3 Configuring the Extended ECC
Description Required for the NEs that are connected through the Ethernet NMS interface or the subtending ports. Set the parameters as follows:
l l
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.2.13 Querying IP Routes In normal situations:
l
NEs have correct routes to other OptiX NEs or network segments in which the OptiX NEs are. NEs have correct routes to the third-party GNEs or network segments in which the NEs are. NEs have correct routes to the OptiX NMS or network segment in which the OptiX NMS is. NEs have correct routes to the third-party NMS or network segment in which the third-party NMS is.
A.1.2 Creating NEs by Using the Manual Method A.1.1 Creating NEs by Using the Search Method
It is recommended that you perform the operations to add one or more NEs on a large existing network by using the U2000.
In other cases, this method is preferred.

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

This topic 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 3-6. On the microwave transmission network, the third-party equipment is located at the edge and the OptiX equipment is located in the center. The OptiX equipment needs to transparently transmit the NM messages between the third-party equipment at the edge of the network and the third-party NMS in the center of the network. Figure 3-6 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.
3-12
Issue 02 (2009-10-30)

l
The OptiX NMS and NE1 are located at the same place and the third-party NMS is located at another place. Therefore, construct the DCN between the third-party NMS and NE1 through a router or protocol converter. Allocate IDs and IP addresses for all the NEs according to the conditions of the network. Figure 3-7 Allocation of IDs/IP addresses for all the NEs
132.9.0.7/16 11.0.0.200/16 9-6 132.9.0.6 0.0.0.0
132.9.0.8/16 9-5 131.9.0.5 0.0.0.0 9-4 130.9.0.4 0.0.0.0 9-3 130.9.0.3 0.0.0.0
11.0.0.100/16
10.0.0.200/16 9-1 10.0.0.1 0.0.0.0 10.0.0.100/16 Extended ID-Basic ID IP address Gatew ay 9-2 129.9.0.2 0.0.0.0
Plan NE routes.
Configure a static route between NE1 and the third-party NMS (11.0.0.100). The gateway is the interface address of the router 10.0.0.200. Configure a static route between NE3 and the network segment 131.9.0.0. The gateway is the IP address of NE4 130.9.0.4. Configure a static route between NE3 and the network segment 132.9.0.0. The gateway is the IP address of NE4 130.9.0.4. Configure a static route between NE4 and the network segment 129.9.0.0. The gateway is the IP address of NE3 130.9.0.3. Configure a static route between NE4 and the network segment 10.0.0.0. The gateway is the IP address of NE3 130.9.0.3. Configure a static route between NE4 and the third-party NMS (11.0.0.100). The gateway is the IP address of NE3 130.9.0.3.

Context
NOTE
In this configuration example, only the configuration information about the typical NEs, NE1, NE3, and NE4 is provided.
Issue 02 (2009-10-30)
3-13
Procedure
Step 1 See A.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.2.1 Setting NE Communication Parameters and set the NE communication parameters. The values for the related parameters are provided as follows. Parameter Value Range NE1 IP Address Gateway IP Address Subnet Mask 10.0.0.1 0.0.0.0 (default value) 255.255.0.0 (default value) NE3 130.9.0.3 0.0.0.0 (default value) 255.255.0.0 (default value) NE4 130.9.0.4 0.0.0.0 (default value) 255.255.0.0 (default value)
Step 3 See A.2.2 Configuring DCCs and configure the DCCs. The values for the related parameters are provided as follows. Parameter Value Range All Ports (NE201) Other Line Ports (NE201) 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) TCP/IP All Line Ports (NE202 and NE203) Enabled (default value) D1 (default value of the PDH microwave port whose capacity is smaller than 16 E1s) D1-D3 (default values of other line ports) TCP/IP
Enabled/Disabled Channel Type
Enabled (default value) D1 (default value of the PDH microwave port whose capacity is smaller than 16 E1s) D1-D3 (default values of other line ports)
Protocol Type
TCP/IP
Step 4 See A.2.5 Creating Static IP Routes and create the static IP routes.
The values for the related parameters are provided as follows. Paramete r Destinatio n Address Subnet Mask Gateway IP Address Value Range NE1 11.0.0.100 255.255.0. 0 10.0.0.200 NE3 131.9.0.0 255.255.0. 0 130.9.0.4 NE3 132.9.0.0 255.255.0. 0 130.9.0.4 NE4 129.9.0.0 255.255.0. 0 130.9.0.3 NE4 10.0.0.0 255.255.0. 0 130.9.0.3 NE4 11.0.0.100 255.255.0. 0 130.9.0.3
Step 5 See A.2.3 Configuring the Extended ECC and configure the extended ECC. The values for the related parameters are provided as follows. Parameter Value Range NE1 IP Port (on the server side) Opposite IP (on the client side) Port (on the client side) Specified mode 1601 (default value) 0.0.0.0 (default value) 1601 (default value) NE3 Specified mode 1601 (default value) 0.0.0.0 (default value) 1601 (default value) NE4 Specified mode 1601 (default value) 0.0.0.0 (default value) 1601 (default value)
Step 6 See A.2.12 Querying ECC Routes and query the ECC routes. The expected result is as follows:
l
On NE1,
The route and gateway between NE1 and 129.9.0.2, 130.9.0.3, 130.9.0.0, 131.9.0.0, and 132.9.0.0 are 129.9.0.2. The route and gateway between NE1 and 10.0.0.0 are 10.0.0.1. The route and gateway between NE1 and 11.0.0.100 are 10.0.0.200. The route and gateway between NE3 and 131.9.0.0 and 132.9.0.0 are 130.9.0.4. The route and gateway between NE3 and 130.9.0.0 are 130.9.0.3. The route and gateway between NE3 and 129.9.0.2, 10.0.0.1, 10.0.0.0, and 11.0.0.100 are 129.9.0.2. The route and gateway between NE4 and 131.9.0.0 and 132.9.0.0 are 131.9.0.5. The route and gateway between NE4 and 130.9.0.0 are 130.9.0.4.
On NE3,

On NE4,

Issue 02 (2009-10-30)
The route and gateway between NE4 and 129.9.0.0, 10.0.0.0, 10.0.0.1, and 11.0.0.100 are 130.9.0.3.
Step 7 See A.1.1 Creating NEs by Using the Search Method and create the NEs on the centralized NMS. 10.0.0.1 is the search domain of the IP address of the GNE. In normal cases, all the NEs can be created on the centralized NMS. ----End
Postrequisite
To ensure the interconnection between the third-party NMS and the third-party GNE, the following routes need to be added.
l
Route between the third-party NMS and the network segment 132.9.0.0. The gateway is 11.0.0.200. Route between NE7 and the network segment 11.0.0.100. The gateway is 132.9.0.6.
3.8 Task Collection

This topic provides the hyper links of the operation tasks regarding the relevant feature.
Related Concepts
A.1.2 Creating NEs by Using the Manual Method A.1.4 Changing the NE ID A.2.1 Setting NE Communication Parameters A.2.2 Configuring DCCs A.2.5 Creating Static IP Routes A.2.6 Setting Parameters of the OSPF Protocol A.2.7 Enabling the ARP Proxy A.2.13 Querying IP Routes A.2.3 Configuring the Extended ECC A.1.1 Creating NEs by Using the Search Method

Relevant Alarms
l
3-16
Issue 02 (2009-10-30)

l
Relevant Events
None.
3.10 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. The OSI over DCC solution applies the transfer function of the network layer of the protocol stack. Hence, no extra overhead and service channel are needed. The IP over DCC solution allows different vendors to multiplex the same DCC channel. The NMS of a vendor need not be directly connected to the equipment of the vendor. The IP over DCC function supports the automatic rerouting function and hence can protect the channel that transmits the management information. The IP over DCC solution enables the development of management tools that are based on the mature IP protocol stack, for example, FTP and Telnet.
l l l
Q: Why does the NMS always fail to log in to an NE? A: Common causes are as follows:
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.
Issue 02 (2009-10-30)
Check the DCC bytes used by DCCs with the maintenance staff of third-party equipment.
2. 3. 4. 5.
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. Query IP routes at the gateway NE to check if there is a route to the interconnected NE and a route to other third-party equipment. If no route is obtained, the OSPF protocol interconnection fails.
6.
3-18
Issue 02 (2009-10-30)
4
About This Chapter
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 manages 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. 4.1 Feature Description With the OSI over DCC solution, the NM message is encapsulated in the standard IP protocol stack for transmission. Hence, this solution can be adopted only if the OptiX equipment supports the OSI protocol stack. In addition, this solution can be adopted when the equipment in the center of the network needs to provide an NM message transmission path over OSI for the NE at the edge of the network. 4.2 Basic Concept This topic describes the basic concepts that you need to be familiar with before you use the OSI over DCC solution. 4.3 Availability The OSI over DCC solution needs the support of the corresponding boards. 4.4 Relation with Other Features 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. 4.5 Realization Principle Learning about the realization principle of the OSI over DCC solution can help you know more about this feature. 4.6 Configuration Flow The configuration of the OSI over DCC solution consists of two parts, that is, the configuration communications data at the peer end of the NE and the creation of the NE on the NMS. 4.7 Configuration Example This topic uses an example to describe how to plan and configure the OSI over DCC solution according to the conditions of the network. 4.8 Task Collection This task collection includes all the tasks related to features.
4.9 Relevant Alarms and Events When the communication between the U2000 and an NE fails, the U2000 reports the corresponding alarm. 4.10 FAQs This topic provides the answers to the questions that are frequently raised when the OSI over DCC solution is used.
4-2
Issue 02 (2009-10-30)

With the OSI over DCC solution, the NM message is encapsulated in the standard IP protocol stack for transmission. Hence, this solution can be adopted only if the OptiX equipment supports the OSI protocol stack. In addition, this solution can be adopted when the equipment in the center of the network needs to provide an NM message transmission path over OSI for the NE at the edge of the network. Figure 4-1 shows how the NM message is transmitted by using the OSI over DCC solution. The NM message encapsulated in compliance with the OSI protocol can be transmitted on the DCC through the optical fiber or microwave, or be transmitted over the Ethernet between the Ethernet NM interfaces or between the NE cascade interfaces. Figure 4-1 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
4.2 Basic Concept

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

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

Figure 4-2 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.
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.
4-4
Issue 02 (2009-10-30)
Network Layer
The main function of the network layer is to specify the network layer address for a network entity and to provide the transferring and addressing functions. The NE applies the ISO-defined connectionless network service (CLNS) to realize the network layer function. The CLNS is comprised of the following three protocols:
l
Connectionless network protocol (CLNP) The CLNP protocol complies with ISO 8473. It has functions similar to the IP in the TCP/ IP protocol stack. In the CLNP protocol, the network service access point (NSAP) works as the network layer address. The NSAP functions as the IP address in the IP protocol. Its address format is as shown in Figure 4-3. Figure 4-3 Format of the NSAP address
IDP Higher order DSP AFI IDI+pad DFI ORG RES RD Area System ID 9 10 11 12 13 14 15 16 17 18 19
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 4-3 and has one to thirteen bytes. The area ID is used to address the routes between areas. The NSAPs of the NEs in the same L1 route area must have the same area ID but those in the same L2 route area can have different area IDs. You can manually set the area ID. The default value of the area ID is 0x47000400060001.
SYS ID The SYS ID refers to the system ID shown in Figure 4-3 and has six bytes. The SYS ID is used to address the routes within an area. The value of the first three bytes of the SYS ID of the OptiX equipment is always 0x08003E. The last three bytes are the NE ID.
NSEL The NSEL refers to the port ID of the network layer protocol. It has one byte. The NSEL of the OptiX equipment is always 0x1D.
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
Issue 02 (2009-10-30)
4-5
neighbor of the NE in a different area and participates only in the routes in its own area. It issues a default route that points to its closest L2 NE and accesses other areas through the default route. The NE whose role is L2 can be a neighbor of the L2 NE in a different area and also can participate in the routes in the backbone area. The backbone area is formed by consecutive L2 NEs. That is, the L2 NEs in the backbone area must be consecutive (connected). In the network as shown in Figure 4-4, as the L2 NEs in the backbone area are not consecutive, the NEs in area 4 are isolated from the NEs in other areas. By default, the role of the OptiX equipment is L1. Figure 4-4 Layered routes of IS-IS protocol routes (L2 not consecutive)
OSI DCN T2000
L1 L2
Area 2
Area 3
Area 1
Backbone
Area 4
NOTE
L2 NEs are classified into two categories, the NE with only the L2 role and the NE with both the L2 role and the L1 role. In general, an L2 NE has the L1 role.
l
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.
4-6
Issue 02 (2009-10-30)
OSI Tunnel
This solution is used when the transmission network that adopts the OSI over DCC solution needs to use the transmission network that adopts the IP over DCC solution to transparently transmit the NM message. The OSI tunnel function involves that a virtual LAPD channel is established between the NEs on the IP network. In this manner, the NM message encapsulated in compliance with the OSI protocol is transparently transmitted. Figure 4-5 shows an application example of the OSI tunnel. In this example, the third-party equipment adopts the OSI over DCC solution and needs to pass the service through the OptiX transmission network that adopts the IP over DCC solution Hence, an OSI tunnel needs to be established between NE1 and NE3. Perform the following steps to delete the VLAN service:
l
Note that the SDH line connecting the OptiX equipment to the third-party equipment adopts the DCC over OSI protocol, whereas the SDH line and radio link inside the network adopt the IP over DCC protocol. Enable the OSI tunnel function on NE1. The IP address of the opposite NE is the IP address of NE3 (that is, 129.9.0.3). The LAPD role is "network". Enable the OSI tunnel function on NE3. The IP address of the opposite NE is the IP address of NE1 (that is, 129.9.0.1). The LAPD role is "user".
Figure 4-5 Application example of the OSI tunnel

OSI tunnel enabled NE 1 NE 2 OSI tunnel enabled NE 3
129.9.0.1 129.9.0.2
129.9.0.3
Third-party NMS
OptiX equipment Ethernet link
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.
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
Direct Access Mode

In the direct access mode, the NMS accesses an NE as the gateway NE. All transfer NEs on the access path query the L1 routing table and L2 routing table of the network layer according to the NSAP address of the NE to be accessed to obtain the corresponding route. The L1 routing table and the L2 routing table are based on the IS-IS protocol. Each route item in the L1 routing table includes the following:
l l l
Destination System ID Cost Adjacency No.
Each route item in the L2 routing table includes the following:

l l l
Destination AREA ID Cost Adjacency No.

NOTE
The adjacency No. is the ID of an LAPD connection. You can query the link adjacency table of the data link layer to obtain the mapping relation between the adjacency No. and the LAPD connection.
In the OSI over DCC solution, theoretically, the NMS can access any NE using the direct access mode, that is, the NMS can consider any NE as the gateway NE. To improve the communication efficiency, there should not be too many NEs that are accessed in the direct access mode in a network.
4.3 Availability
The OSI over DCC solution needs the support of the corresponding boards. Table 4-1 Availability of the OSI over DCC solution Feature OSI over DCC solution
4-8
Applicable Board CST
Applicable Board Version All the functional versions

Issue 02 (2009-10-30)
Feature
Applicable Board CSH SL1D IF1 IFU2 IFX2
Applicable Board Version All the functional versions All the functional versions All the functional versions All the functional versions All the functional versions

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

Learning about the realization principle of the OSI over DCC solution can help you know more about this feature.
Gateway Mode
Figure 4-6illustrates how the OSI over DCC solution transfers NMS messages to a non-gateway NE when the NMS adopts the gateway mode to access the NE.
Issue 02 (2009-10-30)
4-9
Figure 4-6 Realization principle of message transferring (gateway mode)

Application TP4 ES-IS/CLNP Application TP4 TP4 IS-IS/CLNP LAPD DCC Transfer NE Application TP4 IS-IS/CLNP LAPD DCC Destination NE
ES-IS/CLNP IS-IS/CLNP LAPD
Ethernet
Ethernet DCC
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 4-6 is OSI, the gateway NE transfers the messages to the transfer NE through the OSI protocol stack. After receiving the packet that encapsulates the messages, the network layer of the transfer NE queries the destination NSAP address of the packet. If the NSAP address is not the same as the address of the local station, the transfer NE queries the L1 routing table or the L2 routing table according to the destination NSAP address to obtain the corresponding route, and then transfers the packet. After receiving the packet, the network layer of the destination NE reports the packet to the application layer through the transport layer because the destination NSAP address of the packet is the same as the address of the local station. The application layer acts according to the message sent from the NMS.
2. 3.
4.
5.
Direct Connection Mode

Figure 4-7 illustrates how the OSI over DCC solution transfers NMS messages to a destination NE when the NMS adopts the direct connection mode to access the NE.
4-10
Issue 02 (2009-10-30)
Figure 4-7 Realization principle of message transferring (direct connection mode)

Application TP4 ES-IS/CLNP IS-IS/ES-IS/CLNP LAPD Ethernet Ethernet DCC 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.

The configuration of the OSI over DCC solution consists of two parts, that is, the configuration communications data at the peer end of the NE and the creation of the NE on the NMS. Table 4-2 Configuration flow for the OSI over DCC solution Step 1 Operation A.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. If the extended NE ID specified during the DCN planning is required, change Extended ID.

l
Set NSAP Address according to the external DCN planning. 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.
Issue 02 (2009-10-30)
4-11
Step 3
Operation A.2.2 Configuring DCCs
Description 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. Set LAPD Role at the ends of an LAPD link to Network and User. 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. Adopt the default values for the other parameters.
A.2.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.
NOTE By default, the CLNS role of the NE is set to L1.
A.2.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 passthrough node. Set LAPD Actor of the two pass-through nodes to Network and User.
A.2.3 Configuring the Extended ECC
Required for the NEs that are connected through the Ethernet NMS interface or the subtending ports. Set the parameters as follows:
l l
NOTE This operation is performed to disable the automatic extended ECC function of the NE.
4-12
Issue 02 (2009-10-30)
Step 7
Operation A.2.14 Querying OSI Routes
Description In normal situations:

l
The L1 routing table of the L1 NE has the routes to all the NEs in the area. 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.2 Creating NEs by Using the Manual Method A.1.1 Creating NEs by Using the Search Method
It is recommended that you perform the operations to add one or more NEs on a large existing network by using the U2000.

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

This topic 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 4-8. The total number of equipments on the network is more than 50. The third-party equipment supports only the OSI over DCC solution.
Issue 02 (2009-10-30)
4-13
Figure 4-8 Networking diagram
NE203 Third-party NMS OSI DCN Network cable NE201
NE204
NE103
NE101 NE102 NE202
OptiX equipment Network cable

l
The number of OptiX equipments and third-party equipments is more than 50. It is, however, recommended that the number of NEs in each area is equal to or smaller than 32. Therefore, the equipments are divided into two areas and four NEs on the bone network are selected as L2 NEs.
4-14
Issue 02 (2009-10-30)

l
Figure 4-9 Allocation of NE areas

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

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.4 Changing the NE ID and modify the NE ID. The values for the related parameters are provided as follows.
Parameter
Value Range NE101 NE102 102 9 (default value) NE103 103 9 (default value)
101 9 (default value)
Step 2 See A.2.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.2.2 Configuring DCCs and configure the DCCs. The values for the related parameters are provided as follows. Parameter Value Range NE101 Enabled/Disabled Channel Type Enabled (default value) D1 (default value of the PDH microwave port whose capacity is smaller than 16 E1s) D1-D3 (default values of other line ports) Protocol Type LAPD Role OSI Network NE102 Enabled (default value) D1 (default value of the PDH microwave port whose capacity is smaller than 16 E1s) D1-D3 (default values of other line ports) OSI User (port that is connected to NE101) Network (port that is connected to other NEs) NE103 Enabled (default value) D1 (default value of the PDH microwave port whose capacity is smaller than 16 E1s) D1-D3 (default values of other line ports) OSI User (port that is connected to NE101)
Step 4 See A.2.8 Configuring the CLNS Role and configure the CLNS role. The values for the related parameters are provided as follows. Parameter Value Range NE101 Configuration Role
4-16
NE102 L2
NE103 L1 (default value)

Issue 02 (2009-10-30)
L2
Step 5 See A.2.3 Configuring the Extended ECC and configure the extended ECC. The values for the related parameters are provided as follows. Parameter Value Range NE103 IP 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.2.14 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. 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. On NE103, the routes of NE101 and NE103 can be viewed in the L1 routing table.
Step 7 See A.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
4.8 Task Collection

This task collection includes all the tasks related to features.
Related Concepts
A.1.2 Creating NEs by Using the Manual Method A.1.4 Changing the NE ID A.2.1 Setting NE Communication Parameters A.2.2 Configuring DCCs A.2.8 Configuring the CLNS Role A.2.9 Configuring the OSI Tunnel A.2.14 Querying OSI Routes A.2.3 Configuring the Extended ECC A.1.1 Creating NEs by Using the Search Method

Relevant Alarms
l
Relevant Events
None.
4.10 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
The disadvantages are as follows:

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

l
The OSI network is not applied as wide as the TCP/IP network and there are not many OSIbased management tools.
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. 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.
Issue 02 (2009-10-30)
4-19
DCC Transparent Transmission Solution
About This Chapter

Using the DCC 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. 5.1 Feature Description In general, the transmission equipment uses only bytes D1 to D3 as DCCs and does not use other DCC bytes. Based on this characteristic, the DCC transparent transmission solution applies different DCCs to transmit the NM messages of different vendors to realize communication between NM messages. The NMS of a vendor can manage only the NEs of the vendor. Hence, this solution has a great limitation. That is, this solution is applicable only when the network is comprised of the OptiX equipment and the third-party SDH equipment that does not support the IP over DCC function or OSI over DCC function. 5.2 Availability The DCC transparent transmission solution needs the support of the corresponding boards. 5.3 Relation with Other Features If you apply the DCC transparent transmission solution to communicate NM messages when the OptiX equipment is used together with third-party equipment to form a network, you can use any of the HWECC protocol stack, IP protocol stack, and OSI protocol stack to manage the OptiX equipment. It is recommended that you use the HWECC protocol stack. 5.4 Realization Principle The OptiX equipment realizes the transparent transmission of overheads through the overhead cross-connect matrix. 5.5 Configuration Flow The configuration of the DCC transparent transmission solution consists of two parts, namely, the configuration of communications data at the near end and the creation of NEs on the NMS. 5.6 Configuration Example This topic uses an example to describe how to plan and configure the DCC transparent transmission solution according to the conditions of the network. 5.7 Task Collection This topic provides the hyperlinks of the operation tasks regarding the relevant feature.
5.8 Relevant Alarms and Events When the communication between the U2000 and an NE fails, the U2000 reports the corresponding alarm. 5.9 FAQs This topic provides the answers to the questions that are frequently raised when the DCC transparent transmission solution is used.
5-2
Issue 02 (2009-10-30)

In general, the transmission equipment uses only bytes D1 to D3 as DCCs and does not use other DCC bytes. Based on this characteristic, the DCC transparent transmission solution applies different DCCs to transmit the NM messages of different vendors to realize communication between NM messages. The NMS of a vendor can manage only the NEs of the vendor. Hence, this solution has a great limitation. That is, this solution is applicable only when the network is comprised of the OptiX equipment and the third-party SDH equipment that does not support the IP over DCC function or OSI over DCC function. When DCC bytes are used to transparently transmit NM messages, there are two networking scenarios:
l l
The OptiX equipment is at the edge of a network. The OptiX equipment is in the center of a network.
OptiX Equipment at the Edge of a Network

In this networking scenario, there are two possibilities:
l
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, as shown in Figure 5-1.
Figure 5-1 DCC transparent transmission solution when the OptiX equipment is at the edge of a network (1)
D4-D12
D4-D12 D4-D12
D4-D12
OptiX equipment
Third-party equipment
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, as shown in Figure 5-2.
Issue 02 (2009-10-30)
5-3
Figure 5-2 DCC transparent transmission solution when the OptiX equipment is at the edge of a network (2)
D1-D3
D1-D3 D1-D3
D1-D3
OptiX equipment
OptiX Equipment in the Center of a Network

In this networking scenario, there are two possibilities:
l
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, as shown in Figure 5-3.
Figure 5-3 DCC transparent transmission solution when the OptiX equipment is in the center of a network (1)
D1-D3 D1-D3
D1-D3 D1-D3
OptiX equipment
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, as shown in Figure 5-4.
5-4
Issue 02 (2009-10-30)
Figure 5-4 DCC transparent transmission solution when the OptiX equipment is in the center of a network (2)
D4-D12
D4-D12
D4-D12
D4-D12
OptiX equipment
5.2 Availability
The DCC transparent transmission solution needs the support of the corresponding boards. Table 5-1 Availability of the DCC Transparent Transmission Solution Feature DCC transparent transmission solution Applicable Board SL1D IF1 Applicable Board Version All the functional versions All the functional versions

If you apply the DCC transparent transmission solution to communicate NM messages when the OptiX equipment is used together with third-party equipment to form a network, you can use any of the HWECC protocol stack, IP protocol stack, and OSI protocol stack to manage the OptiX equipment. It is recommended that you use the HWECC protocol stack.

The OptiX equipment realizes the transparent transmission of overheads through the overhead cross-connect matrix. In the receiving direction:
Issue 02 (2009-10-30)
5-5
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. 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 5-5 shows how an NE uses bytes D1 to D3 as DCCs to transparently transmit bytes D4 to D12. Figure 5-5 Realization principle of the DCC transparent transmission
D4-D12 Overhead crossconnect matrix D1-D3 CPU
SDH signal
Overhead bus
Overhead bus
SDH signal
Line processing unit
System control unit
Line processing unit

The configuration of the DCC transparent transmission solution consists of two parts, namely, the configuration of communications data at the near end and the creation of NEs on the NMS.
5-6
Issue 02 (2009-10-30)
Table 5-2 Configuration flow for the DCC transparent transmission solution Step 1 Operation A.1.4 Changing the NE ID Remarks Required. Set the parameters as follows:
l

l
For the GNE, set IP Address and Subnet Mask according to the planning of the external DCN. For the GNE, set Gateway IP Address if the external DCN requires that the default gateway is configured for the NE. 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 when the third-party equipment uses bytes D1 to D3 as DCCs. Set the parameters as follows:
l l
Set Channel Type of the SDH port to D4-D12. Adopt the default values for the other parameters.
In the other cases, all the parameters take the default values. 4 A.2.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
A.2.13 Querying IP Routes
There is an ECC route between the GNE and each of its managed non-GNEs.
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.
Issue 02 (2009-10-30)
5-7
Step
Operation A.1.1 Creating NEs by Using the Search Method
Remarks In the other cases, this method is preferred.

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

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

l
The networking is formed by the OptiX radio transmission equipment and the third-party SDH optical transmission equipment and the third-party equipment does not support the IP over DCC or OSI over DCC solution. Therefore, the DCC transparent transmission solution is used. Select NE1 that is closest to the NMS as GNE. Allocate IDs and IP addresses for all the NEs according to the situation of the network.
l l
Issue 02 (2009-10-30)
5-9

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

Context
NOTE
In this configuration example, only the configuration information about NE1 is provided.
Procedure
Step 1 See A.1.4 Changing the NE ID and change the NE ID. The values for the related parameters are provided as follows.
5-10
Issue 02 (2009-10-30)
Parameter
Value Range NE1
1 9 (default value)
Step 2 See A.2.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.2.2 Configuring DCCs and configure the DCC. The values for the related parameters are provided as follows. Parameter Value Range SDH Line Port on the Ring Enabled/Disabled Channel Type Protocol Type Enabled (default value) D4-D12 HWECC (default value) SDH Microwave Port on the Ring Enabled (default value) D4-D12 HWECC (default value)
Step 4 See A.2.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 (2009-10-30)
5-11
Parameter Sink Timeslot/Port
Value Range Related parameter value of the SDH microwave port on the ring D1 Related parameter value of the SDH microwave port on the ring D2 Related parameter value of the SDH microwave port on the ring D3
Transparent Transmission of Overhead Bytes at Sink Port
Step 5 See A.2.12 Querying ECC Routes and query the ECC route. The expected result is as follows:
l
The ECC routes to NE2, NE3, and NE4 can be queried on NE1.
Step 6 See A.1.1 Creating NEs by Using the Search Method and create NEs in the search mode on the centralized NMS. The search domains include the following: The search 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
5.7 Task Collection

Related Concepts
A.1.2 Creating NEs by Using the Manual Method A.2.2 Configuring DCCs A.2.4 Configuring DCC Transparent Transmission A.2.12 Querying ECC Routes A.1.1 Creating NEs by Using the Search Method

Relevant Alarms
l
GNE_CONNECT_FAIL
5-12
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
Relevant Events
None.
5.9 FAQs
This topic provides the answers to the questions that are frequently raised when the DCC transparent transmission solution is used. Q: Compared with other solutions for communicating NM information, what advantages and disadvantages does the DCC transparent transmission solution have? A: The advantages are as follows:
l
The IP protocol stack or the OSI protocol stack need not be used. Therefore, a small amount of system resources are occupied. The configuration is simple.
The disadvantages are as follows:

l l l
The NMS of each vendor can be accessed to the DCN only through its own NE. Only DCC bytes can be transparently transmitted. The automatic rerouting function is weak.
Q: How can I use the DCC transparent transmission solution to interconnect the OptiX equipment with the third-party equipment? A: The steps are as follows: 1. 2. 3. 4. Check the DCC bytes used by DCCs with the maintenance staff of third-party equipment to ensure that different vendors use different DCC bytes. Analyze the routes for DCC transparent transmission with the maintenance staff of thirdparty equipment. Configure data according to the negotiated results and the network planning. Query ECC routes at the GNE. If there are no routes to non-GNEs, the interconnection fails.
DCC Transparent Transmission Through the External Clock Interface Solution
About This Chapter

Using the DCC transparent 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. 6.1 Feature Description By using the DCC transparent transmission through the external clock interface solution, DCC bytes are loaded into the timeslots of the E1 provided by the external clock interface and then transmitted. In this manner, DCC bytes can be transparently transmitted only if third-party network can transmit E1 services. 6.2 Availability The DCC transparent transmission through the external clock interface solution needs the support of the corresponding equipment and boards. 6.3 Relation with Other Features If you apply the DCC transparent transmission through the external clock interface solution to communicate NM messages when the OptiX equipment is used together with third-party equipment to form a network, you can use any of the HWECC protocol stack, IP protocol stack, and OSI protocol stack to manage the OptiX equipment. It is recommended that you use the HWECC protocol stack. 6.4 Realization Principle It is through the overhead cross-connect matrix that the OptiX equipment realizes the transparent transmission of DCCs through the external clock interface. 6.5 Configuration Procedure To configure the solution of transparently transmitting DCCs through the external clock interface, you need to perform other configuration operations in addition to configuring the HWECC solution. 6.6 Configuration Example
This topic uses an example to describe how to plan and configure the DCC transparent transmission solution according to the actual network conditions through a detailed example. 6.7 Task Collection This topic provides the hyperlinks of the operation tasks regarding the DCC transparent transmission through the external clock interface feature. 6.8 Relevant Alarms and Events When there is a fault in communication between the U2000 and an NE, the U2000 reports the corresponding alarm. 6.9 FAQs This topic provides the answers to the questions that are frequently raised when the DCC transparent transmission through the external clock interface solution is used.
6-2
Issue 02 (2009-10-30)

By using the DCC transparent transmission through the external clock interface solution, DCC bytes are loaded into the timeslots of the E1 provided by the external clock interface and then transmitted. In this manner, DCC bytes can be transparently transmitted only if third-party network can transmit E1 services. There are two networking scenarios for the DCC transparent transmission through the external clock interface solution:
l
Direct Access Mode The NE is accessed to the third-party network through the external clock interface. Indirect Access Mode The NE is accessed to the third-party network through the service interface.
Direct Access Mode

Figure 6-1 provides a networking example of the direct access mode. In this example, the thirdparty network is a PDH network that provides E1 interfaces for the OptiX NEs at both ends. In this case, you can directly connect an E1 cable that connects to an external clock interface to the third-party network. The third-party network then transmits the E1 as an ordinary service. Thus, DCC bytes are transparently transmitted between the two NEs. A special application of the direct access mode is to use an E1 cable to directly connect the external clock interfaces of two OptiX NEs. Figure 6-1 Networking example for the DCC transparent transmission through the external clock interface solution (direct access mode)
External clock interface DCC bytes E1 cable PDH netw ork External clock interface DCC bytes E1 cable
Indirect Access Mode

Figure 6-2 provides a networking example of the indirect access mode. In this example, the third-party network is an SDH/PDH hybrid network. PDH signals are transmitted on the transmission path although the network provides SDH optical interfaces for the OptiX NEs at both ends. In this case, first use an E1 cable to connect the external clock interface to an E1 port of a 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 6-2 Networking example for the DCC transparent transmission through the external clock interface solution (indirect access mode)
External clock interface E1 port of a tributary unit DCC bytes SDH/PDH netw ork Fiber DCC bytes Fiber External clock interface E1 port of a tributary unit
6.2 Availability
The DCC transparent transmission through the external clock interface solution needs the support of the corresponding equipment and boards. Table 6-1 Availability of the DCC transparent transmission through the external clock interface solution Feature DCC Transparent Transmission Through the External Clock Interface Solution Applicable Board CST CSH Applicable Board Version All the functional versions All the functional versions

If you apply the DCC transparent transmission through the external clock interface solution to communicate NM messages when the OptiX equipment is used together with third-party equipment to form a network, you can use any of the HWECC protocol stack, IP protocol stack, and OSI protocol stack to manage the OptiX equipment. It is recommended that you use the HWECC protocol stack.

It is through the overhead cross-connect matrix that the OptiX equipment realizes the transparent transmission of DCCs through the external clock interface. In the receiving direction:
6-4
Issue 02 (2009-10-30)
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 6-3 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. Figure 6-3 Realization principle of the DCC transparent transmission through the external clock interface
External clock interface Overhead bus Clock unit
Overhead crossconnect matrix D1-D3 CPU
System control unit
6.5 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.
Issue 02 (2009-10-30)
6-5
Table 6-2 Procedure for configuring the solution of transparently transmitting DCCs through the external clock interface Step 1 Operation A.2.2 Configuring DCCs Remarks Required. Set the parameters as follows:
l
Set Enabled/Disabled of the used external clock interface to Enabled. Adopt the default values for the other parameters.
A.5.1 Creating the Cross-Connections of Point-to-Point Services
In the case of indirect access, perform this operation to set up the point-to-point cross-connection between the E1 port to which the external interface is connected and the specific timeslot of the port on the SDH line board. This port on the SDH line board is used to interconnect with the third-party equipment. The specific timeslot is used to transparently transmit the NM messages.

This topic uses an example to describe how to plan and configure the DCC transparent transmission solution according to the actual network conditions through a detailed example. 6.6.1 Networking Diagram The topic describes the networking information of the NEs. 6.6.2 Service Planning The service planning information contains all the parameter information required for configuring the NE data. 6.6.3 Configuration Process This topic describes the procedure for the data configuration.

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

l
Because NE1 is connected to the third-party equipment through the SDH line, the indirect connection mode is adopted. Because NE2 is connected to the third-party equipment through E1 interfaces, the direct connection mode is adopted. NE1 and NE2 use bytes D1 to D3 to transmit NM messages. In terms of E1, connect the external clock interface to E1 port 1 (4-SP3S-1 port) on the SP3S board in slot 4. According to the negotiation result with the third-party equipment, use the first VC-12 timeslot of SL1D in slot 6 (6-SL1D-1 port) of the control, switch, and clock board on NE1 to transparently transmit the network management messages of the OptiX equipment.
l l

Context
NOTE
l l
In this configuration example, only the configuration information about typical NEs (NE1 and NE2) is provided. In this configuration example, only the configurations different from the HWECC solution are provided.
Issue 02 (2009-10-30)
6-7
Procedure
Step 1 See A.2.2 Configuring DCCs and configure the DCC channel. The values for the related parameters are provided as follows. Parameter Value Range External Clock Interface (NE1) Enabled/Disabled Channel Type Protocol Type Enabled D1-D3 (default value) HWECC (default value) External Clock Interface (NE2) Enabled D1-D3 (default value) HWECC (default value)
Step 2 See A.5.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 Direction Source Slot Source VC4 Source Timeslot Range(e.g.1,3-6) Sink Slot Sink VC4 Sink Timeslot Range(e.g.1,3-6) VC-12 (default value) Bidirectional (default value) 4-SP3S 1 6-SL1D-1 1 1
----End
6.7 Task Collection

This topic provides the hyperlinks of the operation tasks regarding the DCC transparent transmission through the external clock interface feature.
Related Concepts
A.2.2 Configuring DCCs A.5.1 Creating the Cross-Connections of Point-to-Point Services
6-8
Issue 02 (2009-10-30)

When there is a fault in communication between the U2000 and an NE, the U2000 reports the corresponding alarm.
Relevant Alarms
l
Relevant Events
None.
6.9 FAQs
This topic provides the answers to the questions that are frequently raised when the DCC transparent transmission through the external clock interface solution is used. Q: Which of the DCC transparent transmission through the external clock interface solution and the extended ECC solution is used to transfer NM messages between two NEs when the two NEs are installed back-to-back? A: When the distance between the two NEs is within the transmission range of a network cable (the maximum transmission distance of a network cable is within the range from 50 meters to 100 meters), use the extended ECC solution, that is, use a network cable to connect the Ethernet NM ports or NE cascading ports of the two NEs. When the distance between the two NEs exceeds the maximum transmission distance of a network cable but is less than the transmission distance of an E1 cable (the maximum transmission distance of an E1 cable is 300 meters), use the DCC transparent transmission through the external clock interface solution. This is because the extended ECC consumes much less system resources than the DCC transparent transmission through the external clock interface. Q: Can the external clock interface be used to transparently transmit orderwire overhead bytes when the DCC transparent transmission through the external clock interface solution is already applied? A: Yes, the external clock interface can be used to transparently transmit orderwire bytes when the DCC transparent transmission through the external clock interface solution is already applied. This is because the DCC bytes occupy only certain timeslots of the E1 service that is
transmitted by the external clock interface. Hence, the other timeslots of the E1 service can be used to transparently transmit the overhead bytes used by orderwire calls, asynchronous data interface services, and synchronous data interface services. Q: Why does the configuration of the DCC transparent transmission through the external clock interface solution fail? A: Common causes are as follows:
l
The external clock source or the working mode for outputting the external clock is modified to 2 MHz. The wayside E1 service is configured.
6-10
Issue 02 (2009-10-30)
7
About This Chapter
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 950 equipment and the OptiX packet transmission equipment. 7.1 Feature Description 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. 7.2 Basic Concept This topic describes the basic concepts that you need to be familiar with before you use the inband DCN solution. 7.3 Availability The inband DCN function requires the support of the applicable boards. 7.4 Relation with Other Features 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. 7.5 Realization Principle The inband DCN is realized by the packet switching unit and the system control unit. 7.6 Configuration Flow 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. 7.7 Configuration Example This topic uses an example to describe how to plan and configure the inband DCN transmission solution according to the conditions of the network. 7.8 Task Collection This topic provides the hyperlinks of the operation tasks regarding the relevant feature. 7.9 Relevant Alarms and Events
When the communication between the U2000 and an NE fails, the U2000 reports the corresponding alarm. 7.10 FAQs This topic provides the answers to the questions that are frequently raised when the inband DCN solution is used.
7-2
Issue 02 (2009-10-30)

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. A characteristic of the inband DCN mode is the convenient and flexible networking that does not require additional equipment. When the OptiX RTN 950 equipment is interconnected with the OptiX packet transmission equipment through the packet microwave or FE/GE interface, the inband DCN solution can be adopted, as shown in Figure 7-1. Figure 7-1 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
7.2 Basic Concept

This topic describes the basic concepts that you need to be familiar with before you use the inband DCN solution. 7.2.1 Inband DCN Protocol Stack The inband DCN protocol stack is optimized based on the TCP/IP protocol stack. 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.
7.2.1 Inband DCN Protocol Stack

The inband DCN protocol stack is optimized based on the TCP/IP protocol stack.
Issue 02 (2009-10-30)
7-3
Figure 7-2 Inband DCN protocol stack architecture

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

l
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.
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 inband DCN adopts the IP protocol to realize the network layer function.
Transport Layer
The main function of the transport layer is to provide the end-to-end communication service for the upper layer. The NE supports the connection-oriented TCP and the connectionless-oriented UDP.
Routing Protocols
Routing protocols belong to the content of the application layer. The inband DCN uses the open shortest path first (OSPF) protocol. The OSPF protocol is a dynamic routing protocol based on link status. The OSPF protocol divides an autonomous system into several areas. Route nodes exchange routing information in an area. The route nodes at the edge of an area make summary and exchange information with the routers in other areas. Areas are identified by area IDs. The area ID has the same format as the IP address. Currently, the OSPF protocol of the OptiX equipment supports only the routes within an area and does not support the routes between areas. Hence, the gateway NE and all its managed nongateway NEs must be in the same OSPF area. In addition to the dynamic routing protocol, the NE supports static routes. Static routes are manually configured routes. The priority of dynamic routes is higher than that of static routes. If there is a conflict, dynamic routes take priority.

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

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.
7.3 Availability
The inband DCN function requires the support of the applicable boards. Table 7-1 Availability of the IP over DCC solution Feature Inband DCN Solution Applicable Board IFU2 IFX2 EM6T EM6F Applicable Board Version All the functional versions All the functional versions All the functional versions All the functional versions

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

The inband DCN is realized by the packet switching unit and the system control unit.
Inband DCN Packet Forwarding Flow

Figure 7-3 shows how the inband DCN solution is used to transfer the messages from the NMS to the destination NE when the NMS manages the NEs.
Figure 7-3 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. The forwarding NE processes the packet according to the VLAN ID of the received Ethernet data packet. (1) The data packet with a management VLAN ID is considered as a DCN packet and is processed in compliance with the upper protocol. The data packet with a nonmanagement VLAN ID is considered as a service packet and thus is forwarded. (2) In the case of a DCN packet, the network layer of the forwarding NE parses the destination IP address of the data packet. If the destination IP address is not the IP address of the local NE, the forwarding NE obtains the corresponding route from the routing table generated by the OSPF protocol and then forwards the data packet to the corresponding port. 5. 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.
Inband DCN Packet Forwarding Flow

The inband DCN packet is transmitted and received by the packet switching unit and the system control unit.

l
Transmit Direction The system control unit encapsulates the inband DCN packet into the Ethernet data frame again, adds a management VLAN ID, and forward the DCN packet to the packet switching unit. The packet switching unit identifies the inband DCN packet according to the VLAN ID, adds the inband DCN packet to the DCN buffer queue, performs the traffic control according to the pre-set bandwidth, and transmits the DCN packet through the port.
Transmit Direction The packet switching unit receives the Ethernet data frame from the port, identifies the inband DCN packet according to the VLAN ID, and transmits the inband DCN packet to the system control unit.

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 7-2 Configuration flow of communications data at the near end Step 1 Operation A.1.4 Changing the NE ID Remarks Required. Set the parameters as follows:
l

l
For the GNE, set IP Address and Subnet Mask according to the planning of the external DCN. For the GNE, set Gateway IP Address if the external DCN requires that the gateway is configured for the NE. 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.
A.2.10 Setting the VLAN ID and Bandwidth Used by an Inband DCN A.2.11 Configuring the Enable Status of the Inband DCN Function on Ports
Required. Set the parameters as follows: Set the VLAN ID and bandwidth for the inband DCN according to the planning of the DCN. 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.
7-8
Issue 02 (2009-10-30)
Step 7
Operation Creating NEs on the centralize d NMS A.1.2 Creating NEs by Using the Manual Method A.1.1 Creating NEs by Using the Search Method
Remarks It is recommended that you create NEs on the centralized NMS by using this method when you need to add one or more NEs on a large-scale network.

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

This topic describes the networking information about the NEs. In the networking diagram shown in Figure 7-4, the OptiX RTN 950 and the OptiX PTN packet transmission equipment form a network. The OptiX RTN 950 is interconnected with the OptiX PTN equipment through the packet microwave link and the GE optical line. The NMS manages the OptiX RTN 950 and the OptiX PTN packet transmission equipment in a unified manner.
Issue 02 (2009-10-30)
7-9
Figure 7-4 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

l
The NMS manages the OptiX RTN 950 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.
l l
7-10
Issue 02 (2009-10-30)

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). The inband DCN function is enabled on all the service ports on the OptiX PTN packet transmission equipment. For the OptiX RTN 950 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 950 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 950s.
Plan the channel for the inband DCN.

Context
NOTE
In this configuration example, only the configuration information about NE5 and NE7 is provided.
Issue 02 (2009-10-30)
7-11
Procedure
Step 1 See A.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.2.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.2.11 Configuring the Enable Status of the Inband DCN Function on Ports and configure the Enable 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
Enable Status
Enabled
Disabled
Disabled
Step 4 See A.2.10 Setting 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.
7-12
Issue 02 (2009-10-30)
Parameter
Value Range NE5 NE7 4094 (default value) 512 (default value)
Ethernet Board VLAN ID Bandwidth(kbps)
4094 (default value) 512 (default value)
Step 5 See A.1.1 Creating NEs by Using the Search Method and create NEs in the search mode on the centralized NMS. The search domains include the following: The search 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
7.8 Task Collection

Related Concepts
A.1.1 Creating NEs by Using the Search Method A.1.2 Creating NEs by Using the Manual Method A.1.4 Changing the NE ID A.2.1 Setting NE Communication Parameters A.2.5 Creating Static IP Routes A.2.6 Setting Parameters of the OSPF Protocol A.2.13 Querying IP Routes A.2.3 Configuring the Extended ECC A.2.10 Setting the VLAN ID and Bandwidth Used by an Inband DCN A.2.11 Configuring the Enable Status of the Inband DCN Function on Ports

Relevant Alarms
l
NE_COMMU_BREAK
Issue 02 (2009-10-30)
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
Relevant Events
None.
7.10 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
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.
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.
7-14
Issue 02 (2009-10-30)
8 1+1 HSB
8
About This Chapter
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. 8.1 Feature Description In the case of the 1+1 HSB protection, the main channel of the transmit end transmits the RF signal to the opposite end and the standby channel is muted. The main channel and the standby channel of the receive end receive the same RF signal respectively. When the main channel of the receive end is faulty, the service unit of the receive end receives the signal from the standby channel. Hence, the protection switching is realized. 8.2 Basic Concepts This topic describes the basic concepts that you need to be familiar with before you use the 1+1 HSB feature. 8.3 Availability The 1+1 HSB feature requires the support of the applicable boards. 8.4 Relation with Other Features The 1+1 HSB protection is related to the 1+1 FD protection, 1+1 SD protection, N+1 protection, XPIC feature, AM feature, LAG feature, SNCP feature, and ERPS feature. 8.5 Realization Principle The realization principle of the 1+1 HSB for the SDH/PDH microwave is different from the realization principle of the 1+1 HSB for the Hybrid microwave. 8.6 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. 8.7 Configuration Example This topic 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. 8.8 Task Collection This topic provides the hyperlinks of the operation tasks regarding the 1+1 HSB feature.
8 1+1 HSB
8.9 Relevant Alarms and Events When a 1+1 HSB switching occurs on IF boards, the system reports corresponding alarms and abnormal events. 8.10 FAQs This topic provides the answers to the questions that are frequently raised when the 1+1 HSB is used.
8-2
Issue 02 (2009-10-30)
8 1+1 HSB

In the case of the 1+1 HSB protection, the main channel of the transmit end transmits the RF signal to the opposite end and the standby channel is muted. The main channel and the standby channel of the receive end receive the same RF signal respectively. When the main channel of the receive end is faulty, the service unit of the receive end receives the signal from the standby channel. Hence, the protection switching is realized. Figure 8-1 shows the application of the 1+1 HSB protection. Figure 8-1 1+1 HSB protection
Before the Switching Main channel Main channel Receiver MODEM Service MODEM Transmitter Receiver MODEM
MODEM Service
Transmitter
Standby channel After the Switching Main channel
Standby channel
Main channel Receiver MODEM Service
MODEM Service MODEM
Transmitter
Transmitter
Receiver
MODEM
Standby channel
Standby channel
8.2 Basic Concepts

This topic describes the basic concepts that you need to be familiar with before you use the 1+1 HSB feature. 8.2.1 System Configuration The OptiX RTN 950 supports one to three 1+1 HSB protection groups. 8.2.2 Protection Type The 1+1 HSB protection is classified into the revertive mode and the non-revertive mode. 8.2.3 Switching Conditions The switching priority varies according to the switching condition. 8.2.4 Switching Impact
8 1+1 HSB
Within the 1+1 HSB switching time (less than 200 ms), the service is interrupted.
8.2.1 System Configuration

The OptiX RTN 950 supports one to three 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 8-2 shows a typical configuration of one 1+1 HSB protection group on the OptiX RTN 950. Figure 8-2 Typical configuration of one 1+1 HSB protection group
ODU
Hybrid coupler
Antenna
ODU
System control, Switch & Clock board PIU FAN PIU IDU
System control, Switch & Clock board
IF board IF board
8.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.
Non-revertive mode
8-4
8 1+1 HSB
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.
8.2.3 Switching Conditions

The switching priority varies according to the switching condition. Table 8-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. 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 (2009-10-30)
8-5
8 1+1 HSB
Switching Condition Fault on the main equipment
Priority
Description If the switching is in the lockout or forced switching state, or if the current standby equipment is faulty, no HSB switching occurs. Otherwise, the system switches services from the current main board to the standby board. The switching then changes to the automatic switching state. For the trigger conditions of the automatic switching, refer to Table 8-2. 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)
8-6
Issue 02 (2009-10-30)
8 1+1 HSB
Switching Condition Manual switching (external switching)
Priority
Description If the switching is in the lockout, forced switching, or RDI state, or if the standby equipment is faulty, no switching occurs. Otherwise, the system switches services from the main board to the standby board or from the standby board to the main board according to the command. The switching then changes to the manual switching state. When the switching is in the automatic switching state and the main equipment is already restored to normal for the WTR time, the revertive switching occurs. From the time when the main equipment is restored to normal to the time when the revertive switching occurs, the switching is in the WTR state. After the revertive switching, the switching changes to the normal state.
Revertive switching (valid only in revertive mode)
Table 8-2 Trigger conditions of the automatic 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 Priority At the same priority
Issue 02 (2009-10-30)
8-7
8 1+1 HSB
Switching Condition MW_LOF MW_RDI Fault on the IF connection cable R_LOF R_LOS (IF1)
Priority
8.2.4 Switching Impact

Within the 1+1 HSB switching time (less than 200 ms), the service is interrupted.
8.3 Availability
The 1+1 HSB feature requires the support of the applicable boards. Table 8-3 Availability of the 1+1 HSB feature Feature 1+1 HSB Applicable Board IF1 IFU2 IFX2 Applicable Board Version All the functional versions All the functional versions All the functional versions

The 1+1 HSB protection is related to the 1+1 FD protection, 1+1 SD protection, N+1 protection, XPIC feature, AM feature, LAG feature, SNCP feature, and ERPS feature.
l
The configuration mode of 1+1 protection in one direction can only be 1+1 HSB, 1+1 FD, or 1+1 SD. The configuration mode in one direction can be different from that in another direction. The two 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. On the AM-enabled 1+1 HSB Hybrid radio link, after an HSB switching, the standby link works in the modulation mode of the original active link.
l l
8-8

l
8 1+1 HSB
When a Hybrid 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 IFUP port on the active IF board and the slave port is the IFUP port on the standby IF board. This LAG can neither be displayed on the NMS nor configured manually. The 1+1 HSB Hybrid radio link can function as the ring link or ring protection link in the ERPS protection.

The realization principle of the 1+1 HSB for the SDH/PDH microwave is different from the realization principle of the 1+1 HSB for the Hybrid microwave. 8.5.1 SDH/PDH Microwave The cross-connect unit realizes the HSB switching by dually transmitting and selectively receiving the TDM service. 8.5.2 Hybrid Microwave 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.
8.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 8-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. 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.
Issue 02 (2009-10-30)
8 1+1 HSB
4.
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 8-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. 2. 3. 4. 5. The hybrid coupler splits the RF signal received from the antenna into two signals and sends them to the main ODU and the standby ODU. The main ODU and the standby ODU send the processed IF analog signal to the main IF board and the standby IF board respectively. The main IF board and the standby IF board send the service signal to the cross-connect unit. The cross-connect unit selects the service signal from the main IF board and transmits the service signal to the service interface unit. The service interface unit sends the service signal to other equipment.
After the Switching

Figure 8-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
8-10
Issue 02 (2009-10-30)
8 1+1 HSB
Figure 8-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
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.
8.5.2 Hybrid Microwave

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.

Figure 8-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/STM-1
Ethernet
Standby ODU
Standby IF board
Packet switching Unit
Issue 02 (2009-10-30)
8-11
8 1+1 HSB
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 Hybrid microwave frame. The Hybrid microwave frame multiplexed by the MUX unit of the standby IF board does not contain the Ethernet service signal. The IF processing units of the main IF board and the standby IF board receive the Hybrid microwave frame that is multiplexed by their corresponding IF board and modulate the Hybrid microwave frame into the IF analog signal. Then, the IF processing units of the main IF board and the standby IF board send the IF analog signal to the main ODU and the standby ODU respectively. The main ODU transmits the RF signal to the hybrid coupler, which sends the RF signal to the antenna. The standby ODU is muted (that is, the standby ODU does not transmit the RF signal).
5.
6.
7.
Figure 8-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. The hybrid coupler splits the RF signal received from the antenna into two signals and sends them to the main ODU and the standby ODU. The main ODU and the standby ODU send the processed IF analog signal to the main IF board and the standby IF board respectively. The main IF board and the standby IF board demodulate the Hybrid frame from the IF signal.
8-12
Issue 02 (2009-10-30)
8 1+1 HSB
4.
The MUX units of the main IF board and the standby IF board receive the Hybrid microwave frame that is demodulated by their corresponding IF board and then separate the Hybrid microwave frame into the E1 service signal and Ethernet service signal. After being multiplexed into the VC-4, the E1 service signal is transmitted to the crossconnect unit. The Ethernet service signal is transmitted to the GE link on the IF board. The cross-connect unit selects the E1 service signal that is separated by the main IF board and then cross-connects the E1 service signal to the corresponding service interface unit. The 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.
After the Switching

Figure 8-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/STM-1
Ethernet
Standby ODU
Standby IF board
Figure 8-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
Issue 02 (2009-10-30)
8-13
8 1+1 HSB
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 board modulate the Hybrid microwave 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.

When configuring the 1+1 HSB radio link, configure the 1+1 IF protection group first, and then configure the IF/ODU information. Table 8-4 Process for configuring the 1+1 HSB protection mode Step 1 Operation A.3.1 Creating an IF 1+1 Protection Group A.3.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 IF and ODU information on the main radio link only. The parameters need to be set according to the network planning.

This topic 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
8 1+1 HSB
This topic considers the Hybrid radio link created by using the IFU2 board as an example. In the case of the IF1 or IFX2 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.
8.7.1 Networking Diagram The topic describes the networking information of the NEs. 8.7.2 Service Planning The service planning information contains all the parameter information required for configuring the NE data. 8.7.3 Configuration Process This topic describes the procedure for the data configuration.

The topic describes the networking information of the NEs. Figure 8-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 8-11 Networking diagram of 1+1 HSB protection
NE2
NE1

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.
Plan the protection group parameters. The 1+1 protection mode is HSB, providing the equipment protection function. Unless otherwise specified, all the parameters adopt the default values. Note that the reverse switching is enabled so that when both the active IF board and the standby IF board at the sink end report a service alarm, a reverse switching occurs at the source end.
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.
Issue 02 (2009-10-30)
8-15
8 1+1 HSB
Table 8-5 IF planning information Parameter NE1 3-IFU2 Link ID Channel spacing (MHz) AM enabling AM guaranteed capacity mode AM full capacity mode Specified E1 capacity ATPC status 101 28 Enabled QPSK 128QAM 16 Disabled NE2 3-IFU2 101 28 Enabled QPSK 128QAM 16 Disabled
Table 8-6 RF planning information Parameter NE1 23-ODU Transmit frequency (MHz) T/R spacing (MHz) Transmit power (dBm) Receive power (dBm) Transmission status 14930 420 10 -45 unmute NE2 23-ODU 14510 420 10 -45 unmute

Procedure
Step 1 See A.3.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
8-16
NE2 HSB Revertive (default value)

Issue 02 (2009-10-30)
HSB Revertive (default value)
8 1+1 HSB
Parameter
Value Range NE1 NE2 600 (default value) Enable (default value) 3-IFU2 5-IFU2
WTR Time(s) Enable Reverse Switching Working Board Protection Board
600 (default value) Enable (default value) 3-IFU2 5-IFU2
Step 2 See A.3.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-IFU2 Enable AM Channel Space Guaranteed Capacity Modulation Full Capacity Modulation Specified Max E1 Capacity Link ID ATPC Enable Status Enable 28M QPSK 128QAM 16 101 Disabled NE2 3-IFU2 Enable 28M QPSK 128QAM 16 101 Disabled
The values of the ODU parameters are provided as follows. Parameter Value Range NE1 23-ODU TX Frequency(MHz) T/R Spacing(MHz) TX Power(dBm) Power to Be Received (dBm) 14930 420 10 -45 NE2 23-ODU 14510 420 10 -45
Issue 02 (2009-10-30)
8-17
8 1+1 HSB
Parameter
Value Range NE1 23-ODU NE2 23-ODU unmute
TX Status
unmute
----End
8.8 Task Collection

This topic provides the hyperlinks of the operation tasks regarding the 1+1 HSB feature.
Related Concepts
A.3.14 Querying the IF 1+1 Protection Status A.3.16 IF 1+1 Protection Switching A.3.1 Creating an IF 1+1 Protection Group A.3.4 Configuring the IF/ODU Information of a Radio Link

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.
8.10 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?
8 1+1 HSB
A: Common causes are as follows:

l
The IF board and the corresponding ODU that form the 1+1 HSB protection are not included in the slot layout. The standby IF board is configured with services.
Q: In the revertive mode, why does the switching fail to restore after the switching enters the RDI state? A: The revertive mode is invalid for the reverse switching. That is, although both the active and standby equipment are normal, the system does not switch the new standby equipment to active after a reverse switching. Q: When radio links work as ECC links, why is the NMS unable to receive the abnormal HSB switching event of the non-gateway NE? A: When an HSB switching occurs, the ECC needs to reroute. As a result, the ECC between the gateway NE and the non-gateway NE is transiently interrupted and the switching event cannot be reported. Q: When the main ODU is configured with the 1+1 HSB protection, why is the equipment not switched when a switching event is reported after the main ODU reports a configuration alarm? A: In the case of the 1+1 HSB protection group, the system automatically copies the data of the main ODU to the standby ODU. Hence, when the main ODU reports a configuration alarm, the standby ODU also reports the same configuration alarm. As both the main and the standby ODUs report a configuration alarm, no switching occurs in the equipment. To notify the user that the ODU configuration is abnormal, however, the system reports a switching event. Q: What points should be noted before the deletion of a 1+1 HSB protection group? A: Before the deletion of a 1+1 HSB protection group, first ensure that the standby ODU is muted. Otherwise, the signal emitted by the standby ODU interferes with the signal of the main ODU. Q: What methods should be used to handle a 1+1 HSB protection switching failure? A: If the 1+1 HSB protection switching fails, check whether alarms indicating abnormalities are reported on the standby IF board. If yes, handle these alarms. Then, manually perform the 11 HSB protection switching again to check whether the 1+1 HSB protection switching is normal.
Issue 02 (2009-10-30)
8-19
9 1+1 FD
9
About This Chapter
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. 9.1 Feature Description 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. 9.2 Basic Concepts This topic describes the basic concepts that you need to be familiar with before you use the 1+1 FD feature. 9.3 Availability The 1+1 FD feature requires the support of the applicable boards. 9.4 Relation with Other Features The 1+1 FD protection is related to the 1+1 HSB protection, 1+1 SD protection, N+1 protection, XPIC feature, AM feature, LAG feature, SNCP feature, and ERPS feature. 9.5 Realization Principle The realization principle of the 1+1 FD for the SDH/PDH microwave is different from the realization principle of the 1+1 FD for the Hybrid microwave. 9.6 Configuration Process When configuring the 1+1 FD link, configure the 1+1 IF protection group first, and then configure the IF/ODU information. 9.7 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. 9.8 Task Collection
9 1+1 FD
This topic provides the hyperlinks of the operation tasks regarding the 1+1 FD feature. 9.9 Relevant Alarms and Events When a 1+1 FD switching occurs on IF boards, the system reports corresponding alarms and abnormal events. 9.10 FAQs This topic provides the answers to the questions that are frequently raised when the 1+1 FD is used.
9-2
Issue 02 (2009-10-30)
9 1+1 FD

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. Figure 9-1 shows the application of the 1+1 FD protection. Figure 9-1 1+1 FD protection
Before the swtiching Main channel Main channel Receiver F1 Service MODEM Transmitter F2 F1 F2 Receiver MODEM Service
MODEM
Transmitter
MODEM
Standby channel
Standby channel
After the swtiching Main channel Main channel
MODEM
Transmitter F1 F1 F2
Receiver
MODEM
Service MODEM Transmitter
F2
Service Receiver MODEM
Standby channel
Standby channel
9.2 Basic Concepts

This topic describes the basic concepts that you need to be familiar with before you use the 1+1 FD feature. 9.2.1 System Configuration The OptiX RTN 950 supports one to three 1+1 FD protection groups. 9.2.2 Protection Type The 1+1 FD protection is classified into the revertive mode and the non-revertive mode.
9 1+1 FD
9.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. 9.2.4 Switching Impact In the case of the HSB switching, the services are interrupted within the HSB switching time (less than 200 ms). In the case of the HSM switching, the service is not affected because the HSM switching is hitless. When the AM function is enabled, the standby channel works in modulation mode for ensuring capacity after the HSM switching occurs. Hence, services of a lower priority are damaged.

The OptiX RTN 950 supports one to three 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 9-2 and Figure 9-3 show two typical configurations of one 1+1 FD protection group on the OptiX RTN 950. Figure 9-2 Typical configuration 1 of one 1+1 FD protection group
ODU
Hybrid coupler
Antenna
ODU
System control, Switch & Clock board PIU FAN PIU IDU
IF board IF board
9-4
Issue 02 (2009-10-30)
9 1+1 FD
Figure 9-3 Typical configuration 2 of one 1+1 FD protection group
ODU
Antenna
ODU
Antenna
System control, Switch & Clock board PIU FAN
IF board IF board
PIU 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.
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 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 FD protection supports two types of switching, namely, HSB switching and HSM switching. The two types of switching are triggered by different conditions.
9 1+1 FD
Trigger Conditions of the HSB Switching

The HSB switching occurs on the equipment side. The equipment-side switching has the same switching action and switching impact as the 1+1 HSB switching but is triggered by different conditions. Table 9-1 Trigger conditions of the 1+1 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. If the switching is in the lockout or forced switching state, or if the current standby equipment is faulty, no HSB switching occurs. Otherwise, the system switches services from the current main board to the standby board. The switching then changes to the automatic switching state. For the trigger conditions of the automatic switching, refer to Table 9-2.
Fault on the main equipment
9-6
Issue 02 (2009-10-30)
9 1+1 FD
Switching Condition Manual switching (external switching)
Priority
Description 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.
Table 9-2 Trigger conditions of the automatic HSB switching Switching Condition Hardware fault on the IF board Hardware fault on the ODU POWER_ALM VOLT_LOS (IF board) RADIO_TSL_HIGH RADIO_TSL_LOW RADIO_RSL_HIGH IF_INPWR_ABN CONFIG_NOSUPPORT Fault on the IF connection cable At the same priority Description
Issue 02 (2009-10-30)
9-7
9 1+1 FD
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.
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 9-3. Table 9-3 Trigger conditions of the automatic HSM switching Switching Condition R_LOC MW_LOF R_LOS R_LOF MW_FECUNCOR MW_BER_SD Medium Low Priority High
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_FECUNCOR 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_FECUNCOR alarm is reported on both the main IF board and the standby IF board, no switching occurs.
l
Revertive switching After the automatic HSM switching occurs, the IF board attempts to perform a revertive switching action periodically. If no service alarm occurs on the main channel at this time, the IF board releases the switching.
NOTE
When the AM function is enabled, the standby channel works in modulation mode for ensuring capacity after the HSM switching occurs. Hence, services of a lower priority are damaged.
9-8
Issue 02 (2009-10-30)
9 1+1 FD

In the case of the HSB switching, the services are interrupted within the HSB switching time (less than 200 ms). In the case of the HSM switching, the service is not affected because the HSM switching is hitless. When the AM function is enabled, the standby channel works in modulation mode for ensuring capacity after the HSM switching occurs. Hence, services of a lower priority are damaged.
9.3 Availability
The 1+1 FD feature requires the support of the applicable boards. Table 9-4 Availability of the 1+1 FD feature Feature 1+1 FD Applicable Board IF1 IFU2 IFX2 Applicable Board Version All the functional versions All the functional versions All the functional versions

The 1+1 FD protection is related to the 1+1 HSB protection, 1+1 SD protection, N+1 protection, XPIC feature, AM feature, LAG feature, SNCP feature, and ERPS feature.
l
The configuration mode of 1+1 protection in one direction can only be 1+1 HSB, 1+1 FD, or 1+1 SD. The configuration mode in one direction can be different from that in another direction. The two IF boards in an XPIC working group cannot be configured into one 1+1 FD protection group, but the two IF boards in different XPIC working groups can be configured into one 1+1 FD protection group. The members of the 1+1 FD protection group cannot participate in the N+1 protection. The 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 Hybrid radio link, after an HSB switching, the standby link works in the modulation mode of the original active link; after an HSM switching, the standby link works in the guaranteed capacity modulation mode. When a Hybrid 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 IFUP port on the active IF board and the slave port is the IFUP port on the standby IF board. This LAG can neither be displayed on the NMS nor configured manually. The 1+1 FD Hybrid radio link can function as the ring link or ring protection link in the ERPS protection.
l l
Issue 02 (2009-10-30)
9-9
9 1+1 FD

The realization principle of the 1+1 FD for the SDH/PDH microwave is different from the realization principle of the 1+1 FD for the Hybrid microwave. 9.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. 9.5.2 Hybrid Microwave 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 9-4 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
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.
9-10
9 1+1 FD
Figure 9-5 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.
After the Switching

Figure 9-6 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
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.
Issue 02 (2009-10-30)
9 1+1 FD
Figure 9-7 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.

Figure 9-8 1+1 FD realization principle (before the switching, in the transmit direction)
Antenna f1 Service Interface Unit E1/STM-1 Main ODU Main IF board Cross-connect Unit
Ethernet
f2 Antenna Standby ODU Standby IF board Packet switching Unit
In the transmit direction:

9 1+1 FD
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 Hybrid microwave frame. The Hybrid microwave frame multiplexed by the MUX unit of the standby IF board does not contain the Ethernet service signal. The IF processing units of the main IF board and the standby IF board receive the Hybrid microwave frame that is multiplexed by the main IF board and modulate the Hybrid microwave frame into the IF analog signal. Then, the IF processing units of the main IF board and the standby IF board send the IF analog signal to the main ODU and the standby ODU respectively. The main ODU transmits the RF signal at frequency f1 to the main antenna. The standby ODU transmits the RF signal at frequency f2 to the standby antenna.
5.
6.
7.
Figure 9-9 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 Hybrid microwave frame from the IF analog signal. The Hybrid microwave frame of the standby IF board is transmitted to the main IF board through the protection bus.
Issue 02 (2009-10-30)
9 1+1 FD
4.
The MUX units of the main IF board and the standby IF board receive the Hybrid microwave frame that is demultiplexed by their corresponding IF board and then separate the Hybrid 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.
5. 6. 7.
8.
After the Switching

Figure 9-10 1+1 FD HSB realization principle (after the switching, in the transmit direction)
Antenna f1 Service Interface Unit E1/STM-1 Main ODU Main IF board Cross-connect Unit
Ethernet
f2 Antenna Standby ODU Standby IF board Packet switching Unit
Figure 9-11 1+1 FD HSB realization principle (after the switching, in the receive direction)
Ethernet
Antenna
f2
Standby ODU
Standby IF board
9-14
Issue 02 (2009-10-30)
9 1+1 FD
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 Hybrid microwave 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 Hybrid microwave 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 Hybrid microwave frames from their corresponding IF board. Then, these Hybrid microwave 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 9-12 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 Hybrid microwave frame modulated by the standby IF board through the protection bus. The MUX unit of the main IF board separates the Hybrid microwave 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.
Issue 02 (2009-10-30)
9-15
9 1+1 FD
9.6 Configuration Process

When configuring the 1+1 FD link, configure the 1+1 IF protection group first, and then configure the IF/ODU information. Table 9-5 Process for configuring the 1+1 FD protection mode Step 1 Operation A.3.1 Creating an IF 1+1 Protection Group A.3.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 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.

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
This topic considers the Hybrid radio link created by using the IFU2 board as an example. In the case of the IF1 or IFX2 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.
9.7.1 Networking Diagram The topic describes the networking information of the NEs. 9.7.2 Service Planning The service planning information contains all the parameter information required for configuring the NE data. 9.7.3 Configuration Process This topic describes the procedure for the data configuration.

The topic describes the networking information of the NEs. Figure 9-13 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.
9-16
Issue 02 (2009-10-30)
9 1+1 FD
Figure 9-13 Networking diagram of 1+1 FD protection
NE2
NE1

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.
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. Note that the reverse switching is not available in the 1+1 FD mode.
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.
Issue 02 (2009-10-30)
9-17
9 1+1 FD
Table 9-7 RF planning information Parameter NE1 23-ODU Transmit frequency (MHz) T/R spacing (MHz) Transmit power (dBm) Receive power (dBm) Transmission status 14930 25-ODU 15000 NE2 23-ODU 14510 25-ODU 14580
420 10 -45 unmute
420 10 -45 unmute
420 10 -45 unmute
420 10 -45 unmute

Procedure
Step 1 See A.3.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-IFU2 5-IFU2 NE2 FD Revertive (default value) 600 (default value) 3-IFU2 5-IFU2
Step 2 See A.3.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.
9-18
Issue 02 (2009-10-30)
9 1+1 FD
Parameter
Value Range NE1 3-IFU2 NE2 3-IFU2 Enable 28M QPSK 128QAM 16 101 Disabled
Enable AM Channel Space Guaranteed Capacity Modulation Full Capacity Modulation Specified Max E1 Capacity Link ID ATPC Enable Status
Enable 28M QPSK 128QAM 16 101 Disabled
The values of the ODU parameters are provided as follows. Parameter Value Range NE1 23-ODU TX Frequency (MHz) T/R Spacing (MHz) TX Power (dBm) Power to Be Received (dBm) TX Status 14930 420 10 -45 25-ODU 15000 420 10 -45 NE2 23-ODU 14510 420 10 -45 25-ODU 14580 420 10 -45
unmute
unmute
unmute
unmute
----End
9.8 Task Collection

This topic provides the hyperlinks of the operation tasks regarding the 1+1 FD feature.
Related Concepts
A.3.14 Querying the IF 1+1 Protection Status
9 1+1 FD
A.3.16 IF 1+1 Protection Switching A.3.1 Creating an IF 1+1 Protection Group A.3.4 Configuring the IF/ODU Information of a Radio Link

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.
9.10 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
The IF board and the corresponding ODU that form the 1+1 FD protection are not included in the slot layout. The main IF board and the standby IF board are not configured in paired slots. The standby IF board is configured with services.
l l
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.
9 1+1 FD
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.
Issue 02 (2009-10-30)
9-21
10 1+1 SD
10
About This Chapter
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. 10.1 Feature Description 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. 10.2 Basic Concepts This topic describes the basic concepts that you need to be familiar with before you use the 1+1 SD feature. 10.3 Availability The 1+1 SD feature requires the support of the applicable boards. 10.4 Relation with Other Features The 1+1 SD protection is related to the 1+1 HSB protection, 1+1 FD protection, N+1 protection, XPIC feature, AM function, LAG, SNCP, and ERPS feature. 10.5 Realization Principle The realization principle of the 1+1 SD for the SDH/PDH microwave is different from the realization principle of the 1+1 SD for the Hybrid microwave. 10.6 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. 10.7 Configuration Example This topic describes how to plan and configure the 1+1 SD radio links by using an example. 10.8 Task Collection This topic provides the hyperlinks of the operation tasks regarding the relevant feature.
10 1+1 SD
10.9 Relevant Alarms and Events When a 1+1 FD switching occurs on IF boards, the system reports the corresponding alarm and abnormal event. 10.10 FAQs This topic provides the answers to the questions that are frequently raised when the 1+1 SD protection is adopted.
10-2
Issue 02 (2009-10-30)
10 1+1 SD

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. Figure 10-1 shows the application of the 1+1 SD protection. Figure 10-1 1+1 SD protection
Before the Swtiching Main channel
T1 T2 T1
Main channel
T2
MODEM Service MODEM
Transmitter
Receiver
MODEM Service
Transmitter
T2 T1
Receiver
MODEM
Standby channel
Standby channel
After the Swtiching Main channel

T1 T2 T2 T1
Main channel
MODEM Service MODEM
Transmitter
Receiver
MODEM Service
Transmitter
T2 T1
Receiver
MODEM
Standby channel
Standby channel
10.2 Basic Concepts

This topic describes the basic concepts that you need to be familiar with before you use the 1+1 SD feature. 10.2.1 System Configuration The OptiX RTN 950 supports one to three 1+1 SD protection groups. 10.2.2 Protection Type The 1+1 SD protection is classified into the revertive mode and the non-revertive mode. 10.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.
10 1+1 SD
10.2.4 Switching Impact In the case of the HSB switching, the services are interrupted within the HSB switching time (less than 200 ms). In the case of the HSM switching, the service is not affected because it is the hitless switching. When the AM function is enabled, the standby channel works in modulation mode for ensuring capacity after the HSM switching occurs. Hence, services of a lower priority are damaged.

The OptiX RTN 950 supports one to three 1+1 SD 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 10-2 shows a typical configuration of one 1+1 SD protection group on the OptiX RTN 950. Figure 10-2 Typical configuration of one 1+1 SD protection group
ODU
Antenna
ODU
Antenna
System control, Switch & Clock board PIU FAN
IF board IF board
PIU 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
10-4
Issue 02 (2009-10-30)
10 1+1 SD
events because the former working channel is not stable, it is recommended that you set the WTR time to 5 to 12 minutes.
l
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 whether the revertive mode, the IF board attempts to perform a revertive switching action periodically after the HSM switching occurs. 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 10-1 Trigger conditions of the 1+1 SD HSB switching Switching Condition Clear switching (external switching) Priority From top downwards, the priority is from the highest to the lowest. Description All external switching states are cleared.
In any state, the switching changes to the lockout state. In the lockout state, no switching occurs until the lockout of protection is cleared.
Issue 02 (2009-10-30)
10-5
10 1+1 SD
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 10-2.
Fault on the main equipment
10-6
Issue 02 (2009-10-30)
10 1+1 SD
Switching Condition Reverse switching (valid only when the reverse switching is enabled)
Priority
Description When both the main IF board and the standby IF board at the sink end report service alarms, they send the alarms to the source end by using the MWRDI overhead in the microwave frame. If the source end is in the lockout or forced switching state, or if the current standby equipment is faulty, no reverse switching occurs. Otherwise, the HSB switching occurs at the source end after the reverse switching timer expires. The reverse switching timer restarts after you successfully add a protection group or if an HSB switching event occurs. The timer duration is the WTR time (in revertive mode) or 5 minutes (in nonrevertive mode). After the reverse switching, the switching changes to the RDI state. If the switching is in the lockout, forced switching, or RDI state, or if the 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.
Manual switching (external switching)
Issue 02 (2009-10-30)
10-7
10 1+1 SD
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 10-2 Trigger conditions of the automatic HSB switching Switching Condition Hardware fault on the IF board Hardware fault on the ODU POWER_ALM VOLT_LOS (IF board) RADIO_TSL_HIGH RADIO_TSL_LOW RADIO_RSL_HIGH IF_INPWR_ABN CONFIG_NOSUPPORT MW_RDI Fault on the IF connection cable R_LOC (IFU2 and IFX2) R_LOF (IFU2 and IFX2) Priority At the same 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
10-8
10 1+1 SD
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 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 10-3. Table 10-3 Trigger conditions of the automatic HSM switching Switching Condition R_LOC R_LOF R_LOS MW_LOF MW_FECUNCOR MW_BER_SD Medium Low Priority High
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_FECUNCOR 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_FECUNCOR alarm is reported on both the main IF board and the standby IF board, no switching occurs.
l
Revertive switching After the automatic HSM switching occurs, the IF board attempts to perform a revertive switching action periodically. If no service alarm occurs on the main channel at this time, the IF board releases the switching.
NOTE
When the AM function is enabled, the standby channel works in modulation mode for ensuring capacity after the HSM switching occurs. Hence, services of a lower priority are damaged.

In the case of the HSB switching, the services are interrupted within the HSB switching time (less than 200 ms). In the case of the HSM switching, the service is not affected because it is the hitless switching. When the AM function is enabled, the standby channel works in modulation mode for ensuring capacity after the HSM switching occurs. Hence, services of a lower priority are damaged.
Issue 02 (2009-10-30)
10-9
10 1+1 SD
10.3 Availability
The 1+1 SD feature requires the support of the applicable boards. Table 10-4 Availability of the 1+1 SD feature Feature 1+1 SD Applicable Board IF1 IFU2 IFX2 Applicable Board Version All the functional versions All the functional versions All the functional versions

The 1+1 SD protection is related to the 1+1 HSB protection, 1+1 FD protection, N+1 protection, XPIC feature, AM function, LAG, SNCP, and ERPS feature.
l
The configuration mode of 1+1 protection in one direction can be only 1+1 HSB, 1+1 FD, or 1+1 SD. The configuration mode 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. If the hybrid radio links are configured with the 1+1 SD protection and if the AM function is enabled, the standby link works in existing modulation mode of the main link after the HSB switching occurs, and works in modulation mode of the guaranteed capacity after the HSM switching occurs. When creating a 1+1 SD protection group of the hybrid radio, the NE automatically creates a load non-sharing LAG whose main port is the IFUP port on the main IF board and whose slave port is the IFUP port on the standby IF board. The LAG is not displayed on the NMS and cannot be configured manually. The hybrid 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.

The realization principle of the 1+1 SD for the SDH/PDH microwave is different from the realization principle of the 1+1 SD for the Hybrid microwave. 10.5.1 SDH/PDH Microwave
10 1+1 SD
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. 10.5.2 Hybrid Microwave 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 10-3 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
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).
Issue 02 (2009-10-30)
10-11
10 1+1 SD
Figure 10-4 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.
After the Switching

Figure 10-5 1+1 SD HSB realization principle (after the switching, in the receive direction)
Antenna
Standby ODU
Standby IF board
10-12
Issue 02 (2009-10-30)
10 1+1 SD
Figure 10-6 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
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 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 send the RF signal).
Figure 10-7 1+1 SD HSM realization principle (after the switching, in the receive direction)
Antenna
Standby ODU
Standby IF board
After the 1+1 SD HSM switching:

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.
10 1+1 SD

Figure 10-8 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. 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 Hybrid microwave frame. The Hybrid microwave frame multiplexed by the MUX unit of the standby IF board does not contain the Ethernet service signal. The IF processing units of the main IF board and the standby IF board receive the Hybrid microwave frame that is multiplexed by the main IF board and modulate the Hybrid microwave frame into the IF analog signal. Then, the IF processing units of the main IF board and the standby IF board send the IF analog signal to the main ODU and the standby ODU respectively. The main ODU transmits the RF signal to the antenna. The standby ODU is muted (that is, the standby ODU does not transmit the RF signal).
5.
6.
7.
10-14
Issue 02 (2009-10-30)
10 1+1 SD
Figure 10-9 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 Hybrid microwave frame. The Hybrid microwave frame of the standby IF board is transmitted to the main IF board through the protection bus. The MUX units of the main IF board and the standby IF board receive the Hybrid microwave frame that is demultiplexed by their corresponding IF board and then separate the Hybrid microwave 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. 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.
Issue 02 (2009-10-30)
10-15
10 1+1 SD
After the Switching

Figure 10-10 1+1 SD HSB realization principle (after the switching, in the receive direction)
Ethernet
Antenna
Standby ODU
Standby IF board
Figure 10-11 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 Hybrid microwave 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 Hybrid microwave frames from their corresponding IF board. Then, these Hybrid microwave 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.
10-16

l
10 1+1 SD
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 Hybrid microwave 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 10-12 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 Hybrid microwave frame modulated by the standby IF board through the protection bus. The MUX unit of the main IF board separates the Hybrid microwave 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.

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.
Issue 02 (2009-10-30)
10-17
10 1+1 SD
Table 10-5 Configuration procedure of 1+1 SD protection Step 1 Operation A.3.1 Creating an IF 1+1 Protection Group A.3.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.

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

The topic describes the networking information about the NEs. Figure 10-13 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 10-13 Networking diagram of the 1+1 SD protection group
NE2
NE1


l
10 1+1 SD
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.
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.
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 10-6 IF planning information Parameter NE1 3-IFU2 Radio Link ID Channel spacing (MHz) Enable AM Modulation Mode of the Guaranteed AM Capacity Modulation Mode of the Full AM Capacity Guaranteed E1 Capacity ATPC Enable Status 101 28 Enabled QPSK 128QAM 16 Disabled NE2 3-IFU2 101 28 Enabled QPSK 128QAM 16 Disabled
Table 10-7 RF planning information Parameter NE1 23-ODU TX Frequency(MHz) T/R Spacing(MHz) TX Power(dBm) RX Power
Issue 02 (2009-10-30)
NE2 23-ODU 14510 420 10 -45

10-19
14930 420 10 -45
10 1+1 SD
Parameter
NE1 23-ODU
NE2 23-ODU Unmute
TX Status
Unmute

This topic describes the process for the data configuration.
Procedure
Step 1 See A.3.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) 600s (default value) Enable (default value) 3-IFU2 5-IFU2 NE2 SD Revertive (default value) 600s (default value) Enable (default value) 3-IFU2 5-IFU2
Step 2 See A.3.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-IFU2 Enable AM Channel Space Guaranteed Capacity Modulation Full Capacity Modulation Specified Max E1 Capacity Link ID
10-20
NE2 3-IFU2 Enable 28M QPSK 128QAM 16 101

Issue 02 (2009-10-30)
Enable 28M QPSK 128QAM 16 101

10 1+1 SD
Parameter
Value Range NE1 3-IFU2 NE2 3-IFU2 Disabled
ATPC Enable Status
Disabled
The values for the related parameters of the ODU are provided as follows. Parameter Value Range NE1 23-ODU TX Frequency(MHz) T/R Spacing(MHz) TX Power(dBm) Power to Be Received (dBm) TX Status 14930 420 10 -45 unmute NE2 23-ODU 14510 420 10 -45 unmute
----End
10.8 Task Collection

Related Concepts
A.3.14 Querying the IF 1+1 Protection Status A.3.16 IF 1+1 Protection Switching A.3.1 Creating an IF 1+1 Protection Group A.3.4 Configuring the IF/ODU Information of a Radio Link

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

IF 1+1 protection switching: indicates that an IF 1+1 protection switching occurs.
10.10 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
The IF board and the corresponding ODU that form the 1+1 SD protection are not added in the slot layout. The main IF board and the standby IF board are not configured in paired slots. The standby IF board is configured with services.
l l
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?
10 1+1 SD
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.
Issue 02 (2009-10-30)
10-23
11
About This Chapter
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. 11.1 Feature Description When the XPIC and CCDP technologies are used, the transmitter transmits two signals over the electromagnetic waves whose polarization directions are orthogonal to each other to the receiver over the same channel. The receiver recovers the original two signals after canceling the interference between the two electromagnetic waves through the XPIC processing. In this manner, the transmission capacity is doubled. 11.2 Basic Concepts This topic describes the basic concepts that you need to be familiar with before you use the XPIC feature. 11.3 Availability The XPIC feature requires the support of the applicable boards. 11.4 Relation with Other Features The XPIC feature is related to the 1+1 protection configuration, ATPC, LAG, AM, and SNCP features. 11.5 Realization Principle 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. 11.6 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. 11.7 Configuration Example
Issue 02 (2009-10-30)
11-1
This topic uses an example to describe how to plan and configure the XPIC Hybrid radio links according to the conditions of the network. 11.8 Task Collection This topic provides the hyperlinks of the operation tasks regarding the XPIC feature. 11.9 Relevant Alarms and Events When the XPIC compensation signal is lost, the XPIC IF board reports the corresponding alarm. 11.10 FAQs This topic describes the answers to the questions that are frequently raised when the XPIC feature is used.
11-2
Issue 02 (2009-10-30)

When the XPIC and CCDP technologies are used, the transmitter transmits two signals over the electromagnetic waves whose polarization directions are orthogonal to each other to the receiver over the same channel. The receiver recovers the original two signals after canceling the interference between the two electromagnetic waves through the XPIC processing. In this manner, the transmission capacity is doubled. The XPIC technology can use the same channel to transmit the service signals whose capacity is two times the capacity of service signals without the application of the XPIC technology. The transmission of two service signals in one direction of the radio link is considered as an example. When the XPIC technology is not used, the bandwidth of two RF channels needs to be used to transmit the two service signals through the adjacent channel alternate polarization (ACAP) channel configuration, as shown in Figure 11-1. When the XPIC technology is used, the bandwidth of one RF channel can transmit the two service signals through the CCDP channel configuration, as shown in Figure 11-2. Figure 11-1 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
Figure 11-2 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
11.2 Basic Concepts

This topic describes the basic concepts that you need to be familiar with before you use the XPIC feature. 11.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. 11.2.2 System Configuration The OptiX RTN 950 supports one to three XPIC working groups.
11.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 11-3. 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 11-4.
Therefore, the capacity in CCDP transmission mode is double the capacity in single-polarized transmission mode. Figure 11-3 Single-polarized transmission
Figure 11-4 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 950 are as follows:
l l
The XPD tolerance is increased, and the notch performance is improved. The XPIC function is realized completely through hardware.

The OptiX RTN 950 supports one to three XPIC working groups.
NE Configuration
Each XPIC working group uses one frequency and consists of the following items:
l l l
Two IFX2 boards Two ODUs One dual-polarized antenna
Figure 11-5 shows the typical configuration of one XPIC working group that is configured on the OptiX RTN 950. The two IFX2 boards are connected through XPIC cables so that the XPIC cancellation signal can be mutually transmitted between the two IFX2 boards. Figure 11-5 Typical configuration of the XPIC
ODU
Dual-polarized antenna ODU System control, Switch & Clock board System control, Switch & Clock board FAN PIU IFX2 IFX2
PIU
IDU
Restrictions on the XPIC Configuration

The restrictions on the XPIC configuration are described as follows:
l
The Hybrid microwave supports the XPIC function whereas the SDH microwave and PDH microwave do not support the XPIC function. The ODU must adopt the separate mounting mode because the dual-polarized antenna is used.
Issue 02 (2009-10-30)

l
In the case of Hybrid microwave, the XPIC workgroup can be configured only at the channel spacing of 28 MHz or 56 MHz.
NOTE
If the XPIC function needs to be disabled, connect the IN and OUT interfaces of the same IF board that supports the XPIC function by using a shorter XPIC cable. Otherwise, the signal on the IF board is degraded.
11.3 Availability
The XPIC feature requires the support of the applicable boards. Table 11-1 Availability of the XPIC feature Feature XPIC Applicable Board IFX2 Applicable Board Version All the functional versions

The XPIC feature is related to the 1+1 protection configuration, ATPC, LAG, AM, and SNCP features.
Relation with the 1+1 Protection Configuration

One XPIC workgroup cannot form a 1+1 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 protection groups. Figure 11-6 shows an example in which radio links in the horizontal and vertical polarization directions of two XPIC workgroups form two 1+1 protection groups.
l
Service channels of the IFX2 boards in slots 3 and 4 form one XPIC workgroup, and service channels of the IFX2 boards in slots 5 and 6 form another XPIC workgroup. Service channels of the IFX2 boards in slots 3 and 5 form one 1+1 HSB protection group, and service channels of the IFX2 boards in slots 4 and 6 form another 1+1 HSB protection group. The service channels of the IFX2 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. The service channels of the IFX2 boards in slots 5 and 6 are the standby channels of the two 1+1 HSB protection groups, which protect main channels.
11-6
Issue 02 (2009-10-30)
Figure 11-6 Typical XPIC configuration (1+1 protection configuration)

V-polarization Dual-polarized antenna
H-polarization
ODU Working channel 1 Hybrid coupler ODU Protection channel 1 SLOT 10 (PIU) SLOT 11 SLOT (FAN) 9 (PIU) CSH IFX2 IFX2 EM6T SLOT 7 SLOT 5 SLOT 3 SLOT 1
ODU Working channel 2 Hybrid coupler ODU Protection channel 2 CSH IFX2 IFX2 SP3D SLOT 8 SLOT 6 SLOT 4 SLOT 2
In the receive direction, if the IFX2 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 IFX2 board in slot 5. The fault also causes loss of the XPIC cancellation signal sent from the IFX2 board in slot 3 to the IFX2 board in slot 4. As a result, HSB switching occurs on the IFX2 board in slot 4 and the services are switched to the channel of the IFX2 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 corresponding to the IFX2 board in slot 3 fails, reverse switching occurs at the local end because service alarms occur on the main and standby channels in the vertical polarization direction at the opposite end. Thus, the services are switched to the channel of the IFX2 board in slot 5. This fault also causes loss of the cancellation signals on the main and standby channels in the horizontal polarization direction at the opposite end, and therefore service alarms occur on the main and standby channels in the horizontal polarization direction at the opposite end. In this case, reverse switching occurs in the horizontal polarization direction at the local end. Thus, the services are switched to the channel of the IFX2 board in slot 6.
Relation with the ATPC Feature

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).
Relation with the AM Feature

l
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.
Issue 02 (2009-10-30)

l
If you enable the AM feature for the radio links in the horizontal and vertical polarization directions of one XPIC workgroup, Guaranteed Capacity Modulation and Full Capacity Modulation of the two radio links must be the same.
Relation with the SNCP Feature

A radio link that is configured with the XPIC feature can work as the working source, protection source, or service sink of the SNCP.
Relation with the LAG Feature

When you configure the XPIC workgroup of the Hybrid radio, 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 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. In actual transmission, the difference between the numbers of E1 services configured at the two IF ports must be less than 2. As shown in Figure 11-6, on the OptiX RTN 950, 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.

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. Figure 11-7 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
11-8
interference in the IF signals transmitted from the ODU to the IF board that supports the XPIC function. 3. 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.
4.

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. Table 11-2 Procedure for configuring the XPIC link Step 1 Operation Complete the physical connections by using the XPIC cables A.3.2 Creating an XPIC Protection Group A.3.3 Setting the Hybrid/AM Attributes of the XPIC Hybrid Radio Link A.3.1 Creating an IF 1+1 Protection Group Description Required. Use the XPIC Cable to connect the X-IN and X-OUT ports on the two IFX2 boards of the XPIC workgroup.
Required. The parameters need to be set according to the network planning information.
Required when the radio links are XPIC Hybrid links. 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.
Issue 02 (2009-10-30)
11-9
Step 5
Operation A.3.4 Configuring the IF/ODU Information of a Radio Link
Description Required. The parameters are set as follows:

l
When the Packet microwave equipment is interconnected with radio links, set Enable IEEE-1588 Timeslot to Enabled. Set Power to Be Received(dBm) to the receive level specified in the network planning. Only after this parameter is set, the antenna non-alignment indication function is enabled. When the antenna non-alignment indication function is enabled, if the actual receive power of the ODU is beyond the range of preset receive power (-3 dBm to +3 dBm), the ODU indicator on the IF board connected to the ODU blinks yellow (300 ms on, 300 ms off), indicating that the antennas are not aligned. After the antennas are aligned for consecutive 30 minutes, the NE automatically disables the antenna non-alignment indication function. TX High Threshold(dBm), TX Low Threshold(dBm), RX High Threshold(dBm), and RX Low Threshold(dBm) only affect the performance events related to the ATPC and can be set as required.
NOTE The preceding parameters need to set to the same values, separately for the radio links in the vertical and horizontal polarization directions. In the case of radio links configured with 1+1 HSB/SD, you need to configure the IF and ODU information on the main radio link only. In the case of radio links configured with 1+1 FD, you need to configure the IF and ODU information on the main radio link and the ODU information on the standby radio link.
NOTE
When you configure the XPIC workgroup of the Hybrid radio, 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 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. In actual transmission, the difference between the numbers of E1 services configured at the two IF ports must be less than 2. As shown in Figure 11-6, on the OptiX RTN 950, 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.

This topic uses an example to describe how to plan and configure the XPIC Hybrid radio links according to the conditions of the network. 11.7.1 Networking Diagram This topic describes the networking information about the NEs. 11.7.2 Service Planning The service planning information contains all the parameter information required for configuring the NE data.
11.7.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 950 are as follows:
l
The Hybrid radio link needs to transmit 32xE1 services and 400 Mbit/s Ethernet services at the same time. The AM function is enabled for each Hybrid radio link. According to the spectrum planning information, the XPIC function needs to be enabled. The protection for the Hybrid radio links must be provided.
l l l

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 Hybrid radio links that adopt the XPIC as shown in Figure 11-8 to meet the requirement for high-capacity transmission, according to the preceding service requirements and the available spectrum resources. As shown in Figure 11-9, NE1 and NE2 have the same board configurations. The EM6T board accesses 400 Mbit/s Ethernet services and the SP3D board accesses 32xE1 services.
Issue 02 (2009-10-30)
11-11
Figure 11-9 Board configuration

V-polarization Dual-polarized antenna
H-polarization
ODU Working channel 1 Hybrid coupler ODU Protection channel 1 SLOT 10 (PIU) SLOT 11 SLOT (FAN) 9 (PIU) CSH IFX2 IFX2 EM6T SLOT 7 SLOT 5 SLOT 3 SLOT 1
ODU Working channel 2 Hybrid coupler ODU Protection channel 2 CSH IFX2 IFX2 SP3D SLOT 8 SLOT 6 SLOT 4 SLOT 2
In this example, two XPIC workgroups form two 1+1 HSB protection groups.
l
The service channels on the IFX2 boards in slots 3 and 4 form one XPIC workgroup. The service channels on the IFX2 boards in slots 5 and 6 form the other XPIC workgroup. The service channels on the IFX2 boards in slots 3 and 5 form one 1+1 HSB protection group. The service channels on the IFX2 boards in slots 4 and 6 form the other 1+1 HSB protection group. The service channels on the IFX2 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 IFX2 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.

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 11-3. Table 11-3 Basic information about the radio links Parameter Link ID
11-12
Link 1 101
Link 2 102
Issue 02 (2009-10-30)
Parameter 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) Channel spacing (MHz) RF configuration mode Polarization direction
Link 1 NE1 NE2 32660 31848 812 56 1+1 HSB V (vertical polarization)
Link 2 NE1 NE2 32660 31848 812 56 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 Attribute

According to the capacity of E1 and Ethernet services and the availability requirement, you can calculate the information about the Hybrid/AM attribute, as provided in Table 11-4. Table 11-4 Information about the Hybrid/AM attribute Parameter Number of E1 services Capacity of Ethernet services (Mbit/ s) AM enabling AM guaranteed capacity mode AM full capacity mode Link 1 16 200 Enabled QPSK 64QAM Link 2 16 200 Enabled QPSK 64QAM
NOTE
The Hybrid radio capacity and the AM function require the proper license file.
Issue 02 (2009-10-30)
11-13
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 11-5. Table 11-5 Information about the Power and ATPC Parameter Transmit power (dBm) Link 1 6.0 (NE1) 6.0 (NE2) Receive power (dBm) -20.0 (NE1) -20.0 (NE2) ATPC enabling ATPC automatic threshold enabling Upper threshold of ATPC adjustment (dBm) Lower threshold of ATPC adjustment (dBm) Disabled Link 2 6.0 (NE1) 6.0 (NE2) -20.0 (NE1) -20.0 (NE2) Disabled -
NOTE
l l l
The transmit power is calculated in AM guaranteed capacity mode. The receive power is calculated in AM guaranteed capacity mode. In this example, the ATPC function is disabled.
Configuration Information About the XPIC Workgroup

Figure 11-9 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 11-6. Table 11-6 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-IFX2 4-IFX2 5-IFX2 6-IFX2 NE2 3-IFX2 4-IFX2 5-IFX2 6-IFX2
11-14
Issue 02 (2009-10-30)

NOTE
Use the XPIC cables with angle connectors to connect the X-IN and X-OUT ports between the two IFX2 boards in the horizontal polarization direction, namely, the IFX2 boards in slots 3 and 4. Use the XPIC cables with angle connectors to connect the X-IN and X-OUT ports between the two IFX2 boards in the horizontal polarization direction, namely, the IFX2 boards in slots 5 and 6.
Configuration Information About the 1+1 HSB Protection Group

Figure 11-9 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 11-7. Table 11-7 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-IFX2 5-IFH2 HSB Revertive Mode 600 Enabled 4-IFX2 6-IFX2 HSB Revertive Mode 600 Enabled NE2 3-IFX2 5-IFH2 HSB Revertive Mode 600 Enabled 4-IFX2 6-IFX2 HSB Revertive Mode 600 Enabled

Procedure
Step 1 Use the XPIC cables with angle connectors to connect the X-IN and X-OUT ports between the two IFX2 boards in the horizontal polarization direction, namely, the IFX2 boards in slots 3 and 4. Step 2 Use the XPIC cables with angle connectors to connect the X-IN and X-OUT ports between the two IFX2 boards in the horizontal polarization direction, namely, the IFX2 boards in slots 5 and 6.
Step 3 See A.3.2 Creating an XPIC Protection Group and create the XPIC workgroups. Parameter Value (NE1) XPIC Workgroup 1 Channel Space Polarization direction-V 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-IFX2-1 101 4-IFX2-1 102 6.0 32660 XPIC Workgroup 2 56M 5-IFX2-1 101 6-IFX2-1 102 6.0 32660 Value (NE2) XPIC Workgroup 1 56M 3-IFX2-1 101 4-IFX2-1 102 6.0 31848 XPIC Workgroup 2 56M 5-IFX2-1 101 6-IFX2-1 102 6.0 31848
812 unmute Disabled
812 unmute Disabled
812 unmute Disabled
812 unmute Disabled
Step 4 See A.3.3 Setting the Hybrid/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 attribute of NE1 and NE2 need to be set to the same values, as provided in the following table. Parameter Value Range 3-IFX2-1 Enable AM Guaranteed Capacity Modulation Full Capacity Modulation Specified Max E1 Capacity Enabled QPSK 4-IFX2-1 Enabled QPSK 5-IFX2-1 Enabled QPSK 6-IFX2-1 Enabled QPSK
64QAM 16
64QAM 16
64QAM 16
64QAM 16
11-16
Issue 02 (2009-10-30)
Step 5 See A.3.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 Enabled 3-IFX2-1(Port-1) 5-IFX2-1(Port-1) 1+1 HSB Protection Group 2 H (Horizontal Polarization) HSB Revertive Mode 600 Enabled 4-IFX2-1(Port-1) 6-IFX2-1(Port-1)
Step 6 A.3.4 Configuring the IF/ODU Information of a Radio Link. In this example, the power to be received is set to the same value for the links of NE1 and NE2. Parameter Value Range 3-IFU2 and 23-ODU Power to Be Received(dBm) -20.0 4-IFU2 and 24-ODU -20.0
----End

This topic provides the hyperlinks of the operation tasks regarding the XPIC feature.
Related Concepts
A.3.2 Creating an XPIC Protection Group A.3.3 Setting the Hybrid/AM Attributes of the XPIC Hybrid Radio Link A.3.1 Creating an IF 1+1 Protection Group

When the XPIC compensation signal is lost, the XPIC IF board reports the corresponding alarm.
Relevant Alarms
l
XPIC_LOS The XPIC_LOS alarm indicates that the XPIC compensation signal is lost.
Relevant Events
None.
11.10 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 IFX2 boards that form the XPIC workgroup must have the same transmit frequency and T/R spacing.
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.
Check whether the dual-polarized antenna is aligned in the correct polarized direction. The XPD can meet the specifications for the antenna only when the polarization direction of the dual-polarized antenna is aligned correctly.
11-18
Issue 02 (2009-10-30)
12 N+1 Protection
12
About This Chapter
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. 12.1 Feature Description The N+1 protection is applicable to the SDH microwave and Hybrid microwave. 12.2 Basic Concepts This topic describes the basic concepts with which you should be familiar before you use the N +1 protection. 12.3 Availability The N+1 protection feature requires the support of the applicable boards. 12.4 Relation with Other Features The N+1 protection is associated with the 1+1 protection, ATPC, LAG, and SNCP. 12.5 Realization Principle The realization principles for the N+1 protection are different in the case of the Hybrid microwave and SDH microwave. 12.6 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. 12.7 Configuration Example This topic uses an example to describe how to plan and configure the N+1 protection for the Hybrid microwave 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 Hybrid microwave and hence is not described in this topic. 12.8 Task Collection This topic provides the hyperlinks of the operation tasks regarding the N+1 protection feature. 12.9 Relevant Alarms and Performance Events When an N+1 protection switching occurs, the IF board reports corresponding alarms.
12 N+1 Protection
12.10 FAQs This topic describes the answers to the questions that are frequently raised when the N+1 protection feature is used.
12-2
Issue 02 (2009-10-30)
12 N+1 Protection

The N+1 protection is applicable to the SDH microwave and Hybrid microwave. As shown in Figure 12-1, N working channels and one protection channel are provided for the TDM services that are transmitted on the SDH microwave or Hybrid microwave and are configured with the N+1 protection. When a working channel is faulty, the normal services on this working channel are switched to the protection channel. When all the working channels are normal, the protection channel can be used to transmit extra services. Figure 12-1 N+1 protection
Site A Normal service 1 Working channel 1 Site B Normal service1
...
Normal service N Extra service
Working channel N Protection channel
...
Protection switching Site A Normal service 1 Working channel 1 Site B Normal service1
...
...
In the case of Ethernet services on the Hybrid microwave, the N+1 protection distributes the service traffic onto each link of a LAG according to the load sharing algorithm of the LAG. When a link fails, the packet switching unit distributes the services on the failed link to the other normal links.
12.2 Basic Concepts

This topic describes the basic concepts with which you should be familiar before you use the N +1 protection.
Issue 02 (2009-10-30)
12-3
12 N+1 Protection
12.2.1 System Configuration (SDH Microwave) If the OptiX RTN 950 on an SDH radio link uses the IF1 boards, the N+1 (N4) protection is supported. In this document, only the common configurations of the 1+1, 2+1, and 3+1 protection modes are described. 12.2.2 System Configuration (Hybrid Microwave) If the OptiX RTN 950 on an SDH radio link uses the IFU2 and IFX2 boards, the N+1 (N4) protection is supported. In this document, only the configurations of the 1+1, 2+1, and 3+1 protection modes are described. 12.2.3 Protection Mode In the case of TDM services over SDH microwave or Hybrid microwave, the N+1 protection is similar to the dual-ended revertive 1:N linear MSP. 12.2.4 Switching Condition In the case of TDM services over SDH microwave or Hybrid microwave, the N+1 protection switching can be triggered by local SF conditions, local SD conditions, local external switching requests, and byte K sent from the NE on the opposite side. This is similar to linear MSP. In the case of Ethernet services over Hybrid microwave, the LAG performs switchings according to the instructions provided by the IF unit. 12.2.5 Switching Impact The N+1 protection switching has different impacts on the services in the case of the Hybrid microwave and SDH microwave.
12.2.1 System Configuration (SDH Microwave)

If the OptiX RTN 950 on an SDH radio link uses the IF1 boards, the N+1 (N4) protection is supported. In this document, only the common configurations of the 1+1, 2+1, and 3+1 protection modes are described.
1+1 Protection Configuration

An IDU 950 supports a maximum of three 1+1 protection groups. 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 12-2 provides a typical configuration of one 1+1 protection group. The configuration is as follows:
l
The IF1 board in slot 3 provides one working channel. The IF1 board in slot 5 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 SL1D board transmit one working service and one extra service, respectively.
12-4
Issue 02 (2009-10-30)
12 N+1 Protection
Figure 12-2 Typical configuration of one 1+1 protection group
ODU Working channel Hybrid coupler
Singel-polarized antenna
ODU Protection channel SLOT 10 (PIU) SLOT 11 SLOT (FAN) 9 (PIU) CST IF1 IF1 SL1D SLOT 7 SLOT 5 SLOT 3 SLOT 1 CST SLOT 8 SLOT 6 SLOT 4 SLOT 2

An IDU 950 supports a maximum of two 2+1 protection groups. One 2+1 protection group occupies three channels and requires that the following items are configured:
l l l
Three IF1 boards Three ODUs One dual-polarized antenna (with one balanced hybrid coupler)
l
The IF1 boards in slots 3 and 5 provide two working channels. The IF1 board in slot 6 provides one protection channel. The three channels are configured in ACAP mode. See Figure 12-4. The transmit power of the three channels should be the same if possible to minimize the adjacent-channel interference. That is, the ODU transmit power that is set for the two working channels should be higher than the ODU transmit power that is set for the protection channel and the increment should exactly offset the extra loss caused by the hybrid coupler. One SL1D board accesses one working service and one extra service. One SL1D board accesses one working service.
l l
l l
Issue 02 (2009-10-30)
12-5
12 N+1 Protection
ODU Working channel 1 Hybrid coupler ODU Protection channel ODU Working channel 2 SLOT 10 (PIU) SLOT 11 SLOT (FAN) 9 (PIU) CST IF1 IF1 SL1D SLOT 7 SLOT 5 SLOT 3 SLOT 1 SL1D CST IF1
Dual-polarized antenna
SLOT 8 SLOT 6 SLOT 4 SLOT 2
Figure 12-4 Typical channel configuration of one 2+1 protection group

Working channel 1 V H Protection channel Working channel 2

An IDU 950 supports a maximum of one 3+1 protection group. One 3+1 protection group occupies four channels and requires that the following items are configured:
l l l
Four IF1 boards Four ODUs One dual-polarized antenna (with two balanced hybrid couplers)

l
12 N+1 Protection
The IF1 boards in slots 3, 4, and 5 provide three working channels. The IF1 board in slot 6 provides one protection channel. The four channels are configured in ACAP mode. See Figure 12-6. 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 for the four channels should be set to the same value. One SL1D board accesses two working services. One SL1D board accesses one working service and one extra service.
l l
l l
ODU Working channel 1 Hybrid coupler ODU Working channel 2 SLOT 10 (PIU) SLOT 11 SLOT (FAN) 9 (PIU) CST IF1 IF1 SL1D SLOT 7 SLOT 5 SLOT 3 SLOT 1
ODU Working channel 3
Hybrid coupler ODU Protection channel CST IF1 IF1 SL1D SLOT 8 SLOT 6 SLOT 4 SLOT 2

Working channel 1 V H Protection channel Working channel 3 Working channel 2
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.
Issue 02 (2009-10-30)
12 N+1 Protection
l
In the case of the N+1 (2N4) protection, the dual-polarized antenna is required. In this case, the ODU must be installed separately from the antenna.
12.2.2 System Configuration (Hybrid Microwave)

If the OptiX RTN 950 on an SDH radio link uses the IFU2 and IFX2 boards, the N+1 (N4) protection is supported. In this document, only the configurations of the 1+1, 2+1, and 3+1 protection modes are described.

An IDU 950 supports a maximum of three 1+1 protection groups. One 1+1 protection group occupies two channels and requires that the following items are configured:
l l l
Two Hybrid IF boards Two ODUs One single-polarized antenna (with one balanced hybrid coupler)
NOTE
Generally, it is recommended that you use the Hybrid IF boards of the same type to create an N+1 protection group. You can also use the combination of the IFX2 (in Hybrid mode) and IFU2 boards to create an N+1 protection group.
l
The IFU2 board in slot 3 provides one working channel. The IFU2 board in slot 5 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 SP3D and EM6T boards access the E1 services and Ethernet services, respectively.
12-8
Issue 02 (2009-10-30)
12 N+1 Protection
ODU Working channel Hybrid coupler
Singel-polarized antenna
ODU Protection channel SLOT 10 (PIU) SLOT 11 SLOT (FAN) 9 (PIU) CSH IFU2 IFU2 EM6T SLOT 7 SLOT 5 SLOT 3 SLOT 1 SP3D CSH SLOT 8 SLOT 6 SLOT 4 SLOT 2

An IDU 950 supports a maximum of two 2+1 protection groups. One 2+1 protection group occupies three channels and requires that the following items are configured:
l l l
Three Hybrid IF boards Three ODUs One dual-polarized antenna (with one balanced hybrid coupler)
NOTE
l
The IFU2 boards in slots 3 and 5 provide two working channels. The IFU2 board in slot 6 provides one protection channel. The three channels are configured in ACAP mode. See Figure 12-9. 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. The SP3D and EM6T boards access the E1 services and Ethernet services, respectively.
l l
Issue 02 (2009-10-30)
12 N+1 Protection
ODU Working channel 1 Hybrid coupler ODU Protection channel ODU Working channel 2 SLOT 10 (PIU) SLOT 11 SLOT (FAN) 9 (PIU) CSH IFU2 IFU2 EM6T SLOT 7 SLOT 5 SLOT 3 SLOT 1 SP3D CSH IFU2
SLOT 8 SLOT 6 SLOT 4 SLOT 2

Working channel 1 V H Protection channel Working channel 2

An IDU 950 supports a maximum of one 3+1 protection group. One 3+1 protection group occupies four channels and requires that the following items are configured:
l l l
Four Hybrid IF boards Four ODUs One dual-polarized antenna (with two balanced hybrid couplers)
NOTE
12-10
Issue 02 (2009-10-30)
12 N+1 Protection
l
The IFU2 boards in slots 3, 4, and 5 provide three working channels. The IFU2 board in slot 6 provides one protection channel. The four channels are configured in ACAP mode. See Figure 12-11. 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. The SP3D and EM6T boards access the E1 services and Ethernet services, respectively.
l l
Dual-polarized antenna ODU Working channel 1 Hybrid coupler ODU Working channel 2 SLOT 10 (PIU) SLOT 11 SLOT (FAN) 9 (PIU) CSH IFU2 IFU2 EM6T SLOT 7 SLOT 5 SLOT 3 SLOT 1 ODU Protection channel CSH IFU2 IFU2 SP3D SLOT 8 SLOT 6 SLOT 4 SLOT 2 ODU Working channel 3 Hybrid coupler

Working channel 1 V H Protection channel Working channel 3 Working channel 2
Limitations of the N+1 Protection for the Hybrid Microwave

The limitations of N+1 protection for the Hybrid microwave are as follows:
12 N+1 Protection
l
The IF channel bandwidth, modulation mode or AM attributes, and E1 capacity need to be set to the same values for the working and protection Hybrid IF boards. In the case of the N+1 (2N4) protection, the dual-polarized antenna is required. In this case, the ODU must be installed separately from the antenna.
12.2.3 Protection Mode

In the case of TDM services over SDH microwave or Hybrid microwave, the N+1 protection is similar to the dual-ended revertive 1:N linear MSP. The dual-ended revertive switching mode is described as follows:
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.
12.2.4 Switching Condition

In the case of TDM services over SDH microwave or Hybrid microwave, the N+1 protection switching can be triggered by local SF conditions, local SD conditions, local external switching requests, and byte K sent from the NE on the opposite side. This is similar to linear MSP. In the case of Ethernet services over Hybrid microwave, the LAG performs switchings according to the instructions provided by the IF unit. Table 12-1 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. Services on the working channel are forcibly switched to the protection channel.
12-12
Issue 02 (2009-10-30)
12 N+1 Protection
Switching Condition Signal failure (SF)
Priority
Description 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. In the case of N+1 protection for the Hybrid microwave, 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, BIP_EXC, or MW_FECUNCOR alarm on the working channel, or when the hardware of an ODU or IF board is faulty, the SF switching is triggered.
Issue 02 (2009-10-30)
12-13
12 N+1 Protection
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. In the case of N+1 protection for the Hybrid microwave, when there is the MW_BER_SD or BIP_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. 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.
12-14
Issue 02 (2009-10-30)
12 N+1 Protection
Switching Condition Exercise switching (external switching)
Priority
Description services are not actually switched. The exercise functionality is used only to check whether an NE can normally implement the N+1 protection protocol.
NOTE
l l 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. If two switching conditions exist on a channel at the same time, the switching of a higher priority preempts the channel. 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. 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 N+1 protection switching has different impacts on the services in the case of the Hybrid microwave and SDH microwave.
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.
Switching Impact of the N+1 Protection (Hybrid Microwave)

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, the Ethernet services are interrupted within the LAG protection switching time (shorter than 500 ms).
12.3 Availability
The N+1 protection feature requires the support of the applicable boards.
Issue 02 (2009-10-30)
12-15
12 N+1 Protection
Table 12-2 Availability of the N+1 protection feature Feature N+1 protection (SDH microwave) N+1 (Hybrid microwave) Applicable Board IF1 IFU2 IFX2 Applicable Board Version All the functional versions All the functional versions All the functional versions

The N+1 protection is associated with the 1+1 protection, ATPC, LAG, and SNCP.
l
The members of a 1+1 protection group cannot be configured as members of an N+1 protection group. The ATPC parameters, such as ATPC enable status and ATPC adjustment thresholds, need to be set to the same values for the members of an N+1 protection group. When creating an N+1 protection group of the Hybrid microwave, you need not create the LAG manually. The NE automatically creates the corresponding LAG. 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 Hybrid 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.

The realization principles for the N+1 protection are different in the case of the Hybrid microwave and SDH microwave. 12.5.1 SDH Microwave The N+1 protection switching for the SDH microwave is realized based on the automatic bridging of the cross-connect unit. 12.5.2 Hybrid Microwave In the case of N+1 protection for the Hybrid microwave, 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.
12.5.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 12.2.1 System Configuration (SDH Microwave) is provides as an example to describe the switching principles of the 2+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.
12 N+1 Protection
Figure 12-12 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 12-13 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)
Issue 02 (2009-10-30)
12-17
12 N+1 Protection
1. 2. 3.
As shown in Figure 12-12, before the switching, the NE sends and receives normal services on the working channels, and sends and receives extra services on the protection channel. After detecting that the signals on the working channels fail, the IF board notifies the system control and communication unit. As shown in Figure 12-13, 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 16.5.2 1:N Linear MSP.

In the case of N+1 protection for the Hybrid microwave, 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. The configuration of the 2+1 protection as described in 12.2.2 System Configuration (Hybrid Microwave) 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.
12-18
Issue 02 (2009-10-30)
12 N+1 Protection
Figure 12-14 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
Issue 02 (2009-10-30)
12-19
12 N+1 Protection
Figure 12-15 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 Hybrid microwave 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 12-14, before the switching, the NE sends and receives normal services on the working channels, 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 12-15, 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 Hybrid microwave realizes the switching on the packet plane by switching the LAG comprising the IF ports.
12-20
Issue 02 (2009-10-30)
12 N+1 Protection
1. 2. 3.
As shown in Figure 12-14, 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 12-15, 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 a Hybrid 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 12.2.2 System Configuration (Hybrid Microwave), the default main port of the LAG is the IF port on the IFU2 board in slot 3.

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.
Issue 02 (2009-10-30)
12-21
12 N+1 Protection
Table 12-3 Procedure for configuring an N+1 protection group (SDH microwave) Step 1 Operation A.3.4 Configuring the IF/ODU Information of a Radio Link Description Required. To configure SDH radio links with the N+1 protection, you need to configure the IF and ODU information for each working link and the protection link. Set the parameters as follows:
l
Set Work Mode, Link ID, and ATPC Enable Status according to the network planning information. During the site commissioning, ATPC Enable Status must be set to Disabled. It is recommended that you set ATPC Upper Threshold (dBm) to the central value plus 10 dB. It is recommended that you set ATPC Lower Threshold (dBm) to the central value minus 10 dB. It is recommended that you set ATPC Automatic Threshold Enable to Disabled. Set TX Frequency(MHz), T/R Spacing(MHz), and TX Power(dBm) according to the network planning information. Set TX Status to unmute. Set Power to Be Received(dBm) to the receive level specified in the network planning. Only after this parameter is set, the antenna non-alignment indication function is enabled. When the antenna non-alignment indication function is enabled, if the actual receive power of the ODU is beyond the range of preset receive power (-3 dBm to +3 dBm), the ODU indicator on the IF board connected to the ODU blinks yellow (300 ms on, 300 ms off), indicating that the antennas are not aligned. After the antennas are aligned for consecutive 30 minutes, the NE automatically disables the antenna non-alignment indication function. When the maximum transmit power allowed in the ATPC adjustment needs to be set, set Maximum Transmit Power (dBm) as required. TX High Threshold(dBm), TX Low Threshold(dBm), RX High Threshold(dBm), and RX Low Threshold(dBm) only affect the performance events related to the ATPC and can be set as required.
l l
NOTE To configure SDH radio links with the N+1 protection, you need to configure the IF and ODU information for each working link and the protection link. Work Mode must be set to 7,STM-1,28MHz, 128QAM for each link.
A.3.6 Creating an N+1 Protection Group
Required. The N+1 protection groups of the equipment at both ends must have the same attributes. The parameters need to be set according to the network planning information.
12-22
Issue 02 (2009-10-30)
12 N+1 Protection
Step 3
Operation Configuring TDM Services
Description Required. For the operations, see Configuration Procedure for Configuring TDM Services in the Configuration Guide.
Table 12-4 Procedure for configuring the N+1 protection (Hybrid microwave) Step 1 Operation A.3.7 Setting IF Attributes Description Required. When the IFX2 board is configured in an N+1 protection group, set XPIC Enabled to Disabled.
Issue 02 (2009-10-30)
12-23
12 N+1 Protection
Step 2
Operation A.3.4 Configuring the IF/ODU Information of a Radio Link
Description Required. To configure Hybrid radio links with N+1 protection, you need to configure the IF and ODU information for each working link and the protection link. Set the parameters as follows:
l
Set Enable AM and Channel Space according to the network planning information. Set Guaranteed Capacity Modulation and Full Capacity Modulation according to the network planning information when the radio links enable the AM function. Set Manually Specified Modulation according to the network planning information when the radio links disable the AM function. During the site commissioning, Enable AM must be set to Disabled, and Manually Specified Modulation is set to Guaranteed Capacity Modulation as planned. Set Specified Max E1 Capacity, Link ID, and ATPC Enable Status according to the network planning information. During the site commissioning, ATPC Enable Status must be set to Disabled. It is recommended that you set ATPC Upper Threshold (dBm) to the central value plus 10 dB. It is recommended that you set ATPC Lower Threshold (dBm) to the central value minus 10 dB. It is recommended that you set ATPC Automatic Threshold Enable to Disabled. When the Packet radio equipment is interconnected with radio links, set Enable IEEE-1588 Timeslot to Enabled. Set TX Frequency(MHz), T/R Spacing(MHz), and TX Power(dBm) according to the network planning information. Set TX Status to unmute. Set Power to Be Received(dBm) to the receive level specified in the network planning. Only after this parameter is set, the antenna non-alignment indication function is enabled. When the antenna non-alignment indication function is enabled, if the actual receive power of the ODU is beyond the range of preset receive power (-3 dBm to +3 dBm), the ODU indicator on the IF board connected to the ODU blinks yellow (300 ms on, 300 ms off), indicating that the antennas are not aligned. After the antennas are aligned for consecutive 30 minutes, the NE automatically disables the antenna non-alignment indication function. When the maximum transmit power allowed in the ATPC adjustment needs to be set, set Maximum Transmit Power (dBm) as required. TX High Threshold(dBm), TX Low Threshold(dBm), RX High Threshold(dBm), and RX Low Threshold(dBm) only
Issue 02 (2009-10-30)
l l
12-24
12 N+1 Protection
Step
Operation
Description affect the performance events related to the ATPC and can be set as required.
A.3.6 Creating an N+1 Protection Group Configuring TDM Services Configuring Ethernet Services
Required. The N+1 protection groups of the equipment at both ends must have the same attributes. The parameters need to be set according to the network planning information. Required. For the operations, see Configuration Procedure for Configuring TDM Services in the Configuration Guide. Required.
l
4 5
For the operations for configuring E-Line services, see Configuration Procedure (E-Line Services) for Configuring Ethernet Services in the Configuration Guide. For the operations for configuring E-LAN services, see Configuration Procedure (E-LAN Services) for Configuring Ethernet Services in the Configuration Guide.
NOTE After a Hybrid 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 12.2.2 System Configuration (Hybrid Microwave), the default main port of the LAG is the IF port on the IFU2 board in slot 3. Hence, you need to be familiar with the following information: 1. You need not create the LAG manually. 2. When creating an E-Line or E-LAN service, configure the Ethernet service to be transmitted from a radio link of the N+1 protection group to the main port of the LAG.

This topic uses an example to describe how to plan and configure the N+1 protection for the Hybrid microwave 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 Hybrid microwave and hence is not described in this topic. 12.7.1 Networking Diagram The topic describes the networking information about the NEs. 12.7.2 Service Planning The service planning information contains all the parameter information required for configuring the NE data. 12.7.3 Configuration Process This topic describes the procedure for the data configuration.
Issue 02 (2009-10-30)
12-25
12 N+1 Protection

The topic describes the networking information about the NEs. As shown in Figure 12-16, the service requirements between two sets of OptiX RTN 950 are as follows:
l
The Hybrid 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 Hybrid radio link. The protection for the Hybrid 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 Hybrid radio links that are configured with the N+1 (N=2) (as shown in Figure 12-16) 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 12.2.2 System Configuration (Hybrid Microwave).
l
The two working channels each transmit 16xE1 services whereas the protection channel does not transmit any E1 services. 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.

12-26
Issue 02 (2009-10-30)
12 N+1 Protection
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 12-5. Table 12-5 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) Channel spacing (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 Attributes

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 12-6. Table 12-6 Information about the Hybrid/AM attributes Parameter Number of E1 services Capacity of Ethernet services (Mbit/s) AM enabling Link 1 (Working Link 1) 16 100 Enabled Link 2 (Protection Link) 0 100 Enabled Link 3 (Working Link 2) 16 100 Enabled
Issue 02 (2009-10-30)
12-27
12 N+1 Protection
Parameter AM guaranteed capacity mode AM full capacity mode
Link 1 (Working Link 1) QPSK 256QAM
Link 2 (Protection Link) QPSK 256QAM
Link 3 (Working Link 2) QPSK 256QAM
NOTE
The Hybrid microwave capacity and the AM function require the proper license file.
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 12-7. Table 12-7 Information about the power and ATPC Parameter Transmit power (dBm) Link 1 (Working Link 1) 16.5 (NE1) 16.5 (NE2) Receive power (dBm) -46 (NE1) -46 (NE2) ATPC enabling ATPC automatic threshold enabling Upper threshold of ATPC adjustment (dBm) Lower threshold of ATPC adjustment (dBm) Disabled 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 -
NOTE
l l l
The transmit power is calculated in AM guaranteed capacity mode. The receive power is calculated in AM guaranteed capacity mode. 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 12.2.2 System Configuration (Hybrid Microwave). According to the microwave type, slot
12 N+1 Protection
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 12-8. Table 12-8 Information about the N+1 (N=2) protection Parameter Work Unit NE1 3-IFU2 5-IFU2 Protection Unit WTR time(s) 6-IFU2 600s (default value) NE2 3-IFU2 5-IFU2 6-IFU2 600s (default value)
Timeslot Allocation for TDM Services

Figure 12-17 shows the timeslots that are allocated for the TDM services according to the service planning information. Figure 12-17 Timeslot allocation diagram
Station Link Link 101 (Working Channel 1) Link 103 (Working Channel 2) User NE1 NE2 User
2-SP3D 3-IFU2 3-IFU2 2-SP3D 3-SP3D:1-16 3-SP3D:1-16 VC12: 1-16(VC4-1) (User A) (User A) 2-SP3D 5-IFU2 5-IFU2 2-SP3D 3-SP3D:17-32 3-SP3D:17-32 VC12: 1-16(VC4-1) (User B) (User B) Pass through Add/Drop
E1 services on NE1 and NE2:

l
User A uses ports 1-16 on the SP3D board in slot 2 to add and drop TDM services. User B uses ports 17-32 on the SP3D board in slot 2 to add and drop TDM services. The E1 services of User A that are accessed through ports 1-16 on the SP3D board occupy VC-12 timeslots 1-16 in the first VC-4 of the IF port on the IFU2 board in slot 3. The E1 services of User B that are accessed through ports 17-32 on the SP3D board occupy VC-12 timeslots 1-16 in the first VC-4 of the IF port on the IFU2 board in slot 5. That is, the two working channels each transmit 16xE1 services whereas the protection channel does not transmit any E1 services.
Planning Information About Ethernet Services (Port Attributes)

Table 12-9 and Table 12-10 provide the information about each port that transmits Ethernet services. The port configurations of NE1 are the same as NE2.
12 N+1 Protection
Table 12-9 Attributes of Ethernet ports Parameter 1-EM6T-3 Accessed Services of User A Encapsulation Type Working Mode Maximum Frame Length (byte) Flow Control TAG Default VLAN ID VLAN Priority 802.1Q Auto-Negotiation 1522 Disabled Access 100 0 (default value) 1-EM6T-4 Accessed Services of User B 802.1Q Auto-Negotiation 1522 Disabled Access 200 0 (default value) 1-EM6T-5 Accessed Services of User C 802.1Q Auto-Negotiation 1522 Disabled Access 300 0 (default value)
NOTE
In this example, all the Ethernet ports on the user side work in auto-negotiation mode. Hence, the Ethernet ports that access services on each NE also need to work in auto-negotiation mode. If the Ethernet port at the opposite end works in a mode other than auto-negotiation, you need to plan the working mode of the Ethernet port at the local end to be the same. Plan the Ethernet ports within a network to work in auto-negotiation mode. In this example, the Ethernet services of all the users do not carry VLAN tags. The corresponding VLAN tags are added to all the Ethernet services that enter the UNI ports. Hence, the tag attribute of all the UNI ports is access.
Table 12-10 Ethernet attributes of microwave ports Parameter Encapsulation Type Working Mode Maximum Frame Length (byte) Flow Control TAG Default VLAN ID VLAN Priority 3-IFU2-1 802.1Q Tag Aware 5-IFU2-1 802.1Q Tag Aware 6-IFU2-1 802.1Q Tag Aware -
Service Planning (Ethernet Services)

Table 12-11 provides the planning information about the E-Line services. The configurations of the E-Line services on NE1 are the same as the configurations of the E-Line services on NE2.
12 N+1 Protection
Table 12-11 Information about VLAN-based E-Line services Parameter NE1/NE2 From User A to NE1/NE2 Service ID Service Name Direction BPDU Source Port Source C-VLANs Sink Port Sink C-VLANs 1 UserAtoNE_Vline UNI-UNI Not Transparently Transmitted 1-EM6T-3 100 3-IFU2-1 100 From User B to NE1/NE2 2 UserBtoNE_Vline UNI-UNI Not Transparently Transmitted 1-EM6T-4 200 3-IFU2-1 200 From User C to NE1/NE2 3 UserCtoNE_Vline UNI-UNI Not Transparently Transmitted 1-EM6T-5 300 3-IFU2-1 300
NOTE
After a Hybrid 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 12.2.2 System Configuration (Hybrid Microwave), the default main port of the LAG is the IF port on the IFU2 board in slot 3. Hence, you need to be familiar with the following information: 1. You need not create the LAG manually. 2. When creating an E-Line or E-LAN service, configure the Ethernet service to be transmitted from a radio link of the N+1 protection group to the main port of the LAG.

Procedure
Step 1 See A.3.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-IFU2 and 23ODU Channel Space Enable AM 28M Enabled 5-IFU2 and 25ODU 28M Enabled 6-IFU2 and 26ODU 28M Enabled
12-31
Issue 02 (2009-10-30)
12 N+1 Protection
Parameter
Value Range 3-IFU2 and 23ODU 5-IFU2 and 25ODU QPSK 6-IFU2 and 26ODU QPSK
Guaranteed Capacity Modulation Full Capacity Modulation Specified Max E1 Capacity Link ID ATPC Enable Status Enable IEEE-1588 Timeslot TX Frequency (MHz) T/R Spacing(MHz) TX Power(dBm) TX Status Power to Be Received(dBm)
QPSK
256QAM 16 101 Disabled Disabled 14935 420 16.5 unmute -46
The values for the relevant parameters of NE2 are provided as follows. Parameter Value Range 3-IFU2 and 23ODU Channel Space Enable AM Guaranteed Capacity Modulation Full Capacity Modulation Specified Max E1 Capacity Link ID 28M Enabled QPSK 5-IFU2 and 25ODU 28M Enabled QPSK 6-IFU2 and 26ODU 28M Enabled QPSK
256QAM 16 101
256QAM 16 103
256QAM 0 102
12-32
Issue 02 (2009-10-30)
12 N+1 Protection
Parameter
Value Range 3-IFU2 and 23ODU 5-IFU2 and 25ODU Disabled Disabled 14571 420 16.5 unmute -46 6-IFU2 and 26ODU Disabled Disabled 14543 420 16.5 unmute -46
ATPC Enable Status Enable IEEE-1588 Timeslot TX Frequency (MHz) T/R Spacing(MHz) TX Power(dBm) TX Status Power to Be Received(dBm)
Disabled Disabled 14515 420 16.5 unmute -46
Step 2 See A.3.6 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-IFU2-1(Port1) 5-IFU2-1(Port1) Select Mapping Direction Select Mapping Way Protection Unit 6-IFU2-1(Port1)
Step 3 See A.5.1 Creating the Cross-Connections of Point-to-Point Services and create the crossconnections of the point-to-point services. The parameters for configuring the cross-connections of the E1 services are set to the same values for NE1 and NE2, as provided in the following table. Parameter Value Range Service of User A Level
Issue 02 (2009-10-30)
Service of user B VC-12

12-33
VC-12
12 N+1 Protection
Parameter
Value Range Service of User A Service of user B Bidirectional 2-SP3D 17-32 5-IFU2-1(Port-1) VC4-1 1-16
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 2-SP3D 1-16 3-IFU2-1(Port-1) VC4-1 1-16
Step 4 Set the parameters of Ethernet ports. 1. See Setting the General Attributes of Ethernet Interfaces and set the general attributes of the Ethernet ports. General Attributes of the Ethernet ports on NE1 and NE2 are set to the same values, as provided in the following table. Parameter Value Range 1-EM6T-3 Enable Port Encapsulation Type Working Mode Max Frame Length(byte) Enabled 802.1Q Auto-Negotiation 1522 1-EM6T-4 Enabled 802.1Q Auto-Negotiation 1522 1-EM6T-5 Enabled 802.1Q Auto-Negotiation 1522
2.
See Setting the Layer 2 Attributes of Ethernet Interfaces and set the Layer 2 attributes of the Ethernet ports. Layer 2 Attributes of the Ethernet ports on NE1 and NE2 are set to the same values, as provided in the following table. Parameter Value Range 1-EM6T-3 TAG Default VLAN ID Access 100 1-EM6T-4 Access 200 1-EM6T-5 Access 300
12-34
Issue 02 (2009-10-30)
12 N+1 Protection
Parameter
Value Range 1-EM6T-3 1-EM6T-4 0 (default value) 1-EM6T-5 0 (default value)
VLAN Priority
0 (default value)
Step 5 Set the Ethernet attributes of the microwave ports. 1. See Setting the General Attributes of the IFUP Port and set the general attributes of the IFUP port. General Attributes of the microwave ports on NE1 and NE2 are set to the same values, as provided in the following table. Parameter Value Range 3-IFU2-1 Encapsulation Type 802.1Q 5-IFU2-1 802.1Q 6-IFU2-1 802.1Q
2.
See Setting the Layer 2 Attributes of the IFUP Port and set the Layer 2 attributes. Layer 2 Attributes of the microwave ports on NE1 and NE2 are set to the same values, as provided in the following table. Parameter Value Range 3-IFU2-1 Tag Tag Aware 5-IFU2-1 Tag Aware 6-IFU2-1 Tag Aware
Step 6 See Configuring the E-Line Service and configure the E-Line services. The parameters for configuring the VLAN-based E-Line services on NE1 and NE2 are set to the same values, as provided in the following table. Parameter Value Range From User A to NE1/NE2 Service ID Service Name Direction BPDU Source Port Source VLANs
Issue 02 (2009-10-30)
From User B to NE1/NE2 2 UserBtoNE_Vline UNI-UNI Not Transparently Transmitted 1-EM6T-4 200
From User C to NE1/NE2 3 UserCtoNE_Vline UNI-UNI Not Transparently Transmitted 1-EM6T-5 300
12-35
1 UserAtoNE_Vline UNI-UNI Not Transparently Transmitted 1-EM6T-3 100
12 N+1 Protection
Parameter
Value Range From User A to NE1/NE2 From User B to NE1/NE2 3-IFU2-1 200 From User C to NE1/NE2 3-IFU2-1 300
Sink Port Sink VLANs
3-IFU2-1 100
----End

This topic provides the hyperlinks of the operation tasks regarding the N+1 protection feature.
Related Concepts
A.3.6 Creating an N+1 Protection Group A.3.15 Querying the IF N+1 Protection Status A.3.17 IF N+1 Protection Switching A.3.18 Starting/Stopping the N+1 Protection Protocol A.3.4 Configuring the IF/ODU Information of a Radio Link
12.9 Relevant Alarms and Performance Events

When an N+1 protection switching occurs, the IF board reports corresponding alarms.
Relevant Alarms
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.
LCS_MISMATCH The LCS_MISMATCH alarm indicates that the license capacities of the boards in the protection group are inconsistent.
Relevant Performance Events

N+1 protection switching This performance event indicates that the N+1 protection switching occurs.
12 N+1 Protection
12.10 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
Protocol not started The state when the N+1 protection protocol is not started Protocol starting The state when the N+1 protection protocol is being started Protocol normal The normal state after the N+1 protection protocol is started Lockout The state after the protection channel is locked out Forced The state after a forced switching Manual The state after a manual switching Exercise The state after an exercise switching Signal failure The state after an SF switching Signal degrade The state after an SD switching WTR The state that lasts from the time the working equipment is restored to normal after an automatic switching to the time the revertive switching occurs in the revertive mode
Q: Why cannot the forced switching be performed when the signal on the protection channel fails? A: After the signal on the protection channel fails, the protection channel is locked out. The lockout of the protection channel has a higher priority than the forced switching. Hence, the forced switching cannot be performed. Q: Why does the creation of an N+1 protection group fail? A: Common causes are as follows:
l l
The radio work mode of the IF board is not configured. In the case of the SDH microwave, the radio work mode of the IF board is not the STM-1 mode.
Issue 02 (2009-10-30)
12-37
12 N+1 Protection
Q: What is the method of handling an N+1 protection switching failure? A: Check whether the protection channel is normal or whether the protection channel is already used to protect other services.
l
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.
12-38
Issue 02 (2009-10-30)
13
Automatic Transmit Power Control
About This Chapter

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. 13.1 Feature Description The ATPC function enables the transmit power of a transmitter, within the ATPC control range, to automatically trace the change of the received signal level (RSL) at the receiver so that the RSL of the receiver remains in a fixed range. 13.2 Availability The ATPC feature requires the support of the applicable boards. 13.3 Relation with Other Features The ATPC feature is associated with the XPIC, N+1 protection, and AM features. 13.4 Realization Principle The ATPC function is implemented through the ATPC overhead in the microwave frame. 13.5 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. 13.6 Configuration Example This topic uses an example to describe how to plan and configure the ATPC according to the conditions of the network. 13.7 Task Collection This topic provides the hyperlinks of the operation tasks regarding the ATPC feature. 13.8 Relevant Alarms and Events When the ATPC adjustment occurs, the IF board reports the relevant performance events. 13.9 FAQs This topic describes the answers to the questions that are frequently raised when the LAG feature is used.
Issue 02 (2009-10-30)
13-1

The ATPC function enables the transmit power of a transmitter, within the ATPC control range, to automatically trace the change of the received signal level (RSL) at the receiver so that the RSL of the receiver remains in a fixed range.
ATPC Functions and Performance

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 13-1.
NOTE
l l
The preset maximum transmit power of the ODU should not be more than the rated maximum transmit power of the ODU. If the actual transmit power of the ODU reaches the preset maximum transmit power whereas the RSL at the receiver fails to be within the value range that has a bias of 2 dB from the central value of the ATPC upper threshold and the ATPC lower threshold, adjustments are no longer made.
If the RSL at the receiver is 2 dB higher than the central value of the ATPC upper threshold and the ATPC lower threshold, the receiver notifies the transmitter of a decrease in the transmit power. Therefore, the RSL can be within the value range that has a bias of 2 dB from the central value of the ATPC upper threshold and the ATPC lower threshold. See Figure 13-1.
Figure 13-1 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
Table 13-1 provides the ATPC performance of the OptiX RTN 950.
Table 13-1 ATPC performance ATPC Control Range Lower Threshold (dBm) Rated minimum transmit power Upper Threshold (dBm) Preset maximum transmit power of the ODU ATPC Adjustment Speed (dB/s) 30
Automatic ATPC Threshold Setting

The functions of the automatic ATPC threshold setting are described as follows:
l
When the automatic ATPC threshold setting is enabled, the ATPC lower threshold and the ATPC upper threshold that are manually set do not take effect. The equipment uses the preset ATPC lower threshold and ATPC upper threshold according to the IF work mode. When the automatic ATPC threshold setting is disabled, the ATPC lower threshold and the ATPC upper threshold that are manually set are used.
13.2 Availability
The ATPC feature requires the support of the applicable boards. Table 13-2 Availability of the ATPC feature Feature ATPC Applicable Board IF1 IFU2 IFX2 Applicable Board Version All the functional versions All the functional versions All the functional versions

The ATPC feature is associated with the XPIC, N+1 protection, and AM features.
l
The ATPC parameters, such as ATPC enable status and ATPC adjustment thresholds, need to be set to the same values for the members of an XPIC workgroups. The ATPC parameters, such as ATPC enable status and ATPC adjustment thresholds, need to be set to the same values for the members of an N+1 protection group. The ATPC function can work with the AM function. It is recommended that you disable the ATPC function if the AM function is enabled.

The ATPC function is implemented through the ATPC overhead in the microwave frame.
Figure 13-2 Realization principle of the ATPC

Transmitter Receiver RSL not within the value range that has a bias of 2 dB from the central valu e of the ATPC upper threshold and ATPC lower threshold RSL not within the value range that has a bias of 2 dB from the central valu e of the ATPC upper threshold and ATPC lower threshold
Microwave frame (ATPC overhead indicates power adjustment and adjustment step)
Adjust the ODU power once according to the ATPC adjustment step
...........
Microwave frame (ATPC overhead indicates power adjustment and adjustment step)
Adjust the ODU power once according to the ATPC adjustment step
...........
RSL within the value range that has a bias of 2 dB from the central valu e of the ATPC upper threshold and ATPC lower threshold
Microwave frame (ATPC overhead indicates no adjustments to the transmit power) ...........
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.
13-4
Issue 02 (2009-10-30)

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

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 13-3 Procedure for configuring the ATPC (TDM microwave) Step 1 Operation A.3.4 Configuring the IF/ODU Information of a Radio Link Description Optional when you need to configure the ATPC. Set the parameters as follows:
l
During the site commissioning, set ATPC Enable Status to Disabled. It is recommended that you set ATPC Upper Threshold (dBm) to the central value plus 10 dB. It is recommended that you set ATPC Lower Threshold (dBm) to the central value minus 10 dB. It is recommended that you set ATPC Automatic Threshold Enable Status to Disabled. To set the maximum transmit power that is supported by the ATPC adjustment, you need to set Maximum Transmit Power(dBm) according to the actual requirements. TX High Threshold(dBm), TX Low Threshold(dBm), RX High Threshold(dBm), and RX Low Threshold(dBm) affect only the ATPC-related performance events. Hence, you need to set these parameters only if required.
Issue 02 (2009-10-30)
13-5
Table 13-4 Procedure for configuring the ATPC (Hybrid microwave) Step 1 Operation A.3.4 Configuring the IF/ODU Information of a Radio Link Description Optional when you need to configure the ATPC. Set the parameters as follows:
l
During the site commissioning, set ATPC Enable Status to Disabled. It is recommended that you set ATPC Upper Threshold (dBm) to the central value plus 10 dB. It is recommended that you set ATPC Lower Threshold (dBm) to the central value minus 10 dB. It is recommended that you set ATPC Automatic Threshold Enable Status to Disabled. To set the maximum transmit power that is supported by the ATPC adjustment, you need to set Maximum Transmit Power(dBm) according to the actual requirements. TX High Threshold(dBm), TX Low Threshold(dBm), RX High Threshold(dBm), and RX Low Threshold(dBm) affect only the ATPC-related performance events. Hence, you need to set these parameters only if required.

This topic uses an example to describe how to plan and configure the ATPC according to the conditions of the network. 13.6.1 Networking Diagram This topic describes the networking information about the NEs. 13.6.2 Service Planning The service planning information contains all the parameter information required for configuring the NE data. 13.6.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 13-3, the ATPC function needs to be enabled for the radio link between the two sets of OptiX RTN 950.
13-6
Issue 02 (2009-10-30)

101 14935M 14515M 28M 1+0 V-polarization
NE1
Tx high Tx low Link ID Tx high station Tx Freq. Tx low station Tx Freq. Channel spacing Channel Type Polarization
NE2

Information About the ATPC

Table 13-5 provides the information about the ATPC. Table 13-5 Information about the ATPC Parameter ATPC Enable Status ATPC Automatic Threshold Enable ATPC Upper Threshold (dBm) ATPC Lower Threshold (dBm) Value Range Enabled Disabled -36.0 -56.0
Information About the IF boards

According to the microwave type and the priorities of IF boards, you can obtain the information about the IF boards, as provided in Table 13-6. Table 13-6 Information about IF boards Parameter IF board Value Range 3-IFU2 (NE1) 3-IFU2 (NE2) RF configuration mode
Issue 02 (2009-10-30)
1+0

Procedure
Step 1 See A.3.4 Configuring the IF/ODU Information of a Radio Link and set the IF/ODU information about the radio link.
l
The values for the relevant parameters of NE1 are provided as follows. Parameter Value Range 3-IFU2 and 23-ODU ATPC Enable Status ATPC Upper Threshold(dBm) ATPC Lower Threshold(dBm) ATPC Automatic Threshold Enable Enabled -36.0 -56.0 Disabled
The values for the relevant parameters of NE2 are provided as follows. Parameter Value Range 3-IFU2 and 23-ODU ATPC Enable Status ATPC Upper Threshold(dBm) ATPC Lower Threshold(dBm) ATPC Automatic Threshold Enable Enabled -36.0 -56.0 Disabled
----End

This topic provides the hyperlinks of the operation tasks regarding the ATPC feature.
Related Concepts
A.3.8 Configuring the ATPC Function A.3.9 Setting the Power Attributes of the ODU A.3.11 Querying the ATPC Adjustment Records
13-8
Issue 02 (2009-10-30)

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

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.
13.9 FAQs
This topic describes the answers to the questions that are frequently raised when the LAG 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:
l
The ATPC adjustment speed is lower than the instantaneous fading speed. This ATPC adjustment speed may be lower than the instantaneous speed of certain fadings. In this case, the transmit power adjusted by the ATPC function fails to offset the fading in a timely manner, and hence, the RSL is more than 2 dB higher or lower than the central value of the ATPC threshold range.
The transmit power reaches the threshold of the ATPC control range, and cannot be increased or decreased.
Issue 02 (2009-10-30)
13-9
14 Adaptive Modulation
14
About This Chapter
Adaptive Modulation
The main feature of the Hybrid microwave is the adaptive modulation (AM) function. 14.1 Feature Description The AM function adjusts the modulation scheme according to the quality of the channel. 14.2 Availability The AM features requires the support of the applicable boards. 14.3 Relation with Other Features The AM feature is associated with the 1+1 protection, N+1 protection, XPIC, and QoS features. 14.4 Realization Principle The AM function is implemented mainly through the AM engine in the Modem unit of the IF board. 14.5 Configuration Procedure To configure the AM, you need to set the AM full capacity mode and the AM guaranteed capacity mode. 14.6 Configuration Example This topic uses an example to describe how to plan and configure the AM according to the conditions of the network. 14.7 Task Collection This topic provides the hyperlinks of the operation tasks regarding the AM feature. 14.8 Relevant Alarms and Events When the AM shift occurs, the IF board reports the relevant alarms and performance events. 14.9 FAQs This topic describes the answers to the questions that are frequently raised when the AM feature is used.
Issue 02 (2009-10-30)
14-1

The AM function adjusts the modulation scheme according to the quality of the channel. In the case of the same channel spacing, the microwave service bandwidth varies with the modulation mode. The higher the modulation efficiency, the higher the bandwidth of the transmitted services is. When the channel quality is favorable (such as on days when the weather is favorable), the equipment adopts a higher 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 the weather is stormy and foggy), the equipment adopts a lower modulation mode to transmit only the services with a higher priority within the available bandwidth and to discard the services with a lower priority. In this manner, the anti-interference capability of the radio link is improved and the link availability of the services with a higher priority is ensured. When the Hybrid microwave equipment adopts the AM technology, it controls service transmission based on the service bandwidth and QoS policy corresponding to the current modulation mode. The E1 services have the highest priority. By adopting the CoS technology, the equipment schedules Ethernet services of different types to the queues with different priorities. The services in the queues with different priorities are transmitted to the microwave port through the SP or WRR algorithm. When the queues with certain priorities are congested due to insufficient microwave bandwidth, the queues with these priorities discard certain or all services. When the Hybrid microwave works in the lowest modulation mode, the equipment transmits only the E1 services and the Ethernet services with a high priority within the available bandwidth. When the Hybrid microwave works in any other modulation mode, all the additional bandwidth is used to transmit the Ethernet services. In this manner, the availability of the links that carry the E1 services and the Ethernet services with the high priority is ensured and the Ethernet service capacity is increased, thus providing the dynamic bandwidth. Figure 14-1 shows the service change caused by the AM. The orange part indicates the E1 services, and the blue part indicates the Ethernet services. The closer to the edge of the blue part, the lower the priority of the Ethernet service is. Under all channel conditions, the E1 services occupy the specific bandwidth that is permanently available. Thus, the availability of the E1 services is ensured. The bandwidth for the Ethernet services varies with the channel conditions. When the channel is in bad conditions, the Ethernet services with a low priority are discarded.
14-2
Issue 02 (2009-10-30)
Figure 14-1 AM
256QAM 128QAM 32QAM QPSK 256QAM Channel capability 64QAM E1 services Ethernet services 128QAM 32QAM 16QAM 16QAM 64QAM
The AM technology adopted by the OptiX RTN 950 has the following features:
l
The AM technology can use the QPSK, 16QAM, 32QAM, 64QAM, 128QAM, and 256QAM modulation mode. The lowest modulation mode (also called "reference mode") and the highest modulation mode (also called "nominal mode") actually used by the AM can be configured. When the modulation modes of AM are switched, the transmit frequency, receive frequency, and channel spacing do not change. When the modulation modes of AM are switched, the step-by-step switching mode must be adopted. When the AM switches the modulation modes to a lower one, the services with the low priority are discarded but no bit errors or slips occur in the services with the high priority. The speed of switching the modulation modes meets the requirement for no bit error in the case of 100 dB/s fast fading.
14.2 Availability
The AM features requires the support of the applicable boards. Table 14-1 Availability of the AM feature Feature AM Applicable Board IFU2 IFX2 Applicable Board Version All the functional versions All the functional versions
Issue 02 (2009-10-30)
14-3
NOTE
Air interfaces which support the AM function 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. In actual transmission, the difference between the numbers of E1 services configured at the two IF ports must be less than 2.

The AM feature is associated with the 1+1 protection, N+1 protection, XPIC, and QoS features.
l l l
When the AM function is enabled, the Hybrid microwave supports the 1+1 protection. When the AM function is enabled, the Hybrid microwave supports the N+1 protection. When the AM function is enabled, the Hybrid microwave supports the XPIC function. When the XPIC function is enabled, the XPIC workgroup can be configured only on the channel spacing of 28 MHz or 56 MHz. When the AM function is enabled, it is recommended that you configure the QoS for Ethernet services transmitted over the Hybrid microwave. After the QoS is configured, available bandwidths are first allocated to transmit Ethernet services of higher priorities when the radio link works in a low-efficiency modulation mode.

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

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

To configure the AM, you need to set the AM full capacity mode and the AM guaranteed capacity mode. Table 14-2 Procedure for configuring the 1+1 HSB protection Step 1 Operation A.3.4 Configuring the IF/ODU Information of a Radio Link Description Configure the AM function and the other IF/ODU information. The parameters need to be set according to the network planning information.

This topic uses an example to describe how to plan and configure the AM according to the conditions of the network.
14-6
Issue 02 (2009-10-30)
14.6.1 Networking Diagram This topic describes the networking information about the NEs. 14.6.2 Service Planning The service planning information contains all the parameter information required for configuring the NE data. 14.6.3 Configuration Process This topic describes the procedure for the data configuration.

This topic describes the networking information about the NEs. Figure 14-4 shows a hop of high-capacity radio link that transmits E1 services and Ethernet services at the same time. To achieve a balance between the link availability and the service bandwidth, the IFU2 boards are used to construct the Hybrid radio link and the AM function is enabled for the Hybrid radio link. Figure 14-4 Networking diagram of the AM
NE2
NE1

The service planning information contains all the parameter information required for configuring the NE data. The radio link has a channel capacity of 28 Mbit/s and transmits 10xE1 fixed TDM services, 20 Mbit/s VoIP voice services, and 100 Mbit/s Internet services. When the AM function is enabled, set the modulation mode as follows according to the service type and bandwidth requirement:
l
In the case of the 10xE1 TDM services and 20 Mbit/s VoIP voice services whose bandwidth needs to be guaranteed, set the AM guaranteed capacity mode to QPSK. Plan the relevant information, including the transmit power and antenna diameter to meet the requirements for the availability of the capacity-guaranteed link. The total service capacity is approximately 140 Mbit/s. Hence, set the AM full capacity mode to 128QAM to ensure the required service bandwidth and the availability of the lowpriority services when the channels are in good conditions. Disable the ATPC function.
Based on the preceding analysis, you can plan the IF and RF information about the radio links.
Issue 02 (2009-10-30)
14-7
Table 14-4 RF planning information Parameter NE1 23-ODU Transmit frequency (MHz) T/R spacing (MHz) Transmit power (dBm) Receive power (dBm) Transmission status 14930 420 10 -45 unmute NE2 23-ODU 14510 420 10 -45 unmute

Procedure
Step 1 See A.3.4 Configuring the IF/ODU Information of a Radio Link and configure the IF/ODU information about the radio link. The values for the related parameters of the IF boards are provided as follows.
14-8
Issue 02 (2009-10-30)
Parameter
Value Range NE1 3-IFU2 NE1 3-IFU2 Enable 28M QPSK 128QAM 10 101 Disabled
Enable AM Channel Space Guaranteed Capacity Modulation Full Capacity Modulation Specified Max E1 Capacity Link ID ATPC Enable Status
Enable 28M QPSK 128QAM 10 101 Disabled
The values for the related parameters of the ODU are provided as follows. Parameter Value Range NE1 23-ODU TX Frequency(MHz) T/R Spacing(MHz) TX Power(dBm) Power to Be Received (dBm) TX Status 14930 420 10 -45 unmute NE1 23-ODU 14510 420 10 -45 unmute
----End

This topic provides the hyperlinks of the operation tasks regarding the AM feature.
Related Concepts
A.3.5 Setting the Hybrid/AM Attribute A.3.13 Querying the AM Status
Issue 02 (2009-10-30)
14-9

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

l
ATPC_P_ADJUSTQPSKWS The ATPC_P_ADJUSTQPSKWS indicates the working second in the case of the QPSK modulation scheme.
QAMWS16 The QAMWS16 indicates the working second in the case of the QAMWS16 modulation scheme.
14.9 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.
14-10
Issue 02 (2009-10-30)

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.
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.
The ATPC function and the AM function cannot work properly together.
When the ATPC function is enabled, the transmit power cannot be the maximum transmit power if the upper ATPC adjustment threshold is set incorrectly. As a result, the improvement to the SNR of the radio link is affected and the AM upshift fails. An ATPC adjustment with a higher rate and a larger step results in less stability of the AM switching.
The ATPC function and the AM function may affect each other when working together. Hence, it is recommended that you disable the ATPC function when the AM function is enabled.
Issue 02 (2009-10-30)
14-11
15 Subnetwork Connection Protection
15
Subnetwork Connection Protection
About This Chapter

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. 15.1 Feature Description The SNCP, which requires one working subnetwork and one protection subnetwork, selects one service from the dually transmitted services. In this manner, the SNCP protects the services that are transmitted across subnetworks. The SNCP is applicable to the ring, tangent rings, intersecting rings, ring with a chain, or mesh network. 15.2 Basic Concepts This topic describes the basic concepts that you need to be familiar with before you use the SNCP feature. 15.3 Availability The SNCP feature requires the support of the applicable boards. 15.4 Relation with Other Features The SNCP service is related to the 1+1 protection scheme, N+1 protection scheme, XPIC, linear MSP, and ERPS. 15.5 Realization Principle The SNCP is realized based on the dual fed and selective receiving mechanism. 15.6 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. 15.7 Configuration Example By using an example, this topic describes how to plan and configure the AM according to the network conditions. 15.8 Task Collection This topic provides the hyperlinks of the operation tasks regarding the relevant feature. 15.9 Relevant Alarms and Events When the SNCP switching occurs, the system control board reports the relevant alarms and performance events.
15.10 FAQs This topic provides the answers to the questions that are frequently raised when the SNCP is adopted.
15-2
Issue 02 (2009-10-30)

The SNCP, which requires one working subnetwork and one protection subnetwork, selects one service from the dually transmitted services. In this manner, the SNCP protects the services that are transmitted across subnetworks. The SNCP is applicable to the ring, tangent rings, intersecting rings, ring with a chain, or mesh network. The OptiX RTN 950 supports the creation of the SNCP between optical transmission links, between radio transmission links, and between optical transmission links and radio transmission links. Figure 15-1 shows the application of the SNCP. Figure 15-1 SNCP
Working SNC Trail source Trail sink
NE A Protection SNC
NE B
Protection switching
NE A Protection SNC
NE B
NOTE
l l
The OptiX RTN 950 supports a maximum of 12 higher order SNCP groups and a maximum of 756 lower order SNCP groups. The SDH/PDH microwave, Hybrid microwave, and STM-1 optical transmission link all support the SNCP.
15.2 Basic Concepts

This topic describes the basic concepts that you need to be familiar with before you use the SNCP feature.
15.2.1 Protection Type The SNCP is classified into the revertive mode and the non-revertive mode. 15.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. 15.2.3 Hold-Off Time The SNCP protects services, whereas the 1+1 protection, N+1 protection and linear MSP protect links. Hence, when the SNCP is configured on a link that is already configured with the linklevel 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. 15.2.4 Switching Conditions The SNCP for different services is triggered by different conditions. 15.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.
15.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 15-2 SNCP service pair
Working source Protection source
Service sink
The working source and the protection source can be optical lines or radio links. The working source and the protection source can be of different types. The service sink can be any line, tributary, or IF.
15.2.3 Hold-Off Time

The SNCP protects services, whereas the 1+1 protection, N+1 protection and linear MSP protect links. Hence, when the SNCP is configured on a link that is already configured with the linklevel 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 1+1 SD and the SNCP work together to describe the functions of the hold-off time.
Coexisting 1+1 SD and SNCP

As shown in Figure 15-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 1+1 SD. In normal cases, the working SNC traverses NE B. Figure 15-3 Coexisting 1+1 SD 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
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 15-4 shows the traffic flow.
Figure 15-4 Traffic flow after the SNCP switching and 1+1 SD 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 15-5 shows the traffic flow after the switching. Figure 15-5 Traffic flow after the revertive SNCP switching
NE A Working SNC
NE B
NE D
NE C
15-6
Issue 02 (2009-10-30)
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 15-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. Figure 15-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 1+1 FD/SD protection, N+1 protection, and linear MSP. 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, it is recommended that you do not set the holdoff time. The reasons are that the 1+1 HSB switching time is far longer than the SNCP
Issue 02 (2009-10-30)
switching time and therefore setting the hold-off time increases the service interruption duration.
l
If the SNCP does not work with the link-level protection or the link-level protection fails, the service on the link is interrupted within the hold-off time. It is recommended that you set the hold-off time to 0 when only the SNCP is configured.

The SNCP for different services is triggered by different conditions. Table 15-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.
15-8
Issue 02 (2009-10-30)
Switching Condition Signal failure
Priority
Description 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 15-2, Table 15-3, and Table 15-4. 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.
Issue 02 (2009-10-30)
15-9
SNCP Switching Conditions (VC-4 Services)

NOTE
The VC-4 service in the following table refers to the VC-4 service that is transmitted over the optical line or SDH microwave.
Table 15-2 Trigger conditions of the automatic SNCP switching (VC-4 services) Switching Condition Hardware fault on the IF board and line board R_LOS 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 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
NOTE
The optional conditions in the preceding table can be the trigger condition of the automatic SNCP switching at the VC-4 level 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 Hybrid microwave.
15-10
Issue 02 (2009-10-30)

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 15-3 Trigger conditions of the automatic SNCP switching (VC-3/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 Optional condition
MW_LIM
TU_AIS TU_LOP LP_UNEQ LP_TIM BIP_SD BIP_EXC
NOTE
The optional conditions in the preceding table can be the trigger condition of the automatic SNCP switching at the VC-3/VC-12 level only after you set automatic switching conditions on the NMS. By default, the optical conditions do not trigger automatic SNCP switching.
Table 15-4 Trigger conditions of the automatic SNCP switching (E1 services transmitted over the Hybrid microwave) Switching Condition Hardware fault E1_AIS R_LOF R_LOC Description Default condition Default condition Default condition Default condition
Issue 02 (2009-10-30)
15-11
Switching Condition MW_LOF MW_LIM MW_BER_EXC
Description Default condition Default condition Default condition

The services are interrupted within the SNCP switching time (less than 50 ms).
15.3 Availability
The SNCP feature requires the support of the applicable boards. Table 15-5 Availability of the SNCP solution Feature SNCP Applicable Board SL1D IF1 IFU2 IFX2 Applicable Board Version All the functional versions All the functional versions All the functional versions All the functional versions

The SNCP service is related to the 1+1 protection scheme, N+1 protection scheme, XPIC, linear MSP, and ERPS.
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. The optical transmission line with the linear MSP can work as the working source, protection source, or service sink of the SNCP. The Hybrid radio ring can use the SNCP and ERPS simultaneously to separately protect the E1 services and Ethernet services on the ring.
15-12
Issue 02 (2009-10-30)

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 15-7 SNCP realization principle (before the switching)

NE A Protection SNC
NE B
Figure 15-8 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. 15-13
Issue 02 (2009-10-30)
connect unit to complete the cross-connection between the protection SNC and the service sink.

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 15-6 Procedure for configuring the SNCP service Step 1 Operation Configur ing the crossconnecti ons of TDM services A.5.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.5.3 Configuring the Automatic Switching of SNCP Services Optional when the TDM service is an SNCP service.
A.5.2 Creating CrossConnections of SNCP Services
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 AM according to the network conditions. 15.7.1 Networking Diagram The topic describes the networking information about the NEs. 15.7.2 Service Planning The service planning information contains the information about all the parameters required for configuring the NE data. 15.7.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 15-9, four sets of the OptiX RTN 950 compose a Hybrid radio ring with the SNCP. On the ring:

l l
The links between NE1 and NE2 and between NE1 and NE4 adopt the 1+1 HSB protection. The links between NE2 and NE3 and between NE3 and NE4 adopt the 1+0 non-protection.
Figure 15-9 Networking diagram of the SNCP ring

Tributary board: 2-SP3S East IF board: 4-IFU2 (M) and 6-IFU2 (S) West IF board: 3-IFU2 (M) and 5-IFU2 (S) E W 16E1 NE1 BSC 4xE1 BTS1 W SNCP W NE4 BTS4 E 4xE1
4xE1 NE2 E BTS2 Tributary board: 2-SP3S East IF board: 4-IFU2 (M) and 6-IFU2 (S) West IF board: 3-IFU2 (M) and 5-IFU2 (S)
Tributary board: 2-SP3S 4xE1 W NE3 E BTS3 Tributary board: 2-SP3S East IF board: 4-IFU2 (M) and 6-IFU2 (S) West IF board: 3-IFU2 (M) and 5-IFU2 (S) East IF board: 4-IFU2 (M) and 6-IFU2 (S) West IF board: 3-IFU2 (M) and 5-IFU2 (S)

Timeslot Allocation Diagram

Figure 15-10 shows the timeslots that are allocated for the TDM services according to the service planning information.
Issue 02 (2009-10-30)
15-15
Figure 15-10 Timeslot allocation diagram (TDM services on the Hybrid microwave ring network)
Station Timeslot NE1 4-IFU2 VC12: 1-8 2-SP3S:1-8 2-SP3S:1-8 2-SP3S:1-8 VC12: 9-12 VC4-1 2-SP3S:9-12 2-SP3S:13-16 Pass through (SNCP w orking path) Pass through (SNCP protection path) Add/Drop (SNCP w orking path) Add/Drop (SNCP protection path) NE2 3-IFU2 4-IFU2 NE3 3-IFU2 4-IFU2 VC12: 1-8 2-SP3S:1-8 VC12: 9-12 2-SP3S:9-12 VC12: 13-16 2-SP3S:1-4 2-SP3S:1-4 2-SP3S:13-16 NE4 3-IFU2 4-IFU2 NE1 3-IFU2
2-SP3S:1-4 2-SP3S:1-4 VC12: 13-16
As shown in Figure 15-10, the information about the timeslots that the TDM services occupy on each NE is as follows:
l
E1 services on NE2:
The E1 services are added to or dropped from the first to eighth ports on the SP3S board in slot 2 of NE2. The E1 services are added to or dropped from the first to eighth ports on the SP3S board in slot 2 of NE1. The E1 services occupy the first to eighth VC-12 timeslots on the ring. The E1 services are added to or dropped from the first to fourth ports on the SP3S board in slot 2 of NE3. The E1 services are added to or dropped from the ninth to twelfth ports on the SP3S board in slot 2 of NE1. The E1 services occupy the ninth to twelfth VC-12 timeslots on the ring. The E1 services are added to or dropped from the first to fourth ports on the SP3S board in slot 21 of NE4. The E1 services are added to or dropped from the thirteenth to sixteenth ports on the SP3S board in slot 2 of NE1. The E1 services occupy the thirteenth to sixteenth VC-12 timeslots on the ring.
E1 services on NE3:
E1 services on NE4:
TIP
On a backhaul network for a mobile base station, the services are accessed from different nodes and then aggregated to the same node for transmission. Hence, you can perform the following operations to allocate the timeslots on the SNCP microwave ring network: 1. Allocate the timeslots to add/drop services on the NEs in anti-clockwise order. Allocate the minimum VC-12 timeslot number to the service on the nearest NE. The number of the timeslot each service occupies does not change on the ring network. 2. Repeat the previous step to configure the timeslots for the services on all the sub-chains. This timeslot allocation method ensures that only the timeslots that the services on the nodes of the aggregation sub-chain occupy change.
15-16
Issue 02 (2009-10-30)

TIP
The principles for obtaining the timeslot cross-connection configurations from the SNCP service timeslot allocation diagram are as follows:
l
A straight line without any dot at either side represents a pass-through service. A straight line with one dot represents an add/drop service. A straight line with an arrow represents a transferred service. The vertical line under the NE name is considered as the reference. If a straight line representing a pass-through service crosses the vertical line, it indicates that crossconnections are configured between the boards on both sides of the vertical line. The corresponding cross-connected timeslots are marked over the straight line. If there is a straight line with one dot on one side of the vertical line, it indicates that SNCP crossconnections are configured between the board on this side of the vertical line and the board under the straight line with one dot. The corresponding cross-connected timeslots are marked over the straight line with one dot.
SNCP
Table 15-7 provides the information about SNCP. Table 15-7 SNCP Parameter Working Source Protection Source Revertive Mode WTR Time Hold-Off Time Switching Condition NE1 See the timeslot allocation diagram. See the timeslot allocation diagram. Revertive 600s (default value) 0 (default value) Necessary conditions for an SNCP switching (default values)
NOTE
Unless otherwise specified, WTR Time, Hold-Off Time, and Switching Condition take the default values.

Procedure
Step 1 See A.5.2 Creating Cross-Connections of SNCP Services and configure the SNCP service cross-connections.
l
The values for the related parameters of NE1 are provided as follows. Parameter Value NE1 Direction Bidirectional
Bidirectional
15-17
Issue 02 (2009-10-30)
Parameter
Value NE1
Level Hold-off Time(100ms) Revertive Mode WTR Time(s) Source Slot
VC-12 0 Revertive 600 3-IFU2-1 (working service) 4-IFU2-1 (protection service)
VC-12 0 Revertive 600 4-IFU2-1 (working service) 3-IFU2-1 (protection service) VC4-1 (working service) VC4-1 (protection service) 13-16 2-SP3S 13-16
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)
1-12 2-SP3S 1-12
The values for the related parameters of NE2 are provided as follows. Parameter Value NE2 Direction Level Hold-off Time(100ms) Revertive Mode WTR Time(s) Source Slot Bidirectional VC-12 0 Revertive 600 3-IFU2-1 (working service) 4-IFU2-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 1-8 2-SP3S -
15-18
Issue 02 (2009-10-30)
Parameter
Value NE2
Sink Timeslot Range(e.g.1,3-6)
1-8
The values for the related parameters of NE3 are provided as follows. Parameter Value NE3 Direction Level Hold-off Time(100ms) Revertive Mode WTR Time(s) Source Slot Bidirectional VC-12 0 Revertive 600 3-IFU2-1 (working service) 4-IFU2-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) 9-12 2-SP3S 1-4
The values for the related parameters of NE4 are provided as follows. Parameter Value NE4 Direction Level Hold-off Time(100ms) Revertive Mode WTR Time(s) Source Slot Bidirectional VC-12 0 Revertive 600 4-IFU2-1 (working service) 3-IFU2-1 (protection service)
Issue 02 (2009-10-30)
15-19
Parameter
Value NE4
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)
13-16 2-SP3S 1-4
Step 2 See A.5.1 Creating the Cross-Connections of Point-to-Point Services and configure the service cross-connections on NE2, NE3, and NE4.
l
The values for the related parameters of NE2 are provided as follows. Parameter Value NE2 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 3-IFU2-1 VC4-1 9-16 4-IFU2-1 VC4-1 9-16
The values for the related parameters of NE3 are provided as follows. Parameter Value NE3 Level Direction Source Slot Source VC4 Source Timeslot Range(e.g.1,3-6) Sink Slot VC-12 Bidirectional 3-IFU2-1 VC4-1 1-8,13-16 4-IFU2-1
15-20
Issue 02 (2009-10-30)
Parameter
Value NE3
Sink VC4 Sink Timeslot Range(e.g.1,3-6)
VC4-1 1-8,13-16
The values for the related parameters of NE4 are provided as follows. 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 3-IFU2-1 1 1-12 4-IFU2-1 VC4-1 1-12
Step 3 See Testing the E1 Service Through PRBS and test the E1 services. Test two E1 services on each base station. The test results should show that the E1 services contain no bit errors. ----End

Related Concepts
A.5.2 Creating Cross-Connections of SNCP Services A.5.3 Configuring the Automatic Switching of SNCP Services A.5.5 Converting a Normal Service into an SNCP Service A.5.6 Converting an SNCP Service to a Normal Service A.5.8 Switching SNCP Services A.5.9 Querying the Protection Status of SNCP Services
Issue 02 (2009-10-30)
15-21

When the SNCP switching occurs, the system control board reports the relevant alarms and performance events.
Relevant Alarms
None.
Relevant Events
l
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.
15.10 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
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
SD The state after the working SNC is automatically switched in the case of an optional trigger condition
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
15-22
Issue 02 (2009-10-30)
16
Linear Multiplex Section Protection
About This Chapter

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. 16.1 Feature Description The linear MSP is applicable to a point-to-point network. The linear MSP is classified into the 1+1 linear MSP and 1:N linear MSP. 16.2 Basic Concepts This topic describes the basic concepts that you need to be familiar with before you use the linear MSP feature. 16.3 Availability The linear MSP requires the support of the applicable boards. 16.4 Relation with Other Features The linear MSP is related to the SNCP. 16.5 Realization Principle The 1+1 linear MSP and the 1:N linear MSP have different switching principles. 16.6 Configuration Procedure To configure a linear MSP service, you need to create the linear MSP protection group and then create the service cross-connections. 16.7 Configuration Example This topic uses an example to describe how to plan and configure the AM. 16.8 Task Collection This topic provides the hyperlinks of the operation tasks regarding the linear MSP feature. 16.9 Relevant Alarms and Events When a linear MSP switching occurs, the system control and communication board reports the corresponding alarms and performance events. 16.10 FAQs
Issue 02 (2009-10-30)
16-1
This topic provides the answers to the questions that are frequently asked when the linear MSP is used.
16-2
Issue 02 (2009-10-30)

The linear MSP is applicable to a point-to-point network. The linear MSP is classified into the 1+1 linear MSP and 1:N linear MSP.
1+1 Linear MSP

The OptiX RTN 950 supports a maximum of six 1+1 linear MSP groups. The 1+1 linear MSP requires one working channel and one protection channel. When the working channel becomes unavailable, services are switched to the protection channel for transmission. Figure 16-1 shows the application of the 1+1 linear MSP. Figure 16-1 1+1 linear MSP
NE A Working channel NE B
Protection channel
Protection switching NE A Working channel NE B
Protection channel
1:N Linear MSP

The OptiX RTN 950 supports a maximum of six 1:N (N11) linear MSP groups. The 1:N linear MSP requires N working channel(s) 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, the extra services that are previously transmitted on the protection channel are interrupted. Figure 16-2 shows the application of the 1:N linear MSP.
Issue 02 (2009-10-30)
16-3
Figure 16-2 1:N linear MSP

NE A Normal service 1 Working channel 1 NE B Normal service1
...
...
Protection switching NE A Normal service 1 Working channel 1 NE B Normal service1
...
...
16.2 Basic Concepts

This topic describes the basic concepts that you need to be familiar with before you use the linear MSP feature. 16.2.1 Protection Type The linear MSP can be classified by protection mechanism, switching mode, and revertive mode. 16.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. 16.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. 16.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.
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.
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.
Hence, the linear MSP is classified into the following modes:

l l l l l l l l
1+1 dual-ended revertive mode 1+1 dual-ended non-revertive mode 1+1 single-ended revertive mode 1+1 single-ended non-revertive mode 1:N dual-ended revertive mode 1:N dual-ended non-revertive mode 1:N single-ended revertive mode 1:N single-ended non-revertive mode
The OptiX RTN 950 supports the following linear MSP modes:
l
1+1 single-ended revertive mode

Issue 02 (2009-10-30)

l l l l
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 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.
16.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 16-1 Meanings of K bytes (linear MSP) K Byte K1 (bit 1 to bit 4) Meaning The four bits carry the bridge request code. Table 16-2 provides the meanings of the four bits. The four bits indicate the number of the service signal to which the bridge request corresponds. 0 represents the null signal, 1-14 represent normal service signals, and 15 represents the extra service signal (applicable only to 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)
NOTE
l l
The OptiX RTN 950 supports six 1:N (N11) linear MSP groups. In the case of certain applications in some regions, when no MS_RDI or MS_AIS is generated, K2 (bit 6 to bit 8) is used to indicate the switching mode (100 indicating the single-ended mode and 101 indicating the dual-ended mode). ITU-T G.841 provides no explicit requirements for the usage. By default, the OptiX RTN 950 does not use the switching mode indication in the case of the 1+1 protection but supports the switching mode indication function in the case of the 1:N protection. You can set the switching mode indication function on the NMS.
16-6
Issue 02 (2009-10-30)
Table 16-2 Bridge request code Bit 1 1 Bit 2 1 Bit 3 1 Bit 4 1 Meaning Lockout of protection channel Forced switching Failure of highpriority 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 l
A reverse request assumes the priority of the bridge request to which it is responding. By default, the OptiX RTN 950 uses 1101 (failure of high-priority signal) and 1011 (degradation of highpriority signal) as the SF/SD switching request. When being interconnected with third-party equipment, the OptiX RTN 950 can use 1100 (failure of low-priority signal) and 1010 (degradation of low-priority signal) as the SF/SD switching request after you make settings on the NMS.
Issue 02 (2009-10-30)
16-7

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 16-3 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)
16-8
Issue 02 (2009-10-30)
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.
Exercise switching (external switching)
Issue 02 (2009-10-30)
16-9
NOTE
l l 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. If two switching conditions exist on a channel at the same time, the switching condition of a higher priority preempts the channel. 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. 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 16.2.2 Meanings of K Bytes. 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. 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.
l l

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.
16.3 Availability
The linear MSP requires the support of the applicable boards. Table 16-4 Availability of the linear MSP solution Feature LMSP Applicable Board SL1D Applicable Board Version All the functional versions

The linear MSP is related to the SNCP. The optical transmission line with the linear MSP can work as the working source, protection source, or service sink of the SNCP.

The 1+1 linear MSP and the 1:N linear MSP have different switching principles. 16.5.1 1+1 Linear MSP
The 1+1 linear MSP adopts the dual fed and selective receiving mechanism to realize the switching. 16.5.2 1:N Linear MSP The 1:N linear MSP adopts the automatic bridge mechanism to realize the switching.
16.5.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 16-3 Realization principle of the 1+1 linear MSP (before the switching)
NE B Working NE A
Protection Working
Protection Normal service
Figure 16-4 Realization principle of the 1+1 linear MSP (after the switching, in single-ended mode)
NE B Working NE A
Protection Working
When the signal on the working channel fails, the switching principle in single-ended mode is described as follows:
1. 2. 3.
Before 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 16-5 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.
16.5.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.
16-12
Issue 02 (2009-10-30)
Figure 16-6 Realization principle of the 1:1 linear MSP (before the switching)
NE B Working NE A
Protection Working
Protection Normal service Extra service
Figure 16-7 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.
NOTE
3. 4. 5.
Actually, to speed up the switching, NE B does not perform a service bridge in Step 3 but performs it in Step 5.
Issue 02 (2009-10-30)
16-13

To configure a linear MSP service, you need to create the linear MSP protection group and then create the service cross-connections. Table 16-5 Procedure for configuring a linear MSP service Step 1 Operation A.4.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 A.5.1 Creating the CrossConnections of Point-to-Point Services Required when the service is a pointto-point service. The parameters need to be set according to the service planning.

This topic uses an example to describe how to plan and configure the AM. 16.7.1 Networking Diagram This topic describes the networking information about the NEs. 16.7.2 Service Planning The service planning information contains all the parameter information required for configuring the NE data. 16.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 16-8, the relative networking information is as follows:
l
To ensure the reliable transmission of the services between NE1 and NE3, the linear MSP is configured for the optical transmission line between NE1 and NE3. NE1 transmits the services in the first 16 E1s of the STM-1 to NE2.
16-14
Issue 02 (2009-10-30)
Figure 16-8 Networking diagram of the linear MSP

16xE1 STM-1
NE2
NE1
NE3
Working port: 1-SL1D-1 Protection port: 1-SL1D-2 Sink board: 3-IFU2

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 NE1 to the IFU2 board in slot 3 of NE2.
NOTE
In this configuration example, only the configuration information about NE1 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 NE1 and BSC. Table 16-6 provides the related planning information. Table 16-6 Linear MSP Parameter Protection Type Switching Mode Revertive Mode SD Enable Protocol Type West Working Unit West Protection Unit NE1 1+1 Linear MSP Single-Ended Switching Non-Revertive Enabled (default value) New Protocol (default value) 1-SL1D-1 1-SL1D-2
NOTE
Unless otherwise specified, SD Enable and Switching Mode Indication take the default values.
Issue 02 (2009-10-30)
16-15

Procedure
Step 1 See A.4.1 Configuring Linear MSP and create the linear MSP. The values for the related parameters are provided as follows. Parameter Value Range NE1 Protection Type Switching Mode Revertive Mode WTR Time(s) SD Enable Mapped Board 1+1 Linear MSP Single-Ended Switching Non-Revertive 600 Enabled
l l
West Working Unit: 1-SL1D-1 West Protection Unit: 1-SL1D-2
Step 2 See A.5.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 NE1 are provided as follows. Parameter Value Range NE1 Level Direction Source Slot Source VC4 Source Timeslot Range(e.g.1,3-6) Sink Slot Sink VC4 Sink Timeslot Range(e.g.1,3-6) VC-12 Bidirectional 1-SL1D-1 VC4-1 1-16 3-IFU2-1 VC4-1 1-16
Step 3 See 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 Concepts
A.4.1 Configuring Linear MSP A.5.1 Creating the Cross-Connections of Point-to-Point Services A.4.2 Querying the Status of the Linear MSP A.4.3 Performing Linear MSP Switching A.4.4 Starting/Stopping the Linear MSP Protocol

When a linear MSP switching occurs, the system control and communication board reports the corresponding alarms and performance events.
Relevant Alarms
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.
16.10 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
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 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.
16-18

l
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.
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.
Issue 02 (2009-10-30)
16-19
17
Ethernet Ring Protection Switching
About This Chapter

The Ethernet ring protection switching (ERPS) is applicable to ring physical networks. The ERPS protects Ethernet services from an owner node to the other nodes on a ring. 17.1 Feature Description When a ring network is configured with the ERPS scheme, in normal cases, the RPL owner node blocks the RPL port on one side and all the services are transmitted through the ports on the other side. In this manner, services will not form loops. If a segment of links fails or an NE becomes faulty, the RPL owner node unblocks its RPL port and thus the services that cannot be transmitted over the faulty point can be transmitted through the RPL port. Therefore, the ring protection is provided. 17.2 Basic Concepts This topic describes the basic concepts that you need to be familiar with before you use the ERPS feature. 17.3 Availability The ERPS feature requires the support of the applicable boards. 17.4 Relation with Other Features The ERPS is associated with the 1+1 protection, LAG, and SNCP. 17.5 Realization Principle The ERPS uses the R-APS protocol to implement protection switching. 17.6 Configuration Procedure The key to configuring the ERPS is creating the ERPS protection instance. 17.7 Configuration Example This topic uses an example to describe how to plan and configure the ERPS according to the conditions of the network. 17.8 Task Collection This topic provides the hyperlinks of the operation tasks regarding the ERPS feature. 17.9 Relevant Alarms and Events When the ERPS is abnormal, the system control and communication board reports the relevant alarms and performance events.
17.10 FAQs This topic describes the answers to the questions that are frequently raised when the ERPS feature is used.
17-2
Issue 02 (2009-10-30)

When a ring network is configured with the ERPS scheme, in normal cases, the RPL owner node blocks the RPL port on one side and all the services are transmitted through the ports on the other side. In this manner, services will not form loops. If a segment of links fails or an NE becomes faulty, the RPL owner node unblocks its RPL port and thus the services that cannot be transmitted over the faulty point can be transmitted through the RPL port. Therefore, the ring protection is provided. The Ethernet ring network as shown in Figure 17-1 is configured with the ERPS scheme. Generally, the RPL owner node (NE D) blocks its RPL 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 blocked port so that the services can be transmitted over the link NE A <-> NE D <-> NE C <-> NE B.
Issue 02 (2009-10-30)
17-3
Figure 17-1 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
The OptiX RTN 950 supports the ERPS scheme that is based on an Ethernet ring consisting of FE or GE links or based on an Ethernet ring consisting of radio links.
17.2 Basic Concepts

This topic describes the basic concepts that you need to be familiar with before you use the ERPS feature. 17.2.1 Protection Instance
A protection instance is the basic unit of the ERPS. 17.2.2 Protection Type The ERPS is revertive. 17.2.3 R-APS Message When the ERPS scheme is used, a switching request is transmitted through the ring-APS (RAPS) message. 17.2.4 R-APS Timer In the ERPS process, three timers are used, including the guard timer, WTR timer, and holdoff timer. 17.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. 17.2.6 Switching Impact The services are interrupted within the ERPS time (less than 100 ms).
17.2.1 Protection Instance

A protection instance is the basic unit of the ERPS. Figure 17-2 shows a protection instance of the ERPS. The protection instance of the ERPS refers to an Ethernet ring that runs the ERPS protocol. On this Ethernet ring, the Ethernet ring node, ring link, ring protection link (RPL), RPL owner, and east (E) ports and west (W) ports at each Ethernet ring node are defined. Figure 17-2 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 RPL 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 950 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 17-2 as an example. Generally, the port on an Ethernet ring node for transmitting counter-clockwise services is an east ring port, and the port on the same Ethernet ring node for receiving 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.
17.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 17-3. 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.
17-6
Issue 02 (2009-10-30)
Figure 17-3 Frame format of an R-APS message

1 byte 1 byte 1 byte 1 byte
Mac Destination Address
Mac Source Address 802.1Q Header Type Flags TLV Offset MEL Version OpCode
R-APS Specific Information (32 bytes)
... Frame Check Sequence
Each R-APS message contains the R-APS specific information. Figure 17-4 shows the frame format of the R-APS specific information. Figure 17-4 Frame format of the R-APS specific information
1 byte 0 1 2 Request /State 3 4 5 6 7 0 1 2 1 byte 3 4 5 Status Reserved 1 D R N B F Status Reserved Node ID (6 bytes) 6 7 1 byte 1 byte
Reserved 2 (24 bytes)
Table 17-1 provides the details about each field in the R-APS specific information. Table 17-1 Description of each field in the R-APS specific information Field Request/State Value 1011 0000 Others Reserved 1
Issue 02 (2009-10-30)
Description Indicates signal fail (SF). Indicates no request (NR). Reserved. Reserved.
17-7
0000
Field Status RPL blocked (RB)
Value 1 0
Description Indicates that an RPL is blocked.

l l
Indicates that an RPL is not blocked. 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 17-1, the following R-APS messages are defined:
l
R-APS (SF) message: A node detecting an SF condition transmits the R-APS (SF) message. The other ring nodes that receive the R-APS (SF) message are 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.
17.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 2s, 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 (2009-10-30)
17-9
Table 17-2 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_FECUNCOR. 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 or ETH_LINK_DOWN alarm is reported.
In the case of a ring consisting of Ethernet links
Reception of the R-APS (SF) message at the local node
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. 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. 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. 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.
17-10
Issue 02 (2009-10-30)
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. 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. 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. 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. 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.
Reception of the R-APS (NR, RB) message at the local node

The services are interrupted within the ERPS time (less than 100 ms).
17.3 Availability
The ERPS feature requires the support of the applicable boards. Table 17-3 Availability of the ERPS Feature Feature ERPS Applicable Board EM6T EM6F IFU2 Applicable Board Version All the functional versions All the functional versions All the functional versions
Issue 02 (2009-10-30)
17-11
Feature
Applicable Board IFX2
Applicable Board Version All the functional versions

The ERPS is associated with the 1+1 protection, LAG, and SNCP.
l
The 1+1 Hybrid radio link can function as the ring link or ring protection link in the ERPS protection. The FE/GE link in the LAG or the 1+1 Hybrid radio link 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 ERPS uses the R-APS protocol to implement protection switching. Figure 17-5 shows the working principle of the ERPS for the OptiX RTN 950.
NOTE
The links on the Ethernet ring as shown in Figure 17-5 and Figure 17-6 can be Ethernet links or radio links. The realization principles of the ERPS in the two cases are the same.
17-12
Issue 02 (2009-10-30)
Figure 17-5 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 17-5, 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.
Issue 02 (2009-10-30)
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 17-6 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 17-6As shown in Figure 17-6, 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.
17-14
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.

The key to configuring the ERPS is creating the ERPS protection instance. Table 17-4 Procedure for configuring the ERPS Step 1 Operation A.7.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. When setting RPLOwner Ring Node Flag, note that only one RPL owner can exist on one Ethernet ring. When setting RPL Port, note that different ERPS protection instances cannot contain any same ports. 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.
A.7.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 (2009-10-30)
17-15

This topic uses an example to describe how to plan and configure the ERPS according to the conditions of the network. 17.7.1 Networking Diagram This topic describes the networking information about the NEs. 17.7.2 Service Planning The service planning information contains all the parameter information required for configuring the NE data. 17.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 17-7, 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.
17-16
Issue 02 (2009-10-30)

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

The service planning information contains all the parameter information required for configuring the NE data. Table 17-5 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 11 NE2 2 3-IFU2-1 4-IFU2-1 No 11 NE3 3 3-IFU2-1 4-IFU2-1 No 11 NE4 4 3-IFU2-1 4-IFU2-1 No 11
Issue 02 (2009-10-30)
17-17
Table 17-6 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.7.1 Creating Ethernet Ring Protection Instances and create the ERPS protection instance. The values for the related parameters are provided as follows. Parameter Value Range NE1 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 11 NE2 2 3-IFU2-1 4-IFU2-1 No 11 NE3 3 3-IFU2-1 4-IFU2-1 No 11 NE4 4 3-IFU2-1 4-IFU2-1 No 11
Step 2 See A.7.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)
17-18
NE2 0
NE3 0
NE4 0
Issue 02 (2009-10-30)
Parameter
Value Range NE1 NE2 500 5 5 NE3 500 5 5 NE4 500 5 5
Guard Time(ms) WTR Time(min) Packet Transmit Interval(s)
500 5 5
----End

This topic provides the hyperlinks of the operation tasks regarding the ERPS feature.
Related Concepts
A.7.1 Creating Ethernet Ring Protection Instances A.7.2 Setting the Parameters of Ethernet Ring Protocol A.7.3 Querying the Status of the Ethernet Ring Protocol

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.
17.10 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.
Issue 02 (2009-10-30)
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.
Control VLAN of the ERPS protection instance is the same as the VLAN ID carried by the Ethernet service packets or the VLAN ID carried by the in-band DCN packets. In this case, change Control VLAN to another value 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.
Different ERPS protection instances use one or more same ring ports. The OptiX RTN 950 does not support Ethernet tangent rings or Ethernet intersecting rings. That is, different ERPS protection instances cannot contain one or more same ports.
More than one RPL owner node is configured on the Ethernet ring network. An Ethernet ring network supports only one RPL owner node.
17-20
Issue 02 (2009-10-30)
18 MSTP
18
About This Chapter
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. 18.1 Feature Description With the defects in the STP and RSTP fixed, the MSTP maximizes the usage of link bandwidths by setting up several independent spanning trees. 18.2 Basic Concepts This topic describes the basic concepts that you need to be familiar with before you use the MSTP feature. 18.3 Availability The MSTP feature requires the support of the applicable boards. 18.4 Relation with Other Features The MSTP is associated with the LAG and ERPS. 18.5 Realization Principle The MSTP complies with IEEE 802.1s. The OptiX RTN 950 supports only the MSTP that generates the CIST. 18.6 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. 18.7 Configuration Example This topic uses an example to describe how to plan and configure the MSTP according to the conditions of the network. 18.8 Task Collection This topic provides the hyperlinks of the operation tasks regarding the MSTP feature. 18.9 Relevant Alarms and Events When the status of the MSTP port changes, the system control unit reports the relevant performance events. 18.10 FAQs
18 MSTP
This topic describes the answers to the questions that are frequently raised when the MSTP feature is adopted.
18-2
Issue 02 (2009-10-30)
18 MSTP

With the defects in the STP and RSTP fixed, the MSTP maximizes the usage of link bandwidths by setting up several independent spanning trees.
STP
The 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 18-1. Figure 18-1 Diagram of the STP
Switch A Switch A
Switch B
Switch C
Switch B Root: Switch A
Switch C
The STP 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.
RSTP
The RSTP is an optimized version of the STP. Compared with the STP, the RSTP can stabilize the network topology in a shorter time. The RSTP is compatible with the STP. They can be identified by the bridge that uses the RSTP for computing the spanning tree.
18 MSTP
Improvement in the MSTP

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. 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 18-2 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 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. Figure 18-2 Limitation 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 18-3 shows the finally generated network topology.

l l
18 MSTP
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 realized. Figure 18-3 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 950 supports only the MSTP that generates the Common and Internal Spanning Tree (CIST). Hence, the OptiX RTN 950 does not support the load sharing function that is implemented through forwarding of packets of different VLANs over different trails.
Typical Application of the MSTP on the OptiX RTN 950

As shown in Figure 18-4, when user equipment accesses the OptiX RTN 950 through two different trails, you can configure the ports on the OptiX RTN 950 that are connected to the user
18 MSTP
network into a port group. This port group, together with the switch on the user network, can run the MSTP. Hence, if a 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. Figure 18-4 Prevention of access network loops
Root Root
Port group CIST Blocked Port
Standards and Protocols Compliance

The MSTP complies with IEEE 802.1s.
NOTE
The OptiX RTN 950 supports only the MSTP that generates the CIST.
18.2 Basic Concepts

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

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.
18-6
Issue 02 (2009-10-30)

l
18 MSTP
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.
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.
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.
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.
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.
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.
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.
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
Issue 02 (2009-10-30)
18 MSTP
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.
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 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.
18-8
Issue 02 (2009-10-30)

NOTE
18 MSTP
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 950 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.
18.3 Availability
The MSTP feature requires the support of the applicable boards. Table 18-1 Availability of the MSTP Feature MSTP Applicable Board EM6T EM6F IFU2 IFX2 Applicable Board Version All the functional versions All the functional versions All the functional versions All the functional versions

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.

The MSTP complies with IEEE 802.1s. The OptiX RTN 950 supports only the MSTP that generates the CIST.
18 MSTP
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 quality is better. (2) If the root bridge IDs are the same, the bridge compares the root path cost values. When the root path cost value is smaller, the quality is better. (3) If the root path cost values are the same, the bridge compares the designated bridge IDs. When the designated bridge ID is smaller, the quality is better. (4) If the designated bridge IDs are the same, the bridge compares the designated port IDs. When the designated port ID is 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:
l
2.
The bridge stores the information of the CBPDU (including the root bridge ID, root path cost, Message Age, and corresponding timers). 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). 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). 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. The root bridge ID that is recorded by the port is different from the root bridge ID of the bridge.
18-10
Issue 02 (2009-10-30)

l
18 MSTP
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. 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. 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 sate. 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.
Classification of port states The blocking, listening, and disabled states are combined into the discarding state in the RSTP.
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.
Issue 02 (2009-10-30)
18-11
18 MSTP
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.

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 18-2 Procedure for configuring the MSTP Step 1 Operation A.8.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. 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.
A.8.2 Setting the Bridge Parameters of the MSTP A.8.3 Setting the Parameters of the CIST
Required when you need to configure the MSTP. The parameters need to be set according to the network planning information.
Required when you need to configure the MSTP. The parameters need to be set according to the network planning information.
18-12
Issue 02 (2009-10-30)
18 MSTP
Step 4
Operation A.8.6 Enabling/ Disabling the MSTP Protocol
Description 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. 18.7.1 Networking Diagram This topic describes the networking information about the NEs. 18.7.2 Service Planning The service planning information contains all the parameter information required for configuring the NE data. 18.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 18-5, NE1 is the OptiX RTN 950, and LAN switch 1 and LAN switch 2 are two Ethernet switches that run the MSTP protocola.
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 950 supports only the MSTP that generates the CIST.
Issue 02 (2009-10-30)
18-13
18 MSTP

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 18-3. Table 18-3 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(Port-1)2-EM6T-2(Port-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 18-4.
18 MSTP
Table 18-4 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 18-5. Table 18-5 CIST Parameter Parameter Bridge Priority Port Priority Path Cost NE1 32768 128 200000

Procedure
Step 1 See A.8.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(Port-1)2-EM6T-2(Port-2)
Issue 02 (2009-10-30)
18-15
18 MSTP
Step 2 See A.8.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 Value Range 7 Hello Time(s) Max Age(s) Forward Delay(s) Enable Edge Attribute Point-to-Point Attribute Max Transmit Packet Count 2 20 15 Disabled auto 3
Step 3 See A.8.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.8.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 Concepts
A.8.1 Creating the MSTP Port Group A.8.2 Setting the Bridge Parameters of the MSTP A.8.3 Setting the Parameters of the CIST A.8.4 Querying the CIST Running Information
18 MSTP
A.8.5 Changing the Spanning Tree Protocol Used by the Port Group A.8.6 Enabling/Disabling the MSTP Protocol A.8.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.
18.10 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 950, 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.
Issue 02 (2009-10-30)
18-17
19 IGMP Snooping
19
About This Chapter
IGMP Snooping
If the multicast router exists in a network, the bridge can enable the IGMP Snooping protocol to realize the multicast function with the operation of the router. 19.1 Feature Description Using the IGMP Snooping protocol can effectively reduce the link bandwidth of the multicast service and improve security of the multicast service. 19.2 Basic Concepts This topic describes the basic concepts that you need to be familiar with before you use the IGMP Snooping feature. 19.3 Availability The IGMP Snooping feature requires the support of the applicable boards. 19.4 Relation with Other Features The IGMP Snooping feature is related to the Ethernet feature, LAG feature, and ERPS feature. 19.5 Realization Principle The IGMP Snooping creates and maintains the mapping between group members and switch ports by sensing IGMP packets. This ensures that multicast packets are transmitted only to the ports that are connected to multicast users. 19.6 Configuration Procedure When the IGMP Snooping protocol is applied, you can set the static router port and the static routing member, except for the IGMP Snooping parameters. 19.7 Configuration Example This topic describes how to plan and configure the IGMP Snooping by using an example. 19.8 Task Collection This topic provides the hyperlinks of the operation tasks regarding the relevant feature. 19.9 Relevant Alarms and Events If the multicast entries or multicast members reach the maximum number, the system control and communication board reports the corresponding abnormal event. 19.10 FAQs
19 IGMP Snooping
This topic provides the answers to the questions that are frequently raised when the IGMP Snooping function is used.
19-2
Issue 02 (2009-10-30)
19 IGMP Snooping

Using the IGMP Snooping protocol can effectively reduce the link bandwidth of the multicast service and improve security of the multicast service.
Multicast Protocol
The multimedia network applications, such as video conference, E-learning, and video on demand (VOD) service, require that information is transmitted from one source to multiple destinations, that is, a one-to-many transmission mode. Simulating the one-to-many transmission through one-to-one mode occupies a large number of bandwidths because the data traffic volume of the multimedia information is large. In addition, information flooding is generated if the broadcast mode is used. Hence, the one-to-many multicast protocol is required. The IP multicast protocol is based on the IP protocol stack. The IP multicast protocol uses a Dtype IP address that is similar to the unicast address to indicate a group. When a packet is transmitted to all the IP hosts in a multicast group, the calling and access mode is similar to the calling and access mode of the unicast. The hosts in an IP multicast group can join or quit this multicast group at any time and at any location, without restrictions on the number of members. The multicast router does not store the member relations of all the hosts. The router stores the information only about whether any host in the physical subnetwork on the physical interface belongs to a specific multicast group. The host stores the information only about the multicast groups that it joins. IP multicast protocols are classified into two categories: (1) communication protocol between the multicast routers; (2) protocol between the multicast routers, hosts, and Layer 2 switches.
l
The communication protocol between multicast routers is used to obtain the multicast routing information. This type of protocol contains the protocol independent multicastdense mode (PIM-DM), protocol independent multicast-sparse mode (PIM-SM), and distance vector multicast routing protocol (DVMRP). The protocol between multicast routers, hosts, and Layer 2 switches is used to forward multicast packets according to the multicast routing information. This type of protocol contains the IGMP, IGMP Snooping, IGMP Proxy, and Cisco group management protocol (CGMP). The IGMP is a Layer 3 multicast protocol, whereas the IGMP Snooping, IGMP Proxy, and CGMP are Layer 2 multicast protocols.
IGMP
Contained in the TCP/IP suite, the IGMP is used to manage members of the IP multicast group. The IGMP creates and maintains the member relations of the multicast group between the host and its adjacent multicast router. The host notifies the local router of joining a specific multicast group and accepting the information from this multicast group through the IGMP. The router periodically queries whether a member of a specific group in the LAN is activated through the IGMP (that is, whether the member of a specific multicast group still exists in the network segment), and thus collects and maintains the member relations of groups that are connected to the router. Through this mechanism, the multicast router creates a table, which contains the ports of the router and members of each specific group in the subnetworks corresponding to each port. When receiving the packet of a specific group, the router forwards the packet only to these ports that have the members of this group.
19 IGMP Snooping
The router uses the IP multicast address to forward multicast packet. Each multicast group corresponds to a specific IP multicast address. The IP multicast address is a D-type IP address, which ranges from 224.0.0.0 to 239.255.255.255.
IGMP Snooping
When the multicast router is connected to the host by using the bridge, and if the bridge disables the Layer 2 multicast protocol, the switch broadcasts the multicast packet at Layer 2, as shown in Figure 19-1. When the multicast router is connected to the host by using the bridge, if the bridge enables the Layer 2 multicast protocol (such as IGMP Snooping), the bridge can establish the mapping between groups members and switch ports and thus can forward the packet only to the ports that have group members. Figure 19-1 Transmission of multicast packets (with the IGMP Snooping protocol disabled)
Internet/ Intranet Video stream
VOD server Multicast router Video stream Layer 2 Ethernet switch Video stream Video stream Video stream
Multicast group member
Non-multicast Non-multicast group member group member
Figure 19-2 Transmission of multicast packets (with the IGMP Snooping protocol enabled)
Internet/ Intranet Video stream
VOD server Multicast router Layer 2 Ethernet switch Video stream Video stream
Multicast group member
Non-multicast Non-multicast group member group member
19-4
Issue 02 (2009-10-30)
19 IGMP Snooping
The IGMP Snooping function creates and maintains the mapping between group members and switch ports by sensing IGMP packets. After the IGMP Snooping protocol is enabled, the bridge considers the port that receives the IGMP query packet as the router port. When the bridge detects the response that is transmitted to the router port, the bridge adds the port that receives the response and the router port to a specific multicast group. When the bridge detects that a certain port in a multicast group does not respond to the IGMP query packet for consecutive times that exceed the threshold, the bridge deletes this port from the multicast group. After the IGMP Snooping is enabled, the bridge queries the multicast table in which the source port is the router port when receiving the multicast packet. If a multicast group that matches the multicast address exists in the multicast table, the bridge forwards the packet to this multicast group. If no multicast group exists, the bridge discards the multicast packet or broadcasts the packet depending on the NM setting. The IGMP packet is available in three versions: V1, V2, and V3. The OptiX RTN 950 can process versions V1 and V2.
19.2 Basic Concepts

This topic describes the basic concepts that you need to be familiar with before you use the IGMP Snooping feature.
l
Router port The router port refers to a port that connects to the multicast router. Multicast member port The multicast member port refers to a port that connects to the multicast group member. The multicast group member refers to a host that joins a multicast group.
Multicast group The multicast group records the mapping between the router ports, MAC multicast addresses, and multicast group members. A multicast group is also called a multicast table entry. Multicast table entries are classified into the static multicast table entry and dynamic multicast table entry. A static multicast table entry must be manually configured by users and will not be aged. A dynamic table entry is obtained by the bridge through the SVL/IVL mode. A dynamic table entry will be aged.
NOTE
If a router port is not refreshed in a certain period (that is, no IGMP request from this port is received), all the multicast groups that are related to this router port are deleted. This mechanism is called aging, and this period is called aging time. The aging time is eight minutes by default and can be set by using the NMS. The OptiX RTN 950 supports up to 512 multicast groups.
l l
Maximum query response time When transmitting the IGMP query packet to the multicast member port, the router port starts the maximum query response timer. If the bridge does not receive the IGMP response packet within the maximum query response time, the no-response times of the port are increased by one. When the no-response times of the port exceed the pre-set threshold, the bridge deletes the multicast member from the multicast group.
IGMP general query packet

Issue 02 (2009-10-30)
19 IGMP Snooping
The IGMP general query packet refers to a packet that is transmitted by the multicast router to the multicast group members. The IGMP general query packet is used to query which multicast groups have members.
l
IGMP specific query packet The IGMP specific query packet refers to a packet that is transmitted by the multicast router to the multicast group members. The IGMP specific query packet is used to query whether specific multicast groups have members.
IGMP report packet The IGMP report packet refers to a report packet that is transmitted by a host to the multicast router. The IGMP report packet is used to applying for the joining of a multicast group or to respond to the IGMP query packet.
Quickly delete The quickly delete is the advanced attribute of the multicast member port. When this function is enabled, a port is directly deleted from the multicast group after receiving the IGMP leave packet.
19.3 Availability
The IGMP Snooping feature requires the support of the applicable boards. Table 19-1 Availability of the IGMP Snooping Feature IGMP Snooping Applicable Board IFU2 IFX2 EM6T EM6F Applicable Board Version All the functional versions All the functional versions All the functional versions All the functional versions

The IGMP Snooping feature is related to the Ethernet feature, LAG feature, and ERPS feature.
l l l
The IGMP Snooping protocol can be enabled only in the E-LAN service. One LAG can become a member of the multicast group. The ERPS does not affect the IGMP Snooping.

The IGMP Snooping creates and maintains the mapping between group members and switch ports by sensing IGMP packets. This ensures that multicast packets are transmitted only to the ports that are connected to multicast users.
19 IGMP Snooping
Processing Flow
The 802.1q bridge processes the IGMP Snooping as follows: 1. If the bridge receives the IGMP general query packet or the IGMP specific query packet, it processes this packet as follows: (1) The bridge checks whether the port that receives the packet is already learnt as the router port. (2) If this port is not learnt, the bridge records this port as the router port. (3) If the port that receives this packet is already recorded as the router port, the bridge broadcasts this packet in the specific multicast group and starts the timer for the maximum query response time. Otherwise, the bridge broadcasts this packet in the VLAN domain of the 802.1q bridge. After receiving the query packet, the router port refreshes the MAC address aging time of the port. 2. If the bridge receives the IGMP report packet, it processes this packet as follows: (1) The bridge checks whether the multicast record is already learnt in the VLAN domain of the 802.1q bridge. (2) If this multicast record is not learnt and if the multicast group does not exist, the bridge creates the multicast group and creates the mapping between the router ports, MAC multicast addresses, and multicast group members by considering this port as the multicast member port. (3) If this multicast record is not learnt, but this port is not contained in the multicast member ports of the multicast group, the multicast group adds this port as the multicast member port. (4) If this multicast record is learnt, the bridge re-sets the count of no-response times for this multicast member. 3. If the bridge receives the multicast packet, it processes this packet as follows: (1) Queries the multicast table that uses the source port as the router port. (2) If a multicast group that matches the multicast address exists in the multicast table, the bridge forwards the packet to this multicast group. (3) If no multicast group exists, the bridge discards the multicast packet or broadcasts the packet in the VLAN range according to the NM setting. 4. The bridge processes the aging of dynamic multicast members as follows: (1) If the maximum query response time times out, the bridge adds one to the no-response times of the multicast member. (2) If the no-response times of a multicast member exceeds the threshold, the bridge deletes this multicast member port. (3) When the members in the multicast group leave the group, the multicast management router sends the specific query packet to all the connected switches (applicable to IGMPv2 only). In this manner, the router determines whether any members exist in the group. If there are no members, the router deletes this multicast group. 5. The bridge ages the dynamic router port as follows: After the VLAN learns the router port, a router port aging timer is enabled for this port. If the timer times out, the bridge deletes the router port. If this port is the last router port in the VLAN domain, the bridge deletes all the multicast groups that are learnt in the VLAN domain. 6.
Issue 02 (2009-10-30)
The bridge processes the leave packet as follows:

19 IGMP Snooping
If the bridge receives a leave packet, the bridge deletes this multicast member from the multicast group. If this port is the last multicast member port in the VLAN domain, the bridge deletes this multicast group.
NOTE
The 802.1d bridge processes the IGMP Snooping in a similar way. The difference is that the 802.1d learns the packet by using the SVL mode rather than using the IVL mode, and the 802.1d bridge broadcasts the packet without the restriction of the VLAN domain.
Version
The IGMP packet is available in three versions: V1, V2, and V3. The Ethernet switching board can process versions V1 and V2. V2 is compatible with V1. Compared with V1, V2 is improved as follows:
l
Supports the leave packet. This packet can efficiently decrease the delay generated in the process of deleting the multicast group.
Supports the specific query packet. This packet allows broadcasting the IGMP query packet only in the specific multicast group.
Supports the setting of maximum response query time

When the IGMP Snooping protocol is applied, you can set the static router port and the static routing member, except for the IGMP Snooping parameters. Table 19-2 Procedure for Configuring the IGMP Snooping Step 1 Operation A.9.1 Configuring the IGMP Snooping Protocol Description Required. The parameters need to be set according to the service planning. It is recommended that you use the default values. Optional. If a routing port need not be aged, you can configure the port as a static routing port. 3 A.9.5 Creating a Member of a Static Multicast Group Optional. If a multicast member need not be aged, you can configure the port as a static multicast group member.
A.9.4 Creating Static Router Ports
19-8
Issue 02 (2009-10-30)
19 IGMP Snooping
Step 4
Operation A.9.6 Adding a Quickly Deleted Port
Description Optional. If only one receiver of the multicast service is connected to the multicast member port, you can set the fast leave function for the member port. After receiving the leave packets, the member port is deleted immediately and does not forward the query packet.

This topic describes how to plan and configure the IGMP Snooping by using an example. 19.7.1 Networking Diagram The topic describes the networking information about the NEs. 19.7.2 Service Planning The service planning information contains all the parameter information required for configuring the NE data. 19.7.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 19-3, the E-LAN service (service ID: 1; service name: qlan_igmp) of NE1 carries the multicast service. To increase the multicast efficiency, you need to enable the IGMP Snooping function. The service requirements are as follows:
l l
NE1 functions as the end node and accesses the network through the 3-IFU2 board. The 5-EM6T-3 port is directly connected to a host.
Issue 02 (2009-10-30)
19-9
19 IGMP Snooping
Figure 19-3 Networking Diagram
NE1 Internet/Intranet FE FE FE Ethernet switch Host Ethernet switch VOD server
Host
Host
Host
Host

The service planning information contains all the parameter information required for configuring the NE data. In this example, the IGMP Snooping information is as follows:
l l l
The aging time is set to the default value (8s). The maximum number of no responses is set to the default value (3). The router port can be the IFUP port only. Hence, you can set the 3-IFU2-1 port to the static router port to prevent it from being aged. The 5-EM6T-3 port is connected to a host. Hence, you can set the port to the fast leave port. In this case, after receiving the IGMP Leave packets, the equipment can quickly delete the port from the multicast group.
NOTE
The static router port and the fast leave port need to be set according to the requirements.

Procedure
Step 1 See A.9.1 Configuring the IGMP Snooping Protocol and configure the IGMP Snooping protocol. The values for the parameters of Protocol Configuration are provided as follows.
19 IGMP Snooping
Parameter
Value Range NE1
Enabled Protocol Router Port Aging Time (min) Maximum Times of No Response from Multicast Members
Enabled 8 3
Step 2 See A.9.6 Adding a Quickly Deleted Port and add a quickly deleted port. The values for the parameters of Fast Leave Member Port are provided as follows. Parameter Value Range NE1 Port 5-EM6T-3
Step 3 See A.9.4 Creating Static Router Ports and create the static router ports. The values for the parameters of Route Management are provided as follows. Parameter Value Range NE1 Port 3-IFU2-1
----End

Related Concepts
A.9.1 Configuring the IGMP Snooping Protocol A.9.2 Querying the Port Information of the Routers A.9.3 Querying the Information About the Multicast Groups A.9.4 Creating Static Router Ports A.9.5 Creating a Member of a Static Multicast Group A.9.6 Adding a Quickly Deleted Port A.9.7 Calculating IGMP Packets
19 IGMP Snooping

If the multicast entries or multicast members reach the maximum number, the system control and communication board reports the corresponding abnormal event.
Relevant Alarms
None.

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

For details, see RMON Event Reference.
19.10 FAQs
This topic provides the answers to the questions that are frequently raised when the IGMP Snooping function is used. Q: Does the IGMP Snooping change the packets that are transmitted between the multicast server and the host? A: The IGMP Snooping function is the multicast constraint mechanism that is adopted by the L2 equipment. This function is used for managing and controlling the multicast group so that the packets transmitted by the multicast service are propagated among the multicast group. The IGMP Snooping function, however, does not change the packets.
19-12
Issue 02 (2009-10-30)
20
About This Chapter
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. 20.1 Feature Description The LAG aggregates multiple physical links to form a logical link that is at a higher rate to transmit data. Link aggregation functions between adjacent equipment. Hence, link aggregation is not related to the architecture of the entire network. Link aggregation is also called port aggregation because links correspond to ports one to one on an Ethernet. 20.2 Basic Concepts This topic describes the basic concepts that you need to be familiar with before you use the LAG feature. 20.3 Availability The LAG features requires the support of the applicable boards. 20.4 Relation with Other Features The LAG is related to the 1+1 protection scheme, N+1 protection scheme, XPIC, ERPS, MSTP, IGMP Snooping, and AM. 20.5 Realization Principle 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. 20.6 Configuration Procedure When applying the LAG protocol, you need to configure the LAG and configure the priorities of ports in the LAG as required. 20.7 Configuration Example By using an example, this topic describes how to plan and configure LAGs according to the network conditions. 20.8 Task Collection This topic provides the hyperlinks of the operation tasks regarding the relevant feature.
20.9 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. 20.10 FAQs This topic provides the answers to the questions that are frequently raised when the LAG is adopted.
20-2
Issue 02 (2009-10-30)

The LAG aggregates multiple physical links to form a logical link that is at a higher rate to transmit data. Link aggregation functions between adjacent equipment. Hence, link aggregation is not related to the architecture of the entire network. Link aggregation is also called port aggregation because links correspond to ports one to one on an Ethernet. As shown in Figure 20-1, the LAG provides the following functions:
l
Increased bandwidth The LAG provides users with an economical method of increasing the link bandwidth. The 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 members by using the load sharing algorithm, thus realizing the load sharing function at the link level.
Increased availability The links in a LAG dynamically back up each other. When a link fails, another link in the LAG quickly replaces the faulty link. The process in which link aggregation starts the backup link is related only to the links in the same LAG and is not related to the links that are not in the LAG.
Figure 20-1 Link aggregation group

Link 1 Link 2 Ethernet packet Link 3 Link aggregation group Ethernet packet
The LAG complies with IEEE 802.3ad.
20.2 Basic Concepts

This topic describes the basic concepts that you need to be familiar with before you use the LAG feature. 20.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. 20.2.2 Port Types In the LAG, ports are classified into the main port and slave port. 20.2.3 Switching Condition A service is switched between ports when a port fails or the key chip of a port is faulty.
20.2.4 Switching Impact During a LAG switching (the switching time is not longer than 500 ms), all the services on the link are interrupted.
20.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 perform aggregation depending on the physical status of a port (up or down).
Static aggregation A user manually creates a LAG. When a user adds or deletes a member port, the LACP protocol is started. A port can be in the selected or standby state. The LACP protocol determines the active and inactive links in the aggregation group. Static aggregation is more accurate and more effective than manual aggregation in controlling link aggregation.
Load Sharing
The LAG supports the following load sharing modes:
l
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:

AUTO Based on MAC addresses, including the source MAC address, destination MAC address, and source MAC address Xor destination MAC address. Based on IP addresses, including the source IP address, destination IP address, and source IP address Xor destination IP address.
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 950 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.
20-4
Issue 02 (2009-10-30)
20.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
The main port represents the LAG to participate in service configuration. A LAG has exactly one main port. The main port can either in the selected state or in the standby state, independent of the port status. The main port must be in the affiliated aggregation group until the aggregation group is deleted. When the aggregation group is deleted, all the services in the aggregation group continue to exist on the main port and no services are lost.
NOTE
In a LAG, when the port status is selected, the port can bear services; when the port status is standby, the port cannot bear services.
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
The slave port cannot participate in service configuration. A LAG can have several slave ports. The slave port can either in the selected state or in the standby 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 20-1 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.
Issue 02 (2009-10-30)
20-5
Switching Condition The microwave port is in the link down state.
Description 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, or IF_CABLE_OPEN 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. If the hardware of an 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.
The hardware of an IF unit or ODU is faulty.
The LACP detects a failure in the link.

During a LAG switching (the switching time is not longer than 500 ms), all the services on the link are interrupted.
20.3 Availability
The LAG features requires the support of the applicable boards. Table 20-2 Availability of the LAG feature Feature LAG Applicable Board IFU2 IFX2 EM6T EM6F Applicable Board Version All the functional versions All the functional versions All the functional versions All the functional versions

The LAG is related to the 1+1 protection scheme, N+1 protection scheme, XPIC, ERPS, MSTP, IGMP Snooping, and AM.

l
When you create a 1+1 HSB/FD/SD protection group of the Hybrid radio, the NE automatically creates a LAG in non-load sharing mode. The main port is the IFUP port on the main IF board and the slave port is the IFUP 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 Hybrid radio, the NE automatically creates a LAG in load sharing mode. By default, the main port is the IFUP 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 Hybrid radio, manually create the LAG because the NE does not automatically create a corresponding LAG. One LAG can be a member of an MSTP port group. One LAG can be a member of an IGMP Snooping multicast group. 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. FE ports and GE ports cannot be aggregated.
l l l

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).
Issue 02 (2009-10-30)
20-7
Figure 20-2 Frame format of the LACP packet
Table 20-3 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.
20-8
Issue 02 (2009-10-30)
Parameter Actor_System_Priority/ Partner_System_Priority Actor_System/ Partner_System Actor_Key/Partner_Key
Meaning System priority at the local end/opposite end System ID at the local end/ opposite end Operation key at the local end/opposite end
Description 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.
Procedure for Creating the Static LAG

As shown in Figure 20-3, 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. 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.
3.
4.
Issue 02 (2009-10-30)
20-9
Figure 20-3 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.
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.

When applying the LAG protocol, you need to configure the LAG and configure the priorities of ports in the LAG as required.
20-10
Issue 02 (2009-10-30)
Table 20-4 Procedure for configuring the LAG based on the 802.1q bridge St ep 1 Operation A.10.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. 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. When the Hybrid radio uses the N+0 non-protection scheme, set Load Sharing to Sharing for the equipment at both ends. 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. 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. 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. 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.
A.10.2 Setting the Port Priority
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.
Issue 02 (2009-10-30)
20-11

By using an example, this topic describes how to plan and configure LAGs according to the network conditions. 20.7.1 Networking Diagram The topic describes the networking information about the NEs. 20.7.2 Service Planning The service planning information contains all the parameters required for configuring the NE data. 20.7.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 20-4, the Hybrid radio link between NE1 and NE2 adopts the 2+0 nonprotection scheme. Hence, the IFUP ports that correspond to the radio link need to be configured as a load-sharing LAG. Figure 20-4 Networking diagram
Link 1 Link 2 NE1 Main port: 3-IFU2-1 Standby port: 3-IFU2-2 LAG NE2 Main port: 3-IFU2-1 Standby port: 3-IFU2-2

The service planning information contains all the parameters required for configuring the NE data. Table 20-5 provides the information about LAG configuration on the NE. Table 20-5 LAG information Parameter LAG Type Load Sharing NE1 Static (default value) Sharing ME2 Static (default value) Sharing
20-12
Issue 02 (2009-10-30)
Parameter Load Sharing Hash Algorithm System Priority Main Port Slave Port
NE1 Source MAC (default value) 32768 (default value) 3-IFU2-1 3-IFU2-2
ME2 Source MAC (default value) 32768 (default value) 3-IFU2-1 3-IFU2-2
NOTE
The load sharing hash algorithm can be set to any of the following six modes: source MAC, destination MAC, source and destination MAC, source IP, destination IP, and source and destination IP. Unless otherwise specified, set the algorithm to the default mode.

Procedure
Step 1 See A.10.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 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 3-IFU2-2
----End

Related Concepts
A.10.1 Creating a LAG A.10.2 Setting the Port Priority A.10.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.
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.
20.10 FAQs
This topic provides the answers to the questions that are frequently raised when the LAG is adopted. Q: Does the OptiX RTN 950 support the dynamic LAG? A: The OptiX RTN 950 does not support the dynamic LAG.
20-14
Issue 02 (2009-10-30)
21
About This Chapter
Link State Pass Through
The link state pass through (LPT) is used to detect the faults that occur at the service access node and in the intermediate transmission network. The LPT notifies the equipment that accesses the service of starting the backup link at the earliest time for communication, thus making sure the normal transmission of the important data. 21.1 Feature Description OptiX RTN 950 realizes certain functions of the LPT. When the Hybrid radio link is faulty, the Ethernet port that is associated with the radio link is shut down automatically. In this manner, when the transmission network is faulty, the service accessing equipment is notified of this failure. 21.2 Availability The LPT feature requires the support of the applicable boards. 21.3 Relation with Other Features The LPT feature is related to the 1+1 protection configuration and N+1 protection configuration. 21.4 Realization Principle The OptiX RTN 950 realizes the LPT function by configuring the mapping between the IF interface and the Ethernet port. 21.5 Configuration Procedure The configuration procedure for the LPT contains only one configuration task. 21.6 Configuration Example This topic uses an example to describe how to plan and configure the LPT. 21.7 Task Collection This topic provides the hyperlinks of the operation tasks regarding the LPT feature. 21.8 Relevant Alarms and Events There are no alarms or performance events related to the LPT. 21.9 FAQs This topic provides the answers to the questions that are frequently asked when the LPT is used.
Issue 02 (2009-10-30)
21-1

OptiX RTN 950 realizes certain functions of the LPT. When the Hybrid radio link is faulty, the Ethernet port that is associated with the radio link is shut down automatically. In this manner, when the transmission network is faulty, the service accessing equipment is notified of this failure. The LPT realized by the OptiX RTN 950 is used to detect and report the faults that occur in the intermediate transmission network. The LPT notifies the equipment that accesses the service of starting the backup link at the earliest time for communication, thus ensuring the normal transmission of the important data. The LPT is a link-based protection scheme. The application of the LPT is as shown in Figure 21-1. Figure 21-1 LPT networking diagram
Standby link
Service link Router A NE1 NE2 RouterB
In normal situations, the data of router A and router B is exchanged on the service link. When the link between router A and router B is faulty, the communication between router A and router B is interrupted. For important users, however, even when such fault occurs, the important data must be transmitted normally. Thus, the system must be able to detect and report faults at the earliest time and then start the backup link to ensure the communication. When the LPT function is enabled, the equipment detects and reports the faults. Then, the data communication equipment such as a router can start the standby link for communication. In this manner, the normal transmission of important data is ensured.
21.2 Availability
The LPT feature requires the support of the applicable boards.
21-2
Issue 02 (2009-10-30)
Table 21-1 Availability of the LPT feature Feature LPT Applicable Board EM6T EM6F Applicable Board Version All the functional versions All the functional versions

The LPT feature is related to the 1+1 protection configuration and N+1 protection configuration.
l
In the case of a radio link configured with the 1+1 protection, the LPT closes the Ethernet port to which the radio link corresponds only if both the main and standby radio links are faulty. In the case of a radio link configured with the N+1 protection, the LPT closes the Ethernet port to which the radio link corresponds only if both the main and standby radio links are faulty.

The OptiX RTN 950 realizes the LPT function by configuring the mapping between the IF interface and the Ethernet port. As shown in Figure 21-2, the LPT function is realized as follows: 1. 2. 3. When the service link is faulty, the IF unit shuts down the IFUP port. After detecting that the IFUP port is shut down, the packet switching unit reports the fault to the system control unit. After receiving the fault information about the interface, the system control unit finds the corresponding Ethernet port according to the mapping between the IF interface and the Ethernet port. Then, the system control unit instructs the Ethernet interface unit to shut down the Ethernet port. When the fault in the link is rectified, the system control unit instructs the Ethernet interface unit to open the corresponding Ethernet port.
4.
Issue 02 (2009-10-30)
21-3
Figure 21-2 Realization diagram of the LPT function
Standby link
Service link Router A NE1 NE2 Router B
NOTE
l l
If the service link is faulty bidirectionally, NE1 and NE2 can detect the fault in the service link. In this case, NE1 and NE2 shut down their corresponding Ethernet ports. If the service link is faulty unidirectionally, for example, from the direction B to A, only NE1 can detect the fault in the service link. In this case, only NE1 shuts down the corresponding Ethernet port.

The configuration procedure for the LPT contains only one configuration task. Table 21-2 Procedure for configuring the LPT Step 1 Operation A.11 LPT Configuration Description Required. Set the aggregation port and the corresponding access port according to the planning information.

This topic uses an example to describe how to plan and configure the LPT. 21.6.1 Networking Diagram This topic describes the networking information about the NEs. 21.6.2 Service Planning
The service planning information contains all the parameter information required for configuring the NE data. 21.6.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 21-3, the services transmitted by each BTS carry VLAN tags. When the radio link between NE1 and NE2 is faulty, you need to close the Ethernet port that is associated with the IF port and request the accessed BTS to enable the standby link, thus ensuring the normal communication of important data. Figure 21-3 Networking diagram of the LPT
3-IFU2-1 (to NE2) 1-EM6T-1 (to BTS1) 1-EM6T-2 (to BTS2) 3-IFU2-1 (to NE1) 1-EM6T-5 (to BSC)
BTS1 VLAN ID: 100-109 NE1 BTS2 VLAN ID: 110-119 Ethernet link Radio link NE2 BSC

Configuration Information About the LPT

Table 21-3 provides the configuration information about the LPT. Table 21-3 Configuration information about the LPT Parameter Aggregate port Access port NE1 3-IFU2-1 1-EM6T-1 1-EM6T-2 NE2 3-IFU2-1 1-EM6T-5
Issue 02 (2009-10-30)
21-5

Procedure
Step 1 See A.11 LPT Configuration and configure the LPT. 1. Configure the aggregation point. The values for the related parameters are provided as follows. Parameter Value Range NE1 Board Port 3-IFU2 1 NE2 3-IFU2 1
2.
Configure the access point. The values for the related parameters are provided as follows. Parameter Value Range NE1 Board Port 1-EM6T 1 1-EM6T 2 NE2 1-EM6T 5
----End

This topic provides the hyperlinks of the operation tasks regarding the LPT feature.
Related Concepts
A.11 LPT Configuration

There are no alarms or performance events related to the LPT.
21.9 FAQs
This topic provides the answers to the questions that are frequently asked when the LPT is used.
Q: Can the LPT inform the equipment at the opposite end when the Ethernet link between the client equipment and the Ethernet port at the local end is interrupted? A: No. In the case of OptiX RTN 950, the LPT function detects and reports the faults that occur on the intermediate transmission link. When the Hybrid radio link is faulty, the Ethernet port that is associated with the radio link is shut down automatically. In this manner, the accessed client equipment is informed when the transmission network is faulty.
Issue 02 (2009-10-30)
21-7
22 QoS
22
About This Chapter
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. 22.1 Feature Description In legacy IP networks, all packets are processed in first in first out (FIFO) queues according to the best effort strategy. This method cannot meet the stringent requirements of the new service for the bandwidth, delay, and delay jitter. Therefore, the QoS technology is developed. 22.2 Basic Concepts This topic describes the basic concepts that you need to be familiar with before you use the QoS feature. 22.3 Availability The QoS feature requires the support of the applicable boards. 22.4 Relation with Other Features The QoS feature is associated with the AM feature. 22.5 Realization Principle The CAR and traffic shaping are based on the token bucket algorithm. 22.6 Configuration Procedure Before applying a QoS policy to a specific QoS object, you need to set the QoS policy. 22.7 Configuration Example This topic uses an example to describe how to plan and configure the QoS according to the conditions of the network. 22.8 Task Collection This topic provides the hyperlinks of the operation tasks regarding the relevant feature. 22.9 Relevant Alarms and Events There are not any QoS-related alarms or abnormal events. 22.10 FAQs
22 QoS
This topic describes the answers to the questions that are frequently raised when the QoS feature is used.
22-2
Issue 02 (2009-10-30)
22 QoS

In legacy IP networks, all packets are processed in first in first out (FIFO) queues according to the best effort strategy. This method cannot meet the stringent requirements of the new service for the bandwidth, delay, and delay jitter. Therefore, the QoS technology is developed. Newly emerging services have special requirements for transmission performance indexes such as the bandwidth, delay, and delay jitter. The best effort service mode that is adopted by legacy networks, however, does not provide complete service capabilities. The QoS technology is developed to solve this problem. To support voice, video, and data services that have different service requirements, a network must be able to differentiate communication types and thus provide relevant services. Figure 22-1 shows how packets are transmitted through an interface that does not support the QoS.
l
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. Therefore, the packet that first arrives enters the queue first. 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 guaranteed.
Figure 22-1 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
Figure 22-2 shows how the packets are transmitted through prioritized queues when an interface supports the QoS.
l
After packets arrive at the interface, the packets are classified first. This method is called flow classification. After the flow classification is complete, flows of different types can be processed according to their different QoS requirements. Then, these packets enter the tail of their corresponding queues according to their types. The interface transmits the higher-priority packets in the queue first and then transmits the lower-priority packets in the queue. In this manner, the higher-priority packets are always transmitted first and these packets have only low delay jitter. In addition, the packet loss ratio and delay jitter can be reduced even in the case of network congestion.
l l
Issue 02 (2009-10-30)
22-3
22 QoS
Figure 22-2 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
As shown in Figure 22-2, prioritized queues illustrate only one function of the QoS. Congestion management is provided through the prioritized queues. The OptiX RTN 950 provides multiple QoS functions, including the differentiated service (DiffServ), flow classification, committed access rate (CAR), traffic shaping, and queue scheduling. These functions comply with IEEE 802.1p, RFC 2474, RFC 2698, RFC 2309, RFC 2597, and RFC 2598.
...
Lowest
22.2 Basic Concepts

This topic describes the basic concepts that you need to be familiar with before you use the QoS feature. 22.2.1 DiffServ As an end-to-end QoS control model, the DiffServ can be simply realized and easily extended. 22.2.2 Flow Classification The OptiX RTN 950 supports two flow classification methods, namely, simple flow classification and complex flow classification. 22.2.3 CAR The CAR is a type of traffic policing technology. When the CAR is used, the rate of the traffic after flow 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. 22.2.4 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. 22.2.5 Queue Scheduling The OptiX RTN 950 supports three queue scheduling methods, namely, strict-priority (SP), weighted round robin (WRR), and SP+WRR. 22.2.6 QoS Model The OptiX RTN 950 supports the QoS model based on ports.
22-4
Issue 02 (2009-10-30)
22 QoS
22.2.1 DiffServ
As an end-to-end QoS control model, the DiffServ can be simply realized and easily extended.
DiffServ Domain
In a DiffServ model, a packet represents its QoS level through the carried QoS information. The DiffServ model provides differentiated services for collections of packets that have different QoS levels. Based on the DiffServ model, a network is divided into several DiffServ domains (also referred to as DS domains). A DS domain consists of a group of network nodes (DS nodes) that provide the same service policy and realize the same per-hop behavior (PHB). The DS nodes can be classified into two types, namely, DS edge nodes and DS interior nodes. In the DS domain as shown in Figure 22-3, the DS edge node identifies the QoS information (VLAN priority and DSCP value) carried by the packets that enter the DS domain. After that, the DS edge node aggregates the packets that are at the same QoS level. A collection of the aggregated packets is called a behavior aggregate (BA). The DS edge node controls the traffic of the BA based on the configured PHB service level, and forwards the BA to the DS interior node. The DS interior node controls the traffic of the BA based on the PHB service level and then forwards the BA to the DS edge node of the next hop. Figure 22-3 DiffServ model
DS interior node
DS domain Non-DS node DS edge node DS edge node Non-DS node
PHB Service Level

The PHB service level indicates the forwarding action performed by the DS node on the BA. The forwarding action can meet a specified requirement. PHB service levels provide eight types of QoS, namely, BE, AF1, AF2, AF3, AF4, EF, CS6, and CS7. The mapping relation between the priority (C-VLAN priority, S-VLAN priority, and DSCP value) of a packet in the DS domain and the eight PHB service levels can be configured. A default DS domain is available on the OptiX RTN equipment. Before the configuration, all the ports are in this domain. The default DS domain cannot be modified or deleted. In this default DS domain, a default mapping relation is defined. Table 22-1 and Table 22-2 provide the mapping relations between the priorities of ingress packets and PHB service levels and the mapping relations between the priorities of egress packets and PHB service levels on the OptiX RTN 950. BE is the default PHB service level.
NOTE
The packet that carries the C-VLAN priority, S-VLAN priority, or DSCP value is trusted by the OptiX RTN 950. The untrusted packet is mapped to the BE service level by default and forwarded in best effort mode. If the DS domain is defined by the user, the DSCP value that is not mapped to the AF1-CS7 service levels is mapped to the BE service level by default and forwarded in best effort mode.
Issue 02 (2009-10-30)
22-5
22 QoS
Table 22-1 Mapping relations between the priorities of ingress packets and PHB service levels C-VLAN Priority 0 1 2 3 4 5 6 7 S-VLAN Priority 0 1 2 3 4 5 6 7 DSCP (Decimal) 0 8, 10, 12, 14 16, 18, 20, 22 24, 26, 28, 30 32, 34, 36, 38 40, 46 48 56 PHB Service Level BE AF1 AF2 AF3 AF4 EF CS6 CS7
Table 22-2 Mapping relations between the priorities of egress packets and PHB service levels PHB Service Level 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 (Decimal) 0 8, 10, 12, 14 16, 18, 20, 22 24, 26, 28, 30 32, 34, 36, 38 40, 46 48 56
22.2.2 Flow Classification

The OptiX RTN 950 supports two flow classification methods, namely, simple flow classification and complex flow classification.
Simple Flow Classification

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

In the case of the complex flow classification, specified services are classified according to the C-VLAN/S-VLAN ID, C-VLAN/S-VLAN priority, or DSCP value. The flow type is based on
22 QoS
the associated Ethernet service type of the traffic. The OptiX RTN 950 supports the following flow types:
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.
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.
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.
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 CVLAN ID+CVLAN priority or SVLAN ID +SVLAN priority. The OptiX RTN 950 supports the logical AND setting for the two matching rules.
In the case of complex flows, the following QoS processing operations can be performed:
l l l l
Passes or discards the flow according the access control list (ACL). Maps the flow into a new PHB service class. In the ingress direction, restrict the rate of the flow by using the CAR. In the egress direction, perform the flow shaping.
22.2.3 CAR
The CAR is a type of traffic policing technology. When the CAR is used, the rate of the traffic after flow 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 950 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 lower than or equal to 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 is changed) and then forwarded.
Issue 02 (2009-10-30)
22 QoS
l
When the rate of packets that pass the restriction of the CAR is lower than or equal to 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 lower than or equal to 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).
Figure 22-4 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 22-4 CAR processing
MBS PIR CBS CIR PIR CIR PIR MBS CBS CIR
CAR
22.2.4 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. After the traffic shaping function is enabled, the OptiX RTN 950 processes the packets as follows if packets are not available in the buffer queue:
l l
If the rate of the packets is lower than or equal to the preset CIR, the packets are directly forwarded. If the rate of the packets is higher than the CIR but is lower than or equal to the PIR, the packets at a rate higher than the CIR enter the buffer queue and the buffer queue forwards the packets 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 lower than or equal to 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 lower than or equal to 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 packets are available in the buffer queue, the packets rate of which passes the restriction of the PIR enter the buffer queue and the buffer queue forwards these packets at a rate equal to the CIR.
22 QoS
As is evident from the preceding processing mechanism, the differences of the traffic shaping from the CAR are as follows:
l
In the processing of the CAR, the packet that does not conform to the traffic features is downgraded or directly discarded. In the processing of the traffic shaping, the packet that does not conform to the traffic features is stored in the buffer. The packet is directly discarded only when the buffer overflows. The traffic shaping increases the delay of services, but the CAR does not.
Figure 22-5 shows the traffic change after the traffic shaping. During the 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 22-5 Processing of the traffic shaping
PBS PIR CBS CIR
PIR CIR
PIR
Shaping
CIR
22.2.5 Queue Scheduling

The OptiX RTN 950 supports three queue scheduling methods, namely, strict-priority (SP), weighted round robin (WRR), and SP+WRR.
Basic Concepts
Available bandwidth at a port: refers to the bandwidth that the system allocates to a port.
l
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 IFUP port is an internal Ethernet port on the Hybrid IF board. In the transmit direction of Hybrid microwave, the Ethernet services transmitted to the MUX/DEMUX unit of the Hybrid IF board through the IFUP port and are then mapped into the Hybrid microwave frames. In the receive direction of Hybrid microwave, the Ethernet services are demapped from the Hybrid microwave frames and then transmitted to the packet switching unit through the IFUP port. The main differences between the IFUP port and the GE/FE port are as follows:
The IFUP port is an internal Ethernet port. It transmits and receives MAC frames and does not have PHY-layer functions.
Issue 02 (2009-10-30)
22 QoS
The bandwidth over the IFUP port is equal to the Ethernet service bandwidth that the Hybrid microwave supports. Hence, when the AM function is enabled in the case of Hybrid microwave, the bandwidth over the IFUP port changes according to the modulation mode.
SP Scheduling Algorithm
Figure 22-6 illustrates the SP scheduling algorithm. Figure 22-6 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
The SP scheduling algorithm is designed for key service applications. A key service must be processed with the highest priority when congestion occurs so that the response delay can be shortened. For example, a port provides eight outgoing queues, which are prioritized from 7 to 0 in a descending order. 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 22-7 illustrates the WRR scheduling algorithm.
22-10
Issue 02 (2009-10-30)
22 QoS
Figure 22-7 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 outgoing queues and schedules the packets in these queues in turn. This ensures that each queue obtains a certain service period. For example, a port provides four queues. In a descending order of priority, the WRR configures the w4, w3, w2, and w1 weights for the four queues respectively. Each weight stands for the proportion of resources that the relevant queue can obtain from the total resources. If this port is a 100 Mbit/s port and the weights of its four queues are set to 50, 30, 10, and 10 (corresponding to w4, w3, w2, and w1 respectively) by the WRR scheduling algorithm, a minimum of 10 Mbit/ s bandwidth is guaranteed for the queue with the lowest priority. This prevents the disadvantage that packets in the queues with lower priorities may fail to obtain service for a long time in the case of the SP queue scheduling. Another advantage of the WRR scheduling is as follows: Although scheduling of multiple queues is performed in the polling manner, time segment allocated to each queue is not fixed. That is, when a queue is empty, the packets in the next queue are scheduled immediately. In this manner, the bandwidth resources can be fully utilized.
SP+WRR Scheduling Algorithm

As shown in Figure 22-8, the SP+WRR scheduling algorithm combines the advantages of the SP and WRR scheduling algorithms. That is, when the SP+WRR scheduling algorithm is used, one of the outgoing queues is configured as an SP queue so that the priority of these packets can be always scheduled first. In this manner, the key services are processed first. The other outgoing queues adopt the WRR scheduling algorithm so that each queue can obtain a certain service time segment.
Issue 02 (2009-10-30)
22-11
22 QoS
Figure 22-8 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
Consider the port that supports eight outgoing queues as an example.

l
Queue 8 (CoS priority of which is 7) uses the SP algorithm. When this queue has packets, these packets are forwarded first. When this queue does not have packets, packets in other queues are allowed transmitting. Service time segment is allocated to queues 1-7 (CoS priorities of which are 0-6 respectively) according to the weights 1:2:4:8:16:32:64, and at each time segment the packets in the corresponding queue are transmitted. If the queue that corresponds to a time segment does not have packets, this time segment is removed and the packets in the queue that corresponds to the following time segment are transmitted. For example, if four queues are weighted as follows: 1:2:4:8, the WRR allocates the service time segments in the form of cyclic sequence with a period of 432443414342434.
If the traffic shaping of some queues is enabled, the bandwidth is first allocated to the queue traffic shaping of which is enabled according to the preset CIR. The remaining bandwidth is allocated to the queue traffic shaping of which is disabled by using the preceding algorithm. For example, the traffic shaping is enabled for queues 5 and 7, the preset CIR of both queues is 10 Mbit/s, and the total port bandwidth is 25 Mbit/s. In this case, the service time segments are allocated to queue 5, queue 7, and the remaining queues according to the WRR algorithm in which the weights are 10:10:5. When a service time segment corresponding to the collection of the remaining queues arrives, this service time segment is allocated to the remaining queues based on the SP+WRR algorithm. That is, this service time segment is first allocated to queue 8 and then is allocated to queues 1, 2, 3, 4, and 6 according to the weights of these queues 1:2:4:8:32. When the congestion occurs on the egress queues, the packet that is marked yellow in the CAR processing or in the processing of the traffic shaping is first discarded.
22.2.6 QoS Model

The OptiX RTN 950 supports the QoS model based on ports. Figure 22-9 shows the QoS model that is used on the OptiX RTN 950.
22-12
Issue 02 (2009-10-30)
22 QoS
Figure 22-9 QoS model

Ingress Ingress port Egress Egress port
Apply the port policy
Apply the DiffServ policy
Apply the DiffServ policy
Apply the port policy
Apply the port shaping
QoS application point Supported QoS processing functions Service direction
Table 22-3 provides the QoS technologies that are used by each QoS application point in this model. Table 22-3 QoS technologies supported by each application point of the QoS model Application Point of the QoS Ingress Policy Port policy Adopted QoS Technology Complex flow classification (specific service being classified according to the CVLAN/S-VLAN ID, CVLAN/S-VLAN priority, or DSCP value) CAR DiffServ policy Simple flow classification (ingress packets being classified into flows at different PHB service levels according to their priorities) Forwarding the flows at different PHB service levels into corresponding port queues, and remarking packet priorities according to PHB service levels
22-13
Egress
DiffServ policy
Issue 02 (2009-10-30)
22 QoS
Application Point of the QoS
Policy Port policy
Adopted QoS Technology Shaping (based on queues corresponding to PHB service levels) Running the queue scheduling algorithm (SP, WRR, or SP+WRR) for the queues at different PHB service levels after the queue policy is set
Port shaping
Shaping (based on egress ports)
22.3 Availability
The QoS feature requires the support of the applicable boards. Table 22-4 Availability of the QoS feature Feature QoS DiffServ Applicable Board EM6T/EM6F IFU2/IFX2 Flow classificati on CAR EM6T/EM6F IFU2/IFX2 EM6T/EM6F IFU2/IFX2 Traffic shaping Queue scheduling QoS model EM6T/EM6F IFU2/IFX2 EM6T/EM6F IFU2/IFX2 EM6T/EM6F IFU2/IFX2 Applicable Board Version All the functional versions

The QoS feature is associated with the AM feature.
22 QoS
When the AM function is enabled, it is recommended that you configure the QoS for the Ethernet services over the Hybrid 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.

The CAR and traffic shaping are based on the token bucket algorithm. 22.5.1 CAR The CAR uses the dual token bucket three color marker algorithm. 22.5.2 Traffic Shaping The traffic shaping uses the dual token bucket three color marker algorithm that is similar to the algorithm used by the CAR. The buffer queue, however, is added before the Tc token bucket in the algorithm used by the traffic shaping.
22.5.1 CAR
The CAR uses the dual token bucket three color marker algorithm.
Token Bucket Algorithm

Figure 22-10 shows the basic working principle of the token bucket algorithm. Figure 22-10 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.
22 QoS
Dual Token Bucket Three Color Marker Algorithm

Figure 22-11 shows the basic working principle of the dual token bucket three color marker algorithm that is used by the CAR. Figure 22-11 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
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.
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.
If a packet does not obtain the Tp token, this packet is marked red. This type of packets is directly discarded.
22.5.2 Traffic Shaping

The traffic shaping uses the dual token bucket three color marker algorithm that is similar to the algorithm used by the CAR. The buffer queue, however, is added before the Tc token bucket in the algorithm used by the traffic shaping. Figure 22-12 shows the basic working principle of the dual token bucket three color marker algorithm that is used by the traffic shaping.
22 QoS
Figure 22-12 Basic working principle of the algorithm that is used by the 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
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 PBS.
...
CIR
When the buffer queue is empty, the packet is processed as follows:

l l l
If a packet does not obtain the Tp token, this packet is directly discarded. If a packet obtains the Tp and Tc tokens, this packet is directly forwarded. If a packet obtains the Tp token but does not obtain the Tc token, this packet enters the buffer queue.
When the buffer queue is not empty, the packet is processed as follows:
l
If a packet obtains the Tp token but does not obtain the Tc token, this packet directly enters the buffer queue. Otherwise, it is directly discarded. If the packet in the buffer queue obtains the Tc token, the packet is directly forwarded. Otherwise, the packet 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 according to the related congestion avoidance algorithm. In this manner, the forwarding efficiency and bandwidth utilization of the buffer queue are ensured.

Before applying a QoS policy to a specific QoS object, you need to set the QoS policy.
Issue 02 (2009-10-30)
22-17
22 QoS
Table 22-5 Procedure for configuring the QoS Step 1 Operation Remarks
A.12.1 Creating Required. a DS Domain Set the parameters according to the network planning information.
NOTE The E-Line services that are transparently transmitted in point-to-point mode only support matching DSCP packets with PHB service classes. In the default DS domain, however, packets match with PHB service classes based on the C-LAN priority. Hence, you need to configure a new DS domain.
A.12.2 Changing the Ports That Use the DS Domain
Optional. When several applied ports in the same DS domain need to match with PHB service classes based on the packet type, you can set Packet Type to different values for the applied ports.
A.12.3 Creating Required when you need to apply QoS policies other than DS and a Port Policy port shaping for a specific port. Set the parameters according to the network planning information.
A.12.4 Creating Required when you need to perform the CAR or shaping the Traffic operation for a specific flow over the port. Set the parameters according to the network planning information.
A.12.5 Setting the Port That Uses the Port Policy A.12.6 Configuring Port Shaping
Required after you create a port policy.
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. 22.7.1 Networking Diagram The topic describes the networking information about the NEs. 22.7.2 Service Planning The service planning information contains all the parameter information required for configuring the NE data. 22.7.3 Configuration Process This topic describes the procedure for the data configuration.
22 QoS

The topic describes the networking information about the NEs. As shown in Figure 22-13, the Ethernet services on each BTS carry VLAN tags and different types of Ethernet services carry different VLAN priorities. Hence, you need to perform the corresponding QoS operations for each type of Ethernet service based on the VLAN priority. Figure 22-13 Networking diagram
BTS2 VLAN 110 To NE3:3-IFU2-1 To BTS2:1-EM6T-3 To BTS3:1-EM6T-4 To NE2:1-EM6T-1 To NE4:3-IFU2-1 To NE5:4-IFU2-1 NE4 BTS3 VLAN 120 To NE5:3-IFU2-1 To BTS5:1-EM6T-3 To NE3:4-IFU2-1 To NE6:3-IFU2-1 To BTS4:1-EM6T-3 NE3 NE2 BTS1 VLAN 100 BTS4 VLAN 110 NE1 BSC To NE1:3-IFU2-1 To NE3:1-EM6T-1 To BTS1:1-EM6T-3 To NE2:3-IFU2-1 To BTS1:1-EM6F-1
NE6 BTS5 VLAN 120
NE5

QoS (DiffServ)
DS is the basis for QoS. It is recommended that the VLAN priority or DSCP value of the BTS services be allocated by the service type. Then, the transmission network creates the corresponding DS domain according to the allocated VLAN priority or DSCP value. Each Ethernet port involved in the service must use the same DS configuration. In this example, the BTS services are allocated with corresponding VLAN priorities according to the service type, and the NEs allocate the PHB service classes according to the VLAN priority, as provided in Table 22-6. Each Ethernet port involved in the service uses the same DS configuration. Table 22-6 Service class and PHB service class PHB Service Class CS7 CS6
Issue 02 (2009-10-30)
VLAN Priority 7 6
Corresponding Service Type 22-19
22 QoS
PHB Service Class EF
VLAN Priority 5
Corresponding Service Type Real-time voice service and signaling service (R99 conversational and R99 streaming services) Real-time OM and HSDPA services (OM streaming and HSPA streaming services) Non-real-time R99 service (R99 interactive and R99 background services) HSDPA data service (HSPA interactive and background services)
AF4 AF3
4 3
AF2
AF1 BE
1 0
NOTE
During the mapping of the PHB service class, CS7 is not recommended, because CS7 may be used to transmit Ethernet protocol packets or inband DCN packets on the NE.
QoS (Queue Scheduling Mode)

Generally, each Ethernet port involved in the service uses the same queue scheduling mode. Table 22-7 lists the queue scheduling mode used by each Ethernet port involved in the service in this example. Table 22-7 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
22-20
Issue 02 (2009-10-30)
22 QoS
QoS (CAR or Shaping for a Specified Service)

To perform the CAR or shaping processing for a specified service, you need to configure the DS edge node accordingly. In this example, the CAR processing needs to be performed on the DS edge node in the uplink direction (from the BTS to the BSC) of the non-real-time R99 service on each base station (that is, the service with VLAN priority 2). Table 22-8 lists the CAR parameters. Table 22-8 CAR parameters Parameter CIR CBS PIR PBS "Yellow" Packet Processing Mode Value 4096 kbit/s 5120 bytes 8192 kbit/s 10240 bytes Mapped to the EF queue
In this example, the shaping processing needs to be performed in the uplink direction (from the BTS to the BSC) of the real-time OM and HSDPA services on each base station. Table 14 lists the shaping parameters. Table 22-9 Shaping parameters Parameter CIR CBS PIR PBS Value 2048 kbit/s 2560 bytes 4096 kbit/s 5120 bytes
NOTE
The CBS/PBS is in direct proportion to the CIR/PIR. That is, the larger the value of the CBS/PBS, the more the burst packets are permitted. In this example, the values of the CBS and the PBS are set according to the bytes that are transmitted at CIR and PIR during a 10 ms period.
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.
22 QoS
NOTE
When port shaping is not configured, the OptiX RTN 950 automatically performs port shaping according to the bandwidth over the IFUP ports.

Procedure
Step 1 See A.12.1 Creating a DS Domain and create a DS domain. The values for the related parameters that need to be set in the main interface are provided as follows. Parameter Mapping Relation ID Mapping Relation Name Packet Type Value 2 DiffservForBackhaul cvlan
The values for the related parameters that need to be set in the Ingress Mapping Relation tab page are provided as follows. CVLAN 0 1 2 3 4 5 6 7 SVLAN IP DSCP PHB BE AF11 AF21 AF31 AF41 EF CS6 CS7
The values for the related parameters that need to be set in the Egress Mapping Relation tab page are provided as follows. PHB BE AF11
22-22
CVLAN 0 1
SVLAN
IP DSCP
Issue 02 (2009-10-30)
22 QoS
PHB AF21 AF31 AF41 EF CS6 CS7
CVLAN 2 3 4 5 6 7
SVLAN
IP DSCP
NOTE
The AF1 is classified into three sub service classes, namely, AF11, AF12, and AF13, only one of which is valid. In this example, the AF11 is used. It is the same case with the AF2, AF3, and AF4.
The values for the related parameters that need to be set in the Application Port tab page are provided as follows. Paramete r Selected Port Value NE1 3-IFU2-1 1-EM6F-1 NE2 1-EM6T-3 1-EM6T-1 3-IFU2-1 NE3 3-IFU2-1 4-IFU2-1 1-EM6T-1 NE4 3-IFU2-1 1-EM6T-3 1-EM6T-4 NE5 1-EM6T-3 3-IFU2-1 4-IFU2-1 NE6 1-EM6T-3 3-IFU2-1
NOTE
The mapping relation defined in the default DS domain is the same as the mapping relation defined in the DS domain that is created in this step. Therefore, you can skip this step.
Step 2 See A.12.3 Creating a Port Policy and create the port policy.
l
The values for the relevant parameters of NE1 and NE3 are provided as follows. Parameter Policy ID Policy Name Grooming Police After Reloading Value 1 Port_Comm SP (CS7, CS6, and EF) WRR (AF4 to AF1) SP (BE)
Issue 02 (2009-10-30)
22-23
22 QoS
Parameter Policy Weight(%)
Value 5 (AF4) 60 (AF3) 30 (AF2) 5 (AF1)
Bandwidth Limit
Disabled (for all PHB service classes)
The values for the relevant parameters of NE2 and NE5 are provided as follows. Parameter Policy ID Policy Name Grooming Police After Reloading Value 1 Port_Comm SP (CS7, CS6, and EF) WRR (AF4 to AF1) SP (BE) Policy Weight(%) 5 (AF4) 60 (AF3) 30 (AF2) 5 (AF1) Bandwidth Limit Disabled (for all PHB service classes) 2 Port_Car SP (CS7, CS6, and EF) WRR (AF4 to AF1) SP (BE) 5 (AF4) 60 (AF3) 30 (AF2) 5 (AF1) Disabled (for all PHB service classes) 3 Port_Shaping SP (CS7, CS6, and EF) WRR (AF4 to AF1) SP (BE) 5 (AF4) 60 (AF3) 30 (AF2) 5 (AF1) Disabled (for all PHB service classes)
The values for the related parameters of NE4 and NE6 are provided as follows. Parameter Policy ID Policy Name Grooming Police After Reloading Value 1 Port_Car SP (CS7, CS6, and EF) WRR (AF4 to AF1) SP (BE) Policy Weight(%) 5 (AF4) 60 (AF3) 30 (AF2) 5 (AF1) Bandwidth Limit Disabled (for all PHB service classes) 2 Port_Shaping SP (CS7, CS6, and EF) WRR (AF4 to AF1) SP (BE) 5 (AF4) 60 (AF3) 30 (AF2) 5 (AF1) Disabled (for all PHB service classes)
22-24
Issue 02 (2009-10-30)
22 QoS
Step 3 See A.12.4 Creating the Traffic and create the flows for NE2, NE4, NE5, and NE6.
l
Parameters of NE2: The values for the related parameters that need to be set in the main interface are as follows. Parameter Value Port_Car Traffic Classification ID ACL Action 1 Permit Port_Shaping 1 Permit
The values for the related parameters that need to be set in the INGRESS tab page are as follows. Parameter Value Port_Car Match Type Match Value CoS Bandwidth Limit CIR(kbit/s) PIR(kbit/s) CBS(byte) PBS(byte) Handling Mode CVlan priority 2 Enabled 4096 8192 5120 10240 Discard (red) Remark (yellow) Pass (green) Relabeled CoS - (red) EF (yellow) - (green) Port_Shaping CVlan ID 100 Disabled CVlan priority 3
The values for the related parameters that need to be set in the EGRESS tab page are as follows.
Issue 02 (2009-10-30)
22-25
22 QoS
Parameter
Value Port_Car Port_Shaping Enabled 2048 4096 2560 5120
Bandwidth Limit CIR(kbit/s) PIR(kbit/s) CBS(byte) PBS(byte) Parameters of NE4:
Disabled -
The values for the related parameters that need to be set in the main interface are as follows. Parameter Value Port_Car Traffic Classification ID ACL Action 1 Permit Port_Shaping 1 Permit 2 Permit
The values for the related parameters that need to be set in the INGRESS tab page are as follows. Parameter Value Port_Car Match Type Match Value CoS Bandwidth Limit CIR(kbit/s) PIR(kbit/s) CBS(byte) PBS(byte) CVlan priority 2 Enabled 4096 8192 5120 10240 Port_Shaping (Traffic Classification ID=1) CVlan ID 110 Disabled CVlan priority 3 Port_Shaping (Traffic Classification ID=2) CVlan ID 120 Disabled CVlan priority 3
22-26
Issue 02 (2009-10-30)
22 QoS
Parameter
Value Port_Car Port_Shaping (Traffic Classification ID=1) Port_Shaping (Traffic Classification ID=2) -
Handling Mode
Discard (red) Remark (yellow) Pass (green)
Relabeled CoS
- (red) EF (yellow) - (green)
The values for the related parameters that need to be set in the EGRESS tab page are as follows. Parameter Value Port_Car Port_Shaping (Traffic Classification ID=1) Enabled 2048 4096 2560 5120 Port_Shaping (Traffic Classification ID=2) Enabled 2048 4096 2560 5120
Bandwidth Limit CIR(kbit/s) PIR(kbit/s) CBS(byte) PBS(byte) Parameters of NE5:
Disabled -
The values for the related parameters that need to be set in the main interface are as follows. Parameter Value Port_Car Traffic Classification ID ACL Action 1 Permit Port_Shaping 1 Permit
The values for the related parameters that need to be set in the INGRESS tab page are as follows.
Issue 02 (2009-10-30)
22-27
22 QoS
Parameter
Value Port_Car Port_Shaping CVlan ID 130 Disabled CVlan priority 3
Match Type Match Value CoS Bandwidth Limit CIR(kbit/s) PIR(kbit/s) CBS(byte) PBS(byte) Handling Mode
CVlan priority 2 Enabled 4096 8192 5120 10240 Discard (red) Remark (yellow) Pass (green)
Relabeled CoS
- (red) EF (yellow) - (green)
The values for the related parameters that need to be set in the EGRESS tab page are as follows. Parameter Value Port_Car Bandwidth Limit CIR(kbit/s) PIR(kbit/s) CBS(byte) PBS(byte) Parameters of NE6: The values for the related parameters that need to be set in the main interface are as follows. Parameter Value Port_Car Traffic Classification ID 1 Port_Shaping 1 Disabled Port_Shaping Enabled 2048 4096 2560 5120
22-28
Issue 02 (2009-10-30)
22 QoS
Parameter
Value Port_Car Port_Shaping Permit
ACL Action
Permit
The values for the related parameters that need to be set in the INGRESS tab page are as follows. Parameter Value Port_Car Match Type Match Value CoS Bandwidth Limit CIR(kbit/s) PIR(kbit/s) CBS(byte) PBS(byte) Handling Mode CVlan priority 2 Enabled 4096 8192 5120 10240 Discard (red) Remark (yellow) Pass (green) Relabeled CoS - (red) EF (yellow) - (green) Port_Shaping CVlan ID 140 Disabled CVlan priority 3
The values for the related parameters that need to be set in the EGRESS tab page are as follows. Parameter Value Port_Car Bandwidth Limit CIR(kbit/s) PIR(kbit/s) CBS(byte) PBS(byte)
Issue 02 (2009-10-30)
Port_Shaping Enabled 2048 4096 2560 5120

22-29
Disabled -
22 QoS
Step 4 See A.12.5 Setting the Port That Uses the Port Policy and set the ports that use the port policy. l The values for the related parameters of NE1 are provided as follows. Parameter Value Port_Comm Port 3-IFU2-1 1-EM6F-1
l
The values for the related parameters of NE2 are provided as follows. Parameter Value Port_Comm Port 1-EM6T-1 Port_Car 1-EM6T-3 Port_Shaping 3-IFU2-1
The values for the related parameters of NE3 are provided as follows. Parameter Value Port_Comm Port 3-IFU2-1 4-IFU2-1 1-EM6T-1
The values for the related parameters of NE4 are provided as follows. Parameter Value Port_Car Port 1-EM6T-3 1-EM6T-4 Port_Shaping 3-IFU2-1
The values for the related parameters of NE5 are provided as follows. Parameter Value Port_Comm Port 3-IFU2-1 Port_Car 1-EM6T-3 Port_Shaping 4-IFU2-1
The values for the related parameters of NE6 are provided as follows. Parameter Value Port_Car Port 1-EM6T-3
Port_Shaping 3-IFU2-1
Issue 02 (2009-10-30)
22-30
22 QoS
----End

Related Concepts
A.12.1 Creating a DS Domain A.12.3 Creating a Port Policy A.12.4 Creating the Traffic A.12.6 Configuring Port Shaping A.12.7 Querying the Port Policy A.12.8 Querying the DS Domain of a Port

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

None.
22.10 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.
Issue 02 (2009-10-30)
22-31
23 ETH-OAM
23
About This Chapter
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. 23.1 Feature Description ETH-OAM enhances the Ethernet Layer 2 maintenance to strongly support the service continuity verification, service deployment commissioning, and network fault locating. The Ethernet unit provides a complete Ethernet OAM solution according to the ETH-OAM standard specified in IEEE 802.1ag and IEEE 802.3ah. 23.2 Basic Concepts This topic describes the basic concepts that you need to be familiar with before you use the ETHOAM. 23.3 Availability The ETH-OAM feature requires the support of the applicable boards. 23.4 Relation with Other Features The ETH-OAM feature does not affect other Ethernet features. 23.5 Realization Principle The ETH-OAM realizes different OAM operations through different OAM packets. 23.6 Configuration Procedure The configuration procedure of 802.1ag OAM and the configuration procedure of 802.3ah OAM are independent of each other. 23.7 Application Example (802.1ag OAM) This topic describes how to plan and configure the 802.3ag OAM feature by using an example. 23.8 Application Example (802.3ah OAM) This topic describes how to plan and configure 802.3ah OAM by using an example. 23.9 Task Collection The operation tasks related to 802.1ag OAM and the operation tasks related to 802.3ah OAM are independent of each other. 23.10 Relevant Alarms and Events
23 ETH-OAM
When an NE detects an abnormality by using ETH-OAM operations, the NE reports the corresponding alarm. 23.11 FAQs This topic provides the answers to the questions that are frequently raised when the ETH-OAM is used.
23-2
Issue 02 (2009-10-30)
23 ETH-OAM

ETH-OAM enhances the Ethernet Layer 2 maintenance to strongly support the service continuity verification, service deployment commissioning, and network fault locating. The Ethernet unit provides a complete Ethernet OAM solution according to the ETH-OAM standard specified in IEEE 802.1ag and IEEE 802.3ah. The traditional Ethernet maintenance and fault locating method has the following disadvantages:
l
The current frame test method is based on only the encapsulation format where the data encapsulation of the same type is contained. Thus, this test method is not applicable to other encapsulation formats where the data encapsulation of different types is contained. The current port loopback function focuses on all packets at the port. Thus, the loopback cannot be performed for a specific service selectively.
With the continuous development of the Ethernet, carriers focus more on the equipment maintainability. Solutions to OAM of the transmission network are required urgently. Thus, the ETH-OAM is developed. Based on the MAC layer, the Ethernet OAM (ETH-OAM) protocol checks Ethernet links by transmitting OAM protocol packets. This protocol is independent of the transmission medium. The OAM packets are processed only at the MAC layer, having no impact at other layers of the Ethernet. Compared with the traditional Ethernet maintenance and fault locating method, the ETH-OAM has the following advantages:
l
As a low-rate protocol, the ETH-OAM protocol occupies low bandwidth. Thus, this protocol does not affect services carried on the link. The ETH-OAM is not related to the encapsulation format of the Ethernet. Thus, the OAM function between different encapsulation formats can be realized. The ETH-OAM allows the loopback to be performed for a specific service selectively. The ETH-OAM can detect faults in the hardware. The ETH-OAM can detect and locate faults automatically.
l l l
The OptiX RTN 950 provides Ethernet OAM solutions in compliance with IEEE 802.1ag and IEEE 802.3ah. As shown in Figure 23-1, the combination of IEEE 802.1ag and IEEE 802.3ah provides a complete Ethernet OAM solution.
Issue 02 (2009-10-30)
23-3
23 ETH-OAM
Figure 23-1 ETH-OAM solution

IEEE 802.3ah IEEE 802.1ag IEEE 802.3ah
Transmission network
Customer Ethernet equipment Microwave equipment
The IEEE 802.1ag OAM focuses on the maintenance of end-to-end Ethernet links. Based on services, the IEEE 802.1ag OAM realizes 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 in the network. The IEEE 802.1ag OAM realizes the endto-end Ethernet maintenance by performing the CC, LB, and LT tests. The IEEE 802.3ah OAM focuses on the point-to-point Ethernet link maintenance between two directly-connected equipment. The IEEE 802.3ah OAM does not focus on the specific service. It maintains the Ethernet point-to-point link by performing OAM auto-discovery, link performance monitoring, remote loopback, and self-loop test.
23.2 Basic Concepts

This topic describes the basic concepts that you need to be familiar with before you use the ETHOAM. 23.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. 23.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). 23.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.
23-4
Issue 02 (2009-10-30)
23 ETH-OAM
23.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
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.
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
23 ETH-OAM
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 of other NEs 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 23-2 shows the logical diagram of the maintenance domain layers. Figure 23-2 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
ME levels for the user: 7, 6, 5 ME levels for the supplier: 4, 3

23-6

l
23 ETH-OAM
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
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.
23.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 23-1 shows the IEEE 802.1ag ETH-OAM operations and application scenarios. Table 23-1 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. The LB can be used to test the status of the link from the source MEP to any MP in the maintenance domain. Application Scenario
l
Description
l
The unidirectional connectivity is tested. The link status is checked in real time.
LB
The bidirectional connectivity is tested. The fault location or test is singleended. Compared with the continuity test, the loopback test is not a continuous test. Thus, you need to start the test manually each time.
To find which link on the network is faulty, you must use the LB and LT testing methods rather than the CC testing method. By using the LB testing method, you can check whether the link between the local equipment to the destination equipment is faulty, but cannot find the equipment where the fault occurs. By using the LT testing method, you can check whether the link between the local equipment and the
23-7
Issue 02 (2009-10-30)
23 ETH-OAM
Operation Name LT
Explanation 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.
Application Scenario
l
Description destination equipment is faulty. In addition, you can find which segment of the link is faulty.
The problem can be located on site. The fault point can be located. Compared with the LB test, all the MPs on the link under LT test respond to the LTM frames. According to the LTM messages, you can find all the MIPs from the source MEP to the destination MEP.
23.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 23-2 shows the IEEE 802.3ah ETH-OAM operations and application scenarios. Table 23-2 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
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.
The equipment that supports the IEEE 802.3ah OAM protocol is identified. If the autodiscovery fails, the related alarm is reported.
23-8
Issue 02 (2009-10-30)
23 ETH-OAM
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.
l
Description
The service performance of the link is monitored in real time. The link performance within a specific range is precisely analyzed and monitored. 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.
Issue 02 (2009-10-30)
23-9
23 ETH-OAM
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.
l
Description
The problem can be located on site. 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. The loopback on the port and the intra-board loopback can be tested. Once a loop occurs during the networking operation, it is detected and the related alarm is reported.
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.
23.3 Availability
The ETH-OAM feature requires the support of the applicable boards. Table 23-3 Availability of the ETH-OAM Feature Feature ETH-OAM Applicable Board EM6T EM6F Applicable Board Version All the functional versions All the functional versions
23-10
Issue 02 (2009-10-30)
23 ETH-OAM
Feature
Applicable Board IFU2 IFX2
Applicable Board Version All the functional versions All the functional versions

The ETH-OAM feature does not affect other Ethernet features.

The ETH-OAM realizes different OAM operations through different OAM packets. 23.5.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. 23.5.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.
23.5.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 23-3 shows the IEEE 802.1ag OAMPDU.
Issue 02 (2009-10-30)
23-11
23 ETH-OAM
Figure 23-3 IEEE 802.1ag OAMPDU

OAM Mac Destination Address
OAM Mac Source Address Ether Type(VLAN) Ether Type(OAM) Type Length Service-ID VLAN Tag VER OAM Type
OAM Date
Frame Check Sequence
OAM Mac Destination Address: Indicates the broadcast address (in the case of 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 OMA packet types, see Table 23-4. Table 23-4 Mapping between the OAM type values and OMA 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
l l l l l
CC
The CC is used to test the link status unidirectionally. The realization principle is as follows:
23-12
Issue 02 (2009-10-30)
23 ETH-OAM
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 23-4, 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. Figure 23-4 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.
As shown in Figure 23-5, the realization principle of the LB is as follows: 1.

Issue 02 (2009-10-30)
MEP1 transmits the LBM packets to MEP4.

23 ETH-OAM
2.
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.
3.
Figure 23-5 Loopback test diagram
MEP1
MIP2 LBM LBR
MIP3
MEP4
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.
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. 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 23-6, the realization principle of the LT is as follows: 1. 2. 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.
23-14
23 ETH-OAM
3.
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 23-6 LT test diagram
MEP1
1
MIP2 LTM LTR LTM LTR
MEP3
3
NOTE
Only an MEP can initiate or terminate an LT test.
23.5.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 23-7 shows the IEEE 802.3ah OAMPDU.
Issue 02 (2009-10-30)
23-15
23 ETH-OAM
Figure 23-7 IEEE 802.3ah OAMPDU
Octets 6 6 2 1 2 1 42-1496 4
MAC Destination Address MAC Source Address Type Subtype Flags Field Code Data/Pad Field Frame Check Sequence
l l l l l
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 Filed: 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 23-5. Table 23-5 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.
0x02
Variable request
23-16
Issue 02 (2009-10-30)
23 ETH-OAM
Code 0x03 0x04 0x05-0x FD 0xFE
OAMPDU Variable response Loopback control Reserved Organization specific
Usage Responds to one or multiple specific MIB messages. Enables or disables the remote OAM loopback. Reserved. Indicates the selective extended OAMPDU function used by different equipment manufacturers. Reserved.
0xFF
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 23-8, 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 23-6 lists details of OAM configuration bytes.
Issue 02 (2009-10-30)
23-17
23 ETH-OAM
Figure 23-8 Packet format of the information OAMPDU

Octets 1 1 1 2 1 1 2 3 4 Fields Information Type Information Length OAM Version Revision State OAM Configuration OAMPDU Configuration OUI Vendor Specific Information Fixed Values 0x01 0x10 0x01
Octets 6 6 2 1 2 1
Fields Destination Address Source Address Length/Type Subtype Flags Code
Fixed Values 01-80-c2-00-00-02
88-09 0x03
LOCAL INFORMATION TLV
0x00
42-1496 Data/Pad 4 FCS
INFORMATION OAMPDU
1 1 1 2 1 1 2 3 4
Information Type Information Length OAM Version Revision State OAM Configuration OAMPDU Configuration OUI Vendor Specific Information
0x02 0x10 0x01
REMOTE INFORMATION TLV

1 1 1 2 Information Type Information Length OUI Organization Specific Value 0xFE
ORGANIZATION SPECIFIC INFORMATION TLV
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.
23-18
23 ETH-OAM
Table 23-6 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
Variable retrieval
When this bit is set to 1, it indicates that the data terminal equipment (DTE) supports the transmission of the variable response OAMPDU. When this bit is set to 0, it indicates that the DTE does not support the transmission of the variable response OAMPDU. 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. When this bit is set to 0, it indicates that the DTE does not support the monitoring on bit error performance of links.
Link events
Issue 02 (2009-10-30)
23-19
23 ETH-OAM
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. When this bit is set to 0, it indicates that the DTE does not support the remote loopback. 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. 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. When this bit is set to 1, it indicates that the OAM mode of the DTE is set to Active. 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 23-7.
Unidirectional support
OAM mode
23-20
Issue 02 (2009-10-30)
23 ETH-OAM
Table 23-7 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 23-9, 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 (2009-10-30)
23-21
23 ETH-OAM
Figure 23-9 Packet format of the event notification OAMPDU

Octets 2 1 1 2 8 8 8 8 4 Fields Sequence Number SEQUENCE NUMBER Event Type Event Length Event Time Stamp Errored Svmbol Window Errored Svmbol Threshol Errored Svmbol Error Running Total Event Running Total Fixed Values
0x01 0x28
Octets 6 6 2 1 2 1
Fields Destination Address Source Address Length/Type Subtype Flags Code
Fixed Values 01-80-c2-00-00-02
88-09 0x03
ERRORED SYMBOL PERIOD EVENT 1 Event Type 0x02 1 Event Length 0x1A 2 Event Time Stamp 2 Errored Frame Window 4 Errored Frame Threshol 4 Errored Frames 8 Error Running Total 4 Event Running Total 1 1 2 4 4 4 8 4 ERRORED FRAME ENENT Event Type 0x03 Event Length 0x1 Event Time Stamp C Errored Frame Window Errored Frame Threshol Errored Frames Error Running Total Event Running Total
0x01
42-1496 Data/Pad 4 FCS
ENENT NOTIFICATION OAMPDU
ERRORED FRAME PERIOD EVENT 1 Event Type 0x04 1 Event Length 0x12 2 Event Time Stamp 2 Err.Fr.Sec.Sum.Window 2 Err.Fr.Sec.Sum.Threshol 2 Err.Fr.Sec.Summary 4 Error Running Total 4 Event Running Total ERRORED FRAME SECONDS SUMMARY 1 Event Type 0xF 1 Event Length E 3 OUI x Organization Specific Value ORGANIZATION SPECIFIC EVENT
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.
23-22
Issue 02 (2009-10-30)

NOTE
23 ETH-OAM
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 l 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. 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. 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 23-10, 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 23-10 Packet format of the loopback control OAMPDU
Octets 6 6 2 1 2 1 1+41 4 Fields Destination Address Source Address Length/Type Subtype Flags Code Data/Pad FCS 0x04 88-09 0x03 Octets 1 Fields Remote Loopback Command Fixed Values 0x01 Fixed Values 01-80-c2-00-00-02
ENABLE REMOTE LOOPBACK COMMAND

1 Remote Loopback Command 0x02
LOOPBACK CONTROL OAMPDU
DISABLE REMOTE LOOPBACK COMMAND
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 (2009-10-30)
23 ETH-OAM
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.

The configuration procedure of 802.1ag OAM and the configuration procedure of 802.3ah OAM are independent of each other. 23.6.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. 23.6.2 IEEE 802.3ah OAM When you use the 802.1ag OAM function, you can perform appropriate OAM operations as required.
23.6.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.
23-24
Issue 02 (2009-10-30)
23 ETH-OAM
Table 23-8 Flow for configuring the 802.1ag OAM service Step 1 Operation A.13.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. 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.
Issue 02 (2009-10-30)
23-25
23 ETH-OAM
Step 2
Operation A.13.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. Set Maintenance Association Name to the same value for the NEs for which OAM operations are performed. Set Relevant Service to the same service for the NEs for which OAM operations are performed.
23-26
Issue 02 (2009-10-30)
23 ETH-OAM
Step 3
Operation A.13.3 Creating an MEP Point
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. Set Board and Port to the board and port where the OAM operation is started or terminated. Set VLAN to a VLAN. The settings of the source and sink MEPs must be the same. In the same MA, the value of MP ID must be unique. 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. If the sink maintenance point is identified based on the MP ID, CC Status must be set to Active.
Issue 02 (2009-10-30)
23-27
23 ETH-OAM
Step 4
Operation Creating Remote MEPs in an MA
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. Set Maintenance Association Name to the value of Maintenance Association Name that is set in the second step. If other MEPs may initiate OAM operations to an MEP in the same MA, set the other MEPs to be the remote MEPs.
A.13.4 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. Set Board and Port to the board and port through which the Ethernet service passes. In the same MA, the value of MP ID must be unique.
A.13.5 Performing a CC Test A.13.6 Performing an LB Test A.13.7 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.
23.6.2 IEEE 802.3ah OAM

When you use the 802.1ag OAM function, you can perform appropriate OAM operations as required.
23 ETH-OAM
Table 23-9 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. Set OAM Working Mode to Active for the NE that starts the discovery.
Link Performance Monitoring
A.14.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.14.3 Modifying the OAM Error Frame Monitoring Threshold
Remote Loopback
A.14.4 Performing Remote Loopback
Self-Loop Test
A.14.5 Enabling Self-Loop Detection
Issue 02 (2009-10-30)
23-29
23 ETH-OAM
23.7 Application Example (802.1ag OAM)

This topic describes how to plan and configure the 802.3ag OAM feature by using an example. 23.7.1 Networking Diagram The topic describes the networking information of the NEs. 23.7.2 Service Planning The service planning information contains all the parameter information required for configuring the NE data. 23.7.3 Configuration Process This topic describes the procedure for the data configuration.

The topic describes the networking information of the NEs. Figure 23-11 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.
Figure 23-11 Networking diagram for configuring VLAN-based E-Line services

NodeB A VLAN 100-109
3-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
23-30
Issue 02 (2009-10-30)
23 ETH-OAM

Planning Information About the MP

Figure 23-12 shows the planning information about the MP. Figure 23-12 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 23-10, Table 23-11, Table 23-12, Table 23-14, and Table 23-15 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 23-10 Information about the MD Parameter Maintenance Domain Name Protection Level NE1 MD1 4 NE2 MD1 4 NE3 MD1 4
Table 23-11 Information about the MA Paramete r Maintenan ce Domain Name

Issue 02 (2009-10-30)
NE1 MD1 MD1
NE2 MD1 MD1
NE3 MD1 MD1
23-31
23 ETH-OAM
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 23-12 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 23-13 Information about the remote MEP Parameter Maintenance Domain Name Maintenance Association Name NE1 MD1 MA1 MD1 MA2 NE3 MD1 MA1 MD1 MA2
23-32
Issue 02 (2009-10-30)
23 ETH-OAM
Parameter Remote Maintenance Point ID
NE1 2 4
NE3 1 3
Table 23-14 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 23-15 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.13.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
Issue 02 (2009-10-30)
NE2 MD1 4
NE3 MD1 4
MD1 4
23-33
23 ETH-OAM
Step 2 See A.13.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 (ms)
Step 3 See A.13.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 MP ID Direction CC Status
23-34
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

Issue 02 (2009-10-30)
23 ETH-OAM
Step 4 See 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.13.4 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
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
The values for the relevant parameters of NE3 are provided as follows. Parameter Maintenance Domain Name Board Value Range MD1 4-IFU2
Issue 02 (2009-10-30)
23 ETH-OAM
Parameter Port MP ID
Value Range 4-IFU2-1(port-1) 8
Step 6 See A.13.7 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 Sink Maintenance Point ID Value Range MD1 MA1 1 2
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 Sink 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
23.8 Application Example (802.3ah OAM)

This topic describes how to plan and configure 802.3ah OAM by using an example. 23.8.1 Networking Diagram The topic describes the networking information of the NEs. 23.8.2 Service Planning The service planning information contains all the parameter information required for configuring the NE data. 23.8.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.
23 ETH-OAM

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 23-13, 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 23-13 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 23-16 provides the parameters of the OAM. Table 23-16 Parameters of the OAM Parameter Port OAM Protocol Enabled
Issue 02 (2009-10-30)
NE1 1-EM6T-1(Port-1) Enabled
NE2 1-EM6T-1(Port-1) Enabled

23-37
23 ETH-OAM
Parameter OAM Working Mode Link Event Notification
NE1 Active Enabled
NE2 Active Enabled
Error Frame Monitoring Information of the OAM

Table 23-17 provides the error frame monitoring information of the OAM. Table 23-17 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) Error Frame Signal Periodic Monitor Window(s) Error Frame Signal Periodic Monitor Threshold(s) NE1 1-EM6T-1(Port-1) 2000 2 2976 2 120 2 2 2 NE2 1-EM6T-1(Port-1) 2000 2 2976 2 120 2 2 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.14.1 Enabling the OAM Auto-Discovery Function and enable the OAM auto-discovery function.
23 ETH-OAM
The values for the related parameters are provided as follows. Parameter Enable OAM Protocol OAM Working Mode Value Range Enabled Active
Step 2 See A.14.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.14.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) Error Frame Signal Periodic Monitor Window(Entries) Error Frame Signal Periodic Monitor Threshold(Entries) Value Range 1-EM6T-1(Port-1) 2000 2 2976 2 120 2 2 2
----End

The operation tasks related to 802.1ag OAM and the operation tasks related to 802.3ah OAM are independent of each other. 23.9.1 Task Collection(802.1ag OAM) This topic provides the hyperlinks of the operation tasks regarding 802.1ag OAM.
23 ETH-OAM
23.9.2 Task Collection (802.3ah OAM) This topic provides the hyperlinks of the operation tasks regarding 802.3ah OAM.
23.9.1 Task Collection(802.1ag OAM)

This topic provides the hyperlinks of the operation tasks regarding 802.1ag OAM.
Related Concepts
A.13.1 Creating an MD A.13.2 Creating an MA A.13.3 Creating an MEP Point A.13.4 Creating an MIP A.13.5 Performing a CC Test A.13.6 Performing an LB Test A.13.7 Performing an LT Test
23.9.2 Task Collection (802.3ah OAM)

This topic provides the hyperlinks of the operation tasks regarding 802.3ah OAM.
Related Concepts
A.14.1 Enabling the OAM Auto-Discovery Function A.14.2 Enabling the Link Event Notification A.14.3 Modifying the OAM Error Frame Monitoring Threshold A.14.4 Performing Remote Loopback A.14.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.
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.
ETH_CFM_RDI
23-40
23 ETH-OAM
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.
ETH_EFM_Discover 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.
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_Fault 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.
23.11 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.
Issue 02 (2009-10-30)
23-41
24
About This Chapter
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. 24.1 Feature Description The synchronous Ethernet is a clock frequency synchronization technology of the Ethernet physical layer. The synchronous Ethernet can directly extract the clock signal from the serial bit stream on the Ethernet link and transmit data by using the clock signal to realize the synchronization and transfer of the clock signal. 24.2 Availability The synchronous Ethernet feature requires the support of the applicable boards. 24.3 Relation with Other Features The synchronous Ethernet feature does not affect the other features. 24.4 Realization Principle The realization of the synchronous Ethernet feature complies with ITU-T G.8261 and ITU-T G. 8262. 24.5 Configuration Procedure By default, the NEs consider that all the Ethernet links provide the clock signals. Hence, you need to configure the clock source and relevant information for the NEs that use the synchronous Ethernet clock. 24.6 Application Example This topic describes how to plan and configure the synchronous Ethernet feature by using an example. 24.7 Task Collection This topic provides the hyperlinks of the operation tasks regarding the synchronous Ethernet feature. 24.8 Relevant Alarms and Events When the Ethernet link provides the clock source and an anomaly occurs, the NE reports the corresponding alarm. 24.9 FAQs
This topic provides the answers to the questions that are frequently asked when the synchronous Ethernet is used.
24-2
Issue 02 (2009-10-30)

The synchronous Ethernet is a clock frequency synchronization technology of the Ethernet physical layer. The synchronous Ethernet can directly extract the clock signal from the serial bit stream on the Ethernet link and transmit data by using the clock signal to realize the synchronization and transfer of the clock signal.
Application of the Synchronous Ethernet

As shown in Figure 24-1, several sets of the OptiX RTN 950 form the synchronous Ethernet. The synchronous Ethernet provided by the microwave transmission equipment transfers the clock information between the RNC equipment and NodeB. Figure 24-1 Application of the Synchronous Ethernet
FE NodeB
NE2
NE1 FE/GE
FE
RNC
NodeB
Ethernet clock signal Ethernet link
Performance of the Synchronous Ethernet

l l
The synchronous Ethernet complies with ITU-T G.8261 and ITU-T G.8262. The clock signal recovered by the synchronous Ethernet meets the requirement of 50 ppb frequency accuracy.
24.2 Availability
The synchronous Ethernet feature requires the support of the applicable boards. Table 24-1 Availability of the synchronous Ethernet feature Feature synchronous Ethernet Applicable Board EM6T EM6F Applicable Board Version All the functional versions All the functional versions
Issue 02 (2009-10-30)
24-3

The synchronous Ethernet feature does not affect the other features.

The realization of the synchronous Ethernet feature complies with ITU-T G.8261 and ITU-T G. 8262. As shown in Figure 24-2, the synchronous Ethernet function of the OptiX RTN 950 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.
2.
When the Ethernet interface is the clock source of the local NE that outputs clock signals to the downstream equipment: 1. 2. The system clock module sends a highly precise system clock to the Ethernet interface of the NE. The PHY component of the Ethernet interface sends the clock through the code stream in the Ethernet link.
Figure 24-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
24-4
Issue 02 (2009-10-30)

By default, the NEs consider that all the Ethernet links provide the clock signals. Hence, you need to configure the clock source and relevant information for the NEs that use the synchronous Ethernet clock. Table 24-2 Procedure for configuring the synchronous Ethernet Step 1 Operation A.6.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.
24.6 Application Example

This topic describes how to plan and configure the synchronous Ethernet feature by using an example. 24.6.1 Networking Diagram This topic describes the networking information about the NEs. 24.6.2 Service Planning The service planning information contains the information about all the parameters required for configuring the NE data. 24.6.3 Configuration Process This topic describes the procedure for the data configuration.

This topic describes the networking information about the NEs. Based on Configuration Example (Radio Links on the Hybrid Microwave Chain Network), configure the synchronous Ethernet clock according to the clock synchronization requirements. As shown in Figure 24-3, the relevant networking information is as follow:
l
The microwave transmission network is synchronized with the clock of the BSC through a link aggregation group consisting of two GE links. The clock synchronization signal is transmitted to the BTS through the FE signal. All the BTSs and NEs support the synchronous Ethernet function.
l l
Issue 02 (2009-10-30)
24-5
l
The radio links between NE1 and NE2, between NE3 and NE4, and between NE3 and NE5 are configured with the 1+1 protection, whereas the other radio links are configured with the 1+0 non-protection.
Figure 24-3 Networking diagram of the synchronous Ethernet

3-IFU2-1(to NE3) 5-IFU2-1(to NE3) 1-EM6T-5(to BTS2) 1-EM6T-6(to BTS3) 6-IFU2-1(to NE4) 5-IFU2-1(to NE4) 3-IFU2-1(to NE5) 4-IFU2-1(to NE5) 1-EM6T-1(to NE2)
FE BTS2 FE BTS3 NE4
3-IFU2-1(to NE2) 5-IFU2-1(to NE2) 1-EM6F-1(to BSC) 1-EM6F-2(to BSC)
GE FE NE3 FE NE2
3-IFU2-1(to NE1) 5-IFU2-1(to NE1) 1-EM6T-1(to NE3) 1-EM6T-5(to BTS1)
GE
NE1 BTS1
BSC
FE NE6
3-IFU2-1(to NE5) 1-EM6T-5(to BTS5)
NE5 BTS5
4-IFU2-1(to NE3) 6-IFU2-1(to NE3) 5-IFU2-1(to NE6) 1-EM6T-5(to BTS4)
BTS4

Clock Source Information

According to Clock Synchronization Policy, Figure 24-4 shows the clock source information. Figure 24-4 Networking diagram (clock for a Hybrid microwave chain network)
3-IFU2-1/ 5-IFU2-1 Internal GE NE4 NE3 NE2 GE NE1 1-EM6F-1/ 1-EM6F-2/ Internal BSC
NE6 3-IFU2-1/ Internal
NE5 4-IFU2-1/ 6-IFU2-1 Internal Clock
1-EM6T-1/ 3-IFU2-1/ Internal 5-IFU2-1 Internal
24-6
Issue 02 (2009-10-30)

NOTE
Separately configure the Ethernet clock source for each link in the LAG.
Clock Protection
In this example, a chain network is set up. Thus, only the clock source protection based on priorities is needed, whereas the SSM or extended SSM protection need not be configured.
Clock Synchronization Policy for a Base Station

In this example, the radio transmission network is synchronized with the BSC through the GE interface, and transmits the timing reference signal to the base station through the FE interface.

Procedure
Step 1 See A.6.1 Configuring the Clock Sources and configure the clock sources. The values for the related parameters are provided as follows. Paramete r Clock Source Value NE1 1-EM6F-1 1-EM6F-2 Internal Clock Source NE2 3-IFU2-1 5-IFU2-1 Internal Clock Source NE3 1-EM6F-1 Internal Clock Source NE4 3-IFU2-1 5-IFU2-1 Internal Clock Source NE5 4-IFU2-1 6-IFU2-1 Internal Clock Source NE6 3-IFU2-1 Internal Clock Source
Step 2 See A.6.9 Querying the Clock Synchronization Status and query the clock synchronization status of the NEs. NE Working Mode of all the NEs should be Tracing Mode. ----End

This topic provides the hyperlinks of the operation tasks regarding the synchronous Ethernet feature.
Related Concepts
A.6.1 Configuring the Clock Sources A.6.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
SYNC_C_LOS The SYNC_C_LOS alarm indicates that the class of the synchronization source is lost. 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.
24.9 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.
24-8
Issue 02 (2009-10-30)
25
About This Chapter
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. 25.1 Feature Description The RMON feature is based on the management information base (MIB) in the architecture of the simple network management protocol (SNMP). The RMON defines the method of managing Ethernet performance. Through the RMON function, you can monitor the performance of the Ethernet port as you monitor the performance of the SDH or PDH port. 25.2 Basic Concepts This topic describes the basic concepts that you need to be familiar with before you use the RMON feature. 25.3 Availability The RMON feature requires the support of the applicable boards. 25.4 Relation with Other Features RMON does not affect other features. 25.5 Realization Principle 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. 25.6 Configuration Procedure When applying the RMON, you need to perform different operations as required. 25.7 Configuration Example By using an example, this topic describes how to plan and configure the synchronous Ethernet according to the network conditions. 25.8 Task Collection This topic provides the hyperlinks of the operation tasks regarding the relevant feature. 25.9 Relevant Alarms and Events
Issue 02 (2009-10-30)
25-1
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. 25.10 FAQs This topic provides the answers to the questions that are frequently raised when the synchronous Ethernet is adopted.
25-2
Issue 02 (2009-10-30)

The RMON feature is based on the management information base (MIB) in the architecture of the simple network management protocol (SNMP). The RMON defines the method of managing Ethernet performance. Through the RMON function, you can monitor the performance of the Ethernet port as you monitor the performance of the SDH or PDH port. In the case of the Ethernet port of the transmission product, the port performance needs to be measured and the port data needs to be managed. In the case of the traditional SDH performance data management method, a report period is pre-set and the statistics of the Ethernet ports are reported periodically. This method has the following disadvantages:
l l
The communication load is increased, which affects normal management operations. No history performance data is provided, which brings difficulty to analysis on user services. No performance threshold-crossing alarm is supported.
As the network is becoming more and more complex, a method of managing network sections is required. Thus, the RMON emerges. To manage Ethernet ports, the RMON defines a serial of statistic formats and functions to realize data exchange between the control stations and detection stations that comply with the RMON standards. Compared with the traditional performance data management method, the RMON has the following advantages:
l
All statistics data is saved at the agent and the out-of-service operation on the NMS is supported. The RMON can count the port data, set and query the control information, and analyze the performance of the connected Ethernet segments. In addition, the RMON can save the history performance data and NMS can query the statistics of a board only when required. In this manner, less data traffic for managing the network is required. The RMON supports flexible performance alarms. The alarms and performance events related to changes in network performance are reported to the NMS, which facilitates management of a network. Multiple management stations are supported.
25.2 Basic Concepts

This topic describes the basic concepts that you need to be familiar with before you use the RMON feature. 25.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. 25.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.
25.2.3 List of RMON Alarm Entries The RMON alarm entries refer to the table entries in the RMON alarm group. 25.2.4 List of RMON Performance Entries The RMON performance entries refer to the table entries in the RMON statistics group or history group.
25.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
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.
25.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.
25-4
Issue 02 (2009-10-30)
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 25.2.4 List of RMON Performance Entries.
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 25.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.
Monitored object This specifies the port on which performance data is collected. You can set monitored objects for each history table type.
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
History table type

Issue 02 (2009-10-30)
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
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.
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.
25.2.3 List of RMON Alarm Entries

The RMON alarm entries refer to the table entries in the RMON alarm group. Table 25-1 List of RMON alarm entries Alarm Name ETHDROP ETHEXCCO L ETHLATECO L RXBBAD TXDEFFRM 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. 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. Source EM6T, EM6F, IFU2, and IFX2
ETHUNDER ETHOVER ETHFRG
25-6
Issue 02 (2009-10-30)
Alarm Name ETHJAB
Description The number of received errored oversized packets crosses the threshold. The number of received collisions crosses the threshold. The number of frames that have FCS check errors crosses the threshold.
Source
ETHCOL ETHFCS
25.2.4 List of RMON Performance Entries

The RMON performance entries refer to the table entries in the RMON statistics group or history group. Table 25-2 List of RMON performance entries Category of Performa nce Entries Basic performanc e Name of a Performance Entry Source
Packets received (packets) Drop events (times) Bytes received (bytes) Oversized packets received (packets) Undersized packets received (packets) Multicast packets received (packets) Broadcast packets received (packets) Fragments received (packets) Jabbers received (packets) Collisions (times)
EM6T, EM6F, IFU2, and IFX2
Extended performanc e
Unicast packets transmitted (packets) Pause frames received (frames) Pause frames transmitted (frames) FCS errored frames (frames) Good bytes received (bytes)
Issue 02 (2009-10-30)
25-7
Category of Performa nce Entries
Name of a Performance Entry
Source
Good bytes transmitted (bytes) Bad bytes received (bytes) Unicast packets received (packets) Multicast packets transmitted (packets) Broadcast packets transmitted (packets) Rate of good full-frame bytes received (bytes) Rate of good full-frame bytes transmitted (bytes) Good full-frame bytes received (bytes) Good full-frame bytes transmitted (bytes) Late collisions (times) Frames unsuccessfully transmitted after successive collisions (frames) Delayed frames (frames)
25.3 Availability
The RMON feature requires the support of the applicable boards. Table 25-3 Availability of the RMON feature Feature RMON Applicable Board EM6T EM6F IFU2 IFX2 Applicable Board Version All the functional versions All the functional versions All the functional versions All the functional versions
25-8
Issue 02 (2009-10-30)

RMON does not affect other features.

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 l
If the maintenance engineer clicks Start, the RMON agent does not reset the performance counting register. 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.
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.

When applying the RMON, you need to perform different operations as required. Table 25-4 Procedure of configuring the RMON Step 1 Operation A.15.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. Set Sampling Period as required. If you need to browse over 10 performance events, set Display Mode to List.
25-10
Issue 02 (2009-10-30)
Step 1
Operation A.15.4 Browsing the Performance Data in the History Group of an Ethernet Port
Description Required if the history performance events of the Ethernet port need to be browsed.
l
Select the Ethernet port, performance events, and the start/end time of browsing period for the browsing operation. Set History Table Type as required. If you need to browse over 10 performance events, set Display Mode to List.
A.15.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.15.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. 25.7.1 Networking Diagram The topic describes the networking information about the NEs. 25.7.2 Troubleshooting Analysis This topic describes the basic thoughts when you use the RMON function to rectify Ethernet faults. 25.7.3 Troubleshooting Flow This topic describes how to rectify service faults.

The topic describes the networking information about the NEs. As shown in Figure 25-1, 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 25-1 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
25.7.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. 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
25.7.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. 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. The traffic transmitted from 4-IFU2-1 on NE2 is almost equal to the traffic received at 4IFU2-1 on the opposite NE1. The traffic transmitted from 4-IFU2-1 on NE1 is almost equal to the traffic received at 1EM6F-5 on NE1. 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 l
The devices at both ends work in different modes. A hardware fault occurs at the local end. 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 Setting the General Attributes of Ethernet Interfaces 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 Setting the General Attributes of Ethernet Interfaces in the Configuration Guide.
Step 3 See the Alarms and Performance Events References for handling the fault. 1.
2.
----End

Related Concepts
A.15.1 Browsing the Performance Data in the Statistics Group of an Ethernet Port A.15.2 Configuring an Alarm Group for an Ethernet Port A.15.3 Configuring a History Control Group A.15.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.
RMON Performance Value Above the Upper Limit This abnormal event indicates that the current RMON performance value is higher than the preset upper limit.
25.10 FAQs
This topic provides the answers to the questions that are frequently raised when the synchronous Ethernet 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.
Analyzing the transmission and receiving of data packets at each port

25-14
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.
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.
Issue 02 (2009-10-30)
25-15
A Task Collection
Task Collection
This task collection contains all the network management system (NMS) operation tasks related to the product features. A.1 Managing NEs Before you configure NEs, ensure that the NEs can be managed on the NMS. A.2 Managing Communications To manage the NE by the NMS, ensure that the DCN communication is normal. A.3 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 the MSP The OptiX RTN 950 supports the linear MSP. A.5 Managing TDM Services The TDM services involve the SDH service and the PDH service. A.6 Managing the Clock To ensure the clock synchronization between transmission nodes on a transport network, you need to manage the NE clock. A.7 Managing the ERPS The Ethernet ring protection switching (ERPS) on the FE/GE ring or Hybrid radio ring can be configured to protect the Ethernet service. A.8 Managing the MSTP The OptiX RTN 950 supports only the MSTP that generates the CIST. A.9 Managing the IGMP Snooping If the multicast router exists on a network, the bridge can enable the IGMP Snooping protocol to realize the multicast function with the operation of the router. A.10 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.11 LPT Configuration
Issue 02 (2009-10-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. A-1
A Task Collection
If a hybrid radio link is faulty, the Ethernet port related to the hybrid radio link is automatically disabled through the LPT function. A.12 Managing the QoS By managing the QoS, you can provide the services of different levels for different service types. A.13 Using the IEEE 802.1ag OAM By using the 802.1ag OAM, you can maintain Ethernet services in an end-to-end manner. A.14 Using the IEEE 802.3ah OAM By using the IEEE 802.1ag OAM, you can maintain the point-to-point Ethernet links. A.15 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-2
Issue 02 (2009-10-30)
A Task Collection
A.1 Managing NEs

Before you configure NEs, ensure that the NEs can be managed on the NMS. A.1.1 Creating NEs by Using the Search Method The 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.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.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.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.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.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.7 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.8 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 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
A Task Collection
Procedure
Step 1 On the Main Topology, choose File > Discovery > NE. Step 2 Optional: 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.
NOTE
l l
When Address Type is set to NSAP Address, ensure that the U2000 is installed with the OSI protocol stack software. 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 3 Optional: Repeat Step 2 to add several search domains. Step 4 Select Search for NE in the Search for NE dialog box.
NOTE
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. If Create NE after search is selected, you need to specify NE User and Password.
Step 5 Click Start Search, and then the Auto Discovery dialog box is displayed. After the search is complete, all the NEs that are found are displayed in the Result list. Step 6 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 7 Optional: Repeat Step 6 to create other NEs that are not created. ----End
A-4 Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 02 (2009-10-30)
A Task Collection
Related References
B.1.1 Parameter Description: NE Searching

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.
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 View, right-click New > NE. The Add Object dialog box is displayed. Step 2 Choose RTN Series > OptiX RTN 950 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 (2009-10-30)
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.2 Parameter Description: NE Creation
A.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 Task Collection
Prerequisite
You must be an NM user with NE operator authority or higher.

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. 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.
----End
Issue 02 (2009-10-30)
A-7
A Task Collection
A.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

U2000
Procedure
Step 1 In the Main Topology, right-click the NE whose ID needs to be modified. Step 2 Choose Object Attributes, and then the Object Attributes 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, and then 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
Related References
B.1.3 Parameter Description: NE Attribute_NE ID Change
A.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
A Task Collection
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 Object 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.
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.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. 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 When you need to synchronize the NE time with the NMS time, set the time synchronization mode and the related parameters.
A Task Collection
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 l
When you need to synchronize the NE time with the NMS time, set Synchronous Mode to NM. 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 5 When you need to synchronize the NE time with the time on the NTP server, set the time synchronization mode and the related parameters. 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.
A-10
Issue 02 (2009-10-30)
A Task Collection
b.
Configure the parameters related to the NTP server.
c. d. 6. a. b. c. d. ----End
Click Apply. Close the dialog box that is displayed indicating the operation result. Select the NE to be copied, right-click, and then choose Copy Standard NTP Server. 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.
Optional: Copy the configuration of the upper-layer NTP server.
Related References
B.1.4 Parameter Description: NE Time Synchronization
Issue 02 (2009-10-30)
A-11
A Task Collection
A.1.7 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. 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.
A-12
Issue 02 (2009-10-30)
A Task Collection
Step 5 After the related parameters are configured, click OK. ----End
Related References
Parameter Description: Standard NTP Key Management
A.1.8 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 On the Main Topology, choose Configuration > NE Batch Configuration > NE Time Localization Management.
A Task Collection
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.5 Parameter Description: Localization Management of the NE Time
A.2 Managing Communications

To manage the NE by the NMS, ensure that the DCN communication is normal. A.2.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.2.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.2.3 Configuring the Extended ECC When there is no DCC between two or more NEs, connect the Ethernet NM ports or NE cascading ports on the system control unit of the NEs to realize communication through the extended ECC. A.2.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.2.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.2.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.2.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.2.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 950 is L1.
A Task Collection
A.2.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.2.10 Setting the VLAN ID and Bandwidth Used by an Inband DCN 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.2.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.2.12 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.2.13 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.2.14 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.

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. When you configure multiple parameters, click Apply respectively. ----End
Related References
B.3.1 Parameter Description: NE Communication Parameter Setting
A Task Collection

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: Set the attributes of the DCC. 1. 2. Click Create. Then, the Create dialog box is displayed. Set the attributes of the DCC.
3.
Click OK.
Step 4 Optional: Change the enable status of the DCC. 1. 2. 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.
Step 5 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.
----End
Related References
B.3.2 Parameter Description: DCC Management_DCC Rate Configuration
A Task Collection

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

U2000
Procedure
Step 1 In the NE Explorer, select the NE, and then choose Communication > ECC Management from the Function Tree. Step 2 Set the ECC Extended Mode. Step 3 Set other parameters when the ECC extended mode is set to the specified mode.
Step 4 Click Apply. A dialog box is displayed indicating that this operation will reset the communication between NEs. Step 5 Click OK. ----End
Related References
B.3.4 Parameter Description: ECC Management_Ethernet Port Extended ECC
A.2.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
A Task Collection
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.
Step 5 Click OK. ----End
Related References
B.3.3 Parameter Description: DCC Management_DCC Transparent Transmission Management

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.
A Task Collection
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.
Step 5 Click OK. Close the dialog box that is displayed. ----End
Related References
B.3.7 Parameter Description: IP Protocol Stack Management_IP Route Management Creation

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. Then, close the dialog box that is displayed. ----End
Related References
B.3.8 Parameter Description: IP Protocol Stack Management_OSPF Parameter Settings
A.2.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 Task Collection
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
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 950 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. 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.3.9 Parameter Description: OSI Management_Network Layer Parameter
A Task Collection

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.
Step 5 Click OK. Step 6 Configure the attributes of the OSI tunnel according to the network planning.
Step 7 Click Apply. ----End

A Task Collection
Related References
B.3.11 Parameter Description: OSI Management_OSI Tunnel
A.2.10 Setting the VLAN ID and Bandwidth Used by an Inband DCN

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.
Related References
B.3.12 Parameter Description: DCN Management_Bandwidth Management
A.2.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
A Task Collection
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. Step 6 Select IF. Step 7 Configure the enable status of the inband DCN function on ports.
Related References
B.3.13 Parameter Description: DCN Management_Port Setting

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

U2000
Issue 02 (2009-10-30)
A-23
A Task Collection
Procedure
Step 1 In the NE Explorer, select the NE from the Object Tree and then choose Communication > NE ECC Link Management from the Function Tree. Step 2 Check whether the ECC route and related parameters are set correctly in NE ECC Link Management List. ----End
Related References
B.3.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.3.6 Parameter Description: IP Protocol Stack Management_IP Route Management
A.2.14 Querying OSI Routes

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

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.3.10 Parameter Description: OSI Management_Routing Table
A.3 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.3.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.3.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.3.3 Setting the Hybrid/AM Attributes of the XPIC Hybrid Radio Link After the XPIC protection group is created, you need to configure the Hybrid/AM attributes of the XPIC Hybrid radio link according to the planned values. A.3.4 Configuring the IF/ODU Information of a Radio Link By configuring the IF/ODU information of a radio link, you can configure the IF/ODU information that is frequently used by the SDH/PDH radio link based on each radio link. A.3.5 Setting the Hybrid/AM Attribute By configuring the Hybrid/AM attribute, you can set the working mode of the Hybrid IF boards. A.3.6 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.3.7 Setting IF Attributes In the case of different IF boards, different parameters need to be set. A.3.8 Configuring the ATPC Function To configure the ATPC function, set the ATPC attributes of the IF board.
A Task Collection
A.3.9 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.3.10 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.3.11 Querying the ATPC Adjustment Records By querying the ATPC adjustment records, you can be familiar with the running status of the ATPC function. A.3.12 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.3.13 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.3.14 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.3.15 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.3.16 IF 1+1 Protection Switching You can perform external switching on the IF 1+1 protection by performing IF 1+1 protection switching. A.3.17 IF N+1 Protection Switching You can perform external switching on the IF N+1 protection by performing IF N+1 protection switching. A.3.18 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.3.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. The IF boards of an IF 1+1 FD/SD protection group must be configured in two paired slots.

U2000
A Task Collection
Background Information
When a 1+0 service is converted into a 1+1 service 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 Apply, and then close the dialog box that is displayed indicating the operation result. ----End
Related References
B.4.5 Parameter: IF 1+1 Protection_Create
A.3.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 IFX2 boards and the ODUs to which the IFX2 boards are connected must be added on the NE Panel.

U2000
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Link Configuration from the Function Tree.
A Task Collection
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.4.1 Parameter Description: Link Configuration_XPIC Workgroup_Creation
A.3.3 Setting the Hybrid/AM Attributes of the XPIC Hybrid Radio Link
After the XPIC protection group is created, you need to configure the Hybrid/AM attributes of the XPIC Hybrid 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
The IFX2 board supports the Hybrid/AM function.
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 the Hybrid/AM Configuration tab. Step 4 Configure the Hybrid/AM attributes of the XPIC Hybrid radio link.
Related References
B.4.2 Parameter Description: Link Configuration_XPIC
A.3.4 Configuring the IF/ODU Information of a Radio Link

By configuring the IF/ODU information of a radio link, you can configure the IF/ODU information that is frequently used by the SDH/PDH radio link based on each radio link.
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.

U2000
Precautions
l
In 1+1 HSB/SD protection mode, one protection group corresponds to one radio link. In this case, you need configure only the IF/ODU information of the active device. In 1+1 FD protection mode, one protection group corresponds to one radio link. In this case, you need configure the IF/ODU information of the active device and the ODU information of the standby device.
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. A-29
Issue 02 (2009-10-30)
A Task Collection
l
In the case of one XPIC radio link, one XPIC workgroup corresponds to two radio links. The IF/ODU information of the two radio links in different polarization directions should be separately configured. In the case of N+1 radio links, one N+1 protection group corresponds to N+1 radio links and the IF/ODU information of the N+1 radio links should be configured respectively.
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.4.7 Parameter: Link Configuration_IF/ODU Configuration
A.3.5 Setting the Hybrid/AM Attribute

By configuring the Hybrid/AM attribute, you can set the working mode of the Hybrid IF boards.
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
The OptiX RTN 950 supports the Hybrid/AM function and the corresponding IF boards are IFU2 and IFX2.
Procedure
Step 1 In the NE Explorer, select a Hybrid IF board from the Object Tree and then choose Configuration > Hybrid/AM Configuration from the Function Tree. Step 2 Configure the parameters of the Hybrid/AM attribute.
A Task Collection
Related References
B.14.3 Parameter Description: Hybrid/AM 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.
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. The IF1 boards must work in the STM-1 mode.

U2000
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.
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.
Issue 02 (2009-10-30)
A-31
A Task Collection
Step 3 Configure the attributes 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 an IF port to which a working channel corresponds from Select Mapping Way, and then click 3. .
Repeat 4b to select the IF ports to which other working channels correspond. Click .
4. 5.
Select Protection Unit from Select Mapping Direction. Select an IF port to which a protection channel corresponds from Select Mapping Way, and then click .
Step 5 Click OK. Close the dialog box that is displayed indicating the operation result. ----End
Related References
B.4.3 Parameter Description: N+1 Protection_Create
A.3.7 Setting IF Attributes

In the case of different IF boards, different parameters need to be set.
Prerequisite
l l

U2000
A Task Collection
Context
l l l
The IF1 board is used for TDM microwave. The IFU2 board is used for Hybrid. The IFX2 board is used for XPIC Hybrid.
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 IF attributes. Step 4 Click Apply. ----End
Related References
B.14.1 Parameter Description: IF Interface_IF Attribute
A.3.8 Configuring the ATPC Function

To configure the ATPC function, set the ATPC attributes of the IF board.
Prerequisite
l l
Precautions
l
For the IF boards that are configured with 1+1 protection, configure only the ATPC attributes of the active 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 IF/ODU configuration

NOTE
In the IF/ODU configuration dialog box, the ATPC adjustment thresholds cannot be changed.

U2000
Procedure
Step 1 Select the corresponding board from the Object Tree in the NE Explorer. Choose Configuration > IF Interface from the Function Tree.
A Task Collection
Step 2 Click the ATPC Attributes tab. Step 3 Configure the parameters of ATPC attributes.
Related References
B.14.2 Parameter Description: IF Interface_ATPC Attribute
A.3.9 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.
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
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.14.7 Parameter Description: ODU Interface_Power Attributes
A.3.10 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 Task Collection
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.3.11 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.14.4 Parameter Description: ATPC Adjustment Records
A Task Collection
A.3.12 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 corresponding board from the Object Tree in the NE Explorer. Choose Configuration > Performance Graph Analyze 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.
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.3.13 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 IF 1+1 protection must be configured.

U2000
Procedure
Step 1 In the NE Explorer, select a Hybrid IF board from the Object Tree and then choose Configuration > Hybrid/AM Configuration from the Function Tree. Step 2 Click Query. Step 3 Query the AM status. ----End
A Task Collection
Related References

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.4.6 Parameter Description: IF 1+1 Protection
A.3.15 Querying the IF N+1 Protection Status

You can learn about the current information of the IF N+1 protection by querying the IF N+1 protection status.
Prerequisite
l l
You must be an NM user with NE administrator authority or higher. The IF N+1 protection must be configured.

U2000
Issue 02 (2009-10-30)
A-37
A Task Collection
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 IF N+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 IF N+1 protection status. ----End
Related References
B.4.4 Parameter Description: N+1 Protection
A.3.16 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, and then close the displayed dialog box. Step 5 Click Query Switch Status to check whether the switching operation is successful. ----End
A.3.17 IF N+1 Protection Switching

You can perform external switching on the IF N+1 protection by performing IF N+1 protection switching.
A Task Collection
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, and then close the displayed dialog box. Step 5 Click Query Switch Status to check whether the switching operation is successful. ----End
A.3.18 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
You must be an NM user with NE operator authority or higher. The IF N+1 protection must be configured.

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 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.
A Task Collection
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. Close the displayed prompt dialog box. Step 4 Click Query to check the protocol status. ----End
A.4 Managing the MSP

The OptiX RTN 950 supports the linear MSP. A.4.1 Configuring Linear MSP You can configure linear MSP to protect services over the optical fibers between two nodes. A.4.2 Querying the Status of the Linear MSP By using this operation, you can know the current information about the linear MSP. A.4.3 Performing Linear MSP Switching By using this operation, you can perform the external switching on the linear MSP. A.4.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.4.1 Configuring Linear MSP

You can configure linear MSP to protect services over the optical fibers between two nodes.
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
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.
A Task Collection
Step 4 Click OK, and then close the dialog box that is displayed. ----End
Postrequisite
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 unidirectional cross-connections between the services and the protection channels, in addition to configuring the bidirectional cross-connections between the services and the working channels.
Related References
B.5.1 Parameter Description: Linear MSP_Creation
A.4.2 Querying the Status of the Linear MSP

By using this operation, you can know the current information about the linear MSP.
A Task Collection
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. Step 3 In Protection Group, click the linear MSP group to be queried. Step 4 Click Query > Query Switching Status, and then close the dialog box that is displayed. In Slot Mapping Relation, query the status of the linear MSP. ----End
Related References
B.5.2 Parameter Description: Linear MSP
A.4.3 Performing Linear MSP Switching

By using this operation, you can perform the external switching on 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 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, and then close the dialog box that is displayed. ----End
A Task Collection
A.4.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, 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. Close the prompt dialog box that is displayed. Step 4 Click Query to query the protocol status. ----End
A.5 Managing TDM Services

The TDM services involve the SDH service and the PDH service. A.5.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. A.5.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.5.3 Configuring the Automatic Switching of SNCP Services You can manually add certain alarms for the automatic switching of SNCP services. A.5.4 Deleting Cross-Connections When a service is not used, you can delete the cross-connections of this service to release the corresponding resources.
A Task Collection
A.5.5 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.5.6 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.5.7 Querying TDM Services You can learn about the TDM services that are configured for an NE by querying TDM services. A.5.8 Switching SNCP Services You can perform external switching on SNCP services by performing this operation. A.5.9 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.

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
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 Create. The Create SDH Service dialog box is displayed. Step 3 Configure the parameters of a new SDH service.
A-44
Issue 02 (2009-10-30)
A Task Collection
Related References
B.6.1 Parameter Description: SDH Service Configuration_Creation
A.5.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
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 Create SNCP Service. The Create SNCP Service dialog box is displayed. Step 3 Configure the parameters of a new SNCP service.
Issue 02 (2009-10-30)
A-45
A Task Collection
Related References
B.6.2 Parameter Description: SDH Service Configuration_SNCP Service Creation
A.5.3 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 Initiation Condition to which the working service corresponds.
A Task Collection
Step 3 Set the initiation condition for the working service. Click OK.
Step 4 Right-click 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 Initiation Condition of the working service to be the same as Initiation Condition of the protection service.
Step 6 Click Apply, and then close the dialog box that is displayed. ----End
Related References
B.6.6 Parameter Description: SNCP Service Control
A.5.4 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. Click OK. Then, close the dialog box that is displayed. Step 3 Select the cross-connection that needs to be deleted in Cross-Connection.
A Task Collection
Step 4 Deactivate the service. 1. Right-click the service and choose Deactivate from the shortcut menu. Then, a dialog box is displayed, querying whether you need to deactivate the selected service. Click OK. Then, a dialog box is displayed, indicating that this operation will clear the corresponding service data on the NE side. Click OK. Then, close the dialog box that is displayed. 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.
2.
3. 1. 2.
Step 5 Delete the service.
Step 6 Click Query. The queried information should show that the cross-connection is already deleted. ----End
A.5.5 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 In Cross-Connection, select the configured SDH service. Right-click and choose Expand to Unidirectional from the shortcut menu. Step 3 Select the expanded unidirectional service. Right-click and choose Convert to SNCP Service from the shortcut menu. Then, a dialog box is displayed, querying whether you need to perform this operation. Step 4 Click OK.
A Task Collection
Then, the Create SNCP Service dialog box is displayed. Step 5 Set the parameters of the SNCP service.
Related References
B.6.3 Parameter Description: SDH Service Configuration_Converting Normal Services Into SNCP Services
A.5.6 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.
A Task Collection
Procedure
Step 1 Select the corresponding board from the Object Tree in the NE Explorer. Choose Configuration > SDH Service 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
Postrequisite
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.
Related References
B.6.4 Parameter Description: SDH Service Configuration_Converting SNCP Services Into Normal Services
A.5.7 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.6.5 Parameter Description: SDH Service Configuration
A Task Collection
A.5.8 Switching SNCP Services

You can perform external switching on SNCP services by performing this operation.
Prerequisite
l l

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.5.9 Querying the Protection Status of SNCP Services

You can know the current information of an SNCP service by querying the protection status of SNCP services.
Prerequisite
l l

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
A Task Collection
Related References
A.6 Managing the Clock

To ensure the clock synchronization between transmission nodes on a transport network, you need to manage the NE clock. A.6.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.6.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.6.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.6.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 clock ID from being transmitted on the link that is connected to other clock subnets. A.6.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 SDH 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.6.6 Modifying the Parameters of the Clock Output The NE outputs the 2-Mbit/s external clock regardless of the clock quality. A.6.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.6.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.6.9 Querying the Clock Synchronization Status You can know the current clock synchronization status of an NE by querying the clock synchronization status.
A.6.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 Task Collection
Prerequisite

U2000
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > 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.
NOTE
or
to adjust the priority of this
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.
----End
A Task Collection
Related References
B.7.1 Parameter Description: Clock Source Priority Table
A.6.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 > Clock Subnet Configuration. Step 2 Click the Clock Subnet tab. Step 3 Start the clock protection protocol and configure its parameters.
Related References
B.7.2 Parameter Description: Clock Subnet Setting_Clock Subnet
A.6.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 Task Collection
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 > 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.7.3 Parameter Description: Clock Subnet Setting_Clock Quality
A.6.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 clock ID from being transmitted on the link that is connected to other clock subnets.
A Task Collection
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 > Clock Subnet Configuration. Step 2 Click the SSM Output Control tab. Step 3 Set the SSM control status.
Related References
B.7.4 Parameter Description: Clock Subset Setting_SSM Output Control
A.6.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 SDH 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
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Clock > Clock Subnet Configuration. Step 2 Click the Clock ID Status tab.
A Task Collection
Step 3 Set the clock ID control status.
Related References
B.7.5 Parameter Description: Clock Subset Setting_Clock ID Enabling Status
A.6.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 > Phase-Locked Source Output by External Clock. Step 2 Modify the parameters of the clock output.
Related References
B.7.8 Parameter Description: Output Phase-Locked Source of the External Clock Source
A.6.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

U2000
A Task Collection
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Clock > Clock Source Switching. Step 2 Click the Clock Source Switching Conditiontab. Step 3 Change the conditions for clock source switching.
Related References
B.7.7 Parameter Description: Clock Source Switching_Clock Source Switching
A.6.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 > 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.7.6 Parameter Description: Clock Source Switching_Clock Source Restoration Parameters
A Task Collection
A.6.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 > Clock Synchronization Status. Step 2 Query the clock synchronization status. ----End
Related References
B.7.9 Parameter Description: Clock Synchronization Status
A.7 Managing the ERPS

The Ethernet ring protection switching (ERPS) on the FE/GE ring or Hybrid radio ring can be configured to protect the Ethernet service. A.7.1 Creating Ethernet Ring Protection Instances The Ethernet ring protection switching (ERPS) protection is configured through creation of Ethernet ring protection instances. A.7.2 Setting the Parameters of Ethernet Ring Protocol The parameters to be set include the hold-off time, WTR time, and guard time. A.7.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.7.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.
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. A-59
Issue 02 (2009-10-30)
A Task Collection

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.
Related References
B.9.1 Parameter Description: ERPS Management_Creation
A.7.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.
A Task Collection
Step 3 Set the parameters of Ethernet ring protocol.
Related References
B.9.2 Parameter Description: ERPS Management
A.7.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

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.8 Managing the MSTP

The OptiX RTN 950 supports only the MSTP that generates the CIST.
Issue 02 (2009-10-30)
A-61
A Task Collection
A.8.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.8.2 Setting the Bridge Parameters of the MSTP This topic describes how to set the bridge parameters and port parameters of the MSTP. A.8.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.8.4 Querying the CIST Running Information By querying the CIST running information, you can be familiar with the current information of the CIST. A.8.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.8.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.8.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.8.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
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.
A-62
Set Protocol Type and Enable Protocol.

A Task Collection
1.
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
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.9.3 Parameter Description: MSTP Configuration_Port Group Creation
A.8.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
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. Step 2 Click the Bridge Parameters tab. Step 3 Select the port group ID. Step 4 Click the Bridge Parameters tab.
A Task Collection
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.9.5 Parameter Description: MSTP Configuration_ Bridge Parameters
A.8.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. 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.
A-64
Issue 02 (2009-10-30)
A Task Collection
Related References
B.9.6 Parameter Description: MSTP Configuration_CIST Parameters
A.8.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. Step 3 Click Query. Step 4 Query the CIST running information. ----End
A Task Collection
Related References
B.9.7 Parameter Description: MSTP Configuration_Running Information About the CIST
A.8.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.8.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
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 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.8.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 ... Description Then ...
Issue 02 (2009-10-30)
A-67
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 board where the member ports are located from the drop-down list of Board. 2. Select the port to be deleted from Selected Port List. 3. Click
TIP
Related References
B.9.4 Parameter Description: MSTP Configuration_Port Group Configuration
A.9 Managing the IGMP Snooping

If the multicast router exists on a network, the bridge can enable the IGMP Snooping protocol to realize the multicast function with the operation of the router. A.9.1 Configuring the IGMP Snooping Protocol This topic describes how to configure the IGMP Snooping protocol for a specific E-LAN service. A.9.2 Querying the Port Information of the Routers
A Task Collection
By querying the port information of the router, you can be familiar with the port information of each router that runs the IGMP Snooping protocol. A.9.3 Querying the Information About the Multicast Groups This topic describes how to query the information about each multicast group in the IGMP Snooping protocol. A.9.4 Creating Static Router Ports Static router ports are not aged. A.9.5 Creating a Member of a Static Multicast Group The members of a static multicast group are not aged. A.9.6 Adding a Quickly Deleted Port If an Ethernet port is connected to only one host, you can set this Ethernet port as a quickly deleted port. A.9.7 Calculating IGMP Packets By calculating IGMP packets, you can be familiar with the information about the IGMP packets received and transmitted through the IGMP Snooping protocol.
A.9.1 Configuring the IGMP Snooping Protocol

This topic describes how to configure the IGMP Snooping protocol for a specific E-LAN service.
Prerequisite
l l
You must be an NM user with NE operator authority or higher. The E-LAN service must be created.

U2000
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Ethernet Protocol Configuration > IGMP Snooping Configuration from the Function Tree. Step 2 Click the Protocol Configuration tab. Step 3 Set the attributes of the IGMP Snooping protocol.
Related References
B.9.8 Parameter Description: IGMP Snooping Configuration_Protocol Configuration
A.9.2 Querying the Port Information of the Routers

By querying the port information of the router, you can be familiar with the port information of each router that runs the IGMP Snooping protocol.
A Task Collection
Prerequisite

U2000
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Ethernet Protocol Configuration > IGMP Snooping Configuration from the Function Tree. Step 2 Click the Router Port Management tab. Step 3 Click Query. Step 4 Query the port information of the routers. ----End
Related References
B.9.10 Parameter Description: IGMP Snooping Configuration_Route Management
A.9.3 Querying the Information About the Multicast Groups

This topic describes how to query the information about each multicast group in the IGMP Snooping protocol.
Prerequisite
l l l
You must be an NM user with NE operator authority or higher. The E-LAN service must be created. The NNI port must be configured for the E-LAN service.

U2000
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Ethernet Protocol Configuration > IGMP Snooping Configuration from the Function Tree. Step 2 Click the Route Member Port Management tab. Step 3 Click Query. Step 4 Query the information about the multicast groups. ----End
A Task Collection
Related References
B.9.12 Parameter Description: IGMP Snooping Configuration_Route Member Port Management

Static router ports are not aged.
Prerequisite
l l l
You must be an NM user with NE operator authority or higher. The E-LAN service must be created. The UNI port must be configured for the E-LAN service.

U2000
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Ethernet Protocol Configuration > IGMP Snooping Configuration from the Function Tree. Step 2 Click the Router Port Management tab. Step 3 Click New. Step 4 Set the attributes of the static router ports. 1. 1. Set Service ID and VLAN ID. Select the static router port from the drop-down list of Available Port. Click
TIP
2.
Click OK.
----End
A Task Collection
Related References
B.9.11 Parameter Description: IGMP Snooping Configuraiton_Static Router Port Creation
A.9.5 Creating a Member of a Static Multicast Group

The members of a static multicast group are not aged.
Prerequisite
l l l
You must be an NM user with NE operator authority or higher. The E-LAN service must be created. The NNI port must be configured for the E-LAN service.

U2000
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Ethernet Protocol Configuration > IGMP Snooping Configuration from the Function Tree. Step 2 Click the Route Member Port Management tab. Step 3 Click New. Step 4 Set the attributes of members in the static multicast group. 1. 1. Set Service ID and VLAN ID. Select the member ports from the drop-down list of Available Port. Click
TIP
2.
Click OK.
----End
A Task Collection
Related References
B.9.13 Parameter Description: IGMP Snooping Configuration_Static Multicast Group Member Creation
A.9.6 Adding a Quickly Deleted Port

If an Ethernet port is connected to only one host, you can set this Ethernet port as a quickly deleted port.
Prerequisite

U2000
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Ethernet Protocol Configuration > IGMP Snooping Configuration from the Function Tree. Step 2 Click the Protocol Configuration tab. Step 3 Click Add. Step 4 Set the attributes of the quickly deleted port. Step 5 Click Apply. ----End
Related References
B.9.9 Parameter Description: IGMP Snooping Configuration_Adding Port to Be Quickly Deleted
A.9.7 Calculating IGMP Packets

By calculating IGMP packets, you can be familiar with the information about the IGMP packets received and transmitted through the IGMP Snooping protocol.
Prerequisite

U2000
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Ethernet Protocol Configuration > IGMP Snooping Configuration from the Function Tree.
A Task Collection
Step 2 Click the Packet Statistics tab. Step 3 Click Query. Step 4 Calculate the IGMP packets. ----End
Related References
B.9.14 Parameter Description: IGMP Snooping Configuration_Data Statistics
A.10 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.10.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.10.2 Setting the Port Priority In a LAG that uses the static aggregation mode, a port with higher priority is first selected to transmit services. A.10.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.10.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
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 Create Link Aggregation Group dialog box is displayed. The system displays the Create Link Aggregation Group dialog box.
A Task Collection
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 on the keyboard to select multiple ports.
4.
Click OK, a dialog box is displayed for confirmation, and then click OK to close the dialog box.
----End
Related References
B.9.15 Parameter Description: Ethernet Link Aggregation Management_LAG Creation
Issue 02 (2009-10-30)
A-75
A Task Collection

In a LAG that uses the static aggregation mode, a port with higher priority is first selected to transmit services.
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
Related References
B.9.16 Parameter Description: Ethernet Link Aggregation_Port Priority
A.10.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

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, and then close the displayed prompt dialog box. Step 4 In the Main Interface, select the LAG to be queried and then query the information about the LAG.
A Task Collection
The system displays the information about the slave port in the lower part of the Main Interface. Step 5 Click the Port Priority tab. Step 6 Click Query, and then close the displayed prompt dialog box. Step 7 Query the port priority of the LAG. ----End

If a hybrid radio link is faulty, the Ethernet port related to the hybrid radio link is automatically disabled through the LPT function.
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 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > LPT Management from the Function Tree. Step 2 Click New. The Create LPT dialog box is displayed.
Issue 02 (2009-10-30)
A-77
A Task Collection
Step 3 Configure the board and port of the Convergence Point. Step 4 Set Access Point. 1. 2. In the Board list, select the board of the access point. In Port, select the required port, and then click .
Related References
B.9.17 Parameter Description: LPT Management_Creation
A.12 Managing the QoS

By managing the QoS, you can provide the services of different levels for different service types. A.12.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.12.2 Changing the Ports That Use the DS Domain This topic describes how to add or delete a port that uses the DS domain and set the packet type over the port. A.12.3 Creating a Port Policy By creating a port policy, you can create a new port policy.
A Task Collection
A.12.4 Creating the Traffic By creating the traffic, you can configure ACL and CAR for a specified traffic stream on a specified port. A.12.5 Setting the Port That Uses the Port Policy This topic describes how to set the port that uses the port policy. A.12.6 Configuring Port Shaping This topic describes how to configure the traffic shaping for a port or an egress port. A.12.7 Querying the Port Policy This topic describes how to query the port policy of a port. A.12.8 Querying the DS Domain of a Port This topic describes how to query the mapping relation between a port and a DS domain.
A.12.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 950 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. The default DS domain cannot be modified or deleted.
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 Create. The Create DS Mapping Relation dialog box is displayed. The Create DS Mapping Relation dialog box is displayed. Step 3 On the main interface, configure the attributes of the DS domain. Step 4 Click the Ingress Mapping Relation tab. Step 5 Configure the mapping relations between the priorities of ingress packets and PHB service classes. Step 6 Click the Egress Mapping Relation tab. Step 7 Configure the mapping relations between the priorities of egress packets and PHB service classes.
A Task Collection
Step 8 Select Board where the application ports exist from Application Port. Step 9 Select a port from Available Port, and then click
TIP
Related References
B.11.2 Parameter Description: DiffServ Domain Management_Create

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.
A-80
A Task Collection

U2000
The OptiX RTN 950 has a default DS domain, for which 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. You cannot add or delete a port that uses the default DS domain.
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 Select the DS domain for which you need to add or delete an application port on the main interface. Step 3 Click the Apply Port 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 Port. 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 dropdown list of Available Port. 3. Click You need to change the packet type identified by the port
TIP
Select a new packet type from the drop-down list of Packet Type.
Related References
B.11.3 Parameter Description: DiffServ Domain Applied Port_Modification
A Task Collection
A.12.3 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 from the Function Tree. Step 2 Click New. The Create Port Policy dialog box is displayed. Step 3 Set the ID and name of the port policy. Step 4 Configure the scheduling, weight, and shaping of the egress queue.
Related References
B.11.5 Parameter Description: Port Policy
A.12.4 Creating the Traffic

By creating the traffic, you can configure ACL and CAR for a specified traffic stream on a specified port.
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.
A-82

l
A Task Collection
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 from the Function Tree. Step 2 Click the Traffic Classification Configuration tab. Step 3 Click New. The Create Traffic Classification dialog box is displayed. The Create Traffic Classification dialog box is displayed. Step 4 Configure the attributes of a new traffic.
Related References
B.11.6 Parameter Description: Port Policy_Traffic Classification Configuration
Issue 02 (2009-10-30)
A-83
A Task Collection
A.12.5 Setting the Port That Uses the Port Policy

This topic describes how to set the port that uses the port policy.
Prerequisite
Tools, Instruments, and Materials

U2000
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > QoS Management > Policy Management from the Function Tree. Step 2 Click the Applied 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 Applied Port. Select a port from Available Port, and then click
TIP
Related References
B.11.4 Parameter Description: Policy Management
A Task Collection
A.12.6 Configuring Port Shaping

This topic describes how to configure the traffic shaping for a port or 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.
Related References
B.11.7 Parameter Description: Port Shaping Management_Creation
A.12.7 Querying the Port Policy

This topic describes how to query the port policy of a port.
Prerequisite

U2000
A Task Collection
Procedure
Step 1 Select the NE from the Object Tree in the NE Explorer. Choose Configuration > QoS Management > Policy Management from the Function Tree. Step 2 Click the CoS Queue Configuration tab. Step 3 Click Query. Step 4 Query the CoS configuration of the port policy. Step 5 Click the Traffic Classification Configuration tab. Step 6 Click Query. Step 7 Query the traffic classification of the port policy. Step 8 Click the Applied Object tab. Step 9 Click Query. Step 10 Query the ports that use the port policy. ----End
Related References
A.12.8 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
The OptiX RTN 950 has a default DS domain, for which 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. The default DS domain cannot be modified or deleted.
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 Ingress Mapping Relation tab. Step 3 Click Query.
A Task Collection
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 Egress Mapping Relation tab. Step 6 Click Query. 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 Apply Port tab. Step 9 Click Query. Step 10 Query the ports that use the DS domain. ----End
Related References
B.11.1 Parameter Description: Diffserv Domain Management
A.13 Using the IEEE 802.1ag OAM

By using the 802.1ag OAM, you can maintain Ethernet services in an end-to-end manner. A.13.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. A.13.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.13.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.13.4 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.13.5 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.13.6 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.13.7 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 Task Collection
A.13.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
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
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. The system displays the New Maintenance Domain dialog box. Step 4 Set the parameters of the MD.
Related References
B.10.1 Parameter Description: Ethernet Service OAM Management_Maintenance Domain Creation
A.13.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.
A-88
A Task Collection

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.
Related References
B.10.2 Parameter Description: Ethernet Service OAM Management_Maintenance Association Creation
A.13.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
A Task Collection
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.
Related References
B.10.3 Parameter Description: Ethernet Service OAM Management_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
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.
A Task Collection
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.10.5 Parameter Description: Ethernet Service OAM Management_MIP Creation
A.13.5 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.
Prerequisite
l l l
You must be an NM user with NE operator authority or higher. The MEP must be created. The remote MEP must be created.

U2000
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
A Task Collection
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
Before the CC test, you can set CC Test Transmit Period(ms) according to the actual requirements.
TIP
l l
Alternatively, you can enable a CC test by right-clicking an MEP and then choosing Activate CC from the shortcut menu. To disable a CC test, right-click the MEP where the CC test is performed and then choose Deactivate CC from the shortcut menu.
Step 4 Click Close. ----End
A.13.6 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).
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 MEPs must be created at the remote end. The CC function must be enabled.

U2000
l l
Only MEPs can initiate the LB test, and the MEP can work 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. The LB Test dialog box is displayed.
A Task Collection
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 Set the parameters involved in the LB test.
Step 6 Click Start Test. Then, the LB test result is displayed in the Test Result window. ----End
Related References
B.10.6 Parameter Description: Ethernet Service OAM Management_LB Enabling
A.13.7 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 MEPs must be created at the remote end. 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
A Task Collection
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. The LT Test dialog box is displayed. 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 Set the parameters involved in the LT test.
Step 6 Click Start Test. Then, the LT test result is displayed in the Test Result window. ----End
Related References
B.10.7 Parameter Description: Ethernet Service OAM Management_LT Enabling
A.14 Using the IEEE 802.3ah OAM

By using the IEEE 802.1ag OAM, you can maintain the point-to-point Ethernet links. A.14.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.14.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.14.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.14.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.14.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.14.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 Task Collection
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 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
The OAM mode includes the active mode and the passive mode. For two interconnected systems, the OAM mode of either or both systems must be the active mode. Otherwise, the OAM auto-discovery fails. If the OAM modes of the two systems are 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.10.8 Parameter Description: Ethernet Port OAM Management_OAM Parameter
A.14.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 Task Collection
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
After the OAM auto-discovery operation is successful at both ends, the link fault detection and performance detection are automatically started.
l
To report the detected link fault event to the opposite equipment, you need to set Remote Alarm Support for Link Event to Enabled for the local equipment. To report the detected link fault event to the opposite equipment, you need to set Remote Alarm Support for Link Event to Enabled and set Error Frame Period Window (Frame) and Error Frame Monitor Threshold for the local equipment. After Remote Alarm Support for Link Event is set to Enabled at the opposite port, if the opposite end detects link performance degradation, you can query the 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 Remote Alarm Support for Link Event is set to Enabled at the opposite port, if the opposite equipment detects a link fault event, you can query the ETH_EFM_Fault 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.
Step 4 Click Apply. Then, close the dialog box that is displayed. ----End
Related References
A Task Collection

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.

U2000
After the OAM auto-discovery operation is successful, set Error Frame Period Window (Frame) and Error Frame Monitor Threshold, and set Remote Alarm Support for Link Event to Enabled for the local equipment. If the local equipment detects a link event in the receive direction, it informs the opposite equipment of the link event. If the remote alarm for the link event is also supported 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.10.9 Parameter Description: Ethernet Port OAM Management_OAM Error Frame Monitoring
A.14.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 Task Collection
Prerequisite
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
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.
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 choose Enable Remote Loopback from the drop-down menu of OAM. Step 4 Set Remote Side Loopback Response to Enabled.
A.14.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 Task Collection
Prerequisite
l l
You must be an NM user with NE operator authority or higher. All the external physical ports on the Ethernet service processing board must be enabled.

U2000
When the self-loop detection is enabled for an external physical port, if the self-loop situation occurs at the port, the ETHOAM_SELF_LOOP alarm is reported
Procedure
Step 1 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.15 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.15.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.15.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.15.3 Configuring a History Control Group When configuring a history control group for an Ethernet port, you configure how the history performance data of the port is monitored. The Ethernet board monitors the history performance data of each port at the default sampling interval of 30 minutes. An Ethernet board stores 50 history performance data items. A.15.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.15.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 Task Collection
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
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.12.1 Parameter Description: RMON Performance_Statistics Group
A.15.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
A Task Collection
Related References
B.12.4 Parameter Description: RMON Performance_RMON Setting

When configuring a history control group for an Ethernet port, you configure how the history performance data of the port is monitored. The Ethernet board monitors the history performance data of each port at the default sampling interval of 30 minutes. An Ethernet board stores 50 history performance data items.
Prerequisite
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. 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.12.3 Parameter Description: RMON Performance_History Control Group
A.15.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
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 History Group tab. Step 3 Set the parameters of the history group. Step 4 Click Apply. ----End
Related References
A-102
Issue 02 (2009-10-30)
B Parameters Description
Parameters Description
This topic describes the parameters used in this document. B.1 Parameters for NE Management This topic describes the parameters that are used for managing network elements (NEs). B.2 Parameters for Cable Management This topic describes the parameters that are used for managing cables. B.3 Parameters for Communications Management This topic describes the parameters that are used for communications management. B.4 Radio Link Parameters This topic describes the parameters that are related to radio links. B.5 Multiplex Section Protection Parameters This topic describes the parameters that are related to multiplex section protection (MSP). B.6 SDH/PDH Service Parameters This topic describes the parameters that are related to SDH/PDH services. B.7 Clock Parameters This topic describes the parameters that are related to clocks. B.8 Parameters for Ethernet Services This topic describes the parameters that are related to Ethernet services. B.9 Ethernet Protocol Parameters This topic describes the parameters that are related to the Ethernet protocol. B.10 Parameters for the Ethernet OAM This topic describes the parameters that are related to the Ethernet operation, administration and maintenance (OAM). B.11 QoS Parameters This topic describes the parameters that are related to QoS. B.12 RMON Parameters This topic describes the parameters that are related to RMON performances. B.13 Parameters for the Orderwire and Auxiliary Interfaces This topic describes the parameters that are related to the orderwire and auxiliary interfaces. B.14 Parameters for Board Interfaces
Issue 02 (2009-10-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. B-1
This topic describes the parameters that are related to board interfaces. B.15 Parameters for Overhead This topic describes the parameters that are related to overhead.
B-2
Issue 02 (2009-10-30)
B.1 Parameters for NE Management

This topic describes the parameters that are used for managing network elements (NEs). B.1.1 Parameter Description: NE Searching This topic describes the parameters that are used for searching for NEs. B.1.2 Parameter Description: NE Creation This topic describes the parameters that are related to NE creation. B.1.3 Parameter Description: NE Attribute_NE ID Change This topic describes the parameters that are used for changing NE IDs. B.1.4 Parameter Description: NE Time Synchronization This topic describes the parameters that are used for synchronizing the time of NEs. B.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.6 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 Parameter Description: NE Searching

This topic describes the parameters that are used for searching for NEs.
Navigation Path
On the Main Topology, choose File > Discovery > NE.
Issue 02 (2009-10-30)
B-3
Parameters for the Search Field

Parameter Address Type Value Range IP Address of GNE NSAP Address IP Address Range of GNE
l
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. 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. To search for all the NEs that communicate with the gateway NE, select IP Address Range of GNE. 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.
B-4
Issue 02 (2009-10-30)
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. 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. 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
Parameter for Searching for NEs

Parameter Search for NE Value Range Selected Deselected Default Value Selected Description This parameter specifies whether to search for all the NEs in the specified domain.
Issue 02 (2009-10-30)
B-5
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. 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
This parameter specifies the user name to be entered when an NE is created. This parameter is valid only when Create NE after search is selected. This parameter specifies the password to be entered when an NE is created. This parameter is valid only when Create NE after search is selected. This parameter specifies whether to automatically upload the NE data after the NE is found and created. If only Upload after create is selected, Search for NE and Create NE after search are selected automatically.
Password
Upload after create
Selected Deselected
Deselected
B-6
Issue 02 (2009-10-30)
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
GNE Address
GNE ID
Created As GNE
Yes No
Yes
This parameter specifies the password to be entered when an NE is created. This parameter is valid only when Create NE after search is selected.
Connection Mode
Common Security SSL
Common
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 Creating NEs by Using the Search Method
B.1.2 Parameter Description: NE Creation

This topic describes the parameters that are related to NE creation.
Navigation Path
1. 2. In the Physical View, right-click New > NE. Choose RTN Series > OptiX RTN 950 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
ID
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. 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.
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.
l
Name
This parameter specifies the name of the NE. After you specifies the name of the NE, the name is displayed under the icon of the NE.
Remarks
This parameter specifies the remarks of the NE.
B-8
Issue 02 (2009-10-30)
Parameter Gateway Type
Value Range Non-Gateway Gateway
Default Value Non-Gateway
Description
l
This parameter is set to Gateway if the new NE is a gateway NE. This parameter is set to Non-Gateway if the new NE is a nongateway NE. 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
Affiliated Gateway Protocol
IP OSI
IP
This parameter needs to be set when Gateway Type is set to Gateway. When the OSI over DCC solution is used, this parameter is set to OSI. In other cases, this parameter is set to IP.
IP Address
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.
Connection Mode
Common Security SSL
Common
Port NE User
1400 -
Issue 02 (2009-10-30)
B-9
Parameter Password
Value Range -
Default Value -
Description 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.
NSAP Address
Related Tasks
B.1.3 Parameter Description: NE Attribute_NE ID Change

This topic describes the parameters that are used for changing NE IDs.
Navigation Path
1. 2. Select the NE from the Object Tree in the NE Explorer. Choose Configuration > NE Attribute from the Function Tree. Click Modify NE ID. The Modify NE ID dialog box is displayed.
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. 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.
B-10
Issue 02 (2009-10-30)
Parameter New 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.
Related Tasks
A.1.4 Changing the NE ID
B.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 Synchronous Mode Value Range Standard NTP NM Null
l
Default Value Null
Description This parameter indicates the name of the NE. This parameter indicates the ID of the NE.
l
If this parameter is set to NM, the NE synchronizes the time of the NMS server. 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.
Issue 02 (2009-10-30)
B-11
Parameters for the Standard NTP Server

Parameter Standard NTP Server Identifier Value Range NE ID IP
l
Default Value NE ID
Description
l
If the NE functions as the gateway NE, this parameter is set to IP. 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. 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. If the NE functions as the gateway NE, this parameter is set to the IP address of the external NTP server. If the NE functions as a non-gateway NE, this parameter is set to the ID or IP address of the gateway NE. If the NTP server does not need to authenticated, this parameter is set to the value "0". 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).
Standard NTP Server
Standard NTP Server Key
0 to 1024
B-12
Issue 02 (2009-10-30)
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). It is recommended that you use the default value. This parameter indicates whether Synchronization Starting Time is the daylight saving time. This parameter is set according to the actual situation. This parameter indicates the period of synchronizing the time of the NE with the time of the NMS. It is recommended that you use the default value.
DST
Selected Deselected
Deselected
Synchronization Period (days)
1 to 300
Related Tasks
A.1.6 Synchronizing the NE Time
B.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. On the Main Topology, choose Configuration > NE Batch Configuration > NE Time Localization Management.
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. B-13
Issue 02 (2009-10-30)
2.
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.
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. This parameter is set according to the place where the NE is located. The parameters related to daylight saving time can be valid only when this parameter is selected. This parameter is set according to the situation whether daylight saving time is used in the place where the NE is located.
DST
Selected Deselected
Deselected
Offset
1 to 120 Unit: minute(s)
This parameter specifies the offset value of the daylight saving time. This parameter specifies the method of adjusting the daylight saving time.
Start Rule
DATE WEEK DATE-WEEK
WEEK
Start Time End Rule
DATE WEEK DATE-WEEK
WEEK
This parameter specifies the start daylight saving time. This parameter specifies the method of adjusting the daylight saving time.
End Time
This parameter specifies the end daylight saving time.
B-14
Issue 02 (2009-10-30)
Related Tasks
A.1.8 Localizing the NE Time
B.1.6 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 950 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. This parameter specifies the time of automatically disabling the operations such as loopback, and shutdown of the laser.
Auto Disabling
Disabled Enabled
Enabled
Auto Disabling Time(min)
1 to 2880
B.2 Parameters for Cable Management

This topic describes the parameters that are used for managing cables. B.2.1 Parameter Description: Fiber Search This topic describes the parameters that are used for searching for fibers. B.2.2 Parameter Description: Fiber Creation This parameter describes the parameters that are used for creating fibers. B.2.3 Parameter Description: Radio Link Creation This topic describes the parameters that are used for creating radio links.
B.2.1 Parameter Description: Fiber Search

This topic describes the parameters that are used for searching for fibers.
Navigation Path
1. 2. Choose File > Discovery > Fiber from the Main Menu. 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, and the click . 3. Click Search.
Parameters for Searching For Fibers

Parameter Source NE Value Range Default Value Description This parameter indicates the name of the source NE on which fibers or radio links are found. This parameter indicates the board and slot of the source NE on which fibers or radio links are found. This parameter indicates the number of the port on the board of the source NE on which fibers or radio links are found. This parameter indicates the name of the sink NE on which fibers or radio links are found. This parameter indicates the board and slot of the sink NE on which fibers or radio links are found. This parameter indicates the number of the port on the board of the sink NE on which fibers or radio links are found. This parameter indicates the level of the found fiber or the working mode of the found radio link.
Source Board
Source Port
Sink NE
Sink Board
Sink Port
Level
B-16
Issue 02 (2009-10-30)
Parameter Name
Value Range -
Default Value -
Description This parameter indicates the name of the found fiber or radio link. This parameter indicates the direction of the found fiber. This parameter indicates whether the found fiber or radio link conflicts with the fiber or radio link displayed on the NMS. This parameter indicates whether the cable is created successfully. This parameter indicates the type of the found fiber or cable.
Direction
Two-Fiber Bidirectional Single-Fiber Unidirectional
Conflict with logical link (Y/N)
Yes No
Operation Result
Succeeded Failed
Fiber/Cable Type
Related Tasks
Creating an Optical Transmission Line or Radio Link by Using the Search Method
B.2.2 Parameter Description: Fiber Creation

This parameter describes the parameters that are used for creating fibers.
Navigation Path
1. 2. Choose File > Create > Link from the Main Menu. The Add Object dialog box is displayed. Choose Link > Fiber from the Object Tree.
Parameters for Fibers

Parameter Create Ways Value Range Common Ways Batch Ways
l
Default Value Common Ways
Description
l
If Common Ways is selected, fibers need to created one by one. If Batch Ways is selected, fibers can be created in batches.
Fiber/Cable Type
Fiber
Fiber
This parameter indicates that Fiber/Cable Type to be created is a fiber.

B-17
Issue 02 (2009-10-30)
Parameter Name
Value Range -
Default Value -
Description This parameter specifies the name of the fiber to be created. The name consists of up to 255 characters, excluding certain special marks such as | * ? " < >. This parameter specifies the remark information customized by the user. This parameter specifies the source NE on which the fiber needs to be created. This parameter specifies the board, slot, and port of the source NE on which the fiber needs to be created. This parameter indicates the level that corresponds to the port on the board. This parameter specifies the medium type of the fiber.
Remarks
Source NE
Source NE Slot-Board Type-Port
Rate Level
Medium Type
G.652 G.653 G.654 G.655
G.652
Sink NE
This parameter specifies the sink NE on which the fiber needs to be created. This parameter specifies the board, slot, and port of the sink NE on which the fiber needs to be created. This parameter specifies the direction of the fiber to be created. This parameter specifies the length of the fiber to be created. This parameter specifies the attenuation of the fiber to be created.
Sink NE Slot-Board Type-Port
Direction
Two-Fiber Bidirectional Single-Fiber Unidirectional
Length(km)
Attenuation(dB)
B-18
Issue 02 (2009-10-30)
Parameter Created On
Value Range -
Default Value -
Description This parameter specifies the time when the fiber is created. This parameter specifies the name of the person who creates the fiber. This parameter specifies the name of the person who maintains the fiber.
Creator
Maintainer
Related Tasks
Creating an SDH Optical Transmission Link by Using the Manual Method
B.2.3 Parameter Description: Radio Link Creation

This topic describes the parameters that are used for creating radio links.
Navigation Path
1. 2. Choose File > Create > Link from the Main Menu. The Add Object dialog box is displayed. Choose Link > Microwave Link from the Object Tree.
Parameters for Microwave Links

Parameter Fiber/Cable Type Value Range Radio Link Default Value Radio Link Description This parameter indicates that a radio link needs to be created is Fiber/Cable Type. This parameter specifies the name of the radio link to be created. The name consists of up to 255 characters, excluding certain special marks such as | * ? " < >. This parameter specifies the remark information customized by the user.
Name
Remarks
Issue 02 (2009-10-30)
B-19
Parameter Source NE
Value Range -
Default Value -
Description The parameter specifies the source NE on which the radio link needs to be created. This parameter specifies the board, slot, and port of the source NE on which the radio link needs to be created. This parameter indicates the level that corresponds to the port on the IF board. The parameter specifies the sink NE on which the radio link needs to be created. This parameter specifies the board, slot, and port of the sink NE on which the radio link needs to be created. This parameter specifies the length of the radio link to be created. This parameter indicates the time when the radio link is created. This parameter specifies the name of the person who creates the radio link. This parameter specifies the name of the person who maintains the radio link.
Source NE Slot-Board Type-Port
Rate Level
Sink NE
Sink NE Slot-Board Type-Port
Length(km)
Created On
Creator
Maintainer
Related Tasks
Creating a Radio Link by Using the Manual Method
B.3 Parameters for Communications Management

This topic describes the parameters that are used for communications management.
B-20
Issue 02 (2009-10-30)
B.3.1 Parameter Description: NE Communication Parameter Setting This topic describes the parameters that are used for NE communication setting. B.3.2 Parameter Description: DCC Management_DCC Rate Configuration This topic describes the parameters that are used for configuring the DCC rate. B.3.3 Parameter Description: DCC Management_DCC Transparent Transmission Management This topic describes the parameters that are used for DCC transparent transmission management. B.3.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.3.5 Parameter Description: NE ECC Link Management This topic describes the parameters that are used for NE ECC link management. B.3.6 Parameter Description: IP Protocol Stack Management_IP Route Management This topic describes the parameters that are used for IP route management. B.3.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.3.8 Parameter Description: IP Protocol Stack Management_OSPF Parameter Settings This topic describes the parameters that are used for OSPF settings. B.3.9 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.3.10 Parameter Description: OSI Management_Routing Table This topic describes the parameters that are related to OSI routing tables. B.3.11 Parameter Description: OSI Management_OSI Tunnel This topic describes the parameters that are related to the OSI tunnels. B.3.12 Parameter Description: DCN Management_Bandwidth Management This topic describes the parameters that are used for bandwidth management of the inband DCN. B.3.13 Parameter Description: DCN Management_Port Setting This topic describes the parameters that are used for setting ports of the inband DCN. B.3.14 Parameter Description: Access Control This topic describes the parameters that are used for access control of the NMS. B.3.15 Parameter Description: LCT Access Control This topic describes the parameters that are used for LCT access control.
B.3.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.
Issue 02 (2009-10-30)
B-21
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 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.
Gateway IP Address
Related Tasks
B.3.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.
Parameters for DCC Rate Configuration

Parameter Port Value Range Default Value Description This parameter indicates the port that is connected to the DCC channel.
B-22
Issue 02 (2009-10-30)
Parameter Enabled/Disabled
Value Range Enabled Disabled
Default Value Enabled (for line ports) Disabled (for external clock interfaces)
Description 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. 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. If external clock interfaces are used to transparently transmit the DCC solution, Enabled/Disabled is set to Enabled for the external clock interfaces.
Channel Type
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 Type for the SDH line ports is set to a value that is the same as the value for third-party network. If the DCC transparent transmission solution is adopted, the value of Channel Type 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. If the OSI over DCC solution is adopted, Protocol Type is set to OSI. This parameter is valid only when Protocol Type is set to OSI. 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.
LAPD Role
User Network
User
Issue 02 (2009-10-30)
B-23
Related Tasks
B.3.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. 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.
Parameters for DCC Transparent Transmission Management

Parameter Source Timeslot/ Porta 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 Sink Timeslot/ Porta
B-24
l l
Default Value -
Description This parameter indicates the source timeslot or port.

l
Only one overhead byte can be selected each time. X1, X2, X3, and X4 indicate the customized overhead bytes that are used for transmitting asynchronous data services. An overhead byte cannot be a byte that is used. For example, an overhead byte cannot be a byte in the used DCC channel.
This parameter indicates the sink timeslot or port.

Issue 02 (2009-10-30)
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. An overhead byte cannot be a byte that is used. For example, an overhead byte cannot be a byte in the used DCC channel. 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 Source Timeslot/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.2.4 Configuring DCC Transparent Transmission
B.3.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 (2009-10-30)
B-25
Parameters for the ECC Extended Mode

Parameter ECC Extended Mode Value Range Auto mode Specified mode Default Value Specified 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.0.0.0 1601 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. This parameter can be set only when the NE functions as the server of the extended ECC. In normal cases, the NE that is close to the U2000 functions as the server. 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 1601
l
Description
l
This parameter is valid only when ECC Extended Mode is set to Specified mode. 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. Opposite IP and Port are respectively set to the IP address of the server NE and the specified pot number.
Related Tasks
B.3.5 Parameter Description: NE ECC Link Management

This topic describes the parameters that are used for NE ECC link management.
B-26 Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. Issue 02 (2009-10-30)
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 0 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. If the value is set to 0, it indicates that the source NE is adjacent to the destination NE. 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. If the ECC route is generated automatically, the priority is 4. If the ECC route is added manually, the priority is 5.
Level
4 5
Mode
Manual Automatic
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.
SCC No.
Related Tasks
B.3.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 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.
l
Mask Gateway IP Address
Protocol
DIRECT STATIC OSPF RIP OSPF_ASE OSPF_NSSA
DIRECT: indicates the route between the local NE and an adjacent NE. STATIC: indicates the route that is created manually. OSPF: indicates the route between the local NE and a non-adjacent NE. RIP: indicates the route that is discovered by the routing information protocol. OSPF_ASE: indicates the route whose Destination Address is beyond the OSPF domain. OSPF_NSSA: indicates the route whose Destination Address is in a not so stubby area (NSSA). A route can be deleted in the case of STATIC only, but cannot be edited in the other cases. Compared with a dynamic route, a static route has a higher priority. If any conflict occurs, the static route is preferred.
Issue 02 (2009-10-30)
B-28
Parameter Interface
Value Range -
Default Value -
Description 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. Hop Count 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. This parameter indicates whether the current IP route is available.
Hop Count
0 to 65535
Working Status
Working Unworking
Related Tasks
B.3.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.
Issue 02 (2009-10-30)
B-29
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.
Mask Gateway IP Address
Related Tasks
B.3.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.
OSPF Parameters
Parameter Area Value Range Default Value 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. When setting the area for the NEs, you need to set the NEs that run the OSPF protocol to the same area.
B-30
Issue 02 (2009-10-30)
Parameter DCC Hello Timer (s)
Default Value 1
Description
l
DCC Hello Timer(s) specifies the Hello packet timer at the DCC interface. 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. DCC Hello Timer(s) determines the interval for the hello packet timer to transmit the hello packets. In the case of two interconnected NEs, DCC Hello Timer(s) must be set to the same value. DCC Neighbor Dead Time(s) specifies the dead time of a neighbor router at the DCC interface. 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. DCC Neighbor Dead Time(s) should be set to a value that is a minimum of twice the value of DCC Hello Timer(s). 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 Neighbor Dead Time(s)
1 to 65535
DCC Retransmission Timer(s) DCC Delay(s)
1 to 65535
DCC Retransmission Timer(s) specifies the interval for transmitting a request through the DCC interface to retransmit the link state advertisement (LSA) packets.
l
1 to 3600
DCC Delay(s) specifies the delay time to transmit the LSA packets through the DCC interface. 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).
Issue 02 (2009-10-30)
B-31
Parameter LAN Hello Timer (s)
Default Value -
Description
l
DCC Hello Timer(s) specifies the hello packet timer at the LAN interfaces. 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. LAN Hello Timer(s) determines the interval for the hello packet timer of the NE to transmit the hello packets. In the case of two interconnected NEs, LAN Hello Timer(s) must be set to the same value. LAN Neighbor Dead Time(s) specifies the dead time of a neighbor router at the LAN interface. 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. 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). 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.
LAN Neighbor Dead Time(s)
LAN Retransmission Timer(s) LAN Delay(s)
1 to 65535
LAN Retransmission Timer(s) specifies the time for transmitting a request for retransmission of the LSA packets through the LAN interface.
l
1 to 3600
LAN Delay(s) specifies the delay time to transmit the LSA packets through the LAN interface. 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).
B-32
Issue 02 (2009-10-30)
Parameter Interface Type Enable Flag
Value Range lan Enabled Disabled
Default Value lan Enabled
Description This parameter specifies the interface type of the OSPF protocol. This parameter specifies Enable Flag of the OSPF protocol.
Related Tasks
B.3.9 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 L1 L2 Default Value L1 Description This parameter indicates the name of the NE.
l
An NE whose Configuration Role is set to L1 cannot function as a neighbor of an NE in the other area. It uses a route in the local area only and access the other area by distributing the default route of the nearest L2 NE. 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.
Issue 02 (2009-10-30)
B-33
Related Tasks
B.3.10 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. 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. This parameter indicates the system ID of the destination NE. Generally, the system ID is the MAC address. This parameter indicates the number of hops that reach the destination NE or destination area.
Peer End System ID Destination SYSID
Metric
B-34
Issue 02 (2009-10-30)
Parameter Adjacency No.1
Value Range -
Default Value -
Description 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.2
Related Tasks
A.2.14 Querying OSI Routes
B.3.11 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 l
This parameter specifies the LAPD actor. 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 Configure LAPD Enable
Enabled Disabled
Enabled
This parameter indicates whether the current LAPD is enabled. This parameter specifies whether the LAPD is enabled.
Issue 02 (2009-10-30)
B-35
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). L2 Wait Time to Retry(s) indicates the interval for retransmitting packets at the LAPD link layer. 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. This parameter needs to be set according to the planning information. In normal cases, it is recommended that you use the default value. This parameter specifies L2 Retry Times. L2 Retry Times indicates the maximum number of packet retransmission attempts at the LAPD link layer. 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. 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
B-36
Issue 02 (2009-10-30)
Parameter L3 Hello Timer(s)
Default Value 3
Description
l
This parameter specifies L3 Hello Timer (s). 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. 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. This parameter needs to be set according to the planning information. In normal cases, it is recommended that you use the default value. This parameter specifies L3 E3 Timer (s). L3 E3 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. L3 E3 Timer(s) needs to be set according to the network situation. If the network is in good situation, L3 E3 Timer(s) can be set to a greater value. Otherwise, it is recommended that you set L3 Hello Timer(s) to a smaller value. This parameter needs to be set according to the planning information. In normal cases, it is recommended that you use the default value.
L3 E3 Timer(s)
1 to 200
50
Issue 02 (2009-10-30)
B-37
Parameter L3 IS Timer(s)
Default Value 10
Description
l
This parameter specifies L3 IS Timer (s). 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. 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. This parameter needs to be set according to the planning information. In normal cases, it is recommended that you use the default value. This parameter specifies L3 Hold Timer (s). L3 Hold Timer(s) indicates the hold timer at the LAPD link network layer. 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. This parameter needs to be set according to the planning information. In normal cases, it is recommended that you use the default value. This parameter specifies COST. COST indicates the overhead value of the virtual LAPD that corresponds to the OSI tunnel. The overhead value determines whether this link is perverted. If the overhead value is smaller, this link has a higher priority to be selected. This parameter needs to set according to the planning information.
L3 Hold Timer(s)
2 to 63
COST
1 to 63
20
l l
Related Tasks
B.3.12 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 1 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 950 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. 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(kbps) E1 Port Bandwidth (kbps) Tunnel Bandwidth (kbps) IF Port Bandwidth (kbps)
This parameter specifies the bandwidth of the inband DCN. The OptiX RTN 950 does not support this parameter. The OptiX RTN 950 does not support this parameter. The OptiX RTN 950 does not support this parameter.
Related Tasks
A.2.10 Setting the VLAN ID and Bandwidth Used by an Inband DCN
B.3.13 Parameter Description: DCN Management_Port Setting

This topic describes the parameters that are used for setting ports 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 Port Settings tab.
Parameters for Setting FE or GE Ports

Parameter Port Name Enable Status Value Range Enabled Disabled
l
Default Value Enabled
Description This parameter indicates the name of the FE or GE port.

l
This parameter specifies whether the FE or GE port is enabled. The inband DCN can transmit the network management information over the link only after the inband DCN function is enabled at the FE or GE ports at both ends of a link.
Parameters for Setting IF Ports

Parameter Port Name Enable Status Value Range Enabled Disabled
l
Description This parameter indicates the name of the IF port.

l
This parameter specifies whether the IF port is enabled. The inband DCN can transmit the network management information over the link only after the IF ports at both ends of a link are enabled on the inband DCN.
Related Tasks
A.2.11 Configuring the Enable Status of the Inband DCN Function on Ports
B.3.14 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-40
Issue 02 (2009-10-30)
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 Baud Rate Value Range Selected Deselected 1200 2400 4800 9600 19200 38400 57600 115200
l
Default Value Selected
Description After Enable Serial Port Access is selected, the NE can access the NMS or command lines through the serial port.
l
9600
This parameter specifies the data transmission rate in the communications through serial ports. 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.3.15 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.
Parameters for LCT Access Control

Parameter NE Value Range Default Value Description This parameter indicates the name of the NE.
Issue 02 (2009-10-30)
B-41
Parameter LCT Access Control Switch
Value Range Enable Access Disable Access
Default Value Enable Access
Description
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. 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. 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. 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.4 Radio Link Parameters

This topic describes the parameters that are related to radio links. B.4.1 Parameter Description: Link Configuration_XPIC Workgroup_Creation This topic describes the parameters that are related to the XPIC function. B.4.2 Parameter Description: Link Configuration_XPIC This topic describes the parameters that are related to the XPIC function. B.4.3 Parameter Description: N+1 Protection_Create This topic describes the parameters that are used for creating an IF N+1 protection group. B.4.4 Parameter Description: N+1 Protection This topic describes the parameters that are related to IF N+1 protection. B.4.5 Parameter: IF 1+1 Protection_Create This topic describes the parameters that are used for creating an IF 1+1 protection group. B.4.6 Parameter Description: IF 1+1 Protection This topic describes the parameters that are related to IF 1+1 protection. B.4.7 Parameter: Link Configuration_IF/ODU Configuration This topic describes the parameters that are used for configuring the IF/ODU.
B-42
Issue 02 (2009-10-30)
B.4.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 7M 14M 28M 56M Polarization direction-V Polarization direction-H l l l
Default Value 7M
Description
l
This parameter specifies the working bandwidth of the radio link. When this parameter is set to 56M, the high-power ODU must be used. This parameter indicates the polarization direction of a radio link. It is recommended that you install the two IFX2 boards that form an XPIC workgroup in the slots that are at the same layer or in the same column, and set the IF port on the IFX2 board that has a smaller slot number to Link ID-V and the IF port on the other IFX2 board to Link ID-H. Set Link ID-V and Link ID-H. A link ID is an identifier of a radio link and is used to prevent the radio links between sites from being wrongly connected. 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. 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
l l
Issue 02 (2009-10-30)
B-43
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. The transmit power of the ODU must be set to the same value at both ends of a radio link. 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. This parameter is set according to the planning information. 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.. This parameter is set to limit the maximum transmit power of the ODU within this preset range. The maximum transmit power adjusted by using the ATPC function should not exceed this value. This parameter is set according to the planning information. This parameter indicates the channel central frequency. 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. This parameter is set according to the planning information.
Maximum Transmit Power (dBm)
Transmission Frequency(MHz)
B-44
Issue 02 (2009-10-30)
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. 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. 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. 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. The T/R spacing of the ODU should be set to the same value at both the ends of a radio link. When this parameter is set to mute, the ODU does not work but can normally receive microwave signals. When this parameter is set to unmute, the ODU normally transmits and receives microwave signals. In normal cases, this parameter is set to unmute.
Transmission Status
unmute mute
unmute
Issue 02 (2009-10-30)
B-45
Parameter ATPC Enabled
Value Range Disabled Enabled
Default Value Disabled
Description
l
This parameter specifies whether the ATPC function is enabled. 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. The settings of the ATPC attributes must be consistent at both ends of a radio link. In the case of areas where fast fading severely affects the radio transmission, it is recommended that you set this parameter to Disabled. 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. The central value between the ATPC upper threshold and the ATPC lower threshold is set as the expected receive power. 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. You can set the ATPC upper threshold only when ATPC Automatic Threshold Enable Status is set to Disabled. This parameter specifies whether the automatic threshold function is enabled. 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.
ATPC Upper Threshold(dBm) ATPC Lower Threshold(dBm)
-75.0 to -20.0 -35.0 to -90.0
-45.0 -70.0
ATPC Automatic Threshold Enable Status
Disabled Enabled
Disabled
B-46
Issue 02 (2009-10-30)
Related Tasks
A.3.2 Creating an XPIC Protection Group
B.4.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.
l
Polarization direction-H Link ID-H
IF Channel Bandwidth
7M 14M 28M 56M
7M
IF Channel Bandwidth refers to the channel spacing of the corresponding radio links. This parameter is set according to the planning information.
Issue 02 (2009-10-30)
B-47
Parameter Power to Be Received -V(dBm)
Value Range -
Default Value -
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. When the antenna misalignment indicating function is enabled, if the actual receive power of the ODU exceeds the range of receive power3 dB, the ODU LED of the IF board connected to the ODU is on (yellow) for 300 ms and off for 300 ms repeatedly, indicating that the antenna is not aligned. 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. This parameter is set according to the planning information. 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. When the antenna misalignment indicating function is enabled, if the actual receive power of the ODU exceeds the range of receive power3 dB, the ODU LED of the IF board connected to the ODU is on (yellow) for 300 ms and off for 300 ms repeatedly, indicating that the antenna is not aligned. 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. This parameter is set according to the planning information.
Power to Be Received -H(dBm)
B-48
Issue 02 (2009-10-30)
Parameter Maximum Transmit Power (dBm)
Value Range -
Default Value -
Description
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.. This parameter is set to limit the maximum transmit power of the ODU within this preset range. The maximum transmit power adjusted by using the ATPC function should not exceed this value. This parameter is set according to the planning information. 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. The transmit power of the ODU should be set to the same value at both ends of a radio link. 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. This parameter is set according to the planning information. This parameter indicates or specifies the transmit frequency of the ODU, namely, the channel central frequency. 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. The difference between the transmit frequencies of both the ends of a radio link should be one T/R spacing. This parameter needs to be set according to the planning information.
Transmit Power (dBm)
Transmission Frequency(MHz)
Issue 02 (2009-10-30)
B-49
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. 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. 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. 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. The T/R spacing of the ODU should be set to the same value at both ends of a radio link. This parameter indicates or specifies the transmit status of the ODU. If this parameter is set to mute, the transmitter of the ODU does not work but can normally receive microwave signals. If this parameter is set to unmute, the ODU can normally transmit and receive microwave signals. In normal cases, this parameter is set to unmute.
Transmission Status
unmute mute
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-50
Issue 02 (2009-10-30)
Parameter AM Mode
Value Range Asymmetric
Default Value Asymmetric
Description If AM Mode is set to Asymmetric, the AM switching in one direction of the radio link does not trigger the AM switching in the other direction of the radio link.
NOTE The Optix RTN equipment supports onlyAsymmetric.
AM Enable Status
Disabled Enabled
Disabled
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. 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 Guaranteed 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 Guaranteed AM Capacity.
This parameter is valid only when AM Enable Status is set to Enabled.
Issue 02 (2009-10-30)
B-51
Parameter Modulation Mode of the Full AM Capacity
Value Range QPSK 16QAM 32QAM 64QAM 128QAM 256QAM
Default Value -
Description 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. Manually Specified Modulation Mode QPSK 16QAM 32QAM 64QAM 128QAM 256QAM Guaranteed E1 Capacity l
QPSK
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.
When AM Enable Status is set to Enabled, this parameter depends on IF Channel Bandwidth and Modulation Mode of the Guaranteed AM Capacity and cannot be set. When AM Enable Status is set to Disabled, this parameter depends on IF Channel Bandwidth and Manually Specified Modulation Mode and cannot be set.
E1 Capacity
1 to 75
This parameter specifies the number of E1 services that can be transmitted in Hybrid work mode.
Parameters for ATPC Management

Parameter Group ID Value Range Default Value Description This parameter indicates the object to be set.
B-52
Issue 02 (2009-10-30)
Parameter ATPC Enable Status
Description
l
This parameter specifies whether the ATPC function is enabled. 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. The settings of the ATPC attributes must be consistent at both ends of a radio link. In the case of areas where fast fading severely affects the radio transmission, it is recommended that you set this parameter to Disabled. 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. Set the central value between the ATPC upper threshold and the ATPC lower threshold to a value for the expected receive power. 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. You can set this parameter only when ATPC Automatic Threshold Enable Status is set to Disabled.
-75.0 to -20.0 -35.0 to -90.0
-45.0 -70.0
Issue 02 (2009-10-30)
B-53
Parameter ATPC Automatic Threshold Enable Status
Description
l
This parameter specifies whether the ATPC automatic threshold function is enabled. 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. If this parameter is set to Disabled, you need to manually set ATPC Upper Threshold(dBm) and ATPC Lower Threshold(dBm).
Related Tasks
A.3.3 Setting the Hybrid/AM Attributes of the XPIC Hybrid Radio Link
B.4.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. When the time after the former working channel is restored to normal reaches the set WTR time, a revertive switching occurs. It is recommended that you use the default value.
B-54
Issue 02 (2009-10-30)
Parameter Enabled
Description
l
This parameter specifies whether the SD switching function of N+1 protection is enabled. When this parameter is set to Enabled, the SD condition is considered as a trigger condition of protection switching. It is recommended that you set this parameter to Enabled.
Slot Mapping Relation Parameters

Parameter Select Mapping Direction Value Range Work Unit Protection Unit
l
Default Value Work Unit
Description
l
This parameter specifies the mapping direction of N+1 protection. This parameter is set according to the planning information. In the case of N+1 protection, map N IF ports as Work Unit and map the remaining IF port as Protection Unit. This parameter is set according to the planning information.
Select Mapping Way
Mapped Board
This parameter indicates the working unit and protection unit that have been set.
Related Tasks
B.4.4 Parameter Description: N+1 Protection

This topic describes the parameters that are related to IF N+1 protection.
Navigation Path
Select the NE from the Object Tree in the NE Explorer. Choose Configuration > N+1 Protection from the Function Tree.
Protection Group Parameters

Parameter Protection Group ID
Issue 02 (2009-10-30)
Value Range -
Default Value -
Description This parameter indicates the ID of the protection group.

B-55
Parameter WTR Time(s)
Default Value -
Description
l
This parameter indicates or specifies the WTR time. When the time after the former working channel is restored to normal reaches the set WTR time, a revertive switching occurs. It is recommended that you use the default value. This parameter indicates or specifies whether the SD switching function of N +1 protection is enabled. When this parameter is set to Enabled, the SD condition is considered as a trigger condition of protection switching. It is recommended that you set this parameter to Enabled.
SD Enable
Enabled Disabled
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 Protection Unit Remote/Local End Indication
Related Tasks
A.3.15 Querying the IF N+1 Protection Status
B.4.5 Parameter: IF 1+1 Protection_Create

This topic describes the parameters that are used for creating an IF 1+1 protection group.
B-56
Issue 02 (2009-10-30)
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
l
Default Value HSB
Description
l
This parameter specifies the working mode of the IF 1+1 protection. 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. 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. 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. The FD mode and SD mode are compatible with the HSB switching function. This parameter is set according to the planning information.
Issue 02 (2009-10-30)
B-57
Parameter Revertive Mode
Value Range Revertive Mode Non-Revertive Mode
Default Value Revertive Mode
Description
l
This parameter specifies the revertive mode of the IF 1+1 protection. 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. 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. It is recommended that you set this parameter to Revertive Mode. This parameter specifies the wait-torestore (WTR) time. When the time after the former working channel is restored to normal reaches the set WTR time, a revertive switching occurs. You can set WTR Time(s) only when Revertive Mode is set to Revertive Mode. It is recommended that you use the default value. This parameter indicates whether the reverse switching function is enabled. 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. This parameter is valid only when Working Mode is set to HSB or SD. In normal cases, it is recommended that you set this parameter to Enabled.
WTR Time(s)
300 to 720
600
Enable Reverse Switching
Enabled Disabled
Enabled
Working Board
This parameter specifies the working board of the protection group.
B-58
Issue 02 (2009-10-30)
Parameter Protection Board
Value Range -
Default Value -
Description 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.3.1 Creating an IF 1+1 Protection Group
B.4.6 Parameter Description: IF 1+1 Protection

This topic describes the parameters that are related to IF 1+1 protection.
Navigation Path
Select the NE from the Object Tree in the NE Explorer. Choose Configuration > IF 1+1 Protection from the Function Tree.
Protection Group Parameters

Parameter Protection Group ID Value Range Default Value Description This parameter indicates the ID of the protection group.
Issue 02 (2009-10-30)
B-59
Parameter Working Mode
Value Range HSB FD SD
Default Value HSB
Description
l
This parameter indicates the working mode of the created IF 1+1 protection group. 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. 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. 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. The FD mode and SD mode are compatible with the HSB switching function. This parameter is set according to the planning information. This parameter indicates or specifies the revertive mode of the protection group. 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. 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. It is recommended that you set this parameter to Revertive Mode.
Revertive Mode
Revertive Mode Non-Revertive Mode
Revertive Mode
B-60
Issue 02 (2009-10-30)
Parameter WTR Time(s)
Default Value 600
Description
l
This parameter indicates or specifies the WTR time. When the time after the former working channel is restored to normal reaches the set WTR time, a revertive switching occurs. You can set WTR Time(s) only when Revertive Mode is set to Revertive Mode. It is recommended that you use the default value. This parameter indicates or specifies whether the reverse switching function is enabled. 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. This parameter is valid only when Working Mode is set to HSB or SD. This parameter indicates the switching state on the equipment side. Unknown is displayed when the switching state on the channel side is not queried or not obtained after a query. This parameter indicates the switching state on the channel side. Unknown is displayed when the switching state on the channel side is not queried or not obtained after a query.
Enable Reverse Switching
Enabled Disabled
Enabled
Switching Status of Device
Switching Status of Channel
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, WTR Time(s), and Enable Reverse Switching must be set to the same value at both ends of a radio hop.
Issue 02 (2009-10-30)
B-61

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
B.4.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-62
Issue 02 (2009-10-30)
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
l
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. 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 This parameter is not applicable to the IFU2 board and the IFX2 board.
Issue 02 (2009-10-30)
B-63
Parameter Enable AM
Default Value Disable
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. 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.
NOTE This parameter is not applicable to the IF1 board.
Channel Space
7M 14M 28M 56M
7M
Channel Space indicates the channel spacing of the corresponding radio link. This parameter is set according to the planning information.
Guaranteed Capacity Modulation
QPSK 16QAM 32QAM 64QAM 128QAM 256QAM
QPSK
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. This parameter is valid only when Enable AM is set to Enabled.
B-64
Issue 02 (2009-10-30)
Parameter Full Capacity Modulation
Default Value -
Description 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 Full Capacity Modulation must be higher than Guaranteed E1 Capacity.
This parameter is valid only when Enable AM is set to Enabled.

Manually Specified Modulation
QPSK 16QAM 32QAM 64QAM 128QAM 256QAM
QPSK
This parameter specifies the modulation scheme that the radio link uses for signal transmission. This parameter is valid only when Enable AM is set to Disabled.
Guaranteed E1 Capacity
When Enable AM is set to Enabled, this parameter depends on Channel Space and Guaranteed E1 Capacity and is not configurable. When Enable AM is set to Disabled, this parameter depends on Channel Space and Manually Specified Modulation Mode and is not configurable.
Specified Max E1 Capacity
This parameter specifies the number of E1 services that can be transmitted in the Hybrid work mode.
Issue 02 (2009-10-30)
B-65
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. 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. 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
1 to 4094
This parameter indicates the received ID of the radio link.

NOTE When the radio link becomes faulty, this parameter is displayed as an invalid value.
ATPC Enable Status
Disabled Enabled
Disabled
This parameter specifies whether the ATPC function is enabled. If the APTC function is enabled, the transmit power of the transmitter automatically varies within the specified ATPC range according to the change of the RSL at the receive end. In the case of areas where fast fading severely affects the radio transmission, it is recommended that you set this parameter to Disabled. 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. Set the central value between the ATPC upper threshold and the ATPC lower threshold to a value for the expected receive power. 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
ATPC Upper Threshold(dBm)
-75.0 to -20.0
-45.0
B-66
Issue 02 (2009-10-30)
Parameter ATPC Lower Threshold(dBm)
Value Range -35.0 to -90.0
Default Value -70.0
Description Lower Threshold(dBm) to the difference between the planned central value between the ATPC upper threshold and the ATPC lower threshold and 10 dB. You can set the ATPC upper threshold only when ATPC Automatic Threshold (dBm) is set to Disabled.
ATPC Automatic Threshold Enable
Enabled Disabled
Disabled
This parameter specifies whether the ATPC automatic threshold function is enabled. 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. If this parameter is set to Disabled, you need to manually set ATPC Upper Threshold(dBm) and ATPC Lower Threshold(dBm).
Enable IEEE-1588 Timeslot
Enabled Disabled
Disabled
If the OptiX RTN 950 is interconnected with the packet radio equipment, this parameter is set to Enabled. Otherwise, this parameter is set to Disabled.
Issue 02 (2009-10-30)
B-67
Parameters for Configuring the ODU

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. 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. The difference between the transmit frequencies of both the ends of a radio link should be one T/R spacing. This parameter needs to be set according to the planning information. This parameter indicates the range of the transmit frequency of the ODU. The Range of Frequency(MHz) depends on the specifications of the ODU.
Range of TX Frequency(MHz)
Actual TX Frequency(MHz) Actual RX Frequency(MHz)
This parameter indicates the actual transmit frequency of the ODU. This parameter indicates the actual receive frequency of the ODU.
B-68
Issue 02 (2009-10-30)
Value Range -
Default Value -
Description
l
This parameter specifies the spacing between the transmit frequency and the receive frequency of an ODU to prevent interference between them. 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. 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. 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. The T/R spacing of the ODU should be set to the same value at both the ends of a radio link.
Actual T/R Spacing(MHz) TX Power(dBm)
This parameter indicates the actual T/R spacing of the ODU.

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. This parameter cannot take a value greater than the preset value of Maximum Transmit Power(dBm). The transmit power of the ODU should be set to the same value at both ends of a radio link. 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. This parameter needs to be set according to the planning information. 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
TX High Threshold(dBm)
Issue 02 (2009-10-30)
B-69
Parameter TX Low Threshold (dBm)
Value Range -
Default Value -
Description 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. 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. 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. TX High Threshold(dBm) and TX Low Threshold(dBm) are valid only when the ATPC function is enabled. 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. 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. If the value of the actual receive power of the ODU is greater than the preset value
RX High Threshold(dBm)
B-70
Issue 02 (2009-10-30)
Parameter RX Low Threshold (dBm)
Value Range -
Default Value -
Description of RX High Threshold(dBm), the system does not record it.
Power to Be Received(dBm)
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. When the antenna misalignment indicating function is enabled, if the actual receive power of the ODU exceeds the range of receive power3 dB, the ODU LED of the IF board connected to the ODU is on (yellow) for 300 ms and off for 300 ms repeatedly, indicating that the antenna is not aligned. 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. This parameter needs to be according to the planning.
Issue 02 (2009-10-30)
B-71
Parameter Maximum Transmit Power (dBm)
Value Range -
Default Value -
Description
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. This parameter is set to limit the maximum transmit power of the ODU within this preset range. The maximum transmit power adjusted by using the ATPC function should not exceed this value. 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. If the ATPC function is enabled, the queried actual transmit power may be different from the preset value.
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. When this parameter is set to Mute, the transmitter of the ODU does not work but can normally receive microwave signals. When this parameter is set to Unmute, the ODU can normally transmit and receive microwave signals. In normal cases, it is recommended that you set this parameter to unmute.
Actual TX Status
Unmute Mute
This parameter indicates the actual transmit status of the ODU.
Equipment Information
Parameter Frequency(GHz) Value Range Default Value Description This parameter indicates the frequency band where the ODU operates.
B-72
Issue 02 (2009-10-30)
Parameter Equipment Type
Value Range -
Default Value -
Description
l
This parameter indicates the equipment type of the ODU. PDH and SDH indicate the transmission capacity only and is irrelevant to the type of transmitted service. This parameter indicates whether the ODU is a Tx high station or a Tx low station. The transmit frequency of a Tx high station is one T/R spacing higher than the transmit frequency of a Tx low station.
Station Type
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
A.3.4 Configuring the IF/ODU Information of a Radio Link
B.5 Multiplex Section Protection Parameters

This topic describes the parameters that are related to multiplex section protection (MSP). B.5.1 Parameter Description: Linear MSP_Creation This topic describes the parameters that are used for creating linear MSP groups. B.5.2 Parameter Description: Linear MSP This topic describes the parameters that are related to linear MSP groups.
B.5.1 Parameter Description: Linear MSP_Creation

This topic describes the parameters that are used for creating linear MSP groups.
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.
Issue 02 (2009-10-30)
B-73

Parameter Protection Type Value Range 1+1 Protection 1:N Protection
l
Default Value 1+1 Protection
Description
l
This parameter specifies the protection type of the linear MSP group. 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. 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. If extra services need to be transmitted or several working channels are required, select 1:N Protection. This parameter is set according to the planning information. This parameter specifies the switching mode of the linear MSP. In single-ended mode, the switching occurs only at one end and the state of the other end remains unchanged. In dual-ended mode, the switching occurs at both ends at the same time. If the linear MSP type is set to 1:N Protection, Switching Mode can be set to Dual-Ended Switching only.
Switching Mode
Single-Ended Switching Dual-Ended Switching
Single-Ended Switching (1+1 Protection) Dual-Ended Switching (1:N Protection)
B-74
Issue 02 (2009-10-30)
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. 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. 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. It is recommended that you set this parameter to Revertive. If the linear MSP type is set to 1:N Protection, Revertive Mode can be set to Revertive only. This parameter specifies the WTR time. When the time after the former working channel is restored to normal reaches the preset WTR time, a revertive switching occurs. You can set WTR Time(s) only when Revertive Mode is set to Revertive. It is recommended that you use the default value. The new protocol is supported at the early stage, and the mainstream protocol version is used currently. 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. The new protocol is more mature, and the restructure protocol complies with the standard. It is recommended that you use the new protocol. You must ensure that the interconnected NEs run the protocols of the same type.
WTR Time(s)
300 to 720
600
l l
Protocol Type
New Protocol Restructure Protocol
New Protocol
Issue 02 (2009-10-30)
B-75
Parameter SD Enable
Description
l
This parameter indicates or specifies whether the switching at the SD alarm of the linear MSP is enabled. When this parameter is set to Enabled, the B2_SD alarm is considered as a switching condition. It is recommended that you set this parameter to Enabled.

Parameter Select Mapping Mode 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
This parameter specifies the mapping board and port in the mapping direction. If the protection type is set to 1+1 Protection, only one line port can be mapped as West Working Unit. Only one line port can be mapped as West Protection Unit. 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.4.1 Configuring Linear MSP
B.5.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 1+1 Protection 1:N Protection
l
Default Value -
Description This parameter indicates the ID of the protection group.

l
This parameter indicates the protection type of the linear MSP group. 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. 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. If extra services need to be transmitted or several working channels are required, select 1:N Protection. This parameter indicates or specifies the switching mode of the linear MSP. In single-ended mode, the switching occurs only at one end and the state of the other end remains unchanged. In dual-ended mode, the switching occurs at both ends at the same time. If the linear MSP type is set to 1:N Protection, Switching Mode can be set to Dual-Ended Switching only.
Switching Mode
Single-Ended Switching Dual-Ended Switching
Single-Ended Switching (1+1 Protection) Dual-Ended Switching (1:N Protection)
Issue 02 (2009-10-30)
B-77
Default Value Non-Revertive (1+1 Protection) Revertive (1:N Protection)
Description
l
This parameter indicates or specifies the revertive mode of the linear MSP. 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. 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. It is recommended that you set this parameter to Revertive. If the linear MSP type is set to 1:N Protection, Revertive Mode can be set to Revertive only. This parameter indicates or specifies the WTR time. When the time after the former working channel is restored to normal reaches the preset WTR time, a revertive switching occurs. You can set WTR Time(s) only when Revertive Mode is set to Revertive. It is recommended that you use the default value. This parameter indicates or specifies whether the reverse switching function is enabled. When this parameter is set to Enabled, the B2_SD alarm is considered as a switching condition. It is recommended that you set this parameter to Enabled.
WTR Time(s)
300 to 720
600
SD Enable
Enabled Disabled
Enabled
B-78
Issue 02 (2009-10-30)
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. 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. You must ensure that the interconnected NEs run the protocols of the same type. 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
This parameter indicates the protocol status of the linear MSP.

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
Local Remote
Related Tasks
A.4.2 Querying the Status of the Linear MSP
Issue 02 (2009-10-30)
B-79
B.6 SDH/PDH Service Parameters

This topic describes the parameters that are related to SDH/PDH services. B.6.1 Parameter Description: SDH Service Configuration_Creation This parameter describes the parameters that are used for creating point-to-point crossconnections. B.6.2 Parameter Description: SDH Service Configuration_SNCP Service Creation This topic describes the parameters that are used for creating SNCP services. B.6.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.6.4 Parameter Description: SDH Service Configuration_Converting SNCP Services Into Normal Services This topic describes the parameters that are used for converting SNCP services into normal services. B.6.5 Parameter Description: SDH Service Configuration This topic describes the parameters that are used for configuring SDH services (namely, configuring cross-connections). B.6.6 Parameter Description: SNCP Service Control This topic describes the parameters that are used for controlling SNCP services.
B.6.1 Parameter Description: SDH Service Configuration_Creation

This parameter describes the parameters that are used for creating point-to-point crossconnections.
Navigation Path
l
Select the NE from the Object Tree in the NE Explorer. Choose Configuration > SDH Service Configuration from the Function Tree. Click Create.
B-80
Issue 02 (2009-10-30)
Parameters
Parameter Level Value Range VC12 VC3 VC4
l
Default Value VC12
Description
l
This parameter specifies the level of the service to be created. If the service is an E1 service or a data service that is bound with VC-12 channels, set this parameter to VC12. If the service is a data service that is bound with VC-3 channels, set this parameter to VC3. If all the services on a VC-4 channel pass through the NE, set this parameter to VC4. When this parameter is set to Unidirectional, create only the crossconnections from the service source to the service sink. When this parameter is set to Bidirectional, create the crossconnections from the service source to the service sink and the cross-connections from the service sink to the service source. In normal cases, it is recommended that you set this parameter to Bidirectional.
Direction
Bidirectional Unidirectional
Bidirectional
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. This parameter cannot be set when Source Slot is set to the slot of the tributary board. This parameter indicates the timeslot range of the service source. 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. This parameter is set according to the planning information.
Source Timeslot Range(e.g.1,3-6)
Issue 02 (2009-10-30)
B-81
Parameter Sink Slot Sink VC4
Value Range -
Default Value -
Description 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. This parameter cannot be set when Sink Slot is set to the slot of the tributary board. This parameter specifies the timeslot range of the service sink. 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. This parameter is set according to the planning information. This parameter specifies whether to immediately activate the configured service. To immediately deliver the configured SDH service to the NE, set this parameter to Yes.
Activate Immediately
Yes No
Yes
Related Tasks
B.6.2 Parameter Description: SDH Service Configuration_SNCP Service Creation

This topic describes the parameters that are used for creating SNCP services.
Navigation Path
l
Select the NE from the Object Tree in the NE Explorer. Choose Configuration > SDH Service Configuration from the Function Tree. Click Create SNCP Service.
B-82
Issue 02 (2009-10-30)

Parameter Service Type Direction Value Range SNCP Bidirectional Unidirectional Default Value SNCP Bidirectional Description This parameter indicates that the type of the service to be created is SNCP.
l
When this parameter is set to Unidirectional, create only the crossconnections from the SNCP service source to the SNCP service sink. 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. In normal cases, it is recommended that you set this parameter to Bidirectional. This parameter specifies the level of the SCNP service to be created. If the service is an E1 service or a data service that is bound with VC-12 channels, set this parameter to VC12. If the service is a data service that is bound with VC-3 channels, set this parameter to VC3. If all the services on a VC-4 channel pass through the NE, set this parameter to VC4. This parameter specifies the duration of the hold-off time. 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. If multiple link-based protection schemes, such as SNCP, 1+1 protection, and N+1 protection, are available at the same time, the hold-off time needs to be set to a duration that is longer than the switching duration for the multiple linkbased protection schemes. If only the SNCP scheme is available, it is recommended that you set the hold-off time to 0.
Level
VC12 VC3 VC4
VC12
Hold-off Time (100ms)
0 to 100
Issue 02 (2009-10-30)
B-83
Default Value Non-Revertive
Description
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. If this parameter is set to NonRevertive, the service is not switched from the protection channel to the original working channel. It is recommended that you set this parameter to Revertive. This parameter specifies the WTR time. When the time after the former working channel is restored to normal reaches the preset WTR time, a revertive switching occurs. You can set WTR Time(s) only when Revertive Mode is set to Revertive. It is recommended that you use the default value.
WTR Time(s)
300 to 720
600
l l

l
Sink Slot
This parameter specifies the slot of the service sink.
B-84
Issue 02 (2009-10-30)
Parameter Sink VC4
Value Range -
Default Value -
Description
l
This parameter specifies the number of the VC-4 channel where the service sink is located. This parameter cannot be set when Sink Slot is set to the slot of the tributary board. This parameter specifies the timeslot range of the service sink. 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. This parameter is set according to the planning information. After the Configure SNCP Tangent Ring checkbox is selected, you can quickly configure the SNCP service for the SNCP ring tangent point. In normal cases, it is recommended that you do not select this checkbox. This parameter specifies whether to immediately activate the configured SNCP service. After the Activate Immediately checkbox is selected, you can immediately activate the created SNCP service.
Configure SNCP Tangent Ring
Selected Deselected
Deselected
Selected Deselected
Selected
Related Tasks
A.5.2 Creating Cross-Connections of SNCP Services
B.6.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. Select the NE from the Object Tree in the NE Explorer. Choose Configuration > SDH Service Configuration from the Function Tree.
Issue 02 (2009-10-30)
2. 3.
In Cross-Connection, select the configured SDH service. Right-click and choose Expand to Unidirectional from the shortcut menu. Select the expanded unidirectional service. Right-click and choose Convert to SNCP Service from the shortcut menu.

Parameter Service Type Direction Level Value Range SNCP Unidirectional VC12 VC3 VC4
l
Default Value SNCP Unidirectional VC12
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. If the service is an E1 service or a data service that is bound with VC-12 channels, set this parameter to VC12. If the service is a data service that is bound with VC-3 channels, set this parameter to VC3. If all the services on a VC-4 channel pass through the NE, set this parameter to VC4. This parameter specifies the duration of the hold-off time. 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. If multiple link-based protection schemes, such as SNCP, 1+1 protection, and N+1 protection, are available at the same time, the hold-off time needs to be set to a duration that is longer than the switching duration for the multiple linkbased protection schemes. If only the SNCP scheme is available, it is recommended that you set the hold-off time to 0.
0 to 100
B-86
Issue 02 (2009-10-30)
Default Value Non-Revertive
Description
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. 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. It is recommended that you set this parameter to Revertive. This parameter specifies the WTR time. When the time after the former working channel is restored to normal reaches the preset WTR time, a revertive switching occurs. You can set WTR Time(s) only when Revertive Mode is set to Revertive. It is recommended that you use the default value.
WTR Time(s)
300 to 720
600
l l

l
Issue 02 (2009-10-30)
B-87
Parameter Sink Slot Sink VC4
Value Range -
Default Value -
Description 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. This parameter cannot be set when Sink Slot is set to the slot of the tributary board. This parameter specifies the timeslot range of the service sink. 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. This parameter is set according to the planning information. After the Configure SNCP Tangent Ring checkbox is selected, you can quickly configure the SNCP service for the SNCP ring tangent point. In normal cases, it is recommended that you do not select this checkbox. This parameter specifies whether to immediately activate the configured SNCP service. After the Activate Immediately checkbox is selected, you can immediately activate the created SNCP service.
Selected Deselected
Deselected
Selected Deselected
Selected
Related Tasks
A.5.5 Converting a Normal Service into an SNCP Service
B.6.4 Parameter Description: SDH Service Configuration_Converting SNCP Services Into Normal Services
This topic describes the parameters that are used for converting SNCP services into normal services.
B-88
Issue 02 (2009-10-30)
Navigation Path
1. 2. Select the corresponding board from the Object Tree in the NE Explorer. Choose Configuration > SDH Service Configuration from the Function Tree. In Auto-Created Cross-Connection, select the configured service. Right-click and choose Convert to Non-Protection Service from the shortcut menu.

Parameter Service Type Value Range SNCP Default Value SNCP Description
l
This parameter specifies the SNCP service to be created. If the service is an E1 service or a data service that is bound with VC-12 channels, set this parameter to VC12. If the service is a data service that is bound with VC-3 channels, set this parameter to VC3. If all the services on a VC-4 channel pass through the NE, set this parameter to VC4.
Direction Level
Unidirecitonal VC12 VC3 VC4
Unidirecitonal VC12
This parameter indicates the direction of the SNCP service.

l
This parameter indicates the level of the SNCP service. If the service is an E1 service or a data service that is bound with VC-12 channels, set this parameter to VC12. If the service is a data service that is bound with VC-3 channels, set this parameter to VC3. If all the services on a VC-4 channel pass through the NE, set this parameter to VC4.
Issue 02 (2009-10-30)
B-89
Parameter Hold-off Time (100ms)
Default Value 0
Description
l
This parameter specifies the duration of the hold-off time. 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. If multiple link-based protection schemes, such as SNCP, 1+1 protection, and N+1 protection, are available at the same time, the hold-off time needs to be set to a duration that is longer than the switching duration for the multiple linkbased protection schemes. If only the SNCP scheme is available, it is recommended that you set the hold-off time to 0. 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. 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. It is recommended that you set this parameter to Revertive. This parameter specifies the WTR time. When the time after the former working channel is restored to normal reaches the preset WTR time, a revertive switching occurs. WTR Time(ms) can be set only when Revertive Mode is set to Revertive. It is recommended that you use the default value.
Revertive Mode
Revertive Non-Revertive
Non-Revertive
WTR Time(ms)
l l
Source Slot
B-90
Issue 02 (2009-10-30)
Parameter Source VC4
Value Range -
Default Value -
Description
l
This parameter specifies the number of the VC-4 channel where the service source is located. This parameter cannot be set when Sink Slot is set to the slot of the tributary board. This parameter indicates the timeslot range of the service source. 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. This parameter is set according to the planning information.
Sink Slot Sink VC4

l
This parameter specifies the number of the VC-4 channel where the service sink is located. This parameter cannot be set when Sink Slot is set to the slot of the tributary board. This parameter specifies the timeslot range of the service sink. 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. This parameter is set according to the planning information. After the Configure SNCP Tangent Ring checkbox is selected, you can quickly configure the SNCP service for the SNCP ring tangent point. In normal cases, it is recommended that you do not select this checkbox.
Selected Deselected
Deselected
Issue 02 (2009-10-30)
B-91
Parameter Activate Immediately
Default Value Selected
Description
l
This parameter specifies whether to immediately activate the configured SNCP service. After the Activate Immediately checkbox is selected, the SNCP service is activated immediately.
Related Tasks
A.5.6 Converting an SNCP Service to a Normal Service
B.6.5 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.
Cross-Connection Parameters
l
Default Value -
Description
l
This parameter indicates the level of the service. If the service is an E1 service or a data service that is bound with VC-12 channels, VC12 is displayed. If the service is a data service that is bound with VC-3 channels, VC3 is displayed. 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
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.
B-92
Issue 02 (2009-10-30)
Parameter Activation Status
Value Range Yes No
Default Value -
Description This parameter indicates whether to activate the service. The OptiX RTN 950 does not support this parameter. The OptiX RTN 950 does not support this parameter. The OptiX RTN 950 does not support this parameter. The OptiX RTN 950 does not support this parameter.
Bound Group Number Lockout Status Trail Name Schedule No.
Parameters for Automatically Generated Cross-Connections

l
Default Value -
Description
l
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 950 does not support this parameter. The OptiX RTN 950 does not support this parameter. The OptiX RTN 950 does not support this parameter.
Issue 02 (2009-10-30)
B-93
Related Tasks
A.5.7 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 SNCP 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
Sink
Level
VC12 VC3 VC4
Current Status
This parameter indicates the current switching mode and switching status of the services of the protection group.
B-94
Issue 02 (2009-10-30)
Value Range Revertive Non-Revertive
Default Value -
Description
l
This parameter indicates or specifies the revertive mode of the service. This parameter determines whether to switch the service from the protection channel 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. If this parameter is set to NonRevertive, the service is not switched from the protection channel to the original working channel. It is recommended that you set this parameter to Revertive. This parameter indicates or specifies the WTR time. When the time after the former working channel is restored to normal reaches the preset WTR time, a revertive switching occurs. You can set WTR Time(s) only when Revertive Mode is set to Revertive. It is recommended that you use the default value. This parameter indicates or specifies the duration of the hold-off time. 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. If multiple link-based protection schemes, such as SNCP, 1+1 protection, and N+1 protection, are available at the same time, the hold-off time needs to be set to a duration that is longer than the switching duration for the multiple linkbased protection schemes. If only the SNCP scheme is available, it is recommended that you set the hold-off time to 0.
WTR Time(s)
300 to 720
0 to 100
Issue 02 (2009-10-30)
B-95
Parameter Initiation Condition
Value Range TIM EXC SD UNEQ
Default Value NULL
Description
l
This parameter indicates or specifies the conditions that trigger the protection switching of the service. If TIM is selected, the SNCP service considers the HP_TIM or LP_TIM alarm as an automatic switching condition. If EXC is selected, the SNCP service considers the B3_EXC or BIP_EXC alarm as an automatic switching condition. If SD is selected, the SNCP service considers the B3_SD or BIP_SD alarm as an automatic switching condition. If UNEQ is selected, the SNCP service considers the HP_UNEQ or LP_UNEQ alarm as an automatic switching condition. It is recommended that you set Initiation Condition to the same condition for Working Service and Protection Service. The protection switching conditions in 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 950 does not support this parameter. The OptiX RTN 950 does not support this parameter. This parameter indicates whether the working service or protection service is currently received by the protection group.
Service Grouping Group Type Active Channel
Related Tasks
A.5.3 Configuring the Automatic Switching of SNCP Services A.5.9 Querying the Protection Status of SNCP Services
B-96
Issue 02 (2009-10-30)
B.7 Clock Parameters

This topic describes the parameters that are related to clocks. B.7.1 Parameter Description: Clock Source Priority Table This topic describes the parameters that are related to the priority table of a clock source. B.7.2 Parameter Description: Clock Subnet Setting_Clock Subnet This topic describes the parameters that are related to a clock subnet. B.7.3 Parameter Description: Clock Subnet Setting_Clock Quality This topic describes the parameters that are related clock quality. B.7.4 Parameter Description: Clock Subset Setting_SSM Output Control This topic describes the parameters that are related to SSM output control. B.7.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.7.6 Parameter Description: Clock Source Switching_Clock Source Restoration Parameters This topic describes the parameters that are related to clock source restoration. B.7.7 Parameter Description: Clock Source Switching_Clock Source Switching This topic describes the parameters that are related to the switching conditions of a clock source. B.7.8 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.7.9 Parameter Description: Clock Synchronization Status This topic describes the parameters that are related to the clock synchronization status.
B.7.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 > Clock Source Priority. Click the System Clock Source Priority List tab.
Issue 02 (2009-10-30)
B-97
Parameters
Parameter Clock Source Value Range Default Value Description
l
External clock source 1 indicates the external clock source at the CLK or TIME1 port on the CST or CSH board in physical slot 7. External clock source 2 indicates the external clock source at the CLK or TIME1 port on the CST or CSH board in physical slot 8. The internal clock source is always at the lowest priority and indicates that the NE works in the free-run mode. The clock sources and the corresponding clock source priority levels are determined according to the clock synchronization schemes. This parameter indicates the type of the external clock source signal. This parameter is set according to the external clock signal. In normal cases, the external clock signal is a 2 Mbit/s signal.
External Clock Source Mode
2Mbit/s 2MHz
2Mbit/s
B-98
Issue 02 (2009-10-30)
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. This parameter indicates which bit of the TS0 in odd frames of the external clock signal is used to transmit the SSM. 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.6.1 Configuring the Clock Sources
B.7.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 > Clock Subnet Configuration. Click the Clock Subnet tab.
Issue 02 (2009-10-30)
B-99
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. The NEs that trace the same clock source should be allocated with the same clock subnet ID.
B-100
Issue 02 (2009-10-30)
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. 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. If the SSM protocol is stopped, it indicates that the S1 byte is not used. The NE selects and switches a clock
Issue 02 (2009-10-30)
B-101
Parameter
Value Range
Default Value
Description 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.
B-102
Issue 02 (2009-10-30)
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. 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.6.2 Configuring Clock Subnets
B.7.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 > Clock Subnet Configuration. Click the Clock Quality tab.
Issue 02 (2009-10-30)
B-103
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.
B-104
Issue 02 (2009-10-30)
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. G.811 Reference Clock: the clock signal specified in ITU-T G. 811. 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 ITUT G.812. G.812 Transit Clock: the transit exchange clock signal specified in ITU-T G.812. Between G.812 Transit Clock and G.812 Local Clock: lower than the quality level of the transit exchange clock signal specified in ITUT G.812 but higher than the quality level of the local exchange clock signal specified in ITUT G.812. G.812 Local Clock: the local exchange clock signal specified in ITUT G.812.
Issue 02 (2009-10-30)
B-105
Parameter
Value Range
Default Value
Description
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. SETS Clock: the clock signal of the SETS. 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.6.3 Self-Defined Clock Quality
B.7.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 > Clock Subnet Configuration. Click the SSM Output Control tab.
B-106
Issue 02 (2009-10-30)
Parameters
Parameter Line Port Value Range Default Value Description
l
This parameter indicates the name of the line clock port. 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. This parameter is valid only when the SSM protocol or the extended SSM protocol is started. This parameter indicates whether the SSM is output at the line port. 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.
Control Status
Enabled Disabled
Enabled
Related Tasks
A.6.4 Configuring the SSM Output Status
B.7.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 > Clock Subnet Configuration.
Issue 02 (2009-10-30)
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. 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. This parameter is valid only when the extended SSM protocol is started. This parameter indicates whether the clock source ID is output at the line port. 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.
Enabled Status
Enabled Disabled
Enabled
Related Tasks
A.6.5 Configuring the Clock ID Output Status
B.7.6 Parameter Description: Clock Source Switching_Clock Source Restoration Parameters

This topic describes the parameters that are related to clock source restoration.
B-108
Issue 02 (2009-10-30)
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 NonRevertive, the NE does not automatically switch the clock source to the higher-priority clock source when this higher-priority clock source restores. Correct setting of Clock Source Switching Condition ensures the reliability of the clock source switching. To improve the clock quality, select Auto-Revertive. Otherwise, to prevent jitter of the clock, generally, it is recommended that you set this parameter to Non-Revertive.
Issue 02 (2009-10-30)
B-109
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 unstability of the clock source state within a short time. This parameter is valid only when Higher Priority Clock Source Reversion Mode is set to Auto-Revertive.
Related Tasks
A.6.8 Modifying the Recovery Parameter of the Clock Source
B.7.7 Parameter Description: Clock Source Switching_Clock Source Switching

This topic describes the parameters that are related to the switching conditions of a clock source.
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 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
B-110
Issue 02 (2009-10-30)
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. Lock: A clock source in the priority table is in the locked state. The clock source in the locked state cannot be switched. 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
Related Tasks
A.6.7 Changing the Conditions for Clock Source Switching
B.7.8 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 > Phase-Locked Source Output by External Clock.
Issue 02 (2009-10-30)
B-111
Parameters
Parameter 2M Phase-Locked Source Number Value Range External Clock Source 1 External Clock Source 2 Default Value Description This parameter indicates the number of the external clock source output of the NE.
l
External Clock Output Mode
2Mbit/s 2MHz
2Mbit/s
This parameter specifies the mode of the output clock. 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. This parameter is valid only when External Clock Output Mode is set to 2Mbit/s. This parameter indicates which bit of the TS0 in odd frames of the output clock signal is used to transmit the SSM. If this parameter is set to ALL, it indicates that all the bits of the TS0 are used to transmit the SSM. It is recommended that you use the default value.
External Clock Output Timeslot
SA4 to SA8 ALL
ALL
B-112
Issue 02 (2009-10-30)
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. If this parameter is set to Threshold Disabled, it indicates that the external clock source always outputs the clock signal. It is recommended that you use the default value. This parameter specifies the failure condition of the 2 Mbit/ s phase-locked clock source. It is recommended that you use the default value. This parameter is valid only when 2M PhaseLocked Source Fail Condition is not set to No Failure Condition. 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. 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
2M Phase-Locked Source Fail Action
Shut Down Output 2M Output S1 Byte Unavailable Send AIS
Shut Down Output
Related Tasks
A.6.6 Modifying the Parameters of the Clock Output
B.7.9 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 > 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-114
Issue 02 (2009-10-30)
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. 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. 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.6.9 Querying the Clock Synchronization Status
Issue 02 (2009-10-30)
B-115
B.8 Parameters for Ethernet Services

This topic describes the parameters that are related to Ethernet services.
B.8.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.8.2 Parameter Description: E-Line Service This topic describes the parameters that are related to E-Line services. B.8.3 Parameter Description: VLAN Forwarding Table Item_Creation This topic describes the parameters that are used for creating VLAN forwarding table items. B.8.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.8.5 Parameter Description: E-LAN Service This topic describes the parameters that are related to E-LAN services. B.8.6 Parameter Description: QinQ Link_Creation This topic describes the parameters that are used for creating a QinQ link.
B.8.1 Parameter Description: E-Line Service_Creation

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. The New E-Line Service dialog box is displayed.

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.
Service Name
B-116
Issue 02 (2009-10-30)
Parameter Direction
Value Range UNI-UNI UNI-NNI NNI-NNI
Default Value UNI-UNI
Description
l
This parameter specifies the direction of the E-Line service. This parameter is set according to the planning information. 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. If the BPDU packets are used as the service packets and transparently transmitted to the opposite end, set this parameter to Transparently Transmitted. In other cases, set this parameter to Not Transparently Transmitted. This parameter is set according to the planning information.
BPDU
Not Transparently Transmitted Transparently Transmitted
Not Transparently Transmitted
MTU(byte)
The OptiX RTN 950 does not support this parameter. The OptiX RTN 950 does not support this parameter.
Service Tag Role
Issue 02 (2009-10-30)
B-117
Parameter Source Port
Value Range -
Default Value -
Description
l
This parameter specifies the port of the service source. This parameter is valid only when Direction is set to UNI-UNI or UNI-NNI. 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. The value of this parameter cannot be the same as the value of Sink Port. The value of this parameter cannot be used for the E-LAN port. This parameter is set according to the planning information.
B-118
Issue 02 (2009-10-30)
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. This parameter is valid only when Direction is set to UNI-UNI or UNI-NNI. The number of VLANs must be the same value of Sink VLANs. If this parameter is set to null, all the services at the source port are used as the service source. 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. Uses the QinQ link to carry the E-Line service. This parameter is valid only when Direction is set to UNI-NNI. Selects the QinQ link ID. A QinQ link ID is preset in QinQ Link. This parameter is valid only when Direction is set to UNI-NNI.
Bearer Type
QinQ Link
QinQ Link
QinQ Link ID
Issue 02 (2009-10-30)
B-119
Parameter Bearer Type 1
Value Range QinQ Link
Default Value QinQ Link
Description
l
Uses the QinQ link to carry the E-Line service. This parameter is valid only when Direction is set to NNI-NNI. Selects the QinQ link ID of the first QinQ link. This parameter is valid only when Direction is set to NNI-NNI. The QinQ link ID is preset in QinQ Link. Uses the QinQ link to carry the E-Line service. This parameter is valid only when Direction is set to NNI-NNI. Selects the QinQ link ID of the second QinQ link. This parameter is valid only when Direction is set to NNI-NNI. The QinQ link ID is preset in QinQ Link.
QinQ Link ID 1
Bearer Type 2
QinQ Link
QinQ Link
QinQ Link ID 2
B-120
Issue 02 (2009-10-30)
Parameter Sink Port
Value Range -
Default Value -
Description
l
This parameter specifies the port of the service sink. 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. The value of this parameter cannot be the same as the value of Source Port. The value of this parameter cannot be used for the E-LAN port. This parameter is set according to the planning information.
Issue 02 (2009-10-30)
B-121
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. The number of VLANs must be the same value of Source VLANs. If this parameter is set to null, all the services at the sink port are used as the service sink. 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.
B.8.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. This parameter indicates or specifies the name of the E-Line service.
Issue 02 (2009-10-30)
Service Name
B-122
Parameter Source Node Sink Node Service Tag Role
Value Range -
Default Value -
Description This parameter indicates the source node. This parameter indicates the sink node. The OptiX RTN 950 does not support this parameter. The OptiX RTN 950 does not support this parameter.
l
MTU(byte)
1518 to 9600
BPDU
Not Transparently Transmitted Transparently Transmitted
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. If the BPDU packets are used as the service packets and transparently transmitted to the opposite end, set this parameter to Transparently Transmitted. If the BPDU packets are used as the protocol packets to compute the spanning tree topology of the network, set this parameter to Not Transparently Transmitted.
Active
Active Inactive
This parameter indicates whether E-Line service is active.
Issue 02 (2009-10-30)
B-123
Parameters for the User Network Interface (UNI)

Parameter Port VLANs Value Range 1 to 4094 Default Value Description This parameter indicates the UNI port. 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. This parameter is valid only when Direction is set to UNI-UNI or UNI-NNI in the process of creating an E-Line service. If this parameter is set to null, all the services of the UNI work as the service source or service sink. 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-124
Issue 02 (2009-10-30)
Parameters for the Network Node Interface (NNI)

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. This parameter is valid only when Direction is set to UNI-UNI or UNI-NNI in the process of creating an E-Line service. This parameter indicates the NNI port. This parameter is valid only when Direction is set to UNI-UNI or UNI-NNI in the process of creating an E-Line service. This parameter indicates or specifies the VLAN ID of the NNI port. This parameter is valid only when Direction is set to UNI-NNI or NNI-NNI in the process of creating an E-Line service. This parameter is preset in QinQ Link.
Port
S-VLAN ID
Parameters for the Port Attributes

Parameter Port Value Range Default Value Description This parameter indicates the QinQ link ID of the QinQ link connected to the port.
Issue 02 (2009-10-30)
B-125
Parameter Enable Port
Value Range -
Default Value -
Description
l
This parameter indicates whether to enable the port. This parameter is preset in General Attributes of Ethernet Interface. This parameter indicates the encapsulation type of the port. This parameter is valid only when Direction is set to UNI-UNI or UNI-NNI in the process of creating an E-Line service. If this parameter is set to Null, the port transparently transmits the received packets. If this parameter is set to 802.1Q, the port identifies the packets that comply with the IEEE 802.1Q standard. If this parameter is set to QinQ, the port identifies the packets that comply with the IEEE 802.1 QinQ standard. This parameter is preset in General Attributes of Ethernet Interface. This parameter indicates the tag of the port. This parameter is preset in Layer 2 Attributes of Ethernet Interface .
Encapsulation Type
Null 802.1Q QinQ
TAG
Tag Aware Access Hybrid
B-126
Issue 02 (2009-10-30)
B.8.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
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. 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. In normal cases, Ethernet services are bidirectional. Hence, you need to set bidirectional conversion of VLAN IDs.
B.8.4 Parameter Description: E-LAN Service_Creation

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. The New E-LAN Service dialog box is displayed.

Parameter Service ID Value Range 1 to 4294967294 Default Value Description
l
This parameter specifies the ID of the E-LAN service. The OptiX RTN 950 supports simultaneous creation of an E-LAN service only.
Service Name
This parameter specifies the name of the E-LAN service.

l
BPDU
This parameter indicates the transparent transmission tag of the BPDU packets. In the case of an ELAN service, this parameter supports only transparent transmission of the BPDU packets and cannot be set manually. Not Transparently Transmitted indicates that the BPDU packets are used as the protocol packets to compute the spanning tree topology of the network.
B-128
Issue 02 (2009-10-30)
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. 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. 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. This parameter is set according to the planning information. This parameter specifies whether to enable the MAC address self-learning function. 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.
Self-Learning MAC Address
Enabled
Enabled
Issue 02 (2009-10-30)
B-129
Parameter MAC Address Learning Mode
Value Range -
Default Value -
Description
l
This parameter indicates the mode used to learn an MAC address. 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.
MTU(byte)
Service Tag Role
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. This parameter is valid only when Tag Type is set to S-Awared. This parameter is set according to the planning information.
B-130
Issue 02 (2009-10-30)
Parameter VLANs/CVLAN
Default Value -
Description
l
This parameter specifies the VLAN ID of the UNI port. 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. If this parameter is set to null, all the services of the UNI work as the service source or service sink. 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.
Parameters of NNIs
Parameter Port Value Range Default Value Description
l
This parameter indicates the NNI port. This parameter is valid only when Tag Type is set to S-Awared. This parameter specifies the S-VLAN ID of the NNI port. This parameter is valid only when Tag Type is set to S-Awared.
SVLANs
Issue 02 (2009-10-30)
B-131
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. The default split horizon group ID is 1 and cannot be set manually. A split horizon group member indicates the logical port member in the split horizon group. The port members that are added to the same split horizon group cannot communicate with each other. The OptiX RTN 950 supports only the division of the split horizon group members according to the Ethernet physical port. 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.
Split Horizon Group Member
B.8.5 Parameter Description: E-LAN Service

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-132
Issue 02 (2009-10-30)

Parameter Service ID Value Range 1 to 4294967294 Default Value Description
l
This parameter indicates the ID of the E-LAN service. The supports simultaneous creation of an E-LAN service only.
Service Name
This parameter specifies the name of the E-LAN service.

l
BPDU
This parameter indicates the transparent transmission tag of the BPDU packets. In the case of an ELAN service, this parameter supports only transparent transmission of the BPDU packets and cannot be set manually. Not Transparently Transmitted indicates that the BPDU packets are used as the protocol packets to compute the spanning tree topology of the network.
Issue 02 (2009-10-30)
B-133
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. 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. 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. This parameter indicates whether to enable the MAC address self-learning function. 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.
Self-Learning MAC Address
Enabled
Enabled
B-134
Issue 02 (2009-10-30)
Parameter MAC Address Learning Mode
Value Range -
Default Value -
Description
l
This parameter indicates the mode used to learn an MAC address. 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.
MTU(byte)
Service Tag Role
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. This parameter is valid only when Tag Type is set to S-Awared. This parameter is set according to the planning information.
Issue 02 (2009-10-30)
B-135
Parameter VLANs/CVLAN
Default Value -
Description
l
This parameter specifies the VLAN ID of the UNI port. 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. 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. 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.
Parameters for NNIs

Parameter Port Value Range Default Value Description
l
This parameter indicates the NNI port. This parameter is valid only when Tag Type is set to S-Awared.
B-136
Issue 02 (2009-10-30)
Parameter SVLANs
Value Range -
Default Value -
Description
l
This parameter specifies the S-VLAN ID of the UNI port. This parameter is valid only when Tag Type is set to S-Awared. 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.
Parameters for the Port Attributes

Parameter Port Enable Port Value Range Enabled Disabled Default Value Description This parameter indicates the bound port. The corresponding port can normally carry the services only when this parameter is set to Enabled.
Issue 02 (2009-10-30)
B-137
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. If this parameter is set to Null, the port transparently transmits the received packets. If this parameter is set to 802.1Q, the port identifies the packets that comply with the IEEE 802.1Q standard. If this parameter is set to QinQ, the port identifies the packets that comply with the IEEE 802.1 QinQ standard. If all the accessed services are frames with the VLAN tag (tagged frames), set this parameter to "Tag Aware". If all the accessed services are frames without the VLAN tag (untagged frames), set this parameter to "Access". If the accessed services contain tagged frames and untagged frames, set this parameter to "Hybrid".
TAG
Tag Aware Access Hybrid
Tag Aware
B-138
Issue 02 (2009-10-30)
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. The default split horizon group ID is 1 and cannot be set manually. A split horizon group member indicates the logical port member in the split horizon group. The port members that are added to different split horizon groups cannot communicate with each other. The supports only the division of the split horizon group members according to the Ethernet physical port. 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.
Split Horizon Group Member
Issue 02 (2009-10-30)
B-139
Parameters for Static MAC Addresses

Parameter VLAN ID Value Range Default Value 1 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. 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. This parameter is set according to the planning information. This parameter indicates or specifies the static MAC address. A static MAC address is an address that is set manually. It is not aged automatically and needs to be deleted manually. 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. This parameter specifies the Ethernet port that corresponds to the MAC address. This parameter is set according to the planning information.
MAC Address
Egress Interface
B-140
Issue 02 (2009-10-30)
Parameters for Self-Learning MAC Address

Parameter VLAN ID Value Range Default Value 1 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. 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. This parameter is set according to the planning information. This parameter indicates or specifies the self-learning MAC address. A selflearning MAC address is also called a dynamic MAC address. The bridge uses the SVL or IVL mode to obtain the entries. A self-learning MAC address can be aged. This parameter specifies the Ethernet port that corresponds to the MAC address. This parameter is set according to the planning information.
MAC Address
Egress Interface
Issue 02 (2009-10-30)
B-141
Parameters for Disabled MAC Addresses

Parameter VLAN ID Value Range Default Value 1 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.
l
MAC Address
This parameter specifies or indicates the disabled MAC address. A disabled MAC address is also called a blacklisted MAC address. 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 1 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.
B-142
Issue 02 (2009-10-30)
Maintenance Association Parameters

Parameter Maintenance Domain Name Maintenance Association Name Value Range Default Value Description This parameter indicates the maintenance domain of the created maintenance association.
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. This parameter can contain a maximum of eight bytes. This parameter specifies the interval for transmitting packets in the CC test. The CC is performed to check the availability of the service.
CC Test Transmit Period(ms)
1s 10s 1m 10m
1s
Parameters for the MEP

Parameter Maintenance Domain Name Maintenance Association Name Node VLAN MP 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 l
This parameter specifies the MEP ID. 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. This parameter specifies the direction of the MEP. "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.
Direction
Ingress Egress
Ingress
Issue 02 (2009-10-30)
B-143
Parameter CC Status
Value Range Active Inactive
Default Value Active
Description
l
This parameter specifies whether to enable the CC function of the MEP. In the case of the tests based on the MP IDs, CC Status must be set to Active.
B.8.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. The New QinQ Link dialog box is displayed.
Parameters for the General Attributes

Parameter QinQ Link ID Board Value Range 1 to 4294967295 Default Value Description This parameter specifies the ID of the QinQ link. This parameter specifies the board where the QinQ link is located. This parameter specifies the port where the QinQ link is located.
l
Port
S-Vlan ID
1 to 4094
This parameter specifies the VLAN ID (at the network operator side) for the QinQ link. This parameter is set according to the planning information.
B.9 Ethernet Protocol Parameters

This topic describes the parameters that are related to the Ethernet protocol.
B-144
Issue 02 (2009-10-30)
B.9.1 Parameter Description: ERPS Management_Creation This topic describes the parameters that are used for creating ERPS management tasks. B.9.2 Parameter Description: ERPS Management This topic describes the parameters that are used for Ethernet ring protection switching (ERPS) management. B.9.3 Parameter Description: MSTP Configuration_Port Group Creation This topic describes the parameters that are used for creating MSTP port groups. B.9.4 Parameter Description: MSTP Configuration_Port Group Configuration This topic describes the parameters that are used for creating MSTP port groups. B.9.5 Parameter Description: MSTP Configuration_ Bridge Parameters This topic describes the parameters that are related to MSTP bridges. B.9.6 Parameter Description: MSTP Configuration_CIST Parameters This topic describes the parameters that are related to the MSTP CIST. B.9.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.9.8 Parameter Description: IGMP Snooping Configuration_Protocol Configuration This topic describes the parameters that are used for configuring the IGMP snooping protocol. B.9.9 Parameter Description: IGMP Snooping Configuration_Adding Port to Be Quickly Deleted This topic describes the parameters that are used for adding a port to be quickly deleted. B.9.10 Parameter Description: IGMP Snooping Configuration_Route Management This topic describes the parameters that are used for IGMP Snooping protocol route management. B.9.11 Parameter Description: IGMP Snooping Configuraiton_Static Router Port Creation This topic describes the parameters that are used for adding static router ports. B.9.12 Parameter Description: IGMP Snooping Configuration_Route Member Port Management This topic describes the parameters that are used for managing the route member ports of the IGMP Snooping protocol. B.9.13 Parameter Description: IGMP Snooping Configuration_Static Multicast Group Member Creation This topic describes the parameters that are used for adding static multicast groups. B.9.14 Parameter Description: IGMP Snooping Configuration_Data Statistics This topic describes the parameters that are used for collecting the data statistics of the IGMP Snooping protocol. B.9.15 Parameter Description: Ethernet Link Aggregation Management_LAG Creation This topic describes the parameters that are used for creating a link aggregation group (LAG). B.9.16 Parameter Description: Ethernet Link Aggregation_Port Priority This topic describes the parameters that are related to the port priority of a LAG. B.9.17 Parameter Description: LPT Management_Creation This parameter describes the parameters that are used for creating LPT management. B.9.18 Parameter Description: Port Mirroring_Creation
This topic describes the parameters that are used for creating port mirroring tasks.
B.9.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.
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. The ERPS ID must be unique.
East Port
This parameter specifies the east port of the ERPS instance. This parameter specifies the west port of the ERPS instance.
l
West Port
RPLOwner Ring Node Flag
Yes No
No
This parameter specifies whether the node on the ring is the ring protection link (RPL) owner. Only one node on the ring can be set as the RPL owner for each Ethernet ring.
RPL Port
This parameter specifies the RPL port.
B-146
Issue 02 (2009-10-30)
Parameter Control VLAN
Default Value -
Description
l
This parameter specifies the VLAN ID of Control VLAN. 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.
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.7.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.
Issue 02 (2009-10-30)
B-147
Parameters
Parameter ERPS ID Value Range 1 to 8 Default Value Description
l
This parameter specifies the ID of the ERPS instance. The ERPS ID must be unique.
East Port
This parameter specifies the east port of the ERPS instance. This parameter specifies the west port of the ERPS instance.
l
West Port
RPL Owner Ring Node Flag
Yes No
No
This parameter specifies whether a node on the ring is the ring protection link (RPL) owner. Only one node on the Ethernet ring can be set as the RPL owner.
RPL Port Control VLAN
1 to 4094
This parameter specifies the RPL port.

l
This parameter specifies the VLAN ID of Control VLAN. Each node on the Ethernet ring transmits the Ring-APS (R-APS) packets on the dedicated R-APS channel to ensure consistency between the nodes when the ERPS switching is performed. Control VLAN is used for isolating the dedicated R-APS channel. Therefore, the VLAN ID in Control VLAN cannot be the same as the VLAN IDs that are contained in the service packets or inband DCN packets.
B-148
Issue 02 (2009-10-30)
Parameter Destination Node
Value Range 01-19-A7-00-00-01
Default Value 01-19-A7-00-00-01
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
Hold-Off Time(ms)
0 to 10000, in step of 100
This parameter specifies the hold-off time of the ERPS holdoff timer. 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 holdoff 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 hold-off timer times out, the node checks the link status regardless whether the fault that triggers the startup of the timer exists. If the fault exists, the node reports it to trigger an ERPS. This fault can be the same as or different from the fault that triggers the initial startup of the hold-off timer.
Issue 02 (2009-10-30)
B-149
Parameter Guard Time(ms)
Value Range 10 to 2000, in step of 10
Default Value 500
Description
l
This parameter specifies the guard time of the ERPS guard timer. 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 RAPS 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-150
Issue 02 (2009-10-30)
Parameter WTR Time(min)
Default Value 5
Description
l
This parameter specifies the WTR time of the WRT timer in the case of ERPS protection. 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. The WTR timer is used to prevent frequent switching caused by the unstable working channel.
Packet Transmit Interval(s)
1 to 10
This parameter specifies the interval for transmitting the R-APS packets. This parameter specifies the level of the maintenance entity. This parameter indicates the last switching request.
Entity Level
0 to 7
Last Switching Request
Issue 02 (2009-10-30)
B-151
Parameter RB Status
Value Range -
Default Value -
Description This parameter indicates the RB status of the packets received by the working node.
l
noRB: The RPL is not blocked. RB (RPL Blocked): 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. 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-152
Issue 02 (2009-10-30)
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 receive the R_APS (NR, RB) packets. Protection: The Ethernet ring is in protected state. For example, a node on the ring is in the WTR period, because the fault on the node triggers the ERPS or the fault is rectified.
Node Carried with Current Packet
This parameter 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.
Related Tasks
A.7.2 Setting the Parameters of Ethernet Ring Protocol A.7.3 Querying the Status of the Ethernet Ring Protocol
B.9.3 Parameter Description: MSTP Configuration_Port Group Creation

This topic describes the parameters that are used for creating MSTP port groups.
Navigation Path
1. 2. 3.
Issue 02 (2009-10-30)
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 950 supports the CIST MSTP only. STP: stands for Spanning Tree Protocol. This parameter specifies whether to enable the protocol of the port group or a member port in the port group. If the STP or MSTP is enabled, the spanning tree topology is automatically reconfigured. As a result, the services are interrupted.
Enable Protocol
Enabled Disabled
Disabled
Parameters for Application Ports

Parameter Board Value Range Default Value Description This parameter specifies the board where the 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.8.1 Creating the MSTP Port Group
B.9.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 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.8.7 Modifying the Configuration Data of the MSTP Port Group
B.9.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.
Issue 02 (2009-10-30)
B-155

Parameter Port Group ID Value Range Default Value Description
l
This parameter indicates the ID of the port group. This parameter can be set to only the port group ID that is automatically allocated.
MST Domain Name
The OptiX RTN 950 does not support this parameter. The OptiX RTN 950 does not support this parameter. The OptiX RTN 950 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. This parameter can be set to only the port Group ID that is automatically allocated. This parameter specifies the interval for transmitting the CBPDU packets through the bridge. The greater the value of this parameter, the less the network resources that are occupied by the spanning tree. The topology stability, however, decreases.
Hello Time(s)
1 to 10
B-156
Issue 02 (2009-10-30)
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. 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. This parameter specifies the holdoff time of a port in the listening state and in the learning state. 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.
Forward Delay(s)
4 to 30
15
Port Parameters
Parameter Port Value Range Default Value Description This parameter indicates the port in the port group.
Issue 02 (2009-10-30)
B-157
Parameter Enable Edge Attribute
Description
l
This parameter specifies the management edge attributes of the port. 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. An edge port only receives BPDU packets. 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.
B-158
Issue 02 (2009-10-30)
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. false: forced nonpoint-to-point link attribute true: forced point-topoint link attribute auto: automatically detected point-to-point link attribute 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 halfduplex, Actual Pointto-Point Attribute is false. Only the port whose Actual Point-to-Point Attribute is true can transmit the fast transition request and response messages. 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.
Issue 02 (2009-10-30)
B-159
Parameter Max Transmit Packet Count
Default Value 3
Description
l
This parameter specifies the maximum number of packets to be transmitted. 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 the interval time of transmitting the hello packets. This parameter needs to be set according to the planning information.
Related Tasks
A.8.2 Setting the Bridge Parameters of the MSTP
B.9.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 that the OptiX RTN 950 supports only the MSTP that uses common and internal spanning tree (CIST).
Issue 02 (2009-10-30)
B-160
Parameter Bridge Priority
Default Value 32768
Description
l
The most significant 16 bits of the bridge ID indicates the priority of the bridge. When the value is smaller, the priority is higher. As a result, the bridge is more possible to be selected as the root bridge. 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.
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. When the value is smaller, the priority is higher. This parameter indicates the status of the network that the port is connected to. In the case of the bridges on both ends of the path, set this parameter to the same value.
Path Cost
1 to 200000000
200000
Related Tasks
A.8.3 Setting the Parameters of the CIST
Issue 02 (2009-10-30)
B-161
B.9.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
l
Description This parameter indicates the ID of the port group.

l
This parameter indicates the running mode of the protocol. MSTP: stands for Multiple Spanning Tree Protocol. The OptiX RTN 950 supports only the CIST-based MSTP. STP: stands for Spanning Tree Protocol.
B-162
Issue 02 (2009-10-30)
Parameter Bridge Priority
Default Value 32768
Description
l
This parameter indicates the priority of the bridge. The most significant 16 bits of the bridge ID indicates the priority of the bridge. When the value is smaller, the priority is higher. As a result, the bridge is more possible to be selected as the root bridge. 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 950 does not support this parameter. The OptiX RTN 950 does not support this parameter. The OptiX RTN 950 does not support this parameter. The OptiX RTN 950 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
Issue 02 (2009-10-30)
B-163
Parameter Root Port Priority
Default Value 128
Description
l
This parameter indicates the priority of the root port. The most significant eight bits of the ID of the root port indicate the priority of the root port. When the value is smaller, the priority is higher.
Root Port Hello Time(s)
1 to 10
This parameter indicates the root port.

l
This parameter indicates the interval for transmitting CBPDU packets through the bridge. The greater the value of this parameter, the less the network resources that are occupied by the spanning tree. The topology stability, however, decreases. This parameter specifies the maximum age of the CBPDU packet that is recorded by the port. 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.
Max Age(s)
6 to 40
20
B-164
Issue 02 (2009-10-30)
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. 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 950 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
Issue 02 (2009-10-30)
B-165
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 Learning: only receives or transmits BPDU packets Forwarding: forwards user traffic, and transmits/receives BPDU packets The most significant eight bits of the port ID indicate the port priority. When the value is smaller, the priority is higher. This parameter indicates the status of the network that the port is connected to. In the case of the bridges on both ends of the path, set this parameter to the same value. The most significant 16 bits of the bridge ID indicates the priority of the bridge. When the value is smaller, the priority is higher. As a result, the bridge is more possible to be selected as the root bridge. 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.
Priority
0 to 240, in step of 16
128
Path Cost
1 to 200000000
200000
Bridge Priority
0 to 61440, in step of 4096
32768
B-166
Issue 02 (2009-10-30)
Parameter Bridge MAC Address
Value Range -
Default Value -
Description This parameter indicates the MAC address of the bridge.

l
Designated Port Priority
128
The most significant eight bits of the port ID indicate the port priority. When the value is smaller, the priority is higher.
Design Port Edge Port Attribute
Disabled Enabled
Enabled
This parameter indicates the designated port.

l
This parameter specifies the management edge attributes of the port. 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. An edge port only receives BPDU packets. 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
This parameter indicates the actual management edge attributes of the port.
Issue 02 (2009-10-30)
B-167
Parameter Point to Point
Value Range false true auto
Default Value auto
Description
l
This parameter specifies the point-topoint attribute of the port. false: forced nonpoint-to-point link attribute true: forced point-topoint link attribute auto: automatically detected point-to-point link attribute 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 halfduplex, Actual Point to Point Attribute is false. Only the port whose Actual Point-to-Point Attribute is true can transmit the fast transition request and response messages. 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.
B-168
Issue 02 (2009-10-30)
Parameter Max Count of Transmitting Message
Default Value 3
Description
l
This parameter indicates the maximum number of packets to be transmitted. 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 each hello time. This parameter indicates the running mode of the protocol. MSTP: stands for Multiple Spanning Tree Protocol. The OptiX RTN 950 supports only the CIST-based MSTP. STP: stands for Spanning Tree Protocol. This parameter indicates the interval for transmitting the CBPDU packets through the bridge. The greater the value of this parameter, the less the network resources that are occupied by the spanning tree. The topology stability, however, decreases.
Protocol Running Mode
STP MSTP
Hello Time(s)
1 to 10
Issue 02 (2009-10-30)
B-169
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. 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. This parameter specifies the holding time of a port in the listening state and in the learning state. 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.
Forward Delay(s)
4 to 30
15
Remain Hop
The OptiX RTN 950 does not support this parameter.
Related Tasks
A.8.4 Querying the CIST Running Information
B.9.8 Parameter Description: IGMP Snooping Configuration_Protocol Configuration

This topic describes the parameters that are used for configuring the IGMP snooping protocol.
B-170
Issue 02 (2009-10-30)
Navigation Path
1. 2. Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Ethernet Protocol Configuration > IGMP Snooping Configuration from the Function Tree. Click the Protocol Configuration tab.

Parameter Service ID Enabled Protocol Value Range Enabled Disabled Default Value Disabled Description This parameter indicates the service ID.
l
This parameter specifies whether to enable the IGMP Snooping protocol. If the bridge accesses a LAN where the IGMP multicast server exists, you can enable the IGMP Snooping protocol according to the requirement.
Issue 02 (2009-10-30)
B-171
Parameter Router Port Aging Time (min)
Default Value 8
Description
l
If an entry is not updated in a certain period (that is, no IGMP query packet from this multicast address is received), this entry is automatically deleted. This mechanism is called aging, and this period is called aging time. If this parameter is set to a very large value, the bridge stores excessive multicast entries that are outdated. Consequently, the resources of the multicast table are exhausted. If this parameter is set to a very small value, the bridge may delete the multicast entry that is required. Consequently, the forwarding efficiency decreases.
B-172
Issue 02 (2009-10-30)
Parameter Maximum Times of No Response from Multicast Members
Value Range 1 to 4
Default Value 3
Description
l
This parameter specifies the maximum number of multicast group members who do not respond. If the IEEE 802.1q bridge transmits an IGMP group query packet to the multicast member ports, the IEEE 802.1q bridge starts the timer for the query of the maximum number of responses. If no IGMP report packets are received within the query time, the IEEE 802.1q bridge adds one to the number of no responses at the port. When the number of no responses exceeds the preset value of Maximum Times of No Response from Multicast Members, the IEEE 802.1q bridge deletes the additional multicast members from the multicast group. This parameter specifies the maximum number of allowable multicast groups. The multicast group records the mapping relations between the ports on the router, MAC multicast addresses, and member ports in the multicast group.
Maximum Number of Multicast Groups
Issue 02 (2009-10-30)
B-173
Parameter Maximum Number of Multicast Group Members
Value Range -
Default Value -
Description
l
This parameter specifies the maximum number of allowable multicast group members. A multicast group member refers to the NE that is added to a multicast group.
Actual Multicast Count
This parameter indicates the number of actually used multicast groups. This parameter indicates the number of actually used multicast group members.
Actual Multicast Members Count
Related Tasks
A.9.1 Configuring the IGMP Snooping Protocol
B.9.9 Parameter Description: IGMP Snooping Configuration_Adding Port to Be Quickly Deleted

This topic describes the parameters that are used for adding a port to be quickly deleted.
Navigation Path
1. 2. 3. Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Ethernet Protocol Configuration > IGMP Snooping Configuration from the Function Tree. Click the Protocol Configuration tab. Click Add.
Parameters for Fast Leave Ports

Parameter Service ID Value Range Default Value Description This parameter indicates the service ID.
B-174
Issue 02 (2009-10-30)
Parameter VLAN ID
Default Value 1
Description
l
This parameter specifies the VLAN where the port to be quickly deleted is located. This parameter needs to be set according to the planning information. This parameter specifies the type of the port to be quickly deleted. This parameter needs to be set according to the planning information.
Port Type
V-UNI V-NNI
V-UNI
Port
This parameter specifies the port to be quickly deleted.
Related Tasks
A.9.6 Adding a Quickly Deleted Port
B.9.10 Parameter Description: IGMP Snooping Configuration_Route Management

This topic describes the parameters that are used for IGMP Snooping protocol route management.
Navigation Path
1. 2. Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Ethernet Protocol Configuration > IGMP Snooping Configuration from the Function Tree. Click the Router Port Management tab.
Parameters for Router Port Management

Parameter Service ID Value Range Default Value Description This parameter specifies the ID of the created ELAN service.
Issue 02 (2009-10-30)
B-175
Parameter VLAN ID
Value Range 1
Default Value 1 to 4094
Description
l
This parameter indicates the VLAN ID of the router port. The value of this VLAN ID should be the same as the value of VLANs/CVLAN for the V-UNI port in the E-LAN service.
Port Type Port Port Status
This parameter indicates the type of the router port. This parameter indicates the router port. This parameter indicates the status of the router port. This parameter indicates the time when the router port is created. This parameter indicates the remaining aging time of the router port.
Port Creating Time
Port Remainder Aging Time(min)
Related Tasks
A.9.2 Querying the Port Information of the Routers
B.9.11 Parameter Description: IGMP Snooping Configuraiton_Static Router Port Creation

This topic describes the parameters that are used for adding static router ports.
Navigation Path
1. 2. 3. Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Ethernet Protocol Configuration > IGMP Snooping Configuration from the Function Tree. Click the Router Port Management tab. Click New.
B-176
Issue 02 (2009-10-30)
Parameters for Router Port Creation

l
VLAN ID
1 to 4094
This parameter indicates the VLAN ID of the router port. The value of this VLAN ID should be the same as the value of VLANs/CVLAN for the V-UNI port in the E-LAN service.
Available Port Selected Port
This parameter indicates the available ports.

l
This parameter indicates the specified router port. A router port refers to the port that is connected to the multicast router. It functions as the V-UNI port in the E-LAN service. This parameter needs to be set according to the planning information.
Related Tasks
B.9.12 Parameter Description: IGMP Snooping Configuration_Route Member Port Management

This topic describes the parameters that are used for managing the route member ports of the IGMP Snooping protocol.
Navigation Path
1. 2.
Issue 02 (2009-10-30)
Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Ethernet Protocol Configuration > IGMP Snooping Configuration from the Function Tree. Click the Route Member Port Management tab.
Parameters for Multicast Groups Information

l
VLAN ID
1 to 4094
This parameter indicates the VLAN ID of the router port. The value of this VLAN ID should be the same as the value of SVLAN for the V-NNI port in the E-LAN service.
Multicast MAC Address
This parameter indicates the multicast MAC address. This parameter indicates the type of the multicast group. This parameter indicates the time when the multicast group is set up.
Multicast Groups Type
Multicast Group Creating Time
Parameters for Multicast Group Members Information

l
VLAN ID
1 to 4094
This parameter indicates the VLAN ID of the multicast group member. The value of this VLAN ID should be the same as the value of SVLAN for the V- NNI port in the E-LAN service.
Port Type
This parameter indicates the type of the multicast group member.
B-178
Issue 02 (2009-10-30)
Parameter Port
Value Range -
Default Value -
Description This parameter indicates the multicast group member port. This parameter indicates the remaining aging times of the multicast group member port.
Port Remainder Aging Times
Related Tasks
A.9.3 Querying the Information About the Multicast Groups
B.9.13 Parameter Description: IGMP Snooping Configuration_Static Multicast Group Member Creation
This topic describes the parameters that are used for adding static multicast groups.
Navigation Path
1. 2. 3. Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Ethernet Protocol Configuration > IGMP Snooping Configuration from the Function Tree. Click the Route Member Port Management tab. Click New.
Parameters for Router Port Creation

l
VLAN ID
1 to 4094
This parameter specifies the VLAN ID of the router port. The value of this VLAN ID should be the same as the value of SVLANs for the VUNI port in the E-LAN service.
Multicast MAC Address
This parameter specifies the multicast MAC address. This parameter indicates the available interfaces.
B-179
Available Port
Issue 02 (2009-10-30)
Parameter Selected Port
Value Range -
Default Value -
Description
l
This parameter indicates the preset port of the multicast group members The multicast group member port refers to a port that is connected to the multicast group member. This port is a V-NNI port in the ELAN service. This parameter needs to set according to the planning information.
Related Tasks
A.9.5 Creating a Member of a Static Multicast Group
B.9.14 Parameter Description: IGMP Snooping Configuration_Data Statistics

This topic describes the parameters that are used for collecting the data statistics of the IGMP Snooping protocol.
Navigation Path
1. 2. Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Ethernet Protocol Configuration > IGMP Snooping Configuration from the Function Tree. Click the Packet Statistics tab.
Parameters for Routing Member Interface Management

Parameter Service ID VLAN ID Value Range Default Value Description This parameter indicates the service ID. This parameter indicates the VLAN ID of the service.
Port Type Port
This parameter indicates the port.
B-180
Issue 02 (2009-10-30)
Parameter Packet Statistics Status
Value Range -
Default Value -
Description This parameter indicates or specifies the status of collecting the packet statistics. This parameter indicates the number of received IGMPv1 query packets. This parameter indicates the number of received IGMPv2 query packets. This parameter indicates the number of received IGMPv3 query packets. This parameter indicates the number of received packets showing that the IGMP is transmitted from the multicast group. This parameter indicates the number of received packets that are reported by the IGMPv1 members. This parameter indicates the number of received packets that are reported by the IGMPv2 members. This parameter indicates the number of received packets that are reported by the IGMPv3 members. This parameter indicates the number of packets that cannot be recognized or processed. This parameter indicates the number of discarded error packets.
IGMPv1 Query Packet Count IGMPv2 Query Packet Count IGMPv3 Query Packet Count IGMP Leaving Packet Count
IGMPv1 Member Report Packet Count
Unrecognized or Unprocessed Packet Count Discarded Incorrect Packet Count
Related Tasks
A.9.7 Calculating IGMP Packets
Issue 02 (2009-10-30)
B-181
B.9.15 Parameter Description: Ethernet Link Aggregation Management_LAG Creation

This topic describes the parameters that are used for creating a link aggregation group (LAG).
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. The Create Link Aggregation Group dialog box is displayed.

Parameter LAG No. Value Range 1 to 65535 Default Value 1 Description
l
This parameter specifies the LAG number to be set manually. This parameter is valid only when Automatically Assign is not selected. This parameter indicates whether LAG No. is allocated automatically. When Automatically Assign is selected, LAG No. cannot be set.
Automatically Assign
Selected Deselected
Selected
LAG Name
This parameter specifies the LAG name.
B-182
Issue 02 (2009-10-30)
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 the Selected or Standby state. The aggregation information is exchanged among different equipment through the LACP protocol to ensure that the aggregation information is the same among all the nodes. Manual: You can manually 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. According to the physical up or down state, you can determine whether to perform an aggregation.
Revertive Mode
Revertive Non-Revertive
Non-Revertive
This parameter can be set only when Load Sharing is set to Non-Sharing.
Issue 02 (2009-10-30)
B-183
Parameter Load Sharing
Value Range Sharing Non-Sharing
Default Value Non-Sharing
Description
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. 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. This parameter is valid only when Load Sharing of a LAG is set to Sharing. The load sharing computation methods include: MAC address specific allocation (based on the source MAC address, destination MAC address, and XOR between source MAC address and source MAC address), IP address specific allocation (based on the source IP address, destination IP address, and XOR between source IP address and source IP address).
Load Sharing Hash Algorithm
Source MAC Destination MAC Source and Destination MAC Source IP Destination IP Source and Destination IP
Source MAC
B-184
Issue 02 (2009-10-30)
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. 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.
Port Settings Parameters

Parameter Main Board Value Range Default Value Description
l
This parameter specifies the main board in a LAG. This parameter is set according to the planning information.
Issue 02 (2009-10-30)
B-185
Parameter Main Port
Value Range -
Default Value -
Description
l
This parameter specifies the main port in a LAG. 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. This parameter specifies the slave board in a LAG. This parameter is set according to the planning information. This parameter specifies the salve port in a LAG. 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.
Board (Available Slave Ports)
Port (Available Slave Ports)
Selected Slave Ports
This parameter indicates the selected slave ports.
Related Tasks
A.10.1 Creating a LAG
B.9.16 Parameter Description: Ethernet Link Aggregation_Port Priority

This topic describes the parameters that are related to the port priority of a LAG.
B-186
Issue 02 (2009-10-30)
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
Port Priority
0 to 65535
32768
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. When ports are added into a LAG, the port of the highest priority is preferred for service transmission.
Related Tasks
B.9.17 Parameter Description: LPT Management_Creation

This parameter describes the parameters that are used for creating LPT management.
Navigation Path
1. 2. Select the NE from the Object Tree in the NE Explorer. Choose Configuration > LPT Management from the Function Tree. Click New.
Parameters for Convergence Points

Parameter Board Value Range Default Value Description This parameter specifies the board at the convergence point.
Issue 02 (2009-10-30)
B-187
Parameter Port
Value Range -
Default Value -
Description This parameter specifies the port on the board of the convergence point.
NOTE One port can be in an LPT only.
Parameters for Access Points

Parameter Board Port Value Range Default Value Description This parameter specifies the board at the access point. This parameter specifies the port on the board of the access point.
NOTE The access point supports selection of multiple ports on different boards.
Related Tasks
B.9.18 Parameter Description: Port Mirroring_Creation

This topic describes the parameters that are used for creating port mirroring tasks.
Navigation Path
1. 2. Select the corresponding board from the Object Tree in the NE Explorer. Choose Configuration > Port Mirroring from the Function Tree. Click New. The Port Mirror Management dialog box is displayed.

Parameter Mirror Name Value Range Default Value Description
l
This parameter specifies the name of the mirroring task. After the mirroring function of the port is enabled, you can monitor all the mirrored ports by analyzing the packets at the mirroring port only. As a result, you can easily manage the ports.
B-188
Issue 02 (2009-10-30)
Parameter Direction
Value Range Ingress Egress
Default Value Ingress
Description
l
This parameter specifies the direction in which the service to be monitored. Ingress indicates that the uplink direction of the service to be monitored. Egress indicates that the downlink direction of the service to be monitored. This parameter specifies the mirroring listener port and the listened port. Mirror Listener Port: The port where services are available cannot be selected. Otherwise, the creation fails.
Mirror Listener Port Listened Port
l l
B.10 Parameters for the Ethernet OAM

This topic describes the parameters that are related to the Ethernet operation, administration and maintenance (OAM). B.10.1 Parameter Description: Ethernet Service OAM Management_Maintenance Domain Creation This topic describes the parameters that are used for creating maintenance domains. B.10.2 Parameter Description: Ethernet Service OAM Management_Maintenance Association Creation This topic describes the parameters that are used for creating maintenance associations. B.10.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.10.4 Parameter Description: Ethernet Service OAM Management_Remote MEP Creation This topic describes the parameters that are used for creating a remote MEP. B.10.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.10.6 Parameter Description: Ethernet Service OAM Management_LB Enabling This topic describes the parameters that are used for enabling the LB. B.10.7 Parameter Description: Ethernet Service OAM Management_LT Enabling This topic describes the parameters that are used for enabling the LT. B.10.8 Parameter Description: Ethernet Port OAM Management_OAM Parameter This topic describes the OAM parameters that are related to Ethernet ports. B.10.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.
Issue 02 (2009-10-30)
B-189
B.10.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 Description
l
This parameter specifies the name of the maintenance domain. The maintenance domain refers to the network for the Ethernet OAM. This parameter can contain a maximum of eight bytes. This parameter specifies the level of the maintenance domain. The values 0-2 indicate the carrier level, the values 3-4 indicate the supplier level, and the values 5-7 indicates the user level. When the value is set to 0, the maintenance domain is at the lowest level. The values 1-7 indicate that the level increases in a sequential order. 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.
Maintenance Domain Level
0 1 2 3 4 5 6 7
Related Tasks
A.13.1 Creating an MD
B-190
Issue 02 (2009-10-30)
B.10.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 Maintenance Association Name Value Range Default Value Description This parameter indicates the maintenance domain of the created maintenance association.
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. 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
CC Test Transmit Period(ms)
1s 10s 1 min 10 min
1s
This parameter specifies the interval for transmitting packets in the CC. The CC is performed to check the availability of the service.
Related Tasks
A.13.2 Creating an MA
B.10.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 Port VLAN MP 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 specifies the board where the MEP is located. This parameter specifies the port where the MEP is located. This parameter indicates the VLAN ID of the current service.
l l
This parameter specifies the MEP ID. 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. This parameter specifies the direction of the MEP. 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. This parameter specifies whether to enable the CC function of the MEP. In the case of the tests based on the MP IDs, CC Status must be set to Active.
Direction
Ingress Egress
Ingress
CC Status
Active Inactive
Active
Related Tasks
A.13.3 Creating an MEP Point
B-192
Issue 02 (2009-10-30)
B.10.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 Maintenance Domain Name dialog box is displayed. Click New.

Parameter Maintenance Domain Name Maintenance Association Name Remote Maintenance Point ID(_e.g:1,3-6) Value Range 1 to 2048 Default Value 1 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. 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
Creating Remote MEPs in an MA
B.10.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.
Issue 02 (2009-10-30)
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 MP ID Value Range 1 to 2048 Default Value 1 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.
l l
This parameter specifies the MIP ID. 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.10.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. The LB Test dialog box is displayed.

Parameter MP ID Value Range Selected Deselected Sink Maintenance Point MAC Address
B-194
Description This parameter needs to be selected if the LB test is performed on the basis of MP IDs. This parameter needs to be selected if the LB test is performed on the basis of MAC addresses.
Issue 02 (2009-10-30)
Selected Deselected
Selected
Parameter Maintenance Domain Name Maintenance Association Name Source Maintenance Point ID
Value Range -
Default Value -
Description 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. Only the MEP can be set to the source maintenance point. This parameter specifies the destination maintenance point in the LB test. Only the MEP can be set to the destination maintenance point. Destination Maintenance Point ID can be set only when MP ID is selected. This parameter specifies the MAC address of the port where the destination maintenance point is located in the LB test. Only the MAC address of the MEP can be set to the MAC address of the destination maintenance point. Destination Maintenance Point MAC Address can be set only when Sink Maintenance Point MAC Address. This parameter specifies the number of packets transmitted each time in the LB test. When the value is greater, the required duration is longer. This parameter specifies the length of a transmitted LBM packet. If the packet length is different, the test result may be different. In normal cases, it is recommended that you use the default value. This parameter specifies the priority of transmitting packets. 0 indicates the lowest priority, and 7 indicates the highest priority. In normal cases, this parameter is set to the highest priority.
Destination Maintenance Point ID
Destination Maintenance Point MAC Address
00-00-00-00-00-00
Transmitted Packet Count
1 to 255
Transmitted Packet Length
64 to 1400
64
Transmitted Packet Priority
0 to 7
Issue 02 (2009-10-30)
B-195
Parameter Detection Result
Value Range -
Default Value -
Description This parameter indicates the relevant information and result of the LB test.
Related Tasks
A.13.6 Performing an LB Test
B.10.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. The LT Test dialog box is displayed.
Test Node Parameters

Parameter Maintenance Domain Name Maintenance Association Name Source Maintenance Point ID Value Range Default Value Description 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. Only the MEP can be set to the source maintenance point. This parameter specifies the MAC address of the board where the destination maintenance point is located. Only the MAC address of the MEP can be set to the MAC address of the destination maintenance point.
Destination Maintenance Point MAC Address
00-00-00-00-00-00
B-196
Issue 02 (2009-10-30)
Parameters for the Test Result

Parameter Source Maintenance Point 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
1 to 64
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. The number of hops indicates the adjacent relation between the responding maintenance point to the source maintenance point. The number of hops increases by one when a responding point occurs on the link from the source maintenance point to the destination maintenance point.
Test Result
This parameter indicates the result of the LT test.
Related Tasks
A.13.7 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 (2009-10-30)
B-197

Parameter Port Enable OAM Protocol Value Range Enabled Disabled
l
Description This parameter indicates the corresponding port.

l
This parameter indicates or specifies whether to enable the OAM protocol. 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. This parameter indicates or specifies the working mode of the OAM. The port whose OAM working mode is set to Active can initiate the OAM connection. The port whose OAM working mode is set to Passive can only wait for the opposite end to send the OAM connection request. The OAM working mode of the equipment at only one end can be Passive. This parameter indicates or specifies whether the local link events can be notified to the opposite end. 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. This parameter is set according to the planning information.
OAM Working Mode
Active Passive
Active
Link Event Notification
Enabled Disabled
Enabled
B-198
Issue 02 (2009-10-30)
Parameter Remote Side Loopback Response
Description
l
This parameter indicates or specifies whether the port responds to the remote loopback. 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. 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
This parameter indicates the status of transmitting packets at the local end. 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. This parameter indicates the status of receiving packets at the local end. 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.
Port Receive Status
FWD DISCARD LB
Issue 02 (2009-10-30)
B-199
Related Tasks
A.14.1 Enabling the OAM Auto-Discovery Function A.14.2 Enabling the Link Event Notification
B.10.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. 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.
Error Frame Period Window (frame) Error Frame Period Threshold (frame)
1488 to 892800000, in step of 1 -
892800000
This parameter specifies the window of monitoring the error frame period.
l
This parameter specifies the threshold of monitoring the error frame period. Within the specified value of Error Frame Period Window(frame), if the number of error frames on the link exceeds the preset value of Error Frame Period Threshold(frame), an alarm is reported.
Error Frame Second Window(s)
60
This parameter specifies the time window of monitoring the error frame second.
B-200
Issue 02 (2009-10-30)
Parameter Error Frame Second Threshold (s)
Default Value 1
Description
l
This parameter specifies the threshold of monitoring error frame seconds. 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
This parameter specifies the threshold of monitoring the error frame signal period. 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.11 QoS Parameters

This topic describes the parameters that are related to QoS. B.11.1 Parameter Description: Diffserv Domain Management This topic describes the parameters that are used for managing DiffServ domains. B.11.2 Parameter Description: DiffServ Domain Management_Create This parameter describes the parameters that are used for creating DiffServ (DS) domains. B.11.3 Parameter Description: DiffServ Domain Applied Port_Modification This topic describes the parameters that are used for changing DiffServ (DS) domain applied ports. B.11.4 Parameter Description: Policy Management This topic describes the parameters that are related to port policies. B.11.5 Parameter Description: Port Policy This topic describes the parameters that are used for creating port policies. B.11.6 Parameter Description: Port Policy_Traffic Classification Configuration
This parameter describes the parameters that are used for creating traffic classification. B.11.7 Parameter Description: Port Shaping Management_Creation This topic describes the parameters that are used for creating port shaping management tasks.
B.11.1 Parameter Description: Diffserv Domain Management

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 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 the domain. The default Diffserv domain cannot be modified and deleted.
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. C-VLAN indicates the client-side VLAN, and the value 7 indicates the highest priority.
B-202
Issue 02 (2009-10-30)
Parameter SVLAN
Value Range 0 to 7
Default Value -
Description
l
This parameter indicates the priority of the S-VLAN of the ingress packets. S-VLAN indicates the server-side VLAN, and the value 7 indicates the highest priority. This parameter indicates the DSCP priority of the IP addresses of the ingress packets. 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.
IP DSCP
0 to 63
Issue 02 (2009-10-30)
B-203
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. 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. The PHB service classes are BE, AF1, AF2, AF3, AF4, EF, CS6, and CS7. The priorities (C_VLAN priority, S_VLAN priority, and DSCP value) contained in the packets of the DiffServ domain and the eight PDB 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-204
Issue 02 (2009-10-30)
Parameters for Egress Mapping Relation

Parameter PHB Value Range BE AF1 AF2 AF3 AF4 EF CS6 CS7
l
Default Value -
Description
l
This parameter indicates the PHB service class of the DiffServ domain. 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. The PHB service classes are BE, AF1, AF2, AF3, AF4, EF, CS6, and CS7. The priorities (C_VLAN priority, S_VLAN priority, and DSCP value) contained in the packets of the DiffServ domain and the eight PDB service classes meet the requirements of the specified or default mapping relation.
CVLAN
0 to 7
This parameter indicates the priority of the C-VLAN of the egress packets. C-VLAN indicates the client-side VLAN, and the value 7 indicates the highest priority.
Issue 02 (2009-10-30)
B-205
Parameter SVLAN
Value Range 0 to 7
Default Value -
Description
l
This parameter indicates the priority of the S-VLAN of the egress packets. S-VLAN indicates the server-side VLAN, and the value 7 indicates the highest priority. This parameter indicates the DSCP priority of the IP addresses of the ingress packets. 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.
IP DSCP
0 to 63

Parameter Port Value Range Default Value Description This parameter indicates the port that uses the DiffServ domain.
Related Tasks
A.12.8 Querying the DS Domain of a Port
B.11.2 Parameter Description: DiffServ Domain Management_Create

This parameter describes the parameters that are used for creating DiffServ (DS) domains.
Navigation Path
1. 2. Select the NE from the Object Tree in the NE Explorer. Choose Configuration > QoS Management > Diffserv Domain Management from the Function Tree. Click Create. The Create DS Mapping Relation dialog box is displayed.
B-206
Issue 02 (2009-10-30)

Parameter Mapping Relation ID Value Range 2 to 8 Default Value 2 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.
l
Mapping Relation Name
Packet Type
cvlan svlan ip-dscp
cvlan
This parameter specifies the type of the packet. The packets trusted by the OptiX RTN 950 are the C_VLAN, S_VLAN and IP DSCP packets that contain the C_VLAN priority, S_VLAN priority, or DSCP value. By default, the untrusted packets are mapped to the BE service class for best-effort forwarding.
NOTE The E-Line point-to-point transparent transmission service supports only the mapping from DSCP packets to the PHB service class.
NOTE
If one default DS domain exists on the OptiX RTN equipment, Mapping Relation ID is set to 1, Mapping Relation Name is set to Default Map. If these parameters are not set, all the ports belong to the domain. The default DS domain cannot be modified and deleted.
Issue 02 (2009-10-30)
B-207
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. C-VLAN indicates the client-side VLAN, and the value 7 indicates the highest priority. This parameter specifies the S-VLAN priority of the ingress packets. S-VLAN indicates the server-side VLAN, and the value 7 indicates the highest priority. This parameter specifies the DSCP priority of the IP addresses of the ingress packets. 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.
SVLAN
0 to 7
IP DSCP
0 to 63
B-208
Issue 02 (2009-10-30)
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. 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. The PHB service classes are BE, AF1, AF2, AF3, AF4, EF, CS6, and CS7. The priorities (C_VLAN priority, S_VLAN priority, and DSCP 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.
Issue 02 (2009-10-30)
B-209
Parameters for Egress Mapping Relation

Parameter PHB Value Range BE AF1 AF2 AF3 AF4 EF CS6 CS7
l
Default Value -
Description
l
This parameter indicates the PHB service class of the DS domain. 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. The PHB service classes are BE, AF1, AF2, AF3, AF4, EF, CS6, and CS7. The priorities (C_VLAN priority, S_VLAN priority, and DSCP 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
This parameter specifies the C-VLAN priority of the egress packets. C-VLAN indicates the client-side VLAN, and the value 7 indicates the highest priority.
B-210
Issue 02 (2009-10-30)
Parameter SVLAN
Value Range 0 to 7
Default Value -
Description
l
This parameter specifies the S-VLAN priority of the egress packets. S-VLAN indicates the server-side VLAN, and the value 7 indicates the highest priority. This parameter specifies the DSCP priority of the IP addresses of the egress packets. 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.
IP DSCP
0 to 63

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.
Available Port
Issue 02 (2009-10-30)
B-211
Parameter Selected Port
Value Range -
Default Value -
Description
l
This parameter displays the selected port list. The ports in the list use the mapping relations between DS domains. Encapsulation Type determines the packet types that the port trusts. In the case of a UNI port, set Packet Type to cvlan or ipdscp. In the case of an NNI port, set Packet Type to svlan.
Related Tasks
A.12.1 Creating a DS Domain
B.11.3 Parameter Description: DiffServ Domain Applied Port_Modification

This topic describes the parameters that are used for changing DiffServ (DS) domain applied ports.
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.
B-212
Issue 02 (2009-10-30)
Parameter Packet Type
Value Range cvlan svlan ip-dscp
Default Value cvlan
Description
l
This parameter specifies the type of the packet. The packets trusted by the OptiX RTN 950 are the C_VLAN, S_VLAN and IP DSCP packets that contain the C_VLAN priority, S_VLAN priority, or DSCP value. By default, the untrusted packets are mapped to the BE service class for best-effort forwarding.
NOTE The E-Line point-to-point transparent transmission service supports only the mapping from DSCP packets to the PHB service class.
Board
This parameter specifies the board where the port is located. This parameter indicates the available port. This parameter indicates the selected port. The selected port is applied to the DS domain.
Available Port Selected Port
NOTE
If one default DS domain exists on the OptiX RTN 950, 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 the domain. The port applied to the default DS domain cannot be modified.
Related Tasks

This topic describes the parameters that are related to port policies.
Issue 02 (2009-10-30)
B-213
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 Value Range 1 to 36 Default Value Description
l
This parameter indicates the policy ID of the port. The OptiX RTN 950 supports a maximum number of 36 policies.
Policy Name
This parameter indicates or specifies the policy name of the port.
B-214
Issue 02 (2009-10-30)
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 950 provides different QoS policies for the queues at different service classes. CS6-CS7: indicates the highest service grade, which is mainly involved in signaling transmission. 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. 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. BE: indicates that the traffic is forwarded in best-effort manner without special processing.
Issue 02 (2009-10-30)
B-215
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. 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. The OptiX RTN 950 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-216
Issue 02 (2009-10-30)
Parameter
Value Range
Default Value
Description
l
This parameter is set according to the planning information. 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. This parameter can be set only when Grooming Police After Reloading is set to WRR. This parameter is set according to the planning information. This parameter indicates or specifies whether the traffic shaping function is enabled for the PHB service class queues in the egress direction. CIR (kbit/s), PIR (kbit/s), CBS (byte), and PBS (byte) can be set only when Bandwidth Limit is set to Enabled. This parameter is set according to the planning information.
Policy Weight(%)
1 to 100
25
Bandwidth Limit
Disabled Enabled
Disabled
Issue 02 (2009-10-30)
B-217
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. 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. This parameter is set according to the planning information. 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. 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. This parameter is set according to the planning information.
PIR(kbit/s)
B-218
Issue 02 (2009-10-30)
Parameter CBS(byte)
Value Range -
Default Value -
Description
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. This parameter is set according to the planning information. 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. This parameter is set according to the planning information.
PBS(byte)
Related Tasks
A.12.5 Setting the Port That Uses the Port Policy A.12.7 Querying the Port Policy
B.11.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 from the Function Tree. Click the CoS Queue Configuration tab. Click New. The Create Port Policy dialog box is displayed.
Issue 02 (2009-10-30)
B-219
Parameters
Parameter Policy ID Value Range 1 to 36 Default Value Description
l
This parameter specifies the policy ID of the port. The OptiX RTN 950 supports a maximum number of 36 policies.
Automatically Assign
Selected Deselected
Deselected
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. This parameter specifies the policy name of the port.
Policy Name
B-220
Issue 02 (2009-10-30)
Parameter CoS
Default Value -
Description
l
The BE, AF1, AF2, AF3, AF4, EF, CS6, and CS7 service classes respectively map eight queuing entities. The OptiX RTN 950 provides different QoS policies for the queues at different service class. CS6-CS7: indicates the highest service grade, which is mainly involved in signaling transmission. 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. 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. BE: indicates that the traffic is forwarded in best-effort manner without special processing.
Issue 02 (2009-10-30)
B-221
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. 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. The OptiX RTN 950 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-222
Issue 02 (2009-10-30)
Parameter
Value Range
Default Value
Description
l
This parameter is set according to the planning information. 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. This parameter can be set only when Grooming Police After Reloading is set to WRR. This parameter is set according to the planning information. This parameter indicates or specifies whether the traffic shaping function is enabled for the PHB service class queues. CIR (kbit/s), PIR (kbit/s), CBS (byte), and PBS (byte) can be set only when Bandwidth Limit is set to Enabled. This parameter is set according to the planning information.
Policy Weight(%)
1 to 100
25
Bandwidth Limit
Disabled Enabled
Disabled
Issue 02 (2009-10-30)
B-223
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. 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. This parameter is set according to the planning information. 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. 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. This parameter is set according to the planning information.
PIR(kbit/s)
B-224
Issue 02 (2009-10-30)
Parameter CBS(byte)
Value Range -
Default Value -
Description
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. This parameter is set according to the planning information. 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. This parameter is set according to the planning information.
PBS(byte)
Related Tasks
A.12.3 Creating a Port Policy
B.11.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 from the Function Tree. Click the Traffic Classification Configuration tab. Click New. The Create Traffic Classification dialog box is displayed.
Issue 02 (2009-10-30)
B-225

Parameter Traffic Classification ID Value Range 1 to 1024 Default Value Description This parameter specifies the ID of the traffic classification.
l
ACL Action
Permit Deny
Permit
The access control list (ACL) determines whether to forward or discard the packets that enter the port according to the specified matching rules. When this parameter is set to Permit, the ACL on the ingress side filters the packets that enter the port. Only the packets that match the specified rules can be received by the port. When this parameter is set to Deny, the ACL on the ingress side does not filter the packets that enter the port.
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. The OptiX RTN 950 supports the setting of the logical AND between multiple matching rules.
B-226
Issue 02 (2009-10-30)
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. 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. If the matching value of the packets is the same as the preset Match Value, the packets match the rules of complex traffic classification. This parameter is set according to 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
Issue 02 (2009-10-30)
B-227
Parameter CoS
Default Value -
Description
l
This parameter specifies the PHB service class queue mapped by the traffic classification packets. 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. This parameter is set according to the planning information. This parameter indicates or specifies whether the CAR operation is performed for the flow in the ingress direction. CIR (kbit/s), PIR (kbit/s), CBS (byte), and PBS (byte) can be set only when Bandwidth Limit is set to Enabled. This parameter is set according to the planning information.
Bandwidth Limit
Disabled Enabled
Enabled
B-228
Issue 02 (2009-10-30)
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. 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. This parameter is set according to the planning information.
Issue 02 (2009-10-30)
B-229
Parameter PIR(kbit/s)
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. 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. This parameter is set according to the planning information.
B-230
Issue 02 (2009-10-30)
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. This parameter is set according to the planning information. 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. This parameter is set according to the planning information. 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. The OptiX RTN 950 supports Color Blindness only.
PBS(byte)
Coloration Mode
Color Blindness
Color Blindness
Issue 02 (2009-10-30)
B-231
Parameter Packet Color
Value Range Red Yellow Green
Default Value -
Description Packets can be dyed in three colors: red, yellow, and green. The packets in red are first discarded.
l
Handling Mode
Discard Pass Remark
This parameter specifies the method of handling the packets. Discard: The packets are discarded. Pass: The packets are forwarded. 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.
Relabeled CoS
CS7 CS6 EF AF4 AF3 AF2 AF1 BE
If the handling method is set to "Remark", you can reset the CoS of the packets.
B-232
Issue 02 (2009-10-30)
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. CIR (kbit/s), PIR (kbit/s), CBS (byte), and PBS (byte) can be set only when Bandwidth Limit is set to Enabled. This parameter is set according to the planning information. 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. 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. This parameter is set according to the planning information.
CIR(kbit/s)
Issue 02 (2009-10-30)
B-233
Parameter PIR(kbit/s)
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. 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. This parameter is set according to the planning information. 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. This parameter is set according to the planning information.
CBS(byte)
B-234
Issue 02 (2009-10-30)
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. This parameter is set according to the planning information.
Related Tasks
A.12.4 Creating the Traffic
B.11.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 (kbyte) PIR (kbit/s) Value Range Default Value Description This parameter specifies the slot ID. This parameter specifies the port. If the traffic shaping function is enabled, OptiX RTN 950 processes the packets in the buffer queue through the following methods when no packets are available in the queue. l If the rate of the packets is not higher than the
B-235
Issue 02 (2009-10-30)
Parameter PBS (kbyte)
Value Range -
Default Value -
Description specified CIR, the packets are forwarded directly to the next port. l When the rate of the packets is higher than the CIR but is not higher than the PIR, the packets whose rate is higher than the CIR enter the buffer queue, which forwards the packets to the next port at the CIR. l When the rate of the packets is higher than the PIR, the packets are discarded first in the case of network congestion. l If the rate of the packets is not higher than the CIR during a certain period of time, a part of the burst packets are directly transmitted. The maximum traffic of the burst packets is determined by the CBS. l If the rate of the packets is higher than the CIR but is not higher than the PIR during a certain period of time, a part of the burst packets enter the buffer queue. The maximum traffic of the burst packets is determined by the PBS. When certain packets exist in the buffer queue, the packets whose rate is higher than the PIR directly enter the buffer queue, which forwards the
B-236
Issue 02 (2009-10-30)
Parameter
Value Range
Default Value
Description packets to the next port at the CIR.
Related Tasks
A.12.6 Configuring Port Shaping
B.12 RMON Parameters

This topic describes the parameters that are related to RMON performances. B.12.1 Parameter Description: RMON Performance_Statistics Group This topic describes the parameters that are related to RMON statistics groups. B.12.2 Parameter Description: RMON Performance_History Group This topic describes the parameters that are related to RMON history groups. B.12.3 Parameter Description: RMON Performance_History Control Group This topic describes the parameters that are related to RMON history control groups. B.12.4 Parameter Description: RMON Performance_RMON Setting This topic describes the parameters that are related to RMON setting.
B.12.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 Value Range 5 to 150 Default Value 5 Description This parameter specifies the object to be monitored.
l
This parameter specifies the duration of the monitoring period. This parameter is valid only when History Table Type is set to Custom Period 1 and Custom Period 2.
Issue 02 (2009-10-30)
B-237
Parameter Display Accumulated Value
Description
l
This parameter specifies the method of displaying the performance events. 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. If this parameter is selected, the displayed value is an absolute value that is currently stored in the register. This parameter specifies the method of displaying the performance events. 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. This parameter indicates the description of different colors. This parameter is valid only when Display Mode is set to Graphics. This parameter indicates the queried performance events. This parameter is valid only when Display Mode is set to List.
Display Mode
Graphics List
List
Legend
Color Description
Event
Related Tasks
A.15.1 Browsing the Performance Data in the Statistics Group of an Ethernet Port
B.12.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 Value Range Default Value Description The parameter indicates the object to be monitored.
Issue 02 (2009-10-30)
B-238
Parameter Ended History Table Type
Value Range 30-Second 30-Minute Custom Period 1 Custom Period 2
Default Value 30-Second
Description This parameter specifies the start time and end time of the monitoring period. This parameter specifies the monitoring period.
Display Mode
Graphics List
List
This parameter specifies the method of displaying the performance events. 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. This parameter indicates the description of different colors. This parameter is valid only when Display Mode is set to Graphics. This parameter indicates the queried performance events. This parameter is valid only when Display Mode is set to List.
Legend
Color Description
Event
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.12.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.
Issue 02 (2009-10-30)
B-239
Parameters
Parameter 30-Second Value Range Enabled Disabled 30-Minute Enabled Disabled Custom Period 1 Enabled Disabled Custom Period 2 Enabled Disabled History Register Count(1-50) Period Length(300 to 43200 seconds, a multiple of 30) 1 to 50 16 6(Custom Period 2) 300 to 43200 900 Disabled 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. This parameter indicates or specifies whether to enable Custom Period 1. This parameter indicates or specifies whether to enable Custom Period 2. This parameter indicates or specifies the quantity of the history registers.
l
This parameter indicates or specifies the monitoring period in Custom Period 1. The value must be an integer multiple of 30. This parameter indicates or specifies the monitoring period in Custom Period 2. The value must be an integer multiple of 30.
Period Length(300 to 86400 seconds, a multiple of 30)
300 to 86400
86400
Related Tasks

This topic describes the parameters that are related to RMON setting.
Navigation Path
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 Value Range Default Value Description This parameter indicates the object to be collected.
Issue 02 (2009-10-30)
B-240
Parameter 30-Second
Default Value -
Description 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
This parameter indicates or specifies whether to enable the 30-Minute monitoring function. In RMON History Control Group of the NE, if 30-Minute is set to Disabled, Not Supported is displayed for this parameter. This parameter indicates or specifies whether to enable the monitoring function based on Custom Period 1. In RMON History Control Group of the NE, if Custom Period 1 is set to Disabled, Not Supported is displayed for this parameter. This parameter indicates or specifies whether to enable the monitoring function based on Custom Period 2. In RMON History Control Group of the NE, if Custom Period 2 is set to Disabled, Not Supported is displayed for this parameter.
Custom Period 1
Enabled Disabled
Custom Period 2
Enabled Disabled
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 1.
Issue 02 (2009-10-30)
B-241
Parameter Custom Period 2
Description This parameter indicates or specifies whether to enable the monitoring function based on Custom Period 2.
l
Threshold Detect
Report All Do Not Detect Report Only the Upper Threshold Report Only the Lower Threshold
Report All
This parameter indicates or specifies the threshold detection method. 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. If an event does not support this parameter, Not Supported is displayed.
Upper Threshold
0 to 9223372036854775 80
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
0 to 9223372036854775 80
Threshold Unit
Related Tasks
A.15.2 Configuring an Alarm Group for an Ethernet Port A.15.4 Browsing the Performance Data in the History Group of an Ethernet Port
B.13 Parameters for the Orderwire and Auxiliary Interfaces

This topic describes the parameters that are related to the orderwire and auxiliary interfaces. B.13.1 Parameter Description: Orderwire_General This topic describes the parameters that are used for general orderwire features. B.13.2 Parameter Description: Orderwire_Advanced This topic describes the parameters that are used for advanced orderwire features. B.13.3 Parameter Description: Orderwire_F1 Data Port This topic describes the parameters that are used for F1 data ports. B.13.4 Parameter Description: Orderwire_Broadcast Data Port This topic describes the parameters that are used for broadcast data ports. B.13.5 Parameter Description: Environment Monitoring Interface
This topic describes the parameters that are used for environment monitoring interfaces.
B.13.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.
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. 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. The call waiting time should be set to the same for all the NEs.
Dialling Mode
Pulse Dual-Tone Frequency
Dual-Tone Frequency
This parameter indicates the dialling mode of the orderwire phone.
Issue 02 (2009-10-30)
B-243
Parameter Telephone No.
Value Range -
Default Value 888
Description
l
This parameter specifies the telephone number of the network-wide orderwire conference call. When a OptiX RTN 950 dials the telephone number 888, the orderwire phones of all the NEs on the orderwire subnet ring. When a OptiX RTN 950 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. The telephone number of the orderwire conference call should be the same for all the nodes on the same subnet. 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. This parameter specifies the orderwire phone number of the local station. An addressing call refers to a point-to-point call. 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. 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. The orderwire phone number cannot be set to the group call number 888 and cannot start with 888.
Phone 1
100 to 99999999
101
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.
B.13.2 Parameter Description: Orderwire_Advanced

This topic describes the parameters that are used for advanced orderwire features.
B-244
Issue 02 (2009-10-30)
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.
Parameters for Bytes Occupied by Orderwire Phones

Parameter Orderwire Occupied Bytes Value Range E1 E2
l
Default Value E1
Description
l
This parameter specifies the overhead byte that is used to transmit the orderwire signals. 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.
B.13.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 Channel Value Range Default Value Description
l
This parameter indicates the available F1 data channel. Two data channels should be selected for the configuration.
No 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. If an IF port is selected, this parameter corresponds to the customized F1 byte in the microwave frame at the IF port.
B-245
Issue 02 (2009-10-30)
Parameter Data Channel 2
Value Range
Default Value
Description
l
If F1 is selected, this parameter corresponds to the F1/S1 interface on the AUX board. The F1/S1 interface complies with ITU-T G.703 and operates at the rate of 64 kbit/s.
B.13.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. In the case of a radio link, a customized serial overhead byte in the microwave frame is used to transmit the asynchronous data services. When this parameter is set to the SERIAL1, the F1/S1 interface on the corresponding AUX board is used. When this parameter is set to the SDH optical/electrical line port, the value of Overhead Byte of this port is used. When this parameter is set to the IF port, the customized Serial byte in the microwave frame of this port is used.
Broadcast Data Source
Available Broadcast Data Sink
This parameter indicates the available broadcast data sink.
B-246
Issue 02 (2009-10-30)
Parameter Selected Broadcast Data Sink
Value Range -
Default Value -
Description
l
When this parameter is set to the SERIAL1, the F1/S1 interface on the corresponding AUX board is used. When this parameter is set to the SDH optical/electrical line port, the value of Overhead Byte of this port is used. When this parameter is set to the IF port, the customized Serial byte in the microwave frame of this port is used.
B.13.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. Manual Control: Relay Status in Major Alarm(K0) and Relay Status in Critical Alarm(K1) need to be set. This parameter indicates that the status of the relay is set manually for major alarms. Enable: The relay is set to the "0N" status for major alarms. Disabled: The relay is set to the "OFF" status for major alarms. This parameter is valid only when Relay Control Mode is set to Manual Control.
Relay Status in Major Alarm(K0)
Disabled Enabled
Disabled
Issue 02 (2009-10-30)
B-247
Parameter Relay Status in Critical Alarm(K1)
Description
l
This parameter indicates that the status of the relay is set manually for critical alarms. Enable: The relay is set to the enabled status for critical alarms. Disabled: The relay is set to the disabled status for critical alarms. 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. If this parameter is set to Relay Turns On/Low Level, an alarm is generated when the relay is turned on. This parameter is valid only when Using Status is set to Used.
Alarm Severity
Critical Alarm Major Alarm Minor Alarm Warning Alarm
Critical Alarm
This parameter specifies the severity of the alarm that is generated at the input relay.
Parameters for the Output Relay

Parameter Operation Object Value Range Default Value Description This parameter indicates the operation object.
B-248
Issue 02 (2009-10-30)
Parameter Output Path Name Use or Not
Value Range Unused Used
Default Value Unused
Description 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 Temperature Upper Threshold (Deg.C) Temperature Lower Threshold (Deg.C) Value Range -40.0 to 80.0 Default Value Description This parameter indicates the operation object. This parameter specifies the upper temperature threshold of the board. When the actual temperature is higher than the preset value, an alarm is generated. This parameter specifies the lower temperature threshold of the board. When the actual temperature is lower than the preset value, an alarm is generated.
-40.0 to 80.0
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.
B.14 Parameters for Board Interfaces

This topic describes the parameters that are related to board interfaces. B.14.1 Parameter Description: IF Interface_IF Attribute This topic describes the parameters that are related to IF attributes. B.14.2 Parameter Description: IF Interface_ATPC Attribute
This topic describes the parameters that are related to the ATPC attributes. B.14.3 Parameter Description: Hybrid/AM Configuration This topic describes the parameters that are used for configuring the Hybrid/AM function. B.14.4 Parameter Description: ATPC Adjustment Records This topic describes the parameters that are related to ATPC adjustment records. B.14.5 Parameter Description: PRBS Test This topic describes the parameters that are related to the pseudorandom binary sequence (PRBS) test. B.14.6 Parameter Description: ODU Interface_Radio Frequency Attribute This topic describes the parameters that are related to radio frequency attributes of an ODU. B.14.7 Parameter Description: ODU Interface_Power Attributes This topic describes the parameters that are used for configuring the power attributes of the ODU. B.14.8 Parameter Description: ODU Interface_Equipment Information This topic describes the parameters that are used for configuring the equipment information of the ODU. B.14.9 Parameter Description: ODU Interface_Advanced Attributes This topic describes the parameters that are used for configuring the advanced attributes of the ODU. B.14.10 Parameter Description: SDH Interfaces This topic describes the parameters that are related to the SDH interfaces. B.14.11 Parameter Description: Automatic Laser Shutdown This topic describes the parameters that are related to the automatic laser shutdown (ALS) function. B.14.12 Parameter Description: PDH Interfaces This topic describes the parameters that are related to the PDH interfaces. B.14.13 Parameter Description: Ethernet Interface_Basic Attributes This topic describes the parameters that are related to the basic attributes of an Ethernet interface. B.14.14 Parameter Description: Ethernet Interface_Flow Control This topic describes the parameters that are related to flow control. B.14.15 Parameter Description: Ethernet Interface_Layer 2 Attributes This topic describes the parameters that are related to the Layer 2 attributes. B.14.16 Parameter Description: Ethernet Interface_Advanced Attributes This topic describes the parameters that are used for configuring the advanced attributes. B.14.17 Parameter Description: Microwave Interface_Basic Attributes This topic describes the parameters that are related to the basic attributes of microwave interfaces. B.14.18 Parameter Description: Microwave Interface_Layer 2 Attributes This topic describes the parameters that are related to the Layer 2 attributes of microwave interfaces. B.14.19 Parameter Description: Microwave Interface_Advanced Attributes This topic describes the parameters that are related to the advanced attributes of microwave interfaces.
B.14.1 Parameter Description: IF Interface_IF Attribute

This topic describes the parameters that are related to IF attributes.
Navigation Path
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 Radio Link ID Value Range 1 to 4094 Default Value 1 Description This parameter indicates the corresponding IF interface.
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. 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. This parameter indicates the received ID of the radio link. 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.
Received Radio Link ID
1 to 4094
Issue 02 (2009-10-30)
B-251
Parameter IF Port Loopback
Value Range Non-Loopback Inloop Outloop
Default Value Non-Loopback
Description
l
This parameter indicates or specifies the loopback status of the IF interface. Non-Loopback indicates that the loopback is cancelled or not performed. Inloop indicates that the IF signals transmitted to the opposite end are looped back. Outloop indicates that the received SDH signals are looped back. 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 NonLoopback. This parameter indicates or specifies whether the radio link transmits the wayside E1 service. 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. This parameter indicates or specifies the slot in which the 2M wayside service is accessed. This parameter can be set only when 2M Wayside Enable Status is set to Enabled. 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. This parameter indicates or specifies the status of transmitting the 350 MHz carrier signals at the IF interface. This parameter can be set to Start in the commissioning process only. In normal cases, this parameter is set to Stop. Otherwise, the services are interrupted.
2M Wayside Enable Statusa
Disabled Enabled
Disabled
2M Wayside Input Boarda
350 MHz Consecutive Wave Status
Stop Start
Stop
B-252
Issue 02 (2009-10-30)
Parameter XPIC Enabledb
Description
l
This parameter indicates or specifies whether the XPIC function of the IFX2 board is enabled. If the IFX2 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 IFX2 board.
Enable IEEE-1588 Timeslotc
Enabled Disabled
Disabled
If the OptiX RTN 950 is interconnected with the packet radio equipment, this parameter should be set to Enabled. Otherwise, this parameter should be set to Disabled.
NOTE
l l l
a. The IFU2 and IFX2 boards do not support the 2M wayside service. b. The IFU2 and IF1 boards do not support the XPIC function. c. The IF1 board does not support the IEEE-1588 timeslot function.
Related Tasks
A.3.7 Setting IF Attributes
B.14.2 Parameter Description: IF Interface_ATPC Attribute

This topic describes the parameters that are related to the ATPC attributes.
Navigation Path
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 Value Range Default Value Description This parameter indicates the corresponding IF interface.
Issue 02 (2009-10-30)
B-253
Parameter ATPC Enable Status
Description
l
This parameter specifies whether the ATPC function is enabled. 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. The settings of the ATPC attributes must be consistent at both ends of a radio link. In the case of areas where fast fading severely affects the radio transmission, it is recommended that you set this parameter to Disabled. 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. Set the central value between the ATPC upper threshold and the ATPC lower threshold to a value for the expected receive power. 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. You can set the ATPC upper threshold only when ATPC Automatic Threshold (dBm) is set to Disabled.
-75.0 to -20.0 -35.0 to -90.0
-45.0 -70.0
B-254
Issue 02 (2009-10-30)
Parameter ATPC Automatic Threshold Enable Status
Description
l
This parameter specifies whether the ATPC automatic threshold function is enabled. 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. If this parameter is set to Disabled, you need to manually set ATPC Upper Threshold(dBm) and ATPC Lower Threshold(dBm). This parameter indicates that the equipment automatically uses the preset ATPC upper and lower thresholds. This parameter is valid only when ATPC Automatic Threshold Enable Status is set to Enabled.
ATPC Upper Automatic Threshold(dBm) ATPC Lower Automatic Threshold(dBm)
Related Tasks
A.3.8 Configuring the ATPC Function

This topic describes the parameters that are used for configuring the Hybrid/AM function.
Navigation Path
In the NE Explorer, select a Hybrid IF board from the Object Tree and then choose Configuration > Hybrid/AM Configuration from the Function Tree.
Parameters
Parameter Port IF Channel Bandwidth Value Range 7M 14M 28M 56M Default Value 7M 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.
Issue 02 (2009-10-30)
B-255
Parameter AM Mode
Value Range Asymmetric
Default Value Asymmetric
Description When AM Mode is set to Asymmetric, the AM switching in one direction of the radio link does not trigger AM switching in the other direction of the radio link.
NOTE On the OptiX RTN equipment, this parameter can be set to Asymmetric only.
AM Enable Status
Disable Enable
Disable
When this parameter is set to Disable, the radio link uses only the specified modulation scheme. In this case, you need to select Manually Specified Modulation Mode. When this parameter is set to Enable, 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 Guaranteed AM Capacity QPSK 16QAM 32QAM 64QAM 128QAM 256QAM QPSK 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. This parameter is valid only when AM Enable Status is set to Enable. 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 Enable.
B-256
Issue 02 (2009-10-30)
Parameter Manually Specified Modulation Mode
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 Disable.
Guaranteed E1 Capacity
When AM Enable Status is set to Enable, this parameter depends on IF Channel Bandwidth and Modulation Mode of the Guaranteed AM Capacity and is not configurable. When AM Enable Status is set to Disable, this parameter depends on IF Channel Bandwidth and Manually Specified Modulation Mode and is not configurable.
E1 Capacity
This parameter specifies the number of E1 services that can be transmitted in the Hybrid work mode.
Related Tasks
A.3.5 Setting the Hybrid/AM Attribute A.3.13 Querying the AM Status
B.14.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.
Parameters
Parameter Port Event NO. Adjustment Time 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.
B-257
Issue 02 (2009-10-30)
Parameter Adjustment Direction Switchover Transmitted Power(dBm) Received Power (dBm)
Value Range -
Default Value -
Description 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.3.11 Querying the ATPC Adjustment Records
B.14.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 Direction Value Range Cross Tributary
l
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. In the tributary direction, the PRBS test is performed to check the connectivity of the cable from the tributary board to the DDF. 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
1 to 255
This parameter indicates or specifies the duration of the PRBS test.
B-258
Issue 02 (2009-10-30)
Parameter Measured Time
Value Range s 10min h
Default Value s
Description 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.14.6 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
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 Value Range Default Value Description This parameter indicates the corresponding ODU.
Issue 02 (2009-10-30)
B-259
Parameter Transmit Frequency(MHz)
Value Range -
Default Value -
Description
l
This parameter indicates or specifies the transmit frequency of the ODU, namely, the central frequency of the channel. 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. The difference between the transmit frequencies at both ends of a radio link should be one T/R spacing. This parameter is set according to the planning information. 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. 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. 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. 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. The T/R spacing of the ODU should be set to the same value at both ends of a radio link.
T/R Spacing(MHz)
Actual Transmit Frequency(MHz) Actual Receive Frequency(MHz) Actual T/R Spacing(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.
B-260
Issue 02 (2009-10-30)
Parameter The Range of frequency Point (MHz)
Value Range -
Default Value -
Description This parameter indicates the working range of the frequency of the ODU.
B.14.7 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. 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.. This parameter is set to limit the maximum transmit power of the ODU within this preset range. The maximum transmit power adjusted by using the ATPC function should not exceed this value. This parameter is set according to the planning information.
Issue 02 (2009-10-30)
B-261
Parameter Transmit Power (dBm)
Value Range -
Default Value -
Description
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). The transmit power of the ODU should be set to the same value at both ends of a radio link. 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. This parameter is set according to the planning information. 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. When the antenna misalignment indicating function is enabled, if the actual receive power of the ODU exceeds the range of receive power3 dB, the ODU LED of the IF board connected to the ODU is on (yellow) for 300 ms and off for 300 ms repeatedly, indicating that the antenna is not aligned. 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. This parameter is set according to the planning information. This parameter indicates the actual transmit power of the ODU. If the ATPC function is enabled, the queried actual transmit power may be different from the preset value.
Power to Be Received(dBm)
Actual Transmit Power(dBm)
Actual Received Power(dBm)
This parameter indicates the actual receive power of the ODU.
B-262
Issue 02 (2009-10-30)
Parameter Actual range of Power(dBm)
Value Range -
Default Value -
Description This parameter indicates the range of the actual transmit power of the ODU.
Equip 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. PDH and SDH indicate the transmission capacity only and is irrelevant to the type of transmitted service. This parameter indicates whether the ODU is a Tx high station or a Tx low station. The transmit frequency of a Tx high station is one T/R spacing higher than the transmit frequency of a Tx low station.
Station Type
Tx Low Tx High
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
Standard Power Output High Power Output
Related Tasks
A.3.9 Setting the Power Attributes of the ODU
B.14.8 Parameter Description: ODU Interface_Equipment Information

This topic describes the parameters that are used for configuring the equipment information of the ODU.
Navigation Path
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.
Issue 02 (2009-10-30)
Parameters
Parameter Board Frequency(GHz) Equipment Type Value Range PDH SDH
l
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. PDH and SDH indicate the transmission capacity only and is irrelevant to the type of transmitted service.
T/R Spacing(MHz) Intermediate Frequency Bandwidth (MHz) Station Type
This parameter indicates the T/R spacing of the ODU. This parameter indicates the IF frequency bandwidth of the ODU.
l
This parameter indicates whether the ODU is a Tx high station or a Tx low station. 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.
B.14.9 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
Select the ODU from the Object Tree in the NE Explorer. Choose Configuration > ODU Interface from the Function Tree. Click the Advanced Attributes tab.
B-264
Issue 02 (2009-10-30)
Parameters
Parameter Board RF Loopback Value Range Non-Loopback Inloop
l
Description This parameter indicates the corresponding ODU.

l
This parameter indicates or specifies the loopback status of the RF interface of the ODU. Non-Loopback indicates that the loopback is canceled or not performed. Inloop indicates that the RF signals transmitted to the opposite end are looped back. 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. In normal cases, this parameter is set to Non-Loopback. This parameter indicates or specifies the transmit status of the ODU. If this parameter is set to mute, the transmitter of the ODU does not work but can normally receive microwave signals. If this parameter is set to unmute, the ODU can normally transmit and receive microwave signals. In normal cases, this parameter is set to unmute.
Configure Transmission Status
unmute mute
unmute
Actual Transmission Status Factory Information
unmute mute -
This parameter indicates the actual transmit status of the ODU. This parameter indicates the manufacturer information about the ODU.
B.14.10 Parameter Description: SDH Interfaces

This topic describes the parameters that are related to the SDH interfaces.
Navigation Path
l
Select the corresponding board from the Object Tree in the NE Explorer. Choose Configuration > SDH Interface from the Function Tree.
Issue 02 (2009-10-30)
l
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 Open Close
l
Default Value Open
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. This parameter is set for SDH optical interfaces only. In normal cases, this parameter is set to Open. This parameter indicates or specifies the loopback status on the SDH interface. Non-Loopback indicates that the loopback is canceled or not performed. Inloop indicates that the SDH signals transmitted to the opposite end are looped back. Outloop indicates that the received SDH signals are looped back. 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. In normal cases, this parameter is set to Non-Loopback.
Optical(Electrical) Interface Loopbacka
Non-Loopback Inloop Outloop
Non-Loopback
B-266
Issue 02 (2009-10-30)
Parameter VC4 Loopbackb
Description
l
This parameter indicates or specifies the loopback status in the VC-4 path. Non-Loopback indicates that the loopback is canceled or not performed. Inloop indicates that the VC-4 signals transmitted to the opposite end are looped back. Outloop indicates that the received VC-4 signals are looped back. 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. In normal cases, this parameter is set to Non-Loopback.
NOTE
l l
a: Indicates the parameters that are supported when Port is selected from the list box. b: Indicates the parameters that are supported when VC4 Channel is selected from the list box.
B.14.11 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 Value Range Default Value Description This parameter indicates the corresponding optical interface.
Issue 02 (2009-10-30)
B-267
Parameter Automatic Shutdown
Description
l
This parameter indicates or specifies whether the Automatic Laser Shutdown function is enabled or disabled for the laser. 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. 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.14.12 Parameter Description: PDH Interfaces

This topic describes the parameters that are related to the PDH interfaces.
Navigation Path
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.
l l
Parameters
Parameter Port Port Name Value Range Default Value Description This parameter indicates the corresponding port. This parameter indicates or specifies the name of the port.
B-268
Issue 02 (2009-10-30)
Parameter Tributary Loopback
Default Value -
Description
l
This parameter indicates or specifies the loopback status in the associated path of the tributary unit. Non-Loopback indicates that the loopback is canceled or not performed. Inloop indicates that the PDH signals transmitted to the opposite end are looped back. Outloop indicates that the received PDH signals are looped back. 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. In normal cases, this parameter is set to Non-Loopback.
Port Impedance
75 Ohm 120 ohm
This parameter indicates the impedance of a path, which depends on the tributary unit.
l
Service Load Indication
Load Non-Loaded
This parameter indicates or specifies the service loading status in a specific path. When this parameter is set to Load, the board detects whether alarms exist in the path. When this parameter is set to NonLoaded, the board does not detect whether there are alarms in the path. 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.
Issue 02 (2009-10-30)
B-269
Parameter Retiming Mode
Value Range Normal Retiming Mode of Tributary Clock Retiming Mode of Cross-connect Clock
Default Value -
Description
l
This parameter indicates or specifies the retiming mode of a specific path. 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. When this parameter is set to Normal, the retiming function is not used. 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. When this parameter is set to the retiming function is used with the clock of the upstream tributary unit traced., the retiming function is used with the clock of the cross-connect unit traced. It is recommended that the external clock, instead of the retiming function, should be used to provide reference clock signals for the equipment. If the retiming function is required, it is recommended that you set this parameter to Retiming Mode of Cross-connect Clock.
Port Service Type
E1
This parameter indicates the type of services that are processed in a path. It depends on the services that are transmitted in a path.
B.14.13 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.
B-270
Issue 02 (2009-10-30)

Parameter Port Name Enable Port Value Range Enabled Disabled Port Mode Layer 2 Layer 2 Default Value Enabled Description This parameter indicates the port name. This parameter specifies the port name. This parameter indicates the working mode of the port. This parameter indicates the working mode of the port.
l
Encapsulation Type
Null 802.1Q QinQ
This parameter specifies the method of the port to process the received packets. If you set this parameter to Null, the port transparently transmits the received packets. If you set this parameter to 802.1Q, the port identifies the packets that comply with the IEEE 802.1Q standard. If you set this parameter to QinQ, the port identifies the packets that comply with the IEEE 802.1 QinQ standard.
Issue 02 (2009-10-30)
B-271
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. When the equipment on the opposite side works in auto-negotiation mode, set the working mode of the equipment on the local side to Auto-Negotiation. 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 FullDuplex, 100M FullDuplex, or 1000M Full-Duplex depending on the port rate of the equipment on the opposite side. 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 HalfDuplex, 100M HalfDuplex, or AutoNegotiation depending on the port rate of the equipment on the opposite side. The GE optical interface supports the 1000M full-duplex mode only.
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.
B-272
Issue 02 (2009-10-30)
Parameter Auto-Negotiation Enable
Value Range Auto-Negotiation 10M Half-Duplex 10M Full-Duplex 100M Half-Duplex 100M Full-Duplex 1000M Full-Duplex
Default Value 100M Full-Duplex
Description
l
This parameter specifies the autonegotiation capability of the Ethernet port. This parameter is valid only when Working Mode is set to AutoNegotiation. This parameter specifies the attribute of the logical port. The SFP on the EM6F, CSHB and CSHC board supports the optical port and electrical port.
Logical Port Attribute
Optical Port Electrical Port
Optical Port
Physical Port Attribute
This parameter indicates the attribute of the physical port.
B.14.14 Parameter Description: Ethernet Interface_Flow Control

This topic describes the parameters that are related to flow control.
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 Flow Control tab.

Parameter Port Value Range Default Value Description This parameter indicates the port name.
Issue 02 (2009-10-30)
B-273
Parameter Non-Autonegotiation Flow Control Mode
Value Range Disabled Enable Symmetric Flow Control
Description
l
This parameter is valid only when Working Mode is not set to Auto-Negotiation. 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 This parameter is valid only when Working Mode is set to AutoNegotiation. 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
Auto-Negotiation Flow Control Mode
Disabled Enable Symmetric Flow Control
Disabled
B.14.15 Parameter Description: Ethernet Interface_Layer 2 Attributes

This topic describes the parameters that are related to the Layer 2 attributes.
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 Layer 2 Attributes tab.

Parameter Port Value Range Default Value Description This parameter indicates the port name.
B-274
Issue 02 (2009-10-30)
Parameter QinQ Type Domain
Value Range -
Default Value -
Description
l
This parameter specifies the QinQ type domain. 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. 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. QinQ Type Domain should be set to the same value for all the ports on the EM6T/ EM6F board.
Issue 02 (2009-10-30)
B-275
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-1. If all the accessed services are frames with the VLAN tag (tagged frames), this parameter is set to Tag Aware. If all the accessed services are frames without the VLAN tag (untagged frames), this parameter is set to Access. If the accessed services contain tagged frames and untagged frames, this parameter is set to Hybrid. This parameter is valid only when TAG is set to Access or Hybrid. For details about the functions of this parameter, see Table B-1. This parameter is set according to the actual situations.
Default VLAN ID
1 to 4094
B-276
Issue 02 (2009-10-30)
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. For details about the functions of this parameter, see Table B-1. 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-1 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 receives 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 receives the frame.
Ingress UNI
Issue 02 (2009-10-30)
B-277
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
Egress UNI
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. If the VLAN ID in the frame is not Default VLAN ID, the port directly transmits the frame.
B.14.16 Parameter Description: Ethernet Interface_Advanced Attributes

This topic describes the parameters that are used for configuring the advanced attributes.
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 Value Range Default Value Description This parameter indicates the port name. This parameter indicates the physical parameters of the port.
B-278
Issue 02 (2009-10-30)
Parameter MAC Loopback
Value Range Non-Loopback Inloop
Description
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. In normal cases, it is recommended that you use the default value. 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. In normal cases, it is recommended that you use the default value.
PHY Loopback
Non-Loopback Inloop
Non-Loopback
Loopback Check
This parameter specifies whether to enable loop detection, which is used to check whether a loop exists on the port. This parameter specifies whether to enable the loop port shutdown function. This parameter specifies the egress PIR bandwidth. 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.
Loopback Port Shutdown Egress PIR Bandwidth (kbit/s) Enabling Broadcast Packet Suppression
Disabled Enabled
Disabled
Issue 02 (2009-10-30)
B-279
Parameter 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 30% or higher.
B.14.17 Parameter Description: Microwave Interface_Basic Attributes

This topic describes the parameters that are related to the basic attributes of microwave interfaces.
Navigation Path
l
Select the NE from the Object Tree in the NE Explorer. Choose Configuration > Interface Management > Microwave Interface from the Function Tree. Click the Basic Attributes tab.
Parameters
Parameter Port Name Port Mode Value Range Layer 2 Default Value Layer 2 Description This parameter indicates the corresponding IF port. This parameter indicates or specifies the customized port name. This parameter indicates the working mode of the Ethernet name.
B-280
Issue 02 (2009-10-30)
Parameter Encapsulation Type
Value Range Null 802.1Q QinQ
Default Value 802.1Q
Description
l
This parameter specifies the method of the port to process the received packets. If this parameter is set to Null, the port transparently transmits the received packets. If this parameter is set to 802.1Q, the port identifies the packets that comply with the IEEE 802.1Q standard. If this parameter is set to QinQ, the port identifies the packets that comply with the IEEE 802.1 QinQ standard.
B.14.18 Parameter Description: Microwave Interface_Layer 2 Attributes

This topic describes the parameters that are related to the Layer 2 attributes of microwave interfaces.
Navigation Path
l
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

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. This parameter can be set only when Encapsulation Type in General Attributes is set to QinQ.
Issue 02 (2009-10-30)
B-281
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 frame-processing methods, see Table B-2. If all the accessed services are frames that contain the VLAN tag (tagged frames), set this parameter to "Tag Aware". If all the accessed services are frames that do not contain the VLAN tag (untagged frames), set this parameter to "Access". If the accessed services contain tagged frames and untagged frames, set this parameter to "Hybrid". This parameter is valid only when TAG is set to Access or Hybrid. For details about the functions of this parameter, see Table B-2. This parameter needs to be set according to the actual situations. This parameter is valid only when TAG is set to Access or Hybrid. For details about the functions of this parameter, see Table B-2. 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.
Default VLAN ID
1 to 4094
VLAN Priority
0 1 2 3 4 5 6 7
Table B-2 Data frame processing Status Type of Data Frame Tagged frame Processing Method Tag Aware The port receives the frame. Access The port discards the frame. Hybrid The port receives the frame.
Ingress Port
B-282
Issue 02 (2009-10-30)
Status
Type of Data Frame Untagged frame
Processing Method Tag Aware The port discards the frame. Access The port receives the frame after the VLAN tag that corresponds to "Default VLAN ID" and "VLAN Priority" are added to the frame. The port strips the VLAN tag from the frame and then transmits the frame. Hybrid The port receives the frame after the VLAN tag that corresponds to "Default VLAN ID" and "VLAN Priority" are added to the frame.
l
Egress Port
Tagged frame
The port transmits the frame.
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. If the VLAN ID in the frame is not "Default VLAN ID", the port directly transmits the frame.
B.14.19 Parameter Description: Microwave Interface_Advanced Attributes

This topic describes the parameters that are related to the advanced attributes of microwave interfaces.
Navigation Path
l
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.
Issue 02 (2009-10-30)
B-283
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. 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. This parameter indicates the received ID of the radio link. 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. This parameter indicates or specifies the loopback status of the IF interface. Non-Loopback indicates that the loopback is cancelled or not performed. Inloop indicates that the IF signals transmitted to the opposite end are looped back. Outloop indicates that the received SDH signals are looped back. 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 NonLoopback. This parameter indicates or specifies the loopback status on the composite interface. Non-Loopback indicates that the loopback is cancelled or not performed. Inloop indicates that the composite signals transmitted to the opposite end are looped back. Outloop indicates that the received composite signals are looped back. In normal cases, this parameter is set to Non-Loopback.
Received Radio Link ID
IF Port Loopback
Non-Loopback
Composite Port Loopback
Non-Loopback
B-284
Issue 02 (2009-10-30)
Parameter Error Frame Discard Enabled
Description
l
This parameter indicates or specifies whether to discard the Ethernet frame when a CRC error occurs in an Ethernet frame. If the Ethernet service transmitted on the IFUP port is a voice service or a video service, you can set this parameter to Disabled. The IF1 board does not support this parameter. This parameter indicates the MAC address of the port. The IF1 board does not support this parameter. This parameter indicates the transmit rate of the local port. The IF1 board does not support this parameter. This parameter indicates the receive rate of the local port. The IF1 board does not support this parameter. 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. In normal cases, it is recommended that you use the default value. The IF1 board does not support this parameter.
MAC Address
Transmitting Rate (Kbit/s)
Receiving Rate (Kbit/s)
MAC Loopback
Non-Loopback Inloop
Non-Loopback
PHY Loopback
Non-Loopback
Non-Loopback
The IF port on the OptiX RTN 950 does not support the setting of this parameter.
B.15 Parameters for Overhead

This topic describes the parameters that are related to overhead. B.15.1 Parameter Description: Regenerator Section Overhead This topic describes the parameters that are related to the regenerator section overheads (RSOHs). B.15.2 Parameter Description: VC-4 POHs
This topic describes the parameters that are related to the VC-4 path overheads (POHs). B.15.3 Parameter Description: VC-12 POHs This topic describes the parameters that are related to the VC-12 path overheads (POHs).
B.15.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.

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
J0 to be Received ([Mode]Content)
[Disabled]
This parameter specifies the J0 byte to be received. If this parameter is set to [Disabled], the board does not monitor the received J0 byte. It is recommended that you use the default value.
B.15.2 Parameter Description: VC-4 POHs

This topic describes the parameters that are related to the VC-4 path overheads (POHs).
Navigation Path
1. 2. Select the NE 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.

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 LP_TIM or LP_TIM_VC3 alarm, this parameter is set according to the J1 byte to be received at the opposite end.
l
J1 to be Received ([Mode]Content)
[Disabled]
If this parameter is set to [Disabled], the board does not monitor the received J1 byte. It is recommended that you use the default value.
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.
C2 to be Received
Issue 02 (2009-10-30)
B-287
Parameters for Overhead Termination

Parameter Object VC4 Overhead Termination Value Range Termination Pass-Through Auto
l
Default Value Auto
Description This parameter indicates the object to be set.

l
If this parameter is set to Pass-Through, the NE forwards the original overhead after monitoring the VC-4 path overhead regardless of the C2 byte. 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. 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. It is recommended that you use the default value.
B.15.3 Parameter Description: VC-12 POHs

This topic describes the parameters that are related to the VC-12 path overheads (POHs).
Navigation Path
1. 2. Select the NE 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.

Parameters for the Trace Byte

Parameter Object
B-288
Value Range -
Default Value -
Description This parameter indicates the object to be set.

Issue 02 (2009-10-30)
Parameter J2 to be Sent
Value Range -
Default Value [16 Bytes]HuaWei SBS
Description If the NE at the opposite end reports the HP_TIM alarm, this parameter is set according to the J2 byte to be received by the NE at the opposite end.
l
J2 to be Received
[Disabled]
If this parameter is set to [Disabled], the board does not monitor the received J2 byte. It is recommended that you use the default value.
Parameters for the Signal Flag

Parameter Object Signal Label (L1,L2,L3 of V5) to be Sent Signal Label (L1,L2,L3 of V5) to be Received Value Range Default Value Description This parameter indicates the object to be set. If the NE at the opposite end reports the LP_SLM or LP_SLM_VC3 alarm, this parameter is set according to the V5 byte to be received at the opposite end. If the NE at the local end reports the LP_SLM or LP_SLM_VC3 alarm, this parameter is set according to the V5 byte to be sent at the opposite end.
Issue 02 (2009-10-30)
B-289
C Glossary
C
Terms are listed in an alphabetical order. Number 1U 1+1 protection
Glossary
The standard electronics industries association (EIA) rack unit (44 mm/ 1.75 in.) A radio link protection system composed of one working channel and one protection channel. Two ODUs and two IF boards are used at each end of a radio link.
A Adaptive modulation A technology that is used to automatically adjust the modulation mode based on the channel quality. When the channel quality is favorable, the equipment adopts a high-efficiency 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. A network element that adds/drops the PDH signal or STM-x (x < N) signal to/from the STM-N signal on the SDH transport network. A channel configuration method, which uses two adjacent channels (a horizontal polarization wave and a vertical polarization wave) to transmit two signals.
Add/Drop multiplexer Adjacent channel alternate polarization
Automatic A method of adjusting the transmit power based on fading of the transmit transmit power signal detected at the receiver. control
Issue 02 (2009-10-30)
C-1
C Glossary
Co-channel dual polarization Cross polarization interference cancellation
A channel configuration method, which uses a horizontal polarization wave and a vertical polarization wave to transmit two signals. The cochannel dual polarization is twice the transmission capacity of the single polarization. A technology used in the case of the co-channel dual polarization (CCDP) to eliminate the cross-connect interference between two polarization waves in the CCDP.
D DC-C A power system, in which the BGND of the DC return conductor is shortcircuited 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 shortcircuited with the PGND on the output side of the power supply cabinet and is isolated from the PGND on the line between the output of the power supply cabinet and the electric equipment. 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. An antenna intended to radiate or receive simultaneously two independent radio waves orthogonally polarized.
DC-I
Digital modulation Dual-polarized antenna
E Equalization A method of avoiding selective fading of frequencies. Equalization can compensate for the changes of amplitude frequency caused by frequency selective fading. A symptom that the quality of the transmitted information is degraded because some bits of a data stream are errored after being received, decided, and regenerated.
Bit error
F Forward error correction Frequency diversity 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. 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.
C-2
Issue 02 (2009-10-30)
C Glossary
G Gateway network element A network element that is used for communication between the NE application layer and the NM application layer.
H Hybrid radio The hybrid transmission of Native E1 and Native Ethernet signals. Hybrid radio supports the AM function.
I Indoor Unit The indoor unit of the split-structured radio equipment. It implements accessing, multiplexing/demultiplexing, and IF processing for services.
Internet Group The protocol for managing the membership of Internet Protocol multicast Management groups among the TCP/IP protocols. It is used by IP hosts and adjacent Protocol multicast routers to establish and maintain multicast group memberships. Intermediate frequency IGMP snooping The transitional frequency between the frequencies of a modulated signal and an RF signal. 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.
L Layer 2 switch 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. The local maintenance terminal of a transport network, which is located on the NE management layer of the transport network. 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. A type of transport entity, mainly engaged in transferring signals from the input of the trail source to the output of the trail sink, and monitoring the integrality of the transferred signals.
LCT Link aggregation group Trail
Issue 02 (2009-10-30)
C-3
C Glossary
Multiplex section protection Multiple Spanning Tree Protocol
The function performed to provide capability for switching a signal between and including two MST functions, from a "working" to a "protection" channel. MSTP is an evolution of the Spanning Tree Protocol and the Rapid Spanning Tree Protocol, and was introduced in IEEE 802.1s as amendment to 802.1Q, 1998 edition. Standard IEEE 802.1Q-2003 now includes MSTP.
N N+1 protection Network element A microwave link protection system that employs N working channels and one protection channel. A network element (NE) contains both the hardware and the software running on it. One NE is at least equipped with one system control board which manages and monitors the entire network element. The NE software runs on the system control Unit. The network management system in charge of the operation, administration, and maintenance of a network. A network element whose communication with the NM application layer must be transferred by the gateway network element application layer.
Network management system Non-gateway network element
O Orderwire Outdoor unit A channel that provides voice communication between operation engineers or maintenance engineers of different stations. The outdoor unit of the split-structured radio equipment. It implements frequency conversion and amplification for RF signals.
P Plesiochronous Digital Hierarchy Polarization 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. 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.
C-4
Issue 02 (2009-10-30)
C Glossary
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.
R Rapid Spanning Tree Protocol 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.
S Single polarized antenna Space diversity An antenna that can transmit only one channel of polarized electromagnetic waves. 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. An algorithm defined in the IEEE 802.1D. It configures the active topology of a Bridged LAN of arbitrary topology into a single spanning tree. A logical entity in the transmission network, which comprises a group of network management objects. A subnet can contain NEs and other subnets. A function, which allows a working subnetwork connection to be replaced by a protection subnetwork connection if the working subnetwork connection fails, or if its performance falls below a required level. A hierarchical set of synchronous digital transport, multiplexing, and cross-connect structures, which is standardized for the transport of suitably adapted payloads over physical transmission networks.
Spanning Tree Protocol Subnet Subnetwork connection protection Synchronous Digital Hierarchy
U U2000 A unified network management system developed by Huawei. It can support all the NE level and network level management functions, and can manage the transport network, access network, and MAN Ethernet in a unified manner.
Issue 02 (2009-10-30)
C-5
C Glossary
Virtual LAN
An end-to-end logical network that can travel through several network segments or networks by using the network management software based on the switch LAN. The IEEE 802.1Q is the main standard for the virtual LAN.
C-6
Issue 02 (2009-10-30)
D Acronyms and Abbreviations
D
A ADC AGC APS ARP ASK ATPC AU
Acronyms and Abbreviations
Acronyms and abbreviations are listed in alphabetical order.
Analog Digit Converter Automatic Gain Control Automatic Protection Switching Address Resolution Protocol Amplitude Shift Keying Automatic Transmit Power Control Administrative Unit
B BER BIOS BIP BPDU BSC Bit Error Rate Basic Input Output System Bit-Interleaved Parity Bridge Protocol Data Unit Base Station Controller
C CAR CBS CCDP CF CGMP

Issue 02 (2009-10-30)
Committed Access Rate Committed Burst Size Co-Channel Dual Polarization Compact Flash card Cisco Group Management Protocol
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. D-1
CIR CIST CoS CPU CRC CVLAN C-VLAN
Committed Information Rate Common and Internal Spanning Tree Class of Service Central Processing Unit Cyclic Redundancy Check Customer VLAN Customer VLAN
D DC DCC DCN DSCP DVMRP Direct Current Data Communications Channel Data Communication Network Differentiated Services Code Point Distance Vector Multicast Routing Protocol
E ECC E-LAN EMC EMI ERPS ES-IS ETSI Embedded Control Channel Ethernet-LAN Electromagnetic Compatibility Electromagnetic Interference Ethernet Ring Protection Switching End System to Intermediate System European Telecommunications Standards Institute
F FCS FD FE FEC FIFO FLP FPGA Frame Check Sequence Frequency Diversity Fast Ethernet Forward Error Correction First In First Out Fast Link Pulse Field Programmable Gate Array
D-2
Issue 02 (2009-10-30)
FTP
File Transfer Protocol
G GE GFP GTS GUI Gigabit Ethernet Generic Framing Procedure Generic Traffic Shaping Graphical User Interface
H HDB3 HDLC HSB HSM High Density Bipolar Code 3 High level Data Link Control procedure Hot Standby Hitless Switch Mode
I ICMP IDU IEC IEEE IETF IF IGMP IP IPv6 IS-IS ISO ITU-T IVL Internet Control Message Protocol Indoor Unit International Electrotechnical Commission Institute of Electrical and Electronics Engineers The Internet Engineering Task Force Intermediate Frequency Internet Group Management Protocol Internet Protocol Internet Protocol version 6 Intermediate System to Intermediate System International Standard Organization International Telecommunication Union - Telecommunication Standardization Sector Independence VLAN learning
L LAN LAPD
Issue 02 (2009-10-30)
Local Area Network Link Access Procedure on the D channel

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd. D-3
LAG LAPS LB LCT LDPC LMSP LPT
Link Aggregation Group Link Access Procedure-SDH LoopBack Generation-Local Craft Terminal Low-Density Parity Check code Linear Multiplex Section Protection Link State Pass Through
M MA MAC MADM MBS MD MDI MEP MIB MP MSP MSTP MTBF MTTR MTU Maintenance Association Medium Access Control Multi Add-Drop Multiplexer Maximum Burst Size Maintenance Domain Medium Dependent Interface Maintenance End Point Management Information Base Maintenance Point Multiplex Section Protection Multiple Spanning Tree Protocol Mean Time Between Failure Mean Time To Repair Maximum Transmission Unit
N NE NLP NMS NNI NSAP Network Element Normal Link Pulse Network Management System Network-to-Network Interface or Network Node Interface Network Service Access Point
D-4
Issue 02 (2009-10-30)
OAM ODU OSI OSPF
Operations, Administration and Maintenance Outdoor Unit Open Systems Interconnection Open Shortest Path First
P PDH PIM-DM PIM-SM PIR PPP PRBS Plesiochronous Digital Hierarchy Protocol Independent Multicast-Dense Mode Protocol Independent Multicast-Sparse Mode Peak Information Rate Point-to-Point Protocol Pseudo-Random Binary Sequence
Q QinQ QoS QPSK 802.1Q in 802.1Q Quality of Service Quadrature Phase Shift Keying
R RF RFC RIP RMON RNC RS RSL RSSI RSTP RTN Radio Frequency Request For Comment Routing Information Protocol Remote Monitoring Radio Network Controller Reed-Solomon encoding Received Signal Level Received Signal Strength Indicator Rapid Spanning Tree Protocol Radio Transmission Node
S SD Space Diversity
Issue 02 (2009-10-30)
D-5
SDH SFP SNC SNCP SNMP SNR SP SSM STM STM-1 STM-1e STM-1o STM-N STP SVL
Synchronous Digital Hierarchy Small Form-Factor Pluggable SubNetwork Connection Sub-Network Connection Protection Simple Network Management Protocol Signal-to-Noise Ratio Strict Priority Synchronization Status Message Synchronous Transport Module SDH Transport Module -1 STM-1 Electrical Interface STM-1 Optical Interface SDH Transport Module -N Spanning Tree Protocol Shared VLAN Learning
T TCI TCP TDM TMN TU Tag Control Information Transfer Control Protocol Time Division Multiplex Telecommunication Management Network Tributary Unit
U UDP UNI User Datagram Protocol User-Network Interface
V VC VC12 VC-12 VC3 Virtual Container Virtual Container -12 Virtual Container -12 Virtual Container -3
D-6
Issue 02 (2009-10-30)
VC-3 VC4 VC-4 VCG VLAN VoIP VPN
Virtual Container -3 Virtual Container -4 Virtual Container -4 Virtual Concatenation Group Virtual LAN Voice over IP Virtual Private Network
W WAN WRR WTR Wide Area Network Weighted Round Robin Wait to Restore Time
X XPD XPIC Cross-Polarization Discrimination Cross-polarization Interference Cancellation
Issue 02 (2009-10-30)
D-7

OptiX RTN 950 Hybrid Feature Description

Uploaded by

Document Information

Original Description:

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

OptiX RTN 950 Hybrid Feature Description

Uploaded by

Copyright:

Available Formats

OptiX RTN 950 Radio Transmission System V100R002C00

HUAWEI TECHNOLOGIES CO., LTD.

Trademarks and Permissions

Huawei Technologies Co., Ltd.

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

OptiX RTN 950 Feature Description

About This Document

About This Document

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

About This Document

OptiX RTN 950 Feature Description

Chapter 1 Introduction to the DCN

3 IP over DCC Solution

4 OSI over DCC solution

5 DCC Transparent Transmission Solution

6 DCC Transparent Transmission Through the External Clock Interface Solution

7 Inband DCN Solution

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

OptiX RTN 950 Feature Description

About This Document

11 Cross-Polarization Interference Cancellation

13 Automatic Transmit Power Control

14 Adaptive Modulation 15 Subnetwork Connection Protection

16 Linear Multiplex Section Protection

17 Ethernet Ring Protection Switching

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

About This Document

OptiX RTN 950 Feature Description

Chapter 19 IGMP Snooping

20 Link Aggregation Group

21 Link State Pass Through

25 Remote Network Monitoring

B Parameters Description C Glossary D Acronyms and Abbreviations

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

OptiX RTN 950 Feature Description

About This Document

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

About This Document

OptiX RTN 950 Feature Description

Updates in Issue 02 (2009-10-30) Based on Product Version V100R002

Updates in Issue 01 (2009-06-30) Based on Product Version V100R002

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd.

OptiX RTN 950 Feature Description

3 IP over DCC Solution................................................................................................................3-1

OptiX RTN 950 Feature Description

4 OSI over DCC solution.............................................................................................................4-1

5 DCC Transparent Transmission Solution.............................................................................5-1

6 DCC Transparent Transmission Through the External Clock Interface Solution........6-1

OptiX RTN 950 Feature Description

7 Inband DCN Solution...............................................................................................................7-1

OptiX RTN 950 Feature Description

OptiX RTN 950 Feature Description

11 Cross-Polarization Interference Cancellation...................................................................11-1

13 Automatic Transmit Power Control...................................................................................13-1

OptiX RTN 950 Feature Description

15 Subnetwork Connection Protection...................................................................................15-1

OptiX RTN 950 Feature Description

16 Linear Multiplex Section Protection...................................................................................16-1

17 Ethernet Ring Protection Switching...................................................................................17-1

OptiX RTN 950 Feature Description

20 Link Aggregation Group......................................................................................................20-1

OptiX RTN 950 Feature Description

21 Link State Pass Through.......................................................................................................21-1